aol complete reference
Post on 09-Mar-2015
Embed Size (px)
AOL COMPLETE HAND BOOK: WHO COLUMNSWHO columns are used to track the information updated or inserted by the users against the tables. FND_STANDARD package is used for this purpose. FND_STANDARD.SET_WHO Procedure is used to update the WHO columns in a Table when a DML operation s (i.e. INSERT, UPDATE) performed. 1) Created by 2) Creation date 3) Last _updated_by 4) last_update_date 5) last_update_login Use fnd_profile.VALUE ('USER_ID') for retrieving the user_id which will be used by created_by column. Creation date and last_update_date will be normally SYSDATE. last_updated_by is same as created_by. Use USERENV ('SESSIONID') for getting the last_update_login id.
Key FND Tables in Oracle ApplicationHere there are few key FND tables that we use in our AOL queries. FND_APPLICATION: Stores applications registered with Oracle Application Object Library. FND_APPLICATION_TL: Stores translated information about all the applications registered with Oracle Application Object Library. FND_APP_SERVERS: This table will track the servers used by the E-Business Suite system. FND_ATTACHED_DOCUMENTS: Stores information relating a document to an application entity. FND_CONCURRENT_PROCESSES: Stores information about concurrent managers. FND_CONCURRENT_PROCESSORS: Stores information about immediate (subroutine) concurrent program libraries. FND_CONCURRENT_PROGRAMS: Stores information about concurrent programs. Each row includes a name and description of the concurrent program. FND_CONCURRENT_PROGRAMS_TL: Stores translated information about concurrent programs in each of the installed languages. FND_CONCURRENT_QUEUES: Stores information about concurrent managers. FND_CONCURRENT_QUEUE_SIZE: Stores information about the number of requests a concurrent manager can process at once, according to its work shift. FND_CONCURRENT_REQUESTS: Stores information about individual concurrent requests. FND_CONCURRENT_REQUEST_CLASS: Stores information about concurrent request types. FND_CONC_REQ_OUTPUTS: This table stores output files created by Concurrent Request. FND_CURRENCIES: Stores information about currencies. FND_DATABASES: It tracks the databases employed by the eBusiness suite. This table stores information about the database that is not instance specific. FND_DATABASE_INSTANCES: Stores instance specific information. Every database has one or more instance. FND_DESCRIPTIVE_FLEXS: Stores setup information about descriptive flexfields. FND_DESCRIPTIVE_FLEXS_TL: Stores translated setup information about descriptive flexfields. FND_DOCUMENTS:
Stores language-independent information about a document. FND_EXECUTABLES: Stores information about concurrent program executables. FND_FLEX_VALUES: Stores valid values for key and descriptive flexfield segments. FND_FLEX_VALUE_SETS: Stores information about the value sets used by both key and descriptive flexfields. FND_LANGUAGES: Stores information regarding languages and dialects. FND_MENUS: It lists the menus that appear in the Navigate Window, as determined by the System Administrator when defining responsibilities for function security. FND_MENUS_TL: Stores translated information about the menus in FND_MENUS. FND_MENU_ENTRIES: Stores information about individual entries in the menus in FND_MENUS. FND_PROFILE_OPTIONS: Stores information about user profile options. FND_REQUEST_GROUPS: Stores information about report security groups. FND_REQUEST_SETS: Stores information about report sets. FND_RESPONSIBILITY: Stores information about responsibilities. Each row includes the name and description of the responsibility, the application it belongs to, and values that identify the main menu, and the first form that it uses. FND_RESPONSIBILITY_TL: Stores translated information about responsibilities. FND_RESP_FUNCTIONS: Stores security exclusion rules for function security menus. Security exclusion rules are lists of functions and menus inaccessible to a particular responsibility. FND_SECURITY_GROUPS: Stores information about security groups used to partition data in a Service Bureau architecture. FND_SEQUENCES: Stores information about the registered sequences in your applications. FND_TABLES: Stores information about the registered tables in your applications. FND_TERRITORIES: Stores information for countries, alternatively known as territories. FND_USER: Stores information about application users. FND_VIEWS: Stores information about the registered views in your applications.
Attachment in Oracle ApplicationWhat is attachment in oracle application? The attachments feature in oracle application enables users to link unstructured data, such as images, word-processing documents, spreadsheets, or text to their application data. For example, users can link images to items or video to operations as operation instructions. Where to find an attachment? There is an attachment icon in the oracle application toolbar that indicates whether the Attachments feature is enabled in a form block. When the button is dimmed, the Attachment feature is not available. When the Attachment feature is enabled in a form block, the icon becomes a solid paper clip. The icon switches to a paper clip holding a paper when the Attachment feature is enabled in a form lock and the current record has at least one attachment. Attachment types: An attached document can be: 1] Short Text Text stored in the database containing less than 2000 characters.
2] Long Text Text stored in the database containing 2000 characters or more. 3] Image An image that Oracle Forms can display, including: bmp, cals, jfif, jpeg, gif, pcd, pcx, pict, ras, and tif. 4] OLE Object An OLE Object that requires other OLE server applications to view, such as Microsoft Word or Microsoft Excel. 5] Web Page A URL reference to a web page which you can view with your web browser. Tables Involved: For Importing Attachments in oracle application one has to populate following tables. 1. FND_DOCUMENTS 2. FND_ATTACHED_DOCUMENTS 3. FND_DOCUMENTS_TL 4. FND_DOCUMENT_DATATYPES. 5. FND_DOCUMENT_CATEGORIES 6. FND_DOCUMENTS_LONG_TEXT (Long text type attachment). 7. FND_DOCUMENTS_SHORT_TEXT (Short text type attachment). 8. FND_DOCUMENTS_LONG_RAW 9. FND_LOBS (File type attachments). FND_DOCUMENTS: FND_DOCUMENTS stores language-independent information about a document. For example, each row contains a document identifier, a category identifier, the method of security used for the document (SECURITY_TYPE, where 1=Organization,2=Set of Books, 3=Business unit,4=None), the period in which the document is active, and a flag to indicate whether or not the document can be shared outside of the security type (PUBLISH_FLAG). Other specifications in this table include: datatype (DATATYPE_ID, where 1=short text,2=long text, 3=image, 4=OLE object), image type, and storage type (STORAGE_TYPE, where 1=stored in the database, 2=stored in the file system). The document can be referenced by many application entities and changed only in the define document form (USAGE_TYPE=S); it can be used as a fill-in-the-blanks document, where each time you use a template, you make a copy of it (USAGE_TYPE=T); or it can be used only one time (USAGE_TYPE=O).Images and OLE Objects cannot be used as templates. FND_ATTACHED_DOCUMENTS: FND_ATTACHED_DOCUMENTS stores information relating a document to an application entity. For example, a record may link a document to a sales order or an item. Each row contains foreign keys to FND_DOCUMENTS and FND_DOCUMENT_ENTITIES. There is also a flag to indicate whether or not an attachment was created automatically. FND_DOCUMENTS_TL: FND_DOCUMENTS_TL stores translated information about the documents in FND_DOCUMENTS. Each row includes the document identifier, the language the row is translated to, the description of the document, the file in which the image is stored, and an identifier (MEDIA_ID) of the sub-table in which the document is saved (FND_DOCUMENTS_SHORT_TEXT, FND_DOCUMENTS_LONG_TEXT, or FND_DOCUMENTS_LONG_RAW). FND_DOCUMENT_DATATYPES: FND_DOCUMENT_DATATYPES stores the document datatypes that are supported. Initial values are: short text, long text, image, and OLE Object (DATATYPE_ID=1, 2, 3, or 4). Customers can add datatypes to handle documents stored outside of Oracle and use non-native Forms applications to view/edit their documents. The table uses a "duplicate record" model for handling multi-lingual needs. That is, for each category there will be one record with the same CATEGORY_ID and CATEGORY_NAME for each language. FND_DOCUMENT_CATEGORIES: FND_DOCUMENT_CATEGORIES stores information about the categories in which documents are classified. For example, documents may be considered "Bill of Material Comments", "WIP Job Comments", etc. Document categories are used to provide a measure of security on documents. Each form that enables the attachment feature lists which categories of documents can be viewed in the form. This table uses a "duplicate record" model for handling multi-lingual needs. FND_DOCUMENTS_LONG_TEXT: FND_DOCUMENTS_LONG_TEXT stores information about long text documents. FND_DOCUMENTS_SHORT_TEXT: FND_DOCUMENTS_SHORT_TEXT stores information about short text documents.
FND_DOCUMENTS_LONG_RAW: FND_DOCUMENTS_LONG_RAW stores images and OLE Objects, such as Word Documents and Excel spreadsheets, in the database. FND_DOCUMENT_ENTITIES: FND_DOCUMENT_ENTITIES lists each entity to which attachments can be linked. For example, attachments can be linked to Items, Sales Orders, etc. Since the table uses a "duplicate record" model for handling multi-lingual needs, for each document entity there will be one record with the same DOCUMENT_ENTITY_ID and DATA_OBJECT_CODE for each language. Queries: 1] To find all Long Text attachments:SELECT FAD.SEQ_NUM "Seq Number", FDAT.USER_NAME "Data Type", FDCT.USER_NAME "Category User Name", FAD.ATTACHED_DOCUMENT_ID "Attached Document Id", FDET.USER_ENTITY_NAME "User Entity", FD.DOCUMENT_ID "Do