Show TOC

 Payment Specifications

Use

You can summarize receivables that a business partner is to pay with one payment, using a specific payment method, and specific bank details, and receivables that you want to pay to a business partner into payment specifications for automatic processing in the payment program and processing in payment lots.

Integration

In the document display, the payment data shows that a line item has been included in a payment specification. Navigation to the payment specification is supported.

For the display in the account balance, you can include the field PDTYP ( Category of Payment Specification ) in the line layout. You can also display the field IPAYD where an icon indicates whether an item is assigned to a payment specification or not.

Features

With the transaction Payment Specification for Payment Run , you can group open items and at this level, define payment data such as payment method, bank data, and DME data. The payment program processes this data for payment (payment specification of category Payment Program ).

You can also only group items using the transaction Payment Specification for Payment Lot (for example, without specification of payment data such as payment method, bank data) and use the payment specification thus created as selection criteria for the processing of incoming payments (payment specification of category Valid for Payment Lot ).

The system saves this payment data at header level and the related items at item level in the object payment specification.

You can include items from different business partners and contract accounts in one payment specification. In the payment specification you must always specify the paying business partner and (if the specification is for the payment run) the paying contract account. You can use the function for incoming payments, outgoing payments, and in principle, for all payment methods. In the related line items, only the category of the payment specification (field DFKKOP-PDTYP) is set. The payment data entered (for example, payment method) is not entered in the line item.

When you create a payment specification, the same authorization checks that apply to the document change function apply (company code, business area, and authorization group of contract account). Using the authorization object F_KKINDPAY, the system checks, dependent on the category of the payment specification and the activity, whether a user has the required authorization.

Activities

When you create/change a payment specification for the payment run, you can select either all items or only preselected items. You define the default for each user in the user parameter 8PAY_XITMS (A = all items, R = only preselected items).

You define screen variants for payment specifications in the Implementation Guide for Contract Accounts Receivable and Payable , under Start of the navigation path Business Transactions Next navigation step Payments Next navigation step Incoming/Outgoing Payment Creation. End of the navigation path You define the default user-specific in the user parameter 8IP.

If you define event 0606, when you post the document you can define for each business partner item that a specification is required for the item. This means that the payment run does not pay this item until a payment specification has been created for it. Items of this category are preselected items.

If you define event 0616, on the initial screen of the transactions for creating a payment specification (and in the dialog box for subsequent selection of additional items), you can define additional selection criteria. This means that from the list of selected items, you can display only certain items (filter function) by evaluating your selection entries in the module specified here.

At event 0609 you can visualize customer-specific fields that you have defined in header table DFKKIP_GRP using a CI include in the creation, display, and change transactions. Your own fields are then displayed on a separate tab page.