Issue in creating sales order

Hi all,
I have created a contract of 10 ton. i have created a sales order of 20 ton with refernce to that contract. system just gives me a warning that sales order quantity exceeds contract quantity. I want error in place of warning.
How can i do that?
Please respond.
Best Regards,
AI.

HI,
in T code Vov7
you can select 'b" in completion rule.
also check this
Completion rule for quotation / contract
The rule for establishing when a quotation or contract is complete.
Use
You can, for example, specify that a quotation is complete only after its quantity has been fully referenced by subsequent documents. The system uses the completion rule to determine the status of a quotation or contract that has been referenced by other documents (by subsequent sales orders, for example).
Dependencies
If you want the system to apply the completion rule, you must first select the Update document flow field in document flow control in SD Customizing using the following menu path: Sales and Distribution --> Sales --> Maintain copy control for sales documents --> Copy control: Sales document to sales document (at item level).

Similar Messages

Issue when creating sales order with Sold-to/Ship-to Party's state

Hi All,
we have issue while creating Sales Order with picking up of State tax
for Ship-to-party & Sold-to-party.
<b>When we create a sales order, for the sold to party 140052732 and
ship to party 140052733 it is picking state tax. Which should not
suppose to pick? Because the partner is marked as tax exemption</b>.
Can any body tell me how can we solve this issue!
Why this is happening!
How to make not to pick tax when it is marked for tax exemtion.
As i am not Functional guy i am not aware what is happening here!
Can anybody solve this issue!
Thanks in advance.
Thanks,
Deep.

Hi Deep
What do you mean by "It is picking up state tax"? Does it mean that in the pricing procedure it is picking up a condition type which is meant for state tax?
If so go and check the condition record meant for it. Follow the following steps
1) Go to Sales order
2) Select the line item for which the state tax is being picked.
3) In the condition tab select analysis.
4) In Analysis you shall find the condition type meant for state tax.
5) See which condition record has been found.
6) Go to VK12, enter the state tax condition type and check the condition record for that state tax.
7) If wrong correct it.
8) If anything else come back to the post and inform the details
Thanks
Regards
Sunil

Issue when creating sales order with Sold-to/Ship-to Party's state tax

Hi All,
we have issue while creating Sales Order with picking up of State tax
for Ship-to-party & Sold-to-party.
<b>When we create a sales order, for the sold to party 140052732 and
ship to party 140052733 it is picking state tax. Which should not
suppose to pick? Because the partner is marked as tax exemption</b>.
Can any body tell me how can we solve this issue!
Why this is happening!
How to make not to pick tax when it is marked for tax exemtion.
As i am not Functional guy i am not aware what is happening here!
Can anybody solve this issue!
Thanks in advance.
Thanks,
Deep.

Hi Deep
What do you mean by "It is picking up state tax"? Does it mean that in the pricing procedure it is picking up a condition type which is meant for state tax?
If so go and check the condition record meant for it. Follow the following steps
1) Go to Sales order
2) Select the line item for which the state tax is being picked.
3) In the condition tab select analysis.
4) In Analysis you shall find the condition type meant for state tax.
5) See which condition record has been found.
6) Go to VK12, enter the state tax condition type and check the condition record for that state tax.
7) If wrong correct it.
8) If anything else come back to the post and inform the details
Thanks
Regards
Sunil

Issue in creating Sales Order in CRM 7.0 IC WEB

Hello Experts,
I am working on CRM7 and ECC 6 integration. I have configured Sales Order ( transaction type ZOR) in CRM. Using GUI the sales order is properly created in CRM and getting replicated to ECC without any issues.
I started configuring IC web UI, systematically followed C04 and C78 and completed all the steps including IC_BT transaction profile customization but inspite of this I am unable to create sales order in IC web.
I am geting error "No transaction type available for creating transactions" and if I go into details of this error it shows a page as follows
Diagnosis
No transaction type is available when creating a transaction. This can be due to the following reasons:
u2022     No transaction type is available according to Customizing
u2022     The user has no authorization for the transaction type
System Response
It is not possible to create the transaction.
Procedure
Make sure that:
u2022     The transaction type is set up in Customizing
u2022     The user has authorization for the transaction type
I have checked everything , nothing seems to be wrong. Can anyone advice how to resolve this issue
Thanks and Regards
Ambar

goto IMG where you defined the ZOR. Select the ZOR and choose Channel on the left, is ICW Interaction Center Webclient a choice? or add it.
We noticed that once any transaction was set to an option, we had to set these for all transactions in the ICWC, ISA, Gui, etc.

ISSUE ON CREATE SALES ORDER USING BAPI

Hi,
   I am creating a sales order using bapi BAPI_SALESORDER_CREATEFROMDAT2.But it it fails to create a sales order abd below is my code pls check and correct me to create a sales order.
LOOP AT DATA_TAB.
clear: l_order_header_in,
       l_salesdocument,
       l_order_partners,
       l_order_items_IN,
       l_order_schedules_IN.
refresh: l_order_items_in,
         l_order_partners,
         l_order_schedules_IN,
         l_return.
Order header
l_order_header_in-DOC_TYPE    = DATA_TAB-AUART.
l_order_header_IN-SALES_ORG   = DATA_TAB-VKORG.
l_order_header_IN-DISTR_CHAN = data_tab-vtweg.
l_order_header_in-division    = DATA_TAB-SPART.
l_order_header_in-REF_1_S     = DATA_TAB-IHREZ_E.
l_order_header_in-PURCH_NO_S = DATA_TAB-BSTKD_E.
l_order_header_in-PO_DAT_S    = data_tab-bstdk_e.
l_order_header_in-PO_METH_S   = DATA_TAB-BSARK_E.
l_order_header_in-DOC_DATE    = DATA_TAB-AUDAT.
l_order_header_in-REC_POINT   = DATA_TAB-EMPST.
l_order_header_inX-DOC_TYPE    = 'X'.
l_order_header_INX-SALES_ORG   = 'X'.
l_order_header_INX-DISTR_CHAN = 'X'.
l_order_header_inX-division    = 'X'.
l_order_header_inX-REF_1_S     = 'X'.
l_order_header_inX-PURCH_NO_S = 'X'.
l_order_header_inX-PO_DAT_S    = 'X'.
l_order_header_inX-PO_METH_S   = 'X'.
l_order_header_inX-DOC_DATE    = 'X'.
l_order_header_inX-REC_POINT   = 'X'.
Partner data SOLD TO PARTY
l_order_partners-ITM_NUMBER = DATA_TAB-POSNR.
l_order_partners-partn_role = 'SP'.
l_order_partners-partn_numb = DATA_TAB-kunnr1.
append l_ordeR_partners.
Partner data SHOP TO PARTY
l_order_partners-ITM_NUMBER = DATA_TAB-POSNR.
l_order_partners-partn_role = 'SH'.
l_order_partners-partn_numb = DATA_TAB-kunnr2.
append l_ordeR_partners.
Order items
l_order_items_IN-ITM_NUMBER = DATA_TAB-POSNR.
l_order_items_IN-material   = DATA_TAB-MABNR.
l_order_items_IN-BATCH      = DATA_TAB-CHARG.
l_order_items_IN-REASON_REJ = DATA_TAB-ABGRU.
append l_order_items_IN.
l_order_items_INX-ITM_NUMBER = DATA_TAB-POSNR.
l_order_items_INX-material   = 'X'.
l_order_items_INX-BATCH      = 'X'.
l_order_items_INX-REASON_REJ = 'X'.
append l_order_items_INX.
Schedules for quantity
l_order_schedules_IN-itm_number = DATA_TAB-POSNR.
l_order_schedules_IN-req_qty    = DATA_TAB-KWMENG.
append l_order_schedules_IN.
Schedules for quantity
l_order_schedules_INX-itm_number = data_tab-posnr.
l_order_schedules_INX-req_qty    = 'X'.
append l_order_schedules_INX.
Conditions for value
l_order_conditions_IN-itm_number = DATA_TAB-POSNR.
l_order_conditions_IN-cond_type = DATA_TAB-KSCHL.
l_order_conditions_IN-cond_value = DATA_TAB-KBETR.
l_order_conditions_IN-currency   = DATA_TAB-KOEIN.
append l_order_conditions_IN.
Conditions for value
l_order_conditions_INX-itm_number = DATA_TAB-POSNR.
l_order_conditions_INX-cond_type = 'X'.
l_order_conditions_INX-cond_value = 'X'.
l_order_conditions_INX-currency   = 'X'.
append l_order_conditions_INX .
endloop.
BAPI to create sales order
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
SALESDOCUMENTIN =
ORDER_HEADER_IN =      l_order_header_IN
ORDER_HEADER_INX =     l_order_header_INX
IMPORTING
SALESDOCUMENT =        l_salesdocument
TABLES
RETURN =               l_return
ORDER_ITEMS_IN =       l_order_items_IN
ORDER_ITEMS_INX =      l_order_items_INX
ORDER_PARTNERS =       l_order_partners
ORDER_SCHEDULES_IN =   l_order_schedules_in
ORDER_SCHEDULES_INX = l_order_schedules_inX
ORDER_CONDITIONS_IN = l_order_conditions_in
ORDER_CONDITIONS_INX = l_order_conditions_inX
IF SY-SUBRC = 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
   WAIT           = C_X
IMPORTING
RETURN        =
ENDIF.
Pls help me to solve the issue.
Thanks,
Rajendra.

Hi Raj
This is the sameple code which works fine for me,
REPORT zkb_sales_order.
DATA: w_order_header_in TYPE bapisdhd1,
      i_order_partners TYPE TABLE OF bapiparnr,
      w_order_partners TYPE bapiparnr,
      i_return TYPE TABLE OF bapiret2,
      w_return TYPE bapiret2,
     i_order_items_in TYPE TABLE OF bapisditm,
     w_order_items_in TYPE bapisditm,
     i_order_items_inx TYPE TABLE OF bapisditmx,
     w_order_items_inx TYPE bapisditmx,
    i_order_conditions_in TYPE TABLE OF bapicond,
    w_order_conditions_in TYPE bapicond,
    i_order_conditions_inx TYPE TABLE OF bapicondx,
    w_order_conditions_inx TYPE TABLE OF bapicondx.
CLEAR w_order_header_in.
w_order_header_in-doc_type = 'ZSO'.
w_order_header_in-sales_org = '1000'.
w_order_header_in-distr_chan = '01'.
w_order_header_in-division = '01'.
w_order_header_in-req_date_h = sy-datum.
w_order_header_in-sales_dist =   '000001'.
CLEAR: i_order_items_in,w_order_items_in.
w_order_items_in-material = 77.
w_order_items_in-salqtynum = 1.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    input = w_order_items_in-material
IMPORTING
    output = w_order_items_in-material.
APPEND w_order_items_in TO i_order_items_in.
* SP
CLEAR: i_order_partners,w_order_partners.
w_order_partners-partn_role = 'AG'.
w_order_partners-partn_numb = '2000016'.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
    input = w_order_partners-partn_numb
IMPORTING
    output = w_order_partners-partn_numb.
APPEND w_order_partners TO i_order_partners.
CLEAR: i_order_conditions_in,w_order_conditions_in.
w_order_conditions_in-itm_number = '000010'.
w_order_conditions_in-cond_type =   'PR00'.
w_order_conditions_in-cond_value = 100.
APPEND w_order_conditions_in TO i_order_conditions_in.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
*   SALESDOCUMENTIN               =
    order_header_in               = w_order_header_in
*   ORDER_HEADER_INX              =
*   SENDER                        =
*   BINARY_RELATIONSHIPTYPE       =
*   INT_NUMBER_ASSIGNMENT         =
*   BEHAVE_WHEN_ERROR             =
*   LOGIC_SWITCH                  =
*   TESTRUN                       =
*   CONVERT                       = ' '
* IMPORTING
*   SALESDOCUMENT                 =
TABLES
   return                        = i_return
   order_items_in                = i_order_items_in
*   ORDER_ITEMS_INX               =
    order_partners                = i_order_partners
*   ORDER_SCHEDULES_IN            =
*   ORDER_SCHEDULES_INX           =
   order_conditions_in           = i_order_conditions_in
*   ORDER_CONDITIONS_INX          =
*   ORDER_CFGS_REF                =
*   ORDER_CFGS_INST               =
*   ORDER_CFGS_PART_OF            =
*   ORDER_CFGS_VALUE              =
*   ORDER_CFGS_BLOB               =
*   ORDER_CFGS_VK                 =
*   ORDER_CFGS_REFINST            =
*   ORDER_CCARD                   =
*   ORDER_TEXT                    =
*   ORDER_KEYS                    =
*   EXTENSIONIN                   =
*   PARTNERADDRESSES              =
READ TABLE i_return INTO w_return WITH KEY type = 'E'.
IF sy-subrc NE 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
ENDIF.
LOOP AT i_return INTO w_return .
WRITE: / w_return-type,
w_return-id,
w_return-number,
w_return-message.
ENDLOOP.
Regards
Kathirvel

Issue in creating sales order with ref contract(quantity)

hi friends,
I am creating sales order with reference contract using
"BAPI_SALESORDER_CREATEFROMDAT1"
my issue is with quantity field when i am entering quantity as 1 then it is taking as 0.001
i am also declaring its unit field too but there is no change.
in my program i am taking quantity as parameter.
field description is like this Order qty in sales units - 00009001 corresponds to 9.001
is there any chance of changing the quantity .
please help.

There is another similar post...look at those comments. Consider the data types in use...in true numeric fields with decimals, the decimal is implied, so look at how you're sending and/or converting any value.... For instance, if I were sending data to a quantity field described as curr 15, decimals 3, I would expect that I needed to send 1.000 (or perhaps 1000, depending on my testing) in the input to get a quantity of 1.

Issue in creating sales order using process_header API (web service)

Hi All,
I am trying to create sales order header using web service call to OE_ORDER_PUB.Process_header API.
When I pass the inputs and test the service,I get output with return_status='S'. But no record falls at the OE_ORDER_HEADER_ALL table.
I cant identify where the problem is.Is there any commit missing? Pls help me resolve this issue.
Thanks,
Vinoth

Hi All,
I am trying to create sales order header using web service call to OE_ORDER_PUB.Process_header API.
When I pass the inputs and test the service,I get output with return_status='S'. But no record falls at the OE_ORDER_HEADER_ALL table.
I cant identify where the problem is.Is there any commit missing? Pls help me resolve this issue.
Thanks,
Vinoth

Issue in creating sales order using process_header API

Hi all,
We have a requirement to create sales order using apps adapter in ebiz from SOA suite composite.I used OE_ORDER_PUB.Process_header API to create order header.
When I pass the inputs and test the service,I get output with return_status='S'. But no record falls at the OE_ORDER_HEADER_ALL table.
I cant identify where the problem is.Pls suggest me with the things to resolve this issue.
Thanks,
goutham

Hi all,
We have a requirement to create sales order using apps adapter in ebiz from SOA suite composite.I used OE_ORDER_PUB.Process_header API to create order header.
When I pass the inputs and test the service,I get output with return_status='S'. But no record falls at the OE_ORDER_HEADER_ALL table.
I cant identify where the problem is.Pls suggest me with the things to resolve this issue.
Thanks,
goutham

Issue in creating sales order using BAPI's...?

Hi Guru's,
i had generated the sales order using the BAPI..but could please guide me how to declare the data declaratin same fields as globally and how to move internal table and how to append ....
thanks in advance...
REPORT z_bapi_salesorder_create.
Sales document type
PARAMETERS: p_auart TYPE auart OBLIGATORY.
Sales organization
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
Distribution channel
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
Division.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
Sold-to
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
Ship-to
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
Material
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
Quantity.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
Plant
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
    EXPORTING
      sales_header_in     = header
      sales_header_inx    = headerx
    IMPORTING
      salesdocument_ex    = v_vbeln
    TABLES
      return              = return
      sales_items_in      = item
      sales_items_inx     = itemx
      sales_schedules_in = lt_schedules_in
      sales_schedules_inx = lt_schedules_inx
      sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
   COMMIT WORK AND WAIT.
     call FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.

*& Report ZAREPAS30
REPORT zarepas30.
DATA : gs_vbeln                   TYPE vbak-vbeln,
       gs_order_header_in         TYPE bapisdhd1,
       gs_order_header_inx        TYPE bapisdhd1x,
       gt_order_items_in          TYPE STANDARD TABLE OF bapisditm,
       gwa_itab1                  TYPE bapisditm,
       gt_order_items_inx         TYPE STANDARD TABLE OF bapisditmx,
       gwa_itab2                  TYPE bapisditmx,
       gt_order_partners          TYPE STANDARD TABLE OF bapiparnr,
       gwa_itab3                  TYPE bapiparnr,
       gt_return                  TYPE STANDARD TABLE OF bapiret2,
       gwa_itab4                  TYPE bapiret2.
Sales document type
PARAMETERS: p_auart TYPE auart OBLIGATORY.
Sales organization
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
Distribution channel
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
Division.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
Requested Delivery Date
PARAMETERS: p_edatu TYPE edatu OBLIGATORY.
Sold-to
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
Ship-to
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
Material
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
Quantity.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
Plant
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
gs_order_header_in-doc_type = p_auart.
gs_order_header_inx-doc_type = 'X'.
Sales organization
gs_order_header_in-sales_org = p_vkorg.
gs_order_header_inx-sales_org = 'X'.
Distribution channel
gs_order_header_in-distr_chan = p_vtweg.
gs_order_header_inx-distr_chan = 'X'.
Division
gs_order_header_in-division = p_spart.
gs_order_header_inx-division = 'X'.
Reguested Delivery Date
gs_order_header_in-req_date_h = p_edatu.
gs_order_header_inx-req_date_h = 'X'.
gs_order_header_inx-updateflag = 'I'.
Partner data
Sold to
gwa_itab3-partn_role = 'AG'.
gwa_itab3-partn_numb = p_sold.
APPEND gwa_itab3 TO gt_order_partners .
ship to
gwa_itab3-partn_role = 'WE'.
gwa_itab3-partn_numb = p_ship.
APPEND gwa_itab3 TO gt_order_partners .
ITEM DATA
gwa_itab2-updateflag = 'I'.
Line item number.
gwa_itab1-itm_number = '000010'.
gwa_itab2-itm_number = 'X'.
Material
gwa_itab1-material = p_matnr.
gwa_itab2-material = 'X'.
Plant
gwa_itab1-plant    = p_plant.
gwa_itab2-plant   = 'X'.
Quantity
gwa_itab1-target_qty = p_menge.
gwa_itab2-target_qty = 'X'.
APPEND gwa_itab1 TO gt_order_items_in.
APPEND gwa_itab2 TO gt_order_items_inx.
Line item number.
gwa_itab1-itm_number = '000020'.
gwa_itab2-itm_number = 'X'.
Material
gwa_itab1-material = p_matnr.
gwa_itab2-material = 'X'.
Plant
gwa_itab1-plant    = p_plant.
gwa_itab2-plant   = 'X'.
Quantity
gwa_itab1-target_qty = p_menge.
gwa_itab2-target_qty = 'X'.
APPEND gwa_itab1 TO gt_order_items_in.
APPEND gwa_itab2 TO gt_order_items_inx.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
    order_header_in               = gs_order_header_in
    ORDER_HEADER_INX              = gs_order_header_inx
IMPORTING
    SALESDOCUMENT                 = gs_vbeln
tables
    RETURN                        = gt_return
    ORDER_ITEMS_IN                = gt_order_items_in
    ORDER_ITEMS_INX               = gt_order_items_inx
    order_partners                = gt_order_partners.
Check the return table.
LOOP AT gt_return into gwa_itab4 WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error occured while creating sales order '.
ELSE.
Commit the work.
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Document ', gs_vbeln, ' created'.
ENDIF.

Confirmation Quantity issue while creating Sales order using BAPI

Hi SDN,
Can anyone of you help mein the below issue:
I have a program to create a sales order using upload file. for this i use "BAPI_SALESORDER_CREATEFROMDAT2" & for changing existing "BAPI_SALESORDER_CHANGE".
Now If the upload file contains the Same Material, Based on other conditions, it needs to create Multiple sales order.
When the first Salesorder is created, the Quantity is getting confirmed (Confirmed quantity VBEP-BMENG). But during actual run, since the confirmation is getting done for the same material in the above Sales order, the confirmation is not being done in the subsequent Sales order".
This poses a problem for business, user need to manual refresh the u201Cconfirmed quantity for each line item in the particular SO where it failed during program upload.
Also while uploading using the BAPI, if we wait forsometime after creating the first sales order in Debug, then the above material is unlocked & the confirmation quantity is done for the subsequent sales order also.
But in the actual run, this is creating a problem. Some Refresh or Unlocking problem.
Can you please suggest a suitable solution for this issue.
Thanks & regrads,
Chaitanya LBK

Have you tried backorder processing?
V_V1
V_V2
V_RA
V_R1
V_R2

Issues in creating sales order

I have created a new "sales document type" and assigned to particular sales area, but when I am creating an order user that "sales document type ", In the initial screen I have select "ZDIS" as sales order 1000/10/10 as sales area after entering this data when i come on the order screen the ship to party
and sold to party field is disabled, but when i creating the order with another "sales document type"
those field are open, plz help me out.

Hi,
You have to check the Partner Determination Procedure - and respective assignements to relavant document types.you can check in VOPA T.code.
Regards,
Sirisha

Issues :- after creating sales order mail goes to customer

Hello everybody , my requriment is that
after creating the sales order , the sales order number goes to the customer
so how can i solve this requriment
i tryed to find out user-exit but i didn't get proper EXIT point .
please help me out
ASAP

Hi Sandeep
Your requiremet is not clear.
I hope you want to send Sales order details to Customer via email.
If Yes.
You can configure in NACE transaction for Medium 5, this is purely functional, contact your functional consultant
Regards
Madhan

Issue with profit center while creating sales order (VA01).

Hello Gurus,
When I creating sales order (Material need to be configure from VA01->Extra->Configuration) with reference of existing then XVBAP is populating the correct profit center. But when creating new sales order from scratch for the same material, at that time XVBAP is getting wrong profit center for index 2.
Thanks in Advance!!

Debugging Sales order at Enhancement MV45AFZB ->form userexit_move_field_to_cobl.

Updating price in already created sales order

Hi all,
I have an issue. When we create sales order, system will display current date pricing on sales order, for example total value of sales order is 9000. Now before delivery, prices change and we have to manually update price on sales order individually. Is there any report available that can update price of all already created sales orders instead of going on sales order and update one by one.
Please respond.
Best Regards,
AI.

Hello,
You can update the pricing for all the created orders at a time in VA05 .
Goto Transaction code VA05 and give all the sales orders and then in the MENU click on
EDIT->MASS CHANGE>NEW PRICING
And update the New pricing, then will carry out new pricing for all the sales orders at a time.
OR,
There is also one function module SD_BULK_CHANGE , Create your own Query in SQV1 and make changes.
Hope it will resolve , Please revert if you need further details
thanks,
santosh

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

Issue in creating sales order

Similar Messages

Maybe you are looking for