onedevatlasBeta
Browse the atlas
AllABAPCAPUI5BTP
AppApptypeAn application you deploy and use, installed into a system or loaded into an application as a component, rather than a library whose functions you call.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

abapOpenReview

A code-review tool for SAP GUI that ties a checklist to a transport request: a transport whose diff contains code must be approved before it can be released.

Comes with two transport system enhancements. A transport request that contains a code diff must be approved before it can be released, a check the README says can be deactivated, and reviews are closed after a transport request is released. The repository also holds the program zaor_import_default_checklist, which imports a default checklist of three items: dependencies changed in other transport requests, customizing settings that are in the transport request or already created in the target system, and API major changes bumped to dependents. Its design goals are to work via SAP GUI with no Eclipse integration, to be customizable and extendable, and a version requirement of 702, with abapGit as the way in.

GitHub34 ★
abaplint4,637 lines

Facts

Last pushLicenceGPL-2.0

Where it sits

Lives in
ABAP
Provides
Code reviewABAPCode reviewcapabilityReading a change before it moves on: which files or objects a change contains, what changed in each since an earlier version, and what a reviewer decided about each part. Comparing two versions of one object is where it starts; the review is the record kept of the decision.
Flavors
Standard ABAP
Requires
abapGitabapGitartifactThe only installation route the README's design goals name for getting the tool into a system.

Who is behind it

Lars HvamLars HvamPersonMaintains this
In the atlas: maintains 13, contributes to 92, wrote 1@larshpmaintainerJohannes GerbershagenPersonContributes to this
In the atlas: maintains 1, contributes to 7@germanysourcesLeTyskerPersonContributes to this
In the atlas: contributes to 1@LeTyskerMarc BernardPersonContributes to this
In the atlas: contributes to 26@mbtools3 contributors

Before choosing this

Signals

ActivityQuietNo published releases; repository quiet for 31 months

It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.

What it declares

Every artifact

Type
App
Origin
Independently maintained

As an app

Where it runs
Inside the system it serves
Distributed through
abapGit

Connections2

README

quoted from larshp/abapOpenReview under GPL-2.0, read
larshp/abapOpenReview/README.mdOn GitHub

abapOpenReview

ABAP Review Tool

Design goals

  • Work via SAP GUI(ie. no Eclipse integration)
  • Version requirement: 702
  • Customizable and extendable
  • Install via abapGit

Integration in the transport system

abapOpenReview comes with two transport system enhancements:

  • When a transport request contains code diff, it must be approved before the transport request can be released. This check can be deactivated.
  • Reviews are closed after a transport request is released.

Default checklist

The repository contains the program zaor_import_default_checklist to import a default checklist with the following items:

  • Dependencies changed in other transport requests? When yes, the code will proparly break in target system, when this transport request is transported before the transport requests with the dependencies.
  • All associated Customizing-Settings contained in transport request or are already created manually /via ALE-transfer in target system (e.g. Characteristics in CT04, Classes in CL02)?: Not all Customizing-Settings are transported automatically e.g. the characteristics in transaction CT04, the classes in transaction CL02 (both from the classification API) or z-tables not marked correctly as customizing-tables. In this point we should make sure, that the Customizing-Settings between source and target system don't differ.
  • API-Major-Changes (class, function-module etc.) bumped to dependents?: When your transport request introduces major-changes, the dependents, which uses the APIs, can break. In this point we should make sure, that the dependents are compatible with the new API.
GPL-2.0, read

Others providing4

Compare all 5 on the Code review page →
Code review
  1. abapTimeMachineShows a whole ABAP object as it stood at a past version
  2. abap-transport-reviewTransport release check gated by GitHub pull request approval
  3. AVESAP GUI version explorer and code reviewer for transport requests
  4. VERTEXADT extension for Eclipse and VS Code showing three SAP GUI tools

Details

Sources3
Added by handdiscovered herechecked
github.com/larshp/abapOpenReviewtree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, developer-experience
abaplint
issues under its own abaplint configuration0
lines4,637
statements2,602
objects43
files30
analysed, main
abaplint version2.120.84
read fromabaplint.app,
Flavors1
Standard ABAP
“* Work via SAP GUI(ie. no Eclipse integration)” — larshp/abapOpenReview — README, Design goalschecked
Contributors3
Johannes GerbershagenLeTyskerMarc Bernard

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:larshp-abapopenreview
JSON
/artifacts/larshp-abapopenreview.json
MCP
Connecting an agent