This appendix covers the following topics:
This section describes the profiles used to filter system items by category. The Item Category Filter and Item Category Set Filter profiles enable the reduction of system items downloaded to the mobile computer device.
The following system items are replicated to the mobile computer device:
Items used in a service request assigned to or created by the mobile user
Item instance items used in a service request assigned to or created by the mobile user
Items used in debrief lines
Items used in item orders
Items present in a good subinventory assigned to the mobile user
Items present in the inventory organization specified by the Service: Inventory Validation Organization profile
For Oracle Mobile Field Service Store and Forward - Laptop, set the following profiles to filter the system by category:
See "Setting Up Profile Options for Oracle Mobile Field Service Store and Forward Applications" for a complete description of these profiles.
For Oracle Mobile Field Service Store and Forward - Pocket PC, set the following profiles to filter the system by category:
See "Setting Up Profile Options for Oracle Mobile Field Service Store and Forward Applications" for a complete description of these profiles.
The two category profiles for the Oracle Mobile Field Service Store and Forward applications enable you to setup category sets (profile 1) and relate categories to this (profile 2). The category set and category profile make the unique key for replication. The values that can be selected for the category set profile are all categories sets of the master organization and the inventory organizations.
Note: You can set the category profiles for the Oracle Mobile Field Service applications at all levels.
The following are the rules governing the use of category profiles.
If the category profile is not set (no category is entered), then all items related to the default inventory organization are replicated to the mobile clients
If the category profile is set (category is entered), then the system items replicated are filtered based in inventory organization and category.
Items used in a service request created on the backend will not be impacted by this profile. But for service requests that the field service technician wants to create on a mobile computer device the category profile will limit the list of items available.
The category profile does not affect the OnHandQty (stock in subinventory).
If profiles CSL_ITEM_CATEGORY_SET_FILTER and CSL_ITEM_CATEGORY_FILTER are also both set, an additional filter on the item category/category set combination applies.
Items used in a field service report debrief are replicated as normal. This is independent of the category profile.
Complete the following steps to set up system items for install base transactions:
Log in to the Forms application using the responsibility Inventory.
Create a miscellaneous transaction, putting the item in a Subinventory.
Navigate to Setup > Organizations > Subinventories.
Create at least one subinventory in the Service Master Organization.
The subinventory should be a Quantity Tracked, Asset Subinventory.
Set the Locator Control value to None.
Create a subinventory in the inventory organization, which will be used as the good subinventory.
In the same organization as the subinventory of the mobile resource, create system items that are one of the following:
Transactable (Inventory tab page)
Trackable (Inventory tab page)
Serviceable (Service tab page)
Of type Material (Service tab page)
Put the trackable item you defined above in your good Subinventory (using Miscellaneous Transactions). Also put a non-trackable item there. The trackable item should be created as an install base product instance in the back end.
Under the responsibility Field Service Manager, navigate to Spares Management > Setup > Resource Addresses and Subinventories.
Create a new record for your mobile resource by entering its name. Assign a Primary Address and the two Subinventories you created to it.
The condition of the Subinventory in the Master Organization should be set to Defective and the condition of your Transaction Organization Subinventory should be set to Usable.
Set up profiles as indicated in the following table:
Adjusting transaction types so they can be used for install base updates can be done under the responsibility Installed Base Admin and navigating to Setups > Transaction Types and Sub Types. Transaction types can be used for removing install base products by setting the Change Owner To field in the Source Info section of the form to Internal. By setting this field to External, the transaction type can be used for installing new install base products.
Whether an install base update is done when removing a part in Oracle Mobile Field Service Store and Forward depends on the selected transaction type when doing a material transaction.
If the Change Owner To value of the selected transaction type is set to Internal, then the install base product to be removed can be indicated in Oracle Mobile Field Service Store and Forward.
If the Change Owner To value is set to External, than a trackable product can be indicated from a usable subinventory. An install base product will be created upon debriefing the material transaction in Field Service Debrief with the Update Installed Base check box selected.
To create an item order in an Oracle Mobile Field Service Store and Forward application, at least one usable (good) subinventory has to be defined and assigned to the field service technician. Two usable subinventories have to be defined and assigned to the field service technician to perform transfers.
Subinventories are set up using the Field Service Administrator responsibility and the Resource Addresses and Subinventories window. See the Oracle Field Service Implementation Guide for more details.