Skip navigation

ActiveX Overview

 

ActiveX is a Microsoft technology made up of small programs that are used within Microsoft products. Within JD Edwards EnterpriseOne, we have used this technology in Internet Explorer (IE) to provide specific enhanced functionality since the first web release of E1.

 

At the time E1 was first released to the web, Internet Explorer was the only supported browser. Having been the most stable and widest spread, this made the selection to use ActiveX easy as the enhanced functionality could be controlled through these small programs.  When working with the grid and media objects, the specific areas affected are shown (images are with ActiveX enabled):

 

  • Grid - Import / Export, Copy / Paste

      ImportExportActiveX.png
  • Media Object – Text, OLE

    MOBJActiveX.png

Fast forward many years down the road and now we have multiple strong browsers which provide alternatives to customers.  No longer is Internet Explorer (IE) the dominant browser, with Chrome, Firefox, and Safari all competing in this space.  Now, the question comes, what alternative options can Oracle provide customers to the Microsoft Internet Explorer (IE) only ActiveX controls?

 

Further, what alternatives can be provided before Microsoft support for ActiveX ends?  Although JD Edwards EnterpriseOne supports the new Microsoft Edge browser with Windows 10, ActiveX controls are not supported with the Edge browser by Microsoft.  Instead, they have chosen to end support with the IE11 release.  Further, Microsoft has indicated IE11 support will end with Windows 10, making Windows 10 the last officially supported OS release for IE11.

 

Alternative Solution

 

Starting as far back as 8.98.3, Oracle JD Edwards has been providing a non-ActiveX solution to customers.

 

Grid

 

When first moving from the ActiveX to non-ActiveX, the grid functionality for copy / paste and export / import did not provide the same level of functionality as the ActiveX controls. This is mainly because the functionality was provided to us in the ActiveX control to work with Excel.  This functionality is not inherent in html or java code.

 

Over time, this functionality has been enhanced and now, the grid, with ActiveX and non-ActiveX provide the same functionality for copy / paste and export / import, with the following exceptions (images are with ActiveX disabled).

 

  • Import from Excel is not available

    ImportNone.png
  • Cannot Export to an existing file

    ExportNone.png

Alternatively, an import is done from either CSV or the Clipboard.  An import from the clipboard is similar to a copy / paste.

 

The export options included are the same as ActiveX, however, there is no option to select a specific file or worksheet in the Excel export as there is with ActiveX.

 

Media Object (MOBJ)

 

Text

 

This change in functionality allows for Text attachments to be created using an ADF HTML editor instead of the ActiveX rtf editor.  This change requires the files to be stored in a different format in the database. With the 9.2 release, they are referred to as etxt attachment types.

Due to the change in storage, there is a conversion available to move the attachment types from the ActiveX rtf storage into the new etxt attachment type.

 

Please note, once you create an attachment in the ADF editor or run the conversion over the data to convert to this type, there is no method of moving the data back to the ActiveX format.

In the following image, you can see how the toolbar is different when ActiveX is disabled as well as no OLE option.

 

MOBJNone.png

 

Troubleshooting Tip – If ActiveX is enabled, the option to work with a text attachment will not show in any browser other than Internet Explorer.  As we have learned, this is because ActiveX is Microsoft’s technology and only works with IE.  If ActiveX is disabled, the text editor will display in all browsers.  Below is a screen shot where ActiveX controls are enabled and the user logged in with the Chrome browser.  Notice, both the Text and OLE options are missing from the toolbar in the following image.

 

MOBJActiveXMissing.png

 

OLE

 

Object Linking and Embedding (OLE) is another Microsoft product.  Basically, OLE is a file management container, which allows for embedding the attachment into the file and then retrieving the file for viewing. Other functionality exists within the OLE container, which has been utilized, but since this interaction is entirely built around ActiveX functionality, it is only available with Internet Explorer.

 

There are two options in Server Manager which will enable the OLE functionality.  True for ActiveX and OLE only.  The OLE only option will turn off ActiveX functionality for text attachments and grid, but will enable it for the OLE MOBJ storage.  This allows any customers who have used OLE to still access these attachments while still being able to go browser independent for text and grid functionality. 

 

ActiveXSettings.png

 

Please note, when ActiveX or OLE-Only is enabled, the ability to access the Advanced Media Object functionality with 9.2 is disabled.  Further, Bug 25495854 - ADD A NOTE IN SUPPORTACTIVEXIE JAS.INI was added requesting a pop-up message in Server Manager when changes are made. 

 

Selecting ActiveX or non-ActiveX

 

From the paragraphs above, we understand there is business justification for either using or not using ActiveX controls. This is a business decision which will have to be made by each company.  Below is a summary of attributes for each.

 

ActiveX

  • Stores text in ActiveX RTF mode

 

Pros

  • Able to export to a specific Excel file / workbook
  • Able to import from a specific Excel file / workbook

 

Cons

  • Requires Internet Explorer
    • Only supported up to IE11
    • Support for IE11 has a set end of life
  • Cannot use Advanced Media Object functionality

 

Non-ActiveX

  • Stores text in etxt format

 

Pros

  • Browser Independent (Internet Explorer, Chrome, Firefox, Safari)
    • Do not have to worry about end of life support
  • Can convert existing ActiveX RTF to etxt
    • Once you go to etxt, there is not an option to go back to ActiveX RTF
  • OLE – Optional
  • Use Advanced Media Object functionality (only with OLE and ActiveX disabled)

Cons

  • Export / Import functionality the same except
    • Import from Excel is not available
    • Cannot Export to an existing file

 

Resources

 

EOL Microsoft support for ActiveX controls

  • Has the Web Browser EDGE or Windows 10 been Certified for E1? (Doc ID 2040422.1)

 

In Your Face Message when Changing ActiveX settings

 

Add import from Excel with ActiveX off

  • Bug 18399260 : IMPORT FROM EXCEL WITH ACTIVEX TURNED OFF
  • For members of Quest, you can vote on this bug to move it up the list. See Enhancement Requests via Quest User Groups (Doc ID 1192883.1) for details.

 

ActiveX turned off

  • Non-ActiveX Controls (HTML) for EnterpriseOne Grid Import / Export and Media Object Attachments for all browsers Firefox, Chrome, Internet Explorer (IE), Safari (Doc ID 780761.1)

 

ActiveX enabled

  • Working with E1 Web Client ActiveX Controls for Media Object and Grid Export / Import with Internet Explorer (Doc ID 1056203.1)

 

Advanced Media Object Functionality (Tools Release 9.2)

  • Understanding Advanced Media Object (MOBJ) functionality available in 9.2.1 and newer (Doc ID 2199562.1)

When researching an issue with OMW, it is best to start with the OMW logging.  In the debug log, this is done by searching for the F98211 table.  Then you look at the insert statement to locate the data dictionary alias.  The best way to do this is to download Notepad++. Then open the log file and do a Find (CTRL-F) for the F98211. Select the button for Find All in All Opened Documents or if you have multiple documents open use Find All in Current Document if only working with one file.

 

FindAllCurrent.png

 

Then you can scroll through the results looking at the codes.  As an example, in the log we would have an entry similar to the following:

 

Jun 22 13:45:31.990006 - 5892/9072 WRK:Starting jdeCallObject        INSERT INTO SY910.F98211 (LDLOGKEY, LDLOGSEQ, LDOMWLDTAI, LDOMWLDATA, LDOMWDFS1, LDOMWDFS2, LDOMWDFS3, LDOMWDFD1, LDOMWDFD2, LDOMWDFD3, LDOMWDFN1, LDOMWDFN2, LDOMWDFN3, LDPID, LDMKEY, LDUSER, LDUPMJ, LDUPMT, LDTIMEZONES, LDDSAVNAME) VALUES ('B1B8210E-F047-45B8-95DA-3110F5F71E4E',17,'149T','R55000T|UBE|E910|USER |',' ',' ',' ',0,0,0,0.000000,0.000000,0.000000,'P98220', 'TOOLSB','USER',115173,134531.000000,' ',' ')

Reviewing the insert statement, we can locate the data dictionary error message alias '149T'.

 

Note: Many of the codes may be simply action called items which can be ignored.  For example, 130S is one of these.  As you go through the log, you’ll have to weed through these entries to locate the actual issue.

 

To look up any given code:

  1. Log into EnterpriseOne > Fastpath to DD > Launch the Error Messages application > Enter the alias into the Alias QBE field to search.
    DDFastpath.png
  2. Enter the alias from the insert statement from the log into the data item QBE and press find
    ErrorCodeDD.png
  3. Open the data dictionary item and select the Item Glossary tab to see the full details of the message
    Glossary.png

 

If you look at the OMW logging in OMW, you should see a message similar to what we see in the Glossary Text.

 

  1. Highlight the object in OMW
  2. Row exit > Logging
  3. Find
  4. Select the log entry or Row > Log Detail

 

Some of the error codes can be self-explanatory in their resolution. However, others may need further research.  Once you locate the error code, simply search in MOS for the code and you should get a document with details on its resolution.  This process can be seen in the following examples where we locate the code and the document with additional details.

 

Example with Document:

 

Jun 03 07:24:44.061005 - 2608/3944 WRK:Starting jdeCallObject INSERT INTO SY910.F98211 (LDLOGKEY, LDLOGSEQ, LDOMWLDTAI, LDOMWLDATA, LDOMWDFS1, LDOMWDFS2, LDOMWDFS3, LDOMWDFD1, LDOMWDFD2, LDOMWDFD3, LDOMWDFN1, LDOMWDFN2, LDOMWDFN3, LDPID, LDMKEY, LDUSER, LDUPMJ, LDUPMT, LDTIMEZONES, LDDSAVNAME) VALUES ('54497473-6a7f-49b9-8fce-0e8a396c41b5',2,'130H','a required Template|the destination for this version.  Template must exist in the target location before the version, or be in the same project if this action is being done on the project.|',' ',' ',' ',0,0,0,0.000000,0.000000,0.000000,'P98220', 'TOOLSB','USER',115154,72444.000000,' ',' ')

 

Check In Fails for One Specific UBE version. Error: 130H - Template Must Exist In The Target Location Before The Version (Doc ID 2011394.1)

 

Example with Document:

 

Jan 05 19:47:37.609003 - 3748/1612 WRK:Starting jdeCallObject INSERT INTO JDE812.SY812.F98211 VALUES ('07829c75-9eaf-4dbd-951d-903a85a685fa',12,'130J','c:\e812\DV812\include\F0005.h|FUtil::CopyF|',' ',' ',' ',0,0,0,0.000000,0.000000,0.000000,'P98220','TOOLSB','USER',110005,194737.000000,' ',' ')

 

Error 130J "Failed to write file" during Check-In or Check-Out of a Business Function or Table (Doc ID 631737.1)

 

Additional details on this troubleshooting process can be found in document Understanding OMW Logging in Object Management Workbench (P98220) (Doc ID 1569747.1) and OMW Troubleshooting Tips and Techniques (Doc ID 660791.1).

Are you or have you experienced issues with the grid (import / export) or media object (icons missing) with your Internet Explorer browser?  Many grid and media object issues are actually ActiveX control issues, and not a problem with the E1 html client.  However, troubleshooting and identifying ActiveX as the cause and resolution can be confusing when someone does not have any experience with Microsoft ActiveX controls.  Over the years, we have provided two main documents in order to help identify and resolve these issues:

 

  • E1: MOBJ: Working with E1 Web Client ActiveX Controls for Media Object and Grid Export / Import (Doc ID 1056203.1)
  • E1: GRID: Troubleshooting Internet Explorer ActiveX Control Installation and Configuration Issues (Doc ID 1621386.1)

  

Both of these documents provide installation instructions and troubleshooting information.  Recently, we have added a new Troubleshooting Flow Chart, which is linked from the previous documents.  This new flowchart provides a visual step by step set of troubleshooting steps complete with videos to show what needs to be done.  Be sure to try it out the next time your struggling with Internet Explorer and ActiveX controls.  (An example screen shot is shown below)

Note: If you have not seen it, be sure to review the previous blog post, Running JD Edwards EnterpriseOne with Internet Explorer (IE) Compatibility View.

FlowChart.png

 

The quote, “The Only Thing That Is Constant Is Change -” by Heraclitus is ever so true when it comes to computing.  Looking around today, the cell phone technology is more powerful than computers a few years ago and as computers change, likewise the software.


If you have grown with the JD Edwards EnterpriseOne (E1) software and Internet Explorer (IE) through the years, you are well aware of our use of activeX controls and the subsequent requirement of compatibility view with IE10 and IE11. 

Compatibility view has been more of a recent requirement which is fortunately no more, but is still causing mischief and misunderstanding depending on your E1 tools release.

As Microsoft has improved on the browser, they have gone from the Standard Mode to a new Edge Mode with IE11. With the E1 code being built to run on standard mode, this required the use of Compatibility view for all of the E1 functionality to work correctly.

With the release of 9.1.5, the IE code in E1 has been uplifted to utilize the edge IE coding and html5 throughout E1, which means we no longer use the old IE standard mode. When reviewing the minimum technical requirements (MTR) via Certifications on MyOracle Support (MOS) this is reflected by support for only IE10 and IE11 with 9.1.5. 

 

Browser

Supported TR

Compatibility View

IE 8

8.98.1 – 9.1.4.7

N

IE 9

8.98.4.4 – 9.1.4.7

N

IE 10

9.1.2 – 9.1.4.7

Y

IE 10

9.1.5 - Onward

N

IE 11

9.1.4 – 9.1.4.7

Y

IE 11

9.1.5 - Onward

N

 

Based on the requirements in the table and your installed release, open Internet Explorer and click on the drop down for settings, Compatibility View is in the list.  From here it is easy to add or remove the URL based on the tools release requirements.

CompatibilityView.png

For 9.1.5, when compatibility view is turned off, the catch is ensuring not only the removal of any E1 URL previously added but removing the check box for "Display intranet sites in Compatibility View". 

Please note: A symptom in 9.1.5 of the check box or URL not being removed is a missing preference item for the Enable Simplified Row/Form Exits. 

Whether a seasoned veteran or a newbie, learning a new ERP system can be an uphill battle, regardless of the position one holds, which makes it nice when a software vendor can do something to help increase the upskilling of individuals learning the product.

 

One way JD Edwards completes this task is with its naming convention.  Really?  JD Edwards naming convention?  Are you serious!?  How can a codename actually help a user to better understand E1 vs a longer, more descriptive, name which may be more intuitive!?  Whoa there, I hear what you are saying, but there really has been a plan all along with this method, which has served JD Edwards well for many years and actually leads to a lower total cost of ownership.

 

No doubt you have heard words of wisdom all of your life, for instance:

 

"Time is really the only capital that any human being has, and the only thing he can’t afford to lose." —Thomas Edison

 

Our naming convention actually helps to fulfill your need to save time.  The real Business Reason behind a standard naming convention is that it promotes:

  • Understanding
  • Taking ownership
  • Governance
  • Reporting
  • Integration


Consider this fact about the potential complexity with tables.

In 2007 there was a posting stating SAP has over 125,000 standard tables, http://scn.sap.com/thread/328958.


The handy reference on this third party site, http://www.jdetables.com/, lists EnterpriseOne 9.1 as having a total of 5112 tables. Although, I am not certain this is the exact amount, even if it were 10,000 tables, the less complicated JDE data model would be significantly easier to understand than SAP’s 125,000+.  This is low TCO (total cost of ownership) by design!!!

 

Ok, so there are fewer tables, which means less JD Edwards EnterpriseOne 9.1 Business Process Models (Doc ID 1642289.1), but what does this have to do with the naming conventions?

 

In JD Edwards, the naming convention for objects tells you the:

  • Object type
  • System code
  • Group type

 

For example,

  • F = File
  • Position 1-2: Is the System (09 General Accounting / 41 Inventory / 12 Fixed Asset / 09E Expenses, etc.)
  • Position 3-4: 01 (Master Table) 11 (Detail Table) 02 (Balance / Summary)


What is F0911?

  • File + General Accounting + Detail Table

And F0902?

  • File + General Accounting + Balances Table

 

Of course, these are simple examples but with this "basic" tip you can navigate most key important data models in JDE.  And the best part is this naming conversion doesn’t end with the tables.  Naming conventions are used for all object types.  See the following diagram taken from the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide under Chapter 3 Understanding JD Edwards EnterpriseOne Naming Conventions

 

NamingConventionforObjects.png

 

Using this foundation, you can begin to learn the ins and outs of the product quicker, and if you are developing new content, simply use the same convention with system code 55-59 to identify custom objects and the transition is an easy one!  For more details on the naming convention for all of the object types, including new ones not shown in the graphic, see the JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide under Chapter 3 Understanding JD Edwards EnterpriseOne Naming Conventions.

Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see https://community.oracle.com/docs/DOC-1022508 for instructions.