Have a Problem in EAM work order creation API........

I have used the following code to create work order but i was unable to do so
I am getting return status SUCCESS(S)....
but am unable to view the record in EAM_WORK_ORDERS_V..
any sort of help would be appreciated...
declare
g_eam_wo_relations_tbl0 eam_process_wo_pub.eam_wo_relations_tbl_type;
g_eam_wo_relations_rec eam_process_wo_pub.eam_wo_relations_rec_type;
g_eam_op_rec0 eam_process_wo_pub.eam_op_rec_type;
g_eam_op_rec1 eam_process_wo_pub.eam_op_rec_type;
g_eam_op_network_rec0 eam_process_wo_pub.eam_op_network_rec_type;
g_eam_op_network_rec1 eam_process_wo_pub.eam_op_network_rec_type;
g_eam_mat_req_rec0 eam_process_wo_pub.eam_mat_req_rec_type;
g_eam_mat_req_rec1 eam_process_wo_pub.eam_mat_req_rec_type;
g_eam_di_rec0 eam_process_wo_pub.eam_direct_items_rec_type;
g_eam_di_rec1 eam_process_wo_pub.eam_direct_items_rec_type;
g_eam_res_rec0 eam_process_wo_pub.eam_res_rec_type;
g_eam_res_rec1 eam_process_wo_pub.eam_res_rec_type;
g_eam_res_inst_rec0 eam_process_wo_pub.eam_res_inst_rec_type;
g_eam_res_inst_rec1 eam_process_wo_pub.eam_res_inst_rec_type;
g_eam_op_tbl0 EAM_PROCESS_WO_PUB.eam_op_tbl_type;
g_eam_op_tbl1 EAM_PROCESS_WO_PUB.eam_op_tbl_type;
g_eam_op_network_tbl0 EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
g_eam_res_tbl0 EAM_PROCESS_WO_PUB.eam_res_tbl_type;
g_eam_res_inst_tbl0 EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
g_eam_sub_res_tbl0 EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
g_eam_res_usage_tbl0 EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
g_eam_mat_req_tbl0 EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
g_eam_di_tbl0 EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type;
g_out_eam_wo_relations_tbl eam_process_wo_pub.eam_wo_relations_tbl_type;
g_out_eam_wo_rec eam_process_wo_pub.eam_wo_rec_type;
g_out_eam_wo_tbl eam_process_wo_pub.eam_wo_tbl_type;
g_out_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type;
g_out_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
g_out_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;
g_out_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
g_out_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
g_out_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
g_out_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
g_out_eam_di_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type;
g_eam_wo_rec1 eam_process_wo_pub.eam_wo_rec_type;
g_eam_wo_rec2 eam_process_wo_pub.eam_wo_rec_type;
g_eam_wo_tbl0 eam_process_wo_pub.eam_wo_tbl_type;
g_eam_wo_res_usg_tbl0 eam_process_wo_pub.eam_res_usage_tbl_type;
l_return_status VARCHAR2(1);
l_msg_count NUMBER;
g_eam_wo_usg_rec1 eam_process_wo_pub.eam_res_usage_rec_type;
g_eam_wo_usg_rec2 eam_process_wo_pub.eam_res_usage_rec_type;
begin
g_eam_wo_rec1 := null;
g_eam_wo_rec1.transaction_type := EAM_PROCESS_WO_PVT.G_OPR_CREATE;
g_eam_wo_rec1.batch_id := 1;
G_EAM_WO_REC1.HEADER_ID := 1;
G_EAM_WO_REC1.WIP_ENTITY_ID := NULL;
g_eam_wo_rec1.wip_entity_name := '10040';
g_eam_wo_rec1.organization_id := 207;
g_eam_wo_rec1.asset_group_id := 16884;
g_eam_wo_rec1.asset_number := '28Z1933';
g_eam_wo_rec1.rebuild_item_id := null;
g_eam_wo_rec1.rebuild_serial_number := null;
G_EAM_WO_REC1.MAINTENANCE_OBJECT_SOURCE := 1;
g_eam_wo_rec1.maintenance_object_type := 3;
g_eam_wo_rec1.maintenance_object_id := 1768219;
g_eam_wo_rec1.parent_wip_entity_id := null;
g_eam_wo_rec1.manual_rebuild_flag := null;
g_eam_wo_rec1.owning_department := 4002 ;
g_eam_wo_rec1.description := 'Creating a Released Work Order';
g_eam_wo_rec1.class_code := 'MAINT';
g_eam_wo_rec1.status_type := wip_constants.released;
g_eam_wo_rec1.date_released := sysdate-100;
g_eam_wo_rec1.firm_planned_flag := 1;
g_eam_wo_rec1.scheduled_start_date := sysdate;
g_eam_wo_rec1.requested_start_date := sysdate;
g_eam_wo_rec1.scheduled_completion_date := sysdate;
g_eam_wo_rec1.material_issue_by_mo := 'N';
g_eam_wo_rec1.priority := 10;
g_eam_wo_rec1.issue_zero_cost_flag := 'Y';
g_eam_wo_rec1.po_creation_time := 1;
g_eam_wo_rec1.job_quantity := 1;
g_eam_wo_rec1.notification_required := 'N';
g_eam_wo_tbl0(1) := g_eam_wo_rec1;
EAM_PROCESS_WO_PUB.PROCESS_WO
( p_bo_identifier => 'EAM'
, p_api_version_number => 1.0
, p_init_msg_list => TRUE
, p_commit => 'Y'
, p_eam_wo_rec => g_eam_wo_rec1
, p_eam_op_tbl => g_eam_op_tbl0
, p_eam_op_network_tbl => g_eam_op_network_tbl0
, p_eam_res_tbl => g_eam_res_tbl0
, p_eam_res_inst_tbl => g_eam_res_inst_tbl0
, p_eam_sub_res_tbl => g_eam_sub_res_tbl0
, p_eam_res_usage_tbl => g_eam_res_usage_tbl0
, p_eam_mat_req_tbl => g_eam_mat_req_tbl0
, p_eam_direct_items_tbl => g_eam_di_tbl0
, x_eam_wo_rec => g_eam_wo_rec2
, x_eam_op_tbl => g_out_eam_op_tbl
, x_eam_op_network_tbl => g_out_eam_op_network_tbl
, x_eam_res_tbl => g_out_eam_res_tbl
, x_eam_res_inst_tbl => g_out_eam_res_inst_tbl
, x_eam_sub_res_tbl => g_out_eam_sub_res_tbl
, x_eam_res_usage_tbl => g_eam_res_usage_tbl0
, x_eam_mat_req_tbl => g_out_eam_mat_req_tbl
, x_eam_direct_items_tbl => g_out_eam_di_tbl
, x_return_status => l_return_status
, x_msg_count => l_msg_count
, p_debug => 'Y'
, p_output_dir => '/sqlcom/log/lv115dyp'
, p_debug_filename => 'eambo22.log'
, p_debug_file_mode => 'w'
dbms_output.put_line('work order creation status:'||l_return_status);
commit;
END;
thanks in advance
DEV

You have opened the render engine, not the full program.
Mylenium

Similar Messages

Oracle EBS drill link targets for EAM Work Order and Asset

Hi All - I am running Oracle EBS 12.1.3 and OBIEE 11g and I'm trying to link from OBIEE to EBS, but struggling to find the target functions / parameters to provide a direct URL link to EBS EAM Work Order and Asset. I have successfully linked to a Purchase Order View page, I would like to find the similar for EAM Asset and Work Order.
I can see some parameters in WorkOrderDetailsPGCO but can't seem to work out how to get to the page from a URL.
For reference MOS Note 555254.1 has some details, but not for EAM.
Has anyone provided users in any reporting system with a link to EAM Work Order or Asset page and if so how were the links generated?
Thanks,
Gareth

I am giving this a bump as I really need some help with this. Is I run the SQL with TOAD or SQLPlus it seems to consistently runs fine, The problem seems to only be from APEX. I think it has do to with the non-persistent state.

Unable to Update EAM Work Order

Hi Team,
I want to update the attribute columns of EAM Work Order. The eam_work_orders_v.attribute10 has to be updated with a quote number that is generated from order management. I tried using the following api
set serveroutput on;
Declare
l_eam_wo_rec EAM_PROCESS_WO_PUB.eam_wo_rec_type;
l_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type;
l_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
l_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;
l_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
l_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
l_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
l_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
l_out_eam_wo_rec EAM_PROCESS_WO_PUB.eam_wo_rec_type;
l_out_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type;
l_out_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
l_out_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;
l_out_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
l_out_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
l_out_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
l_out_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
l_out_eam_direct_items_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type;
x_eam_wo_rec EAM_PROCESS_WO_PUB.eam_wo_rec_type;
x_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type;
x_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
x_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;
x_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
x_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
x_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
x_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
x_eam_direct_items_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type;
X_status VARCHAR2(4000);
X_msg_cnt NUMBER;
X_msg_data VARCHAR2(4000);
Begin
fnd_global.apps_initialize (user_id => 27789,
resp_id => 23119,
resp_appl_id => 426
COMMIT;
l_eam_wo_rec := null; Record Group need to be initialized at the beginning
l_eam_wo_rec.WIP_ENTITY_NAME := '665443';
l_eam_wo_rec.organization_id := 12384;
l_eam_wo_rec.attribute10 := '2112000245';
l_eam_wo_rec.NOTIFICATION_REQUIRED := NULL;
l_eam_wo_rec.TRANSACTION_TYPE := '2';
l_eam_wo_rec.ASSET_NUMBER := '11234';
l_eam_wo_rec.ASSET_GROUP_ID := 481810;
l_eam_wo_rec.SCHEDULED_START_DATE := sysdate;
l_eam_wo_rec.SCHEDULED_COMPLETION_DATE := SYSDATE;
l_eam_wo_rec.STATUS_TYPE := wip_constants.released; -'Unreleased';
l_eam_wo_rec.OWNING_DEPARTMENT := 6003;
l_eam_wo_rec.PRIORITY := 10 ;
l_eam_wo_rec.SHUTDOWN_TYPE := null;
l_eam_wo_rec.class_code := 'WS0';
--l_eam_wo_rec.material_issue_by_mo := 'N';
--l_eam_wo_rec.issue_zero_cost_flag := 'Y';
--l_eam_wo_rec.po_creation_time := 1;
--l_eam_wo_rec.job_quantity := 1;
--l_eam_wo_rec.notification_required := 'N';
/* Additional Parameters to be passed Start */
l_eam_wo_rec.ACTIVITY_TYPE := 1; --It should be the lookup code value for the activity_type
l_eam_wo_rec.maintenance_object_source := 1;
l_eam_wo_rec.maintenance_object_type := 3;
l_eam_wo_rec.maintenance_object_id := 26005;
l_eam_wo_rec.requested_start_date := SYSDATE;
l_eam_wo_rec.job_quantity := 1;
l_eam_wo_rec.wip_supply_type := null;
/* Additional Parameters to be passed End */
apps.EAM_PROCESS_WO_PUB.PROCESS_WO
( p_bo_identifier => 'EAM'
, p_api_version_number =>1.0
, p_init_msg_list =>TRUE
, p_commit => 'Y'
, p_eam_wo_rec =>l_eam_wo_rec
, p_eam_op_tbl =>l_eam_op_tbl
, p_eam_op_network_tbl =>l_eam_op_network_tbl
, p_eam_res_tbl =>l_eam_res_tbl
, p_eam_res_inst_tbl =>l_eam_res_inst_tbl
, p_eam_sub_res_tbl =>l_eam_sub_res_tbl
, p_eam_res_usage_tbl =>l_eam_res_usage_tbl
, p_eam_mat_req_tbl =>l_eam_mat_req_tbl
, p_eam_direct_items_tbl => l_out_eam_direct_items_tbl
, x_eam_wo_rec =>x_eam_wo_rec
, x_eam_op_tbl =>x_eam_op_tbl
, x_eam_op_network_tbl =>x_eam_op_network_tbl
, x_eam_res_tbl =>x_eam_res_tbl
, x_eam_res_inst_tbl =>x_eam_res_inst_tbl
, x_eam_sub_res_tbl =>x_eam_sub_res_tbl
, x_eam_res_usage_tbl =>x_eam_res_usage_tbl
, x_eam_mat_req_tbl =>x_eam_mat_req_tbl
, x_eam_direct_items_tbl => x_eam_direct_items_tbl
, x_return_status =>X_status
, x_msg_count =>X_msg_cnt
, p_debug =>'Y'
, p_output_dir => '/user/temp'
, p_debug_filename =>'Amit_6_EAM_WO_DEBUG2.log'
, p_debug_file_mode => 'a'
commit;
DBMS_OUTPUT.PUT_LINE('Status : '||X_status);
IF X_msg_cnt > 0 THEN
DBMS_OUTPUT.PUT_LINE('Error Occurred in WO Creation : '|| X_msg_cnt||' : '||SQLERRM||' : '||SQLCODE);
END IF;
DBMS_OUTPUT.PUT_LINE('First record inserted.......');
END;
The Result:
anonymous block completed
Status : E
Error Occurred in WO Creation : 3 : ORA-0000: normal, successful completion : 0
First record inserted.......
Can i know if missed something over here??
Thanks
Mohan

Hi,
If you have a maintenance BOM and Routing for the activity in use for your work order
The work order created will get the data defaulted from those BOM and Routing ie operations , BOM and Routing.
Please check whether you have the BOM and routing and also please compare the BOM and routing information with the information you are adding.
Also make sure that you are passing all the mandatory inputs.
thanks
Krishna

Work Order Creation Time

Hi Guys
I need a help with a problem here
Our maintenance guys work in 3 different shifts. We would like to get a report about the workload in each shift
I was wondering if its possible to get a list of orders with the creation time of each order.
How can I get this info? The work order creation time?
Thanks and Regards

Transaction IW38 will give you a list based on the the date created you would need to create a varaint with a list of the user ID's that belong in each of the 3 shiftes this would then give a report of the orders created by Shift on any given day.
Alternatively if you wanted to find out the orders on a weekly basis this could be done using the user ID's with a period of time over a week for instance.
Hope this helps
Jim

Material Availability check during work order creation and Release

Hello All,
We are checking material availability at creation as well as release
Say we have Material XYZ=100 in stock MMBE
Now XYZ =100 is say at normal storage location =75
and scrap storage location=05 and serviceable =20
Currently when availability check is performed it checks for 95 (It excludes scrap storage location 05 )
but we want Availability check to be only for normal stock =75 and not for Serviceable and Scrap location
how to do this in configuration or via exits
Since if the material is under Scrap location it is not counting in Availability check at work order creation this logic is working fine but I do know from where this control is put that when the material is in the stock of scrap it is not counting in Availability check for work orders.Same thing I want to extend it to Serviceable stock .
Why not it is consider it for Scrap storage location , what is config or any MM enhancement
So that when Availability check run it will not consider Materials at SCRAP as well as SERVISABLE storage location also.
Please have your views on this
Regards
pratap

Hello
There are two option for your requiement
1. Changing the status of the servisable storage location stock to restricted use stock . You can include or exclude this stock status material in OPJJ. This solution is not storage location dependent. It is stock status dependent.
2. Please refer the enhancement for the storage location determination. I am not sure about this funtionality:
For production orders the following enhancement is available:
PPCO0005 enhancement for storage loc. determination/backflushing
You can use this enhancement to change the storage location and the indicator 'backflushing' in the reservation.
The enhancement PPCO0005 contains the following enhancement components:
Function exit
EXIT_SAPLCOSD_001 storage location determination/backflushing
You can find the description in modification text of the function exit.
You can find an example of the user exit in the function group XC01 in the include LXCO1F05.
warm regards
Ramakrishna

How to make material availability check work during Work Order creation

Hi Experts,
Kindly advice about these matters:
1. How to make material availability check work during Work Order creation?
My requirement is Work Order can not be created when it has missing parts. I have set the config to '3' can not created when is has missing parts, but it still does not work.
I have implemented SAP Notes 1148139 on my system (SAP ECC 6 Ehp 5) also, but still does not have any effect.
I must not set the config Res./Purch Doc creation to 'immediately', because it does not fit to my user requirement. Is there anyone knows how to solve this requirement?
2. How to make information message/ Availability check screen appear when sparepart is missing, without clicking Availability Check button? for example: appear when clicking Save button.
Thank you
-amoonra-

Hi Maheswaran,
I have implement the prerequisite notes. (Notes 790219 and 1034962). Do you know why it is still does not work?
Thanks
-amoonra-

EAM Work Order Capitalization

Can we capitalize incomplete Work Order, as this comes under the definition of CIP, especially at the period close if Work order is still open, this cost has to be shown in CIP, if to be caplitalized later.
Kindly suggest
Regards
Yasir

Hi.
I have downloaded the latest client from Service Marketplace: Support Packages and Patches -> My Company's Application Components -> My Company's Software -> SAP EAM WORK ORDER -> SAP EAM WORK ORDER 1.0 -> Comprised Software Component Version -> SAP EAM WORK ORDER CLIENT 1.0 -> Win32.
Under installations and upgrades you can find it at My Company's Application Components -> My Company's Software -> SAP EAM WORK ORDER -> SAP EAM WORK ORDER 1.0 -> 51041739.
Hope it helps.
/Michael.

Does Mavericks have the problem fixed with working with the Dell UltraSharp U3014 30 inch monitor?

Does Mavericks have the problem fixed with working with the Dell UltraSharp U3014 30 inch monitor?

I have this (or a similar) issue and I did notice something interesting. After I boot into Windows via Bootcamp (where I have the U3014 specfic driver installed) and then reboot into MacOS X (Mavericks) the monitor works flawlessly.
I would hazard a guess that this means bootcamp is retaining the driver used in Windows. Kind of the reverse of the TB GBE adapter driver issue.
To explain my issue for anyone else: the monitor flicks on and off as if the connection was poor. Connecting via HDMI. Connection is fine and as stated, everything works fine in Bootcamp.

SAP EAM Work Order 1.0 and SAP Field Service 1.0

Hi All,
Related to these two new applications launched recently by SAP, taking advantage of the fusion between SAP and Sybase (SAP EAM Work Order 1.0 and SAP Field Service 1.0), someone already implemented some of these new features in mobile?
If someone did, may share some information regarding these new features?
Best regards,
Rogério Reis
Someone can help?
Edited by: Rogério Reis on Dec 12, 2011 11:33 AM

Hi,
Please review the link below
http://news.techworld.com/mobile-wireless/3280507/sap-announces-new-push-into-mobile-applications/
Regards
Carlos

Oracle MES for EAM Work Order

Hi,
We know Oracle MES supports discrete Work orders.
Is it supports EAM Work Order also.
we need to introduce Clock in Clock out functionality against resources of EAM WO.
Thanks
Raman

Hi Din;
Please check below notes and see its helpful for your issue:
Department Wise Work Order Release Approvers in EAM using AME [ID 944918.1]
EAM DOCUMENT APPROVALS USING AME [ID 972652.1]
Regard
Helios

Close work order using api

hi every one..
can any one plz tell me how to close eam work order by using api
plz say to me how to approach.
thanks in advance
ram

hi sandeep..
thanks for your response..
but i need to close eam work order by using Work Order Business Object API.
in this api there one procedure calld Process_Master_Child_WO.
the sample code has been given by some body..as follows..plz help me how to use this code..because im not aware of api's
plz any one help me...
thanks in advance...
Ram.
set serveroutput on;
Declare
l_eam_wo_rec EAM_PROCESS_WO_PUB.eam_wo_rec_type;
l_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type;
l_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
l_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;
l_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
l_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
l_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
l_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
l_out_eam_wo_rec EAM_PROCESS_WO_PUB.eam_wo_rec_type;
l_out_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type;
l_out_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
l_out_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;
l_out_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
l_out_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
l_out_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
l_out_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
l_out_eam_direct_items_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type;
x_eam_wo_rec EAM_PROCESS_WO_PUB.eam_wo_rec_type;
x_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type;
x_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
x_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;
x_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
x_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
x_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
x_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
x_eam_direct_items_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type;
X_status VARCHAR2(4000);
X_msg_cnt NUMBER;
X_msg_data VARCHAR2(4000);
Begin
fnd_global.apps_initialize (user_id => 27789,
resp_id => 23119,
resp_appl_id => 426
COMMIT;
l_eam_wo_rec := null; Record Group need to be initialized at the beginning
l_eam_wo_rec.WIP_ENTITY_NAME := '665443';
l_eam_wo_rec.organization_id := 12384;
l_eam_wo_rec.attribute10 := '2112000245';
l_eam_wo_rec.NOTIFICATION_REQUIRED := NULL;
l_eam_wo_rec.TRANSACTION_TYPE := '2';
l_eam_wo_rec.ASSET_NUMBER := '11234';
l_eam_wo_rec.ASSET_GROUP_ID := 481810;
l_eam_wo_rec.SCHEDULED_START_DATE := sysdate;
l_eam_wo_rec.SCHEDULED_COMPLETION_DATE := SYSDATE;
l_eam_wo_rec.STATUS_TYPE := wip_constants.released; -'Unreleased';
l_eam_wo_rec.OWNING_DEPARTMENT := 6003;
l_eam_wo_rec.PRIORITY := 10 ;
l_eam_wo_rec.SHUTDOWN_TYPE := null;
l_eam_wo_rec.class_code := 'WS0';
--l_eam_wo_rec.material_issue_by_mo := 'N';
--l_eam_wo_rec.issue_zero_cost_flag := 'Y';
--l_eam_wo_rec.po_creation_time := 1;
--l_eam_wo_rec.job_quantity := 1;
--l_eam_wo_rec.notification_required := 'N';
/* Additional Parameters to be passed Start */
l_eam_wo_rec.ACTIVITY_TYPE := 1; --It should be the lookup code value for the activity_type
l_eam_wo_rec.maintenance_object_source := 1;
l_eam_wo_rec.maintenance_object_type := 3;
l_eam_wo_rec.maintenance_object_id := 26005;
l_eam_wo_rec.requested_start_date := SYSDATE;
l_eam_wo_rec.job_quantity := 1;
l_eam_wo_rec.wip_supply_type := null;
/* Additional Parameters to be passed End */
apps.EAM_PROCESS_WO_PUB.PROCESS_WO
( p_bo_identifier => 'EAM'
, p_api_version_number =>1.0
, p_init_msg_list =>TRUE
, p_commit => 'Y'
, p_eam_wo_rec =>l_eam_wo_rec
, p_eam_op_tbl =>l_eam_op_tbl
, p_eam_op_network_tbl =>l_eam_op_network_tbl
, p_eam_res_tbl =>l_eam_res_tbl
, p_eam_res_inst_tbl =>l_eam_res_inst_tbl
, p_eam_sub_res_tbl =>l_eam_sub_res_tbl
, p_eam_res_usage_tbl =>l_eam_res_usage_tbl
, p_eam_mat_req_tbl =>l_eam_mat_req_tbl
, p_eam_direct_items_tbl => l_out_eam_direct_items_tbl
, x_eam_wo_rec =>x_eam_wo_rec
, x_eam_op_tbl =>x_eam_op_tbl
, x_eam_op_network_tbl =>x_eam_op_network_tbl
, x_eam_res_tbl =>x_eam_res_tbl
, x_eam_res_inst_tbl =>x_eam_res_inst_tbl
, x_eam_sub_res_tbl =>x_eam_sub_res_tbl
, x_eam_res_usage_tbl =>x_eam_res_usage_tbl
, x_eam_mat_req_tbl =>x_eam_mat_req_tbl
, x_eam_direct_items_tbl => x_eam_direct_items_tbl
, x_return_status =>X_status
, x_msg_count =>X_msg_cnt
, p_debug =>'Y'
, p_output_dir => '/user/temp'
, p_debug_filename =>'Amit_6_EAM_WO_DEBUG2.log'
, p_debug_file_mode => 'a'
commit;
DBMS_OUTPUT.PUT_LINE('Status : '||X_status);
IF X_msg_cnt > 0 THEN
DBMS_OUTPUT.PUT_LINE('Error Occurred in WO Creation : '|| X_msg_cnt||' : '||SQLERRM||' : '||SQLCODE);
END IF;
DBMS_OUTPUT.PUT_LINE('First record inserted.......');
END;

HOW TO: EAM - Work Order Page - Change Concurrent Program to run

Hi,
my customer is using EAM and in the Work Order Search page the customer can select a work order and press the button "Print Work Orders". The standard work order (BI Publisher report) print is submitted.
Their request is to submit the Customized version of this concurrent program.
Can this be done and how can this be done?
Thanks in advance.
Regard Roel
Edited by: user13071061 on 6-okt-2010 6:26

Hi,
Can you please check that what is the Template of Standard Work Order Report.
It comes from the setup for Document Types in Oracle. Most probably the template will be
XXL-FO. And if yes, then you need to have the customized report also, in XXL-FO Template and then in Document Types just give the name of the customized Template Name (Register the Template and Data Definition in Oracle first). Save it
and then run the page again to see if now it picks the template of your customized report or not.
Thanks,
Gaurav

EAM Work order completion issue

Hi guys
We have a requirement where we need to complete a work order using an API call .
There are times where even when all operations are completed the users dont change the status to complete.
I've tried using the EAM_PROCESS_WO_PUB.PROCESS_WO to change the status to different statuses and it works for some statuses,
but when I try to change the status of the WO from released to complete it gives me the following error.
change from 3 to 4 not poss
oddly this call does change the system status of the work order to complete but not the status type
any ideas , suggestions?
Thanks
Dan

user eam_completion API
take care
Aamir

Eam Work order assignment info

Hi Guys
This is a followup to a question I asked in the SCM forum but was asked to post EAM questions here by Sandeep who answered my previous questions graciously.
A> I am tracking a specific situation- when every operation assigned to a work order is completed I need to execute a pl/sql Concurrent program.
For this one I think the work order status would be changed to complete?
B>I am also tracking another situation- When a resource is assigned to a work order I need to execute a pl/sql conc prog.
What table info gets set when this happens?
Thanks
Jake

A> WIP_MOVE_TRANSACTIONS is probably what you are looking for. Write a trigger on that table.
B> WIP_OPERATION_RESOURCES is the table used. So you can write a trigger on that table.
Hope this helps,
Sandeep Gandhi

Work order creation

Hi Everybody,
Pl let me know whether any BAPI is there to create a Work Order with reference to an existing Notification.
This is in Plant maintenance area.
Thanks in advance.
Suresh
Message was edited by: Revuru S Suresh

Revuru,
Just a hint: this is ABAP-specific question, so better re-post it at ABAP Development, and given activity at this forum you will get an answer within tens of minutes
VS
Message was edited by: Valery Silaev

Have a Problem in EAM work order creation API........

Similar Messages

Maybe you are looking for