Hierarchy
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JSD (Package) Appl. dev. R/3 Publishing Sales and Distribution System
Basic Data
| Data Element | VSPEBENE |
| Short Description | Shipping document level |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | VSPEBENE | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | SDoc.level |
| Medium | 15 | Ship.doc.level |
| Long | 20 | Shipping doc.level |
| Heading | 2 | Lv |
Documentation
Definition
The shipping document level controls access to the function module for the shipping document type in the main program for shipping document creation. This determines the dataset for which the shipping document is to be created. In addition, the shipping document level defines the accessing interface. The admissible shipping document levels depend on the shipping document type category.
The following shipping document levels are possible:
- Printing works (shipping document type category 4 = general)
A shipping document on this level is created for each printing works; that is, the function module for creating the shipping document is called up for each printing works.
- Truck route (shipping document type category 1 = truck route-oriented)
A shipping document at truck route level is accessed for each (daily) truck route.
- Unloading point (shipping document type category 1 = truck route-oriented)
A shipping document at unloading truck route level is created for each combination of truck route and unloading point and contains information on all drop-offs that are transported to the unloading point by means of this truck route.
The main program for shipping document creation (RJVSP001) calls the function module for this shipping document type according to the sort sequence. This access sequence corresponds to the unloading point sequence for the truck route, with papers at unloading point level being created before those at the delivery round and odd bundle (see below) levels.
- Delivery round (shipping document type category 1 = truck route-oriented)
A shipping document at delivery round level is created for each delivery round (to be covered by a carrier) in a carrier truck route. The assignment is to the first unloading point (from the carrier's point of view) in the carrier route. If several truck routes serve the same unloading point, the shipping documents are assigned to the first truck route.
- Odd bundle (shipping document type category 1 = truck route-oriented)
The creation program for a shipping document at odd bundle unloading point level is called up once for each odd bundle created.
- Issue (shipping document type category 2 = issue-oriented)
A shipping document at issue level is created for each issue with all unloading data for the issue in question.
Please note that the shipping document level only defines access of the creating function module and its interface.
The following levels are planned but not yet implemented:
- Postal pack/container
- Ship-to party's address
- Issue-logistical delivery type
Example
- A program for labeling edition shipments is executed once for each edition and shipping date (at issue level). One unit (page) in the shipping document contains an address.
- The function module for creating standard delivery exceptions is called up once for each odd bundle. This means that the delivery exceptions are created only for those issues that are contained in this odd bundle and the assigned full bundles. If, however, this function module is assigned to the shipping document level delivery round, all the data on a delivery round served by a carrier is transferred to the function module. All the delivery exceptions are created for an entire delivery round (with several odd bundles if applicable).
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
