Scenario Overview:
In our integration landscape, the data flow is:
AccordFT (MFT) → FTP → SAP PO → File (Archival) → SAP PO → SAP CAR/POSDTA
We are using a single standard interface and mapping for all countries. File processing is dynamic, and files are handled based on the country code.The MFT team confirmed that SAF files were successfully processed and sent from their end. However, SAP PO did not receive the files for one specific country, and the data was not delivered to the SAP CAR system.
Issue:
- Files were successfully sent from MFT
- No messages were visible in SAP PO for one country
- Other country files were processed successfully using the same interface
- Data was not reaching SAP CAR
Additionally, the issue was difficult to trace because:
- No explicit errors were observed
- Configuration appeared correct and consistent
Cause - The issue occurred after replacing the old PO server with a new server in the ICO configuration.
The scenario was successfully tested in QA without any issues, as the system was still pointing to the old server. This created a false positive validation, and the issue only surfaced in Production after switching to the new server.
QA:
In Production:
- The configuration was updated to use the new server
- The issue appeared only after this change
Further analysis revealed that:
- There were only two ICOs and two sender channels with similar configurations
These existed because: - One set was originally used for the old server
- Another set was created for the new server configuration
- After replacing the old server with the new one, both configurations became effectively identical, leading to overlap
Additionally, the interface design included connected flows:
- One flow handles file pickup and archival in SAP PO
- Another flow processes and delivers data to SAP CAR
Due to similar sender channel configurations (same server and path, different users), one channel interfered with file pickup. Because of the connected interface design:
- The file was not picked correctly in the inbound flow
- As a result, downstream processing to SAP CAR did not occur
- Since the configurations were nearly identical and no errors were thrown, the issue was not immediately visible.
Solution:
To resolve the issue:
- Reviewed all sender channels and ICOs for overlapping configurations
- Identified the duplicate/conflicting sender channel
- Stopped the unnecessary sender channel
- Requested the MFT team to resend the SAF file
After implementing the fix:
- SAP PO successfully picked up the file
- The archival flow executed correctly
- The file was processed and delivered to SAP CAR
Key Takeaways:
- Avoid maintaining duplicate ICOs and sender channels with identical configurations
- Ensure clear separation when transitioning from old to new servers
- Validate end-to-end flows, especially when interfaces are interconnected (archival + processing flows)
- Always test using the actual target server (Production-like setup)
- Similar configurations without errors can still cause silent processing conflicts
#abap