Multiple Installed Base Instances are created for a NonSerialized Item when the Order Quantity > 1

8/21/2014
0 Comments
Scenario:
Create a Sales Order for a non-serialized item with quantity more than 1-> Ship it -> Multiple IB
records created
Cause:
The System Profile 'CSI: Auto-split Instances During Instantiation' is used to auto split
instances with multiple quantity to 1 per instance at time of instance creation.
0 Comments

Item is shipped in Oracle Order Management but IB is not

created
8/19/2014
0 Comments
We usually come across this scenario where Item is shipped in Oracle Order Management and
the order line is closed but IB is not created.
Below listed are possible checks that can be done to debug the reasons for this.
1. Item Setup
Is your item set up as IB trackable?
An item needs to be set up as IB trackable in Master and every child inventory org in order to
interface the item's transaction to Oracle Installed Base.
Check from form:
INVENTORY (R) > Item > Organization Item > Service Tab > Attribute: Installed Base

Trackable
Check using query:
SELECT segment1, organization_id, comms_nl_trackable_flag
FROM mtl_system_items_b
WHERE segment1 = '&your_item_number';
2. Validate Shipment
Does your Order Management shipment go through the inventory interface for a shippable item?
Although your order line is closed, the inventory interface (kicked off from ship confirm trip stop
interface) may not complete. Only after the inventory interface
is completed will the transaction be sent to the Installed Base interface.
Check from form
INVENTORY -> Transactions -> Material Transactions
Pick up your shipping organization
Query by Source = Sales Order, Source Id = Sales Order Number
You will see your Order Issue transaction here if your inventory interface is completed.
Write down transaction_id for use in upcoming steps.
Check using query:
SELECT transaction_id
FROM mtl_material_transactions
WHERE trx_source_line_id = &order_line_id
AND transaction_type_id = 33;
If you don't see your transaction, please check why the transaction is pending in the inventory
interface process.
Check from form:
INVENTORY (R) > Transactions >Transaction Open Interface
INVENTORY (R) >Transactions > Pending Transactions
Check using query:
SELECT process_flag, error_code, error_explanation
FROM mtl_transactions_interface
WHERE trx_source_line_id = &order_line_id
AND transaction_type_id = 33;

SELECT process_flag, error_code, error_explanation

FROM mtl_material_transactions_temp
WHERE trx_source_line_id = &order_line_id
AND transaction_type_id = 33;
3. Message in Event Queue
For a shippable item, does the transaction from inventory publish a message to the Event queue?
After completing the above three steps, your OM shipment transaction should publish (send) a
message to the Service Fulfillment Manager Event queue.
Check using query:
SELECT msg_code, msg_status, msg_creation_date, body_text
FROM xnp_msgs
WHERE dbms_lob.instr(body_text, '&transaction_id') <> 0
[****&transaction_id is inventory transaction_id for sales order issue and the one you get from
step 2]
If the above query returns no row, then your message has not been published.
To find out why the message is not published, set up the CSI debug option through the following
Profile options
CSI: Debug Level = 10
CSE: Debug = Y
CSI: Log File Path = < a valid value from 'utl_file_dir' parameter> ;
Do one more OM shipment transaction, and review the csi debug file called csiinv.hook.dbg.
This file will tell you why the message failed to publish to
SFM Event queue.
If the transaction for some reason did not publish in SFM, you can use following script to
republish it.
declare
l_header_id number;
l_mtl_txn_id number := &Transaction_ID;
l_return_status varchar2(1) := fnd_api.g_ret_sts_success;
begin
csi_inv_txn_hook_pkg.postTransaction(
p_header_id => l_header_id,
p_transaction_id =>l_mtl_txn_id,

x_return_status =>l_return_status);
end;
/
4. Check SFM
Is the SFM Event Manager Queue Service up and running?
If your message is published to SFM and your SFM Event Manager Queue Service is up and
running, the transaction will go to Install Base unless the message failed
when being processed.
Check from form to make sure SFM is running
SFM System Administrator(R) > Administration > Queue Console > Services
You should see your SFM Event Manager Queue Service has 1 in both Actual and Target. If not,
your SFM is not up and running.
Check using query to make sure message is not failed
SELECT msg_code, msg_status, msg_creation_date, body_text
FROM xnp_msgs
WHERE dbms_lob.instr(body_text, 'MTL_TRANSACTION_ID') <> 0
AND dbms_lob.instr(body_text, '&transaction_id') <> 0
(&transaction_id is the one you get from step 2)
5. Transaction in SFM
Did the transaction go through SFM sucessfully?
If your SFM is up and running, but the transaction has failed in SFM.
Query results returned from step 4 will have a msg_status = 'FAILED' or 'REJECT'.
To reprocess an individual erred message, go to your Notification Inbox:
Use SFM System Administrator Responsibility:
Nav: Operations -> Notifications
- Click on 'View Details'
- Review and resolve the error
- Click on 'Respond'
- Select Action 'Retry Messages'
- Click OK
The message should now disappear from your Notification Inbox and will have a status of

'READY'. These messages will be re-queued to be processed by the SFM Event Manager Queue
To reprocess all failed messages, you can run the concurrent program
Use SFM System Administrator Responsibility:
Nav: Concurrent -> Run Requests > XDP Resubmit Failed Messages
If the message still fails after resubmition, report to Oracle Support with the detailed error
message in body_text column from step 4 query
6. Transaction error in Installed Base Interface
If the transaction goes through SFM without a problem, and you still do not
see the Item Instance updated in Install Base, check if the transaction erred in
the Transactions Error Processing form.
Check from form:
Oracle Installed Base Admin(R) > Transaction errors Re-processing
Check using query:
SELECT processed_flag, error_text
FROM csi_txn_errors
WHERE inv_material_transaction_id = &transaction_id
(&transaction_id is the one you get from step 2)
7. Check Invalid CSI objects
If you have any errors in step 6 and 7, check if you have any invalid 'CSI' objects.
If yes, recompile them and resubmit the error transaction.
Mark error transactions to be processed by setting Process Flag and Submit the program,
Resubmit Interface Process concurrent program with 'Selected' as parameter.
0 Comments

ORA-06508: PL/SQL: could not find program unit being

called in Package CSI_ITEM_INSTANCE_PUB Procedure
GET_ITEM_INSTANCES - Resubmitting Error
Transactions

8/19/2014
0 Comments
This error occurs usually after applying any CSI related patch that affects CSI forms.
Below solutions shows the process to resubmit such error transactions.
Solution:
1. Recompile any invalid objects
select object_name, object_type
from all_objects
where status = 'INVALID'
and object_name like 'CSI%'
and owner = 'APPS';
2.

Restart SFM

3. Using the Transactions Error Processing form in the Install Base Administrator
responsibility, check Process Flag against the transactions that need to be resubmitted.
Remember the transaction_id of these transactions.
4.

Submit the Resubmit Interface Process concurrent program with Selected as parameter.

This would ensure it runs only for the transactions that have the process flag checked.
5. Re-query the transactions using the transaction_ids captured earlier.
0 Comments

Add/View attachments in Oracle Installed Base-R12

6/3/2014
0 Comments

0 Comments

R12 Field Service: Query to troubleshoot why Service

Activity Code is missing in the List Of Values on a Debrief
Material Transaction
2/17/2014
0 Comments

tDownload

File

Query in attached file can be used to identify which of the flags are not set as expected during
setup.
Below are the source location to correct setup where ever required.
cs_transaction_types_vl cttv:
Field Service Dispatcher -> Service Request -> Setup -> Charges -> Service Activities and
Billing Types
cs_txn_billing_types ctbt:
Field Service Dispatcher -> Service Request -> Setup -> Charges -> Service Activities and
Billing Types
cs_bus_process_txns cbpt:
Field Service Dispatcher -> Service Request -> Setup -> Charges -> Service Business Process
cs_business_processes cbp:
Field Service Dispatcher -> Service Request -> Setup -> Charges -> Service Business Process
csi_txn_sub_types ctst:
Oracle Install Base Admin -> Setups -> Transaction Types
csi_txn_types ctt:
Oracle Install Base Admin -> Setups -> Source Transaction Types
csi_instance_statuses:
Oracle Install Base Admin -> Setups -> Instance Statuses
0 Comments

Query to fetch list of Service Contracts linked to IB

11/20/2013
0 Comments
For a covered product, one first relates the contract to the install base and then the install base to
the item. In such a case, the column OBJECT1_ID1 will refer to the install base id. The item id
on the install base record then relates to the inventory record.
Contract modifier can be used as you can have more than one contract with the same contract

number. The combo of number/modifier has to be unique, so if you use the combo you know you
get 1 contract.
SELECT kl.line_number, ks.NAME, i.segment1
FROM okc_k_headers_b kh,
okc_k_lines_b kl,
okc_k_items ki,
okc_line_styles_v ks,
csi_item_instances c,
mtl_system_items_b i
WHERE kh.contract_number_modifier IS NULL
AND kh.ID = kl.dnz_chr_id
AND kh.ID = ki.dnz_chr_id
AND kl.ID = ki.cle_id
AND kl.lse_id = ks.ID
AND ki.jtot_object1_code IN ('OKX_CUSTPROD')
AND c.last_vld_organization_id = i.organization_id
AND TO_NUMBER(ki.object1_id1) = c.instance_id
AND c.inventory_item_id = i.inventory_item_id
0 Comments

What is the use of profile option, "CSD: Validate bill-to and

ship-to before opening Service Request"?
3/20/2013
0 Comments
When profile is set to Yes then the Service Request is validated for 'bill-to' and 'ship-to'
addresses, and a proper message is shown if 'bill-to' or 'ship-to' is missing.
After showing messages the Repair Order form is closed. The user then has to go to the Service
Request form and enter the missing address in order to open the Service Request in Repair Order
from.
When profile is set to No or Null then the Service Request is not validated for missing 'bill-to' or
'ship-to' address and the user can open the Service Request in the Repair order form.
******************************************************************************
********************************************************************
When creating a Service Request using Installed Base product the Bill To & Ship To information
in Contacts/Addresses tab of Service Request form is defaulting from Customer, not from
Installed Base.

Is it possible to default the Bill To and Ship To addresses from Installed Base record instead of
from Customer?
Answer is Yes
In 11i the application does not allow users to default Bill To and Ship To addresses from Installed
Base.
Also, for addresses belonging to Related Parties, the Relationship between Parties have to
established in the Contact Center > Relationships tab first.
The ability to default the Bill To and Ship To address from Installed Base has been added in
12.1.2 (Enhancement Request (ER) BUG:5585944 CSXSRISR BILL TO AND SHIP TO
ADRESSES NOT POPULATED FROM INSTALL BASE).
Additional code has been added to handle that functionality and there is also a new profile called
'Service: Default Bill To and Ship To Address Options' with the following options:
- Default from Customer
- Default from Installed Base
0 Comments

Install Base Open Interface-records not processed-fixes

2/18/2013
0 Comments
Sometimes the Install Base Open Interface program completes execution with no errors reported
but also there are no records processed.
Possible Solutions:
You can include the Source System Name parameter on the next run to correct the
problem.
(or)
The Open Interface program was failing because Install Base was not properly setup on the test
environment. The Install Parameters had not been set.
The following query returned 0 rows:
SELECT * FROM csi_install_parameters

Complete Install Parameters setup as per Oracle Installed Base Implementation Guide and
retest.
(or)
If the HZ_PARTIES table contains multiple records with the same party name each will have a
unique party number so the 1 to 1 relationship is from party number and not party name. The
user must uniquely identify the party so the party number MUST be supplied as well as the party
name - the error will then not occur.
The error can be worked around by ensuring that the csi_i_party_interface table is
populated with party_name AND party_number and not just party_name
0 Comments

Install Base Open Interface program

2/18/2013
0 Comments
Below is the process of running the Install Base Open Interface program
Step1: Load Interface Tables
Step2: Run Install Base Open Interface Program
Step3: Confirm Records Created Successfully
Read More
0 Comments

Oracle Install base- How To Change The Default

Organization Used When Creating Item Instances In Install
Base
2/18/2013
0 Comments
You can set the default organization on the Install Base item instance creation screen by
changing the profile option, "Service: Inventory Validation Organization"