ENTRY POINTUnder review

FA080CHQ

User Function FA080CHQ()

Participates in the decision on cheque consistency checking during settlement.

FA080CHQFINA080

01 · OVERVIEW

Overview

The official index describes a return indicating whether cheque consistency should be checked. P12.2210 shows lRet := ExecBlock without explicit context but does not identify the internal caller in that record. Polarity, default and all conditions were not confirmed. GitHub research found no useful example. (Refs. 1–2) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function FA080CHQ()

Parameters

Entry point context

UnconfirmedContext to confirm

The complete technical contract remains unconfirmed. Do not assume types, PARAMIXB positions or aliases beyond the evidence described.

Return value

Assigned to lRet; evidence here is insufficient to recommend .T. or .F. as a default.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA080.PRX - () -> LRET:=EXECBLOCK("FA080CHQ",.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

Do not disable consistency through a constant return without understanding affected checks. Inspect the caller and test valid and invalid cheques.
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.