- SAP Managed Tags:
By vinod.srinivasan2, abishek.suvarna and jayendra.bisnik
In our previous blog post - Package Configuration Manager: Getting Started - we discussed how you could get started with the Package Configuration Manager tool. The next step is to outline some of the standard Business Scenarios that the SAP Partners can use the tool in their SAP SuccessFactors implementations.
We have now seen the tool being used by SAP Partners for a variety of business scenarios globally. They have created their business packages (based on industries and country-specific requirements) and deployed them in their implementation projects with a click of a button. Furthermore, some SAP Partners used a combination of SAP Best Practices and their custom packages to fulfill their customers' requirements. We'll be discussing two common scenarios where the Package Configuration Manager has brought in value to SAP Partners.
Scenario 1: Standard Implementation for Small and Medium-sized Enterprises (SMEs)
A Southeast Asian customer with 2000 employees is looking to implement a Hire-to-Retire solution. The customer wanted the SAP Partner to apply the SAP-recommended core HR business processes. The customer project has a budget, as well as timeline constraints.
The SAP Partner decides to use the standard SAP Best Practices available and create a custom script for the customer-specific requirements in the Package Configuration Manager. The custom configuration block (as shown in Figure 1) is developed in the tool's company view. The SAP Best Practices and this custom configuration block are deployed successfully. As most of the effort is focused on customer-specific requirements (custom configuration block), the effort required for implementation activities is significantly reduced, at the same time, increasing the quality of configuration.
Scenario 2: Complex staggered global Employee Central implementation with a large number of country localizations
A North American customer with more than 50 subsidiaries chooses SAP SuccessFactors Employee Central implementation for managing their HR and People Engagement processes. They required a global Employee Central implementation to provide information about employees' work/life events in the organization. The project roadmap consists of multiple phases, with 80% of the employee population covered in the first two phases. The challenge for the SAP Partner is to manage the stages of implementation and prepare for the next phase while completing ongoing activities.
The project starts with North America that includes mainly the USA and Canada. The SAP Partner quickly sets up the customer development environment with SAP Best Practices' configuration to start the first conversation with the customer. The customer-specific requirements are built directly into the development environment and also incorporated in the package. Once the customer signs-off the configuration, the SAP Partner can quickly deploy the whole configuration block in the QA environment that allows the customer to start their testing activities immediately. At the same time, the SAP Partner implementation team is building packages required for the next phase of the project.
For the second phase, they prepare the packages for European and Asian subsidiaries. They can reuse the existing localization configuration blocks created in the first phase for a few countries. For other localizations, they create new configuration blocks in the Partner workspace within the Package Configuration Manager. The rest of the project is managed with similar iterations using SAP Activate Methodology by the SAP Partner.
During the project, the SAP Partner can optimize their resources by automating the repetitive tasks and minimizing human errors. The Package Configuration Manager provides consistency, high quality, and visibility because the tool is the one source of truth for customer configuration management. With the approach outlined above, the SAP Partner can smoothly transition through the different implementation project stages, meet deadlines, and ensure customer satisfaction.
Finally, the Package Configuration Manager can also be used by SAP Partners to deliver industry-specific flavors. As described above, the industry variants for Employee Central implementation, which entails custom Generic Objects, Config UIs, Business Rules, Workflows, and others, can be created quickly using the tool. SAP Partners can use the demo landscape to showcase their proprietary solution to customers. We will be talking in detail about the industry-specific solutions in a later blog.
We hope this blog provided some good insights into how the tool can be leveraged in various SAP SuccessFactors implementation projects. We look forward to collaborating with you on this topic.
In our previous blog post - Package Configuration Manager: Getting Started - we discussed how you could get started with the Package Configuration Manager tool. The next step is to outline some of the standard Business Scenarios that the SAP Partners can use the tool in their SAP SuccessFactors implementations.
We have now seen the tool being used by SAP Partners for a variety of business scenarios globally. They have created their business packages (based on industries and country-specific requirements) and deployed them in their implementation projects with a click of a button. Furthermore, some SAP Partners used a combination of SAP Best Practices and their custom packages to fulfill their customers' requirements. We'll be discussing two common scenarios where the Package Configuration Manager has brought in value to SAP Partners.
Scenario 1: Standard Implementation for Small and Medium-sized Enterprises (SMEs)
A Southeast Asian customer with 2000 employees is looking to implement a Hire-to-Retire solution. The customer wanted the SAP Partner to apply the SAP-recommended core HR business processes. The customer project has a budget, as well as timeline constraints.
Figure 1: Deployment of Partner Packages in a standard scenario
The SAP Partner decides to use the standard SAP Best Practices available and create a custom script for the customer-specific requirements in the Package Configuration Manager. The custom configuration block (as shown in Figure 1) is developed in the tool's company view. The SAP Best Practices and this custom configuration block are deployed successfully. As most of the effort is focused on customer-specific requirements (custom configuration block), the effort required for implementation activities is significantly reduced, at the same time, increasing the quality of configuration.
Scenario 2: Complex staggered global Employee Central implementation with a large number of country localizations
A North American customer with more than 50 subsidiaries chooses SAP SuccessFactors Employee Central implementation for managing their HR and People Engagement processes. They required a global Employee Central implementation to provide information about employees' work/life events in the organization. The project roadmap consists of multiple phases, with 80% of the employee population covered in the first two phases. The challenge for the SAP Partner is to manage the stages of implementation and prepare for the next phase while completing ongoing activities.
Figure 2: Deployment with Package Configuration Manager in a phased staggered implementation following the SAP Activate Methodology
The project starts with North America that includes mainly the USA and Canada. The SAP Partner quickly sets up the customer development environment with SAP Best Practices' configuration to start the first conversation with the customer. The customer-specific requirements are built directly into the development environment and also incorporated in the package. Once the customer signs-off the configuration, the SAP Partner can quickly deploy the whole configuration block in the QA environment that allows the customer to start their testing activities immediately. At the same time, the SAP Partner implementation team is building packages required for the next phase of the project.
For the second phase, they prepare the packages for European and Asian subsidiaries. They can reuse the existing localization configuration blocks created in the first phase for a few countries. For other localizations, they create new configuration blocks in the Partner workspace within the Package Configuration Manager. The rest of the project is managed with similar iterations using SAP Activate Methodology by the SAP Partner.
During the project, the SAP Partner can optimize their resources by automating the repetitive tasks and minimizing human errors. The Package Configuration Manager provides consistency, high quality, and visibility because the tool is the one source of truth for customer configuration management. With the approach outlined above, the SAP Partner can smoothly transition through the different implementation project stages, meet deadlines, and ensure customer satisfaction.
Finally, the Package Configuration Manager can also be used by SAP Partners to deliver industry-specific flavors. As described above, the industry variants for Employee Central implementation, which entails custom Generic Objects, Config UIs, Business Rules, Workflows, and others, can be created quickly using the tool. SAP Partners can use the demo landscape to showcase their proprietary solution to customers. We will be talking in detail about the industry-specific solutions in a later blog.
We hope this blog provided some good insights into how the tool can be leveraged in various SAP SuccessFactors implementation projects. We look forward to collaborating with you on this topic.
10 Comments
| User | Count |
|---|---|
| 7 | |
| 6 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
