ENTRY POINTUnder review

FIN290NAT

User Function FIN290NAT()

Validation recorded in FINA290 nature handling.

FIN290NATFINA290

01 · OVERVIEW

Overview

P12.2210 records lRet := ExecBlock("FIN290NAT") in FA290NAT. The call passes no explicit context and omits the rule consuming lRet. Its name does not establish the nature, field or stage validated. No useful GitHub implementation was found. (Refs. 1–2) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function FIN290NAT()

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; complete acceptance policy pending.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA290.PRW - FA290NAT() -> LRET := EXECBLOCK("FIN290NAT")

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 caller in the target release before proposing an implementation. Its internal function name does not establish positioned aliases or commit timing.
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.