sap-usi-exception
A shared root exception class and text getter API used across SchwarzIT's USI ABAP developments, converting an exception's text into a common format such as BAPIRET2 or SYMSG.
Every USI package reuses one root exception class from this repository rather than defining its own, and an extensible text getter API converts an exception's text into a common format such as BAPIRET2 or SYMSG for the caller that needs it. It installs as its own ABAP package, /USI/EXCEPTION, with no further dependencies. It stops at the exception class and the text conversion; what raises the exception is left to each USI package.
Facts
Where it sits
Who is behind it
In the atlas: maintains 3@SchwarzITmaintainerDennis SchaafContributes to this
In the atlas: contributes to 3@d-schaafMarc F. BernardContributes to this
In the atlas: contributes to 4@marcfbeJörg NeumannContributes to this
In the atlas: contributes to 3@NeumannJoergPatrick HahnContributes to this
In the atlas: contributes to 3@patrick2464 contributors
What it declares
Every artifact
- Type
- Package
- Origin
- Independently maintained
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Turning a failure into a response a client can act on
Download
README
quoted from SchwarzIT/sap-usi-exception under Apache-2.0, read
USI Exception
Purpose
The component offers an extensible text getter API that can be used to convert exception texts into various common formats such as BAPIRET2 or SYMSG.
It additionally contains our root exception class, that will be reused by all USI developments.
Installation Guide
This component has no dependencies and no special authorizations are required.
It is recommended to create the repository using the follwing settings.
| Field | Value |
|---|---|
| Git Repository URL | https://github.com/SchwarzIT/sap-usi-exception |
| Package | /USI/EXCEPTION |
| Display Name | USI Exception |
| Labels | SchwarzIT |
Note: The package name must start with /USI/ to avoid issues when pulling the repository.
After cloning the repository the basic customizing has to be maintained manually. The process is described here.
How to contribute
Please check our contribution guidelines to learn more about this topic.
Further information
History
Others providing
Compare all 5 on the Error handling page →- throwthrowA minimalistic way to raise an ABAP exception, from a text passed directly or, with no argument, from the system fields a preceding MESSAGE statement filled, as a static method or through an interface.independent, abapRaises an ABAP exception from a text or the last system message
- ABAP-PRCABAP-PRCA framework for custom multi-step ABAP processes: a process class declares the states, and the framework runs each document through them and monitors the run.independent, abapFramework for multi-step ABAP processes with monitoring
- RESULT-for-ABAPRESULT-for-ABAPAn ABAP implementation of the result pattern: a method returns an object built with ok or fail instead of raising an exception for an expected failure, and several results combine into one.independent, abapResult pattern for ABAP instead of exceptions for expected failures
- EITHER-FOR-ABAPEITHER-FOR-ABAPAn ABAP class implementing the Either pattern, holding a success value or an error from a method call in one object, with checks for which side it holds and exceptions for misuse.independent, abapABAP class implementing the Either pattern
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
abaplint
History in the atlas
- First seen.
For your agent
- Ref
artifact:schwarzit-sap-usi-exception- JSON
- /artifacts/schwarzit-sap-usi-exception.json
- MCP
- Connecting an agent