HR-BENEFITS

Benefits :- Mainly used in USA and maintain third party. Considered as EE and ER contributions. EE dependents like (father,mother,spouse,son,daughter).. Simply called as , Insurance or Corporate medical proposes (TTK,Mediassist..) In SAP we have to configure with different plans. 1-Health plan 2-Saving Plan 3-Insurance Plan 4-Cobra Plans 5-Flexible Spending Accounts (FSAs) 6-Stock Purchase Plans 7-Credit Plans 8-Miscellaneous Plans SAP Configuration path :-SPRO-PM-Benefits (have to do backend config.) Main infotypes are , IT167(Health plan),IT168(Saving plan),IT169 (Insurance plan)and IT171(General Benefits Information). We have to the enrollments.

more generous than legislation requires, and to allow regular plan participation to continue even when certain events occur. If you do not select a particular event type, the system will not collect qualified beneficiaries who experience that event. 2. If non-resident aliens who receive no income from US sources are excluded from qualifying for COBRA, enter the appropriate residence status. The residence status is stored on the Residence Status (infotype 0094) record.

3. Indicate whether the legally required COBRA coverage continuation period begins when a COBRA qualifying event occurs or when regular health coverage ends, as determined by the plan's termination rule. 4. Use the indicator Restrict offer to last participation to specify whether you want to offer qualified beneficiaries only those COBRA-relevant plans and plan options in which they were enrolled prior to the qualifying event, rather than all COBRA-relevant plans for which they were eligible. 5. Use the indicator Offer only FSAs with positive balance to specify whether you want to offer COBRA coverage continuation only for those FSAs that have a positive balance on the date of the COBRA event or for all FSAs regardless of their balance. Define Additional Qualified Beneficiary Subtypes Use In this step, you can determine whether or not certain types of persons can be COBRA-qualified beneficiaries for certain types of COBRA qualifying events. For each type of event, COBRA legislation prescribes which types of person can become qualified beneficiaries. This is the case for employees, spouses, children, and stepchildren. The types of events for which these types of person can be qualified beneficiaries are, therefore, predefined in the system. However, for other persons, such as domestic partners and their children, your company policy will determine which events qualify a person for COBRA coverage. You therefore need to specify in this step any such additional persons who can qualify. The types of person who can be qualified beneficiaries are determined by the subtype of theFamily/Related Persons infotype (0021). Standard settings Certain potential COBRA-qualified beneficiaries are predefined in the system (as explained above). For any additional types of person that you want to specify as potential qualified beneficiaries, the system only allows you to specify those events that make sense for the type of person that you have selected. Divorce, for example, is not relevant for a domestic partner. Define Unavailability Reasons Use In this IMG activity, you enter and store the Unavailability Reasons for COBRA coverage. If the health insurance plan administrator receives notice from an individual of a qualifying event, a second qualifying event, or of a Social Security disability determination and the administrator determines that COBRA coverage or an extension of COBRA coverage is not available, the administrator must notify the individual of the unavailability and explain why COBRA coverage is not available. This Notice must be provided regardless of the reason for denying the request for COBRA coverage, including that the notice of the qualifying event was incomplete or not furnished in a timely manner. The Notice of Unavailability of COBRA Coverage must be sent within the time frame specified for the COBRA Election Notice. Example Examples of reasons for the unavailability of COBRA coverage include: Voluntary Drop of Coverage There has been no loss of group coverage Coverage was previously terminated for non-payment of premiums The SSA disability determination was not provided within 60 days of receipt The disability did not occur during the first 60 days under COBRA The company terminated the group plan and no alternative plan is available The person moved from the insurer's service area; no alternate is available Define Early Termination Reasons

In this step, you define the possible reasons for early termination of COBRA coverage, as required in your organization. These entries are freely definable. When COBRA coverage is terminated early in the COBRA Participation tool, a reason is automatically recorded on the COBRA-Qualified Beneficiary infotype (0211). Example A beneficiary fails to make payments within the specified payment period. The employer terminates COBRA coverage and the reason Non-payment of premium is recorded on infotype 0211. A disabled beneficiary is granted 11 months additional coverage on top of the basic 18 month continuation period. Within this 11 months, the beneficiary notifies the employer that she is no longer disabled. The employer terminates COBRA coverage and the reason No longer disabled is recorded on infotype 0211. Form Setup In this section of the IMG, you set up form/letter templates for COBRA using either SAPscript or office applications, for example, Microsoft Word. The following table shows the characteristics of form printing using SAPscript or office templates, and may help you to decide which technology you want to use: SAPscript Office Suitable for efficient mass processing Recommended for a smaller set of forms only Stability depends on front end installation Works on all platforms supported by Works only in connection with a front end running the SAP GUI for SAP Windows and the corresponding office application Supports printing in background Background printing not supported (*) Knowledge of SAPscript and/or ABAP Knowledge of Microsoft Word and/or VBA required for required for customizing customizing (*) Background printing cannot be supported technically with office forms, since no SAP front end is available to run the office application. Set Up SAPScript Forms In this section of the IMG you set up the form layout for COBRA letters and prepare the standard COBRA letters using SAPscript. Set Up SAPScript Templates In this step, you set up the SAPscript templates for COBRA letters, COBRA enrollment forms, COBRA confirmation forms, and COBRA invoices.

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: 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

Recommendation
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.

Activities
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. a) From the Form Painter, choose Utilities -> Copy from client. b) 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. c) 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. 2. Return to the Form Painter initial screen and modify your copies of the standard SAPscript templates as required.

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

Help ->

Example
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. 4. Double-click on the HEADER window to select it. 5. Choose Edit -> Text elements to access the text element editor. 6. Change the text as required. 7. Return to the form windows list. 8. Save your changes. 9. Choose Forms -> Activate to activate your modifications. Set Up Notification Text In this step, you set up the notification texts printed on the standard COBRA letters using SAPscript. The master copies of the notification texts are always delivered in client 000, and you should always copy these to your customizing client and modify them there, as you require. Thus from release to release, new versions may be delivered by SAP to client 000, but your modified texts are not overwritten. The SAP letter generation logic is as follows; 1. One of the following letters is always generated: Notice_Of_Continuation_Rights Notice_of_Second_Event Notice_of_Bancruptcy 2. Depending on whether it is for the employee, spouse or children, one or more additional enrollment letters are generated: Election_By_Employee Election_By_Spouse Election_By_Dependent_Child 3. An enrollment form is printed per COBRA-qualified beneficiary. If this logic and the texts provided do not suit your needs, proceed to implement your own user exit for this purpose.

Custom letterswhere you can

Activities
First copy the COBRA texts to the client you are currently customizing; 4. Select the menu path Utilities -> Copy from client. 5. In the following screen, enter an asterisk (*) in the field Text name. 6. Enter 'PACO' in the field Text ID. 7. Enter 'EN' in the field language. 8. Select 'Process'. Then modify the texts, if you require; 9. In the first screen 'Standard Text: Request', enter the name of the text you want to modify. 10. Enter 'PACO' in the field Text ID. 11. Enter 'EN' in the field Language. 12. Select 'Process'. You can now modify and save your text. For more detailed instructions on copying, comparing and modifying texts, select the menu path Help -> Extended help. Set Up Office Templates In this section, you set up templates for your COBRA letters using office applications. You do this as follows: 1. You copy the sample form templates in the Business Document Service (BDS). 2. You modify the copied templates to meet your requirements.

Copy Templates in BDS In this step you copy the sample templates provided by SAP, giving the copy a new name. Activities 1. In the Business Document Navigator, expand the node for the relevant document and position your cursor on the template that you want to copy. 2. Choose Copy document. 3. Enter a description and language for the document in the following dialog box and choose Continue. 4. Repeat steps 2 and 3 until you have copied all the templates you need. 5. Save your changes. Modify Templates In this step, you set up the office templates for COBRA forms. Requirements You have copied the sample form templates in the previous step. Standard settings An interface between the application server and a word processor running on the front end enables you to generate forms using office applications. The interface consists of a set of macros within the form template and a set of tables used for transferring the data needed for generating forms. The following macros are triggered by the application server: Macro Description InitDisplay() Initialization when form is displayed (print preview) InitPrint() Initialization when form is printed InitCustomize() Initialization when form is opened for customizing InsertData() Generates the form FinishedDisplay() Called after form is generated FinishedPrint() Called after form is generated FinishedCustomize() Called after form is generated DeleteCurrentData() Removes the data inserted by InsertData() (only used for customizing) EditMacro() Opens window to edit macros (only used for customizing) All data required for form generation is collected on the application server and exported to the front end in the form of tables. Each exported table is characterized by a public name and a structure that is defined within the SAP System. These characteristics are listed below: Column A indicates the structure used for confirmation forms, column B indicates the structure used for enrollment forms, and column C indicates the structure used for invoice forms. Public Name A B C Description Texts TEXTPOOL Language dep. texts HeaderData RPBENFORM_HEADER Data needed for header COBRAData RPCOBLET01 General COBRA data COBRAEvent RPCOBEVENT COBRA event data HealthPlan RPBEN_DA RPBEN_OA RPBEN_DA Health plans SpendaPlan RPBEN_DD RPBEN_OD RPBEN_DD Flexible spending accounts Dependents RPBENDDP RPBENODP Benefit dependents The number of forms that can be printed depends on the form generation mode. The following generation modes are possible: Print Display (print preview) Customize (the activities in this IMG step)

While the modes "Display" and "Customize" generate one form only (for a particular personnel number), The "Print" mode can generate forms for a set of personnel numbers. Program Flow for Mode "Print" Application Server Front End Open template Word processor opens template with startup macro InitPrint() Loop at "set of selected personnel numbers" -> Read data from database -> Export tables to front end -> Call macro InsertData() InsertData() reads tables, generates form and prints it Endloop Call macro FinishedPrint() Close template Program Flow for Modes "Display" and "Customize" Application Server Front End Read data from database Export tables to front end Word processor opens template with startup macro InitDisplay() or InitOpen template Customizing() which calls InsertData() InsertData() reads tables, generates form Call macro FinishedDisplay() or FinishedCustomizing() In all of these modes, the macro InsertData() generates a form. In the "Customize" mode, it also prints them. The macro therefore reads the data from the exported tables and inserts it into the template. You can access the tables via an object model using the public name of the table, for example: set table = ThisDocument.Container.Tables("HealthPlan").table The sample templates use two different techniques to insert data into the two parts of the form: The header part contains the address window and the personnel header data. This part has a fixed layout and uses fields for inserting the data. The plan part contains the current or offered benefit plans. This part has to be generated dynamically by macros. In order to adapt the header part and the page header and footer to your own needs you can easily modify the template by moving the fields, formatting the text, inserting text and pictures, and so on. All sections and parts of the plan list (for example, plan type, amounts, and so on) are based on styles. These styles start with SAP_A for paragraph styles and SAP_Z for character styles. You can change the plan part as follows: If you only want to change the visual appearance of the plan list, for example the fonts, font sizes, or indentations, you simply need to change these styles accordingly. If you want to change the structure or the order of the plan list, you need to adjust the macros. Further notes In order to keep the sample templates language independent, all language-dependent texts are read from the exported table 'Texts', which contains all text elements starting with a 'F' from the function group HRBENUSCOBRA. Consequently, the sample templates do not contain any language-dependent strings. Note that if you add any coded text to the template or the macros, the template becomes languagedependent, in which case you need to set up a translated copy of the template for each language

required. You can do this by creating language variants in the Business Document Navigator (for more information, see the previous IMG step). Recommendation In order to avoid a virus warning each time a document is opened, you should deactivate the macro virus protection in Microsoft Word (Tools -> Options -> General). You need to do this for each frontend (Microsoft Word installation). Note that the sample templates are always printed to the default printer installed on the front end, and that each form creates its own print job. Therefore, if you are printing a large set of forms, SAP recommends that you disable visual notification of successfully processed print jobs to prevent repeat messages. Due to a bug in Microsoft Word, a template becomes corrupted if you insert a document variable into the header or footer of a page. One possible workaround is to use CustomDocumentProperties as in the sample templates. Activities 1. Specify the form template and form type that you want to modify on the selection screen. 2. Enter a test personnel number and a key date, if desired. If you make these entries, the system uses the corresponding personnel data and plan data to generate a test form so that you can immediately check your changes. 3. Choose Execute. The text processor appears within the SAP screen. If you provided test data in step 2, the form is automatically generated. Otherwise the template is retrieved from the database. 4. Modify the template. 5. If you provided test data in step 2, you can check your changes by choosing Refresh to regenerate the form. 6. Before you save the template, choose Reset form. This removes the test data from the form. 7. Save the template. Assign Templates to Form Types In this step, you assign the form templates to the form types. You also determine whether you want to use a SAPscript template or an office template. Activities 1. Select a form type. 2. Indicate whether you want to use a SAPscript or an office template. 3. If you want to use a SAPscript template, specify the name of the relevant template. 4. If you want to use an office template, specify the name of the relevant template and the version number. Custom Letters In this step, you implement the user exit to set up your own COBRA letters of notification. This user exit is called PCOB0001. Note You should carry out this step only if both of the following apply: The SAP standard processes does not suit your needs. You are a competent ABAP programmer. For general information about user exits, see the SAP Library ( Basis Components -> ABAP Workbench (BC-DWB) -> Changing the SAP Standard (BC) -> Customer Exits ). In addition, you can access detailed information about each user exit when you assign it to your project (see step 2. below). Activities 1. Create a project for the user exit. a) Enter a name for your project. b) Choose Create.

c) Enter the details of your project and choose Save. 2. Assign the user exit(s) to your project. a) Choose Components. b) Enter the name of the user exit to implement; in this case, PCOB0001. For more information on a user exit, see the exit documentation. c) Choose Save. d) Choose Back. 3. Make your coding modifications. a) Choose Enhancement assignments. b) Choose Change. c) Select the user exit you want to write code for. d) Select the include ZXPBCO01. The system prompts you to create this include, and you can continue to write your coding in it. 4. Activate your project by returning to the initial screen and choosing Activate project.