This chapter covers the following topics:
You set up Responsibilities and Menus for Mobile Supply Chain Applications the same way as you set them for other Oracle Applications. There are four seeded mobile UI menus applicable to Mobile Supply Chain Applications. You can use these menu entries as seeded and assign them to individual users or you can modify them to include or exclude specific transactions for specific users.
The following responsibilities are seeded by default and are available for immediate use:
Materials Management-This responsibility contains all the mobile transactions for processing material within Oracle Inventory. It provides transactions such as miscellaneous receipt, transact move order, and ship confirm.
Mobile Quality User -This responsibility contains the mobile user interfaces for Oracle Quality transactions. It supports transactions for entering and viewing quality collection plans.
Manufacturing Mobile Apps -This responsibility contains the mobile user interface for Oracle Manufacturing (WIP) transactions. It provides transactions such as component issues, assembly completions and job inquiries.
Materials & Mfg-This is the super user responsibility for Oracle Mobile Supply Chain Applications. It contains all the transactions from both the Materials Management and Manufacturing Mobile Apps responsibilities. It is essentially the superset of menu options for Receiving, Inventory, Manufacturing, Picking, and Shipping.
MWA Administrator- This responsibility contains two menu entries that can be used on the mobile device for Administrator purposes:
Telnet Session Monitor allows you to monitor the session of another mobile user. This is useful for training and demonstration purposes. This functionality is often called mirroring. Both users must be on the same MWA server. For example if the dispatcher is being used, both users must have been routed to the same actual MWA server.
Send Message allows you to send a brief text message to another mobile user. The recipient receives the message when he/she presses the next key on the mobile device. This does not disrupt the ability to process transactions. For this functionality to work, both users must be on the same MWA server.
Related Topics
Defining a Responsibility: Oracle Applications System Administrator's Guide
Windows and Navigator Paths Oracle Mobile Supply Chain Applications User's Guide