Error on RESB table changing planning order using BAPI_PRODORD_CHANGE

Hallo.
In my custom program ZINTERFACE_ORDER, I use BAPI 'BAPI_PRODORD_CHANGE' to change multiple production order (quantity / start date/ end date).
CALL FUNCTION 'BAPI_PRODORD_CHANGE'
     EXPORTING
number       = wk_ordine
orderdata    = wk_orderdata
orderdatax = wk_orderdatax
     IMPORTING
return         = bapi_return.
First order change works right, but the second order generate the error:
TYPE: E
ID      : CO
NUMBER : 888
MESSAGE: Internal: Error when reading document table RESB
The error is generated by COXT_BAPI_ORDER_CHANGE , called internally from the above BAPI_PRODORD_CHANGE
And I have to exit from my custom report and reprocess the second order to work.
It seems that there is a lock on RESB table.
Could you
help me?
Thanks a lot
Giancarlo

You need to find the lock that is being set. After your BAPI Commit, you need to test that the lock is cleared. If not, do a wait for 1 sec and retest.
Unlock (and lock) are queued objects that do not occur until after the commit is complete. Because they are queued, they can get slow. Especially when a background process is going to try to work with multiple in a short period of time.
Neal

Similar Messages

ASCP: How do I get the list of 1st level planned orders using msc_full_pegging table

How do I get the list of 1st level planned orders using msc_full_pegging table, is any one having the script.

Do you mean supply_type? If so, yes it will be in pegging table as supply_type or otherwise you can join this table with msc_supplies by joining transaction_id column and get the order_type from that which will be the supply type.
Thanks,
Abhishek Sharma
P.S:- Try opening the discussion in a separate window and see if you get the option to mark it correct or helpful,

BAPI to change planned orders details

Hi Experts,
I need BAPI to change Planned order details,which are created through SNP PPM's.I searched for Bapi and got one 'BAPI_MOSRVAPS_SAVEMULTI3' but this BAPI will change order details if created for PP/DS PPM's.
Kindly suggest will this BAPI only work or someother.
I want to keep the PPM name blank and save the order details through BAPI.
Pls reply asap.
Thanks
surbhi

Hi Surbhi,
You may please search on google, there are lots of tutorial on BDC, you will surely get the solution... in short BDC is to record a transaction & then use same recording to generate ABAP program & you can play with screen navigations & update the fields you required...
Regards,
Adarsh

Updating resource in planned order using reference characteristics

hi,
Please let me know the table and field to be used to map corresponding field (PLPOD - ARBPL) in ECC. I am trying to update work center in planned order using reference char.
Regards,
Yogesh

Yogesh,
table and field PLPOD-ARBPL are correct , and same shoild be reflected into characterstic data.
check syntex of dependencies once again , and test configuration using CU50 , and see the result.
while running transaction you can have trace on which can help you to see your dependencies are gettinmg trigered or not.
hope it helps you.
Regards

Creation of SNP Planned Orders using Optimizer

Dear Experts .....
I am facing some problems while creating SNP Planned orders using Optmizer ( Discret Optimization).....
For eg.
I am using 3 months horizon ... the first two months is daily buckets with 12 hours capacity each one and the last month is weekly buckets.
The product minimun lot size exceed the daily capacity .... this way planned order have been created in the weekly buckets at the end of the horizon.
I need the system to create orders in the correct date avoiding use of safety stock .....
Regards
Mauricio

Those other 2 settings was already done .....
It is still not working .... iI am receiving the following message ...
Production process model/PDS 00000000000001011301001 S: Cannot be executed
Message no. /SAPAPO/SNPOPT159
Diagnosis
Production process model 00000000000001011301001 S at location 0100 is intended for cross-period lot size planning. It can be started in bucket 20110404->20110404. However, it does not then end in the same bucket.
Thanks for your effort trying to help me with this issue.

When I create a Planned order using PDS, the Setup time is coming as 0.

We have been using PPMs for a long time, and now we are trying to migrate to PDS.
We are currently in SCM 7.0.
I successfully created the PDS in APO (using CIF from R/3). In the PDS (in APO), for a particular activity, I see the activity type is "S", and the Activity Duratiion (Fixed) is 43,200 Seconds.
However, when I create a planned order using this PDS, the activity time is zero (End time = Start Time).
When we use the PPM the setup time comes correctly.
Any help will be appreciated..

Senthil,
Thanks for your views.
I have checked all that you have suggested, and it is okay. The issue still persists.
One thing that I noticed was that it is working fine in the old SCM 5.0 environment - the setup time is coming correctly in the planned order.
However, we have this issue in the new SCM 7.0 environment. Is there something that is different in SCM 7.0 in terms order explosion ?
Reagrds,
Sastry

Need Automatic Lead-time scheduling in Planned Order using MD11

All,
Our users have a requirement that when they create a planned order using MD11, they would like system to do automatic lead-time scheduling based on the "basic finish date" entered by the user. Currently the system is taking 3 days from the in-house time maintained in material master to calculate the basic start date. But users want to use the 100 days that have been maintained in the routing.
Currently users have to click on "manual scheduling" on the planned order for system to pick up 100 days from routing which is an additional step for the users. Hence users want an automatic way in which system would do lead-time schedule when they enter the basic finish date.
Thanks,
Swapnil

Dear Swapnil,
In my understanding it is the standard SAP behaviour even if you have made the necessary settings in OPU5 for the planned
order type.
If my understanding is correct, then as per this setting the MRP behaves for the particular plant and order type combination.
Whenever you create a planned order manually you have to do a detailed scheduling and then you get the production dates
for the planned order.(This might be because generally when a planned order is converted into production order the system
carries out a lead time scheduling.- Check the same and correct me if I'm wrong)
Even if you update the material master through CA97,you will not get the detailed scheduling done along with the production
dates.So you have to perform this manual activity during MD11.
What is the reason of setting the in-house production time as 3 days,if the exact production time is going to be more?
Check and revert
Regards
S Mangalraj

Change planned order - MD12

Hi,
What is the function of 'assign version' from the list of 'edit' in MD12 - change planned order.
Is there a way to change the BOM revision level assigned by MRP run?
Currently MRP assign the most recent revision level to a planned order, and I would like to be able to change it to a previsious revision level.
Thanks
Lin-Lin Li

Hi,
"Assign Version" is like the reading Master data in Planned Order.
Now try this. in your Pl. Order Change Screen, slect Master data Tab pag.
Then try the "Assign Version", your BOM details in the lowerpart of the screen vanishes.
You will get the message saying "Explosion data has changed, please re-explode" if you confirm this by Pressing Enter.
Then the BOM details dat will go off and you can select another PV.
Otherwise directly you can change the PV in the entry screen itself.
Hope this helps..
Regards,
Siva

BADI For Changing Planned order Qty during MRP Run

Hi,
My requirement is i want to change Planned order qty based on some conditions during MRP run(MD02). Is there any BADI to fullfill my requirement.
Thanks,
Kishore

Not sure I understand the situation correctly...You want to delete the planned orders before MRP runs again. WHy do you want to do that ? Are these firmed Planned orders ?

Error while mass conversion of Planned order to production order

Hi All,
Thanks in Advance for help. We are facing one issue since Oct-2011.
We have set up batch jobs for early morning to convert planned orders in to production orders. This is set up for transaction COHV.
We have both MTO and MTS scenario.
But problem occurs in Make to Order (MTO) scenario.
Error comes in ST22 as " SAPSQL_ARRAY_INSERT_DUPREC"
*..Reservierungsköpfe inserten
IF NOT rkpf_i[] IS INITIAL.
INSERT rkpf FROM TABLE rkpf_i.
ENDIF.
Note : This error is not coming on consistent basis, it comes randomly. Secondly we are not aware of the reason/root cause of this error, hence not able to replicate error at all on Quality server.(Quality is backup of production till nov-2011)
Writing to SAP, they debugged and provided note 504255. A part of that note says "Remember that this note describes a MODIFICATION which differs from
the standard behavior of the system. Therefore, the customer assumes
the responsibility for the implementation of this source code
change. Due to this reason, SAP AG does not provide any support or
maintenance for the changed source code."
Hence client is reluctant to implement that note.
Can any one help us out on
1) What can be the cause of error as mentioned above?
2) Resolution apart from SAP note?
Best regards,
Ravi Davda

Hi Ravi,
I am also facing same kind of issues from past couple of months.
Sometimes this issue come up as sales order credit ststus is not approved and some times it happens due the following error INSERT rkpf FROM TABLE rkpf_i..
I am also looking for some permanent solution.And today I have also faced same error and will be converting it manually.
And can you tell for which client you are working?And if you find any solution for this please update me
Regards
Punjabi

Reg error when trying to convert planned order to production order

Dear all,
While trying to convert planned order to production order we are getting error CO684,( you cannot make an assignment to make to order stock---create an order with respect to sale order where account assignment to sales order or project is not allowed in settlement profile to chosen order type.
What is to be done to correct it.
Thanks in advance
Regards
madhav

Hi
Check which settlement profile maintained in your order type using OPJH.
Then go to the t.code OKO7 and select the same settlement profile which is there in your order type.
In receivers
Change the sales orders settings to
Sales orders 1 Settlement Optional
If in your scenrio not using sales order the change to Settlement not allowed
try this
Thanks
S.Murali

Change sales order using BAPI_SALESORDER_CHANGE

Hi i want to add a new line item to the existing sales order using BAPI_SALESORDER_CHANGE
but when i am trying it is giving
'Schedule line 0001 for item 000020 does not exist ' error..
please help me..

*********I wanted to add an new line item.***.. this is my code..********
LOOP AT gt_input3 INTO st_input3.
*Finding Max No of line Items
    IF fl_set IS INITIAL.
      READ TABLE gt_vbap INTO st_vbap WITH KEY vbeln = st_input3-vbeln.
      IF sy-subrc EQ 0.
        lv_posnr = st_vbap-posnr.
        fl_set = 'X'.
      ENDIF.
    ENDIF.
*Populate Item details
    lv_posnr = lv_posnr + 10.
    lv_vbeln = st_input3-vbeln.
    lv_order_header_inx-updateflag = 'U'.
    st_order_item_in-itm_number = lv_posnr.
    st_order_item_in-material = st_input3-matnr.
    st_order_item_in-target_qty = st_input3-imv_qty.
    st_order_item_in-plant = st_input3-werks.
    st_order_item_in-store_loc = st_input3-lgort.
   st_order_item_in-store_loc = st_input3-lgort.
    APPEND st_order_item_in TO lt_order_item_in.
*Populate item updation Details
    st_order_item_inx-itm_number = lv_posnr.
    st_order_item_inx-updateflag = 'U'.
    st_order_item_inx-material = 'X'.
    st_order_item_inx-plant = 'X'.
    st_order_item_inx-store_loc = 'X'.
    st_order_item_inx-target_qty = 'X'.
    APPEND st_order_item_inx TO lt_order_item_inx.
*Populate the Schedule Lines
    st_schedule_lines-itm_number = lv_posnr.
    st_schedule_lines-sched_line = '0001'.
    st_schedule_lines-req_qty = st_input3-imv_qty.
    APPEND st_schedule_lines TO lt_schedule_lines.
*Populate the update details of schedule lines
    st_schedule_linesx-itm_number = lv_posnr.
    st_schedule_linesx-sched_line = '0001'.
    st_schedule_linesx-req_qty = 'X'.
    st_schedule_linesx-updateflag = 'U'.
    APPEND st_schedule_linesx TO lt_schedule_linesx.
       AT END OF vbeln.
*Call BAPI Sales order change
      CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
        EXPORTING
          salesdocument    = lv_vbeln
          order_header_inx = lv_order_header_inx
        TABLES
          return           = lt_return
          order_item_in    = lt_order_item_in
          order_item_inx   = lt_order_item_inx
          schedule_lines   = lt_schedule_lines
          schedule_linesx = lt_schedule_linesx.
*Save Sales Order
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = 'X'.
      CLEAR lv_posnr.
      READ TABLE lt_return INTO st_return WITH KEY type = 'E'.
      st_ipfile_err3-message = st_return-message.
*Error Log
      LOOP AT gt_temp3 INTO st_temp3.
        IF st_ipfile_err3-message IS NOT INITIAL.
          MOVE st_temp3-record TO st_ipfile_err3-record.
          IF fl_set1 IS INITIAL.
            APPEND st_temp_err TO gt_ipfile_err3.
            fl_set1 = 'X'.
          ENDIF.
          APPEND st_ipfile_err3 TO gt_ipfile_err3.
        ELSE.
          APPEND st_temp3 TO gt_audit3.
        ENDIF.
        CLEAR : st_temp3,
                st_temp_err,
                st_ipfile_err3,
                fl_set.
      ENDLOOP.
      REFRESH : gt_zrman,

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

Creating SNP planned order using ''BAPI_MOSRVAPS_SAVEMULTI3'

Hi Experts,
I am new to SAP-APO, kindly clarify my question. I am using 'BAPI_MOSRVAPS_SAVEMULTI3' with source of supply PDS for creating SNP planned order by passing 'EE' in the table parameters 'ORDER_HEAD-MASTER_ATPCAT'. It is creating a planned order which is PPDS planned order with number range starting from '1000...' rather than creating SNP planned order with number range starting from '8000..'. Please let me know what might be the reason for the BAPI misbehaving incorrectly. Also kindly let meknow what are specific parameters to pass to above bapi to create SNP planned order.

Hi,
The BAPI BAPI_MOSRVAPS_SAVEMULTI3 is used for creating PPDS inhouse orders.
You will have to use BAPI_MOSRVAPS_CREATESNPORDER for SNP inhouse orders creation from SNP PPMs( there is no explict mention of SNP PDS- you may please check).
Regards
Datta

Define start date in SNP interactive table of planned order

hi,
does anyone know how to control the start date and the scheduling of planned order created in the SNP interactive table?

Hi Arieh,
For SNP Pl.Order the standard SAP APO behavior is to control the availability date (End date).
To control Start date you have to convert SNP Pl.Order in PP/DS Pl.Order. Then in the PPT1, production periodic view you can change by start date if you change the strategy to Forwards.
Regards, Marius

Error on RESB table changing planning order using BAPI_PRODORD_CHANGE

Similar Messages

Maybe you are looking for