ENTRY POINTUnder review

FA110SE5

User Function FA110SE5()

Complements data after SE5 is written in automatic receivable settlement.

FA110SE5FINA110

01 · OVERVIEW

Overview

The specific page documents execution after SE5 is written and a null return. P12.2210 records ExecBlock in FA110AUT without a fourth argument. This does not establish completed commit or authorize arbitrary field writes. The editorial example only records the call without changing bank movements. No useful GitHub implementation was found. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function FA110SE5()

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

Nil according to the specific page.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function FA110SE5()
    // Editorial diagnostic after the documented write; no field writes.
    ConOut("FA110SE5: settlement extension")
Return Nil

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.
// FINA110.PRX - FA110AUT() -> EXECBLOCK("FA110SE5",.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.