SAP FVD_OBJ_OB_CT_SAVE Function Module for Saves the Changed Status of a Condition Table (Cascading)

Search SAP Function Modules

FVD_OBJ_OB_CT_SAVE is a standard fvd obj ob ct save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Saves the Changed Status of a Condition Table (Cascading) 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 fvd obj ob ct save FM, simply by entering the name FVD_OBJ_OB_CT_SAVE into the relevant SAP transaction such as SE37 or SE38.

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

Function FVD_OBJ_OB_CT_SAVE 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 'FVD_OBJ_OB_CT_SAVE'"Saves the Changed Status of a Condition Table (Cascading)
  EXPORTING
   I_STR_CONDTAB_KEY =  "Key Structure for Condition Table
   I_VERS =  "Versions-ID KonditionsTableau
*  I_PRODTYPE = '0340' "Product Category
   I_SAVE_EFFECT =  "Conditions: Type of Effect of Save Operation
   I_FLG_INUPDATETASK =  "In Verbucher updaten: TRUE (='X') und FALSE (=' ')
*  I_FLG_DELETE_PHYSICAL = CON_FALSE "Physikalisch löschen TRUE (='X') und FALSE (=' ')
*  I_FLG_STOP_RELEASE = CON_FALSE "Freigabeworkflow umgehen: TRUE (='X') und FALSE (=' ')
*  I_FLG_TEST_ONLY = CON_TRUE "Nur Test - Kein Update:  TRUE (='X') und FALSE (=' ')
   I_LOG_HANDLE =  "Application Log: Log Handle

 IMPORTING
   E_RC =  "Return Value, Return Value after ABAP Statements

EXCEPTIONS
   NOTICE_OCCURED = 1    ERROR_OCCURED = 2 

.

IMPORTING Parameters details for FVD_OBJ_OB_CT_SAVE

I_STR_CONDTAB_KEY - Key Structure for Condition Table

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

I_VERS - Versions-ID KonditionsTableau

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

I_PRODTYPE - Product Category

Data type: TB_PR_PRODTYPE
Default: '0340'
Optional: No
Call by Reference: Yes

I_SAVE_EFFECT - Conditions: Type of Effect of Save Operation

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

I_FLG_INUPDATETASK - In Verbucher updaten: TRUE (='X') und FALSE (=' ')

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

I_FLG_DELETE_PHYSICAL - Physikalisch löschen TRUE (='X') und FALSE (=' ')

Data type: BOOLE_D
Default: CON_FALSE
Optional: No
Call by Reference: Yes

I_FLG_STOP_RELEASE - Freigabeworkflow umgehen: TRUE (='X') und FALSE (=' ')

Data type: BOOLE_D
Default: CON_FALSE
Optional: No
Call by Reference: Yes

I_FLG_TEST_ONLY - Nur Test - Kein Update: TRUE (='X') und FALSE (=' ')

Data type: BOOLE_D
Default: CON_TRUE
Optional: No
Call by Reference: Yes

I_LOG_HANDLE - Application Log: Log Handle

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

EXPORTING Parameters details for FVD_OBJ_OB_CT_SAVE

E_RC - Return Value, Return Value after ABAP Statements

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOTICE_OCCURED - Es liegen eine oder mehrer Informationen vor

Data type:
Optional: No
Call by Reference: Yes

ERROR_OCCURED - Es sind ein oder mehrere Fehler aufgetreten

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_OBJ_OB_CT_SAVE 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.

ABAP code using 7.40 inline data declarations to call FM FVD_OBJ_OB_CT_SAVE

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