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 | XAGGVTREF_OI_KK |
| Short Description | Transfer at Contract 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_CONTRACT | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Contract |
| Medium | 20 | Tfr at Contract Lvl |
| Long | 40 | Transfer at Contract Level |
| Heading | 50 | Transfer at Contract Level |
Documentation
Definition
Transfer at contract level
Use
If you set this indicator for an external system, when you post to a business partner, the system saves a trigger entry with this business partner, the contract account posted to, and the contract.
Dependencies
This means that on the subsequent transfer of open items to the external system, all items for this business partner, contract account, and contract are transferred. Documents from other contract accounts or contracts are not transferred unless there is a separate trigger entry with the other contract account and contract.
The prerequisite is that the transfer of open items has been activated in the company code and for the external system.
Caution
Even if you always manually post documents with a contract, in certain posting processes, such as payments on account or installment plans, that cover several contracts, there may be postings without a contract. In this case, no contract account can be specified on creation of the trigger entry for open items. The trigger entry is therefore saved with only the business partner and contract account. During the transfer, for this trigger entry, all line items with this business partner and contract account but without a contract are transferred to the external system.
If you do not want line items to be transferred to the external system without a contract in this cse, you can set the No Transfer of Documents without Contract indicator such that these trigger entries are not created. If you do not generally want to suppress these documents, alternatively you can delete this trigger before creation by implementing event 3800 Outbound Interface: Filter Triggers and Receiver Determination, or by filtering the line items affected during the transfer by implementing event 3830 Outbound Interface: Add or Filter Entries before Transfer .
Notes
You can use the transfer at contract level, for example, if you work with several external systems that are each to receive only part of the documents dependent on the contract type. 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 type.
Example
You are working with an external system S1 and have activated the transfer at contract 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 = C1.
In the next transfer to the external system S1, all open line items of business partner BP1 with contract account CA1 and contract C1 are transferred. Documents for contract account CA2 and contract C2 are not transferred.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 473 |
