We were working with the energy and water resource management client on Supply planning implementation project. As part of that there were some reports which need to be migrated to cloud “as-is”, since reports are built on plan specific data and then fed to downstream applications.
Initially the solution looks simple, as we made required changes in report sql at cloud, then through SOAP API report is submitted and generated csv file put at SFTP, and using middleware file loaded to the EBS side staging table.
But later we started observing the spike in supply plan data volume. Result of this, we started facing issue while inserting data in to custom staging table. So, we decided to create multiple reports based on date horizon. Since the plan data is incremental, we started facing difficulty to determine report count that is needed for a single plan. Also creating multiple report isn’t robust solution.
About the Author
Prasad Chavan is working with Trinamix Inc. as a Consultant having good experience Over 7+ years in implementing, developing and supporting VCP Modules for discrete manufacturing and worked with client in different geographies. Worked as Onsite lead for EBS SCM and VCP applications for UK based client. Focus area ASCP, Fusion Supply planning and analytics, OTBI. Completed BE in Computer Engineering and PGD in Operations Management.
