## Issue Details:-- In the OOB Install of 7.6.4 sp 2 SRM is not working properly. When you go chose a SR and fill out the information and try to save it you get a error message. See below for the filter log.

Thu Feb 02 2012 12:16:36.4800 */ <Filter Level:0 Number Of Filters:48> Checking "SRM:REQ:USM_UpdateUSMDataFromAtrium" (500)
<FLTR> <TID: 0000005216> <RPC ID: 0000052506> <Queue: Fast > <Client-RPC: 390620 > <USER: bbarbou1 > <Overlay-Group: 1 > --> Passed -- perform actions
<FLTR> <TID: 0000005216> <RPC ID: 0000052506> <Queue: Fast > <Client-RPC: 390620 > <USER: bbarbou1 > <Overlay-Group: 1 > 0: Set Fields
<FLTR> <TID: 0000005216> <RPC ID: 0000052506> <Queue: Fast > <Client-RPC: 390620 > <USER: bbarbou1 > <Overlay-Group: 1 > "The specified requestable offering <OI-944bc3c32c894b44ad26e43e63165ddf> was not found in <BMC.ASSET>.
<FLTR> <TID: 0000005216> <RPC ID: 0000052506> <Queue: Fast > <Client-RPC: 390620 > <USER: bbarbou1 > <Overlay-Group: 1 > **** Error while performing filter action: Error 191014
<FLTR> <TID: 0000005216> <RPC ID: 0000052506> <Queue: Fast > <Client-RPC: 390620 > <USER: bbarbou1 > <Overlay-Group: 1 > **** Filter "SRM:REQ:USM_UpdateUSMDataFromAtrium": No enabled error handler

When opening CMDB:USMAPIInterface form and put anything as a qualifier to retrieve some entries I get “Invalid Qualifier Encountered” It does not matter what I try the same message always appears.
If we look at BMC:Core:BMC_Offerings this offering code does not exist. Also we can not look at the actual service request to see what is wrong because of continued errors concerning USM data.
We are also getting warning messages from the SRM:Service Catalog Manager with notes that : Exception occur while retrieving USM data. (ARWARN 150502).

Legacy ID:KA366691

## Solution:-- It was a configuration issue.

-- The main cause of this is the RO Instance ID. The RO Instance ID is the ID for the RO that represents the SRD. This ID is related to default services defined by SRM.  You could relate another service/offering by using the fields on the SRD console.
-- In this issue, customer might have to deleted the RO either accidently and by some unknown reason that represents this SRD hence, to fix this we have to create a new RO within CMDB and then attach it to SRD, cause the RO is not there and it needs to be recreated. So, if we delete the SRD and recreated then it will create a new related RO.

==> So by all this customer need to:--
-- Take export of the SRD
-- Delete the SRD
-- Import it back with prefix
-- So then, they can see the data being populated again with RO instance ID, RO Recon ID and RO Dataset ID.
-- With above approach, it will create a new record in BMC.CORE:BMC_RequestableOffering and it resolved the issue.

1. BMC Service Request Management