CCSET SAP (Payment Cards: Interface for Settlement) Structure details
Description: Payment Cards: Interface for Settlement
Structure field list including key, data, relationships and ABAP select examples
CCSET 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: Interface for Settlement" 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_CCSET TYPE CCSET.
The CCSET table consists of various fields, each holding specific information or linking keys about Payment Cards: Interface for Settlement data available in SAP. These include MANDT (Client), HKONT (General Ledger Account), BUKRS (Company Code), BELNR (Accounting Document Number).. 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 CCSET 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 |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
HKONT | General Ledger Account | HKONT | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | ||
BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | 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 | VCNUM | 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 in character format | CAUTWR | DEC | 23(4) | BAPICURR | ||||
SETWR | Payment cards: Final amount in character format | CSETWR | DEC | 23(4) | BAPICURR | ||||
CCWAE | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
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 | Assigned to domain | MERCH | |||
LOCID | Payment cards: Point of receipt for the transaction | LOCID_CC | CHAR | 10 | Assigned to domain | LOCID_CC | |||
TRMID | Payment cards: Terminal | TRMID | CHAR | 10 | CHAR10 | ||||
CCBTC | Payment cards: Settlement run | CCBTC | CHAR | 10 | ALPHA | CCBTC | |||
NAME1 | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
NAME2 | Name 2 | NAME2_GP | CHAR | 35 | NAME | ||||
ORT01 | City | ORT01_GP | CHAR | 35 | TEXT35 | ||||
ORT02 | District | ORT02_GP | CHAR | 35 | TEXT35 | ||||
STRAS | House number and street | STRAS_GP | CHAR | 35 | TEXT35 | ||||
PSTLZ | Postal Code | PSTLZ | CHAR | 10 | PSTLZ | ||||
REGIO | STATE (State, Province, County) | REGIO | CHAR | 3 | T005S | REGIO | |||
LAND1 | Country Key | LAND1 | CHAR | 3 | T005 | LAND1 | LND | ||
EXDFL | Payment cards: Additional data provided | EXDFL | CHAR | 1 | XFELD | ||||
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
CCTNR | Payment Cards: Transaction Number for SET | CCTNR_SET | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
CCTTYP | Payment Cards: Transaction Type for SET | CCTTYP_SET | CHAR | 1 | CCTTYP_SET | ||||
PAYMENT_NUMBER | Transaction number | PROCESS_NO | CHAR | 9 | CHAR9 | ||||
PAYMENT_AMOUNT | Payment cards: Amount to be authorized | CAUTWV | DEC | 23(4) | BAPICURR | ||||
SPLITALLOWED | Allow split | SPLIT_EN | CHAR | 1 | SPLIT_EN | ||||
DEPOSIT | Allow settlement automatically | DEP_EN | CHAR | 1 | CHAR01 | ||||
PRIMARY_SUBRC | Primary Return Value f. Whether Transaction was Settled | 0 | |||||||
SECOND_SUBRC | Secondary Return Value for Further Information | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure CCSET using ABAP code?
As CCSET 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 CCSET as there is no data to select.How to access SAP table CCSET
Within an ECC or HANA version of SAP you can also view further information about CCSET 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