catalog for the system attributes max limit for all system objects

[VENKITTA SUBRAMANIAN]

Just checking the community if there is any documentation or SQL query available to get the list of Max size for each system attributes for all system objects.

Ex:  Risk Description - Max. 250 Characters ; Project Name: Max. 80 Characters, Investment ID:20 Characters, Project Description - 762

Any pointer is greatly appreciated

Thanks
-Venkitta

[Suman Pramanik]

Hi Venkitta

There is not one place but if you look at the datatype of each attribute we go by that. So if you run the PPM Schema report you will be able to get the Column details 

------------------------------
Thanks & Regards
Suman Pramanik
Sr. Principal Support Engineer | Customer Success & Support, Enterprise Software Division
Broadcom
------------------------------

[VENKITTA SUBRAMANIAN]

Thanks Suman for the quick response.

Ex:  Project Code (unique_code) has varchar2(60) but the Max size 20 characters. 

So, the only option is, we have to manually check the max size for each system attribute?

[Nick Darlington]

To account for triple-byte UTF characters required for globalization the database has space reserved for 3x the amount of characters in the Clarity UI.  Hence varchar2(60) = 20 UI characters allowed.

[Nick Darlington]

Also if you are On Premises with access to the installation files, definitions of almost all system attributes are to be found in the /META-INF/component/omd folder xml files.

For example, investment code from /META-INF/pma/omd/investment.xml size of 20:

<attribute code="unique_code" table="INV_INVESTMENTS" column="code" dataType="string" dataSize="20" editable="true" unique="true" required="true" dwEnabled="true" apiAlias="code" apiDefaultGroup="true">
    <nls languageCode="en" name="Investment ID" description="Investment Unique Name"/>
</attribute>

This reveals the data sizes acceptable to the application regardless of the requirements placed upon the backend to be able to hold all encoded data of that type.

[VENKITTA SUBRAMANIAN]

Thanks Nick but Unfortunately, we are in SaaS.

[Nick Darlington]

For the most part then you'll just have to take the database field size and divide by 3 then.  The majority (if not all) user-editable text fields with a fixed size are set this way.

[VENKITTA SUBRAMANIAN]

Thanks