SAP CRM_BUPA_FRG0060_CREATE Function Module for
CRM_BUPA_FRG0060_CREATE is a standard crm bupa frg0060 create 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 crm bupa frg0060 create FM, simply by entering the name CRM_BUPA_FRG0060_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUPA_HOURS_DIALOG
Program Name: SAPLBUPA_HOURS_DIALOG
Main Program: SAPLBUPA_HOURS_DIALOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_BUPA_FRG0060_CREATE 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 'CRM_BUPA_FRG0060_CREATE'".
EXPORTING
IV_PARTNER_GUID = "
IV_SCHEDULE_TYPE = "
IS_DATA = "
IMPORTING
ET_RETURN = "
EV_ERROR = "
IMPORTING Parameters details for CRM_BUPA_FRG0060_CREATE
IV_PARTNER_GUID -
Data type: BU_PARTNER_GUIDOptional: No
Call by Reference: Yes
IV_SCHEDULE_TYPE -
Data type: CRMT_BU_SCHEDULE_TYPEOptional: No
Call by Reference: Yes
IS_DATA -
Data type: BUPA_CRMF02Optional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_BUPA_FRG0060_CREATE
ET_RETURN -
Data type: BUS_BAPI-RETURN_TABLEOptional: No
Call by Reference: Yes
EV_ERROR -
Data type: BUS_BAPI-ERROROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_BUPA_FRG0060_CREATE 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_et_return | TYPE BUS_BAPI-RETURN_TABLE, " | |||
| lv_iv_partner_guid | TYPE BU_PARTNER_GUID, " | |||
| lv_ev_error | TYPE BUS_BAPI-ERROR, " | |||
| lv_iv_schedule_type | TYPE CRMT_BU_SCHEDULE_TYPE, " | |||
| lv_is_data | TYPE BUPA_CRMF02. " |
|   CALL FUNCTION 'CRM_BUPA_FRG0060_CREATE' " |
| EXPORTING | ||
| IV_PARTNER_GUID | = lv_iv_partner_guid | |
| IV_SCHEDULE_TYPE | = lv_iv_schedule_type | |
| IS_DATA | = lv_is_data | |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| EV_ERROR | = lv_ev_error | |
| . " CRM_BUPA_FRG0060_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM CRM_BUPA_FRG0060_CREATE
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 RETURN_TABLE FROM BUS_BAPI INTO @DATA(ld_et_return). | ||||
| "SELECT single ERROR FROM BUS_BAPI INTO @DATA(ld_ev_error). | ||||
Search for further information about these or an SAP related objects