Warehouse Management System Tools

7/29/2019 Warehouse Management System Tools

1/48

Data Driven Applications Overview

A data driven application (DDA) is a RedPrairie product application that is created for the client and/or Web frameworkusing DDA technology provided in the shared application library (SAL) that is distributed with RedPrairie standard product

a separate development environment is not required. DDA technology lets you define queries and maintenanceapplications, and perform actions on the data that is retrieved using Controller commands and data configurations.

DDA technology lets project teams and customers use pre-defined data to dynamically draw the user interface elementsand manage various types of applications. This can reduce project costs and the turnaround time required for the

development of custom applications.

What do you want to learn about?

DDA Functionality

Types of DDAs

DDA Modality

DDA Parent/Child Relationships

Customization Levels

DDA Toolbar

DDA Development Process

DDA Functionality

These are the features that DDAs support:

Action buttons on child DDAs and in the toolbar

Appearance of DDAs matches the RedPrairie standard

Command button execution of commands

Context data is persisted between queries

Data can be refreshed

Dynamic queries with or without input data

Filter groups (tabs and group boxes) for organizing submit and display fields

Graphing support

Grid or graph location is selectable

Maintenance functions (such as using a DDA to add, change or remove data rows)

Multiple row display operations

Parent/child associations between DDAs

2011 RedPrairie Corporation

Comments on this topic?

Page 1 of 48Data Driven Applications Overview

7/14/2011file://C:\Temp\~hh80D.htm


2/48

Data related to the top-level (parent) DDA is displayed on the same screen as the parent and can be maintainedwithout having to drill down on a field in the parent

Parent submit fields displayed on tabs when filter groups or child DDAs exist

Sub-queries based on field-level data

DDA Types

Each DDA is associated with a DDA type, which defines the type of service that the application will perform.

These are the types of DDAs that can be defined:

Action

Bar Chart

Cascading

Dynamic DDA

Filter

Lookup

Maintenance

Mnt Change

Mnt Create

Mnt Remove

Pie Chart

Query

Raw Query

Single Row Select

XML Tree








3/48

DDA Modality

Modality defines how the DDA is displayed within the client or Web framework . These are the types of modality that can beapplied to a DDA:

None

Modeless

Modeless with Refresh

Modal

Modal with Refresh

If a DDA is invoked from a menu, it is always executed as Modeless with Refresh, and any other modality defined for the

DDA is ignored.

If a DDA is modal, and it has a action button on it that calls a modeless form, the second form takes over the display of the

first form in the same modal form.

You use the Target New Window attribute on the Data Driven Application Maintenance window to define modality for aDDA.

DDA Parent/Child Relationships

You can define a parent/child relationship between DDAs; however, the functionality for establishing parent/childrelationships is only available for these DDA types: Maintenance, Query and Single Row Select.

A parent/child relationship is typically used to support actions (such add, modify or delete) on the data retrieved by the

parent. The parent is the DDA that provides access to the child DDA . A child DDA, which can also contain action buttons, isdisplayed on a tab on the parent DDA.

This is the order in which the system adds child DDA tabs to the parent DDA:

Submit fields for the parent are painted on the first tab

If tab-type filter groups have been defined for the parent, then those are drawn on the next tab(s)

Child grids (with or without action buttons) are painted on subsequent tabs, the order of which is determined by the

order in which they appear in the Children list on the Parent/Child window, or the Parent/Child tab of the Data DrivenApplication Maintenance window.

When you specify a parent/child association for a DDA, you define the






4/48

fields on the parent DDA that you want to pass to the child DDA, and

fields not on the parent DDA that you want to pass to the child DDA.

Customization Levels

Each data driven application (DDA) is associated with a customization level (defined by the Customization Level attribute).

The value for this attribute determines the level of the data that should be used from the database. Data that is distributed

with the RedPrairie standard product is distributed with a customization level of 0.

When you create a DDA in your RedPrairie product instance, it is automatically assigned an incremented customization

level; usually incremented by 10. When the MCS framework is determining which database entry to use, it uses thecustomization level as one of the determining factors. Entries with a higher customization level take precedence over those

with a lower customization level.

The customization level is also used to preserve the customizations when the product instance is upgraded or enhanced.For example, during a product installation or upgrade, safetoload data is data that can be loaded at any time and it will not

overwrite data that may have been added since the last time it was loaded. The data is made safe by a customization level(cust_lvl) column that is part of the primary key on the table.

Bootstraponly data is data that will generally be customized by an implementation team. As a result, bootstraponly data isonly loaded when the system is initially installed. This data is never loaded again as part of an upgrade, so as to prevent

the changes made by the implementation team or the customer from being overwritten. This data includes, for example,policies, optional areas and menu groups.

DDA Toolbar

The toolbar that appears on the Data Driven Application Maintenance window provides quick access to standard commands

such as Exit, New, and Save, and includes additional functions for working with the development of DDAs.

This table lists the standard and DDA-specific controls that appear on the Data Driven Application Maintenance windowtoolbar, and the action that takes place when you click the control.








5/48

DDA Development Process

These are the steps that you will take to develop a DDA:

1. Determine the goal of the DDA. For information, see DDA Types.

2. Determine what child and action DDAs will be needed. For information, see DDA Parent/Child Relationships.

3. Determine what filter groups (tabs and group boxes) will be needed, and create them for each DDA. For

information, see Maintain DDA Filter Groups .

4. Use the DDA creation wizard to create all of the necessary action and child DDAs, and authorize roles and users to

access them. For information, see Add a DDA Using the Wizard .

5. Use the DDA creation wizard to create the parent DDAs , authorize roles and users to access them, and assign theparent DDAs to menu groups.

6. If you created filter groups (tabs and group boxes), then assign display and submit fields to filter groups. For

information, see Modify the Submit Fields on a DDA or Modify the Display Fields on a DDA .

Control Action

Exits the current application.

Creates a new record.

Saves your work.

Lets you delete the current record.

Clears all of the information that was entered in the application.

Note: Does not clear default information.

Retrieves information from the database.

Displays the previous record.

Displays the next record.

Shows or hides the grid view.

(DDA-specific.) Displays the Run Command window that lets you retrieve the available columndata that a Controller command returns. This information is helpful for determining which fields to

include on a DDA.

(DDA-specific.) Displays the DDA Export Parameters window that lets you export DDAconfiguration data to a collection of comma-separated-value (CSV) files.

(DDA-specific.) Displays the Authorization window that lets you to modify the role and user

authorizations and the menu group assignment for a DDA.

(DDA-specific.) Displays the Copy Data Driven Application window that lets you copy an existing

DDA and use it as a template for creating a new DDA.

(DDA-specific.) Displays the DDA Filter Group Maintenance window that lets you define the

attributes of a tab or group box.

Displays help for the current window.






6/48

7. Exit the RedPrairie and instance and then log in again to access the DDA and determine whether it performs asexpected.

Maintain DDAs

You can create a DDA using the DDA creation wizard, or by copying an existing DDA.

When you create a DDA, you define the

general attributes of the DDA, such as the framework in which it appears, the display name of the DDA, the Controllercommand that drives the DDA and any command qualifiers.

miscellaneous attributes, such as the

modality, which determines how the window is displayed within the client or Web framework.

Note: For more information, see DDA Modality .

whether qualifiers are published prior to the DDA command being executed.

position of the grid view or graph on the window.

user-defined group name for the DDA.

user-defined reference number for the DDA.

whether query controls (the Profile and Criteria list boxes) are available.

Note: For more information, see Profiles and Criteria Schemes .

whether the Find function is automatically executed when the DDA is opened.

actions, such as those which will launch another DDA (for example, to add or modify a record) or execute a Controller

command (for example, to delete a record).

submit fields, that support the entry of search criteria.

display fields, that support the display of data retrieved from the database.

parent/child associations, that define the DDA(s) that will be accessible from another DDA.

Note: For more information, see DDA Parent/Child Relationships .

menu group in which the DDA will appear.

users and roles who will be authorized to access the DDA.

After you create a DDA, you can modify its attributes, assign submit and display fields to filter groups, retrieve columndata, export DDA configuration data to a collection of comma-separated value (CSV) files, and delete the DDA when

necessary.






7/48

You use Data Driven Application Maintenance to define a client and/or Web-based DDA for a RedPrairie product.

What do you want to do?

Add a DDA Using the Wizard

Add a DDA Using the Copy Feature

Modify a DDA

Authorize Roles and Users for a DDA

Maintain DDA Filter Groups

Delete a DDA

Export a DDA

Add a DDA Using the Wizard

When you add a new DDA using the wizard, you define the framework in which it appears, the display name of the DDA,the Controller command that drives the DDA and the command qualifiers.

Note: It is good practice to create child and actions DDAs prior to creating a parent DDA, so that you can link tothem during the creation of the parent DDA.

To add a DDA using the wizard

1. Start Data Driven Application Maintenance.

2. Click .

3. On the Add New window, in the ID box, type a unique identifier for the DDA.

4. From the Type list, select the type of function that the DDA will perform.

5. From the Usage list, select the framework in which the DDA will be executed.

6. In the MLS Text box, type the title of the DDA that will appear in the user interface; for example, on the application

window, navigation bar and Applications menu.

7. In the Command box, type the Controller command that will return information to the DDA or execute the action for

which the DDA was created.

8. If desired, in the Qualifier box, type an argument that will be appended to the Command for the purpose of limitingthe extent of the command.

9. If desired, in the Group Name box, type the name of the group with which you want to associate this DDA.

10. If desired, in the Reference box, enter a value that can be used to reference this DDA.






8/48

11. Click Next.

12. On the Run Command window, take one of these actions.

13. Continue with the procedure to select the submit fields for a new DDA.

Add a DDA Using the Copy Feature

You can create a new DDA by copying an existing DDA using the Copy Data Driven Application window. When you create a

new DDA from a copy, you enter a unique DDA identifier and, if desired, a DDA type. When you click OK, the new DDA iscreated and you can save or modify the DDA as required.

To add a DDA using the copy feature


2. Click , and then in the grid view , select the DDA that you want to copy.

3. Click .

4. On the Copy Data Driven Application window, in the New DDA ID box, type a unique identifier for the new DDA.

5. From the Type list, select the type of DDA that you want to create, and then click OK.

6. When a message appears stating that the copy was successful, click OK. The new DDA appears on the Data DrivenApplication Maintenance window.

7. If desired, continue with the procedure to modify a DDA.

If you want to... Then...

Execute the Controller command to

retrieve the available column data,

Take these actions.

1. If desired, in the Initialize Qualifier box, type thequalifier that you want to apply to the command when

it is initially executed.

2. Click OK.

Continue creating a DDA without

executing the Controller command,Click Cancel.







9/48

Modify a DDA

You can modify a DDA using the Data Driven Application Maintenance window. When you modify a DDA, you can changethe DDA's

general attributes, including the framework in which it appears, the display name of the DDA, the Controller command

that drives the DDA and the command qualifiers.

miscellaneous attributes, including the

modality, which defines how the window appears within the client or Web framework

Note: For more information, see DDA Modality .

whether qualifiers are published prior to the DDA command being executed

position of the grid view or graph on the window

user-defined group name for the DDA

user-defined reference number for the DDA

whether query controls (the Profile and Criteria list boxes) are available, and

whether the Find function is automatically executed when the DDA is opened.

actions, including adding, modifying or deleting the actions associated with the DDA.

submit fields, including adding, modifying or deleting the submit fields that appear on the DDA.

display fields, including adding, modifying or deleting display fields that appear on the DDA.

parent/child associations, and the designation of fields that you want to pass to a child DDA.

roles and users that will have access to the DDA, and

the menu group in which the DDA will be displayed.

You can also add filter groups (tabs and group boxes) to a DDA.


Modify the General and Miscellaneous Attributes of a DDA

Modify the Action Attributes for a DDA

Modify the Submit Fields on a DDA

Modify the Display Fields on a DDA

Modify the Parent/Child Associations for a DDA


Create a Menu Group for a DDA

Associate a DDA with a Menu Group






10/48


Use this procedure to specify the roles and users that will have access to a DDA in a RedPrairie product.

Note: For more information, see Users and User Accounts and Roles and Role Assignments. .

To authorize roles and users for a DDA

1. If you are not using the DDA wizard, then access the Authorization window.

2. On the Authorization window, in the Roles Available list, take one of these actions:

Select the role(s) that you want to authorize to access the DDA, and then click .

Note: To select consecutive roles from the list, select the first role, press and hold down Shift, andthen select the last role. To select nonconsecutive roles, press and hold down Ctrl, and then select

each role.

Click to authorize all of the roles to access the DDA.

3. In the Users Available list, take one of these actions:

Select the user(s) that you want to authorize to access the DDA, and then click .

Click to authorize all of the users to access the DDA.

4. To remove any roles or users from the Assigned list, take one of these actions:

Select the role(s) or user(s) that you want to remove from the Assigned list, and click .

Click to remove all of the roles or users from the Assigned list.

5. When you have finished authorizing roles and users, click Next.

6. Continue with the procedure to create a menu group for a DDA .


A filter group is a named set of attributes that defines a tab or group box, which can be assigned to a DDA. After you








11/48

create a filter group, you can assign display or submit fields to it. You can also assign it to another filter group; forexample, you can assign a group box to another group box or to a tab.

You use the DDA Filter Group Maintenance to create filter groups. When you create a filter group, you can specify

a unique identifier for the filter group.

the title that will be displayed on the tab or group box defined by the filter group.

the sequential order in which the filter groups appear on a data driven application.

the type of filter group, either tab or group box.

that the filter group appears on another (parent) filter group; for example, that a group box appears on a tab oranother group box.

that the filter group is attached to another filter group (for example, that it resides next to, above or below another

filter group), the position of the attachment and the amount of offset between the two filter groups.

the number of columns on the filter group.

the tab order on the filter group.

the border style, if any.

the amount of offset between columns and between rows.

After filter groups are defined, you can assign submit and display fields to filter groups. For details, see Modify the SubmitFields on a DDA or Modify the Display Fields on a DDA .

You can also use DDA Filter Group Maintenance to modify and delete filter groups when necessary.


Add or Modify a DDA Filter Group

Delete a DDA Filter Group

Retrieve DDA Column Data

When adding or modifying a DDA , you can execute the Controller command for the DDA to retrieve the available column

data (fields) from the database. The column data can be retrieved into the Available list on the Submit Fields or DisplayFields tabs on the Data Driven Application Maintenance window, making the fields available for assignment to the DDA.

You use the Run Command window to define an initialize qualifier , if used, and execute the DDA Controller command.

To retrieve DDA column data

1. If you have not already done so, start Data Driven Application Maintenance.

2. Click , and then from the grid view, select the DDA for which you want to view column data.

3. Select the Submit Fields tab or the Display Fields tab.

4. Click .






12/48

5. On the Run Command window, if desired, in the Initialize Qualifier box, type a qualifier to limit the extent of the DDAcommand.

6. Click OK. If all of the fields are already displayed in the Available and Assigned lists, then there will be no change inthe data. If the command retrieves fields that are not currently displayed, they will appear in the Available list.

Export a DDA

You can export a DDA configuration to a collection of comma-separated value (CSV) files that represent the column datathat constitutes the DDA. You can then transfer and use the DDA configuration in another RedPrairie instance, as long as

the underlying commands are compatible.

The export function saves all of the DDA configuration data, including descriptions and MLS catalog entries.

You use the DDA Export Parameters window to export a DDA configuration.

To export a DDA


2. Click , and then from the grid view, select the DDA that you want to export.

3. Click . The DDA Export Parameters window appears displaying the information for the selected DDA.

4. Click OK.

5. When a message appears asking if you want to continue with the export, click Yes.

6. When a message appears stating that the export was successful, click OK.

7. On the server PC for the RedPrairie product instance in which you are working, locate the configuration files in this

folder: $LESDIR/dda_exports/.

Delete a DDA

If you delete a standard product DDA , it can be restored by reinstalling the server software from the RedPrairie product

installation CD-ROM. A custom DDA, however, is not included on the product installation CD-ROM. Therefore, beforedeleting a custom DDA, consider exporting the DDA first so that it can be restored from the export if it is needed in the

future. For more information, see Export a DDA.








13/48

To delete a DDA


2. Click , and then from the grid view, select the DDA that you want to delete.

3. Click .

4. When a message appears asking if you want to delete the DDA, click OK.

Database Archives

A system's database is typically designed for execution purposes rather than historical record keeping. In order to keep asystem's execution tables lean for performance purposes, database archiving functionality lets you save historical data in a

database archive. Some of the best candidates for database archiving include

shipment information

receipt information

daily transactions, and

order activity.

Before you begin working with database archives, it is recommended that you take a few moments to learn about

the types of database archives, and

the database archive process.

Use Database Archive Maintenance to add and maintain database archives.

Maintain Database Archives

Database archives let you save historical data, such as shipment information, receipt information, daily transactions and








14/48

order activity in a database archive. Use Database Archive Maintenance to add and maintain database archives.


Add a Database Archive

Modify a Database Archive

Delete a Database Archive

File Loading

You can manually load data from a comma-separated value (.csv) file into a RedPrairie database using the Load FileOperations window. This lets you quickly add a large amount of information to your RedPrairie database at one time,

instead of adding each individual piece of information using a maintenance application or host transaction download. This isespecially useful if you have already added the information to one of your other third party applications that lets you export

information to a .csv file.

Load File Operations uses the logic in an associated control file to determine whether data is being added or updated, andlets you load data into a database from .csv files that are located on

a local client workstation, or

the application server.

IMPORTANT: The location of the control file is determined by a system policy (SYSTEM-INFORMATION/PRODUCT-LAYERS/DATA-PATHS) that lets you specify the folder(s) in which control files are located for the database tables.

For more information, see SYSTEM-INFORMATION_PRODUCT-LAYERS_Policy_Overview.

When you use Load File Operations to load data, the data is added or updated; it is not deleted. For example, if a record

exists in the database, but not in the .csv file, when the .csv file is loaded, the record is not removed from the database. Ifyou need to manually remove records from the database, you must do so using SQL commands.

Before you begin performing load file operations, it is suggested that you take a few minutes to learn about these concepts.


File Loading Usage Examples

Valid .csv Data File Attributes

Example of a .csv Data File







15/48

Perform Load File Operations

The Load File Operations window lets you load data into a database from .csv files that are located on a local clientworkstation or the application server.

IMPORTANT: Use this procedure with caution. Loading data into a database, if done improperly, can result inunexpected system behavior. It is suggested that you back up your data before attempting this procedure.

To perform load file operations

1. Start Load File Operations.

2. Take one of these actions.

Note: The control file associated with the table appears in the Control File box.


Note: The Load File button becomes available.


If you... Then...

Know the name of the table into which you want to load

data from a file,

Take these actions.

1. In the Table Name box, type the name ofthe database table.

2. Click .

Do not know the table name, or you want to select the

data file from the grid view,Click , and then in the grid view, select thetable name.

If you... Then...

Know the folder and name of the file that

you want to load,In the File Name box, type the folder and name of the file.

Want to browse to the file that you want to

load,

Take these actions.

1. Click Browse.

2. On the File Name window, browse to the file that you wantto load.

3. Click Open.

Note: You may have several files to load; however, you can

only load one at a time.

If the data file that you want to load is located on the... Then select...

Application server, Server.

Client workstation, Client.





16/48

5. If desired, in the Field Delimiter box, type the symbol that separates the values in the file that you are loading intothe database table.

6. Click Load File. The file loading process begins and may take several seconds or minutes (depending on the size ofyour file).

7. When a message appears stating that the file load was successful, click OK. Information about the file loading

process appears in the File Load Results box.

Jobs

A job is a command that is configured to run in the background while your RedPrairie application server instance is

operating. Jobs are executed within a thread of the RedPrairie server, and they are managed by the server's job manager.A job can be

timer-based; that is, configured to run at set intervals. For example, you can configure a job to run every 600

seconds.

schedule-based; that is, configured to run at a predefined time. For example, you can configure a job to run every 1stand 15th of the month at midnight.

Jobs are configured in Job Maintenance, and they are stored in the database.

Note: Prior to version 2010.1.x, jobs were configured in Schedule Agent Operations and stored in the registryfile.

After jobs are configured, you can use the RedPrairie Console to monitor the status of, and stop and start the scheduling ofjobs. For more information, see Manage Jobs and Tasks.

Before you configure jobs, it is suggested that you take a few minutes to learn about these concepts.


Job Configuration in a Clustered Environment

Job-Specific Environment Variables

Job Tracing








17/48

Tasks

A task is either a program or a Java thread that starts when your RedPrairie application server starts, and it continues torun in the background as configured while your server instance is operating. A task can be run

as a completely separate program, which runs in parallel with the RedPrairie application server (process-based task).

Process-based tasks are executables (programs) that can be implemented in any programming language.

as a separate Java thread, which runs within the application server itself (thread-based task). The task managerinstantiates thread-based tasks using a Java class, which implements the Java runnable interface.

Note: A Java thread-based task will use fewer system resources than a process-based task.

IMPORTANT: If you are creating a process-based task in the C programming language on an AIX server, and the

task calls srvInitialize(), then you must define a unique LIBPATH environment variable for the task. For detailedinformation, see Add or Modify a Task.

Tasks are configured in Task Maintenance, and they are stored in the database.

Note: Prior to version 2010.1.x, tasks were configured and stored in the registry file.

After tasks are configured, you can use the RedPrairie Console to monitor the status of tasks, and to stop and start tasks.For more information, see Manage Jobs and Tasks.

Before you configure jobs, it is suggested that you take a few minutes to learn about these concepts.


Task Configuration in a Clustered Environment

Task-Specific Environment Variables

Task Tracing

Thread-Based Task Testing

Maintain Jobs

You use Job Maintenance to create and schedule jobs. When you create a job, you

specify a unique ID for the job.

provide a descriptive name for the job.






18/48

.

optionally, define log file and trace level details.

specify a node ID if working in a clustered environment.

indicate whether the job is

timer- or schedule-based, and then define the timing or schedule for the job.

enabled to start.

able to start even though another instance of that job is currently running.

optionally, define an environment variable value that is specific to the job.

Once you have created jobs, you can use Job Maintenance to

modify job attributes, and

delete jobs.

IMPORTANT: Maintaining jobs is a system administrative task that requires knowledge of RedPrairie development

concepts and experience in RedPrairie command development.


Add or Modify a Job

Delete a Job

Maintain Tasks

You use Task Maintenance to create tasks. When you create a task, you

specify a unique ID for the task.

provide a descriptive name for the task.

indicate whether the task is

thread- or process-based

enabled to start, and

able to restart if terminated.

enter the program that executes the task (for process-based tasks).

enter the class name that executes the task (for thread-based tasks).

identify the directory from which the program to run process-based tasks will execute.

optionally, define a log file name and location.






19/48

.

optionally, define an environment variable value that is specific to the task.

Once you have created tasks, you can use Task Maintenance to

modify task attributes, and

delete tasks.

IMPORTANT: Maintaining tasks is a system administrative task that requires knowledge of RedPrairie

development concepts and experience in RedPrairie command development.


Add or Modify a Task

Delete a Task

Manage Jobs and Tasks

You use the Web-based, RedPrairie Console to view the status of the jobs and tasks that are configured for your

environment. More specifically, you can

view a list of all jobs and tasks along with their attributes and session details

stop and start the scheduling of jobs, and

stop and start tasks.

IMPORTANT: You must have the administrative password to access the Console. This is not your RedPrairie login

password. It is a unique password for the Console, and it was defined during the application server installation.


Monitor Jobs and Tasks

Stop and Start Jobs and Tasks

Reports

You can generate and maintain standard and custom reports that allow you to view the status of activities within yourfacility.








20/48

Example of a Reporting Report

Before you begin working with the reports, it is recommended that you take a few moments to learn

how reports are generated, and

how you can change the appearance of the report.

Label Compliance

As part of your daily routine, you need to print labels and reports at different times as you process inventory through your

warehouse.

If you are using RedPrairie Warehouse Management or RedPrairie Parcel , label compliance lets you specify a label(s)

and/or report(s) to print for an order at specified breakpoints (exit points) in the warehouse process during the order'slifetime. For example, you can configure the system so that

when a shipment is staged, the customer's case labels and pallet labels are automatically printed along with the

carrier's bill of lading.

when a package is manifested, the customer's packing list is automatically printed.

Note: If you are using RedPrairie Warehouse Management or RedPrairie Parcel , label formats for the top 100

retailers are included. Other RedPrairie products do not currently support label functionality.

The system handles compound entities that have their own label formats and documents; for example, for a particular

combination of customer and carrier type, print the customers LTL ship label.

Label compliance gives you the ability to configure the system to flexibly choose the correct type and number of labelsand/or reports to automatically print at the exact points in the warehouse process when those labels and/or reports are

needed and at the exact printer(s) where they need to be printed.

Before you begin using label compliance, it is suggested that you learn about these concepts.


Document types

Report formats

Label formats

Compliant configurations

Printing exit points

Precedence

Document groups

Load levels

Printing location






21/48

Reports/Labels Client Applications

There are several RedPrairie client applications that you can use to perform report functions. If you are using RedPrairie

Warehouse Management or RedPrairie Parcel , there are several RedPrairie client applications that you can use to performlabel functions.

Note: Other RedPrairie products do not currently support label functionality.

Before you begin working with these applications, it will be helpful if you learn what each application lets you do.


Report Maintenance

Report Operations

Report Archive

Label Format Maintenance

Document Type Maintenance

Compliant Configuration Maintenance

Define and Maintain Report Options

Report options identify

the report ID

a description for the report

the report layout

the printer at which the report will print

the product to which the report applies

optionally, the number of days to store the report in the report archive

if applicable, whether to log an Event Management event when the report is generated, and

the event name, if logging an Event Management event for the report.








22/48

Once you define the report options in Report Maintenance, you can preview and print reports in Report Operations.


Define Options for a Custom Report

Modify Options for a Report

Delete a Report

View a Report

Use this procedure to view reports.

Note: If you have defined custom reports for this RedPrairie product in Report Maintenance, then those reports

are also accessible for viewing.

Note: Permission for users to view and print reports is granted in Authorization Maintenance.

To view a report

1. Start Report Operations.

2. Click , and then from the grid view, select the report that you want to view.

3. If a list of parameters appears, and you want to limit the amount of information that will appear in the report, then

type or select the parameter values that apply. For example, in Warehouse Management, if you selected theInventory report, and you want to view details for a specific location, then select the location from the Location

Lookup box, or in Workforce Management, if you selected the Quality Audit report, and you want to view details for aspecific aisle area, then select the aisle area from the Aisle Area Lookup box.

4. Click Preview. On the Report Preview window, you can take these actions.


View the table of contents for

the report,

Click .

The table of contents appears. You can click on any entry to view it inthe report.

Export the report information to

a file or a folder,

Click Export.

Note: You can save the report information as a Microsoft Excel(.xls) document, an HTML or HTML Frames (.mht) document, in

portable document (.pdf), or rich text document (.rtf) format.

View multiple pages of the

report on the Report Previewwindow,

Click and then select the page layout that you want to view.

Note: Click to return to the single page view.

Split the Report Preview

Click and drag the splitter bar towards the bottom of the Report

Preview window.






23/48


Print a Report

Use this procedure to print reports on a printer connected to the Reporter server.

Note: If you have defined custom reports for this RedPrairie product in Report Maintenance, then those reportsare also accessible for printing.


To print a report

1. Start Report Operations.

2. Click , and then from the grid view, select the report that you want to print.

3. If a list of parameters appears, and you want to limit the amount of information that will appear in the report, thentype or select the parameter values that apply. For example, in Warehouse Management, if you selected the

Inventory report, and you want to view details for a specific location, then select the location from the LocationLookup box, or in Workforce Management, if you selected the Quality Audit report, and you want to view details for a

specific aisle area, then select the aisle area from the Aisle Area Lookup box.

4. Click Print.

5. On the Report Print window, select the print options, and then click Print.

window into two separateviews, Note: For example, you can view multiple pages of a report as

thumbnails in one view, while viewing a single page of the report inthe other view. You can then double-click on a thumbnail to view

that page in the single-page view.

Locate a specific word or

phrase in the document,

Click .

On the Find window, in the Find What: box, type the word or phrase.

Then select the appropriate match options and click Find Next.


Copy report information into

another application or report,

Click to cut the current page to the clipboard. Select the locationto paste the page, right-click and then from the Shortcut menu,

select Paste.

Note: You can paste the report in a textual or graphical format.

Print the report to a local

printer connected to your PC,Click . On the Print window, select the print options, and thenclick Print.

Close the Report Preview

window, Click .






24/48

View an Archived Report

Use this procedure to view archived reports.


To view an archived report

1. Start Report Archive.

2. Click , and then from the grid view, select the report that you want to view.

3. If a list of parameters appears, and you want to limit the amount of information that will appear in the report, then

type or select the parameter values that apply. For example, in Warehouse Management, if you selected theInventory report, and you want to view details for a specific location, then select the location from the Location

Lookup box, or in Workforce Management, if you selected the Quality Audit report, and you want to view details for aspecific aisle area, then select the aisle area from the Aisle Area Lookup box.

4. Click Preview. When the report appears, you can take these actions.



View the table of contents for

the report,

Click .

The table of contents appears. You can click on any entry to view it in

the report.

Export the report information toa file or a folder,

Click Export.

Note: You can save the report information as a Microsoft Excel(.xls) document, an HTML or HTML Frames (.mht) document, in

portable document (.pdf), or rich text document (.rtf) format.

View multiple pages of thereport on the Report Preview

window,

Click and then select the page layout that you want to view.

Note: Click to return to the single page view.

Split the Report Preview

window into two separateviews,

Click and drag the splitter bar towards the bottom of the ReportPreview window.

Note: For example, you can view multiple pages of a report as

thumbnails in one view, while viewing a single page of the report in

the other view. You can then double-click on a thumbnail to viewthat page in the single-page view.

Locate a specific word or

phrase in the document,

Click .

On the Find window, in the Find What: box, type the word or phrase.

Then select the appropriate match options and click Find Next.







25/48

Print an Archived Report

Use this procedure to print archived reports to a printer connected to the Reporting server.

To print an archived report

1. Start Report Archive.

2. Click , and then from the grid view, select the report that you want to print.

3. Click Print.

4. On the Report Print window, select the print options, and then click Print.

Maintain Label Formats

Label Format Maintenance lets you maintain the different formats of labels that you print in your facility; for example, a

generic case label, customer A's case label, and client A's/customer B's case label.

When you use Label Format Maintenance to define a label format, you specify

a name and description for the label format

an optional media file to associate with the label

whether the label format requires an RFID-enabled printer, and

Copy report information into

another application or report,

Click to cut the current page to the clipboard. Select the locationto paste the page, right-click and then from the Shortcut menu,

select Paste.

Note: You can paste the report in a textual or graphical format.

Print the report to a local

printer connected to your PC,Click . On the Print window, select the print options, and thenclick Print.

Close the Report Previewwindow, Click .








26/48

.


Add or Modify a Label Format

Delete a Label Format

Maintain Document Types

If you are using RedPrairie Warehouse Management or RedPrairie Parcel , you can use Document Type Maintenance to

create and maintain document types, such as pallet label, Bill of Lading report and storage location label.



Add a Document Type

Modify a Document Type

Delete a Document Type

Maintain Compliant Configurations

If you are using RedPrairie Warehouse Management or RedPrairie Parcel , you can use Compliant ConfigurationMaintenance to create and maintain compliant configurations.



Add a Compliant Configuration

Modify a Compliant Configuration

Delete a Compliant Configuration








27/48

Manually Print a Label

Use this procedure to manually print a label.

Note: Label functionality is available if you are using RedPrairie Warehouse Management or RedPrairie Parcel .Other RedPrairie products do not currently support label functionality.

To manually print a label

1. Start Print Label Operations.

2. If you want to narrow the list of labels from which to select, in the search criteria boxes, type, look up or select theappropriate information.

3. Click , and then from the grid view, select the label that you want to print.

4. If you want to select a printer other than the default to which to print the label, from the Default Printer list, select

the printer.

5. In the label argument box(es), type, look up or select the appropriate information to uniquely identify the item for

which you want to print a label. For example, if you choose to print a storage location label, the system will display aStorage Location box in which you can type or look up the specific storage location for which you want to print a

label.

6. Click .

7. When you are finished printing labels, click .

Manually Print a Compliant Document

Use this procedure to manually print a report or label based on its compliant configuration(s).

To manually print a compliant document

1. Start Compliant Label Print Operations.

2. In the Inventory ID box, type the inventory identifier, such as Load Number, Load UCC, Case Identifier and Sub-LoadUCC Code, for which you want to print a compliant report(s) or label(s).








28/48

3. From the Exit Point list, select the point in the warehouse process at which the report(s) or label(s) that you want tomanually print have been configured to automatically print. The system generates a list of the report(s) and label(s)

that match the compliant configuration(s).

4. Select the check box(es) next to the report(s) and/or label(s) that you want to manually print.

5. From the Default Printer list, select the printer to which to print the selected report(s) and/or label(s).

6. Click Print.

7. When you are finished printing compliant documents, click .

View Label Formats

Use this procedure to view details about the label formats stored in the system.


To view label formats

1. Start Label Format Maintenance.

2. If you want to narrow the list of label formats to be viewed, in the search criteria boxes, type, look up or select the

appropriate information. For example, if you only want to view the label formats associated with a specific defaultprinter, then from the Default Printer list, select the printer.

3. Click , and then from the grid view, select the label format that you want to view.

4. When you are finished viewing the label format(s), click .

View Document Types








29/48

Use this procedure to view details about the document types stored in the system.

Note: Label functionality is available if you are using RedPrairie Warehouse Management or RedPrairie Parcel .

Other RedPrairie products do not currently support label functionality.

To view document types

1. Start Document Type Maintenance.

2. If you want to narrow the list of document types to be viewed, in the search criteria boxes, type, look up or selectthe appropriate information. For example, if you only want to view report document types, then from the Document

Type Code list, select Report.

3. Click , and then from the grid view, select the document type that you want to view.

4. When you are finished viewing the document type(s), click .

View Compliant Configurations

Use this procedure to view details about the compliant configurations stored in the system.


To view compliant configurations

1. Start Compliant Configuration Maintenance.

2. From the Document Type list, select the document type of the compliant configuration that you want to view.

3. Click , and then from the grid view, select the compliant configuration that you want to view.

4. When you are finished viewing the compliant configuration(s), click .







30/48

Security

To log in, users must have a valid user authorization within the system. User authorization consists of

a user ID

a locale ID

security options (including a password and account status information)

address information (optional)

roles, and

menu options.

Authorization Maintenance lets you secure information within your system. You can limit a user's access to client functions

by assigning roles to each individual user. A role defines which client applications (or menu options) a user can start.

In addition, you can restrict a user's ability to view specific information within a client application window. For example,system administrators typically maintain users within your system by starting Authorization Maintenance. You may want to

restrict a system administrator from seeing pay rate information for other users, but need to allow them to start theapplication. By defining limited executable parameters, you can restrict a system administrator's view of the pay rate field,

while still allowing the administrator to start the application.

To understand how the security functions within your system work, it will be helpful if you learn more about these

concepts.


Users and User Accounts

Roles and Role Assignments

Change a Password

Passwords are used as a security device to ensure the integrity of the information within your system. Therefore, it is

important that they remain confidential. If you have reason to believe that a password is no longer confidential, then it isrecommended that it be changed.

To change a password

1. From the Tools menu, select Change Password.

2. On the Change Password window, enter the password that you want to change.

3. Enter the new password.

4. Re-enter the new password to confirm the spelling.







31/48

5. Click OK.

6. When the message appears stating that the password was updated successfully, click OK.

Change a Locale ID

If there is more than one locale defined in your system, you can easily change the attributes that appear in the GUI tomeet your language requirements.

To change locales

IMPORTANT: You can change locale IDs while your system is running; however, to apply the changes you mustexit the system and then log in again.

1. From the Tools menu, select Change Locale.

2. From the list of available locales, select the locale ID for the locale that you want to use.

Tracing

The RedPrairie tracing functionality helps you, along with RedPrairie customer support, identify and solve system issues. Atrace captures the events that take place within the system whenever a process or task is performed, and then displays the

results in a log file. You can analyze the log file to

learn about a process or form flow within an application

identify system configuration issues

identify user issues, and

learn how your system performs a task.

When you perform a trace, you can specify the filename for the trace log file and any additional information that you wantincluded (such as application flow messages or system performance statistics). The system saves the log file in the LES

director in the Log directory for that environment on the application server.

Note: By default, your user ID is used when naming the trace log file. It is recommended that you change the

default filename to something more specific about the trace and to prevent accidentally saving a new trace overyour existing.









32/48

Command Profile Log File

Tracing Options

The RedPrairie products let you specify the additional information that you want included with your trace file (such as

application flow messages or system performance statistics). You can also specify the filename for the saved trace log file.

You use the Trace Options window to specify the trace log filename and the additional options. You can access the TraceOptions window from the Tools menu by selecting Tracing and then Trace Options.

Note: You can also configure your user preferences to prompt you for the trace options when enabling the trace.For information about user preferences, see User Preferences .

Command Profile Log File

A command profile log file is a separate log file that is saved whenever you perform a trace. In this log file, the trace logfile and the information on the other options included in the trace (such as application flow messages or system

performance statistics) are saved together. This lets you view all of the trace information from a single source.

Note: The command profile log file using the same name as the trace log file but has the file extension of .cmdprf

instead of .log. The command profile is typically saved in the same location as the trace log file.

You use the Command Profiler window to view the command profile log file. This window appears after you opened a saved

command profile log file from the Open Command Profile window or when you click Yes to view the trace that you justperformed.

IMPORTANT: The command profile log file is the recommend file to use when viewing and analyzing traceinformation.

Initiate a Trace

To initiate a trace










33/48

1. From the Tools menu, select Tracing, and then take one of these actions.

2. On the Trace Options window, in the Server File Name box, type a name for the log file.

3. In the Server Trace Flags list, take one or more of these actions.

Note: Clear the check box to no longer view the information.

4. Click OK.

5. If a message appears asking if you want to activate tracing now, click Yes.

Note: To verify that the tracing has been activated, from the Tools menu, select Tracing, and then verify that a

check mark appears next to Tracing Enabled.

6. Perform the task(s) that you want to trace.

7. When the task(s) are completed, turn off the trace.

8. When a message appears asking if you want to view the log file, click Yes. The Command Profiler window appearsand the command profile log file for the trace is displayed.

Note: If you click No, you can view the trace information at a later date. For detailed information on opening thecommand profile log file for a saved trace, see Open a Saved Trace .

9. View the log file. For detailed information on displaying specific information for analysis, see View a Trace .

If your user preferences are... Then select...

Set to always prompt you for trace optionswhen performing a trace,

Note: For information about user

preferences, see User Preferences Window .

Tracing Enabled.

Not set to prompt you for trace options when

performing a trace,Trace Options.

If you want the trace to include... Then select the check box for...

Commands being executed by an application, Application Flow Messages.

Execution of SQL statements (such as selects,commits and rollbacks),

SQLLib Calls.

Server processing functions (such as finding,

parsing and executing commands and Cfunctions), Server Flow Messages.

Processing of arguments (such as the event ID,triggering system, destination system, IFD ID

and IFD version),

Server Arguments.

Database and cache performance statistics(such as the amount of time spent in

preparation, execution and retrieving data fromthe database and cache),

Performance Statistics.

Identifiers for the processes, Display Process ID in All Messages.

All commands, arguments, statements and

messages,Command Profiling.




34/48

Open a Saved Trace

You use the Open Command Profile window to open the command profile log file for the saved trace. You access the Open

Command Profile window from the Tools menu by selecting Tracing, View Trace, and then Open Trace.

To open a saved trace

1. If you have not already done so, initiate a trace. For detailed instructions, see Initiate a Trace .

2. From the Tools menu, select View Trace File, and then take one of these actions.

3. View the log file. For detailed information on displaying specific information for analysis, see View a Trace .

View a Trace

You use the Command Profiler window to view the command profile log file for a trace. In addition, you can search for anddisplay specific information for analysis. This window appears when you opened a saved trace or when you clicked Yes after

generating a trace.

To view a trace

1. If you have not already done so, open the command profile log file for a trace. For detailed instructions, see Open a

Saved Trace .

Note: The command profile log file is opened immediately after performing the trace and clicking Yes when asked

if you wanted to open the file.

2. On the Command Profiler window, review the log file information.

If you want to open the

command profile log file for the

trace that was...

Then...

The last performed,Select View Last Trace File. The Command Profiler window appears and

the command profile log file for the trace is displayed.

Not the last performed,

Take these actions.

1. Select Open Trace File.

2. On the Open Command Profile window, in the grid view, select the

command profile log file that you want to open.

3. Click Open. The Command Profile window appears and thecommand profile log file for the trace is displayed.








35/48

3. If desired, take one or more of these actions.


View commands that took aspecific amount of time to

execute,

In the Filter area, take these actions.

1. In the Filter Time (ms) box, type the execution time in milliseconds.

2. Click Filter. The results appear in the left pane.

View commands that failed toexecute,

In the Filter area, select the Display Only Bad Statuses check box. Theresults appear in the left pane.

View full scan queries,

In the Filter area, take these actions.

1. Select the Display Only Full Scan Queries check box.

2. If a message appears indicating that you must first scan for bad queriesand asking if you want scan for the queries now, click Yes. The results

appear in the left pane.

Search for specific text,

In the Find area, take these actions.

1. In the Find What box, type the text for which you to locate.

2. From the Search In list, take one of these actions:

If you want to look in the command profile information (left pane),then select cmd_prf.

If you want to look in the trace information (right pane), then select

trc_fil.

3. Click Find Next. Repeat this step to find all occurrences of the text.

Print the trace log file,

Take these actions.

1. From the Tools menu, select View Trace File. The trace log fileinformation appears in a new window.

2. From the File menu, select Print.

3. On the Print window, select the print options, and then click Print.

4. Click Exit. The Command Profiler window appears.

Copy information to theclipboard,

Take these actions.

1. From the Tools menu, select View Trace File. The trace log file

information appears in a new window.

2. Select the information that you want to copy, and then from the Editmenu, select Copy.


4. Open the document into which you want to paste the information, andthen from the Edit menu, select Paste.

Change the window font,

Take these actions.


2. Select the text that you want to change, and then from the Settings

menu, select Font.

3. On the Font window, select the font that you want to apply, and then

click OK.


Change the printer font,

Take these actions.


2. Select the text that you want to change, and then from the Settings

menu, select Printer Font.




36/48

4. When you have finished viewing the trace log file, from the File menu, select Exit.

User Authorization Overview

User authorization is the process of defining the users that can access the system, the functions that they can perform andthe data that they can access.

Before you begin setting up user authorizations, it is suggested that you learn about these concepts.


Setup Tasks



Menu Options

Data Access Groups

Standard Permissions

Custom Permissions

User Authorization Setup Tasks

These are the tasks you must perform to set up user authorizations.

1. Create roles and identify the menu options.

2. Optionally, assign standard permissions and custom permissions to roles. If no standard permissions are assigned to

a role, then by default the role has full access. For more information, see Maintain Roles and Role Assignments.

3. Create user accounts and assign roles to the user accounts. For more information, see Maintain User Accounts .

If desired, you can also

click OK.









37/48

. .

create custom permissions and assign them to roles. See Maintain Custom Permissions or Define and Assign aControl-Specific Custom Permission.

create data access groups and assign them to Collaboration Portal users. See Maintain Data Access Groups.

Note: Data access group restrictions are limited to Collaboration Portal users. Collaboration Portal is comprised ofthese Web-enabled applications: Carrier Portal, Client Portal, Customer Portal , Store Portal, Tracking Portal and

Vendor Portal.


A user is someone who accesses the system using a PC or RFT, or remotely accesses the system from the Internet using a

Web service. In addition, for time and attendance purposes a user is someone for whom time tracking and gross paycalculations are performed.

Every user must be identified in the system with a user account and then assigned specific system privileges. When a userlogs in, the system builds a list of the functions that the user can perform based on the user account settings. Any changes

made to the available functions for a user account will not take effect until the next time the user logs in.

From Authorization Maintenance, access User Maintenance to maintain user accounts and access to your system.


A role is a category used to group menu options (such as client applications, reports orRF screen) for the purpose of

maintaining user authorizations. Once roles are created, they are assigned to the appropriate user account(s) to control the

tasks users are authorized to perform. As an example, you can create a Shipping Supervisor role to identify all of the menuoptions that are needed to fulfill the duties required for that job, and then assign that role to the user account for the

shipping supervisors in your facility.

Roles are organized in a hierarchical structure that uses parent/child relationships to control your ability to assign roles to

other users. This structure restricts the levels of authorization that one user may assign to another user, ensuring thatusers are not given authorization they should not have.








38/48

When you create a role, it is considered a child role. You assign a parent role to the child role to define its position withinthe hierarchy. When assigning the parent role, only the roles to which you are assigned are available for selection. This

ensures that you can only create a role at a level in the hierarchy that is lower than or equal to your highest assigned rolelevel. Similarly, when assigning a role to another user, you are only allowed to assign a role at a level in the hierarchy that

is lower than (but not equal to) your highest assigned role level.

IMPORTANT: The Super role is the exception to the preceding statements. A user assigned to the Super role can

assign the Super role to other users.

For example, if a user is assigned to the role Shipping Supervisor, and this is the highest role level in the hierarchy towhich that user is assigned, that user can create a child role Shipping Clerk and assign it the parent role of Shipping

Supervisor. The shipping supervisor can now assign the Shipping Clerk role to another user, but cannot assign the Shipping

Supervisor role to another user. Only a user with the role that is the parent for the Shipping Supervisor role is authorized toassign the Shipping Supervisor role.

From Authorization Maintenance, access Role Maintenance to maintain roles and role assignments.


Option Types

Menu Options

A menu option is a client application, report, RFT operation or Web service. You can assign a menu option to a role to

define authorization for the menu option. If you are logged in with the Super user account you can also

assign a menu option to a specific user to configure who is authorized to access the menu option.

limit a user's ability to access certain information within a menu option. For example, you might not want a user tosee certain columns or to access certain drill-down information. By including executable parameters for an application,

you can restrict users and secure your system's information.

Note: Alternatively, you can use standard and custom permissions to limit user access. For details, see Standard

Permissions and Custom Permissions .

From Authorization Maintenance, access Role Maintenance to assign menu options to roles. If logged in with the Super user

account, from Authorization Maintenance, access Menu Option Maintenance to further define menu options and theirassignments.








39/48

Data Access Groups

A data access group is a named set of data, such as a list of customers, to which you can assign specific CollaborationPortal users for the purpose of limiting these users' access to that set of customer data within your Transportation

Management system. When you define a data access group, you specify the type of data such as customer, customer type,customer address, client or carrier that you can assign to a data access group. Once data access groups are created and

data items assigned, you then assign the appropriate users.

Note: Data access group restrictions are limited to Collaboration Portal users. Collaboration Portal is comprised of

these Web-enabled applications: Carrier Portal , Client Portal , Customer Portal , Store Portal , Tracking Portaland Vendor Portal .

Data access groups are used when you want to limit users' access to the specific data needed to fulfill their jobresponsibilities. For example, if you want users that work with customers A and B to view and access only this customer

data, you can create a "Customer" type data access group and assign customers A and B to it. Authorized users can thenbe assigned to the data access group.

Users' data access is the sum of all data access groups to which they are assigned. Users without any data access groupassignments will have full visibility to your system data from Collaboration Portal as defined by their role assignments.

From Authorization Maintenance, access Data Access Group Maintenance and Assign Customer/Address to Data AccessGroup to maintain data access groups and data assignments.

Standard Permissions

Standard permissions are permissions that can be assigned to a role to restrict the actions (such as creating, updating anddeleting a record) that a role can perform on a specific application or an all applications assigned to the role.

By default, a role has full access to all of its assigned applications (the Full Access standard permission is assigned). If you

remove Full Access and assign another standard permission(s) to a role, then the role is limited to that standard permission(s). For example, you can assign the Read Only permission to allow the role access to assigned applications and the ability

to retrieve data, but prevent the role from maintaining any data or performing any actions within those applications.

Note: Custom permissions can also be assigned to a role to give the role access to a specific form or to

information and/or functionality on a specific application or form. For more information, see Custom Permissions.

A standard permission can be assigned to a specific application assigned to a role. For example, you can assign the Order

Maintenance application to a role, but assign only the Create and Update standard permissions to it. As a result, usersassigned to the role can create and update orders, but not delete them (the Delete button will be unavailable).

This table lists the standard permissions that you can assign to a role, or to one or more applications assigned to a role.






40/48

From Authorization Maintenance, access Role Maintenance to assign standard and custom permissions to roles. If logged inwith the Super user account, from Authorization Maintenance, access Menu Option Maintenance to assign standard

permissions to an application assigned to a role.

Custom Permissions

A custom permission is a user-defined permission that provides access to a specific form or information and/or functionality

on a specific application or form. Access is granted for all roles to which the custom permission is assigned, and denied forall roles to which it is not assigned.

Custom permissions can be defined for a specific application or form to grant

access to a form within an application.

access to a control, such as a button or check box.

access to information, such as a tab or field.

the ability to maintain the editable grid, such as update the information in a cell and/or add/delete rows.

the ability to edit, save and/or print charts.

the ability to create and/or update addresses.

When you define a custom permission for an application or form, you can select to hide the control (such as the button,

field, check box or tab) for those roles to which the permission is not assigned.

Once a custom permission is defined, you must assign it to the role(s) that you want to have the permission. For moreinformation, see Assign Custom Permissions to a Role.

IMPORTANT: Any role that does not have the custom permission assigned to it will be denied the permission and,if specified, the control will be hidden from those roles.

You use

StandardPermission

Description

Create Lets users create a new record.

Create Address Lets users create a new address record.

Delete Lets users delete a record.

Edit Chart Lets users view and edit a chart.

Full Access Lets users perform all available actions.

Print Chart Lets users print a chart.Read Only Lets users view a list of records.

Save Chart Lets users save changes made to a chart.

Update Lets users update an existing record.

Update Address Lets users update and save an existing address record.






41/48

,

Permission Control Association Setup to maintain control-specific custom permissions for an application or form andassign the permission to a role(s).

Maintain User Authorizations

Use Authorization Maintenance to

create roles

create user accounts

create data access groups, and

assign user functionality.


Maintain Roles and Role Assignments

Maintain User Accounts

Add a User Account Using the Copy Feature

Maintain Menu Options

Maintain Data Access Groups

Maintain Custom Permissions

Define and Assign a Control-Specific Custom Permission

Maintain Roles and Role Assignments

You use Role Maintenance to maintain the roles in your facility. You can specify

an identifier for the role.








42/48

.

the parent role to which this role is assigned.

whether this role is active in the system.

the name of the authorization group (the group of users that this role is authorized to maintain) associated with therole, if applicable.

the data table associated with this role.

After roles are defined you can use Role Maintenance to assign menu options, users, standard permissions and custom

permissions; and to modify and delete roles when necessary.

Alternatively, you can define a control-specific custom permission and assign it to a role(s) using the Permission Control

Association Setup window accessible from a shortcut key sequence (Ctrl+Shift+F6). For instructions, see Define and Assigna Control-Specific Custom Permission .


Add or Modify a Role

Delete a Role

Define or Modify Menu Option Associations for a Role

Define or Modify User Associations for a Role

Assign Standard Permissions to a Role

Assign Custom Permissions to a Role

Maintain User Accounts

When you use User Maintenance to identify a user account, you specify

a unique user and login ID.

the user's first and last names.

an optional media file associated with the user.

a locale and client ID.

an authorization group name. If a RedPrairie Enterprise product (for example, Web Visibility ) is licensed and installed,you can specify the name of the group of users or roles that the current user has authorization to maintain.

security options that let you configure access to the system by

enabling a user's ability to sign on automatically using the Microsoft Windows network user ID and password, or

with a RedPrairie system password.

Note: When using a RedPrairie system password, you can also set a password expiration date and/or a






43/48

requirement to change the password when the user logs into the system for the first time.

defining a user's account status as active, inactive or expired.

defining a user's account expiration date.

requiring external authentication, which validates the user's ability to access the system by using Lightweight

Directory Access Protocol (LDAP).

indicating that a role is a Super user.

address information.

the roles, reports and menu options assigned to this user.

Workforce Management options (if Workforce Management is licensed and installed) by defining

a user group, work team, supervisor and report card association

whether the user is a supervisor

whether the user is unmeasured

a hire date

a schedule

a rate of pay, and

comments.

Time & Incentives options (if Time & Incentives is licensed and installed) by defining

a personal identification number

eligibility for and associated differential pay

eligibility for incentive pay and payroll generation, and

associated wage scales.

Warehouse Management options (if Warehouse Management is licensed and installed) by defining

which warehouse(s) the user is authorized to access

which warehouse is the default for the user, and

whether count back is required for the user.

the data access groups assigned to this user (if Transportation Management is licensed and installed).

fter user accounts are defined you can use User Maintenance to modify user attributes and delete user accounts whenecessary.


Add or Modify a User Account

Delete a User Account


omments on this topic?




44/48

Add a User Account Using the Copy Feature

Authorized

Warehouse Management System Tools

Documents

Transcript of Warehouse Management System Tools