999 line items reached in FI
Hi,
When we are trying to release a billing document we are getting the below error message "999 line items reached in FI". Please through a light on this.
Thanks,
Kumar
Hi
In SAP version 4.6c there is a limitation of posting more than 999 line items in a single document.
In ECC version this limitation is not there.
Now what next for you in order to post document?
Please try to split the document in 2 parts and post it..There is no other alternative to this
If this solves your problem then please award points.
Kind Regards,
Similar Messages
-
Hi all,
In the SD, for One Post Goods Issue Material document and FI document generated.
Accounting document contains two line items.
If the Post Goods Issue contains More than 500items then in FI document generates with more than 1000 line items.
But as per std SAP, Per document 999 line items only.
Client wants to post at a time more than 500 items (DN) Post Goods Issue then more than 1000 line items generated.
How to post morethan 500 items in DN.
Thanks
venuHi
OSS Note 36353:
Summary
Symptom
When you post documents using the AC interface (from SD, MM or other applications), items appear in the FI document which are identical in all or in almost all fields.
This can also cause error message F5 727 ("Maximum number of items in FI reached"). The system issues this error if more than 999 items occur in an FI document.
Other terms
SAPLFACI, VF01, VF02, VF04, MB01, MB11, MR1M, CO15, BSEG, totaling,
document summarization, CKMI_RUN, F5 272, F1 807
Reason and Prerequisites
The system will only total items in the FI document if you made the proper settings for this action in Customizing (= sending application, for example: VBRK for SD, MKPF for MM Position Management, RMRP for MM Logistics Invoice Verification).
There is no summarization, for documents which are entered in FI (object type BKPF) application (for example EDI invoice receipt, FB01, MR0) or in invoice verification (MR01) (with object type BKPF).
The system can only total items in the FI document if they have the same account assignments and only differ in the value fields.
It is therefore not possible to carry out the totaling across different G/L accounts.
The summarization can be achieved by deleting certain fields in all items (can be configured in Customizing).
As a consequence, these fields will not contain data in the FI document. They are therefore no longer available for selection, clearing or reconciliation with other applications.
This field deletion only affects the FI document, not documents from other AC applications.
The field contents deleted in the FI document are still available for the other AC applications and can be updated there. The AC applications are not updated on the basis of the FI document. In addition, there are other summarization procedures in other applications, for example in CO (Note 147766).
Solution
Procedure for configuring summarization:
Carry out the following actions for each object type (sending application, AWTYP field), for which you want to summarize FI documents.
You can find the AWTYP object type on the detail screen 'Document header' under the 'Name' field when you display the document using transaction FB03.
1. If you think an FI document has too many items, find out in which fields the items differentiate.
To do so, display the FI document (FB03) or table BSEG and ONE FI document (SE16).
2. If there are items which are the same in all same account assignments:
Make the following entry in the TTYPV table (transaction OBCY):
Table Field name
As a consequence, items which are the same in all fields except value fields are totaled, that is, they are combined into a single item.
(The '* ' entry can only be made in Release 3.0D or higher.) If you use a release lower than 3.0D, enter any field which, when deleted, will not disrupt transactions from the affected application. As of Release 4.0, the ' ' entry can no longer use transaction SM31 (view maintenance) to make the entry in the TTYPV table. Check whether you can replace the entry ' ' with a field name. The corrections from this note enable you to use the report ZTTYPV to enter ' *' for the relevant object type.)
3. If there are ITEMS which differ in specific fields:
Enter the fields in the TTYPV table.
The contents of the fields entered in the TTYPV table are deleted.
This has a higher summarization effect than entry '* *'!
Typical fields for each application are:
Application AWTYP Table Field name
SD VBRK BSEG MATNR
Billing MEINS
MENGE
PAOBJNR
POSN2
VBEL2
WERKS
MM MKPF BSEG BPMNG
Position Management BPRME
ERFME
ERFMG
MATNR
MEINS
MENGE
PAOBJNR
POSN2
WERKS
BWTAR
MM RMRP BSEG BPMNG
Logistics BPRME
Invoice Verification ERFME
ERFMG
MATNR
MEINS
MENGE
PAOBJNR
WERKS
As of 4.0A
HR HRPAY see Note 116523
Payroll accounting
The list of the allowed fields in Release 3.1I includes the following entries in the TTYPS table:
BSEG BPMNG
BSEG BPRME
BSEG BWTAR
BSEG ERFME
BSEG ERFMG
BSEG MATNR
BSEG MEINS
BSEG MENGE
BSEG PAOBJNR
BSEG POSN2
BSEG PPRCT
BSEG VBEL2
BSEG WERKS
BSEG PRCTR (for restrictions see below)
BSEG FKBER (Note 413418)
General remarks:
Items with identical account assignments but different debit/credit codes (BSEG-SHKZG) will NOT be put together as a single item (for example, revenues and sales deductions in billing documents).
In releases lower than 3.0F, the system did not allow all of these fields as entries for the TTYPV table. To expand the number of fields allowed for the TTYPV table, enter the fields in the TTYPS table. (Call transaction SM31 (view maintenance) to add an entry to the V_TTYPS view.) (You can only add the BSEG BWTAR field using transaction SE16 (table maintenance) for the TTYPS table). The standard system only contains the BSEG-PRCTR field is only contained in the TTYPS table as of Release 4.6B.
This is an SAP table modification. Only enter the fields listed above. Do not enter any other fields without first contacting SAP, since these fields will then be deleted in every FI document from the application in question.
Notes:
When you carry out summarization using the material number (MATNR) during position management or invoice verification transactions, the 'material number' information is lost in the BSEG document table of Financial Accounting. Therefore no entries are written to the BSIM table. This can have the following consequences:
Transactions such as MR51 (accounting documents for material) or MB5B (balance at posting date) produce incorrect results.
The evaluation of balances at material number level (characteristic 0MATERIAL) in the SAP Business Information Warehouse displays faulty or incomplete results.
You can no longer use the Value Flow Monitor (transaction CKMVFM) to compare differences at material level between price difference accounts and the relevant FI postings.
If you delete the material number (MATNR), the amount (MENGE), the unit of measure (MEINS) or the plant (WERKS) in position management, this information is no longer available in financial accounting. The RMVKON00 report (transactions MRKO and MRPI) however, which indicates and settles the consignation stock, is based on the documents of financial accounting. This has two consequences:
If the FI documents are not summarized, each individual withdrawal is indicated in the report and can also be individually settled. If the FI documents are summarized, several withdrawals can be displayed in one single report line and can no longer be separately settled. Furthermore, certain data, such as material number, amount and unit of measure, may no longer be displayed.
If in the FI documents the material number or the plant is deleted and you settle the withdrawal, the tax codes that you defined using the tax indicator (in the material master) or in a purchasing info record can no longer be found. Instead, only the tax code that you defined as default value in the Customizing settings for the invoice verification (transaction OMR2) is determined. If no valid tax code has been defined there, the settlement terminates with message FF 704.
Read Note 38982 to learn how to determine the tax code.
In Release 4. 0A, these restrictions no longer apply to the RMVKON00 report.
Clearing of the GR/IR clearing account for each purchase order item: The account assignments to the purchase order (EBELN) and to the purchase order item (EBELP) are NOT deleted by default. In both the goods receipt with reference to the purchase order (MB01) and the invoice verification, they are assigned to an account in the FI document and thus PREVENT the summarization of the FI document.
This makes it possible to clear the GR/IR clearing account at purchase order item level.
Using Profit center for summarization
If you summarize using the Profit center field in FI, only FI and PCA balances can be reconciled at account level.
A summarization using the Profit center field is only worthwhile if other CO account assignments are also summarized. These account assignments are therefore also not available for a derivation of the Profit center field when the FI document are subsequently posted to Profit Center Accounting using transaction 1KE8. Since summarized documents are always postings the original of which is not posted in FI, you should subsequently post such documents from the sending application component anyway. However, you can directly transfer unoriginal FI documents using Note 102634 or, as of Release 4.5B, using the standard system. In this case, you must make sure that this function is not used for the summarized documents.
For the reason stated above, a summarization using the Profit center field is only worthwhile for transaction HRPAY. Note that HR only supports a subsequent posting from the sending application component as of Release 4.5A. In the releases 4.0A up to and including 4.0B, no programs are available in the standard system to generate subsequently the profit center document. You should implement Note 118533 in these releases beforehand to make sure that the online document flow from HR to PCA works.
A summarization using the Profit center field should definitely not be carried out in Releases 4.0A and 4.0B if the online update to Profit Center Accounting has not been activated in the fiscal year or if it should be activated subsequently (mid-year).
Header Data
Release Status: Released for Customer
Released on: 11.10.2007 08:21:39
Priority: Correction with medium priority
Category: Customizing
Primary Component: FI Financial Accounting
Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_APPL 30 300 31H
SAP_APPL 40 40A 40A
SAP_APPL 45 45A 45A
SAP_APPL 46 46A 46A
SAP_APPL 470 470 470
SAP_APPL 500 500 500
SAP_APPL 600 600 600
Highest Implemented Support Package
Support
Packages Release Package
Name
SAP_APPL 40B SAPKH40B28
SAP_APPL 45B SAPKH45B09
SAP_APPL 46B SAPKH46B01
SAP_HR 40B SAPKE40B28
Related Notes -
Incoming Payment - Posting more than 999 line items through EDI
Hi guys,
I having following issues.
1. incoming 820 is not posting into customer a/c even I configured processing - REMC but creating payment advice
2. once i tried to process payment advice by using f-28 it is posting in to custmer a/c without payment advice ref. also the payment advice still exist in the system.
3. trying to post payment advice having more than 999 items by using f-28 system shows error after 999 items.
4. I tried to process payment advice executing through RFAVIS40 error displays "Payment advice note in Customizing not defined for posting"
I appreciate if some one guide me to solve above.
Thanks,
RK
Message was edited by: RK TalabathulaHi RK,
Pt 3: There is an SAP Notes on this issue 117708 ,
also refer Re: F-44 - Clearing of more than 999 line items
Pt 4: Check OSS note 17449 see for "Payment
advice upon form overflow"
hope this helps.
Please assign points as way to say thanks
Ravi Rana -
More than 999 line items in Invoice
Hi All,
We are having a scenario where more than 999 line items needs to be invoiced in a single billing document. If more than 999 line items are invocied in a single billing document, system can not post the acct document. Our requirement is to create single billing doc for more than 999 and post acct document also successfully.
Please advise if any one has worked on the simillar issue.
Thanks,
RaviHi,
You can not do that with 999 line items in one billing document, the reason is the line items limit in the accounting document, because one line item of billing document must generate two line items (D&C) in the accounting document, although you can maintain the max 999 line items in billing document, but actually the max line items of billing document is 499.
So the other line items more 499 must be generate in a new billing document! Hope can help you understand the scenario.
Regards
Tao -
Need some help on workaround for more than 999 line items in a FI document
Hi all,
user would like to know if there is any way to increase the maximum # of lines for an FI document. Currently, as SAP only allows 999 lines per FI document. The user is encountering an issue when a taxable invoice is uploaded because SAP creates additonal lines for the taxes thereby increasing the line item count beyond the 999 limit. This causes the user to separate out the upload files into several different files which is very time consuming. i have read some replies from previous questions posted on this but none were clear enough on how to actually split the lines and what will happen after the split to the rest of the line items how is the continuation with the first document. can some one give me the explanation or steps on how we can do the split on this document please. we are on 4.6c version. if we have to write some code, what should i explain to the abaper? any kind of inputs would be greatly appreciable.
Thanks in Advance
JayHi,
From your comments, I understand that you are uploading the journals. The steps to handle 999 line items limitation is through functional and technical help.
1. create a dummy GL account
2. In the code, ask the abaper to have a logic such that if more than 900 lineitems (dont check for 999, as some auto postings will be done), then the balance should be loaded to the dummy GL account created and a document should be posted
3. Start reading the remaining docs and follow the same logic as in 2 and ensure that the posting happened in step 2 against dummy GL account should have reversal posting. That is, if step 2 dummy GL account has a credit balance then in step 3 against the same amount a debit entry for the GL account should be posted.
This will ensure that once all the line items are posted, the balance in dummy GL is Zero.
Regards,
Sridevi -
Final total cannot appear when the last line item reached the page end
Hi All,
My report included 2 pages. Problem is the final total cannot appear when the last line item reached the page end. (page 2)
final total will appear on the middle of last page (page 3) when i comment (type = 'BOTTOM').
Below is the program.
CALL FUNCTION 'OPEN_FORM'
EXPORTING
device = 'PRINTER'
dialog = 'X'
form = 'ZBOTM_VOUCHER'
language = sy-langu.
sort itab by vblnr.
LOOP AT itab INTO wa_itab.
move wa_itab-vblnr to reguh-vblnr.
move wa_itab-lifnr to reguh-lifnr.
move wa_itab-rbetr to reguh-rbetr.
reguh-rbetr = reguh-rbetr * -1.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
window = 'MAIN'
element = 'DETAIL'.
t_rbetr = reguh-rbetr + t_rbetr.
AT LAST.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
window = 'LINE'.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
element = 'TOTAL'.
type = 'BOTTOM'
WINDOW = 'MAIN'.
ENDAT.
Thanks.Hi,
Where should I include the code for bottom?
How to open text editor?
Thanks.
Edited by: Alice8 on Feb 7, 2011 9:09 AM -
While clearing document has more than 999 line items system not allowing
Hi,
We have an issue with FI-Customer Clearing. While clearing the error is appearing as document has more than 999 line items. after the detailed checking we found that there are lots of line items posted to Real Exchange Rate diff that to COPA.
To reduce the maximum line items SAP is suggesting to deactivate the Real exchange rate diff.postings to COPA.
Regards,
R.Kumar.Hi,
Please check SAP Note 1353125
Thanks -
F-44 - Clearing of more than 999 line items
Hi,
I am using transaction code F-44 for clearing vendor line items but vendor line items are more than 999 (In fact they are well above 65000) SAP does not allow postings in a single doc of more than 999 line items.
can someone suggest methe procedure of doing this in a batch?? If so, please specify the procedure and transaction code.
Thanks in advanceHi rajesh,
There is an SAP Notes on this issue <b>117708</b>
Please Read the link below:
Posting document with more than 999 items
Also:
Table inserting 999 recorgs
Hope this helps.
Please assign points as way to say thanks. -
Morethan 999 line items for vendor invoices
Hi All,
we had issue for an Invoice upload.
we are uploading the Invoice contains morethan 999 line items. but we are facing error for morethn 999 line items can't post when uploading thorugh ZFB60 transaction.
please advise if any SAP notes are exist or any idea.
Thanks and regards
Prathap
< Please search. >Hi,
What error you are getting? Can you tell me clearly....
Regards,
Mohan. -
More than 999 line items for an FI Document
Hello All,
Per SAP standard, an accounting document can only contain up to 999 line items. However, we have Logistics posting (Backflush) that would yield more than 999 line items in FI. We can't opt for setting summarization in transaction OBCY (FI Summarization based on Object Type) since this would affect GR/IR clearing. We can select reference transaction key MKPF (Material Doc Table) and table BSEG (Field MENGE <Qty>) but GR/IR clearing would be affected since definition of clearing is at Purchasing Doc (EBELN) and Item (EBELP).
Do you have other recommendations?
Thanks.Dear scorpio0485,
Yes ! I have already done posting for morethan 999 line items. but in the standard program we cant do it. We need to go for Z process.
In Zprocess we need to put one cut off line item for ex : 900 or 950. After that hardcode one GL code(clearing GL Code) in program to split the line items. Means the system generates 2 documents.
Please give the following Code to ABAPer
AT END OF xblnr.
mtab[] = ttab[].
CLEAR v_count1.
DESCRIBE TABLE ttab LINES v_lines.
LOOP AT ttab INTO wa_ttab.
v_tabix = sy-tabix.
v_count = v_count + 1.
IF v_count EQ 900.
count = count + 1.
v_count1 = v_count + v_count1.
MOVE-CORRESPONDING wa_ttab TO wa_xtab.
IF v_wtotal < 0.
wa_xtab-newbs = '40'.
wa_xtab-newko = '00003100001'.
ELSE.
wa_xtab-newbs = '50'.
wa_xtab-newko = '00003100001'.
ENDIF.
IF v_dtotal < 0.
wa_xtab-newbs = '40'.
wa_xtab-newko = '0003100001'.
ELSE.
wa_xtab-newbs = '50'.
wa_xtab-newko = '0003100001'.
ENDIF.
IF v_dtotal LE 0.
v_dtotal = v_dtotal * -1.
ENDIF.
IF v_wtotal LE 0.
v_wtotal = v_wtotal * -1.
ENDIF.
wa_xtab-prctr = '0000900008'.
wa_xtab-dmbtr = v_dtotal .
wa_xtab-wrbtr = v_wtotal .
If you need anymore,please let us know -
J1INCHLN posting Error: a maximum of 999 line items are allowed
The local currency of the company code is INR and the the 2. local currency is EUR (Group currency)
When we pay withholding tax (T_Code=J1INCHLN) for a particular months it clears all open items for that month.
After simulation of TDS a/c with various posting dates , it calculates exchange fluctuation gain/loss for group currencies. As a result exchange rate gain and loss accounts are automatically posted compared with each open item posting dates and the posting dates for this transaction.
If there are average 10 business Areas and 25 posting dates with 4 TDS G/L accounts
it has to be crossed more than 999 line items.
Is there a slolution for this problem?
How can we avaoid this problem?
Your replies are mostly appreciated
ThanksHi,
the field for cheque no. assignment is not available in payment screen J1INCHLN, we need to assign the cheque no with T_Code:FCH5 after the document posted. Once we assign one cheque number to a particular document No1.,that cheque no will not be available to assign to another document no2 as it has been already assigned in doc1.
Looking forward to your solution proposals?
How indian companies solve this problem?
BR Tarik -
Hi experts,
I have one validation its like suppose if u have 999 line items then that record should b closed and the both +ve, -ve values should be equal to 0 n new record should start again.
if any body can help me in this regard then i will b thankful to them.
Regards
BohraBecause there may be automatic entries created, you shouldn't go to 999 entries. It should be OK to use 950.
Let's say you have 1100 entries. the first 950 total 10,000 credit. You create the first transaction with 950 entries and then an entry to a control account for 10,000 debit. Then another transaction with the remaining 150 entries and an entry to the same control account for 10,000 credit.
Rob -
+ 999 line items invoice posting in MM
Hi,
How can you manage +999 line items invoices in MM?
Now those invoices are treated in FI, using a program developed that allows the system to split the document in smaller ones, but in the future we want to post them using MM.
There is someone who find a solution to that? Which are best practice in this topic?
thks!
Edited by: Csaba Szommer on Jan 14, 2012 6:19 PMThe invoice was successfully posted. I have done 2 thing:
1) I got implemented User Exit: EXIT_SAPLMRMH_011 in Enhancement: MRMH0002
2) Maintained Transaction VS5 and G/L account no. for relevent chart of accounts in R/3 table T030K. -
Hi,
if we post an invoice in MIRO that contain over than 999 lines items we have a message who block the save.
so what is the path IMG with which i can make modification to have for any account (when i do simulate) one line item (so the total) ?
i hope your help
best regardsHi Johan,
i want not to have possibility for more than 999 lines.
when we do simulate in MIRO, we have the accounts used to post the invoice. for any line item in MIRO we have 3 or 4 accounts to post it (we have a lot of repeated accounts) , so i want to sumup similar accounts and don't have repetition. as result we will have few lines item.
split the invoice is a solution to post invoice that have more than 999 lines but i want the path IMG with which i can make modification to have for any account (when i do simulate) one line item (so the total).
best regards -
Hi
We are running a batch program for Billing through SD(with 12000 line items),Program is running successfully and creating the sales document but failed in creating FI documents with the error"maximum line item can be 999" only.Is there any way to handle this OTHER THAN SPLITTING AND POSTING.
thanks.
henfiHI,
The most commonly used workarounds are as follows:
1) Implement FI summarization (per note 36353).
2) Cancel the original billing document and split it into smaller documents using different payment terms but actually with the same terms.
This will avoid the (999) line item limit for FI postings.
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=11162
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=111813
with reference to invoice splitting.
Regards
Ravinagh Boni
Rewards me if it useful
Maybe you are looking for
-
Can no longer send or receive messages on Mac from non-Apple product users
After installing Yosemite, I was able to send and receive messages to contacts who use Android devices, but that stopped a week ago. Anyone else having this problem?
-
Is there any way to overclock an A64 by adjusting the multiplier?
Is there any way to overclock an A64 by adjusting the multiplier? I have an Athlon64 3200+ (Socket 754) and a MSI K8T Neo-FIS2R. Seems to be a sweet overclocker, but my RAM cannot run at much more than the normal 200 (400) MHz, so FSB overclocking is
-
Come posso utilizzare un Ipad2 usando imac con OSX10.4.11? Esiste itunes installabile sul mio OS e compatibile con Ipad?
-
hi., i need fully TAXINN document.(from top to bottom configuration document) can u send to me ? Very Urgent.
-
How do I get Flash Builder to run the last configuration that was run? I have multiple projects open that aren't runnable but when I click on the run button it always tries to launch the project that is selected. How do I get around this? I set th