Use this activity to define the connection between the employee company activity and the customer company activity. For IFS Cloud 22R1 there are two possible ways how to do that.
The new Multi-Company Project Reporting Rule Setup was introduced to reduce the one-to-one activity links which is hard to administrate and maintain. It should also improve the performance when reporting time and cost on Multi-Company Project activities as it is possible to provide a wildcard option % on the customer side when setting up a rule.
Before start using Multi-Company Project Reporting Rule Setup read About Multi-Company Project Reporting.
Multi-Company Reporting Link Setup
When an employee reports time or cost to an employee company activity defined in this tab, the corresponding customer company activity (of the row which is set as default link for the employee activity) will be used to create the customer company transactions.
Multi-Company Project Reporting Rule Setup
When an employee reports time or cost by entering Customer Project Activity, validation against the Multi-Company Activity Rule Setup is done, and if a valid rule exists the data is fetched to the Employee fields and Time or Cost Registration can be done.
There are 4 types of scenarios that can be configured. For all scenarios, it is mandatory to provide all the information on the employee side.
Refer to the table below to see how you can configure rules connecting customer project activities to employee project activities.
| Customer | Employee | ||||||||
| Company | Project | Sub Project | Activity | Report Code | Company | Project | Sub Project | Activity | Report Code |
| P10 | P1 | % | % | % | P11 | P2 | S2 | A2 | T2 |
| P10 | P1 | S1 | % | % | P11 | P2 | S2 | A2 | T2 |
| P10 | P1 | S1 | A1 | % | P11 | P2 | S2 | A2 | T2 |
| P10 | P1 | S1 | A1 | T1 | P11 | P2 | S2 | A2 | T2 |
Recommendations
One to one mappings will not deliver the intended benefits because it can cause performance issues. The recommendation is to aggregate a set of customer project activities through the wildcard "%" option whenever possible.
Depending on the level where wildcard "%" is used, rules should not be modified when adding new sub projects to customer project, new activities to customer sub project or new report codes to customer activity.
Valid Report codes should have been added to the activities to be connected.
To use Multi-Company Project Reporting Rule Setup Page for Multi-Company Project Reporting the property ENABLE_MCPR_RULES need to be set to YES for the ProjectTransactionUtil object LU in the System Definitions/Object Properties.