| Oracle® Retail POS Suite Configuration Guide Release 14.1 E54474-03 |
|
 Previous |
 Next |
This chapter provides an introduction to the definition and use of parameters and system configurations for the POS Suite applications. It also covers receipt components for the Oracle Retail Point-of-Service application.
|
Note: For Oracle Retail Mobile Point-of-Service, a mobile device is considered another register in a store. Any references to updating parameters for registers include mobile devices. |
This configuration guide addresses the following topics:
Chapter 1, "Overview." This chapter has an overview of the definition and use of parameters, system configurations, and Point-of-Service receipt components.
Chapter 2, "Description of Configuration Methods." This chapter describes how to configure parameters, system configurations, and receipt components.
Chapter 3, "Point-of-Service." This chapter describes the parameters and system configurations available for configuring Oracle Retail Point-of-Service and Oracle Retail Mobile Point-of-Service. The components used to define the contents of receipts are also described.
Chapter 4, "Back Office." This chapter describes the parameters and system configurations available for configuring Oracle Retail Back Office.
Chapter 5, "Central Office." This chapter describes the parameters and system configurations available for configuring Oracle Retail Central Office.
Chapter 6, "Returns Management." This chapter describes the parameters and system configurations available for configuring Oracle Retail Returns Management.
Chapter 7, "System Configurations Common to Multiple Applications." This chapter describes the system configurations for the audit log and password policy. These system configurations are used by more than one application.
Appendix A, "Appendix: Parameters Replaced by Receipt Components." This appendix lists the parameters that were previously used to control printing of receipts, but have been removed.
Appendix B, "Appendix: ACI PIN Comm Configuration." This appendix has additional information for configuring ACI PIN Comm.
Parameters are name value pairs that are used to set options and control behavior in applications. They are used to control flow in an application and to select allowed values for data. Parameters enable flexibility in an application without requiring code to be recompiled.
A parameter group is a set of parameters that are grouped together by category. This makes it easier for an operator to locate a specific parameter. Each application has a set of parameter groups defined for it. A parameter is part of only one parameter group.
For example, the Point-of-Service Discount group contains all the parameters used for applying discounts. If you need to change a parameter relating to discounts, you can easily find the parameter.
A parameter list is a set of parameters selected by an operator and saved in a stored list for distribution to stores and registers. Using parameter lists enables a retailer to maintain consistent settings for parameters across stores and registers. For example, a list named Holiday Sales could be created with parameter settings specifically used for sales during a holiday season. The parameters can then be distributed to stores so that all stores are using the same values during the holiday sale.
A list can contain parameters from multiple applications and multiple groups. The parameter values can be a mix of default values and values saved by the operator to that particular list.
The application user interfaces enable an authorized user to create lists, change the values of parameters in the list, set the location for the distribution, and distribute the parameters. Lists created in Central Office or Back Office are maintained until removed.
After a parameter list is created, the list is distributed in order for the changes to take effect. Parameter updates are distributed by Central Office to stores selected by hierarchy, individually, or store groups. Back Office distributes parameter updates to all registers or individually selected registers. (The store hierarchy defines where stores fit in the retailer's enterprise. See the Oracle Retail POS Suite Implementation Guide, Volume 1 - Implementation Solutions for more information on setting up a store hierarchy.)
When a distribution job is created, the parameter list contains the parameters and their values that exist at that date and time. To change the values to be distributed, the job must be cancelled, the values changed, and the distribution re-scheduled.
The stores included in a data distribution, when based on a hierarchy or store group selection, are resolved at the date and time when the job is executed. If all registers are selected for a distribution from Back Office, the list of registers is also resolved when the job is executed.
Parameter changes made in Central Office are sent to designated stores and distributed to the registers.
If a parameter distribution is not approved until after the scheduled date and time of the job have passed, an authorized operator can select to run the job immediately.
For more information on setting parameter values and distributing the parameters, see Chapter 2.
Each application has specific uses for parameters:
Point-of-Service uses the parameters to direct register operation.
Back Office uses parameters to control its operation and distributes parameters to registers to direct register operation.
Central Office uses parameters to control its operation and distributes parameters to Back Office applications.
Returns Management uses parameters to control its operation.
Back Office can be used to update the parameters of specific registers in the Point-of-Service system. Central Office can be used to update parameters for both Back Office and Point-of-Service registers. Neither Back Office nor Central Office can determine what parameters are currently in use at a register, but they can distribute new parameters to the registers, overriding older parameters.
Parameters that specifically control the behavior of the Back Office application cannot be distributed from Back Office to registers. Parameters that control the behavior of the Central Office application cannot be distributed from Central Office to Back Office.
A master set is a set of default parameter values for a store or register. Central Office holds a master set containing both Back Office and Point-of-Service parameters. Values that are changed and saved as part of a list for distribution to Back Office or Point-of-Service, do not affect the master set of parameters and their values. To change the defaults in the master set, the operator must specifically import the updates to the master set.
Back Office holds a set of default parameter values that are the master set for all Point-of-Service registers at the store. Each store can have only one master set. Values that are changed and saved as part of a list for distribution to registers, do not affect the master set of parameters and their values. To change the defaults in the master set, the operator must specifically import the updates to the master set held at Back Office.
System configurations are used to control functionality in applications. They are used to control flow in an application and to set allowed values for data entered by users. System configurations also enable flexibility in an application without requiring code to be recompiled. System configurations cannot be changed through the user interface of any of the POS Suite applications.
The structure and format of receipts are stored in XML files. Parameter settings that previously defined receipt content are now defined as receipt components in the XML files. Each type of receipt has its own blueprint file. The blueprint files contain the following fields used for creating receipts:
Data components that set the value of fields printed on receipts
Print control components that determine the number of copies of the receipt to be printed
For more information on blueprint files, see the Oracle Retail POS Suite Implementation Guide, Volume 1 - Implementation Solutions.
