RFC destination creation in SAP IDOC (2024)

In this session, SAP SD AND ABAP LEAGUE SUPPORT Raj is going to discuss about how to create RFC destination related IDOCs in SAP. For this we should use transaction code SM59. Ideally its activity from BASIS end. But as a SAP SD consultant it should good to have this knowledge about this RFC creation. In Support project/Implementation project we might get requirement to set up new IDOC and at this time this config will be very helpful. This video will be very helpful in such case of requirements. IDOC configuration in SAP SD.
Subscribe and hit the bell to see new videos: / @sapsdandabapleaguesup...
Check out my channel: / @sapsdandabapleaguesup...
Playlist for more videos related to IDOCS:
• IDOCS

[@neerajnagar120]

Very well explained.

[@SAPSDANDABAPLEAGUESUPPORT]

Thank you

[@madhavarao678]

Thank you sir. Sir, my doubt is, how idoc destination is decided? For example, customer classification edi type has two values, 1. Edi, 2. Web edi. Now, an output is generating idoc from sales order/delivery/invoice. That idoc should go to partner system x if customer classification is edi, partner system y if classification is web edi. Are they controlled by message function and msg variant? If yes, how is it possible.. kindly consider my request and help to understand the idoc setting. Regards sir.

[@SAPSDANDABAPLEAGUESUPPORT]

For both of these RFC Type should be “TCP/IP connection” only. Both will be transferred via PI only. In case of two different destinations we should create two different RFC and two different ports. Based on destination PI team can transfer it to different vendors. That means PI team is the responsible here.

[@mahaboobbasha5635]

Hi sir is that possible to stop the CF orders based on plant.
Here the requirement is system should block the CF order creation based on the plant.

[@SAPSDANDABAPLEAGUESUPPORT]

Yes, that’s very much possible. Let’s add piece of code in MV45AFZZ -> USEREXIT_SAVE_DOCUMENT_PREPARE based on sales document type and plant