Hierarchy
⤷ SD-BIL-IV-SBI (Application Component) Self-Billing Proced.
⤷ VASB (Package) Application Development R/3 Sales / Self-Billing Process
Basic Data
Data Element | DXRELNO |
Short Description | Ext. Release No. (sumJC) for Determination |
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 | 10 | Ex.Rel.No. |
Medium | 15 | Ex.Rel.No. |
Long | 20 | Ext. Release No. |
Heading | 5 | ExRNo |
Documentation
Definition
The sales document is determined via a reference number contained in a SD summarized JIT call.
Use
If you use SD summarized JIT calls for this contractor because of external schedule numbers, you may not receive your (SD) delivery number back in the respective credit advice, but the customer's external order number instead.
In this case, you have to determine the SD delivery for this external order number. If the search finds exactly 1 delivery with this external order number, the self-billing procedure is executed based on this delivery and the respective delivery-related billing document.
Dependencies
Note that further processing is only supported in this process if only 1 SD delivery is determined for an external schedule number and material.
If 2 or more SD deliveries are determined for the external schedule number and material, automatic processing is not possible in the self-billing procedure. You have to assign the transmitted data manually to the respective deliveries; you also have to perform any postings that may be required manually.
Example
History
Last changed by/on | SAP | 20030411 |
SAP Release Created in |