Quantcast
Channel: SCN: Message List - SAP Manufacturing Integration and Intelligence (SAP MII)
Viewing all articles
Browse latest Browse all 4841

Re: Designing a generic transaction for different set of master data values

$
0
0

Hi Praveen,

 

One approach could be that you create 2 transactions:

First one containing the common functionality. For example it would get quantity from SCADA corresponding to each master data key combination. You could send the master data key combination as input to this transaction and then get quantity as output to this transaction.

Second one would iterate on the different interfaces(8 in your case) and then internally call the first transaction to get the quantity.

 

Another approach could be as follows:

This approach would extend the first approach. You could store the XPath of the elements in different XML's in a List in the transaction properties and then use them in the transaction. But this would work if the XML schema is constant for the interfaces i.e. each interface would send the data in the same XML structure each time.

Algorithm could be like this:

Iterate on the Interfaces{

XPath of the interface = List.getValue(index of iterator);

key = XML.getElementValue(XPath);

quantity = call to another transaction(key);

}

Note: Here the order of the interfaces and the namespaces in the collection should be same.

Note: Use #XPath# for getting the value from the collection during runtime.

Basically what I am telling here is that you can save the XPath of different XML's in the transaction properties and then use them while iterating through the XML's.

 

Could you share the XML's you are expecting from different interfaces?

 

Regards,

Rohit Negi.



Viewing all articles
Browse latest Browse all 4841

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>