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

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

Similar Messages

  • 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 Talabathula

    Hi 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

  • 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 advance

    Hi 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.

  • 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

  • How to upload a file which has more than 999 line item  through BDC ?

    Hello Techards
    Hi to all
    Can any body tell me how to upload a file which has more than 999 line item  through BDC for traction F-02 ?
    Thanks in advance.
    Shovan

    Hello Shovan,
    You split it up to post two accounting documents with the help of a "suspense" a/c.
    Say, you have to post the following line items below:
    line 1 - dr. - GL a/c X - $1000
    line 2 - cr. - GL a/c Y - $1
    line 3 - cr. - GL a/c Y - $1
    line 1001 - cr. - GL a/c Y - $1
    You cannot post the above as a single doc in SAP (because of technical reasons), so you need to break it up into 2 documents as below:
    Doc1
    line 1 - dr - GL a/c X - $1000
    line 2 - cr - GL a/c Y - $1
    line 3 - cr - GL a/c Y - $1
    line 998 - cr - GL a/c Y - $1
    line 999 - cr - SUSPENSE a/c - $3
    Doc2
    line 1 - dr - SUSPENSE a/c - $3
    line 2 - cr - GL a/c Y - $3
    Note that there is no incorrect impact on accounting as first we credit suspense a/c by $3 and next we debit the same suspense a/c by $3 as a result the effect is nil. Similarly, we credit $997 to GL a/c Y (which is less by $3) in the first doc which is compensated by the second doc by crediting the shortfall of $3.
    Hope this helps,
    Cheers,
    Sougata.

  • Document split of a paymnt doc. for an invoice wit more than 999 line items

    Hi all,
    my question is . what steps should we take care of in the system, to make the the document Split automatically on a payment document when we post an Invoice with 1001 lines items in it. is it some thing in the config or do we need to update a table or???
    any kind of Input would be really appreciable, as i know this would be the same problem with all other clients too. who ever has more than 999 lineitems on their invoices.
    thanks in advance
    Jay

    The only option is to create a clearing account and post this first entry to this temporary account and in the second entry clear this temporary and complete the transaction posting. Example:
    Entry 1
    Account 1   Dr.  Line 1                        100
    Account 2  Dr   Line 2                          100
    Account 3  Dr.  Line 998                       100
    999 split Account  Cr.                                           300
    Entry 2
    999 split Account Dr.  300
    Account 4    Dr.  Line 1000        100
    Account 5    Dr.  Line 1001          100
    Account 6                        Cr.           500
    It is generally advised to split the transaction after 900 lines if document split is active in your client. Hope this helps. The same logic could be used for all interfaces and ABAP programes.

  • 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
    Jay

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

  • Can we have more than 999 line items in new gl document

    HI
    Can we have more than 999 in new gl document. we are using ecc 6.0. does new gl support this functionality. plz help
    thanks,

    Hi,
    Please check this thread https://forums.sdn.sap.com/click.jspa?searchID=3767300&messageID=3565908
    In NewGL, there's a functionality called "document split". For example if there's one customer line item without business are assignment and 2 offsetting sales items have business area A and B, then the customer line item gets divided into 2 lines with business area A and B automatically on NewGL document. That's why the system must allow more than 999 items in NewGL.
    BUT !!! The limitation on BSEG still exists as I mentioned. This means all documents created from external modules SD, MM, IDoc etc.. (also FI) still can not exceed 999 items when the data gets passed to FI.
    The workaround of reducing the number of items is available by summarization. Note 36353, 310837 explains this functionality.
    Please assign points if it useful.
    Regards
    Ravinagh Boni

  • More than 1000 Line items

    Hi
    User has done the billing for 1300  line items by using transaction code VF01. After completing that process there is a option TO release Accounting, when user select on that button system throwing an error "Maximum number of items in FI
    reached".
    We know that from FI side system will not allow more than 999 line items. Since we are using 4.7 version.
    Invoice have already send to the customer. So, How to solve this issue.
    Please provide me the solution as early as possible.
    Your help would really appreciated.
    Regards,
    Schilukuri

    Hi to everyone,
    My issue has been resolved.
    My requirement is User has done billing (VF01) for more than 1000 line items. After that he was doing that billing document to release to accounting. That time system was throwing an error message." Maximum number of items in FI
    reached"
    Solution:
    Use Transaction OBCY and give work area VBRK  and there you have to give Table name BSEG and give Field name whichever the fields you want to give to group the same line items.(Document may have some same line items).
    refer SAP Note:36353.
    Regards,
    Schilukuri

  • Billing document containing more than 999+ lines

    HI experts,
    If we have to post a billing document containing more than 999+ lines, what would be the configuration in SD so that the billing document can be divided in two documents and reconciliation can happen at later.
    rewards ensured
    Monti

    Dear monti
    You can do so. Follow the IMG Path --> SD --> Billing -> Billing Docs -> Country specific features --> Maintain maximum number of Billing items.
    Here whatever numeric value you assign to sales organization, all your invoices be restricted to that value.  Supposing, if you give 10 there, all your invoices will have ONLY 10 line items and if the delivery has more than that, there will be an invoice split.
    Thanks
    G. Lakshmipathi

  • Problem in CRM_ORDER_MAINTAIN for updating qty in more than 1 line item .

    Hi abapers,
    I am using BAPI CRM_ORDER_MAINTAIN to update quantity. Its updating the quantity properly if there is single line item for a transaction .If more than 1 line item is there then its throwing an exception* "Document is being distributed - changes are not possible"*.
    Scenario:
    I have a itab  which is having 2 line items for a transaction. i run a loop pass the pass the required parameters in CRM_ORDER_MAINTAIN ,do CRM_ORDER_SAVE , BAPI_TRANSACTION_COMMIT for the 1st line item. When i run the 2nd loop, in  CRM_ORDER_MAINTAIN it gives an exception saying NO_CHANGE_ALLOWED for the same transactions 2nd line item. leaving the quantity unchanged for both the line items. What may be the problem?
    Note: We cannot say how many line items are there for an transaction. so no chance of grouping all items at a time and saving at a time.
    Regards,
    Navin

    Hi Navin,
    Why its not possible to use CRM_ORDER_SAVE only once. I think its possible. Call CRM_ORDER_MAINTAIN in loop for all the line item in transaction and after that call CRM_ORDER_SAVE once. Pls follow the below sample code.
    loop at it_item.
    call CRM_ORDER_MAINTAIN. (Here append data for all the line items and miantin the transaction).
    emdloop.
    After endloop call CRM_ORDER_SAVE. Also you can add some wait after CRM_ORDER_SAVE, In order to avoid locking issue.
    PLs let me know where you are trying to use CRM_ORDER_MAINATIAN ? In any BADI or Z program ?
    Regards,
    Amol.

  • More than 1 line items in bdc using table controls for BOM

    Hi....
    how do u update more than one line item for BOM using BDC table control.......
    is there any specific command for doing that.......
    hav tried d following code bt it takes the flatfile i/p FOR 2 LINE ITEMS as 2 different BOM'S.....
    would appreciate ur help....plz provide code.............
    REPORT zbdc4_cs01
           NO STANDARD PAGE HEADING LINE-SIZE 255.
    INCLUDE bdcrecx1.
    DATA : a TYPE i,
           b type i,
           c type i.
    DATA : BEGIN OF it_rec OCCURS 0,
           rec(200) TYPE c,
           END OF it_rec.
    DATA : BEGIN OF ctab OCCURS 0,
           matnr(18),
           werks(4),
           stlan(1),
           END OF ctab.
    DATA : BEGIN OF xtab OCCURS 0,
           idnrk(18),
           menge(13),
           postp(1),
           END OF xtab.
    DATA : BEGIN OF itab OCCURS 0,
           matnr(18),
           werks(4),
           stlan(1),
           idnrk(18),
           menge(13),
           postp(1),
           END OF itab.
    START-OF-SELECTION.
      CALL FUNCTION 'GUI_UPLOAD'
        EXPORTING
          filename            = 'C:/TEST4.TXT'
          filetype            = 'ASC'
          has_field_separator = 'X'
        TABLES
          data_tab            = it_rec.
      LOOP AT  it_rec.
        a = strlen( it_rec-rec ).
        if a = 55.
        itab-matnr = it_rec-rec+0(18).
        itab-werks = it_rec-rec+18(4).
        itab-stlan = it_rec-rec+22(1).
        itab-idnrk = it_rec-rec+23(18).
        itab-menge = it_rec-rec+41(13).
        itab-postp = it_rec-rec+54(1).
        APPEND itab.
        elseif a > 55.
        itab-matnr = it_rec-rec+0(18).
        itab-werks = it_rec-rec+18(4).
        itab-stlan = it_rec-rec+22(1).
        itab-idnrk = it_rec-rec+23(18).
        itab-menge = it_rec-rec+41(13).
        itab-postp = it_rec-rec+54(1).
        APPEND itab.
        itab-idnrk = it_rec-rec+55(18).
        itab-menge = it_rec-rec+73(13).
        itab-postp = it_rec-rec+86(1).
        APPEND itab.
        endif.
      ENDLOOP.
      PERFORM open_group.
      LOOP AT itab.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0100'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29N-STLAN'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'RC29N-MATNR'
                                       itab-matnr.           "'3000000107'.
        PERFORM bdc_field       USING 'RC29N-WERKS'
                                       itab-werks.              "'UN02'.
        PERFORM bdc_field       USING 'RC29N-STLAN'
                                       itab-stlan.              "'1'.
        PERFORM bdc_field       USING 'RC29N-STLAL'
        PERFORM bdc_field       USING 'RC29N-DATUV'
                                      '11.08.2008'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0110'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'RC29K-BMENG'
                                      '1'.
        PERFORM bdc_field       USING 'RC29K-STLST'
                                      '1'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29K-EXSTL'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0111'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29K-LABOR'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0140'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POSTP(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'RC29P-IDNRK(01)'
                                       itab-idnrk.             "'1000000232'.
        PERFORM bdc_field       USING 'RC29P-MENGE(01)'
                                       itab-menge.              "'100'.
        PERFORM bdc_field       USING 'RC29P-POSTP(01)'
                                       itab-postp.             "'L'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0130'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POSNR'.
        PERFORM bdc_field       USING 'RC29P-POSNR'
                                      '0010'.
        PERFORM bdc_field       USING 'RC29P-IDNRK'
                                      '1000000232'.
        PERFORM bdc_field       USING 'RC29P-MENGE'
                                      '100'.
        PERFORM bdc_field       USING 'RC29P-MEINS'
                                      'KG'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0131'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POTX1'.
        PERFORM bdc_field       USING 'RC29P-SANKA'
                                      'X'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0140'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POSNR(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_dynpro      USING 'SAPLCSDI' '0140'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RC29P-POSNR(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=FCBU'.
        PERFORM bdc_transaction USING 'CS01'.
      ENDLOOP.
      PERFORM close_group.

    Hi
    Check this sample code for the Table Control in BDC:
    data: fnam(20) type c.
    move 1 to id.
        loop at TI_STAGING WHERE VENDOR = IT_STAGING-VENDOR AND DOCDATE = IT_STAGING-DOCDATE.
          concatenate 'RM06E-EPSTP(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-itmcategory.
          concatenate 'EKPO-KNTTP(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-accassignment.
          concatenate 'EKPO-EMATN(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-material.
          concatenate 'EKPO-TXZ01(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-shortxt.
          quan = ti_staging-poqty.
          concatenate 'EKPO-MENGE(0' id ')' into fnam.
          perform bdc_field       using fnam quan.
          concatenate 'RM06E-EEIND(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-deliverydate.
          netpr = ti_staging-netpr.
          concatenate 'EKPO-NETPR(0' id ')' into fnam.
          perform bdc_field       using fnam netpr.
          concatenate 'EKPO-MATKL(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-mategroup.
          concatenate 'EKPO-WERKS(0' id ')' into fnam.
          perform bdc_field       using fnam TI_STAGING-plant.
          ID = ID + 1.
        ENDLOOP.
    Regards,
    Vishwa.

  • GL account balance splitting in more than one line item in FSV

    Friends,
    While going through the FSV, gl account balance is splitting in more than one line item with same account name.  But if we total the line items ultimately it is tallying with GL balance.  What might be the reason.  Why it is splitting the balance in more line items with same name and same account number.

    Dear,
    You might be having Document Splitting Activation.with Bussiness Area/ Segment wise/Profit Center Wise. For this please Check - Path > Spro > SAP reference IMG > Financial Accounting (New) > General Ledger Accounting (New) > Business transactions > Document Splitting > Define Document Splitting Characteristics for General Ledger Accounting.
    Please go through this & will  be able see the Document Splitting is based on Bussiness Area/ Segment wise/Profit Center wise or may be both.
    T & R,
    Madhuri Panda

  • BAPI_PR_CHANGE (Not Able to insert more than 3 Line Items)

    Hi Friends,
    I have Issue with BAPI_PR_CHANGE.
    I could Able to insert up to 3 lines items using this BAPI but if I am Trying to Insert More Than 3 BAPI throwing Dump.
    Any Idea on this?
    Any Parameter I need to pass for more than 3 line items.
    Let me know any help on this BAPI...I am on ecc 6.0.
    Thanks,
    Yogesh Patil

    We are on ECC 6.0 and have no problems creating a PR with 100+ line items or adding multiple lines to a existing PR . Please paste the first page of the dump to help me answer your question.
    Thanks,
    Raj

Maybe you are looking for