Problem with creation of Sales Order with reference to Contract

Hi,
I have a problem when creating Sales order with reference to Contract , shipping condition was not copied. Is there any existing copy routines suitable to accomodate this?
Thanks!

your functional team can help you in finding one.

Similar Messages

Creation of sales order with reference to inquiry no.

Hi gurus!
Im having trouble in creation of sales order with reference to inquiry no. The scenario is like this one. In va11(creation of inquiry no.), in the field of SERVICE LEVEL, i indicated a value. after the creation of inquiry no, i want to create a sales order with reference to inquiry no. But the problem is, the SERVICE LEVEL field does not have any value. What is the main problem to this scenario? is it the VARIANT CONFIG or the program itself? please help its urgent
Regards,
Mackoy

Dear Machoy,
In IMG under
Sales and Distribution -> Sales -> Sales Documents -> Maintain Copy Control for Sales Documents -> Copying Control: Sales Document to Sales Document
or Transaction VTAA
http://help.sap.com/erp2005_ehp_02/helpdata/en/70/a7853478616434e10000009b38f83b/frameset.htm
If you create a sales document with reference to a preceding document, the system copies nearly all the data from the preceding document. The data in the preceding document originally comes from the customer and material master records. Because the data is copied from the preceding documents into the sales document, any changes that have been made to the master data records since the preceding document was created are not included in the sales document. If, when you create with reference, you add another item to the document that was not in the preceding document, the system determines the data for it from the master records, such as the material master or info record.
You have created an inquiry and a quotation with reference to this inquiry. Before you created the quotation, you changed some data in the material and customer master records.
You have changed the material description in the material master record. This description is stored in the sales document at item level.
You have changed the terms of payment in the customer master record from ZB01 to ZB03. These are stored in the sales document at header level.
When you created the inquiry, the system copies the original material description to the item. If you enter another item in the quotation for the same material, the system displays the new material description for the new item.
However, the system continues to propose the original term of payment, that is, ZB01, for all items including the new one. This is because it is copied from the header of the preceding document into the header of the quotation, and the change in the customer master record has no affect on the quotation.
Regards,
Naveen.

HOW TO CONTROL ON CREATION OF SALES ORDER WITH REFERENCE TO EARLIER SO?

Dear All,
I want to contol on creation of Sales order with reference to earlier SO? While creation of sales order our enduser are creating sales order with reference to earlier month SO which I want to restrict. Recently I made changes in sales order like payment terms is grayed, system will atomatically pick pay terms from customer master.Now I am getting correct data also but enduser is using old SO no while creating new SO and old payment data is reflecting in fbl5n.
I want to restrict enduser while creating new SO with ref. to old SO. Only for returns they should be able to use Billing refrence. Pl. suggest how to control the with reference to ealier SO.
Nikhil

Nikhil Deshpande,
If you dont want allow create a sales order in referent to other one, just delete the copy control between these sales order type, so when the user tries to create a SO in reference to other one a message is displayed that is not possible.
Thanks,
Mariano.

Creation of sales order with reference to Quotation using BAPI

Hi All,
I am using BAPI "BAPI_SALESORDER_CREATEFROMDAT2" for creating sales order. Can you please tell how can I create a sales order with reference to a Quotation.

Vinit,
In your header structure, set like this:
hdr-REF_DOC = i_order-vbeln. "assign quotation # to sales order
hdr-REFDOC_CAT = 'B'.         "assign Quotation to VBTYP_N.
For each line item, set as follows:
Assigning ref doc to create line item entries in VBFA.
    itm-REF_DOC    = i_order-vbeln. "quote number
    itm-REF_DOC_IT = i_vbap-posnr.   "quote line item #
    itm-REF_DOC_CA = 'B'.
data: ret_text type BAPIRET2.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
      ORDER_HEADER_IN           = hdr
      convert                   = 'X'
    IMPORTING
      SALESDOCUMENT             = salesdoc
    TABLES
      return                    = ret_tbl
      ORDER_ITEMS_IN            = itm
      ORDER_PARTNERS            = prtnr
      ORDER_ITEMS_inx           = itmx
      ORDER_CONDITIONS_IN       = conds
      ORDER_CONDITIONS_INX      = condsx
      order_schedules_in        = schd_lin.
Don't forget those points.

Creation of sales order with reference - Zfields in Add data B are not cop

Hi all,
Please help me in the issue . I am creating sales order with reference to returns order . All item fields are getting copied but the Zfields which are added in addtional data b of sales order are not getting copied. Can anyone please let me know the procedure to copy the custom fields.
Thanks in advance,

The setting of field when copy by reference is best done in the copy rules.
If you go to transaction VTAA, and look to the order type you are copying to, you will find a data transfer rule number.
Then go to transaction VOFM, menu option DATA TRANSFER -> ORDERS and find the matching data transfer rule number.
Select and press the "Source text" button, here you will find the data from the copied order in structure CVBAK, and you can apply the code to set the VBAK structure fields appropriately.
This should then populate the data on the copied order.

Issue with creation of sales order in CRM system

Hi Experts,
Here are the details of the process we followed
1.     We found a Function Module u201CBAPI_BUSPROCESSND_CREATEMULTIu201D which is used to create a sales order in CRM.
2.     We have set a Break point in the FM u201CCRM_ORDER_MAINTAINu201D and tried to create a sales order using the transaction u201CCRMD_ORDERu201D. For this the parameters we have given are
a.     sold-to-party
b.     ship-to-party
c.     quantity
d.     product
And after this we have saved the order and the order is saved and in the debug mode we have the parameters in u201CCRM_ORDER_MAINTAINu201D and we found all these     parameters in the FM.
3.     After this we have given all the parameters mentioned above in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and still the order is not created, gave an error message saying that CRM_ORDER: Incorrect values in the interface object.
4.     We checked the CRM_ORDER badiu2019s interface and it is having only header guid to be given. We gave this header guid also in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and then it gave a different error saying that : Document cannot be saved.
5.     Finally we are not able to know the parameters to be passed to the FM to create an order.
Any inputs will be highly appreciated.
Thanks a lot in advance.
Lakshman.

Hi Easwar,
Now i am able to create a sales order by passing the parameters to "BAPI_BUSPROCESSND_CREATEMULTI" and the parameters i am passing are Process_type in the ORDERADM_H, parner_fct (partner function), partner_no , Quantity and prod_ordered (product name) but after creation of sales order using my report program and if i see the sales order uisng transaction crmd_order (using transaction ID) or crmd_orderadm_h(using headerguid) or crm_order_index, only the PROCESS_TYPE is updated but the remaining parameters which i passed like QUANTITY,PRODUCT NAME,PARTNER NUMBER are not present in the sales order. I am providing the code which i have written for creation of the sales order. Can you please look into it and tell me where i might have went wrong??
*& Report ZCREATEORDER_TEST
REPORT ZCREATEORDER_TEST.
DATA : LV_HEADER_GUID TYPE GUID_32,
WA_HEADER            TYPE         BAPIBUS20001_HEADER_INS,
ITAB_HEADER          TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
ITAB_CREATED_PROCESS TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
ITAB_OBJECTS_TO_SAVE TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS,
ITAB_PARTNER        TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_INS,
lt_product_i TYPE STANDARD TABLE OF BAPIBUS20001_ITEM,
wa_product_i type BAPIBUS20001_ITEM,
lt_schedlin_i type standard table of BAPIBUS20001_SCHEDLIN,
wa_schedlin_i type BAPIBUS20001_SCHEDLIN,
ITAB_INPUT_FIELDS TYPE TABLE OF bapibus20001_input_fields,
ls_inputfields TYPE bapibus20001_input_fields,
WA_PARTNER          TYPE BAPIBUS20001_PARTNER_INS,
ITAB_RETURN          TYPE STANDARD TABLE OF BAPIRET2,
WA_OBJECTS_TO_SAVE LIKE LINE OF ITAB_OBJECTS_TO_SAVE,
           "To store the Objects to be saved.
WA_CREATED_PROCESS LIKE LINE OF ITAB_CREATED_PROCESS,
ITAB_SAVED_OBJECTS   TYPE STANDARD TABLE OF BAPIBUS20001_OBJECT_ID,
WA_SAVED_OBJECTS    LIKE LINE OF ITAB_SAVED_OBJECTS,
GC_X type c.
gc_x = 'x'.
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    ev_guid_32 = lv_header_guid.
CLEAR : WA_HEADER.
Passing the respective values from the Header table to internal table.
WA_HEADER-GUID          = LV_HEADER_GUID.
WA_HEADER-PROCESS_TYPE = 'ZTA'.
APPEND WA_HEADER TO ITAB_HEADER.
*Appending the values to the ITAB_HEADER.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'ORDERADM_H'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'PROCESS_TYPE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
*ls_inputfields-ref_handle = '0000000000'.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-objectname = 'ORDERADM_H'.
ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'ORDERADM_H'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'GUID'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CHANGES MADE
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'LOGICAL_KEY'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'GUID'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
   ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'QUANTITY'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
   ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CHANGES MADE
WA_PARTNER-REF_GUID = LV_HEADER_GUID.
WA_PARTNER-REF_KIND = 'A'.
giving the partner function and partner no 000000038 for slod to party
WA_PARTNER-PARTNER_FCT = '00000038'.
WA_PARTNER-PARTNER_NO = '10017'.
APPEND WA_PARTNER TO ITAB_PARTNER.
*"ADDING VALUES for the product
wa_product_i-header        = lv_header_guid.
wa_product_i-handle        = '0000000001'.
wa_product_i-ordered_prod = '12000014'.
wa_product_i-mode          = 'A'.
APPEND wa_product_i TO lt_product_i.
*"ADDING VALUES for quantity
wa_schedlin_i-quantity   = 30.
wa_schedlin_i-handle = 1.
APPEND wa_schedlin_i TO lt_schedlin_i.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
*ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'REF_GUID'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'PARTNER_FCT'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'PARTNER_NO'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
TABLES
    HEADER          = ITAB_HEADER
    ITEM            = lt_product_i
    RETURN          = ITAB_RETURN
    PARTNER         = ITAB_PARTNER
    INPUT_FIELDS    = ITAB_INPUT_FIELDS
    CREATED_PROCESS = itab_created_process
    SCHEDULELINE    = lt_schedlin_i.
READ TABLE ITAB_CREATED_PROCESS INTO WA_CREATED_PROCESS WITH KEY GUID = LV_HEADER_GUID BINARY SEARCH.
WA_OBJECTS_TO_SAVE-GUID = WA_CREATED_PROCESS-GUID.
Appending the Guid of the contract to be saved to the internal table
APPEND WA_OBJECTS_TO_SAVE TO ITAB_OBJECTS_TO_SAVE.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
EXPORTING
    update_task_local = space
    save_frame_log    = GC_X
TABLES
    objects_to_save   = itab_objects_to_save
    saved_objects     = itab_saved_objects
    return            = itab_return.
Calling the Standard BAPI to Commit the transcation.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
I have debugged the above code, all the values are passing are passing to the FM "'BAPI_BUSPROCESSND_CREATEMULTI'" and these passed to the CRM_ORDER_MAINTAIN and then to CRM_ORDER_READ which are called inside the "'BAPI_BUSPROCESSND_CREATEMULTI'". Finally the sales order is created but not able to see all the values that i am passing except PROCESS_TYPE.
Thanks a lot in Advance,
Lakshman.

Sales order in reference to contract by default

Hello all!
I know that the standart SAP behavior while "create with reference" from va01 is to show all possible docs based on which I can create my sales order. For sales order by default we have quotation.
Do you know if it is possible to change this screen and make contract by default?
It should be possible to create sales order in reference to any of these docs, but contract should be by default instead of quotation.
Much thanks!

Hai Skally,
In sales order : Create with reference icon runs
Program Name       SAPLV45C
Screen Number      0301
To make Quotation as Default
Ask your abaper to change the screen Number default from 0301 to 0302
Program Name       SAPLV45C
Screen Number      0302
Regards,
Mani

Problem when creating a sales order with reference by BAPI

I am facing one problem when creating Sales Order.
The scenario is like this while creating SO With reference to an Order type, a new SO will be automatically created with a diff order Type.
I am using "BAPI_SALESORDER_CREATEFROMDAT2".
I am calling this BAPI in USEREXIT_REFRESH_DOCUMENT.
Am I using the right exit to call this Bapi ?
Problems are like :
1. Ref Sales Order creating without Sales Unit .
2. "Object Status does not exist" error msg is coming for Header and Item level(when clicking the status tab and then object status pushbutton). But if testing the bapi from SE37 in test sequence....no such problem persists.
As for example in case of sales unit,in the debugging mode i have seen that BAPI uses a perform to fill the values in the VBAP structure.But after that when it come back to the main program VBAP remains blank.This ocuurs when the BAPI is called from the exit whereas if tested from SE37, VBAP retains the value.
Can u suggest in this ? This is very very urgent............
Thx in Adv.........................

Thanks........
Your suggestion was a great help to me.I have used a custom FM and called it in starting new task.
Since i am a university fresher working in SAP for nearly 1 year.....can you please explain me the difference between in update task and starting new task.Why the problem was occuring for which you have suggested to call a custom function module.
what is V1 update and V2 update?Is it attached with asynchronous ans synchronous update.It would be a great help to me if you kindly clear my confusions....
thanks in advance.

Variant Matching during Creation of Sales Order with reference to Contract

Hi All,
I have a following scenario. Sales Contract is created on a Configurable Material ' A' and its has a Material Variant "B" with following Charac Values X = X1, Y= Y1 & Z=Z1.
The value of Z= Z1 is set using a Procedure when Sales Document Type = OR ( This is the Document type For sales Order). So, this means variant matching will finally happen at Sales Order creation level, coz all the three reqd. charc. are availabe at that time.This is also our reqmt.
But, now what is happening, a Sales Contract is created for Material A, with Charc values X = X1 & Y= Y1. When a sales order is created with reference to this Contract, immediately during Copying of selected item, Variant Matching gets triggered & Material A is replaced by Material Variant B. Even we dont get into the Configuration Window.
Actually, during copying itself Object Depencies are called and thats leading to variant Matching.
Our requirement is that, it should not get triggered at such early stage. It should happen when Config. window is clicked.
Kindly help. Copy Control of Sales Doc has setting 'No Control' We are in ECC 6.0. Are there some other settigs too.
regards,
Stuti

your functional team can help you in finding one.

Creation of Sales order with reference to SOW contracts(VA01 )

I had created sales order using BAPI_SALESORDER_CREATEFROMDAT2 and now i want to attach the document link for each line item.I could not do it in my program or recording.How can i enter these document type?pls help......

Dear Machoy,
In IMG under
Sales and Distribution -> Sales -> Sales Documents -> Maintain Copy Control for Sales Documents -> Copying Control: Sales Document to Sales Document
or Transaction VTAA
http://help.sap.com/erp2005_ehp_02/helpdata/en/70/a7853478616434e10000009b38f83b/frameset.htm
If you create a sales document with reference to a preceding document, the system copies nearly all the data from the preceding document. The data in the preceding document originally comes from the customer and material master records. Because the data is copied from the preceding documents into the sales document, any changes that have been made to the master data records since the preceding document was created are not included in the sales document. If, when you create with reference, you add another item to the document that was not in the preceding document, the system determines the data for it from the master records, such as the material master or info record.
You have created an inquiry and a quotation with reference to this inquiry. Before you created the quotation, you changed some data in the material and customer master records.
You have changed the material description in the material master record. This description is stored in the sales document at item level.
You have changed the terms of payment in the customer master record from ZB01 to ZB03. These are stored in the sales document at header level.
When you created the inquiry, the system copies the original material description to the item. If you enter another item in the quotation for the same material, the system displays the new material description for the new item.
However, the system continues to propose the original term of payment, that is, ZB01, for all items including the new one. This is because it is copied from the header of the preceding document into the header of the quotation, and the change in the customer master record has no affect on the quotation.
Regards,
Naveen.

Automatic creation of Sales Order with reference to Purchase Order

Hi
I want to create the sales order automatically when we are creating the purchase order.
kindly guide me how to do it,
Pramod

Hi
U can create BDC for Tcode VA01 in T code SHDB with the validation and ask the ABAPer to create one Y/Z Tcode. Then you input the PO no in the Tcode to create the SO in background.
Or
Create BDC for PO AND SO and give logic and validation with input field and ask the ABAPer to crate one Y/Z Tcode to create PO and SO in single execute.
Thx.

Creation of sales order with Variant configuration info

Hi friends,
   I am creating sales order along with Variant configuration data. We have 3 level BOM structure.
I am using BAPI_SALESORDER_CREATEFROMDAT2 and filling in ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF ORDER_CFGS_VALUE, ORDER_CFGS_REFINST
tables exactly the same way BAPISDORDER_GETDETAILEDLIST FM returns.
Sales order is being created with no variant configuration information.(Not in the header level atleast)
Can any one help me on this.
Thanks
Seshagiri

Updating Variant Configuration data for SO item became little tricky for us in an ongoing implementation. After spending some hours investigating the correct combination of data to pass, we were able to post the document correctly. As no detailed documentation is available online for this scenario, I hope this post will help community for similar requirements. J
For updating Variant configuration (VC) data for Sales order item, we need to populate below tables of standard FM or BAPI (e.g. SD_SALESDOCUMENT_CREATE).
Normally the standard FM or BAPI does not return any error messages in case configuration data is not updated successfully.
·         SALES_SCHEDULES_IN: The required date field should be populated with appropriate value (REQ_DATE).
·         SALES_ITEMS_IN: Field PO_ITM_NO should be populated with appropriate value.
·         SALES_CFGS_REF Table:
1.       This table should have 1 record per item.
2.       Combination of CONFIG_ID and ROOT_ID should be unique across line items.
POSEX
000010
CONFIG_ID
000001
ROOT_ID
00000001
SCE
1
COMPLETE
T
CONSISTENT
T
CBASE_ID_TYPE
G
·         SALES_CFGS_INST:
1.       This table should have 1 record per item.
2.       Combination of CONFIG_ID and INST_ID should be unique across line items.
CONFIG_ID
000001
INST_ID
00000001
OBJ_TYPE
MARA
CLASS_TYPE
300
OBJ_KEY
MATNR value
QUANTITY
Quantity value
QUANTITY_UNIT
Quantity Unit
COMPLETE
T
CONSISTENT
T
OBJECT_GUID
MATNR value
PERSIST_ID_TYPE
G
·         SALES_CFGS_VALUE:
1.       Combination of CONFIG_ID and INST_ID should be unique across line items.
2.       We can have multiple characteristics for a material. In that case appropriate records should be inserted in this table. Note that CONFIG_ID and INST_ID should be same for all the rows you insert in this table for multiple characteristics for a material.
3.       The characteristic value should be in SAP internal format.
CONFIG_ID
000001
INST_ID
00000001
CHARC
Material characteristics
VALUE
Material characteristics value
·         SALES_CFGS_VK:
1.       Combination of CONFIG_ID and INST_ID should be unique across line items.
2.       We can have multiple characteristics for a material. In that case appropriate records should be inserted in this table. Note that CONFIG_ID and INST_ID should be same for all the rows you insert in this table for multiple characteristics for a material.
CONFIG_ID
000001
INST_ID
00000001
VKEY
Material characteristics

Prevent Outbound delivery creation in sales orders with delivery block

Hi gurus
We are facing the following issue:
Some sales orders have delivery block header and once they are saved an outbound delivery document is created; we want SAP system creates outbound deliveries only in those cases were sales orders have not a delivery block in header, is there any option or configuration we can use in order to prevent the creation of these documents?
Regards,
Edgar.

Well Edgar,
let's see then in spro
Logistics Execution->Shipping->Deliveries->Define Reasons for Blocking in Shipping
Check out the configuration of your delivery block reason and pay special attention to this instruction:
"In sales documents, you can either enter delivery blocks manually at header level (business data in the sales document header) or they can be proposed automatically by the system. In the latter case, the delivery block must be entered in the respective sales document type (see chapter
"Define sales document types"). In addition, the delivery block in the sales document header is only effective if the delivery block has been assigned to the respective delivery type."
It must be something in the configuration of the delivery block reason you're using.
Regards,
Edgar

Problem in creation of sales order using BAPI

Hi Guru's,
 I am currently working on Minimum Order Value problem. If the ordered item is less than 5$, the requirement is to add a new material MOV to the existing order by filling the difference amount and making it to 5 pounds. I am using the bapi BAPI_SALESORDER_CHANGE to amend the existing order with the MOV material. The material is getting created successfully and the order is getting amended. When i tried to process the order for billing It shows incompletion log exist. On checking the incompletion log it shows "missing configuration". But when i go to the configuration of the material it shows green sign. The most important thing is the material MOV has 2 configuration profile, I believe there is a confusion in selecting the configuration profile for creation of MOV . I came to know about that problem because when i go to change mode (VA02) and try to check the configuration, It askes me to choose the configuration profile and when i choose the configuration profile incompletion log is cleared. When i save the order and send it to billing the billing happens successfully. Could any one help me on this issue.......
Parameters passed to BAPI for configuration.
 st_order_cfgs_ref-posex = '900010'. "PM14/06/07
st_order_cfgs_ref-config_id = '000010'. "PM14/06/07
st_order_cfgs_ref-root_id = '10000010'. "PM14/06/07
append st_order_cfgs_ref to t_order_cfgs_ref. "PM14/06/07
st_order_cfgs_inst-config_id = '000010'. "PM14/06/07
st_order_cfgs_inst-inst_id = '10000010'. "PM14/06/07
append st_order_cfgs_inst to t_order_cfgs_inst. "PM14/06/07
st_order_cfgs_refinst-posex = '900010'. "PM14/06/07
st_order_cfgs_refinst-config_id = '000010'. "PM14/06/07
st_order_cfgs_refinst-inst_id = '10000010'. "PM14/06/07
append st_order_cfgs_refinst to t_order_cfgs_refinst. "PM14/06/07
Thanks in advance...
Shiv

Hi,
Did u have a look at the standard programs which make use of BAPI_SALESORDER_CREATEFROMDAT1
Heres a list...
LWSSOU08
MV45WF0S
MWWMJF21_BAPI_SALESORDER_CREAT
RBUS2032
Regards,
Tanveer.
Please mark helpful answers

Dynamic Credit check - problem -Delivery creation from Sales order

Hi
we have a problem which i would appreciate some help with.
Sales order is blocked for credit and subsequently released via VKM1
BUT as soon as line item is selected and then Sales document > deliver -
the Dynamic credit block kicks in again straight away, no other changes have been made
why is this occurring ?
I managed to get round the problem by creating delivery via VL10c and selecting line item and then create in background

Hi Tony,
Do you have a credit check active again at Delivery level?
In OVA8 - for the combination of credit control area, risk cat & credit group - please check field 'Number of days'.
If you do not wish to carry out the credit check again for the released doc, here you can maintain the number of days.
Description of F1 for this field is as below.
Credit check: Number of days without check
Specifies the number of days after which a changed document must be re-checked for credit.
Use
This function is used for checking documents that have already been released by a credit representative, but that have subsequently been changed. The system does NOT carry out another credit check if the following conditions are met:
The value of the changed order is not greater than the value already approved for credit (inclusive of the deviation factor), AND
The current date is not greater than the original release date plus the number of days specified here
thanks
Anirudh

Problem with creation of Sales Order with reference to Contract

Similar Messages

Maybe you are looking for