SAP ABAP IMG Activity OHAU02FB (Create forms for notice letters)
Hierarchy
☛ SAP_HRCUS (Software Component) Sub component SAP_HRCUS of SAP_HR
   ⤷ PY-US (Application Component) USA
     ⤷ P10C (Package) HR customizing: USA
IMG Activity
ID OHAU02FB Create forms for notice letters  
Transaction Code S_AHR_61000011   IMG-Aktivität: OHAU02FB 
Created on 19981218    
Customizing Attributes OHAU02FB   Create forms for notice letters 
Customizing Activity OHAU02FB   Create forms for notice letters 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHAU02FB    

In this step, you create standardized forms for garnishment notice letters.

Five different types of notice letters exist in the standard system.

  1. Notification letters inform the employee that a garnishment has been received.
  2. Bankruptcy letters inform the originator that a bankruptcy order has been received for the employee.
  3. Release letters inform the originator that a garnishment has ended.
  4. Termination letters inform the originator that the employee has left the company.
  5. Leave of absence letters inform the originator that the employee is on a leave of absence.

Standard settings

As delivered, the standard system uses form class CPL4 for garnishment notice letters and any tables, field names and conversions that are associated with these letters.

Form Creation

This section explains how to set up forms for garnishment notice letters and how to print fields from garnishment master data.

Garnishment master data consists of the infotypes Garnishment Document and Garnishment Order. While any one garnishment is allowed exactly one entry in the infotype Garnishment Document, several entries are permissible for the infotype Garnishment Order. A single support garnishment, for example, may have multiple orders for alimony and alimony arrears.

This disparity affects printing of master data on the respective form. While garnishment document data is printed at fixed positions on the form, garnishment order data can only be printed in a form window.

Garnishment document data is stored in table P0194. Only the key for the vendor is stored in this table. Other data, such as the name of the vendor, is stored in table LFA1. Garnishment order data is stored in table P0195. A wage type must be used to access the fields contained in these tables when printing is required.

As delivered, the standard system uses wage type YG01 to print fields from tables P0194 and LFA1.

Example

  1. The following examples show how to set up data that is to be displayed in fixed positions:
  • Printing the case number

PType    No    Offs    Length    WType    Field        Conv    R    Field offset

EP    07    020    35        YG01    P0194-GCASE

  • Printing the originator

The originator code must be printed, followed immediately by the address of the originator. The originator code is only stored as a value. If the text needs to be printed, conversion 01 must be used. The word Attorney, for example, would then be printed instead of the value 1.

PType    No    Offs    Length    WType    Field        Conv    R    Field offset

EP    08    020    10        YG01    P0194-ORCOD    01

EP    09    020    40        YG01    ADRSO-LINE1    01

EP    10    020    40        YG01    ADRSO-LINE2    01

EP    11    020    40        YG01    ADRSO-LINE3    01

  • Printing the vendor name

PType    No    Offs    Length    WType    Field        Conv    R    Field offset

EP    12    020    35        YG01    LFA1-NAME1

  1. The following example shows how to set up data that is to be displayed in windows.

The wage type used to print fields from table P0195 is specified in the view Garnishment Order Types. An order type is assigned to each garnishment order and is defined in the same view, where it is also assigned a wage type. This enables you to print different fields from table P0195 for different order types within the form.

In this example, garnishment order types CR (Creditor) and CS (Child support) are defined in the view Garnishment Order Types. Wage type MG10 is assigned to order type CR, while wage type MG20 is assigned to order type CS.

In this case, the fields order type and initial balance must be printed in the notice letter for the creditor, while the fields order type and periodic deduction must be printed for child support, together with their unit (e.g. monthly).

  • Setting up the 'form window'

Window        Line area        Column area

F1        24 59            000    077

  • Setting up 'form-related wage type control' in the window

WType    Tab    No    Win    Gr    SGr    LType    CType

MG10    R    01    F1    01    01    01    X

MG20    R    01    F1    01    01    02    X

The creditor is assigned line type 01 and child support is assigned line type 02.

  • Setting up the 'line layout in window'

LType    CType    Offs    Length    Field        FOffs    Conv    Rule

01    X    000    30    P0195-ORDCD            01

01    X    032    14    P0195-IBALN

02    X    000    30    P0195-ORDCD            01

02    X    032    09    P0195-DEDUC

02    X    042    20    P0195-DEDUT            01

  • Printing different addresses on the form

By modifying feature ADDRS, you can choose different subtypes of the infotype Addresses to be printed on the form.

Thus, the notice letter could be sent to an employee's permanent residence, or to a temporary residence.

Feature ADDRS would be set up as follows:

Variable Argument F D Operation
D RCLAS "Ask for form class
CPL4 D VARKY(4) "Ask for form
CPL4 ABCD &ADDRS=3, "For notice letter with form ABCD
CPL4 **** &ADDRS=1, "For all other notice letters
**** &ADDRS=1,

Activities

Using the above examples as a reference, execute this step to set up the forms your enterprise requires for garnishment notice letters.

Further notes

The system includes the following model forms for garnishment answer letters:

Form UFG5: Model notice letter
Form UFG6: Model termination letter
Form UFG7: Model leave of absence letter

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
OHAU02FB US USA
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHAU02FB 0 HLA0009693 Garnishment 
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
PE51 T - Individual transaction object PE51 10 Form Editor 
V_T514C V - View OH14 CPL4 01 Permitted conversions 
V_T514K V - View OH14 CPL4 01 Permitted table names 
V_T514N V - View OH14 CPL4 01 Permitted field names 
History
Last changed by/on SAP  19981218 
SAP Release Created in