| Oracle® Invoice Matching Cloud Service Operations Guide Release 16.0.21 E87300-02 |
|
 Previous |
 Next |
| Oracle® Invoice Matching Cloud Service Operations Guide Release 16.0.21 E87300-02 |
|
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 converts the unit of measure (UOM) on the receipt to the UOM on the invoice.
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.REIM_IND) is set to no. Instead, non-merchandise codes should be added to the NON_MERCH_CODE_HEAD table using the database.
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.
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.
The property file has only technical configurations that are specific to the particular deployment. All the business related configurations are located within the system option scope.
The following properties are configurable
#help settings
help.server.url - Help server URL
reim.help.library - path to the ReIM specific help deck
reim.release.version - help version
reim.help.url.suffix -help URL suffix identifying specific document within the library
reim.help.default.url.suffix -default page within the document
#JMS settings
reim.jms.connection.factory.name -name of the JMS factory within JNDI tree on WL used for spreadsheet induction
reim.jms.queue.doc.induction.name - name of the JMS queue within JNDI tree on WL used for spreadsheet induction
reim.jms.application.code- Application code identifier used for JMS publishing
#Notification settings
reim.jdbc.raf.async.task- name of the data source within JNDI tree on WL used for async publishing
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.
Please note that Log4j is used for batch clients only. Server logging is done using standard WbLogic logging infrostracture.
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 for batch clients.
Table 2-1 Log4J Parameters
| Parameter | Description |
|---|---|
|
log4j.appender.BATCHFILE |
Type of file appender. |
|
log4j.appender.BATCHFILE.File |
Path to the log file where batches will write log entries. |
|
log4j.appender.BATCHFILE.DatePattern |
Date pattern for log file. |
|
log4j.appender.BATCHFILE.Append |
Indicator if the log should append entries to the existing file. |
|
log4j.appender.BATCHFILE.Threshold |
Logging threshold level. |
|
log4j.appender.BATCHFILE.layout |
Pattern layout for log entry. |
|
log4j.appender.BATCHFILE.layout.ConversionPattern |
Pattern for log entry. |
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.
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
To set the language ReIM displays in, set the user language. Choose Preferences from the drop-down menu under the user name, then choose Language in the taskbar. There are two language settings you can choose:
Default: This will permanently change the language for this user. All subsequent sessions will be in this language.
Current Session: This will change the language only for this session. It will revert back to the Default the next time this user logs in.
When finished making your selections, click the Save button.
ReIM allows the user to see dates and times in a format appropriate for their own locale, regardless what the data is stored in. Set the language ReIM displays in, set the user language. Choose Preferences from the drop-down menu under the user name, then choose Regional in the taskbar. There are multiple settings you can choose:
Territory: Choose a territory from this list. ReIM will automatically pick Date, Time, and Number formats appropriate for that territory.
Date Format: Choose an option from this menu to select a date format that is different from the default for the selected Territory.
Time Format: Choose an option from this menu to select a time format that is different from the default for the selected Territory.
Number Format: Choose an option from this menu to select a number format that is different from the default for the selected Territory.
Time Zone: Choose an option from this menu to select your time zone.
When finished making your selections, click the Save button.
Most user interface and message translations are stored in .java files. When you select a different language from the Preferences screen, ReIM will choose the correct .java files for that language.
Some translations for some drop-down menus are stored on four database tables. The tables are RTC_LOOKUP_VALUES_TL, RTC_LOOKUP_TYPES_TL, RAF_FACET_ATTRIBUTE_CFG_TL, and RAF_NOTIFICATION_TYPE_TL. These tables are multilingual; all languages of these strings (English as well as all translations) are stored in the same place.
This file contains a key value pair for some of the labels 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). Some other sources of translatable data is used within the system such as XLIF files and database tables.
