ARCHIV_PROCESS_RFCINPUT SAP Function module

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

Associated Function Group: OA01
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM ARCHIV_PROCESS_RFCINPUT - ARCHIV PROCESS RFCINPUT

CALL FUNCTION 'ARCHIV_PROCESS_RFCINPUT' "
  EXPORTING
    document_entry =            " oarfcin       Structure for document inbox per RFC
*   orgobject =                 " swhactor
  IMPORTING
    okcode =                    " sy-tcode      ABAP Program, Current Transaction Code
    messagestring =             " string        Error message
* TABLES
*   document_data =             " oarfcdata     Structure for data transfer of storage system
  EXCEPTIONS
    NO_AUTHORIZATION = 1        "
    NO_WORKITEM_CREATED = 2     "
    ERROR_PARAMETER = 3         "
    .  "  ARCHIV_PROCESS_RFCINPUT

ABAP code example for Function Module ARCHIV_PROCESS_RFCINPUT

The ABAP code below is a full code listing to execute function module ARCHIV_PROCESS_RFCINPUT 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_okcode  
 
 TYPE SY-TCODE
,
ld_messagestring  
 
 TYPE STRING
,
it_document_data  
 
 TYPE STANDARD TABLE OF OARFCDATA,"TABLES PARAM
wa_document_data
 
 LIKE LINE OF it_document_data
.


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

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

"populate fields of struture and append to itab
append wa_document_data to it_document_data.
.

CALL FUNCTION 'ARCHIV_PROCESS_RFCINPUT'
  EXPORTING
    document_entry =             ld_document_entry
*   orgobject =                  ld_orgobject
  IMPORTING
    okcode =                     ld_okcode
    messagestring =              ld_messagestring
* TABLES
*   document_data =              it_document_data
  EXCEPTIONS
    NO_AUTHORIZATION =           1
    NO_WORKITEM_CREATED =        2
    ERROR_PARAMETER =            3
    .  "  ARCHIV_PROCESS_RFCINPUT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "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_okcode
 
 TYPE SY-TCODE ,
ld_document_entry
 
 TYPE OARFCIN ,
it_document_data
 
 TYPE STANDARD TABLE OF OARFCDATA ,
wa_document_data
 
 LIKE LINE OF it_document_data,
ld_messagestring
 
 TYPE STRING ,
ld_orgobject
 
 TYPE SWHACTOR .


ld_document_entry = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_document_data to it_document_data.
ld_orgobject = 'Check type of data required'.