|
|
Index: Date Index | Thread Index
[Date Prev] | [Date Next] | [Thread Prev] | [Thread Next] [OAUGNet]-Re: PO / HR question
Hi Jim, Please find below my experiences while implementing PO/iProc where HR is installed. We had to suggest two segment Position Flexfield: Position Code.Position Name Position Code: Numeric, 6 to 10 Digits based on Client preference Position Name: Description of the Position Since Position Hierarchy does not support One to Many relationship, It was found that defining unique positions (Position Code.Position Name) was helpful to build the Position Hierarchy. Generally in iProc implementations, there is a possibility that the number of requestors are more accessing the system and if you might want to have requisition hierarchy built in from Requestor level to Final Approver level. In such cases, it is better to have unique position codes to identify each requestor and subsequently thier requisition approval path. Positions are defined for HR organization. Position Hierarchy is not constrained by inventory orgs. You could have requisitioner in One Org (Inventory Org or Department) and Approver in another Org. Once Requisition is approved, then it enters the Procurement Cycle where Buyer Initiates and then it follows PO approval Path. Hope this helps. Cheers DJ Oracle Apps Div : K SOURCE INC 100 West Big Beaver Rd Troy, MI 48084 -------- Original Message -------- Subject: [OAUGNet]-PO / HR question From: Jim <fierosrcul@yahoo.com> Date: Tue, January 24, 2006 2:02 pm To: "OAUG Net listserver" <OAUGNet@oaug.com> Is there anyone using a full install of HR with Purchasing and/or iProcurement? If so, could you contact me regarding to how you set up your HR positions and the PO position hierarchy? We are using position hierarchy, rather than manager<>employee relationship to do routing for approvals and are struggling with what is the most effecient way to set this up and not require a lot of maintenance within HR. (AME is not an option for us because we can not upgrade to 11.5.10 at this time) How many segments do you have in your position flexfield? How are the segments defined? How is your organization defined? Do you have any situations where a requisitioner can be in one org, but the buyer/approver is in a different org? Do you have any situations where you have multiple people with the same position, in an org who need to be requistioners or buyers? Any input into your structure would be appreciated. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ############################################################# This message is sent to you because you are subscribed to the mailing list <OAUGNet@oaug.com>. To unsubscribe, E-mail to: <OAUGNet-off@oaug.com> To switch to the FEED mode, send any message to <OAUGNet-feed@oaug.com> To switch to the DIGEST mode, E-mail to <OAUGNet-digest@oaug.com> To switch to the INDEX mode, E-mail to <OAUGNet-index@oaug.com> Send administrative queries to <OAUGNet-request@oaug.com> ############################################################# This message is sent to you because you are subscribed to the mailing list <OAUGNet@oaug.com>. To unsubscribe, E-mail to: <OAUGNet-off@oaug.com> To switch to the FEED mode, send any message to <OAUGNet-feed@oaug.com> To switch to the DIGEST mode, E-mail to <OAUGNet-digest@oaug.com> To switch to the INDEX mode, E-mail to <OAUGNet-index@oaug.com> Send administrative queries to <OAUGNet-request@oaug.com> Index: Date Index | Thread Index Thank you for using the OAUG Listserver Archive.
|
|