Sales Order and obligatory material's parameter fields - help!!!

Hi,
My problem is:
I've got to create material in MM by using BAPI_MATERIAL_SAVEDATA, so that this material can be later used as an item in Sales Order (SD). Do you know what parameter fields from which structures are obligatory in my case? I've already passed quite a lot of data to this BAPI, but I still get following error:
"Material myMaterial is not defined for sales org. 4000, distr.chan. 01, language FI"
Any suggestion will be appreciated and properly rewarded if useful.
My Java source-code is available below. Check this out and let me know what is missed.
                * HEADDATA FOR BASIC VIEW
               Structure headData = input.getStructure("HEADDATA");
               headData.setValue(_material, "MATERIAL");
               headData.setValue("1", "IND_SECTOR");
               headData.setValue(_matl_type, "MATL_TYPE");
               headData.setValue("X", "BASIC_VIEW");
               headData.setValue("X", "SALES_VIEW");
               //headData.setValue("X", "MRP_VIEW");
               headData.setValue("E", "INP_FLD_CHECK");
                * CLIENTDATAX FOR BASIC VIEW
               Structure clientDatax = input.getStructure("CLIENTDATAX");
               clientDatax.setValue("X", "MATL_GROUP");
               clientDatax.setValue("X", "OLD_MAT_NO");
               // clientdatax.setValue("X", "PROD_HIER");
               clientDatax.setValue("X", "BASE_UOM_ISO");
               clientDatax.setValue("X", "NET_WEIGHT");
               clientDatax.setValue("X", "UNIT_OF_WT_ISO");
               clientDatax.setValue("X", "ITEM_CAT");
               clientDatax.setValue("X", "PUR_VALKEY");
               clientDatax.setValue("X", "LABEL_TYPE");
               clientDatax.setValue("X", "LABEL_FORM");
               clientDatax.setValue("X", "DIVISION");
                * CLIENTDATA FOR BASIC VIEW
               Structure clientData = input.getStructure("CLIENTDATA");
               clientData.setValue("02", "MATL_GROUP");
               clientData.setValue("testmaterial", "OLD_MAT_NO");
               // clientdata.setValue("1000000790","PROD_HIER");
               clientData.setValue("PCE", "BASE_UOM_ISO");
               clientData.setValue(0.111, "NET_WEIGHT");
               clientData.setValue("KGM", "UNIT_OF_WT_ISO");
               clientData.setValue("NORM", "ITEM_CAT");
               clientData.setValue("UV03", "PUR_VALKEY");
               clientData.setValue("1", "LABEL_TYPE");
               clientData.setValue("E1", "LABEL_FORM");
               clientData.setValue("01", "DIVISION");
                * SALESDATAX
               Structure salesDatax = input.getStructure("SALESDATAX");
               salesDatax.setValue("4000","SALES_ORG");
               salesDatax.setValue("01","DISTR_CHAN");
               salesDatax.setValue("X","ITEM_CAT");
               salesDatax.setValue("X","DELYG_PLNT");
                * SALESDATA
               Structure salesData = input.getStructure("SALESDATA");
               salesData.setValue("4000","SALES_ORG");
               salesData.setValue("01","DISTR_CHAN");
               salesData.setValue("NORM","ITEM_CAT");
               salesData.setValue("4200","DELYG_PLNT");
                * PLANTDATAX
               Structure plantDatax = input.getStructure("PLANTDATAX");
               plantDatax.setValue("4200", "PLANT");
               plantDatax.setValue("X", "MRP_TYPE");
               plantDatax.setValue("X", "MRP_CTRLER");
               plantDatax.setValue("X", "REORDER_PT");
               plantDatax.setValue("X", "MINLOTSIZE");
               plantDatax.setValue("X", "LOADINGGRP");
                * PLANTDATA
               Structure plantData = input.getStructure("PLANTDATA");
               plantData.setValue("4200", "PLANT");
               plantData.setValue("ND", "MRP_TYPE");
               plantData.setValue("001", "MRP_CTRLER");
               plantData.setValue("0", "REORDER_PT");
               plantData.setValue("100", "MINLOTSIZE");
               plantData.setValue("0001", "LOADINGGRP");
                * MATERIALDESCRIPTION EN
               Table materialDesc = tables.getTable("MATERIALDESCRIPTION");
               materialDesc.appendRow();
               materialDesc.setValue("ENGLISH", "LANGU");
               materialDesc.setValue("EN", "LANGU_ISO");
               materialDesc.setValue(_material+" - test for sales order", "MATL_DESC");
                * MATERIALDESCRIPTION FI
               materialDesc.appendRow();
               materialDesc.setValue("FINNISH", "LANGU");
               materialDesc.setValue("FI", "LANGU_ISO");
               materialDesc.setValue(_material+" - test FI", "MATL_DESC");
               // materialdesc.insertRow(0);
               // MeasureX
               Table measurex = tables.getTable("UNITSOFMEASUREX");
               measurex.appendRow();
               measurex.setValue("X", "ALT_UNIT_ISO");
               measurex.setValue("X", "UNIT_DIM_ISO");
               measurex.setValue("X", "LENGTH");
               measurex.setValue("X", "WIDTH");
               measurex.setValue("X", "HEIGHT");
               measurex.setValue("X", "VOLUME");
               measurex.setValue("X", "VOLUMEUNIT_ISO");
               measurex.setValue("X", "GROSS_WT");
               measurex.setValue("X", "UNIT_OF_WT");
               measurex.setValue("X", "UNIT_OF_WT_ISO");
               // measurex.insertRow(0);
               // Measure
               Table measure = tables.getTable("UNITSOFMEASURE");
               measure.appendRow();
               measure.setValue("PCE", "ALT_UNIT_ISO");
               // measure.setValue("X","DEL_FLAG");
               measure.setValue("CMT", "UNIT_DIM_ISO");
               measure.setValue(0.111, "LENGTH");
               measure.setValue(0.111, "WIDTH");
               measure.setValue(0.111, "HEIGHT");
               measure.setValue(0.3, "VOLUME");
               measure.setValue("CMQ", "VOLUMEUNIT_ISO");
               measure.setValue(0.111, "GROSS_WT");
               measure.setValue("KGM", "UNIT_OF_WT");
               measure.setValue("KG", "UNIT_OF_WT_ISO");
               //Tax classifications
               Table tax = tables.getTable("TAXCLASSIFICATIONS");
               tax.appendRow();
               tax.setValue("FI", "DEPCOUNTRY");
               tax.setValue("FI", "DEPCOUNTRY_ISO");
               tax.setValue("MWST", "TAX_TYPE_1");
               tax.setValue("1", "TAXCLASS_1");
               //tax.setValue("01", "TAX_IND");
               tax.appendRow();
               tax.setValue("EN", "DEPCOUNTRY");
               tax.setValue("EN", "DEPCOUNTRY_ISO");
               tax.setValue("MWST", "TAX_TYPE_1");
               tax.setValue("2", "TAXCLASS_1");

Hi Alistair,
I have a full access to SAP, so I can create and extend material whenever I want through MM01/MM02, but my target is to develop a method in Java, which creates a fully functional material to be used later in Sales Order.
A code listed in my prevoius post shows most of my method. I've got to indicate that my method works correctly and creates material. I've checked it through MM03 - I mean my material created with my method exists.
Moreover both sales org. and distr. channel are passed to BAPI, as you may see in the following code:
                * SALESDATA
               Structure salesData = input.getStructure("SALESDATA");
               salesData.setValue("4000","SALES_ORG");
               salesData.setValue("01","DISTR_CHAN");
               salesData.setValue("NORM","ITEM_CAT");
               salesData.setValue("4200","DELYG_PLNT");
But the problem occurs when I wanna create Sales Order (VA01) and when I choose the item. Material created by my method causes error:
"Material myMaterial is not defined for sales org. 4000, distr.chan. 01, language FI"
I don't understand why? I'm not SAP specialist, but in my opinion I've passed necessary data.
Do you any idea?
Thanks in advance. Every helpful suggestion will be properly rewarded.
BR,
Rafal

Similar Messages

  • Sales Order and obligatory material's parameter fields

    Hi,
    My problem is:
    I've got to create material in MM by using BAPI_MATERIAL_SAVEDATA, so that this material can be later used as an item in Sales Order. Do you know what parameter fields from which structures are obligatory in my case? I've already passed quite a lot of data to this BAPI, but I still get following error:
    "Material myMaterial is not defined for sales org. 4000, distr.chan. 01, language FI"
    Any suggestion will be appreciated and properly rewarded if useful.
    My Java source-code is available below. Check this out and let me know what is missed.
                    * HEADDATA FOR BASIC VIEW
                   Structure headData = input.getStructure("HEADDATA");
                   headData.setValue(_material, "MATERIAL");
                   headData.setValue("1", "IND_SECTOR");
                   headData.setValue(_matl_type, "MATL_TYPE");
                   headData.setValue("X", "BASIC_VIEW");
                   headData.setValue("X", "SALES_VIEW");
                   //headData.setValue("X", "MRP_VIEW");
                   headData.setValue("E", "INP_FLD_CHECK");
                    * CLIENTDATAX FOR BASIC VIEW
                   Structure clientDatax = input.getStructure("CLIENTDATAX");
                   clientDatax.setValue("X", "MATL_GROUP");
                   clientDatax.setValue("X", "OLD_MAT_NO");
                   // clientdatax.setValue("X", "PROD_HIER");
                   clientDatax.setValue("X", "BASE_UOM_ISO");
                   clientDatax.setValue("X", "NET_WEIGHT");
                   clientDatax.setValue("X", "UNIT_OF_WT_ISO");
                   clientDatax.setValue("X", "ITEM_CAT");
                   clientDatax.setValue("X", "PUR_VALKEY");
                   clientDatax.setValue("X", "LABEL_TYPE");
                   clientDatax.setValue("X", "LABEL_FORM");
                   clientDatax.setValue("X", "DIVISION");
                    * CLIENTDATA FOR BASIC VIEW
                   Structure clientData = input.getStructure("CLIENTDATA");
                   clientData.setValue("02", "MATL_GROUP");
                   clientData.setValue("testmaterial", "OLD_MAT_NO");
                   // clientdata.setValue("1000000790","PROD_HIER");
                   clientData.setValue("PCE", "BASE_UOM_ISO");
                   clientData.setValue(0.111, "NET_WEIGHT");
                   clientData.setValue("KGM", "UNIT_OF_WT_ISO");
                   clientData.setValue("NORM", "ITEM_CAT");
                   clientData.setValue("UV03", "PUR_VALKEY");
                   clientData.setValue("1", "LABEL_TYPE");
                   clientData.setValue("E1", "LABEL_FORM");
                   clientData.setValue("01", "DIVISION");
                    * SALESDATAX
                   Structure salesDatax = input.getStructure("SALESDATAX");
                   salesDatax.setValue("4000","SALES_ORG");
                   salesDatax.setValue("01","DISTR_CHAN");
                   salesDatax.setValue("X","ITEM_CAT");
                   salesDatax.setValue("X","DELYG_PLNT");
                    * SALESDATA
                   Structure salesData = input.getStructure("SALESDATA");
                   salesData.setValue("4000","SALES_ORG");
                   salesData.setValue("01","DISTR_CHAN");
                   salesData.setValue("NORM","ITEM_CAT");
                   salesData.setValue("4200","DELYG_PLNT");
                    * PLANTDATAX
                   Structure plantDatax = input.getStructure("PLANTDATAX");
                   plantDatax.setValue("4200", "PLANT");
                   plantDatax.setValue("X", "MRP_TYPE");
                   plantDatax.setValue("X", "MRP_CTRLER");
                   plantDatax.setValue("X", "REORDER_PT");
                   plantDatax.setValue("X", "MINLOTSIZE");
                   plantDatax.setValue("X", "LOADINGGRP");
                    * PLANTDATA
                   Structure plantData = input.getStructure("PLANTDATA");
                   plantData.setValue("4200", "PLANT");
                   plantData.setValue("ND", "MRP_TYPE");
                   plantData.setValue("001", "MRP_CTRLER");
                   plantData.setValue("0", "REORDER_PT");
                   plantData.setValue("100", "MINLOTSIZE");
                   plantData.setValue("0001", "LOADINGGRP");
                    * MATERIALDESCRIPTION EN
                   Table materialDesc = tables.getTable("MATERIALDESCRIPTION");
                   materialDesc.appendRow();
                   materialDesc.setValue("ENGLISH", "LANGU");
                   materialDesc.setValue("EN", "LANGU_ISO");
                   materialDesc.setValue(_material+" - test for sales order", "MATL_DESC");
                    * MATERIALDESCRIPTION FI
                   materialDesc.appendRow();
                   materialDesc.setValue("FINNISH", "LANGU");
                   materialDesc.setValue("FI", "LANGU_ISO");
                   materialDesc.setValue(_material+" - test FI", "MATL_DESC");
                   // materialdesc.insertRow(0);
                   // MeasureX
                   Table measurex = tables.getTable("UNITSOFMEASUREX");
                   measurex.appendRow();
                   measurex.setValue("X", "ALT_UNIT_ISO");
                   measurex.setValue("X", "UNIT_DIM_ISO");
                   measurex.setValue("X", "LENGTH");
                   measurex.setValue("X", "WIDTH");
                   measurex.setValue("X", "HEIGHT");
                   measurex.setValue("X", "VOLUME");
                   measurex.setValue("X", "VOLUMEUNIT_ISO");
                   measurex.setValue("X", "GROSS_WT");
                   measurex.setValue("X", "UNIT_OF_WT");
                   measurex.setValue("X", "UNIT_OF_WT_ISO");
                   // measurex.insertRow(0);
                   // Measure
                   Table measure = tables.getTable("UNITSOFMEASURE");
                   measure.appendRow();
                   measure.setValue("PCE", "ALT_UNIT_ISO");
                   // measure.setValue("X","DEL_FLAG");
                   measure.setValue("CMT", "UNIT_DIM_ISO");
                   measure.setValue(0.111, "LENGTH");
                   measure.setValue(0.111, "WIDTH");
                   measure.setValue(0.111, "HEIGHT");
                   measure.setValue(0.3, "VOLUME");
                   measure.setValue("CMQ", "VOLUMEUNIT_ISO");
                   measure.setValue(0.111, "GROSS_WT");
                   measure.setValue("KGM", "UNIT_OF_WT");
                   measure.setValue("KG", "UNIT_OF_WT_ISO");
                   //Tax classifications
                   Table tax = tables.getTable("TAXCLASSIFICATIONS");
                   tax.appendRow();
                   tax.setValue("FI", "DEPCOUNTRY");
                   tax.setValue("FI", "DEPCOUNTRY_ISO");
                   tax.setValue("MWST", "TAX_TYPE_1");
                   tax.setValue("1", "TAXCLASS_1");
                   //tax.setValue("01", "TAX_IND");
                   tax.appendRow();
                   tax.setValue("EN", "DEPCOUNTRY");
                   tax.setValue("EN", "DEPCOUNTRY_ISO");
                   tax.setValue("MWST", "TAX_TYPE_1");
                   tax.setValue("2", "TAXCLASS_1");

    I forgot to indicate sth important what actually might be read from my source code. Both sales org. and distr. channel are passed to BAPI to structure SALESDATA. Why SAP doesn't recognize it? Do you know any explanation? or somebody else?
                    * SALESDATA
                   Structure salesData = input.getStructure("SALESDATA");
                   salesData.setValue("4000","SALES_ORG");
                   salesData.setValue("01","DISTR_CHAN");
                   salesData.setValue("NORM","ITEM_CAT");
                   salesData.setValue("4200","DELYG_PLNT");

  • What  balance value  in sales order  and iwant to know table field name in

    where the balance value come in sales order i want make sales order report in which i want to add this filed how we add it  and tell me table field name of balance vlue and how we give it in FS please help me in this my report are left without it please give me solution

    Hello
    where the balance value come in sales order
    Please note that when you raise your question at SDN forum, your question needs to be clear...
    What do you mean by BALANCE VALUE ????
    Regards,
    Sarthak

  • MRP Generated production orders greys out Sales Order and Customer fields

    Hi there,
    The MRP generated production orders greys out the Sales Order and Customer fields for some reasons. These fields are really important as they link the production order to the sales order and the customer's purchase order. Could the SAP team please fix this or advise alternative way of getting the sales order and customer info on production order? Thanks.

    Hello
    MRP only poulated this fields in case the material master has been set up with a strategy group hich is make to order (normally 20). Otherwise MRP summarizes all the requirements from different Customer orders and creates a production order
    Stephan

  • Hide the cost and margin fields on Sales Orders and Invoices

    Hi all,
    I need to hide the cost and margin fields in Sales Orders and Invoices. We sell our products to our employees sometimes, hence we don't want them to know cost and margin information.
    Can this be done?
    Cheers

    Go to VOV7 & as per the Item category ,de - select the Check Box Determine Cost.
    Else remove the Condition Type VPRS & Margin Condition type from the Pricing Procedure
    Best Regards,
    Ankur

  • MRP - Sales order and customer fields grey-out

    Hi there,
    The Sales order and customer fields are grey-out for all MRP generated production orders. Can the SAP programmers please get this fixed? It should either read in the sales order number and the customer number or allow user to type in the sales order, just like the manually created production order.
    cheers

    Hello Gordon,
    If production is make-to-order rather than make-to-stock, the MRP should read in the sales order number and the customer, since it is specific to the sales order. Even for make-to-stock production, where it cannot read in the specific sales order number, it should at least not grey out the field, don't you think so? By greying out the field, users are not allowed to type in the sales order number even when the production order directly relates to a particular sales order. As such, we are not able to link it back to the sales order where other info such as customer's purchase order, etc... can be found.
    Could you please advise alternative way of linking MRP generated production orders to the sales orders? thanks

  • DMS Link witlh Sales order and Material master

    Hi, all
    here is my?
    Can we link DMS to both sales order and material master, for service feedback of a product from customer.
    rgds
    ben

    hi
    you can link the objects through object link in dms.
    go to  tcode dc10 select the documnet type, click on define object link. click on new entry, select VBAP object for sales order and MARA for material master.
    thanks ,
    regards,
    nitin
    award point if useful

  • Update KOMV-KBETR field for sales order and billing

    I would like to update the KOMV-KBETR (condition amount or percentage) under condition tab for both Sales order and billing.
    example:There are two condition types ZA00 and ZB00 and need to get the KBETR value from ZA00 and add it to KBETR value of ZB00 and update the sum in KBER value of ZB00.
    1. creation of sales order & billing.
    2. Change of sales order & billing.
    3. For single & multiple line items in both sales order & billing.
    4. during updation of price in the change mode of sales order & billing.
    5.When user click on Update button in the condition tab(i.e., when clicked on Carryout new pricing)
    I tried with the VOFM routine but as the routine is triggering multiple times the sum is calculated again and again.For that I set flags also.It is working for sales orders but for billing creation the field XKOMV-KBETR is cleared after this routine.
    So I would like to know are there any EXITS for this scenario or any one entountered the similiar issue which I am facing.

    Hi Brad,
       It is an Client requirement.So need to do the addition of that condition types.
    Can you please let me know the configuration point where we can do it and the condition type which we need to update the Rate/Amount value.ie., KOMV-KBETR is and Price list value and not the subtotal one.
    Thanks,
    Srilakshmi Lagisetty.

  • Sales order and billing document fields

    what are the fields for sales order and billing document dates?

    Hi
      Couldnt really get the exact requirement:
    1. If Billing Dates are to be extracted from Sales Documents, we can do that by extracting field <b>FKDAT</b> from table <b>VBKD</b>.
    2. If it is Billing Document creation date, extract from VBRK-ERDAT with below condition.
      select vbrp~vbeln vbrp posnr vbrp~aubel
             vbrp~aupos vbrk~erdat into table itab
             from vbrp as a
             inner join vbrk as b
             on vbrp~vbeln = vbrk~vbeln
             where vbrp~aubel in s_vbeln.  "Sales Documents
       Hope this gives you some idea.
    Kind Regards
    Eswar

  • Sales order and return sales order in the same field

    Hi Everybody,
        I have sales sales order and return sales order in the same field ,how can i separate these two orders in the report.
    Your suggestions are appreciated
    Warm Regards
    Shreya

    Both are sales documents and should be separated by document type....i assume that all the documents are sotrd in the same infocube and if you have tha document type characteristic you can separated them directly in a report
    Regards

  • Function module for open sales order and open PO

    hi all,
    can anyone please tell me that is there any function module to get open sale order  and also for open purchase order?
    regards saurabh.

    Hi ,
    In EKPO Table u select this fields  Purchase Document no and Item no of Purchsing Document , Material no , and Purchase Order Qty.
    In MSEG Table u select this fields Purchase Document no and Item no of Purchsing Document , Material no , and  Qty.
    Both Tables having  Purchase Document  no , So  Purchase Doucment no throguh  u will get the Material and qty , Finally u Subract the both Material Qty's .
    u will get the Open Po For particular Material.
    If ur not getting ,Inform me .
    Regards ,
    Shankar GJ

  • Quantity is different from sale order and delivery

    Hi,
    Gurus,
    Quantity is different from sale order and delivery.
    I identified the Material in the sales order, the item category for this material as BOM.
    I have also checked the bill of material display header overview. The Base Quantity maintained as 1000 EA3. The SUBITEM maintained in G in the unit field in bill of material display.
    Accordingly i have checked the same for material master's additionl data in Units of Measure tab, it is mentioned the basic unit as 1000 EA3 and alternative unit as 600 G.
    My client processed the order for 100 QTY. The QTY for the two sub item is 99.601 each in the sale order.
    My client Question is why in delivery the Material Qty is coming as 99.730 and the SUB ITEM is coming as 99.330 EACH.
    Note:- The material X is maintained in EA3 in Bill of material header overview. I do no how the sale unit came as G for the Material in sale order.
    The other two sub item is perfectly coming as G. Because it is maintained in G in the Bill of Material Display.
    Guide me GURUS.
    Thanks and Regards,
    ANAND

    Hello Rumar
    I guess you entered the text manually in the sales order. The Ship-to may not be having any text, but the Sold-to may be and it may be coming from sold to.
    In transaction VOTXN, check the access sequence for the text type id and see which one takes precedence - one from customer master or from the order by checking the order of accesses.

  • Link Sales Order and PO and Pick & Pack

    Ability to add a manual Link between a Sales Order and Purchase order to reserve the item(s).
    Also do not allow Pick & Pack manager to create pick list for sales orders with an earlier date if other sales orders exists waiting for complete shipment.

    HI,
    WE can use the table VBKD (SALES DOCUMENT: BUSINESS DATA )
    1.  VBELN - Sales order
    2.  BSTKD - Customer Purchase order
    we can link these two fields and can pass the data in a internal table after that Vbeln is also present in
    Tables VBAP ( SALE DOCUMENT ITEM DATA )
    1. VBELN - SALE ORDER
    2. MATNR - MATERIAL NUMBER
    3. KWMENG - ORDER QUANTITY
    which could be used for further procssing
    Thanks
    Rajat

  • Creation of u201CHeader Textu201D in sales Order and Invoice

    Dear friends,
            Can any one guide me the complete configuration settings that are required for creation of u201CHeader Textu201D in sales Order and Invoice. Please help me to overcome this issue.
    Regards,
    Bhanu.

    Hello Bhanu...
    Hope you are aware of the configurations you need to maintain for the Text determination.Anyway, herewith are the steps that may help you to accomplish your requirement.
    Text Determination procedure for sales document header:
    Text can be determined at sales document header level or it can be imported from customer master. The process is...
    Define Text types:Path: Imgsales and distributionbasic functionstext controldefine text types
    Select sales document header. Click on text types go to new entries and define text types. For Eg:Z1
    Define Access sequence:
    Select sales document header
    Click on change icon
    Click on access sequence control button under dialog structure
    Go to new entries and define access sequence number with description.Ex: 55
    Save it and exit
    Define text determination procedure:
    Go to new entries
    Define text determination procedure.Ex: ZX save it and exit
    Assign text id's to text determination procedure:
    Select your text determination procedure(ZX)
    click on text id's in text procedure control button under dialog structure
    go to new entries and maintain entries. Text id:assign text id (Z1) that we defined in the previous step
    Specify sequence No-10
    Check Reference: this indicator specify that the text is reference or copies from preceding object
    Text in obligatory: text will be displayed during copying. the value of this field specifies whether text is obligatory or not and if it is obligatory the how it is to be displayed
    Apart from this... you also have to maintain the text in the Customer master as mentioned in the previous mail..
    For this you have to maintain the customer text.Do the following steps.
    1. Go to Customer master, Choose from the Menu Extras --> Text and mention the text
    2. Then in a sales order automatically wehn you are entering that sold to party..the header message will be appearing..
    In a nutshell i would request you to check weather you have maintained the Sales-Customer text KNVV and also that you have maintained all the required customizing settings for the text procedure, access sequence etc were completed....?
    Also make sure that the text type is also inclueded in the text determination procedure of the sales document header...
    Note: If all the settings of text determination exists and still if the text is not appearing then In sales document Header Text procedure, select sales header procedure, then select Texts in procedure. Check for the Header note, No. box is checked. This check mark ensures text is to be displayed when it is copied..
    Its should be working if all the requried setting are made....
    Reward if this helps..
    Thanks,
    Safeer Rahman

  • Any table keep track of Sales order and relevant IDOC

    hi all,
    Do we have any table to keep track Sales order and its relevant IDOC in the system?
    A list of sales order# given by user, from the list, we would like to find a faster way to get the corresponding IDOC.
    thanks.

    Hi Reetha,
    EDIDS table would have the IDOC Number & sales order number. Parameter 2 is the field in EDIDS which would have the sales order number.
    I understand that this table would have many records but i dont think any other table would have the above combination. If you get any other table, then pls. do update @ it on this thread.
    Thanks,
    Best regards,
    Prashant

Maybe you are looking for