OBJECT_ID stores the Period of Service ID instead of the Assignment ID for PER_ALL_ASSIGNMENTS_M ?
Usually, for transactions related to the Assignment page:
•Object Name → PER_ALL_ASSIGNMENTS_M
• Object ID → Employee Assignment ID
However, in one particular case involving a Local and Global Transfer:
• Module Identifier → LocalAndGlobalTransfer
• Object Name → PER_ALL_ASSIGNMENTS_M
• Object ID → Storing the Period of Service ID instead of the Assignment ID
This behavior seems unusual to me. Has anyone observed the Object ID referencing the Period of Service ID in such cases?Also, is there any Oracle documentation or known explanation related to this behavior?
Tagged:
1