Appendix C RTLOG_FORMAT_REQUIREMENTS.pdf
PDF 16 MB Posted
- Solicitation number
- 36C10B24Q0011
About this file
This document is an appendix to a federal solicitation for a food ordering online and mobile application. The Department of Veterans Affairs Technology Acquisition Center Austin is seeking proposals to develop and implement a VA-wide food ordering application to allow patients, visitors, and staff to order and pay for food from VA medical center cafeterias using a web or mobile interface. Responses are due by June 30, 2022. The selected contractor will be awarded a one-year contract with the option to extend for up to four additional years. The application must integrate with existing VA food service systems, accommodate various dietary restrictions and preferences, and support both online and mobile ordering. It should also allow for food delivery scheduling and notifications. Pricing terms and set asides were not specified in this appendix.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10B24Q0011 0006.docx | DOCX document | |
| 36C10B24Q0011 0005.docx | DOCX document | |
| 36C10B24Q0011 A00003.pdf | ||
| VCS Food Ordering Online and Mobile Application RFQ Questions _ Answers3.pdf | ||
| 36C10B24Q0011 0004.docx | DOCX document | |
| VCS Food Ordering Online and Mobile Application RFQ Questions _ Answers2.xlsx.pdf | ||
| 36C10B24Q0011 0003.docx | DOCX document | |
| VCS Food Ordering Online and Mobile Application RFQ Questions _ Answers.pdf | ||
| Public vs Internal App Store Education.pdf | ||
| 36C10B24Q0011 A00002.pdf | ||
| 36C10B24Q0011 0002.docx | DOCX document | |
| 36C10B24Q0011 A00001_1.pdf | ||
| 36C10B24Q0011 0001.docx | DOCX document | |
| 36C10B24Q0011 A00001.pdf | ||
| Attachment 1 - Service Model Questions.docx | DOCX document | |
| 36C10B24Q0011_1.docx | DOCX document | |
| 36C10B24Q0011.pdf | ||
| Appendix B Mobile App Location Listing.pdf |
Show all 18
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
288 Oracle Retail Merchandising System
1.
2.
3.
4.
5.
FHEAD (Only 1 per file, required) THEAD (Multiple expected, one per transaction, required for each transaction) TCUST (Only 1 per THEAD record allowed, optional for some transaction types, see table below) CATT (Attribute record specific to the TCUST record – Multiple allowed, only valid if TCUST exists) TITEM (Multiple allowed per transaction, optional for some transaction types, see table below) IDISC (Discount record specific to the TITEM record – Multiple allowed per item, optional see table below) IGTAX (Vat/Tax record specific to the TITEM record – Multiple allowed per item, optional see table below) TPYMT (Multiple allowed per transaction, will have the deposit amount for pickup/delivery/layaway orders, optional see table below) TTEND (Multiple allowed per transaction, optional for some transaction types, see table below) TTAIL (1 per THEAD, required) FTAIL (1 per file, required)
Operations Guide, Volume 1 - Batch Overviews and Designs 289
Record Name
Field Name Field Type Default Value Description Required? Justification/ Padding
290 Oracle Retail Merchandising System
Name
Operations Guide, Volume 1 - Batch Overviews and Designs 291
Name
292 Oracle Retail Merchandising System
Name
Operations Guide, Volume 1 - Batch Overviews and Designs 293
Name
294 Oracle Retail Merchandising System
Name
Operations Guide, Volume 1 - Batch Overviews and Designs 295
Name
296 Oracle Retail Merchandising System
Name
Operations Guide, Volume 1 - Batch Overviews and Designs 297
Name
298 Oracle Retail Merchandising System
Name
Operations Guide, Volume 1 - Batch Overviews and Designs 299
Name
300 Oracle Retail Merchandising System
Transaction Type
Includes item records?
Includes tender records?
Includes tax records?
IGTAX?
Includes customer records?
Operations Guide, Volume 1 - Batch Overviews and Designs 301
Record Type Requirements
Record Name Field Name Code Type
302 Oracle Retail Merchandising System
Record Name Field Name Code Type
1.
2.
3.
4.
Note:
5.
Operations Guide, Volume 1 - Batch Overviews and Designs 303
6.
7.
8.
9.
304 Oracle Retail Merchandising System
Type
Requirements
Operations Guide, Volume 1 - Batch Overviews and Designs 305
Type
Requirements
Note:
Transaction Type
Sub-transaction Type
Item Type Tender Type Group
Reference Number Field
Meaning of Reference Field
Req?
TRANSACTION
TYPE
TITEM.Quantity Sign TTEND.Tender Sign TTAX.Tax Sign IDISC.Quantity Sign
306 Oracle Retail Merchandising System
Transaction Type Sub-transaction Type
Reference Number Field
Meaning of Reference Field Req?
TRANSACTION TYPE TITEM.Quantity Sign TTEND.Tender Sign TTAX.Tax Sign IDISC.Quantity Sign
Operations Guide, Volume 1 - Batch Overviews and Designs 307
Transaction Type
Sub-transaction Type
Reference Number Field
Meaning of Reference Field Req?
Reason Code
Reference Number Column Meaning Req?
308 Oracle Retail Merchandising System
Sub Transaction Type
Reason Code
Reference Number Column
Meaning Req?
TRANSACTION TYPE TITEM.Quantity Sign
TTEND.Tender Sign
TTAX.Tax Sign
IDISC.Quantity Sign
TRANSACTION TYPE TITEM.Quantity Sign TTEND.Tender Sign TTAX.Tax Sign IDISC.Quantity Sign
Operations Guide, Volume 1 - Batch Overviews and Designs 309
Reference Number Column
Meaning Req?
310 Oracle Retail Merchandising System
Reference Number Column
Meaning Req?
Reference Number Column
Meaning Req?
Operations Guide, Volume 1 - Batch Overviews and Designs 311
ReSA (Oracle Retail Sales Audit)
File details come from the government source that posted it. Updated .