Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PA-BN (Application Component) Benefits⤷
PBEC (Package) Benefits - Customizing
IMG Activity
| ID | OHBEN0440 | Set Up SAPScript Templates |
| Transaction Code | S_AHR_61002215 | IMG-Aktivität: OHBEN0440 |
| Created on | 19981221 | |
| Customizing Attributes | BEN_00_AD_1_2_E0103 | Administration - mandatory - non-critical - all countries but JP |
| Customizing Activity | BEN_00_SE71 | Transaction SE71 |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHBEN0440 |
In this step, you set up the SAPscript templates for benefits enrollment and confirmation forms.
Requirements
Standard settings
In the standard system, the SAPscript forms HR_BEN_ENRO and HR_BEN_CONF are provided as templates for printing enrollment forms and confirmation forms respectively. You copy these forms from the SAP client 000 to your customizing client, where you can modify their layout as required.
On the standard SAPscript forms, text and benefits data are inserted into in a number of text windows. The windows and their contents are listed below, with an indication of the pages on which they will be positioned when a form is printed:
Window Content Printed on
DATE Form date All pages
EEADDR Employee address First page
EEDATA Employee data First page
EEDATA2 Employee data All pages except first
FOOTER Footer lines All pages
HEADER Header lines First page
MAIN Employee benefits All pages
MAINFRM Frame for window MAIN All pages
OFFER Benefits offer data First page (form HR_BEN_ENRO only)
PAGECNT Page numbering All pages except first
In each text window, SAPscript symbols are used as placeholders for data stored in the SAP System. These symbols are replaced at run time by their values on the given form date. The following data structures from the ABAP Dictionary can be read and data inserted by the standard benefits form driver (function module HR_BEN_FORM_PRINT_SAPSCR):
Data Structure Short Description
P0001 Organizational assignment
P0002 Personal data
P0006 Address (subtype 1 = Permanent address)
P0171 General benefits information
RPBENEVENT Benefits event
T001P Personnel area/subarea
T500P Personnel area
T501T Employee group text
T503T Employee subgroup text
T522T Form of address
T549T Payroll area text
T5UC3 Benefit area text
T5UC9 Second program grouping text
T5UCT First program grouping text
With the exception of the window MAIN, only a single text is printed in each of the text windows, in other words, each window contains a default SAPscript text element. However, in the case of the window MAIN, the window text is distributed across a whole set of text elements. This design gives you a high degree of flexibility when formatting the list of current or offered benefits plans.
The set of standard text elements for the window MAIN is further broken down into subsets for each benefits category. Since the subsets for each category are basically the same, only the text elements for health plans are explained in more detail below, with information about how these are processed by the benefits form driver. Differences and additional information about the other benefits categories are mentioned at the end of this section.
The following text elements are used to format the output of health plans on a benefits form:
Text Element Short Description
HEALTH_AT_FIRST Start of category health plans
HEALTH_AT_NEW_PLTYP New plan type
HEALTH_AT_NEW_BPLAN New plan within given plan type
HEALTH_AT_NEW_LEVEL1 New option within given plan
HEALTH_AT_NEW_LEVEL2 New dependent coverage within given option
HEALTH_AT_END_OF_BPLAN End of given plan
HEALTH_AT_END_OF_PLTYP End of given plan type
HEALTH_AT_LAST End of category health plans
HEALTH_AT_PTSCT_HEADER Column header for additional post-tax costs
HEALTH_AT_IMINC_HEADER Column header for imputed income amount
The form driver first creates the list of offered or current health plans (forms HR_BEN_ENRO or HR_BEN_CONF respectively) and stores it internally. It then processes this list entry by entry and successively moves the health plan data to either the dictionary structure RPBEN_OA (health plan offer, form HR_BEN_ENRO), or RPBEN_DA (health plan display, form HR_BEN_CONF).
For each entry in the list of plans, the form driver determines the text elements that need to be accessed according to the logic implied by the element names. The driver then formats these text elements and prints them in window MAIN in the order given above.
For example, the health plan MED1 is offered to an employee. There are two options for this plan: OPT1 and OPT2, with three dependent coverage levels each: EE, EE+1, and EE+F. The list of plans therefore contains six entries, which are printed from the standard text elements in as follows:
Entry Pl.Type Plan Option Dep.Cov Text Element
1 MEDI MED1 OPT1 EE HEALTH_AT_FIRST
HEALTH_AT_NEW_PLTYP
HEALTH_AT_NEW_BPLAN
HEALTH_AT_NEW_LEVEL1
HEALTH_AT_NEW_LEVEL2
2 MEDI MED1 OPT1 EE+1 HEALTH_AT_NEW_LEVEL2
3 MEDI MED1 OPT1 EE+F HEALTH_AT_NEW_LEVEL2
4 MEDI MED1 OPT2 EE HEALTH_AT_NEW_LEVEL1
HEALTH_AT_NEW_LEVEL2
5 MEDI MED1 OPT2 EE+1 HEALTH_AT_NEW_LEVEL2
6 MEDI MED1 OPT2 EE+F HEALTH_AT_NEW_LEVEL2
(***list of dependents***)
HEALTH_AT_END_OF_BPLAN
HEALTH_AT_END_OF_PLTYP
HEALTH_AT_LAST
As you can see from entry 6 in the above table, a list of possible or current dependents (forms HR_BEN_ENRO or HR_BEN_CONF respectively) is printed for a health plan before the text element HEALTH_AT_END_OF_BPLAN. The benefits form driver produces the list of dependents basically in the same fashion as the list of plans. For every possible or current dependent of the plan, the dictionary structure RPBENODP or RPBENDDP, respectively, is filled, and this data is inserted into a set of SAPscript text elements.
The following are the standard text elements used for printing dependent data:
Text Element Short Description
DEPEND_AT_FIRST Begin of dependent data for given plan
DEPEND_AT_EACH_PERSON Data of single dependent
DEPEND_AT_LAST End of dependent data for given plan
Similarly, the form driver prints beneficiary and investment data for benefits plans from categories other than health. This data is also printed before the text element <category>_AT_END_OF_BPLAN.
The following tables summarize the relevant information on the standard text elements of window MAIN and the data dictionary structures involved in benefits form printing. The above explanations for health plans may be generalized and expanded for all benefits categories, using the data from these tables.
The benefits form driver processes the following standard text elements:
Text Element Available for <category>
<category>_AT_FIRST All categories
<category>_AT_NEW_PLTYP All categories
<category>_AT_NEW_BPLAN All categories
<category>_AT_NEW_LEVEL1 HEALTH, INSURE, MISCEL
<category>_AT_NEW_LEVEL2 HEALTH
<category>_AT_END_OF_BPLAN All categories
<category>_AT_END_OF_PLTYP All categories
<category>_AT_LAST All categories
The following values are possible for the prefix <category>:
Benefits Category Prefix <category>
Credit plans CREDIT
Health plans HEALTH
Insurance plans INSURE
Savings plans SAVING
Flexible spending accounts SPENDA
Miscellaneous plans MISCEL
Stock purchase plans STOCKP
The following standard text elements are available for additional information about a benefits plan. These are printed before text element <category>_AT_END_OF_BPLAN:
Text Element Available for <information>
<information>_AT_FIRST All types
<information>_AT_EACH_PERSON DEPEND, BENEFI, CONTIN
<information>_AT_EACH_ITEM INVEST
<information>_AT_LAST All types
The following values are possible for the prefix <information>:
Type of Information Prefix <information>
Dependents DEPEND
Beneficiaries BENEFI
Contingency beneficiaries CONTIN
Investments INVEST
The following dictionary structures are filled by the benefits form driver when it processes the list of offered or current plans:
Benefits Category Benefits Offer Current Benefits
Credit plans RPBEN_O1 RPBEN_D1
Health plans RPBEN_OA RPBEN_DA
RPBENODP RPBENDDP (dependents)
<Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHBEN0440 | 0 | HLA0006759 | Administration |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | SE71 |
History
| Last changed by/on | SAP | 20000117 |
| SAP Release Created in |
