Search Results synchronize_supp_contact

Overview

APPS.JTF_RS_CONC_RES_PUB is a public PL/SQL package in Oracle E-Business Suite that supports the Resource Manager module within the CRM/Telephony foundation (JTF) schema. Its principal business function is to synchronize the human resources (HR) employee directory with the resource repository maintained in Resource Manager. The package header comment in the source explicitly states that it acts as a concurrent program interface for fetching all employees from the employee database who are valid on the system date and who are not already defined as resources, so that corresponding resource records can be created.

In addition to employee synchronization, the package also manages related entities including parties, supplier contacts, and application users, providing update, termination, and synchronization routines that keep Resource Manager data aligned with HR, HZ (Trading Community Architecture), and FND_USER records. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is typical for concurrent-program-facing public APIs in EBS.

Key Procedures and Functions

The package exposes fourteen documented procedures that can be grouped by the entity they target:

• CREATE_EMPLOYEE — Creates resource records for valid employees not yet present in Resource Manager. Parameters control whether a sales resource is created, the sales credit type, and whether a job-role mapping check is performed.
• TERMINATE_EMPLOYEE — Handles termination of an employee resource.
• UPDATE_EMPLOYEE — Updates existing employee resource records, with an overwrite-name option.
• SYNCHRONIZE_EMPLOYEE — The main concurrent entry point for employee synchronization, returning ERRBUF and RETCODE for the concurrent manager, and supporting options for overwriting names, fetching new employees, sales credit type, and job-role mapping checks.
• UPDATE_TERMINATED_EMPLOYEE — Updates records for employees who have been terminated.
• SYNCHRONIZE_PARTY / UPDATE_PARTY — Synchronize and update party records in the HZ schema linked to resources.
• TERMINATE_PARTNER_REL — Terminates partner relationship records.
• SYNCHRONIZE_SUPP_CONTACT / UPDATE_SUPP_CONTACT / TERMINATE_SUPPLIER_CONTACT — Manage supplier contact resources, including creation, update, and termination.
• UPDATE_USERNAME / UPDATE_USERID — Maintain the linkage between resources and FND_USER accounts.
• SYNCHRONIZE_USER_NAME — Synchronizes the user name associated with a resource.

Tables Accessed

The package reads and writes across several EBS schemas through APPS synonyms:

• JTF_RS_RESOURCE_EXTNS, JTF_RS_RESOURCE_EXTNS_TL, JTF_RS_RESOURCE_EXTN_AUD, and JTF_RS_RESOURCE_EXTN_AUD_S — the core Resource Manager resource extension tables holding resource attributes and translations, with audit counterparts.
• JTF_RS_ROLES_B and JTF_RS_JOB_ROLES — role and job-role mapping definitions used when checking job-role assignments.
• HZ_PARTIES, HZ_PARTY_SITES, HZ_RELATIONSHIPS, HZ_CONTACT_POINTS, and HZ_LOCATIONS — the Trading Community Architecture tables for party, site, relationship, contact point, and location data associated with resources.
• HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS_ALL — HR organization and location data used to source employee details.
• FND_USER and FND_PROFILE_OPTION_VALUES — application user accounts and profile option values used for user-name synchronization and configuration lookups.

Usage Notes

This package is primarily invoked through concurrent programs in Resource Manager that synchronize HR employees into the resource repository, and through related programs that maintain parties, supplier contacts, and user associations. The SYNC procedures return ERRBUF and RETCODE, which are standard concurrent program output conventions, confirming their intended use in that context.

The ETRM metadata indicates the package is not referenced by any other packages (referenced by 0), so it should be treated as an entry point for concurrent scheduling rather than as a building block for other PL/SQL code. Customization typically occurs at the concurrent program parameter level rather than through direct programmatic calls, and the default parameter values (for example, the overwrite-name and job-role mapping flags) allow administrative control over the degree of synchronization applied during each run.