SAP BUPR_CONTP_HOURS_GETDETAIL Function Module for
BUPR_CONTP_HOURS_GETDETAIL is a standard bupr contp hours getdetail 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 bupr contp hours getdetail FM, simply by entering the name BUPR_CONTP_HOURS_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUBA_5
Program Name: SAPLBUBA_5
Main Program: SAPLBUBA_5
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUPR_CONTP_HOURS_GETDETAIL 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 'BUPR_CONTP_HOURS_GETDETAIL'".
EXPORTING
IV_PARTNER = "
* IV_PARTNER_GUID = "
IV_CONTACTPERSON = "
* IV_CONTACTPERSON_GUID = "
* IV_DATE_FROM = "Validity Date (Valid From)
* IV_DATE_TO = "Validity Date (Valid To)
IV_SCHEDULE_TYPE = "Schedule Type
IMPORTING
EV_RULE_ID = "Internal Identification of Rules of Periodic Appointments
TABLES
* T_COMBINEDRULE = "Link Rule
* T_DAILYRULES = "Daily Rules
* T_WEEKLYRULES = "Weekly Rules
* T_MONTHLYRULES1 = "Monthly Rules 1
* T_MONTHLYRULES2 = "Monthly Rules 2
* T_FIXEDRULES = "
* ET_RETURN = "Messages
IMPORTING Parameters details for BUPR_CONTP_HOURS_GETDETAIL
IV_PARTNER -
Data type: BU_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
IV_PARTNER_GUID -
Data type: BU_PARTNER_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CONTACTPERSON -
Data type: BU_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
IV_CONTACTPERSON_GUID -
Data type: BU_PARTNER_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_DATE_FROM - Validity Date (Valid From)
Data type: BAPIBUS1006002_HEADER-VALIDFROMDATEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_DATE_TO - Validity Date (Valid To)
Data type: BAPIBUS1006002_HEADER-VALIDUNTILDATEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SCHEDULE_TYPE - Schedule Type
Data type: BAPIBUS1006_SCHEDULE_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BUPR_CONTP_HOURS_GETDETAIL
EV_RULE_ID - Internal Identification of Rules of Periodic Appointments
Data type: SC_RULEIDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BUPR_CONTP_HOURS_GETDETAIL
T_COMBINEDRULE - Link Rule
Data type: BAPIBUS1006_RULE_R_TOptional: Yes
Call by Reference: Yes
T_DAILYRULES - Daily Rules
Data type: BAPIBUS1006_RULE_D_TOptional: Yes
Call by Reference: Yes
T_WEEKLYRULES - Weekly Rules
Data type: BAPIBUS1006_RULE_W_TOptional: Yes
Call by Reference: Yes
T_MONTHLYRULES1 - Monthly Rules 1
Data type: BAPIBUS1006_RULE_M1_TOptional: Yes
Call by Reference: Yes
T_MONTHLYRULES2 - Monthly Rules 2
Data type: BAPIBUS1006_RULE_M3_TOptional: Yes
Call by Reference: Yes
T_FIXEDRULES -
Data type: BAPIBUS1006_RULE_T_TOptional: Yes
Call by Reference: Yes
ET_RETURN - Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BUPR_CONTP_HOURS_GETDETAIL 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_ev_rule_id | TYPE SC_RULEID, " | |||
| lv_iv_partner | TYPE BU_PARTNER, " | |||
| lt_t_combinedrule | TYPE STANDARD TABLE OF BAPIBUS1006_RULE_R_T, " | |||
| lt_t_dailyrules | TYPE STANDARD TABLE OF BAPIBUS1006_RULE_D_T, " | |||
| lv_iv_partner_guid | TYPE BU_PARTNER_GUID, " | |||
| lt_t_weeklyrules | TYPE STANDARD TABLE OF BAPIBUS1006_RULE_W_T, " | |||
| lv_iv_contactperson | TYPE BU_PARTNER, " | |||
| lt_t_monthlyrules1 | TYPE STANDARD TABLE OF BAPIBUS1006_RULE_M1_T, " | |||
| lv_iv_contactperson_guid | TYPE BU_PARTNER_GUID, " | |||
| lv_iv_date_from | TYPE BAPIBUS1006002_HEADER-VALIDFROMDATE, " | |||
| lt_t_monthlyrules2 | TYPE STANDARD TABLE OF BAPIBUS1006_RULE_M3_T, " | |||
| lv_iv_date_to | TYPE BAPIBUS1006002_HEADER-VALIDUNTILDATE, " | |||
| lt_t_fixedrules | TYPE STANDARD TABLE OF BAPIBUS1006_RULE_T_T, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_iv_schedule_type | TYPE BAPIBUS1006_SCHEDULE_TYPE. " |
|   CALL FUNCTION 'BUPR_CONTP_HOURS_GETDETAIL' " |
| EXPORTING | ||
| IV_PARTNER | = lv_iv_partner | |
| IV_PARTNER_GUID | = lv_iv_partner_guid | |
| IV_CONTACTPERSON | = lv_iv_contactperson | |
| IV_CONTACTPERSON_GUID | = lv_iv_contactperson_guid | |
| IV_DATE_FROM | = lv_iv_date_from | |
| IV_DATE_TO | = lv_iv_date_to | |
| IV_SCHEDULE_TYPE | = lv_iv_schedule_type | |
| IMPORTING | ||
| EV_RULE_ID | = lv_ev_rule_id | |
| TABLES | ||
| T_COMBINEDRULE | = lt_t_combinedrule | |
| T_DAILYRULES | = lt_t_dailyrules | |
| T_WEEKLYRULES | = lt_t_weeklyrules | |
| T_MONTHLYRULES1 | = lt_t_monthlyrules1 | |
| T_MONTHLYRULES2 | = lt_t_monthlyrules2 | |
| T_FIXEDRULES | = lt_t_fixedrules | |
| ET_RETURN | = lt_et_return | |
| . " BUPR_CONTP_HOURS_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BUPR_CONTP_HOURS_GETDETAIL
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 VALIDFROMDATE FROM BAPIBUS1006002_HEADER INTO @DATA(ld_iv_date_from). | ||||
| "SELECT single VALIDUNTILDATE FROM BAPIBUS1006002_HEADER INTO @DATA(ld_iv_date_to). | ||||
Search for further information about these or an SAP related objects