ENTRY POINTUnder review

FA200_02

User Function FA200_02()

Runs after recording title entry confirmation for occurrence 02.

FA200_02FINA200

01 · OVERVIEW

Overview

The specific page places this hook after entry-confirmation data is recorded for occurrence 02. Its UPAR/URET fields are incomplete or carry import errors. The GitHub example writes a constant to E1_FRMBX, saves and restores alias/order/record, but does not check RecLock success. This is a particular demonstration, not proof that the constant suits that field or current process. (Refs. 1–3)

02 · SYNTAX

Syntax

User Function FA200_02()

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

The page contains an incorrect-import marker in its return field; it does not establish that arbitrary values are valid. The available call assigns no result.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA200.PRX - FA200GER() -> EXECBLOCK("FA200_02",.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 confuse entry confirmation with financial settlement. Before writing, verify field meaning, length and allowed content, current SE1 record and lock success.
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.