While there is certainly a lot of hype and excitement around E1 9.2, there is also a lot of confusion. The 9.2 release isn't that much of a change per se; it's
largely new sophisticated and savvy tools built for the Business Analyst and super user to provide highly personalized configuration.
The goal is to relieve IT from needing to develop many of the smaller and more frequent personalization requests end users submit. "Citizen Developers" can now safely develop personalized screen layouts without the need of traditional coding skills. Citizen Developers are users authorized (given security access in JDE) to develop apps via the new tools in 9.2—IoT Orchestration Studio, Pages Composer, One View Financial Statements (OVFS), etc.
Many of these new features are 'light' versions of their more robust toolsets. They have been built to facilitate drag-and-drop development for smaller projects. The Pages Composer tool is a modified 'light' version of the Pages Generator tool. OVFS is a modified 'light' version of One View Reporting (OVR). The IoT Orchestration Studio tool is a 'light' version of Business Services (BSSV).
While we do not discuss each and every feature Oracle released with EnterpriseOne 9.2, we have highlighted the features we have received more questions around.
1. One View Financial Statements
3. Internet of Things (IoT) Orchestration Studio
4. Pages Composer
5. User Defined Objects (UDOs)
One View Financial Statements (OVFS) is a feature of One View Reporting (OVR) itself. OVFS gives Financials staff the flexibility to design their own highly personalized reports rather than tasking IT to develop reports through OVR capabilities.
Four pre-loaded OVFS reports are included with licensing—Balance Sheet by BU / Consolidated Balance Sheet by BU and Income Statement by BU / Consolidated Income Statement by BU. Import and Export functionality (via .zip files) exists to allow transfer of configured reports across environments.
OVFS uses modified versions of Query Manager and OVR functionality. Companies must have a license of OVR to utilize OVFS, and OVFS "developers" should be familiar with OVR functionality, Query Manager, and BI Publisher Layout Editor.
22 modules generate or store records from which reports can be generated from (A/R, A/P, G/L, Sales Order, Inventory, etc). Reports are designed by pulling records from the Accounts Master (F0901), Account Balances (F0902), and Business Unit Master (F0006) tables.
OVFS reports are configured by placing Row Definitions (P09310) and Column Definitions (P09320) onto Statement Definitions (P09340). Statement Definitions are then assigned layout versions, after which BI Publisher Layout Editor is used to drag-and-drop design each of your layout versions. Query Manager is used to define data selection. The system will account for the level of detail rollup, AAI grouping, currency codes, and other factors.
Considering data extraction, remember OVFS is a modified version of OVR. Oracle notes in the administrative tasks section of their One View Administration Guide "One View Reporting is an interactive solution that is not designed to retrieve tens of thousands of database records. If you need to work with a large amount of data, using either the Read Only JDBC driver or a UBE report will provide better performance."
Additionally noted is "When you run a One View report, the HTML server retrieves the report data. The data is then passed to the BI Publisher server for report rendering and generation. This means that running a One View report adds more load to the HTML server and the back end database. The additional load is similar to adding more query users in the system."
How many records does the system retrieve when extracting data for OVFS reports?
The default configuration setting in OVR (unless changed) for retrieve record count is 500. OVR/OVFS demos are very likely retrieving this 500 record count setting which is why reports in those demos render so quickly. We did not find an official maximum limit noted in the Implementation Guide—the default system limitation is 10,000 records.
Oracle's Introduction to One View Financial Statements includes how to set up your system and create reports.
Watchlists are part of One View Reporting; therefore a One View foundation license is necessary to enable them.
Watchlists display notifications users would like to be alerted to (such as approaching/passed thresholds or outstanding tasks) using real-time information. This real-time information updates when a user opens the Watchlist menu, or on a set refresh rate. Notifications use bold and red formatting to easily identify warnings or passed thresholds.
Watchlists allow users to define criteria for their notifications. The criteria displays data pulled from EnterpriseOne queries; therefore Watchlist notifications can only be set up for EnterpriseOne forms that support query functionality. Users cannot create a Watchlist for E1 forms that do not allow queries. This also means users must first create each of their queries within each application for every notification desired.
Watchlists reside as a menu option dropdown next to Recent Reports and Favorites, or in E1 pages (composed or classic). The system accounts for security, meaning a system administrator needs to grant creation, viewing, and sharing access.
The major benefit of Watchlists is immediate recognition of data—outside of EnterpriseOne applications and on user home pages—such as warning thresholds, refresh intervals, and maximum record counts. Displaying this data external of applications vastly improves productivity and reduces the web server load because users do not need to open (or remember to open) each application to view the information they need.
Oracle's One View Watchlists Implementation Guide shows you how to create Watchlists.
IoT Orchestration Studio houses all orchestrations—immediate, real-time transformation of raw data from third-party IoT devices (such as sensors) to valuable and transaction-capable information in JD Edwards EnterpriseOne applications.
Orchestration Studio uses a GUI for the Business Analyst (Citizen Developers) where the need of traditional coding skills is not necessary. An orchestration is a master process defined by four components—white lists, rules engine, cross-references, and service requests.
For traditional IT, data is passed in as XML docs. JSON key/value pairs to create your white lists, cross-references, rules, and service requests.
|For the Citizen Developer, IoT Orchestration Studio uses JD Edwards applications to generate XML/JSON behind the scenes. The Business Service Cross Reference (P952000) application is used to create and manage cross-references and white list records for IoT orchestrations. Accessing the Studio itself is done via a URL that you will need to ask your system administrator for, and you'll need to be authorized in Server Manager.|
This type of development is simpler and better for mobile devices in which most cases no Java is required. The EnterpriseOne AIS server instead calls for metadata.
Your Administrator will need to complete initial server configuration to run Studio and will need to use Server Manager to deploy both an EnterpriseOne AIS (Application Interface Services) server configuration to run the client, and an ADF (Application Development Framework) server to run the Studio. Additionally, you'll need to be on Tools release 18.104.22.168 (22.214.171.124 for E1 9.1) and you'll need to download several IoT Orchestration Components from the Update Center.
From Oracle's Internet of Things Orchestrator FAQs, Q. "Will the JD Edwards EnterpriseOne IoT Orchestrator replace my Business Services?"
A. "E1 Business Services server is a robust tool for integrating JD Edwards EnterpriseOne inbound and outbound transactions as web services using the SOAP protocol. For certain integration patterns, the Business Services server remains the method of choice. The IoT Orchestrator—and more specifically the Application Interface Services (AIS) server—provides a new alternative integration method based on the REST service protocol. The nature of IoT device integration makes the REST protocol a better choice for IoT orchestrations. Both BSSV and AIS continue to be important components in the broader JD Edwards EnterpriseOne Integration Platform."
Oracle's Internet of Things Orchestrator Guide includes how to set up your system and design and manage orchestrations.
Create Enterpriseone pages (with clickable process flows) based on user defined and role-based layouts using drag-and-drop design. Access multiple content types on a single page—web pages, E1 apps, OVRs, watchlists, classic pages, designer panes, external URLs, OBIEE objects, and ADF apps.
The benefits of Pages Composer are that you do not need to know HTML, you can re-size content frames at runtime, and the composed pages are supported on mobile devices. Pages Composer does have limited capabilities (only one ADF app, OVR report, and watchlist is allowed per page) compared to the existing Pages Generator tool. Pages Generator uses JAVA script for more advanced functionality.
You access Pages Composer through your sign-on Personalization menu, under the Manage Content section. Your administrator grants permission for creation, viewing, and managing composed pages. Remember, you must have access granted for any content type you want to add as the system will carry security through to composed pages.
Understand more about each content type—such as the designer pane is how you insert E1 app buttons—and working with composed pages through Oracle's EnterpriseOne Tools Foundation Guide.
User Defined Objects are one of eight web objects—queries, grid formats, Composite Application Frameworks (Café One), OVRs, watchlists, classic E1 pages, composed pages, and images. You can create UDOs for your own use or share them for public use, of course subject to approval and permissions
granted by your system administrator (through Security Workbench).
The Work with User Defined Objects application (P9822OU) is used to manage UDOs. This application helps you control the life cycle for creation and management. P9822OW is a "web OMW" (object management workbench) created specifically for importing/exporting UDOs. UDOs are not stored locally; they work strictly with tables.
After upgrading, grid formats and queries are considered UDOs and moving them to and from PD to PY is now possible. The Table Conversions Workbench is used to bring previous personalization into 9.2.
Oracle's User Defined Objects Approval Application Guide will step you through the UDO approval process.
Learn more about EnterpriseOne 9.2 and initatives including new modules, new application and technical enhancements/features, and documentation and resources through Oracle's Learning Library (LearnJDE.com).