on ‎2020 Dec 10 8:58 PM
Hi Experts
We have archived object ISU_BCONT using standard infostructure SAP_ISU_BCONT.
When we try to read from archive through transaction SARI we can see the list, but it is not possible to open object (business contact). By debugging I found out that the infostructure does not have any values in the two customizing options "Field name Processing" and "Offset Processing". It works fine in our test system which have a "D" in both ("File name is data field" and "Offset is data field"). The customizing table is AIND_STR1.
I am guessing it is not possible to change the infostructure after the archiving have been done? Even changing a standard infostructure might not be possible?
We have also tried to use the report "REARCH_BCONT_READ_SEQ". That seems to try to open all archiving files in the beginning, but that also fails which seems to be a simple timeout - as far as I can tell it loops through ALL records which is not feasible. This even when a specific object and date is given as input.
Any help would be deeply appreciated!
Request clarification before answering.
Thinking out loud on text, so be warned 🙂
So it seems the infostructure has generated table ZARIXIS1 without the offset field "ARCHIVEOFS" because of the wrong costumizing mentioned above.
From SARI customizing I can delete the entries in the table and delete the program after inactivating the infostructure:

When this is done I might be able to change the customizing somehow, more on that later.Then I activate the structure and try to fill it again and this actully seems to fill table ZARIXIS1 again with correct offset (at least in our test system which already had an offset, so might not be the case in production):

That still leaves me with the question - how can I change the infostructure customizing? The table behind is client independant: AIND_STR1. When I try to customize it from our development system, those fields are not open for editing.
That led me to "Field Catalogues" and the table "AIND_SV1S" which seems to be what dictates these values. To my surprise it seems that this is setup correctly:

So how can it be that the infostructure is not generated correctly when the field catalogue specifies it? Maybe it is timing, would you dare to try in a production client? (inactivate, delete table, delete program, reactivate, fill structures)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 5 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.