| SchemaSpy Analysis of openpetra_trunk.publicOpenPetra Version 3 Database | Generated by SchemaSpy |
| Generated by SchemaSpy on Mi Nov 09 18:02 MEZ 2011 | |
| Database Type: PostgreSQL - 9.1.1 |
|
XML Representation Insertion Order Deletion Order (for database loading/purging scripts) |
| Table | Children | Parents | Columns | Rows | Comments |
|---|---|---|---|---|---|
| a_account | 60 | 6 | 26 | 259 | Details about each account code within a ledger. Also holds information on the summary account structure for reporting. |
| a_account_hierarchy | 2 | 4 | 8 | 1 | hierarchy of accounts; what is the root account of the hierarchy |
| a_account_hierarchy_detail | 7 | 10 | 258 | the elements of the hierarchy of accounts; which account is reporting to which other account | |
| a_account_property | 6 | 9 | 2 | Properties and optional values for an account can be saved in this table. | |
| a_account_property_code | 1 | 2 | 7 | 3 | Extra properties that might want to be saved with an account can be defined in this table. |
| a_accounting_period | 12 | 3 | 11 | 20 | Information about each financial period in a ledger. |
| a_accounting_system_parameter | 3 | 24 | 1 | One record describing the limitations imposed on the accounting system. | |
| a_analysis_attribute | 15 | 7 | 10 | 0 | Indicates which accounts use analysis attributes and what attribute types may be used with the account. Analysis attributes are user-definable extra information to be stored against an account. |
| a_analysis_store_table | 2 | 6 | 0 | List of tables in the financial system, meant to be used with analysis attributes. Not available. | |
| a_analysis_type | 2 | 2 | 11 | 0 | Types of analysis attributes. |
| a_ap_anal_attrib | 13 | 11 | 0 | Analysis Attributes applied to an AP for posting to the GL. | |
| a_ap_document | 9 | 6 | 21 | 0 | This is either an invoice or a credit note in the Accounts Payable system. |
| a_ap_document_detail | 3 | 9 | 15 | 0 | An invoice or credit note consists out of several items, or details. This table contains all these details. |
| a_ap_document_payment | 7 | 9 | 0 | This table links the different payments to actual invoices and credit notes. | |
| a_ap_payment | 2 | 6 | 14 | 0 | Records all payments that have been made against an accounts payable detail. |
| a_ap_supplier | 1 | 4 | 17 | 0 | This table defines the concept of a supplier in the AP system and is the centre of the AP system. |
| a_ar_article | 3 | 4 | 11 | 0 | defines an item that can be sold or a service that can be charged for; this can be used for catering, hospitality, store and fees; it can describe a specific book, or a group of equally priced books |
| a_ar_article_price | 2 | 4 | 9 | 0 | assign a price to an article, which can be updated by time |
| a_ar_category | 3 | 2 | 8 | 0 | there are several categories that are can use invoicing: catering, hospitality, store and fees |
| a_ar_default_discount | 5 | 10 | 0 | defines which discounts should be applied by default during a certain event or time period to articles from a certain category | |
| a_ar_discount | 8 | 5 | 23 | 0 | defines a discount that depends on other conditions or can just be assigned to an invoice or article |
| a_ar_discount_per_category | 5 | 8 | 0 | defines which discount applies to which category to limit the options in the UI | |
| a_ar_invoice | 6 | 8 | 17 | 0 | the invoice (which is also an offer at a certain stage) |
| a_ar_invoice_detail | 3 | 12 | 17 | 0 | an invoice consists of one or more details |
| a_ar_invoice_detail_discount | 7 | 10 | 0 | defines which discounts apply one invoice item | |
| a_ar_invoice_discount | 6 | 9 | 0 | defines which discounts apply directly to the invoice rather than the invoice items; this can depend on the customer etc | |
| a_batch | 6 | 3 | 18 | 19 | Store current and forward period general ledger batches for a ledger. |
| a_budget | 1 | 10 | 14 | 0 | Budget information for cost centre-account combinations. |
| a_budget_period | 3 | 11 | 0 | This is the budget data for one period (e.g. a month) | |
| a_budget_revision | 3 | 2 | 9 | 0 | This defines a certain revision of a budget in a ledger in a year. |
| a_budget_type | 2 | 3 | 8 | 5 | Used for initial set up of budgets, for how to calculate amounts for each period. Some possible types are adhoc,same,percentage of annual. |
| a_corporate_exchange_rate | 4 | 10 | 0 | Hold (monthly) corporate rates. | |
| a_cost_centre | 46 | 6 | 17 | 8 | Master cost centre records which contain details of each cost centre and their relationship to each other; determines the cost centre structure. |
| a_cost_centre_types | 2 | 3 | 9 | 2 | Stores standard and user-defined cost centre types. For example: Foreign, Local. |
| a_crdt_note_invoice_link | 5 | 9 | 0 | This table receives a new entry when a credit note is applied to an invoice. Since the invoices and credit notes share the same table, we need a way to link the two, and this is the role of this table. | |
| a_currency | 32 | 3 | 11 | 84 | Unit of money for various countries. |
| a_currency_language | 4 | 13 | 0 | Describes what is to be displayed for a currency and language combination when displaying the amount as text. | |
| a_daily_exchange_rate | 4 | 10 | 0 | Ad hoc exchange rates. | |
| a_email_destination | 3 | 9 | 0 | Where Petra supports it a cross reference between a file and destination can be established for automatic distribution. | |
| a_ep_account | 9 | 16 | 0 | This contains the settings for one specific bank account | |
| a_ep_document_payment | 7 | 9 | 0 | This table links the different EP payments to actual invoices and credit notes. | |
| a_ep_match | 1 | 16 | 41 | 0 | the matches that can be used to identify recurring gift or GL transactions |
| a_ep_payment | 2 | 6 | 11 | 0 | This table acts as a queue for electronic payments. If an invoice is paid electronically, the payment is added to this table. A EP program will go through this table paying all entries to GL and moving them to the a_ap_payment table. |
| a_ep_statement | 1 | 6 | 14 | 0 | List of recently imported bank statements |
| a_ep_transaction | 4 | 24 | 0 | the transactions from the recently imported bank statements; they should help to identify the other party of the transaction (donor, etc) and the purpose of the transaction | |
| a_fees_payable | 7 | 14 | 4 | Fees owed to another ledger. (e.g. admin grant) | |
| a_fees_receivable | 7 | 14 | 4 | Charges to collect from other ledgers. (e.g. office admin fee) | |
| a_form | 2 | 2 | 14 | 0 | The form description for user definable forms such as receipts |
| a_form_element | 6 | 15 | 0 | Each element that can be displayed on a form is defined on this table. | |
| a_form_element_type | 2 | 2 | 9 | 0 | The element types that are available for placing in forms. |
| a_freeform_analysis | 15 | 4 | 9 | 0 | Available analysis values that may be given to a transaction for each analysis type. |
| a_frequency | 2 | 2 | 12 | 7 | Units of time. Used in partner letters. Also used to indicate how often a publication is produced or a receipt is sent to a donor. |
| a_general_ledger_master | 1 | 6 | 18 | 42 | All balances on accounts, including summary information is stored here. |
| a_general_ledger_master_period | 3 | 12 | 840 | The General Ledger Master data for one period (e.g. a month) | |
| a_gift | 6 | 7 | 24 | 22 | Information on the donor's giving. Points to the gift detail records. |
| a_gift_batch | 4 | 8 | 22 | 24 | Information describing groups (batches) of gifts. |
| a_gift_detail | 4 | 13 | 29 | 23 | The gift recipient information for a gift. A single gift can be split among more than one recipient. A gift detail record is created for each recipient. |
| a_ich_stewardship | 6 | 16 | 0 | Contains the calculation for the stewardship for a particular run. Files and reports can be recreated from this. ICH = International Clearing House (Handles transfering of funds and admin grant fees among offices.) | |
| a_journal | 3 | 8 | 22 | 13 | Holds details of each general ledger journal, which contains a group of transactions. |
| a_key_focus_area | 1 | 2 | 7 | 0 | Lookup table for Key Focus Areas |
| a_ledger | 27 | 6 | 88 | 1 | Basic information for each general ledger on the system. Also counters for ledger-specific variables (such as last receipt number). |
| a_ledger_init_flag | 3 | 7 | 0 | Ledger Init Flags | |
| a_method_of_giving | 3 | 2 | 11 | 0 | Special payment programs the donor may give money through. (ie, Gift Aid in the UK). Currently not used in Petra release 1. |
| a_method_of_payment | 5 | 3 | 11 | 0 | Media types of money received. Eg: Cash, Check Credit Card |
| a_motivation_detail | 21 | 9 | 30 | 5 | Used as a subdvision of motivation group. Details of the reason money has been received, where it is going (cost centre and account), and fees to be charged on it. |
| a_motivation_detail_fee | 6 | 9 | 10 | motivation details can have several fees | |
| a_motivation_group | 2 | 3 | 11 | 1 | This is used to track a partner's reason for contacting the organisation/sending money. Divided into Motivation Detail codes. |
| a_prev_year_corp_ex_rate | 4 | 10 | 0 | Old rates no longer in use. | |
| a_prev_year_trans_anal_attrib | 14 | 13 | 0 | GL transaction Analysis Attributes from the previous financial year. | |
| a_previous_year_batch | 2 | 5 | 18 | 0 | GL batches from the previous financial year. |
| a_previous_year_journal | 3 | 11 | 22 | 0 | GL journals from the previous financial year. |
| a_previous_year_transaction | 4 | 9 | 30 | 0 | GL transactions from the previous financial year. |
| a_processed_fee | 12 | 15 | 21 | Stores administrative fees and grants which have been calculated on gifts. | |
| a_recurring_batch | 2 | 5 | 20 | 0 | Templates of general ledger batches which can be copied into the ledger. |
| a_recurring_gift | 3 | 7 | 19 | 0 | Templates of donor gift information which can be copied into the gift system with recurring gift batches. |
| a_recurring_gift_batch | 2 | 8 | 16 | 0 | Templates of gift batches which can be copied into the gift system. |
| a_recurring_gift_detail | 11 | 26 | 0 | Store recipient information for the recurring gift. | |
| a_recurring_journal | 3 | 9 | 20 | 0 | Templates of general ledger journals which are copied into the ledger with recurring general ledger batches. |
| a_recurring_trans_anal_attrib | 16 | 13 | 0 | Detailed analysis information stored along with the recurring transaction template. | |
| a_recurring_transaction | 4 | 13 | 32 | 0 | Templates of general ledger transactions which are copied into the ledger with general ledger batches. |
| a_special_trans_type | 5 | 10 | 0 | Transaction types which have special processing. Eg. Allocation, Reallocation, Gift, Revaluation. | |
| a_sub_system | 3 | 2 | 9 | 3 | Subsystems to the general ledger which can be added and removed independantly. Eg GL, AP, AR, GR |
| a_suspense_account | 4 | 7 | 0 | Lists the suspense accounts of each ledger. | |
| a_system_interface | 4 | 8 | 3 | Shows which systems are interfaced (have been added) to each general ledger. | |
| a_tax_table | 8 | 4 | 12 | 0 | This is used by the invoicing |
| a_tax_type | 3 | 2 | 7 | 0 | used for invoicing |
| a_this_year_old_batch | 2 | 5 | 17 | 0 | GL batches from previous periods in the current financial year. |
| a_this_year_old_journal | 3 | 10 | 22 | 0 | GL journals from previous periods in the current financial year. |
| a_this_year_old_transaction | 4 | 9 | 31 | 0 | GL transactions from previous periods in the current financial year. |
| a_thisyearold_trans_anal_attrib | 16 | 13 | 0 | GL transaction Analysis Attributes from previous periods in the current financial year. | |
| a_trans_anal_attrib | 18 | 13 | 0 | Analysis information entered by the user for a general ledger transaction. | |
| a_transaction | 4 | 12 | 32 | 26 | Detailed information for each debit and credit in a general ledger journal. |
| a_transaction_type | 12 | 6 | 15 | 6 | Various ways a transaction may originate, depending on the subsystem. |
| a_valid_ledger_number | 7 | 9 | 4 | List of foreign ledgers (eg, other fields) which the local ledger may send transctions to. | |
| m_extract | 6 | 9 | 0 | Contains the list of partners in each mailing extract | |
| m_extract_master | 4 | 4 | 19 | 0 | Master file for extracts. Contains names for the extract id |
| m_extract_parameter | 3 | 9 | 0 | Contains a list of parameters that an extract was run with (so it can be rerun) | |
| m_extract_type | 1 | 2 | 8 | 0 | Contains a list of extract type which is needed when extracts need to be rerun |
| p_acquisition | 2 | 2 | 10 | 18 | This table is used to describe how a partner first came into contact with the organisation. Which department entered them. |
| p_action | 2 | 3 | 10 | 0 | A particular action within a process which can be performed on a Partner |
| p_address_element | 1 | 2 | 9 | 0 | This contains the elements which make up an address. Eg Name etc |
| p_address_layout | 4 | 11 | 0 | This table contains the address lines used in laying out an address. Eg a form letter address layout | |
| p_address_layout_code | 2 | 2 | 9 | 0 | This table contains the address layouts generally available for the user. |
| p_address_line | 3 | 8 | 0 | This is an address line which consists of address elements. Used along with p_address_layout and p_address_element to define layout of an address for different countries. | |
| p_addressee_title_override | 3 | 8 | 0 | This is used to override titles that might be different in the address than that in the letter. Eg German Herr Herrn Sehr geehrter Herr Starling in the letter and Herrn Starling in the address. | |
| p_addressee_type | 3 | 2 | 8 | 8 | Ex. Fam - Family, SM - Single Male, etc. |
| p_bank | 1 | 4 | 12 | 0 | Details of an bank |
| p_banking_details | 4 | 4 | 19 | 0 | Any bank details for a partner can be stored in this table |
| p_banking_details_usage | 5 | 8 | 0 | Links p_partner - p_banking_details combination to a usage type | |
| p_banking_details_usage_type | 1 | 2 | 10 | 0 | Usage type information for Banking Details. |
| p_banking_type | 1 | 2 | 9 | 0 | Tells of what type this banking-detail is (bank-account, visa, mastercard, etc. |
| p_business | 1 | 2 | 8 | 24 | List of businesses with codes |
| p_church | 5 | 15 | 0 | Specific information about a church which is a partner | |
| p_contact_attribute | 1 | 2 | 8 | 0 | Possible attributes for partner contacts. Gives the description of each attribute code. An attribute is a type of contact that was made or which occurred with a partner. |
| p_contact_attribute_detail | 2 | 3 | 10 | 0 | Possible attribute details for each contact attribute. Breaks down the attribute into more specifice information that applies to a contact with a partner. |
| p_country | 10 | 3 | 17 | 226 | List of countries with their codes |
| p_customised_greeting | 4 | 9 | 0 | Specific greetings from a user to a partner | |
| p_data_label | 4 | 4 | 20 | 0 | This table is used to define data labels for individual use in each office. |
| p_data_label_lookup | 3 | 9 | 0 | This table holds all lookup values that can be used for data label values. | |
| p_data_label_lookup_category | 2 | 2 | 8 | 0 | This table holds the categories that can be used for data label values. |
| p_data_label_use | 3 | 8 | 0 | This table defines where a data label is used and the order the labels appear in. | |
| p_data_label_value_application | 7 | 18 | 0 | This table holds the label values for application related data. | |
| p_data_label_value_partner | 5 | 16 | 0 | This table holds the label values for partner related data. | |
| p_denomination | 1 | 2 | 9 | 0 | List of denomination codes for churches |
| p_email | 2 | 9 | 0 | email addresses of our organisation | |
| p_family | 1 | 5 | 15 | 7 | Contains details about a family in Partnership with us. May have P_Person records linked to it. |
| p_file_info | 8 | 4 | 14 | 0 | Store information about the physical location of a file linked into Petra |
| p_first_contact | 1 | 2 | 8 | 0 | Lookup table for First Contact Codes (ie. how did person first hear about us) |
| p_form_letter_body | 2 | 3 | 10 | 0 | Text for form letters |
| p_form_letter_design | 4 | 10 | 0 | Configuration info for form letters | |
| p_form_letter_insert | 5 | 10 | 0 | Insertions for a body of text for a given extract and partner | |
| p_formality | 5 | 13 | 0 | Contains the text used in letters | |
| p_foundation | 3 | 5 | 19 | 0 | Foundations - a type of ORGANISATION for fundraising proposals. |
| p_foundation_deadline | 3 | 9 | 0 | The month and day of reviews so that proposals can be sent in time | |
| p_foundation_proposal | 2 | 5 | 15 | 0 | Proposals submitted to a Foundation |
| p_foundation_proposal_detail | 11 | 14 | 0 | A proposal may be for more than one project or key ministry. | |
| p_foundation_proposal_status | 1 | 2 | 7 | 0 | Foundation proposal status codes and descriptions |
| p_interest | 1 | 3 | 8 | 0 | Area of Interest |
| p_interest_category | 1 | 2 | 10 | 0 | Categories for Area of Interest |
| p_international_postal_type | 1 | 2 | 8 | 14 | Post office mailing zone classification |
| p_label | 3 | 16 | 0 | Defines the attributes of different label types. Eg: for address labels. | |
| p_language | 14 | 2 | 9 | 55 | List of language codes |
| p_location | 6 | 3 | 23 | 11 | Address and other data related to that address. |
| p_location_type | 1 | 2 | 9 | 13 | Types of address e.g. home, business |
| p_mailing | 4 | 2 | 14 | 0 | Lists mailings that are being tracked. When entering gifts, the mailing that motivated the gift can be indicated. |
| p_merge_field | 3 | 10 | 0 | Fields within a Mail Merge Form | |
| p_merge_form | 1 | 2 | 7 | 0 | Master record for Mail Merge output creation |
| p_method_of_contact | 1 | 2 | 10 | 0 | How contacts are made |
| p_occupation | 1 | 2 | 9 | 226 | List of occupations with codes |
| p_organisation | 1 | 5 | 11 | 1 | Details of an organisation |
| p_partner | 69 | 8 | 34 | 22 | This is the main table of the partner system. Partners can be individuals, families, organisations (churches, businesses), fields, cost centers, and others. These represent various classes of partners. |
| p_partner_action | 12 | 19 | 0 | A particular action which has been or needs to be applied to a Partner | |
| p_partner_attribute | 4 | 12 | 0 | Mainly introduced for contact details like email addresses and mobile phone numbers, but can be used for any attribute you might want to save for a partner. | |
| p_partner_attribute_type | 1 | 2 | 9 | 0 | All the different Partner attribute types will be stored in here. |
| p_partner_banking_details | 2 | 4 | 7 | 0 | Links p_partner table with p_banking_details table for many to many relationship |
| p_partner_classes | 2 | 2 | 7 | 7 | The class a partner is (PERSON, UNIT, etc. |
| p_partner_comment | 3 | 10 | 0 | Allows multiple as well as arbitrary-length partner comments. | |
| p_partner_contact | 4 | 7 | 18 | 0 | Details of contacts with partners |
| p_partner_contact_attribute | 5 | 8 | 0 | Associates a p_contact_attribute_detail with a p_partner_contact. A contact with a partner may have more than one p_contact_attribute_detail associated with it. | |
| p_partner_contact_file | 5 | 8 | 0 | Link file with a partner contact | |
| p_partner_field_of_service | 7 | 16 | 0 | Tracks the current field of service for the Partner and maintains a history | |
| p_partner_file | 4 | 7 | 0 | Link file with a partner | |
| p_partner_graphic | 4 | 8 | 0 | Any graphic associated to a partner can be stored here. | |
| p_partner_interest | 6 | 12 | 0 | Partner Area of Interest | |
| p_partner_ledger | 3 | 7 | 1 | Used to keep track of partner keys | |
| p_partner_location | 3 | 6 | 23 | 20 | Links partners with locations (addresses) and has specific info about the link (e.g. phone number) |
| p_partner_merge | 5 | 9 | 0 | Partner merge history | |
| p_partner_relationship | 5 | 9 | 0 | Relationships between pairs of partners. Among other relationships, this also relates the FAMILY class partners to the PERSON class partners to indicate members of a family. | |
| p_partner_reminder | 6 | 8 | 23 | 0 | A reminder that can be linked to a Partner or Partner contact |
| p_partner_set | 4 | 3 | 8 | 0 | Defines a Partner set |
| p_partner_set_partner | 5 | 8 | 0 | Places Partners in a Partner set | |
| p_partner_short_code | 3 | 10 | 0 | Stores one or more short codes for a Partner (eg. a donor or recipient code for online giving system) | |
| p_partner_state | 5 | 13 | 0 | A particular state in which the Partner is or has been. The Partner may be in more than one state at one time if there are two different processes relating to them. | |
| p_partner_status | 1 | 2 | 10 | 4 | List of statuses for partners |
| p_partner_tax_deductible_pct | 3 | 8 | 0 | Specifies the percentage of incoming gifts to this recipient that can be considered tax deductible | |
| p_partner_type | 4 | 9 | 15 | Types assigned to each partner. Also known as special types. | |
| p_person | 23 | 7 | 26 | 0 | Details of a person. A person must also have a related FAMILY class p_partner record. |
| p_postcode_range | 1 | 2 | 8 | 0 | Postcode ranges for each region |
| p_postcode_region | 3 | 7 | 0 | Postcode regions and the ranges they contain. | |
| p_process | 2 | 2 | 8 | 0 | Refers to a process through which a Partner may go (eg. application, different status of donor - small->medium->big, etc) |
| p_proposal_submission_type | 1 | 2 | 7 | 0 | Submission type for foundation proposals e.g. EMAIL, LETTER. |
| p_publication | 2 | 4 | 13 | 2 | Details of a publication |
| p_publication_cost | 4 | 10 | 0 | Cost of a publication | |
| p_reason_subscription_cancelled | 1 | 2 | 7 | 7 | List of reasons for cancelling a subscription |
| p_reason_subscription_given | 1 | 2 | 7 | 3 | List of reasons for giving a subscription |
| p_recent_partners | 4 | 9 | 1 | The partners a user has been working with recently | |
| p_relation | 1 | 3 | 11 | 31 | List of relationships between partners. Relations occur in one direction only. The relation code is used in the p_partner_relationship record. |
| p_relation_category | 1 | 2 | 10 | 3 | This table contains the codes that indicate the categories of relations (grouping). |
| p_reminder_category | 1 | 2 | 10 | 0 | This table contains the codes that indicate the categories of reminders |
| p_reports | 3 | 8 | 0 | For Development. Associates Progress program files with their Petra Partner report names. | |
| p_state | 2 | 3 | 10 | 0 | A particular state within a process which can apply to a Partner. Each state will probably need to have an Idle state to indicate when no state applies. |
| p_subscription | 7 | 23 | 0 | Details of which partners receive which publications. | |
| p_tax | 3 | 11 | 0 | Tax reference numbers | |
| p_title | 3 | 8 | 0 | Titles available for use | |
| p_type | 2 | 3 | 12 | 60 | List of all possible special types for a partner. |
| p_type_category | 1 | 2 | 10 | 0 | This table contains the codes that indicate the categories of partner (special) types |
| p_unit | 33 | 7 | 18 | 13 | Details of a unit. This is an organizational unit such as an om field, department, local cost center, etc. |
| p_venue | 2 | 5 | 10 | 0 | Details of a venue |
| pc_attendee | 6 | 5 | 19 | 0 | Lists the attendees at a conference |
| pc_building | 2 | 3 | 8 | 0 | Details of building used for accomodation at a conference |
| pc_conference | 7 | 4 | 10 | 0 | Basic details about a conference |
| pc_conference_cost | 3 | 8 | 0 | Charges for the various outreach options from a conference (currency held in conference master) | |
| pc_conference_option | 4 | 8 | 0 | Lists options that are set for a conference | |
| pc_conference_option_type | 1 | 2 | 11 | 0 | Lists types of options that can be used for a conference |
| pc_conference_venue | 4 | 7 | 0 | Links venues to conferences | |
| pc_cost_type | 2 | 2 | 10 | 0 | Cost types to be used for conference (extra) charges |
| pc_discount | 5 | 12 | 0 | Lists optional discounts for a conference | |
| pc_discount_criteria | 1 | 2 | 10 | 0 | Lists possible criterias that must be met for discounts to be applied |
| pc_early_late | 3 | 11 | 0 | Discounts and Supplements for early or late registration | |
| pc_extra_cost | 6 | 13 | 0 | Contains extra conference costs for individual attendees | |
| pc_group | 4 | 9 | 0 | Contains information about which groups individual attendees are assigned to | |
| pc_room | 6 | 4 | 19 | 0 | Details of rooms used for accommodation at a conference |
| pc_room_alloc | 1 | 7 | 17 | 0 | Links rooms to attendees of a conference or a booking in the hospitality module |
| pc_room_attribute | 6 | 9 | 0 | Attributes assigned to rooms used for accommodation at a conference | |
| pc_room_attribute_type | 1 | 2 | 9 | 0 | Contains type of attributes that can be assigned to a room |
| pc_supplement | 3 | 9 | 0 | outreach travel supplements (by outreach ID) | |
| ph_booking | 1 | 5 | 21 | 0 | make sure charging works for a group or an individual; this summarises all the hospitality services that have to be paid for; also useful for planning meals in the kitchen and room preparation |
| ph_room_booking | 4 | 7 | 0 | Links room allocations and a booking | |
| pm_application_file | 6 | 9 | 0 | Link file with an application | |
| pm_application_forms | 4 | 7 | 17 | 0 | This table contains the list of forms sent or received during the application process. |
| pm_application_forms_file | 7 | 10 | 0 | Link file with an application form | |
| pm_application_status_history | 6 | 12 | 0 | Keeps a history of the application status for short and long term applications. | |
| pm_commitment_status | 2 | 2 | 13 | 7 | This table holds the statuses that are be used for commitments. |
| pm_document | 2 | 5 | 17 | 0 | Document |
| pm_document_category | 1 | 2 | 11 | 0 | This table contains the codes that indicate the categories of document types (grouping). |
| pm_document_file | 6 | 9 | 0 | Link file with a personal document | |
| pm_document_type | 1 | 3 | 11 | 0 | This table contains the codes that indicate the types of documents for a person. |
| pm_formal_education | 4 | 13 | 0 | This table records the formal education that a person has | |
| pm_general_application | 18 | 12 | 37 | 0 | The first part of any application which contains data common to either short term or long term applications. |
| pm_interview | 3 | 12 | 0 | Details of the personal interview of the Worker. | |
| pm_job_assignment | 9 | 21 | 0 | This defines the position one fills. | |
| pm_long_term_support_figures | 3 | 35 | 0 | ||
| pm_ownership | 4 | 13 | 0 | This table describes various things owned by a person whether items of value or physical characteristics. | |
| pm_passport_details | 6 | 18 | 0 | Passport Details | |
| pm_past_experience | 3 | 17 | 0 | This details any previous ministry experience the individual has. | |
| pm_pers_office_specific_data | 3 | 16 | 0 | This table is a 'free-form' table for each office to use as needed. | |
| pm_person_ability | 5 | 12 | 0 | This table describes the ability or abilities one possesses. | |
| pm_person_absence | 3 | 12 | 0 | This table records the absence of a person (holiday, sickness, etc.) | |
| pm_person_commitment_status | 4 | 8 | 0 | This table holds the commitment status history of a person | |
| pm_person_evaluation | 3 | 12 | 0 | This table contains information regarding personal progress reports. | |
| pm_person_file | 4 | 7 | 0 | Link file with a person | |
| pm_person_language | 5 | 14 | 0 | This table contains detail about the language the person speaks. | |
| pm_person_qualification | 5 | 14 | 0 | This table provides detail on qualifications someone may possess. | |
| pm_person_skill | 6 | 19 | 0 | This table describes the skills that a person has (including professional skills but also other ones). | |
| pm_person_vision | 5 | 9 | 0 | ||
| pm_personal_data | 5 | 33 | 0 | This table contains personal data about our staff, eg. tax id. | |
| pm_short_term_application | 25 | 71 | 0 | Table for short term applications. | |
| pm_special_need | 3 | 11 | 0 | This table includes special medical or dietary needs someone may have. | |
| pm_staff_data | 2 | 8 | 19 | 0 | This table contains information regarding recruitment, home office, field office, etc. . |
| pm_year_program_application | 7 | 29 | 0 | This table contains information pertaining to the application process. | |
| pt_ability_area | 3 | 2 | 11 | 224 | Defines the areas in which a person may possess an ability, e.g. plays the guitar. |
| pt_ability_level | 3 | 2 | 10 | 12 | This is the degree to which an ability is possessed, e.g. a little. professional. |
| pt_app_form_types | 1 | 2 | 10 | 0 | This table lists all the various forms that are sent and received in the application process. |
| pt_applicant_status | 2 | 2 | 10 | 21 | This table contains the different codes that indicate where an applicant is in the application continuum. |
| pt_application_type | 1 | 2 | 11 | 1 | This decribes the type of application a person has submitted, e.g, Short-Term, Long-Term, or 2 years. |
| pt_arrival_point | 2 | 2 | 10 | 0 | This table contains the codes used to indicate where the conferee is arriving or departing. |
| pt_assignment_type | 1 | 2 | 10 | 0 | Describes whether a person is full-time, part-time, etc. |
| pt_congress_code | 3 | 2 | 15 | 14 | This table contains the codes that indicate a person's role and/or position at conferences and outreachs. |
| pt_contact | 2 | 2 | 10 | 0 | This list the various methods by which a person learns of this organisation. This table can be changed to fit any field's particular awareness programs. |
| pt_driver_status | 1 | 2 | 10 | 8 | This table contains the codes that indicate the level of ability a drive has. |
| pt_language_level | 3 | 2 | 11 | 13 | This is the degree to which a language is spoken, e.g. a little, phrases, fluent. |
| pt_leadership_rating | 1 | 2 | 10 | 0 | This table contains the codes indicating the leadership potential of someone. |
| pt_leaving_code | 1 | 2 | 10 | 0 | This describes the reason a person left a particular position. |
| pt_marital_status | 2 | 2 | 10 | 10 | This table contains the codes indicating someones marital status. |
| pt_office_specific_data_labels | 2 | 15 | 0 | This table contains the data labels that will be used in the office specific data screen. | |
| pt_outreach_preference_level | 2 | 2 | 10 | 0 | Describes the importance of the country and activity choices. |
| pt_party_type | 1 | 2 | 10 | 0 | This table contains the codes indicating whether groups should be together and for how long. |
| pt_passport_type | 1 | 2 | 10 | 6 | This table contains the codes that indicate the type of passport a person holds. |
| pt_personal_data_labels | 2 | 19 | 0 | This table contains the labels that are attached to the data fields in the Personal Data table. | |
| pt_position | 4 | 3 | 11 | 0 | This is a listing of the different position which exist within our organisation, e.g. Field Leader, Book Keeper, Computer support. |
| pt_qualification_area | 2 | 2 | 10 | 0 | This defines the areas in which a person may posess a qualification, e.g. computing or accountancy. |
| pt_qualification_level | 2 | 2 | 10 | 0 | This is the level to which a qualifications is possessed, e.g. Secondary education, Master's Degree. |
| pt_reports | 3 | 8 | 0 | Associates Progress program files with their Petra Personnel report names. | |
| pt_skill_category | 1 | 2 | 10 | 0 | This is the category that will be used for a person's skill |
| pt_skill_level | 1 | 2 | 10 | 0 | This is the level to which a skill is possessed |
| pt_special_applicant | 1 | 2 | 10 | 0 | This table contains the codes that indicate special situations of applicants. |
| pt_travel_type | 2 | 2 | 10 | 6 | This table contains the codes that indicate the mode of travel being used. |
| pt_valuable_item | 1 | 2 | 10 | 0 | Lists of item(s) of value a person may possess which need to be accounted for various purposes, e.g. customs, or insurance. |
| pt_vision_area | 3 | 2 | 10 | 0 | This defines the area a person may have vision for, e.g. children's work or a particular country. |
| pt_vision_level | 3 | 2 | 10 | 0 | This is the level to which a vision is possessed, e.g. a possibility, do nothing else. |
| s_batch_job | 4 | 18 | 0 | Jobs queued for later execution | |
| s_change_event | 2 | 11 | 0 | Records all database events (ie. insert, update, delete). Gets purged after each export | |
| s_default_file_volume | 4 | 8 | 0 | Set Default Volume for a user group in a specific area | |
| s_error_log | 3 | 15 | 0 | Log of captured runtime errors | |
| s_error_message | 3 | 14 | 0 | List of error messages used by Petra s_errmsg.p program. This allows language-specific runtime error messages to be displayed depending on the language of the logged in user. | |
| s_file | 9 | 2 | 7 | 1 | List of Petra source code files |
| s_form | 3 | 2 | 19 | 0 | List of forms for printers |
| s_function | 4 | 2 | 10 | 0 | Contains all Petra functions to which access can be granted or denied |
| s_function_relationship | 4 | 8 | 0 | Represents a relationship between two particular functions. Eg. Partner Find and Partner Edit | |
| s_group | 38 | 2 | 9 | 0 | List of groups to which users can belong |
| s_group_cost_centre | 6 | 9 | 0 | Gives a group access to a specific cost centre (so that people without other finance access can access data on their own department) | |
| s_group_data_label | 5 | 11 | 0 | Controls the access that a group has to a specific Data Label, if the Data Label is restricted | |
| s_group_extract | 5 | 11 | 0 | Gives a group access to a specific extract | |
| s_group_file_info | 5 | 11 | 0 | Associates a Group with an external document (file info). This may be read, write, delete | |
| s_group_function | 5 | 9 | 0 | Gives the group access to a particular function | |
| s_group_gift | 7 | 13 | 0 | Controls the access that a group has to a specific gift, if the gift is restricted | |
| s_group_ledger | 5 | 8 | 0 | Gives a group access to a specific ledger | |
| s_group_location | 6 | 12 | 0 | Controls the access that a group has to a specific location, if the Location is restricted | |
| s_group_module_access_permission | 5 | 9 | 0 | Security mappings from groups to Petra modules | |
| s_group_motivation | 7 | 13 | 0 | Controls the access that a group has to gifts with a specific motivation | |
| s_group_partner_contact | 5 | 11 | 0 | Controls the access that a group has to a specific Partner contact, if the contact is restricted | |
| s_group_partner_location | 7 | 13 | 0 | Controls the access that a group has to a specific partner location, if the Partner Location is restricted | |
| s_group_partner_reminder | 7 | 13 | 0 | Controls the access that a group has to a specific Partner reminder, if the reminder is restricted | |
| s_group_partner_set | 6 | 13 | 0 | Associates a Group with a Partner Set. This may be an inclusive or exclusive association and may be read, write, delete | |
| s_group_table_access_permission | 4 | 12 | 0 | Security mappings from groups to Petra database | |
| s_job_group | 8 | 10 | 0 | Associates groups with roles | |
| s_label | 3 | 16 | 0 | Attributes for label paper | |
| s_language_specific | 3 | 30 | 0 | Definitions of fields that are language specific. | |
| s_login | 2 | 13 | 121 | Log file of all the log in attempts to the system | |
| s_logon_message | 3 | 7 | 1 | List of logon messages by language | |
| s_module | 7 | 2 | 7 | 12 | List of Petra software modules |
| s_module_file | 2 | 7 | 0 | Holds the relationships between Modules and Files | |
| s_patch_log | 3 | 8 | 0 | Logs each patch procedure that is run | |
| s_report_file | 4 | 11 | 0 | Lists the reports that were generated to file and the file name. | |
| s_report_options | 5 | 15 | 0 | Options for running a report. Indicates the output destination(s), number of copies, page numbers to print, output file, etc. | |
| s_reports_to_archive | 2 | 6 | 0 | Contains the titles of reports that should be archived, not deleted, when Purge Reports is run. | |
| s_selected_output_destination | 4 | 12 | 0 | Currently selected print output destinations | |
| s_system_defaults | 2 | 8 | 3 | The settings that are system wide (iso per user) | |
| s_system_status | 3 | 12 | 1 | Records current status of system (up, maintenance etc.) | |
| s_system_status_log | 3 | 11 | 0 | Log of changes in system status | |
| s_user | 721 | 1 | 23 | 3 | List of users |
| s_user_defaults | 3 | 8 | 14 | Stores various default values and options for each user. | |
| s_user_group | 5 | 8 | 0 | Security mappings of users to groups | |
| s_user_module_access_permission | 4 | 8 | 17 | Security mappings of users to Petra modules | |
| s_user_table_access_permission | 3 | 11 | 22 | Security mappings of users to Petra database | |
| s_valid_output_form | 4 | 7 | 0 | Lists printer forms that are valid for each Petra module. | |
| s_volume | 3 | 3 | 9 | 0 | Volume to either represent a file directory or a volume relative to a parent volume |
| s_volume_partner_group | 2 | 2 | 8 | 0 | Set up a Group for use in Default Volumes |
| s_volume_partner_group_partner | 4 | 7 | 0 | Assign Partners to a Group for use in Default Volumes | |
| s_workflow_definition | 4 | 2 | 10 | 0 | Stores the definition of each workflow. These may be pre-created, or created by the user. |
| s_workflow_group | 5 | 8 | 0 | Which groups have access to this workflow | |
| s_workflow_instance | 1 | 3 | 12 | 0 | A running instance of a defined workflow |
| s_workflow_instance_step | 4 | 10 | 0 | Each step of the running workflow, including the status of that step | |
| s_workflow_step | 4 | 8 | 0 | Stores each step of the workflow | |
| s_workflow_user | 4 | 7 | 0 | Which users have access to this workflow | |
| u_unit_type | 2 | 2 | 8 | 11 | General information about the unit such as unit type and entry conference. |
| um_job | 24 | 5 | 23 | 0 | This table contains information concerning jobs within the unit. |
| um_job_language | 8 | 12 | 0 | Language used on this job. | |
| um_job_qualification | 8 | 13 | 0 | Details of qualifications required for individual jobs. | |
| um_job_requirement | 8 | 12 | 0 | Lists abilities and experience required for various positions. | |
| um_job_vision | 8 | 11 | 0 | Details regarding the vision associated with various jobs. | |
| um_unit_ability | 5 | 9 | 0 | Details of the abilities within the unit. | |
| um_unit_cost | 4 | 25 | 0 | Details pertaining to the costs of being on in the unit. | |
| um_unit_evaluation | 3 | 13 | 0 | Details pertaining to evaluation of the unit. | |
| um_unit_language | 5 | 11 | 0 | Details of the language used within this unit. | |
| um_unit_structure | 4 | 7 | 13 | This contains parent/child relationships. | |
| um_unit_vision | 5 | 8 | 0 | Details of the vision required on this unit. | |
| 347 Tables | 4.505 | 3.054 | |||
| 0 Views | 0 |