Kontakt

Ansicht
Dokumentation

/AIN/VC_EPC - Define ID Versions

/AIN/VC_EPC - Define ID Versions

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity you define ID versions. These versions specify how an ID is encoded on the RFID tag and how it is encoded for use in the information system layers. Electronic product Code (EPC) is the most common form of ID in the RFID world.

EPC is a universal identification scheme for identifying physical objects via Radio Frequency Identification (RFID) tags. EPC data uniquely identifies an individual object. An ID version defines the length and position of this data, without defining its content.

The general structure of EPC encodings on a tag is a string of bits (a binary representation), consisting of a tiered, variable length header followed by a series of numeric fields for which the overall length, structure, and function are completely determined by the header value.

For more information, see http://www.epcglobalinc.org.

An ID version is constructed as follows:

ID Version

The following EPC tag data standards are delivered:

  • 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

Natural language

You set this indicator if you define your own ID as a 'natural language' ID. If you maintain this indicator, you must also implement the BAdI definition: /AIN/BADI_ID_CONV. Natural language IDs are limited to 60 characters.

Encoding Type

  • ID Header (Binary Format)
You define the EPC header value with binary format. The header specifies the EPC type and structure of the EPC tag encoding. The EPC tag encodings include a header field followed by one or more value fields. The header field defines the overall length and format of the value fields. The value fields contain a unique EPC identifier and optional filter value when the latter is judged to be important to encode on the tag itself. Binary IDs are limited to 30 bytes. If you have a natural language representation of a binary ID, such as a URI representation of an EPC, that should also be limited to 60 characters.
  • Decimal Value
You define the EPC header value using decimal format.
  • Total Bits
You define the total bits length of your encoding type. (for example, 64 for 64 bit tag and 96 for 96 bit tag)
  • Profile Name
You define the data profile name to specify which element is used for each encoding type. The profile type is ID Maintenance,and element setsare Input/Output for encoding/decoding, Tag encoding constructs, UI Input, Range for number range selection. The profile is then used to get the elements.
For more detailed information on data profiles, see the IMG activity Auto-ID Infrastructure → Basic Settings → Data Profile → Maintain Profile.
  • Prefix of URN Format
You define the Prefix of URN format that determines the semantics of EPC-URI encodings translated into other EPC encodings and vice versa.
Note: A URI is a character string representation that is commonly used to exchange identity data between software components of a larger system.

Tag Data Constructs

Here, you maintain the element constructs for tags. As delivered, all the elements in element set 'SAP_ID_SET' are supported. When you specify your own element (Element type '12: Tag encoding constructs, no SAP standard element), you must implement the BADI definition: /AIN/BADI_ID_CONV. For each element, specify the bit position and length with conversion type (Integer, ASCII, or truncated ASCII).
For more detailed information, see the IMG activity Maintain Element Sets and Attributes.

Filter Value

Filter values provide additional data that is used for fast filtering and pre-selection of basis logistics types, such as items, inner packs, cases and pallets.

Partition Value

Here, you define the available values of the partition and the corresponding sizes of the company prefix field and item reference field .
The partition indicates where the subsequent company prefix and item reference numbersare divided. This organization matches the structure in the EAN.UCC GTIN in which 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

The following objects are supported as standard:
  • GTIN

  • SSCC

  • GRAI

  • GIAI

  • DOD Construct # 1

For each encoding type, you assign function modules for generating objects (for example, GTIN, SSCC, GRAI, and GIAI ) and for getting serial numbers.

Object Reference

You specify the element (s) that comprise the object .

URN Constructs

You specify the elements for constructing the URN formats.

Issuing Agency

You specify the issuing agency for each encoding type at your company. If you need more than one issuing agency, set the priority using the sequence number.

Default ID Version

You specify the default ID version to be used for encoding and decoding IDs.

Possible Issuing Agencies

You list the possible issuing agencies to choose from when you assign an issuing agencies to your encoding types. Issuing agencies are organizations such as EAN.UCC that are responsible for assigning a unique identifier to an enterprise.

Company Prefix

  • Internal Issuing Agency
Specify the internal issuing agency for each company prefix.
  • Company Prefix
Assigned to a managing entity by EAN or UCC, the company prefix is the same as the company prefix digits within an EAN.UCC GTIN decimal code.
Note:Usually you have to add a leading zero to your UCC company prefix to get the EAN.UCC prefix, that is used in the 14 digit GTIN.
  • Company Prefix Index
The company prefix index encodes the EAN.UCC company prefix. The value of this field is not the company prefix itself, but rather an index to a table that provides the company prefix as well as an indication of the company prefix length. In the 64-bit EPC, the limited number of bits prohibits a literal embedding of the EAN.UCC company prefix. As a partial solution, a company prefix index is used. This index, which can accommodate up to 16,384 codes, is assigned to companies that need to use the 64-bit tags in addition to their existing EAN.UCC company prefixes. The index is encoded on the tag instead of the company prefix, and is subsequently translated to the company prefix at low levels of the EPC system components (that is, at the reader or savant levels).

Define Default ID Version

  1. Choose a default ID version.
  2. Savethe entry.

Define Company Prefix

  1. Define the company prefix that the issuing agency assigns to a managing entity.
  2. If you are using 64-bit EPCs with issuing agency: EAN.UCC (EAN-International), define the company prefix index (even if the company prefix is smaller than 16,383.)
  3. Savethe entry.

Define ID Version

  1. Specify an ID version and description. If you specify your own ID with natural language, you must mark the natural language indicator. When this indicator is marked, the system calls a BADI that allows you to specify your own encoding or decoding logic. For more detailed information, see documentation of BADI definition: /AIN/BADI_ID_CONV.
  2. If your ID is binary, then you specify encoding types you want to encode or decode, and maintain header values with binary and decimal formats. You assign your own data profile (you must first Maintain the Data Profile), URI format prefix, and separator. You must also specify the URN construct, and the element to be used for your URN format.
  3. Maintain the tag data constructs for your IDs. All the elements must be defined in the data profile. For more detailed information, see the IMG activity Maintain Element Sets and Attributes. For each element, you specify the bit position and length with conversion type (Integer, ASCII, or truncated ASCII). When you specify your own element, you must implement the BAdI definition: /AIN/BADI_ID_CONV.
  4. Specify the filter value for each encoding type.
  5. Specify the partition table for 96-bit EPCs.
  6. Create your own function module to generate objects and to get number ranges (if required), and assign this function module using the Object Generationnode of the Define ID Versions in Customizing. When you create the function module, you can copy the template function module '/AIN/TMPL_GEN' for FM for generate objectand '/AIN/TMPL_GET_NRRANGE' for FM for new number range.
  7. Savethe entries.






Vendor Master (General Section)   General Material Data  
This documentation is copyright by SAP AG.

Length: 11658 Date: 20240426 Time: 172038     sap01-206 ( 195 ms )