ENTRY POINTUnder review

FINSALTIT

User Function FINSALTIT()

Adjusts amounts used in receivable settlement.

FINSALTITFINXBX

01 · OVERVIEW

Overview

The index describes settlement-amount adjustment. P12.2210 shows two FA070GRV forms: adding the return to nValPadrao without a fourth argument and adding it to nValRec for E1_VALLIQ with direct context 2. Do not treat that scalar as PARAMIXB[1] or assume the return is an absolute replacement total. 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 FINSALTIT()

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

Value added by the caller; formula and meaning of context 2 pending.

03 · PRACTICAL EXAMPLE

Observed call and context

// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINXBX.PRX - FA070GRV() -> NVALPADRAO += EXECBLOCK("FINSALTIT")
// FINXBX.PRX - FA070GRV() -> REPLACE E1_VALLIQ WITH NVALREC + EXECBLOCK("FINSALTIT", .F.,.F., 2)

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.