Search Results insert_category

Overview

SO_ATT is an Oracle Applications (APPS) PL/SQL package that governs attachment and note handling for Oracle Order Management and related EBS modules. Attachments in EBS are managed through the common FND_ATTACHED_DOCUMENTS / FND_DOCUMENTS framework, while notes are stored in the SO_NOTES table. SO_ATT bridges these two frameworks, allowing order management entities to treat short notes, long notes, and attached documents uniformly. The package declares AUTHID CURRENT_USER and exposes flags such as update_doc_flag and update_ref_flag, which are used to control whether a document or reference row should be updated during attachment processing. Its procedures support marking and clearing records, inserting, updating, and deleting documents and attached documents, and retrieving characteristic metadata such as category, usage, media, and note type. The package is classified as OTHER in the ETRM repository, meaning it is a utility-layer object rather than a documented public API.

Key Procedures and Functions

SO_ATT exposes 23 documented procedures and functions. The mark_record and clear_mark procedures set or reset processing indicators for a source record, distinguishing between short and long text, document versus note source, insert versus update operation, and version (10SC or R10). get_note_name returns a display name for a document, while get_note_error resolves an error message for a message name and optional document id. get_document_usage_type returns the usage type for a note, and get_entity_name derives an entity name from a header id and line id.

Several routines resolve identifiers. get_category_id and get_usage_id convert between usage and category identifiers, while get_media_id returns media and data type identifiers for a document. get_doc_cat_application and get_cat_application return the owning application for a document category or category id. get_note_info consolidates note metadata, returning document id, category id, usage id, usage type, and application id for a given media id and short/long indicator.

The function of interest, get_note_type_code, is a procedure (not a function) that accepts a usage type and returns two OUT parameters: a note type code limited to 'SN' (short note) or 'OT' (other), and an override flag of 'Y' or 'N'. It is typically used to determine how a note should be classified and whether standard attachment behavior may be overridden. The remaining procedures — insert_document, update_document, delete_document, insert_attached_document, update_attached_document, delete_attached_document, and insert_category — perform DML against the FND attachment and document catalog tables.

Tables Accessed

SO_ATT reads and writes through APPS synonyms of the FND attachment framework: FND_ATTACHED_DOCUMENTS, FND_ATTACHED_DOCUMENTS_S, FND_ATTACHMENT_FUNCTIONS, FND_DOCUMENTS, FND_DOCUMENTS_LONG_TEXT and its _S variant, FND_DOCUMENTS_SHORT_TEXT and its _S variant, FND_DOCUMENTS_TL, FND_DOCUMENT_CATEGORIES, FND_DOCUMENT_CATEGORIES_S, FND_DOCUMENT_CATEGORIES_TL, FND_DOC_CATEGORY_USAGES, FND_DOC_CATEGORY_USAGES_S, and SO_NOTES. The FND_DOCUMENTS family stores document metadata, short and long text bodies, translations, and category definitions. The _S tables hold denormalized single-row copies used by the attachment framework. SO_NOTES stores order-management-specific note information, and FND_DOC_CATEGORY_USAGES links categories to their usages, which is the join path that get_note_type_code ultimately depends on.

Usage Notes

SO_ATT is an internal utility package rather than a documented public API; the ETRM repository lists zero packages referencing it, indicating it is invoked primarily from Oracle Forms, concurrent programs, or legacy Order Management code within the APPS schema. Custom development should treat it cautiously: signatures may change between patch levels, and the package is not part of a published integration contract. Where note-type determination is required in custom code, get_note_type_code may be called directly, but callers must supply a valid usage type and handle the OUT parameters for note type code and override flag. Because the package uses AUTHID CURRENT_USER, privileges are resolved against the invoking schema, so grants on the underlying FND tables must exist for any custom caller. Writes to the FND attachment tables should always be performed through this package or an equivalent supported API to preserve the consistency of the attachment framework, and direct DML against FND_DOCUMENTS or SO_NOTES is discouraged.