Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this WIKI is to explain a system limitation which does not allow you to have more than 999 line items per FI document, and also provide you with workarounds you can use to post your document.

Overview

When you are posting an FI document which has more than 999 line items, the system will issue an error message. This is due to the fact that the line item number field (BUZEI) in the BSEG table consists of 3 characters only and therefore the system cannot read more than 999 line items in the FI document. There are some workarounds which can be done so that your document will be successfully posted in the system. 

Well, if for postings with FI posting transactions like FB01, FB60, FB70, FB50, FB05, F-30, FBZ1, F-28, FBZ2, F-53, FB1S, F-03 etc. the maximum number of 999 line items in an FI document is exceeded, error F5 734 is raised. If for postings via the accounting interface (is processed for postings from other modules like from module MM, SD, etc., for postings via accounting BAPIs, Direct Input, IDOC) the maximum number of 999 line items in an FI document is exceeded, a different error F5 727 is raised, but conveys a similar meaning. Another error F5 807 is raised if for postings via the accounting interface (is processed for postings from other modules like from module MM, SD,etc., for postings via accounting BAPIs, Direct Input, IDOC) the maximum number of 999 entries for an FI document in VAT tax database table BSET is exceeded. For postings with FI posting transactions like FB01, FB60, FB70, FB50, FB05, F-30, FBZ1, F-28, FBZ2, F-53, FB1S, F-03 etc. an automatic split is NOT available so far, and most probably will not be available in future either. 

System Limitation

The FI document has more than 999 lines, the system issues error F5 807 ("Number of items in document is too large") or F5 727 ("Maximum number of items in FI reached"), and posting is not possible.

There are no immediate plans to expand the number of line items beyond the current limit (999 lines per document). This is because the line item number (BSEG-BUZEI) field length is defined as 3 numeric positions (leading to a maximum possible number of 999 line items). The SAP development group is aware of this functionality change request, but the change is significant since BSEG is a cluster table which is used in numerous R/3 programs.

Some common transactions where you may experience this issue are: VF01, VF02, VF04, MB01, MB11, MR1M, CO15, MIGO, MB01, MB1A, MB1C, MBST, VL01N, VL02N, VL09

The limitation is still valid, because in ACDOCA, the line item number can have more than 1000 (ACDOCA has provisions for 6 digit line item numbers) but BSEG is still update from all classical FI posting. So you cannot input more than 999 items.

Please read the KBA:
2344521 - F5 727- after migration Simple Finance or S/4 HANA

Solution

There are three ways to resolve the 999:

1) Summarization - as per note 36353.Please be aware that Summarization is only possible for transactions which post via the FI/CO interface. A summarization within Financial Accounting (for example, FB01) does not occur. This is as per SAP Note 166487.

2) Split the document  - Cancel the original document and split it into smaller documents using different payment terms but actually with the same terms.

3) Split  -  Note 103334 will force a delivery split in collective processing if the source order exceeds the item number limit.

•  Goods Movement: Note 1353827
•  Incomming invoices (MM): Notes 1353125 and 1497092
•  Outgoing invoices (SD/CRM): Note 1670486
•  Vendor invoices: Note 1588529

OBSERVATION:

If a goods movement posting to accounting is triggered from the MM module which would result in an FI document with more than 999 line items, the system issues error F5 727 ("Maximum number of items in FI reached") and the posting is not possible. For this, note "1353827 - AC interface: Document split in FI for goods movements" was released. This note makes the system execute an automatic document split in FI for goods movement postings with more than 999 line items. Please keep in mind that this note works only for goods movement.

Related Content

Below you can find some other important notes:

  • 2078335 - FAQ: Error F5 727 when posting via Accounting Interface
  • 1497092 - AC interface: Posting split in FI for incoming invoices
  • 1675235 - Error message F5727 "Maximum number of items in FI reached" when release SD billing document to accounting
  • 1801529 -Error message F5727 "Maximum number of items in FI reached" when release MM doc

Related Documents

Related Notes

SAP NOTE 36353*: *AC interface: Summarizing FI documents

SAP NOTE 103334: Error F5 807 in GI - split deliveries that are too large

SAP NOTE 1353827: AC interface: Document split in FI for goods movements

SAP Note 166487 : TABLE_INVALID_INDEX in FI/CO interface

9 Comments

  1. Former Member

    Hi Marcelo, There looks to be no standard way to resolve this issue. On the other hand, I could see that you have mentioned about FI Summarization as one of the option. However, the SAP Note 166487 states that Summarization is only possible for transactions which are posted via the FI/CO interface. A summarization within Financial Accounting (for example, FB01) does not occur. I suppose, if this condition is mentioned in the 'Purpose' section of this Wiki, the page would be complete. Anyways, I included few more facts with regard to the information you want to convey. Please let me know in case it is objectionable. Thanks.

  2. Former Member

    As a consultant, I have met this limit at several customers and the workarounds do not provide a sufficient solution.

    Could this be the case for an ASUG influence group?

  3. Former Member

    Hello Marcelo,

    There is one more message FF 755 - Maximum permitted number of internal tax items  reached this error comes when this BAPI posting happens. The actual error is similar to the 999 line items. BAPI_ACC_GL_POSTING_POST is used - just would like to know any note is available to address the issue given above also.

     

  4. Former Member

    Hi Krishnan,

    We are also facing the same issue with error FF 755, can you please let me know if these is any solution for this issue.

    Regards,

    Hari Babu

     

     

  5. Former Member

    Hi everybody,

    I have some great news. As you may have heard, SAP's development team has developed Simple Finance.

    In the process, they have removed the 999 line items limitation. 

    Of course, this requires the upgrade to Simple Finance or S/4-HANA, but it could be worth it for several companies struggling with this issue.
    Also, you may not need to upgrade your whole environment if you choose the Central Journal route, as described here:
    http://scn.sap.com/community/epm/financial-excellence/blog/2015/04/01/deployment-scenarios-for-simple-finance-as-central-journal-it-depends

    Let me know if you have additional questions. 

    1. Well...  they 'removed' it by increasing the line item counter from 3 to 6 digits.  There is still a technical limitation though I doubt it will prove to be a legitimate design or functional issue.

      1. Nathan - do you know how this works technically? I'm playing around in an S/4 system and this question has come up. I noted that I did not think there was any 999 limit as in prior ECC versions. I have not tried to manually post >999 line items but I do notice that ACDOCA has provisions for 6 digit line item numbers as you mentioned...but BSEG, etc. is still populated and those tables still only have the 3 digit BUZEI field. Curious.

        1. The line item field in ACDOCA is 6 CHAR, however BSEG is still populated in many scenarios and they didn't change the technical definition of BSEG.  The end result is that the 999 limitation still exists but that's not the case 100% of the time; only when BSEG is updated.

          1. Former Member

            Nathan et al - Any idea when BSEG is not updated in S/4HANA and only ACDOCA gets updated? I am aware that certain scenario like FOREX valuation goes in ACDOCA and not in BSEG but do we have a comprehensive list of such scenarios?