During implementation, the customer may require data flows from Oracle EBS to Demantra worksheet that is not completed through standard workflow. To meet such specific customer requirement, Demantra has a provision in the tool called Business Modeler where you can create custom integration interfaces to populate EBS custom data and then insert it into Demantra table sales data using workflow by Demantra.
This blog provides information on this functionality provided by Demantra-Business Modeler to import the custom data into Demantra Demand Management.
Demantra Integration Interface Design:
The Demantra integration interface is used to create the interface tables where we can fill in the custom EBS data. The following basic steps we require to define the integration interface:
Create a new import integration interface with the user-defined name from Business Modeler: Navigation: Business Modeler> Tools> Integration interface.
Select the series during the definition of this integration interface. These are the Demantra series where you want to fill in your custom data.
Define the time scale (weekly, monthly, quarterly or yearly, etc.) in which we want to add and load the data and also define the time period range for which you want to load this data.
It also allows the selection of Demantra levels to import the data, for example, if we want to import the price data at the item and customer levels, we can select the item and customer levels during their definition.
Also, you can apply a filter within these selected levels, for example we can import the prices of the items for selected customers only by applying the appropriate filter
During the creation of the integration interface, you can decide to create the workflow automatically or manually.
The worksheet can be created automatically or manually during the definition of the integration interface.
How does the Demantra integration interface work?
The Demantra integration interface creates view tables to store custom data.
The workflow can be created automatically during the definition of the Demantra integration interface or manually from Demantra Workflow.
The Demantra workflow is started to submit the records from the interface tables, analyze them, and complete all valid joins in the Demantra base table, that is, the sales data.
The records of the errors during the workflow executions are completed in the respective error tables.
The records with errors are corrected at the source and populated again in the interface tables.
Finally, the Demantra workflow runs again to send all valid records to the sales data table.
Prerequisites:
Make sure all the series where we plan to load the data are already defined.
Make sure that all custom time levels where we want to upload the data are created and imported into Demantra.
Make sure all the Tiers we plan to take the data to are already defined.
conclusion
Demantra Demand Management is a powerful, flexible, and feature-rich forecasting application and therefore customers are easily tempted to implement all the bells and whistles right out of the box. However, this approach can lead to a steep learning curve for business users and can seriously undermine the adoption of this module.
We caution and encourage our clients to take a tiered approach to Demantra implementations to ensure success.
