Down payment condition type (azwr)
Hi guys,
Can you please help me how to configure AZWR (down payment) condition types. how we can raise milestone billing. please let me know.
Hi,
Pls go through the following path:
SPRO>Sales and Distribution>Pricing-->Define and assign pricing procedures.
Assign document pricing procedures to billing types.Check the document pricing procedure assigned for your document type.
Next goto "Define Pricing Procedure Determination".
Check the pricing procedure.
Goto "Maintain pricing procedures".
Select that pricing procedure.
Click on "Control data".
Before this make sure that this condiiton type is defined using "V/06" T.Code.
Add your condition type here in this pricing procedure.
Save the entry.
If you check this in your document,it will be appeared.
Coming to billing of "milestone billing" of billing paln item,just bill each item one by one in the billing plan item.
Goto Order item details.Goto Billing plan.
Maintain the billing block for other items except the one for which you want to bill.
Bill that item using VF01 T.Code.
Regards,
Krishna.
Similar Messages
-
Hello Gurus,
The special condition type AZWR is used for down payment items in sales documents, rather than the
usual condition type PR00. When condition type AZWR is determined, all the other condition types are
set to inactive.
my question is:
(1) When condition type AZWR is determined, all the other condition types are set to inactive. how about there are discount or tax condition for this downpament ?
thanks very much!As soon as the billing date (in the billing plan) for the down payment has been reached, the system creates a down payment invoice and sends it to the customer. Billing type FAZ is used for creating
the down payment request.
Tax is determined when the down payment request is created.
No discount is calculated as condition type AZWR sets all other conditon types to inactive. -
Condition Type AZWR for Down Payments
Hi All,
I am Working on Down Paymnet Requests (Billing Type FAZ). As per the OSS note i understand that we need AZWR Conditon type for Down Paymnet.
I understand that it is for 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
Can you any body explain this more in detail.Thanks
Regards
BashaHi Basha,
Please refer to note 213567:
8. Messages in the FI/CO interface
a) VF525: "Total of down payment to be billed too high."
VF050: "Document & saved (no accounting document generated)"
In the standard system, you cannot perform a clearing of down
payment items with a total that is higher than the value of the
corresponding item to be settled from the partial or final
invoice.A billing document is created, but it cannot be
transferred to Financial Accounting because sending credit memos
to customers as part of down payments is not supported.However,
you do have the option to adjust the value of the down payment
clearing item (condition AZWR) according to the item to be
settled when you create the invoice.In this case, the remainder
of the down payment assigned to this item is proposed again for
clearing in the next partial or final invoice.
According to note 213526 we would use in standard the downpayment
condition AZWR for this process. This condition type could be changed
manually in the invoice. We could reduce the downpayment values
manually and message VF 525 would not appear again, when the downpayment
values would be lower or equal to the main item.
I hope this is helpful.
Regards,
Alex -
when i can ssigned AZWR condition type to pricing procedure, but in sales order how down payment amount will trigger in sales order so please help me
Did you check this thread.....
down payment condition type (azwr)
Thanks,
Raja -
Sales Order with Partial and down payment (milestone billing)
Hello Experts,
I have configured a scenario where a down payment and a partial payment and a closing invoice is done on the billing plan for a sales order. The down payment request was done and posted manually in FI and the process went well. The issue i have is that the down payment is not reflected in my partial invoice or my second invoice and my closing invoice as well is not reflecting the payment made for the partial invoice (which is suppose to contain the amount less the down payment).
Please, how do i resolve this issue?
Thanks.Hi,
See from what i feel from your description is, the business process is as follows:-
1) You receive the down payment request, this goes to a special g/l with indicator "F". Now when you recieve the payment you subsequently clear the amount through T-code F-29. In this case the down payment amount or the advance is treated as a deposit, which you adjust against each partial invoice, or completion of certain project.
2)When you create a partial invoice, considering the example in my earlier post you book complete value of the invoice i.e. RS 800.
The client requires that RS 720 and Rs 80 should goto seprate g/l accounts. IN this case you need to define a condition type say "zadv" assign a new account key to it say "zad" in SPRO>SALES AND DISTRIBUTION>BASIC FUNCTIONS>ACCOUNT ASSIGNMENT/COSTING>REVENUE ACCOUNT DETERMINATION>DEFINE AND ASSIGN ACCOUNT KEYS.After billing of the correspoding amount I.e RS 80 will be cleared through F-39. Please check the same with you FI consultant.
3)Since the condition tab page is greyed out , SPRO>SALES AND DISTRIBUTION>BASIC FUNCTIONS>PRICING>PRICING CONTROL>DEFINE AND ASSIGN PRICING PROCEDURE>ASSIGN PRICING PROCEDURE TO BILLING TYPES. Also check in tcode VOFA wether oc. pric. procedure si assigned or not.After doing this you can add teh condition type "ZADV".
also you can refer to this link down payment condition type (azwr)
Regards
Aadesh Kamat
Edited by: aadesh123 on Jul 14, 2011 6:41 AM -
Condition type for Retension Money and Down Payment in construction co.
Dear Friends,
In construction co they are using advance payment and retension money from the customer. what condition type I should use for Retension money and for Advance payemnt can I used AZWR (Down Payment condition type).
Kindly help me
Regards
Atul.Hi Sridhar,
For sure, down payment is a balance sheet item, but you can get it as "expense" under value type 12 in CO.
So in case you have a purchase order, you will get in CO the cost element which is in the purchase order (and in Fi the account for down payment). In case you don't have a purchase order, the down payment will be register in CO under the cost element you enter in OKEP (and in Fi the account for down payment).
As far as I now, you don't get the down payment on cost center, only on internal oder, WBSelement ...
But is there a way to not get the down payment at all in CO (including internal order and WBSelement) ?
Regards.
Benjamin -
Hi,
I would really appreciate it if someone could shed some light on the AZWR condition type. I have the following queries -
1) When the condition type AZWR is included in a pricing procedure, which account key should be assigned to it ?
2) Should AZWR be included in the pricing procedure that is determined for the downpayment request document (FAZ) ?
3) When AZWR is included the pricing procedure which is determined for the subsequent billing documents, what should be the sequence of the condition types in this pricing procedure including AZWR?
4) What role does AZWR play during the downpayment posting and clearing cycles (Tcodes - F-29 and F-39) ?
I would be most grateful if the above could be illustrated with examples.
Sri.Hiya
Its a down payment condition type and to set it the following Customizing settings have to be made:
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)
Regards -
Down payments added to the net value
Hello Experts,
I have configured downpaymants as per my client requirement . I have entered manually the down payment condition type in the sales order but the down payment value has added to the net value. Is it standard system behaviour or please explain how the down payments behave while creating the sales order.
Thanks in advance.
Thanks,
K
Edited by: kv on Jun 2, 2010 11:43 AMHi Folk,
Can you make the condition type as negative sign and test it again.
Regards,
Ram. -
Down payments configuration and condition AZWR value 0.
Hi,
I am trying to configure the standard down payments but I have the following questions:
1º ) I have configured the condition type AZWR with all the requirements from the manual, condition 2 and the calculation formula 48 but I donu2019t know which position in the pricing procedure has to be located the condition AZWR. It read something that has to be located just before the Tax Condition, my question is that the only requirement. Donu2019t you have any example of one pricing procedure? Because there isnu2019t anyone standard to check in the system.
2º) I have set the billing plan with the billings documents for example 40% FAZ 20% FAZ and 40% F2 however the condition type AZWR in the pricing procedure still with value 0. It doesnu2019t seem the right situation. It should have the value of invoices FAZ.
3º) I bill the first invoice FAZ and the condition AZWR doesnu2019t appear in the invoice due it is value 0 in the sales order I suppose so.
4º) It is possible to assign 40% of the one invoice FAZ to one invoice F2 and the rest 60% to other F2. If I can configure correctly the condition types and the pricing procedures.
Thank you in advance.
Best regards.
Edited by: ALBERTO MARTIN on Oct 19, 2009 11:45 AMHi Gabriel,
Please refer this link
http://help.sap.com/bp_bblibrary/600/BBLibrary_Start.htm
and search for building block E10: Configuration of down payment. Here I can not attach file.
Regards,
Mukul -
Down Payment FAZ Document Posting using AZWR
For configuration of Downpayment for Milestone Billing. We have made
use of Condition Type 'AZWR'. This works fine as long as it is above
the VAT (TAX) Condition Type in the Pricing Procedure. The invoicing
Process in SAP involves Milestone billing with - 10% Advance Amount
(Downpayment) and rest Pro-Rata (%age wise) billing.
In case of Invoicing against a Material, VAT Condition Type is picked
up and AZWR has been configured just above the VAT (TAX) condition type
in the pricing procedure. This works fine when we create FAZ request
through Milestone Billing and the subsequent request in then posted
through F-29.
But with Billing against a Service there are three tax condition types
viz. for SERVICE TAX, for EDU.CESS and for HIGHER EDU.CESS. In this
case too we have configured AZWR just above the three tax condition
types. Now, while creating a FAZ downpayment request. The system picks
up the Tax Amount only for the last tax condition type i.e. (HIGHER
EDU.CESS) in this case. Thus, for example if for the contract value of
Rs.1000. We have 10% as advance, thus, we have - 90.66 as net value and
Rs.9.34 (9.07 as ST + 0.18 as Edu Cess + 0.09 Higher EDU.Cess)as Tax
in the FAZ Request.
The accounting document generated upon saving shows only 90.66 as Net
Value + 0.09 as Tax with the relevant tax code for Higher Edu. Cess
Condition. The rest of the tax conditions are not picked up. Because of
this, during F-29 posting only 1 line item of Tax Amount Rs.0.09 is
picked up with the relevant tax-code, and rest of the taxes are not. We
need all the tax conditions to be posted during FAZ so that the due
ADVANCE AMOUNT IS POSTED.hi Imran
1. Did AZWR is remain statistical or required some GL.?
now this condition type is just for a request for a down payment so there is no reqd for a GL...coz i am doing the same thing here...but as
if now i still face issues on this also and in the billing FAZ type you could see tat the condition base value is shown as the down payment
like as the item billing plan tab page for the down payments...like for eg 10% of the net value ...
2. I take the down payment with FAZ type and post the incoming payment, than how can I post the actual billing (F2)??
well in this is true i do also have the same issue ...f-39 take the downpayments in but does not reflect . but to that i waud also like to
add this if you go to the sales order billing plan tab page of the item and there you got to choose the final invice, just like the downpayments is shown ...then the billing amount will come ...just try it and in the VF01 it will appear as billing FAZ with the downpayment
amount and the F2 also ....but the F2 is delivery related so i think you got to do PGI after the downpayments process then do f2...
if you get more info on that please explian
3. There is no update after the down payment agains the condition type AZWR, did it will manually entered, or what is the bahavior of this.
sorry i hav no info on this
5. Should I create a different pricing procedure with AZWR or what ????
not reqd. coz in the existing pricing procedure you need to have a subtotal after that AZWR
IT WUD BE REALLY KIND OF YOU TO SHARE ANY NEW UPDATES PLEASE
REGARDS -
Down payment no final invoice (F2)
Dear experts
I have configured the system for down payment. I have followed the steps defined for this configuration, i.e:
1) Billing plan. Data related:
a) Material with item category group 0005 (milestone billing).
b) Billing plan type: 01 (Milestone Billing)
c) Date category: 03 (Down payment request -proc.)
d) Date proposal
2) Pricing Procedure:
a) Subtotal with the base value calculation formula 2 (net value) before the condition AZWR.
b) Condition Type AZWR
i) Calculation type B (fixed amount)
ii) Condition category e (down payment request / clearing).
iii) Included before output tax.
iv) Condition 2 (item with pricing)
v) Calculation formula 48
vi) Printing indicator
3) Sales document: TA
4) Sales document position TAO
5) Billing Document
a) Billing type FAZ (down payment request)
b) Billing type FAS for canceling.
c) Billing category P of the billing type.
d) Blocking reason 02 (complete confirmation missing) ->assign it to billing type FAZ.
6) Copying control
a) From TA FAZ. Copying requirement 20 entered at item level (item category TAO).
b) From TA F2. Copying requirement 23 entered at item level (item category TAO).
7) Financial Accounting settings
a) Field status definition G031 assigned to reconciliation accounts - For the `received DP' and `DP requests'.
b) Posting key for DP (ANZ) and for output tax clearing (MVA)
c) G/L account number assignment for the tax account.
d) For posting key 19, set Sales Order as an optional field (OB41).
e) For field status variant 0001, field status group G031, set the sales order as an optional field.
f) Assign the company code to the field status variants (transaction OBC5)
After that to create the DP I have done the following flow:
1. Create sales order (VA01) with a DP set throught a billing plan
2. Create an invoice (VF01) for DP request
3. Collect the down payment related (f-29)
4. Clearing the DP (f-39)
And this should ends with the creation of a final invoice (throught VF01, invoice type F2). However, when I try, the sales orders doesn't have any invoice outstanding to be created and condition AZWR is no updated. Therefore I cannot create the final invoice.
Is there any customizing or step in the process that I have missed??Dear Arijeet
Thanks for your answer.
I have made a new test not doing F-39 before the invoicing. I.e.:
1) VA01 sales order
2) VF01 invoice FAZ
3) F-29 collect DP
4) VF01 invoice F2 -not working
So I have got the same result: no data to be invoiced at all from the original order
I'll appreciate any other suggestion
Kind regards
B -
Hi,
I have created a down payment. It was ok, I have made the followign steps:
1. Create the downpayment using a millestone billing plan in the SD order
2. Create the down payment request in SD (VF01)
3. Posting the down payment request (VF01)
4. Collect the downpayment (F-39)
However when I have try to make the final invoice, no value have been substracted from the total invoice value (the down payment previously made have to be substracted). Why the downpayment quantity is not substracted in the final invoice?
I appreciate any suggestion
Thanks in advance
NOTE: I have made the down payment customizing:
1 Billing plan.
- Material with item category group 0005 (milestone billing).
- Billing plan type: 01 (Milestone Billing)
- Date category: 03 (Down payment request -proc.)
2 Pricing Procedure:
- Subtotal with the base value calculation formula 2 (net value) before the condition AZWR.
- Condition Type AZWR
i) Calculation type B (fixed amount)
ii) Condition category e (down payment request / clearing).
iii) Included before output tax.
iv) Condition 2 (item with pricing)
v) Calculation formula 48
vi) Printing indicator
3 Sales document: TA
4 Sales document position TAO
5 Billing Document: FAZ (down payment request)
6 Copying control
- From TA FAZ. Copying requirement 20 entered at item level (item category TAO).
- From TA F2. Copying requirement 23 entered at item level (item category TAO).
7 Financial Accounting settings
- Field status definition G031 assigned to reconciliation accounts - For the `received DP' and `DP requests'.
- Posting key maintained for the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system)
- G/L account number assignment for the tax account.
- For posting key 19, set the sales order as an optional field (transaction OB41).
- 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)Hi Gonzalez
Say in the sales order ->item data -> billing data you have given the data as follows
Say for example :
Net value - 5000
No. billing date date billing type amount
1st billing date - 07/11/2008 FAZ 1500
2nd billing date - 14/11/2008 FAZ 1000
Final Billing date - 15/11/2008 F1 2500
So when you create 1st billing you will get Rs 1500/- and for the 2nd billing you get amount of Rs.1000/- and When you do your final billing then you will get Rs.2500.
But when the 1st billing doc gets generated for Rs1500 it has to be cleared by FI also and even for the 2nd billing document and finally for the last billing date.Then the accounting gets cleared
Regards
Srinath -
Down Payments & Delivery relevant invoice
Hi!
The problem is to create a down payment request to the customer through an SD order (this can be done with billing plan, item category TAO, condition type AZWR, invoice type FAZ) but we want to create the actual invoicing with a <u>delivery relevant invoice</u> and not an order relevant invoice.
I do not see how this is feasible, if it can be done!
Thanks in advance for you replyI have now a better understanding of your solution.
But then the more "standard" solution of creating down payment through FI (F-37) is about the same, as it is using two different unrelated documents.
What I had in mind was:
1/ Create an order (with delivery block)
2/ Create a down payment request related to this order (VF01)
3/ Cash in the down payment and remove delivery block
4/ Deliver
5/ Create the delivery related invoice. (This invoice would of course then be able to remind customer that a down payment was done, down payment accounting clearing would be also done).
I know, I might be dreaming. But if I am not the only one -
Dear all,
Can any body tell me how to link customer down payment with Billing Document?
My scenario is "customer give 100 rs down payment while billing of 500 rs that down payment 100 rs should be subtract from 500 rs".
Thanks & Regards,
RatishThe 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) -
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 chi,
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
Maybe you are looking for
-
i upgraded new software onto my iphone 4 however it stopped syncing and said error so when i tried to access my phone the itunes USB was showing in my phone screen and now i cannot access my phone
-
BPEL Human Task: how to remove task details section from notification email
This is concerning the human task component of SOA Suite 11g. Upon task assignment, the assignee receives an email notification with an administrator configured text. Below this text the task details are automatically added. How can this be removed?
-
Debugging of Routines in transfer rules
Hi All, I wrote a routine and trying to debug.I tried to debug using "Simulate update" option when we right click in the monitor screen.I don't know how to proceed from there.Could some one explains the steps to debug the routine in transfer rules? Y
-
PLEASE! For the love of all things FLASH CS3! There is a MAJOR bug in CS3 which causes the Panels to overlap once another which annoys the living crap out of me! Does someone know of a fix for this? Also the Output Panel, which in Flash 8 you could d
-
HT201317 how do I share my photos on my macbook pro (OS 10.8.2) with my wifes iPad2 (iOS6)?
how do I share my photos on my macbook pro (OS 10.8.2) with my wifes iPad2 (iOS6)?