F300SE5
User Function F300SE5()Runs after bank movement recording in the former SISPAG return process.
Overview
The official table describes F300SE5 after recording the FINA300 bank movement record and lists no equivalent. SISPAG was discontinued on 2022-08-20, with migration to the FINA430 suite. (TOTVS, ref. 1) The P12.2210 listing places the call in FA300PROCESSA, without a fourth argument or result assignment. (Ref. 2) The former specific page at https://tdn.totvs.com/x/XzowGg reports that it was deleted; its content was not recovered or used to fill missing contracts.
Syntax
User Function F300SE5()Return value
Unconfirmed by accessible sources. The listed call does not assign a result; the diagnostic Return NIL is not presented as an official contract or a settlement confirmation command. (Ref. 2)
Identify invocation after recording in legacy testing
#Include "Protheus.ch"
User Function F300SE5()
// Editorial diagnostic: TOTVS purpose (ref. 1), EURAI call (ref. 2).
// After record writing does not establish transaction commit.
// Fixed message; assumes no SE5 positioning and performs no writes.
ConOut("F300SE5: legacy call identified")
Return NilProposes logging invocation only in the legacy flow. Does not change SE5 or start external integrations. Example not compiled or run in Protheus.
- After recording does not establish commit or final persistence.
- The SE5 name does not prove that the alias is open or the expected record positioned. Check caller context before reading fields.
- The former page was deleted. Parameter and return gaps remain explicit instead of being reconstructed by analogy.
- Do not automatically replace this with F330AE5E, which belongs to FINA330 receivable compensation reversal, a different process.
- Editorial test plan: compare standard and customized behavior in the described operations, inspect resulting records and record release and patch.
- Under review: sources and example checked against documentation; code not compiled or run in Protheus. Exact transaction position and target release behavior remain unconfirmed.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.