There are times in a project when you have to copy an existing solution from one system to another. Or you develop a solution in a sandbox instance, that has no connectivity to other systems in the landscape. Or even you simply develop a scenario sim...
When posting the first part of my description of BOR objects use in IDoc scenarios, I promised a continuation for outbound IDocs, so here it comes. However, I’m not going to focus on the “regular” output procedure, which is described in details in an...
Every time you create a custom IDoc receiver scenario, you have to take care of a few technical things related to IDoc communication. First of all, you have to create the IDoc structure manually, with all its segments. Then, you also have to implemen...
The more I work with graphical mappings in PI, the more I get convinced that the queues & contexts concept is one of the most difficult things to understand there. This is also confirmed by the SDN forum, since most of the mapping problems described ...
Hi Experts,I have an existing 1:1 scenario (file to IDoc) that I had to convert to the so called mapping-based message split scenario. I have already done the development changes, according to the blogs: When I performed a test using identical input...
Hi Sandeep,Receiver SOAP adapter in PI has "native" support for web service authentication. You just put the username and password in the communication channel settings. Regards,Grzegorz
Hi,For purchase orders you need IDoc ORDERS. I'm not sure to understand if your scenario is inbound or outbound (from ECC perspective). Try searching SCN for "ORDERS inbound" or "ORDERS outbound", it will give you a jumpstart.Regards,Greg
Hi Prasad,There is no need for WE21 configuration, you're with this method you are sending IDocs over HTTP using SICF, it is sort of alternative for RFC or files that require a port. However, e.g. the partner profile in WE20 or other IDoc configurati...
