Enhanced Record Identification for Tables with Non-Unique Keys
Updated 19 hours ago
by
Stephanie Krenz
Applies to: dab Nexus 1.18+, SAP Add-On 171 or newer
In version 1.18 of dab Nexus, the handling of tables without unique primary keys was redesigned in conjunction with SAP RFC module 1.71. The goal of this adjustment is to ensure complete and consistent data extraction, even for SAP tables where key fields are incomplete or empty. This ensures that all records are uniquely identified and processed correctly.
What are the impacts of this change?
The technical enhancement introduces several important aspects that must be considered when updating to dab Nexus 1.18 and RFC module 1.71:
End of the previous key definition
Until now, dab Nexus assumed that all extracted tables possessed unique primary keys. However, this is not the case for tables such as FAGLFLEXT, FMGLFLEXT, or PSGLFLEXT, as these are views. They contain fields within the primary key that use the ABAP data element G_OBJNR. In many SAP systems, these fields are padded with zeros by default. As a result, previous versions could encounter records with identical key values, leading to missing or overwritten entries in the output, or causing infinite loops during the extraction process in dab Nexus.
Extended key logic in SAP RFC module 1.71
With version 1.71, the RFC module was enhanced to include additional fields (typically all other fields in the table with the ABAP data type CHAR) in the key definition for affected tables. This ensures that records are uniquely identified even if the table does not possess a primary key with unique values.
Table | Original Key | Extended Key (new) |
FAGLFLEXT | RCLNT, RYEAR, OBJNR00 - OBJNR08, DRCRK, RPMAX | RCLNT, RYEAR, OBJNR00 - OBJNR08, DRCRK, RPMAX, RCNTR, RACCT, ACTIV, RMVCT, etc. |
FMGLFLEXT | RCLNT, RYEAR, OBJNR00 - OBJNR08, DRCRK, RPMAX | RCLNT, RYEAR, OBJNR00 - OBJNR08, DRCRK, RPMAX, RCNTR, RACCT, ACTIV, RMVCT, etc. |
PSGLFLEXT | RCLNT, RYEAR, OBJNR00 - OBJNR08, DRCRK, RPMAX | RCLNT, RYEAR, OBJNR00 - OBJNR08, DRCRK, RPMAX, RCNTR, RACCT, ACTIV, RMVCT, etc. |
Adjustment in dab Nexus 1.18
dab Nexus 1.18 automatically detects these extended keys and uses them internally for record identification. This ensures that all entries are processed uniquely—without data loss or conflicts. This change is fully automated and requires no manual adjustment of existing extraction packages.
FAGLFLEXT) used in existing scheduled tasks, a one-time new initial extraction into a new table must be performed after the update. Merging into existing tables will fail due to the changed key structure. Afterwards, the schedule can resume as usual using the new tableWhat do I need to do as an administrator?
- Ensure that dab Nexus version 1.18 or newer is installed.
- Ensure that SAP RFC module version 1.71 or newer is deployed on the SAP system.
- Perform a test extraction of affected tables (e.g.,
FAGLFLEXT) after the update to verify that all records are extracted completely. - No changes to packages or key fields are necessary – the new logic is applied automatically.
- For affected tables used in existing scheduled tasks, a new initial extraction must be performed. A new target table is required to avoid merge conflicts.
