SAP Tables

EXIT_SAPLF050_004 SAP Function module - FIDCC1 Incoming IDoc: Change/Do Not Process IDoc




EXIT_SAPLF050_004is a standard SAP function module available within R/3 SAPsystems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import/export parameters, exceptions etc as well as any documentation contributions specific to the object. See here to view full function module documentation and code listing, simply by entering the name EXIT_SAPLF050_004 into the relevant SAP transaction such as SE37 or SE80.

Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name EXIT_SAPLF050_004 or its description.


Pattern for FM EXIT_SAPLF050_004 - EXIT SAPLF050 004
Associated Function Group: X050
Released Date: Not Released
CALL FUNCTION 'EXIT_SAPLF050_004' "FIDCC1 Incoming IDoc: Change/Do Not Process IDoc
  EXPORTING
    message_type =              " edmsg-msgtyp  Message Type "FIDCC1"
    idoc_docnum =               " edidc-docnum  IDoc number
*   idoc_contrl =               " edidc         Control Record (IDoc)
  TABLES
    idoc_data =                 " edidd         IDoc Application Data
* CHANGING
*   posting_type =              " boole         Type of IDoc Additional Processing
    .  "  EXIT_SAPLF050_004

ABAP code example for Function Module EXIT_SAPLF050_004

The ABAP code below is a full code listing to execute function module EXIT_SAPLF050_004 including all data declarations. The code uses the latest in-line data declaration syntax but I have included an abap code snipet at the end to show how declarations would look using the original method of declaring data variables up front. 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).
DATA:
it_idoc_data   TYPE STANDARD TABLE OF EDIDD,"tables param
wa_idoc_data LIKE LINE OF it_idoc_data  .

DATA(ld_posting_type) = 'Check type of data required'.

SELECT single MSGTYP
FROM EDMSG
INTO @DATA(ld_message_type).


SELECT single DOCNUM
FROM EDIDC
INTO @DATA(ld_idoc_docnum).

DATA(ld_idoc_contrl) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.. CALL FUNCTION 'EXIT_SAPLF050_004' EXPORTING message_type = ld_message_type idoc_docnum = ld_idoc_docnum * idoc_contrl = ld_idoc_contrl TABLES idoc_data = it_idoc_data * CHANGING * posting_type = ld_posting_type . " EXIT_SAPLF050_004
IF SY-SUBRC EQ 0.   "All OK ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
ld_posting_type TYPE BOOLE ,
ld_message_type TYPE EDMSG-MSGTYP ,
it_idoc_data TYPE STANDARD TABLE OF EDIDD ,
wa_idoc_data LIKE LINE OF it_idoc_data,
ld_idoc_docnum TYPE EDIDC-DOCNUM ,
ld_idoc_contrl TYPE EDIDC .

ld_posting_type = 'Check type of data required'.

SELECT single MSGTYP
FROM EDMSG
INTO ld_message_type.


"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.

SELECT single DOCNUM
FROM EDIDC
INTO ld_idoc_docnum.

ld_idoc_contrl = 'Check type of data required'..