SAP ISU_EDM_SYNC_USAGEFACTOR Function Module for Synchronization of Field Locked for Usage Factors









ISU_EDM_SYNC_USAGEFACTOR is a standard isu edm sync usagefactor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Synchronization of Field Locked for Usage Factors 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 isu edm sync usagefactor FM, simply by entering the name ISU_EDM_SYNC_USAGEFACTOR into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_EDM_SYNC_USAGEFACTOR 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 'ISU_EDM_SYNC_USAGEFACTOR'"Synchronization of Field Locked for Usage Factors
  EXPORTING
   IM_INSTALATION =  "Installation
*  IM_DATEFROM = '99991231' "Date at Which a Time Slice Expires
*  IM_DATETO = '19000101' "Date from Which a Time Slice is Valid
*  IM_COMMIT = ' ' "
*  IM_ROLE_TAB =  "Table Types for PROFROLE
*  IM_EVER_TAB =  "Standard Table for EVER Structure
*  IM_SAVE = ' ' "
*  IM_UF_CUST =  "Customizing for Usage Factor Update

 IMPORTING
   EX_LPASSLIST_OBJ =  "Object Definition of Load Profile Assignment List

EXCEPTIONS
   SYSTEM_ERROR = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLEEDM_USAGEFACTOR_001 Consumption Factor Determination: Filter Out Allocations
EXIT_SAPLEEDM_USAGEFACTOR_002 Determination of Relevant Period
EXIT_SAPLEEDM_USAGEFACTOR_003 Determination of Future Consumption Factor

IMPORTING Parameters details for ISU_EDM_SYNC_USAGEFACTOR

IM_INSTALATION - Installation

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

IM_DATEFROM - Date at Which a Time Slice Expires

Data type: BISZEITSCH
Default: '99991231'
Optional: Yes
Call by Reference: Yes

IM_DATETO - Date from Which a Time Slice is Valid

Data type: ABZEITSCH
Default: '19000101'
Optional: Yes
Call by Reference: Yes

IM_COMMIT -

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

IM_ROLE_TAB - Table Types for PROFROLE

Data type: T_EEDMPROFROLE
Optional: Yes
Call by Reference: Yes

IM_EVER_TAB - Standard Table for EVER Structure

Data type: ISU2A_IEVER
Optional: Yes
Call by Reference: Yes

IM_SAVE -

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

IM_UF_CUST - Customizing for Usage Factor Update

Data type: ITUF_CUST
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISU_EDM_SYNC_USAGEFACTOR

EX_LPASSLIST_OBJ - Object Definition of Load Profile Assignment List

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

EXCEPTIONS details

SYSTEM_ERROR - System error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_EDM_SYNC_USAGEFACTOR 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_system_error  TYPE STRING, "   
lv_im_instalation  TYPE ANLAGE, "   
lv_ex_lpasslist_obj  TYPE ISULP_LPASSLIST, "   
lv_im_datefrom  TYPE BISZEITSCH, "   '99991231'
lv_im_dateto  TYPE ABZEITSCH, "   '19000101'
lv_im_commit  TYPE KENNZX, "   SPACE
lv_im_role_tab  TYPE T_EEDMPROFROLE, "   
lv_im_ever_tab  TYPE ISU2A_IEVER, "   
lv_im_save  TYPE KENNZX, "   SPACE
lv_im_uf_cust  TYPE ITUF_CUST. "   

  CALL FUNCTION 'ISU_EDM_SYNC_USAGEFACTOR'  "Synchronization of Field Locked for Usage Factors
    EXPORTING
         IM_INSTALATION = lv_im_instalation
         IM_DATEFROM = lv_im_datefrom
         IM_DATETO = lv_im_dateto
         IM_COMMIT = lv_im_commit
         IM_ROLE_TAB = lv_im_role_tab
         IM_EVER_TAB = lv_im_ever_tab
         IM_SAVE = lv_im_save
         IM_UF_CUST = lv_im_uf_cust
    IMPORTING
         EX_LPASSLIST_OBJ = lv_ex_lpasslist_obj
    EXCEPTIONS
        SYSTEM_ERROR = 1
. " ISU_EDM_SYNC_USAGEFACTOR




ABAP code using 7.40 inline data declarations to call FM ISU_EDM_SYNC_USAGEFACTOR

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_im_datefrom) = '99991231'.
 
DATA(ld_im_dateto) = '19000101'.
 
DATA(ld_im_commit) = ' '.
 
 
 
DATA(ld_im_save) = ' '.
 
 


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!