A custom, limited permission set (built without FND_ENDUSER, to qualify for LTU/Limited Task User licensing) has the DocReferenceObject connection added, the relevant database method granted, and every cache refreshed — but attachments on the target screen still show 'No Attachment Types Enabled.' What's commonly still missing?

Q: A custom, limited permission set (built without FND_ENDUSER, to qualify for LTU/Limited Task User licensing) has the DocReferenceObject connection added, the relevant database method granted, and every cache refreshed — but attachments on the target screen still show 'No Attachment Types Enabled.' What's commonly still missing?

Grant the ObjectConnectionServices Activity to the custom permission set — this has resolved this exact symptom even without FND_ENDUSER included, once every other piece (DocReferenceObject connection, the relevant database method grant, cache refreshes) was already confirmed correct. Attachments/object connections depend on this Activity being granted separately from the individual database-object and presentation-object grants that are more commonly checked first.

Answer

Grant the ObjectConnectionServices Activity to the custom permission set — this has resolved this exact symptom even without FND_ENDUSER included, once every other piece (DocReferenceObject connection, the relevant database method grant, cache refreshes) was already confirmed correct. Attachments/object connections depend on this Activity being granted separately from the individual database-object and presentation-object grants that are more commonly checked first.

← Browse Security and access questions