Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
VV0C (Package) Customizing R/3 SD packing
IMG Activity
| ID | SIMG_HUMIDEANSSCCNWL | Maintain SSCC Generation for Each Plant / Storage Location |
| Transaction Code | S_P99_41000252 | IMG Activity: SIMG_HUMIDEANSSCCNWL |
| Created on | 19990611 | |
| Customizing Attributes | SIMG_HUMIDEANSSCCNWL | Maintain SSCC generation for each plant / storage location |
| Customizing Activity | SIMG_HUMIDEANSSCCNWL | Maintain SSCC generation for each plant / storage location |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_HUMIDEANSSCCNWL |
In this activity, you can set all parameters for generating Numbers of Shipping Units/Serialized Shipping Container Codes (NSU/SSCCs), except for those on the storage location level.
Example
Normally, your entire organization does not create more than 1,000 billion handling units per year. Therefore, you only need one ILN from which to copy the 7-digit base number into an entry (by leaving all key fields blank: plant and storage location, for example). You have previously created a number range object with a rolling 9-digit internal interval. Now you need to assign this number range object.
If you would also like to send smaller packages and manage them with NVE/SSCCs as well, you would need more than 1,000 billion NSU/SSCCs per year. In this case, you should enter another base number and a new number range object with an internal interval. Assign these to the exact plant and storage location.
Requirements
You must have previously created a number range object and an internal interval. If you want to assign NSU/SSCCs externally and you want the system to check if they lie within the valid range, you must also create an external interval.
Recommendation
If you do not want to generate specific NSU/SSCCs for individual storage locations (and/or plants), leave the storage location (and/or plant) blank, saving you time and effort since there is less information to maintain. You may add information to the individual storage location/plant entries later on if necessary.
If the number range is not sufficient for one year (the expected time period in the standard system in which no NSU/SSCC is to be repeated), you can maintain additional parameters in the same organizational unit. The number range object may not be a rolling number range object in such a case. The system selects and entry in the field Do not use?.
Further notes
The system searches for NSU/SSCC generation parameters in the following key order:
- Plant and storage location: the most detailed of the possible structures
- Warehouse number: maintain the parameters for this organizational unit in the next node
- Plant: the same parameters for all storage locations of one plant. Leave the Storage location field blank.
- Client: the same parameters for all plants. Leave the Plant field blank as well.
Note that the intervals can overlap and therefore the same number assignment is possible twice. You must ensure for your area that the intervals do not overlap.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory 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_HUMIDEANSSCCNWL | 0 | HUM0000002 | Basic functions |
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 |
| T313Y | S - Table (with text table) | SM30 | 00000001HU | Maintain SSCC generation for each plant / storage location |
History
| Last changed by/on | SAP | 19990611 |
| SAP Release Created in |
