Oracle® Retail POS Suite 14.1/Merchandising 14.1 Implementation Guide Release 14.1 E59307-03 |
|
Previous |
Next |
There are certain functionality gaps that exist in the Oracle Retail POS Suite to Oracle Retail Merchandising System integration that are not remedied at this time. This chapter describes theses functional gaps, and the suggested resolution.
Table 7-1 is a list of functionality gaps that exist for the promotion data import.
Table 7-1 Functionality Gaps for Promotion Data Import
Identified Functionality Gap | Suggested Resolution |
---|---|
Oracle Retail Price Management supports a larger field (Change Value - Number) than does POS Suite. This field is the amount, either monetary or percent, to be used to change or replace the current selling price for a sale unit of an item. Could result in loss of data in case of a very large discount amount is sent to the POS Suite. |
Gap to remain unchanged for this release. |
Oracle Retail Price Management supports a larger Item Number field than POS Suite. |
POS Suite logs an error if the database field is exceeded. |
Field for Promotion Price attribute is larger in Oracle Retail Price Management. If Oracle Retail Price Management is configured to allow overlapping promotions, multiple promotions can be applied, and the selling price represents the results of each promotion applied in the Apply Order. One record is downloaded for each promotion applied, and each has the same selling price. The functionality gap between Oracle Retail Price Management and Point-of-Service results in the POS Suite system only applying the best deal, and it does so at the time the transaction is rung up. |
Avoid creating promotions in Oracle Retail Price Management with prices larger than Point-of-Service can support, DECIMAL(13,2). Oracle Retail Price Management should be configured through the System Options to calculate promotional retail using the "Non-Compounding, Best Deal" option when integrating with the POS Suite. This does not account for the use of Price Guides with RPM, but ensures consistent application of promotion discounts between the two systems. |
Table 7-2 is a list of functionality gaps that exist for the price change data import.
Table 7-2 Functionality Gaps for Price Change Data Import
Identified Functionality Gap | Suggested Resolution |
---|---|
Oracle Retail Price Management supports a longer field (Selling Retail) and more precision. |
Gap to remain unchanged for this release. |
Oracle Retail Price Management supports a longer Item ID field. |
Item ID length remains the same in POS Suite and Oracle Retail Price Management. If the item ID is too long in the download file, the record is logged and discarded. |
Oracle Retail Price Management does not send description field in download file. |
Optional Description field is not populated in Point-of-Service. |
Table 7-3 is a list of functionality gaps that exist for the discount rule data import.
Table 7-3 Functionality Gaps for Discount Rule Data Import
Identified Functionality Gap | Suggested Resolution |
---|---|
Oracle Retail Price Management supports a longer Item ID field. |
Item ID length remains the same in POS Suite and Oracle Retail Price Management. If the item ID is too long in the download file, the record is logged and discarded. |
Oracle Retail Price Management field (Threshold Value) is longer and supports more precision. |
Field length remains the same in Oracle Retail Price Management and POS Suite. If the threshold is a decimal value, it is logged and discarded. |
Oracle Retail Price Management supports larger values and more precision than stores. Meaning of value (%, $, or new price) is defined by Change Type. |
Field length remains the same in Oracle Retail Price Management and POS Suite. |
Oracle Retail Price Management does not support the Accounting Method field. |
Assume the discount. |
Oracle Retail Price Management does not directly support the Deal Distribution field. |
Assume ’target' for all with the exception of Multi-Buy promotions created with no reward list which will be set to ’source target'. |
Target Quantity field is not supported in Oracle Retail Price Management. |
Assume target quantity of 1. |
Table 7-4 is a list of functionality gaps that exist for the clearance data import.
Table 7-4 Functionality Gaps for Clearance Data Import
Identified Functionality Gap | Suggested Resolution |
---|---|
Oracle Retail Price Management supports a longer field (Selling Retail) and more precision. |
Gap to remain unchanged for this release. |
Oracle Retail Price Management supports a longer Item ID field. |
Item ID length remains the same in POS Suite and Oracle Retail Price Management. If the item ID is too long in the download file, the record is logged and discarded. |
Oracle Retail Price Management does not send description field in download file. |
Optional Description field is not populated in Point-of-Service. |
Table 7-5 is a list of functionality gaps that exist in Point-of-Service for Oracle Retail Price Management functionality.
Table 7-5 Functionality Gaps for Item Data Import
Oracle Retail Price Management Functionality | Identified Functionality Gap | Suggested Resolution |
---|---|---|
Oracle Retail Price Management supports multiple promotions if configured to allow them. |
Point-of-Service applies only one promotion at the time of transaction; best deal is applied. |
Oracle Retail Price Management should be configured through the System Options to calculate promotional retail using the "Non-Compounding, Best Deal" option when integrating with the POS Suite. This does not account for the use of Price Guides with RPM, but ensures consistent application of promotion discounts between the two systems. |
Oracle Retail Price Management enables the execution of Finance Promotions. Buy N of X with promoted card, get promotional interest % for Z duration. For example, promotion is set up for Visa Credit Card with a threshold of $1,000 and promotion percentage of 0, with a duration of 18 months (for no interest payments if paid in full within 18 months). |
Point-of-Service does not support Finance Promotion components. |
Gap to remain unchanged for this release. |
Table 7-6 is a list of functionality gaps that exist for the Item import.
Table 7-6 Functionality Gaps for Item Data Import
POS Suite Attribute | Identified Functionality Gap | Suggested Resolution |
---|---|---|
Cost |
Cost data is included in the Point-of-Service download file, from Oracle Retail Merchandising System. However, Point-of-Service does not access item cost data from manufacturer. |
Gap to remain unchanged for this release. |
Manufacturer |
Not included in the Point-of-Service download, but Oracle Retail Merchandising System has this data. |
This value is null. |
Planogram |
Not maintained by Oracle Retail Merchandising System. Oracle Retail Merchandising System has a generic attribute that could be used for this purpose. |
Gap to remain unchanged for this release. |
Restocking Fee |
Not maintained by Oracle Retail Merchandising System. Point-of-Service uses this to prompt for a restocking fee during returns. |
Default to false for Oracle Retail Merchandising System imports. |
Activation Required |
Not maintained by Oracle Retail Merchandising System. |
No attribute in Oracle Retail Merchandising System. Not used by Point-of-Service. |
Registry Eligible |
Not maintained by Oracle Retail Merchandising System. |
No attribute in Oracle Retail Merchandising System. Not used by Point-of-Service. |
Employee Discount Eligible |
Identifies an item as eligible for an employee discount. Not maintained by Oracle Retail Merchandising System. |
Default to true for Oracle Retail Merchandising System imports. |
Damage Discount Eligible |
Identifies an item as eligible for damage discount. Not maintained by Oracle Retail Merchandising System. |
Default to true for Oracle Retail Merchandising System imports. |
Size Entry Required |
Not maintained by Oracle Retail Merchandising System. Point-of-Service uses this attribute during a sale or return to prompt for item size. |
Default to false for Oracle Retail Merchandising System imports. |
Itemizing |
POS Suite assumes item data is interpreted as local time. File creation has the local Oracle Retail Merchandising System time, but no timezone info. |
Assume all Timestamps are relative to GMT. |
Localization |
Oracle Retail Merchandising System data file does not contain localized data for a store. |
Accepts one localized text from Oracle Retail Merchandising System and use as all three: stores, user, customer. |
Table 7-7 is a list of functionality gaps that exist for the Merchandise Hierarchy import.
Table 7-7 Functionality Gaps for Merchandise Hierarchy Data Import
POS Suite Attribute | Identified Functionality Gap | Suggested Resolution |
---|---|---|
Merchant ID |
Oracle Retail Merchandising System does not specify a merchant ID with any of the merchandise classification records sent with the Merchandise Hierarchy download. |
Gap to remain unchanged for this release. |
Table 7-8 is a list of functionality gaps that exist for the Store Hierarchy import.
Table 7-8 Functionality Gaps for Store Hierarchy Data Import
POS Suite Attributes | Identified Functionality Gap | Suggested Resolution |
---|---|---|
Store Class |
POS Suite does not accept class. |
Gap to remain unchanged for this release. |
Store Class Description |
POS Suite does not accept class description. |
Gap to remain unchanged for this release. |
Store Format |
POS Suite does not accept format as part of the data import. |
Gap to remain unchanged for this release. |
Format Name |
Store does not accept format name as part of the data import. |
Gap to remain unchanged for this release. |
Some fields can potentially overflow at the database level because the fields are not specifically limited in length by the Data Import XSDs. The following table lists the XML elements that are affected.
Table 7-9 Affected XML Elements
Import | Elements | Maximum Column Size |
---|---|---|
Currency |
CurrencyImport/Currency@IssuingCountryCode |
VARCHAR(4) |
CurrencyImport/Currency@IssuingCountryCode |
VARCHAR(4) |
|
CurrencyImport/Currency@ISOCode |
VARCHAR(3) |
|
CurrencyImport/Currency@Name |
VARCHAR(250) |
|
CurrencyImport/Currency@IssuingCountryNationality |
VARCHAR(120) |
|
Customer |
CustomerImport/Customer@ID |
VARCHAR(14) |
CustomerImport/Customer@EmployeeID |
VARCHAR(10) |
|
CustomerImport/Customer@PreferredLanguage CustomerImport/Customer@PreferredCountry |
VARCHAR(10) |
|
CustomerImport/Customer@TaxID |
VARCHAR(16) |
|
CustomerImport/BusinessCustomer@CompanyName |
VARCHAR(120) |
|
CustomerImport/BusinessCustomer@TaxExemptionCertificate |
VARCHAR(30) |
|
CustomerImport/BusinessCustomer@ExceptionReason |
VARCHAR(30) |
|
CustomerImport/Customer@LastName |
VARCHAR(120) |
|
CustomerImport/Customer@FirstName |
VARCHAR(120) |
|
CustomerImport/Customer@MiddleName |
VARCHAR(120) |
|
CustomerImport/Customer@Salutation |
VARCHAR(120) |
|
CustomerImport/Customer@Suffix |
VARCHAR(120) |
|
CustomerImport/Customer@BirthDate |
VARCHAR(30) |
|
CustomerImport/BusinessCustomer@CompanyName |
VARCHAR(120) |
|
CustomerImport/Customer/Address@Type |
VARCHAR(30) |
|
CustomerImport/Customer/Address@Address1 |
VARCHAR(240) |
|
CustomerImport/Customer/Address@Address2 |
VARCHAR(240) |
|
CustomerImport/Customer/Address@Address3 |
VARCHAR(240) |
|
CustomerImport/Customer/Address@City |
VARCHAR(120) |
|
CustomerImport/Customer/Address@State |
VARCHAR(30) |
|
CustomerImport/Customer/Address@PostalCode |
VARCHAR(30) |
|
CustomerImport/Customer/Address@Territory |
VARCHAR(120) |
|
CustomerImport/Customer/Address@Country |
VARCHAR(30) |
|
CustomerImport/Customer/Telephone@Type |
VARCHAR(30) |
|
CustomerImport/Customer/Telephone@Ext |
VARCHAR(30) |
|
CustomerImport/Customer/Email@Address |
VARCHAR(64) |
|
CustomerImport/Customer@ID |
VARCHAR(14) |
|
CustomerImport/CustomerGroup/Name |
VARCHAR(120) |
|
CustomerImport/CustomerGroup/Description |
VARCHAR(250) |
|
CustomerImport/CustomerGroup/Name or Description@Language CustomerImport/CustomerGroup/Name or Description@Country |
VARCHAR(10) |
|
CustomerImport/CustomerGroup/Name |
VARCHAR(120) |
|
CustomerImport/CustomerGroup/Description |
VARCHAR(250) |
|
CustomerImport/PricingGroup/LocalizedName@Name |
VARCHAR(120) |
|
CustomerImport/PricingGroup/LocalizedName@Description |
VARCHAR(250) |
|
CustomerImport/PricingGroup/LocalizedName@Language CustomerImport/PricingGroup/LocalizedName@Country |
VARCHAR(10) |
|
CustomerImport/PricingGroup/LocalizedName@Name |
VARCHAR(120) |
|
CustomerImport/PricingGroup/LocalizedName@Description |
VARCHAR(250) |
|
Employee |
Employee > EmployeeFullName |
VARCHAR(250) |
Employee > EmployeeLastName |
VARCHAR(120) |
|
Employee > EmployeeFirstName |
VARCHAR(120) |
|
Employee > EmployeeMiddleName |
VARCHAR(120) |
|
Item |
Item > RetailStoreItem > POSIdentity @SupplierID |
VARCHAR(20) |
PreloadData > Color@Code |
VARCHAR(20) |
|
Item@Color |
VARCHAR(20) |
|
PreloadData > Size@Code |
VARCHAR(10) |
|
Item@Size |
VARCHAR(10) |
|
Merchandise Hierarchy |
PreloadData > MerchandiseGroup > Description |
VARCHAR(250) |
PreloadData > POSDepartment > POSDepartmentID |
VARCHAR(14) |
|
PreloadData > POSDepartment > ParentPOSDepartmentID |
VARCHAR(14) |
|
HierarchyList > Hierarchy@Name |
VARCHAR(250) |
|
HierarchyList > Hierarchy > LevelList > Level@Name |
VARCHAR(120) |
|
HierarchyList > Hierarchy > NodeList > Node@ParentNodeID |
VARCHAR(14) |
|
HierarchyList > Hierarchy > NodeList > Node@ID |
VARCHAR(14) |
|
Pricing |
PricingImport > PriceChange @ID |
VARCHAR(20) |
PricingImport > PriceChange > Item @ID |
VARCHAR(14) |
|
PricingImport > PriceChange > Item @TemplateType |
VARCHAR(8) |
|
PricingImport > PriceChange @TemplateType |
VARCHAR(8) |
|
PricingImport > PricePromotion @ID |
VARCHAR(20) |
|
PricingImport > PricePromotion @TemplateType |
VARCHAR(8) |
|
PricingImport>Clearance@ID |
VARCHAR(20) |
|
PricingImport>Clearance>Item@ID |
VARCHAR(14) |
|
PricingImport>Clearance@TemplateType |
VARCHAR(8) |
|
PricingImport>Clearance>Item@TemplateType |
VARCHAR(8) |
|
PricingImport>ClearanceReset@ID |
VARCHAR(20) |
|
PricingImport>ClearanceReset>Item@ID |
VARCHAR(14) |
|
PricingImport>ClearanceReset@TemplateType |
VARCHAR(8) |
|
PricingImport>ClearanceReset>Item@TemplateType |
VARCHAR(8) |
|
DiscountRule > Sources > Source @ID |
VARCHAR(14) |
|
DiscountRule > Targets > Target @ID |
VARCHAR(14) |
|
ScanSheet |
ScanSheetImport>ScanSheet@ItemID |
VARCHAR(14) |
ScanSheetImport>ScanShee@CategoryID |
VARCHAR(14) |
|
ScanSheetImport>ScanSheet@ComponentType |
VARCHAR(1) |
|
ScanSheetImport>ScanSheet@ParentCategoryID |
VARCHAR(14) |
|
ScanSheetImport>ScanSheetI18N@Locale |
VARCHAR(10) |
|
ScanSheetImport>ScanSheetI18N@CategoryName |
VARCHAR(120) |
|
ScanSheetImport>ScanSheetI18N@ScanSheetImageLocation |
VARCHAR(200) |
|
Store Hierarchy |
PreloadData > StoreRegion > RegionID |
VARCHAR(14) |
PreloadData > StoreRegion > RegionName |
VARCHAR(120) |
|
PreloadData > StoreDistrict > DistrictID |
VARCHAR(14) |
|
PreloadData > StoreDistrict > RegionID |
VARCHAR(14) |
|
PreloadData > RetailStore > GeoCode |
VARCHAR(10) |
|
PreloadData > StoreDistrict > DistrictName |
VARCHAR(120) |
|
PreloadData > RetailStore > LocationName |
VARCHAR(150) |
|
PreloadData > RetailStore > DistrictID |
VARCHAR(14) |
|
PreloadData > RetailStore > RegionID |
VARCHAR(14) |
|
PreloadData > RetailStore > GeoCode |
VARCHAR(10) |
|
PreloadData > RetailStore > Address > AddressLine1 |
VARCHAR(240) |
|
PreloadData > RetailStore > Address > AddressLine2 |
VARCHAR(240) |
|
PreloadData > RetailStore > Address > AddressLine3 |
VARCHAR(240) |
|
PreloadData > RetailStore > Address > City |
VARCHAR(120) |
|
PreloadData > RetailStore > Address > State |
VARCHAR(30) |
|
PreloadData > RetailStore > Address > PostalCode |
VARCHAR(30) |
|
PreloadData > RetailStore > Address > Territory |
VARCHAR(120) |
|
PreloadData > RetailStore > Address > Country |
VARCHAR(30) |
|
PreloadData > RetailStore > Address > TelephoneCountryCode |
VARCHAR(30) |
|
PreloadData > RetailStore > Address > TelephoneAreaCode |
VARCHAR(3) |
|
PreloadData > RetailStore > Address > TelephoneLocalNumber |
VARCHAR(30) |
|
HierarchyList > Hierarchy@Name |
VARCHAR(120) |
|
HierarchyList > Hierarchy > LevelList > Level@Name |
VARCHAR(120) |
|
HierarchyList > Hierarchy > NodeList > Node@Name |
VARCHAR(120) |
|
HierarchyList > Hierarchy > NodeList > Node@Descripton |
VARCHAR(250) |
|
Tax |
GEOCode > GeoCodeID |
VARCHAR(10) |
GEOCode > TaxJurisdictionName |
VARCHAR(120) |
|
GEOTaxJurisdiction > GeoCodeID |
VARCHAR(10) |
|
TaxAuthority > TaxAuthorityName |
VARCHAR(120) |
|
TaxAuthority > GeoCodeID |
VARCHAR(10) |
|
TaxableGroup > TaxGroupName |
VARCHAR(120) |
|
TaxableGroup > TaxGroupDescription |
VARCHAR(250) |
|
TaxAuthority > AddressLine |
VARCHAR(240) |
|
TaxAuthority > City |
VARCHAR(120) |
|
TaxAuthority > State |
VARCHAR(30) |
|
TaxAuthority > PostalCode |
VARCHAR(30) |
|
TaxAuthority > CountryCode |
VARCHAR(30) |
|
TaxGroupRule > TaxTypeName |
VARCHAR(30) |
|
TaxGroupRule > TaxRuleName |
VARCHAR(120) |
|
TaxGroupRule > TaxRuleDescription |
VARCHAR(250) |
The following are known gaps in the Oracle Retail POS Suite to merchandising products integration:
The RTLog does not deliver bank deposit details. Currently ORPOS sends it as Nosale.
Currently the integration for branded debit card transactions fail between POS Suite and Oracle Retail Sales Audit.
Oracle Retail Point-of-Service does not support the CatchWeight attribute for items, so the value of the field will always be set to false by Oracle Retail Point-of-Service.
Retailers are restricted to only creating and using items with two character UOMs (Unit of Measure) as part of this integration.
Oracle Retail Merchandising System transforms EA
(Each) to UN
(Unit) for the UOM in Item extracts to POS Suite.
POS Suite does not transform any other UOM in RTLogs to Oracle Retail Merchandising System.
Oracle Retail Point-of-Service translates UN
back to EA
for the RTLog.
Oracle Retail Point-of-Service will send two CTILL records to the RTLog for Till Close:
one for the reconciliation activity
one for the close activity
Note: See Appendix C, "Appendix: XSD Files and Data Element Definition Tables" for more information about mapping the exported XML files to the import XSDs. This appendix contains tables that call out the maximum bytes for any column. |
For the Store Hierarchy Address attribute, Oracle Retail Merchandising System extracts 240 characters while Data Import accepts only 120 characters.
For Pricing External Event ID, Oracle Retail Price Management extracts 11 characters while Data Import accepts only 10 characters.
Data Import can only accept 2^32-1 maximum value for External Event ID. For example, a value of 9999999999, which fits in a NUMBER(10) datatype, is too big for an integer in Java.
Oracle Retail Merchandising System extracts number(20,4) while Data Import accepts only number(13,4).
For Pricing PriceOverrideAmount, Oracle Retail Price Management extracts absolute of (20,4) while Data Import accepts only up to (13,2).
For Pricing Coupon, Oracle Retail Price Management extracts 250 characters while Data Import accepts only 160 characters.
For Pricing Discount Percent, Discount Amount and New Price, Oracle Retail Price Management extracts an absolute of (20,4) while Data Import accepts only up to (10,4).
Data Import can only accept 2^32-1 maximum value for PricingGroupID. For example, a value of 9999999999, which fits in a NUMBER(10) datatype, is too big for an integer in Java.
Promo Description: Oracle Retail Price Management can extract up to 640 characters, while Point-of-Service accepts only 250 characters.
Promo Name: Oracle Retail Price Management can extract up to 160 characters, while Point-of-Service accepts only 120 characters.
When integrated with Oracle Retail Merchandising System, the PreloadData/POSDepartment/DepartmentDefaultTaxGroup
field in the MerchandiseHierarchyImport is defaulted to 0 (zero). It is the responsibility of the implementation team to update this value in the bundle with a real TaxGroup ID for the department in question before the bundle reaches POS Suite. Otherwise, a primary key violation might occur if zero is not an actual TaxGroup ID in the UDM.
The Discountable attribute for an item imported from Oracle Retail Merchandising System is always set to true.
In Back Office, Available Classes and Assigned Classes lists are empty for an item.
The menu is empty in a merchandising products-integrated environment. The retailer must define these.
Oracle Retail Merchandising System does not send GeoCode information to Point-of-Service and will leave this element intentionally missing. If the GeoCode is missing during import, Data Import will default the store's GeoCode to the PostalCode if the country is US or USA. Otherwise, the GeoCode will default to the CountryCode.
See Oracle Retail Merchandising System Operations Guide - Batch Overviews and Designs - Volume 1 Release 12.0.7 for more information.
Items associated with giftcards are not sent from Oracle Retail Merchandising System. It is the retailer's responsibility to insert gift card associated item data in the item master to use gift card functionality in Point-of-Service.
There can be one item number for each card denomination and one for an open amount gift card.
Point-of-Service sends IGTAX records for both VAT and Sales Tax. Oracle Retail Sales Audit has been modified to recognize transactions in which VAT has been charged. It does not include tax in the transaction balancing calculation.
Layaway Deletion Fee is sent to Oracle Retail Sales Audit as Non-Merchandise-Item which is not accepted by Oracle Retail Sales Audit.
Oracle Retail Sales Audit expects Layaway Deletion Fee to be delivered as a record type TTEND. Instead, it is sent as a record type TITEM.
A non-merchandise-item (nmitem) may be created for this fee and mapped in ORPOS.
It is assumed that clients will generate their key. So a key file is not part of the release. POS Suite generates the key (file) and Oracle Retail Merchandising System reads the key from the file.
Oracle Retail Sales Audit expects NM ITEM codes for the NM ITEMS sent for cases similar to the following:
Layaway fee
Layaway delete fee
Shipping charges
Item restocking fee
The RTLogFormat.xml file should be modified so that the following lines are modified to contain the Item ID defined in Oracle Retail Merchandising System for each of these types of items:
<FIELD_FORMAT name="NonMerchandiceItem" type="char" length="25" value="LAYAWAY CREATE FEE ITM ID"/> <FIELD_FORMAT name="NonMerchandiceItem" type="char" length="25" value="LAYAWAY DELETE FEE ITM ID"/> <FIELD_FORMAT name="NonMerchandiceItem" type="char" length="25" value="SHIPPING CHARGE"/> <FIELD_FORMAT name="NonMerchandiceItem" type="char" length="25" value="RESTOCKING FEE"/>
When an item is imported without a POSDepartmentID, that particular item not associated with a POSDepartment. When the item is viewed in Back Office, the POSDepartment list defaults its selection to the first department in the list.
POS Suite permits a store postal code up to 30 characters. But POS Suite expects a US postal code to be a five digit number.
Validation in the POS Suite backend is done to ensure that US postal code is a five digit number.
Any data created in Oracle Retail Merchandising System that does not satisfy these conditions causes the POS Suite uploads to fail.
Store IDs reflect physical store locations. The integration infrastructure must route data objects from Oracle Retail Merchandising System to the appropriate physical store location servers using Store ID.
Data created in Oracle Retail Merchandising System using store IDs that are not configured as Stores in the POS Suite results in this data being ignored by POS Suite.
Table 7-10 shows the default values of attributes when integrating Back Office with Oracle Retail Price Management:
XML extracts varchar2(30) while XSD accepts timestamp(9).
XML extracts only number(10) while XSD accepts upto number(22).
Right now, the java data type is int (2^32) and cannot take values greater than 4294967295 (NUMBER 10 in the database).
All reason codes for discount rules are imported from Oracle Retail Price Management with a value of -1.
When new discount rules are created using Back Office, reason codes are generated using the TypeCode ID, which have a value between 1 and 13. The TypeCode ID is translated into a different attribute value during an RTLog extract to Oracle Retail Sales Audit. For example, because Back Office inserts the TypeCode ID into the ReasonCode column, a typecode of BuyNoOfXGetYAtZ%Off will cause ID 4 to be inserted as a ReasonCode for a new rule. During RTLog extract, a 4 is translated as ORRCMS.
Currently, all third-party Tax and Employee information must be presented in a specific file format for consumption by Central Office.
Implementation team need to be aware of this file format.
Tax and Employee files each have an XML Schema Definition just like other Data Imports. For more information about Tax and Employee XML Schema Definitions, see Appendix C, "Appendix: XSD Files and Data Element Definition Tables".
The integration with Oracle Retail Sales Audit requires that tills are only opened and closed once per business day.
The same Total ID is used for more than one till. This causes the following error message in Oracle Retail Sales Audit:
Duplicate declaration: this total id has already been used by another transaction xxxxx.