Problem in ECO implementation : Revised Item already implemented
Hi,
I have created a custom package to Implement the ECO changes in all the organizations where the target BOM exists. Previously I had only one inventory organization and this package was implementing the changes correctly.
But currently, we have created another Inventory organization, the problem is the ECO implementation is occurring for any one of the either organizations.
In this course, it is failing with the above given errors for the 2nd organization.
Entity Id: XX
Index: 1
Mesg: The revised item YYYY has already been implemented.
Entity Id: XX
Index: 1
Mesg: This record received a fatal error since a fatal error occured in revised item YYYY while checking if the user has access to it.
Entity Id: XX
Index: 1
Mesg: This record received a fatal error since a fatal error occured in revised item YYYY while checking if the user has access to it.
Entity Id: XX
Index: 1
Mesg: An error occured while processing business object ABC in organization XY. Please check the data in this business object and re-run the import process.
Please suggest if there is any thing missing in the set up or whether this is any technical pl/sql related issue.
Thanks,
Anwesha
Try and logout and login and run again.
Or try and see in debug mode why its not reading the BREAK;
Similar Messages
-
List of Issues/ problems in SAP GRC AC 5.3 Implementation
Hello,
Can anyone provide me with the list of most commonly occurring problems related to
1- SAP GRC Suite Installation
2- RAR Module implementation
3- CUP Module implementation
4- ERM Module implementation
5- SPM Module implementation
6- SAP PC 2.5 implementation
7- SAP RT Module implementation
8- SAP GRC Suite Upgradation.
Thanks in advance!!!Hi Abdul,
As such there are no issues in implemeting the AC modules.
Just make sure that you undeploy previously installed SP before deploying the new Support packages.
1. You have to upload the initial file (xml files) again in CUP and ERM. These files should be corresponding to latest support pack.
2. upload the CC 53_Messages.txt file in RAR with every upgrade.
Also restart the server after deploying any following the above steps.
For RT you can follow the note 1225960, 1060673 and make sure to restart the server after configuring the SAP Adapter.
Regards,
shweta -
What oracle best practices in mapping budgeting to be implement at item
Dear Consultant's
Really i need you values Consultantancy
What oracle best practices in mapping budgeting to be implement at item category level or item level
I want to check fund at encumbrance account according to item level
Case:
I have there item category
One is Computer's items
Tow is printer's items
Third is food's item's
I want to implement my budget on item category level
Example:
I want my purchase budget for item with printer's type not exceed 30000USD
And For item with type food's not exceed 45000usd
How to map this in oracle application
The modules implemented on my site
(GL, AP, AR, INV, PURCHASING, OM)
Please give me the oracle best practice that handle this case
Thanks for all of youHi,
It is really difficult to have Budgetary Control on Inventory Items in Average Costing enviornment as you can have only one Inventory Account at the Inventory Organization level.
You have to modify your PO / Requisition Account Generator to populate the Encumbrance Account in PO / Requisition based upon item category. Moreover, the "Reverse Encumbrance" flag in your Inventory Org needs to be unchecked so that the encumbrances are not revered when the goods are received.
Gajendra -
BBP_WFL_APPROV_BADI - There are already implementations active
Hi
I was thinking about using badi BBP_WFL_APPROV_BADI to set up different approvers for approval of the Shopping Cart in SRM. But unfortunately I get the message "There are already implementations active". Looks like SAP is already using this BADI. Does that mean that there is no way that I can use this BADI too?
Best regards
SteenHi Steen,
please look at BBP_WFL_APPROV_BADI in SE80. In the object tree you should see the implemantation(s).
Regards,
Clemens -
Connection Pooling in EJBContainer if Driver already implements
Hi,
Can anybody explain the mechanism in an EJBContainer if the Driver for a particular database already implements the Connection pooling ie JDBC2.0X feature. Does the EJBContainer utilize the already pooled connections or the Container uses it own implementation of the pooledConnection interface.
Thanks in advance
neothe Container uses it own implementation of the pooledConnection interface.
you have to make connection pool in the property file
in weblogic we make connection pool in the weblogic.property file
which server u r using -
Configuring WM in Already Implemented SAP ECC 6.0
Dear all,
In my SAP system all modules like MM,SD,FICO,PP are implemented.
Now we want to implement SAP WM module in already implemented System,
So what are the Key Points to consider While implementing the WM module.
Regards,
Rocky.Hi,
See this link below for the detail's
http://www.karkhanisgroup.com/consulting/wm-warehouse-management.html?showall=1
http://www.erpgenie.com/component/content/article/127
Regards
Bhuban -
Companies activate QM after they have already implemented the MM
Hi guys,
I read the help portal on the following:
In some cases, companies activate QM after they have already implemented the Materials Management (MM) and Inventory Management (MM-IM) components productively. As a result, materials may have been posted to inspection stock type using the functions of the inventory management.
In such cases, you can only activate inspection types for stock-relevant materials if you perform ONE of the following steps:
Step 1 - Post the goods out of inspection stock manually using the functions of the inventory management before you try to activate a stock-relevant inspection type.
Step 2 - Activate the desired stock-relevant inspection type(s) using the function for making mass changes to the inspection settings.
My question
1 - After step 1, how to make the stock post back into the Inspection Lot?
2 - How, which tcode and step to perform on step 2, and what is the things to be aware of on this mass changes?
Thanks
KarenHi, sujit,
Just to double confirm.
Does the following steps correct based on your direction:
Letu2019s say for example, there are 200pcs of material A (i.e. this material A is going to be executed using QM functionality) currently reside at a storage location in QA stock type (i.e. IM stock type, not the QM stock type).
And I would like to use the inspection type 01 to trigger a inspection lot for this 200pcs
I execute the following steps:
1 u2013 move the QA stock type of the 200pcs out of the QA stock type from its existing storage location to another storage location.
2 u2013 activate the 01 inspection type using QA08 for this particular material in this plant.
Does the above steps correct based on my example?
thanks
Karen -
Eng_eco_pub.process_Eco for UPDATE of effectivity_date on revised items
Hi All,
We are on Oracle Applications Rel 11.5.8.
We are trying to update an existing ECO with an ‘UPDATE’ transaction_type using eng_Eco_pub API. Here is the code. We first execute this script with CREATE and ECO is created. However, when we run the same script to UPDATE with transaction_type = ‘UPDATE’, the bill_sequence_id in eng_revised_items is updated to g_miss_num (9.99E125). The API is returning ‘SUCCESS’ and updates the bill_sequence_id to 9.999E125. Not sure what we are missing here. Appreciate any inputs or sample code for UPDATING an already created ECO.
REVISED_ITEM_ID BILL_SEQUENCE_ID CHANGE_NOTICE
11668210 192981011 IK-API0316
REVISED_ITEM_ID BILL_SEQUENCE_ID CHANGE_NOTICE
11668210 9.99E125 IK-API0316
Thank You!
DECLARE
l_eco_name VARCHAR2(10) := 'IK-API0000' ;
l_org_code VARCHAR2(3) := 'GLO';
l_transaction_type VARCHAR2(10) := 'CREATE'; -- or UPDATE for updating the same ECO
l_rev_item_number1 VARCHAR2(20):= '16-2214-01';
l_eff_date DATE := NULL;
v_old_effective_date DATE;
l_new_revised_item_revision VARCHAR2(3) := '-A0';
l_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
l_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
l_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type ;-- := Eng_Eco_Pub.g_miss_revised_item_tbl;
l_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
l_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
l_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
l_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
l_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
l_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- API output variables
x_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
x_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
x_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type ;-- := Eng_Eco_Pub.g_miss_revised_item_tbl;
x_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
x_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
x_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
x_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
x_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
x_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- Other API variables for return status / error handling / debugging
l_error_table Error_Handler.Error_Tbl_Type;
l_return_status VARCHAR2(1) := NULL;
l_msg_count NUMBER := 0;
l_output_dir VARCHAR2(500) := '/apps/orarpt/SJDEV/utl';
l_debug_filename VARCHAR2(60) := 'test.dbg';
-- WHO columns
l_user_id NUMBER := -1;
l_resp_id NUMBER := -1;
l_application_id NUMBER := -1;
l_row_cnt NUMBER := 1;
l_user_name VARCHAR2(30) := 'CA_ADMIN';
l_resp_name VARCHAR2(30) := 'Engineering';
l_comp_eff_date date := null;
l_disable_date date := null;
BEGIN
-- Get the user_id
SELECT user_id,sysdate + 10,sysdate
INTO l_user_id,l_comp_eff_date,l_eff_date
FROM fnd_user
WHERE user_name = l_user_name;
-- Get the application_id and responsibility_id
SELECT application_id, responsibility_id
INTO l_application_id, l_resp_id
FROM fnd_responsibility_tl
WHERE responsibility_name = l_resp_name;
FND_GLOBAL.APPS_INITIALIZE(l_user_id, l_resp_id, l_application_id); -- Mfg / Mfg & Dist Mgr / INV
dbms_output.put_line('Initialized applications context: '|| l_user_id || ' '|| l_resp_id ||' '|| l_application_id );
dbms_output.put_line('before initialixe');
Error_Handler.Initialize;
l_return_status := NULL;
dbms_output.put_line('after initialixe');
-- FOR UPDATE API to update effectivity date on Revised item.
l_eco_rec.eco_name := l_eco_name;
l_eco_rec.organization_code := l_org_code;
l_eco_rec.change_type_code := 'DESIGN';
l_eco_rec.eco_department_name := NULL;
l_eco_rec.priority_code := NULL; --'Medium';
l_eco_rec.approval_list_name := NULL; --'SU_ONLY';
l_eco_rec.reason_code := NULL;
l_eco_rec.Approval_Status_TYPE := 5 ;-- 'Approved'; -- will default to Not submitted for Approval
l_eco_rec.Status_TYPE := 1; -- 1 to bring in SCHEDULE status
l_eco_rec.description := l_eff_date || ' - ECO - '||l_eco_rec.eco_name ;
l_eco_rec.transaction_type := l_transaction_type;
l_eco_rec.return_status := NULL;
IF l_transaction_type ='CREATE' THEN
l_revised_item_tbl(l_row_cnt).transaction_type := l_transaction_type; -- transaction type : CREATE / UPDATE
l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number1;
l_revised_item_tbl(l_row_cnt).new_revised_item_revision := '-A0'; -- pass only if the previous unimplemented updating ECO has a new revision
l_revised_item_tbl(l_row_cnt).Updated_Revised_Item_Revision := ''; -- l_new_revised_item_revision;
l_revised_item_tbl(l_row_cnt).start_effective_date := l_eff_date;
l_revised_item_tbl(l_row_cnt).new_effective_date := l_eff_date ; -- l_comp_eff_date;
l_revised_item_tbl(l_row_cnt).alternate_bom_code := null;
l_revised_item_tbl(l_row_cnt).status_type := 1; -- 'Open'
l_revised_item_tbl(l_row_cnt).change_description := l_rev_item_number1 || ' --B0 ECO - '||l_eco_rec.eco_name ;
l_revised_item_tbl(l_row_cnt).disposition_type :=1 ;
l_revised_item_tbl(l_row_cnt).update_wip := 1;--2
l_revised_item_tbl(l_row_cnt).mrp_active := 1;
--l_revised_item_tbl(l_row_cnt).new_item_revision:= '';
l_revised_item_tbl(l_row_cnt).new_routing_revision:= '';
l_revised_item_tbl(l_row_cnt).from_end_item_unit_number:= ''; -- this field is mandatory
l_revised_item_tbl(l_row_cnt).eco_for_production:=2;
l_revised_item_tbl(l_row_cnt).earliest_effective_date := l_eff_date;
l_revised_item_tbl(l_row_cnt).use_up_item_name := l_rev_item_number1; null;
--l_revised_item_tbl(l_row_cnt).use_up_plan_name :=null;
END IF;
IF l_transaction_type = 'UPDATE' THEN
FOR v_component in (SELECT * from eng_revised_items where change_notice = 'IK-API0000') LOOP
l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number1;
l_revised_item_tbl(l_row_cnt).new_revised_item_revision := '-A0';
l_revised_item_tbl(l_row_cnt).New_Revised_Item_Rev_Desc := '-F0 ik added';
l_revised_item_tbl(l_row_cnt).Updated_Revised_Item_Revision := '-F0';
l_revised_item_tbl(l_row_cnt).Start_Effective_Date := l_eff_date;
l_revised_item_tbl(l_row_cnt).New_Effective_Date := l_eff_date;
l_revised_item_tbl(l_row_cnt).Alternate_Bom_Code := v_component.alternate_bom_designator;
l_revised_item_tbl(l_row_cnt).Status_Type := v_component.status_type;
l_revised_item_tbl(l_row_cnt).Mrp_Active := v_component.Mrp_Active;
l_revised_item_tbl(l_row_cnt).Earliest_Effective_Date := sysdate;
l_revised_item_tbl(l_row_cnt).Requestor := '';
l_revised_item_tbl(l_row_cnt).Use_Up_Plan_Name := v_component.Use_Up_Plan_Name;
l_revised_item_tbl(l_row_cnt).Disposition_Type := v_component.Disposition_Type;
l_revised_item_tbl(l_row_cnt).Update_Wip := v_component.Update_Wip;
l_revised_item_tbl(l_row_cnt).Cancel_Comments := v_component.Cancel_Comments;
l_revised_item_tbl(l_row_cnt).Change_Description := 'TESTING ';
l_revised_item_tbl(l_row_cnt).Attribute_category := v_component.Attribute_category;
l_revised_item_tbl(l_row_cnt).Attribute1 := v_component.Attribute1;
l_revised_item_tbl(l_row_cnt).Attribute2 := v_component.Attribute2;
l_revised_item_tbl(l_row_cnt).Attribute3 := v_component.Attribute3;
l_revised_item_tbl(l_row_cnt).Attribute4 := v_component.Attribute4;
l_revised_item_tbl(l_row_cnt).Attribute5 := v_component.Attribute5;
l_revised_item_tbl(l_row_cnt).Attribute6 := v_component.Attribute6;
l_revised_item_tbl(l_row_cnt).Attribute7 := v_component.Attribute7;
l_revised_item_tbl(l_row_cnt).Attribute8 := v_component.Attribute8;
l_revised_item_tbl(l_row_cnt).Attribute9 := v_component.Attribute9;
l_revised_item_tbl(l_row_cnt).Attribute10 := v_component.Attribute10;
l_revised_item_tbl(l_row_cnt).Attribute11 := v_component.Attribute11;
l_revised_item_tbl(l_row_cnt).Attribute12 := v_component.Attribute12;
l_revised_item_tbl(l_row_cnt).Attribute13 := v_component.Attribute13;
l_revised_item_tbl(l_row_cnt).Attribute14 := v_component.Attribute14;
l_revised_item_tbl(l_row_cnt).Attribute15 := v_component.Attribute15;
l_revised_item_tbl(l_row_cnt).From_End_Item_Unit_Number := v_component.From_End_Item_Unit_Number;
l_revised_item_tbl(l_row_cnt).New_From_End_Item_Unit_Number := '';
l_revised_item_tbl(l_row_cnt).Original_System_Reference :=v_component.Original_System_Reference;
l_revised_item_tbl(l_row_cnt).Return_Status := '';
l_revised_item_tbl(l_row_cnt).Transaction_Type := l_transaction_type;
-- L1, the following is added for ECO enhancement
l_revised_item_tbl(l_row_cnt).From_Work_Order := '';
l_revised_item_tbl(l_row_cnt).To_Work_Order := '';
l_revised_item_tbl(l_row_cnt).From_Cumulative_Quantity := v_component.from_cum_qty;
l_revised_item_tbl(l_row_cnt).Lot_Number := v_component.Lot_Number;
l_revised_item_tbl(l_row_cnt).Completion_Subinventory := v_component.Completion_Subinventory;
l_revised_item_tbl(l_row_cnt).Completion_Location_Name :='';
l_revised_item_tbl(l_row_cnt).Priority := v_component.Priority;
l_revised_item_tbl(l_row_cnt).Ctp_Flag := v_component.Ctp_Flag;
l_revised_item_tbl(l_row_cnt).New_Routing_Revision := v_component.New_Routing_Revision;
l_revised_item_tbl(l_row_cnt).Updated_Routing_Revision := '';
l_revised_item_tbl(l_row_cnt).Routing_Comment := v_component.Routing_Comment;
-- L1, the above is added for ECO enhancement
l_revised_item_tbl(l_row_cnt).Eco_For_Production := v_component.Eco_For_Production;
END LOOP;
END IF;
Eng_Eco_PUB.Process_Eco( p_api_version_number => 1.0
, p_init_msg_list => FALSE
, x_return_status => l_return_status
, x_msg_count => l_msg_count
, p_bo_identifier => 'ECO'
, p_eco_rec => l_eco_rec
, p_eco_revision_tbl => l_eco_revision_tbl
, p_revised_item_tbl => l_revised_item_tbl
, p_rev_component_tbl => l_rev_component_tbl
, p_ref_designator_tbl => l_ref_designator_tbl
, p_sub_component_tbl => l_sub_component_tbl
, p_rev_operation_tbl => l_rev_operation_tbl
, p_rev_op_resource_tbl => l_rev_op_resource_tbl
, p_rev_sub_resource_tbl => l_rev_sub_resource_tbl
, x_eco_rec => x_eco_rec
, x_eco_revision_tbl => x_eco_revision_tbl
, x_revised_item_tbl => x_revised_item_tbl
, x_rev_component_tbl => x_rev_component_tbl
, x_ref_designator_tbl => x_ref_designator_tbl
, x_sub_component_tbl => x_sub_component_tbl
, x_rev_operation_tbl => x_rev_operation_tbl
, x_rev_op_resource_tbl => x_rev_op_resource_tbl
, x_rev_sub_resource_tbl => x_rev_sub_resource_tbl
, p_debug => 'N'
, p_output_dir => l_output_dir
, p_debug_filename => l_debug_filename
dbms_output.put_line('after API call');
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('Return Status: '||l_return_status);
dbms_output.put_line('x_eco_rec.eco_name:'|| x_eco_rec.eco_name );
dbms_output.put_line('x_eco_rec.org_code:'|| x_eco_rec.organization_code);
IF (l_return_status = 'E') THEN
dbms_output.put_line('x_msg_count:' || l_msg_count);
Error_Handler.GET_MESSAGE_LIST(x_message_list => l_error_table);
DBMS_OUTPUT.PUT_LINE('Error Message Count :'||l_error_table.COUNT);
FOR i IN 1..l_error_table.COUNT LOOP
--DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':'||l_error_table(i).table_name);
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':');
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||substr(l_error_table(i).message_text,1,250));
END LOOP;
--ROLLBACK;
ELSE
DBMS_OUTPUT.PUT_LINE('==COMMITING==');
--COMMIT;
END IF;
DBMS_OUTPUT.PUT_LINE('=======================================================');
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('Exception Occured :');
DBMS_OUTPUT.PUT_LINE(SQLCODE ||':'||SQLERRM);
DBMS_OUTPUT.PUT_LINE('=======================================================');
RAISE;
END;Hi All,
We are on Oracle Applications Rel 11.5.8.
We are trying to update an existing ECO with an ‘UPDATE’ transaction_type using eng_Eco_pub API. Here is the code. We first execute this script with CREATE and ECO is created. However, when we run the same script to UPDATE with transaction_type = ‘UPDATE’, the bill_sequence_id in eng_revised_items is updated to g_miss_num (9.99E125). The API is returning ‘SUCCESS’ and updates the bill_sequence_id to 9.999E125. Not sure what we are missing here. Appreciate any inputs or sample code for UPDATING an already created ECO.
REVISED_ITEM_ID BILL_SEQUENCE_ID CHANGE_NOTICE
11668210 192981011 IK-API0316
REVISED_ITEM_ID BILL_SEQUENCE_ID CHANGE_NOTICE
11668210 9.99E125 IK-API0316
Thank You!
DECLARE
l_eco_name VARCHAR2(10) := 'IK-API0000' ;
l_org_code VARCHAR2(3) := 'GLO';
l_transaction_type VARCHAR2(10) := 'CREATE'; -- or UPDATE for updating the same ECO
l_rev_item_number1 VARCHAR2(20):= '16-2214-01';
l_eff_date DATE := NULL;
v_old_effective_date DATE;
l_new_revised_item_revision VARCHAR2(3) := '-A0';
l_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
l_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
l_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type ;-- := Eng_Eco_Pub.g_miss_revised_item_tbl;
l_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
l_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
l_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
l_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
l_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
l_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- API output variables
x_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
x_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
x_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type ;-- := Eng_Eco_Pub.g_miss_revised_item_tbl;
x_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
x_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
x_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
x_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
x_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
x_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
-- Other API variables for return status / error handling / debugging
l_error_table Error_Handler.Error_Tbl_Type;
l_return_status VARCHAR2(1) := NULL;
l_msg_count NUMBER := 0;
l_output_dir VARCHAR2(500) := '/apps/orarpt/SJDEV/utl';
l_debug_filename VARCHAR2(60) := 'test.dbg';
-- WHO columns
l_user_id NUMBER := -1;
l_resp_id NUMBER := -1;
l_application_id NUMBER := -1;
l_row_cnt NUMBER := 1;
l_user_name VARCHAR2(30) := 'CA_ADMIN';
l_resp_name VARCHAR2(30) := 'Engineering';
l_comp_eff_date date := null;
l_disable_date date := null;
BEGIN
-- Get the user_id
SELECT user_id,sysdate + 10,sysdate
INTO l_user_id,l_comp_eff_date,l_eff_date
FROM fnd_user
WHERE user_name = l_user_name;
-- Get the application_id and responsibility_id
SELECT application_id, responsibility_id
INTO l_application_id, l_resp_id
FROM fnd_responsibility_tl
WHERE responsibility_name = l_resp_name;
FND_GLOBAL.APPS_INITIALIZE(l_user_id, l_resp_id, l_application_id); -- Mfg / Mfg & Dist Mgr / INV
dbms_output.put_line('Initialized applications context: '|| l_user_id || ' '|| l_resp_id ||' '|| l_application_id );
dbms_output.put_line('before initialixe');
Error_Handler.Initialize;
l_return_status := NULL;
dbms_output.put_line('after initialixe');
-- FOR UPDATE API to update effectivity date on Revised item.
l_eco_rec.eco_name := l_eco_name;
l_eco_rec.organization_code := l_org_code;
l_eco_rec.change_type_code := 'DESIGN';
l_eco_rec.eco_department_name := NULL;
l_eco_rec.priority_code := NULL; --'Medium';
l_eco_rec.approval_list_name := NULL; --'SU_ONLY';
l_eco_rec.reason_code := NULL;
l_eco_rec.Approval_Status_TYPE := 5 ;-- 'Approved'; -- will default to Not submitted for Approval
l_eco_rec.Status_TYPE := 1; -- 1 to bring in SCHEDULE status
l_eco_rec.description := l_eff_date || ' - ECO - '||l_eco_rec.eco_name ;
l_eco_rec.transaction_type := l_transaction_type;
l_eco_rec.return_status := NULL;
IF l_transaction_type ='CREATE' THEN
l_revised_item_tbl(l_row_cnt).transaction_type := l_transaction_type; -- transaction type : CREATE / UPDATE
l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number1;
l_revised_item_tbl(l_row_cnt).new_revised_item_revision := '-A0'; -- pass only if the previous unimplemented updating ECO has a new revision
l_revised_item_tbl(l_row_cnt).Updated_Revised_Item_Revision := ''; -- l_new_revised_item_revision;
l_revised_item_tbl(l_row_cnt).start_effective_date := l_eff_date;
l_revised_item_tbl(l_row_cnt).new_effective_date := l_eff_date ; -- l_comp_eff_date;
l_revised_item_tbl(l_row_cnt).alternate_bom_code := null;
l_revised_item_tbl(l_row_cnt).status_type := 1; -- 'Open'
l_revised_item_tbl(l_row_cnt).change_description := l_rev_item_number1 || ' --B0 ECO - '||l_eco_rec.eco_name ;
l_revised_item_tbl(l_row_cnt).disposition_type :=1 ;
l_revised_item_tbl(l_row_cnt).update_wip := 1;--2
l_revised_item_tbl(l_row_cnt).mrp_active := 1;
--l_revised_item_tbl(l_row_cnt).new_item_revision:= '';
l_revised_item_tbl(l_row_cnt).new_routing_revision:= '';
l_revised_item_tbl(l_row_cnt).from_end_item_unit_number:= ''; -- this field is mandatory
l_revised_item_tbl(l_row_cnt).eco_for_production:=2;
l_revised_item_tbl(l_row_cnt).earliest_effective_date := l_eff_date;
l_revised_item_tbl(l_row_cnt).use_up_item_name := l_rev_item_number1; null;
--l_revised_item_tbl(l_row_cnt).use_up_plan_name :=null;
END IF;
IF l_transaction_type = 'UPDATE' THEN
FOR v_component in (SELECT * from eng_revised_items where change_notice = 'IK-API0000') LOOP
l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number1;
l_revised_item_tbl(l_row_cnt).new_revised_item_revision := '-A0';
l_revised_item_tbl(l_row_cnt).New_Revised_Item_Rev_Desc := '-F0 ik added';
l_revised_item_tbl(l_row_cnt).Updated_Revised_Item_Revision := '-F0';
l_revised_item_tbl(l_row_cnt).Start_Effective_Date := l_eff_date;
l_revised_item_tbl(l_row_cnt).New_Effective_Date := l_eff_date;
l_revised_item_tbl(l_row_cnt).Alternate_Bom_Code := v_component.alternate_bom_designator;
l_revised_item_tbl(l_row_cnt).Status_Type := v_component.status_type;
l_revised_item_tbl(l_row_cnt).Mrp_Active := v_component.Mrp_Active;
l_revised_item_tbl(l_row_cnt).Earliest_Effective_Date := sysdate;
l_revised_item_tbl(l_row_cnt).Requestor := '';
l_revised_item_tbl(l_row_cnt).Use_Up_Plan_Name := v_component.Use_Up_Plan_Name;
l_revised_item_tbl(l_row_cnt).Disposition_Type := v_component.Disposition_Type;
l_revised_item_tbl(l_row_cnt).Update_Wip := v_component.Update_Wip;
l_revised_item_tbl(l_row_cnt).Cancel_Comments := v_component.Cancel_Comments;
l_revised_item_tbl(l_row_cnt).Change_Description := 'TESTING ';
l_revised_item_tbl(l_row_cnt).Attribute_category := v_component.Attribute_category;
l_revised_item_tbl(l_row_cnt).Attribute1 := v_component.Attribute1;
l_revised_item_tbl(l_row_cnt).Attribute2 := v_component.Attribute2;
l_revised_item_tbl(l_row_cnt).Attribute3 := v_component.Attribute3;
l_revised_item_tbl(l_row_cnt).Attribute4 := v_component.Attribute4;
l_revised_item_tbl(l_row_cnt).Attribute5 := v_component.Attribute5;
l_revised_item_tbl(l_row_cnt).Attribute6 := v_component.Attribute6;
l_revised_item_tbl(l_row_cnt).Attribute7 := v_component.Attribute7;
l_revised_item_tbl(l_row_cnt).Attribute8 := v_component.Attribute8;
l_revised_item_tbl(l_row_cnt).Attribute9 := v_component.Attribute9;
l_revised_item_tbl(l_row_cnt).Attribute10 := v_component.Attribute10;
l_revised_item_tbl(l_row_cnt).Attribute11 := v_component.Attribute11;
l_revised_item_tbl(l_row_cnt).Attribute12 := v_component.Attribute12;
l_revised_item_tbl(l_row_cnt).Attribute13 := v_component.Attribute13;
l_revised_item_tbl(l_row_cnt).Attribute14 := v_component.Attribute14;
l_revised_item_tbl(l_row_cnt).Attribute15 := v_component.Attribute15;
l_revised_item_tbl(l_row_cnt).From_End_Item_Unit_Number := v_component.From_End_Item_Unit_Number;
l_revised_item_tbl(l_row_cnt).New_From_End_Item_Unit_Number := '';
l_revised_item_tbl(l_row_cnt).Original_System_Reference :=v_component.Original_System_Reference;
l_revised_item_tbl(l_row_cnt).Return_Status := '';
l_revised_item_tbl(l_row_cnt).Transaction_Type := l_transaction_type;
-- L1, the following is added for ECO enhancement
l_revised_item_tbl(l_row_cnt).From_Work_Order := '';
l_revised_item_tbl(l_row_cnt).To_Work_Order := '';
l_revised_item_tbl(l_row_cnt).From_Cumulative_Quantity := v_component.from_cum_qty;
l_revised_item_tbl(l_row_cnt).Lot_Number := v_component.Lot_Number;
l_revised_item_tbl(l_row_cnt).Completion_Subinventory := v_component.Completion_Subinventory;
l_revised_item_tbl(l_row_cnt).Completion_Location_Name :='';
l_revised_item_tbl(l_row_cnt).Priority := v_component.Priority;
l_revised_item_tbl(l_row_cnt).Ctp_Flag := v_component.Ctp_Flag;
l_revised_item_tbl(l_row_cnt).New_Routing_Revision := v_component.New_Routing_Revision;
l_revised_item_tbl(l_row_cnt).Updated_Routing_Revision := '';
l_revised_item_tbl(l_row_cnt).Routing_Comment := v_component.Routing_Comment;
-- L1, the above is added for ECO enhancement
l_revised_item_tbl(l_row_cnt).Eco_For_Production := v_component.Eco_For_Production;
END LOOP;
END IF;
Eng_Eco_PUB.Process_Eco( p_api_version_number => 1.0
, p_init_msg_list => FALSE
, x_return_status => l_return_status
, x_msg_count => l_msg_count
, p_bo_identifier => 'ECO'
, p_eco_rec => l_eco_rec
, p_eco_revision_tbl => l_eco_revision_tbl
, p_revised_item_tbl => l_revised_item_tbl
, p_rev_component_tbl => l_rev_component_tbl
, p_ref_designator_tbl => l_ref_designator_tbl
, p_sub_component_tbl => l_sub_component_tbl
, p_rev_operation_tbl => l_rev_operation_tbl
, p_rev_op_resource_tbl => l_rev_op_resource_tbl
, p_rev_sub_resource_tbl => l_rev_sub_resource_tbl
, x_eco_rec => x_eco_rec
, x_eco_revision_tbl => x_eco_revision_tbl
, x_revised_item_tbl => x_revised_item_tbl
, x_rev_component_tbl => x_rev_component_tbl
, x_ref_designator_tbl => x_ref_designator_tbl
, x_sub_component_tbl => x_sub_component_tbl
, x_rev_operation_tbl => x_rev_operation_tbl
, x_rev_op_resource_tbl => x_rev_op_resource_tbl
, x_rev_sub_resource_tbl => x_rev_sub_resource_tbl
, p_debug => 'N'
, p_output_dir => l_output_dir
, p_debug_filename => l_debug_filename
dbms_output.put_line('after API call');
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('=======================================================');
DBMS_OUTPUT.PUT_LINE('Return Status: '||l_return_status);
dbms_output.put_line('x_eco_rec.eco_name:'|| x_eco_rec.eco_name );
dbms_output.put_line('x_eco_rec.org_code:'|| x_eco_rec.organization_code);
IF (l_return_status = 'E') THEN
dbms_output.put_line('x_msg_count:' || l_msg_count);
Error_Handler.GET_MESSAGE_LIST(x_message_list => l_error_table);
DBMS_OUTPUT.PUT_LINE('Error Message Count :'||l_error_table.COUNT);
FOR i IN 1..l_error_table.COUNT LOOP
--DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':'||l_error_table(i).table_name);
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':');
DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||substr(l_error_table(i).message_text,1,250));
END LOOP;
--ROLLBACK;
ELSE
DBMS_OUTPUT.PUT_LINE('==COMMITING==');
--COMMIT;
END IF;
DBMS_OUTPUT.PUT_LINE('=======================================================');
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('Exception Occured :');
DBMS_OUTPUT.PUT_LINE(SQLCODE ||':'||SQLERRM);
DBMS_OUTPUT.PUT_LINE('=======================================================');
RAISE;
END; -
I always have the message : An older item already exist.
When I copy file (that is already on the server) from imacSnow 10.6.7 to server tiger10.4.11, I always have the message : An older item already exist. Even if the file have the same or earlier date. The server and the Imac have the same time and zone on their clock.
If you have problems with updating or with the permissions then easiest is to download the full version and trash the currently installed version to do a clean install of the new version.
Download a new copy of the Firefox program and save the DMG file to the desktop
* Firefox 5.0.x: http://www.mozilla.com/en-US/firefox/all.html
* Trash the current Firefox application to do a clean (re-)install
* Install the new version that you have downloaded
Your profile data is stored elsewhere in the Firefox Profile Folder, so you won't lose your bookmarks and other personal data.
* http://kb.mozillazine.org/Profile_folder_-_Firefox -
Item already locked by user error
Hi, I am getting the problem item already locked by User error when i try to edit a user idm 6.0 So, any solution for this?
The basic reason for this error is the object you are trying to access is already locked by another user (helpdesk/ proxy user or admin).
Generally you can check the lock status who has the active lock on the object from the lh console also.
http://identitycontrol.blogspot.com -
Item already defined at a high level in the product tree
Hi experts,
when I add a BOM into the system, says A is consisted of B and C, I click the button to add this BOM, but system tell me an error "Item already defined at a high level in the product tree. Row no. 2".
Row no 2 is item C, I check all my BOM, C is not contained in any BOM, and B is in another BOM but that BOM didn't contain C or A.
A is in a BOM, but in that BOM, there is no C. It's wreid why C already defined at a high level in the product tree. Thanks...Hi
Please wite following the querry and check
SELECT T0.[Code], T1.[Code] FROM OITT T0 INNER JOIN ITT1 T1 ON T0.Code = T1.Father WHERE T0.[Code] =[%0]
Ashish Gupte -
I am trying to install iTunes 12.0 on my Windows 7 PC to sync my iPhone6. I am getting error message, "Item already exists" on installation of iTunes 12.0. Apple has no fix. Help???
Item or object?
For "Object already exists" or "Access denied" errors when installing try opening Control Panel > Programs and Features > View installed updates then checking for Security Update for Microsoft Windows (KB2918614). Uninstall if you have it, then reboot and try installing again.
For general advice see Troubleshooting issues with iTunes for Windows updates.
The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
tt2 -
I have a problem regarding sales order line item with confimed quanity
Hi Experts,
I have a problem regarding sales order line item with confimed quanity with '0' with delivery block but confirming the sales order quantity once the order is released from credit check.
The situation arises as per the below scenarios.
Scenario - 1 - When the sales order has two line item - one line item with confirmed qunaity in the schedule line and for the 2nd line item there is no available stock for the Material xxxxxx.
Initially the sales order is created for the line item 2 with confirmed quantity = 0, and having the delivery block = 01 for the Material xxxxxx and the order is set with credit check. Once the order is relased from the credit check. The quanity for the item 2 where the confirmed quantity will be = 0 ( Where it is not changing the confirmed quantity)
Scenario -2- Updating the order qunaity for the line item 2 as (9Pcs) it will goes to credit check and save the order.
Maintain the stock for the line item 2 ( 5 Pcs).
Once the order is released from the credit check. Then for the line item 2 the confirm quanity will be seting to 5 Pcs with Delivery blcok 01.
This should not happen, When the credit check is released even though if it has stock based on the delivery blockl it should set the confirmed quanity to Zero.
Can you please help me how to solve this issue.
Looking forward for your reply.
Thanks and Regards,Hi,
I agree with your point. In the sales order When the complete delivery check box is enabled where the confimed qty is set to zero, it is fine but when we save the orderr it goes to credit check. Once we release the order using VKM3 where in the sales order the confimed quantity is setting to 5, But it should set to Zero quantity. Quatity should not be get confirmed it should be Zero Quantity.
Further in SPRO - customizing in the deliveries blocking reasons - It has a tick mark in the confirmation blcok. But we dont want to remove the - Confirmation Block tick mark
Please any one can help me if you have any solution to solve this problem.
Thanks and Regards. -
Problem with status-button in item view of ME21/22/23N
Hello ABAP,
i have to check for some conditions when a PO is saved, and due to those checks either save it or well, not.
This is working fine so far.
when you click check, or save, conditions get checked and window with errors pops up.
I´m using the normal error message procession used in SAPLMEGUI which i have to fill with thos three makros.
I just have one problem, my status button in item line doesnt get updated. i tried with a lot of metafields by now but it seems trial and error is not the way to go here.
any tips?requirement resolved.
solution follows:
DATA: lt_ytab TYPE TABLE OF ysdch_vbap_idnlf,
lt_data TYPE TABLE OF ymmch_check_idnlf_out, "added ID (TYPE INT4) Field to structure
lt_out TYPE TABLE OF char80.
DATA: ls_ytab TYPE ysdch_vbap_idnlf,
ls_mska TYPE mska,
ls_data TYPE ymmch_check_idnlf_out,
ls_out TYPE char80,
lv_row_end TYPE i VALUE 10.
CONSTANTS: lc_col_start TYPE i VALUE 10,
lc_col_end TYPE i VALUE 40,
lc_row_start TYPE i VALUE 10,
lc_title TYPE char80 VALUE
'Fehler, noch Bestand zu Liquidations/Annulationsaufträgen vorhanden'.
*~~~Get header data
ls_head = im_header->get_data( ).
*~~~Get item data
lt_items = im_header->get_items( ).
LOOP AT lt_items INTO lr_item.
ls_item = lr_item-item->get_data( ). "EKPO
"select liquidations/annulations orders for supplier material nr.
SELECT *
FROM ysdch_vbap_idnlf
INTO TABLE lt_ytab
WHERE /fis/idnlf = ls_item-idnlf.
LOOP AT lt_ytab INTO ls_ytab.
"now lets see which of those orders has order stock
SELECT SINGLE kalab kaspe
FROM mska
INTO CORRESPONDING FIELDS OF ls_mska
WHERE vbeln = ls_ytab-vbeln
AND posnr = ls_ytab-posnr.
IF ls_mska-kalab GT 0 OR ls_mska-kaspe GT 0.
ls_data-vbeln = ls_ytab-vbeln.
ls_data-posnr = ls_ytab-posnr.
ls_data-/fis/idnlf = ls_item-idnlf.
ls_data-kalab = ls_mska-kalab.
ls_data-kaspe = ls_mska-kaspe.
ls_data-meins = ls_item-meins.
ls_data-ebelp = ls_item-ebelp.
ls_data-id = ls_item-id. "saved ID for later processing
APPEND ls_data TO lt_data.
ELSE.
CONTINUE.
ENDIF.
ENDLOOP.
ENDLOOP. " lt_item
IF NOT lt_data IS INITIAL.
"we got annulation/liquidation orders with order stock for this material
"so popup a error message
LOOP AT lt_data INTO ls_data.
IF NOT ls_data-vbeln IS INITIAL AND NOT ls_data-posnr IS INITIAL.
mmpur_business_obj_id ls_data-id. "using other makro now and making use of ID
"using mmpur_business_obj_id instead of mmpur_business_obj_it
ENDIF.
mmpur_metafield mmmfd_item_number.
mmpur_message 'W' 'YMMCH' '110' ls_data-vbeln ls_data-posnr ls_data-ebelp ' '.
ENDLOOP.
ch_failed = 'X'.
ENDIF.
Edited by: Florian Kemmer on Sep 7, 2010 3:22 PM -
MI02 : new items for a document with item already counted
Dear.
I try to insert new items for an inventory document.
This document have items already counted.
The system send this error message M7706 : Items already counted (no new items possible).
Do you know a solution to avoid this error message ?
Thanks.M7706 is a hard coded error message, you cannot control it via message attributes.
What you can do is to do a re-count via transaction MI11 with reference to this inventory document. In this case you will be able to add new items, however, you have to enter the counted amounts for the existing items again.
But in my opoinion it's easier to create a new PID as suggested by Jurgen.
Maybe you are looking for
-
Need to calculate the number of records in an XML file
I need to find out how many records I have in an XML file. The file resides on a unix server and before doing anything with, i need to insert the record count into a separate table. Is there any function or procedure that can achieve this?
-
Hi there! I have two macbooks... I did a keynote presentation on one of them, and moved it to the other. Now the keynote won't open! - it says I need to launch an update, but I already did, and I also restarted my computer a number of times. I have t
-
Any call filtering on CallManager 4 or 5?
I know Cisco Personal Assistant will be fade out. I just wonder if there is any call filtering feature on CallManager so that end user can create their own call rules to block / permit the call etc (just like IPMA call filtering). Thanks for help.
-
How to learn JMF / JavaSound? sun docs no good
made you look... okay so maybe certain TECHNICAL docs at sun are updated, but many of the tutorials are not compatible, for a newbie, such as me, that does not help if you're a programmer, reading the docs can help... but not newbs ie: JMFProgrammers
-
I am considering purchasing FCE (and a macbook pro), but need to know a few things from users who have experience with it. First, is FCE totally compatible in terms of file sharing with FCP? I'm a beginer and need to learn editing. I just completed p