SSTR_SRT_WSP_IBCR_CCON_TRANS SAP (SRT: IBC Reference Assignment to Provider Systems incl. IBCR) Structure details
Description: SRT: IBC Reference Assignment to Provider Systems incl. IBCR
Related tables to SSTR_SRT_WSP_IBCR_CCON_TRANS
Access table SSTR_SRT_WSP_IBCR_CCON_TRANS
Structure field list including key, data, relationships and ABAP select examples
SSTR_SRT_WSP_IBCR_CCON_TRANS is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "SRT: IBC Reference Assignment to Provider Systems incl. IBCR" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_SSTR_SRT_WSP_IBCR_CCON_TRANS TYPE SSTR_SRT_WSP_IBCR_CCON_TRANS.
The SSTR_SRT_WSP_IBCR_CCON_TRANS table consists of various fields, each holding specific information or linking keys about SRT: IBC Reference Assignment to Provider Systems incl. IBCR data available in SAP. These include DEST_KEY (SRT: Key/ID of a provider system), RECEIVER_TYPE (SRT: Identifiable Business Context Receiver Type), RECEIVER_NAME (SRT: Identifiable Business Context Receiver Name), RECEIVER_SYSTEM (SRT: Identifiable Business Context Receiver System).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP SSTR_SRT_WSP_IBCR_CCON_TRANS structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
IBCR_ID | SRT: Identifiable Business Context Reference ID | SRT_WSP_IBCR_ID | CHAR | 32 | SYSUUID_C | ||||
DEST_KEY | SRT: Key/ID of a provider system | SRT_WSP_SYSTEM_KEY | CHAR | 32 | SYSUUID_C | ||||
RECEIVER_TYPE | SRT: Identifiable Business Context Receiver Type | SRT_WSP_IBC_RECEIVER_TYPE | CHAR | 10 | CHAR10 | ||||
RECEIVER_NAME | SRT: Identifiable Business Context Receiver Name | SRT_WSP_IBC_RECEIVER_NAME | CHAR | 40 | CHAR40 | ||||
RECEIVER_SYSTEM | SRT: Identifiable Business Context Receiver System | SRT_WSP_IBC_RECEIVER_SYSTEM | CHAR | 120 | SRT_WSP_IBC_RECEIVER_SYSTEM | ||||
CREATED_BY | User Name | UNAME | CHAR | 12 | UNAME | ||||
CREATED_ON | Date of Last Change | UDATUM | DATS | 8 | SYDATS | ||||
CREATED_AT | Time | UZEIT | TIMS | 6 | UZEIT | ||||
CREATED_TC | Transaction Code | TCODE | CHAR | 20 | Assigned to domain | TCODE | TCD | ||
CREATED_CP | ABAP Program Name | PROGRAMM | CHAR | 40 | Assigned to domain | PROGRAMM | RID | ||
IBCR_STRUCTURE | 0 | ||||||||
ID | SRT: Identifiable Business Context Reference ID | SRT_WSP_IBCR_ID | CHAR | 32 | SYSUUID_C | ||||
RECEIVER_TYPE | SRT: Identifiable Business Context Receiver Type | SRT_WSP_IBC_RECEIVER_TYPE | CHAR | 10 | CHAR10 | ||||
RECEIVER_NAME | SRT: Identifiable Business Context Receiver Name | SRT_WSP_IBC_RECEIVER_NAME | CHAR | 40 | CHAR40 | ||||
RECEIVER_SYSTEM | SRT: Identifiable Business Context Receiver System | SRT_WSP_IBC_RECEIVER_SYSTEM | CHAR | 120 | SRT_WSP_IBC_RECEIVER_SYSTEM | ||||
LAST_CHANGE | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
VALID_FROM | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
VALID_TO | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
APPLICATION_COMPONENT_ID | Application component ID | UFPS_POSID | CHAR | 24 | UFPS_POSID | ||||
DESCRIPTIONS | 0 | ||||||||
USAGES | 0 | ||||||||
ASSIGNMENT | 0 | ||||||||
ID | SRT: Identifiable Business Context Reference ID | SRT_WSP_IBCR_ID | CHAR | 32 | SYSUUID_C | ||||
TYPE | WSP Profile Type | SRT_WSP_PROFILE_TYPE | CHAR | 4 | SRT_WSP_PROFILE_TYPE | ||||
SYSTEM_KEY | SRT: Key/ID of a provider system | SRT_WSP_SYSTEM_KEY | CHAR | 32 | SYSUUID_C | ||||
CREATED_BY | User Name | UNAME | CHAR | 12 | UNAME | ||||
CREATED_ON | Date of Last Change | UDATUM | DATS | 8 | SYDATS | ||||
CREATED_AT | Time | UZEIT | TIMS | 6 | UZEIT | ||||
CREATED_TC | Transaction Code | TCODE | CHAR | 20 | TCODE | TCD | |||
CREATED_CP | ABAP Program Name | PROGRAMM | CHAR | 40 | PROGRAMM | RID | |||
CHANGED_BY | User Name | UNAME | CHAR | 12 | UNAME | ||||
CHANGED_ON | Date of Last Change | UDATUM | DATS | 8 | SYDATS | ||||
CHANGED_AT | Time | UZEIT | TIMS | 6 | UZEIT | ||||
CHANGED_TC | Transaction Code | TCODE | CHAR | 20 | TCODE | TCD | |||
CHANGED_CP | ABAP Program Name | PROGRAMM | CHAR | 40 | PROGRAMM | RID | |||
TECHNICAL_CONTACT | 0 | ||||||||
FIRST_NAME | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
LAST_NAME | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
PHONE_NUMBERS | 0 | ||||||||
EMAIL_ADDRESSES | 0 | ||||||||
BUSINESS_CONTACT | 0 | ||||||||
FIRST_NAME | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
LAST_NAME | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
PHONE_NUMBERS | 0 | ||||||||
EMAIL_ADDRESSES | 0 | ||||||||
IBCNOTES | 0 | ||||||||
IBCRNOTES | 0 | ||||||||
RECEIVER_TYPE_LONGTEXTS | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure SSTR_SRT_WSP_IBCR_CCON_TRANS using ABAP code?
As SSTR_SRT_WSP_IBCR_CCON_TRANS is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on SSTR_SRT_WSP_IBCR_CCON_TRANS as there is no data to select.How to access SAP table SSTR_SRT_WSP_IBCR_CCON_TRANS
Within an ECC or HANA version of SAP you can also view further information about SSTR_SRT_WSP_IBCR_CCON_TRANS and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects