Solutions Architecture
About this topic
A solution architecture (SA) is an architectural description of a specific solution. SAs combine guidance from different enterprise architecture viewpoints (business, information and technical), as well as from the enterprise solution architecture (ESA).
Active Ambassadors in This Topic
Community Posts
Currently, our CPQ is tightly integrated with our ERP, providing unique features and functionalities that are not typically found in standalone CPQ solutions. For instance, we can perform mass updates to our BOMs (e.g., replacing one component with another, creating new BOM versions, keeping version and pricing history) directly within our current system.
Mass update capabilities for configurations are often not inherent to CPQ solutions, with vendors suggesting that such functionalities should reside within the ERP. As we transition to a new CPQ, we anticipate needing to use middleware, APIs, or interfaces to achieve similar outcomes.
I would greatly appreciate any insights or experiences you could share regarding the following:
1. Integration Experiences: How have you managed the integration between your CPQ and ERP systems, especially when using middleware or APIs? Especially interested to her from manufacturing companies who use 'smaller' ERP's (we don't use SAP).
2. Mass Update Capabilities: Are we unique in relying on our CPQ for mass updates to configurations, or is this a common challenge? How have others addressed this?
Thank you in advance for your valuable input!
Do you have experience or recommendations for enterprise solutions that support VIN/license plate look up? In order to get details about the automotive and to provide services based on the information.
Corporate culture has no influence on digital security.15%
Prioritizing digital security above other aspects in corporate culture.51%
Creating a work environment that supports mental well-being.18%
All of the above.14%
Your own perspective (Comment).1%
Are you implementing any technology solutions to capture institutional knowledge in case of unexpected talent departures? Which ones?
What were the main challenges your org had with designing an effective architecture for IAM? How did you manage to address those issues?
I lead a department that builds APIs that power the client experience. I am looking to rebrand and establish a new department name that more accurately reflects what we do. Our current name is API and Microservices however, we are not the only department that builds APIs. I am looking for suggestions for a new department name.
We are done! (Please add comment on success factors or mistakes)7%
We have plan in place and executing. (Please add comments on progress and any pitfalls)52%
Dabbling. We have some S/4 but not tackled ECC. (Please add where you dabbled in comments) 38%
We (IT) really wants to move, but struggling to find a business case.31%
Waiting to see if SAP caves and extends support beyond 2030. 9%
Other? 2%