SAP ISU_EDM_DETVAR_BILL_FACT_01 Function Module for
ISU_EDM_DETVAR_BILL_FACT_01 is a standard isu edm detvar bill fact 01 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 isu edm detvar bill fact 01 FM, simply by entering the name ISU_EDM_DETVAR_BILL_FACT_01 into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEDM_FORMULA_DETVAR
Program Name: SAPLEEDM_FORMULA_DETVAR
Main Program: SAPLEEDM_FORMULA_DETVAR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ISU_EDM_DETVAR_BILL_FACT_01 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_DETVAR_BILL_FACT_01'".
EXPORTING
X_FROM = "Structure for From-Date
X_TO = "Structure for To-Date
X_INTSIZETYPE = "Interval length category
X_INTSIZE = "Interval length
X_FORMULADATA = "Data Type for Formula
X_INSTANCE_NUMBER = "Formula Allocation
XT_PROFILE = "EDM Profile Objects (Reference) for Formula (Internal Table)
* X_PARNUMBER = "
* X_PARCSNO = "
CHANGING
XYT_PROFVALUES = "Table Type for EFORMPROFVAL
EXCEPTIONS
MISSING_VALUES = 1 NOT_FOUND = 2 ERROR_OCCURRED = 3
IMPORTING Parameters details for ISU_EDM_DETVAR_BILL_FACT_01
X_FROM - Structure for From-Date
Data type: EEDMDATEFROMOptional: No
Call by Reference: Yes
X_TO - Structure for To-Date
Data type: EEDMDATETOOptional: No
Call by Reference: Yes
X_INTSIZETYPE - Interval length category
Data type: INTSIZETYPEOptional: No
Call by Reference: Yes
X_INTSIZE - Interval length
Data type: INTSIZEOptional: No
Call by Reference: Yes
X_FORMULADATA - Data Type for Formula
Data type: EEDMFORMULAOptional: No
Call by Reference: Yes
X_INSTANCE_NUMBER - Formula Allocation
Data type: E_INSTANCE_NUMBEROptional: No
Call by Reference: Yes
XT_PROFILE - EDM Profile Objects (Reference) for Formula (Internal Table)
Data type: TEFORMPROFILEOptional: No
Call by Reference: Yes
X_PARNUMBER -
Data type: EPARNUMBEROptional: Yes
Call by Reference: Yes
X_PARCSNO -
Data type: E_PARCSNOOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for ISU_EDM_DETVAR_BILL_FACT_01
XYT_PROFVALUES - Table Type for EFORMPROFVAL
Data type: T_EFORMPROFVALOptional: No
Call by Reference: Yes
EXCEPTIONS details
MISSING_VALUES - No existing values
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND - Not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_OCCURRED - Error occured
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_EDM_DETVAR_BILL_FACT_01 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_x_from | TYPE EEDMDATEFROM, " | |||
lv_missing_values | TYPE EEDMDATEFROM, " | |||
lv_xyt_profvalues | TYPE T_EFORMPROFVAL, " | |||
lv_x_to | TYPE EEDMDATETO, " | |||
lv_not_found | TYPE EEDMDATETO, " | |||
lv_x_intsizetype | TYPE INTSIZETYPE, " | |||
lv_error_occurred | TYPE INTSIZETYPE, " | |||
lv_x_intsize | TYPE INTSIZE, " | |||
lv_x_formuladata | TYPE EEDMFORMULA, " | |||
lv_x_instance_number | TYPE E_INSTANCE_NUMBER, " | |||
lv_xt_profile | TYPE TEFORMPROFILE, " | |||
lv_x_parnumber | TYPE EPARNUMBER, " | |||
lv_x_parcsno | TYPE E_PARCSNO. " |
  CALL FUNCTION 'ISU_EDM_DETVAR_BILL_FACT_01' " |
EXPORTING | ||
X_FROM | = lv_x_from | |
X_TO | = lv_x_to | |
X_INTSIZETYPE | = lv_x_intsizetype | |
X_INTSIZE | = lv_x_intsize | |
X_FORMULADATA | = lv_x_formuladata | |
X_INSTANCE_NUMBER | = lv_x_instance_number | |
XT_PROFILE | = lv_xt_profile | |
X_PARNUMBER | = lv_x_parnumber | |
X_PARCSNO | = lv_x_parcsno | |
CHANGING | ||
XYT_PROFVALUES | = lv_xyt_profvalues | |
EXCEPTIONS | ||
MISSING_VALUES = 1 | ||
NOT_FOUND = 2 | ||
ERROR_OCCURRED = 3 | ||
. " ISU_EDM_DETVAR_BILL_FACT_01 |
ABAP code using 7.40 inline data declarations to call FM ISU_EDM_DETVAR_BILL_FACT_01
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