LegalName for Tasks created via the partner-upload-controller

[StWeisshaar]

Description

As operator of BPDM,
I require the business partner object that can be reserved via the Orchestrator Task Worker to contain legalName or nameParts,
so that all relevant information is present.

Acceptance Criteria

• legal entity information are fetched from the Pool based on the legalEntityBpn
• nameParts and legalName are populated based on fetched information

Additional Information

The issue is relevant for the BP explorer context. The partner-upload-controller allows users to upload their sites and addresses. When using the csv upload feature you can not provide any legal entity information. The legal entity information for such a task is currently populated based on the BPNL that was used in authentication. Tasks created via the partner-upload-controller therefore do not contain a legalName or nameParts, but only contain a legalEntityBpn. Such tasks do not fulfill the mandatory field requirements and can create downstream issues.

• 2.1.2 UPLOAD CRITERIA AND MANDATORY FIELDS
• partner-upload-template.txt

Note: Using this endpoint companies will only be able to create sites and address for their own legal entity. This endpoint can not be used to create sites or addresses for any other legal entity. Even subsidiaries are excluded as they will generally have distinct BPNLs.

[StWeisshaar]

@maximilianong @nicoprow Using the BP Explorer companies will only be able to create sites and addresses linked to the legal entity (BPNL) that is present in the authentication token. A parent company will not be able to manage sites and addresses for their subsidiaries using the same token. A separate token will be needed for each legal entity. Is this an intended restriction?

[nicoprow]

@maximilianong @nicoprow Using the BP Explorer companies will only be able to create sites and addresses linked to the legal entity (BPNL) that is present in the authentication token. A parent company will not be able to manage sites and addresses for their subsidiaries using the same token. A separate token will be needed for each legal entity. Is this an intended restriction?

Actually for this version this is the intention as the CSV upload should be restricted to the company's own sites and adddresses. In later enhancements we may be able to also manage owned legal entities.