Kontakt

Ansicht
Dokumentation

HHKCDTC0 - Preliminary Data Medium Exchange - for several payment runs(HK)

HHKCDTC0 - Preliminary Data Medium Exchange - for several payment runs(HK)

CL_GUI_FRONTEND_SERVICES - Frontend Services   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use the preliminary DME program to evaluate payroll results in order to create a database, the so called payment data. Creating payment data is the first step in the process of wage and salary payment.

You can also use the preliminary DME program when you want to perform several part payments within a payroll period for different deadlines (qualified advance payment).

The preliminary DME program can evaluate payments with different payment methods in one payment run. The payment medium programs, that process data created by the preliminary DME program, select the corresponding data records using the payment method.

The preliminary DME program processes not only information from the master data, but also information from an employee's payroll results. You can find additional information in the following sections Payment-Related Information in the Master Data und Payment-Related Information in the Payroll Results in the SAP Library. Choose Human Resources-> Payroll-> Subsequent Activities -> Wage and Salary Payments.

Integration

The payment data created by the preliminary DME program is processed by country-specific payment medium programs of Financial Accounting in order to create payment mediums (for example, DME files for the bank, checks). You have to start this subsequent program after the preliminary DME program has evaluated the employee payroll results and created the payment data.

Prerequisites

You have ended payroll for the payroll period for which you want to perform the wage and salary payment.(Exception: you execute a qualified advance payment before payroll has ended.)

In agreement with Financial Accounting you have checked or made the following settings in Customizing:

  • Set up the payment method (in Customizing of Personnel Management under Personnel Administration -> Personal Data -> Bank Details -> Define Payment Method)
  • Set up the house bank and house bank account (in Customizing of Payroll under Data Medium Exchange -> Preliminary Programs for Data Medium Exchange -> Set Up House Banks)
  • Define the sending bank (using the feature Bank Details of the Sender for Data Medium Exchange (DTAKT) in Customizing of Payroll under Data Medium Exchange -> Preliminary program for Data Medium Exchange -> Define Sending Banks)
  • Define the paying company code if you do not want to use the company code stored in the Organizational Assginment (0001) infotype (use the feature Bank Details of the Sender for Data Medium Exchange (DTAKT) in Customizing of Payroll under Data Medium Exchange -> Preliminary Programs for Data Medium Exchange -> Define Sending Banks).
  • Assign the text key for the payment transactions to transfer wage types (in Customizing of Payroll under Data Medium Exchange -> Preliminary Programs for Data Medium Exchange -> Check Text Keys for Payment Transactions ).
This assignment is not necessary in all country versions.

Features

The preliminary DME program reads the table Payment Information (BT) for each current original event for the employees processed in a payment run in the payroll results.

For each entry in this table the system executes the following steps:

  • The system determines the information about the payee
If custom payee name in selection screen is not specified, payee is determined by the following:
  • from the entry in table Payment information(BT)

  • from table Payee Key (T521B) when the entry in the table Payment information (BT) contains a payee key

  • from infotypes Personal Data (0002) and Address(0006), when the entry in table Payment information(BT) contains neither a payee key nor payee data

If custom payee name is specified in selection screen, then the payee name is determined by the active sources and priority specified in custom payee name.
  • The system evaluates the feature Bank Details of the Sender for Data Medium Exchange (DTAKT) in order to determine the following information:
  • paying company code

  • house bank

  • house bank account

  • The system reads the field Payment Notes in table Payment information(BT):
  • If the field Payment Notes is filled, the content of the field is transferred to the payment data.

  • If the field Payment Notes is not filled, the following text is used: "Wage/salary", , or "Pension", , .

  • The system determines the payment currency:
  • If the field Payment Currency in table Payment Information (BT) contains a value this is used for the payment.

  • If the field Payment Currency in table Payment Information (BT) does not contain a currency, the currency for the payment is taken from the field Currency in table Status Information of Payroll (VERSC).

  • The system reads the sort code of the house bank and the recipient bank from table Bank Master Record (BNKA).
  • The system checks the payment data for consistency. If there is a payment with inconsistent data for an employee, the system does not perform a payment for this employee.
  • For every entry in the table Payment Information (BT) the system creates an entry in the payment data.

If a payment run was not performed correctly (for example because of a program termination) you have to repeat this payment run. Prerequisite for the following procedure is that you have set the indicator Identify Transfers when creating the payment run.

  1. Make the same settings in the selection screen of the preliminary DME program that you made when creating the original payment run.
  2. In addition, enter the date and time of the payment run to be repeated in the input fields Repeat Run: Date and Time.
  3. Inputting this entry means that the system evaluates the entries in the table Payment Information(BT) that the preliminary DME program has indicated with the date and time, but whose date and time agrees with your entries in the input fields Repeat Run: Date and Time.
  4. If you only want to evaluate the entries in table Payment Information(BT) that have been selected, set the indicator only selected records.
If you do not set this indicator, the system also evaluates the entries in table Payment Information(BT) that are not indicated with date and time.
  1. Choose Execute.

If you do not know the date and time of the payment run to be repeated, proceed as follows:

  1. Using program Display Payroll Results (Report H99_DISPLAY_PAYRESULT) display one payroll result (for any employee) that was evaluated for the original payment run.
  2. Display the table Payment Information(BT).
  3. Choose an entry from table Payment Information(BT) which the preliminary DME program had indicated with time and date when creating the original payment run.
  4. Note the values in the fields Date and Time in order to enter them in the selection screen of the preliminary DME program in the Repeat Run: Date and Time fields.

Selection

Set flag for transfers

We recommend that you set this indicator. It ensures that the system marks every processed entry from table Payment Information (BT) with date and time in order to indicate them for later payment runs as "processed". This prevents entries in table Payment Information from being processed again by accident. When payroll is repeated, after you have performed the preliminary DME program, the system does not overwrite those entries indicated with the date and time, but instead performs a difference calculation. For this reason, you must set the indicator Indicate Transfers if you want to perform qualified advanced payments.

Wage Type

You can use this input field to limit a payment run to a certain wage type, in order for example, to pay wage types created for external transfers (infotype 0011) separately from employee salaries.

Test

When you set this indicator, the system only displays the payments to be performed as a result of the payment run. It does not create any payment data and does not change any data in the payroll results.

Custom Payee Name

You can specify the sources of payee name here. From Available sources, select the sources from infotypes: 0009, 0002, 0182 (subtype 1), 0182 (subtype 2), 0182 (subtype 3), and/or 0440. Also, you can define their priority in Active sources and the upper one has the higher priority.

If you do not specify the sources of payee name here, the payee name by default is retrieved from Bank Details infotype (0009). If there is no payee name maintained in infotype 0009, then system retrieves the name format maintained in Personal Datainfotype (0002).

If you have multiple bank types in infotype 0009 and different payee name types are configured in infotype 0440 for different bank types, you have to maintain feature 27PNM.

Note

The SEPAsection is relevant only for the Finland country version. This section of the selection screen has the following fields:

  • Requested Execution Date: Specify the date on which you want the system to transfer the payment details, relevant for bank transfer to Financial Accounting department. Enter the date in the format dd.mm.yyyy.
Note
Enter the date here only in case of an off-cycle payroll run.
  • Date ID for Requested Execution: Specify the date identifier that indicates the date for transfer of payment details, relevant for bank transfer, to Financial Accounting department. The system reads the date identifier from the Date Identifier(T54C5) table and gets the corresponding date from Period-Related Date Entries(T549S) table.
Note
Enter a value in this field only in case of a regular payroll run.
  • Old Method: Select this option button if you want this report to use the old method to create trade union fee reference numbers. For more information, refer Old method for Reference Number creation.
  • Model Avione and YAP: Select this option button if you want the report to create the trade union reference (TUM) number for SEPA payment file using the Model Avoine and YAP calculation method available. For more information, refer Second Model for Reference Number Calculation.
  • Model Digia: Select this option button if you want the report to create the trade union reference (TUM) number for SEPA payment file using the Model Digia calculation method available. For more information, refer Third Model for Reference Number Calculation.

Standard Variants

Output

The preliminary DME program creates a payment run that contains payment data. You can clearly identify each payment run through the combination of Program run date and Identifiction feature. The Identification feature results from the six-figure system time when you started the preliminary DME program. In the identification feature the system replaces the last character of the six-figure system time with a P.

Example: You started the preliminary DME program on 04.14.2001 at 9.25.12. You can identify the payment run created by the combination of the program run date (14.04.2001) and the identification feature (09251P).

The payment data from a payment run is stored in the following tables:

  • Control Records for the Payment Program (REGUV)
  • Payment Data from the Payment Program (REGUH)
  • Processed Items from the Payment Program (REGUP)

The data in these tables is further processed by the payment medium program in Financial Accounting. You can find further information in the SAP Library. Choose Financials -> Financial Accounting -> Accounts Payable -> FI Accounts Receivable and Accounts Payable -> Payments.






General Material Data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 16936 Date: 20240520 Time: 065952     sap01-206 ( 279 ms )