Ansicht
Dokumentation

OHBEN0415 - Set Up SAPScript Templates

OHBEN0415 - Set Up SAPScript Templates

TXBHW - Original Tax Base Amount in Local Currency   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

In this step, you set up the SAPscript templates for COBRA letters, COBRA enrollment forms, COBRA confirmation forms, and COBRA invoices.

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:

  1. 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).
  2. 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.
  3. 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 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 COBRA_AT_FIRST
    COBRA_AT_NEW_PLTYP
    COBRA_AT_NEW_BPLAN
    COBRA_AT_NEW_LEVEL1
    COBRA_AT_NEW_LEVEL2
2 MEDI MED1 OPT1 EE+1 COBRA_AT_NEW_LEVEL2
3 MEDI MED1 OPT1 EE+F COBRA_AT_NEW_LEVEL2
4 MEDI MED1 OPT2 EE COBRA_AT_NEW_LEVEL1
    COBRA_AT_NEW_LEVEL2
5 MEDI MED1 OPT2 EE+1 COBRA_AT_NEW_LEVEL2
6 MEDI MED1 OPT2 EE+F COBRA_AT_NEW_LEVEL2
    (***list of dependents***)
    COBRA_AT_END_OF_BPLAN
    COBRA_AT_END_OF_PLTYP
    COBRA_AT_LAST

As you can see from entry 6 in the above table, a list of possible (form HR_BEN_COB_ENRO) or current dependents (forms HR_BEN_COB_CONF, HR_BEN_COB_INVO) is printed for a plan before text element COBRA_AT_END_OF_BPLAN is output. The COBRA form driver produces the list of dependents basically in the same way 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

DEPEND_AT_LAST

The following recommendations apply when changing the layout and contents of SAPscript forms:

  • Naming conventions for SAPscript COBRA forms
When you copy the standard SAPscript templates from client 000 to your customizing client, you can save your copies under using any names that meet the naming conventions for SAPscript forms. You can therefore create several copies of each SAPscript template in your customizing client.
You can use multiple copies, for example, to set up COBRA eligibility notices and COBRA enrollment forms with different layouts for each benefit area that you administer in your system. The COBRA form driver infers the SAPscript templates to be used for a particular benefit area from the form names entered in the step Assign Templates to Form Types.
  • Customizing of windows on the SAPscript form templates
When you create your own copies of the SAPscript COBRA forms you can modify the name, size, position on page, layout, or contents of standard windows. This is true for all windows which contain a single text only, in other words, all standard windows except MAIN.
In the window MAIN the text is broken down into several text elements. SAPscript therefore cannot automatically generate the text for output, but requires the help of a printing program (either subroutine SAP_GENERATE_EVENT_LETTER of program RPUCOB02, or the COBRA form driver HR_BEN_COB_FORM_PRINT_SAPSCR). For this reason, customizing of the window MAIN is more restricted, as described in the next points.
Keep in mind that the printing program only supplies a limited number of infotype and table work areas with data at run time. The list of supported data structures which may be used as text variables is given above in the sections "COBRA Eligibility Notification" and "Other COBRA Forms".
  • Customizing of text elements in the window MAIN:
COBRA eligibility notification (copy of form HR_BEN_COB_LET01)
On the standard form HR_BEN_COB_LET01, window MAIN contains two text elements: Element COBRA_NOTICE for the notice of continuation rights, and element COBRA_ELECTION for the COBRA election form. Processing of these text elements as described above in section "COBRA Eligibility Notification" is hardcoded in subroutine SAP_GENERATE_EVENT_LETTER of the COBRA letter generation program RPUCOB02.
Therefore, if you wish to follow the standard procedure for COBRA eligibility notification, you must not change the names of these text elements. However, you are free to modify the elements in any other way. For example, you can use your own COBRA text modules instead of the standard ones, or you can determine the text modules that are to be printed for a particular COBRA event and beneficiary according to your own logic.
Alternatively, you may replace both standard text elements with a single, unnamed text element (SAPscript default). In this case, the SAPscript composer can print the text of window MAIN without the help of the COBRA printing program. You therefore have the option of deviating from the two-piece layout of the standard COBRA eligibility notification.
  • Customizing of text elements in window MAIN:
Other COBRA forms (copies of forms HR_BEN_COB_ENRO, etc.)
The text to be printed in window MAIN, in other words, a qualified beneficiary's COBRA offer (form HR_BEN_COB_ENRO) or overview of current COBRA plans (forms HR_BEN_COB_CONF, HR_BEN_COB_INVO), is composed of a set of standard text elements. The names of these text elements are hardcoded in the COBRA form driver HR_BEN_COB_FORM_PRINT and therefore must not be changed or augmented.
Within each standard text element you may choose the format and content freely. In particular, you may delete those text elements which you deem as being unnecessary to print the list of current or offered benefits. For example, if you do not need to print additional information at the top of the list, just drop text element COBRA_AT_FIRST from your copy of the SAPscript COBRA forms.
However, when you customize text elements, take into account the data structures supported by the COBRA form driver and the procedure by which the data are supplied at run time. See the section "Other COBRA Forms" for details.
DEPEND_AT_LAST
  1. Copy the SAPscript templates HR_BEN_COB_LET01 for the COBRA eligibility notification, HR_BEN_COB_ENRO for the COBRA enrollment form, HR_BEN_COB_CONF for the COBRA confirmation form, and HR_BEN_COB_INVO for the COBRA invoice from client 000 to your customizing client.
    1. From the Form Painter, choose Utilities -> Copy from client.
    2. Enter HR_BEN_COB_LET01 as the form to be copied in the field Form name, a name for your copy in the field Target form, and ensure that the field Source client contains the value 000.
    3. Choose Execute.
A copy of the COBRA eligibility notice is created in your customizing client with the name that you specified. Repeat steps 2 and 3 above if you require more copies of the COBRA eligibility notification template. For each copy specify a different name in the field "Target form".
Repeat the steps 2 and 3 above to create copies of the COBRA enrollment form template, COBRA confirmation form template, and COBRA invoice template. Remember that you need to create copies of the confirmation form and invoice templates only if want to administer COBRA enrollment.
  1. Return to the Form Painter initial screen and modify your copies of the standard SAPscript templates as required.
DEPEND_AT_LAST

For detailed information about the Form Painter and SAPscript form editing, choose Help -> Application help.

DEPEND_AT_LAST

The following example shows the steps that you need to follow to change the header on a COBRA enrollment form:

  1. After you have copied the form HR_BEN_COB_ENRO from client 000, as described above, return to the Form Painter initial screen.
  2. Enter the name of your copied form in the Form field.
  3. Select Windows and choose Change.
A list of form windows is displayed.
  1. Double-click on the HEADER window to select it.
  2. Choose Edit -> Text elements to access the text element editor.
  3. Change the text as required.
  4. Return to the form windows list.
  5. Save your changes.
  6. Choose Forms -> Activate to activate your modifications.





SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 26928 Date: 20240523 Time: 174503     sap01-206 ( 328 ms )