Repair order with reference to service nitification.

Hello,
I want to create repair order with reference to service notification S1. but when I click create repair order in action box nothing happens. could any one of you help me in sloving this. where is the link missing in customizing. can you help.
thanks in advance

Hi
Check out the config in Action box
Plant Maintenance and Customer Service - Master Data in Plant Maintenance and Customer Service - Maintenance and Service Processing - Maintenance and Service Notifications - Notification Processing - Additional Functions - Define Action Box
execute it
Select and execute
Define Follow-Up Functions (Generated Tasks/Activities)
Select your notification type, and go for activities, maintain the fields notification type (S1), Fk (0031), scenario, sort no and description.
- Pithan

Similar Messages

Sales order with reference to Service Notification

Hi Freinds,
I have to create a sales order with reference to Service notification (IW51). can someone sugggest me BAPI or Function module to perform this task.
Appriciate your help.
Best regards
Pravin

no std bapi's as far as i know..when you hit create create repair order(in iw51) system calls QM06_RMA_ORDER_CREATE
..whick internally calls SD_ORDER_CREATE..may be this should give some pointers..
Regards
Siva

Create sales order with reference to service order

Hi
I need to create sales order based on the service order . Is there any BAPI function module available for this ?
Please help...
Regards
Sujith

**　プログラムＩＤ　　　　　　 ： ZBAPI_SALESORDER_CREATE *
**　プログラム名称　　 　　 ： Upload Sales Order Creation *
**　処理概要　　　　　　　 　： *
**　作成者　　　　　　　　　　 ： Karthik.P *
**　作成日　　　　　　　　　　 ： 2006/08/10 *
REPORT ZBAPI_SALESORDER_CREATE LINE-SIZE 132 MESSAGE-ID ZMMBAPI .
 Internal table definition *
****<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>>>
DATA: GT_ORDER_HEADER_IN LIKE BAPISDHD1,
*******<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
 GT_ORDER_HEADER_INX LIKE BAPISDHD1X,
*****<<<<<Return Parameter>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
 GT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE, " Return Messages
*********<<<Communication Fields: Sales and Distribution Document Item<>>>>>
 GT_ORDER_ITEMS_IN LIKE BAPISDITM OCCURS 0 WITH HEADER LINE, " Item Data
*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
 GT_ORDER_ITEMS_INX LIKE BAPISDITMX OCCURS 0 WITH HEADER LINE, "Item Data Checkbox
*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
 GT_SALESDOCUMENT LIKE BAPIVBELN-VBELN , "Number of Generated Document
*********<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
 GT_ORDER_PARTNERS LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE, "Document Partner
********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
 GT_ORDER_SCHEDULES_IN LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE, "Schedule Line Data
****<<<<<<<<Checkbox List for Maintaining Sales Document Schedule Line>>>>>>>>
 GT_ORDER_SCHEDULES_INX LIKE BAPISCHDLX OCCURS 0 WITH HEADER LINE, " Checkbox Schedule Line Data
*******Communication Fields for Maintaining Conditions in the Order
 GT_ORDER_CONDITIONS_IN LIKE BAPICOND OCCURS 0 WITH HEADER LINE,
******Communication Fields for Maintaining Conditions in the Order
 GT_ORDER_CONDITIONS_INX LIKE BAPICONDX OCCURS 0 WITH HEADER LINE.
 Data definition *
DATA: BEGIN OF GT_FT_SALES OCCURS 0,
 DOC_TYPE(4) , "Sales Document Type
 SALES_ORG(4) , "Sales Organization
 DISTR_CHAN(2) , "Distribution Channel
 DIVISION(2) , "DIVISION(2)
 SALES_DIST(6) , "Sales district
 INCOTERMS1(3) , "Incoterms (part 1)
 INCOTERMS2(28) , "Incoterms (part 2)
 PMNTTRMS(4) , "Terms of payment key
 PRICE_DATE(8) , "Date for pricing and exchange rate
 PURCH_NO_C(35) , "Customer purchase order number
 PURCH_NO_S(35) , "Ship-to Party's Purchase Order Number
 EXCHG_RATE(8) , "Directly quoted exchange rate for pricing and statistics
 CURRENCY(5) , "SD document currency
 MATERIAL(18), "MATERIAL
 TARGET_QTY(13) , "Target quantity in sales units
 ITEM_CATEG(4) , "Sales document item category
 MATL_GROUP(8) , "Material Group
 PURCH_NO_C1(35), "Customer purchase order number
 SALES_DIST1(6) , "Sales district
 INCOTERMS11(3) , "Incoterms (part 1)
 INCOTERMS21(28), "Incoterms (part 2)
 PMNTTRMS1(4) , "Terms of payment key
 EXCHG_RATE1(8) , "Directly quoted exchange rate for pricing and statistics
 PRICE_DATE1(8) , "Date for pricing and exchange rate
 TRG_QTY_NO(5) , "Factor for converting sales units to base units (target qty)
 DIVISION1(2) , "DIVISION1
 SALQTYNUM(5) , "Numerator (factor) for conversion of sales quantity into SKU
 GROSS_WGHT(3) , "Gross Weight of the Item
 NET_WEIGHT(15) , "Net Weight of the Item
 UNTOF_WGHT(3) ,"Weight Unit
 PARTN_ROLE(2) ,"Partner function
 PARTN_NUMB(10) ,"Customer Number 1
********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
 ITM_NUMBER(6) ,"Item number of the SD document
 REQ_QTY(8) , "Schedule line date
 DLV_DATE(8) , "Schedule line date
 MS_DATE(8) , "Material availability date
 LOAD_DATE(8) , "Loading time (local time with reference to a shipping point)
 GI_DATE(8), "Time of goods issue (local DATE, with reference to a plant)
 TP_DATE(8) , "Transportation planning -time (local w/ref. to shipping pnt)
 ITM_NUMBER2(6) , "Condition item number
END OF GT_FT_SALES,
 MSG(240) TYPE C, " Return Message
 E_REC(8) TYPE C, " Error Records Counter
 REC_NO(8) TYPE C, " Records Number Indicator
 S_REC(8) TYPE C, " Successful Records Counter
 T_REC(8) TYPE C. " Total Records Counter
selection block for EXCEL UPLOAD FILE>>>>>>>>>>>>>>>>>>>>>>>>
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
PARAMETERS FILE TYPE IBIPPARMS-PATH OBLIGATORY.
SELECTION-SCREEN END OF BLOCK B1.
*<<<<AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .>>>>>>>>>>>>
AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
 IMPORTING
 FILE_NAME = FILE.
**<<<<<<<<<<<<<<<<<START-OF-SELECTION.>>>>>>>>>>>>>>>>>>>>>>>>>>>
START-OF-SELECTION.
CALL FUNCTION 'WS_UPLOAD' "#EC *
 EXPORTING
 FILENAME = FILE
 FILETYPE = 'DAT'
 TABLES
 DATA_TAB = GT_FT_SALES
 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
 NO_AUTHORITY = 10
 OTHERS = 11.
IF SY-SUBRC <> 0 .
 MESSAGE E000.
ENDIF.
SKIP 3.
FORMAT COLOR COL_HEADING INVERSE ON.
 WRITE 40 TEXT-001.
FORMAT COLOR COL_HEADING INVERSE OFF.
SKIP 1.
FORMAT COLOR COL_NEGATIVE INVERSE ON.
 WRITE :/ TEXT-002, 13 SY-MANDT , 104 TEXT-003, 111 SY-UNAME,
 / TEXT-004, 13 SY-DATUM , 104 TEXT-005, 111 SY-UZEIT.
FORMAT COLOR COL_NEGATIVE INVERSE OFF.
SKIP 3.
LOOP AT GT_FT_SALES.
 PERFORM SLALE_UPLOAD_DATA.
ENDLOOP.
T_REC = E_REC + S_REC.
SKIP 3.
FORMAT COLOR COL_TOTAL INVERSE ON.
 WRITE: /38 TEXT-007, T_REC.
FORMAT COLOR COL_TOTAL INVERSE OFF.
FORMAT COLOR COL_NEGATIVE INVERSE ON.
 WRITE: /38 TEXT-008, E_REC.
FORMAT COLOR COL_NEGATIVE INVERSE OFF.
FORMAT COLOR COL_TOTAL INVERSE ON.
 WRITE: /38 TEXT-009, S_REC.
FORMAT COLOR COL_TOTAL INVERSE OFF.
*& Form SLALE_UPLOAD_DATA
 text
--> p1 text
<-- p2 text
FORM SLALE_UPLOAD_DATA .
*******<<<<<<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>
 GT_ORDER_HEADER_IN-DOC_TYPE = 'TA'.
 GT_ORDER_HEADER_IN-SALES_ORG = GT_FT_SALES-SALES_ORG . "'0001'
 GT_ORDER_HEADER_IN-DISTR_CHAN = GT_FT_SALES-DISTR_CHAN. "'01'
 GT_ORDER_HEADER_IN-DIVISION = GT_FT_SALES-DIVISION. " '01'
 GT_ORDER_HEADER_IN-SALES_DIST = GT_FT_SALES-SALES_DIST ."'000001'
 GT_ORDER_HEADER_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1. "'CFR'
 GT_ORDER_HEADER_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
 GT_ORDER_HEADER_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS . "'0001'
 GT_ORDER_HEADER_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE ."'20060818'
 GT_ORDER_HEADER_IN-PURCH_NO_C = '32'.
 GT_ORDER_HEADER_IN-PURCH_NO_S = '32'.
 GT_ORDER_HEADER_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE ."'1.00000'
 GT_ORDER_HEADER_IN-CURRENCY = GT_FT_SALES-CURRENCY . " 'EUR'
********<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
 GT_ORDER_HEADER_INX-DOC_TYPE = 'X'.
 GT_ORDER_HEADER_INX-SALES_ORG = 'X'.
 GT_ORDER_HEADER_INX-DISTR_CHAN = 'X'.
 GT_ORDER_HEADER_INX-DIVISION = 'X'.
 GT_ORDER_HEADER_INX-SALES_DIST = 'X'.
 GT_ORDER_HEADER_INX-INCOTERMS1 = 'X'.
 GT_ORDER_HEADER_INX-INCOTERMS2 = 'X'.
 GT_ORDER_HEADER_INX-PMNTTRMS = 'X'.
 GT_ORDER_HEADER_INX-PRICE_DATE = 'X'.
 GT_ORDER_HEADER_INX-PURCH_NO_C = 'X'.
 GT_ORDER_HEADER_INX-PURCH_NO_S = 'X'.
 GT_ORDER_HEADER_INX-EXCHG_RATE = 'X'.
 GT_ORDER_HEADER_INX-CURRENCY = 'X'.
*****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
 GT_ORDER_ITEMS_IN-ITM_NUMBER = '000010'.
 GT_ORDER_ITEMS_IN-MATERIAL = GT_FT_SALES-MATERIAL .
 GT_ORDER_ITEMS_IN-PO_ITM_NO = '32'.
 GT_ORDER_ITEMS_IN-CUST_MAT22 = 'AGNI-IV'.
 GT_ORDER_ITEMS_IN-BILL_DATE = '20060808'.
 GT_ORDER_ITEMS_IN-PLANT = '0001'.
*GT_ORDER_ITEMS_IN-STORE_LOC = '0001'.
 GT_ORDER_ITEMS_IN-TARGET_QTY = GT_FT_SALES-TARGET_QTY . "'1000'
 GT_ORDER_ITEMS_IN-ITEM_CATEG = GT_FT_SALES-ITEM_CATEG . "'TAN'
 GT_ORDER_ITEMS_IN-MATL_GROUP = GT_FT_SALES-MATL_GROUP . "'01'
 GT_ORDER_ITEMS_IN-PURCH_NO_C = GT_FT_SALES-PURCH_NO_C . "'32'
 GT_ORDER_ITEMS_IN-SALES_DIST = GT_FT_SALES-SALES_DIST . "'000001'
 GT_ORDER_ITEMS_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1 . "'CFR'
 GT_ORDER_ITEMS_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
 GT_ORDER_ITEMS_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS . "'0001'.
 GT_ORDER_ITEMS_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE . "'1.00000'
 GT_ORDER_ITEMS_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE . "'20060808'
*GT_ORDER_ITEMS_IN-SALES_UNIT = 'DZ'.
 GT_ORDER_ITEMS_IN-TRG_QTY_NO = GT_FT_SALES-TRG_QTY_NO . "'23'
 GT_ORDER_ITEMS_IN-DIVISION = GT_FT_SALES-DIVISION . "'01'
 GT_ORDER_ITEMS_IN-SALQTYNUM = GT_FT_SALES-SALQTYNUM . "'32'
 GT_ORDER_ITEMS_IN-GROSS_WGHT = GT_FT_SALES-GROSS_WGHT. " ' 25272000'
 GT_ORDER_ITEMS_IN-NET_WEIGHT = GT_FT_SALES-NET_WEIGHT. "'24464000'
 GT_ORDER_ITEMS_IN-UNTOF_WGHT = GT_FT_SALES-UNTOF_WGHT . " 'KG'
*GT_ORDER_ITEMS_IN-CURRENCY = 'EUR'.
 APPEND GT_ORDER_ITEMS_IN.
****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
 GT_ORDER_ITEMS_INX-ITM_NUMBER = '000010'.
 GT_ORDER_ITEMS_INX-MATERIAL = 'X'.
*GT_ORDER_ITEMS_INX-PO_ITM_NO = 'X'.
 GT_ORDER_ITEMS_INX-CUST_MAT22 = 'X'.
 GT_ORDER_ITEMS_INX-BILL_DATE = 'X'.
 GT_ORDER_ITEMS_INX-PLANT = 'X'.
*GT_ORDER_ITEMS_INX-STORE_LOC = 'X'.
 GT_ORDER_ITEMS_INX-TARGET_QTY = 'X'.
 GT_ORDER_ITEMS_INX-ITEM_CATEG = 'X'.
 GT_ORDER_ITEMS_INX-MATL_GROUP = 'X'.
 GT_ORDER_ITEMS_INX-PURCH_NO_C = 'X'.
 GT_ORDER_ITEMS_INX-SALES_DIST = 'X'.
 GT_ORDER_ITEMS_INX-INCOTERMS1 = 'X'.
 GT_ORDER_ITEMS_INX-INCOTERMS2 = 'X'.
 GT_ORDER_ITEMS_INX-PMNTTRMS = 'X'.
 GT_ORDER_ITEMS_INX-EXCHG_RATE = 'X'.
 GT_ORDER_ITEMS_INX-PRICE_DATE = 'X'.
*GT_ORDER_ITEMS_INX-SALES_UNIT = 'X'.
 GT_ORDER_ITEMS_INX-TRG_QTY_NO = 'X'.
 GT_ORDER_ITEMS_INX-DIVISION = 'X'.
 GT_ORDER_ITEMS_INX-SALQTYNUM = 'X'.
 GT_ORDER_ITEMS_INX-GROSS_WGHT = 'X'.
 GT_ORDER_ITEMS_INX-NET_WEIGHT = 'X'.
 GT_ORDER_ITEMS_INX-UNTOF_WGHT = 'X'.
*GT_ORDER_ITEMS_IN-CURRENCY = 'x'.
 APPEND GT_ORDER_ITEMS_INX.
*****<<<<<<Communications Fields: SD Document Partner: WWW
 GT_ORDER_PARTNERS-PARTN_ROLE = 'WE'.
 GT_ORDER_PARTNERS-PARTN_NUMB = '0000000057'.
***GT_ORDER_PARTNERS-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER . " '000010'.
 APPEND GT_ORDER_PARTNERS.
*********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
 GT_ORDER_SCHEDULES_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER." '000010'
 GT_ORDER_SCHEDULES_IN-REQ_QTY = GT_FT_SALES-REQ_QTY . "'234'
 GT_ORDER_SCHEDULES_IN-DLV_DATE = GT_FT_SALES-DLV_DATE ." '20060824'.
 GT_ORDER_SCHEDULES_IN-MS_DATE = GT_FT_SALES-MS_DATE . "'20060808'
 GT_ORDER_SCHEDULES_IN-LOAD_DATE = GT_FT_SALES-LOAD_DATE. " '20060822'
 GT_ORDER_SCHEDULES_IN-GI_DATE = GT_FT_SALES-GI_DATE . " '20060823'
 GT_ORDER_SCHEDULES_IN-TP_DATE = GT_FT_SALES-TP_DATE . "'20060821'
 APPEND gt_ORDER_SCHEDULES_IN.
*********<<<<Communications Fields: SD Document Partner: WWW FLAG>>>>>>>>>>>>>>>>>>
 GT_ORDER_SCHEDULES_INX-ITM_NUMBER = '000010'.
 GT_ORDER_SCHEDULES_INX-REQ_QTY = 'X'.
 GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
 GT_ORDER_SCHEDULES_INX-MS_DATE = 'X'.
 GT_ORDER_SCHEDULES_INX-LOAD_DATE = 'X'.
 GT_ORDER_SCHEDULES_INX-GI_DATE = 'X'.
 GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
 APPEND gt_ORDER_SCHEDULES_INX.
********Communication Fields for Maintaining Conditions in the Order
 GT_ORDER_CONDITIONS_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER ." '000010'
 APPEND GT_ORDER_CONDITIONS_IN.
***Communication Fields for Maintaining Conditions in the Order
 GT_ORDER_CONDITIONS_INX-ITM_NUMBER = '000010'.
 APPEND GT_ORDER_CONDITIONS_INX.
 CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
 EXPORTING
 SALESDOCUMENTIN =
 ORDER_HEADER_IN = GT_ORDER_HEADER_IN
 ORDER_HEADER_INX = GT_ORDER_HEADER_INX
SENDER =
BINARY_RELATIONSHIPTYPE =
INT_NUMBER_ASSIGNMENT =
BEHAVE_WHEN_ERROR =
LOGIC_SWITCH =
TESTRUN =
CONVERT = ' '
 IMPORTING
 SALESDOCUMENT = GT_SALESDOCUMENT
 TABLES
 RETURN = GT_RETURN
 ORDER_ITEMS_IN = GT_ORDER_ITEMS_IN
 ORDER_ITEMS_INX = GT_ORDER_ITEMS_INX
 ORDER_PARTNERS = GT_ORDER_PARTNERS
 ORDER_SCHEDULES_IN = GT_ORDER_SCHEDULES_IN
 ORDER_SCHEDULES_INX = GT_ORDER_SCHEDULES_INX
 ORDER_CONDITIONS_IN = GT_ORDER_CONDITIONS_IN
 ORDER_CONDITIONS_INX = GT_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 =
 IF GT_RETURN-TYPE EQ 'E' .
 E_REC = E_REC + 1.
 READ TABLE GT_RETURN WITH KEY ID = 'V1'.
 FORMAT COLOR COL_NEGATIVE INVERSE ON.
 REC_NO = E_REC + S_REC.
 CONCATENATE TEXT-006 REC_NO ':'
 GT_RETURN-MESSAGE INTO MSG SEPARATED BY SPACE .
 CONDENSE MSG.
 WRITE: / MSG.
 FORMAT COLOR COL_NEGATIVE INVERSE OFF.
ELSEIF GT_RETURN-TYPE EQ 'S'.
 S_REC = S_REC + 1.
 FORMAT COLOR COL_POSITIVE INVERSE ON.
 MSG = GT_RETURN-MESSAGE.
 CONDENSE MSG.
 WRITE: / MSG .
 FORMAT COLOR COL_POSITIVE INVERSE OFF.
 PERFORM COMMIT_MM.
ENDIF.
 CLEAR: GT_RETURN[], MSG.
ENDFORM. " SLALE_UPLOAD_DATA
*& Form COMMIT_MM
 text
--> p1 text
<-- p2 text
FORM COMMIT_MM .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 WAIT = 'X'
 IMPORTING
 RETURN = GT_RETURN.
clear: GT_ORDER_ITEMS_IN[],GT_ORDER_CONDITIONS_IN[].
ENDFORM. " COMMIT_MM

Function module for Create service order with reference to sales doc (RAS )

Hi All,
I have to create a service order (type SM03) with reference to sales document (doc type RAS, in other way it is called as repair order).
I have used function module 'ALM_ME_ORDER_CREATE' && 'CO_ZV_ORDER_POST' to create service order and its working fine but problem is that i am not able to create linking between repair order and service order.
Can anyone suggest me function module, BAPI to create service order with reference as sales document (RAS) so that all related details of sales document will automatically reflect to service order..
Sumit

Try this function module BAPI_ORDER_MAINTAIN. Just search with BAPI_ORDER* in SE37 you will get some more functions.
Regards
Kathirvel

Credit memo with reference to a sales order with reference to a contract?

Hello All
Now I created a quantity contract and the customer paid the Amount that means the billing is done then I started creating sales orders with reference to the contract, can I create credit memos with reference to these sales orders?
Regards
Jacopo Francois

Hi,
You can create a contract for a longer duartion say 1 year, andyou can create sales order in reference to your contract. This would be an ideal scenario in case of service materials.
You can now surely create credit memo's in reference to this sales order.
You will invoice the sales order first and create a credit memo request in reference to your sales invoice and then invoice the credit memo request to raise your credit memo for the customer.
Reward if helpful.
Regards
Ravi

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.

Sales order with reference to sales order

Hi,
 I need to create a sales order with reference another sales order using bapi CreateFromDat2. Please note, Sales Ord. Dist. channel, Div, sold-to to of the new order are different from original order. I gave reference order in field order_header_in-REFDOCTYPE . I am getting following error when I perform single test " FB Call: insufficient parameters. Can any of you tell me how to overcome this issue. And is it possible to create an order refering to another Saler order with different Sales Ord, Dist. channel, Division, sold-to ?
<REMOVED BY MODERATOR>
Cheers
Sudhaker
Message was edited by:
 Alvaro Tejada Galindo

There is an OSS note <a href="https://service.sap.com/sap/support/notes/370988">Note 370988 - BAPIs in SD: Creation with reference</a>
Symptom
This note describes the problems of the 'Create with reference' function when using BAPIs to create sales documents.
If you are working online, you can use this function module to create a sales document with reference to an existing sales document or a billing document (for example, a debit or credit memo request) according to fixed rules. The rules for transferring information from the source document to the target document are defined in the copying control on header and item level. The creation with reference permits an item selection.
When you use BAPIs in SD, a function of this type is not fully available. A reference is only possible for a quantity contract, so that the target quantity of the contract can be reduced by the order quantity of the sales document. Furthermore, the document flow is also updated.
As an alternative to 'Create with reference' in Transaction VA01, two variants are provided for solving the 'Create with reference' problem in the BAPI.
 1. Create a '1:1 ' - that is, a document copy of a sales document (customer quotation, order) with 'BAPI_SALESDOCUMENT_COPY'. At this point, you cannot create the 1:1 copy of either a billing document or a delivery.
 2. Create a sales document that refers to an existing document with 'BAPISDORDER_GETDETAILEDLIST' and 'BAPI_SALESORDER_CREATEFROMDAT2'.
Other terms
BAPI_SALESDOCUMENT_COPY, BAPI_SALESORDER_CHANGE, BAPI_CUSTOMERINQUIRY_CHANGE, BAPI_CUSTOMERQUOTATION_CHANGE, BAPI_SALESORDER_CREATEFROMDAT1, BAPI_SALESORDER_CREATEFROMDAT2, BAPI_SALESORDER_CREATEFROMDATA, BAPISDORDER_GETDETAILEDLIST
Reason and Prerequisites
As of yet, no method exists for creating a sales document that refers to an existing document.
Solution
For solution No. 1
 1. Create the documents using the BAPI_SALESDOCUMENT_COPY function module. However, this only permits a 1:1 copy without factoring out individual items.
 2. After you have created the document copy, you can use a change BAPI to edit this copy.
For solution No. 2
 1. Collect the data for the reference document (for example a customer quotation) with the 'BAPISDORDER_GETDETAILEDLIST' function module. In the example code, focus exclusively on the partners, items, schedule lines and conditions.
 2. Prepare the Data. Execute the 'copying control' manually. This way, you decide which values are to be transferred.
 3. Create the sales document using the 'BAPI_SALESORDER_CREATEFROMDAT2' function module by transferring the prepared data.
 4. Finally, you must remove a COMMIT WORK so that the sales document can be written into the database.
An example of solution 2 is attached as a text file. You are allowed to select items and quantities for example, if you use input parameters. If there are no entries, then transfer 1:1 from the reference document. When you enter the 'condition type' parameter, you can determine whether conditions are copied or recalculated ('G' for transferring from the preceding document; 'B' or ' ' for re-determining, and 'C' for re-determining with transfer of the manual elements).
Sample : <a href="https://websmp108.sap-ag.de/~sapidb/012003146900000486112004E/BAPI_COPY_WITH_REF.txt">ZZ_MS_BAPI_COPY</a>
Regards

Creation of Release order with reference to Contract

Dear experts,
We are doing upgradation from 4.6B to ECC6. During testing ,while creating release order with reference to contract,(Contract was created with Account assignment category-K and item category-D),cost center is copied from contract in purchase order in account assignment tab of item details,
but when i save it window is poping up(account assignment service line item 10-small window) asking to enter cost center again. Even if i enter the same cost center in that window,cost center field,again it is asking same window is poping up for entering cost center.
Can any body please tell me inspite of cost center is copied,why this window is coming ,please suggest.This problem is not there in 4.6B version
Advance thanks,
Regards,
Dayanand

Please check to OXK1, and compare it to both system.Or check the config guide in IMGMM-Purchasingacc.assigment--Set subscreen for acc assingment (coding) block.

Framework order with reference to contract

Dear All,
We make a service contract in which we maintained the short text and Qty as 1 AU in the item overview area and we maintained services in the "Services" tab in the "Item details" area.(We maintained actual quantity in this area)
Now we are creating a Framework order with reference to this contract . When we select services against this contract , system is copying all the service details from contract but qty as 1 AU.
Why system is not copying the quantity mentioned in the contract (Services tab, item details area) into the framework order ????
Nilesh

What ever Order you are creating W.r.to Contract , it may be Frame work or Purchase Order..
they are considered as Release order against that Contract..
a contract is agreement between two parties for a perticular period..
System will not expect you to use the entire Quantity at Once..
That is why the Quantity mentioned in the Contract will not be copied..
By default you will get Qty as 1...
You need to change according to your requirement..

One order with reference to multiple contracts

Hi,
As we create one invoice(consolidated invoice) for multiple orders where condition is header data should be same for all the orders.In the same way can we create one order with reference to multiple contracts?
Please suggest.
Regards,
SATYA

Hi,
Thanks alot for the information.
Is this the only way to create one order for multiple contract? Why i am asking because in SAP we are creating contracts but the release order we are getting it uploaded from other software.I am in a service industry project where we do DP91(resource related billing) for all the contract.But in dp91 we can give only one contract at a time.
But we want to create order where multiple contract can be used .
And where in order we can see the contract number?
In the table it is visible as ref doc but not in the order.
Regards,
SATYA

BAPI-To create production orders with reference to sales order & item

Hi,
Can anyone tell me which is the best method to create open production orders?
Is there any BAPI available for creating production orders with reference to sales order & item.
I tried this BAPI "BAPI_PRODORD_CREATE".
I am getting pop up to enter serial number while executing the custom program.
Which table contains the serial number(effectivity parameters)?.

I have custom screen fields on notification service!
i think a bdc is better.

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.

How to Restrict Return Sales Order with reference to a cancelled invoice

SAP Standard is allowing to create Return Sales Order with reference to a cancelled invoice which practically should not be allowed.
Has any body worked on this problem and what could be the possible solutions so that return sales orders can not be created against a cancelled invoice.
Kindly share your possible solutions.

Hi Standard Process will not allow to create a Sales Order With Cancelled invoice,
Kindly go through at Copy Controls
T.CODE:VTAF
in that some body might have maintained between S1 invoice to RE Sales Document.
Remove the settings then u will be not able to create Sales Order w.r.t to Cancelled Document.
Rewards if Usefull
B.Shyam Sunder
SAP SD Consultant

Create a Sales Order with Reference to Contract using IDoc / LSMW ( AFS )

Hi Gurus,
I need to crate a Sales Order with reference to a Contract. I need to upload Sales Orders with reference to contract via LSMW.
So far, I've been able to create the Sales Order with ref to contract. But, the Sales Order Quantity is not getting deducted from the Original Qty in Referred Contract ( When try to create another Sales Order referring to the same Contract.) When a Sales Order is created manually, this is working fine.
Please tell me if I've missed some parameter which stopping it create the link to exact schedule line ( Sizes level )
The Details of the IDoc which is been created via LSMW are as follows;
Message Type: ORDERS
Basic Type     : /AFS/ORDERS05
Process Code : ORDE / DELO
( Tried with both process codes. But the Identification is the same for both: IDOC_INPUT_ORDERS )
*_In Header;_
Segment : E1EDK02 - IDoc: Document header reference data *
Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
Contract Order is mapped for field BELNR
*_In Item;_
Segment : E1EDP02 - IDoc: Document Item Reference Data *
Qualifier : '043' - Vendor Contract Number ( Tried with ' 005' - Customer Contract, but it's not working )
Contract Order is mapped to field BELNR
Line Item of the Contract is mapped to field ZEILE
I also tried passing the Schedule line of Contract in Segment : E1J3P01 AFS IDoc: Doc.item general data
to following fields;
J_3AETENV
J_3AVGETE
/AFS/UETENR
Still its not getting updated in the VBEP also..
Please help me with regard to this. Points will be awarded for your valuable contribution.
Thanks.

Hi,
This issue is been resolved.
One of my friend helped me with resolving this issue..
Once the below mentioned configurations were done on SPRO, the Sales Order was created with reference to Contract and the Qty was reflected when tried to create a new Order referring the same contract.;
u2022     SPRO --> SD -->Sales --> Sales Documents --> Sales Document Header --> Define Sales Document Types --> Field : Outline agreement message; from blank to u201CBu201D.
u2022     SPRO -->SD -->Sales --> Sales Documents --> Sales Document Header --> Maintain Sales Document Types for AFS --> Field : Outline agreement message; from blank to u201CAu201D

Need a function module to create production order with reference

Hi
I need a function module to create a production order with reference to an existing order. There is no BAPI available for SAP 4.7 release. I found that the function module CO_ZF_PRODUCTIONORDER_CREATE does not create with reference to an existing order.
Any help will be rewarded.
Pavan

Dear Pavan,
Unfortunately there is no FM for this..
Cheers
Nitesh

Repair order with reference to service nitification.

Similar Messages

Maybe you are looking for