BAPICCARD SAP (Communication Table: Means of Payment Order/Billing Document) Structure details
Description: Communication Table: Means of Payment Order/Billing Document
Structure field list including key, data, relationships and ABAP select examples
BAPICCARD 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 "Communication Table: Means of Payment Order/Billing Document" 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_BAPICCARD TYPE BAPICCARD.
The BAPICCARD table consists of various fields, each holding specific information or linking keys about Communication Table: Means of Payment Order/Billing Document data available in SAP. These include CC_NUMBER (Payment cards: Card number), CC_VALID_T (Payment Cards: Valid To), CC_NAME (Payment cards: Name of cardholder), BILLAMOUNT (Value to be billed on the date specified in billing plan).. 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 BAPICCARD 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 |
| CC_TYPE | Payment cards: Card type | CCINS | CHAR | 4 | TVCIN | CCINS | |||
| CC_NUMBER | Payment cards: Card number | CCNUM | CHAR | 25 | VCNUM | CCNUM | |||
| CC_VALID_T | Payment Cards: Valid To | DATBI_CC | DATS | 8 | DATUM | ||||
| CC_NAME | Payment cards: Name of cardholder | CCNAME | CHAR | 40 | TEXT40 | ||||
| BILLAMOUNT | Value to be billed on the date specified in billing plan | CC_BILL_VA | DEC | 23(4) | BAPICURR | ||||
| AUTH_FLAG | Payment cards: Authorization to be transferred | FLGAU | CHAR | 1 | XFELD | ||||
| AUTHAMOUNT | Payment cards: Authorized amount | CC_AUTH_VA | DEC | 23(4) | BAPICURR | ||||
| CURRENCY | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
| CURR_ISO | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
| AUTH_DATE | Payment cards: Authorization date | AUDAT_CC | DATS | 8 | DATUM | ||||
| AUTH_TIME | Payment cards: Authorization time | AUTIM | TIMS | 6 | UZEIT | ||||
| AUTH_CC_NO | Payment cards: Authorization number | AUNUM | CHAR | 10 | CHAR10 | ||||
| AUTH_REFNO | Payment cards: Authoriz. reference code of clearing house | AUTRA | CHAR | 15 | CHAR15 | ||||
| CC_REACT | Payment cards: Response to authorization checks | REACT_SD | CHAR | 1 | REACT_SD | ||||
| CC_RE_AMOUNT | Currency amount in BAPI interfaces | BAPICURR_D | DEC | 23(4) | BAPICURR | ||||
| GL_ACCOUNT | G/L Account Number | SAKNR | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | SAK | C_SAKNR |
| CC_STAT_EX | Payment cards: Status when external system is called? | CCALL | CHAR | 1 | CCALL | ||||
| CC_REACT_T | Payment cards: Result text | RTEXT_CC | CHAR | 40 | TXT40 | ||||
| VIRT_CARD | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| MERCHIDCL | Payment cards: Merchant ID at the clearing house | MERCH | CHAR | 15 | Assigned to domain | MERCH | |||
| .INCLU--AP | 0 | ||||||||
| PRE_AUTH | Payment cards: Preauthorization | CCPRE | CHAR | 1 | XFELD | ||||
| CC_SEQ_NO | Payment cards: Payment card suffix | CCFOL | CHAR | 10 | CHAR10 | ||||
| AMOUNTCHAN | Payment cards: Amount changed | CCVAL | CHAR | 1 | XFELD | ||||
| AUTHORTYPE | Payment cards: Authorization type | CCAUA | CHAR | 1 | CCAUA | ||||
| DATAORIGIN | Payment cards: Entry mode | CSOUR | CHAR | 1 | CSOUR | ||||
| RADRCHECK1 | Payment Cards: Result of Address Check (Address Result) | RCAVR_CC | CHAR | 4 | CHAR4 | ||||
| RADRCHECK2 | Payment Cards: Result of Address Check (Address Approval) | RCAVA_CC | CHAR | 4 | CHAR4 | ||||
| RADRCHECK3 | Payment Cards: Result of Address Check (ZIP Code Result) | RCAVZ_CC | CHAR | 4 | CHAR4 | ||||
| RCARDCHECK | Payment cards: Result of card check (response code) | RCRSP_CC | CHAR | 4 | CHAR4 | ||||
| CC_LIMITED | Payment cards: Limit amount | CCBEG | CHAR | 1 | XFELD | ||||
| .INCLU--AP | 0 | ||||||||
| CC_VERIF_VALUE | Card Verification Value | CVVAL | CHAR | 6 | CVVAL | ||||
| CC_CTRL_FIELD | Control Field for Card Verification Value | CVVCT | CHAR | 1 | CVVCT | ||||
| CC_IN_USE_ST | Usage Status for Card Verification Value | CVVST | CHAR | 1 | CVVST |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPICCARD using ABAP code?
As BAPICCARD 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 BAPICCARD as there is no data to select.How to access SAP table BAPICCARD
Within an ECC or HANA version of SAP you can also view further information about BAPICCARD 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