Down payment according to Italian laws

Dear all, my company is currently running ECC 6.0 EhP 4.
At at the moment the down payment is not following the Italian laws.
Does anybody have news regarding this topic?
Thanks and regards
Alessandro Giani

Hello,
Please check the note 611040.
Regards,
Raghavendra

Similar Messages

Down payment at PO level without line item

Dear All
At the moment when we post down payment request and confirm down payment F-47 and F-48. The system will ask for PO number with line item no.
In practical situation we pay down payment against a PO and not against each line item in PO. e.g. If we have a PO with 20 line item and require 20% down payment according to current standard setup we have to process F-47 for each of these line items which is not desired.
Therefore is it possible to customize the system to post down payment against PO and not at line item level.
It is possible to post F-47 for vendor without referring to PO at all and only refer vendor but we need to refer PO -for reporting and PO status update purposes- just not at line item level.
Any advise?
Regards
Anant

without PO it is not possible to process F-47.
you can not make PO with line items. At least one line item should be maintined

Down payment against Purchase order

Hi SAP GURU
i have one queries regarding down payment made against asset puchase order
I created one asset code, create the PO with accoun assignment categories A, made a advance payment against reference to this PO no .
when i enter the po number in purchase document field, immediatly asset number coming and showing error message
You cannot use this transaction type to post to this asset
Message no. AA834
Diagnosis
The transaction type entered belongs to transaction type group 15. According to the specifications for this transaction type group, posting with transactions types belonging to this group are only allowed in specific asset classes (for example, asset classes for assets under construction).
The asset to which you are posting belongs to class 9000 (chart of depreciation SHV). You cannot post to this class using the transaction type you have entered.
Procedure
Check the asset number entered. You may want to allow posting with this transaction type group for the asset class of the asset.
Can any body suggest what is the right way for the whole scenarion , or i am making some mistake .
points will be awarded for useful answers
with regards
sai krishna

last week i also faced this problem.
Please refer sap note number 310368 valuated goods receipt paragraph and they have clearly mentioned about making down payments against asset purchase order without getting debited to asset account.
You have to make F5 378 message number to be a warning message instead of error message and you have to suppress asset related settings in OB41 posting keys 29 and 39. Posting key 39 is useful when you have down payment request.
If you have done this, then it will show only warning message during down payment that "purchase order is related to asset" and it will not be debited to asset account. Also after following the above steps, it is not necessary for you to give Acquisition: down payments G/L and Down payment clearing G/L in AO90 transaction code.

A/P Down payment invoice Problem

Hi all,
I have the ff. scenario
1.     Create PO
2.     Create A/P DP invoice(20%) against this PO
3.     Create outgoing payment against A/P DP invoice of 20%
4.     Create A/P DP invoice(30%) against this PO
5.     Create outgoing payment against A/P DP invoice of 30%
6.     Create A/P DP invoice(60%) against this PO
7.     Create outgoing payment against A/P DP invoice of 60%
8.     Create a regular A/P invoice against the 3 DP
Problem 1. We have exceeded our payment against the PO w/c in this case is 110%, but SBO allowed to post these Down payments. How can we prevent overpayment base on a specific PO?
Problem 2. Since we have overpayment what we should do on 10% overpayment?
Please help.
Fidel

Hi Fidel,
Sorry for the late post, quite a busy day for me today.
edit - start
Errrrr, line 12 actually should be IF @iBaseType (less-than-symbol)(greater-than-symbol) 22
Why this forum remove those 2 symbols whenever I write them? Anyway, you should understand it, I mean "IF @iBaseType is not equat to 22" in SQL script. Just curious why SDN automatically remove whenever those 2 symbols adjacent to each other, weird...
And the same thing apply to line 25, should be AND TargetType (less-than-symbol)(greater-than-symbol) 19
edit - end
IF @object_type='204'AND @transaction_type='A' -- 204 is object type for A/P DP Invoice
BEGIN
    DECLARE @iBaseType AS INT               -- To contain base document type of A/P DP Invoice
    DECLARE @lDpmPrcnt AS DECIMAL(18,2) -- To contain sum of DP% related to the based PO
     SELECT @iBaseType=BaseType
     FROM ODPO T0
     INNER JOIN DPO1 T1 ON T0.DocEntry=T1.DocEntry
          WHERE T1.DocEntry=@list_of_cols_val_tab_del
     IF @iBaseType<>22          -- Make sure in order to create DP, a PO is required (PO object type is 22)
       BEGIN
          SET @error=-1
          SET @error_message='PO required in order to create purchase down payment'
       END
     ELSE
       BEGIN
          SELECT @lDpmPrcnt=SUM(DpmPrcnt)
          FROM ODPO T0
          INNER JOIN DPO1 T1 ON T0.DocEntry=T1.DocEntry
               WHERE BaseType=22
               AND BaseEntry=(SELECT BaseEntry FROM DPO1 WHERE DocEntry=@list_of_cols_val_tab_del)
               -- Line above is to select all DP related to base PO
               AND TargetType<>19
               -- Line above is to make sure DP that already reversed using A/P Credit Memo is excluded
               AND LineNum=0
               -- Make sure to add line above due to facts that DP% located in document header
               -- and since we join ODPO with DPO1,
               -- if line above doesn't exist, the sum of DP% will duplicated accordingly to number of line items in document
          IF @lDpmPrcnt>100
            BEGIN
               SET @error=-1
               SET @error_message='Down payment percentage already exceeded 100% of PO'
            END
       END
END
Inform me if you have any inquiry or problem regarding this SP.
Best Regards,
Hendry Wijaya
Edited by: Hendry Wijaya on Sep 8, 2011 5:42 PM

Down Payment request more than PO value

Hi All
How I can stop making a down payment Request of more amount than the P.O
Value?
I have changed the Message control and made the warning as error.....Now if
I make a downpayment more than the P.O amount in a single posting, it gives me error message. But, if I create partial payment requests against a PO, it exceeds the value of PO.
For example, suppose I have P.O of Rs 50000
and still I make two downpayments of 40,000 and 50,000 system accepts
I have tried for the user exits, BADi also, but I am unable to get a solution.
Kindly help me in finding a proper solution to this.
Regards
Debasis Panda

Hi Jaya Jaga
As per my knowledge, this is finance related Anyway, I can answer this question and please configure accordingly. Please give feed back.
Follow the Configuration Path
SPRO u2013 Financial Accounting u2013 Accounts Receivable and Accounts Payable - Outgoing Invoices/Credit Memos - Carry Out and Check Document Settings - Maintain Field Status Variants
Then Double click
(OR)
Transaction Code OBC4
Change Radio button option from Suppress to Required. Entry option in Purchase Order field. Then SAVE
Hope this can be clear.
Thanks
Vijay

Error while using Special GL indicator H for Customer Down Payment

Dear Friends,
I have configured the Special GL Indicator H (Security Deposit) for Customer Down Payment received. I also make the necessary settings in OBXY for assignment of Special GL against the reconciliation account.
When I am doing the Customer Down Payment entry through F-29 using special GL indicator H system giing me the following error message
Special G/L indicator H is not defined for down payments
Message no. F5053
Diagnosis
The specified special G/L indicator is not classified as "down payment" or not listed in the list of the target special G/L indicators for indicator "F".
System Response
The entry is not accepted.
Procedure
Enter an allowed special G/L indicator or initiate a change of the default settings
I also check the configuration again but still systems is giving me the same above error.
Kinldy give me the solution or way of doing this ASAP because I am working in an implementation Prj.
Regards,
Sandeep

Dear Surya,
I have made the necessary changes in Special GL Indicator F in their properties I assign target spl GL indicator H but while in spl GL indicator H when I assign target spl GL indicator F system gives me following error
Delete target special G/L indicator
Message no. F4137
Diagnosis
In the SAP system, you can only use "Target special G/L indicators" with "Down payment/down payment request" when "Noted item" is also selected at the same time. These requirements are not fulfilled in the special G/L indicator "H".
Procedure
Delete the specified target special G/L indicator.
Effects on Customizing
You can define when this system message is to be issued in accordance with your requirements.
You do this in Customizing as follows: Cross-Application Components -> Bank Directory -> Change Message Control.
The application area and message number can be taken from the technical documentation.
Thanks,
Sandeep

Down Payment Invoice

Scenario :
The company is collecting Advance from the customer for a sale. The sale includes freight.
The Customer gives 50 % of the sales order which includes freight.
In SBO :
1. 'AR Down Payment Invoice' is raised for advance.
Issue
1. The AR Down Payment does not consider freight.
How to include freight in the down payment..?

Hi,
As the requirement is currently not available in the standard software
version of SAP Business One, we would like to ask you post your
requirement in our SAP Business One Product Development Collaboration
forum. You can find the forum in this link:
/community [original link is broken]
The forum is being moderated by members of the Solution Management team
specialized in certain areas, according to the business you are in.
Partners can impact the design of specific features by posting
suggestions and feedback at this forum.
Regards
Vikas
SAP Business One Forums Team

Cancel A/R down payment invoice and clearing account

The following AR Dowm payment cancelation has been processed (as per the SAp WIKI)
- but the down payment clearning account still has a value - how can this be reversed?
2007A PL 42
1. If a 'Down Payment Invoice' (DPI) is unpaid and requires cancellation, then an 'AR Credit Note' can be used.
2. The 'AR Credit Note' should be based on the DPI. This will create the correct journal entries necessary to cancel the DPI.
3. This is a screenshot of a DPI and its associated journal entry:
4. The credit note based on the unpaid DPI will credit the customer and the associated tax accounts accordingly.
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=21823731

Lisa,
Please compare the journal created for the DPI and the journal made behind the credit note. Does the journal lines match?
Regards,
Nat

Problem in Down Payment Request

Hi,
In SAP documentation for the down payment request, it says we have to use the BO BSEG, event CREATED and wf WS00400011, WS00400021, WS00400022 according to various approvals. But when i use those, the workflow is not getting triggered. Event linkage is activated. Nothing is showing in trace also. In BO, for the CREATED event, the description says that "Posting Item Created with Payment Block". I think there is something related with payment block. Can anyone know what is it mean ??

Check if there are some start conditions associated with the event (SWB_COND).
Secondly check thru SWUE if the workflow is indeed the reciever of the event or not. Might be the case that in PFTC you can see the linakge active but in SWE2 it is still marked inative. It has happened with me so just want you to double check.
And ofcourse you can always try refreshing the buffer !!
regards,
Anuj Sethi

Down Payment for Contracts

Hi,
I have a scenario where a vendor is having yearly contract (PO). He is paid upfront at the begining of the year when invoice for full amount is received (amount debit to vendor pre paid / alternate recon account and credit bank). Later at each month, partial amount is expensed (debit) and pre paid / alternate recon account credited accordingly. At the end of the year the full amount is expensed and pre paid account is also balanced.
I am thinking of using vendor down payment functionality (F-47, special GL indicator A), attach a PO (with Invoicing plan and ERS combination), make down payment. Up till this stage the FI entries are debit vendor pre paid / alternate recon account and credit Bank (which is expected). Now with the Invoice plan, the system creates vendor invoice automatically, FI entries are debit expense and credit vendor recon account. We don not want to pay the vendor again as down payment already exist. Is there an automated way now to post credit entry in vendor pre paid account.
I was also going through the earlier post where I found similar issue (Re: Down Payment). However while posting the invoice I am not getting the entries as mentioned in step 2 (check link) i.e. credit pre paid vendor recon account
Any help is appreciated or any solution as well
SR

we have used the following substitution to do that
pre-req
SYST-TCODE = 'F110' AND BKPF-BLART = 'KZ' AND
BSEG-BSCHL = '29' AND
BSEG-UMSKZ = 'A'
Substitution
field "Payment block' is substituted by constant " " (Empty)
Instead of KZ you need to use the document type that is assigned in the your config FBZP for Payment method in country.
This will not allow the payment for the subsequent invoices and payment program will automatically clear the Down payment when all the invoices which will net the downpayment to Zero have been posted.
Thanks
Ron

Down payment (F-48)   for Asset Purchase Order

Dear Experts,
Please guide me,   i am getting one error while doing down payment to vendor through F-48 ,    I created one asset purchase order, against purchase order making down payment that time i am getting this error message
"You cannot use this transaction type to post to this asset
Message no. AA834
Diagnosis
The transaction type entered belongs to transaction type group 15. According to the specifications for this transaction type group, posting with transactions types belonging to this group are only allowed in specific asset classes (for example, asset classes for assets under construction).
The asset to which you are posting belongs to class 401006 (chart of depreciation WCCD). You cannot post to this class using the transaction type you have entered.
Procedure
Check the asset number entered. You may want to allow posting with this transaction type group for the asset class of the asset. "
my asset is plant and machinery, any configuration is required.
as per my knowledge i checked in T.code : OAYB   transaction type groups   15 only assign AUC asset class and Capital Advance.    In account determination balance sheet accounts   there is Acquistion : Down payment   and Clearin G/lL for Down payment   g/l a/c not assign .
SAP F1 help in that field (above said) is saying that only for AUC.
Please guid me ,   What to do.
Thanks & Regards
Chandu

Hi Chandu,
Can youplease confirm the the Asset Class (the one linked to the asset you are using for carrying out down payment with T.Code F-48) has been set-up in configuration as an AUC asset class. Check on T.Code OAOA for the radio button selected for Status of AUC.
In case your Asset Class - which is Plant & Machinery - has been set up as "No AuC or summary management of AuC" i.e. has been set-up as a final asset class then you will get the error.
Solution Options:
(1) Either change the Asset Class set-up (using T.Code OAOA).
Please note - you might not be permitted/able to do this if the system already has posted transactions for this asset class.
(2) Carry out the downpayment for an AUC Asset (create an AUC Asset using T.Code AS01). Carry out F-48 for this. Later settle this AUC asset to the required/relevant final asset (using T.Codes AIAB and AIBU).
(3) Specify your Asset Class as available for carrying out DownPayment transaction. Use T.Code OAYB and for Transaction Type Group 15, include/add a new entry for your asset class.
(4) Ensure that the Account Determination linked to you asset class (check this in T.Code OAOA) has been correctly and adequately set-up for GL account determination (use T.Code AO90).
Hope this helps.
Regards,
Ruchi

Clearing customer Items with Special G/L Indicator 'A' (down payment)

Hi All,
I've to clear two items of a customer by t.code F-32:
Both items, that I dysplays by t.code FBL5N (u20AC 20.000,00 and - 20.000,00), are with Special G/L Indicator 'A' (down payment).
Only the first one contains a 'tax amount' equal to 4.000,00.
When I process the open Items of the customer by t.code F-32, I expect to see the two items as follows
20.000,00
- 20.000,00
Instead, SAP displays as follows
24.000,00
- 20.000,00
So, I can't clear them as 24.000,00 is not equal to 20.000,00
Could anyone tell me ho to solve?
Thanks

Hi Maurizio,
first of all, thanks for your answer.
I've checked the tax category in the G/L account master data of the special G/L
account used for down payments (A). Tax category is equal to '+ '.
According to this setting, I posted a customer credit memo as follow:
Item 01; posting key 11; Customer account XXX; Amount 24.000,00
Item 02; posting key 09; Customer account XXX; Special G/L Indicator A; Amount 20.000,00 (tax code 20%)
Item 03; posting key 40; Debit tax account; Amount 20.000,00 (tax code 20%)
Now I've to clear the item 02 of that credit memo. When I try to do it by t.code F-32, SAP displays the amount 24.000,00 (with tax amount) and not 20.000,00.
Clearing that item, the system create a automatic posting for tax account of 4000,00.
This is my issue: SAP shouldn't create this posting for tax account.
Thank again.
G.

Create workflow to release Down Payment Request (F-47) before automatic Pyment

Hi Experts,
I use basic workflow for parked document to release all invoice document from AP. But i get problem with down payment request.
In my company, we run down payment by F110 according to down payment request. We use workflow to release parked document before post. But down payment request is created as noted item, so that, it isn't go to workflow when create. Please give me advice how i can manage Down Payment Request. Ex: we want block down payment request when being create and have release function to permit down payment by F110.

Hi,
Using T-code F-47 - Down payment request against raise to possible as follows.
a) Purchase Order Document
b) Production Order
c)PM Order
d)Service Order
e)Process Order
f)Internal Order
Down payment request is not possible against to raise StockTtransfer Order(STO) and display error message.
So, you have to choose the above list only.
Hope, it is useful for you.
Regards,
K.Rajendran

Down Payment From Customer

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,
Ratish

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 Process in SD

Hi All,
We want to implement a down payment progress in our system. I did all of the customizing requirements in SD according to OSS Note 213526.
Furthermore, when I placed an sales order in VA01 and then invoiced in VF01(only invoiced the value in billing plan) -in other words down payment request in SD, I also used F-29 for down payment and the order number appears in that screen and then payed. But the condition AZWR did not change or update.
What is the problem in process or in configuration? In addition to this, I have also checked the configuration steps many times which are in OSS Note.
Regards.

Dear ,
I am doing the downpaymet with in milestone billing plan. i have 3 legs in the billing plan . the first one is acting as down payment
the remaining as normal which can be billed with normal billing plan right?
Billing plan Milestone
Item category TAO
billing document FAZ
Normal billing document F2
Item category group is 0005
Condition type is AZWR
This is all about my config could you please help me to do so..
With Regards
Aswin Nair

Down payment according to Italian laws

Similar Messages

Maybe you are looking for