Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBAS (Package) Financial accounting 'Basis'
Basic Data
| Data Element | XGSUB |
| Short Description | Inter-company posting |
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 | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 0 | |
| Long | 20 | Inter-company postgs |
| Heading | 15 | Inter-company |
Documentation
Definition
Indicator set at document type level. It defines that within a document, account assignment can be cross-company. This means that:
- Accounts are assigned to several trading partners.
- Accounts are assigned to one or more trading partners and one group-external business partner.
It follows that the trading partner is not unique per document.
The company ID defined in the master record for this affiliated business partner cannot be transferred to all line items.
Use
Do not set the indicator in the following cases:
- The partner company is to be inherited in all line items.
Transferrence of the trading partner is mainly required for consolidation purposes, since the system requires this information on the trading partner when making elimination postings. An exception to this transfer logic occurs if you post company code clearing items to an affiliated company.
- You want to enter asset postings with this document type.
Set the indicator in the following cases:
- For business transactions where account assignment is to take place on an inter-company basis.
This is especially true of adjustment postings (see example) and postings that have no effect on sales (e.g. automatic payments).
Example
In the following case, it may be necessary to set this indicator:
Problems can arise in payment transactions if a vendor or a customer has changed its status, for example from a non-affiliated to an affiliated company. In the case of simultaneous payment of old and new items, there is therefore more than one trading partner assigned in the document. Similar problems can occur in the case of payments using several accounts. To make these postings possible, the document type must allow for the payment document to include different trading partners.
History
| Last changed by/on | SAP | 19981109 |
| SAP Release Created in |
