Top 5 Takeaways from INFOCUS 2018

By Hari Karnati and Sarah Mills

If you were at INFOCUS last week, you were most likely consumed with an abundance of JD Edwards education, networking, and a vendor showcase that was buzzing! For those of you who weren’t able to make it to the conference (and for those of you who did, but couldn’t take notes fast enough!), our team has pulled together the key takeaways from the annual conference. As you review, keep in mind the following overarching themes from the event:

  • Support of JDE E1 release 9.2 will continue until 2030, with a focus on continuous improvement and adoption
  • Orchestrator, Operations Simplification, and UXOne continue to be hot topics
  • “You Can Make It Happen” – Oracle’s philosophy empowering the Citizen Developer; the business analysts, non-developers and the end-users

Now that you have these themes in mind, here are the top 5 key takeaways:

5. Server Manager Enhancements

Server Manager enhancements that enable provisioning of a code current EnterpriseOne environment for customers on Power Systems with IBM i. Server Manager for JD Edwards EnterpriseOne enables administrators to easily provision, configure, and manage EnterpriseOne server components. The provisioning capabilities in Server Manager are expanded to include provisioning of Enterprise Server on IBM i and database server – IBM DB2 for IBM i with Application Release 9.2 update2 which includes all current enhancements, application patches and Tools Release These capabilities are available from both the Server Manager UI and REST APIs and provide lowered TCO for setting up a JD Edwards EnterpriseOne environment on IBM I

4. UX One

JD Edwards continues to enhance the user experience through UX One by providing navigation capabilities on Analytic Components. Additional roles and their Analytic Components now provide drilldown and right-click options on context menus with a selection of applications that can be launched. This allows users to easily navigate from analytic graphical presentations to review and act upon detailed master data or transaction information.

UX One Analytic Components provide real-time, transactional information to JD Edwards end users in an intuitive and graphical format. Users are able to visually analyze current business conditions and more easily identify problems that need attention. Navigation from the Analytic Components allows users to quickly take action.

3. Orchestrations

JD Edwards EnterpriseOne Orchestrator is a framework that enables Digital Transformation. There was added focus on Orchestrator and the released orchestrations out of the box to help customers adopt them. JD Edwards EnterpriseOne Orchestrator continues to provide significant functionality for automating EnterpriseOne transactions and interfacing with external systems. The following recent enhancements to Orchestrator further expand its capabilities:

  • Process Recorder allows a user to create a form service simply by recording the step-by-step actions directly in the EnterpriseOne applications. For example, a user could create a form service to return the status of equipment by turning on the Recorder, launching the Work with Equipment Master application, querying on a piece of equipment, selecting the equipment, and turning off the Recorder. The user can choose what information, in this case equipment status, to return from the form. The recorded process can be a single form or a chain of forms, known as an “application stack.” The resulting form service can then be edited in Orchestrator Studio and included as a step in an orchestration. The process of recording the steps is more intuitive, requires less training, and is less error-prone than building the form service manually in Orchestrator Studio, allowing a broader range of citizen developers to participate in the process of creating form services.
  • Report is a new type of service request that allows an orchestration to launch a report (batch job) as an orchestration step. Values for data selection, data sequencing, and version overrides can be passed into the service request as inputs, or they can be saved in the service request as defaults. The result of the process is the same as if the report had been run manually, and the report output file can be manipulated using the File Transfer feature. · File Transfer allows an orchestration step to move a file to a given location using REST, FTP, or SFTP protocols. For example, after a JD Edwards report completes, a file is typically written to a JD Edwards specific output location. Using the File Transfer feature, an orchestration step could automatically move that file from the JD Edwards report output location to another location, such as the Oracle Content and Experience Cloud Service, from where yet another automated process may be triggered. Leveraging this feature to dynamically transfer files can eliminate the development and maintenance of a custom solution to perform the same functionality.
  • Confirmed Completion of Orchestrations provides a set of logged data about the events — and possibly exceptions or errors—that may have occurred during the execution of an orchestration. Administrators can monitor the logs to ensure that orchestrations are completing as expected and react to correct any errant results.

Orchestrator Studio version 6.1 includes usability improvements and enhancements:

  • Users can define an input as an array to process many items in a single orchestration. For example, you can define an orchestration that adds equipment to the Equipment Master application. You can then input an array of data to create many equipment records in a single orchestration. Users can pass the application version as an input to a form service request, allowing the same form service to behave differently depending on which version is specified at runtime. The Studio can automatically load the inputs of form services as orchestration inputs, relieving the user from having to type them manually.
  • Resilient Scheduler allows multiple instances of the Scheduler for executing orchestrations and notifications. The multiple instances of the Scheduler behave like a cluster, providing fault-tolerance and scalability solution.

2. JD Edwards Personalization Framework

JD Edwards EnterpriseOne continues to empower citizen developers and enrich the extensibility frameworks to help customers personalize and extend their solution at a low cost without creating barriers to stay current with JD Edwards. This enables customers to avoid customizations which will help with continuous adoption which was talked about during keynote. The personalization framework with form extensions was a new feature and there are several other planned features to be released in new versions.

1. 64-Bit

Oracle’s JD Edwards EnterpriseOne has supported vendor 64-bit hardware, operating systems, databases, Java, and middleware for many years. Additionally, multiple JD Edwards components, such as HTML Server, AIS Server, Orchestrator and other Java-based components, are 64-bit enabled. Now, to round out our architecture, JD Edwards will enable 64-bit processing for the Enterprise Server and development client. This empowers you to move completely from 32-bit to 64-bit processing.  There are several reasons why you would want to move to 64-bit processing:

  • Moving to 64-bit enables you to adopt future technology and future-proof your environments. If you do not move to 64-bit, you incur the risk of facing hardware and software obsolescence. The move itself to 64-bit is the cost benefit.
  • Many vendors of third-party components, such as database drivers and Java, which JD Edwards EnterpriseOne requires, are delivering only 64-bit components. They also have plans in the future to end or only provide limited support of 32-bit components.
  • It enables JD Edwards to deliver future product innovation and support newer versions of the required technology stack.

There is no impact to your business processes or business data. Transitioning to 64-bit processing is a technical uplift that is managed with the JD Edwards Tools Foundation.

EmeraldCube’s Top 5 Reasons to Attend INFOCUS

We’re counting down the days until the start of INFOCUS, one of the largest industry gatherings for end or power users of JD Edwards. Here are five reasons you should not miss out on this incredible event:

  1. Ten EmeraldCube Educational Sessions

    This year, the EmeraldCube team along with many of our customers, will be presenting ten educational sessions. From “Running JDE 24/7 on the AWS Cloud” (JDE-102580) and “Open for Business: Setting Up and Testing a New Company in JDE” (JDE-104550), to “Consuming Excel Data with Orchestrator” (JDE-104740), you’re guaranteed that EmeraldCube will have an educational session to fit your learning needs. Access our full schedule.


  2. Special Interest Group and User Group Participation

    If you’re participating in one of the many special interest groups such as the HCM SIG or the Financials SIG, we’ll be on hand to answer your questions. You’ll also find us at the E1 Manufacturing and Distribution User Group meetings. We’ll have members from our team of experts on hand to discuss with you the latest business solutions for JD Edwards EnterpriseOne.


  3. EmeraldPrism New Features and Demos – Need We Say More?

    Stop by and see us at Booth #626 during the Exhibitor Showcase. We’ll be providing demos of EmeraldPrism and EmeraldVision, including a sneak peek for INFOCUS attendees of new EmeraldPrism features.


  4. Limited Edition Cubebots Have Landed

    If you’ve attended INFOCUS or Collaborate events in the past, you may already have your collection of EmeraldCube Cubebots started. Make sure to stop by Booth #626 to pick up your limited edition Cubebot.


  5. Win a $500 Amazon Gift Card

    While attending INFOCUS, make sure to sign up to participate in Questopoly. Stop by Booth #626 to play, and you’ll have a chance to win a $500 Amazon Gift Card from EmeraldCube. While you’re there, learn more about EmeraldCloud powered by Amazon Web Services.

We look forward to seeing you in Denver for INFOCUS!

User Defined Objects: They’re Here to Stay

With the release of JD Edwards EnterpriseOne 9.2 Tools in October of 2017, there is a new unified life cycle for managing User Defined Objects (UDO). These include the following:

  • Advanced Queries
  • One View Reports
  • One View Watchlists
  • E1 Pages
  • Composite Application Framework (CafeOne)
  • Composed Pages – TR and above
  • Images/Icons – TR and above
  • Personal Forms – TR 9.2.1 and above
  • Search Groups – TR and above
  • Orchestrations Components – TR 9.2.2 and above
    • Service Request
    • Rules
    • White List
    • Cross Reference
  • Schedules -TR 9.2.2 and above
  • Notifications – TR and above
  • Form Extensions – TR

The solution includes integration with a new Object Management Workbench web application (P98220W), where User Defined Objects can be added to projects and transfer through path code environments. There is also a User Defined Object Administration application (P98220U) for managing UDOs in a single environment. In addition, there is new User Defined Object Security that you can access thru the Security Workbench (P00950) for managing security by role and user.


UDO Life Cycle

The UDO life cycle consists of creation and management. To administer this life cycle, EnterpriseOne provides applications to:

Each personalization feature provides consistent functions for users to: create UDOs for their own personal use; request to share UDOs with others; and modify UDOs created by other users. This is done through the EnterpriseOne interface.
If a user requests to share a UDO, an approver uses the Work with User Defined Objects application (P98220U) to review and approve or reject the UDO.
A users’ ability to create, share and view UDOs depends on the security an administrator has assigned in the Security Workbench – Work With User/Role Security application.
OMW users can package and promote UDOs between path codes using the Web OMW application (P98220W).

Dev 101 Part II: Debugging A Business Function In Visual Studio

In Part I of this blog, we walked through setting up a project in Visual Studio, so a business function can be “Debugged”.

Refresher: Debugging is running an app, UBE or Business Function (code) through a tool that allows the developer to see the logic and calculations take place, line by line, in real time, in order to discern where a problem is located.

We discussed how an application can be debugged using the ER Debugger Tool in JDE, but when an app or a UBE calls a Business Function that is not working as desired, and the developer needs to find out why in order to correct it, a Visual Studio Debug Session is what is needed.

As a VERY simple example, I’ve created a Demo App that calls a VERY simple Business Function. There is a problem in the application and the ER code does not provide any answers. Therefore, we get to debug in C!!! (Only developers will get excited about that…)


The App:

As you can see, the instructions for the app are simple.
The user enters a number into the Inbound Parameter box and clicks the button. If all goes well, a message will appear if they enter a ‘1’, and a different message will appear if they enter a ‘2’.
If any value other than ‘1’ or ‘2’ is entered, the program will explain why this is not correct. 🙂


The App Demo:

Being a good tester, I test what SHOULD work, before testing what might not work.
It’s good to start things off on a positive note.
I enter a ‘1’ and click the button.

Ah. Positive reinforcement is always good.
Next test. See if entering a ‘2’ results in a different message.

Oops. The instructions indicated a different message would be presented, but it said a different POSITIVE message. Something is amiss.
While the app DID let the user know that the functionality is incorrect, the error description could be a bit more specific. Deeper investigation is required.

One more test to see what happens.
I give the program something it won’t expect and see how well the “Help” explains how to correct the issue:

Well, again, the app DID let the user know that the functionality is incorrect…

Next, we get to open the application up in Form Design Studio and see what is going on.

Looking at the ER behind the “Get Message” button, we see that it is calling a Business Function, ECS – Return Values.

We open the function call and verify that the correct parameter is being passed in to the function as indicated by the direction arrows, and that the remaining logic that decides what message to display is dependent on what the function returns.

The “VA evt_cOutBoundVariable_EV02” always receives what is returned from the function, so the error must be in the function.

Referring to Part I of this blog, the developer would then BusBuild the function in JDE, then add the function to their project in Visual Studio C++


Reviewing C Code and Running Debug

As stated, I’ve followed the guidelines in Part I and opened my project in Visual Studio and added the B59DEMO function to the function list.

Scanning the code, a good programmer would be able to see the problem without using debug.

For the rest of us, we will go ahead and run this in debug. 🙂

These are the steps to begin a debug session in VS C++:

  1. Having opened VS and added the function, place a “Breakpoint” at the desired line you would like the program to begin debugging. Do this by setting the cursor to the line and hitting ‘F9’ on your keyboard.

  1. Before opening the application, click on ‘Debug’ on the Menu Bar and select: “Attach to Process”

  1. This window will appear. Ensure the “activeconsole.exe” line is selected and click, “Attach”.

  1. The window in VS C++ will adjust to Debug View and we are now in Debug!
  1. Return to E1 and run the application. Go to the scenario you KNOW doesn’t work first. No use debugging what you know works in this case…

  1. The process is now in debug, and we have stopped on the first line of the function. Notice that the Inbound Parameter is, indeed, a ‘2’ and the Outbound Parameter is ‘ ‘, blank.

  1. Stepping through the code, the issue becomes apparent.
    There is no logic that accounts for an Inbound Parameter of ‘2’. There is no error, per say, but the function is returning a BLANK because there is no code that populates the outbound variable if the inbound parameter is ‘2’!

  1. We know from the ER Code, that if the function returns an error, or the return parameter is blank, we get our “descriptive” error message.

We now have enough information to correct the bug and test.
Go back to the menu bar and select “Stop Debugging” to end the debug session.


Correcting Code and Retesting

Edit the function to correct the “If” Statement like this:

Save the function, then build it by running it through Busbuild.
Run another test.

We see now that the function is corrected, and the application gives the user the second Positive Message!

That concludes this blog entry. I hope you take from this basic demo/example, a positive message: Debugging is not as complicated as it may seem and the more you do it, the easier it gets!!!

Highlights: JD Edwards Release

The latest release of JD Edwards ( is packed full of important updates. What does this mean for you? Our team of Oracle Certified Experts has reviewed the enhancements, providing highlights for both User Experience and Tools:

User Experience

  • Enhanced UX One Roles: Drilldown Navigation Capabilities on Analytic Components
    Additional roles and their Analytic Components now provide drilldown and right-click options on context menus with a selection of applications that can be launched. This allows users to easily navigate from analytic graphical presentations to review and act upon detailed master data or transaction information.
  • Adding Business View Columns to Form (query only)
    EnterpriseOne continues to empower citizen developers by providing frameworks to personalize and extend their EnterpriseOne implementation. Citizen developers can add available business view columns on the form header, grid, or both dynamically as user defined objects (UDOs).
  • Grid Personalization
    EnterpriseOne now supports the capability to personalize grid labels as part of the Grid Format user defined object. This will be very helpful for customers to personalize grid labels with more intuitive names for their user base without the need of development.
  • Application Exit Personalization
    This enables customers to further simplify form navigation and personalize their experience to meet specific role, industry, and user requirements. With the User Defined Object citizen developers can show, hide, and rename form exits as part of the Personal Form experience.


  • Delivered Notifications
    In October 2017, JD Edwards announced our EnterpriseOne Notifications capabilities. This new functionality is more than just a pop-up alert; the notification system enables workers to remain in touch with critical conditions and events that happen continuously throughout the enterprise. Notifications are available to subscribers even when not signed in to the JD Edwards system, raising awareness and enabling quick action. In this TR JD Edwards has delivered 35 EnterpriseOne notifications that will make it easier to quickly adopt this new functionality and bring immediate business value to our customers.
  • Assigned Subscriptions
    This allows a manager or business analyst can assign subscriptions by role to groups with a common interest or common security settings, removing the requirements of an end-user to individually subscribe to a notification.
  • Delivered Orchestrations
    This release includes business orchestrations to help automate a Procure-to-Pay process with a supplier portal system that previously would have required integration customizations. Customers can quickly adopt these orchestrations and drive immediate business value in your organization.
  • Orchestrator Process Recorder
    This tool provides a simple, intuitive method for a business analyst to create an Orchestrator form requests from within JD Edwards EnterpriseOne applications; making the process of creating service requests a very natural, familiar process for any user who knows how to use JD Edwards EnterpriseOne applications.
  • Launch a Report (UBE) as an Orchestration Step
    This enhancement adds the ability to launch a JD Edwards EnterpriseOne report or batch job as an orchestration step, thereby giving the business analyst even more capability to automate and simplify business processes.
  • Confirmed Completion of Orchestrations
    This feature enables Orchestrator to record the status and details of its successful and unsuccessful REST service requests, allowing successful requests to be confirmed and unsuccessful requests to be retried or debugged.
  • Orchestrator File Transfer
    With this feature business analysts can use Orchestrator file transfer features to either retrieve a file or send a file to a known location using FTP, SFTP, or REST protocols.

Dev 101 Part I: Setting Up a Business Function Debugging Session In Visual Studio

As a Senior Managed Services Developer, I find myself in this sort of conversation all the time with my Apps teammates:

“Mike, can you figure out why X won’t work?”
“I’ll need to run that in debug to be able to see what is going on.”
“Can you just look at the code and get an idea of what is happening?”
“Kind of…”

Hence, the topic of this blog.
But first, let’s step back a little further in that conversation.

“The customer says when they exit the row, the extended weight is not being converted into the correct unit of measure. They expect this value, and they are getting this value”.
(That’s an important sentence, because if it wasn’t offered, the developer would have asked for this information eventually.)

“Can the scenario be reproduced?”
(That question is what the developer truly wants to know first thing off the bat.)

“Yes and no.”
(That’s the last thing a developer wants to hear.)

“I’ll need to run that in debug to be able to see what is going on.”
“Can you just look at the code and get an idea of what is happening?”
“Kind of.”
“What does it LOOK like is happening?”
“It looks like it would be a lot easier to see what is happening if I was able to run it in debug.”

And so it begins.

In JDE, all the modules are constructed in a basic sort of way. They call it Event Rule Logic, because the logic/code is executed based on user executed events, like in an application, or events that occur within a report or a UBE.

Given the scenario above, the developer would open the application in the Form Design Aid and look at the code behind the Row is Exited and Changed event on the grid. There will be a lot of code there. The tool JDE uses to debug Event Rule code is the ER Debugger. It could be run over that event and a “watch” placed on the desired grid column or variable that is being calculated.

Stepping through the code, the developer watches the values change from what it is, to what it will be, once the event ends.

In the case of the scenario described above, the developer would discover that the value is being calculated in a call to a Business Function.

The ER Debugger can only take the developer so far when troubleshooting this type of issue. He/she can see the value before the function call and see the difference in value when the function is returned, but there is no way to tell how the value was calculated without having the ability to debug the Business Function in Visual C++.


Definition Time:

A Business Function is a consolidated program that can be called from multiple places, so code does not have to be reproduced in the application or UBE every time that functionality is required.

Business functions are created in two ways, but ultimately end up in the same format. Whether is a Named Event Rule Business Function or a Business Function written directly in the C programming language, they are debugged in the same way using Microsoft Visual C++.

Now we are at the meat of the story.

In order to debug a Business Function in C, a project has to be set up Microsoft Visual Studio.

These are the steps this developer follows to set up a project in Visual Studio:

    1. Open Microsoft Visual Studio
    2. The first time it opens, no matter what version, it will ask you to select a Project Template. Select Visual Studio C++
    3. From Start Screen, select New Project.
    4. Next, Select Makefile Project

    1. Enter any name (I use Default)

    1. Click OK and Blank out Default.exe (or whatever you named your project) and click OK.

    1. You’ll now have a project that looks like this:

    1. You are now ready to begin adding C Source files to your project.

    1. Select Existing Item then find the Source directory.

    1. Find the function you wish to debug and select it.

    1. Now the function is in your project and can be debugged.

There are a few more steps required to begin debugging, but the setup is complete.

The process to this point will allow you to setup a project, view the code and get a feel for the structure.

Next time, I will demonstrate the process of Attaching to the Process (Activeconsole.exe) and actually debugging a Business Function!

Happy Developing!

UX One: Alert, Analyze, Act

UX One is the latest advancement in the JD Edwards EnterpriseOne user experience. Utilizing the Alert, Analyze, and Act model, JD Edwards is transforming the User Experience and maximizing productivity. These 3 principles in UX One empower you to be more effective and efficient, while performing your day-to-day tasks. With Alerts, you will be notified of what needs your immediate attention. With Analyze (charts), you will be able to view the status of key metrics at-a-glance. Lastly, with Act, you will have access to action items for a quick and easy response.

UX One includes a set of role-based solutions across the broad portfolio of JD Edwards products, and delivers the tools you need to personalize and create your own solutions, so that end users and citizen developers can make the user experience their own.

For more information, review the UX One Data Sheet

Collaborate 2018 Highlights

For those of you who made it to Collaborate this week, we trust everyone had a safe trip home after a very intense week full of great sessions. With 200+ JD Edwards Education Sessions available, I felt overwhelmed with the amount of information provided. I promised myself to summarize what I learned as soon as I got back home, this way all the information would be fresh and available when I needed it! Also, I wanted to share this information with those of you who could not make it out to the conferences this year.

From my point of view (based on the sessions I attended), this year there were 3 main tracks:

  • Maximizing the 9s
  • Continuous Delivery
  • Orchestrator and Notifications

Let’s dive in a bit on each category, and use the links provided to get more information.

Maximizing the 9s

No matter what version of JD Edwards you are on, it is important that you maximize the use of all tools available to you. From real business cases (learn from others) to Oracle’s latest, the overall experience was to convey the idea of taking advantage of the features and functionality available to improve user experience and ultimately maximize your investment. Many sessions highlighted the key features that have been delivered in previous Tools releases and how customers are leveraging these features.

Keynote Presentation:

Keynote Case Studies:

Features and Tools by Tool Release:

UX One Highlights:
Proving an Intuitive, Efficient, and Effective Way for Users to Perform Their Day-to-Day Tasks Using UX One:

New Functionality:
Announcing JD Edwards EnterpriseOne User Experience Enhancements, New Mobile Features, Modern ERP Enhancements, and Tools Digital Transformation Features (TR 

Announcing JD Edwards Lease Management Enhancements for Equipment and Other Non-Property

User Experience: Form Extensions (new in – Oracle Support Document 2384606.1

Continuous Delivery

Oracle’s commitment is to continue to enhance the 9.2 release with incremental enhancement packs, two or three times per year. The questions are, what does this mean and how will this approach affect us? The goal is to create a strategy to move from the “upgrade” to the “update” mentality.

The “Simplified Upgrade” was introduced in TR 9.2. In contrast with the “Traditional Upgrade”, where all the EnterpriseOne objects were replaced, the Simplified Upgrade process identifies and replaces only specific standard JD Edwards EnterpriseOne objects that have changed between application release 9.0 Update 2 or 9.1 and 9.2. The concept is to simplify the upgrade in terms of diminishing the requirement to retrofit custom changes.

JD Edwards Product Roadmap (Doc ID 1317204.1)

Oracle Support for JD Edwards EnterpriseOne Now Through at Least 2028

Understanding Upgrade Types after Tools Release 9.2 and Simplified Upgrade Process (Doc ID 2061189.1)

Additional Tools available:

  • Customize Object Analyzer (TR 9.2.1)
    The Customization Object Analyzer (COA) utility can be used to list EnterpriseOne objects that have been customized. This information is then used to determine the impact and level of effort needed to retro-fit the customizations into a newer application release of the system.  A review of the information, prior to performing modifications within the software, allows for a smoother and more predictable upgrade.
    Understanding Customization Object Analyzer and Application Configuration Analyzer (Doc ID 1499756.1)
  • Application Configuration Analyzer (TR 9.2.1)
    This tool that was introduced with applications release 9.1 and Tools Release 9.1.2. ACA will generate reports to identify differences between environments or data sources for: Processing Options, Data Dictionary items, and User Defined Codes. Comparing these between two environments or data sources is helpful for upgrades as an audit type tool or for helping to diagnose an issue that occurs in one environment but not another.
    Understanding Application Configuration Analyzer (Doc ID 2013069.1)
  • Object Usage Tracking (TR
    This tool provides information to determine frequency of objects being used within a path code. Object usage is captured by User/Role/Environment/Path code each time an object is launched by the user or the system
    Object Usage Tracking Functionality (Doc ID 2267215.1)
  • Simplifying Stay Current (TR 9.2.2)
    • Object Tracking and Enhanced Impact Analysis: This new capability provides tracking and visibility of business functions (BSFN) execution within JD Edwards EnterpriseOne. Business functions are the core logic processing for JD Edwards EnterpriseOne interactive/batch application, hence providing greater insight into their usage simplifies upgrade/patching processes, assists with troubleshoot performance, analyze issues, and manage compliance. Similar to tracking usage of interactive/batch application, business functions statistics are consumable by out of the box UX One analytics and helps customers identify business functions used in their business processes. WATCH VIDEO:
    • Batch Deploy of UDO Packages: This streamlines the process and reduces the effort of applying and deploying key enhancements such as UX One and other User Defined Objects (UDO). Customers can now deploy multiple (UDO) packages at the same time and to multiple environments along with a generating a deployment summary report.
    • Customization Workbench enhanced to support ESUs: The streamlined process of retrofitting customizations which was earlier available for Simplified Upgrade is now extended to support all customized JD Edward EnterpriseOne objects impacted by Electronic Software Updates (ESU).

Orchestrator and Notifications

Orchestrator is an integral part of an Internet of things (IoT) configuration with EnterpriseOne, supporting various integrations such as integrations with Cloud services, third-party applications, custom programs, and more. Combining the power of the JD Edwards EnterpriseOne Orchestrator and AIS Server enables organizations to:

  • Connect IoT data to your business data. The Orchestrator enables customers to collect, filter, analyze, and act on real-time data as it is being transmitted by IoT devices.
  • Simplify the integration of IoT data with the JD Edwards EnterpriseOne Orchestrator Studio. Available starting with EnterpriseOne Tools, the Orchestrator Studio is an intuitive, easy to use web-based application that business analysts can use to create orchestrations that tie IoT device data directly to JD Edwards EnterpriseOne applications, thus eliminating costly, mundane, and error-prone manual input.
  • Extend integrations to other solutions. Starting with EnterpriseOne Tools and Orchestrator Studio 5.1.0, the Orchestrator functionality has expanded to support various integrations including integrations to Cloud services, third-party applications, custom programs, and many more. Keep using it for integrating JD Edwards EnterpriseOne with IoT devices. But start using it for all you REST-based integrations to JD Edwards.

Fresh out of the oven with Tool Release 

Process Recorder

With Orchestrator Studio 6.1.0 and Tools, you can access the Orchestrator Process Recorder in EnterpriseOne to record business process steps directly in the system and save the steps as a form request, which you can then open in the Orchestrator Studio and add to an orchestration. The Process Recorder makes it easier than ever before to turn traditional manual business processes into automated functions with orchestrations. 

Confirmed Completion of Orchestrations

This feature enables Orchestrator to record the status and details of its successful and unsuccessful REST service requests, allowing successful requests to be confirmed and unsuccessful requests to be retried or debugged.

Launch a Report as an Orchestration Step

This enhancement adds the ability to launch a JDE report or batch job as an orchestration step, thereby giving the business analyst even more capability to automate and simplify business processes. 

Orchestrator File Transfer

Business analysts use the Orchestrator Studio to create orchestrations that enable automation of their previously manual business processes, as well as pass and retrieve data between JDE and external systems. Many automated business processes require the movement of physical files from one system to another. To accommodate this requirement, business analysts can use Orchestrator file transfer features to either retrieve a file or send a file to a known location using FTP, SFTP, or REST protocols. These features enable you to create a FTP connector or REST connector in the Orchestrator Studio, that when added to an orchestration, enables the transfer of files to an external server. For example, a business analyst could create an orchestration that runs a JD Edwards EnterpriseOne report and then sends the report output (PDF file) to a document management system via FTP, SFTP, or REST.

For more information and tutorials:

Notifications enable you to stay connected to your business by pushing valuable information to you. More than just a pop-up alert, the notification system enables users to remain in touch with the critical conditions and events that happen continuously throughout the system, and to quickly act upon those events even when they are not signed on to the JD Edwards system. Using Orchestrator Studio, business analyst can design notifications specific to their organizations processes, rules, and required action. Users can subscribe to available notifications and receive updates by email, by text, as browser pop-ups, within the new notification list on the EnterpriseOne menu bar, or in the Work Center. A scheduler allows the notifications to run periodically and automatically, and continuously monitoring the system for critical conditions and events. When a critical event or exception is detected, the notification system will notify the appropriate users via their preferred delivery.


Delivered Notifications

Many notifications have been created and delivered for use by JDE customers via UDOs (User Defined Objects). Each system has its own set of notifications that can be downloaded via the Update Center or Change Assistant. Use the following link to review and download them:

JD Edwards EnterpriseOne Delivered Notifications – 2365066.1

Fresh out of the oven with Tool Release

Assigned Subscriptions

Assigned Subscriptions remove the requirement for a JDE users to subscribe individually to receive a notification. Now a manager or business analyst can assign subscriptions by role to groups with a common interest or common security settings. The assigner can allow subscribers to opt out of assigned subscriptions, or the assigner can disallow subscribers to opt out, thus ensuring that they receive critical notifications.

For more information and tutorials:

Highlights from the Latest JD Edwards E1 Tools Release

As you know every JD Edwards EnterpriseOne Tool Release provides a handful of new tools and enhancements. With Oracle’s concept of release a new TR every 3 to 4 months, it makes difficult for everyone to keep up with what’s available. Use this document with a quick reference of what’s available on each Tools Release. Our hope is that will help you to plan your TR upgrade accordingly.

Features & Tools by TR

  • Tools Release 9.x GA
    Release Release Date Status
    Tools 09-APR-2018 Premier Support
    Tools 22-JAN-2018 Premier Support
    Tools 9.2.2 13-OCT-2017 Premier Support
    Tools 28-JUN-2017 Premier Support
    Tools 25-APR-2017 Premier Support
    Tools 9.2.1 16-NOV-2016 Premier Support
    Tools 26-JUL-2016 Premier Support
    Tools 08-MAR-2016 Premier Support
    Tools 13-JAN-2016 Premier Support
    Tools 9.2 06-OCT-2015 Premier Support
    Tools 21-JUL-2015 Premier Support
    Tools 21-APR-2015 Premier Support
    Tools 27-JAN-2015 Premier Support
    Tools 9.1.5 09-DEC-2014 Premier Support
    Tools 9.1.4 17-DEC-2013 Premier Support
    Tools 9.1.3 08-APR-2013 Premier Support
    Tools 9.1.2 18-SEP-2012 Premier Support
    Tools 9.1 06-DEC-2011 Premier Support
  • TR 9.1.2 and above
    • Customize Object Analyzer (ESU required, Xe thru 9.1)
    • Application Configuration Analyzer (ESU required, 9.1 and above)
  • TR 9.1.5.x and above
    • Alta UI Adoption
    • Media Objects drag & drop
    • Simplified Navigation (KIOSK Mode)
    • Email and Calendar Integration
  • TR 9.2 and above
    • OMW Web (P98220W)
      • To promote UDOs between path codes or environments
      • To Import/Export .zip files containing UDOs
    • Application Interface Services (AIS) Server
    • Simplified Upgrade Method: from 9.0 Update 2 to9.2 or from 9.1 to 9.2
  • TR 9.2.0.x and above
    • Orchestrator Studio – TR
    • Watch List Pane for Composed Pages – TR
    • List View Grid Formats – TR
  • TR 9.2.1 and above
    • UX One
    • Springboard for Composed Pages
    • Watchlist for Databrowser
    • Enhanced Media Objects
  • TR 9.2.1.x and above
    • Object Usage Tracking – TR
    • MO store in DB or File System – TR
    • Enterprise Search: enabling task search from Fast Path – TR
  • TR 9.2.2 and above
    • Orchestrator Studio: Notifications, Subscriptions and Scheduler
    • Server Manager Enhancements
  • TR and above
    • System Simplified Upgrade on a One-Click Provisioned Target
  • TR and above
    • Adding Business View Columns to Form (Query Only)
    • Application Exit Personalization
    • Grid Label Personalization
    • Assigned Subscriptions
    • Orchestration Enhancements: Confirmed Completions, Process Recorder, Launch UBE as step in Orchestration and File Transfer

More Tools

  • Runtime Features
    • Auto-Suggest –TR 9.1 and above
    • Hover View –TR 9.1 and above
    • Change Confirmation –TR 9.1.3 and above
    • Dropdown (UDC) –TR 9.1.3 and above
  • Setup
    • P958973 – Definition
    • P958974 – Authorization

UDOs Available

There are 11 UDOs available:

  • Grid Formats
  • Advanced Queries – TR 9.1
  • One View Reports – TR 9.1
  • E1Pages – TR 9.1
  • One View Watchlists – TR 9.1.3
  • Composite Application Framework (CafeOne) – TR 9.1.3 (URLs and BI), TR 9.1.4 (E1 Apps)
  • Composed Pages – TR
  • Personal Forms – TR 9.2.1
  • Images/Icons – TR 9.2.1
  • Search Groups – TR
  • Orchestrations/Notifications – TR 9.2.2
  • More to come…

Manual Rollback Functionality

As an EmeraldCube Application Managed Services Consultant, I get a lot of tickets and questions about incorrect inventory commitments.  And I’ve found that a lot of users are not leveraging the Manual Rollback functionality for F41021 – or maybe are completely unaware of it.

What is the Manual Rollback Process of Item Location (F41021) File (P42210/R42210)?  And when should you use it?  I’ll cover both; let’s get started.

When a transaction error occurs in a Distribution application, all files except the Item Location (F41021) will roll back.  This means that the transaction will be “undone” or removed from the tables such as F4111 Item Ledger, etc.  However, since the rollback is not automatic in the Item Location file, this leads to incorrect commitments in the F41021.

It is common to run the Sales Order Repost (R42995) and the WO Repost (R3190) in attempt to update or correct your commitments.  However, if I have potential rollback records for F41021 hanging out there, I could cause a bigger mess if I don’t deal with those first.  So, before I run either Repost job, I always look in the Work With F42210 Commitments Recover (P42210) for any F41021 records that may need to be rolled back.

For Example:

Item 1144 has a Qty -12 SO Hard Committed.  However, there are no Open SO’s for this item.  I could run the SO Repost (R42995) in attempt to realign the commitments, but I would first have to create a dummy SO for this item to get the system to “see” a commitment, and then later delete that dummy order. ***Unless you are on 9.2 – more on this later…

Instead, l check the Work With F42210 Commitments Recover (P42210) and I find a record I can roll back.

I select the record and Row Exit to “Roll Back.”

Now, I can reinquire on my item in Detailed Availability.  That -12 SO Hard Commitment is gone and my commitments are updated correctly.

*** (9.2 Enhancement) I mentioned earlier that if you ran the SO Repost (R42995) you would need an open SO for that item or you would need to create a dummy order and later delete your order.  What a pain!  On 9.2 and later you can run the Refresh Inventory Commitments (R42990) instead.

The R42990 can be run at the same time you run the R42995.  These 2 UBE’s run over different data sets, so they are mutually exclusive and designed to run in tandem.  The R42990 runs over F41021, F4101, and F4102, refreshing commitments for those items that do not have an active sales order.  The R42995 runs over F4211 and updates commitments for those items on active sales orders.

So, do you want to wait until you notice a discrepancy before looking for records to roll back?  Or do you want to run the F41021 Commitments Recovery (R42210) on the scheduler?  It would be best practice to run the R42210 before you run the reposts,  and it would be best to run all of them while nobody is creating new transactions in the system.

Before you set the R42210 up on the scheduler though, you will want to consider clearing out the F42210 or at least reviewing each record one by one.  There is a possibility that some of those incorrect commitments were cleaned up using SQL.  If so, rolling back the commitment could create a new problem requiring SQL clean up.

Nichole’s Commitment Correction Checklist:

  1. Review P42210 for potential rollbacks.
  2. Research each rollback, and match it to an invalid open commitment in F41021.
  3. Ensure no SQL fixes have been done.
  4. Perform necessary rollbacks, and delete unnecessary ones that have been corrected via other means.
  5. Either schedule or regularly run R42210, followed by SO/WO reposts, to keep your commitments clean.

Follow the above rules, and your users’ commitment issues will be gone forever – well, at least greatly reduced.