
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 of this blog series ( this blog ), we will look at how to use IDoc Numbers to search for IDocs in HCI Message Monitoring. We will also look at options to use other fields other than IDoc numbers to search for your Message in HCI
For Standard SAP content, this has already been blogged by abinash.nanda in his blog End2End monitoring of HCI message flow in Standard Content - Made easy. In the comments of this blog I had asked the Abhinash the question - How can this be done for Custom Integration Flows eventually leading to this documentation link of HCI.I had previously also used this technique in my blog : HCI -Integrating SalesForce (SFDC) using HCI -Part 2 and hence this in many ways can be repetitive content on SCN but I blog about this technique to ensure there is a continuity in the entire series.
Description | Screen Shot |
---|---|
As-Is recap of the Integration Flow from Part 1
| |
Add a Content Modifier to your Integration Flow
| |
Save & Deploy your Integration Flow & You are done! |
Description | Screen Shot |
---|---|
Trigger your IDoc from SAP ERP & Note your IDoc Number
| |
Eclipse
| |
WebUI
|
Description | Screenshot |
---|---|
Use SAP_Sender and SAP_Receiver in the Content Modifier
|
Description | Screenshot |
---|---|
Note: This setting will now mean that you cannot search with your IDoc Number. | ![]() |
|
In case when the IDoc is triggered from ERP with a packet size greater than 1, the IDoc XML will contain multiple IDoc Tags. What this would mean is that you will have multiple IDoc Numbers in the corresponding payload. Hence, this approach cannot but used with IDoc's with packet size greater than 1.
SAP HCP-IS / HCI provides inbuilt functionality to enable searching for your messages using IDoc Number / Other Fields of the IDoc. It is as simple as adding a Content Modifier with the Header Fields - SAP_ApplicatioID and the corresponding XPATH to be used.
We will now proceed to look at extending this scenario to use a Client Authentication from SAP ERP to HCI instead of Basic Authentication in Part 3 of this blog series.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
7 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |