Problem while creating Service order

Hi Gurus,
I have a problem While creating Service order (me21n) through - Work order it contains service requisitions.
So that means they carry information such as G/L and work order number while entering the requistion no in PO Creation Screen (me21n) which automatically should be picked from the work order refference.
But problem here is the service items and all other are assigned to PO except the Account Assingnment tab which is GL Account and Work Order No and Cost center..
Can anyone explain me this?
Is this something that one can explain?
Regards,
Murugesh R
Rewards for value replies.

Hi Murgesh,
If GL code is not getting bydefault from the system it is needed to be provided by the user.
If normally one GL is there or other than master data services if single GL is there u can set that in SPRO.
it is avalible in deafult settings in order node
If you are creating the order with refrence to PR then it will take account assignement as "F" system will pick up all the details from PM module. This is the integration of MM & PM module.
But if your PO is not w.r.t. PM orders PR then needs to be given manully.
Ramesh
Edited by: RameshChandra Soni on Jul 25, 2008 8:16 AM

Similar Messages

Problem while Creating Service order through Work Order

Hi Gurus,
I have a problem While creating Service order (me21n) through - Work order it contains service requisitions.
So that means they carry information such as G/L and work order number while entering the requistion no in PO Creation Screen (me21n) which automatically should be picked from the work order refference.
But problem here is the service items and all other are assigned to PO except the Account Assingnment tab which is GL Account and Work Order No and Cost center..
Can anyone explain me this?
Is this something that one can explain?
Regards,
Murugesh R
Rewards for value replies.

Closed..

ABAP dump Error while creating service order in PCUI.

Hi Experts,
                 We are getting following ABAP dump error while creating service order in PCUI which is working fine in GUI.
Runtime Errors         RAISE_EXCEPTION
Date and Time          02.01.2008 14:55:38
Short text
Exception condition "TYPE_NOT_FOUND" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
A RAISE statement in the program "CL_CRM_ELEMDESCR==============CP" raised the
exception
condition "TYPE_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
|    function module from the display of active calls.
We have added custom fields in the service application. these custom fields with Z-structure & data elements are included in BSP structure CRMT_BSP_SRV_OIC_SRCHRES in development system.But the same Z structure & custom fields are exist in the production system but not included in BSP Structue CRMT_BSP_SRV_OIC_SRCHRES.
This may be the reason resulting this ABAP dump error in PCUI while creating Service order.
How these Z structures can be included in the BSP Structure CRMT_BSP_SRV_OIC_SRCHRES in production system?
Helpful answers would be rewrded max points as it is high priority issue.
Regards,
Basavaraj Patil

Hi Thirumala,
Thnaks for the reply.
            I have enhanced service application using transaction EEWB to add new custom fields. these fields are there in Z structure created by the system in production system. All the transports are moved to target system. Problem is that Z structure( contains custom fields) created while doing EEWB is not included in BSP structure.
I f transports are missed to move to target system, Is there any other alternative to solve this problem?
Regards,
Basavaraj Patil

Problem while creating sales order

Hi
   We are facing a problem while creating a sales order in R/3. The sales order number is getting generated. But we are not able to view the same in the backend meaning it is not there in the database. Any inputs would be of help.
regs
Steve

Hi everybody,
I've got a problem with this too. I use the BAPI_SALESORDER_CREATEFROMDAT2 with BAPI_TRANSACTION_COMMIT and the webdynpro shows me the document number created in R3 with a Success message. But when I go to R3 and try to display the created sales order, it doesn't exists. So... Maybe I'm doing something wrong with the BAPI_TRANSACTION_COMMIT. ¿Can anybody help me with this?
The code I use is this:
When the user pushes the SAVE button in the WebDynpro, this code executes:
    //@@begin onActionSave(ServerEvent)
     wdThis.wdGetSOCreaCustController().executeBapi_Salesorder_Createfromdat2();
     wdThis.wdGetSOCreaCustController().executeBapi_Transaction_Commit();
    //@@end
In the custom Controller I've got the code for those executions:
public void executeBapi_Salesorder_Createfromdat2( )
    //@@begin executeBapi_Salesorder_Createfromdat2()
     try {
          wdContext.currentBapi_Salesorder_Createfromdat2Element().modelObject().execute();
     catch (Exception ex) {
          wdComponentAPI.getMessageManager().reportException(ex.getMessage(), false);
     wdContext.nodeOutput().invalidate();
    //@@end
public void executeBapi_Transaction_Commit( )
     try {
          wdContext.currentBapi_Transaction_CommitElement().modelObject().execute();
     catch (Exception ex) {
          wdComponentAPI.getMessageManager().reportException(ex.getMessage(), false);
     wdContext.nodeOutput().invalidate();
    //@@end
¿Is something wrong? ¿Is something missing?

Problem while creating service po

HI GURU'S
i am facing problem that while creating service po , in delivery schedule tab system allows only one possible date , but my service quantity is 10 and i need to add 10 different date for 10 quantities , as service will deliver at 10 different days , so how should i maintain different delivery schedule dates
regards

Hi Akshay,
The date in the schedule delivery wont affect much,
you can create the Service PO with single line item, 10 Quantity and can make 10 different SES as per the requirement.
if furthet you want to make sure that the SES should be created within the given period of time then you can use the blanket PO also.
Hope it helps you.
Regards,
Yawar Khan

Error message BP does not exist while creating service order in WEB UI

Hi Experts,
i have an issue while creating a service order in WEB UI the system is automatically taking the BP ""created By"" but while saving the document Error message showing "BP does not exist"
we have already completed set up integration with HR .created the user as BP Role "employee"
Kindly suggest what are the other configuration that need to be checked.
Regards,
D Panda

Hi,
Have you made the assignment of the user (defaulting in created by) to the employee (under the identification tab in employee)?
Regards,
Parul

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.

Error while creating service order in web ic 5.0

Hi All,
we are facing problem with service order in web ic 5.0.whenever we click on service order in navigation area it is throwing an error message as given below.
Note
The following error text was processed in the system RQ4 : No business transaction type was found
The error occurred on the application server pssapcmq_RQ4_01 and in the work process 0 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Module: %_HTTP_START of program SAPMHTTP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system RQ4 in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server pssapcmq_RQ4_01 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server pssapcmq_RQ4_01 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 370 -u: BEJAW1M -l: E -s: RQ4 -i: pssapcmq_RQ4_01 -w: 0 -d: 20080111 -t: 133612 -v: ERROR_MESSAGE_STATE -e: No business transaction type was found
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
Please help me
Regards
Madhav

Hello Madhav,
You have to maintain your 'business transaction profile' (SPRO->CRM->IC Web->Business Transaction->Define bus. trans. prof.) in the customizing and assign that profile to your IC WebClient profile (the one you assigned in the org. model)
In the business transaction profile you must make sure that at least one transaction type (e.g. ZSRV) is assigned as 'Dependent business transaction' and that entry is flagged as 'Service'.
Also make sure that that transaction type (ZSRV) has leading business transaction category 'Service process' (BUS2000116).
This should solve your problem!
Kind regards,
Joost

Problem while creating service PO using bapi_po_create1

hi all,
i am getting error :
In case of account assignment, please enter acc. assignment data for item
what does this mean?
please help,,
thanks,
Siddhartha Prakash

Hi Sid.
I'm having this same problems on creating PO Service. Did you solve it? How did you do that?
I'm using a PR and the Category is 'Y', and I cant find where is the problem.
The tables that I'm passing to the BAPI_PO_CREATE1 are:
POITEM/ POITEMX
POACCOUNT/ POACCOUNTX
POSERVICES
POSRVACCESSVALUES
Please, if you have any idea, let me know!
Tks a lot!
Renata

Problem while creating Sale Order with Reference

Hi Friends,
While creating a Sale Order with Reference, I am unable to copy few fields from Profit Segement(CO - PA Data) in Account assignment Tab.
Any solution how to copy all field values which are in Reference Sale Order Number.
Regards,
sg.

Hi,
Go to VOFM you will find out data transfer routine.
Over here go for the order data transfer routine and select your data transfer routine which you use.
Now check you field name and table name for that particular field which was not copying.
It will be better if you ask your abaper for this.
You have to make changes over here only for data transfer routine.
Hope so this will help you out.
Regards
Raj.

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

Trigger IRODER Idoc from IW31 while creating service order

Hi,
Iam trying to trigger an IDoc for service Order from IW31 transaction. I found the Idoc IORDER is for service order and one way of doing it is from IORD transaction.(Please correct me IORDER is not the correct Idoc !!) However, we dont have status profiles maintained for our order type, so Iam not able to use this method. Could anyone tell me if there is any other way to trigger the same?
Thanks & Regards,
Swarna Munukoti

Hello Sandeep,
Sales Representative is a partner funtion. You need to enter this partner function with a BP in the parties involved assignment block.
As for the pop up, it is controlded bu the partner determination procedure. Based on the partner determniation procedure used, if there are more than one sales representative found, there would be the pop for selection.
Hope the above information helps.
Best regards,
Maggie

Pricing problem while creating sales order doc

Hi friends,
My requirement is to create sales order with ref to contract i am using 'BAPI_SALESORDER_CREATEFROMDAT2' , and I am extracting data from konv table to get price through condition record , but i am getting 4 messages
(S) SALES_HEADER_IN has been processed successfully
(E) Condition PR00 is not allowed as header condition
(W) The sales document is not yet complete: Edit data
(E) Sales document was not changed
and i am not getting pricing for created sales order document.
please help.
regards,
Sravani.

solved

Problem while creating SALES ORDER (OR)

Hi All,
I am unable to create sales order (OR)
Error : Material is not defined for sales areaI have created MMR and CMR Properly.
Please help.
Thanks In Advance
Regards
Abhi

Hi Abhi,
I face similar issue as faced by you.
I went to additional data and changed the description and added the description in which I wanted it to be added but does not help. Am I missing the right place where to make the change?
I am pretty sure that it is a language issue.
I created a sales order, added a product, it worked fine.
Now, I copied this product to a new product, changed description and added it in same sales order it does not work.
Best Regards,
Neha

Settlement rule while creating service order

Hi Gurus,
1. can someone help me in knowing what should be passed as receivers key while updating settlement rule if i am using Sales Order for settlement ; sales order, sales order item, object number of item or something else because i tried to pass all of these but not working.
2. I pass receiver category as SDI.
Kindly help asap.
Thanks,
Ritu

Hi Gurus,
1. can someone help me in knowing what should be passed as receivers key while updating settlement rule if i am using Sales Order for settlement ; sales order, sales order item, object number of item or something else because i tried to pass all of these but not working.
2. I pass receiver category as SDI.
Kindly help asap.
Thanks,
Ritu

Problem while creating Service order

Similar Messages

Maybe you are looking for