Standard xml structures for Event Massage and Event Handler Creation
Like EHPOST1 and EVMSTA02 are there standard xml formats avaiable which EM can read inorder to create handlers and messages. One of the source systems in our client's landscape can only send xml and not IDOCs and we are looking at ways to avoiding using SAP-PI.
Kevin Wilson replied
A couple of ways to approach this Affan,
- You can get the source system to generate an EHPOST or EVMSTA IDoc in XML format. An Idoc is just a structured flat file and traditionally it's positional in nature. The XML format is also a flat file but delimited with the tags as per XML standards - That way all you need to do is have the partner profile set up to use an XML port and drop the XML file in that directory and call EDI_DATA_INCOMING and you are done. We have done this many times quite easily.
- SAP NW PI is an option to take XML and convert it to the BAPI - I would convert it to the IDoc and not the RFC call due to error handling capabilities that exist around the IDoc and not the RFC
- If you like pain then you can get the source system to send an EPCIS (Electronic Product Code Information system) compliant XML message to SAP NW PI and it will do the mapping to EM for you - With this option, traditionally used in the serialized items process, you will have to do quite a bit of customization and development in EM
The order above is in the order for consideration. If 1 is not an option then do 2...