Down payment processed by F110 is blocked

We would like to make a down payment on a purchase order. I entered the payment request with transaction F-47 and the special G/L sign. Then i run the automatic payment program F110 and the item gets paid. The payment program generates a posting with a debit on the vendor and a credit on the sub-bank account. However, the vendor item gets automatically blocked for payment. Therefore, when the invoice is posted, the advance payment will not be automatically deducted.
does someone know why this advance payment gets a payment block and how we can avoid having this payment block?
Thanks and regards,
marlies

Hi,
Clear the down-payment made against invoice through T-Code : F-54 before final invoice payment. When you clear the DP against invoice It will transfer the advance (DP) from special GL to normal GL and clear the payment block.
Down-payment flow :
F-47 : For downpayment request.Noted item. No FI entry
F-48 : For down payment to vendor. As per down-payment request we have to pay DP and without request also we can pay the advance.
F110 : APP
FB60 : Invoice
F-54 : Transfer of Advance from special G/L to Normal by clearing special G/L Items
F110 : Final payment
Regards
Sanjay J

Similar Messages

Down payment process

Hi guru's,
I am working on a downpayment process, where i created a material as per down payment process and changed required custom settings as per milestone billing process. as of business requirement 40% percent need to get advance from customer otherwise billing will not happened,
How can i enter this 40% amount in my sandbox where am creating dummy sales order cycle to test how the plan will work,
I finished till deliver , but i need bill that document , i have to show the amount where it received as advance , how can post that money received.
Please advice me.
thanks & regards
chandra sheker c

hi,
http://help.sap.com/saphelp_470/helpdata/en/14/c8af5ad21411d2acc70000e8a5bd28/frameset.htm
http://help.sap.com/saphelp_470/helpdata/en/01/a9c74e455711d182b40000e829fbfe/frameset.htm
The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
KAPIL

Down payment process for Poland, new business process or not ?

Hello,
I'm a little bit confused about implementation down payment process for Poland.
The OSS-notes 818079 and 1007635 describe a solution for this.
How do I have to implement the correct down payment process for Poland ? Do I have to create an extra business process with new sales order type, new billing type, separate calculation procedure, new output type and so on ?
Or is it possible to use existing business processes in sales and distribution for down payment processes ?
Thanks in advance
Holger

hi,
Check the process for down payment processing
The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
chandu

Down Payment Processing in Milestone billing

I have created sales order that does milestone billing. The down payment is 10 % of amount - Billing type FAZ and condition type AZWR is included in Pricing Procedure and ERL is asigned.
I also have done all the required settings from the help file at:
http://help.sap.com/saphelp_47x200/helpdata/en/4a/ac853478616434e10000009b38f83b/frameset.htm.
But the sales order still says G/L account not found and not saving. Is the G/L account need to found at sales order itself ? If so, where in sales oredr type I have to assigne account determination like KOFI00 etc ? Can any explain this ?
Does the down payment in sales order do the account determination to find G/L account as in case of regeualr billing docs ?

The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
By useing tcode---> VKOA assing the G/L accounts for account deteramination

Down payment processing

Hi Friends,
Could somebody throw light on as how Down payment process is carried out in general. Provide flow for the same.
Thanks

The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)

Down Payment processing for Sales orders using Milestone Billing Plan

Hi,
The business scenario is as follows.
The delivery for the sales orders are to be created only after the pre payment( a percentage of the total sales order value) is made by the customer.
Hence the sales orders while creation are blocked for delivery creation using credit block by means of a userexit.
The credit manager checks the blocked sales orders using VKM1 transaction and verify if there are any payments made by the customer to cover this pre payment to be made.
If it is enough to cover then he releases the sales order manually for delivery creation.This is a complex process since there are too many sales orders and the payments made by the customer may not match the amount to be paid(it can be greater or lesser).The customer just pays a huge amount which is to be distributed among the sales orders for pre payments.
Later, when the invoice is created, the customer account is cleared manually using F-32 transaction for the oldest open invoices.
Here again there is a huge manual effort involved since he need to distribute the amount against the invoices using oldest open item principle.
As a solution we are planning to implement "Down Payment processing for Sales orders using Milestone Billing Plan".
Is this the right solution?
Can you please give the steps in detail to implement this functionality for above scenario?
We are using SAP 4.7 version without Project Systems.
Thanks in advance.
Regards,
Ragesh

Hi Ragesh
Check the links where you will get the entire down-payment configuration
[https://forums.sdn.sap.com/post!replydownpayments ]
Regards
Srinath

Down payment process - merge for FI

Hi everyone,
I have recently setup the downpayment process in SD (ECC 6.0).
It works fine but I have question regarding the SD/FI integration.
I'm creating a sales order for about more than one item, e.g. 10 items. Then we create the down payment request on the basis of the sales order.
SAP creates the FI document also with 10 items and so every single item is displayed in the list of items (FBL5N).
Later we create the invoice after the customer has payed the down payment.
The invoice contains all items, but in the FI document there is only one single item posted.
I'm wondering how we can customize the system that in the FI document for the down payment request SAP merges all items to one single item.
If we create sales order with a lot of items ( > 50 ) it will become confusing for the user in the FBL5n (list of items customer).
Any ideas or experience?
Thank you.
Juergen

You can refer OSS Note 213852 - Analysis of down payment processing with FI and Note 213526 - Customizing of down payment processing SD/FI for details.
Regards,

ACH Payment Process in F110 Program

Hi SAP folks,
I am having a small issue with ACH payment process through F110 Program.
I am using Payment program RFFOUS_T for a payment method " A" for ACH and all variant and other configuration is perfect.
When I execute F110 program, it create DME file for me and let's say I clear one vendor with one invoice only then in DME file I can see record 1, 5, 6, 7, 8, and 9 and file is 100% good to transfer to bank.
Now If I have two Invoice for same vendor and I execute the same process, record 7 with is Addendum record disappears and I will have only 1, 5, 6, 8 and 9.
Our requirement is that let's say we need to pay multiple almost 100 invoices per vendor and we would like to have records 1, 5, 6 and 100 7 records which contains all vendor invoice information and 8 & 9.
I am using CCD format but i guess with program RFFOUS_T it doesn't matter too much.
Has anybody face this issue before ? I have spent hell of the time on this issue but haven't resolved this. I would greatly appreciate your response on this.
Thanks
Perry
Message was edited by: Perry Oza

Hi Perry
I think this problem is because of all the payment is grouped as one payment. You need to make a separate payment for each vendor line items so that you get record 7 as many times as the number of vendor open items.
In FBZP, payment method in company code, there is an option where you can select SINGLE PAYMENT FOR MARKED ITEMS and also you need to give the payment method in each of the line items.
Hopethis helps. We had the same requirement and we getting the expected result
Thanks
Ashok
Assign pointsfor useful answer

EHP 6.0 PO Vendor Down payment process

Hi All ,
our client updated , EHP 6.0 , i have one query , one function updated "LOG_ MMFI _P2P" added new tab po header level payment processing , i want to how we can do po down payment process, how we can create vendor down payment header level or item level , what is uses of TCODE me2dp. Please explain me all this process above function updated "LOG_ MMFI _P2P". previous they are using Normal process now they want to use new process which is updated in EHP6.0 . Let me new process. & how create dp po item level or header level.????
previous they are using below process .
1) ME21N PO create
2) f-47 dp request
3) f-48 dp pay
4)f-54 dp clr
5)f-53 final pay
6) F-44 vendor clear
Thanks & Regards
Jay

Hello Jay,
Kindly follow the below link
http://www.slideshare.net/subhrajyotibhattacharjee7/vendor-downpayment-process-mapping-with-new-ehp4-enhanced-functionality
I think the above will clear your requirement.
Regards,
Vinayak

Customer Down Payment Process

Hi,
Please guide me in the customer down payment process.
I have made a 10000 as down payment to our customer in F-29.
After that i created Customer invoice using F-22.
After that i paid invoice amount thrugh f-39 with the clearing of down paymet.
Now my down payment was fullly utilized and inovice was also paid.
If i see in FBL5N the customer balance zero.
why should i again do the transaction in F-32.
Please guide me
Sateesh

Hi Sateesh,
in f-32 you will clear the open items.
the process will be like this.
1.fist u got the downpayment..so u will post at f-29
system will creat a customer open item here.
2.then u will rise the Customer invoice at f-22
3.then you have to clear the down payment at f-39.
4.then you have to clear the customer open item at f-32.
here you will clear the Customer open item where u have in step 1.
now chekc the balence.
thanks.

Down Payment Processing on the Basis: Document Condition

Hi all,
since Enhancement Pack 2 there is a new possibility of down payment process. The new process is not depending on billing plan instead depending on Document conditions.
With this you can also have the the final invoice delivery related. In the order you have just a new header condition AZWA (debit down payments).
Is there also a possibility to create for this new downpayment process a down payment request with financal bookings (similar to billing type FAZ) ?? The documentation doesn't give any information about this in the new downpayment process.?
Any experience would be nice??
Regards,
Norbert
Documentation for new downpayment process depending on document condition
http://help.sap.com/erp2005_ehp_03/helpdata/EN/ce/b7790d32554ae2abb5d2c4aa4e45d1/frameset.htm

Dear All,
Can anybody write me detailed customizing values for AZWA and AZWB condition types?
Online help is incomplete (e.g. condition class is missing, etc.) and system didn't add automatically these new condition types after business function activation.
Thanks.
Ferenc

Down payment processing error

Hi,
I am facing problems in down payment processing (ECC6.0) with and without billing plan.
What I understand about the normal flow of down payment, once order is saved then down payment request FAZ is billed with reference to the order & it should reflect on the next invoices. Is it the correct flow?
In case of down payment without billing plan, while create billing type FAZ , it gives me message item category TAD can not be billed with billing type FAZ. i am using a dien material.
Even in case of mile stone billing I am getting message only billin rule 4 or 5 can be used. So where do we assign billing rule to billing plan?
I need your valuable input. I am working on ides ecc6.0.
Regards
Suman

Hi,
the message you get is quite easy to explain: you are using doc.type DZ (should be the default doc type for transaction F-29), but you are entering a vendor line item. This is definitely a problem as doc. type DZ usually does not allow vendor lines in the document, you can check it in transaction OBA7.
Another funny thing is you are saying that you want to enter a down payment received from a customer - so why do you have a vendor line in your document? I think this is the main problem, you are just using a wrong account type. Use the customer account you have entered for the down payment request earlier.
If for seom very strange reasons, you still want to use a vendor line in the customer down payment document, then you have to use another document type that allows customer, vendor and also G/L accounts (check OBA7). However, if you are working with document splitting, you should be careful when picking a document type.
Hope that helps, points welcome
Csaba

Down Payment Process - Make Payment on Sales Order

Hi experts
We are looking at implementing the down payment process.
We should be able to record a down payment whilst creating the sales order. However, whilst in the Sales Order, the Payment Means icon is not available (greyed out). I have checked the document settings for Sales Orders etc but cannot find a way to make the Payment Means available to be used.
Any ideas?
Any help appreciated.
Regards
Lorna

Hi Lorna,
the functionality to create a payment from the sales order is not available in all localisations.
To implement the DP process, you can work with either DP Request or DP invoice, depending on when you want to be tax liable. Please have a look at the documentation in the DRC.
All the best,
Kerstin

Down payment process on basis of document conditions

I am trying to setup the down payment process that uses document conditions (available since EH2) and I'm struggling with it. I can't get any values to show in condition type AZWB. I'm wondering if anyone has any experience with this process and can suggest what I might be doing wrong. I found a link to a SAP best practice guide and setup the condition types and pricing procedure per the guide
[http://help.sap.com/bp_retail603/BBLibrary/Documentation/732_BB_ConfigGuide_EN_US.doc]
I entered a value for condition AZWA in the sales order (tried both a header value and a line item value). I then made a down payment for that amount using t-code (F-29). In F-29 I entered the special G/L indicator = A and I referenced the sales order (tried with and without a line item). When I tried to create the invoice for this item I was expecting AZWB to be populated, but instead it has zero in it. I tried working through the debugger for calc routine 49, but got lost halfway through it. However, it did look like it found a value in BSEG for the down payment amount at some point. Can anyone suggest what I might be doing wrong or what else I can look at to help analyze what's going on.
Thanks

Hi,
We are also in process to implement condition-based down paymnet but when we try to enter a down payment with F-29 and referenced the sales order number, the system gave error message u201CMessage no. V1125 - Enter the item numberu201D so we were forced to enter the payment at the line item level.
How did you able to do F-29 at the header level ?
Is there special config we are missing ?
Thanks,
Avishay

Customer Down Payment Process Russia

Hi,
We are currently in the process of implementing our Russian subsidiary into SAP ECC 6.0. In this process we are struggeling to find the correct setup for a specific business process:
For a lot of our customers we are requesting prepayment. We want to handle this in SAP via the down payment process (as in Russia VAT needs to be paid on down payments). So steps are:
We create down payment request for a specific amount.
Customer does down payment + down payment is posted in SAP.
Customer places an order.
We deliver the product and issue invoice (invoice needs link to down payment against which the invoice will be cleared).
Down payment needs to be cleared.
The part we are struggling with is that the down payment the customer does is not for a specific order. It is a lump sum amount which could cover 1 or more futur orders. So for instance down payment can be cleared partially with 1 invoice or serveral invoices can clear 1 down payment.
Question is: How can we handle this correctly in the system? How can we link the down payment to the customer invoice (there needs to be a reference of the down payment in the customer invoice)?

The customer invoice will not be in FI but will be triggered from SD. Russian requirement is that the down payment against which the invoice will be cleared needs to be printed on the invoice.
Also, this seems a lot of manual work (manually transfer the dow payment F-39, manually clear the invoice with transferred down payment F-32, at the end also manually clear the original down payment with the down payment transfers F-32).
If there are only a limited number of such customers this is feasible, but if there are a lot then it becomes cumbersum).
One way of doing it more efficient, I thought, was to manually clear the invoice directly with the down payment via F-32. You can then post the open difference for the down payment surplus again as a down payment. But again this only works manually. I think there is no way to do this automatically (clear invoice with down payment based on amount and against latest down payment + post difference to down payment reconciliation account). I tried via transaction J3RCALD, but this does not seem to work.

Down payment processed by F110 is blocked

Similar Messages

Maybe you are looking for