Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from hovering_yogi on Aug 12 at 10:08 AM I certainly think Adrian's response was overly harsh Horacio and perhaps he will pass on an apology. Adrian although you clearly understand archiving you mention looking at programs that are using the archive and Horacio's suggestions as to an approach (even not understanding what the table is used for and whether it is "standard" or custom) would identify those transactions, and potentially a specific one that a user is frequently running and is selecting archive data when they ideally should not. At least in my experience it would (and like Horacio I am also not familiar with archiving so could be wrong) but the fundamental principles of SAP hold true across all database level access I believe. When everyone's using their own time to try and help others I'm not sure the "I know better than you" mantra added a great deal. Steve
| | | ---------------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. __.____._ | _.____.__ |