Creating Service Instances in Your SAP BTP Subaccount

The default plan of SAP Event Mesh uses a centralized, event-oriented architecture. The service separates communication between sending and receiving applications to ensure the delivery of events and messages between them. In the SAP BTP subaccount, add new instance: Event Mesh. Set the plan to default. In the parameters section, provide the JSON code.

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556
{ 

    "emname": "<provide any name for em>", 

    "namespace": "<provide any namespace>", 

    "version": "1.1.0", 

    "options": { 

        "management": true, 

        "messagingrest": true, 

        "messaging": true 

    }, 

    "rules": { 

        "queueRules": { 

            "publishFilter": [ 

                "${namespace}/*" 

            ], 

            "subscribeFilter": [ 

                "${namespace}/*" 

            ] 

        }, 

        "topicRules": { 

            "publishFilter": [ 

                "${namespace}/*" 

            ], 

            "subscribeFilter": [ 

                "${namespace}/*" 

            ] 

        } 

    } 

}

The most current version of the JSON code is stored in Administration Guide for SAP Ariba Supplier Quotation Management.

The SAP Event Mesh default plan concept supports the following messages and event-enabling concepts:

• Queues
• Queues subscription
• Events
• Asynchronous messaging
• Message client
• Event catalog
• Webhooks

SAP Ariba Direct Materials Sourcing is designed to manage complex sourcing projects, especially when dealing with critical components that often require manufacturing based on detailed technical drawings and specifications.

Due to the complexity of these parts and the need to ensure that quotes are covering the correct parts, the buyer and supplier will need to share a lot of additional documentation. For example, a buyer may need to provide technical drawings, specifications, or cost breakdowns to the supplier. At some stage, the buyer might also ask the supplier to send certain documents with their quote, such as a cost breakdown or necessary certifications. To make it easy to exchange these documents, you'll need to enable the Object Store service on SAP BTP. This service helps manage attachments from the supplier side, ensuring smooth sharing of important files.

The Object Store allows you to store and manage objects. After enabling this service, you will be able to create, upload, download, and delete objects. In the Instances and Subscriptions section, create a new instance. Once the instance is created, the status will be changed to Created.

The SAP Destination service is also used in the process of document exchange between supplier and buyer. In the Instances and Subscriptions section, create a new instance. Select the Lite plan for the destination service. Once the instance is created, the status will be changed to Created. The attachments shared by buyer will be stored in the SAP system, and approuter will enable the supplier to download the documents directly from the system. The destination service will be used to identify which service approuter should use to download the documents.

Activating the SAP Connectivity service is essential for seamless integration and secure communication across the enterprise application landscape. In the Instances and Subscriptions section, create a new instance. Select the Lite plan for the connectivity service. Once the instance is created, the status will be changed to Created.

An XSUAA instance is also needed for document exchange in SAP Ariba supplier quotation management.

In the Instances and Subscriptions section, choose Create service and select Authorization and Trust Management Service. Select the application plan for XSUAA instance. In the Parameters section, provide the following parameters:

123456789101112131415161718192021222324
{
"xsappname": "<your approuter name, application name example: approuter-demo>",
"tenant-mode":"dedicated",
 "description": "Security profile of called application",
 "scopes": [
 {
 "name": "uaa.user",
 "description": "UAA"
 }
 ],
"oauth2-configuration":{
"redirect-uris":["https://*.<redirect domain>.hana.ondemand.com/**"]
},	
 "role-templates": [
 {
 "name": "Token_Exchange",
"description": "UAA",
"scope-references":[
"uaa.user" 
 ]
 }
 ]
}

The most current version of the parameters is stored in the setup guide: Creating an XSUAA instance