SAP MCS_IDOC_ENTRIES_CREATE Function Module for NOTRANSL: LIS: IDoc Systemeinträge anlegen









MCS_IDOC_ENTRIES_CREATE is a standard mcs idoc entries create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: LIS: IDoc Systemeinträge anlegen processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for mcs idoc entries create FM, simply by entering the name MCS_IDOC_ENTRIES_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: MCSE
Program Name: SAPLMCSE
Main Program: SAPLMCSE
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MCS_IDOC_ENTRIES_CREATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'MCS_IDOC_ENTRIES_CREATE'"NOTRANSL: LIS: IDoc Systemeinträge anlegen
EXPORTING
I_IDOCTYP = "IDOC port description
* I_PORTNAME = "Port name, if NEW_PORT = 'X'
* I_PORTTEXT = "Text for port name, if NEW_PORT = 'X'
* I_NEW_PORT = ' ' "Ind.: Port to be created
I_LOGSYS = "Logical system
I_PARNUM = "Partner
* I_NEW_PARTNER = ' ' "Ind. new partner to be created
* I_NEW_LOGSYS = ' ' "Ind. logical system to be created
* I_LOGSYSTXT = "Logical system short text
* I_BASICIDOC = CON_BASIS_IDOC "Basic IDoc
* I_CIMTYP = "Extension IDoc
* I_MESTYP = 'X' "Create message type for IDoc type

EXCEPTIONS
ERROR_EXISTS = 1 IDOC_PORT_UNKNOWN = 2
.



IMPORTING Parameters details for MCS_IDOC_ENTRIES_CREATE

I_IDOCTYP - IDOC port description

Data type: DMCSE-FIDOC
Optional: No
Call by Reference: No ( called with pass by value option)

I_PORTNAME - Port name, if NEW_PORT = 'X'

Data type: DMCSE-PORT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PORTTEXT - Text for port name, if NEW_PORT = 'X'

Data type: DMCSE-PORTTXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_NEW_PORT - Ind.: Port to be created

Data type: XFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_LOGSYS - Logical system

Data type: DMCSE-LOGSYS
Optional: No
Call by Reference: No ( called with pass by value option)

I_PARNUM - Partner

Data type: DMCSE-PARNUM
Optional: No
Call by Reference: No ( called with pass by value option)

I_NEW_PARTNER - Ind. new partner to be created

Data type: XFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_NEW_LOGSYS - Ind. logical system to be created

Data type: XFLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_LOGSYSTXT - Logical system short text

Data type: DMCSE-LOGTXT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BASICIDOC - Basic IDoc

Data type: EDISYN-IDOCTYP
Default: CON_BASIS_IDOC
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CIMTYP - Extension IDoc

Data type: EDISYN-CIMTYP
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MESTYP - Create message type for IDoc type

Data type: XFLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_EXISTS - Errors occurred

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

IDOC_PORT_UNKNOWN - IDoc port is unknown

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MCS_IDOC_ENTRIES_CREATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_i_idoctyp  TYPE DMCSE-FIDOC, "   
lv_error_exists  TYPE DMCSE, "   
lv_i_portname  TYPE DMCSE-PORT, "   
lv_i_porttext  TYPE DMCSE-PORTTXT, "   
lv_i_new_port  TYPE XFLAG, "   SPACE
lv_i_logsys  TYPE DMCSE-LOGSYS, "   
lv_idoc_port_unknown  TYPE DMCSE, "   
lv_i_parnum  TYPE DMCSE-PARNUM, "   
lv_i_new_partner  TYPE XFLAG, "   SPACE
lv_i_new_logsys  TYPE XFLAG, "   SPACE
lv_i_logsystxt  TYPE DMCSE-LOGTXT, "   
lv_i_basicidoc  TYPE EDISYN-IDOCTYP, "   CON_BASIS_IDOC
lv_i_cimtyp  TYPE EDISYN-CIMTYP, "   
lv_i_mestyp  TYPE XFLAG. "   'X'

  CALL FUNCTION 'MCS_IDOC_ENTRIES_CREATE'  "NOTRANSL: LIS: IDoc Systemeinträge anlegen
    EXPORTING
         I_IDOCTYP = lv_i_idoctyp
         I_PORTNAME = lv_i_portname
         I_PORTTEXT = lv_i_porttext
         I_NEW_PORT = lv_i_new_port
         I_LOGSYS = lv_i_logsys
         I_PARNUM = lv_i_parnum
         I_NEW_PARTNER = lv_i_new_partner
         I_NEW_LOGSYS = lv_i_new_logsys
         I_LOGSYSTXT = lv_i_logsystxt
         I_BASICIDOC = lv_i_basicidoc
         I_CIMTYP = lv_i_cimtyp
         I_MESTYP = lv_i_mestyp
    EXCEPTIONS
        ERROR_EXISTS = 1
        IDOC_PORT_UNKNOWN = 2
. " MCS_IDOC_ENTRIES_CREATE




ABAP code using 7.40 inline data declarations to call FM MCS_IDOC_ENTRIES_CREATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single FIDOC FROM DMCSE INTO @DATA(ld_i_idoctyp).
 
 
"SELECT single PORT FROM DMCSE INTO @DATA(ld_i_portname).
 
"SELECT single PORTTXT FROM DMCSE INTO @DATA(ld_i_porttext).
 
DATA(ld_i_new_port) = ' '.
 
"SELECT single LOGSYS FROM DMCSE INTO @DATA(ld_i_logsys).
 
 
"SELECT single PARNUM FROM DMCSE INTO @DATA(ld_i_parnum).
 
DATA(ld_i_new_partner) = ' '.
 
DATA(ld_i_new_logsys) = ' '.
 
"SELECT single LOGTXT FROM DMCSE INTO @DATA(ld_i_logsystxt).
 
"SELECT single IDOCTYP FROM EDISYN INTO @DATA(ld_i_basicidoc).
DATA(ld_i_basicidoc) = CON_BASIS_IDOC.
 
"SELECT single CIMTYP FROM EDISYN INTO @DATA(ld_i_cimtyp).
 
DATA(ld_i_mestyp) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!