Closed larshp closed 3 years ago
We have to consider interface names for R3TR objects and most probably LIMU objects.
Furthermore, we have to define the naming for reuse interfaces (like the one for classes and interfaces; see #143).
To rename the interface names stored in this repostitory, a issue #151 was opened.
Therefore, can we close this one? The documentation about the interface name was add in #146.
The name of the interface follows the pattern zifaff
_v .
Yes, we can close this one
agree, its dococumented
and renaming is https://github.com/SAP/abap-file-formats/issues/151
Specification for the interface names of R3TR objects is available.
Unfortunately, it is still unclear how interface names for LIMU objects shall be handled. See comments in #153.
we currently have:
INTF
andCHKC
are the TADIR R3TR names, which are guaranteed to be unique, I suggest leaving out the "_oo" and "_atc" parts