SAP CS_SO_READ_CONF Function Module for NOTRANSL: Ausgabe des Zustandes der Konfiguration









CS_SO_READ_CONF is a standard cs so read conf 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: Ausgabe des Zustandes der Konfiguration 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 cs so read conf FM, simply by entering the name CS_SO_READ_CONF into the relevant SAP transaction such as SE37 or SE38.

Function Group: CSSO
Program Name: SAPLCSSO
Main Program: SAPLCSSO
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CS_SO_READ_CONF 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 'CS_SO_READ_CONF'"NOTRANSL: Ausgabe des Zustandes der Konfiguration
  EXPORTING
   I_VBELN =  "Sales Order
   I_VBPOS =  "Sales order item
*  I_CUOBJ =  "Configuration

 IMPORTING
   E_INST_FREE =  "Instance Released (Variant Configuration)
   E_INST_LOCKD =  "Instance Locked (Variant Configuration)
   E_INST_INCON =  "Instance Inconsistent (Variant Configuration)
   E_INST_INCOM =  "Instance Incomplete (Variant Configuration)
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCSSO_001 Order/WBS BOM, HTML control
EXIT_SAPLCSSO_002 Order-,Project-,Material BOM. Explos.-/Creation-/Default Date for Browser
EXIT_SAPLCSSO_003 Customer-specific processing result of an explosion in the browser

IMPORTING Parameters details for CS_SO_READ_CONF

I_VBELN - Sales Order

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

I_VBPOS - Sales order item

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

I_CUOBJ - Configuration

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

EXPORTING Parameters details for CS_SO_READ_CONF

E_INST_FREE - Instance Released (Variant Configuration)

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

E_INST_LOCKD - Instance Locked (Variant Configuration)

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

E_INST_INCON - Instance Inconsistent (Variant Configuration)

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

E_INST_INCOM - Instance Incomplete (Variant Configuration)

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

Copy and paste ABAP code example for CS_SO_READ_CONF 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_i_vbeln  TYPE KDST-VBELN, "   
lv_e_inst_free  TYPE BAPICUXPL2-INST_FREE, "   
lv_i_vbpos  TYPE KDST-VBPOS, "   
lv_e_inst_lockd  TYPE BAPICUXPL2-INST_LOCKD, "   
lv_i_cuobj  TYPE VBAP-CUOBJ, "   
lv_e_inst_incon  TYPE BAPICUXPL2-INST_INCON, "   
lv_e_inst_incom  TYPE BAPICUXPL2-INST_INCOM. "   

  CALL FUNCTION 'CS_SO_READ_CONF'  "NOTRANSL: Ausgabe des Zustandes der Konfiguration
    EXPORTING
         I_VBELN = lv_i_vbeln
         I_VBPOS = lv_i_vbpos
         I_CUOBJ = lv_i_cuobj
    IMPORTING
         E_INST_FREE = lv_e_inst_free
         E_INST_LOCKD = lv_e_inst_lockd
         E_INST_INCON = lv_e_inst_incon
         E_INST_INCOM = lv_e_inst_incom
. " CS_SO_READ_CONF




ABAP code using 7.40 inline data declarations to call FM CS_SO_READ_CONF

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 VBELN FROM KDST INTO @DATA(ld_i_vbeln).
 
"SELECT single INST_FREE FROM BAPICUXPL2 INTO @DATA(ld_e_inst_free).
 
"SELECT single VBPOS FROM KDST INTO @DATA(ld_i_vbpos).
 
"SELECT single INST_LOCKD FROM BAPICUXPL2 INTO @DATA(ld_e_inst_lockd).
 
"SELECT single CUOBJ FROM VBAP INTO @DATA(ld_i_cuobj).
 
"SELECT single INST_INCON FROM BAPICUXPL2 INTO @DATA(ld_e_inst_incon).
 
"SELECT single INST_INCOM FROM BAPICUXPL2 INTO @DATA(ld_e_inst_incom).
 


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!