We will be sending iDocs via xml file, so this step is not required. Terms of payment key for bill of exchange charges, Key date of the last interest calculation, Export credit insurance institution number, Indicator for periodic account statements, Bill of exchange limit (in local currency), Date of the last interest calculation run, Tolerance group for the business partner/G/L account, Subsidy indicator for determining the reduction rates, Key of the Lockbox to Which the Customer Is To Pay, Accounting clerks fax number at the customer/vendor, Internet address of partner company clerk, Deletion bock for master record (company code level), Accounting clerks telephone number at business partner. Trigger Outbound Idoc on Customer Master change/ Create - SAP as the Middleware system like EDI / Mulesoft receive the inbound data which could be in the flat file, xml format. Sometimes the fields in standard iDoc type, like ALEAUD, ACC_INVOICE_, ACC_BILLING_ , CREMAS etc are not sufficient. Partner status good information which is not available everywhere, Hello,Thank you for this very rewarding article.However, I have a problem.I hope you can have the solution.In BD64, even though I put my filters on an organizational ELEC structure for example: the generated idocs are also generated on the GAZ organizational structures. SAP Variant Configuration That Will Actually Make Your Life Better. But i want to know why system read field even the field is suppress. determine which IDoc type is dispatched to which receiver port with which logical message. Each basic type defines the basic IDoc segments, the format of data fields, and the size. Let's check out some more detailed information about the records present in each IDoc. , create a partner profile ( IDoc. Simple Guidance for You In SAP MM Interview Questions. Hi Isuru,Does the above program RBDMIDOC supports for Newly created customer master or only once changes are performed. Partner Profile: Partner profile contains parameters that define the electronic interchange of data with a partner via IDoc interface. E.g: ECW_00_800, Create Logical Systems with naming convention system name+CLNT+client no ex: example for receiving system e.g. WP_PER01 is not activated for version 700 ( message getting on WE60 ). Function module MASTER_IDOC_DISTRIBUTE was leveraged to create the outbound IDoc. An outbound iDoc is triggered in SAP. the IDOC is generated sucessfully. The type of port is what defines the data contained in the port. This is important - the IDoc number on one system does not uniquely identify the same IDoc on another system! Complete Guide on trigger an outbound IDoc when Good receipt - SAP To test change pointers,change condition values using transaction VK12.VK12 Change Condition values. Change pointers were turned on, but we could not find ODTF_CCTR message type in the list.