HCI/HCP-IS: IDoc Adapter Deciphered – Part 4 – Trigger IDoc from HCI to SAP ERP Using Basic Authentication
Background
In Part 1 of this blog series, we looked at steps to trigger an IDoc from SAP ERP to HCI from the scratch using Basic Authentication.
In Part 2, we looked at how to use IDoc Numbers to search for IDocs in HCI Message Monitoring.
In Part 3 , we looked at how to use Client Authentication aka Certificate Based Authentication when triggering IDocs from ERP to HCI.
In Part 4 (this blog), we will look at how to trigger IDocs from HCI to SAP ERP using Basic Authentication.
Configure SAP ERP Settings
Martin Dejl in his blog SOAP for IDOC demystified has explained how you can use SOAP messages to send IDoc’s to a SAP ERP system.
Well, guess what, the HCI IDoc adapter uses the same logic. Due credit to Martin Dejl for his blog as that lays the foundation to understand how IDoc’s can be sent over SOAP protocol. Firstly, we will also look at some of the prerequisite that need to be taken care of on ECC to enable IDoc communication over SOAP Protocol.
Configuration | Screenshot |
---|---|
|
|
System : ERP
Transaction: SRTIDOC
|
|
System: ERP
Transaction: SICF
|
|
Configure your Partner Profile in SAP ERP in Transaction WE20
|
Test Configuration using SOAP UI
Before we look at how to configure a receiver IDoc adapter, lets get this working from SOAP UI considering this works using SOAP
Configuration | Screenshot |
---|---|
|
Click on image where required |
|
HCI Configuration
Configuration |
Screenshot |
---|---|
Integration Flow
|
|
IDoc Adapter Configuration
|
Test Your Configuration
Scenario | Results |
---|---|
Scenario 1
Expected Results
|
|
Scenario 2
Expected Results
|
|
Scenario 3
Expected Results
|
|
Scenario 4
Expected Results
|
Application/x-sap.idoc vs Text/XML recommendation
- If IDoc Packaging is required, use Text/XML ( as it is the only supported way )
- If IDoc Packaging is not required,use Application/x-sap.idoc as it provides End to End Tracking of IDoc using ARCKEY.
IDoc Receiver Adapter using Client Authentication
I had blogged previously about using IDoc Receiver Adapter and Client Authentication using HANA Cloud Connector – HCI: Integrate On Premise ERP with HCI IDoc Adapter using HANA Cloud Connector & Client Authentication
In case you would like to use IDoc Receiver Adapter directly with Client Authentication but without HANA Cloud Connector, the previous blog of mine still holds true. The only difference being ,
- No HANA Cloud Connector Configuration is required.
- All the ECC Configuration remains the same.
- HCI Configuration – IDoc Receiver Adapter
- URL will contain URL of ECC ( Not HCC URL )
- Channel will have Client Authentication Selected and Private Key for Client Authentication provided.
Final Summary
With this blog and my reference to HCI: Integrate On Premise ERP with HCI IDoc Adapter using HANA Cloud Connector & Client Authentication , this blog series comes to a end. The Key Message that is required from this series is HCP-IS/ HCI uses IDoc over SOAP as its protocol for IDoc communication and this demands additional configuration / changes in your ECC as with compared to SAP PI.
Feel any info is missing? Any scenario for the IDoc adapter is not covered feel free to drop in a comment and will see if the gap can be addressed.
Hope this series was as enjoyable to read as was to blog on ????
New NetWeaver Information at SAP.com
Very Helpfull