I_BillOfExchangeUsageData
Bill of Exchange Usage Data
I_BillOfExchangeUsageData is a Composite CDS View that provides data about "Bill of Exchange Usage Data" in SAP S/4HANA. It reads from 1 data source (I_BillOfExchange) and exposes 26 fields with key fields CompanyCode, AccountingDocument, FiscalYear, AccountingDocumentItem.
SAP Help Documentation
| Category | Bill of Exchange |
|---|
Purpose
This CDS view provides access to all details of bill of exchange data in database table BSED and BESG . This CDS view provides the data to answer the following business questions: What is the bill of exchange number of a bill of exchange document? What is the status of a bill of exchange document? Who is the drawer of a bill of exchange document? What is the usage data of a bill of exchange document? To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views .
Prerequisites
Authorizations Users who want to use this CDS view must have a role with the following restriction types set to read access: BUKRS (Company Code) You can use the Display Restriction Types app to find out in which business catalogs these restriction types are included.
Structure
Parameters The parameters of the CDS view are as follows: CompanyCode : This parameter is used to represent company code of bills of exchange. AccountingDocument : This parameter is used to represent accounting document number of bills of exchange. FiscalYear : This parameter is used to represent fiscal year of bills of exchange. AccountingDocumentItem : This parameter is used to represent accounting document item number of bills of exchange. Cheque : This parameter is used to represent number of bills of exchange. BillOfExchangeIssueDate : This parameter is used to represent issue date of bills of exchange. BillOfExchangeUsageDate : This parameter is used to represent usage date of bills of exchange. PlannedBillOfExchangeUsage : This parameter is used to represent planned usage of bills of exchange. BillOfExchangeDrawer : This parameter is used to represent drawer name of bills of exchange. BillOfExchangeDrawerCityName : This parameter is used to represent drawer city name of bills of exchange. BillOfExchangeDrawee : This parameter is used to represent drawee name of bills of exchange. BillOfExchangeDraweeCityName : This parameter is used to represent drawee city name of bills of exchange. BillOfExchangeIsAccepted : This parameter is used to indicate whether a bill of exchange is accepted. Region : This parameter is used to represent the region code of journal entries. BillOfExchangeDocumentStatus : This parameter is used to represent document segment status of bills of exchange. BillOfExchangeIsProtested : This parameter is used to indicate whether a bill of exchange is protested. BillOfExchangeIsOnDemand : This parameter is used to indicate whether a bill of exchange is on demand. BusinessPlace : This parameter is used to represent business place. BusinessSectionCode : This parameter is used to represent business section code. BillOfExchangePortfolio : This parameter is used to represent bill of exchange portfolio, Typically, each branch of a business has its own portfolio, possibly with separate portfolios for long-term and short-term checks and bills. Each portfolio is linked to an account for bills receivable. BillOfExchangeDataAgingDate : This parameter is used to represent data aging date of bills of exchange. IsBusinessPurposeCompleted : This parameter is used to indicate whether the business purpose is completed. AuthorizationGroup : This parameter is used to represent the authorization group for accessing usage data of bills of exchange. • • BillOfExchangeUsageDocument : This parameter is used to represent usage document of bills of exchange. • • BillOfExchangeUsage : This parameter is used to represent usage type of bills of exchange.
This CDS view provides access to all details of bill of exchange data in database table BSED and BESG . This CDS view provides the data to answer the following business questions: What is the bill of exchange number of a bill of exchange document? What is the status of a bill of exchange document? Who is the drawer of a bill of exchange document? What is the usage data of a bill of exchange document? To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views .
Prerequisites
Authorizations Users who want to use this CDS view must have a role with the following restriction types set to read access: BUKRS (Company Code) You can use the Display Restriction Types app to find out in which business catalogs these restriction types are included.
Structure
Parameters The parameters of the CDS view are as follows: CompanyCode : This parameter is used to represent company code of bills of exchange. AccountingDocument : This parameter is used to represent accounting document number of bills of exchange. FiscalYear : This parameter is used to represent fiscal year of bills of exchange. AccountingDocumentItem : This parameter is used to represent accounting document item number of bills of exchange. Cheque : This parameter is used to represent number of bills of exchange. BillOfExchangeIssueDate : This parameter is used to represent issue date of bills of exchange. BillOfExchangeUsageDate : This parameter is used to represent usage date of bills of exchange. PlannedBillOfExchangeUsage : This parameter is used to represent planned usage of bills of exchange. BillOfExchangeDrawer : This parameter is used to represent drawer name of bills of exchange. BillOfExchangeDrawerCityName : This parameter is used to represent drawer city name of bills of exchange. BillOfExchangeDrawee : This parameter is used to represent drawee name of bills of exchange. BillOfExchangeDraweeCityName : This parameter is used to represent drawee city name of bills of exchange. BillOfExchangeIsAccepted : This parameter is used to indicate whether a bill of exchange is accepted. Region : This parameter is used to represent the region code of journal entries. BillOfExchangeDocumentStatus : This parameter is used to represent document segment status of bills of exchange. BillOfExchangeIsProtested : This parameter is used to indicate whether a bill of exchange is protested. BillOfExchangeIsOnDemand : This parameter is used to indicate whether a bill of exchange is on demand. BusinessPlace : This parameter is used to represent business place. BusinessSectionCode : This parameter is used to represent business section code. BillOfExchangePortfolio : This parameter is used to represent bill of exchange portfolio, Typically, each branch of a business has its own portfolio, possibly with separate portfolios for long-term and short-term checks and bills. Each portfolio is linked to an account for bills receivable. BillOfExchangeDataAgingDate : This parameter is used to represent data aging date of bills of exchange. IsBusinessPurposeCompleted : This parameter is used to indicate whether the business purpose is completed. AuthorizationGroup : This parameter is used to represent the authorization group for accessing usage data of bills of exchange. • • BillOfExchangeUsageDocument : This parameter is used to represent usage document of bills of exchange. • • BillOfExchangeUsage : This parameter is used to represent usage type of bills of exchange.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_BillOfExchange | _BillOfExchange | from |
Annotations (11)
| Name | Value | Level | Field |
|---|---|---|---|
| VDM.viewType | #COMPOSITE | view | |
| VDM.lifecycle.contract.type | #PUBLIC_LOCAL_API | view | |
| AccessControl.authorizationCheck | #MANDATORY | view | |
| EndUserText.label | Bill of Exchange Usage Data | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| Analytics.dataExtraction.enabled | false | view | |
| AccessControl.personalData.blocking | #REQUIRED | view | |
| ObjectModel.usageType.serviceQuality | #D | view | |
| ObjectModel.usageType.sizeCategory | #XXL | view | |
| ObjectModel.usageType.dataClass | #MIXED | view | |
| ObjectModel.modelingPattern | #ANALYTICAL_DIMENSION | view |
Fields (26)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | CompanyCode | CompanyCode | Receiver Company Code | |
| KEY | AccountingDocument | AccountingDocument | Journal Entry | |
| KEY | FiscalYear | FiscalYear | G/L Fiscal Year | |
| KEY | AccountingDocumentItem | AccountingDocumentItem | Posting View Item | |
| Cheque | Cheque | Cheque No | ||
| BillOfExchangeIssueDate | BillOfExchangeIssueDate | Issue Date | ||
| BillOfExchangeUsageDate | BillOfExchangeUsageDate | Usage | ||
| PlannedBillOfExchangeUsage | PlannedBillOfExchangeUsage | Plan.Usage | ||
| BillOfExchangeDrawer | BillOfExchangeDrawer | Drawer | ||
| BillOfExchangeDrawerCityName | BillOfExchangeDrawerCityName | City of Drawer | ||
| BillOfExchangeDrawee | BillOfExchangeDrawee | Drawee | ||
| BillOfExchangeDraweeCityName | BillOfExchangeDraweeCityName | City of Drawee | ||
| BillOfExchangeIsAccepted | BillOfExchangeIsAccepted | Accepted | ||
| Region | Region | Venue Region | ||
| BillOfExchangeDocumentStatus | BillOfExchangeDocumentStatus | Bill/Ex. Status | ||
| BillOfExchangeIsProtested | BillOfExchangeIsProtested | Bill Protest ID | ||
| BillOfExchangeIsOnDemand | BillOfExchangeIsOnDemand | Bill on Demand | ||
| BusinessPlace | BusinessPlace | Business place | ||
| BusinessSectionCode | BusinessSectionCode | Section Code | ||
| BillOfExchangePortfolio | BillOfExchangePortfolio | Bill Portfolio | ||
| BillOfExchangeDataAgingDate | BillOfExchangeDataAgingDate | Data Aging | ||
| IsBusinessPurposeCompleted | Purpose Completed | |||
| AuthorizationGroup | AuthorizGroup | |||
| BillOfExchangeUsageDocument | _OperationalAcctgDocItem | BillOfExchangeUsageDocument | ||
| BillOfExchangeUsage | _OperationalAcctgDocItem | BillOfExchangeUsage | BoE Usage | |
| _OperationalAcctgDocItem | _OperationalAcctgDocItem |
Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.
-- Derived SQL interpretation of CDS view I_BillOfExchangeUsageData.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
CREATE VIEW I_BillOfExchangeUsageData AS
SELECT
CompanyCode,
AccountingDocument,
FiscalYear,
AccountingDocumentItem,
Cheque,
BillOfExchangeIssueDate,
BillOfExchangeUsageDate,
PlannedBillOfExchangeUsage,
BillOfExchangeDrawer,
BillOfExchangeDrawerCityName,
BillOfExchangeDrawee,
BillOfExchangeDraweeCityName,
BillOfExchangeIsAccepted,
Region,
BillOfExchangeDocumentStatus,
BillOfExchangeIsProtested,
BillOfExchangeIsOnDemand,
BusinessPlace,
BusinessSectionCode,
BillOfExchangePortfolio,
BillOfExchangeDataAgingDate,
cast ( IsBusinessPurposeCompleted as cvp_xblck preserving type ) AS IsBusinessPurposeCompleted,
cast ( AuthorizationGroup as brgru preserving type ) AS AuthorizationGroup,
_OperationalAcctgDocItem.BillOfExchangeUsageDocument AS BillOfExchangeUsageDocument,
_OperationalAcctgDocItem.BillOfExchangeUsage AS BillOfExchangeUsage
FROM I_BillOfExchange AS _BillOfExchange
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- CDS View Field Mapping and Associations
- Understanding the SAP S/4HANA Data Model
- CDS View Extensions and Custom Fields in SAP S/4HANA
- Released APIs and Stability Contracts in SAP S/4HANA
- 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
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA