I_EmplContactCard
Employee Contact Card for CATS Applications
I_EmplContactCard is a Composite CDS View that provides data about "Employee Contact Card for CATS Applications" in SAP S/4HANA. It reads from 1 data source (I_PersonWorkAgreement_1) and exposes 3 fields with key field PersonWorkAgreement. It has 1 association to related views. It is exposed through 1 OData service (UI_SOURCINGPROJECT_MANAGE). It is used in 3 Fiori applications: Manage Sourcing Projects, Display Sourcing Project, Contribute to Sourcing Projects.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_PersonWorkAgreement_1 | _PersonWorkAgreement | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | I_WorkforcePersonImageURL | _WorkforcePersonImageURL | _WorkforcePersonImageURL.Person = _PersonWorkAgreement.Person |
Annotations (10)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | IEMPLCONTACTCARD | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| EndUserText.label | Employee Contact Card for CATS Applications | view | |
| VDM.viewType | #COMPOSITE | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.serviceQuality | #D | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.dataClass | #MASTER | view | |
| AccessControl.personalData.blocking | #REQUIRED | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_SOURCINGPROJECT_MANAGE | UI_SOURCINGPROJECT_MANAGE | V2 | C1 | NOT_RELEASED |
Fiori Apps (3)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F4861 | Manage Sourcing Projects | Transactional | An application to create and manage sourcing projects. |
| F5934 | Display Sourcing Project | Transactional | An application to approve Sourcing Projects. |
| F7757 | Contribute to Sourcing Projects | Transactional | The app is an application to contribute to sourcing projects as an additional user. |
Manage Sourcing Projects
Business Role: Sourcing Manager
Key functionalities:1. Support for "strategic" and "demand driven" sourcing processes2. Determine and invite suppliers as per "preferred supplier list"3. Create/add legal and other co-applicable documents to the sourcing project4. Evaluate and negotiate supplier quotations5. Create awarding scenarios to award the most suitable supplier quotations6. Create follow-on documents for the awarded quotations – purchase orders or central purchase contractsFor more information, see Product Sourcing.
Display Sourcing Project
Business Role: Purchasing Manager
Key functionalities:1. Support for "strategic" and "demand driven" sourcing processes2. Determine and invite suppliers as per "preferred supplier list"3. Create/add legal and other co-applicable documents to the sourcing project4. Evaluate and negotiate supplier quotations5. Create awarding scenarios to award the most suitable supplier quotations6. Create follow-on documents for the awarded quotations – purchase orders or central purchase contractsFor more information, see Product Sourcing.
Contribute to Sourcing Projects
Business Role: Employee - Sourcing
With this release, if the sourcing managers invite you to contribute, you can support them by enhancing the sourcing projects that they have created. For example, you can add attachments to the sourcing projects that you are invited to contribute to.
Fields (3)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | PersonWorkAgreement | I_PersonWorkAgreement_1 | PersonWorkAgreement | |
| PersonExternalID | ||||
| IsBusinessPurposeCompleted | Name |
@AbapCatalog.sqlViewName: 'IEMPLCONTACTCARD'
@AbapCatalog.compiler.compareFilter: true
@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Employee Contact Card for CATS Applications'
@VDM.viewType: #COMPOSITE
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.usageType.serviceQuality : #D
@ObjectModel.usageType.sizeCategory : #L
@ObjectModel.usageType.dataClass: #MASTER
@AccessControl.personalData.blocking: #REQUIRED
define view I_EmplContactCard
as select from I_PersonWorkAgreement_1 as _PersonWorkAgreement
association [0..1] to I_WorkforcePersonImageURL as _WorkforcePersonImageURL on _WorkforcePersonImageURL.Person = _PersonWorkAgreement.Person
{
@Semantics.contact.type: #PERSON
@UI.hidden: true
key _PersonWorkAgreement.PersonWorkAgreement,
@UI.hidden: true
_PersonWorkAgreement._WorkforcePerson.PersonExternalID,
@UI.hidden: true
@Semantics.contact.photo: true
case
when _WorkforcePersonImageURL.WorkforcePersonImageURL is null
then 'sap-icon://person-placeholder'
else
_WorkforcePersonImageURL.WorkforcePersonImageURL
end as EmployeeImageURL,
@Consumption.hidden: true
_PersonWorkAgreement._WorkforcePerson.Person,
@Semantics.text: true
@Semantics.name.fullName: true
@EndUserText.label: 'Name'
_PersonWorkAgreement._WorkforcePerson.PersonFullName,
@UI.hidden: true
@Semantics.telephone.type: [ #CELL ]
_PersonWorkAgreement._WorkforcePerson._WorkplaceAddress.MblNormalizedPhoneNumber,
@UI.hidden: true
@Semantics: { telephone.type: [ #WORK, #PREF ] }
_PersonWorkAgreement._WorkforcePerson._WorkplaceAddress.NormalizedPhoneNumber,
@UI.hidden: true
@Semantics.eMail.address: true
@Semantics:{ eMail.type: [ #WORK ] }
_PersonWorkAgreement._WorkforcePerson._WorkplaceAddress.DefaultEmailAddress,
@UI.hidden: true
@Semantics.name.jobTitle: true
_PersonWorkAgreement._PersonWrkAgrmtForKeyDate(P_KeyDate: $session.system_date)._PersonWorkAgrmtJobText[1:Language = $session.system_language].JobName,
@Consumption.hidden: true
_PersonWorkAgreement.AuthorizationGroup,
@Consumption.hidden: true
_PersonWorkAgreement._PersonWrkAgrmtForKeyDate(P_KeyDate: $session.system_date).PersonWorkAgrmtAuthznGrpg,
@Consumption.hidden: true
_PersonWorkAgreement._WorkforcePerson.IsBusinessPurposeCompleted
// BP Data Controller logic commented for CE2308
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataControllerSet as DataControllerSet,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController1 as DataController1,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController2 as DataController2,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController3 as DataController3,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController4 as DataController4,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController5 as DataController5,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController6 as DataController6,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController7 as DataController7,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController8 as DataController8,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController9 as DataController9,
// @Consumption.hidden: true
// _PersonWorkAgreement._BusinessPartner.DataController10 as DataController10
}
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