Oracle Communities

Oracle Analytics and AI

Child Item

HCM - Position subject area showing Assignment Category Code rather than Assignment Category Name

A.J.

When I pull in the Assignment Category from the HCM - Positions subject area, the results that I see are the Assignment Category Code, and not the Assignment Category name.

Maybe this is being caused by something that my organization has configured incorrectly but it doesn't appear so to me.

From what I can tell from the SQL generated, it is because the join of DW.ASSIGNMENT_CATEGORY_D_TL does not include a join on ASSIGNMENT_CATEGORY but rather has a join between ASSIGNMENT_CATEGORY and LANGUAGE (D1.c3 = D2.c2) which is causing the join to fail and therefore the NVL is always producing the ASSIGNMENT_CATEGORY from DW_POSITION_D and never the ASSIGNMENT_CATEGORY_NAME from DW_ASSIGNMENT_CATEGORY_D_TL.

Am I reading this correctly? Or is there something I should fix on my end?

Find more posts tagged with

FDI Back End

FDI

Fusion AI Data Platform

Accepted answers

JohnW-Oracle

Hi @A.J.,

I didn't realize it when I first responded but we did have a Bug on this and it was scheduled to be fixed in the 25.R2 release.

For your reference, the Bug number is: 37830535

Regards,

John

All comments

JohnW-Oracle

Hello @A.J..

Your results are a little unexpected. This issue may require a SR.

As a test, could you replace your Assignment Category Code and Assignment Category from the HCM - Positions Subject Area with the same from the HCM - Workforce Core Subject Area as follows:

It would be interesting to see if you get different results.

Regards,

John Whitaker

A.J.

Thanks John,

The Assignment Category from HCM - Workforce Core works just fine and I see the value from DW_ASSIGNMENT_CATEGORY_D_TL.ASSIGNMENT_CATEGORY_NAME because the code does a join using the ASSIGNMENT_CATEGORY:

You mention an SR, which I am happy to open an SR if this is something specific to how my organization configured things. I just guessed that since HCM - Positions was delivered, that it might be more widespread and something worth asking on the community.

Please let me know.

Thanks,

A.J.

JohnW-Oracle

Hi @A.J.,

I didn't realize it when I first responded but we did have a Bug on this and it was scheduled to be fixed in the 25.R2 release.

For your reference, the Bug number is: 37830535

Regards,

John

Bhaskar Konar

https://community.oracle.com/products/oracleanalytics/discussion/comment/68491#Comment_68491

Very helpful information.

Thanks for sharing @JohnW-Oracle!