SAP ABAP Data Element WLF_CROSS_COMPANY (AB: Cross-Company Code Payment Documents)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ LO-AB (Application Component) Agency Business (Global Trade)
⤷ WZRE (Package) Agency Business
⤷ LO-AB (Application Component) Agency Business (Global Trade)
⤷ WZRE (Package) Agency Business
Basic Data
Data Element | WLF_CROSS_COMPANY |
Short Description | AB: Cross-Company Code Payment Documents |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | WLF_CROSS_COMPANY | |
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 | 18 | Cross-Company Code |
Long | 33 | Cross-Company Code Documents |
Heading | 45 | Cross-Company Code Payment Documents |
Documentation
Definition
In the case of cross-company-code transactions, the company code of the invoice recipient can vary from that of the invoicing party.
In the case of cross-company-code scenarios in agency business, the vendor is assigned to a different company code to that of the customer. For this scenario, two settlement requests are usually required:
- Cross-company-code sales:
- Invoicing party: Vendor in company code A
- Invoice recipient: Customer in company code B
- Internal clearing: Clearing posting between company codes A and B. In the project, this document must be generated from the first document. It can be triggered, for example, by way of a message with a special function processing type.
- Invoicing party: Creditor number of company code A in company code B
- Invoice recipient: Debtor number of of company code B in company code A
Use
Dependencies
The class-based accounting document creation must be activated.
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 604 |