Purpose
The DME collective bank transfer preliminary program evaluatespayroll results and collects all bank transfers from the BT payrolltable that are labeled as a collective banktransfer.
The program functions in a similar way to the data medium exchangefor single bank transfers preliminary program, except no single banktransfers are created, rather the bank transfer amounts of all selectedpersonnel numbers are added. A bank transfer (collective banktransfer) is written to thepayment data for each:

• Sender (see parameter Determine sender by)


• Recipient key


• Payment method


• Bank transfer wage type.

In addition, a payment list can be created which illustrates whichsingle items make up the collective bank transfers.

Integration
The payment data created by the DME collective bank transferpreliminary program is processed by country-specific payment mediumprograms in Financials to generate payment mediums (DME filesfor the bank). You must start these subsequent programs after the DMEcollective bank transfer preliminary program has evaluated the payrollresults of the employees and generated payment data.

Prerequisites

Complete execution of the report
The DME collective bank transfer preliminary program must bestarted for each payroll period, that is, when starting the report for aparticular period, all collective bank transfers of the previous periodhave already been processed.
If a collective bank transfer is found for a personnel number from theprevious period that has still not be processed, this personnel numberis rejected with an error message.

Advance payment not possible
The DME collective bank transfer preliminary program may only bestarted if payroll for the current period is complete and no changes canbe made in the bank transfer amount of collective bank transfers.

Features

Processing payroll results
All payroll results are read for which retroactive accounting has beenperformed in the current period. If the amount already transferred in aretroactive accounting period differs from the retroactive accountingbank transfer amount, the difference is included in the currentcollective bank transfer.

Summarization of the bank transfer amounts
The bank transfer amounts of the individual personnel numbers are added.A collective bank transfer amounting to the total of the single banktransfers is created for each sender, recipient key, payment method, andbank transfer wage type.
The sender of the bank transfer is determined from the employee(sub-/)personnel area using a feature (see parameter Determinesender by).
The data for the collective bank transfers is written to the paymentpayment data.

Stamping of the BT table
In the update run, the date and time of the program run is written foreach collective bank transfer to the payroll table BT.
A bank transfer highlighted in this way is no longer processed when thereport is started. Exception: Report run (see section Repeat Run)
.

Payment list
The list of single bank transfers that make up a collective banktransfer can be output as a hierarchic list with the ABAP ListViewer(ALV) .
The list is sorted according to sender, recipient, payment method, andbank transfer wage type. A customer-specific variant with sorting andfilter criteria can be provided on the selection screen.

Selection
Normally, only those BT entries are processed that do not have a timestamp (date and time of program run).

Repeat run
To transfer payments again that have already been processed, enter theBT stamp (date and time) of a payment that has been processed in theblock 'repeat run'. The BT stamp of a payment can be found in thepayroll results of the personnel number in the payroll table BT.
A repeat run can be processed in the following ways:


• Clean repeat run

The parameter only records selecte is set. Only the payments thatalready have a BT stamp with the date and time specified are processed.

• Repeat and simultaneous transfer of payments of the balance

If the parameter 'only records selected' is not set, the payments thatdo not have a BT stamp are also selected.
This variant is usually required if after a program termination only asome of the processed BT records are selected, but the run has to berepeated for all BT records (stamped and unstamped).

Standard_variants
A standard variant 01SAP exists for outputting the payment list with theABAP List Viewer (ALV).

Parameter

Other data


• Wage type: Restriction of bank transfer wage types

If only certain bank transfer wage types are to be processed in thecurrent run, enter these wage types.

• Test run

If the parameter is checked, no payment data is generated. The BTentries of the processed personnel numbers are not stamped.
Otherwise, processing takes place as in the update run.

Repeat run
You need these fields if stamped BT entries are to be transferred again(see section Repeat run).

Details about the sender


• Feature for determining the sender

The sender of a collective bank transfer is a personnel (sub-/) area.The sender is output in the payment list.
Enter a feature here with which the sender of the collective banktransfer is determined. This can be the default featureDMECP or anycustomer-specific feature with the same structure. As a rule, thefeature should be maintained in such a way that a summarization into afew personnel (sub-)areas follows.

• Feature for determining sender bank data

With this feature, the bank, account, and paying company code of thesender of the collective bank transfer is determined.
Here, the default featureDTAKT or anycustomer-specific feature with the same structure can be entered.

Output


• Log

With the use of the log switch, a list of the selected BT entries withcollective bank transfers is created for each personnel number. The listcontains all BT entries that meet the selection criteria from the blockAdditional data. Which BT entries should then be processed depend
s on the BT time stamp.
The list is sorted according to period, status indicator (old/new), wagetype, and recipient key.

• Output payment list

The output of the payment list can be eliminated.

• ALV variant

If you have saved your own payment list variant, you can use thisvariant here.

Output
The following lists are created:


• Statistics


• List of the errors that occur when the single bank transfers are
processed

• List of the errors that occur when the collective bank transfers are
processed

• Payment list

Output as hierarchic ALV (ABAP List Viewer).
The list contains for each collective bank transfer the transfer amountsof the individual personnel numbers. In retroactive accounting periods,only the difference of the transfer amount (new amount minus the amountfrom the old payroll results) is displayed.

Procedure in the event of an error

(1) Error list for single bank transfers
This list contains personnel number-related error messages and warningmessages.

Error messages
If an error occurs during the processing of a personnel number, thepersonnel number is rejected. All payments for this personnel numberfrom the payroll table BT are not processed. In the update run, the BTentries of this personnel number are NOT stamped.
The report processing of the next personnel number is continued. Thepayments of the error-free personnel numbers are processed. Thecollective bank transfers created do not contain the bank transferamounts of the personnel numbers with errors.
After the error has been corrected, you can either


• Repeat the entire payment run

Start the report with the date and time details from the BT table of asuccessful personnel number. Do not check the parameter only recordsflagged. Thereby, all personnel numbers (both those processedsuccessfully with BT stamp and those processed with errors without BTstamp) are processed again.

• Perform a separate payment run for the personnel numbers corrected

Start the report again for the same period without data in the block'repeat run'.
Only those personnel numbers are processed that do not have a BT stamp,that is, the personnel numbers with errors from the previous run.

Warning messages
If a warning message appears when the personnel number is beingprocessed, the processing is continued. All payments are processed.
Check the cause of the warning and correct the problem.

(2) Error list for collective bank transfers
This list contains error messages that relate to individual collectivebank transfers.

Error messages
If in the update run an error occurs for a collective bank transfer, allother collective bank transfers are not executed.
Only once all errors have been corrected can the collective banktransfers be transferred to FI.

Warning messages
If a warning message appears for a collective bank transfer, theprocessing of the other (error-free) collective bank transfers iscontinued.
Whether the collective bank transfer with a warning is executed dependson the content of the warning (see long text of the warning message).Check the cause of the warning. It is possible that further manualprocessing will be required.
Example:
If the total amount of all single bank transfers is negative and sotherefore is the collective bank transfer amount, a warning istriggered. If the collective bank transfer is not processed, the amountmust be entered manually with a debit memo from the account of therecipient.
The other bank transfers without a warning are executed.