SAP ABAP IMG Activity W_WLFA_0010 (Payment Types)

Hierarchy

☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ MM-IV-GF (Application Component) General Functions
     ⤷ MR0C (Package) Customizing R/3 Invoice Verification

IMG Activity

ID	W_WLFA_0010	Payment Types
Transaction Code	S_EBS_44000247	IMG Activity
Created on	19981222
Customizing Attributes	W_WLFA_0010	Payment Types
Customizing Activity	W_WLFA_0010	Payment Types

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	W_WLFA_0010

You can use this menu option to define your payment types that depict the different business transactions involved in processing payments for vendors and customers.

You have the following options:

• You change an existing payment type.
• You copy an existing payment type and change it to suit your requirements.
  

In this menu option, you make or check the following settings:

• Payment Type
• For the payment type, enter an alphanumeric key of up to four characters.
• Give the key a text description to explain what it is.
• Vendor Billing Document Type

  You use the vendor billing document type to assign a billing document type to a specific payment transaction. This makes a payment document uniquely identifiable, for example, as an invoice or as a reversal document.

• Input Type

  Here you define the data your payment document contains. Three different input types are available.

• If you use the Without Logistic Data input type, then only Accounting-related fields are available to you when entering header- and item data. You cannot enter material or quantity information, for example.
• If you use the With Logistics Data input type, you can use functions and data from Purchasing and Sales in processing payments.
• If you use the Material-Related input type, you can also use functions and data from Purchasing and Sales in processing payments. In addition, you must maintain the material on item level and enter a net price or determine a net price in pricing.
This input type differs from the other two in that, analogous to an order or purchase order, the price is entered and the values are determined from the amount entered, instead of entering net or gross values. If a pricing condition with a fixed amount was assigned to the costing sheet, the item is valued with this amount. However, the system always calculates a net price on the basis of quantity information. This means that the net price of the condition is generally not identical to the net price entered. However, the value is reflected in the corresponding pricing condition in the scheme.
• Terms of Payment

  You can create a default value that defines how payment terms are to be determined on the vendor and customer side. If required, choose a setting valid for your business process.

• Settlement Calendar

  You can create a settlement calendar to ensure that the documents entered are due on the same dates and are taken into account in a single payment run.

• Post Taxes

  Set this indicator if you not only want to forward the relevant input and output tax code for the respective debit and credit items to Financial Accounting, but the tax amounts as well.

• Calculation of Cash Discount

  This field is only relevant for the settlement request list. As a settlement request list requires the same cash discount condition for all items, an effective cash discount condition must be determined if the cash discount conditions of the items differ.

• A: Calculation of average due date
In this method, an average due date is determined. In this process, the system determines a date on which the total that was paid too early is exactly the same as the total that was paid too late. The system uses the due documents in the first condition. The payment period in the first payment condition in the header of the settlement request list is subtracted from the average due date. This results in a fixed value date. This is then entered in the header and is valid for the whole document. In addition, a single-step cash discount condition is set.
• B: Interest calculation if payment is too early
In this method, a payment date is specified. This is stored in the Fixed Value Date field of the document header and can be changed. Here, too, as in the case of A, the system determines an average due date. Interest is then calculated for the whole amount in line with the interest calculation method for the period between the payment date (fixed value date + payment period in the header) and the average due date. The cash discount percentage is increased accordingly. The cash discount percentage is entered under "Interest for customers (credit) in Dunning. If the payment date falls after the due date determined, interest is not calculated, but the cash discount rate remains unchanged.
• C: Transfer from settlement request list
In this method, the terms of payment are transferred from the settlement request list header, and the conditions at item level are ignored.
• D: Average due date (conditions from debit-side)
This method is analogous to method A. The difference is that the terms of payment are transferred from the debit side.
• E: Interest calculation for early payment (conditions from debit-side)
This method is analogous to method B. The difference is that the terms of payment are transferred from the debit side.
• X : Customer-defined method
You can enter your own method here.

Business Attributes

ASAP Roadmap ID	204	Establish Functions and Processes
Mandatory / Optional	2	Optional activity
Critical / Non-Critical	2	Non-critical
Country-Dependency	A	Valid for all countries

Assigned Application Components

Documentation Object Class	Documentation Object Name	Current line number	Application Component	Application Component Name
SIMG	W_WLFA_0010	0	ALR0000098	Incoming Invoices

Maintenance Objects

Maintenance object type

C

Customizing Object

Assigned objects
Customizing Object	Object Type	Transaction Code	Sub-object	Do not Summarize	Skip Subset Dialog Box	Description for multiple selections
V_TMZR	V - View	SM30	0000000001	☐	☐	Payment Types

History

Last changed by/on	SAP	20101118
SAP Release Created in