When you create a partner application, its data and structure are stored in the database with which you configure the PAD. The application is created with 2 schemas in the database similar to the name below.
1. “app name separated by lower punctuation”
2. “application name separated by lower punctuation”_desk
For example, if the name of your application is “go expense contributor”, there will be 2 schemas in the database for this application.
1. go_expense_contributor: contains the detailed structural information of the application. Everything you see, be it the application jobs under job management or the access details of the electronic list items, is stored in this schema.
2. go_expense_contri_table: contains the publication tables and their structural details.
The important tables to consider in this schematic are specified below.
AdminOption-
this table contains all administrator details such as application PAD name, PAD GUID, PAD Namespace, Sql / other database file location, import details (block size, location, options etc.) , application display name, current users, database version, etc.
You can change the application display settings or other details by updating this table.
IM_ tables-
Instant messaging tables are import tables. When you want to load data from some external source, for example a file or a database, use instant messaging tables as a staging area for loading data.
An IM_ table is created for each cube in the application. If there are 5 cubes in the application. There will be 5 IM_ tables, one for each.
The instant messaging tables can be loaded from a database or from a text file. To load the data from a text file, you can use the “Import Data” function in CAC.
To load the data from a database, you must use SQL to insert the data into the IM_ tables.
IE_ tables-
There is one IE table per analyst model cube. These tables store the details of the import error.
NodeState table-
This table is used to save and review the nodes of the electronic list in the web partner. Annotation information, edit user information (eg date, time, GUID), lock information, etc. is stored in this table. The data of the nodes of the electronic list is saved in xml format.
Job table
This table contains a row for each job currently in the contributor job management (CAC) tree node
_desk
As I mentioned before, the hosts in this schema publish tables and their structural details. There are mainly 3 types of tables to consider.
And_tables-
These are publish tables and 1 table is created for each published cube.
It_ tables-
These contain the structural details of the publication tables and a table is created for each dimension of the published cube.
Cy_ tables-
These contain the structural details of the publication tables and a table is created for each dimension of the published cube.
Sy_ tables
These are system tables and contain the structural details of the publish tables and a table is created for each dimension of the published cube.