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.
This section provides an overview about converting multiple RFT media object attachments to HTML text and how to run the conversion program.
Note:
The Convert RTF to HTML Text program (P98MOHTM) can be run by any user. Use Application Security to secure access to the P98MOHTM application.See "Managing Application Security" in the JD Edwards EnterpriseOne Tools Security Administration Guide.
You can convert Rich Text Format (RTF) media object attachments to HyperText Markup Language (HTML) text format. Media object attachments are stored in the Media Objects Storage table (F00165). To perform the conversion, you run the Convert RTF to HTML Text program (P98MOHTM), which reads the records in F00165, finds all of the text attachments, and determines what records to convert from RTF to HTML format. The conversion program enables you to convert all of the RTF attachments in F00165 in a single batch run, or you can select a group of records to convert in a batch run. The conversion program reads the text attachments in F00165, generates an equivalent HTML attachment for any RTF attachments in the batch run, and updates the appropriate F00165 records with the converted HTML text.
When the conversion process is finished, the program provides a status of Completed or Partial for the records that were processed in the batch. A status of Partial indicates that one or more records could not be converted in the batch.
The system automatically logs records that failed to convert during the conversion process in the Server Manager JAS log at the SEVERE level. You can log in to Server Manager and see which records failed to convert during conversion process. You can use primary key information (such as OBNM, TXKY, and sequence number) to find the particular attachment in F00165 and manually fix any errors.
Before you begin the conversion process, you can configure the Server Manager JAS log at the DEBUG level to see records that successfully converted during the conversion process. Records that successfully convert are logged at the DEBUG level with the component name RTFTOHTML.
The conversion program (P98MOHTM) walks you through the conversion process and provides general status information. When you open the program, the Convert Media Object RTF to HTML text form appears.
Conversion to HTML text format is permanent and cannot be reverted back to RTF format. The default number of records for a batch conversion is 100,000 records, which you can change. The minimum number of records you can define for a batch conversion is 100 records.
Important:
Before you begin the conversion process, backup the F00165 table.To convert RTF media objects to HTML format:
From an EnterpriseOne web client, type P98MOHTM in the fast path.
The Convert Media Objects from RTF to HTML text form appears.
On Convert Media Objects from RTF to HTML text, select the appropriate data source, and then click Start Conversion.
The system generates messages that:
Confirm the data source.
Warn you that the conversion is permanent.
Recommend that you backup the F00165 table.
Explain how to view and edit the RTF text in the HTML editor.
Select the agreement option, and then click OK to continue the conversion process.
Click Back to change the data source.
The system displays the progress status for retrieving the records from F00165.
When the system finishes retrieving the data from F00165, it displays a conversion page that shows:
Total number of text type attachments.
Total number of attachments that have been converted to HTML.
Number of text attachments that need to be converted.
Define the number of records to convert by selecting one of these options:
All--to convert all of the remaining text attachments to HTML.
Change Batch Size--to specify a group of records for batch conversion.
The default number of records for batch conversion is 100,000 records, which you can change. The minimum number of records you can define for batch conversion is 100 records.
From the drop-down list, select the group of records that you want to convert.
Note:
The Change Batch Size drop-down list shows the conversion status (Complete or Partial) for a group of records. If a record in the selected batch fails to convert, a status of partial appears beside that group of records.Click Convert.
The system displays the progress status during the conversion process.
When the system finishes the conversion, it displays a page that shows the results of the conversion:
Conversion Completed--indicates the selected batch conversion is finished.
Selected Batch Size--the number of records defined for this batch conversion.
Number of RTF attachments converted.
Number of errors while converting the text attachments.
If one or more records could not be converted, a link to Server Manager is provided. Click the link and sign into Server Manager to view the conversion errors.
On the conversion results page, select Close.
This action returns you to the analysis results page (discussed in Step 5) that is updated with the latest conversion information.
On the conversion page, do one of the following:
Select the All option and click Convert to convert all of the remaining RFT attachments.
Select the Change Batch Size option, define the number of records to run in the batch conversion, select the next group of records that you want to convert from the drop-down list, and then click Convert.
Click Cancel to exit the program.