Ansicht
Dokumentation

OHAU02GF - Maintenance of infotypes 0194 and 0195

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

This Business Add-In (BAdI) is used in component PY-US-NT-GR. This BAdI enables you to create custom Garnishment Document(0194) and Garnishment Order(0195) infotype records to be in compliance with specific legislation from authorities other than federal.

The interface IF_HRPAYUS_EIWO_CUSTOM_INFTY comprises the following method:

• CREATE_CUSTOM_INFOTYPE_RECORDS: Create custom records for infotype 0194 and 0195.

This method is called after a new pair of infotype records 0194 and 0195 is successfully created for a processed IWO. The business scenario is a new IWO.

• REMOVE_CUSTOM_INFOTYPE_RECORD: Remove custom records for infotype 0194 and 0195.

This method is called after an infotype record 0194 is successfully released (finished) or delimited. The business scenario is the termination of an IWO.

.

Parameters

The following parameters are called using the methods of this BAdI:

• IS_ORDER: The fields in e-IWO Orderstable view can be imported to meet the requirements designated by the authority to process the order.

• IS_BASE_INFOTYPE_0194: The master data record in infotype 0194can be modified to meet the requirements designated by the authority.

• IS_BASE_INFOTYPE_0195: The master data record in infotype 0194can be modified to meet the requirements designated by the authority.

• CV_ERROR_MESSAGE: A message can be created and imported based on the reasons you have implemented this BAdI. The message is a free text that will be passed on to the log application when infotype is created to meet the requirements designated by the authority.

The BAdI described here is optional. Therefore, only implement this BAdI if your enterprise has the need and desire to do so.

These parameters are only required for e-IWO. When implementing this BAdI methods, it is important to keep in mind that is not possible with the standard solution. Hence, you should only implement it if changes in the 0194 and 0195 infotypes are required.

To implement Business Add-In (HRPAYUS_B_EIWO_CUSTOM_INFOTYPE), follow these steps:

1. Execute this IMG step. On the subsequent screen, enter a name for the implementation you wish to create.

2. Choose Create. (Or, alternatively, Edit. The remainder of the documentation for this activity describes the steps to be performed when you create a new implementation.)

Caution

3. Enter a short text for the implementation in the Implementation name field, then choose Continue.

4. On the subsequent screen, specify an Implementation short text, then choose the Interface tabstrip. The name of the implemented class fields are already found in this tabstrip.

5. Save your entries and assign the implementation to a package.

6. Place the cursor on the method you wish to process, then double-click to initiate method processing.

7. Enter the code for the implementation between the statements method ~ and endmethod.

8. Save and implement your code.

9. Return to the Edit Implementationscreen, then save your entries there.

10. If you wish to activate the implementation you have created at a later date, then exit the Edit Implementationscreen without activating the implementation. Otherwise, choose Activatefrom this screen to activate the implementation for immediate use.

There may be an order issued by the authority to be processed which contains an Income Withholding Fee. If an employer receives a withholding order from another state that directs the money to be sent to the State Collection and Disbursement Unit, the fee must be applied. This fee cannot be sent with the normal child support withholding payment, as it goes to a separate bank account and address. For this reason, you may create a custom infotype as a secondary record.

rdisp/max_wprun_time - Maximum work process run time   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 4906 Date: 20240523 Time: 182024     sap01-206 ( 57 ms )