| Process | Message types / IDocs / scenarios |
Financial Accounting This scenario is used to merge a general ledger that is distributed cross many systems in one main system. This allows a local logistics system with its accompanying FI postings to be linked with a central accounting system. The postings can either be transferred on a line item basis or summarized as balances. | Distributed general ledger: Sending FI documents: Scenarios that must be taken into account: - Other accounting scenarios
- Distributed credit management
|
Cost center accounting A cost center accounting module that is distributed across several systems can be merged in one main system, which allows centralized controlling. In the centralized variant of this scenario, master data and transaction data is managed in the main system. In the decentralized variant, transaction data for a cost center can also be managed in a local system; in this case, only totals records are reported to the central system. | Scenarios that must be taken into account: - Other accounting scenarios
|
Internal orders This scenario enables the cross-system posting of an internal order. All transaction data is collected in the home system of the order, and settlement is also performed there. | - BAPI: InternalOrder.SaveReplica
- Internal_Order / Internal_Order01
Scenarios that must be taken into account: - Other accounting scenarios
|
Special ledgers The data contents of a special ledger can be merged from several systems in one central system. The postings can be transferred summarized as balances. | Scenarios that must be taken into account: |
Consolidation This scenario involves a data transmission procedure to copy data from local systems to a centralized system for consolidation. Data can be taken from the consolidation staging ledger or any other ledger. | Scenarios that must be taken into account: - Financial Accounting
- Special ledgers
|
Treasury Workstation The Treasury Workstation allows you to model treasury processes like liquidity analysis or risk analysis in distributed systems. To achieve this, the required data from the local systems is transferred to the central system via Cash Management. In addition, FI-relevant information from the central Treasury Workstation can be sent back to the local (operative FI) systems. | Scenarios that must be taken into account: |
Profitability analysis The local profitability analysis from several local systems can be merged in one central system, which makes both local and cross-system analyses possible. The postings for costing-based profitability analysis can be transferred either on a line item basis (transaction-specific) or accumulated. | Costing-based profitability analysis: Account-based profitability analysis: Scenarios that must be taken into account: - Financial Accounting
- Product cost controlling
|
Distribution of product cost controlling after profitability analysis The cost component split of the costing is required to determine the contribution margin in profitability analysis. If the costing is calculated in a different system than the profitability analysis, the cost component split will also have to be distributed in this scenario. | COPCPA / COPCPA02 Scenarios that must be taken into account: |
Profit center accounting Profit center accounting that is distributed across several systems can be merged in a central system, where central controlling is possible. In the centralized variant of this scenario, the postings from a profit center are periodically transferred to the central system in summarized form. In the decentralized variant, the postings are transferred on a line item basis to the home system of the profit center, and on a summary basis to the central system. | Scenarios that must be taken into account: - Other accounting scenarios
|
