An Error Occured While Processing Business Object In Organization
following section: Section G.1, "Resolving Errors" G.1 Resolving Errors Table G-1 provides actions to take to resolve errors that may occur in Agile Product Lifecycle Management (PLM) Integration Pack for Oracle E-Business Suite: Design to Release. Table G-1 Error messages and solutions ID Flow Error Message AIA/Agile/Ebiz Business/System Action to resolve 1 Sync Item and then Create ECO for that Item and add Revision as A and Submit it You must enter an item revision for revised item <
17:15 3776人阅读 评论(0) 收藏 举报 本文章已收录于: 分类: Oracle Apps(39) 作者同类文章X 版权声明:本文为博主原创文章,未经博主允许不得转载。 EBS Version: 11.5.8Requirement: User need to disable bom component by uploading a csv file which containing the TOP level assemblies to be disable by adding disable_date to all the components/subassemblies. https://docs.oracle.com/cd/E58077_01/doc.116/e40004/ap-f.htm Constraints: 1. The disabling should be done level by level, which means, after disabling upper level, the program can go to lower level to do further disabling. 2. I hate submitting http://blog.csdn.net/orapeasant/article/details/2065705 a lot of 'import bom' request, it's realy ugly. Thus I decide to use BOM_BO_PUB.PROCESS_BOM. Following is my codeFOR c INmy_cur LOOP I := I + 1; l_bom_header_rec.Assembly_item_name := c.assy_item_number; l_bom_header_rec.Organization_code := d.organization_code; l_bom_header_rec.Assembly_type := 1; l_bom_header_rec.attribute_category := gc_header_att_cat; l_bom_header_rec.attribute2 := d.file_name; l_bom_header_rec.Transaction_Type := 'UPDATE'; l_bom_component_tbl(i) := bom_bo_pub.g_miss_bom_component_rec; l_bom_component_tbl(i).transaction_type := 'UPDATE'; l_bom_component_tbl(i).organization_code := d.organization_code; l_bom_component_tbl(i).assembly_item_name := c.assy_item_number; l_bom_component_tbl(i).component_item_name := c.comp_item_number; l_bom_component_tbl(i).operation_sequence_number := c.operation_seq_num; l_bom_component_tbl(i).start_effective_date := c.eff_date; l_bom_component_tbl(i).disable_date := d.disable_date; l_bom_component_tbl(i).item_sequence_number := c.item_num; l_bom_component_tbl(i).so_basis := c.so_basis; l_bom_component_tbl(i).wip_supply_type := c.wip_supply_type; l_bom_component_tbl(i).quantity_per_assembly := c.component_quantity; l_bom_component_tbl(i).projected_yield := c.component_yield_factor; l_bom_component_tbl(i).planning_percent := c.planning_f
Maximo Enterprise Adapter; item; organization; itemorgset; TPAEINTEGRATION Technote (troubleshooting) Problem(Abstract) This document provides information http://www.ibm.com/support/docview.wss?uid=swg21392387 to avoid the error on the error xml file "Error http://www.itpub.net/archiver/tid-1888065.html occurred while processing ITEMORGINFO ( IR number 1, Integration Object number 1 )" importing data to ITEMORGINFO table. Symptom You may not be able to load info on ITEMORGINFO table Resolving the problem ITEMORGINFO is a base Maximo cross-reference table that allows tax an error codes to be associated with items (the ITEM table), and is vital for purchasing. When creating an item record (or tool, or service item), Maximo should automatically create ITEMORGINFO records for all organizations that use the itemset. If you try to import data directly on this table through MEA (Maximo Enterprise Adapter), using an an error occured inbound Integration Interface referencing an Integration Object for the ITEMORGINFO object, you will get an error on the logs, and that error reflected on the error XML generated on the error folder under your MEA Global Directory will look like this:
Id:RI Index :1 Table Name Mesg :Your latest revision for this item is 2.0 from ECO HGHGE13017 row_identifier --------------------------------------- Entity Id:RC Index :1 Table Name Mesg :The parent item 0J24129 you are referencing in component HG0J21621 does not exist on ECO ECO1409006. row_identifier --------------------------------------- Entity Id:RC Index :1 Table Name Mesg :This record received an error status since a severe error occured in the comopnent HG0J21621 while performing user unique conversions. row_identifier --------------------------------------- Entity Id:BO Index :1 Table Name Mesg :An error occured while processing business object ECO1409006 in organization GB9. Please check the data in this business object and re-run the import process. row_identifier --------------------------------------- Total Messages: 1 ʽ: Insert Into Eng_Eng_Changes_Interface (Change_Notice, Organization_Id, Organization_code, Last_Update_Date, Last_Updated_By, Creation_Date, Created_By, Description, Status_Name, --STATUS_TYPE, Initiation_Date, Approval_Status_Name, --APPROVAL_STATUS_TYPE, Approval_Date, Change_Order_Type, Transaction_Type, Process_Flag, Eng_Changes_Ifce_Key) Values (LR_ECO.Eco_Name, P_ORG_ID, v_org_code, Sysdate, v_user_id, Sysdate, v_user_id, LR_ECO.ECO_DESC, --DESCRIPTION LR_ECO.Eco_Status, --x_status_name, -- Open 1, --STATUS_TYPE Sysdate, --INITIATION_DATE 'Approved', Sysdate, --APPROVAL_DATE 'ECN', 'CREATE', --TRANSACTION_TYPE 1, LR_ECO.Eco_Name --, --ENG_CHANGES_IFCE_KEY ); Insert Into Eng_Revised_Items_Interface (Change_Notice, Eng_Changes_Ifce_Key, Organization_Id, Organization_Code, Last_Update_Date, Last_Updated_By, Creation_Date, Created_By, Scheduled_Date, Revised_Item_Number, Assembly_Item_Number, NEW_ITEM_REVISION, --°汾 Transaction_Type, Process_Flag, Bill_Sequence_Id, Revised_Item_Sequence_Id, Eng_Revised_Items_Ifce_Key) Values (LR_ECO.Eco_Name, --CHANGE_NOTICE LR_ECO.Eco_Name, P_ORG_ID, --ORGANIZATION_ID v_org_code, Sysdate, --LAST_UPDATE_DATE v_user_id, Sy