2021-09-21 213526

213526 - Customizing of down payment processing

SD/FI
Version 5 Type SAP Note
Language English Master Language German
Priority Recommendations / Additional Info Category Customizing
Release Status Released for Customer Released On 07.08.2000
Component SD-BIL-IV-DP ( Down Payments )

Please find the original document at https://launchpad.support.sap.com/#/notes/ 213526

Symptom

The Customizing of down payment processing (as of Release 4.0x) is not set
correctly.

Other Terms

OVBP, OVBR, OVBM, OB41, OBC5, OBXR, OB14, OVBO, OVBN, OVBJ, OVV4, OKEP, OBXB,
VOFA, VTFA, V/06, V/08,
AZWR, TAO, copying requirement 20, copying requirement 23, calculation formula
48, pricing requirement 84

Reason and Prerequisites

Useful Customizing settings in down payment processing:

1. No billing plan is created.

2. Customizing of the down payment request

3. In the partial billing document or final invoice in SD, the down payment
is not issued and consequently also not cleared.

4. Settings in the billing plan Customizing

5. Condition and pricing procedure

6. Assign default cost element in CO

Solution

1. If down payment processing should be used in SD, this is only possible

via the functions of the billing plan and only order-related. So that a
billing plan is created on header level, a milestone billing plan type must
be assigned to the order type (Transaction OVBP).On item level, in every
case, an item category must be found which has the billing relevancy I
"Relevant for order-relevant billing - billing plan" (item category TAO is
used in the standard system).If an automatic item category determination is
carried out via the material, the material must have the entry milestone
billing (standard:0005) in the field 'Item category group' (MVKE-MTPOS) in
the SD data 'SalesOrg2'. A milestone billing plan type must be assigned to
the item category with Transaction OVBR (standard: milestone billing plan
type 01).

2. Customizing of the down payment request

© 2021 SAP SE or an SAP affiliate company. All rights reserved 1 of 4

2021-09-21 213526

3. Transaction VOFA: For the down payment request, billing type FAZ
(cancellation billing type FAS) is delivered. This billing type is
identified by billing category 'P'. Consequently, the name of the billing
type and the document type can be customized.

4. In this context it should be mentioned that for a different payer in the

'Branch/Head office' field (XFILKD), a 'B' has to be entered if no head
office has been maintained for the customer in FI.

5. The down payment should be made. The following must also be checked:

a) Transaction VTFA: Copying control must include requirement 023 in

the milestone billing document or final invoice (unlike 021 from the
modification solution in Release 3*).

b) Transaction OB41: for posting key 19 (Special gen. ledger customer),

the field sales order must not be hidden, otherwise no assignment is
carried out (field status maintain ==> additional account assignments,
recommendation: optional entry).

c) Transaction OBC5: A field status variant is assigned to a company

code

d) Transaction OB14:For the field status variant of the company code,

the sales order under the field status group 'Accounts for down
payments received' (G031) under additional account assignment must also
not be hidden (recommendation:optional entry).

e) Transaction OBXR:for the reconciliation accounts of the down

payment, the sales order in the field status variant under additional
account assignments must not be hidden (recommendation: optional
entry).

f) Transaction OBXB:In financial accounting, the automatic posting

transactions for the down payment process must be maintained.

6. Settings in the Customizing of the billing plan:

a) Transaction OVBO: Define billing plan: A milestone billing plan type

which is assigned to the sales document type (optional) or to the item
category (compulsory) must be defined (in the standard system:billing
plan type 01 is assigned to the item category TAO and - if a header
billing plan is used - to the sales document type TA).

b) Transaction OVBN: Define date description for the down payment.

c) Transaction OVBJ:Maintenance of date category for the billing plan

type.

• Corresponding billing rules must be defined for the following date

categories:

• 01 Milestone billing Billing rule 1 or 2

• 03 Down payment request (percent) Billing rule 4

• 04 Down payment request (val.-based) Billing rule 5

d) Transaction OVBM:Maintenance of date proposal for the billing plan

type.

e) Dates can be defined for milestone billing plan types (via the
button Maintain date) and these dates are then proposed in the

© 2021 SAP SE or an SAP affiliate company. All rights reserved 2 of 4

2021-09-21 213526

order.The system does not transfer the original dates but transfers the
dates resulting from the intervals between the dates, beginning with
the current date.

f) Transaction OVBP: Assignment of billing plan type to sales document.

g) This is only required if the header billing plan is used.

h) Transaction OVBR: Assignment of billing plan type and item category.

i) This must always be carried out because otherwise the billing plan
cannot be used.

j) Transaction OVV4: Assign blocking reasons to billing types.

k) If down payments in the order should not be billed immediately, the

blocking reason must be assigned for the down payment billing type
(standard FAZ), otherwise the block is not taken into account.

7. Condition and pricing procedure

a) The down payment condition AZWR is delivered as of Release 4.0A.If

it is missing, you can create it via Transaction V/06 with the
following settings:

• Item condition

• Condition class 'A' Discount or surcharge

• Calculation type 'B' Fixed amount

• Condition type 'e' Down payment request/down payment clearing

• Change options: Value

b) In the pricing procedure, the AZWR must be set as follows (the down
payment condition can also have a different name but it is the
condition type 'e' that is important):

• Insert AZWR after "own" net item value but before the VAT condition

• Set print indicator (old or new procedure can be used)

• Enter requirement 2 (item with pricing)

• Enter calculation formula 48

• If this does not exist, you can create it via Transaction VOFM.

• Task of the calculation formula:

• Value check for a down payment clearing item because the value of AZWR
can be changed manually.If the value of AZWR from the down payment
clearing item exceeds the agreed value in the order, the system
displays an error message (VH 810: "Down payment amount cannot be
higher/lower than the preset value").The billing document cannot be
transferred to Financial Accounting as long as the down payment value
in the order is not increased or is not reduced in the billing
document.

8. Assign default cost element in CO

© 2021 SAP SE or an SAP affiliate company. All rights reserved 3 of 4

2021-09-21 213526

9. If the down payment update is active in the controlling area, a default

cost element and a default revenue element must be maintained for down
payments. This is possible via Transaction OKEP.

10.

Other Components

Component Description

FI-AR-AR-J Integration/Accounting Interface

This document refers to

SAP Note/KBA Title

213444 Advice note, down payment processing SD/FI

113347 Down payment process. as of Release 4.0x (standard)

This document is referenced by

SAP Note/KBA Title

113347 Down payment process. as of Release 4.0x (standard)

213444 Advice note, down payment processing SD/FI

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2021 SAP SE or an SAP affiliate company. All rights reserved 4 of 4