Transact move order API for serial contril item in 10.5.10.2

Hello Friends ,
I need a Help from you , I am badly got struck up. I need to the transact move order part of O2C Cycle Using APIs.
I Could complete the flow upto transact move orders, there i got struck up. Here i need to pass the serial numbers as some of the Items are serialized items.
Can you plz suggest me.
Its in Very Urgent.
i am using version 11.5.10.2
Regards
Ganesh

Hello Ganesh,
Hope you have passes this issue.
I am in the same boat, I need to find out the APIs to update the serial numbers on order at the time of allocation/transact move order step.
Could you please help me with the process/steps/sample code involved in this.
Thanks in advance!
Raj

Similar Messages

Issue in Transact Move order while updating serial number

Hi All,
We need to perform sales order issue of items present in particular subinventory.
I am successful in creating sales order having one item .
I did the pick release of the order using the api ,wsh_picking_batches_pub.create_batch and wsh_picking_batches_pkg.submit_release_request to release the batch.
A move order got created , now I need to allocate the serial number for processing the move order,I used the below script to update the line record with incoming start and end serial number.
But the api is throwing error .
DECLARE
-- Common Declarations
   l_api_version      NUMBER                                 := 1.0;
   l_init_msg_list    VARCHAR2 (2)                          := fnd_api.g_true    ;
   l_return_values    VARCHAR2 (2)                         := fnd_api.g_false;
   l_commit           VARCHAR2 (2)                         := fnd_api.g_false;
   x_return_status    VARCHAR2 (2);
   x_msg_count        NUMBER                                 := 0;
   x_msg_data         VARCHAR2 (255);
   -- WHO columns
   l_user_id          NUMBER                                 := -1;
   l_resp_id          NUMBER                                 := -1;
   l_application_id   NUMBER                                 := -1;
   l_row_cnt          NUMBER                                 := 1;
   l_user_name        VARCHAR2 (30)                          := 'OPERATIONS';
   l_resp_name        VARCHAR2 (30)          := 'MFG_AND_DIST_SUPER_USER_APS';
   -- API specific declarations
   l_header_id        NUMBER                                 := 0;
   l_trohdr_rec       inv_move_order_pub.trohdr_rec_type;
   l_trohdr_val_rec   inv_move_order_pub.trohdr_val_rec_type;
   l_trolin_tbl       inv_move_order_pub.trolin_tbl_type;
   l_trolin_val_tbl   inv_move_order_pub.trolin_val_tbl_type;
   x_trolin_tbl       inv_move_order_pub.trolin_tbl_type;
   x_trolin_val_tbl   inv_move_order_pub.trolin_val_tbl_type;
   x_trohdr_rec       inv_move_order_pub.trohdr_rec_type;
   x_trohdr_val_rec   inv_move_order_pub.trohdr_val_rec_type;
-- Cursor to load Move Order Headers
-- CURSOR c_mo_hdrs IS
-- SELECT * FROM my_custom_move_order_hdrs ;
BEGIN
   fnd_global.apps_initialize (5939, 50625, 20003);
   mo_global.init ('INV');
   -- call API to create move order header
   DBMS_OUTPUT.put_line
                   ('=======================================================');
   DBMS_OUTPUT.put_line ('Calling INV_MOVE_ORDER_PUB.Get_Move_Order API');
   inv_move_order_pub.get_move_order (p_api_version_number      => l_api_version,
                                      p_init_msg_list           => l_init_msg_list,
                                      p_return_values           => l_return_values,
                                      x_return_status           => x_return_status,
                                      x_msg_count               => x_msg_count,
                                      x_msg_data                => x_msg_data,
                                      p_header_id               => 7360068,
                                      p_header                  => NULL,
                                      x_trohdr_rec              => l_trohdr_rec,
                                      x_trohdr_val_rec          => l_trohdr_val_rec,
                                      x_trolin_tbl              => l_trolin_tbl,
                                      x_trolin_val_tbl          => l_trolin_val_tbl
   DBMS_OUTPUT.ENABLE ();
   DBMS_OUTPUT.put_line
                    ('=======================================================');
   DBMS_OUTPUT.put_line ('Return Status: ' || x_return_status);
   IF (x_return_status <> fnd_api.g_ret_sts_success)
   THEN
      DBMS_OUTPUT.put_line ('Error Message :' || x_msg_data);
   END IF;
   -- Print the Move Order Header/Lines to be processed
   IF (x_return_status = fnd_api.g_ret_sts_success)
   THEN
      DBMS_OUTPUT.put_line (   'Header :'
                            || l_trohdr_rec.header_id
                            || ' '
                            || l_trohdr_rec.request_number
                            || ' '
                            || l_trohdr_rec.date_required
                            || ' '
                            || l_trohdr_rec.from_subinventory_code
                            || ' '
                            || l_trohdr_rec.header_status
                            || ' '
                            || l_trohdr_rec.organization_id
                            || ' '
                            || l_trohdr_rec.status_date
                            || ' '
                            || l_trohdr_rec.to_subinventory_code
                            || ' '
                            || l_trohdr_rec.transaction_type_id
                            || ' '
                            || l_trohdr_rec.move_order_type
                            || ' '
                            || l_trohdr_rec.operation
      l_trohdr_rec.from_subinventory_code := 'CustRet';
      --l_trohdr_rec.to_subinventory_code := 'Staging';
      l_trohdr_rec.operation := inv_globals.g_opr_update;
      DBMS_OUTPUT.put_line (   'Header Update :'
                            || l_trohdr_rec.header_id
                            || ' '
                            || l_trohdr_rec.from_subinventory_code
                            || ' '
                            || l_trohdr_rec.to_subinventory_code
                            || ' '
                            || l_trohdr_rec.operation
      FOR i IN 1 .. l_trolin_tbl.COUNT
      LOOP
         DBMS_OUTPUT.put_line (   'Line '
                               || i
                               || ': '
                               || l_trolin_tbl (i).line_id
                               || ' '
                               || l_trolin_tbl (i).line_number
                               || ' '
                               || l_trolin_tbl (i).line_status
                               || ' '
                               || l_trolin_tbl (i).organization_id
                               || ' '
                               || l_trolin_tbl (i).inventory_item_id
                               || ' '
                               || l_trolin_tbl (i).from_subinventory_code
                               || ' '
                               || l_trolin_tbl (i).to_subinventory_code
                               || ' '
                               || l_trolin_tbl (i).quantity
                               || ' '
                               || l_trolin_tbl (i).status_date
                               || ' '
                               || l_trolin_tbl (i).uom_code
                               || ' '
                               || l_trolin_tbl (i).operation
         l_trolin_tbl (i).from_subinventory_code := 'CustRet';
         --l_trolin_tbl (i).to_subinventory_code := 'Staging';
         --l_trolin_tbl (i).inventory_item_id := 19128;
         l_trolin_tbl (i).serial_number_start := '356030032497361';
         l_trolin_tbl (i).serial_number_end := '356030032497361';
         --l_trolin_tbl(i).quantity       := l_trolin_tbl(i).quantity
         l_trolin_tbl (i).operation := inv_globals.g_opr_update;
         DBMS_OUTPUT.put_line (   'Line Updated'
                               || i
                               || ': '
                               || l_trolin_tbl (i).line_id
                               || ' '
                               || l_trolin_tbl (i).from_subinventory_code
                               || ' '
                               || l_trolin_tbl (i).to_subinventory_code
                               || ' '
                               || l_trolin_tbl (i).serial_number_start
                               || ' '
                               || l_trolin_tbl (i).serial_number_end
                               || ' '
                               || l_trolin_tbl (i).operation
      END LOOP;
   END IF;
   DBMS_OUTPUT.put_line
                    ('=======================================================');
   -- call API to create move order header
   DBMS_OUTPUT.put_line
                    ('=======================================================');
   DBMS_OUTPUT.put_line ('Calling INV_MOVE_ORDER_PUB.Process_Move_Order API');
   inv_move_order_pub.process_move_order
                                       (p_api_version_number      => l_api_version,
                                        p_init_msg_list           => l_init_msg_list,
                                        p_return_values           => l_return_values,
                                        p_commit                  => l_commit,
                                        x_return_status           => x_return_status,
                                        x_msg_count               => x_msg_count,
                                        x_msg_data                => x_msg_data,
                                        p_trohdr_rec              => l_trohdr_rec,
                                        p_trohdr_val_rec          => l_trohdr_val_rec,
                                        p_trolin_tbl              => l_trolin_tbl,
                                        p_trolin_val_tbl          => l_trolin_val_tbl,
                                        x_trohdr_rec              => x_trohdr_rec,
                                        x_trohdr_val_rec          => x_trohdr_val_rec,
                                        x_trolin_tbl              => x_trolin_tbl,
                                        x_trolin_val_tbl          => x_trolin_val_tbl
   DBMS_OUTPUT.put_line
                    ('=======================================================');
   DBMS_OUTPUT.put_line ('Return Status: ' || x_return_status);
   IF (x_return_status <> fnd_api.g_ret_sts_success)
   THEN
      DBMS_OUTPUT.put_line ('Error Message :' || x_msg_data);
      ROLLBACK;
     ELSE
     COMMIT;
   END IF;
   DBMS_OUTPUT.put_line
                    ('=======================================================');
-- END LOOP;
EXCEPTION
   WHEN OTHERS
   THEN
      DBMS_OUTPUT.put_line ('Exception Occured :');
      DBMS_OUTPUT.put_line (SQLCODE || ':' || SQLERRM);
      DBMS_OUTPUT.put_line
                   ('=======================================================');
END;
Error Log
=======================================================
Calling INV_MOVE_ORDER_PUB.Get_Move_Order API
=======================================================
Return Status: S
Header :7360068 7360067 15-JUL-13 7 281 15-JUL-13   3
Header Update :7360068 CustRet UPDATE
Line 1: 6730069 1 7 281 19119 Staging 1 15-JUL-13 UN
Line Updated1: 6730069 CustRet Staging 356030032497361 356030032497361 UPDATE
=======================================================
=======================================================
Calling INV_MOVE_ORDER_PUB.Process_Move_Order API
Inv Item Id19119
Old Inv Item Id19119
Inv Item Id-356030032497361
Item Id
Org Id281
Serial Number356030032497361
=======================================================
Return Status: E
Error Message :INV_INV_INVALID_ATTRIBUTE_N_ATTRIBUTE_Start serial number
Please help to solve the issue.
Thanks,
Shruti K. Nayak

Hello Ganesh,
Hope you have passes this issue.
I am in the same boat, I need to find out the APIs to update the serial numbers on order at the time of allocation/transact move order step.
Could you please help me with the process/steps/sample code involved in this.
Thanks in advance!
Raj

How to use OE_ORDER_PUB.PROCESS_ORDER API for serial controlled items?

Hi Guys
We are using OE_ORDER_PUB.PROCESS_ORDER API with a custom application (R12 12.0.4/12.0.6) for booking sales orders. Right now we don't have serial controlled items, however pretty soon, we will launch medical equipment sales for which we have to start using serial controlled items.
Anybody has a sample script for the API dealing with serial controlled items?
Regards,
Raj

What kind of serial number related information do you capture during order creation?
Most businesses either generate serial numbers at the time of Sales order issue OR at wip completion.
Sometimes a serial number is generated at WIP assembly begin.
In any case, as long as you don't ALLOCATE serial numbers to a sales order at the time of entry or booking or reservation, you won't need to worry about serial# for oe_order_pub.
The serial# will come into picture for RMA processing. For that, you can use l_lot_serial_tbl_out oe_order_pub.lot_serial_tbl_type in the oe_order_pub. This will let you record the serial number for the product that is being returned.
Sandeep Gandhi

Mover Order API Serial Number

Hi All,
We have managed to create a sales order and pick release, the status of the line is "Released To Warehouse" with the next stage "Transact Move Order". Some of the items on the sales order are serial number controlled (serial numbers are generated upon receipt from purchase order), hence why the move order has not completed as it requires the serial numbers to be enetered to complete. I can manually do this via the move orders form and can see when I do this that the serial numbers are updated into mrl_serial_numbers_temp, query below for reference.
select wdv.source_header_number, wdv.delivery_id, mtrh.request_number, msnt.fm_serial_number, msnt.to_serial_number
from wsh_deliverables_v wdv, mtl_txn_request_lines mtrl, mtl_txn_request_headers mtrh,
mtl_material_transactions_temp mmtt, mtl_serial_numbers_temp msnt
where wdv.source_line_id = mtrl.txn_source_line_id
and mtrl.header_id = mtrh.header_id
and mtrl.txn_source_line_id = mmtt.trx_source_line_id
and mmtt.transaction_temp_id = msnt.transaction_temp_id
and wdv.source_header_number = '7010000538'
My question is can the move order update or serial numbers be doen via an API, if so which one?
Thanks in advance

Dear Colin,
Can you please tell me whats the value to pass for p_trx_tmp_id in API inv_trx_util_pub.insert_ser_trx ?
I guess, its not the same transaction_temp_id from MTL_MATERIAL_TRANSACTIONS_TEMP
Please let me know how to pass the value for that?
If you can provide a sample code, that would be gr8.
Thanks in advance.
Regards,
Jana

API to update a allocation and transact move orders.

Hi All,
This is for R12 in INV org (NON WMS enabled). Is there a way to update the move order allocation for a pick wave to update the picked quantity and set the missing quantity action to Cycle Count?
Thanks
Amit

We have exact the same requirement here with serial controlled items.
But you can refer to note 269144.1 firstly.

Back order line in transact move order form , drived the inventory negative

Hi,
I had problem with transacting some lines in several move orders (it was stuck and giving error each time I tried to transact or delete from view update allocation –> delete line)
In order to cancel these lines to proceed the manufacturing process I back ordered those lines by:
Inventory super user - > move orders - > transact move order - > tools - > back order line
Note that the move orders type was Manufacturing Pick
Now I noticed that this drives the WIP subinv Negative for those items .
So what is the problem and how can I solve it?
Thank you
Edited by: Ahmed.Abbas on Apr 16, 2011 2:39 AM

hi,
The problem was in the interface managers (Material transaction , Move transaction ) were inactive , i launched them
Review note 141493.1 in metalink to know how.
I also deleted the pending transactions with errors from mtl_material_transactions_temp and mtl_transaction_lots_temp ( the items were lot control ) .
Thats all :)

After Transact Move Order the Supply/Demand Type Disappears in INVDVDSD

1. SR#: 5474007.993
2. URGENT Response Needed? (vs. the normal 48 hour or less reply time): Yes
3. Customer: SIPA S.P.A.
4. Oracle Apps Version: 11.5.9
5. Error(s):None
6. Problem Description/Question:
1. A WIP job is creates and decriments the Available Quantity; but not the
Current On-hand in the Supply/Demand Detail form.
When a pick release is performed, they do not see the WIP job in the
Supply/Demand Detail form and the Current On-hand does not change.
2. After transact move order the supply/demand type disappear, available
quantity at the top right side of the form increases, but there is no line with
demand identifier wip discrete job = 12615.
See: "ELTERM_SUPPLYDEMAND_after_patch.doc" at:
http://gtcr.oracle.com/gtcr-dir/gtcr_12930/5474007.993/
Is It the intended functionality?
7. Steps taken to debug issue:
web-iv "INVDVDSD pick release discrete job"
Located several bugs:
Bug 4885821 SCREEN VIEW SUPPLY/DEMAND ITEM NOT CORRECT
BUG: 2991666 SUPPLY/DEMAND DETAIL FORM (INVDVDSD) DOES NOT
SHOW ITEMS ON MOVE ORDERS
BUG: 3671489 SUPPLY/DEMAND INQUIRY FOR ATP ONLY
SUBINVENTORY INCLUDES NONATP DISCRETE JOBS
Bug:3517095 MRP:ATP INQUIRY FROM WIP SHOWS WRONG RESULT
However; none seem to provide a definitive explanation.
Message was edited by:
Bob Marchant

Thx a lot for ur help dr.
I have activated the material transaction interface and now the stock quantity has decreased.
I just wish to confirm some points in the creation of the new Order Type.
I have done the following setups:
Order Category: Mixed
Transaction type code: Order
Fulfillment Flow: Order Flow - Generic
Line workflow assignment: BO Line - Inventory Interface
Default return line type: Credit Only Line
Default order line type: BO Line - Inventory Interface
Plz confirm if the setups parameters are ok especially the Default return line type: Credit Only Line
Thanks a lot dr.

How to restrict Sales Order LOV in Transact Move Orders

Hello
We would like to restrict LOV in the Transact Move Orders screen to only those orders that were created in that specific Operating Unit. Also, we would like to control the LOV for Release Rules to a specific OU.
I believe the LOVs for both these screens pull from MTL_SALES_ORDERS. Therefore, I guess we would need to create a Value Set of type Table, value will be SEGMENT1 (Sales Orders) but unsure about the where condition.
Any help would be appreciated.
Sanjib

Sanjib
Release Rules: Why don't you use the SRS version if pick releasing rather than the screen. Ofcourse you lose some flexibility to enter order number and customer information. If screen is a must you can take the LOV from the existing form and create a new record group in the new form instance trigger. Add this peice to the lov sql to control the pick release rules result:
(select 1 from org_organization_definitions cust_org
where org.organization_id=cust_org.organization_id
and operating_unit=FND_PROFILE.VALUE('ORG_ID'))
This org is mtl_parmeters table used in LOV.
2. Transact Move Orders: Instead of changing the LOV and playing with the Sales Order Flexfield, you can use the inventory organization security to control who can do a transaction. This will not change the LOV but definitely will control the access to the records after you have queried. As you know this is inventory or warehouse function not the OE function.
You can try one idea though:
Segment2 is order_type which is OU specific. You can create value set that picks the LOV from the order types table for a specific OU, assign that to the segment2 and create a security rule. This rule will have include and exclude rules. You include all the Order types that are in a specific OU and assign that rule to the resp of that OU where move order is transacted. This will limit the LOV of the order types to only those that are availble for that resp. I have not tried this but give it a shot.
Thanks
Nagamohan

How to add new line in transact move order line

Hi,
i am able to update locaotr in Transact move order.
But i want to add two locators for the same line.
I tried to insert one more record in data base, but getting error unique index error.
so how can we add new line in transact move order line .
please help to slove this isse.
Thanks In Advance
Venu.

Hi,
the fact that your question is posted in Order Management section, does the move order automatically generated by OM?
nevertheless, i don't think you should (or allowed, in this case) to add a new line in transact move order. Transact move order only queries (not create records) the move order lines eligible to allocate and transact.
So, I don't see why you need to add a new line in transact move order.
You can, however, add a new line in the allocation of the lines, where for instance, you need to have half of the line allocated to one locator, and the other half to another locator
Thanks

Move Order Numbers for Sales Orders

Hi Every one,
I got a Requirement Like Below.
After booking the Orders in Sales Orders form, we will pick release the Orders.
In our Sales Orders, we are giving the Subinventory from where the Item has to be fetched in the Ware House, while creating the Orders.
For us,While Pick releasing the Orders,We are getting multiple order numbers grouped under a single move order Header. But we require a distinct move order to be generated for each of the Sales Order.
Please Help me by suggesting how this can be accomplished.
Thanks in Advance,
Karthik..

Gerry,
There is standard way as I can see it. As you should be knowing the architecture is to create the picking batch fist (which in turn becomes your move order number) and then loop through for all eligible orders to create move order lines. The way to beat this is to create a batch for each order number. You can create custom program and loop through your eligible order lines and pass order number to picking batch.
If you are on R12( may be even 11.5.10.2), you can use WSH_PICKING_BATCHES_PUB. create_batch and release_batch. Just pass your order number also to to the record. What it does basically is creating a picking_batch (move order number) for each order.
Thanks
Nagamohan

Automatic Goods movement from CO11N for serialized materials

Hello,
I'm dealing with confirmation of discrete production orders. When I confirm last operation, the system has to post Good Receipt automatically but materials are serialized, so I know I cannot use flag "Automatic GR" in control key.
My requirement is:
soon after the confirmation, I want to call MIGO transaction (movement type 101) with order number, yield confirmed, material code coming from CO11N.
Both CO11N and MIGO have to be on line transactions.
I have activated enhancement CONFPP05 but the call transaction MIGO gives me the message "Order xxx is already being processed" because the confirmation isn't still saved .
The BADI WORKORDER_CONFIRM has the same problem.
I haven't found an exit after saving the confirmation.
Have you any suggest?
Regards
Nue

Hello
You can try Background job for all confirmed order, ran MIGO background
thanks
bala

Move Order API

Hi All,
Please advice how to modify move order by updating or deleting either by Interface or by API
i have created Move order by API inv_move_order_pub but unable to modify or delete please advice.
Thanks

Hi;
All APIs are listed in Oracle Integration Repository
http://irep.oracle.com/index.html
API User Notes - HTML Format [ID 236937.1]
R12.0.[3-4] : Oracle Install Base Api / Open Interface Setup Test [ID 427566.1]
Oracle Trading Community Architecture API User Notes, June 2003 [ID 241320.1]
Technical Uses of Customer Interface and TCA-API [ID 269121.1]
"12: How To Access API References via the Oracle Integration Repository" [ ID 462586.1]
"Oracle Integration Repository Documentation Resources Release 12" [ ID 396116.1]
Pelase also check below:
Api's in EBS
http://forums.oracle.com/forums/thread.jspa?forumID=39&threadID=984534&messageID=3890192#3890192
http://sairamgoudmalla.blogspot.com/2009/05/script-to-find-oracle-apis-for-any.html
API
http://forums.oracle.com/forums/thread.jspa?threadID=1038379&tstart=0
List of API
http://forums.oracle.com/forums/message.jspa?messageID=4198097#4198097
Oracle Common Application Components API Reference Guide
download.oracle.com/docs/cd/B25284_01/current/acrobat/jta115api.pdf
List of APIs and open interface R12
http://forums.oracle.com/forums/thread.jspa?messageID=2340033
Regard
Helios

Sales order line for Non Stock items progressed to Closed status, need to be Cancelled.

Hi,
First time posting to this community, I hope someone can help.
Currently we have a setup where non stock items are being added to sales order lines (charges, etc.).
These lines are being progressed through to Closed status automatically.
Users are reporting that they have entered the line in error and would like to change the status of the line to Cancelled.
We are unable to return the material (RMA) as it is non stockable/transactable etc.
Current workaround is to adjust the stock and make finance aware so that the line does not get invoiced.
However, the system still shows that the line is closed (i.e. provided to customer) which is not correct.
Is there any way of getting the line to a status of cancelled?
Your help is very much appreciated.
Regards
Tim

Hi Arif,
Many thanks for the warm welcome.
I'm thinking the only course of action I have for future, is to make the items stockable/transactable/returnable such that an RMA can be performed if added in error.
We can put a large qty into stock at zero value.
Thanks for your help in any case.
Tim

Restrict Sales Order Creation for Serial Numbers already in Sles Order/Sold

We have recently implemented variant configuration and usage of serial numbers.
Facing some problems because of this.
1. If a Material is in Stock e.g Material xyz and serial number 123
System allows us to create sales order and Deliver and Invoice Serial number 124.
I have activated Indicator: Serial Number Existence Requirement thru OIS2. However it solves only part of my problem.
If for Material xyz serial number 123 is in stock but serial number 124 has also been created and assigned to material xyz but not in stock, then system allows me to create sales order, delivery and billing for material xyz and serial number 124.
When I check MMBE I see zero stock when I click on serial number I see serial 123, which is inconsistent.
How to ensure that such a situation does not happen?
Also I do not want the system to create a sales order for a material for which sales order has been created.
e.g. for material xyz and serial 1234 if sales order exists then system should not allow creation of another sales order for the same combination.
However in case of consignment orders the system should allow only the logical transactions like consignment fill up or consignment returns.
Please help.
Regards
Rajkumar Reddy

Hi
This is nothing but Creating Roles and assigning the respective authorizations to the Roles for giving the access to the related Tcodes
This has to be done by basis people
using the Transactions
PFCG
SU21
SUIM
such that every user can not create the sales order or change it.
Reward points if useful
Regards
Anji

How to implement bapi for transaction code f-02 for multiple line items

Hi All,
I am having one requirement to of implementing bapi for tcode f-02.
I have identified the name of the badi e.i. BAPI_ACC_GL_POSTING_POST.
but i dont have any idea how implement it.
i have multiple line items for one header.
Please help me in this.
Regards,
Shoaib.

HI
In recording once u save, the recording comings out the transaction.
If u want the pop-up to display before save. Then in recording also
after entering all data and before Save press enter or do check.Try
this way after that save the transaction.
Regards,
Raghu.

Transact move order API for serial contril item in 10.5.10.2

Similar Messages

Maybe you are looking for