SAP ABAP Data Element CLB_APPLICATION_ID_EXTERNAL (Collaboration: Application ID at Collaboration Platform)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-STW (Application Component) Social Media ABAP Integration Library
⤷
S_CLB_COMMON (Package) Common Objects and Services of the Collaboration Platform

⤷

⤷

Basic Data
Data Element | CLB_APPLICATION_ID_EXTERNAL |
Short Description | Collaboration: Application ID at Collaboration Platform |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CLB_APPLICATION_ID_EXTERNAL | |
Data Type | CHAR | Character String |
Length | 255 | |
Decimal Places | 0 | |
Output Length | 255 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Ext. Appl. |
Medium | 20 | Ext. Application ID |
Long | 30 | External Application ID |
Heading | 30 | External Application ID |
Documentation
Definition
The external application ID is retrieved from the Service Provider, when registering the application.
Use
When collaborating with a Service Provider (such as SAP Jam), it is mandatory to register the application (such as SAIL) with this Service Provider. The resulting ID must be entered in table CLBC_APPLI_PLATF.
Dependencies
If application-based identification via OAuth is necessary, the OAuth consumer token and secret that can be retrieved from a Service Provider (for instance SAP Jam) must also be registered with the on-premise system.
The token (key) is maintained in CLBC_APPLI_PLATF whereas the secret must be stored in the Secure Store.
The SSF application must be entered in CLBC_APPLI_PLATF-SSFAPPL.
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 732 |