This routine was adjusted to comply with the General Personal Data Protection Law (Statute No. 13.70), so that some fields containing data regarded as sensitive and/or personal are blurred, becoming illegible. |
The Settlement routine (FINA460) allows you to negotiate and renegotiate bills.
With the product evolution, the Invoices receivable routine (FINA280) was incorporated by the Settlement routine and was discontinued from version 12.1.17. |
Use esse espaço para colocar exemplos de utilização.
Add this segment when displaying the settlement screen
as also the NCC clearance process using settlement. For this process, use the clearance routine (FINA330).
|
You can associate accessory values to the bills generated by the settlement process:
For further information, check Accessory Values on Accounts Receivable.
Main Fields and Parameters
| Field | Description |
|---|---|
| Inclua o campo | Inclua a descrição relacionada |
| Inclua o campo | Inclua a descrição relacionada |
| Inclua o campo | Inclua a descrição relacionada |
The standard accounting entries remain the same for the inclusion of bills and the posting of settled bills.
What has been added is the view of the values from the FO2 table of the generated bills, which can be changed in the standard entry to identify whether the record originates from the settlement routine.
SE | Description |
500 | When bills are added to Accounts Receivable |
505 | When bills are deleted from Accounts Receivable |
520 | When posting Simple Collection/Protest/Agreement Bills in Accounts Receivable (0/F/G) |
521 | When posting Simple Collection/Notary Bills in Accounts Receivable (1/H) |
522 | When posting Discounted Collection Bills in Accounts Receivable (2) |
523 | When posting Pledged Collection Bills in Accounts Receivable (3) |
524 | When posting Linked Collection Bills in Accounts Receivable (4) |
525 | When posting Collection with Attorney Bills in Accounts Receivable (5) |
526 | When posting Legal Collection Bills in Accounts Receivable (6) |
527 | When cancelling a bill posting in Accounts Receivable |
528 | When posting Pledged Collection Bills in Accounts Receivable (7) |
598 | When generating monetary variation, i.e., settlement and generation of new bills in the same currency (except when currency 1) |
595 (Discontinued) | At the generation of Invoice Receivable |
592 (Discontinued) | At the cancellation of Invoice Receivable |
The invoice LPs of FINA280 will no longer work since their functionality has been absorbed by the FINA460 routine.
The routine was developed over MVC technology, and some functionalities were revised. One of the affected points was the use of entry points with the use of technology that now works as per the documentation below
Entry points for Advpl sources developed using the MVC concept
Most of the entry points were maintained, but some must be reviewed according to the documentation above on the MVC technology.
List of Entry Points:
Entry Point/Documentation | Function | Notes |
|---|---|---|
A460Liquid | Kept functionality | |
A460Liquid | Kept functionality | |
F460SAID | A460Liquid | Replace with FORMCANCEL |
F460GRV | A460Liquid | Replace with MODELCOMMITNTTS |
A460Liquid | Entry point for adding columns in the GetDados of the bill generation screen. Not contemplated in the source because of the technological change, from GetDados to MVC. The customer can create a field in FO2 directly. Discontinued. | |
A460Liquid | Replace with BUTTONBAR | |
F460CAN | A460Liquid | Kept functionality |
F460CON | A460Liquid | Kept functionality |
FA460LOK | a460OK | Replace with FORMLINEPRE |
A460VALLIN | a460OK | Replace for FORMLINEPRE |
a460TudoOK | Replace with FORMCOMMITTTSPRE | |
A460ChecF | Kept functionality | |
A460ChecF | Kept functionality | |
A460Grava | Kept functionality | |
A460Grava | Kept functionality | |
A460Grava | Kept functionality | |
A460Grava | Kept functionality | |
A460Grava | Kept functionality | |
A460Grava | Kept functionality | |
F460CTB | A460Grava | Kept functionality |
A460Cond | Kept functionality | |
A460Cond | Replace with FORMPOS | |
FA460CAN | Kept functionality | |
FA460CAN | Kept functionality | |
FA460CAN | Kept functionality | |
Fa460Repl | Kept functionality | |
Fa460Repl | Kept functionality | |
Fa460Bar | Bill selection screen replaced by GRID from table FO1. Discontinued. | |
Fa460Bar | Bill selection screen replaced by GRID from table FO1. Discontinued. | |
Fa460Edit | Edit button removed in the new structure, replaced with the field edit directly on screen. Discontinued. | |
Fa460Edit | Edit button removed in the new structure, replaced with the field edit directly on screen. Discontinued. | |
Fa460Edit | Edit button removed in the new structure, replaced with the field edit directly on screen. Discontinued. | |
Fa460OK1 | Kept functionality | |
F460CMC7 | Kept functionality | |
F460Cmc7Tc | Kept functionality | |
MenuDef | Kept functionality | |
FA460LiqOk | Kept functionality | |
F460AIncl | Allows viewing or blocking the parameter screen for filtering the bills to be settled. | |
MenuDef | Allows the inclusion of new buttons in the Menudef routine in FINA460A | |
FINA460A | Allows the inclusion of a customized filter for presenting the screen with bills to be settled and/or settlement simulation. | |
FINA460LOAD | Allows the manipulation of generated installments. |
1913202 DSERFINR-7466 DT Interest value field blocked in the settlement receivable.
1703939 DSERFINR-6189 DT Add interest/fine value in the settlement receivable.
FIN0081_CREC_Gatilho_Juros_liquidação
For technical reasons, the settlement routine validates the E1_FILORIG field to position it correctly in its records and avoid competition between users, so sharing FO0, FO1, and FO2 does not influence the routine's behavior.
<!-- esconder o menu -->
<style>
div.theme-default .ia-splitter #main {
margin-left: 0px;
}
.ia-fixed-sidebar, .ia-splitter-left {
display: none;
}
#main {
padding-left: 10px;
padding-right: 10px;
overflow-x: hidden;
}
.aui-header-primary .aui-nav, .aui-page-panel {
margin-left: 0px !important;
}
.aui-header-primary .aui-nav {
margin-left: 0px !important;
}
</style>
|