This chapter contains the following topics:
Media objects and imaging features in Oracle's JD Edwards EnterpriseOne enable you to attach useful information to an application, including information that might currently exist as a paper-based document. The media objects feature enables you to attach the information to applications, forms and rows, and Object Librarian objects. The imaging feature within media objects gives you flexibility to create a more efficient method of information storage.
This table describes the types of information that you can attach to a grid row or a form:
System administrators can also set up templates. A template might include attachments of its own, such as images and shortcuts. For example, you can create a letterhead and a standard form for a memo. You might create a shortcut in the template to provide access to an application that uses data specific to the information that you add to the template.
Text items are items that you create using the JD Edwards EnterpriseOne media objects word processor. They do not require media object queues. The F00165 table contains both the associated key value of the data record to which the text media object is attached, and the text itself. Text items that originate from applications external to JD Edwards EnterpriseOne (for example, Microsoft Word or WordPad) must be stored as OLE objects.
The imaging capabilities available in JD Edwards EnterpriseOne enable you to link to a third-party imaging product. Imaging systems enable you to scan and electronically store paper-based information. For example, this information might include documents such as sales orders, purchase orders, vendor invoices, and product schematics. JD Edwards EnterpriseOne imaging integration includes a media objects viewer and a third-party product that provides scanning and searching interfaces to enable you to find and display images. Implementation of imaging also provides a view of integrated images by using the viewer of the native imaging product.
When you use a third-party vendor, the F00165 table stores the reference to image attachments, but the third-party software controls the search and retrieval of images.
JD Edwards EnterpriseOne media object queues enable the storage location of media objects to be tracked by reference rather than physical network location, which simplifies the administration of media location. For example, the location for media objects on the server can change, and the change is reflected in only one place in JD Edwards EnterpriseOne.
You must define a media object queue to identify the pointer to the location where the actual image files or OLE objects reside. Media object queues provide the system administrator with the ability to easily manage the storage of media objects in the software. Within JD Edwards EnterpriseOne, you must set up media object queues to use images that are outside of the imaging product's domain (for example, scanned images). You can set up media object queues for these types of objects:
Image objects (actual files).
OLE objects (links to files).
URLs (internet addresses).
Image media objects are individual files that are accessed and viewed by using a third-party imaging product. These objects are stored in locations defined with a name and a network-qualified path. For example, if all of the images for financial applications are stored in a directory on the network called \\server1\financials\images
, an image media object queue could be defined as:
Path: \\server1\financials\images
Name: FIN_IMAGES.BMP
OLE media objects are individual objects that are created and viewed by using an OLE-compliant application outside of JD Edwards EnterpriseOne. In JD Edwards EnterpriseOne, the OLE object attached to a row or form is actually a link to the OLE object that resides in a media object queue. The distinction between OLE objects and non-OLE objects is important because, other than graphics files, you cannot attach non-OLE objects from JD Edwards EnterpriseOne if they are not compliant. Examples of valid OLE objects are Microsoft Windows OLE-compliant applications such as Word, Excel, PowerPoint, and Visio. Other examples include sound or video files (.wav or .avi extensions).
Media object queues typically represent network directory locations for JD Edwards EnterpriseOne media object files, such as OLE objects and images. The two media object tables are F98MOQUE and F98101.
The media object queues are stored in the Media Object Queues table, which, along with the Imaging Constants table, should be located in the system data source. The Media Object Queues table contains the associated key value of the data record to which the media object is attached, the image reference, and the OLE reference. The image reference and the OLE reference are queue names. The queue name is used to access the Media Object Queue table for the location of the OLE object or image.
Media object keys are stored in the F00165 table. Media object characterization properties are stored in the F00166 table. The F00167 table stores information indicating which categories the system activates for any given data structure.
If you create a custom application that you want to enable for media object language handling, you must include a data item language preference (alias LNGP) in the generic text data structure that you create.
When you design an application, you can allow the end user to add separate and unique media objects to the same record or different records, based on the language chosen.
If language (LNGP) is not a database column, then you define the media object (GT) data structure to include language as part of the data structure. You place a data dictionary control (LNGP) on the application as a filter field, which should then be loaded with the system value for language. When you design the application this way, you attach two separate media objects, based on the language, to the same record.
If language (LNGP) is a database column, then you include LNGP (database) as a filter field, but you must add a separate record to the database table along with its media object attachment. The media object data structure still contains language as part of the key to retrieve the media object attachment. In both cases, the language filter fields (LNGP) must be loaded with the system value for language. LNGP must be built into the key and not associated with the LNGP column in the F00165 table.
For any database table that contains language as part of its key, you can attach media object functionality for records with different languages. For example, you can create one record for English and a copy of the record for French with unique media object attachments. For tables that do not include language as part of the key to that table, you can have media object languages.