Schedule lines and work area

Hi All!
While entering the multiple line items in the sales order(Quotation) screen , at the 60th item the system throws following error message :
System : Schedule lines of Item 000060 is not in Work are.
Has anyone ever came across such message during quotation creation?
Early reply will be appreciated!
Thanks,
Mamata

Hello Sir,
We have the same issue appearing
Item XX for scheduled line XX is in the work area
I am not too sure about the T-Code OQ77 mentioned above. Could you please let me know the reason behind this error as the sales order the error message is appearing is a standard order (Norm Item).
I am not sure how to get rid of this error as it is appearing in a number of sales orders
Thanks in advance for the replies
Regards,
Doss

Similar Messages

  • Header line and work area

    Hi,
    can anyone please explain me wht is the difference between header line and work area???

    Hi,
    INTERNAL TABLES
    - Internal tables are used to obtain data from a fixed structure for
    dynamic use in ABAP.
    - Each line in the internal table has the same field structure.
    - The main use for internal tables is for storing and formatting data from
    a database table within a program.
    WORK AREAS
    - Work areas are single rows of data.
    - It should have the same format as any of the internal tables.
    - It is used to process the data in an internal table one line at a time.
    Internal Tables with Header Line : Here the system automatically creates the work area. The work area has the same data type as internal table. This work area is called the HEADER line. It is here that all the changes or any of the action on the contents of the table are done. As a result of this, records can be directly inserted into the table or accessed from the internal table directly.
    Internal Tables without Header Line : Here there is no work area associated with the table. Work area is to be explicitly specified when we need to access such tables. Hence these tables cannot be accessed directly.
    HEADER LINE----
    CREATED EXPLICITLY------
    1.Internal table created by referring to another table
    Syntax: Data <f> <type> with header line.
    <type> refers to a table data type or table data objects using type or like.
    Here internal table <f> is created of the type <type>.
    Example:
    DATA t_line TYPE line OCCURS 10 with header line.
    2. Internal table created by referring to existing structure
    Syntax: Data<f> <type> occurs n with header line.
    The lines of the internal table <f> have the data type specified in <type> (Can use either like or type).
    Example:
    DATA flight_tab LIKE sflight OCCURS 10.
    CREATED BY DEFAULT---
    3. Internal table created With a new structure
    Syntax: Data : Begin of <f> occurs <n>,
    <component declaration>,
    End of <f>.
    Work area is created by default.
    Example:
    Data : Begin of itab occurs 10,
    column1 type I,
    column2(4) type C,
    column3 like mara-ernam,
    End of itab.
    reward if useful
    Regards

  • Diff between header line and work area.

    Diff between header line and work area.

    Hi,
    These are table with header line.
    DATA: T_TABLE type table of <table_name> with header line.
    data: begin of t_table occurs 0,
                  field1 type ...
                  field2 type ...
                  field3 type ...
          end of t_table.
    <b>The result is:</b>
    <u><b>TABLE</b></u>    
    FIELD NAME  |FIELD1|FIELD2|FIELD3|  
    HEADER LINE |EE1   |EE2   |EE3   | <---- Line 5 content
               1|AA1   |AA2   |AA3   |  
               2|BB1   |BB2   |BB3   |  
               3|CC1   |CC2   |CC3   |
               4|DD1   |DD2   |DD3   |
               5|EE1   |EE2   |EE3   |
    These are table without header line.
    DATA: T_TABLE type table of <table_name>.
    DATA: T_TABLEX LIKE TABLE OF t_table.
    <b>The result is:</b>
    <u><b>TABLE</b></u>    
    FIELD NAME  |FIELD1|FIELD2|FIELD3|  
                     0|---   |---   |---   | <---- No header Line
                     1|AA1   |AA2   |AA3   |  
                     2|BB1   |BB2   |BB3   |  
                     3|CC1   |CC2   |CC3   |
                     4|DD1   |DD2   |DD3   |
                     5|EE1   |EE2   |EE3   |
    These are work areas:
    Tables <table>.
    DATA: wa type <table>.
    DATA: wa like t_table.
    DATA: wa type line of <table>.
    <b>The result is:</b>
    <u><b>WORK AREA</b></u>  
    |EE1   |EE2   |EE3   | <---- Content
    Regards.
    Marcelo Ramos

  • Internal table with header line and work area.

    data:itab like LIKE bapimepoheader.
    DATA : BEGIN OF it_po_items OCCURS 0.
            INCLUDE STRUCTURE bapimepoitem.
    DATA : END OF it_po_items.
    DATA:it_input         TYPE STANDARD TABLE OF typ_input,
          wa_input         TYPE typ_input,
    LOOP AT it_input INTO wa_input WHERE poind = 'H'.
    CLEAR wa_po_header.
      wa_po_header-doc_type  = wa_input-bsart.
      wa_po_header-comp_code = wa_input-bukrs.
      wa_po_header-vendor    = wa_input-lifnr.
    CLEAR it_po_items.
      it_po_items-po_item = v_itemcount * 10.
      it_po_items-acctasscat = wa_input-knttp.
      it_po_items-material   = wa_input-matnr.
      it_po_items-plant      = wa_input-werks.
      it_po_items-quantity   = wa_input-menge.
      it_po_items-net_price  = wa_input-netpr.
      it_po_items-po_unit    = wa_input-meins.
      it_po_items-free_item  = wa_input-umson.
      it_po_items-tax_code   = wa_input-mwskz.
      it_po_items-gr_ind     = wa_input-wepos.
      it_po_items-gr_non_val = wa_input-weunb.
      it_po_items-incoterms1 = wa_input-inco1.
      it_po_items-incoterms2 = wa_input-inco2.
      it_po_items-vend_mat   = wa_input-idnlf.
      it_po_items-taxjurcode = wa_input-txjcd.
      it_po_items-item_cat   = wa_input-pstyp.
      APPEND it_po_items.
    here my doubt is whether i can move data from work area to internal table in this way?
    whether this is the correct approach or not?

    hii,
    u can define structure and make workarea ,internal table using that structure.
    for example
    types:begin of struct,
             declare all fields,
             end of struct.
    data:wa type struct,
           int_tab type standard table of struct.
    hope this will help u.

  • Is there a DIRECT link between SD schedule lines and delivery lines?

    Is there a direct link (db table) between schedule lines on a sales order (VBEP) and the delivery lines (LIPS)? 
    Is there a function module to retrieve the data?
    Example-
    One order line with 3 schedule lines.
    Each schedule line is for 2 units (total of 6 units).
    Three deliveries made.  1st is for 2 units, 2nd is for 1 unit (backorder), 3rd is for 3 units.
    You can use document flow (table VBFA) or examine the SD document in the delivery line (LIPS) and link the delivery line to the order line.  The schedule line already references the order line.
    I am using math to decrement the schedule lines used and make the link between VBEP and LIPS.  It works fine.  I need four records back....
    1st schedule line for 2 units uses delivery 123
    2nd schedule line for 1 unit (partial) uses delivery 124
    2nd schedule line for 1 unit (partial) uses delivery 125
    3rd schedule line for 2 units uses delivery 125
    Like I said, it works. Just wondering if I missed a more direct link.

    As far as Db link is concern , I don’t remember exactly , but 3 years before I had written a report which see Sales order schedule lines and devilry note lines against sales order.  If you see process wise…. when ever you create PO ( production order you assign some qty using 101 movement type .. and against production order you also give sales order . When you do delivery ( run seclude run ) it delivers against that material number , its movement is 601 ...
    but I remember there’s a link between these tables, VBAP,VBFA AND VBEP , LIPS ...  against every sales order you can see sales invoice ( VBRP,VBRK) and you can also see your delivery note number in document flow .
    I hope this’ll give you some guide line, as right now I can not tell you the exact business process but I remember I written a report in SD 4 years before , in which they required Delivery against production order and sales order ... One more thing you also have production order reference on delivery item number. ( field :Empst ) . I think in my project they were maintaining this field .
    Thanks

  • Schedule Lines and BI

    Hi,
    Can anyone please make me understand how does schedule lines works in BI.
    Regards

    Hi,
    Schedule Line Item Data provides information about the header data of a purchasing document, such as vendor, purchasing organization, order currency, the item data such as material, purchase order quantity, order unit, net price, and the purchasing document delivery schedule lines, such as schedule line number, delivery date, schedule line quantity, value of schedule line quantity.
    Item Line denotes the products or materials description for a Sales Order or Invoice such as Qty, Price and other details will be stored in the ITM.
    Schedule line contains the above product or materials delivery details. Lets say the customer has asked for 1000 X product and he may ask or the company send that 1000 in 3 or 4 schedules and these information will be stored in the SCL.Not all the deliveries needs SCL.it is the division of an item in a sales document according to date and quantity.
    For example, if the total quantity of an item can only be delivered in four partial deliveries, the system creates four schedule lines and determines the appropriate quantities and delivery dates for each schedule line.
    also pls chk this;
    http://help.sap.com/saphelp_nw04/helpdata/en/42/06f3381fff3358e10000000a11402f/content.htm
    Regards
    CSM Reddy

  • Schedule lines and hierarchy

    Hi,
    Can somebody please explain me what are these schedule lines and schedule hierarchy in PSP_SCHEDULE_LINES and PSP_SCHEDULE_HIERARCHY tables.
    Thanks
    --pavan                                                                                                                                                                                                                                                                                                                                           

    Hi,
    Schedule Line Item Data provides information about the header data of a purchasing document, such as vendor, purchasing organization, order currency, the item data such as material, purchase order quantity, order unit, net price, and the purchasing document delivery schedule lines, such as schedule line number, delivery date, schedule line quantity, value of schedule line quantity.
    Item Line denotes the products or materials description for a Sales Order or Invoice such as Qty, Price and other details will be stored in the ITM.
    Schedule line contains the above product or materials delivery details. Lets say the customer has asked for 1000 X product and he may ask or the company send that 1000 in 3 or 4 schedules and these information will be stored in the SCL.Not all the deliveries needs SCL.it is the division of an item in a sales document according to date and quantity.
    For example, if the total quantity of an item can only be delivered in four partial deliveries, the system creates four schedule lines and determines the appropriate quantities and delivery dates for each schedule line.
    also pls chk this;
    http://help.sap.com/saphelp_nw04/helpdata/en/42/06f3381fff3358e10000000a11402f/content.htm
    Regards
    CSM Reddy

  • Please provide logic for schedule lines and material document Quantity.

    Hi ABAPers,
    Please help in the following context.
    Is there any connecting or refrence field for which a particular schedule line item are considerd for the goods reciept of a particular material document.
    Also provide the logic.
    19                    34
    15
    14                   35
    11
    10
    If 19 15 14 11 10 are schedule lines, and 34 35 are two recived quantities,
    Then how can be the possible permutations and combinations logic to find out that, 34 = 19 + 15 and
           35 = 141110.
    Thanks in advance...

    Niles Raut wrote:
    Hello Gurus,
    >
    > This is intracompany STO scenario with delivery. There is one STO for quantity say 1000 pc created in 2008. Delivery and PGI done for 1000 qty in 2008.  Goods are received in receiving plant for qty 1000 in 2008. Now this delivery document is archieved and user has reversed the GR material document in 2010. Now this reversal material docuemnt has zero material qty becasue the delivery was archieved(which is the probable reson)
    >
    > When I want to cancel this reversal material document it gives error that "Qty and / or "delivery completed" ind. or final issue ind. are missing" which is logical since material document has zero quantity.
    >
    > Is there any sap notes or any other way to fix this?
    >
    > Please guide.
    >
    > Regards
    > Nilesh
    Where is actually the problem, if one only reversed 0 quantity?
    Why do you think you need to reverse this reversal again?
    why with year 2010?
    Dont you do anual inventories?  Such stock counts have corrected your stock anyway. if you start cancelling older movements then you create stock inconsistencies again.

  • Schedul lines and delivery

    Hi to all,
    is there a way to identify the connection between the schedul line of sales order (vbep-etenr) and the line of outbound delivery? My problem is that i have 2 or more schedul lines and 2 or more deliveries for the same sales order item and i want match this with a program.
    thx a lot

    Hi,
    Schedule lines are defined by scdule line category.
    As we know that item category is determined by a sales order type,Item category group,Usage,High level item category using VOV4 T.Code.
    These schedule line category is going to be determined by item category and MRP Type by using VOV5 T.Code.
    Means it has indirect relation ship with sales document.
    Each schedule line in a sales order refers to an outbound delivery.So in your order as there are 2 schedule lines two deliveries will come.
    Regards,
    Krishna.

  • Difference between Scheduling lines and Delivery schedule

    Hi SD Experts
    can u say me the clear difference between Scheduling lines and Delivery schedule.
    where we will maintain deliver schedule. whether delivery schedule is automatically created along scheduling agreements..
    with regards
    James

    Hi James,
    Schedule Lines: Has basically information realted to delivery scheduling in Sales Order level.
    Delivery Scheduling: Is a process using which system will determine what are the different activities which need to be performed and time taken for each activitiy only after which the material can be delivered to the customer.
    Delievry scheduling will be started only from the material availability date i.e., system will first determine the material avail date and then do scheduling. By default Standard SAP system does Backward Scheduling in case material availability falls beyond the required delivery date system will do forward schedluing
    Delivery Scheduling consists of the following Basic activities:
    We give deatils while creating order:
    Order Creation Date
    Required Delivery Date
    Order date - Material availability date - Transportation Planning Date - Loading date - Goods Issue Date - Required Delivery Date
    Time Between GI Date and required Delivery Date is called Transit Time
    Time Between LoadingDate and GI Date is called Loading time
    Time Between Material Availability Date and Loading Date consists of 2 components - Pick / PackTime and Transportation Planning Time
    System has to calculate all this before it determines the confirmed delivery date.
    Give your mail Id I have some Presentation I will send you across.
    REWARD POINTS IF IT HELPS
    Regards
    Srini

  • Multiple schedule line and reschedule for product selection

    Hi,
    Is it possible to mainatine multiple sechedule line for sales order where product selection is active
    Let me explain the problem in detail.
    We are using product selection functionality while creating sales order. Say for example in VB11 transaction I have maintained A= A1, A2 and A3. Where A1 has stock 50, A2 has stock 30, A3 has stock 20. Suppose my sales order is 150 for material A. The reason used is 0004 'automatic'. So while creating the sales order, confirmed qty for A1=50, A2 =30 and A3
    = 20. I have unconfirmed qty. 50. for this scenario, I need to enable a
    partial delivery, 1st I need to let the customer know when my 100 pcs going to be delivered and 2nd when my balance 50 pcs going to be delivered. So in the sales order I need to maintain two schedule line , one for
    confirmed 100 and another for unconfirmed 50. I am not able to do this.
    I can maintain only one schedule line per main item and at the sub item
    level not possible to maintain.
    The second problem is that, when I get stock for unconfirmed 50, I can
    not reschedule. can anyone please help to solve this issue?
    Regards,
    Beena

    goto item and doublle click on item and goto schedule lines and chenage the shedule lines..
    wat i know is by avaiblity check it propose the delievry dates of items...
    goto MM02 and mrp 1.. you can give there days to producee..
    OR doc type propose delivery dates.. lead days...
    hope it helps
    you
    ramki

  • Internal table and work area

    Hi,
           can anybody explain the concepts of Internal table and work area.Thanks in advance.

    hai,
    This may help u.
    WORKAREA is a structure that can hold only one record at a time. It is a collection of fields. We use workarea as we cannot directly read from a table. In order to interact with a table we need workarea. When a Select Statement is executed on a table then the first record is read and put into the header of the table and from there put into the header or the workarea(of the same structure as that of the table)of the internal table and then transferred top the body of the internal table or directly displayed from the workarea.
    Each row in a table is a record and each column is a field.
    While adding or retrieving records to / from internal table we have to keep the record temporarily.
    The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
    Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
    e.g.
    data: begin of itab occurs 10,
    ab type c,
    cd type i,
    end of itab. " this table will have the header line.
    data: wa_itab like itab. " explicit work area for itab
    data: itab1 like itab occurs 10. " table is without header line.
    Internal tables are used for storing records which are obtained as a result when we use select statement on database. internal tables are run time entities and doesn't occupy any memory. they are dynamic.
    internal tables are of types.
    1. internal tables with header line. [header and body]
    2. internal tables with out header line. [only body]
    Workarea is the concept which is mainly useful when working with internal tables with out header line.
    at any point of time we can access only one record through header of a internal table. every thing should be done [inserting,modifying, reading ] through header only.
    ex: data: itab like standard table of mara with header line.
    for internal tables with out header line we will create a work area [explicit header] as type of table for storing data into internal table.
    ex: data: itab like mara,
    wa like mara.
    more about internal table types:
    Standard table:
    The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
    You should usually access a standard table with index operations.
    Sorted table:
    The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
    Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
    Hash table:
    The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
    You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
    Hashed tables
    This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index.
    The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always
    have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for
    processing large amounts of data.
    TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY TABLE LINE.
    TYPES: BEGIN OF LINE,
    COLUMN1 TYPE I,
    COLUMN2 TYPE I,
    COLUMN3 TYPE I,
    END OF LINE.
    DATA ITAB TYPE HASHED TABLE OF SPFLI
    WITH UNIQUE KEY CARRID CONNID.
    with regards,
    B.Sowjanya,
    reward points if helpful.

  • How to compare delivery date in schedule lines and PGI in outbound delivery

    Hi,
    I want to create a report to monitor and compare different dates in sales and delivery process.
    One of my key figure is the comparison between date confirmed to the customer, that I can find in the schedule line of the sales order, and the actual goods issue date from the outbound delivery.
    But I can't succeed in making the link between delivery and schedule lines, means between LIKP and VBEP.
    Would you have any idea?
    Thank you.

    It seems there's no exact (table) connection / link between delivery item and schedule line item.
    Those who were searching for this thing (link / connection between delivery item and schedule line) were recommended to use FM "RV_SCHEDULE_CHECK_DELIVERIES".
    This FM calculates the delivered quantity for each schedule line, so it makes link between the delivery item and schedule lines - however if you check the code it's quite sophisticated...
    (if you put a breakpoint in the FM and display a SO in VA03, you can check how the parameters have to be populated with data).
    Schedule Line and Delivery Link
    Edited by: Csaba Szommer on Aug 5, 2011 12:03 AM

  • Mapping between Sales Order-Schedule-Line and Delivery-item

    Hi together,
    I want to extend the Datasource 2LIS_12_VCITM (Delivery-number, -item, Order-number,-item is available) by Sales Order Schedule Line.
    Could not find any ERP table (VBEP and LIPS allow a mapping only on item level) for the mapping between Sales Order Schedule Line and Delivery item yet. The use of the extractor 2LIS_12_VCSCL for the extention (e.g. infoset) afterwards is no option.
    Thanks for your help in advance!!
    Assign full points!!
    Sven

    Hi Reddy,
    thanks for your answer.
    I know that I have to add this field.. but the problem is, how to fill this field. I don't know how to map the delivery-item with the schedule line-item.

  • Difference between sales order schedule line and item level data

    Hi All,
    Could you please let me know what is the difference between sales order schedule line and item level data?
    Thanks,
    Ramya

    Hi Ramya,
    Sales order schedule line contains del date, order qty, rounded qty, confirmed qty, delivery qty, schedule line category, purchase requisition etc.,  ie It contains the full details of sales order data with respect to the scheduled line of delivery.  The total quantity of a sales order item can be subdivided into schedule lines that contain the various subsets with the corresponding delivering dates.
    Sales order Item level data contains details of the item in the sales order like material code, net price, net value, UoM, PO details, reason for rejection if any, material group,billing date, plant etc., ie this
    contains the full details of item irrespective of scheduled line.
    Regards,
    R. Senthil Mareeswaran.

Maybe you are looking for