1. Have you Idoc adapter?

If yes can you tell me the business requirement to go for the Idoc
adapter?

Ans: Yes I worked on Idoc adapter. If we to fetch the data from SAP system and it is a standard
structure and it is huge amount of data then we go for Idoc adapter.

2. Can you take one Idoc to file scenario and explain business requirement to implement that
scenario?

Ans: If you want to fetch the data from SAP system in the form of standard structure of Idoc to post
in file based system in the form file based system structure then we need to implement Idoc to file
scenario.

3. Can you tell me basic type and message type names for Idoc scenario’s what you implemented
recently?

Ans: In my current project we implemented one Idoc to file interface in that Idoc we are using
Invoice details and vendor master data in that message types are CREMAS and INVOIC and basic
types are CREMAS05 and INOVIC04.

4. Have you used any enhanced Idoc? If yes can you tell me the basic and message type and why
you used enhanced Idoc?

Ans: Yes I used one enhanced Idoc in my previous project. We are enhancing the customer master
data Idoc. In that Idoc basic type is ZDEBMAS05 and message type is ZDEBMAS.

5. What is the communication available to communicate SAP systems and tell me which one is
better communication to communicate SAP system?

Ans:

6. Can you use Idoc for synchronous communication?

Ans: No, we can’t implement Idoc for synchronous communication. It will work only for
asynchronous communication.

7. What is the business requirement to choose Idoc’s or in which case we go for Idoc’s?

Ans: If you are fetching the data from SAP system and it will be inbuilt structure for your
requirement and we has to pass less amount of data then we go for the Idoc.

8. What is the configuration settings required to implement Idoc to file scenario in ECC and PI level
in case of dual stack?

Ans: first we need to create one Rfc destination at ECC level using SM59 T-code and connection type
should be 3/ABAP/R3. Once we create a Rfc destination next we need to create one port at ECC level
using T-code WE21. And port type should be TRfc next we need to create two logical system one for
ECC and another for PI using T-code BD54 next we need to assign these logical systems into
corresponding clients using T-code SCC4. Finally we need to create partner profile at ECC level using
T-code WE20 and partner type should be LS. Once we can complete these many settings in ECC level
next we need to create Rfc destination in PI level using T-code SM59. Next we need to create port
and metadata at PI level using T-codes IDX1 & IDX2 vice versa.

9. What you mean by partner profile? What is T-code to create partner profile? What parameters
you have to maintain in partner profile?

Ans:

10. What is use of IDX2 T-code?

Ans: To create metadata at PI level we need to use IDX2 T-code.

11. What is the purpose of metadata?

Ans: Metadata is nothing but Idoc structure we need to import corresponding Idoc structure in PI
system using T-code IDX2.

12. What is the connection type for Idoc_AAE?

Ans:

13. I have trigger one Idoc it is successful in SAP but it is not reached to the PI? How you are going to
troubleshoot this issue?

Ans: In this case we need to monitor TRfc level using T-code SM58. There we can find why it is not
reached to the PI. In this stage we can resolve that issue then Idoc automatically reached to the PI.

14. Where we can see the list of status codes and its description?

Ans: In SAP system we can see the list of T-codes and its description using T-code WE47.

15. If Idoc is successful dispatched from SAP what status code we see in SAP?

Ans: 03 status code.

16. If Idoc is successful posted in SAP what status code we see in SAP?

Ans: 53 status code.

17. What is the T-code we have to see the status of processed Idoc’s?

Ans: Using WE02 T-code we can see status of processed Idoc’s based on Idoc number.

18. Have you worked on Idoc packaging or collect multiple Idoc’s? If yes can you tell me the step by
step?
Ans:

19. In one case sender side communication channel is required can you tell me that case?

Ans: If you want to fetch the multiple Idoc’s from one SAP system in that case we need to use
sender side communication channel.

20. If you going to use sender side Idoc adapter then communication channel and agreement is
required or not?

Ans:

21. Can you tell me the table names of control data and status records?

Ans: EDIDC and EDIDS.

22. Can you tell me the some of Idoc fields names what you used in your scenarios?

Ans:

23. I have implemented Idoc to file scenario it is working fine. After 6 months client asked add 2
more Zfields in existing Idoc. Can you tell me what are the things you need to perform in ECC
and PI?

Ans: First we need to reimport that Idoc

24. I have implemented Idoc to file scenario. It is working fine after some days client asked add 2
more Zfields in existing Idoc and corresponding new structure imported in PI and mapping also
done. Even though it is posted old Idoc data. How to resolve this issue?
25. I have implemented Idoc to file scenario. But I am getting one error in SXMB_MONI. i.e unable
to convert ALE logical messages for particular business system. How to resolve this issue?
26. I have implemented Idoc to file scenario. But I am getting one error in SXMB_MONI. i.e
obligatory node is missing. How to resolve this issue?
27. While creating a metadata using T-code IDX2 it is giving error like this I:00? What is the root cost
for this issue and how to resolve this issue?
28. What are errors you received for Idoc scenarios and how to resolve this issues?
29. What is the T-code to create a port in ECC and PI level?
30. Have worked on Idoc scenario’s using single stack in latest PO 7.5 version? If yes how to
implement this scenario in PO?
31. What are configurations required in ECC and PI in Idoc_AAE?
32. How to monitor the Idoc in PI in case of dual and single stack?
33. We are getting one file from source the file contains multiple records for each record I want to
generate one separate Idoc? Can you implement this requirement? If yes how implement?
34. Have you worked on Idoc tricky method? If yes what is the business requirement?
35. Can you tell me the end to end troubleshooting steps in case of Idoc to file scenario in dual stack
and single stack?
36. Can you tell me the sender Idoc_AAE communication channel parameters?
37. What are RFC parameter types in Idoc_AAE sender channel when we go for the each option?
38. I would like to pass control record value at runtime. Instead of passing this constants at design
level? Can you implement this requirement? If yes how to implement this requirement?
39. Where we see the Idoc metadata in single stack?
40. Can you tell me the disadvantages of Idoc?
41. What is the T-code available to create custom Idoc’s?
42. Can you tell me the end to end troubleshooting steps in case of file to Idoc scenario?
43. How to check the Rfc destination whether it is working fine or not? Assume that you don’t have
SM59 T-code access?
44. How to trigger Idoc from SAP system?
45. Can you tell me the T-code to reprocess failed Idoc’s?