MSEIDOC0 is a standard Module pool for a dialog screen ABAP Program available within your SAP system (depending on your version and release level). It is used for The program takes an
If you would like to execute this report or see the full code listing simply enter MSEIDOC0 into the relevant SAP transactions such as SE38 or SE80
Below is a list of transaction codes which are relevant to this SAP report
WE12 - Test Modified Inbound File
WE15 - Test Outbound Processing from MC
WE16 - Test Inbound File
WE17 - Test Status File
This report can be called from another progam/report simply by using the ABAP SUBMIT statement, see below for example ABAP code snipts of how to do this.
Title: Modification of an Outbound File and Triggering of Inbound Processing
Text Symbol: TST = User settings...
Text Symbol: 002 = Inbound
Text Symbol: 001 = Outbound
INCLUDE IDOC0FRM.
No SAP DATABASE tables are accessed within this REPORT code!
EDI_DATA_INCOMING CALL FUNCTION 'EDI_DATA_INCOMING' EXPORTING pathname = edunix-oldpath port = edunix-sndpor EXCEPTIONS OTHERS = 1.
EDI_PARTNER_GET_DESCRIPTION CALL FUNCTION 'EDI_PARTNER_GET_DESCRIPTION' EXPORTING pi_partyp = edunix-sndprt pi_parnum = edunix-sndprn IMPORTING pe_descrp = sndprn_desc EXCEPTIONS no_valid_partner_type = 1 OTHERS = 2.
EDI_PARTNER_GET_DESCRIPTION CALL FUNCTION 'EDI_PARTNER_GET_DESCRIPTION' EXPORTING pi_partyp = edunix-rcvprt pi_parnum = edunix-rcvprn IMPORTING pe_descrp = rcvprn_desc EXCEPTIONS no_valid_partner_type = 1 OTHERS = 2.
Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.
MSEIDOC0 - Modification of an Outbound File and Triggering of Inbound Processing MSEIDOC0 - Modification of an Outbound File and Triggering of Inbound Processing MSEDTTOP - ABAP/4 Editor: Global Data MSEDTT0P - Global Parameters for Module Pool SAPMSEDS MSEDTO01 - Editor output modules MSEDTI01 - Input modules for editor