The Client over here was trying for an upgrade, so we were trying to list out versions with overrides for estimation purposes. Then we started off with F983051, just to find out that there’s not a single field which would let us know that it has a version override.
Finally on web search, and from Oracle Metalink Documents we found that the RDASPEC information is updated locally in the TAM spec when the version override is created, and then in Central Objects when the version is checked-in.
Whenever a new version is created, if no overrides are performed, only one RDASPEC record is created with a Record Type of ’1′. If additional overrides are performed on the version, then additional RDASPEC records are created. For example, if the user performs data selection overrides, then records are created in the RDASPEC for that report/version with record type 7 with the selection overrides for the version. If section layout overrides are performed, multiple records with record type 3 are created in the RDASPECS. If data sequencing changes are made, then record type 6 records are created in TAM spec and if event rule overrides are performed, record type 16 records are created.
This same information can be seen in the Central Objects when the version has been checked in. If no overrides exist for the version, there will be only one record in the F98761 RDASPEC central object table with the report name in RSOBNM, the version name in RSVERS and a record type RSRCRDTP of ’1′. However, for additional overrides, additional records are written to the central object table with the corresponding record type for the type of override.
At runtime the system looks at the RDASPEC for the version and, depending on the records that exist for
the version, it knows what overrides have occurred on the version and pulls the appropriate override information. Any record types that do not exist at the version level are then pulled from the report template
There is not a standard report or simple inquiry that can be performed to see all versions with overrides. The easiest way to determine this information would be to look at the F98761 table in the central objects data source and find all records with a specific version name that have record types other then just 1. This would indicate some type of override was performed on the object. Depending on the value in the record type field (RSRCRDTP) you can determine what type of override exists for the version. You can also use the Universal Table Browser (UTB) and add the setting of “TAMMENUS=Show” in the [INTERACTIVE RUNTIME] section of the jde.ini to be able to view local TAM spec information and central object information from UTB.
Based on testing and review of the RDASPEC records, the record types are the following:
1 = Base Record
2 = Sections (will have one type 2 record for each section of a report)
3 = Report objects (one record for each report variable and constant on the report)
4 = Column calculation defined on tabular sections
5 = Subsection join (defines join information between sections)
6 = Data Sequencing (will have one record for each data item included in data sequencing)
7 = Data Selection (will have one record for each data item included in data selection)
8 = Database output (one record indicating destination for output -filename)
9 = Database output (one record for each mapping in database output)
10 = Row on tabular section (one record for each row)
11 = Cell on tabular section (one record for each cell)
13 = Row calculation defined on tabular section
16 = Event rule overrides performed at version level
17 = Row on tabular section (record for defined row criteria
18 = Cell on tabular section (record for defined cell criteria)
19 = Column data selection on tabular section
20 = Column and row overrides (tabular section only)
Source: Oracle Documentation/Knowledge Garden