I have done an interface in this area where we sent Control recipe (process order) to multiple third parties. The RFC is imported into PI. Then it involves functional configuration to trigger process order through an RFC Control Recipe download to PI through the TCP\IP connection. PI then maps it to target message(s) and send it to receivers. The acknowledgement is then sent asynchronously through another RFC Process_mess_upload back to ECC.
So you have to work with your functional owner to identify interfaces based on processes and then take it from there.
First you need to identify the interfaces to use. Most probably, it should be handled by config. The example I gave you is triggered by functional configuration. Once you get the message into PI, then you need to work on what format the third party needs the data in...
this depends upon your requirement. If the functional owner suggests an enhancement in an interface, then an ABAPer will come into play. if a requirement can be achieved with standard functionality/configuration, ABAP wont be required. this is true of any interface development.
PI PCS interface is a process interface part of PI-PP (Production planning for process industries) module in SAP. PI 7.3 is the latest release of Process integration which is a middleware used for enterprise integration (exchange of data between different applications or businesses). ECC has the framework to execute PI-PCS interface and in case this data has to flow to and from on organization (implementing SAP) and PI (don't confuse it with module but middleware) is being used for integration, data can flow from SAP to PI and to third party and vice versa.
>>>>>.how the information from the receiver is sent back to the SAP system.
This is possible if you integrate a third party which executes a part of the process and the data has to flow back to ECC (through PI 7.3 for example).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.