Sch line qty is "0" in "EKET" table

Dear all,
Recently, we have been migrated from ECC5.0 to ECC6.0.
While we are checking our wekly schedule lines in the table "EKET", we found some of the sch line quantities are showing as "0" eventhough quantities available in qty delivered or qty issued column with respect to the sch line no.
(In ECC5.0, if qty is available in qty dellivered or qty issued column of EKET, then schedule qty will not be "0") .
Pl suggest us if there is any note available to overcome this issue.
Regards,
M.Selvaganesh,

If it is a service PO, then your PO quantity should be only 1.
If it has more than one. Then you can enter the schedule line.
First you have to make the Qty field optional entry from field selection
OLME-Purchase Order-Define Screen Layout at Document Level-PT9F.
Make the Quantity field as optional entry.
You can see one line item comes default in PO schedule line.
Then you can copy the line item to another line item.
Select the line item and then press Schedule line split.
If your system is showing something different, then please post a screen shot.

Similar Messages

BAPI FOR Deleting a Schedule Line Item from EKES and EKET tables

Dear All,
I would like to for deleting one of the line item from EKES (Po Confirmation ) and the respective line item from the EKET(PO Schedule Line Item Table).
Assume that am allowing the user to select the lineitem from zprogram screen and collecting the PO and Its LIne Item details in an internal table.
Can i Use
<b>BAPI_PO_Change</b> , if so , can anybody tell me the steps to follow to use this bapi for deleting the PO lineItems, since i m going to try BAPI for First time.
pls help me out
Message was edited by: Raja K.P

Hi raja ,
loop at iekko1.
    w_index = sy-tabix.
    item-po_item   = itemx-po_item   = iekko1-ebelp.
    item-quantity = iekko1-mng01.
    itemx-quantity = iekko1-mng01.
    if iekko1-wamng = iekko1-wemng.
    itemx-no_more_gr = item-no_more_gr = 'X'.
    else.
    itemx-no_more_gr = item-no_more_gr = ''.
    endif.
    append item.
    append itemx.
      clear return[].
      call function 'BAPI_PO_CHANGE'
           exporting
                purchaseorder = iekko1-ebeln
           tables
                return        = return
                poitem        = item
                poitemx       = itemx.
      if return[] is initial.
      commit work and wait.
      call function 'DEQUEUE_ALL'.
search for deletion fields which u have to mark 'X'.
before calling this BAPi u have to lock the PO by using ENQUEUE.
<b>
FU BAPI_PO_CHANGE
Text
Change purchase order
Functionality
Function module BAPI_PO_CHANGE enables you to change purchase orders. The Change method uses the technology behind the online transaction ME22N.
Alternatively, the IDoc type PORDCH1 is available. The data from this IDoc populates the interface parameters of the function module BAPI_PO_CHANGE.
Functionality in Detail
Authorization
When you create (activity 02) an Enjoy purchase order, the following authorization objects are checked:
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X bar
For most tables, you can use your own parameters in the associated X bar (e.g. PoItemX) to determine whether fields are to be set initial, values inserted via the interface, or default values adopted from Customizing or master records, etc. (for example, it is not mandatory to adopt the material group from an underlying requisition - you can change it with the BAPI).
Transfer
Purchase order number
The PurchaseOrder field uniquely identifies a purchase order. This field must be populated in order to carry out the Change method.
Header data
The header data of the Enjoy purchase order is transferred in table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the tables PoItem (general item data). Changes regarding quantity and delivery date are to be made in the table PoSchedule.
Use the table PoAccount to change the account assignment information.
Services and limits
Changes to existing items cannot be carried out with the Change method. It is only possible to create new items.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. A new price determination process can be initiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor address in the table PoAddrVendor and the delivery address in the table PoAddrDelivery can only be replaced by another address number that already exists in the system (table ADRC). Changes to address details can only be made using the method BAPI_ADDRESSORG_CHANGE.
Partner roles
You can change all partners except the partner role "vendor" via the table PoPartner.
Export/import data
Export/import data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items. Changes to the export/import data of existing items are not possible.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText. Texts can only be replaced completely.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
If the PO was changed successfully, the header and item tables are populated with the information from the PO.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
Restrictions
With this function module, it is not possible to:
Create subcontracting components (you can only use existing ones)
Create configurations (you can only use existing ones)
Change message records (table NAST) and additional message data (this data can only be determined via the message determination facility (Customizing))
Attach documents to the purchase order
Change foreign trade data
Change service data
Change or reexplode BOMs
A firewall prevents the manipulation of data that is not changeable in Purchasing according to the business logic of the purchase order (e.g. PO number, vendor, etc.).
PO items with an invoicing plan cannot be created or changed using the BAPIs
In this connection, please refer to current information in Note 197958.
To change addresses with numbers from Business Address Services (cantral address management), please use the function module BAPI_ADDRESSORG_CHANGE.
To change variant configurations, please use the function module BAPI_UI_CHANGE. More information is available in the BAPI Explorer under the Logistics General node.
In the case of changes that are to be made via the BAPI_PO_CHANGE, a firewall first checks whether the relevant fields are changeable. This approach follows that of the online transaction. Here it is not possible to change the vendor or the document type, for example.
Example
Example of changes made to a purchase order with:
1. Change in header data
2. Change in item
3. Change in delivery schedule
4. Change in account assignment
5. Change in conditions
6. Change in partners
Parameter: PURCHASEORDER 4500049596
Parameter: POHEADER
PMNTTRMS = 0002
PUR_GROUP = 002
Parameter: POHEADERX
PMNTTRMS = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
CONF_CTRL = 0001
Parameter: POITEMX
PO_ITEM = 00001
PO_ITEMX = X
CONF_CTRL = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
QUANTITY = 10.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELETE_IND = X
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELETE_IND = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
GL_ACCOUNT = 0000400020
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
PO_ITEMX = X
SERIAL_NOX = X
GL_ACCOUNT = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_TYPE = RA02
COND_VALUE = 2.110000000
CURRENCY = %
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 001
ITM_NUMBERX = X
COND_ST_NOX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
Customer Enhancements
The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further Information
1. Note 197958 contains up-to-date information on the purchase order BAPIs.
2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
Parameters
PURCHASEORDER
POHEADER
POHEADERX
POADDRVENDOR
TESTRUN
MEMORY_UNCOMPLETE
MEMORY_COMPLETE
POEXPIMPHEADER
POEXPIMPHEADERX
VERSIONS
NO_MESSAGING
NO_MESSAGE_REQ
NO_AUTHORITY
NO_PRICE_FROM_PO
EXPHEADER
EXPPOEXPIMPHEADER
RETURN
POITEM
POITEMX
POADDRDELIVERY
POSCHEDULE
POSCHEDULEX
POACCOUNT
POACCOUNTPROFITSEGMENT
POACCOUNTX
POCONDHEADER
POCONDHEADERX
POCOND
POCONDX
POLIMITS
POCONTRACTLIMITS
POSERVICES
POSRVACCESSVALUES
POSERVICESTEXT
EXTENSIONIN
EXTENSIONOUT
POEXPIMPITEM
POEXPIMPITEMX
POTEXTHEADER
POTEXTITEM
ALLVERSIONS
POPARTNER
Exceptions
Function Group
2012
</b>
regards
prabhu
Message was edited by: Prabhu Peram

EKET Table (Urgent)

Hi All,
I would like to know where i can find the program which is updating the field WEMNG in table EKET.
Eg: Purchase Order with one line & this line has 2 delivery schedules
PO qty = 10 nos, (EKPO-MENGE)
1st delivery schedule qty = 5 nos (EKET-MENGE)
2nd delivery schedule qty = 5 nos (EKET-MENGE)
The EKET table has 2 entries i.e
line 1: EKET-ETENR = 0001, EKET-MENGE = 5
line 2: EKET-ETENR = 0002, EKET-MENGE = 5
I understand when i do a goods receipt, EKET-WEMNG field is updated, but i want to know which program is actually doing this. Where can i find the code. I checked in MEPO1320 structure, but was unable to find the code, i checked in SAPLMEGUI, but was not successful either, maybe i havent checked in the right place.
Hope my question is clear, await inputs
Regards,
Vivek

Hi Sagun,
The reason i want to know is because, i want to implement the same logic in a query which i am trying to build. I want to subtract the quantity coming from EKES table for line 1 until the quantity is 5 & after that i want it to subtract from line 2.
I hope you are clear of the problem i am facing. Awaiting your inputs to resolve this.
Vivek

Connecting the sale order sch line and delivery no

I want to find a delivery no and item no which is created for a sale order-> item no->schedule line. Is there any table which relates even sch lines. I know VBFA is the table but i want in even connecting schedule lines. If we dont have table is their any methods to find it our?

Link: http://www.sap-img.com/
Topic: Free ABAP eBook Download
SAP MM, SD, FI, PS, PP, PM, HR, System Tables
The above table represents a diagramatic presentation of how tables & fields are linbked.
Regards,
Rajesh Banka
Reward Points if helpful.

Deleted items still apear on EKET Table

Hello All
my question is the following...
why i still see some schedule lines in EKET from deleted items? if i check on EKPO they are delted if i check in me23n they are deleted but they continue to appear on EKET.
how is the deletion process triggered in eket?
thanks in advance

the delivery date of a PO is not stored in EKPO, it is only stored in EKET table.
The quantity in a PO item, is just a total of all quantities in the related schedules.
As long you see a schedule line in the delivery schedule tab in ME23N you will have a record in EKET table, no matter if the PO is marked for deletion or not.
You cannot even the delete the single schedule line, SAP will give you a message to enter a quantity.
if you have many schedule lines per order, then you can delete all but one.
EKET table entries get physically removed when you archive the purchase order, together with EKKO and EKPO records and records from some 100 other tables that belong to the object MM_EKKO

Automatic Payment program -line item cleared not displaying in table

automatic Payment program -line item cleared not displaying in table
i have re run the APP program DUSR1 same earlier it has run twice but table dose not show double payment to vendors how to resolve the issue.
Can some one please guide me on this.

Hi Priyanka,
First, which table are you referring to. If your fist APP run clears the line item, it will no longer be available in the open item.
Please be more specific on the problem so that we can try to help you. If possible, please provide screenshots.
Regards,
Ganesh

Unable to create PR with Service Line & also no entry in ESLH table using

Hi Experts,
I am using BAPI => BAPI_REQUISITION_CREATE to create PR and it is successful to create PR but when I try to create PO is become fail (proably missing entry in ESLH table).
Now my requirement is to create PR with Service Line and an entry in ESLH table (should be filled by SAP automatically). I have been passing the service related/account assigment tables into BAPI but still not working.
Will you please give a solution to create PR with Service Line and also need an entry in ESLH table (its important to my req)?
Also provide some input on Service Line, if possible(How to check Service Line for PR + Account Assignment to Service Line + etc.)?
Note that: If I create PR manually then there have entry in ESLH and hence I can create PO.
Definately the quick solution help me lot...
Thanks
AKG

Hi Experts,
I am using BAPI => BAPI_REQUISITION_CREATE to create PR and it is successful to create PR but when I try to create PO is become fail (proably missing entry in ESLH table).
Now my requirement is to create PR with Service Line and an entry in ESLH table (should be filled by SAP automatically). I have been passing the service related/account assigment tables into BAPI but still not working.
Will you please give a solution to create PR with Service Line and also need an entry in ESLH table (its important to my req)?
Also provide some input on Service Line, if possible(How to check Service Line for PR + Account Assignment to Service Line + etc.)?
Note that: If I create PR manually then there have entry in ESLH and hence I can create PO.
Definately the quick solution help me lot...
Thanks
AKG

Scheduling Line qty greater than the Scheduling agreement qty

Hi Experts,
1. I have a scheduling Agreement (SA), and the qty mentioned against this SA is 1000 (say).
2. Now when i generate schedule lines for this SA (ME38), I am allowed to schedule more than the quantity that's mentioned in the SA.
3. Please advise, is it possible to restrict this behaviour. i.e. I want to give an error message if the Schedule Line qty exceeds the SA qty.
Please advise. Very urgent.
Regards,
Manju.

Hi Manju,
Yes its possible to restrict the case as u mentioned.
Check the below settings:
IMG-MM-Purchasing-Environment data- Define Attributes for system messages
go to meassage no : 00-06-067 set it as Error message.
U'll achieve ur result.
Award points if its helpful
Sangram

How to add line item to sales order item table?

Kindly help me the with the below requirement .
Add line item to sales order(va01) dynamically on click of button. The button is also custom created push button.
In the above requirement I have added the pushbutton to va01 tcode. But when I click on that button I need to add line item to sales order item table.
I tried a lot but I am not successful. If possible can u please help on this.
Regards,
Rachel

Hi!
It's quite easy even in the standard SAP to add a line item for a customer order, I don't think it worth to develop a new button for this.
However if you wanted to add a line automatically, the you can do the following in the program MV45AFZZ, FORM USEREXIT_SAVE_DOCUMENT.
You can use similar code, but with some modifications.
DATA: lv_posnr.
LOOP AT xvbap.
MOVE xvbap-posnr TO lv_posnr.   "get the last posnr
ENDLOOP.
ADD 10 TO lv_posnr.
MOVE 'XYZ' TO xvbap-matnr.   "enter your material number here
MOVE lv_posnr TO xvbap-posnr.
* fill additinal field data in XVBAP if necessary
MOVE 'I' TO xvbap-updkz.                  "Insert line
APPEND xvbap.
Regards
Tamá

Runtime error:ABAP program lines are longer than the internal table

Hi all,
Below is the code I have written,when Iam running it Iam getting
'ABAP program lines are longer than the internal table' runtime error.How can I resolve it.
REPORT ZTEST1 NO STANDARD PAGE HEADING LINE-SIZE 255.
TABLES:MARC,CDHDR,CDPOS.
TYPE-POOLS:SLIS.
DATA:HEADER TYPE SLIS_T_FIELDCAT_ALV,
     WA TYPE SLIS_FIELDCAT_ALV,
     LAYOUT TYPE SLIS_LAYOUT_ALV.
TYPES:BEGIN OF MARC_TY,
        MATNR LIKE MARC-MATNR,
        WERKS LIKE MARC-WERKS,
        EKGRP LIKE MARC-EKGRP,
        MINBE LIKE MARC-MINBE,
        EISBE LIKE MARC-EISBE,
        MABST LIKE MARC-MABST,
       END OF MARC_TY.
TYPES:BEGIN OF MATNR1_TY,
        MATNR1 LIKE CDHDR-OBJECTID,
      END OF MATNR1_TY.
TYPES:BEGIN OF CDHDR_TY,
         OBJECTCLAS LIKE CDHDR-OBJECTCLAS,
         OBJECTID   LIKE CDHDR-OBJECTID,
         CHANGENR   LIKE CDHDR-CHANGENR,
         USERNAME   LIKE CDHDR-USERNAME,
         UDATE      LIKE CDHDR-UDATE,
        END OF CDHDR_TY.
TYPES:BEGIN OF CDPOS_TY,
         OBJECTCLAS LIKE CDPOS-OBJECTCLAS,
         OBJECTID   LIKE CDPOS-OBJECTID,
         CHANGENR   LIKE CDPOS-CHANGENR,
         TABNAME    LIKE CDPOS-TABNAME,
         FNAME      LIKE CDPOS-FNAME,
         CHNGIND    LIKE CDPOS-CHNGIND,
         VALUE_NEW LIKE CDPOS-VALUE_NEW,
         VALUE_OLD LIKE CDPOS-VALUE_OLD,
        END OF CDPOS_TY.
**************TABLE TYPES********************************************
TYPES: MARC_TAB   TYPE TABLE OF MARC_TY,
       MATNR1_TAB TYPE TABLE OF MATNR1_TY,
       CDHDR_TAB TYPE TABLE OF CDHDR_TY,
       CDPOS_TAB TYPE TABLE OF CDPOS_TY.
*******************INTERNAL TABLES************************************
DATA:MARC_ITAB   TYPE MARC_TAB,
     MATNR1_ITAB TYPE MATNR1_TAB,
     CDHDR_ITAB TYPE CDHDR_TAB,
     CDPOS_ITAB TYPE CDPOS_TAB.
****************WORK AREAS********************************************
DATA:MARC_WA   TYPE MARC_TY,
     MATNR1_WA TYPE MATNR1_TY,
     CDHDR_WA TYPE CDHDR_TY,
     CDPOS_WA TYPE CDPOS_TY.
*******************SELECTION-SCREEN***********************************
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
PARAMETERS:PLANT LIKE MARC-WERKS.
SELECT-OPTIONS:MATERIAL FOR MARC-MATNR.
SELECT-OPTIONS:DATE FOR CDHDR-UDATE.
SELECTION-SCREEN END OF BLOCK B1.
START-OF-SELECTION.
SELECT MATNR
        WERKS
        EKGRP
        MINBE
        EISBE
        MABST
        FROM MARC INTO TABLE MARC_ITAB
        WHERE MATNR IN MATERIAL
        AND WERKS = PLANT.
CHECK MARC_ITAB[] IS NOT INITIAL.
LOOP AT MARC_ITAB INTO MARC_WA.
   MATNR1_WA-MATNR1 = MARC_WA-MATNR.
   APPEND MATNR1_WA TO MATNR1_ITAB.
   CLEAR MATNR1_WA.
ENDLOOP.
CHECK MATNR1_ITAB[] IS NOT INITIAL.
SELECT OBJECTCLAS
        OBJECTID
        CHANGENR
        USERNAME
        UDATE
        FROM CDHDR INTO TABLE CDHDR_ITAB
        FOR ALL ENTRIES IN MATNR1_ITAB
        WHERE OBJECTCLAS = 'MATERIAL'
        AND OBJECTID = MATNR1_ITAB-MATNR1
        AND UDATE IN DATE.
CHECK CDHDR_ITAB[] IS NOT INITIAL.
SORT CDHDR_ITAB[] DESCENDING BY OBJECTID CHANGENR.
DELETE ADJACENT DUPLICATES FROM CDHDR_ITAB[] COMPARING OBJECTID.
SELECT OBJECTCLAS
       OBJECTID
       CHANGENR
       TABNAME
       FNAME
       CHNGIND
       VALUE_NEW
       VALUE_OLD
       FROM CDPOS INTO CORRESPONDING FIELDS OF TABLE CDPOS_ITAB
       FOR ALL ENTRIES IN CDHDR_ITAB
       WHERE OBJECTCLAS = CDHDR_ITAB-OBJECTCLAS
       AND OBJECTID = CDHDR_ITAB-OBJECTID
       AND CHANGENR = CDHDR_ITAB-CHANGENR
       AND TABNAME = 'MARC'
       AND FNAME    IN ('MINBE','EISBE','MABST','LVORM')
       AND CHNGIND = 'U'.
CHECK CDPOS_ITAB[] IS NOT INITIAL.
*LOOP AT CDPOS_ITAB INTO CDPOS_WA.
WRITE: / CDPOS_WA-OBJECTCLAS,
         CDPOS_WA-OBJECTID,
         CDPOS_WA-CHANGENR,
         CDPOS_WA-TABNAME,
         CDPOS_WA-FNAME,
         CDPOS_WA-CHNGIND,
         CDPOS_WA-VALUE_NEW,
         CDPOS_WA-VALUE_OLD.
*ENDLOOP.
WA-SELTEXT_L = 'OBJECTCLAS'.
WA-COL_POS   = '1'.
WA-FIELDNAME = 'OBJECTCLAS'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '15'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'OBJECTID'.
WA-COL_POS   = '2'.
WA-FIELDNAME = 'OBJECTID'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '20'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'CHANGENR'.
WA-COL_POS   = '3'.
WA-FIELDNAME = 'CHANGENR'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '8'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'TABNAME'.
WA-COL_POS   = '4'.
WA-FIELDNAME = 'TABNAME'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '5'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'FNAME'.
WA-COL_POS   = '5'.
WA-FIELDNAME = 'FNAME'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '7'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'CHANGING'.
WA-COL_POS   = '6'.
WA-FIELDNAME = 'CHANGING'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '1'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'VALUE_NEW'.
WA-COL_POS   = '7'.
WA-FIELDNAME = 'VALUE_NEW'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '5'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'VALUE_OLD'.
WA-COL_POS   = '8'.
WA-FIELDNAME = 'VALUE_OLD'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '5'.
APPEND WA TO HEADER.
CLEAR WA.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
EXPORTING
    I_PROGRAM_NAME               = SY-REPID
    I_INTERNAL_TABNAME           = 'CDPOS_ITAB'
    I_CLIENT_NEVER_DISPLAY       = 'X'
    I_INCLNAME                   = SY-REPID
CHANGING
    CT_FIELDCAT                  = HEADER[]
EXCEPTIONS
IF SY-SUBRC <> 0.
ENDIF.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
    I_CALLBACK_PROGRAM                = SY-REPID
    IT_FIELDCAT                       = HEADER[]
TABLES
    T_OUTTAB                          = CDPOS_ITAB[]
IF SY-SUBRC <> 0.
ENDIF.

Your select querry on MARC is not matching with MARC_TY.
The field in the MARC table and MARC_TY should be same.
and also, when you are making select querry on CDPOS table
with all entries.
When ever you are using all entries select statement, you should check whether the internal table is having value.
you should check
if CDPOS_IT[] is not initial.
SELECT OBJECTCLAS
OBJECTID
CHANGENR
TABNAME
FNAME
CHNGIND
VALUE_NEW
VALUE_OLD
FROM CDPOS INTO CORRESPONDING FIELDS OF TABLE CDPOS_ITAB
FOR ALL ENTRIES IN CDHDR_ITAB
WHERE OBJECTCLAS = CDHDR_ITAB-OBJECTCLAS
AND OBJECTID = CDHDR_ITAB-OBJECTID
AND CHANGENR = CDHDR_ITAB-CHANGENR
AND TABNAME = 'MARC'
AND FNAME IN ('MINBE','EISBE','MABST','LVORM')
AND CHNGIND = 'U'.
endif.
Regards
Madhan D

How many line item dimensions can a fact table have?

Hi,
How many line item dimensions can a fact table have? Is it tht Max of 16 dimensions(13+3) .Does the 16 dimensions include line items dimensions as well .
Pls reply.
Thanks
Praveen

It includes all dimensios, including line item dimensions.
If you have line item dimension, pl note you cant assign any other characteristic to that dimension.
Ravi Thothadri

What is the maximal line length of type any internal table

Dear all,
who can tell me what is the maximal line length of type any internal table.
Thanks!

There is no limit to the record length of an internal table.
There is overall memory limit for every program (as setup by your basis). So, depending on the width of the ITAB, the number of records in ITAB is limited by the assigned memory.

Sch lines exceeded

Hello,
We are procuring a Material from third party vendor through Sch agreement. Hence during MRP run Sch lines are generated. During last week's MRP run it MRP has given a error message that "Max.9999 Schedule lines possible in Sch aggreement... item .....". When we analysed the issue and understand that there is a counter in sch agreement which counts all sch lines generated for a particular sch agreement (refer ME39) and when it reaches 9999 MRP run gives error message as above. For rectifying the error we found that following are the remedies.
1) Re-number the schedule lines in scheduling agreement
execute function
2) Aggregate the schedule lines in scheduling agreement
execute function
3) Create a new scheduling agreement item.
I wish to know steps which have to be do in order to re-number SL in SA according to solution no. 1.

Hi Taj,
Thanks for attempting to solve my problem.
I tried program RNEWNUMB in SE38. But it shows "Program RNEWNUMB does not exist". Can you please check the program name? If I made a mistake also please highlight.
Also I got an answer from SAP MM forum. Through ME85/ ME86 we can renumber the schedule line counter number.
Now tell me, how much points I need to give for your reply?
Regards,
R. Srinivasan

Schedule Release shipmet QTY not matched with line QTY

the problem is when create schedule release and come to shipment lines and specific in QTY field which come by default from lines i found the QTY less than the line QTY for example i put in the lines (2400) each i found (37.1) and some times i found (.01)
when try to put QTY manual system say QTY should less the line QTY so i try make arround which is delete the header lines and save then re-enter the line agian then system work normally ....this issue repeated many times with all users and specially when create release 2 or 3 from the planned purchase order so we need to know how we can avoid this issue in the future

I do not understand the problem description.
How many lines / shipments / distributions in Planned PO? What is the quantity in each of them.
What is the quantity in Release Shipment / distribution?
What is the exact navigation user is trying what is the error being thrown?

Schedule target qty is less than schedule line qty.....

hi,
please tell me can i avoid users to not to give schedule line qty more than target qty.....
is it possible.....

Hi friend,
yes it can be possible.....
there is a message for it,it may be a warning in your case.... just turn it to error,
Go to spro--->Material management>Purchasing->Environment data--->define message systems...
Go here select your message....it may be some thing like M06xx
select the message and turn it to error......
Now while the user will crete a schedule line in Me38 he will not be able to create schedule line ....
Hope it is usefull.....

Sch line qty is "0" in "EKET" table

Similar Messages

Maybe you are looking for