Move Order Number Generation?

Dear Gurus,
When I tab out the Move order Number field, a number is automatically generated. Is there any setup for this? Can I give a prefix?
Thanks & Regards
Merlin Rajesh

Hi,
The move order number is coming from the sequence MTL_TXN_REQUEST_HEADERS_S.
If you want to prefix it , then you have to customize .
Thanks,
Robert

Similar Messages

Move order number when doing the pick release

hi everyone ,
is there any way to specify the move order number when doing the pick release process
i wante to passe the move order number to the pick release API procedure
or is it possible to change it after doing the pick release
best regards

Uses MTL_TXN_REQUEST_HEADERS_S sequence to generate the move order number in, I believe, when-validate-item tirgger.
Thanks
Nagamohan

Move orader number generation

hi all
i create a sales order with one line of item x with qty 100 and book it
when i pick release it from the shipping transaction , the system generate a move order number .
i take this number and query in MOVE ORDER form by it it return nothing .
i want to know what it means , and in what form i can view this move transaction ?
thanks

Hi,
The move order number is coming from the sequence MTL_TXN_REQUEST_HEADERS_S.
If you want to prefix it , then you have to customize .
Thanks,
Robert

Production order number generation

hi,
i want to modify the format of product order number that system generates after creating the new order in create production order(Transaction code co01) . please help me out and tell how should i procede..
Moderator message : Duplicate post locked.
Edited by: Vinod Kumar on Jun 7, 2011 12:38 PM

Hi
This is a widely used sceanrio in Automotive.Engine ,Chasis are tracked through equipment serial number.
Serial Number can be internal (Assigned by SAP) OR it can be external.The general convention is to follow the numeric range but you can also go for Alphanumeric code.We have used only first 2 digits as alphanumeric balance were numbers having differenet significanace like
Product group
Line
Model
Year
what you are saying can be achieved by entire numeric sequence also.
You will have to define Equipment category , serial number ranges under Plant maintenance..technical objects through SPRO.
Please aslo note in Material master you have to define Sr.no.Profile also.
regards
Prakash

Internal Order Number Generation.

Dear Gurus,
The internal numbers generated in Ko01 are in the number range 71000 to 71999 for the order types ZAMC Z01 etc, but when i am generating the internal numbers, the numbers are being generated as 71001, 71002, 71010, 71020 etc, ie the number increment is not +1 ie it is random, kindly advise why this could be happening.
Thanks,
Anand

I was having the same problem. In my case, there is difference of 20 numbers between one order and another. My user is finicky and she has been making screaming noise that the numbers are not in sequence to each other. I tried to explain to her that Internal Order and its contents are more important than bothering about the numbering but her complaint has become more louder, unfortunately.
I spoke to one of my senior colleagues who advised me that internal numbering logic developed by R/3 SAP follows its own logic pattern which is unexplainable. As I understand from him, it may be based on the data space consumed by the type of Internal Order.
How did I resolve the issue? I converted the internal numbering to external numbering and whatever number given by the finicky user, I started entering to keep her happy. After all, it is their system and I am there for the production support.

?? default purchase order number generation

Hello everyone.
When a purchase order is automatically generated from a sales order, is it possible to make the new PO number the same as the SO number we've just set?
ie we need to manually overwrite the newly generated PO just like we did with the initial SO.
Any help on this would be rewarded with a front row seat in heaven =)

Groovy,
Couple of questions,
Are you creating the SO for a Drop Ship Warehouse which would automatically prompt to create PO.
OR
Are you on the SO manually checking Purchase Orders in the logistics tab and creating the PO.
Each of this scenario can be handled a bit differently.
Couple of things can be done. (1) You may create a User field (Sales Order No.) at the PO header level if the PO has a one to one relation with a SO and if the PO if for multiple SO then create a User field (Sales Order No.) at the row level. and enter the sales Order numbers in this user field.
(2) You can maintain a seperate numbering series for these kinds of SO and PO where you can maintain a Sync.
(3) When you copy a Sales Order to a Purchase Order, Create the PO as a draft and then open draft PO and select a manual numbering and enter the SO number.
NOTE: In his scenario the numbering Series of the SO should be much lower than PO and sometime this could cause ovenruns of number.
I have just given you the 3 possible scenarios. My best bet would be to try the (1) or the (2) one.
Let me know if you have any questions
Suda

'Move order pick slip report' Report not picking XML publisher Template.

Hi,
SUB: i have to create one XML report on .RDF(move order pick slip report).
Submitting procedure move order pick slip report : i have created one Discrete Job and released that Job, then Component pick release for that particular job. then move order number will generates. then automatically fires the 'Move Order Pick Slip' Report.
NOTE: what i meant to say is i am not submitting the report from SRS window. it will fires automatically when Component pick release.
For this i have taken .xml and generated .rtf according to my layout and i have registered with XML publisher also.it is correct . But while running the report i am geting output as XML codes not in template(wht i have .rtf) format.
if i have to see the output in template from. (i have taken in conc program output as XML also) still same problem.
please help me if anybody having solutions.
Thanks
Valli

Hi Valli,
1:The first thing i would suggest that please check the BI Publisher version you are using (on apps/and on template builder also).
2: In any case if your report is not picking up the template and generating the xml output , i suggest you to attach one program "XML Report Publisher" in your SRS.
Oncwe you run your report and its generate the xml output. you have to take the request id & from view ---> submit request--->XML Report Publisher. run this request again.
it will ask for the request id , select the appropriate request id and it will generate the pdf output as per your requirement.
But this is temporary solution , i strongly recommend you to check the updated version of BI Publisher and instaal it on your oracle apps instance. also use the updated version of bi publisher for Layout(Template Builder).
Regards
SRatnesh

Move order pick slip report XML report not geting out put as templete

Hi,
SUB: i have to create one XML report on .RDF(move order pick slip report).
Submitting procedure move order pick slip report : i have created one Discrete Job and released that Job, then Component pick release for that particular job. then move order number will generates. then automatically fires the Move Order Pick Slip Report.
NOTE: what i meant to say is i am not submitting the report from SRS window. it will fires automatically when move order is generated.
for this i have taken .xml and generated .rtf according to my layout and i have registered with XML publisher also.it is correct . But while running the report i am getiing output as geting codes not in template(wht i have .rtf) format.
if i have to see the output in template from. (i have taken in conc program output as XML also) still same problem.
please help me if anybody having solutions.
Thanks
Venakt M

Hi,
Looking for some help on this.
Thanks in advance!
Venkat

Multiple Approval hierarchy for Move Orders

hello
need to know how Multiple approvals can use with move order?
1)move order requisition having three lines for different items and hving three different planners.who will receive notification for approval? all three with same move order number?
if all three will receive some one may able to change details of lines ?how it will work ?
is there any multiple approvals can use for same items with different amounts? how if any one having doc please send to [email protected]
thanks

AME (Approval management engine) allows you to model all sorts of complicated hierarchies for move orders.
Sandeep Gandhi

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

Process Order Batch number generation at the time of order creation

Dear All,
I m facing some issue at the time process order creation:
Current Settings:
1. Batch Number Creation at the time of order create.
Reason for this setting: Release of order is done by releasing operations one by one, therfore batch number will be generated on the final operation release, thats why we set up batch creation at the time of order create.
2. For FG batch number generation there is a program that copy the SFG(in Order BOM) Batch number to FG. ITs a industry requirement.
Problem:
when we create FG order system generate the error message at the time of order creation tht No batch could be determine.
Please suggest the solution
Thanks,

Hi
Hope you have cretaed Batch serch strategy in COB1
U need to maintain it as per your strategy type.

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

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

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

Goods Receipt Screen: Purchase Order number stored

Hi all.
SRM 4.0, server 5.5.
When going into the Goods Receipt screen (BBPCF02 for example), the field Purchase Order Number is pre-filled with the latest PO, that a user has searched for. How could I make sure, that this screen is not filled out with the latest PO but just let the screen display the open POs from within the timeframe? I have too many users that have made a GR, return to the GR screen and then their previous PO number is stored, and they believe they still have not made the GR for that PO, so they do it again. I need to make sure, that the purchase order number value is never stored in this field - any ideas?

OMBT click on the groups button, select the
Material documents for goods movements and inventory diffs.
WA WE WF WH WI WL WO WQ WR WS WV WW WZ
And then select the maintain icon, you need to maintain the number range
for the year 2010.
ands OMBA for accounting finance doc number range
hope this helps

Move Order Number Generation?

Similar Messages

Maybe you are looking for