SAP J_3G_CONDITION_SET_CUA_REPO Function Module for ETM Conditions: GUI Status for Selections and Lists

Search SAP Function Modules

J_3G_CONDITION_SET_CUA_REPO is a standard j 3g condition set cua repo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ETM Conditions: GUI Status for Selections and Lists 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 j 3g condition set cua repo FM, simply by entering the name J_3G_CONDITION_SET_CUA_REPO into the relevant SAP transaction such as SE37 or SE38.

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

Function J_3G_CONDITION_SET_CUA_REPO 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 'J_3G_CONDITION_SET_CUA_REPO'"ETM Conditions: GUI Status for Selections and Lists
  EXPORTING
*  P_SUBMIT_MODE =  "

TABLES
*  P_EXCLUDE =  "

.

IMPORTING Parameters details for J_3G_CONDITION_SET_CUA_REPO

P_SUBMIT_MODE -

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

TABLES Parameters details for J_3G_CONDITION_SET_CUA_REPO

P_EXCLUDE -

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

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

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