This section explains how to set up Inventory and Purchase Parts in IFS Cloud Web and the associated processes available in back office to ensure mobile users have access to the appropriate inventory and purchase parts in mobile.
The IFS system can have many parts registered in different sites, locations, and warehouses. The availability of these parts for each mobile user can vary and change over time.
Assortments and user connected warehouses are used to limit the parts available to a mobile user. This also ensures that these parts are synchronized to mobile users’ devices and available for various material-related actions.
Assortments valid for a mobile user are defined on the Mobile User Assortments page, located under Mobile Maintenance/ Basic Data/ Mobile Part Basic Data in IFS Cloud Web.
To view parts available to a mobile user, use the following pages in IFS Cloud:
Note: In IFS Cloud, assortments are defined on the Part Master Data/Assortment page. Use the Part Operations/Connect Parts command to connect parts to an assortment.
IFS application synchronizes Inventory Parts and Purchase Parts to the mobile app using batch synchronization. When the following scheduled tasks are run, the system collects the parts valid for mobile users into intermediate tables, and then it is used to filter data synchronized to the mobile app.
An administrator can set up these scheduled tasks to run at regular intervals
based on how frequently these entities change. It is recommended to configure
the scheduled tasks to run at a time that does not affect the system during
normal operating hours. If not, it can adversely affect system performance.
The Refresh All Inventory Parts scheduled task includes the Part Site ( i.e.
Contract ) as a parameter. This allows the task to be scheduled at different
times for different time zones or to be split into multiple tasks.
The
Contract parameter supports single values , multiple values,
NULL and '%'. Both NULL and '%' parameter values are treated the same
way and include all sites.
Note: See Note 1 and Note 2 for more information.
The scheduled task updates the mobile_user_invent_part table with valid inventory parts for each mobile user.
The following inventory parts in sites connected to the mobile user are added to this intermediate table.
The system updates the intermediate table (mobile_user_invent_part_tab) whenever changes related to work execution occur. For example, when a new task is assigned to a mobile user with a demand for an inventory part, the system updates the table with the new inventory part. This ensures that the table contains up-to-date part information relevant to the mobile user.
Therefore, when setting the frequency of the scheduled task, mobile users only need to consider the following changes. The table updates automatically in all other instances, so, there is no need to run the scheduled job frequently.
The following workflows use the Inventory Parts synchronized to the mobile.
The scheduled task updates the mobile_user_purch_part table with valid purchase parts for each mobile user. The intermediate table is updated with the following purchase parts from sites connected to the mobile user:
The system updates the intermediate table (mobile_user_purch_part_tab) as changes related to work execution occur.
Therefore, when setting the frequency of the scheduled task, you need to consider only the following changes. The table updates automatically in all other instances, so, there is no need to run the scheduled job frequently.
The following workflows use the Purchase Parts synchronized to the mobile.