SAP Cloud Integration - Trading Partner Management(TPM) - AS2 to SAP IDoc Interface

[rasjoshi]

Hi All,

This blog is demonstration of steps performed in SAP Integration Suite - TPM to developer AS2 to SAP IDoc interface using standard package of Cloud Integration - Trading Partner Management V2.

For testing purpose I have used mendelson software to simulate sender partner and used processdirect at receiver side to demonstrate usage of custom-iflow in TPM. As per current standard package cloud integration supports communication protocols - AS2, SOAP, IDoc and custom iflows can be used to accommodate needed communication protocols for e.g. mail, sftp etc. Similarly custom iflows can be used for pre, post processing and custom mapping program using processDirect adapter.

Pre-requisites :- 

1. New service key created for sender partner in BTP

2. Download TLS certificates from Keystore

3. Download partner public certificate from Mendelson

Before starting b2b scenario configurations in TPM - Agreement completed the MIG and MAG configurations and activate the artifacts. Create template Iflow for X12 to XML as MIG/MAG uses XML files for simulation. Deploy groovyscript and Iflows from package - Cloud Integration - Trading Partner Management V2.

Create identifiers, system, sender and receiver communication channels, import sender's public certificate in security tab, self public certificate under certificates tab. Below are screen shots for reference -

 

                                           Company - Type Systems

                                         Company - Communications

Rx.PD - Process_Direct adapter with path to my generic interface to trigger mail with IDoc - ORDERS05                          

                                         Company - Security

                                         Company - Certificates

P.S. - You can create own keys in Cloud Integration and download public certificate to share with partner system. I am using default one from tenant for demonstration.

Trading Partner Details -

                                         TP - Identifiers

                                         TP - Type Systems

                                         TP - Sender AS2 Channel MDN

                                         TP - Sender AS2 Channel Security

Note :- Create dummy receiver channel or AS2 MDN channel to change the status of system from incomplete to complete. Additionally NRO can be used, create number range ICN_ASC_X12 from manage stores.

Create agreement template, in this scenario TP will be initiator and company will be reactor. 

Create agreement for business transaction b2b scenarios. Once agreement is activated it will create entries in Partner Directory.

To test interface upload payload from mendelson software to cloud integration - 

Cloud Integration --> B2B Monitoring --> Interchanges

Mail received with ORDERS details :- 

Errors/Troubleshooting Details :- 

Error 1 :- Integration flow fails with error “com.sap.it.rt.adapter.as2.api.exception.ChannelConfigException: No certificate value configured for signature verification"

Solution :- SAP Note 3303411

Error 2 :- com.sap.it.rt.adapter.as2.api.exception.InboundProcessingException: com.sap.it.api.pd.exception.PartnerDirectoryException: No partner registered for the incoming request.

Solution :- There was mismatch in system version while creating company profile and trading partner profile and MIG/MAG artifacts 

Error 3 :- <ErrorText>Segment not in defined transaction set</ErrorText> / <ErrorText>Segment not in proper sequence</ErrorText>

Solution :- This was due to wrong data in X12 file.

References :- 

https://api.sap.com/package/CloudIntegrationTradingPartnerManagement/integrationflow

https://help.sap.com/docs/integration-suite/sap-integration-suite/getting-started-with-b2b-scenarios...

#HappyLearning