Sales Order with WBS - Error CJ 070

Hello Friends,
I have got one typical requirement from our client.
The client is in cosmetics business and would be spending huge amount for promotional campaigns. Now the client would like to collect all the costs under WBS tool as statistical and wanted to link the WBS to the sale order. So that we can compare the sales generated for each campaign.
Now when I try to simulate the scenario, the system is throwing the following error message:
Message no. CJ070
Diagnosis
You are attempting to assign a sales document to WBS element I/0065-2-1. WBS element I/0065-2-1 is a statistical WBS element. In this case you cannot assign a sales document item.
And in addition to this, the client does not want to use other objects like internal order etc. for some other reasons.
Can you please advise any suggestions?
Regards,
Santosh Varanasi

Hello  Santosh ,
Could you please refer to the SAP note 43875, which explained the
system behaviour about CJ070?
In the standard system, when creating a sales order and trying to assign
the sales order item to a statistical WBS element, error message
CJ 070= "WBS element & is a statistical WBS elemement" is displayed.
A statistical WBS element cannot be the account assignment
object for a sales order item as correctly indicated in the attached
note 43875. This is the standard system behaviour.
We don't recommend you to deactivate the error message CJ070 because of
the fact that the assigmnet will be checked in the sales order, in the
delivery - during the PGI and in the billing. Althrough you will be able
to create a sales order, you will not be able to make PGI (for
example).
The only one way to use the statistical WBS element in the sales order
is to use the statistical internal order in the sales order and
assign this statistical internal order to a statistical WBS element.
Best regards,
Ronghua Fan

Similar Messages

  • Sales Order with WBS Elements

    Hi,
    I have a sales order having lot of WBS elements assigned.....but I am not able to generate revenue  for one WBS element out of them.
    Can anyone tell what should I do for the same.
    Regards,
    Krishna Singh.
    Edited by: Krishna Prakash Singh on Oct 30, 2008 7:53 AM

    Hi,
    Please check in CJ20N , whether this WBS e has been marked as a billing element or not.
    I think this is not marked as a billing element.
    Thanks,
    Dhruv Kumar Malhotra

  • Error while creating sales order with network/project

    Dear All,
    we are getting the following message while creating a sales order with assembly processing with network/project system .
    The standard Network used as a reference contains assignments to a standard WBS. However you have maintained WBS assignments manually.which assignment should be used?
    manually maint         pre-defined
    reward points are assured for valuable help.
    thanking you
    Best regards,
    R.Srinivasan

    Dear Murali,
    Thankyou very much for your reply.We have checked for these things which you have mentioned.
    ie
    Assignment of Standard WBS in the Standard network and WBS Assignment of Operastional network.We are still getting this error.
    Kindly let me know What are the other possibilities for this error.
    Thanking you,
    Best regards,
    R.Srinivasan

  • Error while creating the sales order with billing reference

    hi alll
    i am getting error while creating the sales order with billing reference.The line items are coming in grey.I am not able to change the items as well as the quantity field.Can u guide me
    cheers
    shalsa007........

    Dear SAP SD 007
    I can confidently tell that an enhancement or an user exit has been applied in your scenario
    You have to check that
    Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
    Your people has solved the standard problem by enhancement
    Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
    Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
    To solve this only your people have used userexit
    Line items and qty greyed out means definately there is some enhancement or user exit applied
    You have to check that
    Regards
    Raja

  • Error while creating sales order with ref using SD_SALESDOCUMENT_CREATE

    Hi
    I am creating sales order with reference using function module SD_SALESDOCUMENT_CREATE , while creating i am getting error
    Document doesn't have document category even thougth i am passing document category in header as well as item lavel.
    In VBUK table there is no value for VGTYP.
    Can you please help me how to resolve it.
    Thanks & regards
    kiran

    Problem resolved by passing   REFDOC_CAT in the FM along with  SD_DOC_CAT.
    Thanks

  • DIServer insert operations for sales orders with error

    DIServer insert operations for sales orders with
    That even though the insert is inserted DocDueDate DocDueDate it says error.
    Subtracting the value of the format 'yyyy-mm-dd', 'yyyy/mm/dd', 'mm-dd-yyyy', 'mm/dd/yyyy' put all reporting
    When the input is entered DocDueDate ShipDate also put together ... but I get an error.
    The error message 'env: Receiver-10Enter due date [ORDR.DocDueDate] 171AddObject2EEE7D98-AB71-464A-93AB-933F0AD3D4DC'
    Purchase order entered into the normal value because the xml is missing or wrong with you.
    Please answer all the possibilities that can be resolved
    This Xml used.
    "<BOM>" +
    "<BO>" +
    "<AdmInfo>" +
    "<Object>oOrders</Object>" +
    "</AdmInfo>" +
    "<QueryParams>" +
    "<DocEntry />" +
    "</QueryParams>" +
    "<Documents>" +
            "<row>" +
            "<DocType>I</DocType>" +
            "<DocDate>2012-01-11</DocDate>" +
            "<DocDueDate>2012-01-11</DocDueDate>" +
            "<CardCode>CD00001</CardCode>" +
            "<Address>Anymode</Address>" +
            "<DocCurrency>KRW</DocCurrency>" +
            "<Comments>[sales orders] LGU TEST</Comments>" +
            "<TaxDate>2012-01-11</TaxDate>" +
            "<JournalMemo>JournalMemo</JournalMemo>" +
            "<Address2>Addr</Address2>" +
            "<BPL_IDAssignedToInvoice>1</BPL_IDAssignedToInvoice>" +
            "</row>" +
    "</Documents>" +
    "<Document_Lines>" +
            "<row>" +
            "<ItemCode>ACDT0100ET</ItemCode>" +
            "<Quantity>1</Quantity>" +
            "<Price>5000</Price>" +
            "<DiscountPercent>10</DiscountPercent>" +
            "<WarehouseCode>A100</WarehouseCode>" +
            "<VatGroup>A2</VatGroup>" +
            "</row>" +
    "</Document_Lines>" +
    "</BO>" +
    "</BOM>";

    I had the same error change the Date to the format yyyymmdd, and problem solved.

  • COPA - Multiple Sales Order with one wbs element.  COPA does not reference

    COPA - Multiple Sales Order with one wbs element.  COPA does not reference of reference of sales order.
    Hi All
    Currently we are in process of implementation of project related to Club Service for one of the client.
    Concept of this project is - there is "X" company engaged in supporting the different shared services for their client e.g. Client IBM - Shared Support Services of IBM is
    u2022     IDM
    u2022     Software Installation
    u2022     Help Desk
    u2022     Maintenance
    Co.. "X' is performing these services for IBM.    So for Co. "X" - IBM is one engagement. Like this way Co. X is performing such activities for many companies e.g. microsoft, HP, ABN AMRO etc.
    Objective - Get the consolidate report from COPA (Customer wise/services wise/sales order wise e.g. IBM/HelpDesk/10002/10).
    We propose a solution to create a project for each engagement and with WBS element. Each WBS element of different services e.g.
    Project IBM Inc.  100.100
    WBS Element    100.100.IDM 
    WBS Element    100.100.SoftIns
    WBS Element    100.100.HelpDesk
    WBS Element    100.100.Maintainance
    For this engagement (IBM), we are creating a sales order with line items (for services) and account assignment is WBS element.  In a sales order, there may be two lines for one services.   In a particular period, there are many such sales orders for this engagement... Milestone billing/period billing is used depending upon the services rendered.
    Now Cost Object will be WBS Element. So cost and revenue will posted to WBS and from this it goes to COPA.  In a month of May 2009 two - sales order is booked with three different line items with account assignment is WBS element.
    Sales Order Line Item No.....Item                  Account Assignment                      Revenue
    10000          100     IDM      100.100.IDM              1000
    10000          200     HELPDESK      100.100.HelpDesk              2000
    10000          100     Maintenance      100.100.Maintainance         3000
    Another Sales order booked with two different line items
    10000          100      IDM     100.100.IDM          3000
    10000          200      HELPDESK     100.100.HelpDesk          4000
    Cost will be booked directly against WBS element.
    In sales order level, there is no profitability segment, as cost object is WBS element.
    Billing, revenue will be posted directly to wbs element, from this revenue and cost of sales goes to COPA.
    Now in COPA,
    1.There is only one line for WBS element ex. 100.100.IDM with revenue 4000 (combing both the sales order)
    2.There is only one line for WBS element ex. 100.100.HelpDesk with revenue 6000 (combing both the sales order)
    3.There is only one line for WBS element ex. 100.100.Maintainance with revenue 4000
    In above case 1 & 2 we will not have reference of sales order and sales order line item in COPA table. There is only one line for this.  So we can not have reporting to sales order level.
    Is there any way by this the reference of sales order and sales order line will come in COPA for case 1 & 2.
    Please help in this issue.
    Regards
    Abhay Dev
    Ph:- 91-22-67782229
    Cell:- 91-9819175185

    Hi,
    For these case (multiple materials with different characteristics); have you consider going to next level of WBS Elements. Meaning; lets say currently you are assigning WBS "Engineering (which is a level 2 WBS)" to all the items in SO. Instead under "Engineering" create 2 or 3 level 3 WBS Elements as E1, E2 etc and assign them 1:1 to your sales order line items. This would eliminate the exit as welll as complex development option. And also will let you get all the data in COPA and in turn you can pull to BW as well for reporting. Just a thought.
    Regards
    Sreekanth

  • Error while creating sales order with ref to contract

    while creating sales order, with refernce to contract system is giving a message
    Configuration not possible for material : Reason 3 --> Help
    Message no. V1360
    and the message is as follwed can any one explain
    Diagnosis
    This may have been caused by one of the following:
    1. The configuration profile for the material allows or requires the bill of materials to be exploded during order processing. However, a plant has not been specified in the item.
    2. The configuration profile of the material allows or requires the bill of materials to be exploded during order processing, but the order quantity in the item must be greater than 0.
    3. A configuration profile has not been maintained
    or
    A configuration is not permitted for the material
    or
    4. The configuration profile of the material allows or requires the bill ofmaterials to be exploded during order processing. However, the system could not determine a date because important data is missing from the item (see incompletion log).

    Hi
    I think you have both Variant configuration and BOM.
    Pls ensure the following.
    1. BOM masterdata is maintained for the variants
    2. Variant configuration is configured correctly
    Configuration profile is created for the material
    Knowledge base object and run time version are available
    3. Maintain materials as not relevant for delivery or dont give delivery quantity as 0
    Once you are sure that these are in proper shape, you can start creating order. The problem wont come.
    Reward points if it helps you.

  • Load a sales order with delivery date in the past

    Hi,
    We want to load in the system a sales order with delivery date in the past, and maintain the schedule delivery date in the past. To do that, in the customizing Sales And Distribution / Basic Functions / Delivery Scheduling and Transportation Scheduling / Define Scheduling By Sales Document Type, I selected the flag Blackwards. But the problem is that the rest of the dates in the scredule line: goods issue date, loading date, material avail.date and transportation Plan Date, are in blank and you cannot enter any data because the system deletes it.
    How can I have these dates informed with dates in the past?
    Thanks in advance,

    You can control this using the "Message Control" in the SAP IMG.
    Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Message Control>Influence Message Control
    Using this you convert Error to Warning or even swith off this message.
    Please refer this thread for complete steps:
    Re: How to change an error message to a warning message in SRM
    Note: you need to suppress the messages relevant to your case here.
    Regards
    Kathirvel

  • EDI: creating a sales order with reference to contract

    Dear gurus,
    we would like to create a sales order with reference to a SD contract from an ORDERS IDoc.
    OSS say we have to populate the E1EDx02 segments with the contract number to do this.
    We tested this in our system by manually editing the incoming IDoc and this is what we found:
    - qualifier u201C005  : Customer Contract Numberu201D set and BELNR = u201Cthe customeru2019s outline agreement number in his MMu201D (= normal MM behaviour) -> reference is not processed at all, sales order is created without reference
    - qualifier u201C043: Vendor Contract Numberu201D set and BELNR = our contract number in SD -> Sales order successfully created. BUT where can I store an external outline agreement number in MM so that the BELNR in the IDoc is populated with it?
    - qualifier u201C058: Customer Contract Numberu201D set and BELNR = the customeru2019s outline agreement number in his MM -> Error:
    The system could not determine a contract number
    Message no. VG226
    Diagnosis
    The system could not determine a contract number for the selection criteria: external contract number 5100000020 and customer number 0044000004.
    This error appears although we maintained the external number 5100000020 in the PO number field (VBKD-BSTKD) in our SD contract.
    Could anyone please explain what we do wrong?
    Cheers
    Alicia

    Hi again,
    @Lakshmipathi: Thank you, but it is VG226, like I wrote. But still, the OSS note is interesting: "You create a sales order with reference to an MM contract using EDI." Where's the sense in that? Why would I ever want to create a sales order with reference to an outline agreement in MM???
    @Rags: Sure we could do that, but I find it hard to believe that there is no standard way to do this. Especially given there are plenty of OSS notes stating that this is possible, e.g. note 562710.
    Any other ideas?
    Cheers
    Alicia

  • G/L Account is missing in item data in sales order with reference to quotation

    Dear SAP Guru,
    I have a problem in accordance with G/L Account missing sales order. Initially, please find the below lines.
    1. If I do the sales order without reference to quotation there is no error in G/L Account missing.
    2. If I do the sales order with reference to quotation there is an error that G/L account is missing in item data.
    I have checked the VKOA, the settings are fine.
    Kindly anyone of you resolve this issue.
    Warm Regards
    Vidya Sagar

    G/L account is missing in item data.
    Many times, it has been discussed on this issue in SCN and please search with the same text so that you will find many threads asking various areas to check.  Take the inputs from there and post here still if you have issue.
    G. Lakshmipathi

  • Sales order with reference to quotation

    How to use BAPI_SALESORDER_CREATEFROMDAT2 to create a sales order with reference to quotation? what parameters I need to fill in?

    Hi,
    I've also had this problem.
    In the past when faces with this requirement I have used
    BAPI_READ_SALES_DOCUMENT (Note:  I am away from a system today so that may not be the EXACT name of the funciton module but it's close ) to read in the document data from the quote, then transfer that data to the input structures of BAPI_SALESORDER_CREATEFROMDAT2.  Seems to work reasonably well although it doesn't offer much in the way of automatic error handling.
    Hope this helps,
    Regards,
    Brent

  • Create a sales order with reference to another one. (BAPI)

    Hi everybody,
    I'm trying to create a new sales order with reference to another one (That's important because of the documents flow).
    I'm using 'BAPI_SALESORDER_CREATEFROMDAT2' but I couldn´t do it yet. I've read some ideas about this kind of creation in this forum; but I still haven´t found the solution yet.
    Some ideas about the BAPI parameters I nedd to complete?
    Thanks in advance!!

    Hi,
    Go through this one
    *& Report ZSD_R_SALESORDER
    report zsd_r_salesorder1 line-size 132 message-id zmmbapi .
    *& Created By : shailaja
    *& Created on : 13.10.2007
    *& Requested By : vardhman
    *& Description of program :
    Internal table definition *
    data: gt_order_header_in like bapisdhead occurs 0 with header line,
    gt_return like bapireturn1 occurs 0 with header line, " Return Messages
    gt_order_items_in like bapiitemin occurs 0 with header line, " Item Data
    gt_salesdocument like bapivbeln-vbeln , "Number of Generated Document
    gt_order_partners like bapiparnr occurs 0 with header line, "Document Partner
    gt_return1 like bapiret2 occurs 0 with header line.
    Data definition *
    types: begin of ty_gt_ft_sales ,
    partn_numb(10) type n ,"Customer Number 1
    partn_role(2) ,"Partner function
    sales_org(4) , "Sales Organization
    distr_chan(2) , "Distribution Channel
    division(002), "DIVISION
    doc_type(4) , "Sales Document Type
    purch_no(020), "Purchase order
    material(18), "MATERIAL
    targetquantity(020),"Target quantity
    reqqty(020), "Req quantity
    reqdate(010), "req date
    *REQ_DATE_H(010),
    ref_1(012), "Ref
    unload_pt(025),
    *PARTN_ROLE(2) ,"Partner function
    *PARTN_NUMB(10) ,"Customer Number 1
    end of ty_gt_ft_sales,
    begin of ty_header ,
    partn_numb(10) ,"Customer Number 1
    partn_role(2) ,"Partner function
    sales_org(4) , "Sales Organization
    distr_chan(2) , "Distribution Channel
    division(002), "DIVISION
    doc_type(4) , "Sales Document Type
    purch_no(020), "Purchase order
    unload_pt(025),
    req_date_h(010),
    end of ty_header,
    begin of ty_item,
    material(18), "MATERIAL
    targetquantity(020),"Target quantity
    reqqty(020), "Req quantity
    reqdate(010), "req date
    ref_1(012), "Ref
    *UNLOAD(025),
    end of ty_item.
    data : msg(240) type c, " Return Message
    e_rec(8) type c, " Error Records Counter
    rec_no(8) type c, " Records Number Indicator
    s_rec(8) type c, " Successful Records Counter
    t_rec(8) type c, " Total Records Counter
    v_matnr like mara-matnr,
    v_parvw type parvw.
    data : gt_ft_sales type standard table of ty_gt_ft_sales with header line.
    data : wa_gt_ft_sales type ty_gt_ft_sales,
    wa_order_items_in like gt_order_items_in,
    wa_gt_ft_sales1 type ty_gt_ft_sales,
    wa_header type ty_header,
    salesdocument like bapivbeln-vbeln.
    selection block for EXCEL UPLOAD FILE
    selection-screen begin of block b1 with frame title text-000.
    parameters file type ibipparms-path obligatory.
    selection-screen end of block b1.
    *<<<<AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .
    at selection-screen on value-request for file .
    perform getname.
    form getname.
    call function 'F4_FILENAME'
    exporting
    program_name = syst-cprog
    dynpro_number = syst-dynnr
    importing
    file_name = file.
    endform.
    *TOP-OF-PAGE.
    top-of-page.
    skip 3.
    format color col_heading inverse on.
    write 40 text-001.
    format color col_heading inverse off.
    skip 1.
    format color col_negative inverse on.
    write :/ text-002, 13 sy-mandt , 104 text-003, 121 sy-uname,
    / text-004, 13 sy-datum , 104 text-005, 121 sy-uzeit.
    format color col_negative inverse off.
    skip 3.
    *START-OF-SELECTION.
    start-of-selection.
    perform get_data.
    perform bapi.
    *end-of-page.
    perform result.
    form result.
    t_rec = e_rec + s_rec.
    skip 3.
    format color col_total inverse on.
    write: /38 text-007, t_rec.
    format color col_total inverse off.
    format color col_negative inverse on.
    write: /38 text-008, e_rec.
    format color col_negative inverse off.
    format color col_total inverse on.
    write: /38 text-009, s_rec.
    format color col_total inverse off.
    endform.
    *& Form get_data
    text
    --> p1 text
    <-- p2 text
    form get_data .
    call function 'WS_UPLOAD' "#EC *
    exporting
    filename = file
    filetype = 'DAT'
    tables
    data_tab = gt_ft_sales
    exceptions
    conversion_error = 1
    file_open_error = 2
    file_read_error = 3
    invalid_type = 4
    no_batch = 5
    unknown_error = 6
    invalid_table_width = 7
    gui_refuse_filetransfer = 8
    customer_error = 9
    no_authority = 10
    others = 11.
    if sy-subrc 0 .
    message e000.
    endif.
    endform. " get_data
    *& Form BAPI
    form bapi .
    loop at gt_ft_sales into wa_gt_ft_sales.
    wa_gt_ft_sales1 = wa_gt_ft_sales.
    at new partn_numb.
    wa_header-doc_type = wa_gt_ft_sales1-doc_type..
    wa_header-sales_org = wa_gt_ft_sales1-sales_org . "'0001'
    wa_header-distr_chan = wa_gt_ft_sales1-distr_chan. "'01'
    wa_header-division = wa_gt_ft_sales1-division. " '01'
    wa_header-purch_no = wa_gt_ft_sales1-purch_no.
    wa_header-req_date_h = wa_gt_ft_sales1-reqdate.
    call function 'CONVERSION_EXIT_PARVW_INPUT'
    exporting
    input = wa_gt_ft_sales1-partn_role
    importing
    output = v_parvw.
    wa_header-partn_role = v_parvw.
    wa_header-partn_numb = wa_gt_ft_sales1-partn_numb.
    wa_header-unload_pt = wa_gt_ft_sales1-unload_pt.
    move-corresponding wa_header to gt_order_partners.
    move-corresponding wa_header to gt_order_header_in.
    append gt_order_header_in.
    append gt_order_partners.
    endat.
    call function 'CONVERSION_EXIT_CCMAT_INPUT'
    exporting
    input = wa_gt_ft_sales1-material
    importing
    output = v_matnr.
    gt_order_items_in-material = v_matnr .
    gt_order_items_in-target_qty = wa_gt_ft_sales1-targetquantity . "'1000'
    gt_order_items_in-req_qty = wa_gt_ft_sales1-reqqty.
    gt_order_items_in-req_date = wa_gt_ft_sales1-reqdate.
    *GT_ORDER_ITEMS_IN-BILL_DATE = wa_GT_FT_SALES1-REQDATE.
    gt_order_items_in-ref_1 = wa_gt_ft_sales1-ref_1.
    append gt_order_items_in.
    clear : wa_gt_ft_sales1,wa_header.
    at end of partn_numb.
    call function 'BAPI_SALESORDER_CREATEFROMDAT1'
    exporting
    order_header_in = gt_order_header_in
    WITHOUT_COMMIT = ' '
    CONVERT_PARVW_AUART = 'X'
    importing
    salesdocument = salesdocument
    SOLD_TO_PARTY =
    SHIP_TO_PARTY =
    BILLING_PARTY =
    return = gt_return
    tables
    order_items_in = gt_order_items_in
    order_partners = gt_order_partners.
    ORDER_ITEMS_OUT =
    ORDER_CFGS_REF =
    ORDER_CFGS_INST =
    ORDER_CFGS_PART_OF =
    ORDER_CFGS_VALUE =
    ORDER_CCARD =
    ORDER_CFGS_BLOB =
    ORDER_SCHEDULE_EX =
    if gt_return-type eq 'E' .
    e_rec = e_rec + 1.
    read table gt_return with key id = 'V1'.
    format color col_negative inverse on.
    rec_no = e_rec + s_rec.
    concatenate text-006 rec_no ':'
    gt_return-message into msg separated by space .
    condense msg.
    write: / msg.
    format color col_negative inverse off.
    elseif gt_return-number = '000'.
    s_rec = s_rec + 1.
    format color col_positive inverse on.
    msg = 'SUCCESS'.
    condense msg.
    write: / msg .
    format color col_positive inverse off.
    write :/ salesdocument, 'Has been created'.
    perform commit_mm.
    endif.
    clear: gt_return[], msg.
    endat.
    endloop.
    endform. " SLALE_UPLOAD_DATA
    *& Form COMMIT_MM
    text
    --> p1 text
    <-- p2 text
    form commit_mm .
    call function 'BAPI_TRANSACTION_COMMIT'
    exporting
    wait = 'X'
    importing
    return = gt_return1.
    clear: gt_order_items_inhttp://].\"GT_ORDER_CONDITIONS_IN[.
    endform. " COMMIT_MM
    inthis pass re_doc field in header...
    Edited by: Naresh kumar

  • Create sales order with reference to a contract

    Hi,
    Is there any BAPI/FM which can be used to create a sales order with reference to a contract.
    Regards,
    Saji.

    Hi Maninder/Srinivas ,
    Could you please provide your valuable inputs on the below query . I have posted a new thread , but haven't got any reply till now . Sorry for posting it again.
       I want to  create an order with reference to a sales contract using BAPI_SALESORDER_CREATEFROMDAT2  .
    1) I passed the contract number to the field REF_DOC at header level , But I got the error message in return table  " Document 4000003639 doesn't have document category " where 4000003639 was the contract number . am i missing anything ? Is there any other values that has to be passed ?
    2) I also tried passing the contract number at item level  but the sales order was created without any reference to the contract .
    Thanks in advance
    Beena

  • Creating sales order with reference to order

    Hi SD gurus.
    I try creating a sales order with reference to order, but I get this error message: "Flow control: Entry SAPMV45B, UER1, E0, *   , AU  , * is missing in T185". I don't know what is missing. Please, could you help me?
    Thanks a lot.
    Marta.

    hi,
    this is to inform you that,
    i went to SE16N given there T185 and checked with UER1 which is an FCODE FOR OVER VIEW SCREEN in VOV8.
    this entry is missing for the combination.
    please check in your sales order in VOV8 whether you have maintained UER1 in the above field.
    if not :
    please maintain the entries missed in T185 in SM30.
    because i have checked teh same in SM30 it is having opportunity to maintain.
    hope this will solve your issue.
    regards,
    balajia
    Edited by: balaji timmampalli achari on Nov 23, 2010 12:00 PM

Maybe you are looking for