ENTRY POINTUnder review

SE5FI460

User Function SE5FI460()

Movement extension in receivable settlement.

SE5FI460FINA460

01 · OVERVIEW

Overview

The official FINA460 migration map retains this functionality and associates it with A460Grava. P12.2210 shows calls in F460ACommit and FaBaixaCR without a fourth argument; the name Commit does not establish that the outer transaction ended. No specific parameter/return contract or useful GitHub implementation was recovered. (Refs. 1–2) Research includes indexed TDN evidence; no complete specific page was recovered.

02 · SYNTAX

Syntax

User Function SE5FI460()

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; 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.
// FINA460A.PRW - F460ACOMMIT() -> EXECBLOCK('SE5FI460',.F.,.F.)
// FINXAPI.PRX - FABAIXACR() -> EXECBLOCK("SE5FI460",.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

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.