Blog Archive

Friday, June 26, 2015

Holding messages in SAP PI

Om 

Case 1:
(use case 1)
Step1: 
Go to runtime work bench--- ;Message Monitoring---Adapter Engine.

Step2: 
Check wts the status of your holding message by comparing first step. 
If it is in Scheduled status then cancel it .

Step3: 
If Step2 operation not successfull then stop the receiver channel and reprocess them , after some time message will go to system error status then you can cancel the messages and it will go in to terminated with error status.

Case 2:

(use case 2)
This will work for other adapters but not for SFTP. I tried all that options but it will not work since it is SFTP adapter and you will not find logs properly on this adapter it always show green & holdings or Scheduled messages cannot be deleted from Message monitoring. Stopping the channel also didn't work as they never went into error or failed status to cancel them

Only option i had was to delete all the EOIO message in the MDT tool link (Messaging System monitoring). There also we need admin id to delete them


case 3:

(use case case 3)
invalid configuration in communication channel

ex: you are supposed to configure transaction name : purchageOrder, but you have configured AdvancedShip notice.

this causes messages like, Delivering or Holding messages, but you will not see messages with Delivered.
( also think , in this case also).






          

Friday, June 19, 2015

SAP PI Proxy connections in single stack and some common errors

Om

Ref: Michal blog and sap help
1. RFC destination G type :SAP_PROXY_ESR ( Connection to ESR content )

  2. HTTP destination to AEX ( we can use this in SXMB_ADM)

Note: No other destination are required((LCRSAPRFC and SAPSLDAPI are used to SLD connection),SAP_PROXY_ESR is used, LCRSAPRFC is obsolete. SAPSLDAPI is only used when reports are executed)

sap help info on :SAP_PROXY_ESR







  

Thursday, June 18, 2015

SAP ECC to SAP PI tcp ip connection error IDOC communication

Om


( sap gateway and program id is same in tcp/ip rfc with inboundRA of nwa)







Idoc configuration in single stack outbound and inbound

Om


Idoc receiver with different options ( default, fromNwa, manual)

Idoc sender with different options ( default, fromNwa, manual)



Main connections IDOC, Proxy in SAP PI


SAP --> IDOC(SAP PI)
1.RFC destination in ECC ( &  port, partner profile in sender)
2. Create Inbound Resource adapter ( inboundRA ) in NWA

for idoc refer Michal blog
also this blog2
dual stack idoc configuration sap doc


SAP PI (IDOC) ---> SAP ECC.
1. create RFC desitnaiton to ecc in NWA. (/* for receiver proxy: it is http destination, for sender proxy it is , http + G type RFC destination from sender SAP system)







Wednesday, June 3, 2015

JMS to IDOC , control records are overwirte in receiver idoc communication channel

Om

Even though over writing control records in idoc receiver communication channel, some times sender system sends sends control records in payload, this causes failure of messages in SAP PI as follows

sending control data from sender system( which is not supposed to send)

this causes error , in audit log and failure of message in sap pi as shown in below error


idoc control records are overwrite as follows


Adding control record to payload failed due to Error while adding control record to idoc payload due to HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted.

MP: exception caught with cause org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted.

Transmitting the message to endpoint using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: org.w3c.dom.DOMException: HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted.

this interface is just pass through, Verified idoc basic type in the configuration.


validated the same in idoc monitoring (meta data) in pimon, if it is properly loaded or not.