I_DunningEntryForOutpDetn
Determine Output Parameter for Dunning
I_DunningEntryForOutpDetn is a Composite CDS View that provides data about "Determine Output Parameter for Dunning" in SAP S/4HANA. It reads from 1 data source (I_DunningEntry) and exposes 30 fields with key fields DunningRunDate, DunningRun, FinancialAccountType, CompanyCode, Customer. It has 2 associations to related views. Part of development package FINS_OUTPUT_MGMT_FO_DUNN.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_DunningEntry | dataview | from |
Associations (2)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | I_UserContactCard | _UserData | _UserData.ContactCardID = $session.user |
| [1..1] | I_CustomerCompany | _CustomerCompany | _CustomerCompany.Customer = $projection.Customer and _CustomerCompany.CompanyCode = $projection.CompanyCode |
Annotations (7)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| AccessControl.personalData.blocking | #REQUIRED | view | |
| EndUserText.label | Determine Output Parameter for Dunning | view | |
| ObjectModel.usageType.dataClass | #MIXED | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #M | view | |
| VDM.viewType | #COMPOSITE | view |
Fields (30)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | DunningRunDate | DunningRunDate | ||
| KEY | DunningRun | DunningRun | ||
| KEY | FinancialAccountType | FinancialAccountType | Fin. Account Type | |
| KEY | CompanyCode | CompanyCode | Receiver Company Code | |
| KEY | Customer | Customer | Sold-to Party | |
| KEY | Supplier | Supplier | Supplier | |
| KEY | OneTimeAcctBankAccount | |||
| KEY | CustomerHeadOffice | CustomerHeadOffice | Head Office | |
| KEY | GroupingDunningArea | GroupingDunningArea | Dunning Area | |
| KEY | GroupingDunningLevel | GroupingDunningLevel | ||
| KEY | DunningClerk | DunningClerk | Dunning Clerk | |
| UserID | ||||
| EmailAddress | _UserData | EmailAddress | E-Mail Address | |
| CompanyCodeCountry | ||||
| AddressIndependentEmailAddress | ||||
| DefaultEmailAddress | ||||
| AccountingClerkInternetAddress | _CustomerCompany | AccountingClerkInternetAddress | Clrk's internet | |
| Country | ||||
| Language | ||||
| DunningPrintDate | DunningPrintDate | |||
| DunningDate | DunningDate | Dunning Date | ||
| LegDunningProcedureOn | LegDunningProcedureOn | Leg.Dunn.Proc. | ||
| DunningProcedure | DunningProcedure | Dunn.Procedure | ||
| DunningLevel | DunningLevel | Dunning Level | ||
| DunningBlockingReason | DunningBlockingReason | Set Dunning Block | ||
| _UserData | _UserData | |||
| _AccountingClerk | _AccountingClerk | |||
| _Customer | _Customer | |||
| _CompanyCode | _CompanyCode | |||
| _CustomerCompany | _CustomerCompany |
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_DunningEntryForOutpDetn.
-- 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_DunningEntryForOutpDetn AS
SELECT
DunningRunDate,
DunningRun,
FinancialAccountType,
CompanyCode,
Customer,
Supplier,
cast (OneTimeAcctBankAccount as cpdky) AS OneTimeAcctBankAccount,
CustomerHeadOffice,
GroupingDunningArea,
GroupingDunningLevel,
DunningClerk,
cast (dataview._AccountingClerk.UserID as farp_mydunnproposal_userid) AS UserID,
_UserData.EmailAddress AS EmailAddress,
dataview._CompanyCode.Country AS CompanyCodeCountry,
_Customer._CustomerToBusinessPartner._BusinessPartner._BPAddressIndependentEmail[1:IsDefaultEmailAddress = 'X'].EmailAddress AS AddressIndependentEmailAddress,
dataview._Customer._StandardAddress._DefaultEmailAddress.EmailAddress AS DefaultEmailAddress,
_CustomerCompany.AccountingClerkInternetAddress AS AccountingClerkInternetAddress,
dataview._Customer.Country AS Country,
dataview._Customer.Language AS Language,
DunningPrintDate,
DunningDate,
LegDunningProcedureOn,
DunningProcedure,
DunningLevel,
DunningBlockingReason
FROM I_DunningEntry AS dataview
LEFT OUTER JOIN I_UserContactCard AS _UserData ON _UserData.ContactCardID = $session.user -- association [0..1]
LEFT OUTER JOIN I_CustomerCompany AS _CustomerCompany ON _CustomerCompany.Customer = Customer AND _CustomerCompany.CompanyCode = CompanyCode -- association [1..1]
;
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