CEP_DOC_PARSE_XML_AND_SAVE SAP Function module - Reads original file (XML) and stores the result

CEP_DOC_PARSE_XML_AND_SAVE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CEP_DOC_PARSE_XML_AND_SAVE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CE_CL
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM CEP_DOC_PARSE_XML_AND_SAVE - CEP DOC PARSE XML AND SAVE

CALL FUNCTION 'CEP_DOC_PARSE_XML_AND_SAVE' "Reads original file (XML) and stores the result
  EXPORTING
    pf_dokar =                  " draw-dokar    Document type
    pf_doknr =                  " draw-doknr    Document number
    pf_dokvr =                  " draw-dokvr    Document version
    pf_doktl =                  " draw-doktl    Document part
*   pf_changenum =              " draw-aennr    Change number
*   pf_keydate =                " draw-adatum   Output date for document
*   pf_app_type = 'XML'         " draw-dappl    XML Application Type
*   pf_original_name = 'CLASSIFICATION'  " cvapi_doc_file-description  Name of the XML Originale
* TABLES
*   pt_char_vals =              " characteristic_vals  Table to hold classification-characteristic-value data
*   error_msgs =                " messages      Optional table which is used to record error messages
  EXCEPTIONS
    DOCUMENT_NOT_FOUND = 1      "               Document Not Found in DMS
    .  "  CEP_DOC_PARSE_XML_AND_SAVE

ABAP code example for Function Module CEP_DOC_PARSE_XML_AND_SAVE

The ABAP code below is a full code listing to execute function module CEP_DOC_PARSE_XML_AND_SAVE including all data declarations. The code uses 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 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_pt_char_vals  
 
 TYPE STANDARD TABLE OF CHARACTERISTIC_VALS,"TABLES PARAM
wa_pt_char_vals
 
 LIKE LINE OF it_pt_char_vals
,
it_error_msgs  
 
 TYPE STANDARD TABLE OF MESSAGES,"TABLES PARAM
wa_error_msgs
 
 LIKE LINE OF it_error_msgs
.

 

SELECT single DOKAR 
  FROM DRAW 
  INTO @DATA(ld_pf_dokar).

 

SELECT single DOKNR 
  FROM DRAW 
  INTO @DATA(ld_pf_doknr).

 

SELECT single DOKVR 
  FROM DRAW 
  INTO @DATA(ld_pf_dokvr).

 

SELECT single DOKTL 
  FROM DRAW 
  INTO @DATA(ld_pf_doktl).

 

SELECT single AENNR 
  FROM DRAW 
  INTO @DATA(ld_pf_changenum).

 

SELECT single ADATUM 
  FROM DRAW 
  INTO @DATA(ld_pf_keydate).

 

SELECT single DAPPL 
  FROM DRAW 
  INTO @DATA(ld_pf_app_type).



DATA(ld_pf_original_name) = some text here
 

"populate fields of struture and append to itab
append wa_pt_char_vals to it_pt_char_vals.
 

"populate fields of struture and append to itab
append wa_error_msgs to it_error_msgs.
.

CALL FUNCTION 'CEP_DOC_PARSE_XML_AND_SAVE'
  EXPORTING
    pf_dokar =                   ld_pf_dokar
    pf_doknr =                   ld_pf_doknr
    pf_dokvr =                   ld_pf_dokvr
    pf_doktl =                   ld_pf_doktl
*   pf_changenum =               ld_pf_changenum
*   pf_keydate =                 ld_pf_keydate
*   pf_app_type =                ld_pf_app_type
*   pf_original_name =           ld_pf_original_name
* TABLES
*   pt_char_vals =               it_pt_char_vals
*   error_msgs =                 it_error_msgs
  EXCEPTIONS
    DOCUMENT_NOT_FOUND =         1
    .  "  CEP_DOC_PARSE_XML_AND_SAVE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_pf_dokar
 
 TYPE DRAW-DOKAR ,
it_pt_char_vals
 
 TYPE STANDARD TABLE OF CHARACTERISTIC_VALS ,
wa_pt_char_vals
 
 LIKE LINE OF it_pt_char_vals,
ld_pf_doknr
 
 TYPE DRAW-DOKNR ,
it_error_msgs
 
 TYPE STANDARD TABLE OF MESSAGES ,
wa_error_msgs
 
 LIKE LINE OF it_error_msgs,
ld_pf_dokvr
 
 TYPE DRAW-DOKVR ,
ld_pf_doktl
 
 TYPE DRAW-DOKTL ,
ld_pf_changenum
 
 TYPE DRAW-AENNR ,
ld_pf_keydate
 
 TYPE DRAW-ADATUM ,
ld_pf_app_type
 
 TYPE DRAW-DAPPL ,
ld_pf_original_name
 
 TYPE CVAPI_DOC_FILE-DESCRIPTION .



SELECT single DOKAR 
  FROM DRAW 
  INTO ld_pf_dokar.
 

"populate fields of struture and append to itab
append wa_pt_char_vals to it_pt_char_vals.

SELECT single DOKNR 
  FROM DRAW 
  INTO ld_pf_doknr.
 

"populate fields of struture and append to itab
append wa_error_msgs to it_error_msgs.

SELECT single DOKVR 
  FROM DRAW 
  INTO ld_pf_dokvr.


SELECT single DOKTL 
  FROM DRAW 
  INTO ld_pf_doktl.


SELECT single AENNR 
  FROM DRAW 
  INTO ld_pf_changenum.


SELECT single ADATUM 
  FROM DRAW 
  INTO ld_pf_keydate.


SELECT single DAPPL 
  FROM DRAW 
  INTO ld_pf_app_type.


ld_pf_original_name = some text here