ENTRY POINTUnder review

F330FLTC

User Function F330FLTC()

Participates in cancellation exemption in FINA330.

F330FLTCFINA330

01 · OVERVIEW

Overview

The historical page describes cancellation exemption but its syntax says Nil and its return section combines “Nil (logico)” with .T./.F. The P12.2210 listing uses the result in a condition with lF330FLTC without showing the IF body. Each value’s operational consequence remains unconfirmed. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function F330FLTC()

Parameters

Entry point context

UnconfirmedContext to confirm

The available excerpt does not document the complete contract. Observed names and arguments are preserved in the caller example.

Return value

The source suggests a logical return but is inconsistent and does not explain polarity. Do not choose .T., .F. or NIL by analogy.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA330.PRX - FA330DESC() -> IF LF330FLTC .AND. EXECBLOCK("F330FLTC",.F.,.F.)

Expected result

The record shows arguments and immediate return use where present. It omits the full caller body and does not establish commit timing.

BEST PRACTICES

Inspect the complete FA330DESC IF and test exempt and nonexempt titles, checking reversal, selection and movements.
A call without a fourth argument does not document a PARAMIXB layout. Preserve caller identifiers and do not invent fields or positions.
Test plan: compare standard and customized flows, exercise success, rejection and repetition, and inspect balances, movements and accounting as applicable.
Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.