SAP table TCC20 (ECM: digital signature network - change master)
SAP table TCC20 has 2 primary key fields being MANDT,H_SIGNNET.
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 | CLNT | 3 | 0 | T000 | MANDT | |
H_SIGNNET | Signature network - ECR / ECO | CHAR | 8 | 0 | CC_DSNETH | ||
H_TOCHECK | Signature Strategy "Check Engineering Change Request" | CHAR | 8 | 0 | CC_H_TOCHECK | ||
H_CHECKED | Signature strategy "ECR checked" | CHAR | 8 | 0 | CC_H_CHECKED | ||
H_APPROVE | Signature strategy "Approve ECR" | CHAR | 8 | 0 | CC_H_APPROVE | ||
H_WITHDRAW | Signature strategy: "Withdraw approval" | CHAR | 8 | 0 | CC_H_WITHDRAW | ||
H_REJECT | Signature strategy "Reject ECR" | CHAR | 8 | 0 | CC_H_REJECT | ||
H_CONVERT | Signature strategy "Convert ECR" | CHAR | 8 | 0 | CC_H_CONVERT | ||
H_COMPLET | Signature strategy "Order complete" | CHAR | 8 | 0 | CC_H_COMPLET | ||
H_INCOMPL | Signature strategy "ECO incomplete" | CHAR | 8 | 0 | CC_H_INCOMPL | ||
H_LOCK | Signature strategy "Lock ECR/ECO" | CHAR | 8 | 0 | CC_H_LOCK | ||
H_UNLOCK | Signature strategy "Unlock ECR/ECO" | CHAR | 8 | 0 | CC_H_UNLOCK | ||
H_CLOSE | Signature strategy "Close order" | CHAR | 8 | 0 | CC_H_CLOSE | ||
H_RELEASE | Signature strategy "Release ECO" | CHAR | 8 | 0 | CC_H_RELEASE |