PARTNER_PAYMENT_CARD_DATA_BLO SAP (PartnerPaymentCardDataBlockingReasons) Structure details
Description: PartnerPaymentCardDataBlockingReasons
Related tables to PARTNER_PAYMENT_CARD_DATA_BLO
Access table PARTNER_PAYMENT_CARD_DATA_BLO
Structure field list including key, data, relationships and ABAP select examples
PARTNER_PAYMENT_CARD_DATA_BLO 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 "PartnerPaymentCardDataBlockingReasons" 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_PARTNER_PAYMENT_CARD_DATA_BLO TYPE PARTNER_PAYMENT_CARD_DATA_BLO.
The PARTNER_PAYMENT_CARD_DATA_BLO table consists of various fields, each holding specific information or linking keys about PartnerPaymentCardDataBlockingReasons data available in SAP. These include TASK_CODE (Change Indicator Role (I = Insert, D=Delete etc. )), BLOCKING_REASON_KEY (), BLOCKING_REASON_DATA (), CONTROLLER ().. 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 (Deep)
SAP PARTNER_PAYMENT_CARD_DATA_BLO 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 |
| CONTROLLER | 0 | ||||||||
| TASK_CODE | Change Indicator Role (I = Insert, D=Delete etc. ) | PARTY_TASK_CODE | CHAR | 1 | |||||
| BLOCKING_REASON_KEY | 0 | ||||||||
| BLOCKING_REASON_DATA | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| VALIDITY_START_DATE | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| UPDATE_INDICATOR | Indicator whether an element carries an updated value or not | UPDATE_INDICATOR | CHAR | 5 | |||||
| VALUE | Proxy: Zeitstempel | PARTNER_DATE_TIME | STRG | 0 | |||||
| VALIDITY_END_DATE | 0 | ||||||||
| CONTROLLER | 0 | ||||||||
| UPDATE_INDICATOR | Indicator whether an element carries an updated value or not | UPDATE_INDICATOR | CHAR | 5 | |||||
| VALUE | Proxy: Zeitstempel | PARTNER_DATE_TIME | STRG | 0 | |||||
| CURRENTLY_VALID | Proxy Data Element (generated) | PARTNER_CURRENTLY_VALID | CHAR | 1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PARTNER_PAYMENT_CARD_DATA_BLO using ABAP code?
As PARTNER_PAYMENT_CARD_DATA_BLO 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 PARTNER_PAYMENT_CARD_DATA_BLO as there is no data to select.How to access SAP table PARTNER_PAYMENT_CARD_DATA_BLO
Within an ECC or HANA version of SAP you can also view further information about PARTNER_PAYMENT_CARD_DATA_BLO 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