@Roel van Zwieten , @Timmermans Roel fyi - this was fixed in 24.1.
Sounds similar to Synchronisation Service Notes from MWO to Cloud | IFS CommunityUnfortunately I don’t see a resolution to that post, but worth reaching out.
When I receive an update of my ticket from R&D, I will share here.
I have confirmed this behavior in 24.1E.0 and created a ticket for it.
What is the reason for inactivating resources? Is this only a temporary deactivation?
If you need more customers in MWO, I guess you canmake sure your customer record has the right attributes to be included in the standard WHERE clause modify the default SQL (which requires Build Place) or wait for the Include rules in 23.2+.
The work order is linked to a single sub project and activity. Tasks are indirectly linked through the work order. 1:n wouldn’t work since you want to allocate work order progress and cost to one project activity.
Apologies, I keep forgetting that you are on 23R1. Are you still not seeing serial objects, even if they are connected to one of your assigned task?For your Serial Objects, can you check if you have a party relationship of type “Customer”?
This is probably related to your equipment issue (I do see lots of customers). Looking at Sync Rules>Entity Details I see this WHERE clause:customer_category_db = 'CUSTOMER' AND customer_id IN (SELECT * FROM customer_info_usg) and customer_id IN ( SELECT customer_no AS customer_no FROM jt_task where task_seq in (select task_seq from mobile_work_order_uiv) UNION SELECT identity AS customer_no FROM EQUIPMENT_OBJECT_PARTY_UIV WHERE party_type_db = 'CUSTOMER' AND contract IN (SELECT contract FROM mobile_equipment_object_access WHERE userid = (SELECT fnd_user FROM fnd_session) ))Looks like you get customers associated to the equipment you see. You could add an “Include” filter to sync additional customers.
@courtney.engel there is also a section on Surveys in this document: IFS Cloud - MWO Service demystified (23R2) - revised version | IFS Community
Can you try to manually commit the activity in PSO? This should create an assignment in Cloud (no need to do anything in DC). If this doesn’t work, there likely is a problem with the messaging from PSO to Cloud, check the Audits and Events pages in PSO. If it does work, I would review the commit rules. My screenshots are from 23.2.3 and a PoC in which the above configuration commits 1,000s of activities every single day.
There are availabilities coming from the task’s earliest/latest start and SLA. On top of that there could be availabilities and availability patterns defined in various places:
Did you activate the SDS?If not - activate it- re-activate the dataset and send a full load, it should start committing today. P.S. As soon as this works for you, I will make sure I add these instructions to Scheduling Demystified 24R1…
What did the template pre-populate in Apps10? I assume this is different from work task templates?
@Alexander Heinze yes the service report created in MWO once a user has completed a Work Assignment Have a look at IFS Cloud - MWO Service demystified (23R2) - revised version | IFS Community, chapter “Modify the Service Report”
Unfortunately the screenshots neither show the added columns nor whether there are more columns available next to Resource ID. Tried again on 6.13.0.9 and it worked as expected.
Can you share a screenshot of your settings?
Are you referring to the server-side reports or the one created in MWO?
Hi Stefania, there is no need to use the Dispatch Console. You define Commit Rules in PSO (standard PSO capability)… ...and put them into a rule collection. These rules are part of the modelling dataset, hence in IFS Cloud you need to create a modelling dataset (ideally matching the name of your scheduling dataset) and the rule collection (same ID as in PSO). See Scheduling Demystified if needed.This will allow you to reference the ruleset on the individual resource or resource type:And finally the database task from your other post will send the assignments to MWO automatically.
Please try Mobile Work Order - Technical Documentation For IFS Cloud and IFS Cloud - MWO Service demystified (23R2) - revised version | IFS Community
Running out of ideas. @Uthpala any idea or should they open a ticket?
Based on your screenshots it looks like for MWO Service you changed sync from Group to Batch, what if you put that back?
What app are you using? You said you had to grant site access to IFSMAINTENGAPP, but the sync page shows the ServiceEngApp. Make sure you use make changes and also force sync for the right app.Does any of your assigned tasks have a serial object associated?
Here you go: For testing you can connect all sites. If you use multiple companies, look at this one as well:
23R1 still uses Grouped Push, so check out the link posted by Uthpala above. In addition the MWO document also includes a section “Grouped push delivery” worth checking out. If you don’t see any objects, one reason may be the the technical MWO users (IFSSERVICEENGAPP (for MWO Service) and IFSMAINTENGAPP (for MWO Maintenance)) don’t have access to the relevant sites.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
