ERPstuff - Oracle EBS Community

Hi friends,

I am new to this forum.
I am facing one issue in Purchasing.
We are using Position hierarchy.

When we are trying to forward the requisition to a person in another OU, the document returned back with the status 'incomplete' to the preparer.

Let me explain with example.
1-->2-->3( all three are in same OU and present in the same hierarchy say HIERARCHY-1.
No.4 is the person in another OU present in another hierarchy but not in the above hierarchy(HIERARCHY-1).

When no.1 prepares the requisition and submit, it goes to no.2.
Before approve the req, no.2 needs to get the approval from no.4.
So he forwards to no.4.but the document returns back with the status of' incomplete'.

how to solve this problem.
Please give me your suggestions.

God Bless
Regards,
Arun

Hi Arun,

You need to add 4(person) in ur Position hierarchy (Hierarhy -1). Then you will not get status as incomplete. Try and let m know.

Plz correct m if i am wrong.

Regards,
Subramanian KN.

[quote]Hi friends,

I am new to this forum.
I am facing one issue in Purchasing.
We are using Position hierarchy.

When we are trying to forward the requisition to a person in another OU, the document returned back with the status 'incomplete' to the preparer.

Let me explain with example.
1-->2-->3( all three are in same OU and present in the same hierarchy say HIERARCHY-1.
No.4 is the person in another OU present in another hierarchy but not in the above hierarchy(HIERARCHY-1).

When no.1 prepares the requisition and submit, it goes to no.2.
Before approve the req, no.2 needs to get the approval from no.4.
So he forwards to no.4.but the document returns back with the status of' incomplete'.

how to solve this problem.
Please give me your suggestions.

God Bless
Regards,
Arun

<i><div align="right">Originally posted by arunprasaths

Hi Arun,

Could you pls tell me the whats the Action Hisory shows ?
Then we can find the workflow with whom that is sitting for approval?

Or else whats the error stack from the Approval through workflow.

Regards,
Umakanth