Archive infostructure customizing when active

[jespergk]

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!

[3070856]

Hi Jesper.

It is possible to "change" a customer info structure after archiving has started. It is actually quite flexible.

There is a "copy" function that will even "move" (re-assign) the entries from the one reference to the other. (I have used in partitioning but don't see why it wouldn't work elsewhere. It has a test function you can use to check). You can also delete and rebuild the entries in the info structure if all data is intact.

You are correct that you should never change a SAP std info structure or catalog. Always create your own. (Catalogue only if required).

As this post is quite old, I'll leave at that for now.

[jespergk · Accepted solution]

So we are not sure if we will do this, but I expect the following procedure would fix it. All this is available through transaction SARI and it's menues.

1. Deactivate the infostructure SAP_ISU_BCONT

2. Delete data

3. Delete program

4. Activate Infostructure

5. Fill the Infostructure (this is client dependent and will fill table ZARIXIS1)

The reason why we are a bit hesitant is because of step 5. We have clients with close to 600.000 archived contacts, so filling the structure could prove to be very time consuming or might even dump.

We are considering creating a custom report based on standard REARCH_BCONT_READ_SEQ, as that actually seems to work without these offsets, but not when too many files are opened at once. We would then use the parameters to only open the relevant files (these can be found directly in table ZARIXIS1 which should be a quick SQL search). This of course would mean the customer would have to provide reasonable search parameters, but it is much less risky.

I will report back if we decide to refill the infostructures. Hope someone can benefit from this at some point!