Oracle Shipping Execution Roles and Users Security.: An Oracle Distribution Topical Essay April 2001

Oracle Shipping Execution
Roles and Users Security.

An Oracle Distribution Topical Essay
April 2001.
Oracle Shipping Roles and Users
- TABLE OF CONTENTS -
1. SHIPPING EXECUTION ROLES AND USERS .................................................................................................................... 4

2. SETTING UP ROLES AND USERS ........................................................................................................................................ 4
2.1. NEW VS. UPGRADE CONSIDERATIONS ................................................................................................................................... 4
2.1.1. Upgrade Installation..................................................................................................................................................... 4
2.1.2. New Installation ............................................................................................................................................................ 4
2.2. DEFINING ROLES.................................................................................................................................................................... 5
2.2.1. Data Access................................................................................................................................................................... 5
2.2.2. Action Controls ............................................................................................................................................................. 5
2.2.3. Role definition samples ................................................................................................................................................. 6
2.2.3.1. Details for Trips. ....................................................................................................................................................................... 6
2.2.3.2. Details for Stops........................................................................................................................................................................ 7
2.2.3.3. Details for Deliveries. ............................................................................................................................................................... 8
2.2.3.4. Details for Lines and Containers. .............................................................................................................................................. 9
2.2.4. Creating a Role........................................................................................................................................................... 10

2.2.4.1. View of Trips tab .................................................................................................................................................................... 10
2.2.4.2. View of Stops tab .................................................................................................................................................................... 11
2.2.4.3. View of Deliveries tab............................................................................................................................................................. 12
2.2.4.4. View of Lines tab .................................................................................................................................................................... 13
2.3. GRANTING ROLES ................................................................................................................................................................ 14

2.3.1. Grant definition........................................................................................................................................................... 14
2.3.2. New users default....................................................................................................................................................... 15
2.3.3. Upgrade default .......................................................................................................................................................... 15
2.3.4. Start Date field............................................................................................................................................................ 15
2.3.5. End Date field ............................................................................................................................................................. 16
2.3.6. Single grant for all organizations ............................................................................................................................... 16
2.3.7. Single grant per organization ..................................................................................................................................... 16
2.3.8. Overlapping Grants .................................................................................................................................................... 16
2.3.8.1. Definition ................................................................................................................................................................................ 16
2.3.8.2. Positive example ..................................................................................................................................................................... 17
2.3.8.3. Negative example .................................................................................................................................................................... 17
2.3.8.4. Dealing with multiple effective grants .................................................................................................................................... 17
2.3.8.5. Avoiding multiple effective grants .......................................................................................................................................... 17
2.3.9. Multiple Shipping roles............................................................................................................................................... 18

2.4. UPDATING GRANTS & ROLES .............................................................................................................................................. 18
2.4.1. Grant Activity Date ..................................................................................................................................................... 19
2.4.2. Finding Grants............................................................................................................................................................ 19
2.4.3. Copying grants............................................................................................................................................................ 20
2.4.4. Finding Roles.............................................................................................................................................................. 20
2.4.4.1. Find ......................................................................................................................................................................................... 21
2.4.4.2. Find All ................................................................................................................................................................................... 21
2.4.5. Updating a user Role .................................................................................................................................................. 21

2.4.6. Copying Roles ............................................................................................................................................................. 21
3. USING ROLES AND USERS.................................................................................................................................................. 22
3.1. USER STATUS ....................................................................................................................................................................... 22
3.2. EXPIRED USERS.................................................................................................................................................................... 23
3.3. DISABLING SHIPPING SECURITY ........................................................................................................................................... 23

3.4. ACCESS TO SETUP MENU ...................................................................................................................................................... 23
4. GLOSSARY .............................................................................................................................................................................. 24
5. APPENDIX ............................................................................................................................................................................... 25
5.1. TEMPLATE FOR TRIPS DEFINITION ....................................................................................................................................... 25
5.2. TEMPLATE FOR STOPS DEFINITION ...................................................................................................................................... 26
5.3. TEMPLATE FOR DELIVERIES DEFINITION .............................................................................................................................. 27
5.4. TEMPLATE FOR LINES & CONTAINERS DEFINITION .............................................................................................................. 28
1.
Shipping Execution Roles and Users
Roles and Users is a set of security features released in Shipping Execution 11i patch set E to secure the
graphic user interface with fine granularity centered around Shipping user roles.
Prior to release 11I patch set E security was limited to the menu level by which user gained access to a screen.
Since 11i the Shipping Transactions form integrates all Shipping functionality across organizations from a
single menu entry. In some cases, the standard security was no longer be suitable. Roles and Users fills this gap.
By implementing Roles and Users, system administrators can control individual user actions and data entity
access for each Shipping form.
2.
Setting up Roles and Users

2.1. New vs. Upgrade Considerations
The security defaults differently on New and Upgraded installations.
2.1.1. Upgrade Installation
This is the most common situation. A customer is upgrading from a version of Oracle Applications
prior 11i4 and is installing Oracle Shipping 11i4 or later.
In this case all existing Application users are automatically granted full privileges. The security is
therefore transparent to upgraded users.
However new shipping users created after the Application upgrade are granted a view-only restrictive
access.
2.1.2. New Installation

A new installation is when a customer is bringing up of Oracle Shipping Application with no preexisting users.
In this case all Application users are new and are therefore automatically granted a minimal viewonly access.
To gain adequate access, a system administrator should assign users to their matching shipping tasks as
defined by a system role. Individual Shipping privileges will remain restricted until users are
granted a role.
To prevent users not involved with Shipping from gaining the default view-only access, simply remove
the Shipping Execution option from the list of system menu.
The first Roles and Users release does not support changing the View-Only or other default privileges.
To track this enhancement see #1524408.
2.2. Defining Roles

Shipping managers or System administrators can provide access to specific Shipping functions by modeling
user responsibilities and creating Shipping Roles.
Each Role is defined as a combination of Data access type and Action list options.
2.2.1. Data Access
Three levels of data access are provided for Trips, Stops, Deliveries, and Lines:
1. Edit: no data restriction to query, edit or save data.
2. View: Query and browse are allowed but data can not be committed. (See note)
3. None: no data access. Provides the highest security. This option may be used to streamline menus.
Note: In a View-Only mode users can not save entries or changes. However in this case Action
processing expectedly does still alter data. To prevent unwanted data changes purposefully edit
the list of Actions.
2.2.2. Action Controls

There are over 60 actions defined for Trips, Stops, Deliveries and Lines.
Actions Controls either enable or disable the Transactions Forms Action poplist and Tools menu bar option.
Disabling access to the Pick Release action prevents access from both the Transactions form and from the
Tools menu bar.
Disabling actions can be used to stream line the shipping options by reducing irrelevant user options.
(See screen captures under section Creating a Role)
2.2.3. Role definition samples

This section is a sample of five generic shipping roles:
1.
2.
3.
4.
5.
Transportation Manager
Shipping Manager
Shipping Sup. w/ Picking
Shipping clerk w/o Picking
Customer service Rep.
Abbreviation at entity level: E : Full Edits; V : View only limited; D : Disabled

Abbreviation at action level: E : Enabled; D : Disabled
2.2.3.1.Details for Trips.
Roles
Role # > 1
Shipping Manager
Shipping Supervisor
Shipping clerk
Customer service
Pre-upgrade users
New users
Default values for custom created roles
Any expired grant
Trips
E Full Edits
|
Shipping Manager
V View-only
|
|
D Disabled
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All Pre-upgrade users
|
|
|
|
|
|
Any New users
|
|
|
|
|
|
|
Custom default
|
|
|
|
|
|
|
|
Expired
|
|
|
|
|
|
|
|
|
Entity Level > E
E
E
E
E
E
E
E
E
D
D
E
E
D
E
E
E
D
D
E
E
D
E
D
E
D
D
E
D
D
E
D
D
D
D
D
D
D
D
D
D
E
E
E
E
E
E
E
E
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
Plan
Unplan
Freight Costs
Launch Pick Release
Print Document Set
Calculate Weight/Volume
Resolve Exceptions form
Pick Release Form
E=Enable /D=Disable
2.2.3.2.Details for Stops.

Roles
Role # > 1
Shipping Manager
Shipping Supervisor
Shipping clerk
Customer service
Pre-upgrade users
New users
Any expired grant
Stops
E Full Edits
|
Shipping Manager
V View-only
|
|
D Disabled
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Any New users
|
|
|
|
|
|
|
Custom default
|
|
|
|
|
|
|
|
Expired
|
|
|
|
|
|
|
|
|
Entity Level > E
E
E
E
E
E
E
E
E
E
D
D
E
E
E
D
E
E
E
D
D
E
E
E
D
E
E
E
D
D
E
E
D
D
D
D
D
D
D
D
D
D
D
D
D
D
E
E
E
E
E
E
E
E
E
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
Plan
Unplan
Freight Costs
Launch Pick Release
Print Document Set
Pick Release form
Update Status
E=Enable /D=Disable
2.2.3.3.Details for Deliveries.

Roles
Role # > 1
Shipping Manager
Shipping Supervisor
Shipping clerk
Customer service
Pre-upgrade users
New users
Any expired grant
Deliveries
E Full Edits
|
Shipping Manager
V View-only
|
|
D Disabled
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Any New users
|
|
|
|
|
|
|
Custom default
|
|
|
|
|
|
|
|
Expired
|
|
|
|
|
|
|
|
|
Entity Level > E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
D
D
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
D
D
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
D
D
E
D
E
E
E
E
D
E
E
E
E
D
E
E
E
D
E
D
D
E
E
D
D
D
D
D
D
D
D
D
D
D
D
E
D
D
D
D
D
D
D
D
D
D
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
Plan
Unplan
Freight Costs
Launch Pick Release
Auto-pack
Auto-pack Master
Pack
Generate Loading Sequ.
UPS Rate and Service
UPS Time in Transit
UPS Address Validation
Print Document Set
Assign to Trip
Unassign from Trip
Auto-create Trip
Ship Confirm
Re-open
Close
Pick Release Form
Resolve Exceptions Form
Generate BOL
Generate Packing Slip
E=Enable /D=Disable
2.2.3.4.Details for Lines and Containers.

Roles
Role # > 1
Shipping Manager
Shipping Supervisor
Shipping clerk
Customer service
Pre-upgrade users
New users
Any expired grant
Lines
&Containers
E Full Edits
|
Shipping Manager
V View-only
|
|
D Disabled
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Any New users
|
|
|
|
|
|
|
Custom default
|
|
|
|
|
|
|
|
Expired
|
|
|
|
|
|
|
|
|
Entity Level > E
Freight Costs
Launch Pick Release
Split Line
Auto-create Deliveries
Assign to Delivery
Unassign from Delivery
Auto-create Trip
Auto-pack
Auto-pack Master
Create Containers
Pack
Unpack
Packing Workbench

UPS Tracking
UPS Time in Transit
Pick Release Form
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
D
D
D
D
D
D
E
E
E
E
E
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
Packing Calculator
E=Enable /D=Disable
Blank Role definition templates are available in the Appendix section.
2.2.4. Creating a Role

Creating a Shipping user role involves either copying an existing role or alternatively creating one from the
ground up.
To copy an existing role please refer to that specific section. Saved roles can not be altered. Therefore existing
roles can only be copied and saved with a new name before being assigned.
Note: Disabling the Pick Release action expectedly prevents access from both the Transactions form and from
the Tools menu bar.
2.2.4.1.View of Trips tab
10
2.2.4.2.View of Stops tab
11
2.2.4.3.View of Deliveries tab
12
2.2.4.4.View of Lines tab
13
2.3.
Granting Roles
2.3.1. Grant definition
A Shipping Grant is as set of user access and action privileges defined by the combination of a shipping role, a
system user, a warehouse organization and an effective date range. Basically a Grant is the connection
between a system Role and a User.
Shipping access privileges are granted to users by assigning a shipping Role to a system User effective from a
Start Date until an optional End Date within an optional Organization.
To navigate to the grant management set of screens: Shipping > Setup > Grants and Roles Definitions >
Grants. Two buttons are provided on the Grant form to conveniently View or Define roles.
When multiple grants are used for a particular user, the resulting grant is the union of all other active grants.
Consequently, you should consider with caution granting a user with multiple overlapping grants.
The resulting union of grants is a access to the most organization and most warehouses with the highest
access.
Single organization grant: The resulting union of effective grants in one organization is an access to
one organization with the highest access.
Multiple organization grant: If at least one of the effective grants allows access to all organizations,
the resulting union will give access to all organizations with the highest access.
Further grants details are covered in the forth coming sections.
14
2.3.2. New users default

By default a new user with no existing grant is safely limited to a View-Only role until a grant is defined and
assigned.
2.3.3. Upgrade default

Existing users upgraded to 11i4 are granted a full access privilege so that upgrading the Shipping Application
does not lock users out of the forms. In that instance new users added after the upgrade are granted a default
view-only access.
2.3.4. Start Date field

The Start Date field can be used to activate a grant either on todays date or on a latter date. So Grants may be
created ahead of time for employees coming on board or Grants can be created the first day of employment.
15
2.3.5. End Date field

Employment at will:
To create an open ended grant, leave the end date value blank.
Last day of employment:
To terminate a users grant enter a present or future end date.
Employment extension:
Grants with future end dates can be updated even after being saved. A future end date can be changed.
Employment history:
Expired grants can not be altered. Passed end dates freeze grants into view-only history records.
2.3.6. Single grant for all organizations

The warehouse value is optional. A blank warehouse value effectively grants a user the same role across all
organization. This type of grant should be used when only one grant is in use. You could use this type of grant
to bypass all security (Grant a super user role to all warehouses.)
Use caution when granting roles for all warehouse organizations to prevent overlapping grants.
2.3.7. Single grant per organization

Generally a user should only have a single active grant per warehouse or the least amount practical. Roles and
Users gives you the ability to grant precisely the privileges required. Try to define roles that match well users
responsibilities so no duplicate grants need to be assigned. If a user responsibilities are across two existing
roles, you should create an new more appropriate role with all particular job attributes. Then create a grant
definition based on that role.
2.3.8. Overlapping Grants

2.3.8.1.Definition
Users can also be granted overlapping roles across warehouses or within the same organizations. The union of
overlapping active role privileges in a warehouse controls the users data access and actions. Administrators
should be cautious when creating overlapping grants.
The resulting user grant being the union of all user active grants, user may get more access than originally
intended.
16
2.3.8.2.Positive example
This example is an illustration of how all-organization overlapping grants can benefit grant management at
times:
Grant 1 - John has been a Picker in M1 organizations since January until an open end date.
Grant 2 - John will be the Picking Supervisor in M1 and V1 from April 1st until April 14th
- In this example, John is normally a Picker in the M1 warehouse. Johns boss is taking time off, so John will be
the acting Picking Supervisor for two weeks for both M1 and V1 organizations.
- Due grant 1 and grant 2 overlap, John will also be a Picker in V1 for two weeks. However this is really a
minor issue because John will already be granted Picking privileges through the temporary Picking Supervisor
grant. (Assuming Picking Supervisor can Pick as well)
2.3.8.3.Negative example
This example is an illustration of draw back condition with overlapping grants across all-organization:
grant 1 - Joe is the Shipping Manager in M1 from August 1st to August 31st.
grant 2 - Joe is the Shipping Supervisor in M1 from January to open end date
grant 3 - Joe is a Picker in all Orgs at all times (blank warehouse & end date)
In this example, because of grant 3, Joe has access to all organizations for picking at all times and will enjoys
the supervisor's privileges for all organizations starting in January. For one month of August, he gets the
manager's privileges in all organizations.
2.3.8.4.Dealing with multiple effective grants

You can limit or eliminate overlapping grants by following these guidelines:
Non warehouse specific overlapping grant - Fragment the grant that is not warehouse specific to
limit the problem to one warehouse overlap only.
Warehouse specific overlapping grant - Merge roles used in the overlapping warehouse. Create a
single role more appropriate than the default union of both grant roles.
2.3.8.5.Avoiding multiple effective grants
Rather than dealing with multiple active grants here is how you can prevent that condition:
Keep the number of active grants minimal by creating many tailored roles.
When creating new grants deactivate some existing ones to prevent grant overlap
Grant multiple warehouses only when a single user grant exist.
17
2.3.9. Multiple Shipping roles

A user can simultaneously have many grants for multiple warehouses to reflect distinct privileges. The grants
referred to here are not overlapping. This is a preferred method of using multiple grants.
Example:
grant 1 - Joe Shipping Manager in M1 since May 15th.
grant 2 - Joe Shipping Supervisor in M3 since January 1st.
The resulting grant privilege is exactly as defined by the two grants. The grant union being empty there is no
overlapping condition.
2.4.
Updating Grants & Roles
18
Grant edits are limited to End date forward or backward selection. Typically only Oracle System
Administrators responsibility can manage grants. Dates can only be defined in a new grant based on the
superseded one.
Role edits are not allowed directly. Once committed a role definition is final. Roles defined in the system can
not be deleted or modified, view-only mode. To enter role changes use the copy method to create a new role
then define a new grant using the new role.
We recommend to define roles carefully since error correction can be time consuming. To enter changes you
will have to first create a new role then second create all new grants based on that role.
2.4.1. Grant Activity Date

Grants validity dates can only be extended or shortened until the grant End Date is passed. After the last hour
of the end date the grant expires. Once expired a grant is no longer editable. Expectedly a user assigned to an
expired grant loses the associated warehouse access.
To extend a temporary shipping worker, you should edit the end date of the current grant before expiration.
Post expiration you need to define a new grant by copying the expired one. Refer to editing grants.
2.4.2. Finding Grants

Grants are found rapidly with details using the Find Grant form. This enhanced form is accessed by opening
the View Find or menu bar Flashlight icon. It provides extras fields not available on the main grant form
(Effectivity and Organization span) Additionally you may also use the standard methods Query by Example or
Find All methods instead.
Steps to find a grant:
Open the grant form by navigating to Shipping >Setups >Grants and Roles >Grants.
Open the Find Grants form by navigating to View >Find or clicking on the flashlight icon.
Enter specific filter information in the form. (See screen capture)
Select the Find button to launch the search
Matching grants are displayed directly in the Shipping Execution Grant form
Close the Find Grant form
19
2.4.3. Copying grants

The following fields can not be edited for an existing grant: User name, Role, Warehouse organization.
Consequently to update a grant you should copy a current grant or copy a close match of the target grant.
Steps to copy a grant:
Open the grant form by navigating to Shipping >Setups > Grants and Roles > Grants.
Find a matching grant (see Finding Grants)
Highlight your grant selection
Insert a new blank grant record by navigating to File > New
Copy the grant record above by navigating to: Edit > Duplicate > Record Above. - This should
have copied the source grant we initially picked.
Change the grant definition at once to define the new access. Be sure all changes are final before
saving the new record. Grants entered in the system can not be edited.
Finally once all changes are final, commit the record.
2.4.4. Finding Roles

The number of existing roles on the system grows rapidly. Searching for roles efficiently can be time saving.
There are currently two ways to find roles. Select a method according to your preferences: speed vs. details see
pros and cons.
The find methods are presented from fast to detailed.
20
2.4.4.1.Find
Provides rapid access to role based on a limited criteria.
Enter the Role screen
Select the task bar Flashlight or navigate to the menu: View > Find.
Make a selection using either Name or Description fields.
2.4.4.2.Find All
Provides a rapid way to review all roles in details.
Enter the Role screen
Select the Find All option under menu View.
Use the keyboard arrow keys to scroll through all existing roles.
Clicking on a tab for more details will select the role and end the current search.
2.4.5. Updating a user Role

Roles can not be directly edited. Instead you can edit a copy of an existing role. If the role you need to assign
does not already exist in the system, you can create a new one from the ground up. Refer to chapter on Role
creation. The easiest method is to copy a near matching role.
Logically once the new role is created you will want assign it to users. To start using a new role define a new
user grant. Role definition for existing Grants is a read only field.
2.4.6. Copying Roles

For security purposes, saved system roles can not be edited. Consequently to update a user role you should
copy the existing role to create a new one:
Finding and selecting a matching role will populate the role form in view only mode.
Select menu or task bar option: File >New - This will insert a new role record.
Select menu option Edit > Duplicate record above from the Shipping Execution Role definition
- This will copy the source role we initially picked. (See screen capture below)
Change all responsibilities settings at once to define the new job description. Be sure all changes
are final before saving the new record. Roles entered in the system can not be edited.
Enter a distinctive value in the role Name field within the Shipping Execution Role Definition
Select Save from the menu to save the new role.
Grant the new role to one or many users. See section on Granting Roles.
21
3.
Using Roles and Users
Implementing this design controls users access only to the options consistent with their tasks defined by roles.
This in turn secures Shipping data by selectively hiding or displaying view-only or in full edit mode. The
Shipping Transactions form navigation menus entries can be restricted to options defined for individual user
role.
3.1. User status
User access falls within on of these different Roles and Users statuses:
Pre-Upgrade users: retain unrestricted access to Shipping Execution

New users: have a default view-only browsing privilege with not actions enabled.
Active users: transactions are controlled by a role definition activated by a grant.
22
Expired users: are denied access to the specific Shipping warehouse and are limited to any of their
grant remaining active if any.
Future users: are notified and denied access.
3.2. Expired users

The Shipping Roles and Users design has no direct security impact outside Shipping Execution. So a user with
all expired Shipping privileges is not prevented from accessing any other Oracle Application responsibilities.
General access is remains managed at the System Administration level not at Shipping fine grain security level.
3.3. Disabling Shipping Security

In the unlikely event you want to disable the Roles and Users security on an existing instance:
1. Create a super user role with all actions enabled in Edit mode
2. Grant all users that super user role.
3.4. Access to setup menu

The Roles and Users setup administration menu should be made available only to Shipping administrators or
System Administrators.
Shipping Super Users managing employees access to Shipping should have the Roles and Users Setup option
part of their system profile under Shipping Execution. Clearly other system users should not.
23
4.
Glossary
Shipping Role:
- Shipping duties defined by an Action access list and Data access to model a user Shipping Execution
privileges.
Shipping Grant:
- User access and actions privilege defined by the combination of a shipping role, a system user, an
organization and an effective date range.
Privileges:
- A set of Shipping functions a user can perform as part of his work responsibilities.
Entities:
- Oracle Shipping entities are defined as Trips, Stops, Deliveries and Lines/Containers.
Edit/View/None:
- Data access control options used in combination with Actions to help define a user role.
24
5.
Appendix
Use the following role templates to help define customized roles in the course of implementation.
5.1.
Roles
Template for Trips Definition

Role # > 1
12345-
Role:
E Full Edits
V View-only
D Disabled
Role:
Role:
Role:
Pre-upgrade users
New users
Any expired grant
Trips
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Role:
|
|
|
|
|
|

|
Any New users
|
|
Custom default
|
|
|
Expired
|
|
|
|
Entity Level >
Plan
Unplan
Freight Costs
Launch Pick Release
Print Document Set
Calculate Weight/Vol
Pick Release Form
E=Enable /D=Disable
E
E
E
E
E
E
E
E
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
D
D
D
D
D
D
D
D
25
5.2.
Roles
Template for Stops Definition

Role # > 1
12345-
Role:
E Full Edits
V View-only
D Disabled
Role:
Role:
Role:
Pre-upgrade users
New users
Any expired grant
Stops
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Role:
|
|
|
|
|
|

|
Any New users
|
|
Custom default
|
|
|
Expired
|
|
|
|
Entity Level >
Plan
Unplan
Freight Costs
Launch Pick Release
Print Document Set
Pick Release Form
Update Status
E=Enable /D=Disable
E
E
E
E
E
E
E
E
E
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
D
D
D
D
D
D
D
D
D
26
5.3.
Roles
Template for Deliveries Definition

Role # > 1
12345-
Role:
E Full Edits
V View-only
D Disabled
Role:
Role:
Role:
Pre-upgrade users
New users
Any expired grant
Deliveries
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Role:
|
|
|
|
|
|

|
Any New users
|
|
Custom default
|
|
|
Expired
|
|
|
|
Entity Level >
Plan
Unplan
Freight Costs
Launch Pick Release
Auto-pack
Auto-pack Master
Pack
Generate Loading Sequ.
UPS Time in Transit
Print Document Set
Assign to Trip
Unassign from Trip
Auto-create Trip
Ship Confirm
Re-open
Close
Pick Release Form
Generate BOL
Generate Packing Slip
E=Enable /D=Disable
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
E
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
27
5.4.
Template for Lines & Containers Definition
Roles
Role # > 1
12345-
Role:
E Full Edits
V View-only
D Disabled
Role:
Role:
Role:
Pre-upgrade users
New users
Any expired grant
Lines
&Containers
Entity Level >
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Role:
|
|
|
|
|
|

|
Any New users
|
|
Custom default
|
|
|
Expired
|
|
|
|
E
Freight Costs
Launch Pick Release
Split Line
Auto-create Deliveries
Assign to Delivery
Unassign from Delivery
Auto-create Trip
Auto-pack
Auto-pack Master
Create Containers
Pack
Unpack
Packing Workbench
UPS Tracking
UPS Time in Transit
Pick Release Form
Packing Calculator
E=Enable /D=Disable
April 03 2001
28
Using Shipping Documents in Oracle Shipping Execution

November 2000
Author: Guy Lasseron
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
Web: www.oracle.com
This document is provided for informational purposes
only and the information herein is subject to change
without notice. Please report any errors herein to
Oracle Corporation. Oracle Corporation does not
provide any warranties covering and specifically
disclaims any liability in connection with this document.
Oracle is a registered trademark, and Oracle Shipping Execution is a
trademark(s) or registered trademark(s) of Oracle corporation.
All other names may be trademarks of their respective owners.
Copyright Oracle Corporation 2000
All Rights Reserved
29

Oracle Shipping Execution Roles and Users Security.: An Oracle Distribution Topical Essay April 2001

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Shipping Execution Roles and Users Security.: An Oracle Distribution Topical Essay April 2001

Uploaded by

Copyright:

Available Formats

Oracle Shipping Execution

Roles and Users Security.

Oracle Shipping Roles and Users

1. SHIPPING EXECUTION ROLES AND USERS .................................................................................................................... 4

2.2.4. Creating a Role........................................................................................................................................................... 10

2.3. GRANTING ROLES ................................................................................................................................................................ 14

2.3.9. Multiple Shipping roles............................................................................................................................................... 18

2.4.5. Updating a user Role .................................................................................................................................................. 21

Oracle Shipping Roles and Users

Oracle Shipping Roles and Users

Shipping Execution Roles and Users

Setting up Roles and Users

2.1.2. New Installation

Oracle Shipping Roles and Users

2.2. Defining Roles

2.2.2. Action Controls

Oracle Shipping Roles and Users

2.2.3. Role definition samples

Abbreviation at entity level: E : Full Edits; V : View only limited; D : Disabled

Entity Level > E

Oracle Shipping Roles and Users

2.2.3.2.Details for Stops.

Entity Level > E

Oracle Shipping Roles and Users

2.2.3.3.Details for Deliveries.

Entity Level > E

Oracle Shipping Roles and Users

2.2.3.4.Details for Lines and Containers.

Entity Level > E

Launch Pick Release

Unassign from Delivery

UPS Rate and Service

Resolve Exceptions Form

Blank Role definition templates are available in the Appendix section.

Oracle Shipping Roles and Users

2.2.4. Creating a Role

Oracle Shipping Roles and Users

2.2.4.2.View of Stops tab

Oracle Shipping Roles and Users

2.2.4.3.View of Deliveries tab

Oracle Shipping Roles and Users

2.2.4.4.View of Lines tab

Oracle Shipping Roles and Users

Further grants details are covered in the forth coming sections.

Oracle Shipping Roles and Users

2.3.2. New users default

2.3.3. Upgrade default

2.3.4. Start Date field

Oracle Shipping Roles and Users

2.3.5. End Date field

2.3.6. Single grant for all organizations

2.3.7. Single grant per organization

2.3.8. Overlapping Grants

Oracle Shipping Roles and Users

2.3.8.4.Dealing with multiple effective grants

Oracle Shipping Roles and Users

2.3.9. Multiple Shipping roles

grant 1 - Joe Shipping Manager in M1 since May 15th.

grant 2 - Joe Shipping Supervisor in M3 since January 1st.

Updating Grants & Roles

Oracle Shipping Roles and Users

2.4.1. Grant Activity Date

2.4.2. Finding Grants