I'd like to know where I can find documentation about the tables and columns mapped by CA UNIVERSE to the MDB for Service Desk? I've looked in the CA SDM Details of the Tables displayed in r12.5 logical data model manual and I'm not finding what I need.
Unfortunately, there is not much documentation around the universe objects/classes themselves. Most of them are a bit self-explanatory by names. If you look into the properties of a given object, it'll give some information about the Select Statement or Where Clause its using, which inturn needs to be mapped manually by looking at the Logical data model.
There are some filters that might be referencing objects in classes, so you'd have to go look at the details of those objects to see what its really pulling.
Finally there's Derived Tables, which again have SDM logical name syntax associated to the tables/columns the table is created from.
This could be a great idea to be considered if there is good enough community demand on it.
I've looked into the properties of the object, it gave me the table name and the object name which our DBA can't find in the MDB. We can see that object in the derived universe and I can use that object in a report, but there doesn't seem to be a related column name in the database that we can find.
Maybe this link helps? https://wiki.ca.com/display/CASM1401/Objects+and+Attributes
If its a custom table, this approach might help. Look for NX_ROOT/site/ddict.sch or NX_ROOT/site/mods/*.sch files
You should see entries like this in that file:
p1 NR_Comment -> CURR_PROV nr_com ;
string to the right side of CURR_PROV is the real item in SQL Server / Oracle.
I looked in the site folder but there wasn't a file called ddict.sch and the .sch files in the mods folder didn't have anything like your describing.
Try to use bop_sinfo
bop_sinfo -q cr
this command should give you name of the physical name
instead of cr you can specify any other object that you looking for.
Where do I do that command?
CA SDM server cmd
That command works great for the cr ----> call_req but the field I'm trying to find is call Request_Area_Description in the universe, we can't find it in the db - the universe says it's in the 'cr' table and it is in the universe - does that make sense?
I totally forgot about another aspect.
Attribute Aliases. These are additional virtualized attributes that you can define in SDM so that it makes it a bit easier for reporting.
Service Desk -> Administration tab -> Service Desk -> Application Data -> Codes -> Attribute Aliases
Ok, I see it is an alias you can find them in SDM under administration tab ->Service Desk->application data->code->attribute alliases
you will see that this is alias for cr object attribute category
You can perform command
bop_sinfo -d cr |findstr category
you will get
category SREL -> pcat.persistent_id
so pcat is the factory you are looking for
bop_sinfo -q pcat
wil give you
Factory pcat < Prob_Category >
So Prob_Category is the table you looking for
Ok - I found the alias for request_area_description and it's call category.description - so do I put the entire string in the command
eg. bop_sinfo -d cr |findstr category.description
bop_sinfo -d cr |findstr category?
Since category is SREL attribute to pcat, and description is the attribute of pcat
give me description of the category that is related to the request
I think this should cover it:
C:\PROGRA2\CA\SERVIC1\sdk\websvc\R11>bop_sinfo -qd cr | findstr /i category
category SREL -> pcat.persistent_id
category_f LOCAL INTEGER
category_prev LOCAL SREL -> pcat.persistent_id
In your case you’re looking for category.description right?
SO, it would be pcat table’s description field:
C:\PROGRA2\CA\SERVIC1\sdk\websvc\R11>bop_sinfo -qd pcat | findstr /i description
Thanks Raghu, that helps a lot. I will show this to our DBA and see if she can find it in the pcat table in the db.
One more question, just curious - what does -d and -q and /I stand for?
There is no pcat table in database only Prob_Category
-q shows relation database name
Do you have any further questions on this topic?
If not, please mark Raghu's answer as correct
Thanks Paul, I marked Raghu's answer as correct.