Q: which adapter should you use while integrating with any SAP system? Explain why?
A: SAP gives us following options to communicate with SAP systems.
1. IDoc Adapter
2. RFC Adapter
Explanation: If you take a close look at the adapters specified here, the one thing that strikes right away is the usage of proxies. We know that proxy generation is possible only if your WAS is >= 6.20. So, that is one parameter that comes up straight away for the usage of proxies.
Hence Use Proxies only if the WAS version is >= 6.20. And the biggest advantage of the proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine – so it will and should give us a better performance.
Next Iâ€™ll go for IDoc Adapter and last RFC adapter. What do you say guys????
Q: What is Program ID and where do you use it?
A: Program ID??? There is no idea in my mind but after 10 seconds I got it and the answer is: We will use it in RFC destination while creating RFC destination but I was not aware of what it does? Thatâ€™s much only I could answer but I searched SDN and found out the following answer:
Well, the program id can be anything, even your name. 🙂 But the catch here is that you should have the same in both the RFC destination and your RFC adapter.
Q: Where do you find Application Server(Gateway) and Application Server Service(Gateway)?
A: TCODE : SMGW -> Goto-> Parameters -> Display
You will find the required info under Attributes. Application Server(Gateway) is the Gateway hostname and Application Server Service(Gateway) is the Gateway service.
Usually the Gateway service is sapgwXX where XX is the system number.
Q: What is the main difference between RFC and IDOC Adapter and when we go for RFC and IDOC with ex?
A: IDoc and BAPI are both are SAP-objects. IDoc adapter used for ASync- communication. RFC adapter used for sync-async communication
Q: Sender Agreement is required for IDoc adapter? Why?
A: NO, Sender Agreement is not required for IDOC adapter, instead we will do settings from R/3 to XI system, so we don’t have any option to create an IDOC adapter in sender side, and we will trigger the IDocs through we19 and transfer the data.
Q: What is Global container in SAP XI?
A: Container object—> can be only used in the function it is defined in.
Global container > it can be used and remain visible across the different function.
Global container – in the old days it was used to store objects in mappings now we can use global variables instead.
Container Object: This object enables you to cache the values that you want to read again when you next call the same user-defined function.
From SP14 and above avoid Global Container. Use Java Section of Message Mapping to define Global Variables and to use them in your UDF’s.
Q: What is Context Handling and where do we use it?
A: Context handling you use when you want to group elements in different node from source into the single node of target with multiple occurrence of element( remove context) and if you want to do reverse of it the use function split by value .
Q: In which situation you used file to file scenario?
A:We use FTP when the file involved is not on the XI Server but on any other remote system. The senarion we use File -to-file is when u have FTP adapters on both systems (sender/receviers). These systems could be Non-SAP Systems also..or when the partner systems are small in size……
Q: In IDoc to file scinario how we will get file name as idoc number at run time for every IDoc number?
A:The idoc number we will be generated for evey idoc ..and the number will 16-digit unquie number and u can check the status of the idoc in Transaction Code “IDX5”.
Q: If we are using business serevices in file to idoc scinario where we can specify the logical system names and what is the importance of logicalsystems.
A:We specify the logical system name in “WE20”
Q:Is it possible to trasfer the data with out using IR(repository)?
A:Yes, it is possible.
Configure sender and receiver communication channels in a Business Service or System, as usual.
Create a Receiver Determination:
1. The Service has to be a valid business service or system in the ID.
2. Interface name can be anything you make up, but should be unique. In this case, it is “nonexistence_interface”.
3. Namespace name can be anything you make up or already exists. In this case, it is “http://abc.com”.
Enter a valid service for the Receiver and save in Receiver Determination.
Create Interface Determination and do following:
1. Use the same Interface name as the sender.
2. Use the same Namespace name as the sender.
3. Do NOT enter any Interface Mapping.
Create Sender and Receiver Agreements as usual.
The interface is now ready to be activated and executed. Once executed, you can examine the content of the payload in SXMB_MONI. It will contain whatever the data you sent, but you will also receive an error indicating that the message is not XML (which can be ignored).
The main points of this exercise is:
1. IR is not necessary for development of interfaces in XI.
2. In ID, any name can be used for Sender Interface and Namespace names, and they do not need to exist in IR.
3. No Mapping can be used, since the data may not be XML.
4. The Receiver Interface and Namespace names must match that of the Sender Interface and Namespace names.
5. Most importantly: the data sent thru XI does NOT have to be in XML; any data can be sent thru XI.
Q: what is the protocol used for File?
Here it depends on the where the file is located. If the file is in same Local network as XI is then NFS (Network File system is best suited) Otherwise FTP
NFS protocol when we are required to poll the files from local machines.
FTP protocol when we are required to poll the file from the FTP server which are in the remote side or outside of the firewall..
Q: What is the use of IDX2?
A: Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.