So we all know that S/4Hana is the latest version and the future of SAP but what about the tables we are familiar with, are they still available and what do tables like OA2C_CLIENT look like in an S4Hana SAP system. If you havent seen or logged into an S/4Hana system you might be surprise how similar it looks to the previous ERP/ECC version. Infact when using using the gui it is difficult to tell the difference, and for many of database tables the same is true.
Object Name: OA2C_CLIENT
Dictionary Type: Transparent table
Description: OAuth 2.0 Clients
Field | Data Element | Data Type | length (Dec) | Check table | Description | Conversion Routine | Domain Name | MemoryID | AppClass | SHLP | SHLP Field | ConvExit |
MANDT | MANDT | CLNT | 3(0) | Client | MANDT | TEST | ||||||
CLIENT_UUID | OA2C_UUID | CHAR | 32(0) | OAuth 2.0 Client UUID | OA2C_UUID | |||||||
PROFILE | OA2C_PROFILE | CHAR | 30(0) | OAuth 2.0 Client Profile | OA2C_PROFILE | |||||||
SPS_NAME | OA2C_TYPE | CHAR | 20(0) | OAuth 2.0 Service Provider Type | OA2C_TYPE | |||||||
CLIENT_ID | OA2C_CLIENT_ID | SSTR | 261(0) | OAuth 2.0 Client ID | OA2C_CLIENT_ID | |||||||
CREATED_BY | OA2C_CREATED_BY | CHAR | 12(0) | Created By | AS4USER | |||||||
CREATED_ON | OA2C_CREATED_ON | DATS | 8(0) | Created On | AS4DATE | |||||||
CREATED_AT | OA2C_CREATED_AT | TIMS | 6(0) | Created At | AS4TIME | |||||||
CHANGED_BY | OA2C_CHANGED_BY | CHAR | 12(0) | Changed By | AS4USER | |||||||
CHANGED_ON | OA2C_CHANGED_ON | DATS | 8(0) | Changed On | AS4DATE | |||||||
CHANGED_AT | OA2C_CHANGED_AT | TIMS | 6(0) | Changed At | AS4TIME | |||||||
AUTHORIZATION_ENDPOINT | OA2C_AUTHORIZATION_ENDPOINT | STRG | 0(0) | OAuth 2.0 Authorization Endpoint | OA2C_AUTHORIZATION_ENDPOINT | |||||||
TOKEN_ENDPOINT | OA2C_TOKEN_ENDPOINT | STRG | 0(0) | OAuth 2.0 Token Endpoint | OA2C_TOKEN_ENDPOINT | |||||||
REVOCATION_ENDPOINT | OA2C_REVOCATION_ENDPOINT | STRG | 0(0) | OAuth 2.0 Revocation Endpoint | OA2C_REVOCATION_ENDPOINT | |||||||
AUTHENTICATION_METHOD | OA2C_CLIENT_AUTHENTICATION | INT4 | 10(0) | OAuth 2.0 Client Authentication Method | OA2C_CLIENT_AUTHENTICATION | |||||||
AUTH_CODE_ALLOWED | CHAR | 1(0) | OAuth 2.0 Grant Type Authorization Code allowed | |||||||||
SAML20_ALLOWED | CHAR | 1(0) | OAuth 2.0 Grant Type SAML 2.0 Bearer Assertion allowed | |||||||||
REFRESH_ALLOWED | CHAR | 1(0) | OAuth 2.0 Grant Type Refresh allowed | |||||||||
RT_VALIDITY | OA2C_RT_VALIDITY | INT4 | 10(0) | OAuth 2.0 Client Refresh Token Validity [d] | OA2C_RT_VALIDITY | |||||||
REDIRECT_URI_HOST | OA2C_REDIRECT_URI_HOST | STRG | 0(0) | OAuth 2.0 Client Redirect URI Host | OA2C_REDIRECT_URI_HOST | |||||||
REDIRECT_URI_PORT | INT4 | 10(0) | OAuth 2.0 Client Redirect URI registered @ auth. server | |||||||||
CS_SEGMENT_COUNT | INT4 | 10(0) | Number of Token Segments in Secstore | |||||||||
SAML20_NAMEFMT | OA2C_SAML20_NAMEFMT | INT4 | 10(0) | OAuth 2.0 Client SAML 2.0 NameID Format | ||||||||
SAML20_AUDIENCE | SAML2_ENTITY_NAME | STRG | 1024(0) | SAML2 Entity ID | SAML2_ENTITY_ID | |||||||
TARGET_PATH | OA2C_TARGET_PATH | STRG | 0(0) | OAuth 2.0 Client Target Path | OA2C_TARGET_PATH | |||||||
RESOURCE_ACCESS | OA2C_PARAM_KIND | CHAR | 1(0) | OAuth 2.0 Client - ICF Client Interface: Parameter kind | OA2C_PARAM_KIND | |||||||
USER_EMAIL_NUM | OA2C_USER_EMAIL_NUM | NUMC | 3(0) | OAuth 2.0 Client User E-Mail Address Number | NUMC3 | |||||||
CONFIGURATION | OA2C_CONFIGURATION | CHAR | 32(0) | OAuth 2.0 Client Configuration | OA2C_CONFIGURATION |