Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GJVA (Package) Joint venture accounting
Basic Data
| Data Element | JV_XCP_BUKRS |
| Short Description | Company code of partner |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BUKRS | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | T001 |
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 | 9 | XC_Part.C |
| Medium | 18 | XC partner company |
| Long | 29 | Cross company partner company |
| Heading | 4 | XCPC |
Documentation
Definition
This company code is regarded as the 'partner company code' in a CO cross company posting.
If you create an entry without specifying a partner company (field is left blank), this entry will be a generic entry which is valid for any occuring partner company in a CO posting, provided that no other specific entry exists for this partner company.
If a specific partner company entry exists, its settings will prevail the settings of the generic entry.
General definition of originating- and partner- company code
CO cross company postings involve costobjects which belong to the same controlling area, but to different company codes.
A cost allocation between those objects will create CO line items for each participating CO object and its partner object.
Each CO line item is the data source for a JV line item.
The company code of the CO object, to which the CO line item belongs is regarded as the 'originating' company code, while that of the partner object is regarded as the 'partner compay code'.
For details on cross company customizing see the corresponding chapter of the JV implementation guide
History
| Last changed by/on | SAP | 20020108 |
| SAP Release Created in |
