SAP table QIWKTAB (Table of qRFC Inbound Queues to Be Activated Automatically)
SAP table QIWKTAB has 3 primary key fields being MANDT,TYPE,QNAME.
If you're only analyzing data from a single SAP instance you may omit field MANT in your relationships as it will we the same across the entire dataset. On the other hand, if you're combining data from multiple SAP instances you need to take MANDT into account.
Field | Description | Data Type | Length | Decimals | Checktable | Data Element | |
---|---|---|---|---|---|---|---|
MANDT | Client ID | CLNT | 3 | 0 | * | SYMANDT | |
TYPE | Internal Data Element | CHAR | 1 | 0 | SYINPUT | ||
QNAME | Name of tRFC Queue | CHAR | 24 | 0 | TRFCQNAM | ||
EXEMODE | Registration Mode | CHAR | 1 | 0 | EXEMODE | ||
WKSTATE | Internal Data Element | CHAR | 1 | 0 | SYINPUT | ||
MAXTIME | Maximum Runtime of Queue/Destination Scheduler | INT4 | 10 | 0 | DEST_MAXRUNTIME | ||
DATUM | System Date | DATS | 8 | 0 | SYDATUM | ||
UZEIT | System Time | TIMS | 6 | 0 | SYUZEIT | ||
RFCMESS | Internal Data Element | CHAR | 72 | 0 | SYENTRY | ||
USERDEST | "Local" RFC destination with LOGON details | CHAR | 32 | 0 | * | USERDEST | |
GROUPDEST | Logon/Server Group Name | CHAR | 20 | 0 | RZLLI_APCL | ||
TDELAY | Delay Between Two Registration Retries | INT4 | 10 | 0 | TDELAY | ||
NRETRY | No. of attempts | NUMC | 4 | 0 | RETRY | ||
USERID | User Name | CHAR | 12 | 0 | SYUNAME | ||
NACTIVE | No. of attempts | NUMC | 4 | 0 | RETRY | ||
HOSTID | Logical destination (specified in function call) | CHAR | 32 | 0 | * | RFCDEST | |
SCHED_WATCH | Monitoring Time for Destination/Queue Scheduler | INT4 | 10 | 0 | SCHED_WATCH_TIME |