SAP SHELL_BDC_OPEN_GROUP Function Module for Joint Venture BDC Open Group Shell









SHELL_BDC_OPEN_GROUP is a standard shell bdc open group SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Joint Venture BDC Open Group Shell 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 shell bdc open group FM, simply by entering the name SHELL_BDC_OPEN_GROUP into the relevant SAP transaction such as SE37 or SE38.

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



Function SHELL_BDC_OPEN_GROUP 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 'SHELL_BDC_OPEN_GROUP'"Joint Venture BDC Open Group Shell
EXPORTING
* I_CLIENT = SY-MANDT "Client
* I_DEST = FILLER8 "Destination
* I_GROUP = FILLER12 "Group
* I_HOLDDATE = FILLER8 "Hold Date
* I_KEEP = FILLER1 "Keep
* I_USER = FILLER12 "User

EXCEPTIONS
CLIENT_INVALID = 1 DESTINATION_INVALID = 2 GROUP_INVALID = 3 HOLDDATE_INVALID = 4 INTERNAL_ERROR = 5 QUEUE_ERROR = 6 RUNNING = 7 USER_INVALID = 8
.



IMPORTING Parameters details for SHELL_BDC_OPEN_GROUP

I_CLIENT - Client

Data type: APQI-MANDANT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DEST - Destination

Data type: APQI-DESTSYS
Default: FILLER8
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_GROUP - Group

Data type: APQI-GROUPID
Default: FILLER12
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_HOLDDATE - Hold Date

Data type: APQI-STARTDATE
Default: FILLER8
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_KEEP - Keep

Data type: APQI-QERASE
Default: FILLER1
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_USER - User

Data type: APQI-USERID
Default: FILLER12
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CLIENT_INVALID -

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

DESTINATION_INVALID -

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

GROUP_INVALID -

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

HOLDDATE_INVALID - Invalid Hold Date

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

INTERNAL_ERROR - Internal Error

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

QUEUE_ERROR - Queue Error

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

RUNNING - BDC Group Already Running

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

USER_INVALID - User Invalid

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

Copy and paste ABAP code example for SHELL_BDC_OPEN_GROUP 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_client  TYPE APQI-MANDANT, "   SY-MANDT
lv_client_invalid  TYPE APQI, "   
lv_i_dest  TYPE APQI-DESTSYS, "   FILLER8
lv_destination_invalid  TYPE APQI, "   
lv_i_group  TYPE APQI-GROUPID, "   FILLER12
lv_group_invalid  TYPE APQI, "   
lv_i_holddate  TYPE APQI-STARTDATE, "   FILLER8
lv_holddate_invalid  TYPE APQI, "   
lv_i_keep  TYPE APQI-QERASE, "   FILLER1
lv_internal_error  TYPE APQI, "   
lv_i_user  TYPE APQI-USERID, "   FILLER12
lv_queue_error  TYPE APQI, "   
lv_running  TYPE APQI, "   
lv_user_invalid  TYPE APQI. "   

  CALL FUNCTION 'SHELL_BDC_OPEN_GROUP'  "Joint Venture BDC Open Group Shell
    EXPORTING
         I_CLIENT = lv_i_client
         I_DEST = lv_i_dest
         I_GROUP = lv_i_group
         I_HOLDDATE = lv_i_holddate
         I_KEEP = lv_i_keep
         I_USER = lv_i_user
    EXCEPTIONS
        CLIENT_INVALID = 1
        DESTINATION_INVALID = 2
        GROUP_INVALID = 3
        HOLDDATE_INVALID = 4
        INTERNAL_ERROR = 5
        QUEUE_ERROR = 6
        RUNNING = 7
        USER_INVALID = 8
. " SHELL_BDC_OPEN_GROUP




ABAP code using 7.40 inline data declarations to call FM SHELL_BDC_OPEN_GROUP

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 MANDANT FROM APQI INTO @DATA(ld_i_client).
DATA(ld_i_client) = SY-MANDT.
 
 
"SELECT single DESTSYS FROM APQI INTO @DATA(ld_i_dest).
DATA(ld_i_dest) = FILLER8.
 
 
"SELECT single GROUPID FROM APQI INTO @DATA(ld_i_group).
DATA(ld_i_group) = FILLER12.
 
 
"SELECT single STARTDATE FROM APQI INTO @DATA(ld_i_holddate).
DATA(ld_i_holddate) = FILLER8.
 
 
"SELECT single QERASE FROM APQI INTO @DATA(ld_i_keep).
DATA(ld_i_keep) = FILLER1.
 
 
"SELECT single USERID FROM APQI INTO @DATA(ld_i_user).
DATA(ld_i_user) = FILLER12.
 
 
 
 


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!