Dear Lakshmipathi,
I tried this above by maintaining 999 lines for the sales org. still I am getting error of maximum line in FI reached. Plz revert if I can achieve via restriction in VF01 transaction for future.
regards
SP Shukla
↧
Re: validation in VF01
↧
Re: validation in VF01
In your original post, you said 99 line items and now you had indicated 999. Please let me know exactly where you need to control. Needless to mention, for the said error, you need to try from FI side and not from SD side. For information, for each line item in SD, there would be two line items posted in FI. Hence, you need to spell out clearly. As I already indicated, if the requirement is to have restrict the number of line items in FI, then have a discussion with your FI consultant.
You can also have a look at the following notes:-
- Note 36353 - AC interface: Summarizing FI documents
- Note 1497092 - AC interface: Posting split in FI for incoming invoices
G. Lakshmipathi
↧
↧
Re: validation in VF01
Dear Lakshmipathi,
it is 999 lines, mistakenly written as 99 lines.
above notes I already checked but due to business process we can not do as per notes.
I need validation from SD side in VF01 transaction where if acct document is not going to be generate for any bill no due to maximum FI lines reached (message) system wont allow user to save that bill.
Tried to write validation in RV60AFZZ to count lines of XVBRP if it is 999 then system will show error and will not allow to save the bill. But I think 999 lines includes all condition types. I am not able guide abaper to check this event of 999 error (maximum no of line item FI reached)
waiting revert for possible way out to incorporate the restriction in VF01 t code.
regards
SP Shukla
↧
Re: Error in :Posting keys for account determination
Hello,
is the Account key Z48 maintained in transaction OB40 ?
If so please check if is present in table T030B.
Best regards,
Ivano.
↧
Re: Condition type EK01 missing in pricing procedure A V (error message V1206)
Hello Victor,
could you please check if any custom requirement routine has been assigned to EK01 in the pricing procedure ?
If so please ensure that KOBEV_nnn form just checks KOMK fields. See the SAP note 156230.
Best regards,
Ivano.
↧
↧
Re: validation in VF01
You can find out what is the maximum line items that can be created for a billing document on the FI side, by checking the number of pricing condition types that can be passed to accounting. Then divide that condition type from 999 to find the number of line items that can be maintained in the billing document. Then provide the details to ABAP'er to write the code in the user exit.
above notes I already checked but due to business process we can not do as per notes.
I am not clear on due to business process, as the solution can be possible by applying the note. Is there any restriction from FI side?
Regards,
↧
Picking Error
Hello,
I have the following issue at the picking process:
- It was created a order sales with 4 materials (item: 10, 20, 30, 40).
- It was executed the picking for all items.
- It was created an invoice for all items (then we noticed the item 20 wasn't there)
This invoice is already billed. This issue was in 05/2013, but only now they noticed this issue.
When we look at Flow of Documents we can see that item 20 still with the status "Processing", while the others items are all done.
We don't know what to do with this item, because it was billed, it is not in inventory, it is just lost in somewhere of system.
And this item is not in the company anymore!
Do you guys have any idea about what happened and what can we do to fix it?
Thank you!
↧
Re: Picking Error
Hello,
I suppose that the SD process is: order -> delivery -> picking -> invoice.
The delivery has items 10, 20, 30, 40 all picked.
But the subsequent billing document has only items 10, 30, 40. So the delivery item 20 is unbilled.
Is it right ?
Why don't you simply run VF01 to bill item 20 of the delivery ?
Best regards,
Ivano.
↧
Re: validation in VF01
Dear Shukla,
check the copycontrol between Delivery to Invoice(VTFL) and Item level TAN check Data VBRK/VBRP=351
.i think need to make changes in 351 routine.check with your Abaper.
Regards,
Rakesh rahul
↧
↧
Cross Company - Different Sales Area - Intercompany
Dear Gurus,
My client having the following requirement and having one issue while I am processing this.
My company book the provision of rebate at company code 1000 sales area 1000+10+10, and customer lets say 12345,
When create manual rebate payment in the rebate agreement system automatically create credit memo request, plus there is a provision to change the sold to party.
So when I change the sold to party there that is created on company code 2000 sales area 2000+10+10 and lets say customer is 7777, system give the error message that "Sold to party not maintain for sales area 1000+10+10"
I have assign the document type to both sales area, plus If I separately choose this document type and create credit memo request for customer 7777 system cant give me any error message...
Please suggest the reason and required action so that system can facilitate this.
regards,
↧
Re: Cross Company - Different Sales Area - Intercompany
Hi Imran,
Can you check Account group for this customer 7777,.
I believe this could be Intercompany Billing customer which is supposed to be created in both Sales area
After extending the customer to both sales areas, you also should maintain this customer at Sales organization customization under INTERCOMPANY CUSTOMER field
please try and revert
regards,
santosh
↧
Re: Cross Company - Different Sales Area - Intercompany
Both customer account group are same, basically its not only one customer, the behaviour apply to thousands of customers.
I have the following observations that's why system give the message and looking for any option for this.
when in manual payment of rebate I input the value of rebate and save it, system automatically create the credit memo request, and the same customer is saved along with the sales area at header level, like 12345, 1000+10+10,
when I use va02, and change the customer system cant change the header data sales area to 2000+10+10, so its simply give the error message, and document type also assign on both sales area, system basically cant re-determine the sales area.
So is there any possibility for this.
regards,
↧
Re: Error in :Posting keys for account determination
""" Now we want to capture CST and VAT seperately for both the materails.For that two new account keys created and incorporated the same in scrap pricing procedure and and new G/Ls created and assigned """
Where you assigned at Pricing(Accounting key/Accruals) in V/08.
Have you activated accruals field for these condition types in V/06.
Have you assigned the Posting keys correctly for this Accounting key?(Take help from your FI guy)
(IMG>>Fin Accounting new>>Fin.Accounting Basic settings(new)>>Document>>Define posting keys)
Can you please elaborate on your requirement of Capturing VAT/CST amounts?
Phanikumar
↧
↧
Re: Credit Note issue against AR Down payment
Hi Lakshmipathy,
Please find below steps followed:
Step 1. Create Order with down payment and billing plan
Step 2.Create Invoice with FAZ(Z1AZ)
Step 3.Post incoming payment
F-29 done
Step 4.Reversal of Incoming payment
F-39 Cleardown payments
If we use
this transaction, do you see any issue ?
Step 5. Issue debit memo against the FAZ(Z1AZ)
Create Debit memo request and debit memo
Document 9002000724
saved (no accounting document generated)
Message no. VF050
When tried to release the document to accounting, the
following error.
No account is specified in item 0000001001
Message no. F5670
Diagnosis
No account was specified for account type
"S" in item "0000001001" of the FI/CO document.
System Response
The Financial Accounting program cannot
process the document.
Procedure
A system error has probably occurred in
the application you called up. Check the data transferred to item
"0000001001" of the FI/CO document.
Please advise on this.
Thanks
Sreekantha
↧
Re: Credit Note issue against AR Down payment
Hi,
open billing document in VF02 and click on revenue accounts (shift + F11) check analysis account determination search any error for gl determination
and Down payment cleared document Reverse and Reset in FBRA
Or normal item cancel in FB08
Thanking you
Mahesh
↧
Re: Credit Note issue against AR Down payment
Hi ,
We have done the document reverse and reset in FBRA.or normal item cancel in FB08.
Business want to issue Debit Note with reference to the Down payment invoice(FAZ). While doing the same I am facing the account determination issue, as the down payment is with only noted item.
Hope my issue is understood correctly.
Debit Note issue with reference to Down payment line item
Case 1: Business has created only Down payment request and received down payment incoming payment against FAZ. Further milestone related billing is not yet done.
Step 1. Create Order with down payment and billing plan
Step 2. Create Invoice with FAZ
Accounting entries: only one line item with noted item A down payment request.
Step 3. Post incoming payment
F-29 done
Step 4. Reversal of Incoming payment
F-39 Clear down payments or
Down payment document reverse and reset in FBRA.
or FB08.
Step 5. Issue debit memo (DR)against the FAZ
Create Debit memo request and debit memo
Error: Document XXXXXXX saved (no
accounting document generated)
Message no. VF050
When tried to release the document to accounting, the following error.
No account is specified in item 0000001001
Message no. F5670
Diagnosis
No account was specified for account type
"S" in item "0000001001" of the FI/CO document.
System Response
The Financial Accounting program cannot
process the document.
Procedure
A system error has probably occurred in
the application you called up. Check the data transferred to item
"0000001001" of the FI/CO document.
There is no account determination for the Down
payment line item(as it was noted item and the payment is entered in FI ).
Can this be over come by issuing the Debit note from FI with reference to Down payment Invoice FAZ ?.
Case 2: Business has created Down payment request and received down payment incoming payment against FAZ .Mile stone related billing is also done which will have Milestone billing line item and Down payment line item.
Step 1. Create Sales order
Step 2. Create Down payment request
Step 3. Post incoming payment
F-29 done
Step 4. Create the next mile stone related billing.
Invoice XXXXXXXX with Down payment cleared line item and invoicing line item
Step 5. Raise debit note with reference to Milestone relating line items
Only line item with invoicing line needs to be selected while raising Debit memo request:
Step 6. Create billing document
Note: For the down payment line item, we need to follow the process of Case 1(Can this be over come by issuing the Debit note from FI with reference to Down payment Invoice FAZ ?) by issuing FI Debit note.
Thanks
Sreekantha
↧
Re: Billing issue
Hi Srinu,
No POD concept implemented
Net value exist.
No in completion log in delivery.
The SAP note speaks if invoice is created for multiple deliveries in our case the invoice is created for single delivery.
Regards,
Ali
↧
↧
Re: Credit Note issue against AR Down payment
Follow the instructions given in the following note:-
- Note 882254 - How to create an CreditNote on an AR downpayment Invoice
G. Lakshmipathi
↧
Re: Billing issue
Hi Lakshmipathi,
The PGI is completed, the status of line item at delivery "status overview tab" is 'C' Completely processed.
Regards,
Ali
↧
Re: Credit Note issue against AR Down payment
Hi Lakshmipathy,
I tried to do FB08 but the following:
Not possible to reverse the document in financial accounting
Message no. F5673
Diagnosis
Document '9002000726' in company code 'XXXX' should be reversed. However,
this document was not posted in the Financial Accounting module, VBRK is,
rather, of type ''.
System Response
Documents which were not originally posted in Financial Accounting also
cannot be reversed in Financial Accounting.
Procedure
Reverse the original transaction. You can display the original document from
the FI document via 'Environment' -> 'Original doc.'.
But it allows through F-39.
2.VF11 also it will not support: Down payment request 9002000726 cannot be canceled.
Thanks
Sreekantha
↧