GTRT_CRM_BAD_PARTNER SAP (Grantor: BAD - Partner) Structure details
Dictionary Type: Structure
Description: Grantor: BAD - Partner
Description: Grantor: BAD - Partner
ABAP Code to SELECT data from GTRT_CRM_BAD_PARTNER
Related tables to GTRT_CRM_BAD_PARTNER
Access table GTRT_CRM_BAD_PARTNER
Related tables to GTRT_CRM_BAD_PARTNER
Access table GTRT_CRM_BAD_PARTNER
Structure field list including key, data, relationships and ABAP select examples
GTRT_CRM_BAD_PARTNER 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 "Grantor: BAD - Partner" 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_GTRT_CRM_BAD_PARTNER TYPE GTRT_CRM_BAD_PARTNER.
The GTRT_CRM_BAD_PARTNER table consists of various fields, each holding specific information or linking keys about Grantor: BAD - Partner data available in SAP. These include ORDERADM_H_GUID (CHAR32 data element for SYST), REF_GUID (CHAR32 data element for SYST), REF_HANDLE (Handle), REF_KIND (Object Type).. 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: Can be enhanced (character-type)
SAP GTRT_CRM_BAD_PARTNER 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 |
| PARTNER_GUID | CHAR32 data element for SYST | SYCHAR32 | CHAR | 32 | SYCHAR32 | ||||
| ORDERADM_H_GUID | CHAR32 data element for SYST | SYCHAR32 | CHAR | 32 | SYCHAR32 | ||||
| REF_GUID | CHAR32 data element for SYST | SYCHAR32 | CHAR | 32 | SYCHAR32 | ||||
| REF_HANDLE | Handle | CRMT_HANDLE | NUMC | 10 | |||||
| REF_KIND | Object Type | CRMT_OBJECT_KIND | CHAR | 1 | CRM_OBJECTKIND | ||||
| REF_PART_HANDLE | Count parameters | NUMC4 | NUMC | 4 | NUMC4 | ||||
| REF_PARTNER_FCT | Partner func. | CRMT_PARTNER_FCT | CHAR | 8 | COM_PARTNER_FCT | ||||
| REF_PARTNER_NO | Field of length 16 | CHAR16 | CHAR | 16 | CHAR16 | ||||
| REF_NO_TYPE | Partner Number Type (e.g. GUID, Pers. No., ...), Internal | CRMT_PARTNER_NO_TYPE | CHAR | 2 | COMT_PARTNER_NO_TYPE | ||||
| REF_DISPLAY_TYPE | Object Type, for Which Partner Number is to be Shown | CRMT_PARTNER_DISPLAY_TYPE | CHAR | 2 | COMT_PARTNER_NO_TYPE | ||||
| KIND_OF_ENTRY | Source of a partner in a transaction | CRMT_PARTNER_KIND_OF_ENTRY | CHAR | 1 | CRM_PARTNER_KIND_OF_ENTRY | ||||
| PARTNER_FCT | Partner func. | CRMT_PARTNER_FCT | CHAR | 8 | COM_PARTNER_FCT | ||||
| PARTNER_NO | Partner Number | CRMT_PARTNER_NO | CHAR | 32 | CRM_PARTNER_NO | ||||
| DISPLAY_TYPE | Object Type, for Which Partner Number is to be Shown | CRMT_PARTNER_DISPLAY_TYPE | CHAR | 2 | COMT_PARTNER_NO_TYPE | ||||
| NO_TYPE | Partner Number Type (e.g. GUID, Pers. No., ...), Internal | CRMT_PARTNER_NO_TYPE | CHAR | 2 | COMT_PARTNER_NO_TYPE | ||||
| MAINPARTNER | Main Partner (For Ambiguous Partner Functions) | CRMT_PARTNER_MAIN | CHAR | 1 | CRM_BOOLEAN | ||||
| RELATION_PARTNER | CHAR32 data element for SYST | SYCHAR32 | CHAR | 32 | SYCHAR32 | ||||
| ADDR_NR | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| ADDR_NP | Person number | AD_PERSNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_PERSNUM | CDT | ADDRESS |
| ADDR_TYPE | Address type (1=Organization, 2=Person, 3=Contact person) | AD_ADRTYPE | CHAR | 1 | AD_ADRTYPE | ||||
| ADDR_ORIGIN | Origin of a Partner Address | CRMT_ADDR_ORIGIN_MD | CHAR | 1 | CRM_ADDR_ORIGIN_MD | ||||
| STD_BP_ADDRESS | Standard Business Partner Address (Depending on Addr.Type) | CRMT_PARTNER_STD_BP_ADDRESS | CHAR | 1 | XFELD | ||||
| ADDR_OPERATION | Transaction for BP Address Determination | BU_OPERATION | CHAR | 6 | Assigned to domain | BU_OPERATION | |||
| CALENDAR | Maintain Calendar for the Partner? | CRMT_PARTNER_CALENDAR | CHAR | 1 | CRM_BOOLEAN | ||||
| DISABLED | No INBOX Selection for the Partner | CRMT_PARTNER_DISABLED | CHAR | 1 | CRM_BOOLEAN | ||||
| ERROR_FLAG | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| PARTNER_SRC_SYS | Logical System from Which Partner Originates | COMT_PARTNER_SRC_SYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| BP_PARTNER_GUID | CHAR32 data element for SYST | SYCHAR32 | CHAR | 32 | SYCHAR32 | ||||
| PARTNER_PFT | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
| PFT_SUBTYPE | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
| GUID | CHAR32 data element for SYST | SYCHAR32 | CHAR | 32 | SYCHAR32 | ||||
| ADDRESS_GUID | CHAR32 data element for SYST | SYCHAR32 | CHAR | 32 | SYCHAR32 |
| Key field | Non-key field |
How do I retrieve data from SAP structure GTRT_CRM_BAD_PARTNER using ABAP code?
As GTRT_CRM_BAD_PARTNER 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 GTRT_CRM_BAD_PARTNER as there is no data to select.How to access SAP table GTRT_CRM_BAD_PARTNER
Within an ECC or HANA version of SAP you can also view further information about GTRT_CRM_BAD_PARTNER 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