Adding a "In Relationship" install base instance to a Repair Order

Hi,
When we try to add an install base instance to a Repair Order in Depot Repair, I'm not able to add a line for a unit that has an usage of "In Relationship". I checked the SQL and Depot Repair is not able to add such units.
We're able to return a unit that has an usage of "In Relationship" from Order Management as well as Service Request. Is there a way this can be done in Depot Repair.
Any help is very much appreciated.
Thanks,
Madan

I'm not sure the need is as obvious as you suspect.
The first problem I come to is "which user?". If the Service Request has 10 activities steps, from 10 different users, which of them is the Service Request Completed user? The only way this would be informative would be the rare service requests that have
no processes and must be handled manually, in which case the real fix is to create processes for these service requests so they don't need to be handled manually.
As to setting this: there's two big options:
the way this is set for Incidents is by the form controls. If you were to replicate that behavior, you'll probably want to add a custom control to the form that sets the completed user to the current console if the status has changed to completed during
that session, which is a lot of real SDK development work.
Alternatively, you could use a workflow that triggered on the status being changed from anything else to completed, and set this value based on the last user to edit this SR. I'd recommend doing this with a
custom workflow in PowerShell, but you could use Orchestrator, C# workflows, patrol scripts, etc.

Similar Messages

IB52: FM for adding partner to the Install Base

Hi,
My requirement is to add Service Contact (partner) on the Installed Base - IB52
How to add a Partner on to the Installed Base - which Function Module to use?
Thanks
Rajeev

Using following FMs:
ls_comp_det-OBJECT_GUID = ls_comm_product-product_guid.
CALL FUNCTION 'CRM_IBASE_COMP_FIND'
CRM_IBASE_COMP_CHANGE
BAPI_IBASE_SAVE
BAPI_TRANSACTION_COMMIT

Installed Base instance not created for Models(ATO/PTO).

Hi,
In the existing BOM for the PTO model I have attached the Warranty Item.
Generated a SO.
Now warranty gets created in service contracts, but when I query the SO in IB all the standard items show up but the Model Item does not show up.
Can some one tell me how we can create a component of relationship in IB for all the lines in the BOM with the Model Item as the parent.
Thanx.,
Surya.

Hi,
You would need to do relevant configuration in Account Identification Profile
The path for the same is
IMG -> CRM -> IC WebClient -> Master Data -> Define Account Identification Profile
You would need to add ICCMP_IBASE to your account identification profile.This can be done by selecting your account identification profile and double clicking "Object Components"
Regards,
Deepak

Installed Base Instance Creation from Order Import

Is it possible for the Order Import to create the product instances when it imports an Sales Order?
If it is; what should be done to achieve it?
Thanks.

I am sorry this issue did not resolved. Once I get answer for this will certainly post and share with all.

Is there a way for a SR Task to update the Install Base Status instance to Active

Release 12.1.3
When a field service install task is closed is there anyway for the Install Base instance on the SR to have its status updated to "Installed"?

Thanks Shachar.
I had tried using AEGP_GetEffectParamUnionByIndex and forgot to mention that in the original post, oops!
After you suggested it, I looked over it once again, but still couldn't find any promising/useful attributes.
It seems that the structs returned within the union don't have a parking spot for the ui_flags. I double checked this in AE_Effect.h, and it matches up with what I'm seeing in the xcode debugger.
Heres one example (Checkbox rom AE_Effect.h):
/** CheckBox -- PF_Param_CHECKBOX
typedef struct {
/* PARAMETER VALUE */
PF_ParamValue value;
/* PARAMETER DESCRIPTION */
PF_Boolean dephault;
A_char reserved; /* padding */
A_short reserved1;
union {
const A_char *nameptr;
} u;
} PF_CheckBoxDef;
So, they have a few attributes (name, default values, and current value) but no ui_flags. Bummer!
-Andy

Install Base Accounting Class code

Hi,
Iam using api csi_item_instance_pub.update_item_instance for updating Install base instance.
Iam able to update the partyid, account id but not accounting class code.
Can anyone please help me how to update accounting class code along with party information.
Any help is highly appreciated.
Here is my code which Iam using to update Item instance..
CREATE OR REPLACE PROCEDURE updateib_load_test
IS
g_instance_id_lst csi_datastructures_pub.id_tbl;
l_instance_rec apps.csi_datastructures_pub.instance_rec;
p_ext_attrib_values apps.csi_datastructures_pub.extend_attrib_values_tbl;
p_party_tbl apps.csi_datastructures_pub.party_tbl;
p_account_tbl apps.csi_datastructures_pub.party_account_tbl;
l_pricing_attrib_tbl apps.csi_datastructures_pub.pricing_attribs_tbl;
l_org_assignments_tbl apps.csi_datastructures_pub.organization_units_tbl;
l_asset_assignment_tbl apps.csi_datastructures_pub.instance_asset_tbl;
l_txn_rec apps.csi_datastructures_pub.transaction_rec;
x2_txn_rec apps.csi_datastructures_pub.transaction_rec;
l_return_status VARCHAR2 (100);
l_msg_count NUMBER;
l_msg_data VARCHAR2 (2000);
l_created_manually_flag VARCHAR2 (100);
----l_org_id NUMBER := 204;
n NUMBER := 1;
v_instance_id NUMBER;
p_commit VARCHAR2 (5);
p2_commit VARCHAR2 (5);
p_validation_level NUMBER;
p_init_msg_lst VARCHAR2 (500);
v_instance_party_id NUMBER;
v_ip_account_id NUMBER;
l_relationship_tbl apps.csi_datastructures_pub.ii_relationship_tbl;
v_relationship_id NUMBER;
v_success VARCHAR2 (1) := 'T';
x2_return_status VARCHAR2 (100);
x2_msg_count NUMBER;
x2_msg_data VARCHAR2 (2000);
p2_validation_level NUMBER;
p2_init_msg_lst VARCHAR2 (500);
a NUMBER;
t1_msg_dummy VARCHAR2 (1000);
t1_output VARCHAR2 (1000);
l_not_created NUMBER;
l_buffer VARCHAR2 (32767);
l_problem EXCEPTION;
l_message VARCHAR2 (2000);
CURSOR updateib_cur
IS
SELECT *
FROM ib_conv_stg
WHERE updateib = 'Y'
AND status_stg = 'V'
AND new_instance_number IS NOT NULL
AND transaction_id_stg = 8077;
BEGIN
-- DBMS_OUTPUT.put_line ('AFTER BEGIN');
apps.fnd_file.put_line (apps.fnd_file.LOG, 'AFTER BEGIN');
FOR updateib_rec IN updateib_cur
LOOP
BEGIN
l_instance_rec.accounting_class_code := fnd_api.g_miss_char;
IF p_party_tbl.EXISTS (1) IS NOT NULL
THEN
p_party_tbl.DELETE;
END IF;
IF p_account_tbl.EXISTS (1) IS NOT NULL
THEN
p_account_tbl.DELETE;
END IF;
IF p_ext_attrib_values.EXISTS (1) IS NOT NULL
THEN
p_ext_attrib_values.DELETE;
END IF;
/* SELECT apps.csi_item_instances_s.NEXTVAL
INTO v_instance_id
FROM SYS.DUAL;*/
l_instance_rec.instance_id :=
TO_NUMBER (updateib_rec.new_instance_number);
l_instance_rec.instance_number := updateib_rec.new_instance_number;
apps.fnd_file.put_line (apps.fnd_file.LOG,
l_instance_rec.instance_id);
l_instance_rec.object_version_number := updateib_rec.object_version;
apps.fnd_file.put_line (apps.fnd_file.LOG,
l_instance_rec.object_version_number
--l_instance_rec.inventory_item_id := updateib_rec.inventory_item_id;
l_instance_rec.inv_master_organization_id :=
updateib_rec.inv_master_organization_id;
--189;
l_instance_rec.mfg_serial_number_flag :=
updateib_rec.mfg_serial_number_flag;
--'Y';
--l_instance_rec.serial_number := updateib_rec.ls_serial_number;
---'LOG0005';
l_instance_rec.quantity := updateib_rec.quantity; --1;
l_instance_rec.unit_of_measure := updateib_rec.unit_of_measure;
--'EA';
l_instance_rec.accounting_class_code :=
updateib_rec.accounting_class_code;
apps.fnd_file.put_line (apps.fnd_file.LOG,
updateib_rec.new_instance_number
|| 'instance_rec'
|| l_instance_rec.accounting_class_code
|| 'updateib'
|| updateib_rec.accounting_class_code
--'CUST_PROD'; --'INV';
l_instance_rec.instance_status_id := updateib_rec.instance_status_id;
--510;
l_instance_rec.customer_view_flag := updateib_rec.customer_view_flag;
--'N'; --N
l_instance_rec.merchant_view_flag := updateib_rec.merchant_view_flag;
--'Y'; --Y
l_instance_rec.sellable_flag := updateib_rec.sellable_flag;
--'Y'; --N
--l_instance_rec.active_start_date := updateib_rec.active_start_date;
--SYSDATE;
l_instance_rec.location_type_code := updateib_rec.location_type_code;
--'HZ_PARTY_SITES';
l_instance_rec.location_id := updateib_rec.location_id; --375885;
l_instance_rec.install_date := updateib_rec.install_date;
--SYSDATE;
l_instance_rec.install_location_type_code :=
updateib_rec.install_location_type_code;
--'HZ_PARTY_SITES';
l_instance_rec.install_location_id :=
updateib_rec.install_location_id;
--375885;
--l_instance_rec.vld_organization_id :=
--updateib_rec.last_vld_organization_id;
--2104;
l_instance_rec.creation_complete_flag :=
updateib_rec.creation_complete_flag;
--'Y';
--l_instance_rec.object_version_number :=
--updateib_rec.object_version_number;
-- 1;
l_instance_rec.external_reference :=
updateib_rec.ls_external_reference;
l_instance_rec.instance_usage_code :=
updateib_rec.instance_usage_code;
l_instance_rec.inv_organization_id :=
updateib_rec.inv_organization_id;
l_instance_rec.inv_subinventory_name :=
updateib_rec.inv_subinventory_name;
l_instance_rec.inv_locator_id := updateib_rec.inv_locator_id;
l_instance_rec.manually_created_flag :=
updateib_rec.manually_created_flag;
l_instance_rec.last_oe_po_number := updateib_rec.last_oe_po_number;
l_instance_rec.instance_type_code :=
updateib_rec.ls_instance_type_code;
l_instance_rec.attribute3 := updateib_rec.ls_warranty_expiration_date;
--l_instance_rec.UPDATE_ORACLE:= updateib_rec.UPDATE_ORACLE;
-- ************* FOR PARTIES **********************************************************
/* SELECT apps.csi_i_parties_s.NEXTVAL
INTO v_instance_party_id
FROM SYS.DUAL;*/
p_party_tbl (1).instance_party_id := updateib_rec.instance_party_id;
p_party_tbl (1).instance_id :=
TO_NUMBER (updateib_rec.new_instance_number);
p_party_tbl (1).party_source_table :=
updateib_rec.owner_party_source_table;
--'HZ_PARTIES'; --
p_party_tbl (1).party_id := updateib_rec.owner_party_id;
--442143; --13478;
p_party_tbl (1).relationship_type_code := 'OWNER';
p_party_tbl (1).contact_flag := 'N';
-- l_party_tbl (1).active_start_date := updateib_rec.active_start_date;
--SYSDATE;
p_party_tbl (1).object_version_number :=
updateib_rec.object_version_p;
apps.fnd_file.put_line (apps.fnd_file.LOG,
p_party_tbl (1).object_version_number
-- *********** FOR PARTY ACCOUNT *****************************************************
/* SELECT apps.csi_ip_accounts_s.NEXTVAL
INTO v_ip_account_id
FROM SYS.DUAL;*/
p_account_tbl (1).ip_account_id := updateib_rec.ip_account_id;
p_account_tbl (1).instance_party_id := updateib_rec.instance_party_id;
p_account_tbl (1).party_account_id :=
updateib_rec.owner_party_account_id;
--755865;
p_account_tbl (1).relationship_type_code := 'OWNER';
--l_account_tbl (1).active_start_date := updateib_rec.active_start_date;
--SYSDATE;
p_account_tbl (1).object_version_number :=
updateib_rec.object_version_a;
apps.fnd_file.put_line (apps.fnd_file.LOG,
p_account_tbl (1).object_version_number
-- 1;
p_account_tbl (1).parent_tbl_index := 1;
p_account_tbl (1).call_contracts := 'Y';
-- ************************** TRANSACTION REC *****************************************
l_txn_rec.transaction_date := SYSDATE;
l_txn_rec.source_transaction_date := SYSDATE;
l_txn_rec.transaction_type_id := 1;
l_txn_rec.object_version_number := 1;
-- *************** API CALL *******************************************************
-- DBMS_OUTPUT.put_line ('BEFORE CREATE ITEM INSTANCE');
apps.fnd_file.put_line (apps.fnd_file.LOG,
'BEFORE UPDATE ITEM INSTANCE'
END;
BEGIN
fnd_msg_pub.initialize;
csi_item_instance_pub.update_item_instance
(p_api_version => 1.0,
p_commit => apps.fnd_api.g_true
--Defaults assigned in the package
p_init_msg_list => apps.fnd_api.g_true
--Defaults assigned in the package
p_validation_level => apps.fnd_api.g_valid_level_full
--Defaults assigned in the package
p_instance_rec => l_instance_rec,
p_ext_attrib_values_tbl => p_ext_attrib_values,
p_party_tbl => p_party_tbl,
p_account_tbl => p_account_tbl,
p_pricing_attrib_tbl => l_pricing_attrib_tbl,
p_org_assignments_tbl => l_org_assignments_tbl,
p_asset_assignment_tbl => l_asset_assignment_tbl,
p_txn_rec => l_txn_rec,
x_instance_id_lst => g_instance_id_lst,
x_return_status => l_return_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data
COMMIT;
apps.fnd_file.put_line (apps.fnd_file.LOG,
'AFTER UPDATE ITEM INSTANCE'
apps.fnd_file.put_line (apps.fnd_file.LOG, 'test' || l_msg_data);
/* apps.fnd_file.put_line (apps.fnd_file.LOG,
'test1'
|| apps.fnd_msg_pub.get
(l_lcv,
apps.fnd_api.g_false
IF l_return_status != apps.fnd_api.g_ret_sts_success
THEN
l_not_created := l_not_created + 1;
ROLLBACK;
RAISE l_problem;
END IF;
updating STATUS in stg table
BEGIN
IF l_return_status = 'S'
THEN
dbms_output.put_line('satus :'||l_return_status);
COMMIT;
END IF;
COMMIT;
END;
-------------exception l_problem
EXCEPTION
WHEN l_problem
THEN
IF (l_msg_count > 0)
THEN
l_buffer := '';
FOR l_lcv IN 1 .. l_msg_count
LOOP
l_message :=
apps.fnd_msg_pub.get (l_lcv, apps.fnd_api.g_false);
END LOOP;
END IF;
COMMIT;
END;
END LOOP;
END updateib_load_test;

Hi Nagamohan,
Thanks for your reply.
Iam using the Location type code 'HZ_PARTY_SITES'.
Actually Iam updating existing instance to update party information.
The existing instance has the accounting_class_code as 'CUST_PROD'.
I want to update accounting class code to 'INV' while updating party information.
Iam able to update party information but not able to update accounting class code.
When I digged into the api, csi_item_instance_pub.update_item_instance I found some code which was updating the accounting_class_code to null if there is party information to be updated. I think this is the reason Iam not able to update accounting class.
Please help me if there is any chance of updating accounting class code along with party information.
Thanks in advance

Oracle Install Base -Unable to find Expire relationship button

Hi Experts,
I am not able to find "Expire Relationship" button under Configuration Tab while trying to expire parent and child relationship in oracle install base for an intem instance.But for some item instance I am able to find the "Expire Relationship" button under Configuration Tab.
Can any one please let me know why the "Expire Relationship" button is available for some item and not available for some item instances.
Thank you.
Ravi S

Duplicate post.
Oracle Install Base -Unable to find Expire relationship button
Unable to find Expire relationship button

Install Base - Unable to find "Expire Relationship" button

Hi Experts,
I am not able to find "Expire Relationship" button under Configuration Tab while trying to expire parent and child relationship in oracle install base for an intem instance.But for some item instance I am able to find the "Expire Relationship" button under Configuration Tab.
Can any one please let me know why the "Expire Relationship" button is available for some item and not available for some item instances.
Thank you.
Ravi S

Duplicate post.
Oracle Install Base -Unable to find Expire relationship button
Unable to find Expire relationship button

Error while updating Instances in Install Base

Hi Experts,
I am using the "csi_item_instance_pub.update_item_instance" API to update the
instance details. when i change the owner party and it's contacts(transfer ownership), I am getting following errors.
1)Owner account for external parties is mandatory. Please provide a valid Account for the Owner Party - 1221238 for some instance.
Eventhough i verified the correct party id and it's account id, it shows the same errror.
2)For some cases, I am getting the error like "The Object Version Number passed does not match with the one existing in Installed Base tables" .
Any suggestions for the above will be a great help for me .
Thanks in advance,
Ravi.
Edited by: user11291639 on Oct 28, 2009 9:45 PM

Thanks you,
By this Note id:395136.1
Iam unable to find this Set profile 'HZ: Generate Events for DQM Real-Time Synchronization' to No
with this Note id:278422.1
We are unable to find this proifle option : HZ: Data Sharing and Security Enabled profile
we are using applications 11i.
please help to find this Profile option.
But with this note id:ID 395136.1
This is Working.
Query for HZ: DQM Synchronization Method profile. Set the value to Disable.
But iam facing proble while uploding data to DFF ,Error--SQL exception occurred during PL/SQL upload.
Thanks for the Support-
Sowmya.
Edited by: user13419037 on Aug 11, 2011 11:53 PM
Edited by: user13419037 on Aug 12, 2011 12:03 AM
Edited by: user13419037 on Aug 12, 2011 3:45 AM

Major/Minor Line Relationships in Oracle Service Contracts&Install Base.

Hi,
We have come across a scenario where, based on some business validations, Coverage of a Major Line needs to be TERMINATED.
So, In that case if the Major Line has child lines(Minor) within, then do we need to 'EXPIRE' the 'COMPONENT-OFF' relationship between the Major and its Minor's, which helps in synchronising the data in Service Contracts and the Install Base for that Major Line.
Any inputs would be of great help.
Thanks,
-Santosh.

yes, please define major and minor terms here. are you referring to model (major) and component (minor) relationship?
Also if you just remove component-of relationship, you will end up with orphans. is that ok from business perspective?
~Amol

How to update item instance in oracle install base?

Hi,
I have a doubt in updating item instance in oracle install base.
I am using a API named csi_item_instance_pub.update_item_instance for this. I want to update Party OWNER, party contacts, Current location,Install location, bill_to address,ship_to address..etc. When i try to update party owner, it is updating in csi_i_parties(col:party_id) as well as updating in csi_item_instance(owner_party_id). In csi_item_instance table,owner_party_id column is updated. but corresponding owner_party_account_id is not changed. I have given party_account_id to update in csi_ip_accounts table. It has changed in csi_ip_accounts table. But in csi_item_instance table(owner_party_account_id) is not changing. Can anybody help on how to change owner_party_account_id in csi_item_instance table please? Thanks in advance.
--Muruga
Edited by: Murugeshapps on Jul 1, 2009 12:07 AM

Out of the box, I don't think that there is any API or program to delete the records from csi_item_instances because deleting IB record affects many modules (like Inventory, Order, Service Contracts etc). IB records should be expired if they are created incorrectly and you can run Transaction History Purge program to delete all history records related to that item.
Thanks
Shree

Can we swap serial Numbers for an item instance in Install Base

Hi,
Can anyone please let me know if we can swap/replace serial number of an item instance in Install Base. If so, please let me know how to do it.
Thanks in Advance.

Oh, I did find where it is defined. It's a form function under Setup in Oracle Install Base Admin responsibility. I think you would have had it if you had CMRO installed.
Following are the values in the form:
Application Name: Complex Maintenance Repair and Overhaul
Transaction Typa: ITEM_SERIAL_CHANGE
Transaction Name: Item Serial Change
Description: Item Number and or Serial Number Change
In Out: Checked
Alka

Party-Relationships in Installed Base

Hi,
Can anybody highlight on purpose/uses/advantages of setting party relationships in Installed base.
What can be acheived by creating these relationships?
Regards,
Mohammed

hi,
You need to assign partner determination procedure to install base. First define partner determination procedure. Then assign it to your install base category. You can do the same in spro crm> master data> install base.
Now, after assigning pdp to install base category, when you will create install base and click on goto partner, you will get partner whose partner function you have used in partner determination procedure.
Best regards
Pankaj Kumar

Transfer the ownership of a particular Item Instance in Install Base

Hi Friends,
Can somebody help me figure out, the changing of ownership of a particular item instance in Install base terminates the relevant line in an active Service Contract. The status in Install base for the item still remains active for that particular contract. Also is it a standard functionality that the a new contract be created with the new owner automatically or does this needs to be driven through a custom API.
Thanks in advance for the help,
Kunal

Hi Martin.........
You can use OINM table. Here you get the date wise details of item cost and Instock...
Else you can use inventory Valuation table too upto To Date.
Its in Inventory Reports.......
Hope this table will help you.....
Regards,
Rahul

Our Client gave a requirement to mass update the additional attributes in Install base for instances in Release 11i.

Hi,
Our Client gave a requirement to mass update the additional attributes in Install base for instances in Release 11i.
So I tried the below code to update:
But getting the error:
The Object Version Number passed does not match with the one existing in Installed Base tables.
Can any one please help how to fix it.
Code:
declare
x_instance_rec CSI_DATASTRUCTURES_PUB.INSTANCE_REC;
p_ext_attrib_values CSI_DATASTRUCTURES_PUB.EXTEND_ATTRIB_VALUES_TBL;
p_party_tbl CSI_DATASTRUCTURES_PUB.PARTY_TBL;
p_account_tbl CSI_DATASTRUCTURES_PUB.PARTY_ACCOUNT_TBL;
p_pricing_attrib_tbl CSI_DATASTRUCTURES_PUB.PRICING_ATTRIBS_TBL;
p_org_assignments_tbl CSI_DATASTRUCTURES_PUB.ORGANIZATION_UNITS_TBL;
p_asset_assignment_tbl CSI_DATASTRUCTURES_PUB.INSTANCE_ASSET_TBL;
p_txn_rec CSI_DATASTRUCTURES_PUB.TRANSACTION_REC;
x_instance_id_lst CSI_DATASTRUCTURES_PUB.ID_TBL;
x_return_status VARCHAR2(2000);
x_msg_count NUMBER;
x_msg_data VARCHAR2(2000);
x_msg_index_out NUMBER;
t_output VARCHAR2(2000);
t_msg_dummy NUMBER;
p_validation_level NUMBER;
p_commit VARCHAR2 (5);
p_init_msg_lst VARCHAR2 (500);
cursor stg_tab_cur is select instance_id,Safety_line_type from gewind_ib_iea_values;
TYPE stg_tab IS TABLE OF gewind_ib_iea_values%ROWTYPE INDEX BY BINARY_INTEGER;
stg_tab_var stg_tab;
stg_tab_bin_int BINARY_INTEGER;
BEGIN
x_instance_rec.instance_id := FND_API.G_MISS_NUM;
x_instance_rec.object_version_number := FND_API.G_MISS_NUM;
p_txn_rec.transaction_id := FND_API.G_MISS_NUM;
p_txn_rec.transaction_date := SYSDATE;
p_txn_rec.source_transaction_date := SYSDATE;
p_txn_rec.transaction_type_id := 1;
stg_tab_bin_int :=0;
For gewind_ib_iea_values in stg_tab_cur LOOP
stg_tab_bin_int := stg_tab_bin_int + 1;
P_ext_attrib_values(stg_tab_bin_int).instance_id :=gewind_ib_iea_values.instance_id;
P_ext_attrib_values(stg_tab_bin_int).attribute_id := 10023;
P_ext_attrib_values(stg_tab_bin_int).attribute_value := gewind_ib_iea_values.Safety_line_type;
dbms_output.put_line(P_ext_attrib_values(stg_tab_bin_int).instance_id);
dbms_output.put_line(P_ext_attrib_values(stg_tab_bin_int).attribute_value);
csi_item_instance_pub.update_item_instance(
1.0,
p_commit,
p_init_msg_lst,
1,
x_instance_rec,
p_ext_attrib_values,
p_party_tbl,
p_account_tbl,
p_pricing_attrib_tbl,
p_org_assignments_tbl,
p_asset_assignment_tbl,
p_txn_rec, x_instance_id_lst,
x_return_status,
x_msg_count,
x_msg_data);
commit;
-- Output the results
if x_msg_count > 0 then
for j in 1 .. x_msg_count
loop
fnd_msg_pub.get ( j , FND_API.G_FALSE , x_msg_data , t_msg_dummy );
t_output := ( 'Msg' || To_Char ( j ) || ': ' || x_msg_data );
dbms_output.put_line ( SubStr ( t_output , 1 , 255 ) );
end loop;
end if;
dbms_output.put_line('x_return_status = '||x_return_status);
dbms_output.put_line('x_msg_count = '||TO_CHAR(x_msg_count));
dbms_output.put_line('x_msg_data = '||x_msg_data);
COMMIT;
end loop;
END;
Regards,
Ravichander

This question is Assumed Answered -- It would be great if you could share the solution with us.
Thanks,
Hussein

Adding a "In Relationship" install base instance to a Repair Order

Similar Messages

Maybe you are looking for