REGUHM
Payment Data for Cross-Payment Run Payment Medium
REGUHM is an SAP database table in S/4HANA. Payment Data for Cross-Payment Run Payment Medium. It contains 20 fields. 4 CDS views read from this table.
CDS Views using this table (4)
| View | Type | Join | VDM | Description |
|---|---|---|---|---|
| I_BkPaytRunDocCrsPaytRunPayt | view_entity | from | BASIC | Payment run documents settlement data |
| I_CrossPaymentRunPayment | view | from | BASIC | Pay Data for Cross-Pay Run Pay Medium |
| I_Paymentstatistics_Base | view | inner | BASIC | Base View for Payment Statistics |
| TSI_BAT_STATUS_entry | view | inner |
Fields (20)
| Key | Field | Data Element | Description | Domain | Type | Length |
|---|---|---|---|---|---|---|
| KEY | mandt | MANDT | Client | |||
| KEY | laufd | LAUFD | Run On | |||
| KEY | laufi | LAUFI | Identification | |||
| KEY | zbukr | DZBUKR | Paying co. code | |||
| KEY | lifnr | LIFNR | Supplier | |||
| KEY | kunnr | KUNNR | Customer | |||
| KEY | empfg | EMPFG | Pmnt Recipient | |||
| KEY | vblnr | VBLNR | Payment Doc.No. | |||
| laufd_m | LAUFD_M | Date of Payment Med. | ||||
| laufi_m | LAUFI_M | ID Payment Medium | ||||
| hbkid | HBKID | House Bank | ||||
| hktid | HKTID | Account ID | ||||
| rzawe | RZAWE | Payment Method | ||||
| uzawe | UZAWE | Pmnt Meth. Sup. | ||||
| waers | WAERS | Currency | ||||
| zaldt | DZALDT_ZHL | Doc. Pstg Date | ||||
| valut | VALUT | Value date | ||||
| crval | PRQ_CRVAL | Value date payee | ||||
| ausfd | AUSFD | Due Date | ||||
| batchno | abap.numc |
Derived SQL schema, reconstructed from the indexed DDIC field metadata (field names, types, lengths and key flags) — a functional representation, not the verbatim SAP source.
-- Payment Data for Cross-Payment Run Payment Medium
-- Category TRANSPARENT · Delivery class A
-- Derived schema, generated from indexed DDIC field metadata (not the verbatim SAP source).
CREATE TABLE REGUHM (
MANDT, -- Client [MANDT]
LAUFD, -- Run On [LAUFD]
LAUFI, -- Identification [LAUFI]
ZBUKR, -- Paying co. code [DZBUKR]
LIFNR, -- Supplier [LIFNR]
KUNNR, -- Customer [KUNNR]
EMPFG, -- Pmnt Recipient [EMPFG]
VBLNR, -- Payment Doc.No. [VBLNR]
LAUFD_M, -- Date of Payment Med. [LAUFD_M]
LAUFI_M, -- ID Payment Medium [LAUFI_M]
HBKID, -- House Bank [HBKID]
HKTID, -- Account ID [HKTID]
RZAWE, -- Payment Method [RZAWE]
UZAWE, -- Pmnt Meth. Sup. [UZAWE]
WAERS, -- Currency [WAERS]
ZALDT, -- Doc. Pstg Date [DZALDT_ZHL]
VALUT, -- Value date [VALUT]
CRVAL, -- Value date payee [PRQ_CRVAL]
AUSFD, -- Due Date [AUSFD]
BATCHNO, -- abap.numc
PRIMARY KEY (MANDT, LAUFD, LAUFI, ZBUKR, LIFNR, KUNNR, EMPFG, VBLNR)
);
Learn More
- Understanding Data Lineage in SAP S/4HANA
- SAP Tables vs CDS Views — Key Differences
- Understanding the SAP S/4HANA Data Model
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA