Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PA-BN (Application Component) Benefits⤷
PBEC (Package) Benefits - Customizing
IMG Activity
| ID | OHBEN0415 | Set Up SAPScript Templates |
| Transaction Code | S_AHR_61002099 | IMG-Aktivität: OHBEN0415 |
| Created on | 19981221 | |
| Customizing Attributes | BEN_00_CN_1_2_I0101 | COBRA notification - mandatory - non-critical - US |
| Customizing Activity | BEN_00_SE71 | Transaction SE71 |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHBEN0415 |
In this step, you set up the SAPscript templates for COBRA letters, COBRA enrollment forms, COBRA confirmation forms, and COBRA invoices.
Requirements
Standard settings
In the standard system a number of SAPscript forms are provided as templates for printing the COBRA letter, COBRA enrollment form, COBRA confirmation form, and COBRA invoice, respectively. You copy these forms from client 000 to your customizing client, where you can modify their layout as required.
The standard letter for a COBRA-qualifying event is generated from two SAPscript templates:
Template Short Description
HR_BEN_COB_LET01 COBRA eligibility notification
HR_BEN_COB_ENRO COBRA enrollment form
If you intend to use the COBRA Administration module only up to the point of letter generation, you only need to copy and modify only these two templates. However, if you also want to enroll COBRA-qualified beneficiaries in plans and generate invoices for them you require copies of the following additional templates in your customizing client:
Template Short Description
HR_BEN_COB_CONF COBRA confirmation form
HR_BEN_COB_INVO COBRA invoice
The features and use of all standard templates are addressed in more detail in the following sections.
COBRA Letter Generation
The subroutine SAP_GENERATE_EVENT_LETTER of program RPUCOB02 generates letters as follows:
- For each qualifying event, a single notice of continuation rights is printed. Depending on what persons actually qualify for COBRA, the notice is addressed either to the employee, the spouse or divorced spouse, or a dependent child (in this order). If the relevant dependent address has not been maintained, the system uses the employee's permanent address instead (subtype '1' of the Addresses infotype 0006).
- For each COBRA-qualified beneficiary, a COBRA election form is printed. The election form layout varies for employee, spouse or divorced spouse, and dependent children, allowing not only the choice of individual COBRA coverage, but of family coverage as well, if applicable.
- In addition, a COBRA enrollment form is printed for each qualified beneficiary. The enrollment form lists all COBRA-relevant plans for which the person in question is eligible plus the possible dependents who may be covered by these plans.
The notice of continuation rights and the COBRA election form are both generated from your copy of SAPscript template HR_BEN_COB_LET01, whereas the COBRA enrollment form is generated from your copy of SAPscript template HR_BEN_COB_ENRO.
COBRA Eligibility Notification
The format and text of the eligibility notification parts of the standard COBRA letter must be contained in your copy of SAPscript form HR_BEN_COB_LET01:
- Part 1 (notice of continuation rights) is printed on several pages whose layout is defined by the form pages FIRST and NEXT.
- Part 2 (COBRA election form) is printed on a separate page ELECTION.
On the standard SAPscript form HR_BEN_COB_LET01, text is inserted into 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 page
DATE Letter date FIRST, NEXT
EVDATA COBRA event data FIRST
FOOTER Footer lines FIRST, NEXT, ELECTION
HEADER Header lines FIRST, ELECTION
MAIN COBRA notification FIRST, NEXT
COBRA election form ELECTION
MAINFRM Frame for window MAIN FIRST, NEXT, ELECTION
PAGECNT Page numbering NEXT
QBADDR COBRA beneficiary address FIRST
In each window, SAPscript symbols are used as placeholders for data stored in or produced by the SAP System. These symbols are replaced at run time by their values on the given letter date. The following data structures from the ABAP Dictionary can be read and data inserted by the COBRA Letter Generation program (RPUCOB02):
Data Structure Short Description
P0006 Address (subtype 1 = Permanent address)
P0021 Family / related persons
P0106 Related persons (North America)
RPCOBLET01 COBRA letter variables
RPCOBQBDAT COBRA benefit data
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, there are two text elements COBRA_NOTICE and COBRA_ELECTION, which are used to print the notification of continuation rights and the COBRA election form, respectively.
Both of these text elements are composed of standard text modules, which also need to be copied from client 000 to your customizing client. This procedure is described in the next IMG step.
Other COBRA Forms
In the standard system, copies of SAPscript forms HR_BEN_COB_ENRO, HR_BEN_COB_CONF, and HR_BEN_COB_INVO are used for printing the COBRA enrollment form, COBRA confirmation letter, and COBRA invoice, respectively.
On the standard SAPscript forms, text and benefits data are printed into a number of text windows. The windows and their meanings are listed below, and it is indicated on which pages they will be placed on form output:
Window Meaning Printed on
DATE Form date All pages
FOOTER Footer lines All pages
HEADER Header lines First page
MAIN COBRA plans All pages
MAINFRM Frame for window MAIN All pages
PAGECNT Page numbering All pages except first
QBADDR COBRA beneficary address First page
QBDATA COBRA beneficiary data First page
QBDATA2 COBRA beneficiary data All pages except first
In each window, SAPscript symbols are used. These symbols are placeholders for data stored in the SAP system and will be replaced at run time by their values as of the given form date. The following data structures from the ABAP Dictionary are supported in this way by the standard COBRA form driver (function module HR_BEN_COB_FORM_PRINT_SAPSCR ):
Data Structure Short Description
P0001 Organizational assignment
P0002 Personal data
P0006 Address (subtype 1 = Permanent address)
P0021 Family / related persons
P0106 Related persons (North America)
RPCOBLET01 COBRA letter variables
RPCOBQBDAT COBRA benefit data
T001P Personnel area/subarea
T500P Personnel area
T501T Employee group text
T503T Employee subgroup text
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 COBRA plans.
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 COBRA 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 COBRA health plans
The following text elements are used to format the output of flexible spending accounts on a benefits form:
SPENDA_AT_FIRST Start of COBRA flexible spending accounts
SPENDA_AT_NEW_PLTYP New plan type
SPENDA_AT_NEW_BPLAN New plan within given plan type
SPENDA_AT_END_OF_BPLAN End of given plan
SPENDA_AT_END_OF_PLTYP End of given plan type
SPENDA_AT_LAST End of COBRA flexible spending accounts
The form driver HR_BEN_COB_FORM_PRINT_SAPSCR first creates the list of offered or current COBRA plans (forms HR_BEN_COB_ENRO and HR_BEN_COB_CONF / HR_BEN_COB_INVO) and stores it internally. It then processes the list entry by entry and successively moves the plan data to either the dictionary structure RPBEN_OA (COBRA offer, form HR_BEN_ENRO) or RPBEN_DA (COBRA plan display, forms HR_BEN_COB_CONF, HR_BEN_COB_INVO).
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 COBRA health plan MED1 is offered to a qualified beneficiary. There are two options for this plan: OPT1 and OPT2, with t
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 | OHBEN0415 | 0 | HLA0100334 | Initial Notification |
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 | 20000114 |
| SAP Release Created in |
