SAP RSTR_DECODE_ACA_ENTRY Function Module for









RSTR_DECODE_ACA_ENTRY is a standard rstr decode aca entry SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rstr decode aca entry FM, simply by entering the name RSTR_DECODE_ACA_ENTRY into the relevant SAP transaction such as SE37 or SE38.

Function Group: STR1
Program Name: SAPLSTR1
Main Program: SAPLSTR1
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RSTR_DECODE_ACA_ENTRY 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 'RSTR_DECODE_ACA_ENTRY'"
  EXPORTING
   ENTRY =  "
*  ENTRY_2 =  "

 IMPORTING
   REPORT_NAME =  "
   MANAGEMENT_ACTION =  "
   PART =  "
   FORM_NAME =  "
   RETURN_CODE =  "
   DURATION =  "Runtime
   LENGTH_OF_DATA =  "
   OFFSET_IN_1 =  "
   OFFSET_IN_2 =  "
   LINKNUMBER =  "
   MESSAGENUMBER =  "

EXCEPTIONS
   ENTRY_2_NEEDED = 1    ENTRY_2_IS_NO_EXTENSION = 2    INCONSISTENT_ENTRY = 3    NOT_A_ACA_ENTRY = 4
.



IMPORTING Parameters details for RSTR_DECODE_ACA_ENTRY

ENTRY -

Data type: RSTRENTR
Optional: No
Call by Reference: Yes

ENTRY_2 -

Data type: RSTRENTR
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for RSTR_DECODE_ACA_ENTRY

REPORT_NAME -

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

MANAGEMENT_ACTION -

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

PART -

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

FORM_NAME -

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

RETURN_CODE -

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

DURATION - Runtime

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

LENGTH_OF_DATA -

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

OFFSET_IN_1 -

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

OFFSET_IN_2 -

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

LINKNUMBER -

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

MESSAGENUMBER -

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

EXCEPTIONS details

ENTRY_2_NEEDED -

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

ENTRY_2_IS_NO_EXTENSION -

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

INCONSISTENT_ENTRY -

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

NOT_A_ACA_ENTRY -

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

Copy and paste ABAP code example for RSTR_DECODE_ACA_ENTRY 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_entry  TYPE RSTRENTR, "   
lv_report_name  TYPE RSTRENTR, "   
lv_entry_2_needed  TYPE RSTRENTR, "   
lv_management_action  TYPE RSTRENTR, "   
lv_part  TYPE RSTRENTR, "   
lv_entry_2  TYPE RSTRENTR, "   
lv_form_name  TYPE RSTRENTR, "   
lv_entry_2_is_no_extension  TYPE RSTRENTR, "   
lv_return_code  TYPE RSTRENTR, "   
lv_inconsistent_entry  TYPE RSTRENTR, "   
lv_duration  TYPE RSTRENTR, "   
lv_not_a_aca_entry  TYPE RSTRENTR, "   
lv_length_of_data  TYPE RSTRENTR, "   
lv_offset_in_1  TYPE RSTRENTR, "   
lv_offset_in_2  TYPE RSTRENTR, "   
lv_linknumber  TYPE RSTRENTR, "   
lv_messagenumber  TYPE RSTRENTR. "   

  CALL FUNCTION 'RSTR_DECODE_ACA_ENTRY'  "
    EXPORTING
         ENTRY = lv_entry
         ENTRY_2 = lv_entry_2
    IMPORTING
         REPORT_NAME = lv_report_name
         MANAGEMENT_ACTION = lv_management_action
         PART = lv_part
         FORM_NAME = lv_form_name
         RETURN_CODE = lv_return_code
         DURATION = lv_duration
         LENGTH_OF_DATA = lv_length_of_data
         OFFSET_IN_1 = lv_offset_in_1
         OFFSET_IN_2 = lv_offset_in_2
         LINKNUMBER = lv_linknumber
         MESSAGENUMBER = lv_messagenumber
    EXCEPTIONS
        ENTRY_2_NEEDED = 1
        ENTRY_2_IS_NO_EXTENSION = 2
        INCONSISTENT_ENTRY = 3
        NOT_A_ACA_ENTRY = 4
. " RSTR_DECODE_ACA_ENTRY




ABAP code using 7.40 inline data declarations to call FM RSTR_DECODE_ACA_ENTRY

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!