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

Similar Messages

Update termination error while doing PGR

Hi,
I got this error while doing PGR, please do suggest the dolution.
Update was terminated
System ID....   DPT
Client.......   900
User.....   SDUSER
Transaction..   VL02N
Update key...   4BEAA8A2A6DA0609E1000000AC1107A7
Generated....   12.05.2010, 18:38:55
Completed....   12.05.2010, 18:38:56
Error Info...   Update program: I/O error Error; function Update, RC= 4, key
Thanks,
Swapnil

Hi Lakshmipathi,
I have checked the analysis in SM13, got the folllowing,
Function Module        SERIALNUMBER_POST
Status                        Update was terminated
Report                        LIEP1U01
Row                            159
Error details   Class:     IS         Number:    229
Update program: I/O error Error; function Update, RC= 4, key

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

Termination error while doing me31k

HI Experts,
This is the sincere apology for the previous thread which was in capital letter subject" termination error while doing me31k
Posted: Mar 6, 2012 2:56 AM
HI while performing transaction ME31K I'm getting follow error
Runtime error: DYNPRO_NOT_FOUND
What Happened?
Error in the ABAP application Program
The current ABAp program "SAPLXM06" had to be terminated because it has come across a statement that unfortunately canont be executed.
Error Analysis
The system attempted to use dynpro 0201 in program "SAPLXM06".
This dynpro does not exist.
Trigger Location of Run TIme Error
Program: SAPLXM06
Include: MM06E00C_CUSTSCR1_HEAD_SET_DAT
ROW: 10
There is a Edit button, that allows you to change the subject
Edited by: Jürgen L. on Mar 6, 2012 8:41 AM

Dear MM user,
Follow the documentation of this enhancement (see transaction SMOD):
Within the documentation of enhancement MM06E005, via TA SMOD, it specifically states that if you use the enhancement you must generate six listed dynpros (screens), even if you are not using them.
So you may goto transaction CMOD and enhance the same.
For example, the dynpro area should be like the following:
Calling screen No. Area Called screen No. ShortTxt
SAPMM06E 0101 CUSTSCR1 SAPLXM06 0101 Subscreen: PO header
SAPMM06E 0111 CUSTSCR1 SAPLXM06 0111 Subscreen: PO item
SAPMM06E 0201 CUSTSCR1 SAPLXM06 0201 Subscreen: agreement
Regards,
ian Wong Loke Foong

Update Termination Error while creating Delivery

Hello Experts,
I am trying to create delivery with reference to Standard Order when I click on SAVE I am getting message that delivery is being created. But when I am trying to open the same delivery in change mode I am getting Update termination Error saying delivery not created.
So what I tried doing is while creating delivery I have given Picked quantity and done with PGI then i am able to save the Delivery successfully and table LIKP is also updated. But this is not always that I can do. In my production system, without doing PGI I should able to save Delivery.
Please could anybody help me on this ..is there any SAP notes?
PS: My system is upgraded from ECC 6.0 Ehp2 to ECC 6.0 Ehp7.
Many Thanks in advance.
Priyanka J.

Hello Kiran, Hello Klaus,
Below are the details;
Function Module
RV_DELIVERIES_SAVE
Status
Update was terminated
Report
LV50UF0L
Row
50
Error details   Class:
00
Number:
671
Internal session terminated with a runtime error POSTING_ILLEGAL_STATE
MENT (see ST22)

Update termination error in Nimination change

Hi All,
The issue is regarding the e-mail message that the user is receiving in SAP mail box when trying to change the nomination.
where we need to maintain the e-mail address to avoid this update termination error?
Regards,
Suresh.D

Use transaction SU01.
Regards,
John.

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 was terminated error ,while doing PGI

Hello All,
While Posting Goods issue for a Delivery we are geeting -Update was terminated error.
When Analysed in SM13 ,it shows error message as :-Error Info... C4 001: Value "03/09/2010
Checked for various dates in Delivery ,Sales Order & delivery both created after 9th march 2010.
Please advice ,if someone have encountered same kind of issue .?
Do we have way to find clue to error through update key.?
Update key... 4BA0B325C79F00BEE10080009974E162
Regards,
Vikas

Hi Vikas,
This is Basis issue, you need to talk with the basis team.
They will clear this issue.
Hope it helps,
Regards,
MT

Update Termination Error while modifying PO in ME22n

Hi All,
I am facing one problem,while modifying the PO using ME22n.After modifying the PO when I save it ,Express Document "update was terminated" error comes.
Can anybody please guide me on this, why it is happening .It's very urgent.
Thanks in advance.

Hi
Check the following link:
http://www.sapfans.com/forums/viewtopic.php?p=822485&sid=253f8b02796c0b390a5180b3d1a86661
Though not relevant for PO......the basics are same.
Regards
Aravind
Assign points if useful

Update termination error while parking multiple items using BAPI fn module

hi experts,
i am facing a problem with bapi_incominginvoice_park.when i am trying to park invoice for single item for the po the invoice number is generating and getting updated in database in the same way when i am trying to park for multiple items the invoice number is genrating but not getting updated in database table.Here i am getting error 'Express document update terminated BY THE user'.How to solve this problem to find these error i have gone to se13 transaction,there it is showing SAQCL_DUPRC.it is saying duplicate errors in table but there are no duplicates in table.
Thanks,
Vinod

hi vinod ....i tried the following it worked...
while sending tax info dont send any tax table manually i.e updating the vit_tax table using append statement
also while testing function module for multiple PO , no need to provide the tax info in the tax table
what we have to do is only to provide 'X' In the tax calculation option in the header details
HEADERDATA-CALC_TAX_IND = 'X'.
1.this will enable tax
2. will make the po status green so that the parked document can be posted .

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

Termination error while creating and saving Work Order from a Notification

Hi All,
While creating Work Order from a Maintenance Notification, we get a error message "Update Termination OPROL Initial Number". This happens even while creating Maintenance Notification & Work Order separately and assigning the Notification in the Objects tab of the Order subsequently.
Could any body please help in this issue.
Thanks,
SS

Hi Sourabh,
Please check the link:
Express Document Update terminated while Scheduling Preventive single Plan
it will help you, it is actually the Number range issue.
Regards,
Yawar Khan

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 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...

Automatic price update if key field values changed in sales order and bill

Hi Experts,
I have requirement as follows.
Scenario: - We wanted carryout the pricing based on Incoterms, customer and material. I have created the condition table with these fields. And maintained the condition record. The values will flow to sales order without any problem.

Problem: - When we change the incoterms say for CIF to FOB the system should redetermine the price automatically, but this is not happening (If will redetermine only freight). If we carryout new pricing manually the right price will flow.

Expectations: - Is their any exit or any configuration setting where in system will redetermine the price automatically if we change the field value in sales order(For the field value it will be used to create condition table).
If anyone done this please help me with setting or Exit and code to enable us to come out from the situation.
We need this to happen while creating sales order as well as billing, Since @ billing prices will be redetermined.
Thanks in advance for the needful.
With regards,
Manjunatha H.S.
M: 9740433511


Hi Shivakumar,
You can use USEREXIT_NEW_PRICING_VBAP in include SAPMV45A for this.
Regards
Nikhilesh

Update terminated error while doing changes in sales order

Similar Messages

Maybe you are looking for