ENTRY POINTUnder review

F430REJ

User Function F430REJ()

Handles rejected-record data before it is cleared.

F430REJFINA430

01 · OVERVIEW

Overview

Official support describes rejected-data handling before clearing. The P12.2210 call occurs in FA430GER without a fourth argument or result assignment. No specific variable layout or useful GitHub example was recovered. The historical correspondence with FA300REJ does not authorize transferring another hook’s contract automatically. (Refs. 1–3) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function F430REJ()

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

Unconfirmed; no result assignment appears in the located excerpt.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA430.PRX - FA430GER() -> EXECBLOCK("F430REJ",.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 assume SE2 is positioned or alter rejection reasons without knowing their source. In testing, separate accepted and rejected records and ensure rejected titles are not incorrectly settled.
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.