Professional Documents
Culture Documents
SD Condition Based Down Payments: Key Process Flow
SD Condition Based Down Payments: Key Process Flow
Introduction:
Often in business, especially in a make-to-order environment, customers may be required to pay some
amount in advance before delivery of goods.
Normally, down payment agreements are made for producing and delivering goods to customers in the
capital goods, or plant engineering and construction industries.
Down payments are payments made before completion of the product, with no interest. They represent
short or medium term outside capital procurement and therefore improve the company’s liquidity
situation.
This process is used to create requests for down payment, record the receipt of the down payment,
create a final invoice after the deduction of the down payment received and a receipt of the final amount
due on the invoice.
The integrated process allows for a proper document flow to be maintained between the sales and
financial transactions.
Down payments form part of the agreement with the customer and are saved in the sales order.
The value of the agreed down payment can either be created as an amount or percentage value of the
item.
Prerequisite:
It must be ensured that the business function SD_01 under
ENTERPRISE_BUSINESS_FUNCTIONS is activated via T-code: SFW5. It’s the technical prerequisite for the
condition-based down payment function.
Getting Started
Customizing – Sales & Distribution
AZWA for debit down payments. AZWA has the calculation type B (fixed amount). It is configured as a
group condition and can be entered for the header or item.
AZWB for billing. AZWB has the calculation type G (formula) and the condition category e (down payment
demand/settlement).
AZDI for rounding differentials balance. AZDI has the calculation type B (fixed amount), the condition
class A (surcharges or discounts), condition type L (generally new when copying) and this condition
cannot be edited manually. It is an item condition.
The condition type AZWR is used for down payment values that have already been provided, but which
have not yet been cleared. This condition type must be included in the relevant pricing procedure before
output tax with condition 2 (item with pricing) and the calculation formula 48 (down payment clearing
value must not be bigger than the item value).
Before applying condition AZWR, create a subtotal with the base value calculation formula 2 (net value).
If condition AZWR is changed manually, you can retrieve information about the original system proposal
from the subtotal.
Configure Reconciliation Account (OBXR) – Assign the field status area G031 for the G/L
accounts Down Payments Received and Down Payments Requested chosen.
Set Accounting Configuration (OBXB) – Configure the posting key for the down payments (ANZ)
and the output tax billing (MVA).
Configure posting Key (OB41) – Sales Order must be set as optional entry for the posting key 19.
Set field status area (OB14) – You must set Sales Order as optional entry for field status
variant 0001, field status group G031.
Assign field status variants to company code (OBC5)
Business Process:
Billing
Conclusion:
Down Payment Clearing – During Final Billing, the accounting document to settles the down-payment
amount per the value in condition type AZWB. In the customer line item report via transaction
code FBL5N select the Cleared items radial button and the Normal items tickbox. Execute the report and
you can see that the customer invoice you created and the normalized transfer posting you made are
now cleared. At this point the SAP customer down payment process is complete!