Off late, most of my customers, where I see a trend, are long-standing heavily customized major customers on ERP (Enterprise Resource Planning) on EBS who want to convert themselves to the cloud, and they expect us to provide the same level of customizations that EBS supports them in the cloud. So that's the challenge where we are currently. We have a few strategic advisory accounts like that, and we are evaluating those customizations to see how we can plug them as part of the solution offering so that the customer retains their current custom behavior and they don't have to deal with too many changes with their users. And that's the biggest change that we are working on. And there is a bundle of such initiatives that we do internally. Custom roles are one such thing. There are several areas of improvement. In the procurement cloud, we have today the landed cost management, where there's a lot of flexibility, which has been given on the cloud side in terms of costing. So the license and pricing have become a little complex area. And then auto management has completely changed in the cloud, the way the pricing strategy has been. It's been more complex and more flexible in the cloud. So that's the second area where we see challenges. These two, plus yes, now with self-service procurement, the dynamics have changed in global procurement, where the corporate will do the billing and invoicing, and we can do it from any big use, placing purchase orders and all that, the consolidation and the dynamics of testing. So these are some of the things which have greater flexibility, but at the same time, there is complexity in terms of implementation. We try to implement everything within the same window of the same customer window of six months. In future releases, I would like to see the idea of automating the period close process, which would be beneficial for sustenance after go-live. It is more like sustenance, both go live. If there is a mechanism where the period close can be automated, or it can be if the product can come up with a dashboard specifically for that, which ties with the sequence of the sub-ledgers, what are the conflicts to close the sub-ledger areas to facilitate and close the ledger area? Which consumer buying? That's one initiative or one idea that I'm thinking about. There are quite a few like that, which are more from the sustenance standpoint, more than the implementation standpoint.
Off late, most of my customers, where I see a trend, are long-standing heavily customized major customers on ERP (Enterprise Resource Planning) on EBS who want to convert themselves to the cloud, and they expect us to provide the same level of customizations that EBS supports them in the cloud. So that's the challenge where we are currently. We have a few strategic advisory accounts like that, and we are evaluating those customizations to see how we can plug them as part of the solution offering so that the customer retains their current custom behavior and they don't have to deal with too many changes with their users. And that's the biggest change that we are working on. And there is a bundle of such initiatives that we do internally. Custom roles are one such thing. There are several areas of improvement. In the procurement cloud, we have today the landed cost management, where there's a lot of flexibility, which has been given on the cloud side in terms of costing. So the license and pricing have become a little complex area. And then auto management has completely changed in the cloud, the way the pricing strategy has been. It's been more complex and more flexible in the cloud. So that's the second area where we see challenges. These two, plus yes, now with self-service procurement, the dynamics have changed in global procurement, where the corporate will do the billing and invoicing, and we can do it from any big use, placing purchase orders and all that, the consolidation and the dynamics of testing. So these are some of the things which have greater flexibility, but at the same time, there is complexity in terms of implementation. We try to implement everything within the same window of the same customer window of six months. In future releases, I would like to see the idea of automating the period close process, which would be beneficial for sustenance after go-live. It is more like sustenance, both go live. If there is a mechanism where the period close can be automated, or it can be if the product can come up with a dashboard specifically for that, which ties with the sequence of the sub-ledgers, what are the conflicts to close the sub-ledger areas to facilitate and close the ledger area? Which consumer buying? That's one initiative or one idea that I'm thinking about. There are quite a few like that, which are more from the sustenance standpoint, more than the implementation standpoint.