Error is Shiiping point in Sales order

Hi friends,
Ship.condition loading grp 0001 plant SF01 StLoc PR03 not defined
I have a material which has been created in storage location PR03. I am trying to make a sales order but when i try to save the sales order order I am getting the above error in incompletion log.
Can u please help me out of this.
Thanx.
Sriram.S.

Dear Sriram,
Go through this path and check the settings
IMG>Logistics execution>Shipping>Picking>Determine picking location-->Define storage conditions, Assign picking locations.
Transactions OMS6 and OVL3
If settins not avail do the setting accordint to your shipping point plantshipping conditions+storage location.
Also check the settings of shipping point dtermination in the OVL2 transaction.
I hope it will help you
Regards,
Murali.
Edited by: Murali Mohan.T on Mar 7, 2008 12:36 PM

Similar Messages

Error during Performing Setup - SD Sales Orders...

Hi gurus,
I am getting an error while Performing Setup - SD Sales Orders by following the below steps from SAP best practices document for Sales Overview cube(0SD-C03).
In the Display IMG view choose Data Transfer to the SAP Business Information Warehouse à Settings for Application-Specific DataSources à Logistics à Managing Extract Structures à Initialization à Filling in the Setup Table  Application-Specific Setup of Statistical Data  SD-Sales Orders - Perform Setup.
ERROR MESSAGE IS: "Error determining rate: foreign curr. local curr.
USD date 11/06/2005(doc. 9153)"
Thanks.
Syed.
Note: This topic is marked as questions and will be rewarded with points.

hi Syed,
you can use transaction SNOTE,
and menu go to->sap note browser, find if that oss note is there. this note quite old (2001).
manually, you can check program LSCUNF01 (SE38),
and compare with following (for r/3 4.6a - 4.6d),
depend on your r/3 version.
please ask basis help.
FORM ABWCT_EXIST
Delta 001
Context Block
FORM abwct_exist USING loc_curr for_curr exc_date
                                         value(exc_type).
*------- DATC enthält das invertierte Datum -
CONVERT DATE exc_date INTO INVERTED-DATE datc.
Delete Block
Insert Block
*----- TCURV als erstes lesen, falls Invertierung aktiv -
IF tcurv-kurst NE exc_type OR tcurv-mandt NE mandt.
    SELECT SINGLE * FROM tcurv CLIENT SPECIFIED
           WHERE kurst       = exc_type
            AND   mandt       = mandt.
ENDIF.
Delta 002
Context Block
      ENDIF.
    ENDIF.
Alter Eintrag nicht verwendbar -
ELSE.
Delete Block
*----- TCURV als erstes lesen, falls Invertierung aktiv -
    IF tcurv-kurst NE exc_type OR tcurv-mandt NE mandt.
      SELECT SINGLE * FROM tcurv CLIENT SPECIFIED
             WHERE kurst       = exc_type
              AND   mandt       = mandt.
    ENDIF.
Insert Block

Change pointer for Sales Order

Hi,
Using change pointers I want to create an IDOC when ever a specific field in the sales order line item is changed. I have activated the change pointer for message type ORDRSP. Also maintained the following entries in BD52
VERKBELEG(Object) VBAP(Table) ABGRU(field).
After this when I change this field at the sales order line item, it inserts entries into change pointer table.
But my problem is creating IDOC's from those change pointer entries. I am not sure which function module (MASTERIDOC_CREATE_XXXXX) works for this.
Anyhelp on this highly appreciated.
Thanks
Ram

Hi Ram,
I don't think so you can use change pointer for sales order changes. Usually, it is done through transaction code<b> NACE</b> - configuring condition for output type.
You can setup requeirement in procedure control to trigger IDoc ORDRSP for any changes in item level.
Hope this will help you and give an idea.
Regards,
Ferry Lianto

SDK Error -5002 when adding a sales order

I'm getting an error -5002 when adding a sales order.
Source code:
      IDocuments m_so2 = SBOCOMUtil.newDocuments(icmp, SBOCOMConstants.BoObjectTypes_Document_oOrders);
      line = m_so2.getLines();
      m_so2.setCardCode("2173231916");
      m_so2.setCardName("test Sales order");
      SimpleDateFormat formatter = new SimpleDateFormat("dd.MM.yyyy");
      Date today = Calendar.getInstance().getTime();
      m_so2.setDocDueDate(today);
      line.setItemCode("01005");
      line.setDiscountPercent(new Double(10));
      line.setItemDescription("description Testing");
      line.setQuantity(new Double(3));
      line.setTaxCode("0");
      line.add();
      long rc = m_so2.add();
Question:
Where can I find a list of error codes that can be easy to understand? PDF, word, etc.
Thanks.

Hi Diego,
Looking at your code I see that you are doing a
line.add();
You dont need to have this here unless you are adding another line to your document.
Maybe this will help you.
Also just because java is a bit different from VB get the last error message using
SBOErrorMessage errMsg= comp.getLastError();
System.out.println(errMsg.getErrorMessage());
-Cormac

Error while assigning Smartform in Sale Order

Dear All,
For taking the sale order printout, I do not want to create a SAP SCRIPT Form. So in NACE transaction, I have created one output type 'ZA01' and assigned a new Smartform to that output type.
Now, after adding this output type in Sale Order, when I am going to print the sale order using ZA01 output type system is giving error that WRITE_FORM is invalid, START_FORM is missing.
Please tell whether can we assign the Smartform to sale order or not. And if yes then how to correct the error.
Kind Regards,
Vishal

Dear Raghu,
I have checked it. And the entry is present in that table. But this error is coming only when I am giving Smartform. But system is not giving any error when I am giving script form.
So the problem is only for SmartForm.
Regards,
Vishal

Warning/Error Message delivery unit in sales order

Hello,
how is it possible to throw a warning or error message in the sales order, when the entered quantity is not a multiple of the delivery unit specified in material master sales tab 1?
Thanks
Anne

Hi,
Please take the help of your abaper and modify the user exit for sales order . Put a validation check at the time of entering the order quantity w . r .t delivery unit mentioned in the material master for that sales area and through a warning or error message as per your requirement.
For user exit please go through the below link:
http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/content.htm
Hope this will help you to resolve your issue.
Regards,
Krishna O

Error while creating quotation in sales order verion ?

Dear All,
while creating an quotation in sales order version management getting an error.
Sales Doc. MsgType Message Class        Msg.No. Message text
           E       AM                        53 Specify either address number or address
           W       V1                       555 The sales document is not yet complete:
           E       V4                       219 Sales document was not changed
thanks
vincent

Dear Vincent
May be this is related ABAP Issue please check with them because i found same issue
"BAPI_SALESORDER_CREATEFROMDAT2" - getting error while executing in se37.
"Specify either address number or address handle " BAPI_SALESORDER_CREATEFR

Error while creating OTR by sales order from SAP ECC to TM

Hi Experts,
We are trying to integrate ECC to TM. As of now we have managed to send sales order to TM but getting the following error. Messages are getting failed in SAP TM. Even if the product exists in the system (TM) still the error message persists. I have CIFed location, business partner, product from ECC and everything exists in SAP TM with the same business system group. Kindly advise.
Thanks & Regards,
Aunkur De

Hello Aunkur De,
Could you check if the business partner was assigned in to your location?
I have passed for a issue like that.
Best regards,
Vicente Picardi

Budget error while creating delivery from sales order

hi Gurus,
System is throwing error PB603 "Item 004 WBS element ABC-XXX budget exceeded" while creating delivery from sales order.
I am picking material from unrestricted plant stock (not in project stock).
I am also confused as sales order has 3 line items & error shows Item 004 !

Hi Kuldeep,
Check this note,
Note 159387 - Message BP603: incorrect line item is displayed
Its valid only till 4.6. Might give you some idea but.
Regards,
Gokul

Update terminated error while doing changes in sales order

Hi
We had found below error message while trying to save a sales order
RV_sales_document_update
Report-LV45UF0V
Row 265
Error details-SAPSQL_ARRAY_INSERT_DUPREC-671
This had happened for 2 sales orders alone..
"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
"SAPLV45U" or "LV45UF0V"
"VBEP_BEARBEITEN"
We are not using any user exit for VBEP...
Can u please tell us how to overcome this error
Regards
Sudha

How was it solved ? I have the same Issue.
<< Moderator message - Everyone's problem is important. But the answers in the forum are provided by volunteers. Please do not ask for help quickly. And consider opening your own thread on this >>
Thanks
Abhinav
Edited by: Rob Burbank on Jan 12, 2011 4:08 PM

Run Time Error while Entering Quantity in Sales Order

Dear All,
Iam getting Run time Error while iam entering material quantity in sales order.Please find the screenshot of the same.
kindly Help Me.Me. Plz note that we had done a system copy two days back to our new server.
Rgds
Thomson
ST22 Screenshot

Dear All
Its Resolved Thanks For your Valuable time Support
INCLUDE LV03VFB4 inside below code trigger error.
PERFORM VVBBD_AUFBAUEN USING WA_AVBBD
                                    WA_AVBBD-APOMOBILE
                                    DA_SUBRC
                                    DA_UPDKZ
                                    DA_VVBBD_TABIX
                                    0.
This Was the Error some how 0 was there we are removed the 0 now it is working fine
Rgds
Thomson

Error While doing settlement for Sale Order in MTO scenario

Hi,
In MTO Scenario - when i try to settle Sales Order i am getting the below error. Even i have maintained the settlement cost element for PSG in allocation structure A1.
Kindly help me
Define a settlement cost element for receiver type PSG
Message no. KD506
Diagnosis
In allocation structure A1 (controlling area BP01), you did not define which cost element should be used when settling costs/revenues of the sender. Nor did you define receiver type PSG.
Procedure
Assign a different allocation structure to the settlement sender (-> Master data -> Settlement rule -> Goto -> Settlement parameters), or maintain allocation structure A1.
Thanks
Kishore

Hi
Please check your allocation structure , it looks that settlement cost element that you have assigned in the allocation strcuture is not having correct cost element category.
Go to Allocation structure configuration (OKO6) and check your allocation structure A1.
check settlement cost elements is it by cost element or you have assigned separate cost element for settlement.
if you wants to settle with same cost element select By cost element.
if you wants to settle with different cost element create a cost element and assign settlement cost element.
http://help.sap.com/saphelp_di46c2/helpdata/EN/9d/1f4b6e5733d1118b3f0060b03ca329/frameset.htm
hope this helps you.
Regards

Error while trying to create sales order using oe_order_pub.process_order

Hi All,
I am trying to create a sales order using oe_order_pub.process_order api..
The Procedure i had written is as follows.
CREATE OR REPLACE PROCEDURE TEST_PROC
AS
x_return_status VARCHAR2(250);
x_msg_count NUMBER;
x_msg_data VARCHAR2(250);
F varchar2(2000);
--out parameters
x_header_rec OE_Order_PUB.Header_Rec_Type;
x_header_val_rec OE_Order_PUB.Header_Val_Rec_Type;
x_Header_Adj_tbl OE_Order_PUB.Header_Adj_Tbl_Type;
x_Header_Adj_val_tbl OE_Order_PUB.Header_Adj_Val_Tbl_Type;
x_Header_price_Att_tbl OE_Order_PUB.Header_Price_Att_Tbl_Type;
x_Header_Adj_Att_tbl OE_Order_PUB.Header_Adj_Att_Tbl_Type;
x_Header_Adj_Assoc_tbl OE_Order_PUB.Header_Adj_Assoc_Tbl_Type;
x_Header_Scredit_tbl OE_Order_PUB.Header_Scredit_Tbl_Type;
x_Header_Scredit_val_tbl OE_Order_PUB.Header_Scredit_Val_Tbl_Type;
x_line_tbl OE_Order_PUB.Line_Tbl_Type;
x_line_val_tbl OE_Order_PUB.Line_Val_Tbl_Type;
x_Line_Adj_tbl OE_Order_PUB.Line_Adj_Tbl_Type;
x_Line_Adj_val_tbl OE_Order_PUB.Line_Adj_Val_Tbl_Type;
x_Line_price_Att_tbl OE_Order_PUB.Line_Price_Att_Tbl_Type;
x_Line_Adj_Att_tbl OE_Order_PUB.Line_Adj_Att_Tbl_Type;
x_Line_Adj_Assoc_tbl OE_Order_PUB.Line_Adj_Assoc_Tbl_Type;
x_Line_Scredit_tbl OE_Order_PUB.Line_Scredit_Tbl_Type;
x_Line_Scredit_val_tbl OE_Order_PUB.Line_Scredit_Val_Tbl_Type;
x_Lot_Serial_tbl OE_Order_PUB.Lot_Serial_Tbl_Type;
x_Lot_Serial_val_tbl OE_Order_PUB.Lot_Serial_Val_Tbl_Type;
x_action_request_tbl OE_Order_PUB.Request_Tbl_Type;
--in parameters
l_header_rec OE_Order_PUB.Header_Rec_Type;
t_line_tbl OE_ORDER_PUB.Line_Tbl_Type;
BEGIN
apps.mo_global.set_org_context(204,null,'ONT');
l_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
l_header_rec.ORG_ID := 204;
l_header_rec.ORDER_TYPE_ID := 1437;
l_header_rec.SOLD_TO_ORG_ID := 1290;
l_header_rec.SHIP_TO_ORG_ID:=1425;
l_header_rec.INVOICE_TO_ORG_ID:=1424;
l_header_rec.PRICE_LIST_ID := 1000;
l_header_rec.salesrep_id := 1006;
l_header_rec.ORDER_CATEGORY_CODE := 'MIXED';
l_header_rec.VERSION_NUMBER := 0;
l_header_rec.OPEN_FLAG := 'Y';
l_header_rec.BOOKED_FLAG := 'Y';
l_header_rec.PRICING_DATE := sysdate;
l_header_rec.TRANSACTIONAL_CURR_CODE := 'USD';
l_header_rec.created_by := FND_GLOBAL.USER_ID;
l_header_rec.creation_date := sysdate;
l_header_rec.LAST_UPDATED_BY := FND_GLOBAL.USER_ID;
l_header_rec.LAST_UPDATE_DATE := sysdate;
l_header_rec.attribute1 := '250';
l_header_rec.operation := 'CREATE';
t_line_tbl(1) := OE_ORDER_PUB.G_MISS_LINE_REC; ---check
t_line_tbl(1).inventory_item_id := 193742;
t_line_tbl(1).ordered_quantity := 1;
t_line_tbl(1).operation := 'CREATE';
oe_debug_pub.initialize;
--oe_debug_pub.SetDebugLevel(1);
OE_MSG_PUB.INITIALIZE();
OE_Order_PUB.Process_Order
( -- p_org_id => 204,
--p_operating_unit => 'ONT',
p_api_version_number => 1.0,
p_init_msg_list => FND_API.G_TRUE,
p_return_values => FND_API.G_TRUE,
p_action_commit => FND_API.G_TRUE,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_header_rec => l_header_rec,
p_old_header_rec => OE_Order_PUB.G_MISS_HEADER_REC,
p_header_val_rec => OE_Order_PUB.G_MISS_HEADER_VAL_REC,
p_old_header_val_rec => OE_Order_PUB.G_MISS_HEADER_VAL_REC,
p_Header_Adj_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_TBL,
p_old_Header_Adj_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_TBL,
p_Header_Adj_val_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_VAL_TBL,
p_old_Header_Adj_val_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_VAL_TBL,
p_Header_price_Att_tbl => OE_Order_PUB.G_MISS_HEADER_PRICE_ATT_TBL,
p_old_Header_Price_Att_tbl => OE_Order_PUB.G_MISS_HEADER_PRICE_ATT_TBL,
p_Header_Adj_Att_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_ATT_TBL,
p_old_Header_Adj_Att_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_ATT_TBL,
p_Header_Adj_Assoc_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL,
p_old_Header_Adj_Assoc_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL,
p_Header_Scredit_tbl => OE_Order_PUB.G_MISS_HEADER_SCREDIT_TBL,
p_old_Header_Scredit_tbl => OE_Order_PUB.G_MISS_HEADER_SCREDIT_TBL,
p_Header_Scredit_val_tbl => OE_Order_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL,
p_old_Header_Scredit_val_tbl => OE_Order_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL,
p_line_tbl => t_line_tbl,
p_old_line_tbl => OE_Order_PUB.G_MISS_LINE_TBL,
p_line_val_tbl => OE_Order_PUB.G_MISS_LINE_VAL_TBL,
p_old_line_val_tbl => OE_Order_PUB.G_MISS_LINE_VAL_TBL,
p_Line_Adj_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_TBL,
p_old_Line_Adj_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_TBL,
p_Line_Adj_val_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_VAL_TBL,
p_old_Line_Adj_val_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_VAL_TBL,
p_Line_price_Att_tbl => OE_Order_PUB.G_MISS_LINE_PRICE_ATT_TBL,
p_old_Line_Price_Att_tbl => OE_Order_PUB.G_MISS_LINE_PRICE_ATT_TBL,
p_Line_Adj_Att_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_ATT_TBL,
p_old_Line_Adj_Att_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_ATT_TBL,
p_Line_Adj_Assoc_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_ASSOC_TBL,
p_old_Line_Adj_Assoc_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_ASSOC_TBL,
p_Line_Scredit_tbl => OE_Order_PUB.G_MISS_LINE_SCREDIT_TBL,
p_old_Line_Scredit_tbl => OE_Order_PUB.G_MISS_LINE_SCREDIT_TBL,
p_Line_Scredit_val_tbl => OE_Order_PUB.G_MISS_LINE_SCREDIT_VAL_TBL,
p_old_Line_Scredit_val_tbl => OE_Order_PUB.G_MISS_LINE_SCREDIT_VAL_TBL,
p_Lot_Serial_tbl => OE_Order_PUB.G_MISS_LOT_SERIAL_TBL,
p_old_Lot_Serial_tbl => OE_Order_PUB.G_MISS_LOT_SERIAL_TBL,
p_Lot_Serial_val_tbl => OE_Order_PUB.G_MISS_LOT_SERIAL_VAL_TBL,
p_old_Lot_Serial_val_tbl => OE_Order_PUB.G_MISS_LOT_SERIAL_VAL_TBL,
p_action_request_tbl => OE_Order_PUB.G_MISS_REQUEST_TBL,
x_header_rec => x_header_rec,
x_header_val_rec => x_header_val_rec,
x_Header_Adj_tbl => x_Header_Adj_tbl,
x_Header_Adj_val_tbl => x_Header_Adj_val_tbl,
x_Header_price_Att_tbl => x_Header_price_Att_tbl,
x_Header_Adj_Att_tbl => x_Header_Adj_Att_tbl,
x_Header_Adj_Assoc_tbl => x_Header_Adj_Assoc_tbl,
x_Header_Scredit_tbl => x_Header_Scredit_tbl,
x_Header_Scredit_val_tbl => x_Header_Scredit_val_tbl,
x_line_tbl => x_line_tbl,
x_line_val_tbl => x_line_val_tbl,
x_Line_Adj_tbl => x_Line_Adj_tbl,
x_Line_Adj_val_tbl => x_Line_Adj_val_tbl,
x_Line_price_Att_tbl => x_Line_price_Att_tbl,
x_Line_Adj_Att_tbl => x_Line_Adj_Att_tbl,
x_Line_Adj_Assoc_tbl => x_Line_Adj_Assoc_tbl,
x_Line_Scredit_tbl => x_Line_Scredit_tbl,
x_Line_Scredit_val_tbl => x_Line_Scredit_val_tbl,
x_Lot_Serial_tbl => x_Lot_Serial_tbl,
x_Lot_Serial_val_tbl => x_Lot_Serial_val_tbl,
x_action_request_tbl => x_action_request_tbl,
--For bug 3390458
p_rtrim_data => 'N',
p_validate_desc_flex => 'Y' -- bug4343612
COMMIT;
if x_msg_count > 0 then
for l_index in 1..x_msg_count loop
x_msg_data := oe_msg_pub.get(p_msg_index => l_index, p_encoded => F);
PRINT('x_msg_data: '||x_msg_data);
end loop;
end if;
-- Check the return status
if x_return_status = FND_API.G_RET_STS_SUCCESS then
PRINT('success');
else
PRINT('failure');
end if;
PRINT('x_return_status: '||x_return_status);
PRINT('x_msg_count: '||x_msg_count);
PRINT('x_msg_data: '||x_msg_data);
PRINT('x_header_val_rec: '||x_header_val_rec.accounting_rule);
PRINT('x_header_rec header_id: ' ||x_header_rec.header_id);
PRINT('x_header_rec order_number: ' ||x_header_rec.order_number);
PRINT('x_header_rec ship_to_org_id: ' ||x_header_rec.ship_to_org_id);
PRINT('x_header_rec payment_term_id: ' ||x_header_rec.payment_term_id);
PRINT('x_header_rec order_source_id: ' ||x_header_rec.order_source_id);
PRINT('x_header_rec order_type_id: ' ||x_header_rec.order_type_id);
PRINT('x_header_rec price_list_id: ' ||x_header_rec.price_list_id);
PRINT('x_header_rec invoicing_rule_id: ' ||x_header_rec.invoicing_rule_id);
PRINT('x_header_rec accounting_rule_id: ' ||x_header_rec.accounting_rule_id);
PRINT('x_header_rec org_id: ' ||x_header_rec.org_id);
PRINT('x_header_rec sold_to_org_id: ' ||x_header_rec.sold_to_org_id);
PRINT('x_header_rec invoice_to_org_id: ' ||x_header_rec.invoice_to_org_id);
PRINT('x_header_rec salesrep_id: ' ||x_header_rec.salesrep_id);
PRINT('x_header_rec invoice_to_org_id: ' ||x_header_rec.invoice_to_org_id);
PRINT('x_header_rec operation: ' ||x_header_rec.operation);
PRINT('x_header_rec transactional_curr_code: ' ||x_header_rec.transactional_curr_code);
PRINT('x_header_rec orig_sys_document_ref: ' ||x_header_rec.orig_sys_document_ref);
PRINT('x_header_rec request_date: ' ||x_header_rec.request_date);
PRINT('x_header_rec conversion_rate_date: ' ||x_header_rec.conversion_rate_date);
PRINT('x_header_rec last_update_date: ' ||x_header_rec.last_update_date);
PRINT('x_header_rec ordered_date: ' ||x_header_rec.ordered_date);
PRINT('x_header_rec creation_date: ' ||x_header_rec.creation_date);
PRINT('x_header_rec created_by: ' ||x_header_rec.created_by);
END;
It is throwing the following Error.
SQL> exec TEST_PROC;
x_msg_data: ORA-01403: no data found in Package OE_ORDER_WF_UTIL Procedure
Create_HdrWorkItem
x_msg_data: User-Defined Exception in Package OE_ORDER_WF_UTIL Procedure
Start_HdrProcess
failure
x_return_status: U
x_msg_count: 2
x_msg_data: User-Defined Exception in Package OE_ORDER_WF_UTIL Procedure
Start_HdrProcess
x_header_val_rec: Immediate
x_header_rec header_id: 156408
x_header_rec order_number: 64097
x_header_rec ship_to_org_id: 1425
x_header_rec payment_term_id: 4
x_header_rec order_source_id: 0
x_header_rec order_type_id: 1437
x_header_rec price_list_id: 1000
x_header_rec invoicing_rule_id: -2
x_header_rec accounting_rule_id: 1
x_header_rec org_id: 204
x_header_rec sold_to_org_id: 1290
x_header_rec invoice_to_org_id: 1424
x_header_rec salesrep_id: 1006
x_header_rec invoice_to_org_id: 1424
x_header_rec operation: CREATE
x_header_rec transactional_curr_code: USD
x_header_rec orig_sys_document_ref: OE_ORDER_HEADERS_ALL156408
x_header_rec request_date: 02-APR-09
x_header_rec conversion_rate_date:
x_header_rec last_update_date: 02-APR-09
x_header_rec ordered_date: 02-APR-09
x_header_rec creation_date: 02-APR-09
x_header_rec created_by: 13615
Any help on this would be appreciated.
I am using R12..

Hi Nagamohan,
Thanks for the reply..It was Vision Instance that i was working on..
There was some problem in setups. I had run the same script on other instance and it is working.
Before signing off i have one more doubt...
The script which i used is creating a sales order with booked_flag='Y' but flow_status_code is still 'ENTERED'
how can i change it to 'BOOKED' using API...
Thanks for the help...

Account Assignment Error When Posting GI Against Sales Order

Hello SAP Experts,
We are currently experiencing a problem during goods issueance against sales order (VL02N). The system terminates the issueance and gives error:
"Account XXXXXX requires an assignment to a CO object".
We have tried maintaining the GL account in OKB9 and assign a default profit center there but i didn't work. The material master also contains the profit center. We were only able to post the transaction if we try to default the a cost center in FS00. However we dont want to assign a default cost center as cost centers differ by plant. We are wondering why it asks the cost center considering that it already contains the sales order assignment. We checked the field selection of the GL account, movement type and even the posting key and all showed that the cost center is not required. We are now in a dead end situation here. Please please help us.
Thanks in advance!

Hello Praveen,
Thank you for your immediate response.
What confuses me is the fact that it asks for a CO element when in fact it is already assigned to one (it is goods issuance against sales order). Do you know why is the system behaving that way?
Thanks!.

Error in BAPI_SALESORDER_CREATEFROMDAT2 to create sales order

Hi all,
I'm trying to create a sales order using bapi_salesorder_createfromdat2. I have given the import parameters as per the documentation. But i'm getting the following error messages from the return parameter
number       message
233           SALES_HEADER_IN has been processed successfully
233           SALES_ITEM_IN has been processed succesfully
555          The sales document is not yet complete: Edit
311           Standard Order 73 has been saved
I gave the partner role (SP) and partner number in ORDERS_PARTNERS. But i din get any message regarding its processing.
Pls can anyone guide me to create sales order using this bapi.
Thanks & Regards,
Revathi.

Hi
     I Think there problem in passing data to function module some important data is missing
    run the functional in se37 and pass the data and see the result i have created sale order by passing the value below
header-doc_type = 'ZS4'.
    header-sales_org    = wa_temp1-vkorg.
    header-purch_no     = wa_temp1-bstnk.
    header-distr_chan   = wa_temp1-vtweg.
    header-division     = wa_temp1-spart.
    header-purch_no_s   = wa_temp1-bstnk.
    wa_partner-partn_role = 'AG'.
    wa_partner-partn_numb = wa_temp1-kunnr.
    APPEND wa_partner TO it_partner.
    wa_partner-partn_role = 'WE'.
    wa_partner-partn_numb = wa_temp1-kunnr.
    APPEND wa_partner TO it_partner.
    CLEAR: wa_partner.
      wa_item-material   = wa_temp2-matnr.
      wa_item-plant      = wa_temp2-werks.
      wa_item-req_qty    = wa_temp2-fkimg.
      wa_item-target_qty = wa_temp2-fkimg.
       APPEND wa_item TO it_item.
with regards
Nilesh

Error is Shiiping point in Sales order

Similar Messages

Maybe you are looking for