Search Results delete_synch_history

Overview

ASG_DOWNLOAD is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, shipping with the application since the 12.1.1 release train and carried forward into 12.2.2. Its header, last revised under the 120.1.12010000.1 version stamp, identifies it as a component of the Oracle Sales and Marketing infrastructure — the "ASG" prefix denotes the Sales/TeleSales foundation objects, and the package is classified in the ETRM repository under the generic API classification "OTHER."

The package implements the server-side engine for the field-sales synchronization subsystem, commonly referred to colloquially as the "autodownload" or "auto-download" mechanism. Field representatives and mobile clients register interest in specific publications and resources; when a change occurs on the server, ASG_DOWNLOAD records the affected primary keys, resource identifiers, and DML operations into an intermediate staging table so that the next synchronization cycle can deliver the correct delta to each entitled user. The package thus mediates between published transactional data and the download queues consumed by the synchronization client, and it exposes routines for marking data dirty, refreshing the staging tables, and purging obsolete synchronization history.

Key Procedures and Functions

Twenty-eight documented procedures and functions are catalogued. The most prominent is the overloaded MARKDIRTY family: five variants (MARKDIRTY and MARK_DIRTY) accept a publication item, one or more access or resource identifiers, a DML type or a DML list, a timestamp, and optionally a list of primary key values. Together they flag records as changed so the staging logic can queue them for download.

• GETPRIMARYKEYS / GET_PK — retrieve primary key values for a given publication or staging context.
• PROCESSSDQ / PURGESDQ / DELETE_SDQ / INSERT_SDQ — operate on the System Dirty Queue, inserting new dirty records, processing pending entries, and removing processed or obsolete rows.
• STOREDELETEDPK — records primary keys of deleted rows for propagation as deletions.
• ISFIRSTSYNC — determines whether a given user or resource is performing an initial synchronization, which governs the population strategy.
• DELETE_SYNCH_HISTORY — clears historical synchronization records, supporting housekeeping of queue tables.
• RESET_ALL_GLOBALS — re-initializes package-level package global state between synchronization runs.
• LOG — writes diagnostic or audit entries to the logging table.
• IS_EXISTS / GET_LISTFROM_STRING / USER_INCOMPATIBILITY_TEST — utility routines that test for entity existence, parse delimited identifier lists into collections, and validate whether a user is incompatible with a resource or publication.

The declared types — user_list, access_list, dml_list, qid_list, pk_list, username_list, and the internal session and cursor types — provide the PL/SQL collection interfaces used by these entry points. Constants OK, FAIL, INS, UPD, DEL, and ALL_USERS indicate the DML and user-selection semantics.

Tables Accessed

The package reads and writes a well-defined set of APPS synonyms. It consumes the publication and configuration metadata held in ASG_PUB, ASG_PUB_ITEM, ASG_CONFIG, and ASG_CONF_INFO; queues pending change records in ASG_SYSTEM_DIRTY_QUEUE and its snapshot ASG_SYSTEM_DIRTY_QUEUE_S; records deletions in ASG_DELETE_QUEUE; and manages purge activity through ASG_PURGE_SDQ and ASG_COMPLETE_REFRESH. User and resource entitlement data are drawn from ASG_USER, ASG_USER_PUB_RESPS, FND_USER, and JTF_RS_RESOURCE_EXTNS. Event-related data resides in ASG_EVENTS_S, while JTM_CON_REQUEST_DATA supplies concurrent-request identifiers. These relationships confirm that the package is the coupling point between the Sales/TeleSales publication model, the FND user directory, and the resource-extensions view of the field organization.

Usage Notes

ASG_DOWNLOAD is an internal, server-side package and is not exposed as a user-facing form. It is invoked by the Oracle Sales and Marketing synchronization concurrent programs and by the download client when the field representative initiates a refresh, and it is referenced by approximately seventy-five other packages within the application, which makes it a foundational dependency of the module. In 12.1.1 and 12.2.2 the synchronization client calls into this package indirectly through the ASG public API layer; direct custom invocations should therefore be restricted to advanced integrations that must inject changes into the dirty queue, and should always observe the published DML constants and collection types to preserve queue integrity.