{"id":100,"date":"2022-06-10T06:24:27","date_gmt":"2022-06-10T10:24:27","guid":{"rendered":"https:\/\/sco-solutions.com\/staging\/?p=100"},"modified":"2023-08-06T14:15:17","modified_gmt":"2023-08-06T18:15:17","slug":"workflow-de-aprobacion-de-operaciones-intracompany","status":"publish","type":"post","link":"https:\/\/sco-solutions.com\/en\/blog\/workflow-de-aprobacion-de-operaciones-intracompany\/","title":{"rendered":"WORKFLOW FOR THE APPROVAL OF INTRACOMPANY OPERATIONS"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

From SCO Solutions we have supported different clients from multiple industries to respond to challenges through innovative technological solutions that generate true value. On this occasion, we share with you\u00a0a solution that we developed for a Multinational<\/strong>\u00a0which required having a functionality that can record and identify transactions between business units (Intracompany) in accounting in order to obtain information for management purposes (reporting holding and local analysis), the Balance Sheet, Income Statement in each of SAP systems corresponding to two different business lines, as well as complying with regulatory requirements of the energy sector.<\/p>

What was done to respond to this requirement?<\/strong><\/p>

Two automatic posting programs were created, one for each line of business (that is, one in each SAP system) for intracompany transaction postings. The above is processed with a single transaction Z , to be executed from either of the two systems. The SAP system from where the process starts is considered as the sender system and consequently the other SAP system will be the receiver, considering:<\/p>