BrowseAll ecosystems
Everything in the atlas
4 of 2362
Type
Domain: 2
Origin
Signals
More: 3
Group by: Capability
Domain Learning & ReferenceDomain Data & PersistenceLicence MITLicence ISCLicence SAP Developer License AgreementClear all
EntryBySignalsLast activity
abap-tasks-trackerabap-tasks-trackerA task-management tool for SAP projects, built on a CDS view over a BOPF business object with a Fiori list report as its interface, showing that transactional model wired end to end.independent, abap
Task tracker on a BOPF-backed CDS view with a Fiori list report
abaprapunmanagedabaprapunmanagedA practice repository for the unmanaged RAP scenario: a sales order business object whose behaviour implementation delegates to an existing function group.independent, abap
Practice repository for the unmanaged RAP scenario
abaprapunmanagedsaveabaprapunmanagedsaveA practice repository for the managed RAP scenario with unmanaged save: a purchase order business object whose SAVE phase and late numbering are written by hand.independent, abap
Practice repository for managed RAP with unmanaged save
abap-docsabap-docsSAP's ABAP Keyword Documentation scraped from help.sap.com and committed as Markdown in two libraries, Standard ABAP and ABAP Cloud, with keyword and category indexes for the MCP servers and LLMs it is generated for.independent, abap
ABAP Keyword Documentation as Markdown with indexes
The Markdown is a snapshot of whatever help.sap.com served when the pipeline last ran, and the Standard library is scraped from the `latest` index, so which release a page describes follows from the scrape date rather than from anything the corpus states. `package.json` states ISC and the repository carries no LICENSE file, so what the copied SAP documentation may be used for is not stated in it.