Report Desk Tables

Release Date: TBA
Version 8.6

Elliott Report Desk, initially released in Elliott v8.6, relies on a series of database tables that reside in the Root directory.  Following is a list of the files and a description of their usage:

  • SYRDCOLB: This table is a list of Elliott table/columns that have been identified as a special type, like CustNo -- not a default type like String or Number.  Whenever a column is dragged to the Report Columns list, the software will check here to see if it has already had a special type associated with it.  If so, that is used instead of the default type.  Whenever a Netcellent developer indicates a special type to associated with a column in the report columns list, and the report is saved, the entry in this table is changed or a new one is added.  Note:  Only Netcellent developers update this table.  The unique key for this table is table and column.
  • SYRDCOLE:  This table is just like SYRDCOLB except that is only updated by Enhancement developers.   The unique key for this table is table and column.
  • SYRDOUTP:  When a Report Desk report is run, the output parameters are saved here for the particular user/report so that the next time it is run by the same user, it will default to the same settings.  It optionally can be used when recording an input parameters template (next table) to save the output parameters with the input parameters.  The unique key for this table is login, company number, report and sequence number.
  • SYRDTPLT:  This table stores input parameter settings for each user/report combination.  The last input settings are saved automatically.  Additionally, a user can fill in the report parameters, add a description, and reuse those parameters (optionally including output parameters) on demand in the future.  The unique key for this table is login, company number, report and sequence number.
  • SYRDTTLB:  Whenever a user drags a column to the Report Columns list, it first looks here for the most popular column title recorded and uses that if available.  The top ten titles are shown in a drop down list.  If any of those titles don't work well, a new column title can be entered.  The unique key for this table is table, column and title.
  • SYRDTYPB:  This table defines the special types known to Elliott Report Desk.  This table does not change very often.  It contains information like the length of the field, whether a type is upper case only, any reformatting is needed after entry, etc.  The unique key for this table is type.
  • SYRDUDRB:  This table contains the bulk of information to define a report, including WHERE parameters, sort order if allowed, report columns and some additional information.  Netcellent defines the entries in this table.  The unique key for this table is report-id, origin, template number, sequence number and variation.
  • SYRDUDRC:  When a customer changes a Netcellent report or an Enhancement report, the details are saved here, and they override the base or enhancement version of the report.   The unique key for this table is report-id, origin, template number, sequence number and variation.
  • SYRDUDRE:  This table is just like SYRDUDRB except that it is only updated by Enhancement developers.   The unique key for this table is report-id, origin, template number, sequence number and variation.
  • SYRDUDTB:  This table contains the most basic data about a report, namely the Primary table and the basic SELECT statement for running the report.  Optionally, user functions can be defined here that can be used as report columns in the report designer.  This table can only be updated by Netcellent developers.  An important reason for this is that SELECT statements sometimes have to be declared in a specific way to maximize performance.   The unique key for this table is report-id and template number.
  • SYRDUDTC:  Whenever a customer creates a new report from a base report or an enhanced report, the corresponding SYRDUDTB or SYRDUDTE is copied here so that its definition is preserved, even if Netcellent changes the original.   The unique key for this table is report-id and template number.
  • SYRDUDTE:   This table is just like SYRDUDTB except that it is only updated by Enhancement developers.   The unique key for this table is report-id and template number. 
  • SYDRPLOG:  This table contains a record for every Report Desk report that users run.  It contains typical logging data, like date-and-time, user, workstation, etc., plus information for analyzing performance, such as the SQL SELECT statement, and the timings for various processing of the report.
JEG

Developer Documentations

  1. Received Code 9999 with Web Services Call
  2. Received Return Status Code 3 When Using Elilogin Login Method
  3. Elliott Web Service Requirements
  4. Elliott eStore Checklist
  5. LN API
  6. FN API
  7. RN API
  8. IN and DF API Change (V9.0)
  9. FA API Changes (V9.0)
  10. VA API Changes (V9.0)
  11. CartService
  12. EliarachService
  13. ElicshtxService
  14. EliattrbService
  15. ElisyscdService
  16. EliNoteService
  17. El2rstimService
  18. EliOrderService
  19. ItemInquiry
  20. EliitmiqService
  21. EliShiptoService
  22. El2getfrService
  23. Steps Required to Test ReportWriter in V8.2
  24. Installation of ElliottService, NETcellent’s Web Services for Elliott
  25. ResellerFinder
  26. EliaptrxService
  27. VendorInquiry
  28. EliloginService
  29. ElislsmnService
  30. EliserhsService
  31. EliatpobService
  32. ElievprcService
  33. ElihdtrxService
  34. ElicuswlService
  35. QueryTurnaround
  36. InvoiceInquiry
  37. ElicustmService
  38. EligetcdService
  39. OrderInquiry
  40. EliordiqService
  41. EliecontService
  42. EliautdpService
  43. El2CrCrdService
  44. Log-Timer / ElliottTimer.Ini Support
  45. Alpha Document Number Support (V8.5/V9.0)
  46. ElliottService System.TypeInitializationException
  47. Feature - Printing API to Dynamically Set Number of Copies
  48. The Values and Meanings of Distribution Types - ARDISFIL, APDISFIL, IMDISFIL, BMDISFIL
  49. DD API Changes (V9.0)
  50. PA API (8.5)
  51. Validate License API
  52. AP API
  53. TP API: Temporary Path
  54. Data Structures for Report Desk Defaults and Enforcements
  55. COBOL to VB Interface Programs
  56. IN API: Option to Support Files and Folders Validation
  57. FF API: File Functions
  58. ID API
  59. LK: Links API
  60. FFLNearYou
  61. Report Desk Developing and Debugging
  62. Developing a New Elliott V8.6 Report Desk User Defined Report (UDR)
  63. CustomerInquiry
  64. Elliott API (JSON Web Service)
  65. Animating COBOL Code in Elliott V8.5
  66. Preliminary Programming Changes for Elliott 8.6
  67. CV API
  68. System Lock File Requirements
  69. How to Write Test Codes for C# ESS Projects
  70. Solving the Inability to Debug Elliott on a New Server
  71. Report Desk: Developing Custom Reports
  72. Report Desk Tables
  73. Report Desk Database Delivery Strategy

Feedback and Knowledge Base