Ansicht
Dokumentation

RPIPITU0 - Changing Garnishment Status from Active to Inactive/Pending/Released

RPIPITU0 - Changing Garnishment Status from Active to Inactive/Pending/Released

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

Description

This report enables you to set the status of a garnishment to one of the following statuses:

  • Inactive
  • Released
  • Pending

Use

This report can filter garnishment orders by Order Typeand Category in the Order type selectionand Document category selectionsections. These fields are read from infotypes 0195 and 0194, respectively.

. A batch input session is created which sets the required status for all of the selected garnishments on a specific date. You can process the batch input session via the menu path System -> Services -> Batch input -> Sessions.

If you want to set the status 'inactive' for garnishments, only garnishments are selected which have the status 'active'.

If you want to set the status 'released' for garnishments, garnishments are selected which have the status 'active' or 'inactive'.

If you want to set the status 'pending' for garnishments, garnishments are selected which have the status 'active'.

Garnishments which meet the following criteria are flagged as repaid:

  • As of the specified date, the garnishment has no garnishment orders, or
  • As of the specified date, there are no periodic claims, and once-only claims have been repaid in full.

These flags are used as a default if you want to change the status to 'inactive'. There is no default setting for changing the status to 'released'.

There are two ways to start this report. If you have not set a flag for the field 'Run as batch processing', a list is created of all selected garnishments, and the default garnishments are flagged. You can choose to reject these defaults or set flags for other garnishments that were not proposed by the system. You must do this if you want to set the status to 'released'. You can then create the batch input session for which all of the flagged garnishments are used.

If you have set a flag for the field 'Run as batch processing', a list is not created. Instead, a batch input session is created immediately. Only the garnishments proposed by the system are used. This prevents you from changing the status to 'released' automatically.

Output

The list has the following structure:

  1. The garnishments are grouped according to:
  • Personnel area
  • Personnel subarea
  • Employee group
  • Employee subgroup
  1. This is followed by information on:
  • Employee
  • Status and category of the garnishment
  • Vendor and case number
  • Garnishment number
  • A flag that has been set for the field 'R' means that the garnishment meets the above criteria; that is, it has been repaid.
  • The first field in the list determines whether the garnishment should be used for creating the batch input session. Flags have already been set for the garnishments proposed by the system.

Double-clicking on an entry in the list enables you to access the master data of the corresponding garnishment.






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

Length: 3763 Date: 20240520 Time: 105856     sap01-206 ( 62 ms )