FKKBIXBIT0_PY_ALL SAP (Work Structure for Payments - Raw Data) Structure details
Description: Work Structure for Payments - Raw Data
Related tables to FKKBIXBIT0_PY_ALL
Access table FKKBIXBIT0_PY_ALL
Structure field list including key, data, relationships and ABAP select examples
FKKBIXBIT0_PY_ALL 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 "Work Structure for Payments - Raw Data" 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_FKKBIXBIT0_PY_ALL TYPE FKKBIXBIT0_PY_ALL.
The FKKBIXBIT0_PY_ALL table consists of various fields, each holding specific information or linking keys about Work Structure for Payments - Raw Data data available in SAP. These include MANDT (Client), SRCTATYPE (Source Transaction Type), SRCTAID (Source Transaction ID), BITPACKUUID (GUID of Package of Billable Items).. 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 FKKBIXBIT0_PY_ALL 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 |
BITNO | Internal Number of Billable Item | BITNO_INT_KK | NUMC | 6 | |||||
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
SRCTATYPE | Source Transaction Type | SRCTATYPE_KK | CHAR | 5 | Assigned to domain | SRCTATYPE_KK | |||
SRCTAID | Source Transaction ID | SRCTAID_KK | CHAR | 22 | ALPHA | SRCTAID_KK | |||
BITPACKUUID | GUID of Package of Billable Items | BITPACKUUID_KK | RAW | 16 | GUID16 | ||||
BITPACKCNO | Sequence Number of Billable Item in Package | BITPACKCNO_KK | NUMC | 8 | NUMC8 | ||||
BITCAT | Billable Item Class | BITCAT_KK | CHAR | 4 | TFK8101C | BITCAT_KK | FKK_BIX_BITCAT | ||
VKONT | Contract Account Number | VKONT_KK | CHAR | 12 | FKKVK | ALPHA | VKONT_KK | KTO | FKKVKP_F4 |
PYMET | Payment Method | PYMET_KK | CHAR | 1 | Assigned to domain | PYMET_KK | |||
EMBVT | Bank Details ID of Payee | EMBVT_KK | CHAR | 4 | CHAR4 | ||||
EMGPA | Alternative Business Partner for Payments | EMGPA_KK | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BUPA | |
PCARD_GUID | Key for Payment Card Supplement | XGUID_PC_KK | RAW | 16 | |||||
PCARD_GUID32 | Key for Payment Card Supplement (CHAR Format) | CGUID_PC_KK | CHAR | 32 | SYSUUID_C32 | ||||
PYREF | Payment Reference | PYREF_KK | CHAR | 30 | PYREF_KK | ||||
PY_AMOUNT | Maximum Available Payment Amount of Payment Type | PY_AMOUNT_KK | CURR | 13(2) | WRTV7 | ||||
PY_CURR | Transaction Currency | BLWAE_KK | CUKY | 5 | TCURC | WAERS | FWS | ||
PY_PRIO | Priority of Payment Type | PY_PRIO_KK | NUMC | 4 | |||||
BITREF32 | External Reference of Billable Item (32 Places) | BITREF32_KK | CHAR | 32 | BITREF32_KK | ||||
PY_GROUP | Grouping of Payment Data Items | BIT_PY_GROUP_KK | CHAR | 8 | |||||
EXCHIST | History Record Exists for Exception | BITEXCHIST_KK | CHAR | 1 | XFELD | ||||
CHHIST | History Record Exists for Change | BITCHHIST_KK | CHAR | 1 | XFELD | ||||
EXCDATE | Exception Date | BITEXCDATE_KK | DATS | 8 | DATS | ||||
EXCTIME | Time of Exception | BITEXCTIME_KK | TIMS | 6 | TIMS | ||||
EXCREASON | Exception Reason for Billable Items | BITEXCREASON_KK | CHAR | 2 | TFK8105E | BITEXCREASON_KK | |||
EXCUSNAM | Name of User Who Excepted the Item | BITEXCUSNAM_KK | CHAR | 12 | USR02 | XUBNAME | |||
CCARD_ID | Payment Card ID | BU_CCID | CHAR | 6 | CHAR6 | ||||
CCINS | Payment card type | CC_INSTITUTE | CHAR | 4 | TB033 | CC_INSTITUTE | |||
CCNUM | Payment cards: Card number | CCNUM | CHAR | 25 | Assigned to domain | CCNUM | |||
DATAB | Payment cards: Valid from | CC_DATAB | DATS | 8 | DATUM | ||||
DATBI | Payment Cards: Valid To | CC_DATBI | DATS | 8 | DATUM | ||||
CCNAME | Payment cards: Name of cardholder | CCNAME | CHAR | 40 | TEXT40 | ||||
CGUID | GUID of a Payment Card | CARD_GUID | RAW | 16 | SYSUUID | ||||
ENCTP | Type of Encryption | CCSECA_ENCTYPE | CHAR | 1 | CCSECA_ENCTYPE | ||||
AUNUM | Payment cards: Authorization number | AUNUM_KK | CHAR | 25 | CHAR25 | ||||
AUTRA | Payment Cards: Authorization Reference Number | AUTRA_KK | CHAR | 25 | CHAR25 | ||||
AUDAT | Payment cards: Authorization date | AUDAT_CC | DATS | 8 | DATUM | ||||
AUTIM | Payment cards: Authorization time | AUTIM | TIMS | 6 | UZEIT | ||||
AUTWR | Payment cards: Authorized amount | AUTWR | CURR | 15(2) | WERTV8 | ||||
CCWAE | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
MERCH | Payment cards: Merchant ID at the clearing house | MERCH | CHAR | 15 | TCCM | MERCH | |||
PCARD_XSETT | Billing Status | XSETT_KK | CHAR | 1 | XSETT_KK |
Key field | Non-key field |
How do I retrieve data from SAP structure FKKBIXBIT0_PY_ALL using ABAP code?
As FKKBIXBIT0_PY_ALL 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 FKKBIXBIT0_PY_ALL as there is no data to select.How to access SAP table FKKBIXBIT0_PY_ALL
Within an ECC or HANA version of SAP you can also view further information about FKKBIXBIT0_PY_ALL 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