-
Notifications
You must be signed in to change notification settings - Fork 3
ZABAK configuration
The standard way to use abaK is by defining constant data sources in table ZABAK.
| ID | Unique ID | |
| USE_SHM | Use shared memory | |
| DESCRIPTION | Free-text description | |
| FORMAT_TYPE | Built-in format type | DB/XML/CSV |
| CONTENT_TYPE | Built-in content type | INLINE/URL/SERVER/SO10 |
| CONTENT | Constants definition | Depends on the data type |
| ID | NAME | FORMAT_TYPE | CONTENT_TYPE | CONTENT |
|---|---|---|---|---|
| GLOBAL | System-wide global constants | DB | INLINE | ZABAK_GLOBAL |
| PROJX | Constants for Project X | DB | INLINE | ZPROJX_ABAK |
| ZPROJY | Constants for program ZPROJY | CSV | SERVER | /projects/zprojy/constants.csv |
| ZPROG1 | Constants for program ZPROG1 | XML | INLINE | <abak>(...)</abak> |
This example defines 4 data sources: GLOBAL, PROJX, PROJY, ZPROG1. They reflect 4 possible different scopes. Be aware, though, that abaK does not enforce the scope in any way. The scope will be adopted by convention.
Any code that wants to use the global constants just needs to instantiate abaK with the GLOBAL id.
The custom constants tables (like ZABAK_GLOBAL and ZPROJX_ABAK) must respect a specific structure. To learn about it, please refer to Format: SAP table.
Likewise, to learn about the XML format please refer to Format: XML.
Declaring data sources in table ZABAK is the right way to use abaK. This will provide a centralized register of all the constants defined in the system. The only reason for not using ZABAK is the need to extend abaK with custom made data sources.