ENTRY POINTUnder review

FA340NDFGRV

User Function FA340NDFGRV()

NDF-processing call with three context elements.

FA340NDFGRVFINA340

01 · OVERVIEW

Overview

P12.2210 records {cTitAdt,cTitPrc,.F.} in F340GerDic without assigning a return. The routine index identifies the hook without defining element meanings, mutability or transaction timing. Do not transfer the F340GERNDF contract to this call. 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 FA340NDFGRV()

Parameters

PARAMIXB

ArrayExecution context

Three observed elements: cTitAdt, cTitPrc and .F.; semantic contract remains pending. (Refs. 1–2)

Return value

Unconfirmed; the excerpt shows no use of the result.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA340.PRX - F340GERDIC() -> EXECBLOCK("FA340NDFGRV",.F.,.F.,{CTITADT, CTITPRC, .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

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.