Sales Order is getting created without quantity field getting populated?

Hi All,
I am creating sales order with the help of IDocs. Here I am using the standard function module IDOC_INPUT_ORDERS.
But, when I execute this function module idocs are getting generated successfully but the quantity field is not getting updated. It is getting populates as Zero.
With in this function module there is a perform to check_idoc_orders, when the data flow comes to this point quantity field MENGE is getting cleared.
So just want to know what could be the reason why quantity field is getting cleared.
Raghu

Hello
Q1 )
If I change option 1 or 2 :
1 User decides on creation if material is missing
Answer:If Material is not Created the system wont allow to add you that material until unless you create the material master created.I am considering here that you don't have material master
2 Creation even though no material is available
Answer:It will allow you to create the work order.i am considering here that you don't have sufficient stock.
Q2) what should be the expected Status for Option 1 or 2.
Before Config it was showing
Status is showing Mat.availability not checked ( MANC ).
After Option 1 or 2, Expected Status ?
Answer: You need to enter value 02 on the Availability Check field on the MRP3 tab of Material Master via TC MM02.
you will be get Material committed MACM after Saving the Order.
Br
Rakesh

Similar Messages

Sales Order Pricing : Access Not Made (initilized field).

Dear members,
In my sales order for a condition type, I am getting message as access not made (Initialized field) and there is a yellow Exclamation mark on one of the field (field name is price group).
I have a condition record maintained, But why I am getting this message.
I have read some threads here and saw my access sequences and went down to table fields, all table fields are correct. (meaning The see komk fields are assigned to document fields).
If this yellow mark comes, is it be configuration error or a data error ?
please let me know. Thank you
Madhu.

Hi Madhu
Go to the access sequence and check wheather sub-routines has been maintained.in the access sequence or Exclusive box has been checked for any key combination. If it has been checked then remove that check box and then create the sales order. then there wont be any problem
Regards
Srinath

Extending sales order change BAPI and updating custom fields

Hi
i added 3 new fields into VA01/02/03 screen.i added at the header level in the additional data tab B area and appended them in VBAK table.
i want to change these values using sales order change BAPI.i added the fields in the structure VBAKKOZ,VBAKKOZX,BAPE_VBAK,BAPE_VBAKX.
may i know what else i need to do?should i move them anywhere with in the code or does the bapi take those values automatically using EXTENSIONIN structure?
also can some one send me code to actually check if bapi is changing my values?
if poss tell me how should i populate values into BAPI.

After adding field in structures VBAKKOZ,VBAKKOZX,BAPE_VBAK,BAPE_VBAKX, create pair of name-value pair extensiot structure and value.
Fill values as follows :
Data :   ls_parex TYPE bapiparex,
            lt_parex TYPE STANDARD TABLE OF bapiparex.
ls_parex-structure = 'BAPE_VBAK'.
ls_parex-valuepart1+0(10) = Sales order no
ls_parex-valuepart1+10(XX) = somevalue. <---- Value for custom field no 1
ls_parex-valuepart1+XX(XX) = somevalue. <---- Value for custom field no 2
APPEND ls_parex TO lt_parex .
clear ls_parex.
ls_parex-structure = 'BAPE_VBAKX'.
ls_parex-valuepart1+0(10) = Sales order no
ls_parex-valuepart1+10(1) = 'X'. <--- checkbox mark for custom field no 1
ls_parex-valuepart1+11(1) = 'X'. <--- checkbox mark for custom field no 2
APPEND ls_parex TO lt_parex.
Same pair for VBAKKOZ & VBAKKOZX
Updating custom fields
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
      salesdocument    = Sales order number
      order_header_inx = 'U'   <--- U for update
    TABLES
      extensionin      = lt_parex[].
Edited by: nkarwa on Oct 25, 2010 12:39 PM

What is the difference between sales order with picking and without picking

hi friends,
i would like to know what is the difference between sales order with picking and without picking.
thanks
skrishnan

Hello,
Picking refers to preparing the right quantity and quality of goods for shipping on schedule as required by the customer.
Once picking is configured, SAP Sd automatically generates picking lists and picking labels which can be tagged to the relevant goods. SAP can be configured to ensure that picked quantity is confirmed before goods are issued. This can be done using transaction code VSTK. In T-code VSTK, picking confirmations can be set, which ensure that goods picked for delivery are in accordance with picking slips.
Picking thus helps in monitoring each item using the picking status. Picking is normally done in SAP SD by a shipping clerk.
Prase

Sales order cannot be created for the delivery date before 20.10.2008

when i create a sales order today (18102008) sales order cannot be created for the delivery date before 20.10.2008
how the system is checking the 2 days duration for delivery date - which table is having this duration days.
is it dependent on sales order type.....
actually i checkeup in V0V8 - even then i couldn't solve this error when i am creating the sales order.
Pls suggest

Dear Selvamuthu
In normal circumstances, you can create as many as sale orders as you can irrespective of delivery date, and system will not prevent to create unless you apply some user exit for some reason.
Check any user exit is applied for that sale document type where some logic would have been written in such a way that if stock is available, sale order can be created.
thanks
G. Lakshmipathi

Sales order to automatically create assembly order

Hi one and all,
How to set up a system to be able to choose materail requriment transferred from sales order to automatically create an assembly order, a planned order, and a process order?

Hi,
Assigh the repective Planning startegy group at MRP view of material Master.
81 - Assembly porcessing for planned order
82 - Assembly porcessing for production order.
86 - Assembly porcessing for Process order
Try with this and crate Sale order.
Regards
PradeeP

Want to see the sales order which is created with reference

Hi Gurus,
I created a sales order with reference to a contract. I forgot the sales order number and contract number..
how can i search my sales order which is created w.f.t acontract.we dont have the access for VA42, VA45.
cHEERS,
Sumith

Dear Sumith
Go to VA05, click your mouse on "Further sel.criteria", so that you will have some options to choose like "Sales Document Type", "Created by".
You can choose either of these and execute so that it will display the respective document.
thanks
G. Lakshmipathi

Sales Order is not creating with reference to Quantity Contract.

Dear SAP Experts,
I am creating a Sales Order with reference to quantity contract but system showing an error *"""Material SUG10051 does not exist in RG1 Table for Excise Group 42 - Message no. ZCOMM002"""* i am not getting y system showing this error because all the necessary configuration for series group is maintained already.
Please advise me what should i do.
Looking forward for your quick response on the same.
Regards
Parul Deshwal

Hi
As per STD SAP, all billing items will be updated in RG1 register.
The control is in J1ID where you have to select "Material and Chapter ID combination" and choose the tab "Material type".
There against the billing material code, maintain "F"
Also check setting
IMG --> Logistics General --> Taxes on Goods movements --> India Check Basic Settings, Master Data, A/c deteremination, Business transactions and Tools.

Getting error in while changing sales order which is created using BAPI

Hi All,
   I have created the sales order using BAPI ( BAPI_SALESORDER_CREATEFROMDAT1 ) and i am successfully creating sales order using this BAPI. But while i want to change sales order iam changing Shipping Conditions in Header Data of sales order .its giving an error .can any know any thing about this.
Error mesage :    No status object is available for SDI 300082407/10    (Order Number/Item Number)
In Header i am passing these values ...
     wa_order_header_in-doc_type = vbak-auart.
    wa_order_header_in-sales_org = vbak-vkorg.
    wa_order_header_in-distr_chan = vbak-vtweg.
    wa_order_header_in-division = vbak-spart.
Do i required to pass the below values ? in Header structure ( BAPISDHEAD1 ).
REFOBJECTTYPE
REFOBJECTKEY
REFDOCTYPE
Regards,
Sudhakar Reddy A

rectified

Sales Order Material Determination Cannot Change Quantity of the Sub-item

Hi SAP Guru's,
Has anyone encountered this scenario?
1. Created a standard order with an item as material substitution
2. Created a pro-forma invoice referencing the sales order created
3. Went into VA02 to change the item quantity of the higher level item in the material substitution
Expectation is that once you change the quantity of the higher level item, the quantity of the sub-item should also reflect whatever is in the quantity of the higher level item.
Actual Result is that only the higher level item quantity is changed, the sub item quantity remained the same.
Is there any configuration or copy control that we can check regarding this?

Hi Maurice,
Apologies! The qty of the sub item should change when you change it in VA02 even after proforma is created.
Could you pls check the item categories TAX and TAPS config i.e. the material entered should get item category TAX and the sub item should have TAPS or the item categories should have same configuration as TAX and TAPS.
Please check.
Regards,
Raghu.

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

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");

Sales order do not create after SAP upgradation to package EHP7

Dear Experts,
SAP client is recently upgraded to EHP7. Since then we are observing difficulty in Sales order creation [VA01] manually [with or without order reference].
When click on SAVE button, entire screen display get freezed, without any message [Error/Information/Warning] pop-up. it seems as if system was trying to display message; caused due to any kind of event occurrence; but unable to show up.
Moreover, when we click on "BACK" or "EXIT" button, then it prompts choices to save the data. Yet again we receive the same freeze response whenever chose "Yes" option.
Please note:- before up-gradation, we were able to create orders with the same data, what we are using to create now.
Any help or clue on this subject would be highly appreciated.
Thank you for all your help.
Best regards,
Rahul Agarwal

Hi,
did you check what are the sales orders Enhancements that are activated with EHP7 under T.code-SFW5

Email Sales Order Confirmation to "Created By" -

Hi Experts
I have a requirement where we need to email the Order confirmation output to the person who has created the sales order.
So lets say i am creating a sales order and my user id is 9999. (SY-UNAME).
Now as we have implemented HR module and our PERNR and user name are same.
So in other words my PERNR will also be 9999 and email is maintained in HR record and well as user record.
How can i achieve this functionality and Email order confirmation printout to "Created By".
We dont want to send order confirmation to SP or SH but just created by.
Thanks in advance.

HI Shiva,
I did exactly as you said but it send the email to the email ID maintained in Ship-to-party customer.
I think "Recipient" field is just used for cover page (Incase you are printing cover page), i dont think SAP uses it for sending the form output.
I think SAP sends output based on the partner function, so if i specify SH, SAP will send it to SH.
I tried using "Created By" partner type too and all email setting are maintained for the creator and printer is properly setup but it doesn't allow me to use this partner function.
I tried using both "$1" and "§§" but both of them doesn't work.
I have also tried using Employee responsible partner type "ER" but even that doesn't work.
Will appreciate if you can provide a solution for this.
Thanks in advance.

Temporary invoice on sales order containing items with & without delivery

Hi,
I have a sales order which contains both items due to be billed on delivery and due to be billed without delivery.
Could you please let me know how to create a temporary invoice on the basis of the order. The true/final invoice will work on the basis of the goods issue for the items on delivery and on the order for the other items.
Thanks,

Order & Delivery Related Billing depends on Item Category.First check these settings in VOV7.Now check the Copy Control settings in VTLA for Item Category relevant for Delivery Related Billing (F2).
Now check in VTFA for Item Category relevant for Order Related Billing (F5).
As per my understanding , you need the Final Invoice with both Line Items which could not be possible as Billing relevance is different for these two Items.
Best Regards,
Ankur

Sales Order is getting created without quantity field getting populated?

Similar Messages

Maybe you are looking for