Purchase order with reference to internal order

Dear all
I am creating a purchase order with reference to a statistical internal order.The total PO value should not exceed the budgeted amount for that statistical internal order.How should i achieve this?
Thanks in advance.
Madhavi

Hello
First Create Budget Profile.
Make Specification In Availability Control as Activation Type ''01- Automatic activation during budget allocation''
Usage 100 and Tick ''Overall'' check box.
After that Make Setting for your Controlling area in SPRO Path '' Define Tolerance Limit for Availibility control''

Similar Messages

Error message display for PO creation with reference to internal orders

Sir,
While creating PO with Tcode ME21N (item category I) with reference to ' Internal Order with Funds provided (Tcode KO12), system displaying error message when Budget is exceeded.
But when Funds provision is not mentioned (Funds value is initial in KO12) , error message is not being given by the system during Po creation with ME21N.
Where should I configure in img(Tcode SPRO) , so that system will throw error mesage while creating PO without Budget Provision (Funds not mentioned ) in Internal Orders.
Regards,
Srinivasa Murthy

Hi Anupam,
The error message display as follows. (when the PO Price exceeds the Planned Funds kept for internal order)
This error comes during PO creation Process and PO can not be saved. This error message display is correct.
Item 001 Order 600643 budget exceeded
Message no. BP604
Diagnosis
In document item 001 Order 600643, budget for fiscal year 2009 was exceeded by 99,960,000.00 INR.
But my question is 'when funds have not at all been mentioned for the internal order' then system has to throw the same error as mentioned above. But it is not happening. System is allowing the PO to save which is not correct.
Regards,
Srinivasa Murthy

Purchase order with reference to Sales Order

Dear SAP Gurus,
I want to create a Purchase Order with reference to sales order.
I want to take the material in my stocks also. If i create a Purchase order with account assignment, i am able to take the inventory of that material as it is consumed at the time of GR (MIGO).
hope you understand my requirement.
Ashish

Hi
Go to SPRO->Logistic general->Tax on goods movement->India->Movement types.
Here you will find the group of movement types check which movement types is mantained for the out side movement groups or inward movement.
also check the Material Master in MRP view if the collective requirements (02) is mantained.
Regards
Sri

Create purchase order with reference to Sales order Line item

Hi All,
i had a requirement that i need to create the Purchase order with reference to sales order line item...
In T.code me27 client requied a input field for sales order no and with that order reference he want the data of line item to PO creation line item screen.....
please sujjust......how to proceed......
regards,
Ravi Nemani

Hi
Go to SPRO->Logistic general->Tax on goods movement->India->Movement types.
Here you will find the group of movement types check which movement types is mantained for the out side movement groups or inward movement.
also check the Material Master in MRP view if the collective requirements (02) is mantained.
Regards
Sri

Creation of production order with reference to sales order

dear all guru's,
i m having a requirement of creating production order with ref to sales order but without changing my old strategy of make to stock.
regards
ujwal

Hi,
For the purpose of creation of production order with reference to sales order while maintaing MTS strategy you need to maintain Make to stock strategy 40 in strategy group in MRP-3 View of Material Master.
This is the only Make-to-Stock Strategy which enables you create Production Order against both Sales order as well as Demand / PIR.
So if your strategy group is already 40 then you need not change it.
However if you are using any other Make-to - Stock strategy like 10, 11 etc. then it is not possible to create Production Order against Sales Order since they dont consider Sales Order in planning.So you need to change them and set strategy group as 40.
Hope this helps.
Revert if you have any doubt.
Regards,
Tejas
Edited by: Tejas Pujara on Sep 27, 2008 8:50 AM

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

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.

GI with reference to internal order

Hello,
We want to make a GI 261 with reference to an internal order using MIGO and get the error message:
Order xxxxxx not found or not permitted for goods movement
Message no. C6001
Diagnosis
Either the order xxxxxx does not exist or you have specified an order for which the function you want cannot be executed. For example, no goods receipt for a CO internal order or no goods issue with reference to a reservation can be carried out.
Procedure
Check your entries and select an order for which the desired function is permitted.
I would appreciate any suggestions as I have no idea how to post it.
Regards,
Grzegorz Skorus

Hi Gurus,
I am also getting same ERROR while doing Goods issue with reference to the Internal order with 261 movement type
Order 920040 not found or not permitted for goods movement
Message no. C6001
Diagnosis
Either the order 920040 does not exist or you have specified an order for which the function you want cannot be executed. For example, no goods receipt for a CO internal order or no goods issue with reference to a reservation can be carried out.
Procedure
Check your entries and select an order for which the desired function is permitted
Please give the T-code and detailed description for below solution
the configuration of Field Selection Comparison: moment Type - G/L Account sap sdn

Bapi To create sales order with reference of sales order.

Hi all,
Having requerment To create sales order with reference of onother open sales order.
Example: there open sales order which having qty of 20 for that 10 qty as already billed , for remain 10 qty as to create the new sales order with reference to the excsiting one.
Please guide me how do it.
Regards,
Santosh
Edited by: santosh jajur on May 15, 2010 11:47 AM

Hi Santhosh,
check this thread.
Re: Open Sales Order Migration
The last part of the thread says done.
hope you get a hint from that.
Also this one
Re: how to create open sales order using BAPI....?
http://abaplovers.blogspot.com/2008/02/bapi-sales-order-create-code.html
Regs,
SuryaD.
Edited by: SuryaD on May 15, 2010 9:09 PM
Edited by: SuryaD on May 15, 2010 9:10 PM
Edited by: SuryaD on May 15, 2010 9:11 PM

Production order with reference to sales order

Hi experts,
I have created one sales order.
I am getting an error as "sales order has no CO object" while creating production order with reference to that sales order. Can anyone help me on this ?
Thanks in advance.
Rgds,
Parul.

Dear singh,
pls check this given by yadav
T. Code: OKKP - Maintaining Controlloing Area
Select your Controlling Area and Click: Activate components/control indicators (left-hand Dialog Structure)
Here, Under Tab: Activate, check Boxes: Sales Order, Cost Objects, etc..
Check whether Strategy Group is maintained in Material Master (MM02) --> View: MRP3.
T. Code: VA02/ VA03 --> Tab: Procurement -> Column: RqTy
There, Check whether requirement type is relevant for MTO.
More information:
Req. type: KE (if, Reqmts class: 040 Mke-to-ord.w/o cons. - possible to create Production order)
Req. type: KEK (If, Reqmts class: 020)
Req. type: KSV (used for Make to stock - Planning with Assembly Planning Strategy 40 is being used in the MRP3 view of the material)
Also, Check other relevant settings in:
SPRO --> IMG --> Sales & Distribution --> Basic Functions --> Availability Check and Transfer of Requirements --> Transfer of Requirements
Best Regards,
vraj

Process order with reference to sales order

Dear All,
Is there any provision to create a manual process order with reference to a sales order .
Regards,
venkat

If you would like to create a process order with assignment to sales order item, then you have to enter the sales order item on the initial screen of the Transaction COR1 via the Arrow besides the input field for reference process order. This is the standard way to assign sales order for process order in COR1.
For production orders, there is a separate Transaction CO08 for this purpose. But for process order, there is no such separate transaction available.

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

Service Order with reference to sales order

Hi all,
My client is selling finish material and services to finish material my client requirement is Once we save the sales order, line item with service material system should generate Service order for serves which we are selling to customer
can any one guide me how to configure in SAP the movement we sales order system should generate the Service order
Thanks
Ram

Hi Ram
Say your finish material sales order is ZFIN and service order is ZSER.
Create a BDC program to create ZSER type sales order.(Take help of ABAPer).
Create new output type ZCRE. Assign this BDC program to ZCRE output type, such that when ZCRE triggers ZSER sales order creates.
Now assign ZCRE output type to ZFIN sales order type.
So conclusion, when you save ZFIN sales order, automatically ZCRE output type will trigger.
ZCRE internally calls VA01 for ZSER sales order. So ZSER get created when you save ZFIN.
try and revert

Production Order with reference to Sale Order.

Hi
The scenario im working on is qty contract. we create a qty contract and then create release orders as and when we get the requirement from the customer. Its a make to order scenario. So once the release order is created with ref to the qty contract, we do an mrp run using md02/md50. Then we create a prod order in Co07/Co08, the prod order is taking the qty contarct as ref instead of the release order(std sale order). When i give the sale order number in co07, the system is throwing an error "Account assignment cannot be carried out because of different origin number".
The details of the error is as follows:
Diagnosis
"The sales doc (release order) to which you want to refer is based on sales doc xxxxx (qty contract). Thesefore the settlemet and possible the inventory management are carried out using the number of the preceding document
procedure
Enter the doc and item number of the preceding doc(qty contarct).
But i want the productio order to be created with ref to the sale order(release order) only.
Please help me with a suitable solution. Also let me know where the assignment is made.
Thanks
Madhu

Hi Madhu,
In Make-to-Order, the reference Sales document will be the first document in the sequence where schedule lines are created.
In your case pls check, with which reference document you have prepared the contract.
In Co07, You need to take first document no. in the sequence in which schedule lines are created.
Following example will make you very clear.
Suppose Sales documents are created in following sequence
1) S. Inquiry (Schedule lines created)> S.Quotation > S.Order
For MPS run, I have to supply S.Inquiry no instead of S.Order
2) S. Inquiry (Schedule lines created)> S.Quotation (Schedulines Modified) > S.Order
For MPS run, I have to supply S.Quotation no instead of S.Order, S.Inquiry
3) S. Inquiry (Schedule lines created)> S.Quotation > S.Order (Schedulines Modified)
For MPS run, I have to supply S.Order no instead of S.Inquiry, S.Quotation.
Rewards if it is useful to you.
Regards,
Chintan

Reference of internal order in PO creation

Hi Friends,
Is there any way to control system not to allow to create purchase orders with reference to Internal orders if they are not released and not approved.
Present it is stopping at GR level if order is not released but we want to control this at PO level. Please suggest if any option to control this.
Best Regards

You can use the badi ME_PROCESS_PO_CUST, method PROCESS_ACCOUNT.

Purchase order with reference to internal order

Similar Messages

Maybe you are looking for