SAP HR_BEN_COB_GET_OFFER Function Module for
HR_BEN_COB_GET_OFFER is a standard hr ben cob get offer 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 hr ben cob get offer FM, simply by entering the name HR_BEN_COB_GET_OFFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRBENUSCOBRA
Program Name: SAPLHRBENUSCOBRA
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function HR_BEN_COB_GET_OFFER 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 'HR_BEN_COB_GET_OFFER'".
EXPORTING
PERNR = "
COB_SUBTY = "
COB_OBJPS = "
COB_OFFER_TYPE = "
DATUM = "
DESIRED_CURRENCY = "
* DESIRED_PERIOD = "
* QB_BENEFIT_DATA = "
REACTION = "
IMPORTING
SUBRC = "
TABLES
* HEALTH_OFFER = "
* SPENDA_OFFER = "
* POSS_DEPENDENTS = "
* REGULAR_PLTYPES = "
* COBRA_DEPENDENTS = "
ERROR_TABLE = "
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_SAPLHRBENUSCOBRA_004 Function exit within 'HR_BEN_COB_GET_TOTAL_COSTS'
IMPORTING Parameters details for HR_BEN_COB_GET_OFFER
PERNR -
Data type: PSKEY-PERNROptional: No
Call by Reference: No ( called with pass by value option)
COB_SUBTY -
Data type: COB_SUBTYOptional: No
Call by Reference: No ( called with pass by value option)
COB_OBJPS -
Data type: OBJPSOptional: No
Call by Reference: No ( called with pass by value option)
COB_OFFER_TYPE -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
DATUM -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
DESIRED_CURRENCY -
Data type: T5UD3-CURREOptional: No
Call by Reference: No ( called with pass by value option)
DESIRED_PERIOD -
Data type: T549R-ZEINHOptional: Yes
Call by Reference: No ( called with pass by value option)
QB_BENEFIT_DATA -
Data type: RPCOBQBDATOptional: Yes
Call by Reference: No ( called with pass by value option)
REACTION -
Data type: SY-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HR_BEN_COB_GET_OFFER
SUBRC -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for HR_BEN_COB_GET_OFFER
HEALTH_OFFER -
Data type: RPBEN_OAOptional: Yes
Call by Reference: Yes
SPENDA_OFFER -
Data type: RPBEN_ODOptional: Yes
Call by Reference: Yes
POSS_DEPENDENTS -
Data type: RPBENODPOptional: Yes
Call by Reference: Yes
REGULAR_PLTYPES -
Data type: RPCOBPLTYPEOptional: Yes
Call by Reference: Yes
COBRA_DEPENDENTS -
Data type: T74ABOptional: Yes
Call by Reference: Yes
ERROR_TABLE -
Data type: RPBENERROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_BEN_COB_GET_OFFER 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_pernr | TYPE PSKEY-PERNR, " | |||
lv_subrc | TYPE SY-SUBRC, " | |||
lt_health_offer | TYPE STANDARD TABLE OF RPBEN_OA, " | |||
lv_cob_subty | TYPE COB_SUBTY, " | |||
lt_spenda_offer | TYPE STANDARD TABLE OF RPBEN_OD, " | |||
lv_cob_objps | TYPE OBJPS, " | |||
lt_poss_dependents | TYPE STANDARD TABLE OF RPBENODP, " | |||
lv_cob_offer_type | TYPE C, " | |||
lt_regular_pltypes | TYPE STANDARD TABLE OF RPCOBPLTYPE, " | |||
lv_datum | TYPE SY-DATUM, " | |||
lt_cobra_dependents | TYPE STANDARD TABLE OF T74AB, " | |||
lt_error_table | TYPE STANDARD TABLE OF RPBENERR, " | |||
lv_desired_currency | TYPE T5UD3-CURRE, " | |||
lv_desired_period | TYPE T549R-ZEINH, " | |||
lv_qb_benefit_data | TYPE RPCOBQBDAT, " | |||
lv_reaction | TYPE SY-MSGTY. " |
  CALL FUNCTION 'HR_BEN_COB_GET_OFFER' " |
EXPORTING | ||
PERNR | = lv_pernr | |
COB_SUBTY | = lv_cob_subty | |
COB_OBJPS | = lv_cob_objps | |
COB_OFFER_TYPE | = lv_cob_offer_type | |
DATUM | = lv_datum | |
DESIRED_CURRENCY | = lv_desired_currency | |
DESIRED_PERIOD | = lv_desired_period | |
QB_BENEFIT_DATA | = lv_qb_benefit_data | |
REACTION | = lv_reaction | |
IMPORTING | ||
SUBRC | = lv_subrc | |
TABLES | ||
HEALTH_OFFER | = lt_health_offer | |
SPENDA_OFFER | = lt_spenda_offer | |
POSS_DEPENDENTS | = lt_poss_dependents | |
REGULAR_PLTYPES | = lt_regular_pltypes | |
COBRA_DEPENDENTS | = lt_cobra_dependents | |
ERROR_TABLE | = lt_error_table | |
. " HR_BEN_COB_GET_OFFER |
ABAP code using 7.40 inline data declarations to call FM HR_BEN_COB_GET_OFFER
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 PERNR FROM PSKEY INTO @DATA(ld_pernr). | ||||
"SELECT single SUBRC FROM SY INTO @DATA(ld_subrc). | ||||
"SELECT single DATUM FROM SY INTO @DATA(ld_datum). | ||||
"SELECT single CURRE FROM T5UD3 INTO @DATA(ld_desired_currency). | ||||
"SELECT single ZEINH FROM T549R INTO @DATA(ld_desired_period). | ||||
"SELECT single MSGTY FROM SY INTO @DATA(ld_reaction). | ||||
Search for further information about these or an SAP related objects