Search Results task_assign_post_insert

Overview

ASG_SERVICE_ACC is a public PL/SQL package in the APPS schema that belongs to the Oracle E-Business Suite Service / TeleService family of modules. Its name and structure indicate that it was originally designed to maintain "service accesses" — the records that govern which resources, parties, incidents, and tasks are entitled to work with a given service request across a distributed server topology. The header stamp (120.1, dated 2005/08/12) and the embedded comment "this package has been replaced by CSF_ACCESS_PKG" identify it as a legacy compatibility shell: the body has been deliberately reduced so that every documented procedure and function contains only a NULL statement or a trivial return. The package remains in the 12.1.1 and 12.2.2 file systems so that dependent objects still compile and so that existing trigger or form code calling ASG_SERVICE_ACC does not raise ORA-06550 or ORA-04068 errors.

In practice, ASG_SERVICE_ACC acts as the access-maintenance layer for the service request data model. The "trigger handler" routines at the end of the package — TASK_ASSIGN_TRIGGER_HANDLER among them — were the entry points invoked by database triggers on the Incident, Tasks, and Task Assign tables to keep access records synchronized with the parent service request.

Key Procedures and Functions

• RUN_COMMAND — generic command dispatcher; now a no-op.
• ISEXISTING — returns a flag indicating whether an access record already exists for a given account, primary key, and server.
• INSERTACC — inserts a new access row for a resource on a given server.
• UPDATEACC — updates an existing access row, using an operation code to distinguish insert/update/delete semantics.
• ISMOBILEUSER — determines whether a resource is defined as a mobile (field service) user.
• GETSERVERID — returns the server identifier associated with a resource ID.
• UPDATEACCESSES_PARTYID, UPDATEACCESSES_INCIDENTID, UPDATEACCESSES_TASKID — cascading maintenance of access rows when the key-owning party, incident, or task changes.
• UPDATEMOBILEUSERACC — refreshes mobile-user access entries for a resource/server pair.
• INCIDENT_PRE_UPDATE, INCIDENT_POST_UPDATE — pre/post image handlers for the Incident (SR) entity.
• TASKS_POST_INSERT, TASKS_PRE_UPDATE — task table DML handlers.
• TASK_ASSIGN_POST_INSERT, TASK_ASSIGN_PRE_UPDATE, TASK_ASSIGN_PRE_DELETE — DML handlers for the task assignment relationship.
• INCIDENT_TRIGGER_HANDLER, TASKS_TRIGGER_HANDLER, TASK_ASSIGN_TRIGGER_HANDLER, SR_CONTACT_TRIGGER_HANDLER — database trigger callbacks that fan out to the entity-specific handlers above.

Tables Accessed

The ETRM metadata for this object does not expose a direct table list, which is consistent with the package having been hollowed out. Historical documentation and the parameter signatures (party_id, incident_id, task_id, resource_id, server_id) indicate that the original implementation read and wrote the service access tables — the ASG_ACCESSES family and its mobile-user companions — through APPS synonyms. In its delivered 12.1.1 / 12.2.2 state no DML is executed; every routine returns NULL or a constant. Consequently the package is not a source of data integrity risk and does not appear in the tables-referenced section of the data dictionary report.

Usage Notes

ASG_SERVICE_ACC is an internal plumbing package. It is not exposed on any form or concurrent program and is referenced by zero other PL/SQL packages per the ETRM metadata, meaning it is called exclusively from database triggers or from historical application code that has since been superseded by CSF_ACCESS_PKG. A user search for "task_assign_trigger_handler" resolves to the TASK_ASSIGN_TRIGGER_HANDLER routine described above; in 12.1.1 and 12.2.2 that handler is effectively inert, and access maintenance for task assignments is now performed by CSF_ACCESS_PKG. Customizations should not be built against ASG_SERVICE_ACC because Oracle has marked it as replaced; extensions belong in the CSF_ACCESS_PKG API. The package may be safely left in place, and it should not be dropped, since dropping it could invalidate dependent triggers or cause compilation failures in legacy schemas.