SAP WCFJ_MODIFY Function Module for WCM: Add Entries to the Catalog









WCFJ_MODIFY is a standard wcfj modify SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for WCM: Add Entries to the Catalog 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 wcfj modify FM, simply by entering the name WCFJ_MODIFY into the relevant SAP transaction such as SE37 or SE38.

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



Function WCFJ_MODIFY 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 'WCFJ_MODIFY'"WCM: Add Entries to the Catalog
  EXPORTING
   I_IWERK =  "Planning Plant
   I_OBJART =  "Object Type
   I_OBJTYP =  "Subobject Type
   I_OBJNR =  "Object Number
   I_USAGE =  "Usage of WCM Object
   I_AKTYP =  "Activity Category
   I_CATPROFILE =  "Catalog Profile
   I_CATTYP1 =  "1. Catalog Type
   I_CATTYP2 =  "2. Catalog Type

CHANGING
   UPDFLG =  "Data has Changed = X
   LNKFLG1 =  "Entries does Exist = X (1. Catalog)
   LNKFLG2 =  "Entries does Exist = X (2. Catalog)

EXCEPTIONS
   ERROR = 1
.



IMPORTING Parameters details for WCFJ_MODIFY

I_IWERK - Planning Plant

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

I_OBJART - Object Type

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

I_OBJTYP - Subobject Type

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

I_OBJNR - Object Number

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

I_USAGE - Usage of WCM Object

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

I_AKTYP - Activity Category

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

I_CATPROFILE - Catalog Profile

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

I_CATTYP1 - 1. Catalog Type

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

I_CATTYP2 - 2. Catalog Type

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

CHANGING Parameters details for WCFJ_MODIFY

UPDFLG - Data has Changed = X

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

LNKFLG1 - Entries does Exist = X (1. Catalog)

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

LNKFLG2 - Entries does Exist = X (2. Catalog)

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

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for WCFJ_MODIFY 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_error  TYPE STRING, "   
lv_updflg  TYPE WCTP1_FLG_TYPE, "   
lv_i_iwerk  TYPE WCTP1_IWERK_TYPE, "   
lv_lnkflg1  TYPE WCECATFLG, "   
lv_i_objart  TYPE WCTP1_OBJART_TYPE, "   
lv_lnkflg2  TYPE WCECATFLG, "   
lv_i_objtyp  TYPE WCTP1_OBJTYP_TYPE, "   
lv_i_objnr  TYPE WCTP1_OBJNR_TYPE, "   
lv_i_usage  TYPE WCEUSAGE, "   
lv_i_aktyp  TYPE WCTP1_AKTYP_TYPE, "   
lv_i_catprofile  TYPE WCECATPROFILE, "   
lv_i_cattyp1  TYPE QKATART, "   
lv_i_cattyp2  TYPE QKATART. "   

  CALL FUNCTION 'WCFJ_MODIFY'  "WCM: Add Entries to the Catalog
    EXPORTING
         I_IWERK = lv_i_iwerk
         I_OBJART = lv_i_objart
         I_OBJTYP = lv_i_objtyp
         I_OBJNR = lv_i_objnr
         I_USAGE = lv_i_usage
         I_AKTYP = lv_i_aktyp
         I_CATPROFILE = lv_i_catprofile
         I_CATTYP1 = lv_i_cattyp1
         I_CATTYP2 = lv_i_cattyp2
    CHANGING
         UPDFLG = lv_updflg
         LNKFLG1 = lv_lnkflg1
         LNKFLG2 = lv_lnkflg2
    EXCEPTIONS
        ERROR = 1
. " WCFJ_MODIFY




ABAP code using 7.40 inline data declarations to call FM WCFJ_MODIFY

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



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!