SAP UPSCP_OBJECT_KEY_MAINTAIN Function Module for









UPSCP_OBJECT_KEY_MAINTAIN is a standard upscp object key maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 upscp object key maintain FM, simply by entering the name UPSCP_OBJECT_KEY_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

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



Function UPSCP_OBJECT_KEY_MAINTAIN 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 'UPSCP_OBJECT_KEY_MAINTAIN'"
EXPORTING
IM_OBJTYP = "Object type
* IM_CALLMODE = KUPS_DISTRIBUTION "
* FLG_CHANGE = KUPS_FALSE "Object Key Can Be Changed
* IM_DLOCK = ' ' "ALE Distribution Packet: Include Distribution Lock

CHANGING
CH_OBJID = "ALE Distribution Packet : Object Key
CH_OBJVAL = "ALE Distribution Packet: Object Validity
CH_MESCOD = "

EXCEPTIONS
FAILURE = 1
.



IMPORTING Parameters details for UPSCP_OBJECT_KEY_MAINTAIN

IM_OBJTYP - Object type

Data type: API_UPSITM-OBJTYP
Optional: No
Call by Reference: Yes

IM_CALLMODE -

Data type: C
Default: KUPS_DISTRIBUTION
Optional: Yes
Call by Reference: Yes

FLG_CHANGE - Object Key Can Be Changed

Data type: XFELD
Default: KUPS_FALSE
Optional: Yes
Call by Reference: Yes

IM_DLOCK - ALE Distribution Packet: Include Distribution Lock

Data type: UPS_DLOCK
Default: SPACE
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for UPSCP_OBJECT_KEY_MAINTAIN

CH_OBJID - ALE Distribution Packet : Object Key

Data type: API_UPSITM-OBJID
Optional: No
Call by Reference: Yes

CH_OBJVAL - ALE Distribution Packet: Object Validity

Data type: API_UPSITM-OBJVAL
Optional: No
Call by Reference: Yes

CH_MESCOD -

Data type: API_UPSITM-MESCOD
Optional: No
Call by Reference: Yes

EXCEPTIONS details

FAILURE -

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

Copy and paste ABAP code example for UPSCP_OBJECT_KEY_MAINTAIN 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_failure  TYPE STRING, "   
lv_ch_objid  TYPE API_UPSITM-OBJID, "   
lv_im_objtyp  TYPE API_UPSITM-OBJTYP, "   
lv_ch_objval  TYPE API_UPSITM-OBJVAL, "   
lv_im_callmode  TYPE C, "   KUPS_DISTRIBUTION
lv_ch_mescod  TYPE API_UPSITM-MESCOD, "   
lv_flg_change  TYPE XFELD, "   KUPS_FALSE
lv_im_dlock  TYPE UPS_DLOCK. "   SPACE

  CALL FUNCTION 'UPSCP_OBJECT_KEY_MAINTAIN'  "
    EXPORTING
         IM_OBJTYP = lv_im_objtyp
         IM_CALLMODE = lv_im_callmode
         FLG_CHANGE = lv_flg_change
         IM_DLOCK = lv_im_dlock
    CHANGING
         CH_OBJID = lv_ch_objid
         CH_OBJVAL = lv_ch_objval
         CH_MESCOD = lv_ch_mescod
    EXCEPTIONS
        FAILURE = 1
. " UPSCP_OBJECT_KEY_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM UPSCP_OBJECT_KEY_MAINTAIN

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 OBJID FROM API_UPSITM INTO @DATA(ld_ch_objid).
 
"SELECT single OBJTYP FROM API_UPSITM INTO @DATA(ld_im_objtyp).
 
"SELECT single OBJVAL FROM API_UPSITM INTO @DATA(ld_ch_objval).
 
DATA(ld_im_callmode) = KUPS_DISTRIBUTION.
 
"SELECT single MESCOD FROM API_UPSITM INTO @DATA(ld_ch_mescod).
 
DATA(ld_flg_change) = KUPS_FALSE.
 
DATA(ld_im_dlock) = ' '.
 


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!