01. GENERAL DATA
Product | |
Product Line | Protheus Line |
Segment | Services |
Module | TOTVS Backoffice (Protheus Line) - Managerial Accounting (SIGACTB) 






|
Function | Efetivação (CTBA350) |
Country | Brazil |
Ticket | 19125366 |
Requisite/Story/Issue | DSERCTR1-44381 |
02. STATUS/REQUIREMENT
Change the entry confirmation after validations.
03. SOLUTION
At this EFELANC entry point, the record is positioned right after confirmation (or not), making it possible to change the result.

04. FURTHER INFORMATION
The entry point will be positioned immediately after the entry confirmation.
In this example, the balance type is being changed.
EFELANC – Handles the record after confirmation (or not).
Requirement Characteristics. Description: | The entry point EFELANC allows handling of the record right after confirmation (or not) within the CTBA350 – Pre-Entry Confirmation routine. | Events: | ExistBlock("EFELANC") | Source Program: | CTBA350.PRW | Function (EP): | EFELANC() – Allows handling the record of whether or not it was executed in the CTBA350 – Pre-Entry Execution routine. | Parameters: | None. | Return: | None. |
#Include "Protheus.ch"
// // adjusts the record in CT2 after finalization/entry. Routine ctba350 - Pre-Entry finalization.
User Function EFELANC()
Local aArea := GetArea()
IF EMPTY(CT2->CT2_ITEMD)
RECLOCK( 'CT2', .F. )
CONOUT("record : " + STR(CT2->(RECNO())) + " positioned ")
CT2->CT2_TPSALD := "9"
CT2->(MSUNLOCK())
ENDIF
RestArea(aArea)
Return |
This Entry Point is triggered exclusively for accounting entry that do not present inconsistencies, meaning those that are finalized directly. Entries with inconsistencies, however, are not recorded, and when displayed on screen (Question "Show Acct. Entry?" = Yes), they must be corrected by the user, being processed by another system flow in that case. |
|
05. RELATED SUBJECTS
