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

OFBIZ-11683 Fixed: Humanres tree allows existing OU to be added again #283

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from

Conversation

SebastianEcomify
Copy link
Contributor

Fixed: Humanres tree allows existing OU to be added again (OFBIZ-11683)

roleTypeId 'INTERNAL_ORGANIZATIO' is added for PartyRelationship in the
DemoData to prevent duplicate entries.

Thanks Pierre Smiths for reporting the issue

roleTypeId 'INTERNAL_ORGANIZATIO' is added for PartyRelationship in the
DemoData to prevent duplicate entries.

Thanks Pierre Smiths for reporting the issue
@sonarcloud
Copy link

sonarcloud bot commented Mar 2, 2021

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@JacquesLeRoux
Copy link
Contributor

HJi Sebastian,

I tested and after adding the data I was able to add a "company" to "company" as it exists in trunk HEAD. Then you get an infitinte recursive tree that does not seem to fit to me.

Also please comment your change to be used in the description of the commit and of course to better understand what you are doing, TIA

@PierreSmits
Copy link
Member

Hi Sebastian, all,

We should not regard departments as internal organisations (we should reserve that for fiscal/legal entities, requiring their own CoAs).

The roll-up for departments should be:

Best regards,
Pierre

@PierreSmits
Copy link
Member

Hi,

Why are you treating departments of the internal organisation (partyID=company) as internal organisations as well? Should these have their own accounting preferences, as well as having their own gl schema?

Clearly, departments, teams, etc. should not be treated as internal organisations but rather as what they are intended to portray.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants