Send IDOC From ABAP Trail Version NPL to Cloud Platform Integration (outbound Part1)
In this Blog I will describe the different Steps on an outbound IDOC Process that sends an IDOC of basic type FLIGHTBOOKING_CREATEFROMDAT01 and Message Type FLIGHTBOOKING_CREATEFROMDAT to SAP cloud Platform Integration iflow that sends the IDOC XML to an email account. It is assumed that you have familiarity with CPI.
- Use Transaction RZ11 to set the value of the profile parameter icm/HTTPS/client_sni_enabled to true.
- Use Transaction SALE to Create Logical System and then assign the Logical System to the client. Create Logical System
- Assign the logical System to Client
- In the Cloud Platform Trial Account – Go the integration Suite and Choose Operations View Choose leystore and create a new Key pair for CPI
- Enter the required value and choose Create and down the Certificate file
- Back in ECC NPL ABAP System – Start the transaction STRUST and choose SSL Client Standard and import the file that was downloaded in the previous step – Choose Add Certificates and Save these changes in addition add the root certificates
- Create and RFC Destination type G in transaction SM59 the path prefix is the IFLOW we will create in subsequent Steps with the the user name and password is the clientid and client secret that you can get the CPI Service instance config file.. For SSL Certificates choose the Default SSL that you had imported the client Corticates in STRUST.
- Check the RFC Connection you can 500 or Not Found is the IFLOW is not yet created.
- As we plan to send IDOC we need to activate the Service /sap/bc/idoc_xml show below 10) To Select the IDOC message type and Basic type go transaction and note FLIGHTBOOKING_CREATEFROMDAT and Basic type FLIGHTBOOKING_CREATEFROMDAT01
- Go to transaction WE21 and Create XML-HTTP port that is used to send IDOC XML
- Create a Partner Profile for NPLCPI001 for partner type LS using the transaction WE20
- Configure the output bound Parameters in the same transaction WE20
- Now We Create the IFLOW in cloud Platform Integration Suite as shown below
- Choose the IDOC and enter the parameters as follows. Please note that /cxf is omitted from the address field as this automatically added by CPI on deployment
- In the Content Modifier we will add three header variables that we will send in the email body. The content Modifier is as shown below
- To configure email we need to create email credentials in the security material in the operations view. A blog for gmail configuration is described below https://blogs.sap.com/2020/12/06/cloud-platform-integration-gmail-configuration-and-integration-flow/ We have created mailUser which should be used here
- Configure the Email Adapter properties as show below
- Save and Deploy the Integration and make sure that it has started by checking in the operations view
- To Test this we will Trigger IDOC from WE19 and choose the the option via message type and enter FLIGHTBOOKING_CREATEFROMDAT
- Click the Root EDIC and enter the following information
- Click the node E1BPSBONEW and enter some valid information for Flight Booking
- We have all the information for the IDOC – Click Standard outbound processing on the top right and make sure any errors are resolved. You can also check in Tcode WE02 that an IDOC with Status 3 has been created due the previous steps.
- Now we go the SAP Cloud Platform integration and choose operations View – Select the Deployment and choose View Message Monitoring and make that success message is displayed for this or look at any error message by change the info to trace and resend the idoc to resolve any error
Check you email account to verify the email has been received as configured in the email adapter settings the IDOC content
A great step-by-step guide! Thanks for sharing.
In IDOC adapter, under connection tab, the address is given as '/NplIdoc' .. can you brief about what is value and how you araived to this value, is this name given by us or SAP standard.
How to differenciate the back end SAP systems if there are multiple and CPI should process according to back end SAP..
When you create an integration in CPI you give a name- when CPI creates with this name it adds an extension. Don't include the extension when you enter the IDOC adapter. parameter.
good blog, keep posting. it helped me a lot