3 Replies Latest reply on Mar 20, 2015 6:53 AM by 2718701

    What is the difference between "Public Tables" and "Internal Tables" in eTRM?


      Are "Internal tables" visible to the user via some form, can any query be done on these tables via frontend or backend?

      Or can a user store some data into these tables or they are just being used by the system as a caching mechanism?


      All the documentation states that "Internal Tables: This section includes a list of private, internal tables used by Oracle Projects; we do not provide additional documentation for these tables." So what does these tables actually do and are they needed from the end user/DBA perspective?


      (Please excuse if my question seems too basic, totally new to eTRM and E-Business Suite.)



        • 1. Re: What is the difference between "Public Tables" and "Internal Tables" in eTRM?
          Pravin Takpire

          You can always Query any table if you know the table name and have privileges. But for Internal Tables Oracle is not going to provide any documentation or information. Developers are not required to query these tables because the data would be available via some other views.



          1 person found this helpful
          • 2. Re: What is the difference between "Public Tables" and "Internal Tables" in eTRM?
            Cuauhtemoc Amox

            The private/public distinction is mainly due to Oracle managing them (through seeded code e.g. forms, stored procedures) and they could potentially change on new release, thus making any custom code fail and require modifications to account for such changes, The expectation is also to manage data through Oracle provided code (Forms/OAF for GUI, programs and APIs in the back end) and avoid at all cost direct SQL manipulation as this could break integrity.


            The expectation for public ones is for their structure to remain fairly stable and thus make your custom code less prone to require updates with new application versions. This are also expected to be manipulated by the customer as per their needs and this most likely refer to interface tables where you can insert new records for data conversions/interfaces and then update/delete depending on the results of processing them.


            From DBA perspective, they are all database objects and should be handled as usual, save for particular oracle recommendations depending on features implemented for the eBS (e.g. advanced compression, tablespace management).

            1 person found this helpful
            • 3. Re: What is the difference between "Public Tables" and "Internal Tables" in eTRM?

              Hi Cuauhtemoc Amox,


              Thanks! Your reply explained my queries in details and in very basic understandable form. Really appreciate your kind effort!


              I had just one last query that if the customer can insert new records in the public tables and say they enter some sensitive data like invoice-customer details, can these data in public tables (sensitive or not) move into any of the internal tables via some forms, stored procedures etc. at any point of time, or the internal tables will hold only the system/ release related information?


              Thanks again!