EVENT
This process is part of the procedure for processing the items from oneof the payment groups already formed by the payment program.

INTERFACE
In this interface you can remove individual items from the paymentgroup by indicating that they are not due. These items are not includedin any further processing in the payment run. Payment methods can berestricted further for items due for payment, and the value date at thesender bank can be recalculated.

Description
This item is not yet due and will not be processed further by thepayment program.

Description
Payment methods to be included when further processing paymentrequests.

Value range
There is no limit to the number of payment methods used, but thepayment methods chosen must be selected from those already imported. Ifin the additional component the system determines that none of thepayment methods are allowed, the return code must also be entered. Ifnot, the payment methods from the payment run parameters are used.

Description
This parameter can be used to pass on errors to the payment program,which can then be issued in the form of messages in the additional log.
'0': No errors occurred
'1': No valid table entries (Customizing)
'2': No valid payment method
'3': Unspecified error

Description
Recalculated value date for the sender bank.

Description
Unique key number for a payment request.

Description
Cash discount terms 1

Description
Options for writing the additional log. The additional component canuse these options for issuing messages. The options are set in thepayment run parameters.
Field: xtrfa, additional log for due date
Field: xtrzw, additional log for determining payment method in allcases
Field: xtrze, additional log for determining payment method in case of
error
Field: xtrbl, not applicable

Description
A series of fields, the contents of which must correspond to oneanother so that items can be paid together.

Description
Payment methods remaining after payment run activity up to this pointthat can be used for payment.