RFQ_BC_TOKEN
RFQ Block Chain Token for Supplier
RFQ_BC_TOKEN is an SAP database table in S/4HANA. RFQ Block Chain Token for Supplier. It contains 6 fields. 1 CDS views read from this table.
CDS Views using this table (1)
| View | Type | Join | VDM | Description |
|---|---|---|---|---|
| P_RFQBlockChainToken | view | from | BASIC |
Fields (6)
| Key | Field | Data Element | Description | Domain | Type | Length |
|---|---|---|---|---|---|---|
| KEY | mandt | MANDT | Client | |||
| KEY | requestforquotation | VDM_REQUESTFORQUOTATION | RFQ | |||
| KEY | supplier | LIFNR | Supplier | |||
| KEY | emailaddress | AD_SMTPADR | E-Mail Address | |||
| accesstoken | abap.strg | |||||
| changedatetime | TZNTSTMPS | Time Stamp |
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.
-- RFQ Block Chain Token for Supplier
-- Category TRANSPARENT · Delivery class L
-- Derived schema, generated from indexed DDIC field metadata (not the verbatim SAP source).
CREATE TABLE RFQ_BC_TOKEN (
MANDT, -- Client [MANDT]
REQUESTFORQUOTATION, -- RFQ [VDM_REQUESTFORQUOTATION]
SUPPLIER, -- Supplier [LIFNR]
EMAILADDRESS, -- E-Mail Address [AD_SMTPADR]
ACCESSTOKEN, -- abap.strg
CHANGEDATETIME, -- Time Stamp [TZNTSTMPS]
PRIMARY KEY (MANDT, REQUESTFORQUOTATION, SUPPLIER, EMAILADDRESS)
);
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