feat: added output management integration

[Venkatakrishnan774]

Disclaimer: Do not include SAP-internal or customer-specific information in this PR (e.g. internal system URLs, customer names, tenant IDs, or confidential configurations). This is a public repository.

Description

Output Management is a BTP shared service which has features like sending documents to external system in various channels like EDI/EMAIL/Print. As part of this, we are mainly concentrating on the email use case where one can send email via our framework along with attachments if necessary.

We are exposing capabilities via util methods of sending email as BTP destination based and via integrated MCP hub. When using the MCP Hub way, we are giving the capability to construct the required payload and invoke the util functions. When using the BTP destination way, we are giving the options to input the destination details and the payloads.

Related Issue

Closes #<issue_number>

(Link to the GitHub issue this PR addresses)

Type of Change

Please check the relevant option:

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Code refactoring
• Dependency update

How to Test

Describe how reviewers can test your changes:

1. Step 1
2. Step 2
3. Expected result

Checklist

Before submitting your PR, please review and check the following:

• I have read the Contributing Guidelines
• I have verified that my changes solve the issue
• I have added/updated automated tests to cover my changes
• All tests pass locally
• I have verified that my code follows the Code Guidelines
• I have updated documentation (if applicable)
• I have added type hints for all public APIs
• My code does not contain sensitive information (credentials, tokens, etc.)
• I have followed Conventional Commits for commit messages

Breaking Changes

If this PR introduces breaking changes, please describe:

• What breaks
• Migration path for users
• Alternative approaches considered

Additional Notes

Add any additional context, screenshots, or information that would help reviewers.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Venkatakrishnan774
❌ lokeshkumarkuntal
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[betinacosta]

Hi. Could you give a more detailed description of this new feature for future reference? Also, is necessary that the title follows commit convention, for exemple: feat: added output management integration.

[tiagoek]

SDK Module Review

Check	Status	Findings
bdd	✅ PASS	0
binding-shape	✅ PASS	0
commits	✅ PASS	0
concurrency	✅ PASS	0
constants	✅ PASS	0
deletion-hygiene	✅ PASS	0
deps-supply	✅ PASS	0
disclosure	❌ BLOCK	1
docs	❌ BLOCK	1
errors-logging	✅ PASS	0
hardcode	✅ PASS	0
http-hygiene	✅ PASS	0
license-spdx	✅ PASS	0
patterns	✅ PASS	0
pr-size	✅ PASS	0
quality-gate-parity	✅ PASS	0
secrets	✅ PASS	0
telemetry	❌ BLOCK	1
testing-depth	❌ BLOCK	1
versioning	✅ PASS	0

Findings (4)

• [BLOCK] DIS-07 — PR body contains unfilled 'Closes #<issue_number>' placeholder (at PR_BODY, no code line to anchor)
• [BLOCK] DC-02 — user-guide.md missing ## Installation section (inline on src/sap_cloud_sdk/outputmanagement/user-guide.md:1)
• [BLOCK] PY-TEL-06 — New @record_metrics added (3 occurrences) but no test asserts record_request_metric was called (at tests/, no code line to anchor)
• [BLOCK] TD-10 — New module 'outputmanagement' has no integration test (at tests/outputmanagement/integration/, no code line to anchor)

4 finding(s): 1 posted as inline comment(s) on the affected lines, 3 not tied to a code line (listed above).

---

Generated by sdk-review-skill · v1

[NicoleMGomes]

Why not use enum directly?

[NicoleMGomes]

Isn't this tenant specific destination?