Picking Area
Hai Friends,
While creating delivary document (VL01N) when entered storage location picking area is grey out, but in Transfer order (LT03) materia is pick but in VL01N enter the picking quntity How it possible pls help me
Regards
Reddy KS
Hi Reddy,
We can do Picking of the materials in two ways.
1. Manual Picking
2. Picking using Warehouse Management
1. Manual Picking is possible when you are not maintaing any warehouse for your Plant or storage location. Then in this process, if you create delivery using VL01N then the pick quantity will not be greyed out. You can give the quantity there.
2. But if you mantaine warehouse for your plant or storage location then its not possible to do manual picking. Thatsway the Pickquanity field is greyed out in VL01N. The using transaction LT03 , you can do picking. In LT03 you give Warehouse no. and Deliveryno. and the materials will be picked. Or using t.code VL02N go into the delivery you can do Picking, this will take you to LT03 Screen.
Hope this gives you idea.
For better understanding you do picking once with warehouse and once without warehouse management. You will get clear idea.
REWARD IF HELPFUL.
Regards,
Praveen
Similar Messages
-
ratings and picks are not shown in the pictures in the filmstrip, although marked in the LR presets. Who can help?
found the solution: the filmstrip was to small !!!
-
Queue Determination by Picking Area
Dear all,
I am having difficulty with the correct Queue determination.
Current config has four wild cards (***) and no Door, determining Queue-A
I have added one line in my config table where the wild card voor Picking Area is replaced with a Real Picking Area number, and I have assigned one location to it. Also this line has Queue-B as queue to be determined
In my TO the destination bin is the one with the picking area mentioned above.
Still, the new Queue is not found.
I do not get it. Do you? If you do, please let me know.
Best regards,
NickThere is a very useful SAP OSS Note out there that sets out the correct settings required for Placements/ Removals and Other stock transfers. Have a look at:
Note 320804 - Created transfer orders are assigned to no queue
thanks,
Adam. -
Picking Area in the material master is GRAY
Hi,
If I maintain a material master manually by tcode MM01, the picking area in the WM view is not gray (changeable) when I try to change it again via tcode MM02;
but if I create the data with LSMW, the filed is gray when I try to change it via MM02.
Kindly please advise what the reason is.
Thanks.It is hard to follow this thread. On 8/19 at 4:51you wrote:
the WM view is not gray (changeable) when I try to change it again via tcode MM02
on 08/21 at 8:06 you wrote:
I extend WM views of material master via transaction MM02, the picking area is changeable
and today at 3:40 you wrote:
If I maintain the material master via tcode MM02, I can see the field "picking area" is grey,
Can you clarify what which statement is the correct one?
Or did you change some settings between theses statements?
Edited by: Jürgen L. on Aug 22, 2008 8:10 AM -
Picking area doesn't work for MDE
Hi Gurus,
I create a picking area for warehouse( W01)storage type(S01)picking area(P01),
then i assigned areas and activities to queue(Warehouse(s71)screen(01)tranc.type(A)source type(S01)source picking area(P01)destination type(***) destination picking area(**)+door(**)+ Queue(Q01)).
then i did mb1a+201 ,my destination bin was assigned to picking area 001, and my source type was S01, but my TO didn't go to queue Q01, why ? can you give me some hint?
by the way , if i didn't use picking area(Warehouse(s71)screen(01)tranc.type(A)source type(S01)source picking area(**)+destination type(*)+ destination picking area(*)+door(**)+ Queue(Q01)).
My TO will go to Q01.
Thank you in advance!
BR,
DragskyDo use ***, now it works!
-
Transfer Order Splitting By Picking Area
Hi,
Appreciate some help on this one.
Our system is currently set to split picking transfer orders by storage type - I'm trying to switch this off.
Instead I would like to split by picking area, so if I have say, picking area 001 across 2 storage types, I would like a pick that goes across these 2 storage types to be created on ONE TO.
I have tried various combinations of sorting and splitting but so far no luck.
It seems that the 'Split Picking Area' check box in Define Profile > Profile for Transfer Order Splitting actually refers to the storage type.
If this option is checked, I get 2 TOs, even though my picking area is the same across the 2 storage types I am testing.
If this option is unchecked, I get one TO, even if I set the picking areas to be different. It is almost like the picking area has no influence.
I read something about 'Forced' splitting - I wonder if there is an option to uncheck 'Split Picking Area' and then set my sorting in a such a way that I get my desired split??
Any hints or tips gratefully received.
Thanks
GuyHi,
"Instead I would like to split by picking area, so if I have say, picking area 001 across 2 storage types, I would like a pick that goes across these 2 storage types to be created on ONE TO."
I would think that you do not have one picking area across 2 storage types. You define picking areas per storage type. So if you give them the same name, that does not mean that they are the same picking areas. So the effect you describe is a split per storage type because they have different picking areas.
Best regards
Juergen -
Picking area-no values found?
hi all,
in material master-view plant/data stor1 input option 'Picking Area' is not showing any values though i defined warehouse number, storage type, storage sections and picking area using the path: SPRO>LE>WareHouse Management>Master Data>Define Picking Area.
Pls do suggest me on this.
regards,
chinta
Edited by: chinta on Feb 21, 2012 5:16 PMi did the same bro... but no use...
the values are displayed in 'warehouse management tab 1' but not in ' plant data stor 1' any how i resolved it by doing this here
SPRO>LE>Shipping>Picking>Lean WM>Define control parameters and number ranges f warehouse no>define control parameters and number ranges f. warehouse no
and
SPRO>LE>Shipping>Picking>Lean WM-->Control Plant/storage location/ware houe no assignment
thats it i got the result..
thank you bro.. for your help.
thanks and regards
chinta -
I have set up production supply to split TOs per picking area. Master data is OK, config is OK.
But it is not working. Is this setting ignored for production supply?
I have even debugged the process and the program finds the correct entry in T312B, with SPLKB field set to X. Yet, nothing happens.
Config was verified by another experienced consultant.
Any ideas?Read documentation on operation SETIN.
-
Picking Area not defined.
Dear Experts,
I had checked the configuration Setting on my system & I found that Picking Area is not defined.
So my query is why GR's,GI,Shipping is happening smoothly though picking area is undefined.
Thanks & Regards,
Olet MallaPicking Area is optional in SAP Warehouse management whereas You must define atleast one storage section for the storage type. It groups the storage bins along with Picing strategies.
It is not relevant for Inventory Management only relevant for warehouse picking. -
Album Picks are Driving Me Insane
Because I haven't upgraded from 3.2.4 or asked others for a workaround, I thought I post here before giving feedback.
I'm not sure when the application engineers decided that if stacked images are added to an album the stack pick should automatically become an album pick that must be manually removed even after choosing a new stack pick, but it wasn't always this way. Of that I'm sure.
This is driving me insane because I can't find a way to change the default, and I can't remove the album pick from multiple stacks simultaneously.
After I do the work to choose stack picks, I don't need the album to display a different image as the pick. In my workflow, this is a severe hinderance that costs me time and causes me to run the risk of overlooking acceptable images that I've already chosen to display as the pick. If I need to use the album pick feature, I can make that decision without any help from the application. The main thing that's kept me with Aperture is that I hate LR's DAM- especially the stack feature.
Please tell me that this has been addressed in 3.4. If this is the case, I might just find the time to update my huge library.
DLSI am still trying to wrap my head around this. I think we may be seeing different behavior. When I create a new Album from a selection in a Project that includes Stacks, the Album Pick is set, but it is always the same as the Stack Pick. Yes? This, to me, is what I would expect. (From a computational point-of-view, there is no difference between designating the Stack Pick as the Album Pick, or not designating it, when the rule is that if there is no Album Pick designated, use the Stack Pick.)
DLScreative wrote:
... at the very least, when I choose a new stack pick in the album, it should either replace the album pick or wipe it.
Why? The Album pick is a separate, Album-specific designation. The Album pick is set to the Stack Pick when the Album is created, and remains so until you change one or the other. You can change either in the Album. I don't see why changing the Stack Pick in the Album should remove or replace the Album Pick. If it's the Album Pick you want to change or remove, change it or remove it. If you want to change the Stack Pick, you can do this either in the Project or in the Album. But again, the Album Pick and the Stack Pick are independent once the Album is created.
From a practical point of view, you can put the Album Pick and Stack Pick icons next to each other on the Toolbar (this might be the default) and simply click each if you want to set an Image as both the Album Pick and the Stack Pick.
... I should also be able to select all stacks and remove all album picks at once.
Agreed. There should be a way to "reset" Album Picks to the current Stack Picks.
I spent a good three hours going through and clearing album picks- that I didn't choose to create- one at a time, and I'm still coming across some that I missed.
How did you remove them?
Here is one method:
- Set the filter to "Stack picks only". With an Album selected, this will show Album Picks where they exist.
- Select the first Image with with an Album Pick badge showing, and click "Stacks➞Remove Album Pick". Go to next Stack ("Stacks➞Next Stack" or whatever keyboard shortcut you have assigned). At this point, you can either check for the Album Pick badge, and then remove the Album Pick, or you can click "Stacks" and see whether the menu choice is "Remove Album Pick" or "Set Album Pick". Repeat for each Stack until you get to the last Stack in the Album.
If you want to make the current Stack Picks the Album Picks, you can do this by creating a new Album from the Project. Mark all Images in the Album (I use Flags), select the Project, select the marked Images, and create a new Album. New Albums created from Projects set the Album Pick to be the Stack Pick. Now you have two Albums containing the same Images. One has all the old Album Picks. In the other, the left-most Image in each Stack is both the Stack Pick and the Album Pick. The result is that you have redesignated the Album Picks to be the Stack Picks.
DLScreative wrote:
BTW: The shortcut to add or remove an album pick is command+shift+\ (I've come to know it all too well) It's also available in the Stacks Menu under Make/Clear Album Pick.
Yes. I was trying to differentiate between issuing commands (from a menu or the toolbar or a keyboard shortcut) and effecting a result by moving Images. Afaik, Album-Pick-making must be done by command. Stack-Pick-making can be done by moving an Image to the left-most position in a Stack.
I'm still thinking through your workflow. That this presents a rock in your stream means something isn't right. -
Hi Friends,
I have made following configuration setting for Transfer Order split for Picking area
In profile for Transfer Order split, I made Tick mark for TO split for Picking area, Set sort Sequense as 2 and set sort sequnce as Storage tyep and Material and Bin No.
Create Storage Bin Structure with Differnet Picking area and 2 different materials available in Differnet Pick area.
When I creat sale order, Delviery. When I cteate TO, System creating Single TO for Delivery. It is not Spliting 2 TO based on Pick area. what setting need to be done to split TO based on Pick area. Please confirm.
Thanks
MadhavanHi,
you should assign Profile for transfer order split in IMG: Warehouse Management>Activities>Transfers>Processing Performance Data / TO Split>Control for Performance Data Processing / Define TO Split-->Performance data control
Andrzej -
Stack picks are lost when duplicating a book - any ideas?
Hi everyone,
I've noticed that when I duplicate a book in Aperture 2, my "picked" image settings/choices from each stack are lost and i have to go back and re-pick the images I want to use. With the 100 page books this becomes very time consuming and annoying - is there anyway around this so that duplicate book means exactly that (not duplicate-most-of-the-book-but-not-the-important-bits)
The only workaround I've found so far is to extract the versions I want to use and then delete the old stacks - which works but is still a chunk of time to have to spend.I've discovered that the solution to this problem is to pull the "picked" image out of the stack, and then delete the stack (to keep the album tidy and straightforward). That way there are no options for Aperture to revert to when duplicating a book/light table.
-
People picker are not displaying all the users from the existing Synchronization Connections
Hello, I need help.
I have two domains, an old domain and a new domain that were are migrating to.
I have 2 connections for Users Synchronizations, one to the old domain and one to the new domain.
Here is what is happening: when I open people picker from any of the web applications only the users that existed in the old domain are showing and not the new users that are been added to the new domain. Basically people picker is displaying old data/users.
What can I do?The People Picker doesn't leverage UPA Sync Connections. Is there a one way or two way trust set up between the domains? If it is one way (where the old trusts the new), then you need to leverage the peoplepicker-searchadforests property: http://technet.microsoft.com/en-us/library/cc263460(v=office.12).aspx.
You also need to make sure your SharePoint servers have port access to the Domain Controllers in the new domain: https://peoplepicker.codeplex.com.
Trevor Seward
Follow or contact me at...
  
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs. -
Partial Pick Confirming Sales Order
Hi Folks,
I have a requirement where I have to Pick Confirm and Ship confirm Sales Order through API.
1. When the quantites to be picked are same as quantity ordered the code seems to work just fine.
But suppose in my example my quantity in SO line is 50 and I want to partially Ship confirm the lines lets say 20 quantites.
then which API i need to use?
The approach I am following is while pick confirming I am passing 20 quantites only and the ship confirming it.
I researched and found that we can use the following API to update shipping attributes 'WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes' but when I run it (I tried before and after Pick confirm) the API runs fine but no changes are getting affected and the code Pick confirms all the quantity.
Could some please help me with this.
Please find the codes for pick confirm and updating shipping attributes
Pick confirm code
DECLARE
lv_order_num number := 700145812;
vMoveOrderLineId NUMBER;
p_pick_conf_qty NUMBER;
pStatus VARCHAR2(100);
pMsgData VARCHAR2(4000);
v_movehdr_rec INV_MOVE_ORDER_PUB.TROHDR_REC_TYPE;
v_movehdr_val_rec INV_MOVE_ORDER_PUB.TROHDR_VAL_REC_TYPE;
v_moveln_tbl INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_p INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_zero_tbl INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_zero_tbl_p INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_d INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_o INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_val_tbl INV_MOVE_ORDER_PUB.TROLIN_VAL_TBL_TYPE;
v_mold_tbl INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
v_mold_tbl_p INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
l_mold_tbl INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
l_moveln_tbl INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
l_trolin_rec INV_MOVE_ORDER_PUB.TROLIN_REC_TYPE;
l_trolin_tbl INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
l_return_status VARCHAR2(240);
l_msg_count NUMBER;
l_msg_data VARCHAR2(2000);
l_move_hdr_id NUMBER;
l_move_order_no NUMBER := 0;
v_return_values VARCHAR2(2000) := FND_API.G_TRUE;
v_move_hdr_rec INV_MOVE_ORDER_PUB.TROHDR_REC_TYPE;
v_move_hdr_val_rec INV_MOVE_ORDER_PUB.TROHDR_VAL_REC_TYPE;
v_api_pick_confirm NUMBER;
cv_fail VARCHAR2(100) := 'Fail';
cv_success VARCHAR2(100) := 'Success';
g_user_id number;
g_resp_id number;
g_resp_appl_id number;
p_user_name varchar2(100) := 'SYSADMIN';
p_resp_name varchar2(100) := 'Order Management Super User';
p_mo_apps varchar2(100) := 'ONT';
CURSOR c_mmtt_recs(vMoveOrderLineId NUMBER) IS
SELECT transaction_header_id,
transaction_temp_id,
source_code,
source_line_id,
transaction_mode,
lock_flag,
last_update_date,
last_updated_by,
creation_date,
created_by,
last_update_login,
request_id,
program_application_id,
program_id,
program_update_date,
inventory_item_id,
revision,
organization_id,
subinventory_code,
locator_id,
transaction_quantity,
primary_quantity,
transaction_uom,
transaction_cost,
transaction_type_id,
transaction_action_id,
transaction_source_type_id,
transaction_source_id,
transaction_source_name,
transaction_date,
acct_period_id,
distribution_account_id,
transaction_reference,
requisition_line_id,
requisition_distribution_id,
reason_id,
lot_number,
lot_expiration_date,
serial_number,
receiving_document,
demand_id,
rcv_transaction_id,
move_transaction_id,
completion_transaction_id,
wip_entity_type,
schedule_id,
repetitive_line_id,
employee_code,
primary_switch,
schedule_update_code,
setup_teardown_code,
item_ordering,
negative_req_flag,
operation_seq_num,
picking_line_id,
trx_source_line_id,
trx_source_delivery_id,
physical_adjustment_id,
cycle_count_id,
rma_line_id,
customer_ship_id,
currency_code,
currency_conversion_rate,
currency_conversion_type,
currency_conversion_date,
ussgl_transaction_code,
vendor_lot_number,
encumbrance_account,
encumbrance_amount,
ship_to_location,
shipment_number,
transfer_cost,
transportation_cost,
transportation_account,
freight_code,
containers,
waybill_airbill,
expected_arrival_date,
transfer_subinventory,
transfer_organization,
transfer_to_location,
new_average_cost,
value_change,
percentage_change,
material_allocation_temp_id,
demand_source_header_id,
demand_source_line,
demand_source_delivery,
item_segments,
item_description,
item_trx_enabled_flag,
item_location_control_code,
item_restrict_subinv_code,
item_restrict_locators_code,
item_revision_qty_control_code,
item_primary_uom_code,
item_uom_class,
item_shelf_life_code,
item_shelf_life_days,
item_lot_control_code,
item_serial_control_code,
item_inventory_asset_flag,
allowed_units_lookup_code,
department_id,
department_code,
wip_supply_type,
supply_subinventory,
supply_locator_id,
valid_subinventory_flag,
valid_locator_flag,
locator_segments,
current_locator_control_code,
number_of_lots_entered,
wip_commit_flag,
next_lot_number,
lot_alpha_prefix,
next_serial_number,
serial_alpha_prefix,
shippable_flag,
posting_flag,
required_flag,
process_flag,
error_code,
error_explanation,
attribute_category,
attribute1,
attribute2,
attribute3,
attribute4,
attribute5,
attribute6,
attribute7,
attribute8,
attribute9,
attribute10,
attribute11,
attribute12,
attribute13,
attribute14,
attribute15,
movement_id,
reservation_quantity,
shipped_quantity,
transaction_line_number,
task_id,
to_task_id,
source_task_id,
project_id,
source_project_id,
pa_expenditure_org_id,
to_project_id,
expenditure_type,
final_completion_flag,
transfer_percentage,
transaction_sequence_id,
material_account,
material_overhead_account,
resource_account,
outside_processing_account,
overhead_account,
flow_schedule,
cost_group_id,
demand_class,
qa_collection_id,
kanban_card_id,
overcompletion_transaction_id,
overcompletion_primary_qty,
overcompletion_transaction_qty,
end_item_unit_number,
scheduled_payback_date,
line_type_code,
parent_transaction_temp_id,
put_away_strategy_id,
put_away_rule_id,
pick_strategy_id,
pick_rule_id,
common_bom_seq_id,
common_routing_seq_id,
cost_type_id,
org_cost_group_id,
move_order_line_id,
task_group_id,
pick_slip_number,
reservation_id,
transaction_status,
transfer_cost_group_id,
lpn_id,
transfer_lpn_id,
pick_slip_date,
content_lpn_id
FROM MTL_MATERIAL_TRANSACTIONS_TEMP
WHERE move_order_line_id = vMoveOrderLineId;
l_moveln_fidx NUMBER;
l_moveln_lidx NUMBER;
n_mvln_cntr NUMBER;
l_Index NUMBER := 1;
v_records_in_mmtt NUMBER := 0;
REC C_MMTT_RECS%ROWTYPE;
BEGIN
select user_id
into g_user_id
from fnd_user
where user_name = p_user_name;
select responsibility_id, application_id
into g_resp_id, g_resp_appl_id
from apps.fnd_responsibility_vl
where responsibility_name = p_resp_name;
Apps.FND_Global.Apps_Initialize(g_user_id, g_resp_id, g_resp_appl_id);
MO_GLOBAL.INIT(p_mo_apps);
for mol in (select wda.delivery_id,
wda.delivery_detail_id,
wda.parent_delivery_detail_id,
wdd.source_code,
wdd.inventory_item_id,
wdd.organization_id,
wdd.ship_from_location_id,
wdd.ship_to_location_id,
wdd.requested_quantity,
wdd.requested_quantity_uom,
wdd.move_order_line_id,
wdd.org_id,
mtrl.quantity,
mtrl.quantity_delivered
from wsh_delivery_details wdd,
wsh_delivery_assignments wda,
oe_order_lines_all ol,
oe_order_headers_all oh,
mtl_txn_request_lines mtrl,
mtl_txn_request_headers mtrh
where wdd.source_line_id = ol.line_id
and wdd.delivery_detail_id = wda.delivery_detail_id
and ol.header_id = oh.header_id
and wdd.move_order_line_id = mtrl.line_id(+)
and mtrl.header_id = mtrh.header_id(+)
and oh.order_number = lv_order_num) loop
vMoveOrderLineId := mol.move_order_line_id;
p_pick_conf_qty := mol.quantity - nvl(mol.quantity_delivered,0);
SELECT COUNT(move_order_line_id)
INTO v_records_in_mmtt
FROM MTL_MATERIAL_TRANSACTIONS_TEMP
WHERE move_order_line_id = vMoveOrderLineId;
IF v_records_in_mmtt > 1 THEN
pStatus := cv_fail;
pMsgData := 'Wrong number of records in MMTT for the MOVE_ORDER_LINE_ID : ' ||
vMoveOrderLineId;
DBMS_OUTPUT.PUT_LINE('Multiple records in MMTT for move_order_line_id = ' ||
vMoveOrderLineId);
v_api_pick_confirm := 0;
GOTO end_of_pkcnf;
ELSIF v_records_in_mmtt = 0 THEN
--means that the delivery is already pick confirmed
pStatus := cv_success;
DBMS_OUTPUT.PUT_LINE('No records in MMTT for move_order_line_id = ' ||
vMoveOrderLineId ||
' hence it is already pick confirmed');
v_api_pick_confirm := 0;
GOTO end_of_pkcnf;
END IF;
SELECT mtrh.header_id, mtrh.request_number
INTO l_move_hdr_id, l_move_order_no
FROM mtl_txn_request_headers mtrh, mtl_txn_request_lines mtrl
WHERE mtrh.header_id = mtrl.header_id
AND mtrl.line_id = vMoveOrderLineId;
DBMS_OUTPUT.PUT_LINE('Obtained MTRH.HEADER_ID = ' || l_move_hdr_id ||
' MTRH.REQUEST_NUMBER = ' || l_move_order_no ||
' for move_order_line_id = ' || vMoveOrderLineId);
INV_MOVE_ORDER_PUB.GET_MOVE_ORDER(p_api_version_number => 1.0,
p_init_msg_list => FND_API.G_FALSE,
p_return_values => v_return_values,
x_return_status => l_return_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data,
p_header_id => l_move_hdr_id,
p_header => l_move_order_no,
x_trohdr_rec => v_move_hdr_rec,
x_trohdr_val_rec => v_move_hdr_val_rec,
x_trolin_tbl => v_moveln_tbl,
x_trolin_val_tbl => v_moveln_val_tbl);
COMMIT;
DBMS_OUTPUT.PUT_LINE('Return status of INV_MOVE_ORDER_PUB.GET_MOVE_ORDER = ' ||
l_return_status);
IF l_return_status != FND_API.G_RET_STS_SUCCESS THEN
pStatus := cv_fail;
pMsgData := 'Failed to get move order inv_move_order_pub.get_move_order for MOVE_ORDER_LINE_ID : ' ||
vMoveOrderLineId;
GOTO end_of_pkcnf;
END IF;
OPEN c_mmtt_recs(vMoveOrderLineId);
FETCH c_mmtt_recs
INTO rec;
CLOSE c_mmtt_recs;
v_mold_tbl(1).transaction_header_id := rec.transaction_header_id;
v_mold_tbl(1).transaction_temp_id := rec.transaction_temp_id;
v_mold_tbl(1).source_code := rec.source_code;
v_mold_tbl(1).source_line_id := rec.source_line_id;
v_mold_tbl(1).transaction_mode := rec.transaction_mode;
v_mold_tbl(1).lock_flag := rec.lock_flag;
v_mold_tbl(1).last_update_date := rec.last_update_date;
v_mold_tbl(1).last_updated_by := rec.last_updated_by;
v_mold_tbl(1).creation_date := rec.creation_date;
v_mold_tbl(1).created_by := rec.created_by;
v_mold_tbl(1).last_update_login := rec.last_update_login;
v_mold_tbl(1).request_id := rec.request_id;
v_mold_tbl(1).program_application_id := rec.program_application_id;
v_mold_tbl(1).program_id := rec.program_id;
v_mold_tbl(1).program_update_date := rec.program_update_date;
v_mold_tbl(1).inventory_item_id := rec.inventory_item_id;
v_mold_tbl(1).revision := rec.revision;
v_mold_tbl(1).organization_id := rec.organization_id;
v_mold_tbl(1).subinventory_code := rec.subinventory_code;
v_mold_tbl(1).locator_id := rec.locator_id;
v_mold_tbl(1).transaction_quantity := rec.transaction_quantity;
v_mold_tbl(1).primary_quantity := rec.primary_quantity;
v_mold_tbl(1).transaction_uom := rec.transaction_uom;
v_mold_tbl(1).transaction_cost := rec.transaction_cost;
v_mold_tbl(1).transaction_type_id := rec.transaction_type_id;
v_mold_tbl(1).transaction_action_id := rec.transaction_action_id;
v_mold_tbl(1).transaction_source_type_id := rec.transaction_source_type_id;
v_mold_tbl(1).transaction_source_id := rec.transaction_source_id;
v_mold_tbl(1).transaction_source_name := rec.transaction_source_name;
v_mold_tbl(1).transaction_date := rec.transaction_date;
v_mold_tbl(1).acct_period_id := rec.acct_period_id;
v_mold_tbl(1).distribution_account_id := rec.distribution_account_id;
v_mold_tbl(1).transaction_reference := rec.transaction_reference;
v_mold_tbl(1).requisition_line_id := rec.requisition_line_id;
v_mold_tbl(1).requisition_distribution_id := rec.requisition_distribution_id;
v_mold_tbl(1).reason_id := rec.reason_id;
v_mold_tbl(1).lot_number := rec.lot_number;
v_mold_tbl(1).lot_expiration_date := rec.lot_expiration_date;
v_mold_tbl(1).serial_number := rec.serial_number;
v_mold_tbl(1).receiving_document := rec.receiving_document;
v_mold_tbl(1).demand_id := rec.demand_id;
v_mold_tbl(1).rcv_transaction_id := rec.rcv_transaction_id;
v_mold_tbl(1).move_transaction_id := rec.move_transaction_id;
v_mold_tbl(1).completion_transaction_id := rec.completion_transaction_id;
v_mold_tbl(1).wip_entity_type := rec.wip_entity_type;
v_mold_tbl(1).schedule_id := rec.schedule_id;
v_mold_tbl(1).repetitive_line_id := rec.repetitive_line_id;
v_mold_tbl(1).employee_code := rec.employee_code;
v_mold_tbl(1).primary_switch := rec.primary_switch;
v_mold_tbl(1).schedule_update_code := rec.schedule_update_code;
v_mold_tbl(1).setup_teardown_code := rec.setup_teardown_code;
v_mold_tbl(1).item_ordering := rec.item_ordering;
v_mold_tbl(1).negative_req_flag := rec.negative_req_flag;
v_mold_tbl(1).operation_seq_num := rec.operation_seq_num;
v_mold_tbl(1).picking_line_id := rec.picking_line_id;
v_mold_tbl(1).trx_source_line_id := rec.trx_source_line_id;
v_mold_tbl(1).trx_source_delivery_id := rec.trx_source_delivery_id;
v_mold_tbl(1).physical_adjustment_id := rec.physical_adjustment_id;
v_mold_tbl(1).cycle_count_id := rec.cycle_count_id;
v_mold_tbl(1).rma_line_id := rec.rma_line_id;
v_mold_tbl(1).customer_ship_id := rec.customer_ship_id;
v_mold_tbl(1).currency_code := rec.currency_code;
v_mold_tbl(1).currency_conversion_rate := rec.currency_conversion_rate;
v_mold_tbl(1).currency_conversion_type := rec.currency_conversion_type;
v_mold_tbl(1).currency_conversion_date := rec.currency_conversion_date;
v_mold_tbl(1).ussgl_transaction_code := rec.ussgl_transaction_code;
v_mold_tbl(1).vendor_lot_number := rec.vendor_lot_number;
v_mold_tbl(1).encumbrance_account := rec.encumbrance_account;
v_mold_tbl(1).encumbrance_amount := rec.encumbrance_amount;
v_mold_tbl(1).ship_to_location := rec.ship_to_location;
v_mold_tbl(1).shipment_number := rec.shipment_number;
v_mold_tbl(1).transfer_cost := rec.transfer_cost;
v_mold_tbl(1).transportation_cost := rec.transportation_cost;
v_mold_tbl(1).transportation_account := rec.transportation_account;
v_mold_tbl(1).freight_code := rec.freight_code;
v_mold_tbl(1).containers := rec.containers;
v_mold_tbl(1).waybill_airbill := rec.waybill_airbill;
v_mold_tbl(1).expected_arrival_date := rec.expected_arrival_date;
v_mold_tbl(1).transfer_subinventory := rec.transfer_subinventory;
v_mold_tbl(1).transfer_organization := rec.transfer_organization;
v_mold_tbl(1).transfer_to_location := rec.transfer_to_location;
v_mold_tbl(1).new_average_cost := rec.new_average_cost;
v_mold_tbl(1).value_change := rec.value_change;
v_mold_tbl(1).percentage_change := rec.percentage_change;
v_mold_tbl(1).material_allocation_temp_id := rec.material_allocation_temp_id;
v_mold_tbl(1).demand_source_header_id := rec.demand_source_header_id;
v_mold_tbl(1).demand_source_line := rec.demand_source_line;
v_mold_tbl(1).demand_source_delivery := rec.demand_source_delivery;
v_mold_tbl(1).item_segments := rec.item_segments;
v_mold_tbl(1).item_description := rec.item_description;
v_mold_tbl(1).item_trx_enabled_flag := rec.item_trx_enabled_flag;
v_mold_tbl(1).item_location_control_code := rec.item_location_control_code;
v_mold_tbl(1).item_restrict_subinv_code := rec.item_restrict_subinv_code;
v_mold_tbl(1).item_restrict_locators_code := rec.item_restrict_locators_code;
v_mold_tbl(1).item_revision_qty_control_code := rec.item_revision_qty_control_code;
v_mold_tbl(1).item_primary_uom_code := rec.item_primary_uom_code;
v_mold_tbl(1).item_uom_class := rec.item_uom_class;
v_mold_tbl(1).item_shelf_life_code := rec.item_shelf_life_code;
v_mold_tbl(1).item_shelf_life_days := rec.item_shelf_life_days;
v_mold_tbl(1).item_lot_control_code := rec.item_lot_control_code;
v_mold_tbl(1).item_serial_control_code := rec.item_serial_control_code;
v_mold_tbl(1).item_inventory_asset_flag := rec.item_inventory_asset_flag;
v_mold_tbl(1).allowed_units_lookup_code := rec.allowed_units_lookup_code;
v_mold_tbl(1).department_id := rec.department_id;
v_mold_tbl(1).department_code := rec.department_code;
v_mold_tbl(1).wip_supply_type := rec.wip_supply_type;
v_mold_tbl(1).supply_subinventory := rec.supply_subinventory;
v_mold_tbl(1).supply_locator_id := rec.supply_locator_id;
v_mold_tbl(1).valid_subinventory_flag := rec.valid_subinventory_flag;
v_mold_tbl(1).valid_locator_flag := rec.valid_locator_flag;
v_mold_tbl(1).locator_segments := rec.locator_segments;
v_mold_tbl(1).current_locator_control_code := rec.current_locator_control_code;
v_mold_tbl(1).number_of_lots_entered := rec.number_of_lots_entered;
v_mold_tbl(1).wip_commit_flag := rec.wip_commit_flag;
v_mold_tbl(1).next_lot_number := rec.next_lot_number;
v_mold_tbl(1).lot_alpha_prefix := rec.lot_alpha_prefix;
v_mold_tbl(1).next_serial_number := rec.next_serial_number;
v_mold_tbl(1).serial_alpha_prefix := rec.serial_alpha_prefix;
v_mold_tbl(1).shippable_flag := rec.shippable_flag;
v_mold_tbl(1).posting_flag := rec.posting_flag;
v_mold_tbl(1).required_flag := rec.required_flag;
v_mold_tbl(1).process_flag := rec.process_flag;
v_mold_tbl(1).error_code := rec.error_code;
v_mold_tbl(1).error_explanation := rec.error_explanation;
v_mold_tbl(1).attribute_category := rec.attribute_category;
v_mold_tbl(1).attribute1 := rec.attribute1;
v_mold_tbl(1).attribute2 := rec.attribute2;
v_mold_tbl(1).attribute3 := rec.attribute3;
v_mold_tbl(1).attribute4 := rec.attribute4;
v_mold_tbl(1).attribute5 := rec.attribute5;
v_mold_tbl(1).attribute6 := rec.attribute6;
v_mold_tbl(1).attribute7 := rec.attribute7;
v_mold_tbl(1).attribute8 := rec.attribute8;
v_mold_tbl(1).attribute9 := rec.attribute9;
v_mold_tbl(1).attribute10 := rec.attribute10;
v_mold_tbl(1).attribute11 := rec.attribute11;
v_mold_tbl(1).attribute12 := rec.attribute12;
v_mold_tbl(1).attribute13 := rec.attribute13;
v_mold_tbl(1).attribute14 := rec.attribute14;
v_mold_tbl(1).attribute15 := rec.attribute15;
v_mold_tbl(1).movement_id := rec.movement_id;
v_mold_tbl(1).reservation_quantity := rec.reservation_quantity;
v_mold_tbl(1).shipped_quantity := rec.shipped_quantity;
v_mold_tbl(1).transaction_line_number := rec.transaction_line_number;
v_mold_tbl(1).task_id := rec.task_id;
v_mold_tbl(1).to_task_id := rec.to_task_id;
v_mold_tbl(1).source_task_id := rec.source_task_id;
v_mold_tbl(1).project_id := rec.project_id;
v_mold_tbl(1).source_project_id := rec.source_project_id;
v_mold_tbl(1).pa_expenditure_org_id := rec.pa_expenditure_org_id;
v_mold_tbl(1).to_project_id := rec.to_project_id;
v_mold_tbl(1).expenditure_type := rec.expenditure_type;
v_mold_tbl(1).final_completion_flag := rec.final_completion_flag;
v_mold_tbl(1).transfer_percentage := rec.transfer_percentage;
v_mold_tbl(1).transaction_sequence_id := rec.transaction_sequence_id;
v_mold_tbl(1).material_account := rec.material_account;
v_mold_tbl(1).material_overhead_account := rec.material_overhead_account;
v_mold_tbl(1).resource_account := rec.resource_account;
v_mold_tbl(1).outside_processing_account := rec.outside_processing_account;
v_mold_tbl(1).overhead_account := rec.overhead_account;
v_mold_tbl(1).flow_schedule := rec.flow_schedule;
v_mold_tbl(1).cost_group_id := rec.cost_group_id;
v_mold_tbl(1).demand_class := rec.demand_class;
v_mold_tbl(1).qa_collection_id := rec.qa_collection_id;
v_mold_tbl(1).kanban_card_id := rec.kanban_card_id;
v_mold_tbl(1).overcompletion_transaction_id := rec.overcompletion_transaction_id;
v_mold_tbl(1).overcompletion_primary_qty := rec.overcompletion_primary_qty;
v_mold_tbl(1).overcompletion_transaction_qty := rec.overcompletion_transaction_qty;
v_mold_tbl(1).end_item_unit_number := rec.end_item_unit_number;
v_mold_tbl(1).scheduled_payback_date := rec.scheduled_payback_date;
v_mold_tbl(1).line_type_code := rec.line_type_code;
v_mold_tbl(1).parent_transaction_temp_id := rec.parent_transaction_temp_id;
v_mold_tbl(1).put_away_strategy_id := rec.put_away_strategy_id;
v_mold_tbl(1).put_away_rule_id := rec.put_away_rule_id;
v_mold_tbl(1).pick_strategy_id := rec.pick_strategy_id;
v_mold_tbl(1).pick_rule_id := rec.pick_rule_id;
v_mold_tbl(1).common_bom_seq_id := rec.common_bom_seq_id;
v_mold_tbl(1).common_routing_seq_id := rec.common_routing_seq_id;
v_mold_tbl(1).cost_type_id := rec.cost_type_id;
v_mold_tbl(1).org_cost_group_id := rec.org_cost_group_id;
v_mold_tbl(1).move_order_line_id := rec.move_order_line_id;
v_mold_tbl(1).task_group_id := rec.task_group_id;
v_mold_tbl(1).pick_slip_number := rec.pick_slip_number;
v_mold_tbl(1).reservation_id := rec.reservation_id;
v_mold_tbl(1).transaction_status := rec.transaction_status;
v_mold_tbl(1).transfer_cost_group_id := rec.transfer_cost_group_id;
v_mold_tbl(1).lpn_id := rec.lpn_id;
v_mold_tbl(1).transfer_lpn_id := rec.transfer_lpn_id;
v_mold_tbl(1).pick_slip_date := rec.pick_slip_date;
v_mold_tbl(1).content_lpn_id := rec.content_lpn_id;
v_mold_tbl(1).transaction_quantity := p_pick_conf_qty;
v_mold_tbl(1).primary_quantity := p_pick_conf_qty;
v_mold_tbl(1).shipped_quantity := p_pick_conf_qty;
INV_PICK_WAVE_PICK_CONFIRM_PUB.PICK_CONFIRM(p_api_version_number => 1.0,
p_init_msg_list => FND_API.G_FALSE,
p_commit => FND_API.G_FALSE,
x_return_status => l_return_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data,
p_move_order_type => 3 -- PickWave - Order
p_transaction_mode => 1 -- 1:On-Line, 2:Concurrent, 3:Background
p_trolin_tbl => v_moveln_tbl_d,
p_mold_tbl => v_mold_tbl,
x_mmtt_tbl => v_mold_tbl,
x_trolin_tbl => v_moveln_tbl_o,
p_transaction_date => SYSDATE);
COMMIT;
DBMS_OUTPUT.PUT_LINE('Return status of INV_PICK_WAVE_PICK_CONFIRM_PUB.PICK_CONFIRM = ' ||
l_return_status);
IF l_return_status != FND_API.G_RET_STS_SUCCESS THEN
pStatus := cv_fail;
pMsgData := 'Failed to pick confirm move order inv_pick_wave_pick_confirm_pub.pick_confirm for MOVE_ORDER_LINE_ID : ' ||
vMoveOrderLineId;
GOTO end_of_pkcnf;
END IF;
v_api_pick_confirm := 1;
dbms_output.put_line('Status of the Pick Confirm is : ' ||
l_return_status);
<<end_of_pkcnf>>
NULL;
end loop;
END;
Updating Shipping attributes
DECLARE
--Standard Parameters.
p_api_version NUMBER;
init_msg_list VARCHAR2(30);
p_commit VARCHAR2(30);
--Parameters for WSH_DELIVERY_DETAILS_PUB.update_shipping_attributes.
source_code VARCHAR2(15);
changed_attributes WSH_DELIVERY_DETAILS_PUB.ChangedAttributeTabType;
--out parameters
x_return_status VARCHAR2(10);
x_msg_count NUMBER;
x_msg_data VARCHAR2(2000);
x_msg_details VARCHAR2(3000);
x_msg_summary VARCHAR2(3000);
-- Handle exceptions
vApiErrorException EXCEPTION;
BEGIN
-- Initialize return status
x_return_status := WSH_UTIL_CORE.G_RET_STS_SUCCESS;
-- Call this procedure to initialize applications parameters
FND_GLOBAL.APPS_INITIALIZE(user_id => 0,
resp_id => 21623,
resp_appl_id => 660);
source_code := 'OE';
changed_attributes(1).delivery_detail_id := 9317811; -- delivery_detail_id
changed_attributes(1).shipped_quantity := 0; -- quantity to update
changed_attributes(1).cycle_count_quantity := 30;
--Call to WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes.
WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes(p_api_version_number => 1.0,
p_init_msg_list => init_msg_list,
p_commit => p_commit,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_changed_attributes => changed_attributes,
p_source_code => source_code);
commit;
IF (x_return_status <> WSH_UTIL_CORE.G_RET_STS_SUCCESS) THEN
RAISE vApiErrorException;
ELSE
dbms_output.put_line('The shipped quantity is updated with ' ||
changed_attributes(1)
.shipped_quantity || ' for the delivery detail ' ||
changed_attributes(1).delivery_detail_id);
END IF;
EXCEPTION
WHEN vApiErrorException THEN
WSH_UTIL_CORE.get_messages('Y',
x_msg_summary,
x_msg_details,
x_msg_count);
IF x_msg_count > 1 THEN
x_msg_data := x_msg_summary || x_msg_details;
DBMS_OUTPUT.PUT_LINE('Message Data : ' || x_msg_data);
ELSE
x_msg_data := x_msg_summary;
DBMS_OUTPUT.PUT_LINE('Message Data : ' || x_msg_data);
END IF;
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('Unexpected Error: ' || SQLERRM);
END;
ThanksHi,
Goto VTFL.Select you valid combination.
Click on item.Select yout item category there.Goto details.
Select the Pos/neg quantity field as "+".
Maintain the billing quantity as "A".
Maintain VBRK/VBRP as "001".
Save.
Goto VOV7 and select your item category.Details.
Select completion rule as "B" and billing relevance as "F".
Save.
Pls go through the follwing threads that are posted by me earlier.
[Invoice split|Re: Invoice split]
[Splitiing of invoice|Re: Invoice split]
Regards,
Krishna. -
Set item categaries of sales order is not relevant for picking
dear friends:
when i created the outbound delivery and must maintain the picking quantity of materails.i change the configration of system so that not nessesary maintain the picking quantity. set item categaries of sales order is not relevant for picking via t_code:vlop,what it effect .help me analyze it .
best regards.Hello,
In TA :OVLP set/reset the indicator according to your requirement.
In the case of outbound deliveries, only the delivery items that are relevant for picking are transferred to the Warehouse Management (WM) component. Certain items such as text items or service items (consulting activities) are not relevant for picking.(in those cases uncheck the box)
In the case of inbound deliveries, this indicator controls whether the item is relevant for putaway.
This indicator must be set in order for the item to be included in a Warehouse Management transfer order and then put away.
Regards,
Nisha
@award pts if helpful.
Maybe you are looking for
-
It's possible to make Hierarchical Tree from multiple tables ?
the famous example for Hierarchical Tree is about employee_id and manager_id field in employees table ............ so I was wondering it's possible to make[b] Hierarchical Tree from multiple tables ? and How ?? if the answer associate with example th
-
Cannot hear audio for subclips playback in source monitor
Hi, My editor has merged a bunch of video and multichannel audio on his computer and created merged clips and sub clips for me to look at. Now it's my turn to make selects from the merged subclips, but when I open the project on my computer the subcl
-
I'm getting a very large number of Document Fetch Failures (the majority are 500 errors) when crawling our French site. We are not having any problems with crawling our English sites which are similar to the French site (just the language difference)
-
not seen by pc on itunes with usb cable. holding sleep/wake button does nothing. only button that works is the on/off button. all I get is the apple screen WTH!
-
Trying to find pl/sql that will show you what script is running
I'm looking for a way, inside sql, to find the name of an executing/running script from inside the script itself. For example, I have a master script called run.sql with these contents: @@a.sql @@b.sql exit A.sql has these contents: spool a.log selec