SAP STPU1_BUFFER_USEDIN Function Module for NOTRANSL: Pseudo-USEDIN auf der STEP_INSTANCE Tabelle









STPU1_BUFFER_USEDIN is a standard stpu1 buffer usedin SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Pseudo-USEDIN auf der STEP_INSTANCE Tabelle processing and below is the pattern details for this FM, 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 stpu1 buffer usedin FM, simply by entering the name STPU1_BUFFER_USEDIN into the relevant SAP transaction such as SE37 or SE38.

Function Group: STPU1
Program Name: SAPLSTPU1
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function STPU1_BUFFER_USEDIN 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 'STPU1_BUFFER_USEDIN'"NOTRANSL: Pseudo-USEDIN auf der STEP_INSTANCE Tabelle
EXPORTING
INSTANCE_OID = "
ENTITY_NAME = "
ATTR_INDEX = "
* ALL_USAGES = ' ' "

IMPORTING
OID_LIST = "

TABLES
STEP_INSTANCES = "
STEP_VALUES = "
.



IMPORTING Parameters details for STPU1_BUFFER_USEDIN

INSTANCE_OID -

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

ENTITY_NAME -

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

ATTR_INDEX -

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

ALL_USAGES -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for STPU1_BUFFER_USEDIN

OID_LIST -

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

TABLES Parameters details for STPU1_BUFFER_USEDIN

STEP_INSTANCES -

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

STEP_VALUES -

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

Copy and paste ABAP code example for STPU1_BUFFER_USEDIN 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_oid_list  TYPE CASTP_OID_LIST, "   
lv_instance_oid  TYPE STEP_INSTANCE-STEP_ID, "   
lt_step_instances  TYPE STANDARD TABLE OF STEP_INSTANCE, "   
lv_entity_name  TYPE STEP_INSTANCE-ENTITY_NAME, "   
lt_step_values  TYPE STANDARD TABLE OF STEP_LONG_VALUE, "   
lv_attr_index  TYPE C, "   
lv_all_usages  TYPE C. "   SPACE

  CALL FUNCTION 'STPU1_BUFFER_USEDIN'  "NOTRANSL: Pseudo-USEDIN auf der STEP_INSTANCE Tabelle
    EXPORTING
         INSTANCE_OID = lv_instance_oid
         ENTITY_NAME = lv_entity_name
         ATTR_INDEX = lv_attr_index
         ALL_USAGES = lv_all_usages
    IMPORTING
         OID_LIST = lv_oid_list
    TABLES
         STEP_INSTANCES = lt_step_instances
         STEP_VALUES = lt_step_values
. " STPU1_BUFFER_USEDIN




ABAP code using 7.40 inline data declarations to call FM STPU1_BUFFER_USEDIN

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.

 
"SELECT single STEP_ID FROM STEP_INSTANCE INTO @DATA(ld_instance_oid).
 
 
"SELECT single ENTITY_NAME FROM STEP_INSTANCE INTO @DATA(ld_entity_name).
 
 
 
DATA(ld_all_usages) = ' '.
 


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!