F90SE5GRV
User Function F90SE5GRV()Complements SE5 after a title is settled in automatic settlement.
Overview
The specific TOTVS page allows complementary SE5 writes after a title is settled and states that parameters and return do not apply. Its example uses RecLock and illustrative E5_MEUCPO, which is not guaranteed to exist in the dictionary. The historical listing also records FINA091; this does not establish identical flow in every release. (Refs. 1–2)
Syntax
User Function F90SE5GRV()Return value
Not applicable according to the official page.
Editorial example based on documentation
#Include "Protheus.ch"
User Function F90SE5GRV()
// Editorial diagnostic at the documented stage; no illustrative field writes.
ConOut("F90SE5GRV: per-title 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 - F090BAIXA() -> EXECBLOCK("F90SE5GRV")
// FINA091.PRX - FA091AUT() -> EXECBLOCK("F90SE5GRV")The record shows arguments and immediate return use where present. It omits the full caller body and does not establish commit timing.
- The diagnostic below only identifies the call. Before writing, verify the SX3 field, positioning and RecLock result. Distinguish this per-title extension from F90TOTGRV’s totalizer extension; do not assume execution after commit.
- 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.