Hierarchy
FI-CA (Software Component) FI-CA⤷
FI-CA (Application Component) Contract Accounts Receivable and Payable⤷
FKKOI (Package) FI-CA: Outbound Interface for GPART Items
Basic Data
| Data Element | XAGGVKONT_OI_KK |
| Short Description | Transfer at Contract Account Level |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | AGGREGATION_CONT_ACCT | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Cont. Acct |
| Medium | 20 | Tfr at Contr.AcctLvl |
| Long | 40 | Transfer at Contract Account Level |
| Heading | 50 | Transfer at Contract Account Level |
Documentation
Definition
Transfer at contract account level
Use
If you set this indicator for an external system, when you post to a business partner, a trigger entry is saved with this business partner and the contract account posted to.
Dependencies
This means that on the subsequent transfer of open items to the external system, all items for this business partner and contract account are transferred regardless of the contract posted to. Documents from other contract accounts are not transferred unless there is a separate trigger entry with the other contract account.
The prerequisite is that the transfer of open items has been activated in the company code and for the external system.
Notes
You can use the transfer at contract account level, for example, if you work with several external systems that are each to receive only part of the documents dependent on the contract account category. In this case, you have to define an own implementation for event 3800 Outbound Interface: Filter Triggers and Receiver Determination and delete the trigger dependent on the contract account category.
Example
You are working with an external system S1 and have activated the transfer at contract account level for this system.
Business partner BP1 has two contract accounts, CA1 and CA2, each with a contract C1 and C2. There are documents for both contract accounts and the related contracts that have already been transferred to the external system for information purposes in previous mass runs. A new document with business partner BP1, contract account CA1, and contract C1 is posted.
This leads to a trigger entry for open items with system = S1, business partner = BP1, contract account = CA1, and contract = space.
In the next transfer to the external system S1, all open line items of business partner BP1 with contract account CA1 are transferred. Documents for contract account CA2 are not transferred.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 473 |
