Dear All,
This blog describes how you can manage deployment without writing any code to move your objects from one environment to other environment. CPQ Provides codeless deployment feature called "Deploy/Send Changes" action to perform migration activity.
When an administrator wishes to do a deployment task, follow the steps below to understand the procedure.
Never move your objects without business user signoff and as well copying it from one environment to other environment manually.
Go to Deployment Packages
Click Send
Go to Destination Environment and Click Deploy
with this approach, Admins can easily migrate the objects without doing manually or writing any code to move from one environment to other.
Available components
Developers utilize the CPQ Dev environment to create, design/build and test Business Requirements. Once the build and test are completed according to the User Story or business need, developers will deploy the item to UAT/TST.
Customers and business owners primarily use the CPQ UAT/Test environment to test the business requirements provided during the Explore Phase. Only once business owners have signed off on successful testing will objects be deployed to PRD.
For the sales process, Sales Reps/Sales Managers/Account Managers mostly use the CPQ PRD(Production) environment.
Another approach through CI/CD concept using CPQ for the Global Scripts
References
https://www.sap.com/cxworks/article/2589632798/project_delivery_framework_for_sap_cpq_configure_pric...
https://pmtips.net/article/the-8-phases-of-a-project-explained
This blog describes how you can manage deployment without writing any code to move your objects from one environment to other environment. CPQ Provides codeless deployment feature called "Deploy/Send Changes" action to perform migration activity.
When an administrator wishes to do a deployment task, follow the steps below to understand the procedure.
Never move your objects without business user signoff and as well copying it from one environment to other environment manually.
Deployment Process and Documentation
To access this feature, go to . The page that displays contains the following tabs:
Go to Deployment Packages
Click Send
Go to Destination Environment and Click Deploy
with this approach, Admins can easily migrate the objects without doing manually or writing any code to move from one environment to other.
Available components
- Approval Rule
- Cart Level Aggregates
- Categories
- CRM Integration
- Currencies
- Custom Actions
- Custom Calculations
- Custom Fields
- Custom Tables
- Global Scripts
- Guided Selling
- Item Actions Workflow
- Markets
- Notifications
- Permissions
- Quote Item Custom fields
- Quote Tables
- Responsive Templates
- Territories
- UserTypes
- Workflow
CPQ Standard Process of Deployment
Developers utilize the CPQ Dev environment to create, design/build and test Business Requirements. Once the build and test are completed according to the User Story or business need, developers will deploy the item to UAT/TST.
Customers and business owners primarily use the CPQ UAT/Test environment to test the business requirements provided during the Explore Phase. Only once business owners have signed off on successful testing will objects be deployed to PRD.
For the sales process, Sales Reps/Sales Managers/Account Managers mostly use the CPQ PRD(Production) environment.
 Note : Deployment Process will be carried out by an Admins  and not every Individuals. There is no API's available for Deploy /Send Changes for automating the process through CI/CD. Refer the available SAP CPQ API Documentation |
Continuous Integration/Continuous Delivery (CI/CD) Process in SAP CPQ – Best Practices
Another approach through CI/CD concept using CPQ for the Global Scripts
References
https://www.sap.com/cxworks/article/2589632798/project_delivery_framework_for_sap_cpq_configure_pric...
https://pmtips.net/article/the-8-phases-of-a-project-explained
- SAP Managed Tags:
2 Comments
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
