REGUHM_LST SAP (Cross-Payment Run Payment Medium Creation: Reporting) Structure details
Description: Cross-Payment Run Payment Medium Creation: Reporting
Structure field list including key, data, relationships and ABAP select examples
REGUHM_LST 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 "Cross-Payment Run Payment Medium Creation: Reporting" 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_REGUHM_LST TYPE REGUHM_LST.
The REGUHM_LST table consists of various fields, each holding specific information or linking keys about Cross-Payment Run Payment Medium Creation: Reporting data available in SAP. These include MANDT (Client), LAUFD (Date on Which the Program Is to Be Run), LAUFI (Additional Identification), ZBUKR (Paying company code).. 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: Not classified
SAP REGUHM_LST 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 |
| MANDT | Client | MANDT | CLNT | 3 | T000 | 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 | T001 | BUKRS | |||
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | KRED_C |
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | C_KUNNR |
| EMPFG | Payee code | EMPFG | CHAR | 16 | EMPFG | ||||
| VBLNR | Document Number of the Payment Document | VBLNR | CHAR | 10 | BKPF | ALPHA | BELNR | ||
| LAUFD_M | Date of Payment Medium Run | LAUFD_M | DATS | 8 | DATUM | ||||
| LAUFI_M | Identification of the Payment Medium Run | LAUFI_M | CHAR | 6 | LAUFI | ||||
| HBKID | Short Key for a House Bank | HBKID | CHAR | 5 | T012 | HBKID | |||
| HKTID | ID for account details | HKTID | CHAR | 5 | T012K | HKTID | |||
| RZAWE | Payment Method for This Payment | RZAWE | CHAR | 1 | T042Z | ZLSCH | |||
| UZAWE | Payment Method Supplement | UZAWE | CHAR | 2 | T042F | UZAWE | |||
| WAERS | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
| ZALDT | Posting date of the payment document | DZALDT_ZHL | DATS | 8 | DATUM | ||||
| VALUT | Value date | VALUT | DATS | 8 | DATUM | ||||
| CRVAL | Value Date at Payee's Bank | PRQ_CRVAL | DATS | 8 | DATUM | ||||
| AUSFD | Due date of the paid items | AUSFD | DATS | 8 | DATUM | ||||
| BATCHNO | 0 | ||||||||
| SAKNR | G/L Account Number | SAKNR | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | SAK | C_SAKNR |
| PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
| RWBTR | Amount Paid in the Payment Currency | RWBTR | CURR | 13(2) | WRTV7 | ||||
| HWAER | Local Currency | HWAER | CUKY | 5 | Assigned to domain | WAERS | |||
| RBETR | Amount in Local Currency | RBETR | CURR | 13(2) | WRTV7 | ||||
| ZNME1 | Name of the payee | DZNME1 | CHAR | 35 | TEXT35 | ||||
| ZNME2 | Name of the payee | DZNME1 | CHAR | 35 | TEXT35 | ||||
| ZORT1 | City of the payee | DZORT1 | CHAR | 35 | TEXT35 | ||||
| ZLAND | Country Key | DZLAND | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| ZBNKS | Country Key | DZBNKS | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| ZBNKY | Bank key of the payee's bank | DZBNKY | CHAR | 15 | BANKK | ||||
| ZBNKL | Bank number of the payee's bank | DZBNKL | CHAR | 15 | BANKL | ||||
| ZBNKN | Bank account number of the payee | DZBNKN | CHAR | 18 | BANKN | ||||
| ZBKON | Bank Control Key of the Payee's Bank | DZBKON | CHAR | 2 | BKONT | ||||
| BKREF | Reference specifications for bank details | BKREF | CHAR | 20 | CHAR20 | ||||
| BVTYP | Partner Bank Type | BVTYP | CHAR | 4 | BVTYP | ||||
| KOINH | Account Holder Name | KOINH_FI | CHAR | 60 | KOINH | ||||
| BUSAB | Accounting clerk | BUSAB | CHAR | 2 | Assigned to domain | BUSAB | |||
| RPOST | Number of Items Paid | RPOST | DEC | 5 | PACK3 | ||||
| XDONE | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON |
| Key field | Non-key field |
How do I retrieve data from SAP structure REGUHM_LST using ABAP code?
As REGUHM_LST 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 REGUHM_LST as there is no data to select.How to access SAP table REGUHM_LST
Within an ECC or HANA version of SAP you can also view further information about REGUHM_LST 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