Hello,
I recently started adopting gCTS for a project.
When storing tabledata in gCTS repositories, I noticed that there are usually two files associated with a table. One file in /tabledata that includes the whole record with all attributes and another file in /objects/TABU containing all index columns and a hash. For a simple customizing the structure of the second file looks as follows (some values have been redacted for confidentiality):
[ { "table":"***redacted***", "index": [ { "columns": [ { "key":"MANDT", "value":"001" }, { "key":"***redacted***", "value":"***redacted***" } ], "hash":"i7/vUO+UJ6oY+kyQN3IZLZZOkgI=" } ] }]
The goal of my project is to create records for existing customizing tables in an external application and import them into an SAP system from a gCTS repository. Therefore it is important to understand the structure of the corresponding gCTS files in order to be able to create them manually. While the other information in these files is easily understandable, the hash value requires some clarification.
- What is the value "hash" used for in the SAP system? What information does the hash resemble? Since it is not written into the actual table, is it important for this information to be correct or can a default value be used here without breaking in the SAP system. The gCTS import seems to be working with reusing the same hash again for different tables and records. However, completely leaving out the hash field leads to errors.
- How is the value "hash" calculated? Can it be calculated manually from other information (e.g. index column names and values)?
Best regards,
Jonas
