Problem related to Sales Header Tab of Sales Order

Hello All,
The problem is related to Sales Order processing through T-Code VA01 where we want the sales order to be raised in the back date and when we change the Requested Delivery Date the message shown is " Change in invoice date : Billing Date is Redetermined " after that the Billing Date in the Billing Document Flap of Sales Order Header also gets changed automatically to the date given as Requested Delivery Date.Why does this happen ? What are the configurations required for this?
Apart from this in case of any Sales Contract Processing through T-Code VA41 the Requested Delivery Date option is not Reflected on the screen which leads to the appearance of the server date (present date ) in the Billing Date section of the Sales header even if the Contract is raised in the back date. Please suggest the configuration required to get the requested delivery date option reflected on the screen.
Looking forward to some valuable suggestions
Thanks & Regards
Priyanka Mitra

Hello,
With reference to your reply I want to mention that I am not creating any contract with reference to any previous document , I want to create a fresh independent contract in back date where i have already maintained all taxes and pricing. I want the billing date to be reflected also in back date along with the pricing date & requested delivery date.I have also checked in the UTXJ condition type where there it is already maintained that the pricing date is based on billing date but this is ultimately not reflecting in the screen.
Please suggest.
Regards
Priyanka Mitra

Similar Messages

Problem in importing Sales Order with udf in the rows

Dear All,
I am having problem in importing Sales Order with udf in the rows. I mean it is getting imported but the udf values in the rows is not getting updated. But the udf values in the header is getting updated. I am using SAP 8.8 Pl 10.
Can anyone guide me what to do in this scenario?
Regards,
Gary

So , Login to DTW .
with the Desired Database and Login Credentials.
Goto - > Templates - > Customized Templates
Select The Object .
Right Click on the object needed and choose Create Template for the Structure .
Then use this template for import .
Hope it helps
Thanks
Ashish Ranjan

Relation between Sales order and Production order

Hi,
In Make to stock scenario how the relation between Sales order and production order are related.In which table we will get the related fields (expect AUFK,VBAK,AUFO).
warm regards,
Surendar reddy.

The relation between sales order and prodution order is as follows.
Pass AUFNR to AFKO/AFPO Get AUFPL.
Pass AUFPL to AFVC Get BANFN.
Pass BANFn to EBAN Get EBELN.
Hope this works .
Cheers,
Lakshmi Prasanna Gandham

Using bsid and bsad I needed get partner name related to sales order

Hi
Using bsid and bsad I needed get partner name related to sales order
I have gone through the tables but its vbeln column is blank
How can I make relation between bsid and bsad with vbak if vbeln and column is blank in the table bsid and bsad.
Please guide me.
Regards
Sebastian
Edited by: Sebastian John on Apr 21, 2009 3:35 PM

BSID-VBELN = VBRK-VBELN.
Billing document number is there in BSID table.
Regs.

Problem in creating sales order in Make TO Order

Hi all,
We are trying to test the strategy 50 (Make to Order strategy) . To begin with we are trying to create the Sales order. However , we are getting the message "NO availibity check can be carried out for Material " we have assigned the checking group and checking rule .
What can be the possible causes for this problem . Please help me . I will be very grateful . Thanking you.
Kind Regards
Ayaz

Dear ,
Planning startegy 50 , Requirement Type of Customer KEV , in -OVZG -can you please chek the following : Select the Requirement Class for Planning Startgey 50 based on the Requirement Type : KEV
1.Did you mark the Indicator Requirement Transfer in Requiremet Tab
2.Did you mark the Availablity Check marked ?
Goto SPRO-Define Planning Statgey and Comapre the same because it will be copied from OVZG
Hope it is clear
Regards
JH

Problem in creating sales order with BAPI_SALESDOCU_CREATEFROMDATA1.

Hi everybody
I am not able create a sales order with BAPI_SALESDOCU_CREATEFROMDATA1.i also did debugging.its not throwing up any errors in return table. return table is empty. but when i check the BAPI in se37 with same data its creating the sales order.
Here i am attaching my program.please kindly can anyone have a look and tell me whether i did anything wrong in the program.
thx in advance.
*& Report YORDERCREATE
REPORT YORDERCREATE.
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: it_schedules_inx like bapischdlx occurs 0 with header line.
data: it_schedules_in like bapischdl occurs 0 with header line.
types: begin of itab,
auart like vbak-auart,
vkorg like vbak-vkorg,
vtweg like vbak-vtweg,
spart like vbak-spart,
kunnr like kuagv-kunnr,
kunnr1 like kuwev-kunnr,
posnr like vbup-posnr,
matnr like mara-matnr,
Tquan type string,
end of itab.
data: it-out type table of itab with header line.
data: menge(10) type c.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    FILENAME                      = 'C:\VA01.TXT'
FILETYPE                      = 'ASC'
   HAS_FIELD_SEPARATOR           = 'X'
TABLES
    DATA_TAB                      = it-out.
loop at it-out.
header-doc_type = it-out-auart.
headerx-doc_type = 'X'.
header-sales_org = it-out-vkorg.
headerx-sales_org = 'X'.
header-distr_chan = it-out-vtweg.
headerx-distr_chan = 'X'.
header-division = it-out-spart.
headerx-division = 'x'.
headerx-updateflag = 'I'.
*partner data
partner-partn_role = 'SP'.
partner-partn_numb = it-out-kunnr.
append partner.
partner-partn_role = 'SH'.
partner-partn_numb = it-out-kunnr1.
append partner.
*item data
itemx-updateflag = 'I'.
item-itm_number = it-out-posnr.
itemx-itm_number = 'X'.
item-material = it-out-matnr.
itemx-material = 'X'.
item-target_qty = it-out-tquan..
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
*loop at it-out.
*write:/ it-out-auart,it-out-vkorg.
*endloop.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
EXPORTING
   SALESDOCUMENT                 = v_vbeln
    SALES_HEADER_IN               = header
    SALES_HEADER_INX              = headerx
SENDER                        = SENDER
BINARY_RELATIONSHIPTYPE       = 'VORL'
INT_NUMBER_ASSIGNMENT         = ' '
IMPORTING
   SALESDOCUMENT_EX              = v_vbeln
TABLES
   RETURN                        = return
   SALES_ITEMS_IN                = item
   SALES_ITEMS_INX               = itemx
   SALES_PARTNERS                = partner.
SALES_SCHEDULES_IN            = SALES_SCHEDULES_IN
SALES_SCHEDULES_INX           = SALES_SCHEDULES_INX
SALES_CONDITIONS_IN           = SALES_CONDITIONS_IN
SALES_CFGS_REF                = SALES_CFGS_REF
SALES_CFGS_INST               = SALES_CFGS_INST
SALES_CFGS_PART_OF            = SALES_CFGS_PART_OF
SALES_CFGS_VALUE              = SALES_CFGS_VALUE
SALES_CFGS_BLOB               = SALES_CFGS_BLOB
SALES_CCARD                   = SALES_CCARD
KEY_TABLE                     = KEY_TABLE
endloop.
loop at return where type = 'E' or type = 'A'.
exit.
endloop.
if sy-subrc = 0.
write:/ 'error in creating document'.
else.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
   WAIT          = 'X'
IMPORTING
RETURN        = RETURN
commit work and wait.
write:/ 'document',v_vbeln,'created'.
endif.

Hi Patrick,
Here are a couple of issues/recommendations:
1) Checkboxes must be populated by capital X (your headerx-division = 'x' is wrong)
2) Why you are using the COMMIT WORK AND WAIT statement? The CALL BAPI_TRANSACTION_COMMIT does exactly the same! Comment it out or better delete one of them!
3) Does one of your sales order tables (VBAK, VBAP, ....) have any customer appended fields? In this case you have to populate an additional value table and the related index table as well.
Check it out,
Heinz

Problem in Uploading sales order text data using LSMW

Hi All,
I am facing Problem in uploading open sales order data from legacy to SAP using LSMW.
We are trying to upload sales order data using LSMW Standard Batch/Direct input using program name RVINVB10 and program type D. We are not able to upload item text but have no problem in uploading remaining data.
the details we are passing to BTEXHKOM structure are......
BTEXHKOM-OLDNR = IHEADER-OLDORD_NO.
BTEXHKOM-LAISO = 'EN'.
BTEXHKOM-TDID = 'Z009'.
and the for structure BTEXLKOM
BTEXLKOM-OLDNR = IHEADER-OLDORD_NO.
BTEXLKOM-TXPARGRAPH = '/'.
CONCATENATE LITEM-DEPTID LITEM-DEPTNAME
INTO BTEXLKOM-TXLINE SEPARATED BY ' '.
we have three input source structures.
IHEADER Header structure
LITEM Line item structure ( Material data )
IPARTN Partners structure
The structure relationships are
BTEXHKOM <<< IHEADER.
BTEXLKOM <<< IHEADER.
Please let me know if I am doing some thing wrong or some thing else need to be done.
Thanks,
Chindam.

you can pass below values also
OLDNR : order number and item nuber
TXPARGRAPH : VBBK
TXLINE : your text.....

Problem while creating sales order using BAPI

Hi all,
i am creating a sales order from the purchase order data.
when my client will send a PO in EDI format, my 3rd party edi tool will convert that edi formatted PO to text format. then i will upload that text formatted PO to my program then i will create a SO from those uploaded PO data using BAPI BAPI_SALESORDER_CREATEFROMDAT2.
but,no sales order is being created.& also i am not getting any return message.by debugging also, i am not getting the error.plz suggest where i am doing mistake.below is the coding.
DATA:
gfilename LIKE rlgrap-filename.
*--Internal tables
DATA: BEGIN OF i_item OCCURS 50.    "Create Material Document Item
        INCLUDE STRUCTURE BAPISDITM .
DATA: END OF i_item .
DATA: BEGIN OF i_partner OCCURS 20. "Return parameter
        INCLUDE STRUCTURE BAPIPARNR.
DATA: END OF i_partner.
DATA: BEGIN OF i_schedule OCCURS 20. "Return parameter
        INCLUDE STRUCTURE BAPISCHDL .
DATA: END OF i_schedule.
DATA: BEGIN OF i_cond OCCURS 20. "Return parameter
        INCLUDE STRUCTURE BAPICOND .
DATA: END OF i_cond.
DATA: BEGIN OF i_part OCCURS 0,     " Internal table for split data
        part(20),
      END OF i_part.
DATA: BEGIN OF i_return OCCURS 20. "Return parameter
        INCLUDE STRUCTURE bapiret2.
DATA: END OF i_return.
*-- Work areas
DATA: BEGIN OF wa_header .       "sales Document Header Data
        INCLUDE STRUCTURE BAPISDHD1.
DATA: END OF wa_header .
*DATA: BEGIN OF wa_return .       "Output Structure
       INCLUDE STRUCTURE BAPIRET2.
*DATA: END OF wa_return .
DATA: begin of sorder.
     INCLUDE STRUCTURE BAPIVBELN.
DATA: end of sorder.
data:begin of t_upload,
     ebeln(10), "PO no(seagate)
     aedat like sy-datum , "PO date
     bsart(4) , "PO type
     vdatu like sy-datum , "requested delivery date
     kunnr(10) , "customer no-sold-to-party
    kunak like vbak-kunnr, "bill-to-party
     name1_s(20), "name1 of sold-to-party
     name2_s(15), "name2 of sold-to-party
     land1_s(3), "country
     ort01_s(10), "city
     regio_s(3), "region(state/province)
     pstlz_s(10), "postal code
     adrnr_s(10), "address
     bstkd_e(10), "end customer purchase order
     posex(6),     "end customer PO line no(item no)
     kdmat(18),     "end customer material no(part no)
     kunag(10),     "ship-to-party
     name1_c(20),   "name1 of ship-to-party
     name2_c(15),   "name2 of ship-to-party
     land1_c(3),   "country
     ort01_c(10),    "city
     regio_c(3),   "region(state/province)
     pstlz_c(10),   "postal code
     adrnr_c(10),   "address
     posnr(6), "item no(seagate PO line no)
     pstyv(4), "item category
     matnr(18), "material no(seagate 9 digit part no)
     zmeng(13), "Target quantity in sales unit
    vrkme like vbap-vrkme, "sales unit
     meins(3), "UOM
    posnr_tot like vbap-posnr,"Total no. of line items
     werks(4), "plant
    vstel like vbap-vstel, "shipping point
     empst(10), "receiving point
     shtyp(4), "shipment type
     route(6), "route
     vsbed(2), "shipping conds
    rkfkf like vbap-rkfkf, "method of billing for co/ppc orders
     zterm(4), "terms of payment key
     inco1(3), "F.O.B inco term1
     inco2(3), "F.O.B inco term2
     end of t_upload.
Data: wa_upload like t_upload,
       i_upload like standard table of t_upload.
Data:v_kunnr like kna1-kunnr,
      v_posnr like vbap-posnr,
      v_matnr like vbap-matnr,
      v_zmeng like vbap-zmeng,
      v_kunag like kna1-kunnr.
*---Constants
CONSTANTS: c_comma TYPE c VALUE ',',   " For splitting data at commas
           c_01(2) TYPE c VALUE '01', " For movement code in Bapi
           c_b     TYPE c VALUE 'B',   " For mvt. Indicator in Bapi
           c_creat(5) TYPE c VALUE 'CREAT', " For button text
           c_clear(5) TYPE c VALUE 'CLEAR', " For clear button
           c_mvmt(4) TYPE c VALUE 'MVMT',
           c_ok(2)   TYPE c VALUE 'OK',
           c_error(5) TYPE c VALUE 'Error'.
*--SELECTION SCREEN DESIGN--
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME.
PARAMETERS:
            p_auart LIKE vbak-auart, " order type
            p_vkorg LIKE vbak-vkorg, " sales org
            p_vtweg LIKE vbak-vtweg, " dist channel
            p_spart LIKE vbak-spart, " division
            p_vkgrp LIKE vbak-vkgrp, " sales group
            p_vkbur LIKE vbak-vkbur, "sales office
            p_file(256) default 'c:/saleorder.txt'.         "File name
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN PUSHBUTTON 15(10) v_create USER-COMMAND creat.
SELECTION-SCREEN PUSHBUTTON 40(10) v_clear USER-COMMAND clear.
INITIALIZATION -
INITIALIZATION.
v_create = c_creat .
v_clear = c_clear.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
PERFORM selectfile USING p_file.
*--AT SELECTION_SCREEN--
AT SELECTION-SCREEN .
IF sy-ucomm = c_clear.
    PERFORM f_clear.
ELSE.
   IF sy-ucomm <> c_mvmt.
**--- Validating the input data.
     PERFORM f_check_inputs.
    ELSEif sy-ucomm = c_creat.
*--- Validating the input data.
      PERFORM f_check_inputs.
*-- Uploading the PO data.
      PERFORM f_PO_upload.
*---checking the PO data
     PERFORM f_check_upload_data.
*---create sales order from PO data
    PERFORM f_Sales_order_create.
    ENDIF.
FORM f_PO_upload.
gfilename = p_file.
CALL FUNCTION 'WS_UPLOAD'
       EXPORTING
            filename                = gfilename
            filetype                = 'DAT'
       TABLES
            data_tab                = i_upload
       EXCEPTIONS
            conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_type            = 4
            no_batch                = 5
            unknown_error           = 6
            invalid_table_width     = 7
            gui_refuse_filetransfer = 8
            customer_error          = 9
            OTHERS                  = 10.
IF sy-subrc <> 0.
    MESSAGE i398(00) WITH '(WS_UPLOAD)'
    ' Errors occured with exception '
     sy-subrc.
ENDIF.
ENDFORM.                    " f_PO_upload
*&      Form selectfile
      text
     -->P_P_FILE text
FORM selectfile CHANGING value(filename) TYPE c.
CALL FUNCTION 'WS_FILENAME_GET'
       EXPORTING
            def_filename     = gfilename
            def_path         = 'C:\'
            mask             = ',*.txt.'
            mode             = 'O'
            title            = 'Select File Name'
       IMPORTING
            filename         = filename
       EXCEPTIONS
            inv_winsys       = 1
            no_batch         = 2
            selection_cancel = 3
            selection_error = 4
            OTHERS           = 5.
ENDFORM.                    " selectfile
FORM f_Sales_order_create.
PERFORM f_fill_header.
PERFORM f_fill_partner.
PERFORM f_fill_item.
PERFORM f_call_BAPI.
ENDFORM.                    " f_Sales_order_create
*&      Form f_fill_header
      text
--> p1        text
<-- p2        text
FORM f_fill_header.
move p_auart to wa_header-doc_type.
move p_vkorg to wa_header-sales_org.
move p_vtweg to wa_header-distr_chan.
move p_spart to wa_header-division.
move p_vkgrp to wa_header-sales_grp.
move p_vkbur to wa_header-sales_off.
Read table i_upload into wa_upload index 1.
move wa_upload-ebeln to wa_header-purch_no_c.
move wa_upload-aedat to wa_header-purch_date.
move wa_upload-bsart to wa_header-po_method.
move wa_upload-vdatu to wa_header-req_date_h.
move wa_upload-bstkd_e to wa_header-purch_no_s.
*move wa_upload-route to wa_header-route.
move wa_upload-vsbed to wa_header-ship_cond.
move wa_upload-empst to wa_header-rec_point.
move wa_upload-shtyp to wa_header-ship_type.
move wa_upload-zterm to wa_header-pmnttrms.
move wa_upload-inco1 to wa_header-incoterms1.
move wa_upload-inco2 to wa_header-incoterms2.
ENDFORM.                    " f_fill_header
*&      Form f_fill_partner
      text
--> p1        text
<-- p2        text
FORM f_fill_partner.
if not wa_upload-kunnr is initial.
select single kunnr from kna1 into v_kunnr
            where kunnr = wa_upload-kunnr.
if sy-subrc <> 0.
Message E014 with 'customer does not exist'.
else.
move 'AG' to i_partner-partn_role.
move wa_upload-kunnr to i_partner-partn_numb.
move wa_upload-land1_s to i_partner-country.
move wa_upload-name1_s to i_partner-name.
move wa_upload-name2_s to i_partner-name_2.
move wa_upload-ort01_s to i_partner-city.
move wa_upload-regio_s to i_partner-region.
move wa_upload-pstlz_s to i_partner-postl_code.
move wa_upload-adrnr_s to i_partner-address.
append i_partner.
endif.
endif.
if not wa_upload-kunag is initial.
select single kunnr from kna1 into v_kunag
            where kunnr = wa_upload-kunag.
if sy-subrc <> 0.
Message E015 with 'end customer does not exist'.
else.
move 'WE' to i_partner-partn_role.
move wa_upload-kunag to i_partner-partn_numb.
move wa_upload-land1_c to i_partner-country.
move wa_upload-name1_c to i_partner-name.
move wa_upload-name2_c to i_partner-name_2.
move wa_upload-ort01_c to i_partner-city.
move wa_upload-regio_c to i_partner-region.
move wa_upload-pstlz_c to i_partner-postl_code.
move wa_upload-adrnr_c to i_partner-address.
append i_partner.
endif.
endif.
ENDFORM.                    " f_fill_partner
*&      Form f_fill_item
      text
--> p1        text
<-- p2        text
FORM f_fill_item.
loop at i_upload into wa_upload.
if not wa_upload-matnr is initial.
select single maramatnr msegmenge into (v_matnr, v_zmeng) from
                   mara inner join mseg on maramatnr = msegmatnr
                   where mara~matnr = wa_upload-matnr.
if sy-subrc <> 0.
Message E016 with 'material no does not exist'.
elseif v_zmeng LT wa_upload-zmeng.
Message E017 with 'order quantity is greater than the quantity present'.
endif.
endif.
move wa_upload-posnr to i_item-itm_number.
move wa_upload-pstyv to i_item-item_categ.
move wa_upload-matnr to i_item-material.
move wa_upload-zmeng to i_item-target_qty.
move wa_upload-meins to i_item-target_qu.
move wa_upload-werks to i_item-plant.
*move wa_upload-meins to wa_vbap-meins.
*move wa_upload-posnr_tot to wa_vbap-posnr_tot.
move wa_upload-posex to i_item-po_itm_no.
move wa_upload-kdmat to i_item-cust_mat22.
move wa_upload-inco1 to i_item-incoterms1.
move wa_upload-inco2 to i_item-incoterms2.
move wa_upload-zterm to i_item-pmnttrms.
move wa_upload-empst to i_item-rec_point.
move wa_upload-shtyp to i_item-ship_type.
move wa_upload-route to i_item-route.
append i_item.
PERFORM f_fill_schedule_line.
PERFORM f_fill_conditions.
ENDLOOP.
ENDFORM.                    " f_fill_item
*&      Form f_fill_schedule_line
      text
--> p1        text
<-- p2        text
FORM f_fill_schedule_line.
move wa_upload-matnr to i_schedule-itm_number.
move sy-datum to i_schedule-req_date.
move wa_upload-zmeng to i_schedule-req_qty.
append i_schedule.
ENDFORM.                    " f_fill_schedule_line
*&      Form f_fill_conditions
      text
--> p1        text
<-- p2        text
FORM f_fill_conditions.
move wa_upload-matnr to i_cond-itm_number.
move sy-datum to i_cond-conpricdat.
append i_cond.
ENDFORM.                    " f_fill_conditions
*&      Form f_clear
      text
--> p1        text
<-- p2        text
FORM f_clear.
clear:p_auart,
      p_vkorg,
      p_vtweg,
      p_spart,
      p_vkgrp,
      p_vkbur.
ENDFORM.                    " f_clear
*&      Form f_call_BAPI
      text
--> p1        text
<-- p2        text
FORM f_call_BAPI.
clear:i_item,i_partner,i_schedule.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
SALESDOCUMENTIN               =
    ORDER_HEADER_IN               = wa_header
ORDER_HEADER_INX              =
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
IMPORTING
   SALESDOCUMENT                  = sorder
TABLES
RETURN                        =
   ORDER_ITEMS_IN                 = i_item
ORDER_ITEMS_INX               =
    ORDER_PARTNERS                = i_partner
   ORDER_SCHEDULES_IN             = i_schedule
ORDER_SCHEDULES_INX           =
ORDER_CONDITIONS_IN            = i_cond.
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              =
if not ( sorder-vbeln is initial ).
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
write: /'Order number:', sorder.
else.
loop at i_return.
write: / i_return-id, i_return-number, i_return-message(80).
endloop.
*write: /'Error'.
endif.
*loop at i_return.
*write: / i_return-id, i_return-number, i_return-message(80).
*endloop.
ENDFORM.                    " f_call_BAPI

HI
Pricing will be carried basing on the pricing
procedure.
Case1: Prices will be carried out automatically if
necessary condition records are maintained for the
condition type.
For this you can go to Sales Order-> Item Conditions
In the screen you can click on command button Analysis,
which gives you the list of condition types associated
to the pricing procedure. By clicking on the condition
type you can know the action that has taken place.
Case2: Manually forcing prices for Items.
To do this, you have to populate ORDER_CONDITIONS_IN &
ORDER_CONDITIONS_INX. Also note to identify the item
numbers, you manually pass the item number for each item
in the sales order, use the same item number for
populating conditions.
Parameters required:
ORDER_CONDITIONS_IN:
ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
ORDER_CONDITIONS_INX:
ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
   Hope the above info helps you. Do revert back if you
need more info.
Kind Regards
Eswar

Facing the problem while creating sales order

Hi,
I am facing the problem while saving the sales order.
Error in system xxx/400 while copying the document
Message no. CRM_ORDER_MISC 020
Diagnosis
Errors occurred while transferring the document into another system. To view the error messages, see the enclosed log.
Transmission log
u2022Product cannot be recoded for ERP System xxx/400(Notification E CRM_ORDER_MISC 015)
u2022Product cannot be recoded for ERP System xxx/400 (Notification E CRM_ORDER_MISC 015)
Kindly assist me.
Madhu

Hi Madhusadan,
Can you check whether the product exists in the ERP System or not? You can take the product names and can check the same using the Tcode: MM03 in ECC System. Also, it would be good if you have a look at the product from the CRM System if there are any errors or the product is already archived.
Is the Sales Order you are creating from a Preceding Transaction ?
Hope this helps.
Thanks,
Samantak.

Order type Personalization Problem in Standard Sales Order Form

Hi All,
We have a problem in personalization of Sales order form.Here we are trying to personalize three field based on order type
Scenario 1:_
_Nav-->Oredr Management Super User-->Orders,returns-->Sales Orders-->order type-->standard_
In this type if we are navigating to lines it should ask the following fields as mandatory
(Nav-->Oredr Management Super User-->Orders,returns-->Sales Orders-->others form)
1.Shipping Method
2.Freight Terms
3.Shipment priority
Scenario 2:_
_Nav-->Oredr Management Super User-->Orders,returns-->Sales Orders-->order type-->Bill only & Internal & RMA_
then it should navigate to line items without asking those three mandatory fields.
For that we did the following Personalization through Help-->Diagnostics-->Custom Code-->Personalize
Level--> Form level
Enabled-->Yes
Condition_
Trigger Event: When-Validate-Record
Trigger Object: Order
Condition : +(:ORDER.ORDER_TYPE not like '%INTERNAL') and (:ORDER.ORDER_TYPE not like '%BILL%') and (:ORDER.ORDER_TYPE not like '%RMA')+
Processing mode : both
level:site
Actions_
seq:10
type:property
description:Make field mandatory
language:all
enabled:yes
object type:item
target object :ORDER.SHIPPING_METHOD
property name:REQUIRED
value:TRUE
Problem+_
The problem we are facing is when we first select the ordar type as Bill only or Internal or RMA it is working as expected. But first if we are select the order type as standard then we navigiting to lines it is not allowing us without entering those three mandatory fields as expected. Hence the problem is without closing the form we changed the order type as Bill only now also those fields remains as mandatory this is issue .
So hope the problem is clear to you all and we have to move this in production on tomorrow.
If somone helps to resolve this ASAP we would thankful to you.
Thanks in advance
Regards,
CSK

Hi Sandeep,
Thanks for your quick response.
you might not have getting the our problem sorry. let me explain you clearly
If the ordre type is standard the following fields should be mandatory without those fields it should not navigate to line items_
1.Shipping Method
2.Freight Terms
3.Shipment priority
If the ordar type as Bill only or Internal or RMA_
1.Shipping Method
2.Freight Terms
3.Shipment priority
non mandatory should navigate to line items
for that we did three personalization for those three fields as in the previous post
but the problem is
when we first select the ordar type as Bill only or Internal or RMA it is working as expected the fiel sare non mandatory the without closing the form if we select order type as standard then if i try to navigate lines it is not allowing me without entering the three fields. But incase first we are select the order type as standard then we navigiting to lines it is not allowing us without entering those three mandatory fields as expected. Hence the problem is without closing the form now we changed the order type as Bill only or internal or RMA now also those fields remains as mandatory this is issue .
hope now the problem is clear to you .
Thanks in advance
Regards,
CSK

Problem in cs61 sales order bom

Dear sir
i created sale order for item 100 x matrial and item 200 y material ,sales order no 1234.for this sales
order i want to create sales order bom by cs61 . when i create this the system should allows item 100 for x matrial and item 200 for y material for same sales order . but if i give material y for item 100 and material x for .200also the system allowing to create the sales order bom.this will effict the bom .
so system should not allow to create the sales order bom when i give wrong material to item .
pl give me correct solution for above problem
regrds
Baswa

Baswa,
when you create sales order BOM through CS61 its all together new BOM specialy meant for that sales order - material combination.
To create it you can take referance of Material BOM , but there is no such functionality to restrict the componet changes or quantity changes.
The CS61 its self is meant for creating customer specific BOM , which can be all together different from Material BOM. as in many business its required that , we need to modify our existing BOM on customer request to incorporate that customer specific changes. For all other things standard BOM is there in system and its not affected by this new customer specific BOM.
If you need further help , discribe your need of creation of sales order BOM.
Hope it helps you.
Regards
Ritesh

Problem in creating sales order using the FM BAPI_SALESORDER_CREATEFROMDAT

Hi Experts,
I have writen the below codes to create a sales order but it is showing the error message that ' sales order type OR is not defined'. Please help me.
data:itab_header like bapisdhead occurs 0 with header line,
     itab_item   like bapiitemin occurs 0 with header line,
     itab_partner like BAPIPARTNR occurs 0 with header line,
     itab_return like bapireturn1,
     soldtoparty like bapisoldto occurs 0 with header line,
     shiptoparty like bapishipto occurs 0 with header line,
     salesdoc like BAPIVBELN-VBELN .
itab_header-doc_type = 'OR'.
itab_header-sales_org = '1000'.
itab_header-distr_chan = '10'.
itab_header-division = '00'.
append itab_header.
itab_item-material = 'M-01'.
itab_item-req_qty = '1'.
append itab_item.
itab_partner-partn_role = 'AG'.
itab_partner-partn_numb = '1000'.
append itab_partner.
clear itab_partner.
itab_partner-partn_role = 'WE'.
itab_partner-partn_numb = '1000'.
append itab_partner.
clear itab_partner.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
EXPORTING
    ORDER_HEADER_IN           = itab_header
WITHOUT_COMMIT            = ' '
CONVERT_PARVW_AUART       = ' '
IMPORTING
   SALESDOCUMENT              = salesdoc
   SOLD_TO_PARTY              = soldtoparty
   SHIP_TO_PARTY              = shiptoparty
BILLING_PARTY             =
   RETURN                     = itab_return
TABLES
    ORDER_ITEMS_IN            = itab_item
    ORDER_PARTNERS            = itab_partner.
ORDER_ITEMS_OUT           =
ORDER_CFGS_REF            =
ORDER_CFGS_INST           =
ORDER_CFGS_PART_OF        =
ORDER_CFGS_VALUE          =
ORDER_CCARD               =
ORDER_CFGS_BLOB           =
ORDER_SCHEDULE_EX         =.
if itab_return-type ne 'E'.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      WAIT = 'X'.
IMPORTING
   RETURN        =
write: salesdoc.
else.
write: itab_return-message.
endif.

Hello Dillip
The BAPIs BAPI_SALESORDER_CREATE... have certain limitations. In case of BAPI_SALESORDER_CREATEFROMDAT1 you can only create orders for business object 'BUS2032'.
If you have the RFC-enabled function module <b>SD_SALESORDER_CREATE</b> available in your system (which I doubt) then you should use this fm instead of the BAPIs.
Regards
Uwe

Problem in lock Sales order create with BAPI BAPI_SALESORDER_CREATEFROMDAT2

Hi All,
i have the z program to create the sales order with reff quotation in SD With BAPI BAPI_SALESORDER_CREATEFROMDAT2.
this program will excute every 30 mins .
Problem: Some times if i excute the program in background it is taking morethan 30mins so second batch excution also gets starting to create the sales order for same quotation then it is creating 2 sales orders at atime with 1 quotation.
here i am getting duplicate sales orders so i want to lock the creation of duplicate sales order.

Some solutions
- Just lock (ENQUEUE) any object at the start of the job(*), if not locked, you can exit or wait in a loop, will be released at end of job (use a _SCOPE '3' so commit work wont release the lock)
-> This will insure the job runs only once at a time
- Lock the quotation before calling the BAPI, will be released by the COMMIT_WORK (from where do you fetch the quotation, if it is a customer Z_table, you can use the lock object that you have surely created ?) (use a _scope '2')
-> This will insure that at most one job will convert a quotation (i suppose you set a "done" flag or status in the quotation record)
Read [SAP Locks |http://help.sap.com/abapdocu_70/en/ABENSAP_LOCK.htm] if you are not familiar with the concept of lock in SAP.
Regards,
Raymond
(*) E_TABLEE for table, E_TRDIR for program, anything not required by another process

Problem creating a sales order for configurable material in SAP ECC

I have a Variant Configurable material named X.
The structure of this VC material is
Material X has charatcertics CHARCTERISTIC1 and CHARCTERISTIC2.
CHARCTERISTIC1 has values VALUE1
CHARCTERISTIC2 has values VALUE2
I created a sales order manually from VA01 using configurable material and read the values of all configuration tables to be filled from BAPISDORDER_GETDETAILEDLIST. With the help of this data i got an idea how to fill the tables of BAPI BAPI_SALESORDER_CREATEFROMDAT2. But still i am able to create a sales order but the configuration data that i give is not getting populated in the sales order.
Where am i missing. please some body suggest. I am unable to debug and searched the forums
for this information but dint find solution for my problem. some body please tell me where am i missing?
Any help would be highly appreciated
Edited by: jessica sam on Jan 12, 2009 2:59 PM

Even after maintaining the item category MTAC(Mills Make to order config at mat level), the configurable material is not getting replaced in the sales order (va02). It is just showing material variant exists for the configurable material.
The setting in item category for configuration is.
Config. Strategy 01(Sales Order Strategy (TAC, TAM))
Mat. Variant Action 4 (Replace configurable material (Append and change))
ATP material variant 2 (Do not substitute if not completely available)
Structure scope D (Configuration, poss. with BOM explosion)
I have maintained the stock for material variant as well to take care of ATP material varinat setting shown above.
Please suggest if missing something.

A problem about create sales order with reference to contract.

Hello,everyone,
when I create sales order va01,there is user exit in MV45AFZB to check the vbkd-bstkd,unique and fixed length.
but there is no such in contract creation va41.
when I create a contract and copy the data to sales order ,the check code is prevent me from copying
message error:the vbkd-bstkd check is wrong.
how to solve the problem, if I have to use the check in sales order.

The Simple thing may be put a check at contract stage it self, then whatever data is in contract will copy in sales order. So you wont face this problem.
Thanks,
Raja

Problem related to Sales Header Tab of Sales Order

Similar Messages

Maybe you are looking for