Beruflich Dokumente
Kultur Dokumente
January 2018
Oracle® Retail Xstore Point of Service, Host Interface Guide, Release 17.0
E91883-01
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
Primary Author: A. Meske
This software and related documentation are provided under a license agreement containing
restrictions on use and disclosure and are protected by intellectual property laws. Except as
expressly permitted in your license agreement or allowed by law, you may not use, copy,
reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or
display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be
error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing
it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated
software, any programs installed on the hardware, and/or documentation, delivered to U.S.
Government end users are “commercial computer software” pursuant to the applicable Federal
Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication,
disclosure, modification, and adaptation of the programs, including any operating system,
integrated software, any programs installed on the hardware, and/or documentation, shall be
subject to license terms and license restrictions applicable to the programs. No other rights are
granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications,
including applications that may create a risk of personal injury. If you use this software or
hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe,
backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its
affiliates disclaim any liability for any damages caused by use of this software or hardware in
dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC
trademarks are used under license and are trademarks or registered trademarks of SPARC
International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or
registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open
Group.
This software or hardware and documentation may provide access to or information on content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible
for and expressly disclaim all warranties of any kind with respect to third-party content, products,
and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to
your access to or use of third-party content, products, or services, except as set forth in an
applicable agreement between you and Oracle.
Value-Added Reseller (VAR) Language
Oracle Retail VAR Applications
The following restrictions and provisions only apply to the programs referred to in this section
and licensed to you. You acknowledge that the programs may contain third party software (VAR
applications) licensed to Oracle. Depending upon your product and its version number, the VAR
applications may include:
(i) the MicroStrategy Components developed and licensed by MicroStrategy Services Corporation
(MicroStrategy) of McLean, Virginia to Oracle and imbedded in the MicroStrategy for Oracle
Retail Data Warehouse and MicroStrategy for Oracle Retail Planning & Optimization applications.
(ii) the Wavelink component developed and licensed by Wavelink Corporation (Wavelink) of
Kirkland, Washington, to Oracle and imbedded in Oracle Retail Mobile Store Inventory
Management.
(iii) the software component known as Access Via™ licensed by Access Via of Seattle, Washington,
and imbedded in Oracle Retail Signs and Oracle Retail Labels and Tags.
(iv) the software component known as Adobe Flex™ licensed by Adobe Systems Incorporated of
San Jose, California, and imbedded in Oracle Retail Promotion Planning & Optimization
application.
You acknowledge and confirm that Oracle grants you use of only the object code of the VAR
Applications. Oracle will not deliver source code to the VAR Applications to you.
Notwithstanding any other term or condition of the agreement and this ordering document, you
shall not cause or permit alteration of any VAR Applications. For purposes of this section,
"alteration" refers to all alterations, translations, upgrades, enhancements, customizations or
modifications of all or any portion of the VAR Applications including all reconfigurations,
reassembly or reverse assembly, re-engineering or reverse engineering and recompilations or
reverse compilations of the VAR Applications or any derivatives of the VAR Applications. You
acknowledge that it shall be a breach of the agreement to utilize the relationship, and/or
confidential information of the VAR Applications for purposes of competitive discovery.
The VAR Applications contain trade secrets of Oracle and Oracle's licensors and Customer shall
not attempt, cause, or permit the alteration, decompilation, reverse engineering, disassembly or
other reduction of the VAR Applications to a human perceivable form. Oracle reserves the right to
replace, with functional equivalent software, any of the VAR Applications in future releases of the
applicable program.
Contents
1 Overview...........................................................................................1-1
How this Document is Organized ............................................................................ 1-2
Audience........................................................................................................................ 1-2
General Information ................................................................................................... 1-3
Data Formats .......................................................................................................... 1-3
General Rules: ................................................................................................. 1-3
Action Codes & Record Identifiers ..................................................................... 1-4
File Formats ............................................................................................................ 1-4
Required Fields ...................................................................................................... 1-4
Default Values........................................................................................................ 1-4
Fixed Sequence Components - Base Xstore Point of Service........................... 1-5
Xstore Point of Service International Support ....................................................... 1-6
Column Data Types: varchar or nvarchar ......................................................... 1-6
4
Country Return Map Record (COUNTRY_RETURN_MAP) ............................ 2-53
Sales Goal Record (SALES_GOAL) ....................................................................... 2-54
Device Configuration Record (DEVICE_CONFIG)............................................ 2-55
5
Party Id Cross-Reference Record (PARTY_ID_XREF)........................................ 4-12
Party Cross-Reference Record (PARTY_XREF).................................................... 4-13
Party Address Record (PARTY_ADDRESS) ........................................................ 4-14
Employee Record (EMPLOYEE) ............................................................................. 4-16
Employee Store Record (EMPLOYEE_STORE) ................................................... 4-21
Employee Note Record (EMPLOYEE_NOTE)...................................................... 4-22
Employee Password Record (EMPLOYEE_PASSWORD) ................................. 4-23
Employee Task Record (EMPLOYEE_TASK) ...................................................... 4-24
Employee Task Notes Record (EMPLOYEE_TASK_NOTES) .......................... 4-26
Employee Message Record (EMPLOYEE_MESSAGE) ...................................... 4-27
Customer Group Record (CUST_GROUP)........................................................... 4-29
Customer Affiliation Record (CUST_AFFILIATION) ...................................... 4-31
Customer Note Record (CUST_NOTE) ................................................................. 4-32
Customer Merge Record (CUSTOMER_MERGE) .............................................. 4-33
Customer Consent Information Record (CUSTOMER_CONSENT_INFO) .. 4-35
Anonymize Customer Record (CUSTOMER_ANONYMIZE) ......................... 4-36
Anonymize Employee Record (EMPLOYEE_ANONYMIZE)........................... 4-46
5 Inventory...........................................................................................5-1
Stock Ledger Record (STOCK_LEDGER)............................................................... 5-1
Inventory Document Record (INV_DOC) .............................................................. 5-3
Inventory Document Property Record (INV_DOC_PROPERTY)...................... 5-9
Carton Record (CARTON) ....................................................................................... 5-11
Inventory Document Line Item Record (INV_DOC_LINE_ITEM) ................. 5-13
Inventory Valid Destination Record (INV_VALID_DESTINATIONS) ........ 5-17
Inventory Valid Destinations Property
(INV_VALID_DESTINATIONS_PROPERTY) ................................................... 5-19
Inventory Bucket Record (INVENTORY_BUCKET) .......................................... 5-21
Inventory Bucket Property (INVENTORY_BUCKET_PROPERTY) ............... 5-23
Inventory Count Record (INV_COUNT) .............................................................. 5-25
Inventory Count Bucket Record (INV_COUNT_BUCKET).............................. 5-26
Inventory Count Sheet Record (INV_COUNT_SHEET).................................... 5-27
Inventory Count Sheet Property (INV_COUNT_SHEET_PROPERTY) ......... 5-29
Inventory Count Sheet Line Item Record (INV_COUNT_SHEET_LINEITEM)5-31
Inventory Count Sheet Line Item Property
(INV_COUNT_SHEET_LINEITEM_PROPERTY) .............................................. 5-33
Inventory Document Line Serial Record (INV_DOC_LINE_SERIAL)........... 5-35
Inventory Document Shipment Carton Record
(INV_DOC_SHIPMENT_CARTON)..................................................................... 5-37
Inventory Document Shipment Line Item Record
(INV_DOC_SHIPMENT_LINEITEM) .................................................................. 5-39
Inventory Document Shipment Line Item Record Property
(INV_DOC_SHIPMENT_LINEITEM_PROPERTY)........................................... 5-41
Inventory Item Account Modifier Record (INV_ITEM_ACCOUNT_MODIFIER)
5-43
6
Inventory Location Record (INV_LOCATION) .................................................. 5-45
Inventory Location Property (INV_LOCATION_PROPERTY)........................ 5-46
Inventory Location Availability Record (INV_LOCATION_AVAILABILITY)5-48
Inventory Location Bucket Record (INV_LOCATION_BUCKET).................. 5-49
Inventory Location Bucket Property (INV_LOCATION_BUCKET_PROPERTY)5-
50
Inventory Location Modifier Record (INV_LOCATION_MODIFIER).......... 5-52
Inventory Serialized Stock Ledger Record (INV_SERIALIZED_STOCK_LEDGER)
5-54
Document Note Record (DOCUMENT_NOTE) .................................................. 5-55
Inventory Shipper Record (INV_SHIPPER)......................................................... 5-57
Inventory Shipper Method Record (INV_SHIPPER_METHOD) .................... 5-58
Inventory Document In Record (INV_DOC_IN) ................................................ 5-60
Inventory Replenishment Document Line Item Record
(INV_REP_DOC_LINE_ITEM) ............................................................................... 5-62
Shipment Record (SHIPMENT).............................................................................. 5-65
Shipment Property (SHIPMENT_PROPERTY) ................................................... 5-68
Inventory Cross Reference Record (INV_CROSS_REF).................................... 5-70
Fiscal Year Record (FISCAL_YEAR) ...................................................................... 5-72
Inventory Cost Item Yearend Record (INV_CST_ITEM_YEAREND) ............ 5-73
7
7 Taxing ...............................................................................................7-1
Tax Bracket Record (TAX_BRACKET) .................................................................... 7-1
Tax Location Record (TAX_LOCATION) ............................................................... 7-3
Tax Retail Location Mapping Record (TAX_RETAIL_LOCATION_MAPPING)7-4
Tax Authority Record (TAX_AUTHORITY) ......................................................... 7-5
Tax Group Record (TAX_GROUP)........................................................................... 7-8
Tax Group Property (TAX_GROUP_PROPERTY) ................................................ 7-9
Tax Group Rule Record (TAX_GROUP_RULE) .................................................. 7-10
Tax Rate Rule Record (TAX_RATE_RULE) ......................................................... 7-13
Tax Rate Rule Override Record (TAX_RATE_RULE_OVERRIDE)................. 7-16
Tax Postal Code Mapping Record (TAX_POSTAL_CODE_MAPPING) ....... 7-19
Tax Group Mapping Record (TAX_GROUP_MAPPING) ................................ 7-20
Tax Exemption Record (TAX_EXEMPTION) ....................................................... 7-22
8
10 Tenders, Vouchers, & Till Sessions.............................................10-1
Tender Record (TENDER)........................................................................................ 10-1
Tender Availability Record (TENDER_AVAILABILITY)................................. 10-9
Tender Denomination Record (TENDER_DENOMINATION)..................... 10-10
Tender Options Record (TENDER_OPTIONS)................................................. 10-12
Tender Type Record (TENDER_TYPE) ............................................................... 10-20
Tender User Settings Record (TENDER_USER_SETTINGS)......................... 10-22
Tender Repository Record (TENDER_REPOSITORY) .................................... 10-25
Tender Repository Property (TENDER_REPOSITORY_PROPERTY) ......... 10-27
Tender Repository Float Record (TENDER_REPOSITORY_FLOAT) .......... 10-29
Tender Repository Float Property (TENDER_REPOSITORY_FLOAT_PROPERTY)
10-30
Tender Repository Status Record (TENDER_REPOSITORY_STATUS) ..... 10-32
Voucher Record (VOUCHER) ............................................................................... 10-33
Session Record (SESSION).................................................................................... 10-35
Session Tender Record (SESSION_TENDER)................................................... 10-37
11 Security...........................................................................................11-1
Security Group Record (SEC_GROUP)................................................................. 11-1
Security Privilege Record (SEC_PRIVILEGE) ..................................................... 11-3
Security Access Type Record (SEC_ACCESS_TYPE) ......................................... 11-6
Security Access Control List Record (SEC_ACL) ................................................ 11-7
Shared Secret Removal (SEC_PASSWORD)........................................................ 11-8
9
15 Country Pack Information.............................................................15-1
Tax Free Country Record (TAXFREE_COUNTRY) ............................................. 15-1
19 DataLoader .....................................................................................19-1
Overview ..................................................................................................................... 19-1
DataLoader Operation .............................................................................................. 19-2
Starting DataLoader ............................................................................................ 19-2
DataLoader Operation Description .................................................................. 19-2
About .lst files ................................................................................................. 19-2
DataLoader Execution ................................................................................. 19-2
About the failures.dat File.................................................................................. 19-4
Sample failures.dat Line.............................................................................. 19-4
DataLoader Logging ........................................................................................... 19-4
DataLoader Data Files............................................................................................... 19-5
Data File Line Example....................................................................................... 19-5
Replacement File Processing ................................................................................... 19-5
Example................................................................................................................. 19-6
*.reo (reorganize) Files ................................................................................. 19-6
Replacement File Types Processing Comparison ........................................... 19-6
Valid Commands for a Data File Record .............................................................. 19-7
About the “UPDATE” and “UPDATE_SELECT” Action Types .................. 19-7
About the “RUN_SQL” Action Type ........................................................ 19-8
10
Header and Comments ............................................................................................. 19-9
XML Header ......................................................................................................... 19-9
Line Count ..................................................................................................... 19-9
Download Id ................................................................................................. 19-9
Application Date........................................................................................... 19-9
Target Org Node........................................................................................... 19-9
Deployment Name ....................................................................................... 19-9
Download Time ............................................................................................ 19-9
Apply Immediately .................................................................................... 19-10
Example: Dataloader header for file created by Xstore Office. All DataLoader
files created by Xstore Office will have this header. ............................. 19-10
Example: Dataloader header for file not created by Xstore Office...... 19-10
DataLoader Configuration ..................................................................................... 19-10
DataLoaderConfig.xml ..................................................................................... 19-11
DataLoaderConfig.xml Record Definition..................................................... 19-13
DataLoaderConfig.xml Value Translation ......................................................... 19-14
Example Value Translator Usage: StringConcatTranslator......................... 19-14
Dao and Sql Statement Applicability.............................................................. 19-17
Failure Reporting ..................................................................................................... 19-17
11
Send Us Your Comments
Oracle welcomes customers' comments and suggestions on the quality and usefulness of
this document.
Your feedback is important, and helps us to best meet your needs as a user of our
products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us
your name, the name of the company who has licensed our products, the title and part
number of the documentation and the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that
you have the latest version of the document and if any concerns are
already addressed. To do this, access the Online Documentation
available on the Oracle Technology Network Web site. It contains the
most current Documentation Library plus all documents revised or
released recently.
12
Preface
This guide describes the DataLoader, and the format of the DataLoader files used to
populate the Xstore Point of Service database.
Audience
This Host Interface Guide is written for the following audiences:
• Business analysts
• System analysts
• Integrators and implementation personnel
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility
Program website at http://www.oracle.com/pls/topic/
lookup?ctx=acc&id=docacc.
Related Documents
For more information, see the following documents in the Xstore Point of Service 17.0
documentation set:
• Xstore Suite Release Notes
• Xstore Suite Oracle Retail Xstore Suite 17.0/Merchandising 16.0.1 Implementation
Guide
• Xstore Point-of-Service User Guide
• Xstore Point-of-Service Mobile User Guide
• Xstore Point-of-Service Reports Guide
• Xstore Point-of-Service Manager's Guide
• Xstore Point-of-Service Shipping, Receiving, and Inventory Guide
• Xstore Office User Guide
• Oracle Retail Xstore Point-of-Service, Lane Checkout User Interface User Guide
• Xstore Suite Implementation and Security Guide
• Xstore Point-of-Service Frameworks and Technologies Guide
• Xstore Suite Deal Pricing Guide
• Xenvironment User Guide
13
Customer Support
Customer Support
To contact Oracle Customer Support, access My Oracle Support at the following URL:
https://support.oracle.com
When contacting Customer Support, please provide the following:
• Product version and program/module name
• Functional and technical description of the problem (include business impact)
• Detailed step-by-step instructions to re-create
• Exact error message received
• Screen shots of each step you take
Conventions
Navigate: This is a navigate statement. It tells you how to get to the start of the procedure
and ends with a screen shot of the starting point and the statement “the Window Name
window opens.”
This is a code sample
It is used to display examples of code
14
Conventions
15
1
Overview
Note: “Items & Pricing” does not require an Xstore Point of Service
restart, but these changes will not take effect in the middle of a
transaction.
Overview 1-1
How this Document is Organized
Audience
This guide is intended for anyone responsible for interfacing the Xstore Point of Service
application to home office systems, including Operations Technical Support and
Customer Technical Support.
General Information
Data Formats
DateTime fields are always yyyy-mm-dd hh:mm:ss.nnn for a total length of 23
characters. Time values are always in 24-hour format. (e.g. January 15, 2004 2:10 pm will
format as 2004-01-15 14:10:00.000)
Note: SQL server does not provide data types for storing the date
exclusively or the time exclusively. In Microsoft SQL server, only a
DATETIME data type is supported. In Oracle SQL server, the data type
is TIMESTAMP.
For this reason, the date fields (effective_date and end_date)
include a time in addition to the date. The time fields (start_time
and end_time) include a date in addition to the time.
Integer fields are usually a maximum of 11 characters, but may change depending upon
the underlying database. Leading zeroes are suppressed. When the number is negative,
the sign will float in front.
BigInt fields are usually a maximum of 22 characters, but may change depending upon
the underlying database. Leading zeroes are suppressed. When the number is negative,
the sign will float in front.
Decimal fields are usually a maximum of 17 characters. Leading zeroes are suppressed.
The decimal point is always explicit. Most decimal fields will contain 6 places to the right
of the decimal point. The length of decimal fields is specified with the first number
representing the total field width (less the decimal point) followed by a comma and the
precision of the number. A field with a length listed as 17, 6 may hold up to 19 characters
(up to 11 numerals to the left of the decimal point, the decimal point itself, and up to 6
numerals to the right of the decimal point). When the number is negative, the sign will
float in front.
String fields are usually a maximum of 254 characters.
Boolean fields are a maximum of 5 characters. (Note: Value based on FALSE=5
characters.)
The DataLoader will recognize the following:
• FALSE = {0, “false”} // “false” is case-insensitive
• TRUE = {1, “true”} // “true” is case-insensitive
General Rules:
The following sizes and datatypes are used consistently in Xstore Point of Service:
• Organization ID: Integer
• Retail Location ID: Integer
• Party ID: BigInt
• Item ID: String(60)
• Percentage (tax): Decimal(8,6)
• Price, dollar amounts: Decimal(17,6)
• Quantities: Decimal(11,4)
Overview 1-3
General Information
Action Codes
See Chapter 18, “Valid Commands for a Data File Record” for more information.
The first column identifies the action code of the record.
Record Identifiers
The second column is the record identifier. This value will identify to the system the type
of record that follows. Each record identifier may specify a unique field layout for the
record.
File Formats
The DataLoader is designed to adapt flat data files into relational data that Xstore Point
of Service can use. These flat files are referred to generically as “data files” within the
DataLoader. The DataLoader treats each line in the file as a record. Every file line begins
with a command field followed by a record type field which is then followed by the
appropriate data for that record. Fields are typically delimited by an ASCII character and
are referred to by the DataLoader via their index number. Field position indices are 1-
based, where the command is field 1, the record type is field 2, and the first piece of
actual data is 3, and so on. The DataLoader auto-detects the delimiter, so the delimiter
can be any ASCII character that is guaranteed not to appear in the data itself. However,
the same delimiter should be used at all times.
Required Fields
The required fields are denoted by the symbol in the following tables. A blank entry
indicates the field is not required, and the * symbol indicates that additional information
can be found in the comments section.
All flags default to FALSE and are not required unless otherwise noted.
Default Values
When applicable, a default constraint defines the value that will be supplied for a
column whenever a user fails to enter a value.
Overview 1-5
Xstore Point of Service International Support
loc_org_hierarchy.org_code
loc_org_hierarchy.parent_code
loc_org_hierarchy.parent_value
loc_org_hierarchy.level_mgr
18. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
19. Store Manager String 254 The name of the store manager.
“StoreManager” loc_rtl_loc.store_manager
20. Default Tax Decimal 8, 6 The display text used for the tax
Percentage percentage and also shown on
receipts for the store.
“DefaultTax
Percentage” loc_rtl_loc.
default_tax_percentage
26. Email Address String 254 The email address for the retail
location.
“EmailAddress”
loc_rtl_loc.email_addr
39. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
8. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
9. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
12. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
3. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
5. Reason Code String 254 The reason that the store will
be closed on the Close Date.
"reasonCode"
loc_close_dates.
reason_code
5. Answer Text Key String 254 Translation key for the answer
text.
"answerTextKey"
loc_cycle_question_
choices.answer_text_key
15. Validation Rule String 30 The key that points to the code
Key necessary to provide data
validation in
"validation
validationRuleConfig.xml.
RuleKey"
com_trans_prompt_
properties.validation_rule_key
13. Fee Value Decimal 17, 6 The value of the shipping flat
fee or percentage. Ignored in
“feeValue”
the case of a fee type of
SHIP_ITEM_PRICE.
com_shipping_fee_tier.
fee_value
<ValueTranslator
className="dtv.data2.dataloader.valuetranslator.StringReplaceTranslator">
<Param key="searchFor" value="" />
<Param key="replaceWith" value="" />
</ValueTranslator>
6. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
18. List Price Decimal 17, 6 Suggested sale unit retail price
provided by the item
“ListPrice”
manufacturer.
Important! This field should
not be used for pricing an
item.
itm_item.list_price
20. Unit Cost Decimal 17, 6 * Cost for each retail sale unit of
this item.
“UnitCost”
*Display only field, unless a
measuring device such as a
scale or gas pump is used.
itm_item_options.unit_cost
23. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
24. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
25. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
26. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
29. Restocking Fee Decimal 17, 6 Fee applied when this item is
returned.
“RestockingFee”
itm_item_options.restocking_f
ee
44. Prompt for Price Boolean 5 If true, the system will prompt
Flag for the unit price.
“PromptFor itm_item_options.prompt_for_
Price” price_flag
50. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
51. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
55. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
56. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
57. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
58. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
72. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
73. Initial Sale Qty Decimal 11, 4 The default item sale quantity.
(For example, may be set to 2
"InitialSale
for earrings.)
Quantity"
itm_item_options.initial_sale_
qty
98. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
99. Tare Value Decimal 11, 4 Value of the tare on the item.
“TareValue” itm_item_options.tare_value
ApplicabilityCondition
†<Dao name="ItemDimensions">
<ApplicabilityCondition
className="dtv.data2.dataloader.applicability.ValueApplicabilityC
ondition">
<Param key="testValue" value="filePosition=83" />
<Param key="applicableValue" value="" />
<Param key="invert" value="true" />
</ApplicabilityCondition>
20. Unit Cost Decimal 17, 6 * Cost for each retail sale unit of
this item.
“UnitCost”
*Display only field, unless a
measuring device such as a
scale or gas pump is used.
itm_item_options.unit_cost
29. Restocking Fee Decimal 17, 6 Fee applied when this item is
returned.
“RestockingFee”
itm_item_options.restocking_
fee
44. Prompt for Price Boolean 5 If true, the system will prompt
Flag for the unit price.
“PromptFor itm_item_options.prompt_for_
Price” price_flag
55. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
56. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
57. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
58. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
73. Initial Sale Qty Decimal 11, 4 The default item sale quantity.
(For example, may be set to 2
"InitialSale
for earrings.)
Quantity"
itm_item_options.initial_sale_
qty
98. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
99. Tare Value Decimal 11, 4 Value of the tare on the item.
“TareValue” itm_item_options.tare_value
itm_item_options 59 ItemOptions
Name Comment
Field # “Field Name” Type Width Required Table.Column
3-55. See “Item Record (ITEM)” for detailed information about fields 3 through 55.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
70-76. See “Item Record (ITEM)” for detailed information about fields 70 through 76, and fields
81-82.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Note: Clients may use one of two tables to set up the pricing
hierarchy: loc_org_hierarchy or loc_pricing_hierarchy. The two tables
store the same data for the purposes of the price provider. The org
hierarchy is a general-purpose hierarchy table that is able to drive
more functionality in addition to prices, while the pricing hierarchy
table stores less information and is designed only for the price
provider. In the scope of the price provider itself, the two tables are
interchangeable. In fact, their primary keys are identical.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
3. Kit Item Id (PK) String 60 The item identifier for the kit.
“KitItemId” itm_kit_component_p.
kit_item_id
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
10. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
8. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
9. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
34. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
38. Picture Uri String 254 The location of the picture file.
“PictureUri” crm_party.picture_uri
Name Comment
Field # “Field Name” Type Width Required Table.Column
ApplicabilityCondition
†
<Dao name="PartyTelephone">
<ApplicabilityCondition
className="dtv.data2.dataloader.applicability.ValueApplicabilityC
ondition">
<Param key="testValue" value="filePosition=27" />
<Param key="applicableValue" value="" />
<Param key="invert" value="true" />
</ApplicabilityCondition>
********value="filePosition=28
********value="filePosition=29
********value="filePosition=30
ApplicabilityCondition
‡<Dao name="PartyEmail">
<ApplicabilityCondition
className="dtv.data2.dataloader.applicability.ValueApplicabilityC
ondition">
<Param key="testValue" value="filePosition=31" />
<Param key="applicableValue" value="" />
<Param key="invert" value="true" />
</ApplicabilityCondition>
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
hrs_employee_password 3 EmployeePassword
(action="INSERT_ONLY")
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
32. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
3. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
4. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
8. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
9. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
crm_customer_affiliation 4
crm_party 4
crm_party_locale_information 4
crm_party_telephone 4
crm_party_properties 4
Name Comment
Field # “Field Name” Type Width Required Table.Column
crm_party_p
crm_party_email
crm_party_locale_information
crm_party_telephone
crm_customer_notes
cat_delivery_modifier
xom_customer_mod
xom_address_mod
ttr_identity_verification
tax_tax_exemption
cat_charge_acct_users
cat_cust_acct
crm_party
inv_shipment
inv_shipment_address
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
address_type = NULL
WHERE organization_id = ? AND party_id = ?">
<Field configParam="getOrganizationId" dataType="Long"/>
<Field filePosition="03" dataType="String"/>
</Sql>
<Sql sql="UPDATE crm_party_telephone
SET telephone_number = NULL, contact_type = NULL ,
contact_flag = 0, primary_flag = 0
WHERE organization_id = ? AND party_id = ?">
<Field configParam="getOrganizationId" dataType="Long"/>
<Field filePosition="03" dataType="String"/>
</Sql>
<Sql sql="UPDATE crm_customer_notes
SET note = NULL, creator_id = NULL, note_timestamp = NULL
WHERE organization_id = ? AND party_id = ?">
<Field configParam="getOrganizationId" dataType="Long"/>
<Field filePosition="03" dataType="String"/>
</Sql>
<Sql sql="UPDATE cat_delivery_modifier
SET cat_delivery_modifier.address1 = NULL,
cat_delivery_modifier.address2 = NULL,
cat_delivery_modifier.address3 = NULL ,
cat_delivery_modifier.address4 = NULL,
cat_delivery_modifier.city = NULL,
cat_delivery_modifier.state = NULL,
cat_delivery_modifier.postal_code = NULL ,
cat_delivery_modifier.country = NULL,
cat_delivery_modifier.neighborhood = NULL,
cat_delivery_modifier.county = NULL,
cat_delivery_modifier.telephone1 = NULL ,
cat_delivery_modifier.telephone2 = NULL,
cat_delivery_modifier.telephone3 = NULL,
cat_delivery_modifier.telephone4 = NULL,
cat_delivery_modifier.apartment = NULL ,
cat_delivery_modifier.first_name = NULL,
cat_delivery_modifier.middle_name = NULL,
cat_delivery_modifier.last_name = NULL ,
cat_delivery_modifier.shipping_method = NULL,
cat_delivery_modifier.tracking_number = NULL,
cat_delivery_modifier.extension = NULL,
cat_delivery_modifier.delivery_date = NULL WHERE
cat_delivery_modifier.organization_id = ? AND
cat_delivery_modifier.cust_acct_id IN
(SELECT cca.cust_acct_id FROM cat_cust_acct cca
WHERE cca.organization_id = ? AND cca.party_id = ?)">
<Field configParam="getOrganizationId" dataType="Long"/>
<Field configParam="getOrganizationId" dataType="Long"/>
<Field filePosition="03" dataType="String"/>
</Sql>
<Sql sql="UPDATE xom_customer_mod
SET xom_customer_mod.first_name = NULL,
xom_customer_mod.last_name = NULL,
xom_customer_mod.telephone1 = NULL ,
xom_customer_mod.telephone2 = NULL,
xom_customer_mod.email_address = NULL,
xom_customer_mod.ORGANIZATION_NAME = NULL,
xom_customer_mod.SALUTATION = NULL ,
xom_customer_mod.MIDDLE_NAME = NULL,
xom_customer_mod.SUFFIX = NULL
WHERE xom_customer_mod.organization_id = ? AND
xom_customer_mod.order_id IN
(SELECT DISTINCT xom.order_id FROM xom_order_mod xom
JOIN trl_rtrans tr
ON xom.organization_id = tr.organization_id
AND xom.rtl_loc_id = tr.rtl_loc_id
AND xom.business_date = tr.business_date
AND xom.wkstn_id = tr.wkstn_id
AND xom.trans_seq = tr.trans_seq
WHERE tr.cust_party_id = ? AND tr.organization_id = ?)">
<Field configParam="getOrganizationId" dataType="Long"/>
<Field filePosition="03" dataType="String"/>
<Field configParam="getOrganizationId" dataType="Long"/>
</Sql>
<Sql sql="UPDATE xom_address_mod
party_id = ?">
<Field configParam="getOrganizationId" dataType="Long"/>
<Field filePosition="03" dataType="String"/>
</Sql>
<Sql sql="UPDATE inv_shipment SET destination_name = NULL WHERE
organization_id = ? AND destination_party_id = ?">
<Field configParam="getOrganizationId" dataType="Long"/>
<Field filePosition="03" dataType="String"/>
</Sql>
<Sql sql="UPDATE inv_shipment_address
SET address1 = NULL, address2 = NULL, address3 = NULL,
address4 = NULL ,apartment = NULL, city = NULL, state = NULL,
postal_code = NULL, country = NULL, neighborhood = NULL,
county = NULL ,telephone1 = NULL, telephone2 = NULL,
telephone3 = NULL, telephone4 = NULL
WHERE organization_id = ? AND invctl_document_id IN
(SELECT DISTINCT ishp.invctl_document_id
FROM inv_shipment ishp WHERE ishp.organization_id = ?
AND ishp.destination_party_id = ?)">
<Field configParam="getOrganizationId" dataType="Long"/>
<Field configParam="getOrganizationId" dataType="Long"/>
<Field filePosition="03" dataType="String"/>
</Sql>
<Sql sql="UPDATE ttr_send_check_tndr_lineitm
SET payable_to_name = NULL, payable_to_address = NULL,
payable_to_city = NULL, payable_to_state = NULL,
payable_to_postal_code = NULL, payable_to_address2 = NULL,
payable_to_address3 = NULL, payable_to_address4 = NULL,
payable_to_apt = NULL, payable_to_country = NULL,
payable_to_neighborhood = NULL, payable_to_county = NULL
WHERE ttr_send_check_tndr_lineitm.organization_id = ? AND
ttr_send_check_tndr_lineitm.trans_seq IN
(SELECT tr.trans_seq FROM trl_rtrans tr JOIN
ttr_send_check_tndr_lineitm tsc ON tr.organization_id =
tsc.organization_id AND tr.rtl_loc_id = tsc.rtl_loc_id AND
tr.business_date = tsc.business_date AND tr.wkstn_id =
tsc.wkstn_id AND tr.trans_seq = tsc.trans_seq WHERE
hrs_employee_password
hrs_employee_fingerprint
hrs_employee_answers
hrs_employee_notes
hrs_employee
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-1
Stock Ledger Record (STOCK_LEDGER)
Name Comment
Field # “Field Name” Type Width Required Table.Column
7. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-3
Inventory Document Record (INV_DOC)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-5
Inventory Document Record (INV_DOC)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
37. Control Number String 254 The unique identifier for the
packing slip; typically the
"ControlNumber
inventory control document
"
number.
inv_invctl_document.
control_number
Inventory 5-7
Inventory Document Record (INV_DOC)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
4. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Inventory 5-9
Inventory Document Property Record (INV_DOC_PROPERTY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
4. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Inventory 5-11
Carton Record (CARTON)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
4. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Inventory 5-13
Inventory Document Line Item Record (INV_DOC_LINE_ITEM)
Name Comment
Field # “Field Name” Type Width Required Table.Column
13. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
14. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
15. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
17. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
25. Control Number String 254 A value that can be used to tag
a document line item.
"ControlNumber
" inv_invctl_document_
lineitm.control_number
26. Unit Cost Decimal 17, 6 For Stock Valuation; the item
unit cost.
"UnitCost"
inv_invctl_document_
lineitm.unit_cost
Inventory 5-15
Inventory Document Line Item Record (INV_DOC_LINE_ITEM)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-17
Inventory Valid Destination Record (INV_VALID_DESTINATIONS)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-19
Inventory Valid Destinations Property (INV_VALID_DESTINATIONS_PROPERTY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-21
Inventory Bucket Record (INVENTORY_BUCKET)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-23
Inventory Bucket Property (INVENTORY_BUCKET_PROPERTY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-25
Inventory Count Bucket Record (INV_COUNT_BUCKET)
Name Comment
Field # “Field Name” Type Width Required Table.Column
5. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
5. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Inventory 5-27
Inventory Count Sheet Record (INV_COUNT_SHEET)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-29
Inventory Count Sheet Property (INV_COUNT_SHEET_PROPERTY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
5. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Inventory 5-31
Inventory Count Sheet Line Item Record (INV_COUNT_SHEET_LINEITEM)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-33
Inventory Count Sheet Line Item Property (INV_COUNT_SHEET_LINEITEM_PROPERTY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-35
Inventory Document Line Serial Record (INV_DOC_LINE_SERIAL)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-37
Inventory Document Shipment Carton Record (INV_DOC_SHIPMENT_CARTON)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-39
Inventory Document Shipment Line Item Record (INV_DOC_SHIPMENT_LINEITEM)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-41
Inventory Document Shipment Line Item Record Property
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-43
Inventory Item Account Modifier Record (INV_ITEM_ACCOUNT_MODIFIER)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-45
Inventory Location Property (INV_LOCATION_PROPERTY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-47
Inventory Location Availability Record (INV_LOCATION_AVAILABILITY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-49
Inventory Location Bucket Property (INV_LOCATION_BUCKET_PROPERTY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-51
Inventory Location Modifier Record (INV_LOCATION_MODIFIER)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-53
Inventory Serialized Stock Ledger Record (INV_SERIALIZED_STOCK_LEDGER)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-55
Document Note Record (DOCUMENT_NOTE)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-57
Inventory Shipper Method Record (INV_SHIPPER_METHOD)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-59
Inventory Document In Record (INV_DOC_IN)
Name Comment
Field # “Field Name” Type Width Required Table.Column
8. Any value present in this field will be ignored, but the field must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-61
Inventory Replenishment Document Line Item Record (INV_REP_DOC_LINE_ITEM)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-63
Inventory Replenishment Document Line Item Record (INV_REP_DOC_LINE_ITEM)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
4. Any value present in this field will be ignored, but the field must exist.
7. Any value present in this field will be ignored, but the field must exist.
15. Any value present in this field will be ignored, but the field must exist.
Inventory 5-65
Shipment Record (SHIPMENT)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-67
Shipment Property (SHIPMENT_PROPERTY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-69
Inventory Cross Reference Record (INV_CROSS_REF)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-71
Fiscal Year Record (FISCAL_YEAR)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Inventory 5-73
Inventory Cost Item Yearend Record (INV_CST_ITEM_YEAREND)
Name Comment
Field # “Field Name” Type Width Required Table.Column
dsc_discount_group_mapping 3, 27 DiscountGroupMapping
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
9. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
12. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
19. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
3-27. See “Discount Record (DISCOUNT)” for detailed information about fields 3 through 27.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
.
Coupon Cross-Reference Record (COUPON_XREF) (Sheet 1 of 2)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
5. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
24. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Note: The Trigger Type (Field #4) and the Trigger Value that triggers
the deal (Field #5) are automatically concatenated and separated with a
":" as a single entry in the database column prc_deal_trig.deal_trigger.
Dependencies:
There must be a Deal corresponding to each Deal ID in the record.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Dependencies:
There must be a Deal corresponding to each Deal ID in the record.
The Trigger Type (Field #4) and the Trigger Value that excludes the deal (Field #5) are
automatically concatenated and separated with a "~" as a single entry in the database
column prc_deal_trig.deal_trigger.
A normal deal_trigger value is in the format:
<trigger_group>:<trigger_data>, e.g. CUSTGROUP:EMPLOYEE
An exclusionary deal_trigger value is in the format:
<trigger_group>:~<trigger_data>, e.g. CUSTGROUP:~EMPLOYEE
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
12. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
13. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
14. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
VENDOR (Vendor/supplier of
the item, taken from field:
itm_item.vendor), SEASON
(Season for which the item is
designed or released, taken
from field:
itm_item.season_code), STYLE
(style of the item, taken from
field:
itm_item.parent_item_id),
SKU (item’s unique identifier,
taken from field:
itm_item.item_id),
ALLOW_DEAL (checks to
verify deals are allowed, it
ensures that the
itm_item.disallow_discount_fl
ag is not set to true, and the
business logic in the register
does not disallow discounts),
ITEM_STOCK_STATUS (the
item’s stock availability, taken
from field:
itm_item.stock_status),
...continued
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
5. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
doc_document_definition.start_issue_date (filePosition="06")
doc_document_definition.end_issue_date (filePosition="07")
doc_document_definition.start_redeem_date (filePosition="06")
doc_document_definition.end_redeem_date (filePosition="07")
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
5. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
doc_document_definition.start_issue_date (filePosition="06")
doc_document_definition.end_issue_date (filePosition="07")
doc_document_definition.start_redeem_date (filePosition="06")
doc_document_definition.end_redeem_date (filePosition="07")
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
21. Text Code Value String 60 Identifier for the text that will
print on the rebate receipt.
"TextCode
This value is used to retrieve
Value"
text from the com_receipt_text
table; for both receipt type and
segment type. Used from
RcptConfig.xml in a
Textblock to tie in a block of
text from com_receipt_text.
doc_document_definition.
text_code_value
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
3-23 See “Deal Record (DEAL)” for detailed information about these fields.
<Field name="Trigger">
- <ValueTranslator
className="dtv.data2.dataloader.valuetranslator.StringConcatTranslator">
<Param key="string.1" value="COUPON:INPUT_COUPON:" />
<Param key="string.2" value="filePosition=24" />
</ValueTranslator>
</Field>
The Trigger Type and the Trigger Value that triggers the deal are automatically
concatenated and separated with a ":" as a single entry in the database column
prc_deal_trig.deal_trigger.
25-27. See “Deal Record (DEAL)” for detailed information about these fields.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-1
Tax Bracket Record (TAX_BRACKET)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-3
Tax Retail Location Mapping Record (TAX_RETAIL_LOCATION_MAPPING)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-5
Tax Authority Record (TAX_AUTHORITY)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-7
Tax Group Record (TAX_GROUP)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-9
Tax Group Rule Record (TAX_GROUP_RULE)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-11
Tax Group Rule Record (TAX_GROUP_RULE)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-13
Tax Rate Rule Record (TAX_RATE_RULE)
Name Comment
Field # “Field Name” Type Width Required Table.Column
12. Effective Date/ DateTime 23 Date and time the tax rule
Timestamp goes into effect.
"Effective tax_tax_rate_rule.
Datetimestamp" effective_datetime
13. Expiration Date/ DateTime 23 Date and time when the tax
Timestamp rule expires.
"Expiration tax_tax_rate_rule.
Datetimestamp" expr_datetime
14. Daily Start Time DateTime 10 Time each day when the tax
becomes effective.
"DailyStartTime
Dao" Note: Not currently
supported; must be NULL.
tax_tax_rate_rule.
daily_start_time
15. Daily End Time DateTime 10 Time each day when the tax
expires.
"DailyEndTime
Dao" Note: Not currently
supported; must be NULL.
tax_tax_rate_rule.
daily_end_time
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-15
Tax Rate Rule Override Record (TAX_RATE_RULE_OVERRIDE)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
12. Effective Date/ DateTime 23 Date and time the tax rule
Timestamp goes into effect.
"Effective tax_tax_rate_rule_
Datetimestamp" override.effective_datetime
13. Expiration Date/ DateTime 23 Date and time when the tax
Timestamp rule expires.
"Expiration tax_tax_rate_rule_
Datetimestamp" override.expr_datetime
14. Daily Start Time DateTime 10 Time each day when the tax
becomes effective.
"DailyStartTime
Dao" Note: Not currently
supported; must be NULL.
tax_tax_rate_rule_
override.daily_start_time
15. Daily End Time DateTime 10 Time each day when the tax
expires.
"DailyEndTime
Dao" Note: Not currently
supported; must be NULL.
tax_tax_rate_rule_
override.daily_end_time
Taxing 7-17
Tax Rate Rule Override Record (TAX_RATE_RULE_OVERRIDE)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
3. Postal Code (PK) String 254 Postal code that maps to the
tax location.
"PostalCode"
tax_postal_code_
mapping.postal_code
Taxing 7-19
Tax Group Mapping Record (TAX_GROUP_MAPPING)
Name Comment
Field # “Field Name” Type Width Required Table.Column
4. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-21
Tax Exemption Record (TAX_EXEMPTION)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Taxing 7-23
Tax Exemption Record (TAX_EXEMPTION)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
7. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
8. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
11. Account Setup DateTime 23 The date and time the account
Date was set up.
"AccountSetup cat_cust_acct.acct_setup_date
Date"
12. Last Activity DateTime 23 The date and time of the last
Date activity on the account.
"LastActivity cat_cust_acct.last_
Date" activity_date
Name Comment
Field # “Field Name” Type Width Required Table.Column
Note: Changes have been made to this record, fields 5 and 10, for
Xstore version 3.5.1 to provide the ability to look up users by an
identifying value. However, backwards compatibility has been
preserved.
Name Comment
Field # “Field Name” Type Width Required Table.Column
<ValueTranslator className="dtv.data2.dataloader.valuetranslator.MaxLengthTranslator">
<Param key="length" value="30" />
</ValueTranslator>
Name Comment
Field # “Field Name” Type Width Required Table.Column
8. Effective Date DateTime 23 The date and time the user can
use the account.
"EffectiveDate"
cat_charge_acct_
users.effective_date
9. Expiration Date DateTime 23 The date and time the user can
no longer use the account.
"Expiration
Date" cat_charge_acct_
users.expiration_date
10. Account User String 254 The account user name will be
Name set to default when no value is
supplied to the (non-
"AccountUser
truncated) value specified in
Name"
field #5. Legacy records not
populating this new field will
therefore behave in the system
as they have before.
(See ValueTranslator
below.)
cat_charge_acct_
users.acct_user_name
<ValueTranslator className="dtv.data2.dataloader.valuetranslator.DefaultValueTranslator">
<Param key="default" value="filePosition=05" />
</ValueTranslator>
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
4. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
8. Expiration Date DateTime 23 The date and time the user can
no longer use the account
"expiration
plan.
Date"
cat_cust_acct_plan.
expiration_date
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
3-55. See “Item Record (ITEM)” for detailed field information about fields 3-55, 70-75, and 81-83.
56-59. See “Non-Physical Item Record (NON_PHYSICAL_ITEM)” for detailed field information.
60. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
61. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
68. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
70-75, See “Item Record (ITEM)” for detailed information about fields 70-75, and 81.
81
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
27. Covered Item Decimal 17, 6 Price paid for the warranted
Purchase Price item at time of purchase.
"coveredItem itm_warranty.covered_
PurchasePrice" item_purchase_price
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
56-59. See “Non-Physical Item Record (NON_PHYSICAL_ITEM)” for detailed field information.
60. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
61. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
70-72, See “Item Record (ITEM)” for detailed information about fields 70-72, 81.
81
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
3. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
3. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
3. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
5. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
6. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
13. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
14. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
20. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
42. Post Void Open Boolean 5 If true, open the cash drawer
Cash Drawer each time a post void is
Required Flag performed using this tender.
"PostVoidOpen tnd_tndr_options.post_void_o
CashDrawer pen_drawer_flag
Required"
44. Expiration Date DateTime 23 The date when the tender can
no longer be accepted for
"Expiration
service or action.
Date"
default=”3000-01-01 00:00:00”
tnd_tndr_options.expr_date
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
33. Post Void Open Boolean 5 If true, open the cash drawer
Cash Drawer each time a post void is
Required Flag performed using this tender.
"PostVoidOpen tnd_tndr_options.post_void_o
CashDrawer pen_drawer_flag
Required"
Name Comment
Field # “Field Name” Type Width Required Table.Column
35. Expiration Date DateTime 23 The date when the tender can
no longer be accepted for
"Expiration
service or action.
Date"
default=”3000-01-01 00:00:00”
tnd_tndr_options.expr_date
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
8. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
9. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
5. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
6. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
8. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Security 11-1
Security Group Record (SEC_GROUP)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
5. This field is no longer in use. Any value present in this field will be ignored, but the field
must exist.
Security 11-3
Security Privilege Record (SEC_PRIVILEGE)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Security 11-5
Security Access Type Record (SEC_ACCESS_TYPE)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Security 11-7
Shared Secret Removal (SEC_PASSWORD)
Name Comment
Field # “Field Name” Type Width Required Table.Column
Important: This record type only supports the DELETE action. When
applied, the sec_password table will be cleared. Once cleared, the
lead register will generate a new key to secure inter-process
communication between the various in-store modules of Oracle Xstore
Point of Service.
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
9. Clock Out Date Datetime 23 The date and Time for the
Time clock out.
“ClockOutDateT thr_timecard_entry.clock_out_
ime” timestamp
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
10. Blocked Flag String 1 If true, tax free invoices are not
permitted.
"BlockedFlag”
civc_taxfree_country.blocked_
flag
DataLoader can be used to load Xstore Office users rather than exclusively managing
Xstore Office users via the web page.
cfg_user_node 3, 8 UserNode
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
<Sql action="INSERT"
sql="INSERT INTO cfg_user_password (organization_id,
user_name, password, effective_date, create_user_id, create_date)
VALUES (?, ?, ?, ?, ?, ?)">
<Field sysProp="dtv.dataloader.OrganizationId"
dataType="Long" />
<Field filePosition="03" dataType="String" />
<Field literal="gdyb21LQTcIANtvYMT7QVQ==" name="password" /
><!-- default '1234' password -->
<Field variable="$currentDateTimestamp"
name="effectiveDate" dataType="Date" />
<Field literal="DATALOADER" name="create_user_id" />
<Field variable="$currentDateTimestamp"
name="effectiveDate" dataType="Date" />
</Sql>
Name Comment
Field # “Field Name” Type Width Required Table.Column
Overview
This optional type of interface can be used to load transactions into Xcenter for various
business reasons, including performing verified returns. This data will typically come
from an e-commerce or order management system.
Name
Field # “Field Name” Type Width Required Comment
Name
Field # “Field Name” Type Width Required Comment
Name
Field # “Field Name” Type Width Required Comment
16. Tax Amount BigDecim 17,6 u Total tax charged for all line
al items.
TaxAmount
trn_trans.taxtotal
trl_rtrans.taxtotal
Name
Field # “Field Name” Type Width Required Comment
23. Fiscal Session String 100 Fiscal session number for the
Number transaction.
FiscalSession trn_trans.fiscal_session_
Number number
<ValueTranslator
className="dtv.data2.dataloader.valuetranslator.DefaultValueTranslator">
<Param value="filePosition=04" key="default"/>
</ValueTranslator>
8. Line Start Time DateTime Date & Time that line was
started.
BeginDate
Timestamp trl_rtrans_lineitm.begin_date_
timestamp
9. Line End Time DateTime Date & Time that line was
completed.
EndDate
Timestamp trl_rtrans_lineitm.end_date_
timestamp
18. Net Amount BigDecim 17,6 Total price: unit price times
al quantity.
NetAmount
trl_sale_lineitm.net_amt
19. Gross Amount BigDecim 17,6 Total amount: total price plus
al tax.
GrossAmount
trl_sale_lineitm.gross_amt
10. Taxable Amount BigDecim 17, 6 The taxable amount for which
al tax was calculated.
TaxableAmount
trl_sale_tax_lineitm.taxable_amt
14. Tax Exempt BigDecim 17, 6 Amount that was exempt from
Amount al tax.
TaxExemptAmo trl_sale_tax_lineitm.tax_exempt_
unt amt
17. Tax Rule Integer Tax rule used for this tax.
Sequence
trl_sale_tax_lineitm.tax_rule_seq
TaxRuleSequenc _nbr
e
24. Tax Override String 30 The reason code of why tax was
ReasonCode overridden.
TaxOverrideReas trl_sale_tax_lineitm.tax_override
onCode _reascode
8. Line Start Time DateTime Date & Time that line was
started.
BeginDate
Timestamp trl_rtrans_lineitm.begin_date_
timestamp
9. Line End Time DateTime Date & Time that line was
completed.
EndDate
Timestamp trl_rtrans_lineitm.end_date_
timestamp
15. Taxable Amount BigDecim 17,6 Amount for which tax was
al charged.
TaxableAmount
trl_tax_lineitm.taxable_amt
8. Line Start Time DateTime Date & Time that line was
started.
BeginDate
Timestamp trl_rtrans_lineitm.begin_date_
timestamp
9. Line End Time DateTime Date & Time that line was
completed.
EndDate
Timestamp trl_rtrans_lineitm.end_date_ti
mestamp
10. This field is not in use. Any value present in this field will be ignored, but the field must
exist.
22. Acct User Name String 254 Name of user that performed
the tender (house account
AcctUserName
signers).
ttr_tndr_lineitm.acct_user_na
me
Name Comment
Field # “Field Name” Type Width Required Table.Column
Name Comment
Field # “Field Name” Type Width Required Table.Column
DELETE Removes the specified data from the database, if it exists. If the record
to be deleted does not exist, the DELETE will have no effect.
DELETE_BY_ Removes the specified data, only within the specified organization,
ORGANIZATION from the affected table before applying the file records. (*.reo file)
INSERT Indicates this is new data that should be inserted into the database. If
the data to be inserted already exists in the database, the DataLoader
will attempt an update to ensure that the database matches the
information that was sent in the file.
INSERT_ONLY The data will be inserted if it does not already exist. If the data already
exists, no action is taken.
RUN_SQL The Run SQL action type allows for any SQL statement to be executed.
TRUNCATE Deletes all data in the affected table before applying the file records.
(*.rep file)
UPDATE Indicates this record contains existing data that is being modified. If the
record to be modified does not already exist in the database, the
DataLoader will not attempt an INSERT and the update will be neither
effective nor applied.
UPDATE_SELECT Indicates this data should only update database columns referenced by
DataLoader file record fields populated with non-null data. This partial
update feature allows for the update of records without overwriting all
the record's fields.
DataLoader Commands
Command Description
DELETE Removes the specified data from the database, if it exists. If the
record to be deleted does not exist, the DELETE will have no effect.
DELETE_BY_ Removes the specified data, only within the specified organization,
ORGANIZATION from the affected table before applying the file records. (*.reo file)
INSERT Indicates this is new data that should be inserted into the database. If
the data to be inserted already exists in the database, the DataLoader
will attempt an update to ensure that the database matches the
information that was sent in the file.
INSERT_ONLY The data will be inserted if it does not already exist. If the data
already exists, no action is taken.
RUN_SQL The Run SQL action type allows for any SQL statement to be
executed.
TRUNCATE Deletes all data in the affected table before applying the file records.
(*.rep file)
UPDATE Indicates this record contains existing data that is being modified. If
the record to be modified does not already exist in the database, the
DataLoader will not attempt an INSERT and the update will be
neither effective nor applied.
UPDATE_SELECT Indicates this data should only update database columns referenced
by DataLoader file record fields populated with non-null data. This
partial update feature allows for the update of records without
overwriting all the record's fields.
Overview
The DataLoader application is
responsible for translating flat
data files into database data that
can be used by Xstore Point of
Service. For example, many host
systems can be configured to
export data to a delimited flat file.
Then, that flat file is delivered to
the stores throughout the chain.
Finally, the flat file is read in by
the DataLoader and loaded into
the store databases for use. This is
one option for propagating data
changes (such as prices,
employees, etc.) to all the
databases throughout the
enterprise.
DataLoader 19-1
DataLoader Operation
DataLoader Operation
Starting DataLoader
A dataloader2.bat and a dataloader2.sh script are provided with Xstore Point of
Service builds to launch the DataLoader. Assuming that the DataSourceConfig.xml
and DataLoaderConfig.xml configurations are correct, you should only have to run
the dataloader2 script to launch DataLoader. The main class for launching the
DataLoader is dtv/data2/dataloader/DataLoader.
DataLoader Execution
When the DataLoader is executed, the following sequence takes place:
1. The DataLoader reads each qualifying file in the folder (or each file listed in the
.lst file if configured for list files). It will interrogate all files that are not excluded
by the file type filter and will only process files that are effective at the time that it is
run. Only those files which either lack an effective date declaration, or which declare
an effective date prior to—or on—the run date will be processed.
2. The DataLoader performs the following processes as it iterates through each file:
a. The DataLoader scans the entire Data File, creating “Split Files”.
* Split Files are a mechanism for sorting and organizing the data without
loading it all into memory (since Data Files are often hundreds of thousands
of lines).
* Split Files exist only while the DataLoader is executing, not before or after
execution.
b. Once the Split Files are created, the DataLoader will scan through them one at a
time, in the proper order, and load the records.
Records are read and loaded at this point based on the
recordsPerTransaction configuration.
* If a line fails, the entire transaction is retried one record at a time.
* If a record fails individually during this second load, it is written to
failures.dat along with the error that caused it.
c. When the DataLoader has finished loading all the Split Files, it deletes the Split
File.
3. A success.dat file is created if the operation is completed successfully.
DataLoader archives success and failure files in addition to archiving the source files
it processes. These related source/success/failure files are archived to timestamped
folders to ensure their segregation from runs performed at other times. The files
themselves will not be renamed. A DataLoader configuration setting determines
how many days worth of files to archive (both source and result).
4. The Dataloader writes a file with status information about the files that were loaded
to C:\xstore\download directory named summary.ini. Xenvironment can then
process the results and send them to Xstore Office.
For example, the summary.ini file includes the following information about the
loaded files:
[item_images.mnt]
rows=0
failedRows=9
appliedDate=1375392342973
exception.java.lang.NullPointerException=8
DataLoader 19-3
DataLoader Operation
DataLoader Logging
The DataLoader employs log4j loggers for its logging facility. It also defines special
loggers for reporting load successes and failures to the central office, if so configured.
• Dataloader log4j is typically configured with config/dataloader/log4j.xml.
• INFO level logging should be enabled on the
dtv.data2.dataloader.DataLoader category to log a brief report of the data
load.
• Dataloader will log data lines that fail to load to a log4j category called
DATA_LOADER_FAILURES_APPENDER. This category can be configured to use a
separate appender and log failed lines to a separate file.
DataLoader 19-5
Replacement File Processing
Example
*.rep files imply a TRUNCATE operation for each data model with a DataLoader
operation within the replacement file. If a *.rep file has ten insert commands, half of
which are for the ITEM model and half for the ITEM_MESSAGE model, then both the
itm_item and itm_item_msg tables will have all their records deleted before any of the
insert commands are executed.
Note: When viewing the log file, a .rep file will contain one truncate
line for every data type represented in the contents.
For example, if a .rep file with 6 lines is processed, the log will show
that 7 lines were processed; all of the lines plus a truncate line.
DELETE Removes the specified data from the database, if it exists. If the record to
be deleted does not exist, the DELETE will have no effect.
DELETE_BY_ Removes the specified data, only within the specified organization, from
ORGANIZATION the affected table before applying the file records. (*.reo file)
INSERT Indicates this is new data that should be inserted into the database. If the
data to be inserted already exists in the database, the DataLoader will
attempt an update to ensure that the database matches the information
that was sent in the file.
INSERT_ONLY The data will be inserted if it does not already exist. If the data already
exists, no action is taken.
RUN_SQL The Run SQL action type allows for any SQL statement to be executed.
TRUNCATE Deletes all data in the affected table before applying the file records.
(*.rep file)
UPDATE Indicates this record contains existing data that is being modified. If the
record to be modified does not already exist in the database, the
DataLoader will not attempt an INSERT and the update will be neither
effective nor applied.
UPDATE_SELECT Indicates this data should only update database columns referenced by
DataLoader file record fields populated with non-null data. This partial
update feature allows for the update of records without overwriting all
the record's fields.
The DataLoader loads records based on the order in which they are defined in the
DataLoaderConfig.xml. The order in which these action types are declared is
important. It dictates the order in which the DataLoader processes records grouped by
action type. The records are then sorted by their command (or action type).
This list shows the full ordered set of actions:
1. ACTION_TRUNCATE
2. ACTION_DELETE_BY_ORGANIZATION
3. ACTION_DELETE
4. ACTION_INSERT
5. ACTION_UPDATE
6. ACTION_UPDATE_SELECT
7. ACTION_RUN_SQL
8. ACTION_INSERT_ONLY
DataLoader 19-7
Valid Commands for a Data File Record
To run SQL statements from download.mnt, the row in the file must be similar to the
following:
RUN_SQL|update loc_rtl_loc set region = 27
XML Header
Each file contains an XML header line that will dictate when and where the file is
delivered.
Line Count
The line_count attribute is used to indicate how many lines of data are in the file (not
including the header). If it is not present, the DataLoader will not validate total line
count when loading the file, but will still load the file.
Download Id
The download_id attribute is used to identify the download and is used in logging to
separate the processing of one download file from another. The download id, when
present, is included in the logging messages while this file is being processed. (These
logging messages may be replicated to Xcenter to provide corporate visibility for the
processing of download files.)
Application Date
The application_date attribute is used to determine the date on which the file will be
deployed. If the application date attribute is not present, the date that the file is picked
up will be used which means the file will be deployed on the same day.
Deployment Name
If the deployment_name field is populated, the value will be used as the name for the
deployment, otherwise the auto-suggestion name will be used.
Download Time
The download_time attribute is used to indicate when the file will be downloaded.
Possible values are "IMMEDIATE" and "STORE_CLOSE".
- If a deployment is scheduled for immediate download, Xenvironment will begin
to download the file immediately.
DataLoader 19-9
DataLoader Configuration
Apply Immediately
The apply_immediately attribute is used to indicate when the file will be applied.
Possible values are true and false.
- If set to true, the file is loaded immediately.
- If set to false, the file is scheduled to be applied during the closing process.
- If "apply_immediately" is not present, the deployment will be scheduled with
"false".
Note: See the Xstore Office User Guide for more information.
DataLoader Configuration
At the heart of the DataLoader is its configuration. The DataLoader configuration file
(DataLoaderConfig.xml) maps fields from the flat file to fields on Java data objects
which can then be persisted to the database via Xstore’s persistence framework (DTX).
The DTX object information can be found in the Java Doc:
• Table name,
• Java field name,
• Database name,
• or use existing maps for reference
Any modification or transformation of the data that is required will be specified in this
configuration file. Also, SQL statements can be placed in the configuration file in order
to load the data in an appropriate fashion.
DataLoaderConfig.xml
<DataLoaderConfig xmlns:xs="http://www.w3.org/2001/XMLSchema-
instance" xs:noNamespaceSchemaLocation="DataLoaderConfig.xsd">
<Parameter name="DataFileLocation" value="./download"/>
<Parameter name="OrganizationId"
value="${dtv.location.organizationId}"/>
<Parameter name="DataSource" value="Local"/>
<Parameter name="recordsPerTransaction" value="100"/>
<Parameter name="continueIfLineCountInvalid" value="true"/>
<Parameter name="archivePath" value="./download/archive"/>
<Parameter name="archiveDays" value="30"/>
<Parameter name="characterEncoding" value="ISO-8859-1"/>
<Parameter name="processListFiles" value="false"/>
The following table lists and describes the header parameters for
DataLoaderConfig.xml.
Parameter Description
DataFileLocation Specifies from where to read the datafile. This can be an absolute
path pointing to a file (e.g. “c:/xstore/download/download.dat”) or
can point to a directory (“c:/xstore/download/”). If the
DataFileLocation property is set to a directory, the DataLoader
will scan that directory for files with a .lst extension. Each .lst file
found should contain absolute or relative paths to actual data
files to load.
OrganizationId The integer organization ID to use for populating org ID. This is
the value that will be used for the sysProp references in
DataLoaderConfig.xml.
continueIfLineCountInvalid Defines whether or not the DataLoader will process a data file
whose “expected line count sum” fails. (i.e., the LINE_COUNT
specified in the header does not match the actual number of
lines in the file)
archivePath Defines the directory location where data files will be moved
and archived after processing.
DataLoader 19-11
DataLoader Configuration
Parameter Description
archiveDays Defines the number of days that archived folders should be kept.
Note that this is date and time relevant, not just date. One day is
a 24-hour period based on the run date. For example, assume
that archiveDays is set to 1. Data Loader is run at 3:00 PM on 04/
25 and then at 9:00 AM on 04/26. The archive folders from the
04/25 run will not be deleted. Then Data Loader is run at 5:00
PM on 04/26. The 04/25 run is then more than one 24-hour
period before the current one, so the archive folders from 04/25
will be deleted.
processListFiles If the value is "true", then only the contents of *.lst files will be
considered. If there are no *.lst files, then no files will be loaded.
If "false", then files will be loaded as per the functionality
described in “DataLoader Operation Description”.
The value is "false" by default.
Note: List files will be deleted after the data files have been
processed. The data files that were processed are archived.
Element/Attribute Description
RecordType Defines the name of this record type. All record types in a Data File must
correspond to a mapping in the DataLoaderConfig.xml. When a Data
File is downloaded that contains multiple record types, the records are
loaded in the order that they are defined in the
DataLoaderConfig.xml.
Dao Defines a Data Access Object to map this data to. The cardinality for Daos
on a record type is 0..*. No Daos would be acceptable if at least 1 SQL
statement is present for the record type.
DataLoader 19-13
DataLoaderConfig.xml Value Translation
Sql Defines an arbitrary SQL statement to run for this record type. The
cardinality for SQL statements is also 0..* and no SQL statements are
required if there is at least 1 Dao present.
Field Maps data either to a Dao field or to a SQL statement place holder.
sysProp Instructs the DataLoader to use the value of this system property for the
value of this field.
filePosition Instructs the DataLoader to retrieve data from the specified field position
in the data file for the value of this field.
literal Instructs the DataLoader to use the literal data that follows for the value
of this field.
variable Instructs the DataLoader to use some current state of the system as the
value for this field. Currently, $currentDateTimestamp and $currentDate are
available.
name The name of the field to map this data to. This is only applicable for Daos.
dataType The data type (String, Integer, BigDecimal, Long, Date, etc.) of this field.
This is only required for fields in a SQL statement.
In the example above, strings are concatenated together to form the value for the field.
The key=”string.1”, key=”string.2”, and key=”string.3” define the order of the strings,
value=”filePosition=04” and value=”filePosition=05” define the field position in the data
file, and value=”:” is the literal value.
Sample database value for DEAL_TRIGGER example:
Value Translator
Description Parameters
BooleanInverterTranslator
Interprets the data as a boolean value and inverts it. key=true/false value=truth
Truth values include several defaults but are value/false value. Adds to a list
configurable. This translator returns either 0 or 1 to of values to interpret as true and
represent the boolean value after inversion. Users may false.
specify multiple keys for true/false. This translator
key=null value=true/false.
maintains an internal list of truth values and simply
Specifies whether a null value
adds the parameters to it. Useful in cases where the
should be considered true or
input data and the schema have the same flag, but
false before inversion.
inverted. e.g. “allow discounts” v. “disallow
discounts”.
ConditionalValueTranslator
Transforms the data conditionally based on what data key=if: value=then: (1..*, an
is presented. If no “else:” parameter is specified and the “if…then” condition)
presented data does not find a match, the data will be
key=else: value=then: (0..1, an
returned as it was originally presented.
“else” default value)
OptionalStringConcatTranslator
DataLoader 19-15
DataLoaderConfig.xml Value Translation
Value Translator
Description Parameters
SqlQueryTranslator
Performs a SQL query against the database to retrieve key=sql, value=select item_id…
the value to use for this field. If the query returns null, (1..1 the sql query to execute)
then the nullValue parameter value is used for the
key=sql.field.xx
value. If no nullValue is specified and the query returns
value=filePosition=yy (0..*,
null, then the original value from the data file is used.
where xx if the 1 based index of
the sql placeholder and yy is a
field index in the data file. A
literal, variable, or sysProp could
also be used for the value)
StringConcatTranslator
StringMapReplaceTranslator
StringReplaceTranslator
Performs a “search and replace” on the current field key=searchFor value=xx (1..1,
value. where xx is an arbitrary string)
key=replaceWith value=yy (1..1,
where yy is the string to replace
xx with)
ZeroToNullTranslator
Failure Reporting
When a file is deployed from Xstore Office to Xstore Point of Service and processed by
the DataLoader, Dataloader will report errors to Xstore Office through the event logging
facility. A DataLoader error (DATALOADER_ERROR) is reported in the “Updates”
category in the Xstore Office Support Dashboard.
Note: DataLoader will only return errors to Xstore Office for files
deployed from Xstore Office.
DataLoader 19-17
Failure Reporting
Version 17.0
Chapter Change
Entire document In all fields where a string identifies the type of value stored by the
record, changed DECIMAL to BIGDECIMAL.
Chapter Change
Airside Stores & Tax- Removed database tables and Dataloader records and referred reader
Free Transactions to Database Dictionary and Host Interface Guide.
Version 16.0.0.1
Chapter Change
Send Us Your Changed name of Oracle Retail Xstore for Grocery User Guide to Oracle
Comments Retail Xstore Point-of-Service, Lane Checkout User Interface User Guide.
Version 16.0
Chapter Change
Chapter Change
Items and Pricing ITEM Record - Changed Qty Scale to a Decimal Type.
ITEM_OPTIONS Record - Changed Qty Scale to a Decimal Type.