Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« November 2020 | Main | January 2021 »

December 29, 2020

Essbase 21c Support Matrix


*OS Update Level: 
The version listed specifies the minimum update level / service pack / technology level certified.
For example, 6 means that 6 and higher is certified.


A plus sign (+) after the fourth digit in the version number indicates that this and all higher
versions of the JRE/JINIT/JDK extensions are certified. For example, 1.8.0_131+ means that
1.8.0_131 and any higher 1.8.0_xxx versions are certified.

Client Support:



The Oracle databases listed in this column are supported on all platforms that the database supports.
heck Database Certification Matrix for details.
All Oracle configurations - Single instance, RAC, XA, DR are supported. No support with Oracle DB XE.
Oracle recommends using latest Oracle DB PSU's. For latest recommended patch information, refer to 

Direct SQL: 
Direct SQL allows users to connect to the data sources by provide direct SQL in rules files

Platform SQL refers to performing a data load or dimension build using the Connections
and Datasource constructs.



ID & Access:

Note 1: 

For both Oracle Essbase and Oracle Essbase on OCI - Weblogic Embedded LDAP is provided and
is not recommended for production use cases.

Note 2:

All the security provides supported are based on the Weblogic security mode. For details refer:

December 28, 2020

"EPMLCM-13000: Service currently not available error" upon implementing SSL in EPM 11.2.2 environment

Issue: After installed and configured EPM 11.2.2 environment, end to end SSL has been implemented for the below components.

OHS, Hyperion Financial Management, Financial Reporting, Financial Data Quality Management, Enterprise Edition, Calc Manager and WebLogic.

All components seems working as expected; however whilst try to export artifacts under Application groups in Shared Services for FDMEE & Calc Manager, the migration status report shows the status Failed and the error as below:

Error "EPMLCM-13000 - Service currently unavailable"




Cause: This has been identified by Oracle as a BUG 32079785 - ERROR "EPMLCM-13000: SERVICE CURRENTLY NOT AVAILABLE" WHILE IMPORTING FDMEE ARTIFACTS

Possible Solutions to fix this issue --

Solution 1: You can try adding a directive to the ssl.conf file of Oracle HTTP Server:


LimitRequestLine 20000



Solution 2: Try applying the Patch Set Exception (PSE): 32101854 which was provided by Oracle Development for the Release to address this Bug.

Solution 3: Alternatively, you can also try the below steps which we had followed to proceed with the environment. 

Import and Export FDMEE Schema from other environments such as intermediate server ( to QA (11.2.2); and from QA to Prod, DR and Dev.







Welcome Anaplan HyperModel!

Executive summary

In today's world, regardless the size or type of the organization, it's imperative for an organization to keep pace with the current challenges, transform itself or left behind. Lack of coordination between cross functional teams can make it difficult for the business leaders to take agile decisions. With Anaplan HyperModel, teams across organization can work together, build robust models tackling the operational complexity & enable the decision makers to take the correct approach.


HyperModel capabilities drive three key performance benefits

  • Robust - Every organization requires a robust modelling capability to accelerate the decision-making process. With HyperModel, teams can add more dimensions, years, scenarios, and data into a single model for extensive analysis & long-term planning. Furthermore, teams across the organization from different departments can come together & collaborate on a unified, robust model as part of connected planning.


  • Scalable - With HyperModel, teams can expand new plans, load more historical data, adjust forecast and update models as when it is required without archiving any data sets or splitting up the models. Furthermore, business does not have to rearchitect their models to avoid data storage issues.



  •  Adaptable - HyperModel with improve performance & functionality, can take care of any multi-dimensional scenarios with large-scale data sets for in depth analysis. Modelers can build more what-if scenarios incorporating potential business challenges to predict possible outcomes.

Things to consider before implementing HyperModel

  • Is the current model well-built? 

This is a very important analysis which should be carried out before implementing HyperModel. HyperModel uses the same best practices which are applicable for a standard model, hence if the current model is not well built then implementing HyperModel will not make much sense. Therefore, it's essential to review the current model & re-engineer it if required before implementing HyperModel

  • Is combining split models - a good idea?

Before we discuss on combining split models with the help of HyperModel, we must first understand the requirement of split models. If the split models were created to manage the data scalability, then with the use of HyperModel we can combine these split models provided they share common structures.

However, if the split models were created because of different process steps, different levels of granularity, then it will be best to keep the split models as it is. Having said that, we can still use Hypermodel to increase the scalability of these split models to manage more timelines, scenarios etc.



The standard model has a size limitation of 130 GB which is in some cases restricts further development or large-scale modelling. With HyperModel, business can create more robust business solution incorporating more future scenarios & predict a more accurate forecasting.

Though Anaplan hasn't confirmed the size of the HyperModel yet, however many Anaplan enthusiast like me estimate that Anaplan will increase the size from 130 GB to 700 GB. 

Size constraint was one the few challenges holding Anaplan back with respect to other planning tools, however with HyperModel, Anaplan has opened a new door full of possibilities. 

December 22, 2020

Improved Anaplan Experience with new UX

Anaplan has recently introduced it's new UX after classic UX (User experience) which is aimed to provided best user experience for the users to view and edit data (note: although Classic UX is still available for use), resulting in improvement in productivity of a process/organization. App - This is a collection of related pages in the new UX which are focusing the businesses on priority. The end user is getting a chance to look into the planning at a glance without losing an hour, causing an imperative success to their business. With the upcoming intense business competition and a huge uncertainty created due to this pandemic, Covid-19, organizations want to rely more on streamlined business processes which can give result within a moment's notice. This has become the new normal. Hence Anaplan is also looking for an excellent user experience through KPIs and other highlighting factors at the click of a button through both desktop and mobile app. The target behind this approach is not to recreate the excel intuitive interface once again, but to show companies how they can plan more easily with their planning, which would be more user friendly and adds more value to the organization.

The best thing about apps content page is that it can contain multiple pages from different workspaces at the same time. Each page uses 1 workspace and 1 model. Anaplan automatically categories pages as Quick access panel (to scroll directly within the main panel), Most recent (recently accessed pages), Favorites, My Pages. The focus behind designing Anaplan new UX are:

  • Enabling connected planning - Here it is no longer limited to only one model at a time. Users can seamlessly work across multiple models at the same time across any workspaces if he has access.
  • It can perform well across different devices, responsive to device size across desktop & mobile with no extra configurations.
  • It offers best possible user experience, user can handle/edit data across models for planning.
  • It helps user to use fast and easier to handle, leverage end user customization.
  • It has variety of page types - board and worksheet, to analyze data in different ways.


The new UX includes page role which is assigned by Tenant Administrator. Page builder is responsible for creating apps and pages & making page designs. He creates initial boards and worksheets for end users to use. Page builders can create a My Page and later it can be converted to App Page.

To work on Anaplan new user experience, one should have different roles accesses:


 Model Builder

Page Builder

End UserTenant Admin

Enabling My page in the Model





Building apps and pages





Customized Views





Building My Pages





Convert My Pages to an App





Manage Page access by Roles





Page View





Share/Export Pages





Page View Access on Mobile





How a Classic UX user can identify terminologies in new UX:

Classic UX User

New UX User




In new UX, different models from separate workspaces can be seen at the same place







Saved Views



Model Roles & Security - User roles, selective access and dynamic cell access

Model Roles & Security - User roles, selective access and dynamic cell access

Remains same

Functional Areas


Grouping of pages

New UX Terminology:

Navigation Bar - It makes the UX easier to locate to the other location, it can be found at the top of the app to navigate to other page/other app or return to the current page from the dropdown.

  1. Page - it is designed within new UX to access data from models. Any individual app page can be shared with anyone through sharing link icon via email. However, any personal page can't be shared with other. The page can be created in two ways. Either, it can be created as personal page which will exclusively available to the creator or, the page can be created for all available app users. After creating the page, different type of cards can be added like text/grid/chart/KPI/Image/Field/Actions.

Two types of Pages can be created through Create a Page from Landing page -

A. Board - This is used as traditional dashboard for performance management and reporting. End user can find high-level information and can navigate to more details. Each component from the board page is referred to as card. Users use context selectors to adjust/filter data which can be found from the top of the page.It allows to choose label and selector from card option, and gives option to page builders to select which are the items to show/hide.  User can also access KPIs which are designed to access key performance indicators at-a-glance. Another feature from Board is Grid Card which displays data from model and users can have access to edit/change the data, navigate to a linked page and view charts. And lastly Chart Card which helps to display different charts to ease data visualizations. Users can get the previous results by clicking on Reset options. It also helps users to visualize synchronized and hierarchically synced data across grids and cards. Editable text is purple in nature. Users can create a personal copy and also can find the source model from the right top corner of the app page. As an end user, import, export, process and forms can be created which can be launched from action card on a board or worksheet toolbar. End user(having page builder access) can design board by adding & configuring cards (Text/Grid/Chart/KPI/Image/Field), then adding actions(through import/export/process/forms), adjust context selectors, setting up hierarchy sync between grids and publish the changes that the card designer has done. Board layout has also been easier in terms of position by dragging the card and hover below/between to resize cards on the board. The board can have maximum 6 wide and 4 high in a row.

B. Worksheet: It's an interactive page for planning activities using detailed data. It helps to create links between data similar to Board. Context selector is also similar here like board. Main content area is similar like grid card which is also used to change or edit data by end users. Users can refresh, filter & search a grid. HE can export the view from here in .xlxs,.xls, .csv,.txt or .pdf format. Additional insights tab is used to navigate to different pages created from the model.

2. Card - This contains data and content components on a page.To Edit a card in the library, one can do it through renaming or edit from dropdown or make changes in color and card design. The page builder can also delete a card from the library. 

3. Forms - It is an action which allows end user to add list item, only a page builder access holder can create this form. It helps end users to submit data directly to the models.

Landing Page - It displays only those apps which the end user has access. Description sections are provided to add notes to brief about the app. In Quick access panel section, categories can be created with maximum 60 characters and unique in name. Create App option is present here to create an app with name and short description. End user can also Delete app and duplicate app or move page to another app. User can also restore a deleted app within 90 days from manage app section. Under this section, show models will show all the related models and pages here. My Pages are the personalized pages which can be created by end users if he has been given access by workspace admin. Users are facilitated to change one page or multiple pages from one model to other by changing workspace and model name, if it has the same structure.

All the definitions for the new UX can be found in the left bar under GLOSSARY tab. New UX offers end users to personalize the worksheet which an end user can use/modify to track the data. Users can also create My Page using existing views or cards and personalized contents which can be pushed to app as per requirement.

For Mobile Use:

Only primary view can be opened on a worksheet by default, quick links and additional insights are opened as needed. Worksheet grids can be optimized for landscape with adjustable column width and headings for mobile use. Context selectors are located at the bottom of the mobile view.

Advantage of Worksheets over Board for End users:

A. It provides additional insights panel which helps to understand and analyze data, it can be collapsible. Quick links which are related to the app helps to navigate to related page. User can open/expand/adjust secondary view , they can use click back arrow to return to the worksheet.

B. Worksheet toolbar helps user to check cell history, filter, sort, show/hide any column/row, launch available model actions. Configure Worksheet actions can be done through editing toolbar actions. It helps to create pivot from the customized view which can adjust dimensions shown in rows, columns and context selectors. Like Board, worksheet also helps to create import, export, processes and forms.

Restrict Page Access:

To restrict the page access, from the page options dropdown, select Restrict Access, then selected roles will have the access only to that page.

App Page Creation Approach:

  • Review user stories and existing dashboards to identify what are the new UX ideas that can be introduced and what should a page builder include in the page that can help end users to analyze better. 
  • Identify the existing data to create apps and also understand whether it should be suitable for board or worksheets based on the users and their roles in the organization.
  • Try to understand the wants of end users and what information should come to the dashboards, to decide what are the navigation links needed to synchronized between data. It will help page builders to prioritize what are the necessary information that the end user might need to access or view.
  • Based on the models and modules to be used in the new UX, what should be the best format(grid/chart/text/KPI/card) and whether the board or worksheet meet the criteria of the end users in a best possible way.
  • Page builder can also leverage end users to edit/change data according to the need of the models.
Board vs Worksheet Comparison:



What should End user Access?



Review High Level KPIs



Review High Level Data



Advanced formatting or charts



Compare data from multiple modules



Review detailed data



Edit Data



Filter Data



Drill down to detailed area

Good Practices to follow in new UX:

  • Use Categories on App content page to differentiate between pages.
  • Write description to provide hints about model or what to do next - use tooltips and text cards.
  • Use Boards to get key metrics of any organization/department/business at-a-glance.
  • Use Worksheets to deal with big chunk of data, get detailed analysis with an option to edit.
  • Use editable grid and field cards for changing drivers and assumptions.

December 18, 2020

Cradle to Grave Cycle using Supply Planning Cloud and Global Order Promising

Cradle to Grave cycle is often used to describe how a material demand in terms of customer forecast progresses into a firm demand with an actual sales order and eventually dies after satisfying the customer commitment to fulfil and ship in time. In its journey, the demand goes through multiple changes and has to reposition itself to meet supply requirement through multiple backlog management activities. In this blog, you will learn the system behavior of Oracle cloud planning and global order promising modules for events occurring in the day of life of a planner.

The above diagram illustrates the journey of (1) Receiving the forecast from the customer (2) A nightly MRP plan run will pick up the demand and drive the underlying component supplies by suggesting work order and purchase order for Make/Buy items. In stage 3, which can happen after a much longer duration, the customer sends the PO which in turn gets booked as a Sales Order in Oracle. Stage 4 will make an initial scheduling call and provide the dates based on the lead time or supply depending on the configuration selected. In stage 6, MRP plan runs again and considers the firm demand and consumes the forecast and thereby re-adjusting the supplies accordingly. In certain cases, the customers can choose to drive supplies on forecast using a "Planning BOM" as the fine details and configurations might not be known by then. This is often a case with "Build to Print" contract manufacturing companies that are dependent on customer signals. Between stage 6 and 7, the order might go through multiple change especially in a high mix environment or companies that fall in the far left of the value chain (Component manufacturers or component equipment manufacturers). Finally, the order gets shipped out in stage 8 and thereby fulfilling the customer demand ensuring the lead time and operational metrics is attained.

Stage 1 & 2 - Receive Customer Forecast and subsequently run MRP

MRP Plan Suggestion

  • Planned Work Order for the Make Item
  • Determines the Suggested Completion Date based on the "Longest Lead Time Component + Resources" OR Request date whichever is later
  • Suggest Planned Orders for Components & Sub-Assemblies based on the Make Item Suggested Start Date
  • Calculate Material Available Date Based on the Planned Work Order Completion Date
  • Calculate Exceptions on Resources & Supplies
  • Suggest Expedites to meet the Request Date (RD) where  RD is inside the Assembly Cumulative Total Lead Time (TLT) and no on time supply exist

Stage 3 & 4 - Sales Order is entered and Initial Scheduling results is based on MRP plan

Note: Global order promising in cloud (Rel 20D) provides ATP dates only based on the collected data

chedule Ship Date (SSD) will match Need by Date (NBD) if:

  • Assembly On Hand is available
  • OR Supply Constraints identified against Forecast demand have been sorted and promised early or on time
  • Component On Hand is available OR NBD is outside Assembly Cumulative Total Lead Time 

Schedule Ship Date (SSD) will be delayed if:

       NBD is inside the Lead Time AND

       Assembly On Hand is not available some or all Component Supplies based on forecast do not exist or are delayed

       Component On Hand is not available

       SSD will be based on the Longest pole in PO promised dates or Component LT + MLT (manufacturing lead time) of Assembly

Stage 5 - MRP plan run after initial scheduling of the sales order

MRP results from Supply Planning Cloud will be when Schedule Ship Date is greater than Need by Date

  • Consumes Forecast based on SSD and consumption window (XX days backward & forward). Assumes the supplies earlier pegged to Forecast
    • Planned Work Order for the Make Item.
    • Determines the Suggested Completion Date based on the "Longest Lead Time Component + Resources" OR Request date whichever is later
    • Suggest Planned Orders for Components & Sub-Assemblies based on the Make Item Suggested Start Date
    • Calculate Material Available Date & suggestion Ship Date Based on the Planned/WO Completion Date
    • Calculate Exceptions on Resources & Supplies, Suggest Expedites

Stage 6 - Backlog Management

  • How do planners identify list of orders to pull in?

  • Use Backlog report to identify orders where SSD > NBD
  • Supply Plan provide exceptions

    • What would be GOP behavior after the Plan run if Sales Order is rescheduled?

  • Same as Initial scheduling, SSD will continue to be delayed until the supply picture improves

    • What steps should the planners follow to pull-in the order?

     Identify Components causing delay using
  • Expedite Recommendations on Demand Fulfillment
  • Late Supply Pegged to Sales Order
  • Use Supply Shortage Report (not an out of box report)
    • Prioritize Long Lead time items first
    • Supply Planner/Buyers work with suppliers to improve deliveries
    • Check Availability on GOP confirms the SSD can be pulled in and then reschedule


    Stage 6 - Backlog Management

    What would be the plan behavior post pull-in of NBD?

         1) Pulls in Planned Order or WO start dates, subject to the new longest pole date

    2) Reschedule in all Components to meet the new WO start date

    3) Raise exceptions, if any

    Constrained Plan in 20D Supply Planning Cloud

    Un-constrained Plan in 20D Supply Planning Cloud (Behaves similar to 11i/R12 MRP)

           Respects Material Constraints & Resource Constraints as Hard Constraints and pushes out planned Order dates due to component LT constraints when enforced Purchase LT is turned on.

           When turned off only Post processing LT is applied. Processing and Pre Processing LTs are considered as 0

           Within LT, only OH and scheduled receipts can satisfy demands


           Plan compresses the material lead time and resource requirements and overloads

           Window between the sysdate and WO start date becomes the lead time irrespective of the lead time and resource factors

           System assumes that the planners will expedite the supplies and also increase the resource availability by WO start date


    Note: This analysis has been done in a Cloud transformation program for Contract manufacturing client and had been contributed by Naveen Divakaran, Amruta Arunima and Chandra Poonachi

    Digital Manufacturing Execution System integrated with Oracle Manufacturing Cloud

    With digitization of shop floors, organizations are looking for manufacturing execution systems that have fail safe mechanism, single touch reporting, minimum data entry requirement and tightly integrated with core ERP. The MES should have ability to connect with third part drawing and image systems to display 3-D models to operators and integration with PLCs such as Torque Wrench and test beds. It also requires enrichment of data at much granular level to add work instructions, sequence of events to aid the operator with details to avoid judgmental decisions.

    Oracle Manufacturing Execution cloud provides basic manufacturing capabilities including setting up factory floor space, resources, operations, work definitions (router) and execution capabilities like standard and non-standard work order, reworks and transform. It also provides end to end solution to manage quality control and implement maintenance schedule for the equipment's. However, with a missing MES application many customers feel the need to augment manufacturing experiences with following features

    • Ability to add detailed work instructions to a router which is not a count point for ERP
    • Technician's workbench to display work orders based on the work center he is associated to
    • Technician skill validation to ensure he is qualified enough to work on the job
    • Technician's clock-in and clock-out of each operation step to track the execution time
    • Ability to model parallel operation specially in a "Print to Build" assembly of complex integrated products such as gas assemblies and panels
    • Integration to record quality non-conformance and quality results at operation step
    • Andon board production status dashboard to show the health of manufacturing
    • Easy to use UI, touch screen, web intuitive enabled console with minimum data entry
    • Real time integration with Oracle cloud for WIP execution & valuation
    • Persona based Mfg. Engineer & Operator console with easy navigation
    • Display 3-D models to operators during complex assembly operations

    Infosys Light MES PaaS Solution

    Infosys Oracle Practice has built a modular and integrated MES app for filling in the whitespace and can be readily deployed to customers in Hi-Tech and Industrial that uses or intend to use Oracle Cloud application. The scope of the solution not limiting to:

    • Fully configurable MES PaaS using open source technology - opt-in features based on business requirements
    • Master data maintained in Oracle cloud - no data duplication and dual maintenance
    • Real time two way integration between Oracle cloud and MES
    • Touch screen enabled, modern UI including adapters for label printing
    • Validates operator skill-set, clocks operations, capture lot/serial at point of use, displays drawings, tools, safety, consumable to be used on the operations
    • Capture quality inspection data and also create nonconformance issue
    • Update meter readings for assets, create maintenance work orders

    Integration Reference Architecture:

    The integration architecture is built on a modular principle and can be deployed on any integration technology such as Oracle Integration Cloud (OIC), Dell BOOMI and MuleSoft.

    Benefits of Infosys MES App

    December 9, 2020

    Embracing Tranfer Pricing Accounting and Compliance