Previous	Next		Contents	Index	Navigation	Glossary	Library

Example A: PA Implementation Options Table

Operating Unit	Set of Books	Currency	Business Group	Start Organization	PA Period Type
Los Angeles	US	USD	BG1	PORGA	Weekly
San Francisco	US	USD	BG2	PORGB	Weekly
New York	US	USD	BG2	PORGB	Weekly
London	UK	GBP	BG2	PORGB	Weekly

Example A: PA Implementation Options Diagram

Example A: HR Organizations, Labor Resources, and Projects

Business Scenario:

   Set up project PROJ-SF:

• Use a San Francisco responsibility (since San Francisco is the project operating unit) to set up PROJ-SF and the Work Breakdown Structure.

• The Project/Task Organization LOV will show PORGB1, PORGB2, PORGB3, PORGB4, PORGB5, PORGB6 and PORGB7. PORGB1 is selected to be associated with PROJ-SF and its subordinate tasks.

• The expenditure operating unit for PROJ-SF can be either San Francisco or New York. London cannot be the expenditure operating unit for PROJ-SF because it is associated with a different set of books. Similarly, Los Angeles cannot be the expenditure operating unit for PROJ-SF because it is associated with a different business group.

• The Expenditure Organization can be any HR organization under BG2, which includes: BG2, PORGB, PORGBa, PORGBb, PORGBc, PORGB1, PORGB2, PORGB3, PORGB4, PORGB5, PORGB6 and PORGB7. (Note: you can use AutoAccounting and the Account Generator to map to the correct Balancing Segment Value and Cost Center Segment Value in order to generate account numbers for each operating unit).

• Project chargeable employees for PROJ-SF include EMPSF, EMPNY, and EMPLD because San Francisco, New York, and London share the same business group.

• Project PROJ-SF can use any Burden Schedule that is set up and/or updated in operating units that are associated with BG2 (San Francisco, New York and London).

   Enter Expenditures:

• Employee EMPNY will submit timecards and expenses using a New York PA responsibility.

• Chargeable projects consist of PROJ-SF and PROJ-NY. PROJ-LD is not chargeable because it is associated with a different set of books, and PROJ-LA is not chargeable because it is associated with a different business group. EMPNY will charge to PROJ-SF in this case.

• The expenditure operating unit is New York.

• The expenditure organization is PORGB3, the HR organization assigned to EMPNY, unless an organization override is set up in project PROJ-SF.

• If project manager approval is required, the timecard and expenses will be routed to employee EMPSF for approval. (Note: routing can only go to an employee in the same business group.) The Review Timecards/Expense Reports window will display all routed expenditure batches and expenditures across operating units that share the same business group.

   Project Costing:

• After approval, EMPNY's timecard and expenses against PROJ-SF will be processed when New York runs the Cost Distribution process.

• The cost distribution lines are created in New York (the expenditure operating unit), using cost rates set up in New York. Burden costs are calculated using burden schedules tied to the projects.

• Project cost will go from the New York operating unit's PA to US set of books (New York operating unit's GL) with a process initiated by the New York responsibility.

• Expense reports will go from the New York operating unit's PA to the New York operating unit's AP with a process initiated by the New York responsibility. The New York operating unit's AP will then pay expense reimbursement to EMPNY in USD (the functional currency of the operating unit).

• EMPNY can view all of his expenditures in New York on the Expenditure Inquiry Form using a New York Responsibility. EMPSF, the project manager, can view PROJ-SF specific expenditures including EMPNY's timecard and expenses in the Expenditure Inquiry window, using a San Francisco Responsibility (since San Francisco is the project operating unit).

   Project Billing:

• All revenue and invoice processes need to be performed in San Francisco (the project operation unit) using a San Francisco responsibility.

• The Generate Draft Revenue process will create revenue distribution lines in the San Francisco operating unit using project overrides or San Francisco's bill rates.

• Borrowed and lent revenue will be processed according to the setup, because the expenditure organization (PORGB3) is different from the project organization (PORGB1).

• Use the San Francisco responsibility to query revenue figures in the Expenditure Inquiry window. You will see expenditures from all expenditure operating units (in this instance, San Francisco and New York).

• Use the San Francisco responsibility to run the Generate Invoice process.

• Project revenue will go from the San Francisco operating unit's PA to US set of books (the San Francisco operating unit's GL) with the revenue process initiated by the San Francisco responsibility.

• Invoices go from the San Francisco operating unit's PA to the San Francisco operating unit's AR with a process initiated by the San Francisco responsibility. Invoice numbering is processed according to the San Francisco operating unit's implementation options.