SAP 0C10_GET_VALID_STATUS Function Module for









0C10_GET_VALID_STATUS is a standard 0c10 get valid status 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 0c10 get valid status FM, simply by entering the name 0C10_GET_VALID_STATUS into the relevant SAP transaction such as SE37 or SE38.

Function Group: 0C10
Program Name: SAPL0C10
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function 0C10_GET_VALID_STATUS 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 '0C10_GET_VALID_STATUS'"
EXPORTING
ID_SENDERART = "

TABLES
* ET_STATUS = "
* ET_STATUS_TEXTS = "
.



IMPORTING Parameters details for 0C10_GET_VALID_STATUS

ID_SENDERART -

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

TABLES Parameters details for 0C10_GET_VALID_STATUS

ET_STATUS -

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

ET_STATUS_TEXTS -

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

Copy and paste ABAP code example for 0C10_GET_VALID_STATUS 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:
lt_et_status  TYPE STANDARD TABLE OF TKB10SSA, "   
lv_id_senderart  TYPE TKB10SSA-SENDERART, "   
lt_et_status_texts  TYPE STANDARD TABLE OF TJ02T. "   

  CALL FUNCTION '0C10_GET_VALID_STATUS'  "
    EXPORTING
         ID_SENDERART = lv_id_senderart
    TABLES
         ET_STATUS = lt_et_status
         ET_STATUS_TEXTS = lt_et_status_texts
. " 0C10_GET_VALID_STATUS




ABAP code using 7.40 inline data declarations to call FM 0C10_GET_VALID_STATUS

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 SENDERART FROM TKB10SSA INTO @DATA(ld_id_senderart).
 
 


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!