ENTRY POINTUnder review

FA110TOT

User Function FA110TOT()

Complements the automatic receivable-settlement totalizer record.

FA110TOTFINA110

01 · OVERVIEW

Overview

The historical Protheus 10/11 page describes the totalizer extension. Its example saves/restores the workarea and displays a message; it does not actually write fields. P12.2210 also lists FINA910A and FINA920A calls besides FA110AUT: presence in those flows does not establish identical aliases or transactions. No useful GitHub example was found. (Refs. 1–2)

02 · SYNTAX

Syntax

User Function FA110TOT()

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

The example ends without an explicit value; calls assign no result.

03 · PRACTICAL EXAMPLE

Editorial example based on documentation

#Include "Protheus.ch"

User Function FA110TOT()
    // Adapted TOTVS example: diagnostic without a modal window.
    Local aArea := GetArea()
    ConOut("FA110TOT: totalizer extension")
    RestArea(aArea)
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("FA110TOT",.F.,.F.)
// FINA910A.PRW - A910THRLOTE() -> EXECBLOCK( 'FA110TOT', .F., .F. )
// FINA920A.PRW - A920THRLOTE() -> EXECBLOCK('FA110TOT', .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

Distinguish the totalizer from FA110SE5’s per-title extension. For batch processing, prefer a diagnostic without dialogs and establish invocation counts without inferring cardinality from repeated listing entries.
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.