| Oracle® Invoice Matching Operations Guide Release 13.2.9 E73506-01 |
|
 Previous |
 Next |
This chapter of the operations guide is intended for administrators who provide support and monitor the running system.
The content in this chapter is not procedural, but is meant to provide descriptive overviews of the key system parameters that establish the ReIM environment.
See the Oracle Retail Invoice Matching Installation Guide for hardware and software requirements. Also see Oracle Retail application software compatibility information.
Unit of Measure
For invoices sent from RMS with quantities representing weight rather than number of eaches, ReIM assumes that the unit of measure (UOM) on the invoice and the UOM on the receipt are always the same and equal to the cost unit of measure (CUOM). (Unit of measure is not displayed on the invoice nor on the receipt.)
ReIM expects all invoices to be in eaches or the standard unit of measure (SUOM) converted to eaches. No other units of measure can be invoiced using ReIM.
ReIM uses non-merchandise codes defined on the RMS table NON_MERCH_CODE_HEAD. The form that allows users to enter non-merchandise codes in RMS is not available when the RMS invoice match indicator (SYSTEM_OPTIONS.INVC_MATCH_IND) is set to no. Instead, non-merchandise codes should be added to the NON_MERCH_CODE_HEAD table using the database.
A record must be inserted into the IM_SYSTEM_OPTIONS table in order to allow successful login to the application.
Supplier options
All suppliers must have options defined for their invoices to be processed by the system, and the terms defined for those suppliers must be completely updated in RMS. To support the use of suppliers in ReIM, terms must have the following properties on the TERMS_DETAIL table:
ENABLED_FLAG is set to Y.
START_DATE_ACTIVE must be defined.
END_DATE_ACTIVE must be defined.
GL account maintenance
All reason codes, non-merchandise codes, and basic transactions must be mapped through GL account maintenance to support posting to the retailer's financial solution. Transactions are posted to a staging table in ReIM, the extract to update the accounts payable/financial solution is the retailer's responsibility.
Multiview
The Document Find, Group Entry List, and Group Entry pages allow the retailer to define how certain fields display in these screens. The Multiview functionality allows the user to move fields around on the pages and save those views for future use. In order for Multiview to work and for these screens to populate correctly, IM_GLOBAL_PREFERENCES must be populated.
TAX
If TAX is turned on, the retailer must have TAX regions, TAX items, and TAX codes set up in the merchandising system (such as RMS) to support validation of invoiced TAX charges. Verify the following values on the IM_SYSTEM_OPTIONS table:
|
Note: The values below should not be changed after initial setup. Changing them can cause errors in the system. |
NUM_TAX_ALLOW is set to S (single) TAX, N (no) TAX.
TAX_VALIDATION_TYPE is set to RECON (Reconcile TAX), VENDR (Always Use Vendor TAX), or RETLR (Always use Retail TAX).
The DEFAULT_TAX_HEADER is set to Y or N.
TAX_DOCUMENT_CREATION_LVL is set to ITEM or FULL_INVOICE.
Retailer-defined configurations for ReIM are located in the reim.properties file. Every setting in the reim.properties file is configurable, according to the retailer's specific business requirements. Some of these settings also are discussed in the Internationalization section later in this chapter.
The key system parameters contained in this file are described in the tables below. Although default values are given in some instances, retailers are responsible for setting these fields appropriately for their installation and hardware profile, rather than assuming these default values are the best choice.
These settings are dependent on the retailer's unique database installation, except for the bean driver, which should remain at the default value (unless customization is performed.)
| Parameter | Description | Comments |
|---|---|---|
|
datasource.url |
The URL connection string used to connect to the database |
|
|
datasource.schema.owner |
The owning schema used to resolve database types. |
|
|
datasource.bean.driver |
The bean driver for this installation. This should not change unless customization has been performed. |
Default is com.retek.reim.foundation.rms12. |
|
datasource.credential.alias |
The alias for data source credentials. |
For example, USERALIAS. |
These settings are dependent on the retailer's implementation. The pool size refers to the number of available database connections that the retailer intends to keep available.
| Parameter | Description | Comments |
|---|---|---|
|
pool.name |
Default is reim. |
|
|
pool.min |
The least number of database connections available, based on anticipated number of users. |
Default is 20. |
|
pool.max |
The highest number of database connections available, based on anticipated number of users. |
Default is 200. |
|
pool.connectionWait |
Default is 5. |
|
|
pool.propertyCheckInterval |
Sets the time interval. The cache daemon thread "sleeps" between checks to enforce the timeout limits. |
Default is 900 (seconds). |
|
pool.timeToLiveTimeout |
Sets the minimum time, in seconds. A checked-out connection can remain outside of the cache before it becomes a candidate to be closed by the connection cache thread. |
For example, 1200. Default is 0, which disables timeout. |
|
pool.inactivityTimeout |
Sets the minimum time, in seconds. A connection can remain idle before it becomes a candidate to be closed by the connection cache thread when the current cache size is greater than the pool minimum. |
For example, 600. Default is 0, which disables timeout. |
|
pool.abandonedConnectionTimeout |
Sets the minimum time, in seconds. A checked-out connection can remain unused (no SQL activity) before it becomes a candidate to be closed by the connection cache thread. |
For example, 900. Default is 0, which disables timeout. |
| Parameter | Description | Comments |
|---|---|---|
|
document.search.records. |
The maximum number of documents to be returned by the document search screens. This value will depend on the hardware profile. (Integer) |
Default is 10000. |
|
document.quantity.decimals.allowed |
The decimal precision to which quantity is stored on a document. Typically used by grocery retailers. Value is expressed as an integer. For example, to display 4 decimals, this property is set to 4. |
Default is 0. |
|
document.batch.date.format |
The date format used for processing and validating EDI files. (String) |
Default format is yyyyMMddHHmmss. |
|
document.header.quantity. |
For documents that contain a supplier that does not belong to a supplier group, the value of this field dictates if the total header quantity is required on that document. (Integer) |
Default is true. |
|
document.rtv.extdocid. |
Character used to differentiate similar external document IDs for EDI upload. It allows documents with external document IDs already in use to pass EDI validation. Value must be a valid invoice number character, as defined by the parameter, document.validation.regexpr. If not, the underscore character is defaulted. (Character) |
If this property is set to 1, for example, a posted document with an external ID of MYDOC will be named MYDOC_1. Default is _. |
|
document.validation. |
Indicates the characters allowed in an external document (invoice) ID. For example, 0-9, A-Z, space, minus sign, plus sign and underscore. If this property is omitted, the system defaults the setting to alphanumeric. The document.rtv.extdocid.separator value is validated against this field. (String) |
For example, ^[0-9A-Za-z\ \+\-\_]+$ Default is alphanumeric, expressed as \\p{Alnum}+ |
|
document.number.allow. |
Indicates whether document IDs may be entered with a leading zero. |
Valid values: true - document IDs may be entered with a leading 0. false - document IDs may NOT be entered with a leading 0. |
|
document.purge.deals.days |
Indicates when to purge deals from the Invoice Matching tables after they have been successfully uploaded (in number of days). This field is read during the purge batch. |
Default is 10. |
| Parameter | Description | Comments |
|---|---|---|
|
date.cache.poll.interval |
This parameter dictates how frequently the system updates the stored VDATE. (Integer) |
Default is 15 minutes, expressed as 900000. (1000 * 60 * 15 = 900000) |
This setting establishes the size of the batch updates to the database. The value is expressed in number of records.
|
Note: The EDI invoice upload batch process does not use this property. The setting, edi.docbulk.size, is used instead. |
| Parameter | Description | Comments |
|---|---|---|
|
ARRAY_PROCESS_SIZE |
The threshold representing the maximum number of records to be part of a single INSERT or UPDATE operation in classes created by the DALGenerator. (Integer) |
Default is 30. |
| Parameter | Description | Comments |
|---|---|---|
|
edi.data.generator.path |
The path used for the data generator files. (Ignore in production.) (String: @deploy.data.path@) |
|
|
edi.default.location |
The default location assigned to non-merchandise invoices when they come in. (Integer) |
Default is 10000000001. |
|
edi.default.department |
The default department assigned to non-merchandise invoices when they come in |
Default is 1414. |
|
edi.default.class |
The default class assigned to non-merchandise invoices when they come in |
Default is 1000. |
|
edi.upload.multithreaded |
Indicates whether EDI uploads are single-threaded (False) or multi-threaded (True). |
Default is true. |
|
edi.docbulk.size |
The maximum number of documents that EDI will process before issuing an INSERT statement. |
Default is 1000. |
These settings express the number of seconds until the timeout occurs. Variables are in milliseconds. Conversion: millisecond = 1; second = 1000; hour = 3600000; day = 86400000; month = 25992000000; no_expire = -1.
Invoice Matching locks records at the application level to prevent multiple users from manipulating the same data. The following settings dictate how long locks on these records can be maintained before timing out. Use any mathematical expression with the time units listed above. For example, 1 * hour.
| Parameter | Description | Comments |
|---|---|---|
|
business_roles_lock_timeout |
Amount of time until the user's control of (or lock on) the business_roles table ends (times out). |
Default is 1 * hour. |
|
reason_codes_lock_timeout |
Amount of time until the user's control of (or lock on) the reason_codes table ends (times out). |
Default is 1 * hour. |
|
doc_group_list_lock_timeout |
Amount of time until the user's control of (or lock on) the doc_group_list table ends (times out). |
Default is 12 * hour. |
|
doc_head_lock_timeout |
Amount of time until the user's control of (or lock on) the doc_head_lock table ends (times out). |
Default is no_expire. |
|
edi_reject_doc_lock_timeout |
Amount of time until the user's control of (or lock on) the edi_reject_doc table ends (times out). |
Default is 1 * hour. |
|
supplier_options_lock_timeout |
Amount of time until the user's control of (or lock on) the supplier_options table ends (times out). |
Default is 1 * hour. |
|
system_options_lock_timeout |
Amount of time until the user's control of (or lock on) the system_options table ends (times out). |
Default is 1 * hour. |
|
tolerance_dept_lock_timeout |
Amount of time until the user's control of (or lock on) the tolerance_dept table ends (times out). |
Default is 1 * hour. |
|
tolerance_supp_lock_timeout |
Amount of time until the user's control of (or lock on) the tolerance_supp table ends (times out). |
Default is 1 * hour. |
|
tolerance_supp_trait_lock_timeout |
Amount of time until the user's control of (or lock on) the tolerance_supp_trait table ends (times out). |
Default is 1 * hour. |
|
tolerance_system_lock_timeout |
Amount of time until the user's control of (or lock on) the tolerance_system table ends (times out). |
Default is 1 * hour. |
|
receipt_lock_timeout |
Amount of time until the user's control of (or lock on) the receipt_lock table ends (times out). |
Default is 1 * hour. |
|
parent_invoice_lock_timeout |
Amount of time until the user's control of (or lock on) the parent_invoice table ends (times out). |
Default is 1 * hour. |
Thread pool sizing guidelines are as follows:
Nthreads = optimal number of threads
Ncpu = number of available CPUs
Ucpu = target CPU utilization, 0 <= Ucpu <=1
W/C = ratio of wait time to compute time
Nthreads = Ncpu * Ucpu * (1 + ((W/C))
| Parameter | Description | Comments |
|---|---|---|
|
thread.creditnoteautomatch batch.multithreaded |
Indicates whether credit note automatch batch processing is in single-threaded mode (False) or multi-threaded mode (True) |
Valid values are: true - multi-threaded mode false - single-threaded mode |
|
thread.creditnoteautomatch batch.consumerThreadKeep Alive |
The amount of time (in milliseconds) that the batch will keep threads alive after they have completed processing when the current number of runnable threads exceeds the minimum pool size. |
Default is 60000. |
|
thread.creditnoteautomatch batch.consumerThread PoolMin |
Minimum thread pool size. |
Default is 10. |
|
thread.creditnoteautomatch batch.consumerThread PoolMax |
Maximum thread pool size. |
Default is 20. |
| Parameter | Description | Comments |
|---|---|---|
|
creditnoteautomatchbatch. |
This setting determines whether IM_MATCH_* tables are purged after the Credit Note AutoMatch Batch runs. If not purged, data from the previous matching batch process will remain in the workspace tables. |
Valid values are: true - After the Credit Note AutoMatch Batch runs, data is purged from IM-MATCH_* tables (except for IM_MATCH_*_HIST). false - After the Credit Note AutoMatch Batch runs, data remains in the workspace tables. |
| Parameter | Description | Comments |
|---|---|---|
|
thread.invoiceautomatch batch.threadBy |
Indicates the criteria on which invoice automatch threading is based. This setting is depends on the hardware profile and the volume of the thread by groups in implementation (such as areas, locations, and chains). Value should be determined through testing. (String) |
Valid values are: NoThread ThreadByLocation ThreadByDistrict (default) ThreadByRegion ThreadByArea ThreadByChain |
|
invoiceautomatchbatch. process.locks |
Indicates whether the automatch batch process should exclude locked documents. |
Valid values are: true - Locked documents are excluded from matching. false - Locked documents are included in matching. |
These threadings settings are expressed in milliseconds. They are utilized by the EdiUpload process and the Invoice AutoMatch batch process.
| Parameter | Description | Comments |
|---|---|---|
|
thread.backgroundThread |
The amount of time the log-writing thread polls the empty work queue before shutting down. Used only by EdiUpload for rejection files. |
Default is 1800000. |
|
thread.consumerThreadTimeout |
The amount of time the consumer pool threads. Used for executing the transactions for both EdiUpload and AutoMatch. |
Default is 60000. |
|
thread.consumerThreadKeepAlive |
thread.consumer ThreadKeepAlive The amount of time (in milliseconds) that the batch will keep threads alive after they have completed processing when the current number of runnable threads exceeds the minimum pool size. |
Default is 60000. |
|
thread.consumerThreadPoolMin |
Minimum thread pool size. |
Default is 10. |
|
thread.consumerThreadPoolMax |
Maximum thread pool size. |
Default is 100. |
Invoice Matching caches (or stores) translated descriptions for item names and supplier names, for example.
| Parameter | Description | Comments |
|---|---|---|
|
translation.caches_refresh_interval_in_seconds |
The number of seconds that elapse before the translation cache is refreshed. |
Default is 43200. |
|
translation.locations_desc_cache_size |
The number of entries within the locations' description cache that the system is allowed to use for processing of translated information. |
Default is 100000. |
|
translation.suppliers_desc_cache_size |
The number of entries within the suppliers' description cache that the system is allowed to use for processing of translated information. |
Default is 100000. |
|
translation.items_desc_cache_size |
The number of entries within the items' description cache that the system is allowed to use for processing of translated information. |
Default is 100000. |
These settings are used only for installation. After installation, they can be changed by manually altering the logging configuration in log4j.properties.
| Parameter | Description | Comments |
|---|---|---|
|
log.online.file |
Used to define the path for generating log files. |
|
|
log.batch.file |
Establishes the name and directory of the batch log file. |
|
|
log.batch.error.file |
Establishes the name and directory of the batch error files. All errors and routine processing messages for a given program on a given day go into this error file. |
|
|
log.level |
Indicates the lowest level at which messages should be logged. For example, if value=4, all errors labeled warn, error and fatal are logged. |
Valid values are: 2 - fatal 3 - error 4 - warn 5 - validation 6 - info 7 - debug 8 - performance 999 - unknown |
These settings pertain to user security privileges.
| Parameter | Comments |
|---|---|
|
authentication_source |
Valid values are: LDAP |
|
IConnectionSettingsDAO |
Default is: com.retek.reim.merch.utils.PropertyFileLdap SettingsDao |
|
ISecurityDao |
Default is: com.retek.reim.merch.utils.ReIM LdapSecurityDao |
|
ISecurityRelationshipDAO |
Default is: com.retek.reim.merch.utils.LDAP SecurityRelationshipDAO |
|
security.ssl_mode |
Default is 2. |
|
security.port_non_ssl |
Default is 8080. |
|
security.port_ssl |
Default is 8443. |
|
sso_url |
N/A |
|
sso_conf |
N/A |
|
sso_util |
N/A |
|
sso_factory_initial |
N/A |
These settings pertain to the online help URL.
| Parameter | Description | Comments |
|---|---|---|
|
online.help.url |
Represents the URL for online help. |
These settings pertain to credential store management (CSM).
| Parameter | Description | Comments |
|---|---|---|
|
csm.wallet.path |
Specifies the path on which the wallet resides. |
Any path on a filesystem . For example, J:/wallet-store. |
|
csm.wallet.partition.name |
Name of the partition inside the wallet, where user name/passwords are mapped against an alias name. |
For example, reim13. |
This file includes system options settings that cannot be accessed through the graphical user interface (GUI), because they cannot be changed once ReIM has been implemented.
The parameters in this section of the file determine whether the retailer's segments for the IM_GL_OPTIONS table are dynamic or non-dynamic. Rather than being hard-coded, dynamic segments are populated by company/location or department/class numbers from the invoice. This reduces the amount of maintenance necessary to support posting to the retailer's financial solution.
If the retailer's segments are non-dynamic, all settings are N.
If the retailer's segments are dynamic, note the following:
The system allows a maximum of four dynamic segments.
Those GL options that are dynamic can be set up to represent the following
Company
Location
Department
Class
|
Note: Company and location are always paired together, and department and class are always paired together. |
The table below illustrates how dynamic GL options are set up to correspond with the retailer's hierarchy parameters. Where mapping occurs, the GL option assumes the value of the corresponding parameter, as determined by the invoice.
| GL Options | Business Concept Mapping for Dynamic Segments |
|---|---|
|
system.gl_option_dynamic_1=Y |
system.gl_option_dynamic_mapping_1=COMPANY |
|
system.gl_option_dynamic_2=Y |
system.gl_option_dynamic_mapping_2=LOCATION |
|
system.gl_option_dynamic_3=N |
system.gl_option_dynamic_mapping_3= |
|
system.gl_option_dynamic_4=Y |
system.gl_option_dynamic_mapping_4=DEPARTMENT |
|
system.gl_option_dynamic_5=Y |
system.gl_option_dynamic_mapping_5=CLASS |
|
system.gl_option_dynamic_6=N |
system.gl_option_dynamic_mapping_6= |
|
system.gl_option_dynamic_7=N |
system.gl_option_dynamic_mapping_7= |
|
system.gl_option_dynamic_8=N |
system.gl_option_dynamic_mapping_8= |
|
system.gl_option_dynamic_9=N |
system.gl_option_dynamic_mapping_9= |
|
system.gl_option_dynamic_10=N |
system.gl_option_dynamic_mapping_10= |
|
system.gl_option_dynamic_11=N |
system.gl_option_dynamic_mapping_11= |
|
system.gl_option_dynamic_12=N |
system.gl_option_dynamic_mapping_12= |
|
system.gl_option_dynamic_13=N |
system.gl_option_dynamic_mapping_13= |
|
system.gl_option_dynamic_14=N |
system.gl_option_dynamic_mapping_14= |
|
system.gl_option_dynamic_mapping_15= |
|
|
system.gl_option_dynamic_mapping_16= |
|
|
system.gl_option_dynamic_mapping_17= |
|
|
system.gl_option_dynamic_mapping_18= |
|
|
system.gl_option_dynamic_mapping_19= |
|
|
system.gl_option_dynamic_mapping_20= |
The table below provides a list of default action codes, based on document type.
| Parameter | Description | Action Code Default |
|---|---|---|
|
CRDNT |
Credit Note |
|
|
CRDNRC |
Credit Note Request Price |
CBC |
|
CRDNRQ |
Credit Note Request Quantity |
CBQ |
|
CRDNRT |
Credit Note Request TAX Valid Values: CNRTI, if IM_SYSTEM_OPTIONS.TAX_DOCUMENT_CREATION_ LVL = ITEM CNRTF, if IM_SYSTEM_OPTIONS.TAX_DOCUMENT_CREATION_ LVL = FULL INVOICE |
CNRTI |
|
CRDMEC |
Credit Memo Price |
CMC |
|
CRDMEQ |
Credit Memo Quantity |
CMQ |
|
DEBMEC |
Debit Memo Price |
CBC |
|
DEBMEQ |
Debit Memo Quantity |
CBQ |
|
DEBMET |
Debit Memo Tax Valid Values: DMTI, if IM_SYSTEM_OPTIONS.TAX_DOCUMENT_CREATION_ LVL = ITEM DMTF, if IM_SYSTEM_OPTIONS.TAX_DOCUMENT_CREATION_ LVL = FULL INVOICE |
DMTI |
When a parent invoice enters the system, the system can split the invoice into its child invoices. (A parent invoice can contain many locations; a child invoice contains only one.) The retailer determines a string, which the system uses to label a child invoice. This string contains the parent invoice ID plus the system.child_invoice_indicator value plus the location number to which the child invoice is associated.
| Parameter | Description | Default |
|---|---|---|
|
system.child_invoice_indicator |
Used in conjunction with the parent invoice ID and location number to label a child invoice. |
LOC |
The parameter determines how many days the system retains audit trail data before it is purged.
| Parameter | Description | Default |
|---|---|---|
|
system.purge_tolerance_audit_period |
Number of days the system retains audit trail data before it is purged |
3 |
These options indicate types of language translation within the system.
| Parameter | Description | Default |
|---|---|---|
|
system.language_translation_active |
Determines whether the system will perform language translation. |
False |
| system.single_language_translation |
Determines whether the system will perform single-language data translation. |
SL |
| system.multiple_language_translation |
Determines whether the system will perform multi-language data translation. |
ML |
| system.item_description_language_option |
Determines whether the system will perform single-language multi-language data translation of the Description parameter. |
SL |
| system.location_name_language_option |
Determines whether the system will perform single-language multi-language data translation of the Location parameter. |
SL |
|
system.supplier_name_language_option |
Determines whether the system will perform single-language multi-language data translation of the Name parameter. |
SL |
| Parameter | Description | Default |
|---|---|---|
|
system.default_set_of_books_id |
The default label assigned to the retailer's set of books. |
1 |
| Parameter | Description | Default |
|---|---|---|
|
system.duplicate_items_lov |
Determines whether the same item from a different supplier can appear more than once in the item list of values (LOV). |
Y |
| Parameter | Description | Default |
|---|---|---|
|
system.maximum.segments |
Determines the maximum number of segments supported by the system. |
20 |
Oracle Retail Invoice Matching utilizes the industry-standard Apache Log4j logging framework to log system messages and exceptions. This framework is embedded in the application code to allow for configurable logging to suit the needs of the retailer.
The Log4j API system utilizes three main configurable entities:
Loggers
Appenders
Layouts
Loggers are responsible for defining exactly what gets logged. Typically, loggers define a specific level of detail (the log level) for a specific java package name as well as an appender the logger is assigned to. These criteria are then delegated to the appropriate appender for the specific logger. A single logger can be assigned to multiple appenders.
Appenders are used to dictate where logged content is directed to for a given logger. For example, the retailer may wish to configure a log appender to publish a log to a database table, a flat file, or an e-mail address. For each of these options, a separate appender would be defined and assigned to a specific logger.
Layouts are leveraged by the appender to dictate the exact content of the log message. Relevant information may include: date, time, and origin of the error message. These values can all be configured through the log layout.
The log4j.properties file holds all of the information relevant to logging throughout the application. Oracle Retail Invoice Matching ships with a sample log configuration that will log basic messages to a standard file located on the application host machine. Retailers wishing to configure specific Invoice Matching loggers should consult the sample configuration log4j.properties file and the Apache Log4j documentation (http://logging.apache.org/log4j).
Internationalization is the process of creating software that is able to be translated more easily. Changes to the code are not specific to any particular market. ReIM has been internationalized to support multiple languages.
This section describes configuration settings and features of the software that ensure that the base application can handle multiple languages. See also "Java Currency Formatting" in Chapter 6, "Technical Design."
Translation is the process of interpreting and adapting text from one language into another. Although the code itself is not translated, components of the application that are translated may include the following:
Graphical user interface (GUI)
Error messages
The following components are not translated:
Documentation (online help, release notes, installation guide, user guide, operations guide)
Batch programs and messages
Log files
Configuration tools
Reports
Demonstration data
Training materials
The user interface for ReIM has been translated into:
Chinese (simplified)
Chinese (traditional)
Croatian
Dutch
French
German
Greek
Hungarian
Italian
Japanese
Korean
Polish
Portuguese (Brazilian)
Russian
Spanish
Swedish
Turkish
The reim.properties file points the application to the location of the user's properties file based on the locale specified for the user in LDAP.
The properties files ReIMResources and ReIMMessages must include the translations for all user interface strings. The translated properties files are identified by the ISO language code for each language. For example: ReIMResources_de.properties contains the German language resources. Translated properties files for Brazilian Portuguese and Traditional Chinese are further differentiated by the ISO language + country code. For example: ReIMResources_pt_BR.properties for Brazilian Portuguese and ReIMResources_zh_TW.properties for Traditional Chinese.
The Java compiler and other Java tools can only process files which contain Latin-1 and/or Unicode-encoded (\udddd notation) characters. The JDK native2ascii tool converts files which contain other character encodings into files containing Latin-1 and/or Unicode-encoded characters. The translated properties files are all shipped in the Unicode-encoded (\udddd notation).
The system's date formats support either two or four digit year designations. Date formats support month name abbreviations or month numbers. Date formats support limited sequencing: year-month-day, month-day-year, and day-month-year. Date formats support either '-' (dash) or '/' (back slash) delimiters. Date formats must be specified in the DateParameters.properties file.
To enhance the system's performance speed, the system utilizes a cache when performing data translations into another language.
For example, suppose the system has been configured to offer French translations. When a French user encounters a location name, the system retrieves the translated location name from the database and then stores it in a cache. If the system needs to retrieve the same translated location name at a later time (for another user, for example), the system would retrieve it from the cache rather than from the database. This reim.properties value represents the number of entries within the cache that the system is allowed to use for such processing.
For example:
translation.items_desc_cache_size=100000
See Electronic Data Interchange (EDI) Tables and Files in Chapter 5, "Integration."
This file contains a key value pair for every label visible through the GUI at run time. Text labels and error messages have been identified, separated from the core source code, and placed into the properties file. The contents of the file can be used for retailer-specific configuration purposes (such as for the creation of custom labels or error messages).
