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_HUMIDEANSCODE | Maintain Bar Code Specification |
| Transaction Code | S_P99_41000247 | IMG Activity: SIMG_HUMIDEANSCODE |
| Created on | 19990611 | |
| Customizing Attributes | SIMG_HUMIDEANSCODE | Maintain bar code specification |
| Customizing Activity | SIMG_HUMIDEANSCODE | Maintain bar code specification |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_HUMIDEANSCODE |
A handling unit is identified by its external identification (unique). This identification and other characteristics (weight, material contained in the handling unit) are usually specified on a label on the handling unit. In addition to text script, it is becoming more and more common to use bar codes for these labels. In this step, you maintain the structure for the bar code used for this purpose.
Bar codes with a construction similar to that of the EAN 128 standard have first priority. The type and structure of the data is described in introductory data descriptor. For example, data ID "00" in the EAN128 standard defines a Number of Shipping Unit/Serialized Shipping Container Code (NSU/SSCC) with a fixed length of 18.
In the first step, you determine the name of the bar code so that it can be identified later. Then determine the minimum and maximum length of the data descriptor. If the bar code can be uniquely identified by an introductory character string, maintain the string in the "Prefix" field.
In the second part of the first step, define the individual data IDs for the bar code. Some data descriptors are made up of multiple application values placed one after another. This compound is achieved using a part field that is not equal to zero. The value of this part field indicates its place in the total value of the data descriptor.
You can reserve certain data descriptors for future additions but the only thing you can specify is the length. It is sufficient to maintain these data descriptors with an entry greater than zero. For useable/used data descriptors, you must check the "Defined" indicator.
Define the format of the (sub-) data descriptors using the following attributes:
- Format defines whether Numerical, Alphabetical or AlphaNumerical values are allowed.
- Use Length to define fixed or maximum lengths of the values. It does not include the length of the data identification.
- If the value of the data descriptor is variable, it must be limited by a delimiter (that you defined in the first part of step 1). You can indicate this by checking the Delimiter column.
- Many values must be formatted to an even-numbered length for technical reasons. You can do this by checking the Straight length column.
- In the Decimal places column, you can define the number of characters that can be added to the data descriptor in order to estimate the decimal places of the value that is to be represented.
- You can use the Variable length column to define the number of characters that can be added to the data descriptor in order to describe the length of the value that is to be represented. This added number is multiplied by the value in the Multipl. column and then added to the value in the Add.fact. column to figure the actual length. The data descriptor "234", for example, is defined with values "1/2/1" in columns Variable length/Multipl./Add.fact. resulting in a length of the value presented as 4 * 2 + 1 = 9.
- By checking the Quantity variable column, you define that a data descriptor indicates the quantity for variable quantity trade units.
- Enter the unit of measure according to ISO norms in the ISO column.
- Routines that check the values using certain tests are defined in the Checking column. The following routines are currently defined:
- 1: Carries out a digit check using the Modulo-10/EAN procedure
- 2: Carries out a date check in YYYYMMDD format
- 3: Carries out a date check in DDMMYYYY format
- In the Applicatn column, you can enter structure or table fields that are assigned to a data descriptor. This column is not used in the HU environment.
- In the Description column, you can enter a short text to further identify the data descriptor.
Example
The EAN128 standard data descriptor can be found in the standard system and referred to as an example.
Requirements
Standard settings
Recommendation
In the EAN128 standard, the data descriptors 90 to 99 are meant for bilateral and internal company use.
Activities
Further notes
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_HUMIDEANSCODE | 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 |
| VC_T313D | C - View cluster | SM34 | 00000001HU | Maintain bar code types and data descriptors |
History
| Last changed by/on | SAP | 19990611 |
| SAP Release Created in |
