Search Results copy_response_doc

Overview

OKC_TERMS_COPY_GRP is a GROUP-type PL/SQL package in the APPS schema that centralizes the logic required to copy and transition Oracle Contracts (OKC) documents and their associated terms, templates, attachments, and deliverables. Within Oracle E-Business Suite 12.1.1 and 12.2.2, contract authoring follows a document lifecycle in which a source document is duplicated into a target document, a template is instantiated into a live contract, or an existing contract is advanced through a transition such as amendment. Each of these operations requires the coordinated duplication of the header, the terms and articles attached to it, versioning rules, party and contact references, and delivery information. Rather than embedding that logic in every calling form or program, ETRM exposes it through this grouping package, whose procedures act as the single entry point for document and terms duplication. The package is classified as a GRP (group) API, reflecting that it orchestrates multiple underlying entities in one consistent transaction while preserving the source document's structure and version semantics.

Key Procedures and Functions

The package exposes seven documented procedures:

• COPY_DOC — The primary duplication routine. It copies a source document of one document type into a target document, controlling version handling through a keep-version indicator (passed as 'Y' for document transition and 'N' for a straight copy where the target is expected to retain the same article version as the source), and governing whether deliverables, attachments, and abstract content are carried across.
• COPY_TERMS_TEMPLATE — Copies the terms associated with one template into the target context, supporting template-based contract generation.
• COPY_TERMS — Duplicates the terms and articles of an existing document onto a target document independently of the full document copy path.
• CREATE_TEMPLATE_REVISION — Produces a new revision of a terms template, enabling controlled template maintenance without overwriting the prior revision.
• COPY_ARCHIVED_DOC — Copies an archived document, permitting reuse of historical contract content in a new document instance.
• COPY_RESPONSE_DOC — Copies a response document, the routine associated with the user's search term "copy_response_doc." It supports Sourcing and Contracts flows in which a supplier or internal response document must be duplicated into a new response or follow-on document while preserving the article and terms structure.
• PROCESS_MOD_TERMS — Processes modified terms during copy or transition, applying the term changes that result from amendment or negotiation activity.

Tables Accessed

The package operates against a small set of core dictionary and template tables, all referenced through APPS synonyms:

• OKC_BUS_DOC_TYPES_B — The business document type definitions used to validate and resolve the source and target document types passed by callers.
• OKC_TEMPLATE_USAGES — Records the usage relationship between templates and business document types, used when instantiating or copying template-based content.
• OKC_TERMS_TEMPLATES_ALL — The terms template repository, read for template copy operations and updated when creating template revisions.
• DUAL — Used for single-row PL/SQL evaluations and default value resolution.

Because the copy procedures also write the underlying document, terms, and attachment records, they act on the broader OKC table family through the standard ETRM APIs rather than direct DML against these four documented objects.

Usage Notes

OKC_TERMS_COPY_GRP is an internal ETRM API rather than an end-user interface. It is invoked programmatically by Oracle Contracts and Sourcing forms and by other ETRM packages; the metadata records that it is referenced by 19 other packages, confirming its role as a shared service. Typical invocation points include the contract authoring forms where a user selects Copy or Create Version, amendment and transition flows in Sourcing (where the copy-for-amendment and copy-deliverable indicators are set to 'Y'), and any custom extension that must duplicate a contract document or a response document. Callers are expected to supply a valid API version, respect the initialization and commit flags of the FND_API standard, and set the version-keeping and amendment parameters appropriately for the operation. When implementing custom code, the package should be called through its published procedures rather than by replicating its logic, so that version, attachment, and deliverable behavior remains consistent with standard ETRM processing.