Overall Satisfaction with SAP Cloud Platform
SCP is being used as the External Vendor Portal in Loblaw. I used to manage the vendor on-boarding process and vendor promotion process. The vendor gets their own user administration capabilities. Apart from that, WebIDE service is also used for Fiori development. BUILD prototyping service is used for prototyping to fine-tune the business requirements. Business feedback is positive.
- Cost Reduction.
- Lack of documentation.
- Limited number of authorization roles.
- Known constraints for OdataService Provisioning Service.
- Do not have the containerization functionalities.
- Do not have the auto-scale up or down capabilities
- Faster deployment time.
- Cheaper maintenance cost.
- Reduces the total cost of ownership.
- Improved user satisfaction.
We integrated SCP and the backend systems via the OdataService and gateway. The destination for all the backend systems are well defined in the SAP Cloud Platform. RFC calls are being used to communicate with the backend system. In terms of other integration opportunities like datahub and extension factory, it is required to have further investigation.
A few years ago, one of the key considerations for using SAP Cloud Platform was the good integration with other SAP products and systems. A lot of SAP products and systems were used in Loblaw before. We believed that SAP Cloud Platform aligned with the strategic direction in Loblaw.
It is good for Fiori development via WebIDE service. It is no longer required to upgrade the Eclipse anymore. It is also good for the prototyping via BUILD service. Both of these services can accelerate the deployment time and provide better user experience to a business. However, since the Odata Provisioning service lacks the functionalities and not support the latest ODataService version. It is required to think twice before heading down to this direction.