Skip to Content
Product Information

Central Finance – SD Central Down Payment

Introduction

Central Payment is one of the major central process of Central Finance. However, Central Payment have certain limitation when it came to Down Payment.

With SAP S/4HANA OP 1809 this limitation is getting addressed. S/4HANA OP 1809 introduces Central Down Payment for SD process. For MM, it is planned to be rolled out in S/4HANA OP 1809 FP2.

This blog details the business process for SD Central Down Payment in Central Finance system.

Purpose of Central Down Payment

1. Down Payments are managed centrally in Central Finance system (open item).

2. Down Payments are paid centrally in Central Finance system.

3. The delivery or final billing in SD (source system) needs to know whether the down payment has been made or not.

Pre-Requisites – Functional

1. SAP S/4HANA OP 1809 or higher

2. Central Payment Activated (for specified company code in CF system) (Transaction CFIN_CPAY_CUST)

Pre-Requisite (SAP Notes)

2474760 – SD Down Payment in Central Finance with Central Payment Activation

Source System

2489853 – Enabling Down Payment Integration with SD after Central Payment Activation for Source Systems

2462430 – Anzahlungen im Central payment Szenario

2455550 – Down payment clearing from module SD in a Central Payment scenario (Retrieve Down Payment information from CF system)

2693005 – Central Payment: Error message SG105, exchange rate date missing

CF System

2346233 – Central Payment for SAP Central Finance: Pilot Note for Activation of Central Payment

2693005 – Central Payment: Error message SG105, exchange rate date missing

Business Process

SD Central Down Payment in Central Finance supports;

  • Request-Based and
  • Condition-Based Down Payment

Request-Based:

Down Payment is posted with the reference to Down Payment Request and the corresponding sales order is created with milestone-billing plan item category (‘TAO’)

Steps: (Source)

1. Create Sales Order with Standard Item Category ‘TAO’ with down payment in milestone billing plan (VA01).

2. Post Down Payment Request with reference to the Sales Order (VF01) – DPR is technically cleared (ALE-extern) and replicated in CF system

Steps: (CF System)

1. Confirm source system Down Payment Request replicated in CF system (FB03)

2. Post Customer Down Payment for the Down Payment Request (F-29)

Other Options

  • F110 – Automatic Payment
  • F-28 – Incoming Payments
  • FEBA_BANK_STATEMENT – Bank Statement Postprocess
  • FLB2 – Lockbox
  • FB01 + F-32 – Post down payment and then clear down payment request via F-32

Steps: (Source)

1. Create Outbound Delivery (VL01N)

2. Create Billing Document (VF01) – Receivable item is technically cleared (ALE-extern) and replicated in CF system

The Down Payment document number (from log table FINS_CFIN_SDDPLG in CF system) is retrieved* and filled into Invoice Reference field of the receivable item (via RFC CF_FIN_CFIN_SD_DOWNPAY_PRC and Function Module FINS_CFIN_SD_DOWNPAYMENT_READ).

 

Condition-Based:

Down Payment is posted directly, without the reference to Down Payment Request and the corresponding sales order is created with standard Item category (‘TAN’)

Steps: (Source)

1. Create Sales Order with Standard Item Category ‘TAN’ (VA01)

Condition Type ‘AZWA’ – Cond.DownPaymnt/Plnd and ‘AZWB’ – Cond.DownPaymnt/Clr

Steps: (CF System)

1. Post Customer Down Payment (F-29) – With reference to the sales order retrieved from the source system (via the search help ‘Sales Documents per Logistics Source System’)**

Other Options

  • F-28 – Incoming Payments
  • FLB2 – Lockbox
  • FEBA_BANK_STATEMENT – Bank Statement Postprocess
  • FEBA_CHECK_DEPOSIT – Check Deposit Postprocess
  • FBCJ – Cash Journal (Only for cash receipts)
  • FB01 + F-32 – General Document Entry

Steps: (Source)

1. Create Outbound Delivery (VL01N)

2. Create Billing Document (VF01) – Receivable item is technically cleared (ALE-extern) and replicated in CF system.

The Down Payment document number (from log table FINS_CFIN_SDDPLG in CF system) is retrieved* and filled into Invoice Reference field of the receivable item (via RFC CF_FIN_CFIN_SD_DOWNPAY_PRC and Function Module FINS_CFIN_SD_DOWNPAYMENT_READ)

* Data Retrieved from Central Finance System

Following data is retrieved during SD Billing (Source)

  • Company code
  • Customer
  • G/L account
  • Special G/L indicator
  • Assignment
  • Tax code
  • Business area
  • Profit center

 

** Challenges in Reverse Mapping

1. Mapping Relationship is N:1

If the mapping relationship of these fields is N:1, the reverse mapping cannot retrieve a unique value.

  • Use Report FINS_CFIN_MAP_REL to check the mapping relationship.
  • For Value Mapping, you can use the Default flag to ensure a unique value for the reverse mapping.
  • For additional fields mapping, use the BADIs (Source: BADI_FIN_CFIN_DP_MAP; CF system: BADI_FINS_CFIN_DP_MAP) to extend the reverse mapping which is currently available only for above mentioned eight fields.

2. Mapping is Customized

If MDG (standard solution of CFIN for mapping) is not used for value or key mapping, then reverse mapping may not work by standard.

  • Custom mapping should also take care of reverse mapping.

 

I hope this blog will be helpful in understanding and testing SD Central Down Payment.

2 Comments
You must be Logged on to comment or reply to a post.