Hierarchy
⤷ LE-SHP-DL (Application Component) Delivery Processing
⤷ LEDSP (Package) Subsequent Delivery Split
IMG Activity
ID | SIMG_XXLEIDWDSPNFR | Set Number Assignment for Deliveries That Have Been Split |
Transaction Code | S_ALR_87100648 | (empty) |
Created on | 19991111 | |
Customizing Attributes | SIMG_XXLEIDWDSPNFR | Set Number Assignment for Deliveries That Have Been Split |
Customizing Activity | SIMG_XXLEIDWDSPNFR | Set Number Assignment for Deliveries That Have Been Split |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_XXLEIDWDSPNFR |
You can use this activity to define for each delivery type how the number range interval used to create delivery numbers for deliveries that were split should be determined in the decentralized Warehouse Managment system.
New deliveries are created in the decentralized Warehouse Management system during the subsequent outbound-delivery split. Delivery creation is normally only possible in the central ERP system, which is a simple way of guaranteeing the uniqueness of delivery numbers that are used to identify deliveries.
You can also operate a WM system independently and have the central system assign delivery numbers. The numbers must be generated by each WM system itself (in theory, you could set up an independent WM system for each warehouse).
You can also use a determination rule to define for each delivery type that the number range interval in this client is to be dependent on the warehouse number.
You can define the intervals for all delivery types in each warehouse number by leaving the delivery type blank.
You can also assign a separate interval for each delivery type in each warehouse.
You have already maintained intervals using the Define number ranges for deliveries activity.
The result of this activity must be that delivery number assignment is unique for all connected systems. You can achieve the same result by using the interval that is defined in the delivery type for a different number range in each system. This means that you risk interval organization that is not as transparent and you must also use this method for all delivery types.
If you want to avoid maintaining each delivery type separately, the alternative method just involves creating an additional interval for each warehouse number.
Example
Requirements
You must have already maintained the intervals that are to be reassigned in the Define number ranges for deliveries activity.
Standard settings
The standard system does not search for a number range interval for each warehouse number; it uses the delivery-type number range interval.
Recommendation
Set the determination rule for delivery types that you want to use in the decentralized WM systems so that it finds one interval for each warehouse number. Create an interval for all delivery types for each warehouse number. You can use one interval for all warehouse numbers that use the same system.
Activities
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_XXLEIDWDSPNFR | 0 | ALR0000094 | Local Operations |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
V_TVLK_NUM_DEC | V - View | SM30 | 0000000001 | Set Rule for Determining Number Range for each Delivery Type | ||
SNUM | T - Individual transaction object | VN01 | 0000000002 | Define Number Ranges for Deliveries | ||
V_TVLKN | V - View | SM30 | 0000000003 | Set Number Range Interval per Warehouse Number/Delivery Type |
History
Last changed by/on | SAP | 19991111 |
SAP Release Created in |