2006 Apr 17 10:45 PM
Hi All,
Does anyone know which table or tables store the inbox items(documents)? Also, what are some of the most common workflow tables?
Thanks in advance for your feedback.
As the system is running, index records are frequently created for the workflow runtime tables and then deleted again. This has a negative effect on performance during accesses via these indexes.
Note that you MUST shut down the R/3 System before starting the program
Depending on the data volume of the processes, indexes of the database runtime tables should be reorganized regularly (for example on a monthly basis). If you use ORACLE or INFORMIX, you can use the SAP tool SAPDBA to do this.
A reorganization should always be started after an archiving run.
The following tables / indexes should be edited in this case:
SWW_CONT - Index 0
SWW_CONTOB - Index 0
Index A
SWWWIDH - Index 0
Index A
SWWORGTASK - Index 0
Index A
SWWWIAGENT - Index 0
Index A
Index TYP
SWWWIHEAD - Index 0
Index A
Index B
Index C
Index E (as of Release 45A, if distribution is used)
SWWWIDEADL - Index 0
SWWWIRET - Index 0
Index A
SWEINSTCOU - Index B
Index C
Index D
SWWLOGHIST - Index 0
Index 1 (as of Release 4.6A)
SWZAI - Index 0 (if work queues are used)
SWZAIENTRY - Index 0 (if work queues are used)
SWZAIRET - Index 0 (if work queues are used)
SWPNODELOG - Index 0
SWPSTEPLOG - Index 0
SWP_ADM_US - Index 0 (as of Release 4.5A)
SWP_HEADER - Index 0
SWWBINDEF - Index 0 (as of Release 4.0A)
SWWRUNMETH - Index 0 (as of Release 4.0A)
SWWSWPRET - Index 0 (as of Release 4.0A)
SWP_NODEWI - Index 0 (as of Release 4.6A)
Index NOD
Tables
SWWWIHEAD Different selections of data of the table SWWWIHEAD take a long time.
<b>tRFC and qRFC tables</b>Tables ARFCSSTATE and ARFCSDATA
regards
vinod
2006 Apr 17 10:51 PM
As the system is running, index records are frequently created for the workflow runtime tables and then deleted again. This has a negative effect on performance during accesses via these indexes.
Note that you MUST shut down the R/3 System before starting the program
Depending on the data volume of the processes, indexes of the database runtime tables should be reorganized regularly (for example on a monthly basis). If you use ORACLE or INFORMIX, you can use the SAP tool SAPDBA to do this.
A reorganization should always be started after an archiving run.
The following tables / indexes should be edited in this case:
SWW_CONT - Index 0
SWW_CONTOB - Index 0
Index A
SWWWIDH - Index 0
Index A
SWWORGTASK - Index 0
Index A
SWWWIAGENT - Index 0
Index A
Index TYP
SWWWIHEAD - Index 0
Index A
Index B
Index C
Index E (as of Release 45A, if distribution is used)
SWWWIDEADL - Index 0
SWWWIRET - Index 0
Index A
SWEINSTCOU - Index B
Index C
Index D
SWWLOGHIST - Index 0
Index 1 (as of Release 4.6A)
SWZAI - Index 0 (if work queues are used)
SWZAIENTRY - Index 0 (if work queues are used)
SWZAIRET - Index 0 (if work queues are used)
SWPNODELOG - Index 0
SWPSTEPLOG - Index 0
SWP_ADM_US - Index 0 (as of Release 4.5A)
SWP_HEADER - Index 0
SWWBINDEF - Index 0 (as of Release 4.0A)
SWWRUNMETH - Index 0 (as of Release 4.0A)
SWWSWPRET - Index 0 (as of Release 4.0A)
SWP_NODEWI - Index 0 (as of Release 4.6A)
Index NOD
Tables
SWWWIHEAD Different selections of data of the table SWWWIHEAD take a long time.
<b>tRFC and qRFC tables</b>Tables ARFCSSTATE and ARFCSDATA
regards
vinod
2006 Apr 18 2:08 AM
>>which table or tables store the inbox items(documents)?
Did you try any of the SO* tables? SOFM in particular..
Regards,
Suresh Datti
| User | Count |
|---|---|
| 6 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |