2. Preliminary Data Medium Exchange (Pre-DME)
Pre-DME is a Payroll process
Pre-DME evaluates payroll results and creates
payment data to be used by Data Medium
Exchange (DME). DME can be counted as
Finance/Accounting process.
Data Medium Exchange (DME) is the process of
sending to the bank the payment data formatted
according to the banking rules of a country. T
3. RPCDTxx0 and RPCDTxx0_CE (e.g. RPCDTCU0 for
USA, RPCDTCK0 for Canada)
RPCDTAG0 for GB/UK
HxxCDTC0 (e.g. HHKCDTC0 for Hong Kong)
4. Pre-DME processes both information from the master
data and information from the payroll results for an
employee.
For every current original pay result, the
preliminary program DME reads the Payment
Information table (BT) in the payroll results.
5. Information on the payment
recipient
Sender Account Number
Purpose field in table (BT)
Payment currency
Consistency Check
Set Flag for Transfers
Output
The system determines the information on the
payment recipient
•From the entry in the Payment Information table
(BT)
•From the Payee Keys table (T521B), if the entry in
the Payment Information table (BT) contains a
recipient key
•From the Personal Data (0002) and Addresses
(0006) infotypes, if the entry in the Payment
Information table (BT) does not contain a recipient
key and does not contain any recipient data
6. Information on the payment
recipient
Sender Account Number
Purpose field in table (BT)
Payment currency
Consistency Check
Set Flag for Transfers
Output
The system evaluates the Sender Account Number
for Data Medium Exchange feature (DTAKT) to
determine the following information:
•The paying company code
•The house bank
•The house bank account
7. Information on the payment
recipient
Sender Account Number
Purpose field in table (BT)
Payment currency
Consistency Check
Set Flag for Transfers
Output
The system reads the Purpose field in the Payment
Information table (BT):
•If the Purpose field is filled, the contents of the field
are transferred to the payment data
•If the Purpose field is not filled, the following text is
used: "Wage/Salary", <Personnel Number>, <Payroll
Period> or "Pension", <Personnel Number>, <Payroll
Period>.
8. Information on the payment
recipient
Sender Account Number
Purpose field in table (BT)
Payment currency
Consistency Check
Set Flag for Transfers
Output
The system determines the payment currency:
•If the Currency field in the Payment Information
table (BT) contains a currency, this currency is used
for the payment.
•If the Currency field in the Payment Information
table (BT) does not contain a currency, the currency
from the Currency field in the Payroll Status
Information table (VERSC) is used for the payment.
9. Information on the payment
recipient
Sender Account Number
Purpose field in table (BT)
Payment currency
Consistency Check
Set Flag for Transfers
Output
•The system reads the bank codes of the house
bank and the recipient bank from the Bank Master
Record table (BNKA).
•The system checks the payment data for
consistency. If a payment with inconsistent data
exists for an employee, the system does not perform
a payment for this employee.
•For every entry in the Payment Information table
(BT) the system creates an entry in the payment
data.
10. Information on the payment
recipient
Sender Account Number
Purpose field in table (BT)
Payment currency
Consistency Check
Set Flag for Transfers
Output
It is recommended to mark this indicator as it causes
the system to mark every processed entry in the
Payment Information table (BT) with date and time,
to indicate "processed".
This prevents processing more than once
accidentally.
If the payroll run is repeated after you have executed
the preliminary program DME, the system does not
overwrite the entries marked with date and time but
performs a difference calculation. It should be
mark the Set Flag for Transfers indicator to
perform a qualified advance payment.
11. Information on the payment
recipient
Sender Account Number
Purpose field in table (BT)
Payment currency
Consistency Check
Set Flag for Transfers
Output
The preliminary program DME creates a payment
run that contains payment data.
Every payment run has combination of the Program
Run Date and Identification Feature.
The Identification Feature originates from the six-
digit system time of Pre-DME report start run. The
system replaces the last digit of the six digit system
time in the Identification Feature with a P.
The payment data contained in a payment run is
saved in the following tables:
•Control Records for the Payment Program (REGUV)
•Settlement Data from Payment Program (REGUH)
•Processed Items from Payment Program (REGUP)
The data in these tables is further processed by the
payment medium programs in Finance/Accounting
and is usually run via RFFOUS_x reports.
Payment Medium File Table (PAYR)
14. If you make the decision by BANKL in feature DTAKT, than you have
to assign a valid housebank and housebankaccount for the
"otherwise" case. It is important, that the feature returns a valid
housebank and housebankaccount for otherwise case.
Because of technical reasons, the PRE-DME program evaluates the
feature DTAKT twice for each payment. When evaluating feature
DTAKT the first time, the fields BANKL and BANKS aren't yet filled.
However they are filled with the values of the corresponding fields of
table BT second time.
Do not forget to check the customizing of tables T012.,
T012K, BNKA and feature DTAKT.
