Programme SAP RPURMPK0 - Create Third-Party Remittance Posting Run

Description
This report extracts remittance items from the third-party remittancetables T51R5 and T51R6 and places them into a posting run. The postingrun represents remittances in the form of a sequence of documents whichyou 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 firstdue date listed in the update run log from the previous third-partyremittance 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 optionto be sure that you catch any earlier outstanding remittance items.
All remittance items in T51R5 that belong to the defined company codeand business area are selected.

Activity

  • 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 andHR creditor. The third-party remittance posting run is entered at thebottom of the log.

      Activity

      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' fromthe third-party remittance menu path
      Either of these options take you to the 'Display posting runs' overviewscreen, which contains a list of all as yet unposted posting runs inyour 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 bydouble-clicking it to check and release its documents.
      Once all documents are released, you can post the entire run to FI fromthe 'Display posting run' screen.

      Technical details:

      Normal remittance items
      Normal remittance items (those that do not involve accumulators) arehandled as follows:
      Whatever is due within the given due date period is included in theposting run.

      Accumulator remittance items
      The report checks all accumulators with check dates that are less thanor equal to the requested due date. This is based on the assumptionthat whatever has a higher check date than the requested due date islogically not yet known. This makes it possible to determine how muchthe accumulated amount would be, independent of the due date. It isthen also possible to check against given rules and determine a new duedate. After determining the new due date (if necessary), those HRpayees that are due within the given due date period are included inthe posting run.
      If due dates are changed, the corresponding HR creditor entries aremodified in T51R5.

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

      Further information
      A remittance transaction consists of at least two records:
      RESET N1
      Credit posting - credit an HR creditor's account
      Debit posting - debit a withholding account, which is usually anaccount for withholding tax or union dues
      A due date and HR reference number are placed in the credit postingrecord. The due date indicates when the remittance item is due whilethe HR reference number is used to identify the correspondingremittance items when the A/P system acknowledges that payment has beenmade.
      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:
        RESET N1
        • 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:
          RESET N1
          • IN period

          • accounting type="F"

          • company code

          • business area

          • symbolic account

          • debit amount

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

            Precondition
            The payroll run, the data collection run and the update run must havebeen 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, configuredaccordingly in the IMG. SAP does not recommend that you carry outthird-party remittance manually.

878052MSC: Incomplete output for remittance posting runs.
627779MSC: Missing selection texts for RPURMPK0
612136MSC: Acceleration of due items too late
412517GEN: System applies incorrect remittance rule.