BAPICCARDM 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
BAPICCARDM 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_BAPICCARDM TYPE BAPICCARDM.
The BAPICCARDM 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 SD_DOC (Sales and Distribution Document Number), CC_TYPE (Payment cards: Card type), CC_NUMBER (Payment cards: Card number), CC_VALID_F (Payment cards: Valid from).. 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: Cannot Be Enhanced
SAP BAPICCARDM 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 |
OPERATION | Function | MSGFN | CHAR | 3 | MSGFN | ||||
SD_DOC | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
CC_TYPE | Payment cards: Card type | CCINS | CHAR | 4 | TVCIN | CCINS | |||
CC_NUMBER | Payment cards: Card number | CCNUM | CHAR | 25 | VCNUM | CCNUM | |||
CC_VALID_F | Payment cards: Valid from | DATAB_CC | DATS | 8 | DATUM | ||||
CC_VALID_T | Payment Cards: Valid To | DATBI_CC | DATS | 8 | DATUM | ||||
CC_NAME | Payment cards: Name of cardholder | CCNAME | CHAR | 40 | TEXT40 | ||||
DATAORIGIN | Payment cards: Entry mode | CSOUR | CHAR | 1 | CSOUR | ||||
AUTHAMOUNT | Currency amount for BAPIS (with 9 decimal places) | BAPICUREXT | DEC | 28(9) | BAPICUREXT | ||||
CURRENCY | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
CURR_ISO | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
CC_SETTLED | Payment cards: Settlement carried out | SETTL | CHAR | 1 | XFELD | ||||
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 | ||||
AUTH_DATE | Payment cards: Authorization date | AUDAT_CC | DATS | 8 | DATUM | ||||
AUTH_TIME | Payment cards: Authorization time | AUTIM | TIMS | 6 | UZEIT | ||||
MERCHIDCL | Payment cards: Merchant ID at the clearing house | MERCH | CHAR | 15 | Assigned to domain | MERCH | |||
PNTOFRECEI | Payment cards: Point of receipt for the transaction | LOCID_CC | CHAR | 10 | Assigned to domain | LOCID_CC | |||
TERMINAL | Payment cards: Terminal | TRMID | CHAR | 10 | CHAR10 | ||||
SETTLEMRUN | Payment cards: Settlement run | CCBTC | CHAR | 10 | ALPHA | CCBTC | |||
CARDCATEGO | Payment cards: Card category | CCTYP | CHAR | 2 | Assigned to domain | CCTYP | |||
AUTHORTYPE | Payment cards: Authorization type | CCAUA | CHAR | 1 | CCAUA | ||||
STATEXTSYS | Payment cards: Status when external system is called? | CCALL | CHAR | 1 | CCALL | ||||
CC_REACT | Payment cards: Response to authorization checks | REACT_SD | CHAR | 1 | REACT_SD | ||||
AMOUNTAUTH | Currency amount for BAPIS (with 9 decimal places) | BAPICUREXT | DEC | 28(9) | BAPICUREXT | ||||
CURR_CRED | Currency key of credit control area | WAERS_CM | CUKY | 5 | Assigned to domain | WAERS | |||
CURCREDISO | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
AUTH_EXPIR | Payment cards: Authorization has expired | CCOLD | CHAR | 1 | XFELD | ||||
AMOUNTCHAN | Payment cards: Amount changed | CCVAL | CHAR | 1 | XFELD | ||||
PRE_AUTH | Payment cards: Preauthorization | CCPRE | CHAR | 1 | XFELD | ||||
HIGHLEAUTH | Higher-level authorization for billing plan | UELTR_A | NUMC | 6 | Assigned to domain | FPLTR | |||
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 | ||||
REASONTEXT | Payment cards: Result text | RTEXT_CC | CHAR | 40 | TXT40 | ||||
CC_LIMIT | Currency amount for BAPIS (with 9 decimal places) | BAPICUREXT | DEC | 28(9) | BAPICUREXT | ||||
AUTH_USED | Payment card: Authorization Used | AUTHU | CHAR | 1 | CHAR1 | ||||
CC_LIMITED | Payment cards: Limit amount | CCBEG | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure BAPICCARDM using ABAP code?
As BAPICCARDM 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 BAPICCARDM as there is no data to select.How to access SAP table BAPICCARDM
Within an ECC or HANA version of SAP you can also view further information about BAPICCARDM 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