cancel
Showing results for 
Search instead for 
Did you mean: 

Sending messages from PI to MII

0 Kudos

Scenario:

SAP -> PI -> MII

Requirement: Need to get Production Orders data from ECC to PI to MII.

Questions:

1) After downloading the orders from ECC to PI, How PI can send the data to MII --- In this case I don't have any input parameters from MII to PI to fetch orders from ECC. Just need to fetch all the orders till date.

2) If I want to do Order confirmations from MII using PI -- How can I create a request for PI with all my input parameters.

Please help me, How I can configure "XMIIMESSAGELISTENER" in MII (Do I have to configure this to get Messages from PI ? )

Thanks in Advance.

View Entire Topic
0 Kudos

There's no real need to configure the XMIIMESSAGELISTENER component but rather the message processing rules that are hadling the XML messages received by the listener.  The reason why I say that is because the XMIIMESSAGELISTENER is always waiting for an incoming message on the standard HTTP(S) port of the MII server, just a matter of calling the service as defined here:

http://help.sap.com/saphelp_mii140sp01/helpdata/en/4c/7258d9e631469ee10000000a15822d/content.htm

In order for the XMIIMESSAGELISTENER to properly identify the message name so that the proper Processing Rule can be applied you need to either specify the "MessageName" URL parameter.  The other option is to define a XSD Schema and specify the XPath to the name if the document has the name contained inside of the XML defiinition.

On the PI side you configure an HTTP Endpoint and be sure to include "&session=false" in the URL as a parameter so that HTTP sessions are not created each time PI sends a message to MII.

Hope this helps,

Sam

PS: The help link above is for MII 14.0 (Currently in Ramp-Up) but the feature exists in 12.2 but it does not have the EO and EOIO processing as previous releases processed messages based on when they were received.  I believe that PI can control the serialization of messages to MII so that this isn't an issue.