CONTENT

1. Overview

The objective of this study is the technical understanding of the use of the Monetary Variation routine (CTBA380) when in competition with another routine to determine if the routine should be run with exclusive access.

2. Usage scenario

• Account for the integration from any module; 
• perform the monetary variation using the same entities or not used in the integration;
• Observe how the Monetary Variation behaves in competition.

3. Screens

Below are scenarios from the Monetary Variation routine.

Monetary Variation:

1.  Inclusion of Fixed Assets with online accounting and ongoing accounting:

1. Variation performed simultaneously:

With the tests presented above when running these routines simultaneously with others (e.g.: Online or Offline Accounting) transaction control takes place.

The following are other analyzed scenarios that also have this behavior:

• Offline standard entry 801 with same dates and/or Entities different or not.
• Execution of the Monetary Variation routine with the same entities and/or different dates.
• Standard Entry 801 online with different entities and/or on different days. 
• Standard Entry 801 online on different days.
• Inclusions in the Automatic Accounting Entries routine simultaneously running with Monetary Variation.

4. Routines Involved

• ATFA012 - Fixed Asset;
• CTBA380 - Monetary Variation;
• CTBXATU - Generic;
• CTBA102 - Automatic Accounting Entries;
• CTBAATF - ATF Accounting.

5. Closing Remarks

       The Monetary Variation routine depends on and must be executed in exclusive mode, in order to inhibit the interpretation of inconsistencies in its execution.
       With the restructuring of the semaphores, we need to make sure that it remains exclusively enforced.