ENTRY POINTUnder review

F430COMP

User Function F430COMP()

Runs additions after financial writes and accounting in return processing.

F430COMPFINA430

01 · OVERVIEW

Overview

Official support places execution after financial and accounting return processes. P12.2210 records FA430GER without explicit context or result assignment. EURAI’s Universo do Desenvolvedor example only contains comments and Return Nil: it implements no email, writes or integration. These sources do not establish execution after commit. (Refs. 1–4) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function F430COMP()

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 excerpt does not consume the result; the community skeleton uses Nil. This does not document every version’s contract.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA430.PRX - FA430GER() -> EXECBLOCK("F430COMP",.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

Before creating notifications, define the transaction boundary and duplicate prevention during retries. An email comment is not a sending implementation.
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.