Procurement User doesn't get same value as Admin User

Question

A procurement user brought up an issue that Requisition Count field does not show the right values for 2023 and 2024. When testing the same report with my (admin) user, the values are different and correct. This user has the same groups assigned as they do roles in fusion apps. They also have the same Spend Procurement BU security assignment as me. What could be causing them to get a different/incorrect value?

Molly P · Accepted Answer

Hi @Sumanth V -Oracle, thanks for the tip. I did notice a difference in the session logs - for the procurement user, there were extra joining clauses referencing security objects. Example: SEC_OBJ_CODE,

SEC_OBJ_MEMBER_VAL_NUMBER SEC_OBJ_MEMBER_VAL

FROM SEC_SECURE_BY_OBJ_MEMBER_USER

WHERE USERNAME='VALUEOF(NQ_SESSION.USER)'

AND SEC_OBJ_CODE = 'OA4F_SEC_PROC_REQ_BUSINESSUNIT_LIST'

For my user (FAW Service Admin), the clauses don't exist in the session log. Because this was the main difference, I tried adding the FAW Service Admin group to the procurement user. Once I did this, they got the correct results/same results as me. When I removed it again, they got the incorrect results again.

The procurement user has full Spend Procurement BU access, so why are values being restricted? They should get the same results as an admin with full Spend Procurement BU access.

Thanks,

Molly

Sumanth V -Oracle · Accepted Answer

@Molly P - This confirms the behavior seen is due to the data security configured. Please check the data security setup to see if you have any customizations done there.