Ansicht
Dokumentation
VC_FCO_ICO_RSTR_L - Block Intercompany Postings
BAL Application Log Documentation Vendor Master (General Section)This documentation is copyright by SAP AG.
You configure how intercompany (ICO) postings are handled for the following transactions:
| Transaction | App, Fiori UI |
|---|---|
| Time recording, timesheet postings | Manage Direct Activity Allocation (F3697) |
| Manage My Timesheet (F1823) | |
| Activity allocation reposting | Manage Direct Activity Allocation (F3697) |
| Manual supplier invoice | |
| Expense posting through Concur integration | |
| Settlement | Schedule Overhead Accounting Jobs (F3767) |
| Run Settlement - Actual (F4568) | |
| CO assessments/allocations | Schedule Overhead Accounting Jobs (F3767) |
| Overhead calculation, periodic and event-based | Schedule Overhead Accounting Jobs (F3767) |
| Run Overhead Calculation - Actual (F4857) | |
| Manual cost allocation | Reassign Costs and Revenues (F2009) |
| Manual reposting | Reassign Costs and Revenues (F2009) |
You can select one of the following options:
General Settings
- Allow All ICO Postings
- All ICO postings are allowed. This is the default setting.
- Block All ICO Postings
- No ICO postings are allowed.
- Allow Only Listed ICO Postings
- A defined allowlist for certain sender/receiver company code combinations is applied (see Allowlist Configuration). Sender/receiver company code combinations that are not listed will be blocked.
Allowlist Configuration
Before you configure the allowlist, make sure you select the Allow Only Listed ICO Postingsoption under General Settings.
Here you can configure an allowlist for intercompany postings. For a defined company code (one sender company), you can allow all types of intercompany postings to another company code (one receiver company).
Additionally, you can select whether bidirectional postings are allowed. Bidirectional means that posting is allowed from the sender to the receiver company code as well as from the receiver company code to the sender company code.
Note:
The ICO posting restrictions that you define in this activity only apply to postings that are made after the configuration is enabled and have no effect on earlier postings. No tool is available to check actual data, and no report can identify earlier postings that do not match the defined restriction criteria.
Allowlist: Valid Entries
| Sender Company Code | Receiver Company Code | Bidirectional | Result |
|---|---|---|---|
| A | B | No | ICO postings from company code A to company code B are allowed |
| A | B | Yes | ICO postings from company code A to company code B are allowed and vice versa |
| A | Blank | No | ICO postings from company code A to all company codes are allowed |
| A | Blank | Yes | ICO postings from company code A to all company codes are allowed and vice versa |
| Blank | B | No | ICO postings from all company codes to company code B are allowed |
| Blank | B | Yes | ICO postings from all company codes to company code B are allowed and vice versa |
Allowlist: Invalid Entries
| Sender Company Code | Receiver Company Code | Bidirectional | Result |
|---|---|---|---|
| Blank | Blank | Yes/No | Allowlist entry is empty and cannot be saved |
| A | A | Yes/No | Sender and receiver company code entry are identical and cannot be saved |
