C_CollectionsMainContact
Main Contact
C_CollectionsMainContact is a Consumption CDS View that provides data about "Main Contact" in SAP S/4HANA. It reads from 1 data source (I_CollectionsMainContact) and exposes 23 fields with key fields CollectionSegment, BusinessPartner. It is exposed through 7 OData services (UI_COLL_MD_MANAGE, UI_CUSTOMER_CONTACT_MANAGE, UI_DISPUTECASE_MANAGE, ...). It is used in 6 Fiori applications: Manage Dispute Cases (Version 2), Manage Customer Contacts, Manage Resubmissions, ....
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_CollectionsMainContact | I_CollectionsMainContact | projection |
Annotations (8)
| Name | Value | Level | Field |
|---|---|---|---|
| Metadata.allowExtensions | true | view | |
| VDM.viewType | #CONSUMPTION | view | |
| AccessControl.authorizationCheck | #MANDATORY | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.dataClass | #MIXED | view | |
| ObjectModel.representativeKey | BusinessPartner | view | |
| EndUserText.label | Main Contact | view |
OData Services (7)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_COLL_MD_MANAGE | UI_COLL_MD_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_CUSTOMER_CONTACT_MANAGE | UI_CUSTOMER_CONTACT_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_DISPUTECASE_MANAGE | UI_DISPUTECASE_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_HOBRECEIVABLES_DISPLAY | UI_HOBRECEIVABLES_DISPLAY | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_PROCESSRECEIVABLES_MANAGE | UI_PROCESSRECEIVABLES_MAN | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_PROMISETOPAY_MANAGE | UI_PROMISETOPAY_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
| UI_RESUBMISSIONS_MANAGE | UI_RESUBMISSIONS_MANAGE | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
Fiori Apps (6)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F0702A | Manage Dispute Cases (Version 2) | Transactional | Use this app to analyze and further process existing dispute cases. This involves dispute cases that are related to open receivables for your customers. |
| F4707 | Manage Customer Contacts | Transactional | Use this app to manage the customer contacts for your business partners, which are created by collections specialists as result of a customer contact. You use these contacts in the collection process with the Process Receivables app. |
| F4709 | Manage Resubmissions | Transactional | Use this app to manage resubmissions for business partners that were created for outstanding receivables. You use these resubmissions in the collection process with the Process Receivables app. |
| F4710 | Manage Promises to Pay | Transactional | Use this app to manage promises to pay of customers, which were created in the collection process using the Process Receivables app. You can display, edit, and withdraw promises to pay. |
| F5400 | Manage Collections Master Data | Transactional | Use this app to activate customers for Collections Management processes. For activated accounts, you can maintain Collection Groups per Collection Segments as well as assign Specialists on Collection Segment level. |
| F5401 | Display Head Office Receivables | Transactional | If head office / branch relationships are used in SAP FI-AR, the work list entries in SAP Collections Management can be created on the branch level. Accordingly, only the branch related FI line items are shown on the Invoices list in the Process Receivables app. The app Head Office Receivables can be called via the button Display Head Office Receivables in the Process Receivables app. The button is only available, if such a relationship is maintained for the customer. The app provides the information on customer recevievables and related objects (dispute cases, promises to pay, resubmissions, company relationships, notes) from the perspective of the head office. Unlike the Process Receivables, the creation of new objects is not possible in this app. |
Manage Dispute Cases (Version 2)
Business Role: Accounts Receivable Accountant
Use this app to analyze and further process existing dispute cases. This involves dispute cases that are related to open receivables for your customers.
Manage Customer Contacts
Business Role: Accounts Receivable Accountant
Use this app to manage the customer contacts for your business partners, which are created by collections specialists as result of a customer contact. You use these contacts in the collection process with the Process Receivables app.
Manage Resubmissions
Business Role: Accounts Receivable Accountant
Use this app to manage resubmissions for business partners that were created for outstanding receivables. You use these resubmissions in the collection process with the Process Receivables app.
Manage Promises to Pay
Business Role: Accounts Receivable Accountant
Use this app to manage promises to pay of customers, which were created in the collection process using the Process Receivables app. You can display, edit, and withdraw promises to pay.
Manage Collections Master Data
Business Role: Accounts Receivable Accountant
Use this app to activate customers for Collections Management processes. For activated accounts, you can maintain Collection Groups per Collection Segments as well as assign Specialists on Collection Segment level.
Fields (23)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | CollectionSegment | CollectionSegment | ||
| KEY | BusinessPartner | BusinessPartner | ||
| BusinessPartnerPerson | BusinessPartnerPerson | |||
| FirstName | FirstName | |||
| LastName | LastName | |||
| BusinessPartnerName | BusinessPartnerName | |||
| PhoneNumber | PhoneNumber | |||
| MobileNumber | MobileNumber | |||
| FaxNumber | FaxNumber | |||
| FaxCountry | FaxCountry | |||
| EmailAddress | EmailAddress | |||
| ContactPersonDepartment | ContactPersonDepartment | |||
| ContactPersonFunction | ContactPersonFunction | |||
| ContactPersonDepartmentName | ContactPersonDepartmentName | |||
| ContactPersonFunctionName | ContactPersonFunctionName | |||
| ContactPerson | ContactPerson | |||
| ContactCardPictureURL | ContactCardPictureURL | |||
| _BPContactToFuncAndDept | _BPContactToFuncAndDept | |||
| _BusinessPartner | _BusinessPartner | |||
| _CntctPersnDeptValueHelp | _CntctPersnDeptValueHelp | |||
| _CntctPersnFuncValueHelp | _CntctPersnFuncValueHelp | |||
| _CollectionSegment | _CollectionSegment | |||
| _CustomerContact | _CustomerContact |
@Metadata: { allowExtensions: true }
@VDM: { usage: { type: [ #TRANSACTIONAL_PROCESSING_SERVICE ] },
viewType: #CONSUMPTION }
@AccessControl: { authorizationCheck: #MANDATORY }
@ObjectModel: { usageType: { serviceQuality: #C,
sizeCategory: #L,
dataClass: #MIXED },
representativeKey: 'BusinessPartner',
semanticKey: [ 'CollectionSegment',
'BusinessPartner' ] }
@EndUserText: { label: 'Main Contact' }
define root view entity C_CollectionsMainContact
provider contract transactional_query
as projection on I_CollectionsMainContact
{
key CollectionSegment,
key BusinessPartner,
BusinessPartnerPerson,
FirstName,
LastName,
BusinessPartnerName,
PhoneNumber,
MobileNumber,
FaxNumber,
FaxCountry,
EmailAddress,
ContactPersonDepartment,
ContactPersonFunction,
ContactPersonDepartmentName,
ContactPersonFunctionName,
ContactPerson,
ContactCardPictureURL,
/* Associations */
_BPContactToFuncAndDept,
_BusinessPartner,
_CntctPersnDeptValueHelp,
_CntctPersnFuncValueHelp,
_CollectionSegment,
_CustomerContact
}
Learn More
- What Is a CDS View in SAP S/4HANA?
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- CDS View Annotations — A Complete Guide
- 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