Pick priority In order entry
Hi,
Where to look for <b>pick priority</b> field in transaction VA01?
Thanks
Hi
Check the field
<b>VBAP-LPRIO</b>
<b>Reward points for useful Answers</b>
Regards
Anji
Similar Messages
-
Order Entry Without Pick Release And Ship Confirm
I would like to create a sales order in Order Entry (Release 11), but due to some integration requirement, I do not want to go through the Pick Release And Ship Confirmation process but then I would like to go through the AR interface and Autoinvoice process. Are there some interface tables that I can update and processes that I can submit in the background to simulate the Pick Release and Ship Confirm processes. Your advice is much appreciate. Thank you and God bless you.
Speaking as a functional person you can create an Invoice Only cycle, and it will not need to go through the Inventory module, requesting the Pick Release and Ship Confirmation. <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by williamson ():
I would like to create a sales order in Order Entry (Release 11), but due to some integration requirement, I do not want to go through the Pick Release And Ship Confirmation process but then I would like to go through the AR interface and Autoinvoice process. Are there some interface tables that I can update and processes that I can submit in the background to simulate the Pick Release and Ship Confirm processes. Your advice is much appreciate. Thank you and God bless you. <HR></BLOCKQUOTE>
null -
Pick Ticket Printing when Pressing Add Button in Order ENtry
Simple question ...
All I need to do is when I press the Add button when entering and Order is automatically print a Pick Ticket
Not an Order and I do not want to Prompt the Order Entry person if they Want to print a Pick Ticket or an Order or Both.
How do I get Pick Ticket and ONLY the Pick Ticket to print without the prompts? I know I can make an Order look like a Pick Ticket and and go to Print Preferences and Un Check Pick tickets, but I am trying to avoid creating a new form, and whe might want to print both forms again in the future. I am sure it is something simple
Thanks in advance!!!The options window where you Choose Pick ticket / Sales Order cannot be avoided. By system design this window will appear when ever you have Print Picking sheet checked
-
"Demo: Order Entry Demo Application" failed to show up.
I downloaded Wrokshop 8.1 JumpStart kit. and started Exercise#1. However, after
copying demo-orderentry.zip to the target folder as directed, a File_New_Application
did not see "Demo: Order Empty Demo Application" in the right-side pane.
Any clue?Hi, this did not work for me as well. I did the following: took template.xml file from demo-orderentry.zip and compared it to other template.xml files in other template archives (in the C:\bea\weblogic81\workshop\templates folder). According to the differences, I edited this file a bit, updated the demo-orderentry.zip archive and this worked out.
The template.xml looks now like this:
<template-definition>
<project-template id="oe_demo_project"
extends="default"
type="urn:com-bea-ide:project.type:WebApp">
<content type="archive" destination="project" source="default-project.zip" overwrite="true"/>
</project-template>
<application-template id="oe_demo_app">
<display
location="newdialog"
label="Demo: Order Entry Demo Application"
description="Creates a new application containing components for the Order Entry demo."
priority="2"
categories="Demos"/>
<project-template-ref default-name="Schemas" type="urn:com-bea-ide:xbean" template="default"/>
<project-template-ref default-name="AvitekDemoApp" type="urn:com-bea-ide:project.type:WebApp" template="oe_demo_project"/>
</application-template>
</template-definition> -
hi everybody
can anybody tell me if we give at MANUAL ENTRIES field as AUTOMATIC ENTRIES HAS PRIORITY in condition type maintainence and give tick mark on MANUAL ENTRIES at pricing procedure which will system concider FIRST while pricing?Hi,
In pricing procedure (V/08) if you give the condition type as manual that will be entered manually during the sales order processing... normally there will not be access seq and condition records for manual conditions
the manual entries field in V/06 is applicable for automatically determined conditions. its not applicable for above mentined manual conditions. this option is for priority between manual and automatic entries for conditions which assigned with access seq and condition recs...
' ' No limitations
A Free
B Automatic entry has priority
C Manual entry has priority
D Not possible to process manually
Hope you clear now...
Reward if helps
Muthu -
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. -
Accounting for discounts given at the order entry level
Hi,
I'm Anil Wadhwa and I'm working for Amtrex Hitachi Appliances Ltd., Ahmedabad, India. we have implemented Oracle applications 11i and I'm part of the Order to Cash cycle specifically handling the OM Module.
Initially I had the problem of using the discount feature available in Oracle Advanced Pricing and now I have got the solution for the problem.The problem I was trying to explore a feature whereby I was setting up a qualifier where I'm defining the Customer Class as 'DLR' which would be eligible for discount say @10%.
I subsequently set up a modifier where I defined a modifier type discount @10% and attached it with predefined qualifier at both the header and line level.
When I was trying the order entry the price which was defaulting from the attached price list was not getting reduced by 10%.
Now this problem has been solved by giving a request from the 'Oracle Pricing Manager' called as Build Sourcing Rule.
Now I want to know is there any way of accounting the discount given.
Say my list price is 100 and i have given a discount of 10% and my selling price becomes 90.
Then
Debit Credit
Customer 90 Sales account 100
Discount 10
How should I do the setup for discount and make sure that when the modifier gets applied whatever is the discount goes into the appropriate accounting setup.
I will be obliged if somebody can guide me on this issue.
Thanks & Regards,
Anil Wadhwa
[email protected]Anil,
have you used any algorithms for ariving at discounts?
Thanks
AGK -
SD-how to process material packing before sales order entry?
Hi,Guys,
If materials are packed before sales order is created, like:
materia A, 10 batches was put in one bag,
how to model it in R/3? Handling Unit Management can still be used?
Best regards,
CherieMaybe I should tell the scenario more clearly.
Following is the physical process in a High-tech company:
10 finished goods: A , were produced.Batch is 001.
In the plant, they are packed into one bag. And this bag has a packing lable number:100
now comes the sales order for one bag of material A. Stock worker go to the warehouse to get the packing number:100 to deliver this sales order.
This scenario is different from the standard one using HUM. Because the standard scenario packing the materials when doing order entry,but this one is before order entry. -
Mandatory field in sales order entry VA01.
Hello ,
I need help to resolve my problem. I am using transaction VA01. In the sales order entry we have provision for fast entry for characteristics.
This can be customized in SPRO .. IMG -> Sales and Distribution -> Sales Documents -> Fast Data Entry of Characteristics in Sales Documents -> Define Characteristics Display for Overview Screen.
In the characteristics display I have added the required characteristics I need for sales order creation. Now i need to make one of the characteristics field as mandatory for sales order creation.
How can I do that setting, so that each time when the sales order is created the particular characteristics fields pops out to be mandatory?
Thanks in advance.
Regards,
DivyaHi,
How can I do that setting, so that each time when the sales order is created the particular characteristics fields pops out to be mandatory?
Maintain the Entry required for all the desired characteristics of finish material class.
Try and revert.
Thanks
Hrishi -
How to make sales order entry mandatory in CO01
Hi,
I have a scenario where the system should not allow to create production order without the reference of sales order.
I can achieve this by using transaction code CO08.But in some special cases i have to use CO01 transaction for creation of production order.Will the system prompt for sales order entry through Co01 transaction.
Regards
SreenathHy Sreenath,
For this you have to use User Exit.
- Enhancement when Creating an Order :-
PPCO0006 Enhancement to predefine fields in order header
- Enhancement During Order Release :-
PPCO0021 Enhancement for Order Release
Better will be create saprate Order type for such type of requirements and then include that order type in User Exit.
Regards,
Dhaval
Edited by: Dhaval Choksi on Aug 7, 2008 6:12 PM -
Note messages at the time of availability check in sales order entry form
Hello Friends,
Im getting the following note messages at the time of availability check in the sales order entry form.
ATP Process resulted in no data
User defined exception in package OE_SCHEDULE_UTIL Procedure Load_Results_from_rec
User defined exception in package OE_SCHEDULE_UTIL Procedure Load_Results_from_tbl
After this when we book the order, the order line status becomes 'Booked' and does not change to 'Awaiting Shipping'
As a result of which im not able to proceed ahead with the rest of the order to cash cycle.
Can somebody please guide me in resolving this error.
We don't intend to use ATP as the client's business process is such that they maintain adequate inventory balances.
Regards
Anil WadhwaHi Anil
Are you using a RAC DB configuration? Please check if this is true, there are special setup steps that are required to be performed in case of RAC DB configuration and this issue usually occurs if such configuration is missing specifically if its happening randomly for some ATP requests.
You can find actual steps to be performed on metalink.
Thanks
Navneet Goel -
Partner selection at sales order entry: ship-to's flagged for deletion
Hi All,
I need some inputs for the following issue.
For Partner selection at sales order entry level: ship-to's flagged for deletion are also proposed as it is entered in customer master. I dont want to delete the ship-to's marked for deletion in the customer master.
In short - only the ship-to's that are not marked for deletion should get populated.
Kindly suggest if there is an userexit for the same.
Regards
KCBHi,
You can try Blocking option for the particular Ship to Party.
But this will not disable it appearing in the Partner Function Selection Pop up.
Once you block it; though it appear in the selection pop up, you cannot select & proceed, as it gives a error message.
You can set this block in 2 ways.
1 - Tx: XD05
Go to the Tx give the customer number, sales area & Pres enter.
There you can set different type of blocks depend on your scenario.
Save
2 - Tx: XD02
Go to TX, Give the Customer number (Ship to Party) & go in. Since you have marked him as a delete, you'll get a warning message there too.
Select Menu option -> Extras -> Blocking Data
You'll coime to the same screen as above.
Maintain relevant blocks & Save
Check whether it satisfy your requirement.
Best regards,
Anupa -
Need API for getting List price and unit price before Order entry
Hello,
I have requirement of provide unit & list price before order entry (Oracle Pricing and availability form provide the same).
Please suggest any API for the same.
Thanks
Akil.Hi,
Thanks luko,
I got API QP_PREQ_PUB.PRICE_REQUEST, and its return output as expected,
Just have confusion that how many qualifiers we have to send
Here is my sample code
OR REPLACE PROCEDURE xx_web_get_price (
IN NUMBER,
IN NUMBER,
IN NUMBER,
IN NUMBER,
IN VARCHAR2,
IN VARCHAR2,
IN VARCHAR2,
IN NUMBER,
OUT NUMBER,
OUT NUMBER,
OUT VARCHAR2,
OUT VARCHAR2)
QP_PREQ_GRP.LINE_TBL_TYPE;
QP_PREQ_GRP.QUAL_TBL_TYPE;
QP_PREQ_GRP.LINE_ATTR_TBL_TYPE;
QP_PREQ_GRP.LINE_DETAIL_TBL_TYPE;
QP_PREQ_GRP.LINE_DETAIL_QUAL_TBL_TYPE;
QP_PREQ_GRP.LINE_DETAIL_ATTR_TBL_TYPE;
QP_PREQ_GRP.RELATED_LINES_TBL_TYPE;
QP_PREQ_GRP.CONTROL_RECORD_TYPE;
QP_PREQ_GRP.LINE_TBL_TYPE;
QP_PREQ_GRP.QUAL_TBL_TYPE;
QP_PREQ_GRP.LINE_ATTR_TBL_TYPE;
QP_PREQ_GRP.LINE_DETAIL_TBL_TYPE;
QP_PREQ_GRP.LINE_DETAIL_QUAL_TBL_TYPE;
QP_PREQ_GRP.LINE_DETAIL_ATTR_TBL_TYPE;
QP_PREQ_GRP.RELATED_LINES_TBL_TYPE;
VARCHAR2 (240);
VARCHAR2 (240);
QP_PREQ_GRP.QUAL_REC_TYPE;
QP_PREQ_GRP.LINE_ATTR_REC_TYPE;
QP_PREQ_GRP.LINE_REC_TYPE;
QP_PREQ_GRP.LINE_DETAIL_REC_TYPE;
QP_PREQ_GRP.LINE_DETAIL_REC_TYPE;
QP_PREQ_GRP.RELATED_LINES_REC_TYPE;
QP_Attr_Mapping_PUB.Contexts_Result_Tbl_Type;
QP_Attr_Mapping_PUB.Contexts_Result_Tbl_Type;
INTEGER;
BINARY_INTEGER;
VARCHAR2 (240);
VARCHAR2 (60);
oe_debug_pub.debug_on;
oe_debug_pub.initialize;
:= OE_DEBUG_PUB.Set_Debug_Mode ('FILE');
oe_Debug_pub.setdebuglevel (5);
('File : ' || l_file_val);
QP_Attr_Mapping_PUB.
(p_request_type_code => 'ONT',
=> 'L',
=> l_pricing_contexts_Tbl,
=> l_qualifier_Contexts_Tbl);
:= 1;
---- Control Record
.pricing_event := 'LINE'; -- 'LINE';
.calculate_flag := 'Y'; --QP_PREQ_GRP.G_SEARCH_N_CALCULATE;
.simulation_flag := 'N';
.source_order_amount_flag := 'Y';
.rounding_flag := 'Q';
.manual_discount_flag := 'Y';
.request_type_code := 'ONT';
.TEMP_TABLE_INSERT_FLAG := 'Y';
---- Line Records ---------
.request_type_code := 'ONT';
.line_id := 2125125; -- Order Line Id. This can be any thing for this script
.line_Index := '1'; -- Request Line Index
.line_type_code := 'LINE'; -- LINE or ORDER(Summary Line)
.pricing_effective_date := SYSDATE; -- Pricing as of what date ?
.active_date_first := SYSDATE; -- Can be Ordered Date or Ship Date
.active_date_second := SYSDATE; -- Can be Ordered Date or Ship Date
.active_date_first_type := 'NO TYPE'; -- ORD/SHIP
.active_date_second_type := 'NO TYPE'; -- ORD/SHIP
.line_quantity := 1; -- Ordered Quantity
.line_uom_code := p_uom; --'Ea'; -- Ordered UOM Code
.currency_code := p_currency_code; -- 'USD'; -- Currency Code
.price_flag := 'Y'; -- Price Flag can have 'Y' , 'N'(No pricing) , 'P'(Phase)
(1) := line_rec;
------ Line Attribute Record
.LINE_INDEX := 1;
.PRICING_CONTEXT := 'ITEM';
.PRICING_ATTRIBUTE := 'PRICING_ATTRIBUTE3';
.PRICING_ATTR_VALUE_FROM := 'ALL';
.VALIDATED_FLAG := 'N';
(1) := line_attr_rec;
.LINE_INDEX := 1;
.PRICING_CONTEXT := 'ITEM'; --
.PRICING_ATTRIBUTE := 'PRICING_ATTRIBUTE1';
.PRICING_ATTR_VALUE_FROM := p_item_id;
.VALIDATED_FLAG := 'N';
(2) := line_attr_rec;
.LINE_INDEX := 1;
.PRICING_CONTEXT := 'ITEM';
.PRICING_ATTRIBUTE := 'PRICING_ATTRIBUTE2';
.PRICING_ATTR_VALUE_FROM := p_category_id;
.VALIDATED_FLAG := 'N';
(3) := line_attr_rec;
------ Qualifier Attribute Record
.LINE_INDEX := 1; -- Attributes for the above line. Attributes are attached with the line index
.QUALIFIER_CONTEXT := 'MODLIST';
.QUALIFIER_ATTRIBUTE := 'QUALIFIER_ATTRIBUTE4';
.QUALIFIER_ATTR_VALUE_FROM := p_price_list_id;
.COMPARISON_OPERATOR_CODE := '=';
.VALIDATED_FLAG := 'Y';
(1) := qual_rec;
.LINE_INDEX := 1;
.QUALIFIER_CONTEXT := 'CUSTOMER';
.QUALIFIER_ATTRIBUTE := 'QUALIFIER_ATTRIBUTE2';
.QUALIFIER_ATTR_VALUE_FROM := p_customer_account_id;
.COMPARISON_OPERATOR_CODE := '=';
.VALIDATED_FLAG := 'Y';
(2) := qual_rec;
.LINE_INDEX := 1;
.QUALIFIER_CONTEXT := 'CUSTOMER';
.QUALIFIER_ATTRIBUTE := 'QUALIFIER_ATTRIBUTE40';
.QUALIFIER_ATTR_VALUE_FROM := p_customer_category; --'INDUSTRIAL';
.COMPARISON_OPERATOR_CODE := '=';
.VALIDATED_FLAG := 'Y';
(3) := qual_rec;
QP_PREQ_PUB.PRICE_REQUEST (p_line_tbl,
-- Return Status Information ..
:= x_return_status_text;
:= x_return_status;
:= x_line_tbl.FIRST;
IF I IS NOT NULL
THEN
:= x_line_tbl (I).unit_price;
:= x_line_tbl (I).adjusted_unit_price;
END IF;
xx_web_get_price;
Regards,
akil. -
Sales Order Entry via Portal in R/3 4.7
Hi,
is there an iView (out of a Business Package) available for Sales Order Entry via Portal in R/3 4.7 ?
Or do we need to develop this from scratch?
Thanks & Regards,
ErikHi Erik,
The only one I found was in the Business package for Sales but it is listed for ERP2004 only. I found another one in the Business Package for Retail 50.2 that was 4.7 compatible but it is shown as out of maintenance and I was unable to download it. I didn't try very hard to get the download to work. You may want to take a look.
Good Luck,
John -
Aseembly order entry in sales order--item schedule line--Procurement tab
Hi all,
i created a Sales order which includes BOM explosion under which i am trying to seek Assembly order no under Item -- schedule lines-- procurement tab.
currently i am not getting any such data in the particular screen at all.
can anyone suggest if any IMG activity is missing which needs to be configured for geeting the same(assembly order entry inside sales order screen.)
antipitaing replies.
-ujjwalHi
Just try once as below.
Do not create it as a BOM material first of all.
For the Main-item, change the Item category group in the Material master to "0001" and save.
Ensure the Item category assignment in VOV4 as
Order type + Item category group (e,g. 0001) -
> Item category (TAK).
Now, create the new order for the Main-item, manually add the sub-items in the sales order, specify the "Hgh level item number" (item number of the main item) > click enter > save.
Now, in VA02, check schedule line > Procurement tab.
Maybe you are looking for
-
Development Tools Menu Problem
Hello. I'm configuring a scenario and was trying to define a G/L Account Object. I've read in the Operation Guide to open the Generator ObjectType in the Development Tools Menu of SAP B1isn Tool, but somehow i don't have that menu. Can anyone help me
-
Quicktime Clips in PowerPoint Play in IE but not in Safari
When running PowerPoint on my Mac or on my Webserver through IE I can propertly launch Quicktime clips by double-clicking the video window. But when I run PowerPoint through Safari, the double-clicking has a different effect- it seems to be selecting
-
Security between Proxy and Business Services
Dear All We are trying to restrict business service access only through proxy services. Will outbound security using service accounts can do this task? I enabled basic authentication at business service level and tried to pass username/password token
-
I even had to submit this question through Internet explorer
-
Set variables leads to dump error in SEM 4.0
Hi, I am on SEM 4.0 system.In BPS, i am not able to use set variables feature.whenever i hit this button the system does the process for couple of minutes and finally gives a dump error. I applied this note 806362.No success. Any one to my rescue?