CCTRANSACT SAP (Payment Cards: Display Transactions) Structure details
Description: Payment Cards: Display Transactions
Structure field list including key, data, relationships and ABAP select examples
CCTRANSACT 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 Cards: Display Transactions" 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_CCTRANSACT TYPE CCTRANSACT.
The CCTRANSACT table consists of various fields, each holding specific information or linking keys about Payment Cards: Display Transactions data available in SAP. These include MANDT (Client), BUKRS (Company Code), BELNR (Accounting Document Number), GJAHR (Fiscal Year).. 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 or numeric)
SAP CCTRANSACT 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 |
TRANSTAT | ALV Control: Cell Content | LVC_VALUE | CHAR | 128 | TEXT128 | ||||
MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
BELNR | Accounting Document Number | BELNR_D | CHAR | 10 | ALPHA | BELNR | BLN | ||
GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
RFZEI | Payment Card Item | RFZEI_CC | NUMC | 3 | NUM03 | ||||
CCINS | Payment cards: Card type | CCINS | CHAR | 4 | TVCIN | CCINS | |||
CCNUM | Payment cards: Card number | CCNUM | CHAR | 25 | Assigned to domain | CCNUM | |||
CCFOL | Payment cards: Payment card suffix | CCFOL | CHAR | 10 | CHAR10 | ||||
DATAB | Payment cards: Valid from | DATAB_CC | DATS | 8 | DATUM | ||||
DATBI | Payment Cards: Valid To | DATBI_CC | DATS | 8 | DATUM | ||||
CCNAME | Payment cards: Name of cardholder | CCNAME | CHAR | 40 | TEXT40 | ||||
CSOUR | Payment cards: Entry mode | CSOUR | CHAR | 1 | CSOUR | ||||
AUTWR | Payment cards: Authorized amount | AUTWR | CURR | 15(2) | WERTV8 | ||||
CCWAE | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
SETTL | Payment cards: Settlement carried out | SETTL | CHAR | 1 | XFELD | ||||
AUNUM | Payment cards: Authorization number | AUNUM | CHAR | 10 | CHAR10 | ||||
AUTRA | Payment cards: Authoriz. reference code of clearing house | AUTRA | CHAR | 15 | CHAR15 | ||||
AUDAT | Payment cards: Authorization date | AUDAT_CC | DATS | 8 | DATUM | ||||
AUTIM | Payment cards: Authorization time | AUTIM | TIMS | 6 | UZEIT | ||||
MERCH | Payment cards: Merchant ID at the clearing house | MERCH | CHAR | 15 | TCCM | MERCH | |||
LOCID | Payment cards: Point of receipt for the transaction | LOCID_CC | CHAR | 10 | TCCL | LOCID_CC | |||
TRMID | Payment cards: Terminal | TRMID | CHAR | 10 | CHAR10 | ||||
CCBTC | Payment cards: Settlement run | CCBTC | CHAR | 10 | ALPHA | CCBTC | |||
CCTYP | Payment cards: Card category | CCTYP | CHAR | 2 | TVCTY | CCTYP | |||
CCARD_GUID | Reference to Encrypted Payment Card Data | CCARDEC_GUID | CHAR | 32 | SYSUUID_C | ||||
SETRA | Payment Cards: Settlement Reference No. of Clearing House | SETRA_CC | CHAR | 15 | CHAR15 | ||||
RCAVR | Payment Cards: Result of Address Check (Address Result) | RCAVR_CC | CHAR | 4 | TCCRC | CHAR4 | |||
RCAVA | Payment Cards: Result of Address Check (Address Approval) | RCAVA_CC | CHAR | 4 | TCCRC | CHAR4 | |||
RCAVZ | Payment Cards: Result of Address Check (ZIP Code Result) | RCAVZ_CC | CHAR | 4 | TCCRC | CHAR4 | |||
RCRSP | Payment cards: Result of card check (response code) | RCRSP_CC | CHAR | 4 | TCCRC | CHAR4 | |||
RTEXT | Payment cards: Result text | RTEXT_CC | CHAR | 40 | TXT40 | ||||
REACT | Payment Cards: Response to Settlement Result | REACT_CC | CHAR | 1 | REACT_CC | ||||
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
OPBEL | Payment Cards: Document Number of Reopened Receivable | OPBEL_CC | CHAR | 10 | ALPHA | BELNR | |||
VBELN_F | Billing Document | VBELN_VF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | VF | |
VBELN_A | Sales Document | VBELN_VA | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN |
Key field | Non-key field |
How do I retrieve data from SAP structure CCTRANSACT using ABAP code?
As CCTRANSACT 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 CCTRANSACT as there is no data to select.How to access SAP table CCTRANSACT
Within an ECC or HANA version of SAP you can also view further information about CCTRANSACT 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