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:
  
  • Inbound, inclusive ASN handling, unloading, goods delivery (inwards) and warehousing
  • Outbound, comprising picking, container processing, packing, provision, loading, goods outwards and delivery
  • Return goods deliveries
  • Resources, including the set-up of a warehouse order, opening and confirming on the basis of RFID scanning procedures

Proceed: Our Services for You