SAP Auto-ID Infrastructure (SAP AII

)
1 Introduction
SAP Auto-ID Infrastructure (SAP AII) is a flexible, adaptable infrastructure, which creates a connection between Auto-ID technologies and existing systems. On delivery, SAP AII offers various logistical processes, which are pre-set. Furthermore, the user has the option of adapting this content and implementing completely individual processes in a simple way. The following diagram clarifies the main elements of SAP AII and the integration options:

In the context of track & trace, SAP AII is generally used as a local solution for the issues of data consolidation, control and aggregation.

2 Integration scenarios
The following integration scenarios are available for SAP Auto-ID Infrastructure:
   

Standalone Installation Integration with the ERP system Integration with the SAP Object Event Repository Integration with the SAP Object Event Repository and the ERP system

3 User Interface (UI)
SAP AII can be used on the broadest range of platforms. SAP AII offers two user interfaces:
 

Mobile user interface (used on handhelds and PDAs) Desktop user interface (SAP easy access screen, e.g. for executing transactions, reporting and settings in the SAP AII system)

Mobiles User Interface:

4 Master Data
The basic master data in SAP AII are products, locations and devices. A location may be e.g. a storage location. This storage location generally has various devices (e.g. barcode and RFID scanners).

5 Number Range Administration
Number range administration is required in order to achieve clear identification of individual products through serialisation. The tasks of number range administration are mainly the generation, distribution and monitoring of the individual number ranges. If several local SAP AII instances are in use, SAP OER takes on the administration of the entire global number range, whilst the local SAP AII instances order and administer the respective local number ranges.

6 Rules and Activities

SAP AII offers an extensive control processor. This is where configuration takes place of what should happen e.g. when an RFID transponder or a barcode is registered. The standard SAP AII package already includes a large set of predefined rules and the associated activities. With the highly flexible rule framework, users with SAP knowledge are able to adapt and add to these rules with no programming effort. New, customised rules can, of course, be defined at any time. Below is a breakdown of the main processes already supported by the corresponding rules and activities with delivery of SAP AII out-of-the-box: 6.1 Goods Issue SAP AII supports the following points in the goods outwards process, in order to be able to successfully dispatch serialised products:
         

Generation of serial numbers (e.g. EPC, DoD UII or individual formats) Creation of RFID transponders and/or printing of barcode labels Allocation of transponders and/or barcodes to packages, cartons, pallets etc. Automatic generation of hierarchies, e.g. with several levels for boxes outer packagings and pallets Communication of this information e.g. to SAP ERP Scanning and tracking of products or containers in relation to shipping Linking of serial numbers with shipping documents Completeness check at the point of shipping Automatic entry of the goods issue in the SAP ERP system Automatic dispatch of a delivery notice (ASN) to the customers

6.2 Goods Receipt SAP AII supports the following points in the goods Receipt process, in order to be able to successfully receive serialised products:
     

Receipt and processing of the delivery notice (ASN) Logging of the serialised information in the goods receipt control Reconciliation of serial numbers with the delivery notice (ASN) Association of serial numbers with the goods receipt documents Entry of the goods receipt in SAP ERP Automatic creation of the delivery confirmation

6.3 Returnable Transport Items (RTI) The RTI process involves tracking reusable items in a closed cycle (e.g. reusable containers). SAP AII supports the following points here:

 

Tracking the current and historic locations of RTIs on their way through the closed cycle. Here, the place time and condition (full, empty, defective etc.) are recorded for each item. Creation of RFID transponders or barcode labels using all current formats such as SGTIN, GRAI, SSCC etc. Automatic monitoring of events and conditions and integrated notification functions (alert management)

6.4 Kanban In the Kanban scenario, the serialisation of containers in the production processes and the automatic initiation of Kanban-typical replenishment strategies are supported. The following functions form the main standard delivery package for the Kanban scenario:

Automatic emptying of the containers and automatic set-up of the replenishment element (e.g. order, production order, transfer) by scanning one or several RFID transponders or a barcode label. Automatic filling of the container and automatic stock increase in the relevant area as well as closure of the replenishment element by scanning one or several RFID transponders or a barcode label.

6.5 Product Tracking and Authentication

The core functions of product tracking and authentication include the following:
   

Recording of IDs / serial numbers (EPC, UII, IUID, individual formats), hierarchies, locations and events Linking of IDs / serial numbers with business objects, e.g. such as batches, lots, orders, consignments etc. Data exchange with trading partners Queries about IDs, status, place, events, order or other business characteristics (production lot)

   

Notification (alert management) in predefined exceptional situations Authentication using track & trace information (secure supply chain) Authentication with extended features, e.g. such as transponder ID, hologram tags, images with clear product features Logging of authentication attempts and the responses

7. CCMS Monitoring and Alert Management
All error notifications and warnings coming from SAP AII are accessible through the standard CCMS (Computer Centre Management System) monitoring.

8. Technical Reporting and Application Log
All events and movements in SAP AII are recorded in the application log. This memory constitutes the basis for the technical reporting. The monitoring of a packing process can be seen in the example below.

9. Other Functions
 

The Generic Document Interface allows the simple integration of documents into SAP AII and the processing of these documents with Auto-ID data. Auto-ID integration with SAP Extended Warehouse Management (SAP EWM) and covering the following processes: o Inbound, inclusive ASN handling, unloading, goods delivery (inwards) and warehousing o Outbound, comprising picking, container processing, packing, provision, loading, goods outwards and delivery o Return goods deliveries o Resources, including the set-up of a warehouse order, opening and confirming on the basis of RFID scanning procedures

Proceed: Our Services for You

SAP AIE: Not only for Track & Trace
SAP AIE offers more than Track & Trace
In addition to track & trace, SAP Auto-ID Enterprise supports a range of other processes, which you can optimise with this solution and Auto-ID technology (e.g. RFID). These include (e.g.):
    

Automatic goods issue process Automatic goods receipt process Kanban Returnable transport items Authentication

Coming soon: An interactive Flash Demo for Kanban and RTI (SAP AIE)

Product Tracking and Authentication
You can use product tracking and authentication (PTA) to ensure the safe production and secure distribution of your product by creating visibility and traceability across your enterprise and your extended supply chain network. The process enables the following:      Track product flow at multiple hierarchy levels (such as at item, case, or pallet level) to detect discrepancies between the expected and the actual product flow Trace all business events and transactions at unique object level Trace business events at related business document level Perform automated multi-layer authentication of products Establish a chain of custody of the product

Process
For more information about PTA, see the documentation for the three process variants:    Product tracking by delivery Product tracking by EPC Product authentication

Product Tracking by Delivery

Purpose
You can perform this process to track the progress of a delivery as it is processed across your supply chain.

Process Flow

... ...

1. Search for delivery On the search screen you can enter an attribute of the delivery that you want to track. The attributes by which you can search are configurable. 2. Display delivery details SAP object event repository returns a list of all deliveries that match your search criteria. You can select the delivery to display further details associated with the delivery, for example events. You can display the current ID hierarchy associated with a delivery as well as hierarchies from previous events. In this way, you can track the progress of the delivery as well as the individual objects belonging to the delivery.

Product Tracking by EPC

Purpose

You can perform this process to track a product using its EPC. The process gives you visibility of the progress of an EPC throughout delivery processing and information about its associated delivery and EPCs.

Process Flow

... ...

1. Search by EPC On the search screen of SAP object event repository, you manually enter the EPC or a specific status that you want to search for. The attributes by which you can search are configurable. 2. Display EPC hierarchy The system returns the EPC and its attributes. The attributes that are displayed here are configurable. You can display the currently EPC hierarchy associated with the EPC as well as the hierarchies of previous events. You can select the EPC to display the associated events. It is also possibly to select and display the delivery.

Product Authentication

Purpose
If you suspect that a product is counterfeit or are unsure of its heritage, you can perform this process to authenticate a specific EPC.

Process Flow

... ...

1. Enter suspicious EPC On the authentication screen of SAP object event repository, you enter the EPC of the object that you suspect might be counterfeit and one or more attributes, for example the tag ID. The attributes by which you can authenticate are configurable. 2. System performs authentication check for EPC The system searches for the EPC in the system. 3. System returns authentication status The system returns the result of the authentication check and assigns a status to the EPC. The status can be one of the following values: ○ Known

The system has found the EPC in the system and the attribute(s) found for the EPC matches the attribute(s) that you entered.
○ Suspicious

The system has found the EPC in the system, but the attribute(s) found differs from the attribute(s) entered.
○ Unknown

The EPC was not found in the system.

NOTE-RFID REUSAGE IS NOT SUPPORTED BY SAP OER

Central Number Range Administration

Purpose

You can use this process to control the creation and distribution of number ranges in a system landscape with SAP object event repository (the repository) and multiple local instances of SAP Auto-ID Infrastructure (SAP AII). This helps you to ensure the uniqueness of serial numbers across your enterprise and makes tracking of individual IDs easier and more reliable.

Prerequisites
 ● You have defined the instance types of the systems in your system landscape.
○ In your local SAP AII in Customizing, you have defined SAP AII as the local instance. For more information, see the Implementation Guide (IMG) for Auto-ID Infrastructure under Basic Settings  Define Client-Specific Control Parameters. You must do this for each local SAP AII for which you want to request number ranges from the repository. ○ In the repository in Customizing, you have defined the respository as the central instance. For more information, see the Implementation Guide (IMG) for Auto-ID Infrastructure under Settings for SAP Object Event Repository  Define Client-Specific Control Parameters.

● You have set up communication settings between the repository, SAP NetWeaver Exchange Infrastructure (XI), and local instances of SAP AII. For more information, see SAP Service Marketplace at service.sap.com/rfid  Detailed Information and SAP Solution Manager.

Process Flow
...

1. You upload all existing number ranges from your local SAP AIIs to the repository. 2. You create overall number ranges for number range objects in the repository. 3. In a local SAP AII, you request initial number ranges from the repository, if number ranges for number range objects do not already exist. 4. RFID devices request and consume number ranges from local SAP AIIs. For more information about the distribution of number ranges from SAP AII to RFID devices, see Number Range Distribution to Devices. 5. The local SAP AII sends a number range request to the repository via XI when the alert threshold of a number range in a local SAP AII is exceeded. The number range request contains information about the number range object and the size of interval required. 6. The repository returns a new number range interval to the local SAP AII via XI if an overall number range for the requested number range object exists in the repository. If the repository cannot fulfill the request, for example if the overall number range is completely consumed, the request is rejected. You can then manually correct this in the repository, for example by increasing the Number To of the overall interval, and resend the request from the local SAP AII. 7. You can also block and allocate number ranges in the repository for external systems.

Sign up to vote on this title
UsefulNot useful