SAP UMB_SC_GET_CECHAIN_DATA Function Module for









UMB_SC_GET_CECHAIN_DATA is a standard umb sc get cechain data 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 umb sc get cechain data FM, simply by entering the name UMB_SC_GET_CECHAIN_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function UMB_SC_GET_CECHAIN_DATA 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 'UMB_SC_GET_CECHAIN_DATA'"
EXPORTING
* IX_BY_STMAP = ' ' "
* I_SCARD = "
* I_VALID_FR = "
* I_STMAP = "
* I_CLIENT = SY-MANDT "
* IX_BLOB = ' ' "

IMPORTING
E_BLOB_PERIOD = "
ET_PERS = "
ET_STRAT = "
ET_OBJPOS = "
ET_OBJLINKS = "
ET_BLOB_STRATEGY = "
ET_BLOB_PERSPECTIVE = "
ET_BLOB_OBJECTIVE = "
ET_BLOB_LINK = "
.



IMPORTING Parameters details for UMB_SC_GET_CECHAIN_DATA

IX_BY_STMAP -

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

I_SCARD -

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

I_VALID_FR -

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

I_STMAP -

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

I_CLIENT -

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

IX_BLOB -

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

EXPORTING Parameters details for UMB_SC_GET_CECHAIN_DATA

E_BLOB_PERIOD -

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

ET_PERS -

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

ET_STRAT -

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

ET_OBJPOS -

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

ET_OBJLINKS -

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

ET_BLOB_STRATEGY -

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

ET_BLOB_PERSPECTIVE -

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

ET_BLOB_OBJECTIVE -

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

ET_BLOB_LINK -

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

Copy and paste ABAP code example for UMB_SC_GET_CECHAIN_DATA 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_ix_by_stmap  TYPE AS4FLAG, "   SPACE
lv_e_blob_period  TYPE UMC_Y_VALIDFR, "   
lv_et_pers  TYPE UMB_YT_PERSHEADER, "   
lv_i_scard  TYPE UMB_Y_SCARD, "   
lv_et_strat  TYPE UMB_YT_STRATHEADER, "   
lv_i_valid_fr  TYPE UMC_Y_VALIDFR, "   
lv_i_stmap  TYPE UMB_Y_STMAP, "   
lv_et_objpos  TYPE UMB_YT_OBJPOS, "   
lv_i_client  TYPE MANDT, "   SY-MANDT
lv_et_objlinks  TYPE UMB_YT_OBJLINKS, "   
lv_ix_blob  TYPE AS4FLAG, "   SPACE
lv_et_blob_strategy  TYPE UMB_YT_BLOB_STRATEGY, "   
lv_et_blob_perspective  TYPE UMB_YT_BLOB_PERSPECTIVE_EX, "   
lv_et_blob_objective  TYPE UMB_YT_BLOB_OBJECTIVE, "   
lv_et_blob_link  TYPE UMB_YT_BLOB_LINK. "   

  CALL FUNCTION 'UMB_SC_GET_CECHAIN_DATA'  "
    EXPORTING
         IX_BY_STMAP = lv_ix_by_stmap
         I_SCARD = lv_i_scard
         I_VALID_FR = lv_i_valid_fr
         I_STMAP = lv_i_stmap
         I_CLIENT = lv_i_client
         IX_BLOB = lv_ix_blob
    IMPORTING
         E_BLOB_PERIOD = lv_e_blob_period
         ET_PERS = lv_et_pers
         ET_STRAT = lv_et_strat
         ET_OBJPOS = lv_et_objpos
         ET_OBJLINKS = lv_et_objlinks
         ET_BLOB_STRATEGY = lv_et_blob_strategy
         ET_BLOB_PERSPECTIVE = lv_et_blob_perspective
         ET_BLOB_OBJECTIVE = lv_et_blob_objective
         ET_BLOB_LINK = lv_et_blob_link
. " UMB_SC_GET_CECHAIN_DATA




ABAP code using 7.40 inline data declarations to call FM UMB_SC_GET_CECHAIN_DATA

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.

DATA(ld_ix_by_stmap) = ' '.
 
 
 
 
 
 
 
 
DATA(ld_i_client) = SY-MANDT.
 
 
DATA(ld_ix_blob) = ' '.
 
 
 
 
 


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!