F90TOTGRV
User Function F90TOTGRV()Complements the automatic settlement totalizer record.
Overview
The specific page describes the totalizer record and states that parameters do not apply. Its example changes illustrative E5_MEUCPO in SE5; the block caption mistakenly mentions F090FIL while the displayed function is F90TOTGRV. P12.2210 records calls in FINA090 and FINA091. The editorial diagnostic does not reproduce that write. (Refs. 1–2)
Syntax
User Function F90TOTGRV()Return value
The page has no detailed return section; the example ends without an explicit value. Caller excerpts contain no assignment.
Editorial example based on documentation
#Include "Protheus.ch"
User Function F90TOTGRV()
// Totalizer diagnostic; no SE5 writes.
ConOut("F90TOTGRV: totalizer extension")
Return NilTeaching 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.
Observed call and context
// P12.2210 caller excerpt (EURAI, ref. 2); not an entry point implementation.
// FINA090.PRX - FA090AUT() -> EXECBLOCK("F90TOTGRV")
// FINA091.PRX - FA091AUT() -> EXECBLOCK("F90TOTGRV")The record shows arguments and immediate return use where present. It omits the full caller body and does not establish commit timing.
- Do not confuse the totalizer record with each settled title. Before writing, verify the current record, fields and locks. The page does not establish 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.

Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.