Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from SAPAUSSEC on Aug 12 at 7:18 PM You are correct which is why the details will not appear in the
dictionary if it has not been activated in a system nor do these tables
begin with 'ZZ'.
One of my replies indicated that some transactions have settings to
search archives which could be one reason for the increased access.
Another could be archiving data too quickly. It needs to be decided
whether the problem is the size of the table ZARIXFI2 or the accessing.
For the size of the table data passed its retention requirements should
be removed from the archive, whether by complete removal or offline.
For accessing yes the transactions need to be analysed. However settings
or not, the transactions responsible for the increased access need to be
identified. If the reason is not readily apparent then yes the
investigation should include tracing and step through of processing.
The ZARIX set of tables are only updated during an archiving run so the
question of when and how frequently archive is run should also be
examined. Any other access will be read only unless they are being
restructured using archiving tools.
I should also point out that it is possible to link these ZARIX tables
logically using the a feature the data relationship browser to display
all related archived documents - logistics FI and if applicable sales
Hence the accessing could also be indirect.
To protect data integrity what should not happen is to try modifying the
table directly or manually adjusting it. For information it will
eventually be necessary to archive or clean out a data warehouse
| | | ---------------Original Message---------------
From: CWK
Sent: Wednesday, August 12, 2015 10:04 AM
Subject: Archiving Infostructure ZZFI_DOCUMNITK & SAP_FI_DOC_002 for Structure Table ZARIXFI2
Adrian --
ZARIXFI2 is an info-structure table and not everyone uses the SAP "information" functionality. You may be discovering one of the reasons why -- it can easily affect performance. We experimented with some of the information structure possibilities MANY years ago (so my memory is not fresh) in order to provide some desired visibility. Real-time updating of these tables can affect performance if the info-structure in question relates to transactions or processes that generate a lot of new or changed data. I seem to recall that some info-structure can be set up so they aren't updated in real-time, but can be scheduled for update using some kind of batch functionality at night (or the weekend) -- not sure, though. We eventually decided not to use any of the info-structure (you either commit to it or you go with some other visibility solution, such as a data warehouse).
One thing to do with any table that seems to be misbehaving performance-wise is to have your DBA's check it out and make sure Statistics have been run on it.
While there are a number of SAP-owned objects and programs that begin with 'Z' I have never seen one that begins with 'ZZ' -- in my experience ZZ-programs/objects/field definitions, etc. that begin ZZ are always custom.
Good luck,
Carl |
| Reply to this email to post your response. __.____._ |   _.____.__ |
