logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Raks Database Exploration: Firebird SQL Data Structure, Extracting Sales Data, & GM Prefix Tables

pinokio76 4632 6
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Reply | New topic
  • #1 16563944
    pinokio76
    Level 2  
    Due to the fact that while looking for the documentation of the Raksa database, I looked through many pages and could not find the information I needed, so I decided to conduct an investigation myself.
    My problem was to extract the sales data.
    I wrote a piece of code that lists all the Raks database tables together with the fields of those tables (no data of course).
    Additionally, I found fields describing both tables and fields (mainly in trade), which made it easier to link tables and find relevant data for the report.
    For those interested, see Appendix 2 for Excel files.
    1. List of All tables and their fields from the database
    2. List of tables and fields regarding trade - "GM" prefix

    I hope someone will find it useful
    Attachments:
  • ADVERTISEMENT
  • #2 16564279
    Anonymous
    Anonymous  
  • ADVERTISEMENT
  • #3 16564490
    pinokio76
    Level 2  
    If this would be so easy...
    You may as well ask for codes that activate hidden options that you did not pay for in a VW showroom.
    Partners selling software mainly live on services, providing full technical documentation would be a shot in the foot.
    At least no one shared something like this with me and I didn't find anyone willing.
  • ADVERTISEMENT
  • #4 16564527
    Anonymous
    Anonymous  
  • ADVERTISEMENT
  • #5 17507485
    ogon_czyk
    Level 1  
    It may not make sense, but to get to the databases you need the server admin password
  • #6 17508159
    Dżyszla
    Level 42  
    In the case of Firebird
  • #7 18010858
    Robert28wwa
    Level 2  
    In the case of the trading module, the structure of the database is quite simple. Each document type consists mainly of a header part and a positional part. Two tables with relationships with each other. The tables are quite legible. And, as Pinocchio wrote, the names of these tables usually start with the GM prefix. Of course, there are also additional relations to dictionaries and cards (these usually start with the R3 prefix). But for reporting, as a rule, it is enough to refer to the GM tables.
Reply | New topic
Report a violation of the law

Topic summary

The discussion revolves around the challenges of extracting sales data from the Raks database, specifically using Firebird SQL. The user conducted an investigation due to the lack of available documentation and successfully wrote code to list all database tables and their fields. They highlighted the significance of fields related to trade, particularly those with the "GM" prefix, which are essential for reporting. Other participants noted the difficulty in obtaining technical documentation from software vendors, emphasizing that access to the database requires server admin credentials. The structure of the trading module's database is described as straightforward, consisting of a header and positional part with clear relationships between tables.
Summary generated by the language model.
ADVERTISEMENT