SAP formally released Advanced Track and Trace for Pharmaceuticals 2.0 (aka SAP ATTP 2.0) to customer on December 05, 2016.
Most of the pioneers among you, in Pharmaceutical Serialization, who choose ATTP 1.0/1.1 as your Enterprise level central Serial Number Range manager and GS1 EPCIS compliant repository, either went live with it successfully or almost there with limited scope of allocating serial numbers to internal packaging lines and internal EPCIS event capturing for few products.
As Nov-2017 deadline is coming fast… now is the time to look forward to rollout the solution for more internal sites/packaging lines and products as well as for CMO/CPO/3PL serialization integration.
Some of you are trying to understand the compelling reasons to upgrade form ATTP 1.0/1.1 to SAP ATTP 2.0.Following are some feature you should consider…
Master Data Change Logs –
Lack of master data object change log was an important gap in ATTP 1.0 that both IT Quality Assurance and Information Security teams raise concerns about. It only records who changed an object and when the last change was made but no specifics on what data elements were changed.
ATTP 2.0 comes with comprehensive master data change log, out of the box, for all master data objects. This change log tracks all the field level change and lets you look through time using a key date selection criterion.
Serial number range management automation –
ATTP 1.0 requires the business user to perform several manual activities after a GTIN is transferred from SAP R/3/ECC to ATTP to make it ready, so that internal packaging line systems or external CMOs/CPOs can request serial numbers for it. This is a cumbersome and very human resource intensive process. It needs lot of time from master data management teams to prepare several thousands of GTINs, if not more, to be ready for serial number allocation. In addition to this manual intervention is need to close expired number ranges.
ATTP 2.0 comes with “Range Automation Profile” that allows for full end-to-end automation of serial number management which includes automatic creation of range definitions and ranges, activation of the same and eventual closing of range definitions/ranges when they expired. All this can be achieved with proper configuration and avoid any business
Significantly Improved Repository Data Authorization –
ATTP 1.0 has a barebones authorization concept for repository data authorization for display or change. You maintain a table of user-ids and respective Global Location Numbers(GLNs) from which users have either change only access, display only access or both. It is a change management nightmare as that table maintenance is through configuration and you need to use a transport to add authorization for new users and take it across the landscape from DEV to QA and to PROD environments.
ATTP 2.0 come with a more role like authorization concept and all the underlying tables are application tables instead of customizing. You can define location groups and assign them to users instead of individual GLNs. Also you can do this in production environment itself much like you do role assignment.
Business Partner Hierarchy –
ATTP 1.0 only allows you to maintain relationship between “Business Partner” to “Location”.
Among other business partner improvement in ATTP 2.0, you can now maintain Business Partner to Business Partner. For example, to maintain relationship between Sold-to and Ship-tos. This helps to maintain customer/vendor license information as location master does not have these fields.
Improved ATTP data cockpit Fiori app and Two new Fiori apps for authentication and verification –
Existing ATTP web data cockpit was enhanced with display of hierarchy, transactions, reporting events, event XMLs and authorization requests.
Introduction of new authentication Fiori app “Mobile Authenticator” with integrated map display to show where the authentication request came from.
New “Mobile Warehouse” Fiori app for serial number status verification with scanning capability. These applications can be deployed on compatible mobile devices. This is a good starting point as it is only information display transaction at this point and will not allow you to pack/unpack/QA Sampling or do any other true warehouse operations that a material handler does.
Repository Browser Improvements –
ATTP 2.0 support EPCIS Transformation Event. Also it gives more control to the business users and IT support user to trigger EPCIS messages on-demand using standalone transaction. In addition, business users can download EPCIS message into files for email communication with trading partners if needed.
Extensibility of data cockpit is a very useful feature to enhance the data cockpit to add and display custom fields to existing objects if needed.
New Country Reporting in ATTP 2.0 –
All new European Union for European Hub connection – ATTP 2.0 supports connection to European Hub for transferring product and
US Item EPCIS transaction statement support for US DQSA DSCSA.
South Korea returns and disposal reporting enabled.
Improved ECC Add-on for SAP Advanced Track and Trace for Pharmaceuticals –
Integration of delivery batch split items from ECC to ATTP in ATTP 2.0 is a very good improvement from main item only integration in ATT 1.0. With this delivery line item batch split sub-items are also integrated from SAP ECC to ATTP for proper quantity matching.
New EWM Add-on for SAP Advanced Track and Trace for Pharmaceuticals –
This add-on will make compatible SAP EWM applications to seamlessly integrate with ATTP 2.0.
Obviously this is not an exclusive list of all the new features and functionality that comes with ATTP 2.0. Please refer to SAP ATTP 2.0 help documentation on help.sap.com for further details. Also as with most of SAP product first releases there are several minor and some major bugs in ATTP 1.0 which are fixed in ATTP 2.0 that can reduce few weeks of your implementation teams time.