
Technical Name of Business Function |
AIE_OER_PTACOLDCHAIN |
Type of Business Function |
Enterprise Business Function |
Available From |
SAP Auto–ID Infrastructure 7.1 |
Technical Usage |
Event Management |
Application Component |
Event Manager (SCM-EM-MGR) |
Required Business Function |
Automatically activated business function EM, Archiving and Web Interface Improvements (SCM_EM_HIGHVOL) |
Incompatible Business Function |
Not relevant |
You can use this business function to provide content for a high-volume product tracking and authentication process, including display of archived data as well as the related capture and query interfaces for EPC Information Service (EPCIS). Furthermore, you can use cold chain extensions if you are interested in condition monitoring. These are implemented as optional enhancements to the high-volume product tracking and authentication process.
Caution
If you have already installed SAP Auto-ID Enterprise and are using SAP object event repository (SAP OER), all EPCIS interfaces will use a new data model if you activate this business function. This means that you can no longer use the EPICS interfaces to access data that you received through the interfaces before you activated this business function. You can display this data by using the Web user interface (Web Dynpro ABAP) and the appropriate user profiles.
You can use this business function in the Secure Tracking and Tracing business scenario.
To use this business function, you must have installed SAP Auto-ID Enterprise. For more information about SAP Auto-ID Enterprise, see SAP Help Portal at .
To implement SAP OER, you must have installed SAP Auto-ID Infrastructure and SAP Event Management on the same box.
You have installed the following components as of the version mentioned:
Type of Component |
Component |
Required for the Following Features Only |
|---|---|---|
|
Software Component |
SCEMSRV 7.01 |
|
|
Technical Component |
PI_BASIS 7.02 XI CONTENT SCEMSRV 7.01 XI CONTENT SCEMSRV IC 7.01 |
If you want to track finished goods on item-level, you can use this preconfigured content of the new visibility process to make the amount of objects available for a significant period of time. The delivered content comprises the related EPCIS capture and query interfaces, which are suited for high data volumes. As a result, you can reduce the implementation efforts and use a platform for secure tracking and tracing in a high-volume environment.
Note
Consider the following implications when using this new visibility process:
IDs can have a maximum length of 50 characters
ID mapping is no longer used for EPCs, business transaction IDs and business location IDs
Extraction of Product Tracking & Authentication (PTA) scenario data to SAP NetWeaver Business Intelligence is not supported
You can use the high-volume PTA visibility process to ensure the item quality and detect harmful conditions for high-value items that are sensitive to environmental conditions such as temperature, pressure, or humidity.
You or a system can temporarily assign a sensor to an item, for example, a pallet, or to a complete delivery. If you do so, temperature measurements can be reported and processed. This results in a status that reflects whether deviations have occurred. After the goods have reached their destination, the sensor is detached again.
The preconfigured settings reduce the implementation effort significantly.
Note
The attachments, which are sent in the cold chain use case, need additional system resources. This can influence the maximum data throughput and the maximum data volume that has to be administrated for an SAP OER instance.
The ECPIS capture and query interfaces now allow the processing of high data volumes and of IDs of any format with a maximum length of 50 characters. However, the ID syntax is not checked by the system.
The new query SimpleEventQueryWithArchive offers the possibility to query and retrieve data transparently from the archive and the database through the EPCIS query interface.
The usage of these interfaces now results in reduced total cost of ownership (TCO) because less storage space and processor capacity is required.