PYCD_PAYT_CARD_SUITE_CHGREQ SAP (Payment Card SUITE Change Request Message) Structure details
Description: Payment Card SUITE Change Request Message
Related tables to PYCD_PAYT_CARD_SUITE_CHGREQ
Access table PYCD_PAYT_CARD_SUITE_CHGREQ
Structure field list including key, data, relationships and ABAP select examples
PYCD_PAYT_CARD_SUITE_CHGREQ 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 "Payment Card SUITE Change Request Message" 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_PYCD_PAYT_CARD_SUITE_CHGREQ TYPE PYCD_PAYT_CARD_SUITE_CHGREQ.
The PYCD_PAYT_CARD_SUITE_CHGREQ table consists of various fields, each holding specific information or linking keys about Payment Card SUITE Change Request Message data available in SAP. These include PAYMENT_CARD_SUITE_CRT_REQUEST (), CONTROLLER (), MESSAGE_HEADER (), 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 PYCD_PAYT_CARD_SUITE_CHGREQ 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 | ||||||||
PAYMENT_CARD_SUITE_CRT_REQUEST | 0 | ||||||||
CONTROLLER | 0 | ||||||||
MESSAGE_HEADER | 0 | ||||||||
CONTROLLER | 0 | ||||||||
ID | Unique identifier of a business document in a (technical) me | BSFND_NOSC_BUSINESS_DOC_MSG_ID | CHAR | 35 | |||||
UUID | Universally Unique Identifier (without attributes) | RMPS_ATTRIBUTEINDEPENDENT_UUID | CHAR | 36 | |||||
REFERENCE_ID | Unique identifier of a business document in a (technical) me | BSFND_NOSC_BUSINESS_DOC_MSG_ID | CHAR | 35 | |||||
REFERENCE_UUID | Universally Unique Identifier (without attributes) | RMPS_ATTRIBUTEINDEPENDENT_UUID | CHAR | 36 | |||||
PAYMENT_CARD | 0 | ||||||||
CONTROLLER | 0 | ||||||||
BLK_LIST_CMPL_TRNS_IND | Indicator is the representation of a situation that has exac | RMPS_INDICATOR | CHAR | 1 | XSDBOOLEAN | ||||
ID | Proxy Data Element (generated) | BSFND_NOSC_PAYMENT_CARD_ID | CHAR | 25 | |||||
CATEGORY_CODE | Proxy Data Element (generated) | BSFND_PAY_CARD_CATEGORY_CODE | CHAR | 2 | |||||
TYPE_CODE | Proxy Data Element (generated) | BSFND_PAYMENT_CARD_TYPE_CODE | CHAR | 4 | |||||
VALIDITY_START_DATE | Date | RMPS_DATE | DATS | 8 | XSDDATE_D | ||||
EXPIRATION_DATE | Date | RMPS_DATE | DATS | 8 | XSDDATE_D | ||||
ISSUE_DATE | Date | RMPS_DATE | DATS | 8 | XSDDATE_D | ||||
HOLDER_NAME | LANGUAGEINDEPENDENT_MEDIUM_Name | RMPS_LANGU_INDPNDT_MEDIUM_NAME | CHAR | 40 | |||||
ISSUER_NAME | LANGUAGEINDEPENDENT_MEDIUM_Name | RMPS_LANGU_INDPNDT_MEDIUM_NAME | CHAR | 40 | |||||
BLOCK | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure PYCD_PAYT_CARD_SUITE_CHGREQ using ABAP code?
As PYCD_PAYT_CARD_SUITE_CHGREQ 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 PYCD_PAYT_CARD_SUITE_CHGREQ as there is no data to select.How to access SAP table PYCD_PAYT_CARD_SUITE_CHGREQ
Within an ECC or HANA version of SAP you can also view further information about PYCD_PAYT_CARD_SUITE_CHGREQ 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