REGUHO SAP (REGUH version before the 'n'th change) Table details
Dictionary Type: Table
Description: REGUH version before the 'n'th change
Description: REGUH version before the 'n'th change
Table field list including key, data, relationships and ABAP select examples
REGUHO is a standard SAP Table which is used to store REGUH version before the 'n'th change data and is available within R/3 SAP systems depending on the version and release level.
The REGUHO table consists of various fields, each holding specific information or linking keys about REGUH version before the 'n'th change data available in SAP. These include LAUFD (Date on Which the Program Is to Be Run), LAUFI (Additional Identification), ZBUKR (Paying company code), LIFNR (Account Number of Vendor or Creditor).. 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 or numeric)
SAP REGUHO 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 | Assigned to domain | MANDT | |||
| LAUFD | Date on Which the Program Is to Be Run | LAUFD | DATS | 8 | DATUM | ||||
| LAUFI | Additional Identification | LAUFI | CHAR | 6 | LAUFI | ||||
| ZBUKR | Paying company code | DZBUKR | CHAR | 4 | Assigned to domain | BUKRS | |||
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
| EMPFG | Payee code | EMPFG | CHAR | 16 | EMPFG | ||||
| VBLNR | Document Number of the Payment Document | VBLNR | CHAR | 10 | ALPHA | BELNR | |||
| VERSN | Consecutive Change Number | VERSN_REGU | NUMC | 4 | NUM04 | ||||
| WEVWV | Planned usage of the bill of exchange | WEVWV | CHAR | 1 | WEVWV | ||||
| ZBNKS | Country Key | DZBNKS | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| ZBNKN | Bank account number of the payee | DZBNKN | CHAR | 18 | BANKN | ||||
| ZBNKL | Bank number of the payee's bank | DZBNKL | CHAR | 15 | BANKL | ||||
| ZBKON | Bank Control Key of the Payee's Bank | DZBKON | CHAR | 2 | BKONT | ||||
| ZBVTY | Bank Data Indicator for the Payee | DZBVTY | CHAR | 4 | BVTYP | ||||
| ZSWIF | SWIFT/BIC for International Payments | SWIFT | CHAR | 11 | SWIFT | ||||
| ZALDT | Posting date of the payment document | DZALDT_ZHL | DATS | 8 | DATUM | ||||
| RZAWE | Payment Method for This Payment | RZAWE | CHAR | 1 | Assigned to domain | ZLSCH | |||
| RUMSK | Special G/L Indicator of the Payment Transaction | RUMSK | CHAR | 1 | Assigned to domain | UMSKZ | |||
| RZUMS | Target Special G/L Indicator of the Payment Transaction | RZUMS | CHAR | 1 | Assigned to domain | UMSKZ | |||
| HKTID | ID for account details | HKTID | CHAR | 5 | Assigned to domain | HKTID | |||
| HBKID | Short Key for a House Bank | HBKID | CHAR | 5 | Assigned to domain | HBKID | |||
| HKTIW | Short Key of the Account Data for the Bill of Exchange | HKTIW | CHAR | 5 | Assigned to domain | HKTID | |||
| HBKIW | Short Key of the House Bank for Bill/Exch.for Check/Bill/Ex. | HBKIW | CHAR | 5 | Assigned to domain | HBKID | |||
| BVTYP | Partner Bank Type | BVTYP | CHAR | 4 | BVTYP | ||||
| UBKON | Bank control key at our bank | UBKON | CHAR | 2 | BKONT | ||||
| UBKNT | Our account number at the bank | UBKNT | CHAR | 18 | BANKN | ||||
| UBNKS | Bank country key | BANKS | CHAR | 3 | Assigned to domain | LAND1 | BKL | ||
| UBNKL | Bank number of our bank | UBNKL | CHAR | 15 | BANKL | ||||
| UBHKT | G/L Account Number for Our Bank Account / Bank Sub-Account | UBHKT | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | ||
| VALUT | Value date | VALUT | DATS | 8 | DATUM | ||||
| ANFAE | Bill of Exchange Payment Request Due Date | ANFAE | DATS | 8 | DATUM | ||||
| WEFAE | Bill of Exchange Due Date | WEFAE | DATS | 8 | DATUM | ||||
| RBETR | Amount in Local Currency | RBETR | CURR | 13(2) | WRTV7 | ||||
| RSKON | Total Cash Discount for the Payment Trans. (Local Currency) | RSKON | CURR | 13(2) | WRTV7 | ||||
| RWBTR | Amount Paid in the Payment Currency | RWBTR | CURR | 13(2) | WRTV7 | ||||
| RWSKT | Total Cash Discount for the Pmnt Transactn in Pmnt Currency | RWSKT | CURR | 13(2) | WRTV7 | ||||
| RSPE1 | Form Charges | SPES1 | CURR | 11(2) | WERT6 | ||||
| RSPE2 | Form Charges | SPES2 | CURR | 11(2) | WERT6 | ||||
| RPOST | Number of Items Paid | RPOST | DEC | 5 | PACK3 | ||||
| RTEXT | Number of Text Lines for the Items Paid | RTEXT_D | DEC | 5 | PACK3 | ||||
| RSPM1 | Form Charges for Bill of Exchange with Maximum Amount | SPEM1 | CURR | 11(2) | WERT6 | ||||
| RSPM2 | Form Charges for Bill of Exchange with Maximum Amount | SPEM2 | CURR | 11(2) | WERT6 | ||||
| WEHMX | Maximum Amount per Bill of Exchange in Local Currency | WEHMX | CURR | 13(2) | WERT7 | ||||
| WEFMX | Maximum Amount per Bill of Exchange in Payment Currency | WEFMX | CURR | 13(2) | WERT7 | ||||
| WEHRS | Remaining Amount in Local Crcy for Last Bill of Exchange | WEHRS | CURR | 13(2) | WERT7 | ||||
| WEFRS | Remaining Amount in Payment Crcy for Last Bill of Exchange | WEFRS | CURR | 13(2) | WERT7 | ||||
| WEAMX | Number of Bills of Exchange with Maximum Amount | WEAMX | DEC | 3 | PACK2 | ||||
| WDATE | Bill of Exchange Issue Date | WDATE | DATS | 8 | DATUM |
| Key field | Non-key field |
How do I retrieve data from SAP table REGUHO using ABAP code
The following ABAP code Example will allow you to do a basic selection on REGUHO to SELECT all data from the tableDATA: WA_REGUHO TYPE REGUHO.
SELECT SINGLE *
FROM REGUHO
INTO CORRESPONDING FIELDS OF WA_REGUHO
WHERE...
How to access SAP table REGUHO
Within an ECC or HANA version of SAP you can also view further information about REGUHO 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