%20--%3e%3cdefs%3e%3cstyle%3e%20.st0%20{%20fill:%20none;%20}%20.st1%20{%20fill:%20%239dd5da;%20}%20.st2%20{%20fill:%20%23475e73;%20}%20.st3%20{%20clip-path:%20url(%23clippath);%20}%20%3c/style%3e%3cclipPath%20id='clippath'%3e%3crect%20class='st0'%20x='86.5'%20y='408.15'%20width='907'%20height='290.82'/%3e%3c/clipPath%3e%3c/defs%3e%3cg%20class='st3'%3e%3cpath%20class='st2'%20d='M867.51,525.76l-35-106.2c-.91-3.65-4.11-5.94-8.68-5.94h-43.83c-8.22,0-11.87,6.39-9.13,13.7l61.07,173.85,35.57-75.41Z'/%3e%3cpath%20class='st2'%20d='M983.29,413.62h-38.81c-6.39,0-10.05.46-13.24,5.94l-58.3,122.67-67.01,141.41c-3.2,7.31.91,14.15,9.13,14.15h43.83c4.11,0,7.76-3.2,9.13-6.39l124.39-264.08c3.2-6.85-.91-13.7-9.13-13.7'/%3e%3cpath%20class='st2'%20d='M755.37,614.52v-109.12c0-51.14-27.26-97.25-90.81-97.25h-7.2c-62.03,0-92.91,46.11-92.91,97.25v109.12c0,5.48,5.02,10.04,10.04,10.04h36.99c5.48,0,10.04-4.56,10.04-10.04v-109.12c0-27.39,10.96-44.29,36.53-44.29h3.72c25.57,0,36.53,16.89,36.53,44.29v109.12c0,5.48,4.57,10.04,10.04,10.04h36.99c5.02,0,10.04-4.56,10.04-10.04'/%3e%3cpath%20class='st2'%20d='M249.5,518.64c0,32.42-24.65,58.9-55.25,58.9s-54.79-26.48-54.79-58.9,24.2-57.53,54.79-57.53,55.25,25.57,55.25,57.53M302.46,518.64c0-59.36-48.4-109.58-108.21-109.58s-106.27,48.68-107.76,106.82v176.35c0,3.37,4.57,6.74,10.05,6.74h36.98c5.02,0,10.04-3.37,10.04-6.74v-32.19c0-9.62.02-26.75.05-43.71,15.11,8.42,32.34,13.26,50.63,13.26,59.81,0,108.21-50.68,108.21-110.95'/%3e%3cpath%20class='st1'%20d='M377.85,518.64c0-31.96,24.2-57.53,54.79-57.53s55.25,25.57,55.25,57.53-24.65,58.9-55.25,58.9-54.79-26.48-54.79-58.9M324.89,518.64c0,60.27,48.4,110.95,107.75,110.95s108.21-50.68,108.21-110.95-48.4-109.58-108.21-109.58-107.75,50.22-107.75,109.58'/%3e%3c/g%3e%3c/svg%3e)
Custom Fields in SAP Cloud ALM
With pony you extend SAP Cloud ALM with custom fields, search functions, mandatory field checks, consistency checks and automations — directly on SAP BTP.
Why tags in SAP Cloud ALM are not always enough
Additional information that cannot be managed via standard fields is often modeled via tags in the SAP standard. For simple classifications, this approach is sensible and pragmatic.
In real implementation projects, however, it is often about more than pure classification. Customers need to capture business, regulatory or methodological information in a structured way, analyze it unambiguously and in some cases validate it bindingly. When only tags are used for this, long, confusing tag lists, inconsistent maintenance concepts and limited capabilities for reporting, validation and governance quickly emerge.
Custom fields are the prerequisite for capturing company-specific information in a structured way. Without them, this data ends up in free-text fields, Excel lists or external tools — and is lost for analysis, reporting and governance.
Use SAP Cloud ALM more easily in regulated environments
In regulated industries such as pharma, banking or food, changes to SAP systems often have to be documented, assessed and approved according to defined requirements. These requirements describe which information must be captured and reviewed in a traceable manner — but they leave organizations room for choice in how they implement this concretely in their project and ALM processes.
pony supports organizations in using SAP Cloud ALM in a practical way also in such regulated environments. Custom attributes such as GxP Relevance, ICFR Relevance, risk class, compliance status or business approvals can be modeled in SAP Cloud ALM in a structured way, analyzed and integrated into validation or approval processes.
- Simplify the use of SAP Cloud ALM in regulated environments
- Custom attributes for regulatory-relevant information
- Structured documentation instead of free text or Excel
- Support for review, approval and governance processes
What is possible with pony
Custom fields
Typed fields for requirements, user stories and features — centrally configured.
Mandatory field checks
Context-aware mandatory fields for custom fields, depending on status, type or project.
Search functions
Search and filter across custom fields.
Consistency checks
Automated checks on save and on status transitions, also for custom fields.
Automations
Rule-based pre-population of custom fields.
Exchange with third-party systems
Custom fields can also be exchanged with third-party systems via cocat.
Custom fields for requirements, user stories and features
Requirements
Business classification, business area, regulatory context, external references.
User Stories
Acceptance criteria status, estimates, prioritization scheme, ticket IDs.
Features
Roadmap mapping, release context, dependencies, business owners.
Custom fields, mandatory field checks and automations in practice
In this video we show how pony is used and configured in SAP Cloud ALM.
Typical use cases
Complete requirements capture
Requirements and user stories can be typed and categorized via custom attributes — e.g. by business type, implementation relevance or project methodology.
Typing of features
Features can be classified in a structured way via custom attributes — e.g. as Bugfix, Standard Change, Minor Enhancement or Major Enhancement.
Linking to ticket and ITSM systems
Capture, validate and make searchable external keys such as incident or change numbers in a structured way.
Clean status transitions
Couple status transitions to mandatory fields and consistency checks — e.g. no approval without acceptance criteria.
Frequently asked questions
Custom fields in SAP Cloud ALM — implement them now
Book a non-binding consultation and see pony live based on your own requirements.