SAP CS_OV_BOM_TEXT_PROCESS Function Module for NOTRANSL: Langtexteditor für Stücklistentexte









CS_OV_BOM_TEXT_PROCESS is a standard cs ov bom text process 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: Langtexteditor für Stücklistentexte 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 ov bom text process FM, simply by entering the name CS_OV_BOM_TEXT_PROCESS into the relevant SAP transaction such as SE37 or SE38.

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



Function CS_OV_BOM_TEXT_PROCESS 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_OV_BOM_TEXT_PROCESS'"NOTRANSL: Langtexteditor für Stücklistentexte
EXPORTING
I_STLTY = "BOM Category
I_STLNR = "
I_STLAL = "Alternative BOM
I_STKOZ = "
I_KEY_DATE = "Valid-From Date
I_ECN = "Change Number
I_AKTYP = "Activity Type

IMPORTING
E_MARK_TXT_UPDATE = "Update Indicator

CHANGING
C_LTXSP = "
C_STKTX = "

EXCEPTIONS
NO_TEXT = 1
.



IMPORTING Parameters details for CS_OV_BOM_TEXT_PROCESS

I_STLTY - BOM Category

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

I_STLNR -

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

I_STLAL - Alternative BOM

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

I_STKOZ -

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

I_KEY_DATE - Valid-From Date

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

I_ECN - Change Number

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

I_AKTYP - Activity Type

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

EXPORTING Parameters details for CS_OV_BOM_TEXT_PROCESS

E_MARK_TXT_UPDATE - Update Indicator

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

CHANGING Parameters details for CS_OV_BOM_TEXT_PROCESS

C_LTXSP -

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

C_STKTX -

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

EXCEPTIONS details

NO_TEXT -

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

Copy and paste ABAP code example for CS_OV_BOM_TEXT_PROCESS 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_c_ltxsp  TYPE BOM_CLASS_DATA-LTXSP, "   
lv_i_stlty  TYPE BOM_CLASS_DATA-STLTY, "   
lv_no_text  TYPE BOM_CLASS_DATA, "   
lv_e_mark_txt_update  TYPE TTXCT-FUNCTION, "   
lv_c_stktx  TYPE BOM_CLASS_DATA-STKTX, "   
lv_i_stlnr  TYPE BOM_CLASS_DATA-STLNR, "   
lv_i_stlal  TYPE BOM_CLASS_DATA-STLAL, "   
lv_i_stkoz  TYPE BOM_CLASS_DATA-STKOZ, "   
lv_i_key_date  TYPE BOM_CLASS_DATA-DATUV, "   
lv_i_ecn  TYPE BOM_CLASS_DATA-AENNR, "   
lv_i_aktyp  TYPE C. "   

  CALL FUNCTION 'CS_OV_BOM_TEXT_PROCESS'  "NOTRANSL: Langtexteditor für Stücklistentexte
    EXPORTING
         I_STLTY = lv_i_stlty
         I_STLNR = lv_i_stlnr
         I_STLAL = lv_i_stlal
         I_STKOZ = lv_i_stkoz
         I_KEY_DATE = lv_i_key_date
         I_ECN = lv_i_ecn
         I_AKTYP = lv_i_aktyp
    IMPORTING
         E_MARK_TXT_UPDATE = lv_e_mark_txt_update
    CHANGING
         C_LTXSP = lv_c_ltxsp
         C_STKTX = lv_c_stktx
    EXCEPTIONS
        NO_TEXT = 1
. " CS_OV_BOM_TEXT_PROCESS




ABAP code using 7.40 inline data declarations to call FM CS_OV_BOM_TEXT_PROCESS

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 LTXSP FROM BOM_CLASS_DATA INTO @DATA(ld_c_ltxsp).
 
"SELECT single STLTY FROM BOM_CLASS_DATA INTO @DATA(ld_i_stlty).
 
 
"SELECT single FUNCTION FROM TTXCT INTO @DATA(ld_e_mark_txt_update).
 
"SELECT single STKTX FROM BOM_CLASS_DATA INTO @DATA(ld_c_stktx).
 
"SELECT single STLNR FROM BOM_CLASS_DATA INTO @DATA(ld_i_stlnr).
 
"SELECT single STLAL FROM BOM_CLASS_DATA INTO @DATA(ld_i_stlal).
 
"SELECT single STKOZ FROM BOM_CLASS_DATA INTO @DATA(ld_i_stkoz).
 
"SELECT single DATUV FROM BOM_CLASS_DATA INTO @DATA(ld_i_key_date).
 
"SELECT single AENNR FROM BOM_CLASS_DATA INTO @DATA(ld_i_ecn).
 
 


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!