Results for “gsa_indicator_flag”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKX_PARTIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, shipped as part of the OKX – Contracts Integration product family. Its documented purpose is to present a flattened, denormalized list of "Parties" for consumption by contracts integration and downstream reporting processes. Rather than requiring callers to join or parse the full Oracle Trading Community Architecture (TCA) party model, the view exposes a simplified row set drawn exclusively from HZ_PARTIES, restricted to records whose PARTY_TYPE is either PERSON or ORGANIZATION.
Because the view carries a VALID status in both the 12.1.1 and 12.2.2 environments described in the ETRM metadata, it can be treated as a stable, queryable interface. It does not own data of its own; it is a pure projection over the underlying TCA entity, meaning any change to a party in HZ_PARTIES is immediately reflected when the view is queried. This makes it suitable for integration points, concurrent-program extracts, and ad hoc reporting where the full complexity of the TCA schema is unnecessary.
Underlying Base Objects
The documented base object for this view is a single synonym, HZ_PARTIES, which resolves to the APPS-owned TCA party master. The view text confirms a straightforward single-table SELECT with no joins:
SELECT ... FROM HZ_PARTIES P WHERE P.PARTY_TYPE IN ('PERSON','ORGANIZATION')
Consequently, the view inherits the partitioning and indexing characteristics of HZ_PARTIES and depends on the standard TCA grants/synonyms that expose HZ_PARTIES to the APPS schema. Only PERSON and ORGANIZATION party types are returned; other TCA party classifications, if present, are filtered out by the WHERE clause. No relationships, sites, contacts, or account-level tables are joined, so party-level attributes that live in child TCA entities are not available here.
Key Columns
The view surfaces a defined column list. Notable columns and their semantics include:
- PARTY_NUMBER / DESCRIPTION – The party number from HZ_PARTIES; DESCRIPTION is assigned the same value as PARTY_NUMBER in the view definition.
- CUSTOMER_PROSPECT_CODE – Derived via DECODE on TOTAL_NUM_OF_ORDERS: zero orders yields PROSPECT, one order yields CUSTOMER, and anything else defaults to CUSTOMER.
- NAME / PARTY_TYPE – The party name and its type (PERSON or ORGANIZATION).
- B_STATUS / STATUS – Both map to the underlying STATUS column; END_DATE_ACTIVE is set to SYSDATE when STATUS is 'I' or 'D'.
- START_DATE_ACTIVE – Set to SYSDATE for all rows.
- WOMEN_OWNED_FLAG, SMALL_BUSINESS_FLAG, MINORITY_GROUP_LOOKUP_CODE, PRIMARY_UOM_CODE – Returned as NULL placeholders, retained for interface compatibility.
- GSA_INDICATOR_FLAG, COUNTRY, ADDRESS1–ADDRESS4, CITY, POSTAL_CODE, STATE, PROVINCE, COUNTY – Address and classification attributes carried across from HZ_PARTIES.
Common Use Cases and Queries
Typical uses include populating contract party pick lists, customer/prospect classification reports, and integration extracts. Example queries:
SELECT party_number, name, customer_prospect_code FROM okx_parties_v WHERE status = 'A';
SELECT name, city, state, country FROM okx_parties_v WHERE party_type = 'ORGANIZATION' AND gsa_indicator_flag = 'Y';
Because END_DATE_ACTIVE is populated only for inactive/deleted rows, active-party queries should filter on STATUS = 'A'. Note that several columns are hard-coded NULL and cannot be relied upon for ownership or UOM reporting.
-
View: OKX_PARTIES_V 12.1.1
Parties
-
Data Source view to get information about b2c contacts
APPS.AMS_LT_PERSON_DETAILS_V·↳ HZ_PARTIES·Explore AMS module →
-
View: IGS_AD_ACK_LETTER_V 12.1.1
It would return the Acknowledgement Details of a student
APPS.IGS_AD_ACK_LETTER_V·↳ HZ_PARTIES·↳ IGS_AD_APPL_ADMAPPL_V·↳ IGS_AD_APPL_STAT·Explore IGS module →
-
Returns the missing items. For processing application of the student, few documents are required by the admission module. When student forget to send any document or miss out any document , then these documents are treated as missing items
APPS.IGS_AD_MISSING_ITEMS_LETTER_V·↳ HZ_PARTIES·↳ IGS_AD_APLINS_ADMREQ·↳ IGS_AD_APPL_ALL·Explore IGS module →
-
View: UMX_ORGANIZATION_PVT_V 12.1.1
Private view used by UMX
APPS.UMX_ORGANIZATION_PVT_V·↳ HZ_PARTIES·Explore FND module →
-
View: AMS_ORGANIZATION_V 12.2.2
This View returns all entries from the HZ_PARTIES table which have a party_type of ORGANIZATION. Used for list generation.
-
View: IGF_AW_PER_LIST_V 12.1.1
Stores person details used for correspondence
APPS.IGF_AW_PER_LIST_V·↳ HZ_PARTIES·↳ IGF_AP_FA_BASE_REC_ALL·↳ IGF_AW_AWARD_ALL·Explore IGF module →
-
The validations for the individual letters are placed at the SQLl query level that we attach to master document
APPS.IGS_AD_OUTCOME_LETTERS_V·↳ HZ_PARTIES·↳ IGS_AD_APPL_ADMAPPL_V·↳ IGS_AD_APPL_ALL·Explore IGS module →
-
View: AMS_P_ORGANIZATION_V 12.2.2
This View returns all entries from the HZ_PARTIES table which have a party_type of ORGANIZATION. Used for list generation.
-
View: AMS_P_ORGANIZATION_V 12.1.1
This View returns all entries from the HZ_PARTIES table which have a party_type of ORGANIZATION. Used for list generation.
-
View: OKX_PARTIES_V 12.2.2
Parties
-
Table: HZ_IMP_PARTIES_INT 12.2.2
TCA import table for HZ_PARTIES, HZ_PERSON_PROFILES and HZ_ORG_PROFILES
-
View: IGF_AW_AWD_LTR_V 12.1.1
This view selects relevant data for the Award Notification Letter to be sent to a Student
APPS.IGF_AW_AWD_LTR_V·↳ HZ_PARTIES·↳ IGF_AP_FA_BASE_REC_ALL·↳ IGF_AW_AWD_LTR_TMP·Explore IGF module →
-
View: AST_ORG_PARTIES_V 12.2.2
-
Information about parties such as organizations, people, and groups
-
It returns the Missing items for Post Admission Requirements
APPS.IGS_AD_POSTADM_MISS_ITM_LTR_V·↳ HZ_PARTIES·↳ IGS_AD_APLINS_ADMREQ·↳ IGS_AD_APPL_ALL·Explore IGS module →
-
View: AMS_DM_ORGANIZATIONS_V 12.1.1
This view is no longer used for seeded data sources. (15-Jul-2004)View used by the seeded data mining data source for organizations and organization contacts in the Trading Community Architecture.
APPS.AMS_DM_ORGANIZATIONS_V·↳ AMS_DM_PARTY_DETAILS·↳ AMS_DM_PARTY_DETAILS_TIME·Explore AMS module →
-
View: AMS_ORGANIZATION_V 12.1.1
This View returns all entries from the HZ_PARTIES table which have a party_type of ORGANIZATION. Used for list generation.
-
View: AMS_ORG_PROFILES_V 12.2.2
This public view returns an organization profile for an organization. Used for list generation.
APPS.AMS_ORG_PROFILES_V·↳ HZ_ORGANIZATION_PROFILES·Explore AMS module →
-
View: IGF_SL_DISB_LTR_V 12.1.1
Stores persons loan details used for correspondence
APPS.IGF_SL_DISB_LTR_V·↳ HZ_PARTIES·↳ IGF_AP_FA_BASE_REC_ALL·↳ IGF_AW_AWARD_ALL·Explore IGF module →
-
JTF_HZ_ORGANIZATION_PROFILES_V retrieves information about people as contacts for organizations. The table includes information about the person in the context of the organization such as their job title or rank.
APPS.JTF_HZ_ORGANIZATION_PROFILES_V·↳ HZ_ORGANIZATION_PROFILES·Explore JTF module →
-
Container for the generic details for a party, contains details for rows in AMS_DM_DRV_STG. This table is used by mining collection pack. This is a staging table.
-
View: HZ_ORG_PROFILES_CPUI_V 12.1.1
Organization Profiles
APPS.HZ_ORG_PROFILES_CPUI_V·↳ HZ_ORGANIZATION_PROFILES·↳ HZ_PARTIES·Explore AR module →
-
View: IGF_AP_MIS_ITMS_LTR_V 12.1.1
This view is used to return the missing items (missing documents) which are required for Financial Aid processing
APPS.IGF_AP_MIS_ITMS_LTR_V·↳ HZ_PARTIES·↳ IGF_AP_FA_BASE_REC_ALL·↳ IGF_AP_ST_CORR_TEXT·Explore IGF module →
-
View: UMX_ORGANIZATION_PVT_V 12.2.2
Private view used by UMX
APPS.UMX_ORGANIZATION_PVT_V·↳ HZ_PARTIES·Explore FND module →
-
Data Source view to get information about b2c contacts
APPS.AMS_LT_PERSON_DETAILS_V·↳ HZ_PARTIES·Explore AMS module →
-
View: AMS_DM_ORGANIZATIONS_V 12.2.2
This view is no longer used for seeded data sources. (15-Jul-2004)View used by the seeded data mining data source for organizations and organization contacts in the Trading Community Architecture.
APPS.AMS_DM_ORGANIZATIONS_V·↳ AMS_DM_PARTY_DETAILS·↳ AMS_DM_PARTY_DETAILS_TIME·Explore AMS module →
-
Table: HZ_IMP_PARTIES_INT 12.1.1
TCA import table for HZ_PARTIES, HZ_PERSON_PROFILES and HZ_ORG_PROFILES
-
JTF_HZ_ORGANIZATION_PROFILES_V retrieves information about people as contacts for organizations. The table includes information about the person in the context of the organization such as their job title or rank.
APPS.JTF_HZ_ORGANIZATION_PROFILES_V·↳ HZ_ORGANIZATION_PROFILES·Explore JTF module →
-
View: AMS_ORG_PROFILES_V 12.1.1
This public view returns an organization profile for an organization. Used for list generation.
APPS.AMS_ORG_PROFILES_V·↳ HZ_ORGANIZATION_PROFILES·Explore AMS module →
-
Container for the generic details for a party, contains details for rows in AMS_DM_DRV_STG. This table is used by mining collection pack. This is a staging table.
-
View: AST_ORG_PARTIES_V 12.1.1
-
View: AMS_HZ_B2B_MAPPING_V 12.1.1
This view stores the mapping of ams_imp_source_lines table. This is used to populate the data from the data file.
APPS.AMS_HZ_B2B_MAPPING_V·↳ AMS_IMP_LIST_HEADERS_ALL·↳ AMS_IMP_SOURCE_LINES·Explore AMS module →
-
View: AMS_LEAD_MAPPING_V 12.1.1
This view stores the mapping of ams_imp_source_lines table. This is used to populate the data from the data file.
APPS.AMS_LEAD_MAPPING_V·↳ AMS_IMP_SOURCE_LINES·Explore AMS module →
-
APPS.HZ_PARTY_CONTACT_POINTS_V·↳ HZ_CONTACT_POINTS·↳ HZ_PARTIES·Explore AR module →
-
APPS.HZ_ORGANIZATION_PROFILES_V·↳ HZ_ORGANIZATION_PROFILES·↳ HZ_PARTIES·Explore AR module →
-
View: IGS_AD_RESI_LETTER_V 12.1.1
It would return the Residency Details of a student
APPS.IGS_AD_RESI_LETTER_V·↳ HZ_PARTIES·↳ IGS_AD_APPL·↳ IGS_CA_INST·Explore IGS module →
-
staging table to hold data to be imported
-
View: HZ_ORG_PROFILES_CPUI_V 12.2.2
Organization Profiles
APPS.HZ_ORG_PROFILES_CPUI_V·↳ HZ_ORGANIZATION_PROFILES·↳ HZ_PARTIES·Explore AR module →
-
View: AMS_HZ_B2B_MAPPING_V 12.2.2
This view stores the mapping of ams_imp_source_lines table. This is used to populate the data from the data file.
APPS.AMS_HZ_B2B_MAPPING_V·↳ AMS_IMP_LIST_HEADERS_ALL·↳ AMS_IMP_SOURCE_LINES·Explore AMS module →
-
View: AMS_LEAD_MAPPING_V 12.2.2
This view stores the mapping of ams_imp_source_lines table. This is used to populate the data from the data file.
APPS.AMS_LEAD_MAPPING_V·↳ AMS_IMP_SOURCE_LINES·Explore AMS module →
-
APPS.HZ_PARTY_CONTACT_POINTS_V·↳ HZ_CONTACT_POINTS·↳ HZ_PARTIES·Explore AR module →
-
APPS.HZ_ORGANIZATION_PROFILES_V·↳ HZ_ORGANIZATION_PROFILES·↳ HZ_PARTIES·Explore AR module →
-
Container for the generic details for a party, contains details for rows in AMS_DM_DRV_STG. This table is used by mining collection pack. This is a staging table.
-
Detailed information about organizations
-
View: AMS_ORG_DETAILS_V 12.2.2
This view list the details of an Organization
APPS.AMS_ORG_DETAILS_V·↳ HZ_CONTACT_POINTS·↳ HZ_LOCATIONS·↳ HZ_ORGANIZATION_PROFILES·Explore AMS module →
-
View: AMS_ORG_DETAILS_V 12.1.1
This view list the details of an Organization
APPS.AMS_ORG_DETAILS_V·↳ HZ_CONTACT_POINTS·↳ HZ_LOCATIONS·↳ HZ_ORGANIZATION_PROFILES·Explore AMS module →
-
Information about parties such as organizations, people, and groups
-
Container for the generic details for a party, contains details for rows in AMS_DM_DRV_STG. This table is used by mining collection pack. This is a staging table.