ENTRY POINTUnder review

F340GERNDF

User Function F340GERNDF()

Complements fields used when adding the NDF generated by compensation.

F340GERNDFFINA340

01 · OVERVIEW

Overview

TDN documents an array of fields to write to the NDF and shows Local aTit := PARAMIXB without [1]. The P12.2210 call also passes aTit directly and uses the result in a340GerNDF. The page names FINXATU/FA340GeraNDF, while the listing names FINA340/F340GERDIC; verify this version difference. Each field’s inner layout is undocumented here. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function F340GERNDF()

Parameters

PARAMIXB / aTit

ArrayExecution context

Direct NDF field array; inner layout not detailed. (Refs. 1–2)

Return value

Array containing all fields for NDF addition. Preserve received fields when adding custom rules.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function F340GERNDF()
    // Adapted from the TOTVS direct-context example (ref. 1).
    Local aFields := AClone(PARAMIXB)
    // Retains all fields without inventing extra field positions.
Return aFields

Expected result

Teaching proposal with behavior described in comments. Verify the context before compiling in a test environment. Under review: example not compiled or run in Protheus. Verify aliases, locks, transaction position and compatibility in the target release and patch.

04 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA340.PRX - F340GERDIC() -> A340GERNDF := EXECBLOCK("F340GERNDF",.F.,.F.,ATIT)

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 use PARAMIXB[1] as the whole array. Do not invent field/value pair layouts or change tax settings merely to reproduce the documentation.
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.