AIE Auto-ID Enterprise

Release Notes

______________________________________________________________

CopyrightCopyright(c) 2007 SAP AG. All rights reserved.

Neither this document nor any part of it may be copied or reproduced in any form or by anymeans or translated into another language, without the prior consent of SAP AG. Theinformation contained in this document is subject to change without notice.

SAP is a registered trademark of SAP AG.

All other products which are mentioned in this documentation are registered or not registeredtrademarks of their respective companies.

1 AIE Auto-ID Enterprise 11.1 Structure Changes in IMG for SAP Auto-ID Infrastructure 5.1 11.2 AIE-AII Infrastructure 51.2.1 SAP Auto-ID Infrastructure - Enterprise Services (New) 51.2.2 Document Types and Features (New) 51.2.3 ERP Integration (New) 61.2.4 ID Processing 81.2.5 Central Number Range Administration 91.2.6 AIE-AII-AP Application 101.2.6.1 Activities and Rules (Changed) 101.2.6.2 ID Mapping 121.2.6.3 Item Unique Identification (IUID) 131.2.6.4 RFID-Enabled Kanban 141.2.7 AIE-AII-UI User Interface 151.2.7.1 Monitoring 151.2.7.2 User Interface Improvements 161.2.8 AIE-AII-DX Data Exchange 181.2.8.1 AIE-AII-DX-DC Device Integration 181.2.8.1.1 Device Communication and Maintenance 18

______________________________________________________________SAP AG iii

Release-Informationen Inhaltsverzeichnis SAP AG______________________________________________________________

1 AIE Auto-ID Enterprise

1.1 Structure Changes in IMG for SAP Auto-ID Infrastructure 5.1

Use

As of SAP Auto-ID 5.1, the structure of the Implementation Guide (IMG) has changed. You mustregenerate the project IMGs to transfer these changes.

New IMG Structure Nodes

- Basic Settings

- Condition Table Settings

- Unexpected Event Settings

- Physical Object Settings

- Document Type Settings

- Settings for SAP Object Event Repository (SAP OER)

- Master Data

- Vocabularies - ID Mapping

- Business Add-Ins

- BAdIs for Enterprise Services

- BAdIs for Central Number Range Administration

- BAdIs for Kanban

- BAdIs for Profile-Related Tasks

- BAdIs for Document-Related Tasks

- BAdIs That Change or Extend Message Data

Renamed IMG Nodes

- The IMG node Integration is now called Integration Settings .

- The IMG node Data Profile is now called Data Profile Settings.

- The IMG node Conditions and Rules is now called Activities, Conditions, Rules, and MessageTypes.

New IMG Activities

- Basic Settings

- Define Client-Specific Control Parameters

- Number of Retries and Wait Times for Critical Resources

______________________________________________________________SAP AG 1

SAP-System______________________________________________________________

- Barcode Settings -> REFERENCE ONLY: SAP Delivered Bar Code Types

- Maintain Composite Bar Code Elements

- ID Settings -> Maintain Internal & External IAC & Company Prefix

- ID Settings -> Maintain ID Profile

- Integration Settings -> Define Application-Specific Functions for Logical Port Mapping

- Integration Settings -> Map Application Data to Logical Port

- Data Profile Settings -> Maintain Operator UI Profile

- Data Profile Settings -> Maintain Print Profile

- Data Profile Settings -> Maintain User Data Profile

- Data Profile Settings -> Assign Element Sets to Document Context Printing

- Condition Table Settings -> Maintain Condition Tables for Profile Determination

- Condition Table Settings -> Maintain Condition Tables for Object Category Determination

- Condition Table Settings -> Assign Condition Table Set to Usage

- Unexpected Event Settings -> Maintain Reasons for Unexpected Events (UE)

- UI Settings -> Assign Auto-ID Java Mobile UI URL

- Physical Object Settings -> Define Physical Object Categories

- Document Type Settings -> Define Document Types

- Master Data

- Vocabularies - ID Mapping -> Define Business Transaction Types

- Vocabularies - ID Mapping -> Define Business Steps

- Vocabularies - ID Mapping -> Define Disposition Codes

- Activities, Conditions, Rules, and Message Types

- Activities -> Define Activity Categories

- Conditions and Message Types -> Delivered Conditions - Java-Based Mobile Device Msgs

- Conditions and Message Types -> REFERENCE ONLY: Delivd. Condit.- Java-Based MobileDevice Msgs

- Business Add-Ins (BAdIs)

- BAdIs for Enterprise ServicesBAdI: Auto-ID Label Create Request/ConfirmationBAdI: Auto-ID Label Change Request/ConfirmationBAdI: Auto-ID Label Cancel Request/ConfirmationBAdI: Auto-ID Label Print Request/ConfirmationBAdI: Auto-ID Label Encode Request/ConfirmationBAdI: Auto-ID Label Decode Request/ConfirmationBAdI: Auto-ID Label By Elements Query/ResponseBAdI: Auto-ID Label By ID Query/Response

______________________________________________________________SAP AG 2

SAP-System______________________________________________________________

BAdI: Auto-ID Label Device Create Request/ConfirmationBAdI: Auto-ID Label Device Change Request/ConfirmationBAdI: Auto-ID Label Device Cancel Request/ConfirmationBAdI: Auto-ID Label Device by Elements Query/ResponseBAdI: Auto-ID Label Device by ID Query/ResponseBAdI: Auto-ID Label Device Observation Create Request/ConfirmationBAdI: Auto-ID Label Device Observation by Elements Query/Response

- BAdIs for Central Number Range AdministrationBAdI: Number Range Administration EnhancementsBAdI: Send Number Range RequestBAdI: Receive Number Range RequestBAdI: Send Number Range ResponseBAdI: Receive Response for Number Range Request

- BAdIs for KanbanBAdI: Prepare Creation of Tag ID for RFID-Enabled KanbanBAdI: Execute Kanban Status ChangeBAdI: Decode Barcode for RFID-Enabled KanbanBAdI: Retrieve Kanban Master Data from External System

- BAdIs for Document-Related TasksBAdI: Generic Business Document Execution RequestBAdI: Document Search User Interface Enhancement

- BAdI: EPCIS Event Capture

- BAdI: Check Rule

- BAdI: Map Application Log from Activity Message

Renamed IMG Activities

- The IMG activity Define ID Versions is now called Define ID Types.

- The IMG activity Define Conditions for Backend Messages is now called Define Conditions forBackend and Completion Messages.

- The IMG activity Define Conditions for Mobile Messages is now called Define Conditions - SAPWeb Console & Desktop UI.

Deleted IMG Activities

- UI Settings -> Assign Auto-ID Cockpit URL

- UI Settings -> Sample UI Setting -> Assign Sample UI URL

- Data Profile -> Maintain Data Profile

______________________________________________________________SAP AG 3

SAP-System______________________________________________________________

______________________________________________________________SAP AG 4

SAP-System______________________________________________________________

1.2 AIE-AII Infrastructure

1.2.1 SAP Auto-ID Infrastructure - Enterprise Services (New)

Use

As of SAP AII 5.1, you can use the enterprise services in the Automatic Identification LabelProcessing process component, which consists of the following business objects and operations:

- Automatic Identification Label business object

- Create Label operation

- Change Label operation

- Read Label by ID operation

- Read Label by Element operation

- Cancel Label operation

- Print Automatic Identification Label operation

- Encode ID operation

- Decode ID operation

- Automatic Identification Label Device business object

- Create Device operation

- Change Device operation

- Read Device by ID operation

- Read Device by Elements operation

- Deactivate Device operation

- Automatic Identification Label Device Observation business object

- Create Observation operation

- Find Observation by Elements operation

______________________________________________________________SAP AG 5

SAP-System______________________________________________________________

1.2.2 Document Types and Features (New)

Use

As of SAP AII 5.1 the following changes are made.

- The following new document types are added for modeling SAP ERP production orders andproduction versions:

- Production Order (04)

- You can define your own document types to facilitate integration with any external system. You dothis in Customizing with the activity Define Document Types.

- SAP ERP can create physical objects (that is, IDs) in SAP AII.

- ID mapping functionality allows document objects to be identified with SAP AII IDs as well asSAP ERP-specific IDs. For more information see the IMG activity Vocabularies - ID Mappingin Customizing.

- New document components can be used as label fields during tag commissioning.

1.2.3 ERP Integration (New)

Use

As of SAP AII 5.1, the following functionality for handling units (HU) and serial numbers is available:

Handling Unit Enhancements

In SAP AII, you can trigger the creation and updating of handling units (HU) in SAP ERP for storagelocations that are not handling-unit managed or warehouse-managed.

- HUs contain the product, quantity, and object ID information that is specified in SAP AII

- HU updates occur during packing, unpacking, and moving of objects in SAP AII

- HUs can be assigned to an outbound delivery in SAP ERP

Enhanced Routing Capabilities

Routing refers to finding the right backend system to record an SAP AII action. Physical objects in SAPAII now have reference attributes that are used for routing and mapping to SAP ERP.

We provide a template activity for routing (DETERMINE_ROUTING) that you can use as a starting pointfor creating your own routing activities. The following list provides examples of how a customized

______________________________________________________________SAP AG 6

SAP-System______________________________________________________________

routing activity might be defined:

- By document

- By rule parameter

- By location or ID mapping

- Synchronous communication by BAPI calls (needed because appropriate web services are notavailable in SAP ERP)

- Asynchronous communication using XML-messages that are mapped to standard IDOC interfaces inSAP ERP.

Effects on Customizing

You make the following Customizing settings to activate HU and serial number functionality:

Customizing in SAP AII

Under Auto-ID Infrastructure # Activities, Conditions, Rules, and Message Types # Rules# Define Rules

- You copy the rule PACK_HU and maintain the parameters:

- Packaging material in activity HU_PACKMAT_DETERM

- Business system in activity DETERMINE_ROUTING

- You copy the rule MOVE_HU and maintain the parameters:

- Business system in activity DETERMINE_ROUTING

- Set parameter FUNCTION_MODULE

Under Auto-ID Infrastructure# Activities, Conditions, Rules, and Message Types #Conditions andMessage Types # Define Conditions - Java-Based Mobile Device Msgs

- You assign the rule PACK_HU to the mobile readers used for packing.

On the SAP Easy Access screen under Auto-ID Infrastructure #Master Data # ID Mapping

- You add location mapping between a plant/storage location combination for a specific ERP systemand the SAP AII location at which the packing takes place.

- You add location mapping between a plant/storage location combination for a specific ERP systemand the SAP AII location at which the move is registered.

Under Auto-ID Infrastructure# Activities, Conditions, Rules, and Message Types #Conditions andMessage Types #Define Conditions - Java-Based Mobile Device Msgs #Define Conditions for FixedDevice Messages

- You assign the rule PACK_HU to a fixed reader location

Under Auto-ID Infrastructure # Basic Settings # ID Settings # Maintain ID Types

______________________________________________________________SAP AG 7

SAP-System______________________________________________________________

- You configure SAP AII to recognize the SAP ERP objects such as HUs and serial numbers byregistering each type of ERP object as an encoding type within the ID type ERP and entering aprofile name for each ERP encoding type.

Customizing in SAP ERP

You can perform the following Customizing in your SAP ERP system:

- You assign a serial number profile to the relevant materials in SAP ERP

- The serial number profile must allow the assignment of serial numbers during handling unitmaintenance

- You set your SAP ERP system to allow the external creation of serial numbers

SEE_ALSO&

1.2.4 ID Processing

Use

As of SAP AII 5.1 the following enhancements are available:

We support multiple formats such as pure ID URI, tag URI, and hex for EPCs, for the same ID (that is, forthe same physical object).

- Communication between enterprise applications uses the pure identity URI format for objectidentification. SAP AII supports pure identity URIs in outgoing and incoming ASNs.

You can define your own binary or natural language ID. You can also define your own encoding/decodingscheme for these IDs

ID Types, Encoding Types

The ERP ID Type supports SAP ERP to SAP AII integration by identifying SAP ERP objects.

- Encoding types 0HU, 0SN, and 0LOC are added to support processing of handling units, serialnumbers, and plant/storage locations.

To support IUID we deliver a new ID type UII that has two constructs:

- CNSTR1EID

- CNSTR2PART

Physical Object Enhancements

The concept of configurable physical object types is introduced to allow you flexibility in modelingdifferent types of real world objects (such as equipment, kanban, and returnable containers).

For each object type, you can define type-specific attributes that you can use, for example, to definerouting criteria.

______________________________________________________________SAP AG 8

SAP-System______________________________________________________________

1.2.5 Central Number Range Administration

Use

As of SAP Auto-ID Infrastructure 5.1 (SAP AII), you can use central number range administration tocontrol the creation and distribution of number ranges in a system landscape with one or more instancesof SAP AII and an SAP Object Event Repository (SAP OER). Existing features of standalone numberrange administration, that is number range administration without SAP OER, have also been enhanced.

To enable central number range administration, SAP AII 5.1 contains the following features:

- New number range administration user interfaceYou can now perform number range administration tasks on one Web-based UI. The behavior of thisUI differs for standalone and central number range administration and depends on the instance typeof your SAP AII. For more information, see the Implementation Guide (IMG) for DefineClient-Specific Control Parameters. You access this UI on the SAP Easy Access menu underAuto-ID Infrastructure -> Master Data -> Number Ranges -> Number Range Administration.This Web user interface replaces the old SAPGUI user interfaces. However, for standalone and localinstances of SAP AII, it is still possible to access these transactions using the transaction codes.

- Upload reportYou can use this report to upload existing number ranges from a local instance of SAP AII to SAPOER. You access this report from the SAP Easy Access menu under Auto-ID Infrastructure ->Master Data -> Number Ranges -> Number Range Upload.

- Initial number range requestIf no number ranges exist for a number range object type in a local instance of SAP AII, you caneither request an initial number range from SAP OER or create a number range manually in the localinstance. If you create the first number range manually, you use standalone number rangeadministration for the whole number range object type (for example, GTIN) and the local instancebehaves like a standalone instance for this number range object type. In standalone number rangeadministration, number range requests are not sent to SAP OER and all number ranges have to bemaintained manually for this number range object type.

- Number range requestYou can automatically request new number ranges from SAP OER by setting an alert level anddefining a size of number to be requested. When this alert level is reached, a request for a newnumber range is sent to SAP OER and a new number range is returned. For GTIN number rangesyou can still use GTIN ERP integration and request new GTIN number ranges from ERP. To disablethis, and to enable requests from SAP OER, you must set a control parameter in Customizing. Formore information, see the Implementation Guide (IMG) for Define Client-Specific ControlParameters.

- Blocking and allocation of number ranges

______________________________________________________________SAP AG 9

SAP-System______________________________________________________________

In a standalone or a central instance, you can allocate parts of number ranges or block whole numberranges for third party systems that are integrated in the system landscape but that cannot requestnumber ranges automatically.

Effects on Existing Data

- You can continue to use the old number range administration transactions, but we recommend thatyou use the new number range administration UI. However, if you have created your own ID types(previously ID versions) in SAP AII 4.0, you must assign the correct number range database table toyour ID type. In Customizing for Auto-ID Infrastructure, select Basic Settings -> Define ID Types.Select your ID type and encoding type. Under Object Generation, enter the correct database table inthe Number Range Table Name column. If you have also created your own number range databasetable, for example for your own number range object types, check that your table adheres to thefollowing rules:

- The field names of the non-key fields of your table must be the same as, for example, those intable /AIN/TGTIN.

- The field names of the key fields of your table must be the same as the element names of theelement set that you have defined for the number range key.

- As of SAP AII 5.1, the overlap check no longer allows overlapping number ranges for the sameGTIN or the same company prefix (in the case of SSCC) with different encoding types. If you haveexisting GTIN and SSCC number ranges, we recommend that you firstly use the old number rangeadministration transactions to check for existing overlaps. If you do have overlapping GTIN orSSCC number ranges, you must clean up this data before using the new number range administrationUI.

1.2.6 AIE-AII-AP Application

1.2.6.1 Activities and Rules (Changed)

Use

Activities

As of SAP Auto-ID Infrastructure (SAP AII) 5.1, you can use new smaller activities that enable moreflexible custom rule definition. You can make activities even more flexible by creating an additionalactivity context to pass additional data. New activities are also delivered to support RFID-enabled kanban,EPCIS message processing, integration of SAP Extended Warehouse Management (SAP EWM), andhandling unit integration.

It is now also possible to assign activities to an activity category, which is used to group an activityaccording to its function, and to a release. Activities that are marked as "obsolete" are only available to

______________________________________________________________SAP AG 10

SAP-System______________________________________________________________

support upgrade scenarios from previous releases. Customers using SAP AII 5.1 can still use these oldrules, but we recommend that you do not mix activities from different releases and that you do not useobsolete activities when defining customer rules. For a complete list of all activities, see Customizing forAuto-ID Infrastructure under Activities, Conditions, Rules, and Message Types -> Activities ->Define Activities.

Rules

As of SAP AII 5.1, you can also use new and changed rules. Rules for SAP AII 5.1 contain the newsmaller activities and you can recognize them by the suffix *_AA. New rules are also delivered forRFID-enabled kanban, EPCIS message processing, integration of SAP Extended Warehouse Management(SAP EWM), and handling unit integration. For a complete list of all rules, see Customizing for Auto-IDInfrastructure under Activities, Conditions, Rules, and Message Types -> Rules -> Define Rules.

- COMP_BKND_AA replaces COMP_FLEX_BKND

- COMP_LOAD_BKND_AA is new

- COMP_LOAD_NO_BKND_AA is new

- COMP_NO_BKND_AA replaces COMP_NO_BKND

- COMP_PACK_NO_BKND_AA is new

- COMP_UNLOAD_BKND_AA is new

- COMP_UNLOAD_NO_BK_AA is new

- CPACKFINISH_AA replaces CPACKFINISH

- CPACK_AA replaces CPACK

- KANBAN_ASSIGN is new

- KANBAN_MEMORIZE is new

- KANBAN_STATUSCHANGE is new

- LOADU_AA replaces LOADU

- LOAD_AA replaces LOAD_FLEX_BKND

- LOAD_AA_EE is new

- MOVE_AA replaces MOV

- MOVE_AA_EE is new

- MOVE_EWM is new

- MOVE_HU is new

- ODLV_EE is new

- PACKUCHILDREN_AA replaces PACKUCHILDREN

- PACKU_AA replaces PACKU

- PACK_AA replaces PACK

- PACK_AA_EE is new

- PACK_EWM is new

______________________________________________________________SAP AG 11

SAP-System______________________________________________________________

- PACK_HU is new

- TAGCOMGEN_AA is new

- TAGCOMNOTIFY_AA replaces TAGCOMEXT

- TAGCOM_AA replaces TAGCOM

- TAGCOM_AA_EE is new

- TAGDECOMNOTIFY_AA replaces TAGDECOMEXT

- TAGDECOM_AA is new

- TAGREISSUEGEN_AA is new

- TAGREISSUENOTIFY_AA replaces TAGREISSUEEXT

- TAGREISSUE_AA replaces TAGREISSUE

- TAGUPDATEEXT is new

- UNLOADU_AA replaces UNLOADU

- UNLOADU_NO_DOC_AA is new

- UNLOAD_AA replaces UNLOAD_FLEX_BKND

- UNLOAD_AA_EE is new

- UNLOAD_EWM is new

- UNPACKCHILDREN_AA replaces UNPACKCHILDREN

- UNPACK_AA replaces UNPACK

- UNPACK_HU is new

Document Update

The new rules do not allow the assignment of IDs to business transactiondocuments if SAP AII cannotmatch the ID to a document line item. This could occur, for example, if a tag ID such as an SGTINreferences a product that does not exist as a document line item.

If you want to override this behavior and to allow SAP AII to assign IDs to documents even if they do nothave line items that match the ID, you must clear the parameter CV_ERROR_DUE_ITEM_MISMATCHof method OBJECT_ITEM_MATCH in your custom implementation implementation of BADI/AIN/ACTVT000005.

______________________________________________________________SAP AG 12

SAP-System______________________________________________________________

1.2.6.2 ID Mapping

Use

As of SAP Auto-ID Infrastructure (SAP AII) 5.1, the user interface Location Mapping has been removedfrom the SAP Easy Access menu and replaced by the more general ID Mapping user interface underAuto-ID Infrastructure -> Master Data. The function of this user interface is not restricted to locations,but you can use ID mapping to map any type and format of a unique ID to another ID that has a differenttype and format but that identifies exactly the same object.

1.2.6.3 Item Unique Identification (IUID)

Use

As of SAP Auto-ID Infrastructure (SAP AII) 5.1, existing processes support the use of US Department ofDefense (DOD) item unique identification (IUID). Items with IUID barcodes can now be managed withstandalone tag commissioning, packing, moving, and loading, as well as with integrated inbound andoutbound delivery processing.

Additional IUID integrated processes are facilitated by the new generic document interface. However,configuration and development are required for this additional integration.

The following content has been enhanced or changed to support IUID:

- The ID type ERP has been added with encoding type serial number to enable mapping betweenunique item identifiers (UII) and ERP serial numbers.

- The ID type UII has been added with encoding types CNSTR1EID (IUID Construct 1) andCNSTR2PART (IUID Construct 2)

- The bar code types ISO 15434 for formats 05, 06, and DD are delivered. You can define your ownbarcode types in Customizing.

The following features have been added to support IUID:

- You can use the generic document interface to define customer-specific document types, forexample purchase order, and to import a list of UIIs that are to be marked on objects duringproduction.

- You can define new issuing agencies.

______________________________________________________________SAP AG 13

SAP-System______________________________________________________________

- Number range administration supports UIIs. You can define number ranges for IUID construct 1(Number range object EID_SERIALIZED) for each company prefix and can define number rangesfor IUID construct 2 (Number range object PART_NUM_SERIALIZED) for each product within acompany prefix.

- The activity POBJ_IF_FROM_BTD supports the selection of the next ID to commission from a listof IDs in the business transaction document.

- SAP AII translates between the string value stored in a 2D bar code and the embedded field values.

1.2.6.4 RFID-Enabled Kanban

Use

As of SAP Auto-ID Infrastructure (SAP AII) 5.1, you can integrate the kanban replenishment procedure inan external system, such as ERP, with RFID technology. By using RFID tags and devices to exactlymonitor the movements and establish the status of kanban containers, you can use RFID-enabled kanbanto enhance the visibility of your kanban process and to have a better overview of your stock situation.

Note:For information about the availability of ERP integration for the RFID-enabled kanban scenario, seethe SAP Note 1015853.

RFID-enabled kanban contains the following features:

- Predefined kanban-specific ID types

- Predefined kanban-specific rules and activities

- Master data update from external system

- You can use a report to fetch kanban master data from the external system. You access thisreport on the SAP Easy Access screen under Auto-ID Infrastructure -> RFID-EnabledKanban -> Master Data -> Master Data Update (both screens).

- Kanban status mapping

- You can create conditions to define the status of a kanban, which is determined by acombination of device group and command, after a particular action. You create theseconditions in Customizing for Auto-ID Infrastructure under Activities, Conditions, Rules,and Message Types -> Conditions and Message Types -> Define Conditions for FixedDevice Messages.

- Kanban/ID assignment

______________________________________________________________SAP AG 14

SAP-System______________________________________________________________

- Here you have two possibilities. You can display a list of kanbans and a list of tag IDs andassign them manually. Alternatively, you can assign a kanban to a device group and the nexttag ID that is read at that device group is automatically assigned to the kanban.

- Kanban status update

- When a kanban is detected by an RFID device, the status is updated according to the conditionyou define in Customizing. The new status of a kanban is returned via Web services to theexternal system. It is also possible to update the status manually on the user interface. This newstatus is also returned to the external system.

1.2.7 AIE-AII-UI User Interface

1.2.7.1 Monitoring

Use

AS of SAP AII 5.1 the following monitoring functionality is available:

Error Correction

It is important to recognize errors before SAP AII sends the message for loading or unloading to the ERPsystem because it is almost impossible to correct the data afterwards.

The system has the ability to monitor tag scanning for tags that the readers miss or tags that they scan bymistake. You can correct such errors on the Document search by manually inserting tags (if they weremissed) or by manually removing them (if they were scanned by mistake).

You can also manually correct EPC data and scanned quantities on the Document search.

The following enhancements facilitate finding deliveries that have potential scanning errors:

- You can define criteria to identify and display errors more clearly on the Document search by usingthe BAdI: Document Search User Interface Enhancement. For example, you can cause an icon toappear beside items that have been over packed.

- The Document search shows aggregated quantities for each material that is associated with an EPCthat represents a quantity-relevant material

Message History

SAP AII tracks message history to record observations that are created or updated by a device or a mobilemessage and sent to SAP AII. To support this feature, the following functionality is added:

______________________________________________________________SAP AG 15

SAP-System______________________________________________________________

- The Message History search allows you to display message and observation records and shows therelationship between the incoming message from both fixed and mobile devices and thecorresponding observation. You can search Message History by the following criteria:

- Device group ID

- Observation time (from / to)

- Observation received time (from / to)

- Observation ID

- Command

- Archiving is available to remove old history records

- SAP AII stores the observation ID of incoming messages for later analysisThis allows you to compare the recorded observation against the message that was sent.

The following features are not part of message history:

- Tracking how activities create and update observations (actions and action objects)

- Which document SAP AII sends to the backend system

- Which rule is triggered

- EPCs are not stored in the message history

1.2.7.2 User Interface Improvements

Use

As of SAP AII 5.1 the following new features are available in the SAP AII user interface (UI):

Monitoring UIs

User interfaces are available for monitoring packing, loading, and unloading. These UIs:

- Are streamlined to only show operator-related tasks

- Display a table that shows the current actual quantity packed, loaded, or unloaded

- Display an error message telling the operator what has gone wrong

- Are implemented using Web Dynpro for ABAP

A conveyor-packing monitor is available that:

- Displays the contents of the pallet that is being packed

______________________________________________________________SAP AG 16

SAP-System______________________________________________________________

- Contains a Finish Packing button to instruct SAPAII to interpret the next case as part of a new palletand to generate and print pallet tags associated with the cases that were scanned before the FinishPacking button was pressed

- Includes the capability to print tags for items, cases, and pallets

Mobile UIs

The following new and changed functionality is available for the mobile UI:

- The mobile UI transactions below are affected:

- Tag Commissioning

- Tag Decommissioning

- Move

- Pack

- Unpack

- Unpack Child Objects

- Load

- Unload

- Mobile transactions are now under Auto-ID Infrastructure # Tools on the SAP Easy Access screen.

- The UI is based on Java Web Dynpro running on SAP NetWeaver and using RFCs to connect toSAP AII.

- The logon user's authorization determines the business processes that the user sees on the UI (that is,users see the processes that they are authorized to see).

You determine the business processes that are available to be displayed on the mobile UI inCustomizing under Define Conditions Java-Based Mobile Device Msgs.

- Support for 2D bar codes is added

- The ID displays on the UI.

- Reading single and multiple tags is supported

- Writing single tags is supported

Desktop UIs

The following new and changed functionality is available for the desktop UI:

- User interfaces are configurable and users can choose the columns that they see and the order inwhich they see them.

- Search UIs allow you to:

- Define your own queries by choosing the Define New Query link

- Use the Display Hierarchy button to view the object hierarchy

- Use the newly developed Message History search to research messages

- Correct documents on the Document search by inserting objects or removing them from the(actual) document object hierarchy.

______________________________________________________________SAP AG 17

SAP-System______________________________________________________________

- Display errors more clearly on the Document search by using the BAdI: Document SearchUser Interface Enhancement

- View document-related action objects on the Document search UI.

1.2.8 AIE-AII-DX Data Exchange

1.2.8.1 AIE-AII-DX-DC Device Integration

1.2.8.1.1 Device Communication and Maintenance

Use

As of SAP AII 5.1, the following enhancements and changes are available for RFID devices:

- You can send messages from SAP AII to the device controller using your own schema.

- SAP AII can send error messages to the device controller if an error occurs during notificationmessage processing.

- The device communication interface is enhanced to support writing passwords to tags and to killtags.

- You can send IDs in formats other than hex from the device to SAP AII.

- You can send the bar code strings in standard formats from the device to SAP AII. You can enhancethis function to include proprietary formats in Customizing under Auto-ID Infrastructure # BasicSettings # Barcode Settings.

- You can choose to no longer maintain devices because SAP AII uses the device group instead of thedevice.

______________________________________________________________SAP AG 18

SAP-System______________________________________________________________