[Backend] Trace-X uses its own BPDM lookup to identify Customer data for BPNL

[mkanal]

As user
I want that BPDM lookup is managed in trace-x
so that I receive detail information attributes from golden record for a bpnl (address, customer contact, etc )

Background

Currently, Trace-X uses BPDM lookup feature of irs to determine manufacturer name for BPNL. This limits the information attributes of Golden record to the manufacturer name.
This ineffective bpnl lookup should be removed from irs. Trace-X has to develop its own bpnl lookup in order to receive more detail information for a bpnl.

Hints / Details

• https://business-partners.int.demo.catena-x.net/pool/ui/swagger-ui/index.html#/
• https://business-partners.int.demo.catena-x.net/companies/test-company/ui/swagger-ui/index.html#/

Outcome / Acceptance Criteria

Outcome

• ...

Acceptance Criteria

• Manufacture name lookup for bpnl is made by trace-x app

Technical Tasks

• Update integration tests e2e
• Update documentation
• Update IRS Mapping / get rid of old logic
• Implement new BPDM Client
• Add BPDM Mock to test functionality.

Out of Scope

• ...

[mkanal]

@jzbmw Idea is to descope bpn lookup feature from irs. trace-x should provide its own implementation.

[ds-lcapellino]

Currently not testable due to Portal reset and SemanticHub as well as BPDM Service connected to the old keycloak instance.

[ds-mwesener]

Currently waiting for: #778 to be able to test successfully.

[ds-lcapellino]

Architecture changed while implementation from OAuth2.0 to EDC Flow.

[mkanal]

PO acceptance in behalf of @jzbmw. Works as intended.

[ds-lcapellino]

The concept for the new EDC flow will be created within #901.