Ansicht
Dokumentation

RPURMPK0 - Create Third-Party Remittance Posting Run

RPURMPK0 - Create Third-Party Remittance Posting Run

Addresses (Business Address Services)   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This report extracts remittance items from the third-party remittance tables T51R5 and T51R6 and places them into a posting run. The posting run represents remittances in the form of a sequence of documents which you can then examine, release and post to FI.

This report should be run at at least once a day.

The due date you select for the posting run should always be the first due date listed in the update run log from the previous third-party remittance step (Update Remittance Tables from TemSe Object - RPURMU00). When you enter this date in the Due date field, you should also use the "Less than or equal to"selection option to be sure that you catch any earlier outstanding remittance items.

All remittance items in T51R5 that belong to the defined company code and business area are selected.

Activities

  • Enter the earliest due date from the 'Update tables' log
  • Use the 'Less than or equal to' selection option to ensure that earlier outstanding remittance items are included in the posting run
  • Enter any further selection criteria
  • Choose 'Execute'

Output

The report creates a log listing all remittances due by FI vendor and HR creditor. The third-party remittance posting run is entered at the bottom of the log.

Activities

Process posting run:

You now have two options for proceeding to the next step. You can:

  • Double-click on the '3PR posting' line at the bottom of the log

  • Go back to the previous screen and select 'Process posting run' from the third-party remittance menu path

Either of these options take you to the 'Display posting runs' overview screen, which contains a list of all as yet unposted posting runs in your system. You will find your third party remittance run under the 'TP' (Third- party remittance) heading.

From here, you can process your third-party remittance posting run by double-clicking it to check and release its documents.

Once all documents are released, you can post the entire run to FI from the 'Display posting run' screen.

Technical details:

Normal remittance items

Normal remittance items (those that do not involve accumulators) are handled as follows:

Whatever is due within the given due date period is included in the posting run.

The report checks all accumulators with check dates that are less than or equal to the requested due date. This is based on the assumption that whatever has a higher check date than the requested due date is logically not yet known. This makes it possible to determine how much the accumulated amount would be, independent of the due date. It is then also possible to check against given rules and determine a new due date. After determining the new due date (if necessary), those HR payees that are due within the given due date period are included in the posting run.

If due dates are changed, the corresponding HR creditor entries are modified in T51R5.

The link originator is treated as a normal remittance item, but the linked HR payees are included in the posting run regardless of their due date (mostly in the future). This means that the old due date is changed into the new one.

A remittance transaction consists of at least two records:

  1. Credit posting - credit an HR creditor's account
  2. Debit posting - debit a withholding account, which is usually an account for withholding tax or union dues

A due date and HR reference number are placed in the credit posting record. The due date indicates when the remittance item is due while the HR reference number is used to identify the corresponding remittance items when the A/P system acknowledges that payment has been made.

HR reference numbers:

  • Digits 1-2 : "HR"
  • Digits 3-7 : T51R2-REMSN (indicating number of posting run)
  • Digits 8-12: T51RH-LIFSG, defined AP vendors subgroup in order to separate payments into different AP documents (see V_T51RH).

The following fields are stored in the credit posting transaction:

  • IN period
  • accounting type="K"
  • company code
  • business area
  • A/P vendor number
  • credit amount
  • due date
  • HR reference number="HR"+T51R5-REMKY

(please refer to structure EP in "RPCFDI00" for details...)

The following fields are stored in the debit posting transaction:

  • IN period
  • accounting type="F"
  • company code
  • business area
  • symbolic account
  • debit amount

(please refer to structure EP in "RPCFDI00" for details)

Requirements

The payroll run, the data collection run and the update run must have been completed before you can remit anything. Tables T51RL, T51RC, T51RH and T51RD must also be maintained.

Caution

Third-party remittance is intended as an automatic process, configured accordingly in the IMG. SAP does not recommend that you carry out third-party remittance manually.






CPI1466 during Backup   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 6073 Date: 20240601 Time: 183837     sap01-206 ( 90 ms )