SAP table FMFGUSKONTKEY (Key for US Account Assignments)
SAP table FMFGUSKONTKEY has 2 primary key fields being MANDT,USKONTKEY.
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 | * | MANDT | |
| USKONTKEY | United States Federal Government Fields | CHAR | 22 | 0 | FMFG_US_KEY | ||
| HASHVERS | Version for Hash Code | CHAR | 2 | 0 | FMFG_HASHVERS | ||
| HASHCODE | Hash Code to FG Data Fields | CHAR | 16 | 0 | FMFG_HASHCODE | ||
| HASHDEF | Hash Code Defect (Collisions) | CHAR | 2 | 0 | FMFG_HASHDEF | ||
| TP_SUBLEVL | Sublevel Prefix (SP) for Trading Partner | CHAR | 2 | 0 | FMFG_TP_SUBLEVL | ||
| TP_AGENCID | Agency Identifier (AID) for Trading Partner | CHAR | 3 | 0 | FMFG_TP_AGENCID | ||
| TP_ALTRAID | Allocation Transfer Agency Identifier (ATA) Trading Partner | CHAR | 3 | 0 | FMFG_TP_ALTRAID | ||
| TP_BEGPER | Beginning Period of Availability (BPOA) for Trading Partner | NUMC | 4 | 0 | FMFG_TP_BEGPER | ||
| TP_ENDPER | Ending Period of Availability (EPOA) for Trading Partner | NUMC | 4 | 0 | FMFG_TP_ENDPER | ||
| TP_AVTYPE | Availability Type Code (A) for Trading Partner | CHAR | 1 | 0 | FMFG_TP_AVTYPE | ||
| TP_MAIN_ACCT | Main Account for Trading Partner | CHAR | 4 | 0 | FMFG_TP_MAIN_ACCT | ||
| TP_SUB_ACCT | Subaccount for Trading Partner | CHAR | 3 | 0 | FMFG_TP_SUB_ACCT | ||
| TP_BETC | Business Event Type Code for Trading Partner | CHAR | 10 | 0 | FMFG_TP_BETC |