F070ACONT
ExecBlock("F070ACONT", .F., .F.)Runs before accounting data recording during manual settlement in FINA070.
Overview
According to the specific TOTVS documentation, F070ACONT runs within a transaction, is not invoked through automatic processing and receives no information through PARAMIXB. (TOTVS, n.d., ref. 1) Its listed call appears below. (TOTVS, n.d., ref. 2) The editorial example logs a message without opening a screen or changing data. It is under technical review: it has not been compiled or run in Protheus.
Syntax
ExecBlock("F070ACONT", .F., .F.)Return value
The system neither expects nor handles this entry point return value. (TOTVS, n.d., ref. 1)
Log invocation without user interaction
#Include "Protheus.ch"
User Function F070ACONT()
// Diagnostics avoid screens and do not read implicit parameters.
ConOut("F070ACONT: invocation observed during manual settlement")
Return
When the documented scenario invokes the entry point, the console should record the message. The message only confirms execution of the example; it does not prove successful completion of accounting or the transaction.
- Compare standard manual settlement with the same scenario using diagnostics in a test environment. Check financial and accounting results separately.
- Include automatic processing as a control scenario to check the documented invocation difference.
- If you add alias queries, preserve and restore the work areas used.
- Record the release and patch tested. Consulted documentation does not replace confirmation in the target environment.
- Treating entry point invocation as confirmation of commit.
- Reading PARAMIXB inherited from another context as an argument of this entry point.
- Using a logical return to attempt to authorize or cancel settlement without that contract.
- Adding screens that wait for a user decision during processing.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.