RF Transaction - Capture Serial Number

Hello Experts,
I have a scenario where the client wants to
capture the serial numbers during the picking?
capture the serial numbers during the goods issue?
is there any standard RF transactions in ECC 6.0 for capturing serial numbers while picking and GI process? or do we need customization? Please explain.
Can we print the serial numbers in packing slip and invoice??
Thanks,
Sen

Hello Sen,
SAP has included this functionality "Capturing serial numbder during picking" from ERP ECC 5.0 onwords.
LM80 is the standard RF transaction code for capturing serial number.
<b>Can we print the serial numbers in packing slip and invoice??</b>
Yes, you can print the serail number in packing slip and invoice, work with developer on this. For accurate information on this, post query in SD forum as well.
Regards,
Arif Mansuri

Similar Messages

Capture serial number at the time of shipment /delivery

Hi All,
Created Serial profile - XXXX
Added below procedure in it.
Profile         Description                                      serial usage   Eqip req
SDCC      Completness check for delivery                   03          01
SDRE      Maintain returns delivery                               03          01
"Exist Req" Column in Serial number profile: overview is unchecked / not selected as the requirement is, serial numbers should be entered during a business transaction but not as master data.
Hence didnot use t code IQ0 and created any serial number for material.
Assigned Serial profile in Sales tab and General plant 2 view of Material master.
After i create Sales order, i am Unable to populate serial number in VL01N (Delivery). i,e ..in Our bound delivery--> extras--> serial number..i click but ..i donot see ant fileds where i can enter serial numbers manullly.
Is there any setting iam missing?
Pls guide

Hi su,
try adding key
SDLS
Maintain delivery
02
01
regards,
Edgar

Unable to capture serial number in migo!

dear all,
i want to capture the serial numbers that i gave in MIGO transaction befor i save it to do some validation.
i have tried with mb_migo_document badi but the serial numbers are not captured.
is there any other way to capture serail numbers before i save the migo document?

hi,
check these badi.
MB_MIGO_ITEM_BADI BAdI in MIGO for Changing Item Data
MB_MIGO_BADI BAdI in MIGO for External Detail Subscreens

SAP WM-RF 'Serial Number' Transaction LM80 - How does it work?

Hi gurus
We are looking at using the standard SAP RF transaction 'LM80' - 'Serial number capture'
Does anyone have any experience with this transaction? How does it work and what is the process flow?
Cheers
Eddy

Hi
Please advise if this is the process others are using for LM80:
1. Create STO or Sales Order
2. Create Delivery
3. Create Warehouse Transfer Order
4. Pick/Confirm Warehouse Transfer Order
5. Scan serial numbers to completely picked delivery via LM80
6. Post Goods Issue
My question is: is there a way to 'pick' via serial numbers? The process would then be that you scan in serial numbers during picking
kind regards
Ed

Serial Number Not to capture During GR but need to maintain during PGI

Hi All,
Our client is the major distributor of Home appliances.
Following are the line of Business
Import the Goods - Maintains in their Distribution Centers and then Issue to Outlets. Finally, the Outlets will sale to End Customer.
For Warranty claim etc. the client want to capture Serial Number when it is sold to Customer. However for that reason as per my understandings, we have to Activate Serial Number profile at Inventory level and start capturing during Goods receipt itself.
However client do not want to capture it during Inbound Process as it causes operational issues. Hence I wanted to know if there is any option that if Serial number not captured in Inbound, is it possible to maintain at later stage like during Outbound.
I also noticed that if Serial Number Profile once activated , system not allowing to do GR until serial numbers are maintained . How to bypass this as well?
Awaiting for your reply,
Thanks,
JK

Hi Jidnyasu,
Nice day.
If you use transaction OIS3 to select the corresponding serial number profile, and then you could double click the "serializing procedures". After that you will find procedure "MMSL- maintain goods receipt and issue doc.".
Normally, the procedure MMSL will be active to both PGR and PGI but cannot be only active for PGI. And also, there is no other standard way can achieve this.
Hope this information is helpful to you.
Best regards,
Edward

Serial Number Transaction Report export to excel but serial not exported

Hi Experts,
I'm trying to export Serial Number Transaction Report to excel in a client database (SP00 PL47). Basically, the report has two screen, the Serial Number (Top) and Transactions for Serial Number (Bottom). When I try to export it, it only export the Transaction for Serial Number. We Need the serial number to be exported, how do we go about this? I tested same database on SP01 PL07 and exported the Serial Number and Transactions for Serial Number. Why is it working in other database, do we have settings that we need to configure?
Regards,
Sai

Hi Don,
In the serial number transaction report, when you click on the excel tab the Save as window will open just cancel the first window there is onther window opened, just save that window under the other name e.g. 123.
because both the window has same name.
Then check the excel file.
Regards,
Datta Kharat

Serial Number Performance and DB Locking

Hi All,
Can anyone assist with an issue we are having with our SBO2007 PL 42...
There are 8 million Serial Numbers in the system with an average of 1 million Serial Numbers per Item (8 Items). - Table OSRI
There are 40 milion Transactions in the system with and aveage of 5 Transactions per Serial Number.
When the Serial Number Selection Screen opens in a Marketing Document, it slows the entire organisation down and it seems like there are Locks in the Database that are causing this.
Can anyone help me understand why this occurs and if there is any way of overcomming this "Serious" Issue?
Thanks.

Hi,
Please close your duplicated thread.
Thanks,
Gordon

Maintain serial number pop up in MB31 in ECC6.0

Hi,
I have a finished material with serial number profile assigned in work scheduling view where business transaction MMSL( Serial number in goods reciept and issue) is defined as optional(2) in customizing.
We are migrating from 4.6 to Ecc6.0.
In 4.6 with the same master data and customizing setting , MB31 throw Maintains erial number pop up while the same does not apper in ECC6.0
The pop up is appering if serial number profile is changed to Mandatory (3) for MMSL business transaction
Is this the standard changed functionality in upgarde?
Your commnets are highly appreciated..
Edited by: santosh sarda on Nov 8, 2010 6:44 PM

Hi,
thanks for the resonse. we found out the root cause was in customer exit were implimenated but they were inactive in upgraded environment.
EXIT_SAPLIPW1_999
EXIT_SAPMM07M_999

I downloaded Lightroom version 5.7 in order to support tethered capture on my Nikon D750 and its still not working. Additionally when I was prompted to give my serial number for the update it was no where to be found on my Adobe profile although I purchas

I downloaded Lightroom version 5.7 in order to support tethered capture on my Nikon D750 and its still not working. Additionally when I was prompted to give my serial number for the update it was no where to be found on my Adobe profile although I purchased, and am paying monthly for my creative cloud for photography. Please help

Does your Cloud subscription properly show on your account page?
If you have more than one email, are you sure you are using the correct Adobe ID?
https://www.adobe.com/account.html for subscriptions on your Adobe page
If yes
Some general information for a Cloud subscription
Cloud programs do not use serial numbers... you log in to your paid Cloud account to download & install & activate... you MAY need to log out of the Cloud and restart your computer and log back in to the Cloud for things to work
Log out of your Cloud account... Restart your computer... Log in to your paid Cloud account
-Sign in help http://helpx.adobe.com/x-productkb/policy-pricing/account-password-sign-faq.html
-http://helpx.adobe.com/creative-cloud/kb/sign-in-out-creative-cloud-desktop-app.html
-http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
-http://helpx.adobe.com/creative-suite/kb/trial--1-launch.html
-ID help https://helpx.adobe.com/contact.html?step=ZNA_id-signing_stillNeedHelp
-http://helpx.adobe.com/creative-cloud/kb/license-this-software.html
If no
This is an open forum, not Adobe support... you need Adobe staff to help
Adobe contact information - http://helpx.adobe.com/contact.html
-Select your product and what you need help with
-Click on the blue box "Still need help? Contact us"

IB:How to update a serial Number which has Inventory Material Transactions?

Dear friends
first of all thanks for your time and valuable solutions
Install base: How to update a serial Number which has Inventory Material Transactions
problem description:
Install base > quick search
Here is Installbase record, when I query from quick search
Rec#     Item          Item Instance           Serial Number          Status
1     300-7000-01      3000000           1000XXX-0538JQ0003 Return for Adv Exchange
2     300-7000-01     8000000               1000XXX-0538JQ0003-     Return for Adv Exchange
3     300-7000-01     5000000               1000XXX-0538JQ0003-A     Return for Adv Exchange
looking above data, first and third records are the legitimate serial numbers(correct according to the client specs), second record is not legitimate since it has a dash as suffix, we found there are many illegitimate serial Numbers exists, needs to be updated with the right serial Numbers which I analyzed in excel after pulling data from mtl_material_transactions , oe_order_lines_all , mtl_serial_numbers , mtl_system_items_b
basically these are all RMAs
I need to update the second record as 1094SUZ-0538JQ0003-B as per the guidelines, while updating I need to keep all the existing contracts, Warranty, what ever material transations it has, need to be same.
we have a package updating the serial numbers using IB API (csi_Item_Instance_Pub.update_item_instance) but it is updating only the records which has no serial numbers present for that instance, if there is a serial number already exists it is not working.
user define error msg "Serial Number 1094SUZ-0538JQ0003- has Inventory Material Transactions. This serial number cannot be used to update an existing Item Instance", but I need to update this anyway!! or am I missing something here, please advice me
below post looks like similar issue, talks about hard update, I have no clue, by doing that the updated serial number will have same transations, contracts, dates....attached to it like the previous serial number
IB UPDATE_ITEM_INSTANCE ERROR - doesn't allow ACTIVE_START_DATE to change
would be great If you guys help me out, really appreciated!!
unfortunately I couldn't find any solutoin in metalink for the existing serial number update
code for updating the serial number using IB API
          x_msg_count := 0;
x_msg_data := '';
p_instance_rec.instance_id := rec.child_instance_id;
p_instance_rec.serial_number := rec.child_serial_number;
p_instance_rec.object_version_number := rec.child_object_number;
p_txn_rec.transaction_id := Fnd_Api.g_miss_num;
p_txn_rec.transaction_date := SYSDATE;
p_txn_rec.source_transaction_date := SYSDATE;
p_txn_rec.transaction_type_id := 1;
csi_Item_Instance_Pub.update_item_instance
p_api_version => 1.0,
p_commit => Fnd_Api.g_false,
p_init_msg_list => Fnd_Api.g_false,
p_validation_level => 1,
p_instance_rec => p_instance_rec,
p_ext_attrib_values_tbl => p_ext_attrib_values_tbl,
p_party_tbl => p_party_tbl,
p_account_tbl => p_account_tbl,
p_pricing_attrib_tbl => p_pricing_attrib_tbl,
p_org_assignments_tbl => p_org_assignments_tbl,
p_asset_assignment_tbl => p_asset_assignment_tbl,
p_txn_rec => p_txn_rec,
x_instance_id_lst => x_instance_id_lst,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data
Thanks
Suri

Suri
Used this. May not be perfect but should get you there. Only if the table is registered (all the seeded tables should be registered) this will work.
select distinct a.table_name,b.column_name from fnd_tables a, fnd_columns b
where a.table_id=b.table_id
and upper(b.column_name) like '%SERIAL%'
Also this is very old one but if you need history for this change add the history insert logic as well..
DECLARE
l_return_err VARCHAR2 (80);
PROCEDURE debug (p_message IN VARCHAR2)
IS
BEGIN
dbms_output.put_line (SUBSTR (p_message, 1, 255));
END debug;
BEGIN
debug('======================================================================');
debug('Switching from serial number XDT07406. to XDT07406 ');
debug('======================================================================');
UPDATE fa_additions_b
SET serial_number = 'XDT07406'
WHERE serial_number = 'XDT07406.';
debug('No of rows in fa_additions_b updated :'||sql%rowcount);
UPDATE fa_mass_additions
SET serial_number = 'XDT07406'
WHERE serial_number = 'XDT07406.';
debug('No of rows in fa_mass_additions updated :'||sql%rowcount);
UPDATE rcv_serial_transactions
SET serial_num = 'XDT07406'
WHERE serial_num = 'XDT07406.';
debug('No of rows in rcv_serial_transactions updated :'||sql%rowcount);
UPDATE mtl_serial_numbers
SET serial_number = 'XDT07406'
WHERE serial_number = 'XDT07406.';
debug('No of rows in mtl_serial_numbers updated :'||sql%rowcount);
UPDATE mtl_unit_transactions
SET serial_number = 'XDT07406'
WHERE serial_number = 'XDT07406.';
debug('No of rows in mtl_unit_transactions updated :'||sql%rowcount);
UPDATE csi_item_instances_h
SET new_serial_number = 'XDT07406'
WHERE new_serial_number = 'XDT07406.';
debug('No of rows in csi_item_instances_h updated :'||sql%rowcount);
UPDATE csi_t_txn_line_details
SET serial_number = 'XDT07406'
WHERE serial_number = 'XDT07406.';
debug('No of rows in csi_t_txn_line_details updated :'||sql%rowcount);
UPDATE csi_item_instances
SET serial_number = 'XDT07406'
WHERE serial_number = 'XDT07406.';
debug('No of rows in csi_item_instances updated :'||sql%rowcount);
UPDATE wsh_delivery_details
SET serial_number = 'XDT07406'
WHERE serial_number = 'XDT07406.';
debug('No of rows in wsh_delivery_details updated :'||sql%rowcount);
debug('======================================================================');
debug('Switching from serial number jct20591 to JCT20591 ');
debug('======================================================================');
UPDATE fa_additions_b
SET serial_number = 'JCT20591'
WHERE serial_number = 'jct20591';
debug('No of rows in fa_additions_b updated :'||sql%rowcount);
UPDATE fa_mass_additions
SET serial_number = 'JCT20591'
WHERE serial_number = 'jct20591';
debug('No of rows in fa_mass_additions updated :'||sql%rowcount);
UPDATE rcv_serial_transactions
SET serial_num = 'JCT20591'
WHERE serial_num = 'jct20591';
debug('No of rows in rcv_serial_transactions updated :'||sql%rowcount);
UPDATE mtl_serial_numbers
SET serial_number = 'JCT20591'
WHERE serial_number = 'jct20591';
debug('No of rows in mtl_serial_numbers updated :'||sql%rowcount);
UPDATE mtl_unit_transactions
SET serial_number = 'JCT20591'
WHERE serial_number = 'jct20591';
debug('No of rows in mtl_unit_transactions updated :'||sql%rowcount);
UPDATE csi_item_instances_h
SET new_serial_number = 'JCT20591'
WHERE new_serial_number = 'jct20591';
debug('No of rows in csi_item_instances_h updated :'||sql%rowcount);
UPDATE csi_t_txn_line_details
SET serial_number = 'JCT20591'
WHERE serial_number = 'jct20591';
debug('No of rows in csi_t_txn_line_details updated :'||sql%rowcount);
UPDATE csi_item_instances
SET serial_number = 'JCT20591'
WHERE serial_number = 'jct20591';
debug('No of rows in csi_item_instances updated :'||sql%rowcount);
COMMIT;
EXCEPTION
WHEN OTHERS
THEN
l_return_err :='Updating in one of the script has this error:'|| substrb(sqlerrm, 1, 55);
debug('Value of l_return_err='||l_return_err);
END;
Thanks
Nagamohan

Serial number transaction report

Hi,
Where do I find Serial number transaction report?
Do any one know t.code or program name?
I am unable to locate following menu path,
Inventory >>> Inventory Report >>> Serial Number Transaction Report
Please some one guide me.
Thanks and Best Regards,
Mohan

Try using tcode OIYH: Serial Number List
Thanks & Regards
JP

Serial Number Transaction Report Window isn't opening when adding AR Invoice

Hi,
For One of my Client the Serial Number Transaction Report Window is not opening when adding the AR Invoice.
In the Invoice all the item's that is present in the line level are SERIAL MANAGED and Management Method is ON RELEASE ONLY.
Why is it so?

Hi,
Do you receive any error message? Is it possible to add without selecting invoice without selecting serial number?
What is your B1 version and PL?
Thanks & Regards,
Nagarajan

Transaction IQ09 u2013 production ORDER number for the serial number not showed

In the ALV generated by IQ09, we couldn´t see any production order number with its respectives serial numbers listed.
We try to check in NOTES SAP, through "SER*" tables and programs RIQEUI21 and RIOBJK00, but without success.
In the IQ02 and IQ03 transactions, we can find the orders numbers, but our users would like to see at the ALV list.
Anybody knows any transaction that shows serial numbers and production orders in a unique LIST.
Thanks
Claudio.

Hi,
I think you can customized your requirement, see below table
In table SER05, the list of serial number details can be obtained. key the order no in SER05 table, get field OBJKNR, then pass this OBJKNR in table OBJK .
Some useful table for serial numbers
SER00 Generic table for serial numbers
SER01 Serial numbers assigned to a delivery
SER02 Serial numbers assigned to a guarentee
SER03 Serial numbers assigned to a material document
SER04 Serial numbers assigned to an inspection lot
SER05 Serial numbers for a production order
SER06 Serial numbers for Handling Units
SER07 Serial numbers for Stocktaking
SER08 serial numbers for Orders (SD)
I hope that this information clarifies the issue.
Regards,
Sankaran

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

APP-PO-14806 : Lot and/or serial number quantity does not match transaction quantity.

Hi. I Have Error : APP-PO-14806 : Lot and/or serial number quantity does not match transaction quantity. when receiving a transaction from a PO

Hi,
This may occur because one of either have happened
1. Lot Quantity is not equal to the quantitiy being delivered.
2. Check if the item has secondary UOM and if it is matching on the lot form.
Regards
Prakash kumar

RF Transaction - Capture Serial Number

Similar Messages

Maybe you are looking for