JHTFX SAP (IS-M/AM: Billing Index - Order Billing) Table details
Dictionary Type: Table
Description: IS-M/AM: Billing Index - Order Billing
Description: IS-M/AM: Billing Index - Order Billing
Table field list including key, data, relationships and ABAP select examples
JHTFX is a standard SAP Table which is used to store IS-M/AM: Billing Index - Order Billing data and is available within R/3 SAP systems depending on the version and release level.
The JHTFX table consists of various fields, each holding specific information or linking keys about IS-M/AM: Billing Index - Order Billing data available in SAP. These include AVM_NR (IS-M/AM: Sales Document Number), POS_NR (IS-M: Order Item Number), GRUPPABRNR (IS-M/AM: Billing Dataset), FKDAT (IS-M: Planned Billing/Settlement Date).. 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: A - Application table (master and transaction data)Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)
SAP JHTFX table 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 | T000 | MANDT | |||
| AVM_NR | IS-M/AM: Sales Document Number | AVM_NR | CHAR | 10 | JHAK | ALPHA | AVM_NR | JHA | MJHA |
| POS_NR | IS-M: Order Item Number | POS_NR | NUMC | 3 | JHAP | AVM_PNR | |||
| GRUPPABRNR | IS-M/AM: Billing Dataset | GRUPPABRNR | NUMC | 3 | JHAGA | GRUPPABR | |||
| FKDAT | IS-M: Planned Billing/Settlement Date | JHFKTER | DATS | 8 | DATUM | ||||
| BELEGEINH | IS-M/AM: Booking Unit | BELEGEINH | CHAR | 10 | JJTBE | ALPHA | BELEINH | JBE | MJJ1 |
| INHK | IS-M: Business Content Component | INHK_KFM | CHAR | 8 | JJTIKO | ALPHA | INHALTSKOM | JJ1 | |
| BER_TERMIN | IS-M: Date Services were Created for Settlement Purposes | BER_TERMIN | DATS | 8 | DATUM | ||||
| VKORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
| VTWEG | Distribution Channel | VTWEG | CHAR | 2 | TVTW | VTWEG | VTW | C_VTWEG | |
| SPART | Division | SPART | CHAR | 2 | TSPA | SPART | SPA | C_SPART | |
| UEBAR | IS-M: Transfer type | JHUEBART | CHAR | 1 | TJH41 | JHUEBART | |||
| NAMEK | IS-M: Abbreviated form of name for selection | NAMEK | CHAR | 10 | CHAR10 | ||||
| NAMEK_RG | IS-M: Abbreviated form of name for selection | NAMEK | CHAR | 10 | CHAR10 | ||||
| GPNR_AG | Business Partner: Sold-to Party | GPAG | CHAR | 10 | JGTGPNR | ALPHA | GPNR | ||
| GPNR_RG | IS-M: Payer Business Partner | GPNR_RG | CHAR | 10 | JGTGPNR | ALPHA | GPNR | ||
| GPNR_RE | IS-M: Business Partner - Bill-To Party | GPNR_RE | CHAR | 10 | JGTGPNR | ALPHA | GPNR | ||
| LLAND | Country of Destination | LLAND | CHAR | 3 | T005 | LAND1 | VLL | ||
| FSART | IS-M/AM: Billing Method | ISP_FSART | CHAR | 1 | ISP_FSART | ||||
| ZLSCH | Payment Method | DZLSCH | CHAR | 1 | T042Z | ZLSCH | |||
| BANKS | Bank country key | BANKS | CHAR | 3 | T005 | LAND1 | BKL | ||
| BANKL | Bank Keys | BANKK | CHAR | 15 | BANKK | BNK | |||
| BANKN | Bank account number | BANKN | CHAR | 18 | BANKN | ||||
| BKONT | Bank Control Key | BKONT | CHAR | 2 | BKONT | ||||
| BVTYP | Partner Bank Type | BVTYP | CHAR | 4 | BVTYP | ||||
| XEZER | Indicator: Is there collection authorization ? | XEZER | CHAR | 1 | XFELD | ||||
| FAKSP | IS-M: Billing Block | PAM_FAKSP | CHAR | 2 | TVFS | FAKSP | |||
| STTYP | IS-M: Reversal Type | STORNOTYP | CHAR | 1 | STORNOTYP |
| Key field | Non-key field |
How do I retrieve data from SAP table JHTFX using ABAP code
The following ABAP code Example will allow you to do a basic selection on JHTFX to SELECT all data from the tableDATA: WA_JHTFX TYPE JHTFX.
SELECT SINGLE *
FROM JHTFX
INTO CORRESPONDING FIELDS OF WA_JHTFX
WHERE...
How to access SAP table JHTFX
Within an ECC or HANA version of SAP you can also view further information about JHTFX 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