1000 Line items

Hi Gurus
My client requirement is in such a way that the order may include more than 999 line items.
while in standard we can go upto 999 only. So how to incorporate this.
Thanks in advance

Dear Friend
First of all you can not give 999 line items in one sales order
You can only give 499 line items in one sales document The reason behind this is that one FI document can have only 999 line items and for every line item in sales there will be 1 Debit and 1 Credit Entry
So you can only go for 499 line items in one Sales Document
Now regarding modification, its not possible.
Regards
Vishal

Similar Messages

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

How to improve performance on SD document with over 1000 line items

Dear experts,
A lot of our SD document contains 1500 to 5000 line items. Saving a simple change of one line item description would take 5 minutes (with or without pricing considerations). We are on ECC 5.0. Does anyone know of an existing snote or ways that would help to improve performance?
A related question on performance tracing. I have done some tracing and notice that the time to access SQL/buffer/enqueue/RFC only amount to less than 50% (sometimes 5%) of the total processing time. What has the system been doing for the "unrecorded" time?
Thank you and appreciate!
-cynthia

I would check which modules or which parts of code take the most of the processing time. You can use SE30 to check one order save.
If it's not SQL - then it may be internal processing like inefficient loops and so on. For example runtime of nested loops with big tables have grows exponentially.
It may be caused by SAP code - search OSS notes for based on the module names which consume most time.
OR it can be caused by the code in your userexits - then developers have to fix it and redesign using more efficient technique.

ABAP Question- line item transfer from one customer to another

Dear SAP Guru's-
I have a hot issue so any help would be greatly appreciate.
I have a customer that needs to move open A/R line items to one payer to another and without using F-30 or F-21, I recall seeing a program or t-code that gave one the ability to move the line items from one customer to another by selecting all line items or listing specific document numbers. Does anyone know what I am talking about?
If so, does anyone have any information that could share with me so that I can do it or any documentation to start me in the right direction?
POINTS PROMISED

Thank you Murali and Sunil
These t-codes are not helpful and tideous if you have many like a 1000 line items. In addition, you lose the history, the due date information and the document type change for invoices, etc.
I KNOW I saw something that moved all or selected items by document number from one customer to another. It was called payer to payer transfer. I cannot find any information on it.
Any help or more input, more points awarded.
THANKS!

999 line items

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
venu

Hi
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

BDC for LINE Item

hi abaper's
i have to do BDC for vendor line item i have 250 vendor and 1000 line item for these vendor
so please tell me the procedure.
thanks
pardeep

Hi,
Check the sample code.
REPORT YJAR_VENDOR_INBOUND02 NO STANDARD PAGE HEADING LINE-SIZE 255
MESSAGE-ID ZABC.
STRUCTURE DEFINITIONS :
TYPES : BEGIN OF TY_SOURCE ,
LIFNR TYPE LIF16 ,
BUKRS TYPE BUKRS ,
EKORG TYPE EKORG ,
KTOKK TYPE KTOKK ,
NAME1 TYPE AD_NAME1 ,
SORTL TYPE AD_SORT1 ,
LAND1 TYPE LAND1 ,
BANKS TYPE BANKS ,
BANKL TYPE BANKK ,
BANKN TYPE BANKN ,
AKONT TYPE AKONT ,
FDGRV TYPE FDGRV ,
WAERS TYPE BSTWA ,
END OF TY_SOURCE ,
BEGIN OF TY_HEADER ,
LIFNR TYPE LIF16 ,
BUKRS TYPE BUKRS ,
EKORG TYPE EKORG ,
KTOKK TYPE KTOKK ,
NAME1 TYPE AD_NAME1 ,
SORTL TYPE AD_SORT1 ,
LAND1 TYPE LAND1 ,
AKONT TYPE AKONT ,
FDGRV TYPE FDGRV ,
WAERS TYPE BSTWA ,
END OF TY_HEADER ,
BEGIN OF TY_ITEM ,
LIFNR TYPE LIF16 ,
BANKS TYPE BANKS ,
BANKL TYPE BANKK ,
BANKN TYPE BANKN ,
END OF TY_ITEM .
INTERNAL TABLE AND WORK AREA DEFINITIONS :
DATA : T_SOURCE TYPE STANDARD TABLE OF TY_SOURCE INITIAL SIZE 1 ,
W_SOURCE TYPE TY_SOURCE ,
W_SOURCE1 TYPE TY_SOURCE ,
T_TARGET TYPE STANDARD TABLE OF BDCDATA INITIAL SIZE 1 ,
W_TARGET TYPE BDCDATA ,
T_HEADER TYPE STANDARD TABLE OF TY_HEADER INITIAL SIZE 1 ,
W_HEADER TYPE TY_HEADER ,
T_ITEM TYPE STANDARD TABLE OF TY_ITEM INITIAL SIZE 1 ,
W_ITEM TYPE TY_ITEM ,
I(2) TYPE C ,
FNAM(20) .
UPLOADING FLATFILE TO SOURCE INTERNAL TABLE :
PERFORM SUB_UPLOAD_FLATFILE.
PERFORM SUB_SPLIT_DATA.
*include bdcrecx1.
*start-of-selection.
*perform open_group.
LOOP AT T_HEADER INTO W_HEADER .
REFRESH T_TARGET .
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0100'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'RF02K-KTOKK'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
PERFORM BDC_FIELD USING 'RF02K-LIFNR' W_HEADER-LIFNR.
PERFORM BDC_FIELD USING 'RF02K-BUKRS' W_HEADER-BUKRS.
PERFORM BDC_FIELD USING 'RF02K-EKORG' W_HEADER-EKORG.
PERFORM BDC_FIELD USING 'RF02K-KTOKK' W_HEADER-KTOKK.
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0110'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'LFA1-LAND1'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
PERFORM BDC_FIELD USING 'LFA1-NAME1' W_HEADER-NAME1.
PERFORM BDC_FIELD USING 'LFA1-SORTL' W_HEADER-SORTL.
PERFORM BDC_FIELD USING 'LFA1-LAND1' W_HEADER-LAND1.
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0120'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'LFA1-KUNNR'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0130'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'LFBK-BANKL(02)'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'ENTR'.
I = '01' .
LOOP AT T_ITEM INTO W_ITEM WHERE LIFNR = W_HEADER-LIFNR .
CONCATENATE 'LFBK-BANKS(' I ')' INTO FNAM .
PERFORM BDC_FIELD USING FNAM W_ITEM-BANKS.
CONCATENATE 'LFBK-BANKL(' I ')' INTO FNAM .
PERFORM BDC_FIELD USING FNAM W_ITEM-BANKL.
CONCATENATE 'LFBK-BANKN(' I ')' INTO FNAM .
PERFORM BDC_FIELD USING FNAM W_ITEM-BANKN.
I = I + 1 .
IF I GT 5 .
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0130'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'LFBK-BANKS(01)'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' 'P+'.
I = '01'.
ENDIF.
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0130'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'LFBK-BANKS(01)'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '=ENTR'.
ENDLOOP .
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0210'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'LFB1-FDGRV'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
PERFORM BDC_FIELD USING 'LFB1-AKONT' W_HEADER-AKONT.
PERFORM BDC_FIELD USING 'LFB1-FDGRV' W_HEADER-FDGRV.
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0215'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'LFB1-ZTERM'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0220'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'LFB5-MAHNA'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0310'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'LFM1-WAERS'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
PERFORM BDC_FIELD USING 'LFM1-WAERS' W_HEADER-WAERS.
PERFORM BDC_DYNPRO USING 'SAPMF02K' '0320'.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'RF02K-LIFNR'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '=ENTR'.
PERFORM BDC_DYNPRO USING 'SAPLSPO1' '0300'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '=YES'.
*perform bdc_transaction using 'XK01'.
*perform close_group.
CLEAR W_HEADER .
CALL TRANSACTION 'XK01'
USING T_TARGET
MODE 'A'.
ENDLOOP .
*& Form SUB_UPLOAD_FLATFILE
THIS SUBROUTINE IS USED TO UPLOAD THE FLATFILE TO SOURCE INTERNAL TABLE
FORM SUB_UPLOAD_FLATFILE .
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = 'E:/FLATFILE.TXT'
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
IMPORTING
FILELENGTH =
HEADER =
TABLES
DATA_TAB = T_SOURCE
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17
IF SY-SUBRC 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " SUB_UPLOAD_FLATFILE
*& Form SUB_SPLIT_DATA
THIS SUBROUTINE IS USED TO SPLIT DATA FROM SOURCE INTERNAL TABLE TO
HEADER AND ITEM INTERNAL TABLE
FORM SUB_SPLIT_DATA .
LOOP AT T_SOURCE INTO W_SOURCE .
W_SOURCE1 = W_SOURCE .
AT NEW LIFNR .
W_HEADER-LIFNR = W_SOURCE1-LIFNR.
W_HEADER-BUKRS = W_SOURCE1-BUKRS.
W_HEADER-EKORG = W_SOURCE1-EKORG.
W_HEADER-KTOKK = W_SOURCE1-KTOKK.
W_HEADER-NAME1 = W_SOURCE1-NAME1.
W_HEADER-SORTL = W_SOURCE1-SORTL.
W_HEADER-LAND1 = W_SOURCE1-LAND1.
W_HEADER-AKONT = W_SOURCE1-AKONT.
W_HEADER-FDGRV = W_SOURCE1-FDGRV.
W_HEADER-WAERS = W_SOURCE1-WAERS.
APPEND W_HEADER TO T_HEADER .
ENDAT .
W_ITEM-LIFNR = W_SOURCE-LIFNR .
W_ITEM-BANKS = W_SOURCE-BANKS .
W_ITEM-BANKL = W_SOURCE-BANKL.
W_ITEM-BANKN = W_SOURCE-BANKN.
APPEND W_ITEM TO T_ITEM .
CLEAR W_HEADER.
CLEAR W_ITEM .
ENDLOOP.
ENDFORM. " SUB_SPLIT_DATA
Start new screen *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR W_TARGET.
W_TARGET-PROGRAM = PROGRAM.
W_TARGET-DYNPRO = DYNPRO.
W_TARGET-DYNBEGIN = 'X'.
APPEND W_TARGET TO T_TARGET.
ENDFORM. "BDC_DYNPRO
Insert field *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL SPACE.
CLEAR W_TARGET.
W_TARGET-FNAM = FNAM.
W_TARGET-FVAL = FVAL.
APPEND W_TARGET TO T_TARGET.
ENDIF.
ENDFORM. "BDC_FIELD
****************FLAT FILE FORMAT***********************
1000-56 1000 1000 0001 ABC-01 TC IN US 123445678 123456 31000 A1 INR
1000-56 1000 1000 0001 ABC-01 TC IN US 123123123 234567 31000 A1 INR
1000-56 1000 1000 0001 ABC-01 TC IN US 123123123 345678 31000 A1 INR
1000-56 1000 1000 0001 ABC-01 TC IN US 123123123 345679 31000 A1 INR
1000-56 1000 1000 0001 ABC-01 TC IN US 123123123 345670 31000 A1 INR
1000-56 1000 1000 0001 ABC-01 TC IN US 123123123 345671 31000 A1 INR
1000-56 1000 1000 0001 ABC-01 TC IN US 123123123 345672 31000 A1 INR
1000-56 1000 1000 0001 ABC-01 TC IN US 123123123 345673 31000 A1 INR
1000-56 1000 1000 0001 ABC-01 TC IN US 123123123 345674 31000 A1 INR
Regards,
Raj.

10000 Line Items to be uploaded in Single Sales Order

Hi
Need to upload more than 10000 Line items in the Single Sales Order. What could be the best way of uploading it. is LSMW helpful?
Response awaited. thanks
Moni

Can u advise the steps involved in LSMW?
I believe it is not necessary to go for VA01.
we can go for VA02 itself, as the Header data is going to be one and same. If we create a Sales Order with Header data alone and then using VA02 with that particular Sales Order number in LSMW...
but will the total line items can be taken by Sales Order item level.
this is what the clarification needed.
To be very clear:
Let us say, 10 Sales Orders each with 1000 Line Items. What could be the possibility??
is there any solution for uploading like this? As i informed before, in LSMW for VA02 transcation, takes only the first 7 Line items in Sales Order from the Flat File with more the 1000 line items. That is, it takes only upto the line items which we can see in the VA02 screen and i feel the scroll down functionality is not working to upload above 7 line items. Something has to be done on this.
Any pointer on this.
rgds,

Error in entering header level conditional value - toomany line items to PO

Hi experts
I have an issue while processing a PO. While entering condition values like Freight, Customs duty etc in header level where the order contains more than 1000 line items, i am getting an error " too many line items, msg no.899". Can somebody, guide on this how this can be resolved.
rgds
Raghu

HI Raghu,
The only possible way is to create two diffrent PO's.
As you have maintain various conditions, this will lead to updation of many FI documents at the time of GRN.
This is SAP Limitation.
Regards,
Amit
njoy SAP..
njou Life....

The correct purchasing group is not being determined in the SC line item

Dear all,
I have a problem in that for some reason, when a shopping text line item is added to the shopping cart, the wrong purchasing group is determined. Further more when you look in the basic data section they is a drop down against the purchasing group field listing all pruchasing groups setup in the org plan via PPOMA_BBP.
This means that the requisitioner can change the purchasing group to any one even the one that is not relevant to his or her Purchasing Organisation. This of cause is not right because if the requisitioner is allowed to change the P/Grp, the wrong buyer may end up recieving the buyer completion work item.
What is causing this?
We have uniquely assigned P/Orgs to P/Grps and assigned resposiibility of P/GRPS to one unique ORg unit (company).
for example, a suppose product Category 1234567 is assigned to P/GRP 100 & P/GRP 100 is assigned to P/ORG 1000 and the P/GRP responsibility is set to Org unit(company) 1000, The requisition "sits" under an orgunit linked to company 1000.
If a requisitioner creates a text item and assigns product category 1234567, when the item is added to the shopping cart , I expect to see that the followig:
1. The Company code(CC)should be 1000 (This is happening)
2. The P/org should be 1000(This is happending)
3. The Plant sssignment is correct
4. The p/grp is worong. It appear that the first P/Grp is assigned plus a drop down listing all p/grps created for all purchasing P/Orgs.
Regards,
Grace

Yann,
Yes , we have (need to have)set 2 purchasing groups with the responsibility of the same product category. We have to do this because in our organisation, individual company purchasing organisations have same responsibilities to purchase similar products.
Please note that we have a classic scenario implementation. SRM 4, Server 5.
The business requirement and settings in the org plan is for example:
P/Grp 100 has the reponsibility to procure Prod cats LAM001 to LAM010 via its assigned P/org 1000 which is linked to own company 1000 and P/grp 200 also has the reponsibility to procure Prod cats LAM001 to LAM010 via its assigned P/org 2000 which is linked to own company 2000.
Please note that thr buyer responsible for p/grp 100 & 200 are the same and will be the same for similar product cats across the organisation as a whole. Its just the SRM does not allow you in the orgplan to assign the same p/grp to multiple p/orgs, we had to double up on the p/grps.
Also when a requisitioner who sits under company 2000 chooses a product cat 12345 if creating a SC text line, we DO NOT WANT the requisitioner to change the assigned p/grp.We want it defaulted to 200 (based on the org plan setting I have described above) and fixed(greyedout)
when thr line item viewed in the basic data section.
Do you think that because we have set the prod cat range LAM001 to LAM010, which is an alphanumeric product cat range, that could also be the reason for the dropdown listing all orplan p/grps even ones that do not have the product cat LAM001 to LAM010 in its responsubility assignments?
If you are saying that the system does not know which p/grp to pick, why its it displaying all "unrelated" p/rps in the dropdown. I atlest expect to see two p/grps in the dropdown 100 & 200, because only these two p/grps have been set with product cat responsibility for LAM001 to LAM010 in our org plan.
Also if you are saying that is the way SRM was designed to work (which may be the case!!!) how then can we set the org plan to meet our the purchasing org/purchasing grp /prod cat responsibility requirements I have described above?
Regards,
Grace

WBS Element on AR/AP Line Item Report

Hi All
When I run the FBL1n report for a vendor who has a PO which has a WBS element - I dont see the WBS element coming up on the line item report(s).
Although the field is there on the layout - it is not picking the WBS Element into the report - can anyone please tell me why this is and how I can get this field to fill with values...
Thank you
Rukshana

hi,
If you had activated Project Cash Management, you can try report CJIA which can substitute the report line item wise list for a particular project or for a Particular Vendor.
Why the standard system is not showing WBS because, a single Vendor line can be posted against multiple expense so system cannot determine which WBS to be shown in the report so it is left blank in reports, this will be applicable for Purchase order no, Cost Centers, WBS etc.
As suggested by Suresh you can use the BTE 1650, but it will keep one WBS in the line even you have multiple WBS elements used for the document posting.
For Ex
Expense 1 Dr 1000- WBS 1
Expense 2 Dr 1000- WBS 2
Expense 3 Dr 1000- WBS 3
Vendor A Cr 3000
Against Vendor line item A - it will show WBS 1 alone.As there is no standard solution you can use BTE if your are satisfied with the above example or you have to activate Project Cash management to find the exact reporting but in different reporting structure.
Thanks and regards
Praveen.J

With holding line items are not picking up while clearing with F-44 (DP)

Hi Friends,
I hope you resolve my problem.
I have a problem with With holding tax line items. Please see below for more details.
1. Made advance payment to Vendors through F-48
Vendor a/c dr 200,000
    To Bank a/c 196000
    To TDS a/c      4000
2. Raised Vendor invoice through F-43
Expence a/c dr    50000
    To Vendor a/c    49000
    To TDS Payable   1000
3. Cleared Vendor invoice against the Down payment
39A Vendor a/c dr 50000
26 Vendor a/c 49000
40 TDS Payable 1000
While i am tryi ng to do the above invoice with WHT clearing, the system is saying that " With holding tax information is ignored"
The entry while clearing Vendor DP is
37 Vendor   a/c dr 49000
27 Vendor a/c   49000
I have every seeting in the system
1. Tax types, codes, Vendor master, FSG, FBKP, and posting key settings. All are looking fine
Please help me how to clear the WHT automatically without manual intervention.
Kindly correct me where ever u see mistakes
Thank you so much for your advance help
Regards,
Narasim

Hello Ray,
I am very happy that some have taken tthe responsilibility of answering my query.
When i do the F-54, I am able to clear the vendor invoice against with the down payment. But if i go and see the WHT in respective GL account, they are still showing as " Open".
Please help me how to resolve it.
If this is not the correct way, kindly suggest me the right way.
Thanks for all your help
Regards,
Narasim

TDS line items are not getting reflected in J1INCHLN

Hi Experts,
While generating TDS challan we are not getting advance line items in J1INCHLN screen
We made one advance payment which included 2 payment line items and two different tax codes, while generating TDS challan its is showing only one TDS line item that is Rs.1000/-, another TDS line item of Rs.966/- is not showing.
Below is the example
XYZ                                                                         43,000.00
XYZ                                                                         46,000.00
Bank                                                                        96,329.00-
S/Tax Interim-In Cr                                                    5,160.00
S/Tax Interim-In Cr                                                   3,864.00
ST Interim E.C-In Cr                                                 103.00
ST Interim E.C-In Cr                                                 77.00
ST Inter H E.C-In Cr                                                 52.00
ST Inter H E.C-In Cr                                                 39.00
TDS Pble Contractors                                              966.00-
TDS Pble Contractors                                              1,000.00-
I checked the below possibilities for reason why its not getting reflected
Vendor master having recipient type
WITH_ITEM table updated with recipient type
In the line item also having Business Place and section code
Please suggest me is there any way to resolve the issue.
Thanks & Regards,
AIM

Hi,
Check whether the recipient type CO or OT is updated in With_item table for the line items that are missing in J1INCHLN.
If Recipient type is not maintained in vendor master, at the time of posting the entry, then it does not get picked up in J1INCHLN. Even if you maintain in Vendor master later on, the With_item table does not get updated. This is one of the reasons why the line items does not get picked up in J1INCHLN. Check this, as you are confirming that Business Place, Section code etc.. are all present in line items and also that it is appearing correctly in With_item table.
Regards
Divya S

Expense (PR05) - Line item change report

Hi:
We are looking for a report on the changes made in the trip line items after the trip was submitted, approved, transferred to FI (at every status).
Basically if a consultant has submitted an expense and is approved by the manager, Then if consultant is opening that trip again and making the changes in the line item (change in cost object, amount etc) or adding a new line, we need a report which tells when was the change made, what was the change etc.
With the custom program, we are able to get the trip status history but not the line item details (change).
Any suggestions.

It tells the status of the trip but doesn't tell me what change is made.
For example:
If the original trip had one line for Airfare (say 1000) which was approved and transferred.
Later on this was adjusted to Airfare (say 1010) which was again approved.
We want to know amount was changed from 1000 to 1010 on this date. Similarly to cost assignment. Any field which has accounting effect.
Basically our Accounts payable needs to know if they should settle the expenses without waiting for the receipts at month end (in the scenario where cost object is changed later but amount is same, so there is no revised receipt from consultant. They can just settle it again)
Some kind of report which tells when and what change was made (at item level).
Thanks.
Rahul

BAPI_PO_CREATE1 missing GL a/c no. and cost center in every 100th PO line item

We have a strange issue. We are creating Service Purchase Orders by using BAPI_PO_CREATE1 function module. The source for creating PO is a Z table wherein it contains approximately 1000 records. We create one PO per Vendor and all POs are creating successfully but strangely GL account number and cost centers are missing in every 100, 200, 300, 400, 500, etc. line items and have NO issue with other line items. Our purchase order line item interval is 1 which means at every 100th line item we have an issue in missing GL account number and cost centers. We also checked by changing line item interval to '10' and still we have issue at every 1000th line item.
We searched for OSS notes but no luck. Did anyone come across this kind of issue ? Could you please advise.
Regards,
Krish

you can either share your code and your source file to have the people check if the error is on your part or you can directly contact SAP if you are the opinion that it is an error in their BAPI code.
But without looking at code and source file it is not possible to do any evaluation except you are looking for clairvoyants

How to split a line item to 2 line item.

Hi all !
I have a request, help me please !
In system I have a invoice with 1 line item value 1000 USD.
Customer payment 600$. a incoming payment with value 600$ will post to system.
I want incoming payment and invoice will auto clear 600$ but system can't auto clearing because value is not Identical.
I want line item of invoice will split to 2 line item. Line item 1 value 600$ and line item 2 value 400$.
Line item 1 of invoice will auto clear with incoming payment and system will exist a invoice with 1 line item value 400$.
How to split a line item to 2 line item ? Have FM for split a line item to 2 line item in SAP ?
If you have other solution for this request, help me please !
Thanks !

Hi,
Have a look at Split line item - Sales Order
Regards

1000 Line items

Similar Messages

Maybe you are looking for