Hi NPGIFSJOMAII,

Please see the attached test steps which are explained this functionality in the application.

Regards,

Thilina.

Hi @NPGIFSJOMAII ,

That is a good question, I also want to know this, I have some customers who work with different resources on a work task from different maintenance organisations. They are not in 23R1 yet, so no issue there. Do you know if this is also an issue with the time reporting?

@Thommy , Are you the correct person to ask this? Can you explain a bit more on this change in 23R1?

@TLAKLK , Changing the maintenance organisation on thework task will not solve the issue, then we need a work task per maintenance organisation and that is not what we want in this case.

Hi @NPGIFSJOMAII 

You can check the product documentation. (select the user>select the product documentation)

"The Resource needs to be connected to the Maintenance Organization or allowed in any Maintenance Organization on the Site (that is when Maintenance Organization is kept blank on the site record) in Resource Details\Maintenance/Service tab."

Therefore you can avoid this error by doing these steps also.

1. Go to the resource detail and add the site without the maintenance organization.
2. Create a work task and select the maintenance organization you want to connect with. You can add the resource without any errors. This is because the selected resource is not connected to any maintenance organization on the site.

Thanks and regards,
Thilina Lakshitha.

@EqeRobertK  We disconnected our resources from the organizations (kept field blank) as a quick fix for now. When it comes to time reportin later in the process, our not so happy user now manually has to select what organization they time report for. That field (organization) is mandatory to proceed with the time reporting.

I think you can also undo the “Apply Constraints” switch on the Assign Work screen, his will list all resources regardless of Maintenance Org.

Hi all,

Prior to 22R2 the Maintenance definitions were per Employee. With that set-up it was possible to define only one Site and Main.org definition per employee but with the provision to use the connected resources in Work Tasks without any validation on the Maint.Org and Site connected. 

 Continued in the next message…...

With the Secondment for Assets feature in 22R2 release, the Maintenance and Service Specific definitions were moved towards the Resource level.

With this feature the restriction of having an employee for time reporting was removed and time reporting was allowed for a Resource as well.

Further the set-up catered to definition of a seconded employee. For example if the employee is employed in Company A and has to perform work in Company B. Earlier a dummy employee should be created to cater this requirement. But now it can be catered by defining the Active Secondment Employee.

Continued….

About the question raised here. Yes there has been a change so that a user can be connected to one Maint.Org of a site or to Multiple Maint.orgs (keeping the Maint.Org. field blank) and validations are made depending on that when planning a resource.

Further when Time reporting user can specify the required Maint.Org and report time. We haven’t tried to autofill that with the Work Task Maintenance Organization, since it would be confusing in other reporting clients such Quick Report  and Tech Portals.

Hope this clarifies about the changes and appreciate your feedback.

CC : @Thommy 

Thanks & Best Regards

Eresha

Thanks for the background information @ereslk 

Hi @Thommy and @ereslk

Please clarify what consequences this will have on time reporting on work tasks when a person not connected to a Maint Org is reporting time.

1. What will be the source of time/hour cost if no cost is added to the persons resource group?
2. How are postings on time transactions affected when no cost center is added?
3. How is the impact that this newly introduced change is giving compared to previous “IFS-standard” on work task transactions and posting analysis?
4. Please also clarify the consequences this will have on pm actions and work task generation from pm actions in customer production environments installing 23R1

Best regards

Harald Eidem

This update is going to cause alot of problem in our organisations

Hi Harald,

Please refer my answers below:

1. Source of time/hour cost if no cost is added in resource groups?

Costs are fetched using following logic and has not been changed due to the resource setup changes.

• If Use Labor cost used, the the Hourly salary defined in HR is used.
• If Use Labour cost is unticked, and Resource Group exists when reporting time. Cost of Resource Group is fetched.
• If no Resource Group is defined, then the hourly rate defined on the Maintenance Organization is fetched.

2. Postings on time transactions when no cost center is added?

Do you mean the cost center defined in Pre-Postings for the Work Task?

1. Impact the change is giving on previous “IFS-standard” on work task transactions and posting analysis?

There has not been any change to the existing Posting set-up and transactions. But new transactions were introduced to cater the scenarios of Time Reports done from Employees from other companies than Work Task company and Resource time reporting. This information is mentioned in News PPT for 22R2 Release.

1. Consequences on pm actions and work task generation from pm actions in customer production environments installing 23R1

No impact on PM actions and WO generation.

Sorry for the separate replies. Its hard to post lengthy replies.

Get back if there are further concerns.

Best Regards