on ‎2023 Apr 10 10:59 AM
Hi,
I have a scenario where some table data is getting replicated into HANA from an ECC system with the help of SLT.
The requirement is to send these records over to an external system as soon as they reach HANA using an HTTP POST. The table has timestamps allowing me to identify the latest records.
My question is:
Thank you for your help.
Request clarification before answering.
you can use SLT in cascade. In the second SLT configuration, your HANA system would be the source and the external system would be the target.
For this, you can use the SLT SDK: see https://help.sap.com/docs/SAP_LANDSCAPE_TRANSFORMATION_REPLICATION_SERVER/007c373fcacb4003b990c6fac2...
In the SLT BADI, you would use CL_HTTP_CLIENT ABAP Class to call your external system API and post data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think there is anything 'standard' that you can do to get an event in CAP when you enter a record in an underlying DB table through 'non CAP' means.
Thinking out of the box, what you could try are a few things:
Approach A:
1. setup a HANA remote source/virtual table to a HTTP BTP service (CAP or event mesh and then CAP).
2. Use the trigger to call the virtual table which in turn/ultimately 'triggers' a CAP service request.
3. Once you captured the event in CAP, you can process it as if the event came in through a standard OData request.
Approach B:
1. Redirect the call through a CAP OData service which gives you all the options
Approach C
1. Setup business event enablement and connect it to event mesh. So rather than using SLT, you would just trigger an event and push it into the event mesh
2. Build a CAP application that can control and supplement what goes into the target application.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The idea would be that rather than SLT writing to HANA directly, you would do a post to the CAP service to store the information. CAP then would store the information but in the 'after' entity handler you could add any logic you want/need.
| User | Count |
|---|---|
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.