English
Español
AGR0231 - Events
The Events - AGR0231 registration screen is fundamental for using the mão de obra modules, payments (closing), third-party services, variable compensation (RV) and scheduled calculations (CPG).
Most Events are standard system records, however it may be possible and necessary to register Events according to the client’s scenario, as well as change descriptions and codes of standard events as needed or even to comply with state legislation, given that some of these events will later be displayed in Invoices, information and production reports, as is the case with tax events.
Some events are considered in integration routines, therefore, they must reflect events in ERP systems. In this scenario, some events must have identical codes between the SimpleFarm system and the ERP, thus allowing the traceability of information between them.
Events are used in routines and logs of these modules, and can be informative, events considered only during the processing of routines, or “final” events, that is, events that will record values that will later be sent to ERPs or used in reports and statements delivered to employees, customers and suppliers.
Important
Event records are used in routines of the Labor, Payments (Closing), Third-Party Services, Variable Compensation (RV) and Scheduled Calculations (CPG) modules, which are executed respectively through the screens:
- Executar Rotinas (AGR0226), Executar Rotinas (PAG0226), Executar Rotinas (PAG0002), Executar Rotinase (PAG0371), PAG0371 - CPG - Executar Cálculos / Importações.
In addition, the results of routine executions are displayed through their respective Calculations, Processings (batches) and Events on the screens:
What can you do?
- Access the menu Agricultural > Labor > Events (AGR0231);
- Click on Add ;
- To perform the registration, the following fields must be filled in:
- Code: mandatory field, allows alphanumeric values. In some cases, this field must be filled in with the same event code that is related in the ERP;
- Identifier :non-mandatory field, must be filled in for events used in the Routines of the modules described above. For “System Events” this field must be locked for editing, given that its information is standard within the Routine codes;
- Description : mandatory field, the description of the event in question must be entered. This field, regardless of the event type, can be defined as needed;
- Event Type : non-mandatory field, must be used in valuation Events, whether these Events are logged or verified in routines, it must be defined whether the Event will be Debit or Credit;
- Order : organizational registration, not mandatory. When informed, on some screens of the Payments module, the system will respect the order defined in the respective records for the display of events;
- Event Group : non-mandatory field, searches for information from the PAG0210 - Grupo de Eventos record. In addition to being an organizational record for displaying items in the initial grid of the Eventos (AGR0231) screen, the information can be used as a filter in the same grid;
- Relationships :
- Events : non-mandatory field, can be used to relate two events to each other. Created to meet specific routine scenarios, currently without use in standard routines;
- Analyses : non-mandatory field, searches for information from the Análises (BAL0097) screen. Can be used to relate a specific analysis to the event. Created to meet specific routine scenarios, currently without use in standard routines;
- Auxiliary Event - No effect for Transactions : selection field that is inactive by default. Must be active in Events that should not be considered in routines and calculations, whether as Debit or Credit, in this case, informational Events only;
- System Event : selection field unavailable for change. This field is automatically filled by the system. When active, it indicates that that event is standard in the system and routines, therefore, it cannot be deleted and its Identifier cannot be changed, as it could impact the execution of processes;
- Export to payroll : selection field that is inactive by default. For production events in the Labor module, which must be integrated with the ERP, this selection field must be Active. When activating it, the system presents the Operações Relacionadas tab, in which the operations to be used later in the integration “from/to” must be informed;
- Do not apportion by contract : selection field that is inactive by default. For some scenarios of apportioning Invoices between Contracts and Rural Properties, some Events used in the Monthly Invoice, Adjustment (Partial and Closing) and Bonus Routines of the Payments module (example: Unit Value, ATR Value, ATR, Percentage Paid NF, Net Unit Value) should not be apportioned, for this, it is necessary to activate the selection field so that at the time of Routine Execution, such values are not apportioned, allowing the correct generation of invoices according to the defined apportionment;
- Click the Save button to record the registration.
- When the selection field Export to payroll is active for the event in question, this tab will be available to insert the operations and units of measurement that will be related to the event and used later in the “from/to” between SimpleFarm and the ERP system. In this case, depending on the client’s needs, the values of the production logs from the Labor module can be grouped into different SimpleFarm events, and can have, for each one of them, different operations and units of measurement, which will be reflected in certain events within the client’s ERP system, making it possible to identify different origins of employee payroll payment values, according to the parameterization performed;
- Click the Save button to register the record.
English
Español
