About Configuring Project Cross-Charge Fact for PeopleSoft
In the services industry, employees might work on projects that are outside of their own organizations. In such cases, the organization that owns a project and the organization that owns the human resource (the employee), might be different. To handle these scenarios in Peoplesoft, Organizational Sharing method of project accounting is used to share costs and revenue that the project or activity generates between the entities. Rules and accounting procedures are setup that define the agreement between the organization that owns the project and the organization that owns the human resource.
If sharing rules are defined and activated, the Pricing process calls the Sharing Application Engine process (PSA_SHARING) to search for rows that are designated for sharing. These rows are either loaded to Cost Fact or Revenue Fact depending on the analysis type. A row is eligible for the Sharing process if it satisfies the conditions set to in sharing setup page to identify shared rows. For example, an Organization that owns the project or activity differs from the organization that owns the transaction. An applicable sharing rule exists, and the row does not qualify as an exception to the sharing rules.
Organization Sharing Example
Assume there is a 80% revenue sharing rule in place between US004 (Receiver) and US001 (Provider) with no exceptions set.
The shared row that gets created in PeopleSoft is loaded to Cross Charge fact table.
Note:
Internal contract sharing is not supported in this release. In addition, sharing rows created directly via the Add transactions page in PeopleSoft are not supported (that is, using Project Costing, then Transaction Definition, then Add Transactions).