CRUSER in VTIFHAZU
Entered By (DE: Erfasser)
CRUSER is a field in SAP table VTIFHAZU (Underlying transaction status table). It represents "Entered By". Data element: TB_CRUSER. Available in 1 CDS view(s) as CreatedByUser.
Business Meaning
| Description (EN) | Entered By |
|---|---|
| Beschreibung (DE) | Erfasser |
| Data Element | TB_CRUSER |
| Key Field | No |
CDS Views & Technical Names (1)
VTIFHAZU.CRUSER is exposed in CDS views under the following technical name. Views reading the table directly are listed first; "via" marks views that pass the field on through intermediate views.
CreatedByUser
(1 view)
| View | Access | VDM | Release | Description |
|---|---|---|---|---|
| I_FinTransUnderlyingActivity | direct | BASIC | Fin Trans Underlying Activity |
Other Tables with Field CRUSER (28)
| Table | Data Element | Key | Description |
|---|---|---|---|
| ALLOCYCLEXLSX | FCO_ALLOC_CREATED_BY | Allocation Cycle data from Excel upload | |
| ALLODERRULESXLSX | FCO_ALLOC_CREATED_BY | Derivation Rules for Manage Allocation Excel Upload | |
| ALLORCVRBSISXLSX | FCO_ALLOC_CREATED_BY | Allocation Sender Basis data from Excel upload | |
| ALLORECEIVERXLSX | FCO_ALLOC_CREATED_BY | Allocation Receiver data from Excel upload | |
| ALLOSEGMENTXLSX | FCO_ALLOC_CREATED_BY | Allocation Segment data from Excel upload | |
| ALLOSENDERXLSX | FCO_ALLOC_CREATED_BY | Allocation Sender data from Excel upload | |
| ALLOSNDRBSISXLSX | FCO_ALLOC_CREATED_BY | Allocation Sender Basis data from Excel upload | |
| ALLOUPLOADXLSX | FCO_ALLOC_CREATED_BY | XLSX file content from Allocation Excel upload | |
| BUT_DCP_JOBIMP | BU_CRUSR | BP: Data Controller and Purpose Tools - Import Job | |
| CNV_2010C_STATE | CNV_00001_CREATE_USER | Status table for execution of all activities and history | |
| CVI_CUST_CT_LINK | BU_CRUSR | Connec. Between Relationship + Activity Partner for Customer | |
| CVI_CUST_LINK | BU_CRUSR | Assignment Between Customer and Business Partner | |
| CVI_VEND_CT_LINK | BU_CRUSR | Connec. Between Relationship + Activity Partner for Vendor | |
| CVI_VEND_LINK | BU_CRUSR | Assignment Between Vendor and Business Partner | |
| FIN_D_CORR_REQS | UNAME | Correspondence requests with parameteres | |
| IUUC_RS_ORDER | SYUNAME | Table to keep the history for all actions from RS_ORDER | |
| JBDOBJ1 | TB_CRUSER | Object Table for Financial Transactions, General Part | |
| JBRPH | TB_CRUSER | Portfolio hierarchy | |
| T8JU | JV_CRUSER | Joint Operating Agreement | |
| T8JV | JV_CRUSER | Joint Venture | |
| THMHRT_HR | TB_CRUSER | Hedge Relationship | |
| THMT_HEDGE_ITEM | TB_CRUSER | Hedged Item | |
| VTBFHA | TB_CRUSER | Transaction | |
| VTBFHAZU | TB_CRUSER | Transaction Activity | |
| VTBTRA1 | TB_CRUSER | Transaction Authoriz. for Traders | |
| VTBZV | TB_CRUSER | Payment Details for Transaction | |
| VTIFHA | TB_CRUSER | Underlying transaction | |
| VTIFHAPO | TB_CRUSER | Underlying transaction flows |
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