Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up access to ALL BP data records in CX-Pool #1148

Open
19 tasks
zygokaktus opened this issue Jan 20, 2025 · 0 comments
Open
19 tasks

Set up access to ALL BP data records in CX-Pool #1148

zygokaktus opened this issue Jan 20, 2025 · 0 comments

Comments

@zygokaktus
Copy link

zygokaktus commented Jan 20, 2025

Overview

Establish a technical access via API to all BP data records in the CX Pool (B"BP Lookup"), not only the BP data records for companies which are onboarded
CX-member. This shall apply to the BP data of all three levels: L/S/A. The content of the found BP data record shall be displayed.

What's the benefit?

Establishing an access to the whole CX BP data records would be an enabler for an improved BP data maintenance processes of a CX-member.
With this function it will be possible to search for BP in the CX Pool, no matter if they are onboarded yet or not, and use the content of the found data record for further usage (e.g. creating the BP in the own Master Data Management System (MDM) of a CX member).

What are the Risks/Dependencies ?

Detailed explanation

Current implementation

Proposed improvements

Feature Team

Contributor

  • Contributor 1
  • Contributor 2

Committer

  • Committer 1
  • Committer 2

User Stories

  • Issue 1, linked to specific repository
  • Issue 2, linked to another specific repository

Acceptance Criteria

  • Criteria 1
  • Criteria 2
  • Criteria 3

Test Cases

Test Case 1

Steps

  1. Do something
  2. Click something
  3. Add something

Expected Result

  1. Expectation
  2. Expectation
  3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented.

In the context of the standards 126 and 127, typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

  • I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Inbox
Development

No branches or pull requests

1 participant