Public Solution Model (PSM)

The SAP public solution model (PSM) contains all entities in the SAP cloud solution that are released for use by
external consumers. External consumers can be partners who develop solutions on top of the SAP cloud solution
such as add-ons and integration scenarios or administrators.

For example, use SAP data sources to create new reports.

The modular and homogenous architecture of the SAP cloud solution allows SAP to offer external consumers a highly flexible means of developing additional functionality without modifying the standard solution.

Basic Principles

What is PSM Entities?

The Repository Explorer tool window displays SAP content that is released with the public solution model (PSM)
such as business objects, data types, enhancement options, inbound service interfaces, and reuse UIs. You can
explore the content to gain an understanding of the repository structure and the business context and use of SAP
content, which you can reuse and enhance in your solution.

Layer Strategy

The architecture of the SAP cloud solution is structured in three layers:

1.  Presentation — the user interface
2. Application — the business logic
3. Persistence — the database and search index

External consumers can reuse specific SAP content without modifying the standard solution.

For example, external consumers can reuse complete SAP user interfaces and enable navigation from a custom floorplan to an SAP floorpan and from an SAP floorplan to a custom floorplan.

The content developed using the studio resides on a different layer to the SAP content; therefore, SAP content that is released with the public solution model (PSM) can be reused or enhanced without modifying the standard cloud solution. This content can be released for read-only access or for read/write access.

Understanding Deprecation

The current structures and processes defined within the public solution model (PSM) remain stable for the current
and upcoming release. If it is necessary for SAP to make changes to PSM entities to meet technical or business
requirements, SAP uses a deprecation mechanism that allows external consumers to update their solutions in an
appropriate time frame.

Road Map

1. The business object elements are set to deprecated and, if an element is deprecated, all children
   are also deprecated. For example, if a business object node is deprecated, all actions, queries, and
   elements that belong to this node are also deprecated.
2. SAP identifies the use of deprecated elements in a solution, informs the partner or other external consumers
   who developed the solution and provides information about the successor element.
3. The external consumer creates a new version of the solution before another SAP release becomes
   available.
4. The new version of the solution is made available to customers for activation with the new release
   of the SAP solution
5. SAP revokes the respective business object element.

Requesting Release of Additional PSM Entities

If you need to access business content for the SAP cloud solution that has not been released for consumption through
the PSM, you can request SAP to release this business content.

To do this, proceed as follows:

1. Create an incident in the SAP cloud solution and use the prefix PSM.
2. Describe the use case of your solution and what you are trying to achieve (that is, what is the purpose of your
   development/solution?).
3. Describe the required business content/entities to be released in PSM, and why you need them.
4. If you require business content such as the fields of a business object from a UI, provide a screenshot of that
   UI and highlight the elements that need to be enabled for read-access and for write-access.
5. Add your contact information – that is, e-mail address and telephone number – so that SAP can easily get back
   to you in the case of questions.

Reference: © 2017 SAP SE. All rights reserved.