SAP ABAP IMG Activity /AIN/VC_EPC (Maintain ID Types)
Hierarchy
☛ AIN (Software Component) AIN 710: Add-On Installation
   ⤷ AIE-AII (Application Component) Infrastructure
     ⤷ /AIN/DECODE (Package) Auto-ID EPC Decoding
IMG Activity
ID /AIN/VC_EPC Maintain ID Types  
Transaction Code /AIN/38000006   (empty) 
Created on 20040514    
Customizing Attributes /AIN/VC_EPC   EPC Settings 
Customizing Activity /AIN/VC_EPC   EPC Settings 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /AIN/VC_EPC    

Use

In this IMG activity, you define ID types that specify how an ID is encoded on the Radio Frequency Identification (RFID) tag or how it is constructed for use in the system interfaces such as the SAP Auto-ID Infrastructure to ERP interface.

An ID type defines the structure of an ID and the length and position of its components (an example of a component is the serial number in an EPC 1.30 type ID with encoding type SGTIN-96).

The Electronic Product Code (EPC) is the most common form of ID in the RFID world. It is a universal scheme for identifying physical objects using RFID tags. EPC data uniquely identifies an individual physical object. The general structure of EPC encodings on a tag is a string of bits (a binary representation), consisting of a header followed by a series of numeric fields for which the overall length, structure, and position are determined by the header value. For more information about EPCs, see http://www.epcglobalinc.org.

ID Type

We deliver the following commonly used ID types. You may define your own ID types and an optional description if necessary.

  • AII
  • EPC_1.20 EPC Tag Data Standards Version 1.1 Rev.1.20
  • EPC_1.24 EPC Tag Data Standards Version 1.1 Rev.1.24
  • EPC_1.27 EPC Tag Data Standards Version 1.1 Rev.1.27
  • EPC_1.30 EPC Tag Data Standards Version 1.30
  • ERP
  • EWM
  • FMCG
  • GS1
  • GS1_SER
  • HLS
  • SAP
  • SKBN 1.0
  • UII (Item Unique Identification scheme)

Natural language

You set this indicator if you define an ID that is a natural language ID; that is, the ID is represented only in a form that is readable by humans (a #user-readable# form). If you maintain this indicator, depending on the complexity of your ID construction scheme, you may also need to implement the BAdI definition: /AIN/BADI_ID_CONV.

Readable Formats

This table lists the user-readable formats in which an ID type may be represented. For example, an ID of type EPC 1.30 can be expressed in tag URI format or pure URI format.

Default Format

The default format is the format that SAP AII always uses to send and receive the ID to and from different systems. An ID in any other format can always be converted to the default format; however, the reverse is not always true.

Encoding Type

Encoding type refers to a scheme, such as an EPC or UII scheme, for constructing an ID from within an ID type. For example for the ID type EPC 1.30 and above, the following encoding types are possible:

  • DOD1-96
  • GIAI-202
  • GIAI-96
  • GRAI-170
  • GRAI-96
  • SGLN-195
  • SGTIN-198
  • SGTIN-96
  • SSCC-96
  • GSRN-96
  • GDTI-96
  • GDTI-113

GSRN-96, GDTI-96 and GDTI-113 are not used in any of the business scenarios and processes in SAP Solution Manager for SAP Auto-ID Infrastructure.

ID Header

The binary ID header value is defined using binary format. This field is left blank for any ID type that is not expressed in binary format. The binary encoding of the ID includes a header field followed by one or more component fields. The binary ID header defines the overall length and format of the component fields.

ID Header Decimal Value

This field is optional. It contains the binary ID header value in decimal format.

Total Bit Length

This field contains the number of bits in the tag ID (for example, 64 for encoding type SGTIN-64)

Profile

The ID profile for an encoding type specifies the element sets that SAP AII uses for various purposes, such as for generating a serial number to create an ID. Element sets are defined in Customizing under Auto-ID Infrastructure -> Data Profile Settings -> Maintain Element Sets and Attributes.

Each element set in the ID profile is assigned to valid usages such as Mobile UI Default and Key for Serial Number.

Prefix of URN Format

Note: The Prefix of URN Format and the Separator fields are legacy fields that are replaced by the Readable ID Header and Readable ID Construct sections in the dialog structure.

Note: A Uniform Resource Identifier (URI) is a character string representation that is commonly used to exchange identity data between software components over a network, typically the World Wide Web, using specific protocols.

URN Format Separator

This field contains the delimiter for the fields within the binary ID construct.

Binary ID Construct

The binary ID construct defines the component fields that the binary ID header refers to.

For a given encoding type in binary format (for example, SSCC-96) within an ID type (for example, EPC 1.30), the binary ID construct maps the position of each data element within the ID by specifying the start bit position and the length of each element. SAP AII uses this information to encode and decode IDs in binary format.

Partition Reference

If this field is selected, SAP AII uses the Partition Value table (instead of this table) to find the bit lengths for the elements in the ID construct.

Conversion Type

This value specifies the algorithm that SAP AII uses to translate integer and character strings to binary and vice versa.

Filter Value

This table defines the possible values for the FILTER_VALUE element in the ID construct for EPC IDs. Filter values provide additional data that is used for pre-selection of logistics such as items, inner packs, cases, and pallets.

Partition Value

If there is a partition reference in the binary ID construct, SAP AII gets the bit positions and lengths for the elements COMPANY_PREFIX and ITEM_REFERENCE from this table.

For example, for encoding type SGTIN-96, this table defines the sizes of the company prefix field and item reference field. The EAN.UCC GTIN dictates that the company prefix added to the item reference number (plus the single indicator digit) totals 13 digits. The company prefix may vary from 6 to 12 digits and the item reference (including the single indicator digit) may vary from 7 to 1 digit(s).

Object Generation

In this view you make settings for number range objects types.

  • In the FM for Generate Object column, you specify the function module that deconstructs objects into the elements in the ID construct. For example, the function module /AIN/GTIN_GEN specified for encoding type SGTIN-96 creates a GTIN from the elements COMPANY_PREFIX and ITEM_REFERENCE, and vice versa.
  • In the FM for New Serial No., you specify the function module that generates serial numbers for the ID of an encoding type such as SGTIN-96 encoding type.
  • In the Number Range Object Table column, you specify the table that stores number ranges for the selected number range object type. For more information, see Name of a Number Range Object Table.

Object Reference

The object reference specifies the elements that comprise the derived object. If you select the Nr. Ref indicator, a number is generated for that element using the function module for serial number generation that was specified above.

Readable ID Header

The readable ID header (formerly called the Prefix of URN Format) defines the construction of the user-readable format in the same way that the binary ID header defines the construction of the binary ID format. That is, the ID includes a header field followed by one or more component fields.

Readable ID Construct

The readable ID construct defines the component fields that the readable ID header refers to.

For a given encoding type (for example, DOD1-96) within an ID Type (for example, EPC 1.30), the readable ID construct specifies the sequence of the data elements separated by a separator such as a comma or a period.

SAP AII uses this information to encode and decode IDs in readable format.

Attributes

Attributes are additional data of the object, like location, to which an ID is assigned.

In this view for a given encoding type (for example, 0LOC) within an ID Type (for example, FMCG), you can specify the attribute name (internal to SAP Auto-ID Infrastructure) and their URN header as defined by the standard body which maintains the ID type.

The attribute name is used as the field name of the database table where the value of the attribute is stored. You can search for an object by its attribute value through an EPCIS SimpleMasterDataQuery.

Issuing Agency

This table specifies the allowed issuing agencies (for example, GS1) for each encoding type within an ID type. If there is more than one issuing agency for an encoding type, you set the priority using the sequence number.

Default ID Type

SAP AII uses the default ID type if it cannot determine the type of the ID from the information given. This is a required step for all companies.

Required Activities

You mus

Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   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 /AIN/VC_EPC 0 /AIN/R1D0000002 Infrastructure 
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
/AIN/VC_EPC C - View cluster SM34  
History
Last changed by/on SAP  20061102 
SAP Release Created in 200