onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

tailspendmanagement

A CAP reference application for tail spend management: preferred suppliers, region and commodity code mapping, automatic RFP event rules and SAP ERP demand.

A worked CAP application for tail spend, the purchases its README calls more difficult to control and less visible than core procurement activities. It covers preferred supplier management, mapping regions and commodity codes to a supplier, automatic RFP event rule management and SAP ERP demand, published as a reference for customers developing applications internally and as a possible alternative to the current quote automation process on SAP Ariba. It is packaged and deployed to the SAP BTP, Cloud Foundry Runtime by one npm script; the main branch runs against PostgreSQL on SAP BTP, hyperscaler option, and taking it to HANA means converting the database to HDB and updating MTA.YAML.

GitHub1 ★

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
CAP
Demonstrates
Reference appsCAPReference appscapabilityA whole application to read rather than a snippet to copy — somewhere to see how the pieces sit together once there are more than three of them.
Requires
PostgreSQL on SAP BTP, hyperscaler optionPostgreSQL on SAP BTP, hyperscaler optionartifactthe database the main branch runs against, listed first among the pre-requisite BTP services.SAP Application Logging service for SAP BTPSAP Application Logging service for SAP BTPartifactthe logging service listed among the application's pre-requisite BTP services.SAP Job Scheduling serviceSAP Job Scheduling serviceartifactthe scheduling service listed among the application's pre-requisite BTP services.SAP BTP, Cloud Foundry RuntimeSAP BTP, Cloud Foundry Runtimeartifactthe runtime the multi-target application is built and deployed to, listed among the pre-requisite BTP services.

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222@SAP-samplesmaintainerGanesh RamachandranPersonContributes to this
In the atlas: contributes to 3@gnshram1 contributor

What it declares

Every artifact

Type
Sample
Origin
By SAP
Use as
A reference

As a sample

Form
A reference application

Connections5

Download
tailspendmanagement connectionstailspendmanagementPROVIDES→ demonstrates1demonstrates authoredReference appsNEEDS→ needs4needs stated the database the main branch runs against, listed first among the pre-requisite BTP services. SAP-samples/tailspendmanagement — README, Requirements: https://github.com/SAP-samples/tailspendmanagementPostgreSQL on SAP BTP, hyperscaleroptionneeds stated the logging service listed among the application's pre-requisite BTP services. SAP-samples/tailspendmanagement — README, Requirements: https://github.com/SAP-samples/tailspendmanagementSAP Application Logging service for SAPBTPneeds stated the runtime the multi-target application is built and deployed to, listed among the pre-requisite BTP services. SAP-samples/tailspendmanagement — README, Requirements: https://github.com/SAP-samples/tailspendmanagementSAP BTP, Cloud Foundry Runtimeneeds stated the scheduling service listed among the application's pre-requisite BTP services. SAP-samples/tailspendmanagement — README, Requirements: https://github.com/SAP-samples/tailspendmanagementSAP Job Scheduling service

README

quoted from SAP-samples/tailspendmanagement under Apache-2.0, read
SAP-samples/tailspendmanagement/README.mdOn GitHub

REUSE status

Welcome to TailSpend Management

Welcome to the sample use case of the Tailspend Management application. This open source application developed using the Cloud Application Programming Model (CAP) will help as reference for customers developing applications internally as a possible alternative to current quote automation process using SAP Ariba to manage tailspend. Tail Spend is often overlooked or not managed efficiently, as it tends to be more difficult to control and less visible than core procurement activities. Some key aspects provided by Tailspend application to address tail spend are Preferred Supplier Management Mapping Regions and Commodity Codes to Supplier Auto RFP Event Rule Management SAP ERP Demand

Requirements

This solution utilizes BTP Services. Below are pre-requisite services for using this application.
a. PostgreSQL on SAP BTP, hyperscaler
b. SAP Application Logging Service for SAP BTP
c. SAP Job Scheduling Service
d. SAP BTP, Cloud Foundry Runtime

Description

Ariba Quotation process currently utilizes complex option Effective tail spend management can lead to better cost savings and other benefits like Risk Reduction, Efficiency by automating and streamlining the process

Cost Savings: By consolidating suppliers and negotiating better prices companies can realize substantial savings. Risk Reduction: Lower visibility purchases often carry a higher risk.Effective Tail spend management can help mitigate supplier risk and ensure compliance. Efficiency: By Automating and streamlining the tail spend management process, companies can reduce the administrative burden and focus on strategic initiatives. Improved data visibility: This can lead to better decision making as companies gain more accurate understanding of the spend.

Sample View of ITK Lite Admin Application

Reference Image

Database Requirement

Use the main GIT branch if you are using PostgreSQL as your database in BTP. If the database is HANA DB, convert the database HDB and also update MTA.YAML to deploy Multi Target Applications with HANA Database.

Deploy the Application

Prior to running the package and deploy.

Step1: Go to app directory and run npm i command.
Step2: Run the same command npm i under root directory as well.
Step3: Run the following command to build and deploy the file to the SAP BTP, Cloud Foundry environment.

npm run mta:package:deploy

Known Issues

No known Issues

How to Get Support

Create an issue in this repository if you find a bug or have questions about the content.

For additional support, ask a question in SAP Community.

Contributing

If you wish to contribute code, or offer fixes and improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

License

Copyright (c) 2023 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.#� �L�a�s�t� �u�p�d�a�t�e�d� �0�6�/�1�3�/�2�0�2�6� �2�1�:�1�5�:�0�6� � �

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
github.com/SAP-samples/tailspendmanagementtree, 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 domaincap, learning-and-reference
Contributors1
Ganesh Ramachandran

From the repository’s contributor list, .

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