Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
To send IDocs to the R/3 System, you must first configure the inbound processing function in R/3. All of the generated interfaces use the "BAPI" process code. This code refers to the "BAPI_IDOC_INPUT1" function module, which calls the BAPI (as a standard interface) that is to be started by the electronic form.
Defining a Partner Profile
A partner profile is an entry in which the communication parameters are defined. The values entered in the profile are primarily information that is required in the IDoc control record. The recipient (in our case, an R/3 System) must have a corresponding inbound partner profile for these values so that an assignment can be made.
Configuring a Port
IDocs can be exchanged with external systems across different paths or ports. In our case, a sender port must be defined in the control record of the IDoc and then made known to the relevant R/3 System
BAPI BAPI_IDOC_INPUT1 is a template for IDoc Inbound Processing. In this BAPI, the system will find the related function module based on IDoc Message Type.
For example, if you are dealing message type <b>MBGMCR</b> (Goods Movement) then the system will use FM <b>IDOC_INPUT_MBGMCR</b> for further processing.
In this case, you may want to check FM IDOC_INPUT_MBGMCR whether there are custom exits that can be used to place your own logic.
Bluesky
