Skip to Content
Product Information

Extending the scope of an SAP S/4HANA Cloud Starter Pack to address legal requirements

This blog provides an insight into the required activities for the implementation of an SAP S/4HANA Cloud starter pack and the extension of its scope via the localization toolkit.

With the SAP S/4HANA Cloud release 2002 ten starter packs are going to be available, more are on the roadmap for release 2005. The starter packs provide a fixed scope version to run basic business operations and include only configuration. This implies they do not address country/region-specific legal requirements as opposed to the standard local versions delivered for SAP S/4HANA Cloud, an example could be forms or reports. You can leverage the localization toolkit for SAP S/4HANA Cloud for guidance on how to implement localization extensions to meet the legal requirements of the respective country. More information on the starter packs is available in the innovation discovery.

In the picture below you see a project template that describes the implementation sequence for a starter pack as well as functional extensions to meet legal requirements. This can also be used for any implementation of a functional extension on top of a standard local version for SAP S/4HANA Cloud.

As a first step it is important to get an overview of the scope included in the SAP S/4HANA Cloud starter pack. The required customer implementation scope for the respective country should be documented in the Fit-to-Standard results, this will be the foundation to decide if the starter pack is a feasible approach for the customer.

If you proceed with the implementation you need to check for any legal requirements that apply to the respective country and implementation scope. The Localization Feature Overview provides a list of typical localization features included in standard local versions for SAP S/4HANA Cloud. You can use this a checklist for business areas with potential legal requirements.

Once you have a complete list of legal requirements you can proceed with mapping those to development activities. Our expert content on the localization toolkit community page and the Capability Overview will help to get an understanding of available how-to guides for specific localization scenarios and extensibility features. In case of scenarios not yet covered please reach out to us. You can directly channel your requests via the Q&A discussion forum on the SAP community page of the toolkit here. Also consult us if you would like to get our support for a feasibility check or if you are not sure if the described implementation approach will address your requirement completely.

In the next step the customer can request the activation of the starter pack, the procedure is identical to the one for the standard local versions. Please check the SAP Roadmap Viewer for further details. After activation you can proceed with using SSCUIs to add and adopt configuration.

Before you move on with developing the extensions you or the customer might need to set up users and roles with extensibility authorizations in case this is not yet done. Afterwards you should also create test data related to the functional extensions. You can find more details on authorizations in the prerequisite section of the how-to guides. Creating test data will ensure you can test the functional extensions as a part of end-to-end processes.

In the subsequent step you start developing the functional extensions. The how-to guides within the localization toolkit provide a step-by-step description of the development sequence and include code samples for BAdI implementations. If you, for example, want to adapt a form or create a tax report use one of our how-to guides within the expert content area reporting or forms. If you need support during your development, reach out to us. If needed, we can connect you with experts.

The implementation will be concluded after a successful end-to-end test of business processes based on the configuration of the starter pack in combination with the functional extensions.

In case of any issues with the functional extensions the customer would reach out to you for support and bug fixing if you both agreed on this. It is important to keep track of legal changes and adapt or even add functional extensions if required, to ensure the customer is legally compliant.

 

 

Be the first to leave a comment
You must be Logged on to comment or reply to a post.