Hi all gurus,
we're using SRM7 on our testing system and we enabled distribution of contracts to the backend test system using the new eSOA technology. I'm completely new to this kind of procedure; we've seen that the contract distributed are definitely wrong on the backend (e.g. service hierarchies are flattened, service lines have been "locked", and so on) and looking on the SRM system in sxi_monitor tx I can easily check that the XML itself is not correct.
Here are the questions:
- where can I get detailed documentation about this new service, from beginning to the end (SRM creation of XML -> XML sending -> backend receiving -> BAPI ? (I suppose) to create the document) of the process?
- specifically, what's the part of code (FM, methods) in which is defined how to convert the SRM document into an XML file? This should be the point in out task, since it seems that contracts are badly converted into the XML message...
Thanks everyone for the hints and suggestions you might give 😉
EDIT: the problem seems to be related to contracts with service hierarchy... is there feature not supported by standard actually by now? Is there any workaround available? Thanks again 😉
Edited by: Matteo Montalto on Dec 10, 2009 3:09 PM