Intellect – Success Story on PI/PO to CPI Migration
Intellect – Success Story on PI/PO to CPI Migration
Jarvis Australia Supporting the Australian meat industry since 1964. Jarvis provides products and services to the Australian meat industry. They specialize in equipment for meat cutting, boning, and slaughter. They also offer accessories and consumables.
Business Case
To move all active interfaces from SAP PO 7.5 to SAP Integration Suite, ensuring seamless integration and better management of enterprise workflows also leveraging advanced cloud features.
Challenge
The customer operates multiple asynchronous interfaces, requiring automation of reprocessing mechanisms and error notifications according to interface criticality. We need to ensure dynamic configuration of max retry counts, owner details, and priority levels, without runtime modifications to the interface. Implementing custom Iflows for re-processing mechanism.
Solution
To streamline parameter management, we have implemented a common value mapping. When an IDOC is pushed from SAP, it is stored in a dedicated queue assigned to the corresponding partner. We then received the necessary parameters to handle retries, email distribution lists (preventing concurrent error failures due to email restrictions), and other interface-specific properties as per the requirements. By implementing the above solution, we were able to distribute the load to multiple queues, resulting in improved system performance.
Implementation
We used a single Integration Flow to publish IDOCs from SAP. Based on partner information and parameters, messages are routed to different queues as part of a separate Subscriber Flow. The same Integration Flow includes a process to send messages directly to the receiver using the process Direct Adapter.
In case of failure, the message is stored in the same queue until the retry count is reached, after which it is moved to the Error Queue. If email alerts are enabled, an email is sent to the distribution list, prompting them to run an ad-hoc custom Integration Flow to move messages between queues, allowing transactions to be retried.
All tasks are accomplished using the value mapping API in Groovy scripts and a custom header approach, ensuring easy troubleshooting in the BAU phase.
Business Benefits
Guaranteed Message Delivery
Each transaction is tracked and make sure it is sent to a receiver without the involvement of any functional groups.
intelligently determine
In case of data failures, the Integration Flow intelligently determines whether a message needs to be retried based on standard unique identifiers in the exception message, HTTP status codes based on the values stored in the value mapping repository during the initial business requirement and those can be enhanced without changing the interface at runtime.
Email notification
In case of any failures, Email notifications are sent to the respective stakeholders, allowing the BAU team to take appropriate actions based on the error details.
Easy Troubleshooting and Tracking of message
Custom headers allow us to efficiently track messages whenever incidents arise, enabling data validation according to interface-specific configurations for business reference.
Improved Performance
Based on the statistics from SAP PO interfaces, we have optimized the queues and sizing in CPI, preventing performance issues in the event of system outages or receiver system unavailability.
