Advanced SAP PI/PO Message Monitoring Tips

Dynamic Message Processing Logs in SAP CPI: (Custom Headers)   In CPI integration scenarios, we frequently need to log critical business identifiers (IDoc numbers, PO numbers, invoice numbers) in Message Processing Logs (MPL) for: Audit trails and compliance Troubleshooting specific transactions Business monitoring of key documents   Standardized Property Naming Convention Prefix: mpl- for all logging properties Examples: mpl-IDocNumber mpl-PONumber mpl-InvoiceNumber Dynamic Groovy Script Implementation import com.sap.gateway.ip.core.customdev.util.Message def Message processData(Message message) {    // Get all message properties    def properties = message.getProperties()        // Access MPL instance    def messageLog = messageLogFactory.getMessageLog(message)        if(messageLog != null) {        properties.each { key, value ->            // Process only mpl- prefixed properties            if (key.startsWith("mpl-")) {                // Extract header name by removing prefix                String headerName = key.substring(4)                // Add to MPL custom headers                messageLog.addCustomHeaderProperty(headerName, value?.toString())            }        }    }    return message } Implementation Workflow Set Properties (Content Modifier/Previous Steps): Property Name: mpl-IDocNumber Value: 1234567890 Dynamic Processing: sequenceDiagram    Participant CM as Content Modifier    Participant GS as Groovy Script    Participant MPL as MPL        CM->>GS: Sets mpl-IDocNumber=1234567890    GS->>MPL: Automatically logs IDocNumber=1234567890 MPL Output: Custom Headers: | IDocNumber | 1234567890 | | PONumber  | 4500000123 | Best Practices Property Naming: Maintain consistent mpl- prefix Use clear business names (e.g., mpl-SalesOrder) Error Handling: // Enhanced version with null checks if (value != null && !value.toString().isEmpty()) {    messageLog.addCustomHeaderProperty(headerName, value.toString()) } Performance: Limit to essential properties (avoid storing large payloads) Consider property size (MPL has 1000-character limit per header) Extension Opportunities Metadata Enrichment: // Add timestamp automatically messageLog.addCustomHeaderProperty("LogTime", Instant.now().toString()) Integration with Monitoring: Forward these headers to external monitoring tools Use in alerting rules (e.g., missing IDoc numbers) Centralized Library: Deploy script as a shared library artifact Reference across multiple iFlows Real-World Example Scenario: Process IDoc with multiple document references Set Properties: mpl-IDocNumber = 0900000012 mpl-PONumber = 4500009876 mpl-Invoice = 5100000456 MPL Output: Custom Headers: | IDocNumber | 0900000012 | | PONumber  | 4500009876 | | Invoice   | 5100000456 | Troubleshooting: Quickly search MPL by any document number Correlate across systems using logged values This approach significantly reduces maintenance overhead while providing flexible, business-meaningful logging. 

Your CPI iFlow failed… but you can’t find the log. You search everywhere, nothing. The problem? You’re searching with the wrong ID. CPI has 3 types of IDs for filtering logs. Most devs only know Message ID and waste hours. — Here’s the breakdown so you never lose a log again. > Message ID = CPI’s unique log identifier. - Generated automatically per message processing log. - Search result = That exact log. ✅ Use when: You have the log’s direct ID from an error, monitor, or alert. > Correlation ID = Groups logs across flows. - Example: iFlow 1 → ProcessDirect → iFlow 2 - Each has a different Message ID but the same Correlation ID ✅ Use when: You want the whole conversation across flows. > Application ID (SAP_ApplicationID header) - Set manually (Content Modifier, Groovy, etc.) - Search by business-specific ID (Order No, Invoice No, etc.) ✅ Use when: Tracking messages by business context instead of technical IDs. 💡Search order in CPI: Message ID → Correlation ID → Application ID 📌 Pro Tips: – Always log Correlation IDs in chained flows – Use Application IDs for business-level tracking – Bookmark this so you’re never lost in Monitor again — P.S. If this post was worth your 2 mins… Comment ‘Worth’ — it helps more devs find it! #SAPCPI #IntegrationDeveloper #SAPIntegrationSuite #CPI #iFlow #IntegrationMindset #BTPDeveloper #SAPBTP #SAPCloudIntegration #Middleware #TechSimplified #DebuggingTips #IntegrationTips #EnterpriseIntegration #CloudIntegration #SAPDeveloper

🗞️ Message Filtering with Standard & Custom Headers in SAP Integration Suite Monitoring messages in SAP Integration Suite can get tricky when you’re dealing with thousands of messages and multiple interfaces. Especially when filtering messages based on business content or incoming message data fields. Standard filters like Message ID and Correlation ID are useful—but they’re too technical and don’t reflect the business context. ✨ This is where standard and custom header parameters come into play. Using the standard header SAP_ApplicationID, you can enhance the monitor to let you search messages by business object ID, like Sales Order Number or Article Number. Custom headers give you even more flexibility—by extracting values from the payload and setting them in the header, you can filter messages on exactly the business data you need. ✅ The result? Easier tracking, faster error analysis, and business-friendly monitoring in the Message Monitor. 🔗 Full article with an example iFlow: https://lnkd.in/gRsP7AyW 👉 How are you using headers in your Integration Suite projects? #SAPIntegrationSuite #SAPBTP #SAPIntegrationDesign #SAPMiddleware #SAPJMS #DataStore #SAPDevelopers #SAPCommunity #SAPTechTips