SAP Function Modules

SA_DOCUMENTS_BEFORE_EXPORT SAP Function module







SA_DOCUMENTS_BEFORE_EXPORT 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 SA_DOCUMENTS_BEFORE_EXPORT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SA_TRANSPORT_EXITS
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM SA_DOCUMENTS_BEFORE_EXPORT - SA DOCUMENTS BEFORE EXPORT





CALL FUNCTION 'SA_DOCUMENTS_BEFORE_EXPORT' "
  EXPORTING
    iv_client = '000'           " e070c-client  Source client of request
*   iv_datafile =               " c
  IMPORTING
    error =                     " flag          General Flag
  TABLES
    tt_e071 =                   " e071          Change & Transport System: Object Entries of Requests/Tasks
    tt_e071k =                  " e071k         Change & Transport System: Key Entries of Requests/Tasks
*   t_protocol =                " sprot_u       Log Generation Interface
    .  "  SA_DOCUMENTS_BEFORE_EXPORT

ABAP code example for Function Module SA_DOCUMENTS_BEFORE_EXPORT





The ABAP code below is a full code listing to execute function module SA_DOCUMENTS_BEFORE_EXPORT 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:
ld_error  TYPE FLAG ,
it_tt_e071  TYPE STANDARD TABLE OF E071,"TABLES PARAM
wa_tt_e071  LIKE LINE OF it_tt_e071 ,
it_tt_e071k  TYPE STANDARD TABLE OF E071K,"TABLES PARAM
wa_tt_e071k  LIKE LINE OF it_tt_e071k ,
it_t_protocol  TYPE STANDARD TABLE OF SPROT_U,"TABLES PARAM
wa_t_protocol  LIKE LINE OF it_t_protocol .


SELECT single CLIENT
FROM E070C
INTO @DATA(ld_iv_client).

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

"populate fields of struture and append to itab
append wa_tt_e071 to it_tt_e071.

"populate fields of struture and append to itab
append wa_tt_e071k to it_tt_e071k.

"populate fields of struture and append to itab
append wa_t_protocol to it_t_protocol. . CALL FUNCTION 'SA_DOCUMENTS_BEFORE_EXPORT' EXPORTING iv_client = ld_iv_client * iv_datafile = ld_iv_datafile IMPORTING error = ld_error TABLES tt_e071 = it_tt_e071 tt_e071k = it_tt_e071k * t_protocol = it_t_protocol . " SA_DOCUMENTS_BEFORE_EXPORT
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_error  TYPE FLAG ,
ld_iv_client  TYPE E070C-CLIENT ,
it_tt_e071  TYPE STANDARD TABLE OF E071 ,
wa_tt_e071  LIKE LINE OF it_tt_e071,
ld_iv_datafile  TYPE C ,
it_tt_e071k  TYPE STANDARD TABLE OF E071K ,
wa_tt_e071k  LIKE LINE OF it_tt_e071k,
it_t_protocol  TYPE STANDARD TABLE OF SPROT_U ,
wa_t_protocol  LIKE LINE OF it_t_protocol.


SELECT single CLIENT
FROM E070C
INTO ld_iv_client.


"populate fields of struture and append to itab
append wa_tt_e071 to it_tt_e071.
ld_iv_datafile = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_tt_e071k to it_tt_e071k.

"populate fields of struture and append to itab
append wa_t_protocol to it_t_protocol.

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 SA_DOCUMENTS_BEFORE_EXPORT or its description.