Databrowser Security – Part I

Recently, a client came to me with a request to give temporary databrowser access for just a few tables to a new role that was being created. My first thought – not possible, based on having to setup table security within security workbench to deny access to all tables and grant back access to the tables the client wanted the role to see. This would cause a complete loss of access to E1 data for the user, except for those few tables.

But, as many of you know, I love a security challenge.  And this couldn’t be the first time someone has had this request, so I did a little research into the databrowser security and setup.  Success!  I found that starting in 9.1, there is an indirect way around the issue by using public queries, and, even better, in 9.2 there is a new way to setup security to allow the viewing of specific tables through UDO security.

I’m going to focus this blog on the 9.2 solution, since the client that asked the question has just upgraded to 9.2 and that was my focus. But, for my 9.1 friends, stay tuned for part 2 in the next few weeks, where I’ll discuss the 9.1 workaround solution.

With the release of EnterpriseOne 9.2, the User Defined Object enhancement has made it possible to grant users the ability to see specific tables with UDO View security for specific table/business view in Databrowser. The following is a step by step guide in setting up Databrowser security. For our example, we’ll focus on a requirement to give the role DBTROLE access to the F1201 table only.

Step 1: Access Security Workbench (P00950).

Step 2: Select Form menu and choose Set Up Security, Databrowser

Step 3: Enter the role and check the options shown below:

Step 4: Click OK. Do not exit security workbench as you will need to use it again.

The role DBTROLE now has access to use the databrowser application, but also has access to view all tables currently. Using User Defined Object (UDO) View security, we can lock down the role to only access the F1201 table.

Step 1: Access Security Workbench (P00950)

Step 2: Select the Form menu and choose User Defined Object View

We will now add a record to deny all tables to role DBTROLE and grant back access to the F1201.

Step 3: Complete the following fields shown below. NOTE: The View column is very important! A red box means view access will be denied for what you have setup, and the green circle grants access.

Step 4: Clear security cache on the web instance and test.

And that’s it!  That’s all it takes to implement some tighter controls over what users can access within Databrowser in 9.2.  Stay tuned for part 2 of this blog, where we talk about some potential workarounds to accomplish the same goals in 9.1.

Runtime Features

Our team of JD Edwards experts has compiled this post to take you through setting up and using some of the pre-defined Runtime Features, including Auto Suggest, Change Confirmation and Hover Viewer:

Auto Suggest feature enables users to search for and filter text on fields where Auto Suggest is enabled. Auto Suggest searches pre-defined tables and returns records that match text you type into a field. As you type text into a text field, one or more possible matches for the text are found and immediately presented to you in the grid around the field.

The Change Confirmation feature provides a warning prompt that can be displayed within an application when a user takes an action that could result in data loss. Configure a warning to be issued if a User has:

  • Pressed Cancel on a form where something has been changed.
  • Pressed Find on a form where something has been changed.

Hover Viewer or pop-up forms are message forms that show context-based information about a form or grid field. This helps users to view information about form and grid fields without having to navigate away from their current application view. Check out this brief video for a quick overview of the Runtime Features mentioned above.

Tools Release 9.2.3 Highlights

General Availability

November 8th, 2018

Highlights

  • Orchestration Enhancements
  • Notification Framework Enhancements
  • Form Extensibility Enhancements
  • UX One Foundation Simplifications
  • 64-bit Enablement
  • Updated Platform Certifications

Orchestration Enhancements

  • Launching orchestrations from within EnterpriseOne events. This enhancement provides a new Business Function that launches an orchestration or a notification from within a JDE Event Rule. JD Edwards developers can invoke this business function, allowing to trigger an orchestration from EnterpriseOne interactive and batch applications using events and/or table triggers.
  • Orchestrator Monitor. This new feature provides visibility into the health and operation of orchestrations and notifications. A new dashboard is available providing a visible status of orchestrations and notifications as they run.

  • Error handling of orchestration steps: Sometime the design of orchestrations needs the control over how an error in one step might impact the entire orchestration. This new error handling feature enables the designer to specify whether an error in a step should cause the entire orchestration to fail or continue to process. The designer can specify an error message and an orchestration to launch in case of failure.
  • Expanded Orchestrator to consume CSV data file. This enhancement enables orchestrations to read data in comma-separated values (CSV) format, which is easily exported from spreadsheets.

Notification Framework Enhancements

A new Work Center dashboard is available in TR 9.2.3 enabling users to have a better control over their notification messages. This new page, known as “My Worklist”, provides a view of the user’s Notifications and Work Center Messages.

Form Extensibility Enhancements

In this Tools Release, Form Extension is available for entry forms and power forms. This enhancement enables citizen developers to add business view columns to Fix Inspect forms. These extensions can be further consumed on the available personalization and extensibility frameworks such as personal forms, CafeOne and orchestrations.

UX One Foundation Simplifications

JD Edwards continues to deliver improvements to the UX One Foundation. Tools Release 9.2.3 includes the following capabilities:

  • Ability to inquire and view user defined object dependencies.
  • Ability to scan, retrieve, and store user defined object dependencies for Composite Pages.
  • Ability to inquire on UDO view security records.
  • Ability to copy view security records from one user/role to another user/role.
  • Improvements to the Web OMW application to:
  • Easily add new or existing UDOs to an OMW project
  • Copy an OMW Project that contains UDOs

64-bit Enablement

Tools Release 9.2.3 will provide 64-bit processing on the Enterprise Server.  The 64-bit enablement has no impact to JD Edwards business processes or business data.

  • Tools 9.2.3 will deliver JD Edwards Enterprise Server foundation systems and business functions that are compiled for either 32-bit or 64-bit processing.
  • 64-bit enablement will be available only for Application Release 9.2.
  • Customers on Application Release 9.2 will have the option to deploy Tools 9.2.3 as 32-bit or 64-bit.

  • Tools 9.2.3 64-bit will be available for the following JD Edwards certified platforms (see the Certifications tab on My Oracle Support for current certifications):

For additional information please review Cubeology Course:

JD Edwards E1 Tools Release 9.2.3 64-bit Enablement

Updated Platform certifications

Tools Release 9.2.3 includes the following platform certifications:

  • Microsoft Visual Studio 2017 (Enterprise & Deployment Server, Development client) – Doc ID 1
  • Mozilla Firefox 60 ESR
  • Apple iOS 12

Support Policy:

JD Edwards EnterpriseOne Tools 9.2.3 Release will support Application Releases 9.1 and 9.2.

Tools 9.2.3 will not be supported with Application Release 9.0 or 9.0.2 which goes into Sustaining Support effective December 2018.

For details visit: Oracle JD Edwards EnterpriseOne Tools 9.2.3 Release Support Policy (Doc ID 2470298.1)

To download:

  1. Login to MOS
  2. Navigate to [Patches & Updates] for JD Edwards
  3. Using the [Search] option, provide the following and click on [Search]:

  1. Proceed downloading the correspond components:

Preventing Chaos: Year End Prep NOW

Ah, year end – that special time when JDE users begin to look slightly more stressed than usual, and talk turns to integrities, and closing, and consolidations, and more.

If you work in Accounting, then year end is just a part of your regular job or process. You might start stalking the Oracle Support site for the 1099 ESU, so you can remind IT to install the updates. You may even have a checklist that you follow, to make sure you run your integrities, and update your recurring JEs, and finally run R098201 Annual Close.

But, did you ever consider year end processing outside of Finance/Accounting? Let’s face it: JDE is an ERP system, with all the “inter-connectedness” that comes along with that. It’s not enough to run the close, finalize the financial statements, and roll the date forward. You have to think about all the other folks who have processes to do before Accounting pushes that big red CLOSE button. (I know, I know – there’s no big red button. It’d be a lot cooler if there were!)

If the year end processes aren’t considered or followed for all the other JDE functional areas, you can end up with messes to clean up after the new year – or even errors during processing. For example, if pricing changes or expires, and the appropriate actions aren’t taken to enter new pricing or update existing orders, then credit memos could be in your future.

Or, if you forget to do the PDBA Rollover in HCM, employees’ vacation and sick balances will not be created for the new year. And for those of you that like to live dangerously and only extend your Work Day Calendar out one year – your MRP won’t plan if you haven’t created the next year’s calendar records. (By the way, do yourself a favor and extend your Work Day Calendar out 5 years into the future – trust us.)

Tips for a successful year end season:

  • Get started early. Late October/early November is a good time to begin.
  • Consider organizing a Year End Task Force, with representatives from all areas of the business.
  • Make a task list or plan, with deadlines and dependencies.
  • Data cleanup can be started now. Run integrities, and fix any issues in November and December, to make January less painful.
  • Look up the year end bugs/ESUs – 1099s, W2s/T4s, ACA – and all the pre-requisites and Special Instructions that come along with them. It’s a good idea to apply these as soon as they are available, then test them in PY.
  • Request a data refresh of PY to help facilitate testing.

Year end is busy enough, with holidays, and IRS filings, and financial due dates. Don’t make more work, or a mess, if you can avoid it. To get a head start on your plan, download our Year End Checklist (complete with ESU Doc IDs), and begin ticking off the boxes NOW. You can even add your own company or business-specific tasks, then make it part of your regular year end routine. There’s no way to avoid the work that comes at year end, but solid preparation can help avoid chaos and complete the year with less pain.

Classic and Composed Pages

Classic and Composed Pages provide you with a user-friendly interface from which you can access applications, web pages, interactive graphics, and so much more! It’s a basic HTML page where you can include items that enable you to navigate more efficiently and effectively across your JD Edwards system. Classic Pages or E1PAGES, have been around since TR 9.1, almost 7 years since its GA back in December 2011. Are you taking advantage of this powerful tool? – Take a look at this tutorial for a quick review on how to create E1PAGES.

Beginning with tools release 9.2.0.2, JD Edwards introduced a new page composer tool which enables you to design and create user defined layouts without HTML coding knowledge. It’s very simple and can be accessed through the web user-interface. Did you know UXOne layouts were created using this tool? This tutorial will also demonstrate how to use the tool to create simple layouts using: 1-Designed Pane, 2-EnterpriseOne Application, 3-Watchlist Pane and 4-Springboard Pane.

Scheduling and Purging Scheduler Jobs

INTRODUCTION:

This document is to be used as a reference to create and edit scheduler jobs and includes details on how to make changes to existing jobs by purging existing job scheduler records.

P91300 – Job Scheduler application

Running batch jobs to create reports requires users to submit them manually, but another alternative is to schedule them to run at specific times using the EnterpriseOne Scheduler.  Adding these jobs to the EnterpriseOne scheduler is done by the scheduler application (P91300) that allows us to schedule jobs periodically by time (day, week, month, year) or based on a specific interval. The scheduler also allows you to specify the server and time zone to run the job in, run it in specific job queues, and have either of the logging options turned on. It also lets us resubmit a job if it fails.

When we define a scheduled job, the parameters of that job are stored in the Scheduled Job Master table (F91300). The system writes records to the Scheduler table (F91320), indicating each time that the job should be launched. As the job runs, the ‘Job Monitor’ monitors the progress of the job.

Purging Scheduled Jobs

Not all UBE purges scheduled records can be deleted using the DELETE button. We can ONLY delete scheduled records which have status 01 (Scheduled) or 50 (Hold) using the DELETE button. For the rest of the statuses, you need use UBE R91300B to purge the existing records from the list of future job occurrences.

R91300B
WARNING! Running the R91300B without specifying the specific scheduled job to delete upcoming scheduler records for will result in deleting upcoming scheduler records for ALL scheduled UBEs, so be precise in the Data Selection to specify the specific name of the report schedules you want purged.

Here is an example of what the data selection should look like:

The R91300B’s Processing Options allow this report to run in a specific Time zone and in PROOF or FINAL mode. Running this UBE in PROOF mode allows the Administrator to check the PDF report without changing anything in the Scheduler table.  If the results of running this report in PROOF mode are satisfactory, run the UBE again in FINAL mode, and this will delete those selected records from table F91320.  For audit purposes, table F91300 will not be purged, just the R91320.  The R91300B can be run locally or on the Enterprise/Logic server.

If you happen to purge off that specific job’s scheduler records with the R91300B without the Data Selections, the scheduled job must be activated and run again in order to create new scheduled job entries. So, when you activate the job again after purging, update the scheduler to add a future date, which means you are basically setting up the first run date/time again.  If the job date and time are not entered as a future time, the job will not be submitted again.

In order to get the job running, we can follow either of the two options:

  1. Use the ‘Reset Schedule’ button.
  2. OR Get to ‘Job Revisions’ and give it a new start date/time of the current date or later.

Reference JDE Doc ID 1292206.1

To make Purging scheduled jobs easier, we have a feature in EmeraldPrism that can automate this process. EmeraldPrism is our JDE monitoring and alerting tool, and it performs regularly scheduled purges for these and other technical tables. To learn more, visit http://www.emeraldprism.com.

Balance Sheet Lessee Accounting

With the advent of FASB and ISAB standards IFRS 16 and ASC 842, respectively, companies must now track leased assets and report long-term lease liabilities on their balance sheet. For more information about each standard, or to determine the criteria for balance sheet vs expense accounting, please review the FASB and IASB standards. To accommodate these requirements, JD Edwards has released new Lessee Balance Sheet Accounting functionality for 9.1 and 9.2. For customers running 9.0 and older releases, no new functionality is planned. However, see Doc ID 2420929.1 for some suggestions on how to leverage standard JDE functionality for Lease Accounting.

Key dates:

  • For public entities, the standards go into effect for annual periods beginning after 12/15/18 (i.e., 1/1/2019).
  • For all other entities, the standard begins for annual periods beginning after 12/15/19 (i.e., 1/1/2020).
  • Early adoption is permitted for all entities.

So, now you know that Oracle has delivered enhancements, and you know the deadlines for implementation. But where do you go next? Preparing for the new Lessee Accounting requirements can be daunting, but we’re here to help. Before you begin your setup tasks, some things to consider:

  1. Are your leases Property or Non-Property leases? Both types are supported, but the setup is a little different for each. Take some time to gather and review your schedule of leases, and categorize each as Property or Non-Property.
  2. Do you want to align your Non-Property lease assets with the same categories as your regular Fixed Assets? If so, take the time to assign cat codes to your leased assets ahead of time. If not, consider creating new category codes to identify leased assets separately.
  3. Will you calculate and remit lease payments via AP through the Lessee Accounting functionality, or do you want to handle AP payments for leases separately/manually?
  4. What bill codes/charge classes do you require for Lessee Accounting? Consider all facets of a lease, such as initial direct costs, fees, actual rent, etc., then be sure to set up a Bill Code for each.
  5. Consider how to account for leases that are already mid-life. Will you enter Journal Entries for these, or will you allow the Lease Commencement process to create the entries? Adjustments may be required.

To get started, download our Initial Setup document for Balance Sheet Lessee Accounting, which covers initial setup, along with next steps and helpful Oracle links.

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 9.2.2.4. 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 9.2.0.2 and above
  • Images/Icons – TR 9.2.0.2 and above
  • Personal Forms – TR 9.2.1 and above
  • Search Groups – TR 9.2.1.2 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 9.2.2.2 and above
  • Form Extensions – TR 9.2.2.4

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).