Skip to content

AOBJ: Archiving Object #804

Closed
Closed

Description

@larshp

Database table: ARCH_OBJ + other?

define via transaction AOBJ

function modules:
ARCHIVE_OBJECT_GET
ARCHIVE_OBJECT_CREATE
ARCHIVE_OBJECT_DELETE
ARCHIVE_OBJECT_STRUCTURE_SET
function group ARGN

Activity

  1. larshp commented on Jul 4, 2017

    @larshp
    MemberAuthor

    if anyone wants to make a PR, this looks like a quite easy task

    just add a comment here if somebody starts working on it

  2. self-assigned this
    on Jul 5, 2017
  3. bigld commented on Jul 5, 2017

    @bigld
    Collaborator

    I'll do this at the weekend

  4. mbtools commented on Apr 4, 2022

    @mbtools
    Member

    @bigld do you have a custom archive object that you could add to https://github.com/abapGit-tests/AOBJ.git for testing?

    Thanks!

  5. added a commit that references this issue on Sep 7, 2022
    e8ec3d6
  6. xtough commented on Sep 8, 2022

    @xtough

    Hi @mbtools and @larshp ,
    Sorry for throwing a spanner in the works. But SAP is currently also working on an AOBJ handler for abapGit, however with a JSON-based format based on AFF (see https://github.com/SAP/abap-file-formats ). We should avoid creating 2 incompatible formats that would need to be aligned afterwards. At least we should discuss the options. What do you think?
    Thanks, Christoph

  7. mbtools commented on Sep 8, 2022

    @mbtools
    Member

    @xtough I'm not clear about the release compatibility of AFF. Will the JSON version also work with all lower releases supported by abapGit? >=702

  8. xtough commented on Sep 8, 2022

    @xtough

    @mbtools I see your point. There is no easy answer to that. Please bear with me for a few more days until I had a chance to talk to some colleagues that are currently on vacation.

  9. xtough commented on Sep 26, 2022

    @xtough

    Hi @mbtools ,
    sorry for the late response. The short answer is "yes", it is possible to use JSON based metadata also lower releases like 702, as shown recently with the experimental handler for INTF in #5658 . A handler just has to support the format as described in AFF, but does not necessarily have to depend on the AFF framework, which is obviously only available in newer releases. This even makes it possible to reuse the type interfaces like https://github.com/SAP/abap-file-formats/blob/main/file-formats/aobj/type/zif_aff_aobj_v1.intf.abap for AOBJ. Of course, the JSON-based format proposal for AOBJ currently focused on cloud features but missing older features can be added incrementally in a compatible way.
    Cheers, Christoph

  10. mbtools commented on Sep 26, 2022

    @mbtools
    Member

    Alright. We will wait for the AOBJ JSON handler and not implement an XML version.

  11. mbtools commented on Dec 2, 2022

    @mbtools
    Member

    To implement this object type, create a PR or reopen this issue for further discussion.

  12. changed the title [-]AOBJ Archiving Object[/-] [+]AOBJ: Archiving Object[/+] on Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

ciFindings from CI test runsnew featureNew feature or requestserializationTranslate between object types and files

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions