OData Services
OData Services
PUBLIC
2022-10-31
OData Services
2 New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 What's New in OData API v2 Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Add Public Solution Model (PSM) Fields to Standard OData Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3 Transport Custom OData Services with Transport Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4 Compatibility Mode for READ Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.5 Support for User-Friendly IDs in Standard OData Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
2.6 Constant Values to Function Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
OData Services
2 PUBLIC Content
4 OData Service Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
4.1 Creating an OData Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
4.2 Testing an OData Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
OData Services
Content PUBLIC 3
1 SAP Cloud for Customer OData API
The SAP Cloud for Customer OData API conforms to OData version 2 specification.
The complete list of collections (or data end-points) of SAP Cloud for Customer OData API, are listed in the OData
API Reference section of this document.
Related Information
1.1 Purpose
Use the OData API, to query, read, add, update and delete data from and into SAP Cloud for Customer.
This document is a reference point for learning SAP Cloud for Customer OData API. You'll find a short introduction
to the capabilities of the OData API as well as information on where to find more details.
OData (Open Data Protocol) is an OASIS Standard that defines a protocol for building and consuming RESTful APIs,
based on the HTTP protocol.
OData differentiates itself from most of the other RESTful APIs, mainly by providing the following:
The protocol allows filtering data, ordering and paginating of the query results, retrieving number of records, and
more. Querying and modifying data is possible in XML (AtomPub) and JSON formats.
For more information on OData protocol, please visit to http://www.odata.org, where you can find different versions
of OData specifications, community resources (such as OData providers and consumer libraries), sample OData
services and tutorials.
OData Services
4 PUBLIC SAP Cloud for Customer OData API
Related Information
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata
http://www.odata.org/
You can access the SAP Cloud for Customer OData API of your tenant, with the URL pattern: https://
<your_tenant>/sap/c4c/odata/v1/c4codataapi
You can access the metadata of the OData API of your tenant, with the URL pattern: https://
<YourTenant>/sap/c4c/odata/v1/c4codataapi/$metadata
1.5 Authentication
Learn about security options for accessing the SAP Cloud for Customer OData API.
Client applications using the OData API, have four options for providing authorization and authentication for their
users:
• Basic Authentication
• OAuth 2.0
• X.509
• SAML (Security Assertion Markup Language) based single sign-on.
Using OAuth 2.0 requires a trust relationship to be configured between SAP Cloud for Customer and the identity
provider of your client application in the Administrator work center.
See Create Trust Between the Customer Account and SAP Cloud for Customer.
OData Services
SAP Cloud for Customer OData API PUBLIC 5
1.6 Authorization
Authorization of a business user in the user interface is usually the same as the authorization in OData Services.
However, there are some exceptions to this behavior.
Restriction at Work Center Work center view is assigned Work center view is visible OData service with work cen
without data restriction. ter view assigned has full ac
View with no restrictions in the Ad
cess to all data and opera
ministrator work center.
tions.
Access Restriction at In Work center view is assigned Work center view is visible, OData honors RBAM restric
stance with Read and Write restric and data visibility is restricted tion and limits the access.
tion. as configured in user access
Example: Only opportunities
management.
Example: Opportunity with with sales territory 17 are
sales territory 17 is restricted Example: User can see oppor available. Create/Update/
(both Read and Write) for the tunities with sales territory 17 Delete is restricted for oppor
user. only. tunities with sales territory 17.
Restrictions in Field You can use business roles to The object work list (OWL) OData doesn’t honor field re
restrict (Hide/ReadOnly/ doesn’t hide the restricted striction and field is visible in
UnRestricted) the fields (hidden) field, but data isn’t response.
(standard and extension) from displayed.
the work center views added
Thing Inspector UI hides the
to business role.
restricted field.
Example:
ExpectedRevenueAmout
field in an opportunity is hid
den.
Action Restriction You can use business roles to UI restricts user from execut Restriction isn’t honored. It’s
restrict business object ac ing the action. possible to execute the re
tions. stricted function import.
SAP Key User Tool (KUT) KUT fields with business logic. UI honors KUT adaptations KUT adaptations aren’t hon
ored.
Adaptations
Example: KUT field’s visibility
based on business role.
OData Services
6 PUBLIC SAP Cloud for Customer OData API
Behavior in User Interface
Use Case Description (UI) Behavior in OData Service
UI Switches UI switches are defined by UI switches are honored as UI Switches aren’t honored.
custom development and can configured.
Data encapsulated within sec
be used to make fields, but
tion groups that is hidden via
tons, or sections of user inter
UI switch is available in OData
faces hidden, read-only, or
response.
mandatory. You can use them
to assign a particular version
of a UI to a business role and
to its affected users.
To learn more about UI switches, see the blog Make a UI flexible/dynamic using UI Switch .
In previous releases, your users may have been able to consume the impacted OData services without the
necessary authorization assignments. For those users, this is an incompatible change. As of the August 2020
release, you must assign the work center view assignments as listed in the table for these users.
Authoriza
tion Assign
ment Data Work
OData Entity Type
bench Rele
Service Entity Type UI Text (La (Assign at vant Serv
Name Name bel) least one.) ice
OData Services
SAP Cloud for Customer OData API PUBLIC 7
Authoriza
tion Assign
ment Data Work
OData Entity Type
bench Rele
Service Entity Type UI Text (La (Assign at vant Serv
Name Name bel) least one.) ice
COD_SALE
SORDER_W
CVIEW
COD_SALE
SORDER_W
CVIEW
COD_SALE
SORDER_W
CVIEW
OData Services
8 PUBLIC SAP Cloud for Customer OData API
Authoriza
tion Assign
ment Data Work
OData Entity Type
bench Rele
Service Entity Type UI Text (La (Assign at vant Serv
Name Name bel) least one.) ice
COD_SALE
SORDER_W
CVIEW
COD_SALE
SORDER_W
CVIEW
OData Services
SAP Cloud for Customer OData API PUBLIC 9
Authoriza
tion Assign
ment Data Work
OData Entity Type
bench Rele
Service Entity Type UI Text (La (Assign at vant Serv
Name Name bel) least one.) ice
tachment tachments
TIONNAIR
E_WCVIEW
tachmen tachment
TIONNAIR
E_WCVIEW
tReference Reference
tions tions
TIONNAIR
E_WCVIEW
Conditions Conditions
TIONNAIR
E_WCVIEW
OData Services
10 PUBLIC SAP Cloud for Customer OData API
Authoriza
tion Assign
ment Data Work
OData Entity Type
bench Rele
Service Entity Type UI Text (La (Assign at vant Serv
Name Name bel) least one.) ice
ing Rating
TIONNAIR
E_WCVIEW
nAnswers Answers
TIONNAIR
E_WCVIEW
tachment tachments
TIONNAIR
E_WCVIEW
tem Item
TIONNAIR
E_WCVIEW
naire
TIONNAIR
E_WCVIEW
signTime naire
TIONNAIR
E_WCVIEW
OData Services
SAP Cloud for Customer OData API PUBLIC 11
Authoriza
tion Assign
ment Data Work
OData Entity Type
bench Rele
Service Entity Type UI Text (La (Assign at vant Serv
Name Name bel) least one.) ice
Caution
As an administrator, you can assign any workcenter to a OData service without validating the assignment. This
will result in business partners with the same workcenter assigned having access to the OData service and
being able to retrieve data that are not visible to them in the UI. Hence, you must be cautious while assigning
workcenters.
SAP Cloud for Customer OData API supports OData V2 system query options listed below:
• $count
• $expand
• $filter
• $format
• $inlinecount
• $orderby
• $search
• $select
• $skip
• $skiptoken
• $top
Usage information, examples and possible restrictions are described in the SAP Cloud for Customer OData
Developer’s Guide .
OData Services
12 PUBLIC SAP Cloud for Customer OData API
2 New Features
This topic lists all OData API documentation that have been modified in each release version.
• ODATA_BUPA_RELATIONSHIP_1
• ODATA_COMPETITOR_01
• ODATA_CONTACT_01
• ODATA_CUSTOMER_01
• ODATA_EMPLOYEEANDUSER_01
• ODATA_IND_CUSTOMER_01
• ODATA_PARTNERCONTACT_01
• ODATA_PARTNER_01
• ODATA_SERVICEAGENT_01
• ODATA_CONTACT_01
• ODATA_CUSTOMER_01
• ODATA_IND_CUSTOMER_01
OData Services
New Features PUBLIC 13
• ODATA_ACCOUNT_DC_01
• ODATA_CONTACT_04
• ODATA_CUSTOMER_02
• ODATA_CUSTOMER_07
• ODATA_IND_CUSTOMER_02
• ODATA_IND_CUSTOMER_06
• ODATA_BUPA_RELATIONSHIP_1
• ODATA_BUPA_RELATIONSHIP_2
• ODATA_BUSINESSPARTNER_01
• ODATA_BUSINESSUSER_01
• ODATA_COMPETITOR_01
• ODATA_CONTACT_01
• ODATA_CONTACT_02
• ODATA_CONTACT_06
• ODATA_CUSTOMER_01
• ODATA_CUSTOMER_02
• ODATA_CUSTOMER_05
• ODATA_CUSTOMER_14
• ODATA_EMPLOYEEANDUSER_01
• ODATA_IND_CUSTOMER_01
• ODATA_IND_CUSTOMER_02
• ODATA_IND_CUSTOMER_05
• ODATA_MARKETINGATTRIBUTE_10
• ODATA_PARTNERCONTACT_01
• ODATA_PARTNER_01
• ODATA_PARTNER_02
• ODATA_SERVICEAGENT_01
• ODATA_ACCOUNTHIERARCHYLIST_01
• ODATA_BUYINGCENTER_1
• ODATA_BUYINGCENTER_2
• ODATA_CONTACT_01
OData Services
14 PUBLIC New Features
• ODATA_CUSTOMER_04
• ODATA_EMPLOYEEANDUSER_01
• ODATA_EMPLOYEE_BASIC_DATA_01
• ODATA_IND_CUSTOMER_04
• ODATA_MARKETINGATTRIBUTE_1
• ODATA_MARKETINGATTRIBUTE_10
• ODATA_MARKETINGATTRIBUTE_2
• ODATA_MARKETINGATTRIBUTE_3
• ODATA_MARKETINGATTRIBUTE_4
• ODATA_MARKETINGATTRIBUTE_5
• ODATA_MARKETINGATTRIBUTE_6
• ODATA_MARKETINGATTRIBUTE_7
• ODATA_MARKETINGATTRIBUTE_8
• ODATA_MARKETINGATTRIBUTE_9
• ODATA_EMPLOYEEANDUSER_01
• ODATA_EMPLOYEEANDUSER_02
• ODATA_EMPLOYEEANDUSER_03
• ODATA_EMPLOYEEANDUSER_04
• ODATA_EMPLOYEEANDUSER_05
• ODATA_IDENTITY_01
• ODATA_IND_CUSTOMER_DC_01
• ODATA_ACCOUNT_DC_01
• ODATA_CUSTOMER_01
• ODATA_CUSTOMER_02
• ODATA_CUSTOMER_04
• ODATA_CUSTOMER_06
• ODATA_BUPAMERGE_01
• ODATA_IND_CUSTOMER_01
• ODATA_IND_CUSTOMER_02
• ODATA_IND_CUSTOMER_04
• ODATA_CONTACT_01
• ODATA_BUSINESSUSER_01
• ODATA_BUPA_RELATIONSHIP_1
• ODATA_MARKETINGATTRIBUTE_1
• ODATA_MARKETINGATTRIBUTE_2
• ODATA_MARKETINGATTRIBUTE_3
• ODATA_MARKETINGATTRIBUTE_4
OData Services
New Features PUBLIC 15
• ODATA_MARKETINGATTRIBUTE_5
• ODATA_MARKETINGATTRIBUTE_6
• ODATA_MARKETINGATTRIBUTE_7
• ODATA_MARKETINGATTRIBUTE_8
• ODATA_MARKETINGATTRIBUTE_9
• ODATA_MARKETINGATTRIBUTE_10
1. Click your profile on the top right corner of your screen, and select Start Adaptation.
2. Navigate to the screen where the PSM field exists and click to select the relevant section. The system
highlights the section with a red box.
3. In the side pane, click next to Header to see the list of available fields.
4. Navigate to the PSM field and click next to it. The system highlights the PSM field with a red box to indicate
that it is editable.
5. Click Edit. The system displays the table with the list of available OData extensions.
6. Click the Edit icon and the Action column appears in the table.
7. Under Action, click the Add Field icon next to the OData Service where you want to add the PSM field. The
system indicates that it has been added with a check sign in the Field Added column.
8. Click Save.
Note
• This is applicable only for standard PSM fields extended via adaptation. PSM fields created using SAP
Cloud Applications Studio are not supported.
• You can transport PSM OData configuration from a test to a productive environment via Transport
Management. In Transport Management, the Adaptation Changes provider proposes relevant PSM OData
configuration as optional dependencies.
• You cannot remove a PSM field from an OData service if it is already shipped as part of standard OData
service by SAP.
• This feature is not available for the Lead UIs, such as Lead, Lean Lead, and Deal Registration UIs.
You can use Transport Management to move custom OData Services between different tenants.
OData Services
16 PUBLIC New Features
1. To add a Transport Object, under Transport Object Type, select Custom OData Service.
2. Select the Custom Service Name and then click OK.
3. Select the transport object and click Add Selected.
We’ve introduced a new HTTP request header odata-v2-strict-json-format : true, which changes the
results tag in response as follows:
When you use this header, you receive a response payload that is compatible with OData API v2 protocol.
This feature is helpful if you use third-party tools that require strict adherence to the OData V2 protocol.
User-friendly IDs (UIDs or Known IDs) are available as a key to read, update, and delete data records via standard
OData services.
UIDs are the same as the IDs displayed in the user interface and therefore, are more user-friendly. This feature is
offered as an alternative to ObjectID as the key.
ObjectID is used as the key if a UID isn't configured for an entity type. To find the entity type that support UIDs, see
the OData metadata.
https://myxxxxxx.crm.ondemand.com/sap/c4c/odata/uid/v1/c4codataapi/$metadata.
This feature allows constant values to be passed to a query that simplifies the associated Query request by
reducing the number of parameters required.
If only appointments have to be retrieved using this query (and not other activity types such as email and fax),
query parameters TypeCode, GroupCode can be assigned with the following constant values: TypeCode
EQ ”12” and GroupCode NE “0027”.
OData Services
New Features PUBLIC 17
3 OData API Reference
OData API v2 covers over 40 main business objects, allowing read and/or write access to more than 1000
collections (data points). You can access the API reference document here: OData API v2 Reference.
You can access the metadata of the OData API of your tenant, with the URL pattern: https://
<YourTenant>/sap/c4c/odata/v1/c4codataapi/$metadata
The service c4codataapi is a container for several individual object-specific OData services. Hence, extension
fields must be added to these individual services. Extension fields added to individual services automatically reflect
in c4codataapi. The individual services that you need to select when adding an extension field to a particular object
is listed here.
Note
The c4codataapi service does not appear in Key User Extension UI and SAP Cloud Applications Studio.
Appointment activity
EMail activity
Task activity
Visit activity
Campaign campaign
Competitor competitor
OData Services
18 PUBLIC OData API Reference
Object/Entity Type Service
Contact contact
Contract contract
Account customer
Employee employeeanduser
Lead lead
Opportunity opportunity
Partner partner
Product product
OData Services
OData API Reference PUBLIC 19
Object/Entity Type Service
Questionnaire survey
Information on Deprecation
See information on deprecation and our updated API Strategy [page 201].
OData Services
20 PUBLIC OData API Reference
• Appointment Entity Type [page 40]
• EMail Entity Type [page 61]
• Phone Call Entity Type [page 137]
• Task Entity Type [page 170]
Note
For details on the associations between entities, see the navigation details of the respective entity.
The accuracy of the information provided about the Nullable property in the SAP Cloud for Customer OData
API collection document might not always be accurate. If the Nullable attribute has the value:
• True, then this property can be left empty. In some cases, due to application-specific behavior, or the
dependency on the value of another property, a property value must be specified even if the value of the
Nullable property is indicated as True. For create or update calls on such properties, the system returns a
specific error message if the value is left blank.
• False, such a property must never be left blank.
Overview
AccountContactRelationship entity type is already part of C4CODATA, as a part of clean up duplicate entries from
other entity type of AccountContactRelationship which is AccountContactCommunicationData.
Properties
OData Services
OData API Reference PUBLIC 21
3.2.2 Account EntityType
The Account related collections allow you to read and maintain Accounts and their related data such as Address,
Contacts related to the Accounts and their addresses.
3.2.2.1 Account
Overview
The Account collection provides information about corporate customers and prospects. These are existing
organizations and potential customers for the company.
OData Services
22 PUBLIC OData API Reference
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/AccountCollection
Properties
Name
OData Services
OData API Reference PUBLIC 23
Name Type Nullable Max Length Fixed length $ Search Relevant
OData Services
24 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length $ Search Relevant
nicationMediumTy
peCode
Name
OData Services
OData API Reference PUBLIC 25
Name Type Nullable Max Length Fixed length $ Search Relevant
Navigations
OData Services
26 PUBLIC OData API Reference
3.2.2.2 AccountAddress
Overview
The AccountAddress collection provides detailed organization address of corporate customer and prospects.
Account
Properties
OData Services
OData API Reference PUBLIC 27
Name Type Nullable Max Length Fixed length $ Search Relevant
Navigations
Overview
The AccountAttachment collection provides information about various attachments such as Documents, Images
etc. associated to a particular Corporate Customer.
These attachment types can be created, updated, and viewed using this collection.
OData Services
28 PUBLIC OData API Reference
Top Level Entity
Account
Properties
Overview
OData Services
OData API Reference PUBLIC 29
Top Level Entity
Account
Properties
Navigations
Overview
The AccountContactRelationship collection sets up the relationship between contact and accounts. A single
contact can be associated with multiple Accounts and vice versa.
Properties
OData Services
30 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length $ Search Relevant
Navigations
Overview
Usage Scenario
The AccountContacts cannot be created whereas can be updated. This displays the contact details provided in the
AccountContactRelationship.
OData Services
OData API Reference PUBLIC 31
Top Level Entity
AccountContactRelationship
Properties
3.2.2.7 AccountNotes
Overview
The AccountNotes collection provides information about the corporate customers and prospects, and allows to
add and view the data.
Account
OData Services
32 PUBLIC OData API Reference
Properties
Navigations
Overview
Account
OData Services
OData API Reference PUBLIC 33
Usage
The property RoleCode has an associated collection – AccountRoleCodeCollection that gives the list of all the roles
and its descriptions. This collection can be used to find the values that can be given for the property RoleCode
during the creation of this entity.
Properties
Navigations
3.2.2.9 AccountSalesData
Overview
The AccountSalesDataCollection provides information about sales related data for an account like sales
organization, group and its associated incoterms, and payment terms.
OData Services
34 PUBLIC OData API Reference
Top Level Entity
Account
Properties
OData Services
OData API Reference PUBLIC 35
PaymentTermsCode Edm.String TRUE 4 TRUE
Navigations
3.2.2.10 AccountSalesGroupName
Overview
The AccountSalesGroupName collection provides the list of Sales group names present in the AccountSalesData
entity type.
OData Services
36 PUBLIC OData API Reference
Properties
3.2.2.11 AccountSalesOfficeName
Overview
The AccountSalesOfficeName collection provides the list of all Sales group names present in the AccountSalesData
entity type.
Properties
3.2.2.12 AccountSalesOrganisationName
Overview
The AccountSalesOrganisationName collection provides the list of all Sales group names present in the
AccountSalesData entity type.
OData Services
OData API Reference PUBLIC 37
Top Level Entity
Properties
3.2.2.13 AccountTeam
Overview
The AccountTeam collection provides information about the team that belongs to a corporate account.
Account
Properties
OData Services
38 PUBLIC OData API Reference
EndDate Edm.DateTime TRUE
Navigations
3.2.2.14 AccountTeamAddress
Overview
The AccountTeamAddress collection provides the E-mail ID and phone of the employee that belongs to an account
team.
Account
OData Services
OData API Reference PUBLIC 39
Properties
The Appointment related collections allow you to read and maintain appointments and related data such as
attachments and involved parties (such as sender, recipient, account etc.)
3.2.3.1 Appointment
Overview
OData Services
40 PUBLIC OData API Reference
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/AppointmentCollection
Properties
OData Services
OData API Reference PUBLIC 41
OwnerUUID Edm.Guid true
The Property Type Code has a default value and cannot be changed.
Navigations
OData Services
42 PUBLIC OData API Reference
3.2.3.2 Appointment Attachment
Overview
Appointment
Properties
OData Services
OData API Reference PUBLIC 43
3.2.3.3 Appointment Involved Parties
Overview
The Appointment Involved Parties collection provides contact information of all parties involved (such as Sender,
Recipient, Account, Employee Responsible etc.) in the appointment..
Properties
OData Services
44 PUBLIC OData API Reference
Navigations
mentt
Overview
Appointment
Properties
OData Services
OData API Reference PUBLIC 45
TypeCodeText Edm.String true
Overview
BusinessPartnerCollection provides information about all Business Partners i.e. Accounts, Individual Customers,
Contacts, Employees, Competitors, Partners etc.
ThingType property refers to the thing type associated with a business partner instance. ThingType is used for
navigation and displaying data for corresponding Business Partner in the standard UI in SAP Cloud for Customer.
The BusinessPartnerCollection is read-only and can be used to determine the correct entity type referred to in a
party collection based on the Party UUID.
Properties
Mapping
OData Services
46 PUBLIC OData API Reference
ThingType Related C4C-BuPa-UI Corresponding C4CODATA-EntityType
The CodeList Entity Type is a Single EntityType.The EntityGroup description are not required.
3.2.5.1 Codelist
Overview
The Codelist collection provides a list of codes and their corresponding descriptions for a code type collection. It is
automatically added into the service metadata if it contains any properties representing a code type.
Properties
OData Services
OData API Reference PUBLIC 47
3.2.6 Contextual CodeList Entity Type
The ContextualCodeList Entity Type is a Single Entity Type. The EntityGroup description is not required.
Overview
Contextual CodeList collection provides a list of contexts, codes, and their corresponding descriptions.
ContextualCodeList entity type is automatically added into the service metadata, if the service contains any
properties of the type.
Along with Code and Description, ContextualCodeList entity type has a context parameter for which the codes are
relevant. For example, Region in an address is contextual. A Region or State “NY” is relevant both for countries with
country codes: US and GB. If a user has to fetch all region codes of country “US”, corresponding collection has to
be filtered using Context = “US”. If a context is not provided, all the regions in the world shall be returned.
OData Services
48 PUBLIC OData API Reference
Entities cannot be created, updated or deleted in the corresponding entity sets. All entity sets based on
ContextualCodeList shall be read-only. Key of the entity type includes both Code and Context.
Properties
OData Services
OData API Reference PUBLIC 49
3.2.7 Contact Entity Type
The Contact related collections allow you to read and maintain Contacts to Accounts and their personal addresses
Overview
The ContactAttachment collection provides information about various attachments such as Documents, Images
etc. associated to a particular contact.
OData Services
50 PUBLIC OData API Reference
Top Level Entity
Contact
Properties
3.2.7.2 Contact
Overview
The Contact collection provides the contact information of a particular account. The Contacts are organized based
on the accounts from where they originate from. A contact can be related to multiple Accounts/Contacts or can be
related to a single account..
OData Services
OData API Reference PUBLIC 51
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/ContactCollection
Properties
OData Services
52 PUBLIC OData API Reference
AdditionalAcade Edm.String true 4 true
micTitleCode
CategoryCodeText Edm.String
StatusCode Edm.String
StatusCodeText Edm.String
LanguageCodeText Edm.String
TitleCodeText Edm.String
OData Services
OData API Reference PUBLIC 53
Navigations
Overview
The ContactNotes collection provides information about the notes attached to a particular contact..
Contact
Properties
OData Services
54 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length $Search Relevant
Overview
The ContactPersonalAddess collection provides personal address information for a contact. A particular contact
can have multiple personal address and one among them would be the default address.
Contact
Properties
OData Services
OData API Reference PUBLIC 55
Name Type Nullable Max Length Fixed length $Search Relevant
Navigations
Overview
The ContactPersonalPostalAddress collection provides the postal address associated to a particular contact. There
can be multiple addresses associated to a single contact, and any one of the contact can be marked as the default
address.
ContactPersonalAddress
Properties
OData Services
56 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length $Search Relevant
Navigations
OData Services
OData API Reference PUBLIC 57
3.2.7.6 Contact Business Address
Overview
The ContactBusinessAddress collection provides information about the accounts related to a particular contact. A
particular contact can be related to many accounts. It also includes the business address referred to by the contact
for a particular account.
.
Contact
Properties
Navigations
OData Services
58 PUBLIC OData API Reference
3.2.7.7 Contact Business Postal Address
Overview
ContactBusinessAddress
Properties
OData Services
OData API Reference PUBLIC 59
3.2.7.8 Contact Communication Data
Overview
The ContactCommunicationData collection provides information about the workplace addresses associated with a
particular account and contact relationship. There can be only one workplace address maintained for a particular
relationship
Contact
Properties
OData Services
60 PUBLIC OData API Reference
Navigations
The Email related collections allow you to read and maintain Email communication done with business partners
and related data such as attachments and recipients
OData Services
OData API Reference PUBLIC 61
3.2.8.1 EMail
Overview
The EMail collection allows you to synchronize and view E-mail communication done with business partners and
associates the E-mail with related objects such as an account, opportunity, lead, or sales quote.
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/EmailCollection
Properties
Max
Name Type Nullable Length Fixed length
OData Services
62 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length
Navigations
OData Services
OData API Reference PUBLIC 63
3.2.8.2 EMail Attachment
Overview
The EMailAttachment collection provides information about attachments in E-mail. For example, attachments of E-
mail associated to an account, opportunity, lead or sales quote is synchronized with SAP Cloud for Customer, and
thereby can be updated and viewed using EMailAttachmentCollection.
Properties
Max
Name Type Nullable Length Fixed length
OData Services
64 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length
Navigations
Overview
The EMailCcRecipients collection provides information about all the Copied Recipients in E-mail.
OData Services
OData API Reference PUBLIC 65
Properties
Navigations
Overview
OData Services
66 PUBLIC OData API Reference
Note
Properties
Max
Name Type Nullable Length Fixed length
OData Services
OData API Reference PUBLIC 67
3.2.8.5 Email To Recipients
Overview
The EMailToRecipients collection provides information about all “To” Recipients in E-mail.
Properties
Max
Name Type Nullable Length Fixed length
OData Services
68 PUBLIC OData API Reference
Navigations
The Employee related collections allow you to read and maintain Employees and related data such as their
addresses. Employee entity type is already part of C4CODATA, as a part of clean up duplicate entries from other
entity type of employee such as EmployeeBusinessAddress, EmployeeComminicationData and
EmployeeFormattedBusinessAddress.
Properties
OData Services
OData API Reference PUBLIC 69
Name Type Description $search relevant
OData Services
70 PUBLIC OData API Reference
Name Type Description $search relevant
3.2.9.1 Employee
Overview
The Employee collection provides details about internal and external employees for an organization. The
Employees have their respective roles assigned and associated to an account, team etc.
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/EmployeeCollection
OData Services
OData API Reference PUBLIC 71
Properties
OData Services
72 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length
TimeZoneCodeText Edm.String
Navigations
Data Data
Overview
The EmployeeBusinessAddress collection entity provides details about the organization address of the employees.
Employee
OData Services
OData API Reference PUBLIC 73
Properties
Navigations
sAddress sAddress
Overview
The EmployeeCommunicationData collection entity provides workplace organization details of the employees..
OData Services
74 PUBLIC OData API Reference
Top Level Entity
Employee
Properties
Navigations
Overview
The EmployeeFormattedBusinessAddress collection entity provides the employees business address in a format.
OData Services
OData API Reference PUBLIC 75
Usage Scenario
This is only a read-only entity, and cannot be created or updated. It is created automatically once address is
created.
EmployeeBusinessAddress
Properties
Navigations
OData Services
76 PUBLIC OData API Reference
3.2.10 External ID Mapping Entity Type
The External ID Mappping Entity Type is a Single EntityType. The EntityGroup description are not required.
Overview
The ExternalIDMapping collection entity provides mapping details of a local object identifier corresponding to an
object identifier in a remote system.
Usage Scenario
OData Services
OData API Reference PUBLIC 77
Properties
The Individual Customer related collections allow you to read and maintain individual customers and their
addresses. Employee entity type is already part of C4CODATA, as a part of clean up duplicate entries from other
entity type of IndividualCustomer such as EmployeeBusinessAddress, EmployeeComminicationData and
EmployeeFormattedBusinessAddress.
OData Services
78 PUBLIC OData API Reference
Properties
Overview
The Individual Customer collection provides information about customers who are not associated with a corporate
account, and do business with the company directly.
Such customers can be created, updated and viewed using this collection.
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/IndividualCustomerCollection
Properties
OData Services
OData API Reference PUBLIC 79
Name Type Nullable Max Length Fixed length
guageCodeText
CountyName
OData Services
80 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length
OData Services
OData API Reference PUBLIC 81
Name Type Nullable Max Length Fixed length
OData Services
82 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length
Navigations
Overview
The Individual Customer Attachment collection provides information about customers who are not associated with
a corporate account, and do business with the company directly.
These attachments can be created, updated, and viewed using this collection.
OData Services
OData API Reference PUBLIC 83
Top Level Entity
IndividualCustomer
Properties
OData Services
84 PUBLIC OData API Reference
3.2.11.3 Individual Customer Common
Overview
IndividualCustomer
Properties
OData Services
OData API Reference PUBLIC 85
Name Type Nullable Max Length Fixed length
deText
Navigations
Overview
The IndividualCustomerNotes collection allows you to add more information about a Customer.
IndividualCustomer
OData Services
86 PUBLIC OData API Reference
Properties
OData Services
OData API Reference PUBLIC 87
3.2.12 Lead Entity Type
The lead related collections allow you to read and maintain sales leads and related data such as products, parties
involved and business transaction document references.
3.2.12.1 Lead
Overview
The Lead collection(LeanLead) represents an individual or organization that a company has the potential to do
business with and is based on a similar SAP CRM functionality.
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/LeadCollection
OData Services
88 PUBLIC OData API Reference
Attribute Definition
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
OData API Reference PUBLIC 89
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
90 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
OData API Reference PUBLIC 91
Max
Name Type Nullable Length Fixed length $Search Relevant
EmployeeResponsi Edm.Guid
bleUUID
OData Services
92 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
OData API Reference PUBLIC 93
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
94 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
OData API Reference PUBLIC 95
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
96 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
OData API Reference PUBLIC 97
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
98 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
OData API Reference PUBLIC 99
Max
Name Type Nullable Length Fixed length $Search Relevant
Navigation
Overview
The LeanLeadAttachmentFolder collection provides information about existing attached documents in the Leads.
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/LeanLeadAttachmentFolderCollection
Attribute Definition
OData Services
100 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed Length $Search Relevant
Overview
LeanLead
OData Services
OData API Reference PUBLIC 101
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/LeanLeadBusinessTransactionDocumentReference
Collection
Properties
ID Edm.String true 35
Notifications
OData Services
102 PUBLIC OData API Reference
3.2.12.4 Lead Involved Parties
Overview
The LeanLeadInvolvedParties collection provides information about involved parties in the leads.
LeanLead
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/LeanLeadExternalPartyCollection
Properties
OData Services
OData API Reference PUBLIC 103
Name Type Nullable Max Length Fixed Length $Search Relevant
Navigation
Overview
The LeanLeadSalesAndMarketingTeam collection provides information about sales and marketing team of leads.
LeanLead
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/LeanLeadSalesAndMarketingTeamCollection
Properties
OData Services
104 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed Length $Search Relevant
Navigations
Overview
LeanLead
Properties
OData Services
OData API Reference PUBLIC 105
Name Type Nullable Max Length Fixed Length $Search Relevant
Navigations
Overview
The LeanLeadContact collection provides information about all the contacts related to an account of the lead. This
collection cannot be created using OData service. There is a main single contact and multiple contacts for an
opportunity.
LeanLead
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/LeanLeadContactCollection
OData Services
106 PUBLIC OData API Reference
Properties
Navigations
OData Services
OData API Reference PUBLIC 107
3.2.13 Sales Lead Entity Type (Deprecated)
The Sales Lead related collections allow you to read and maintain Sales Leads and related data such as products,
parties involved and business transaction document references.
Overview
The Sales Lead collection provides information about existing Sales Leads.
OData Services
108 PUBLIC OData API Reference
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/LeadCollection
Properties
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
OData Services
OData API Reference PUBLIC 109
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
OData Services
110 PUBLIC OData API Reference
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
Navigations
Overview
The LeadAttachment collection provides information about existing attached documents in Sales Leads.
OData Services
OData API Reference PUBLIC 111
Top Level Entity
Lead
Properties
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
112 PUBLIC OData API Reference
3.2.13.3 Sales Lead Business Document Reference
(Deprecated)
Overview
The LeadBusinessDocumentReference collection provides information about business document references for
Sales Leads.
Lead
Properties
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
ID Edm.String true 35
CRYPTED_LONG_Na
me
OData Services
OData API Reference PUBLIC 113
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
DocumentRelation
shipRoleCode
Navigations
Overview
The LeadInvolvedParties collection provides information about involved parties in Sales Leads.
Lead
OData Services
114 PUBLIC OData API Reference
Properties
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
Navigations
OData Services
OData API Reference PUBLIC 115
3.2.13.5 Sales Lead Product (Deprecated)
Overview
Lead
Properties
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
OData Services
116 PUBLIC OData API Reference
Navigations
Overview
The LeadSalesAndMarketingTeam collection provides information about Sales and Marketing team of Sales Leads.
Lead
Properties
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
OData Services
OData API Reference PUBLIC 117
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
Navigations
OData Services
118 PUBLIC OData API Reference
3.2.14.1 Opportunity
Overview
The Opportunity collection provides information about all opportunities, and these opportunities represent
potential sales. They can be displayed, edited, and even new ones can be created. Opportunities that are converted
from Lead can also be edited.
Properties
AccountUUID true
ApprovalStatusCode
Text
OData Services
OData API Reference PUBLIC 119
Name Type Nullable Max Length Fixed length
ExpectedValue false
Name false
OwnerName true
PrimaryContactID Edm.Sraing
OData Services
120 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length
SalesCycleCodeText Edm.String
OData Services
OData API Reference PUBLIC 121
Name Type Nullable Max Length Fixed length
Navigations
Overview
The OpportunityAppointmentSalesActivity collection provides information about all the sales activities of
opportunities, and these opportunities represent potential sales. These are the activities which are created in order
to follow up with Opportunities. These activities include Appointments, Tasks, PhoneCalls, and E-mails.
Opportunity
OData Services
122 PUBLIC OData API Reference
Properties
Max
Name Type Nullable Length Fixed length
ID Edm.String true 35
BusinessTransaction Edm.String
DocumentRelationshi
pRoleCodeText
OwnerUUID Edm.Guid
OData Services
OData API Reference PUBLIC 123
Navigations
Overview
The OpportunityAttachment collection provides information about all the attachments for opportunities, and these
opportunities represent potential sales. The attachments can be links, images, etc.
Opportunity
Properties
Max
Name Type Nullable Length Fixed length
CreatedOn Edm.DateTime
OData Services
124 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length
Overview
The OpportunityContact collection provides information about all the contacts related to an Account of the
Opportunity, and these opportunities represent potential sales. This collection cannot be created using OData
service. There is a main single contact and multiple contacts for an opportunity.
Opportunity
Properties
OData Services
OData API Reference PUBLIC 125
Name Type Nullable Max Length Fixed length
Mobile Edm.DateTime
Overview
The OpportunityEmailSalesActivity collection provides information about all the e-mail activities created in order to
follow up with the Opportunity.
Opportunity
Properties
Nulla
Name Type ble Max Length Fixed length
ID Edm.Guid true
OData Services
126 PUBLIC OData API Reference
Nulla
Name Type ble Max Length Fixed length
OwnerUUID Edm.Guid
Navigations
OData Services
OData API Reference PUBLIC 127
3.2.14.6 Opportunity Involved Parties
Overview
The OpportunityInvolvedParties collection provides information about all the parties involved in the Opportunity. A
Party can be an employee/organization, who is involved in the Opportunity. They can be a business partner
pertaining to a specialized business Objects, Customer, Supplier, or an Employee. It can also be an organizational
center in the specialized business objects of FunctionalUnit.
Opportunity
Properties
Max
Name Type Nullable Length Fixed length
CRYPTED_LONG_Na
me
OData Services
128 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length
Navigations
Overview
The OpportunityNotes collection provides information about all the text collections or the notes related to an
Opportunity. Examples of text types include explanation texts, internal comments, and shipping instructions.
Opportunity
OData Services
OData API Reference PUBLIC 129
Properties
Overview
The OpportunityContact collection provides information about all the contacts related to an Account of the
Opportunity, and these opportunities represent potential sales. This collection cannot be created using OData
service. There is a main single contact and multiple contacts for an opportunity.
Opportunity
OData Services
130 PUBLIC OData API Reference
Properties
Nulla
Name Type ble Max Length Fixed length
ID Edm.Guid true
BusinessTransaction Edm.String
DocumentRelationshi
pRoleCodeText
OwnerUUID Edm.Guid
OData Services
OData API Reference PUBLIC 131
Navigations
Overview
The OpportunityProduct collection provides information about all the items/products of an Opportunity. An item is
a possibility of selling a quantity of a product or service. It contains product information, quantity, and values.
Opportunity
Properties
Max
Lengt
Name Type Nullable h Fixed length
OData Services
132 PUBLIC OData API Reference
Max
Lengt
Name Type Nullable h Fixed length
Navigations
Overview
The OpportunityProductNotes collection consists of all natural-language texts that refers to an item in an
Opportunity.
Opportunity
OData Services
OData API Reference PUBLIC 133
Properties
Overview
The OpportunitySalesTeam collection specifies a party working on an Opportunity as part of the Sales Team.
Opportunity
OData Services
134 PUBLIC OData API Reference
Properties
Max
Name Type Nullable Length Fixed length
Navigations
Overview
The OpportunityTasksSalesActivity collection provides information about all the task activities created in order to
follow up with the Opportunity..
OData Services
OData API Reference PUBLIC 135
Top Level Entity
Opportunity
Properties
Nulla
Name Type ble Max Length Fixed length
ID Edm.Guid true
OwnerUUID Edm.Guid
PriorityCodeText Edm.String
OData Services
136 PUBLIC OData API Reference
Navigations
The PhoneCall related collections allow you to read and maintain information about PhoneCalls with business
partners and participants in those phone calls.
Overview
The PhoneCall collection allows you to track and document your phone calls with business partners.
OData Services
OData API Reference PUBLIC 137
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/PhoneCallCollection
Properties
OData Services
138 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length $Search Relevant
Navigations
OData Services
OData API Reference PUBLIC 139
3.2.15.2 Phone Call Attachment
Overview
The PhoneCallAttachment collection provides information about the existing attached documents of a Phone Call.
Phone Call
Properties
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
140 PUBLIC OData API Reference
Max
Name Type Nullable Length Fixed length $Search Relevant
Overview
The Phone Call Notes collection allows you to track and document your phone calls with the business partners.
Phone Call
Properties
Max
Name Type Nullable Length Fixed length $Search Relevant
OData Services
OData API Reference PUBLIC 141
Max
Name Type Nullable Length Fixed length $Search Relevant
Overview
The Phone Call Participants collection allows to track and document your phone calls with your business partners.
Phone Call
Properties
OData Services
142 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length
Navigations
The Product related collections allow you to read and maintain products, and categories and sales organization
they are assigned to.
OData Services
OData API Reference PUBLIC 143
3.2.16.1 Product
Overview
A Product is an article or a substance that is manufactured or refined for sale. It can be part of any object instance
such as an Opportunity or Lead etc. Hence, this entity allows you to create, view, and update the product in an
organizational master data
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/ProductCollection
Properties
OData Services
144 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length
Navigations
Overview
The Product Attachment collection provides information about new or existing attached documents of a Product.
Product
Properties
OData Services
OData API Reference PUBLIC 145
Name Type Nullable Max Length Fixed length
Overview
The ProductCategoryAssignment collection provides a category that is associated to a product. This entity helps
you to assign a category to a product.
OData Services
146 PUBLIC OData API Reference
Properties
Navigations
Overview
The Product Category collection contains a tree structure where the Top level hierarchy has multiple sub
categories. A Product can be associated with any of these sub categories or the Top level Hierarchy ID.
Properties
OData Services
OData API Reference PUBLIC 147
Name Type Nullable Max Length Fixed length
Navigations
Overview
The Product Category Hierarchy Description collection provides a Product description of all category hierarchies.
Properties
OData Services
148 PUBLIC OData API Reference
Navigations
Overview
The Product Changed By collection provides information about the Business Partner, who recently changed the
Product. This is a read-only entity.
Properties
Overview
The Product Sales collection provides information about the Sales Organization from which the Product is to be
procured from. Here, we maintain data such as the Quantity and its Unit of Measure, the distribution channel etc.
as mentioned below. We can also track the procurement status.
OData Services
OData API Reference PUBLIC 149
Top Level Entity
Product
Properties
Navigations
OData Services
150 PUBLIC OData API Reference
3.2.16.8 Product Sales Organisation
Overview
The ProductSalesOrganisation collection provides the Sales Organization Information ID of their corresponding
Product
Product
Properties
The ServiceRequest related collections allow you to read and maintain information about ServiceRequest list of
open, completed and in process tickets.
OData Services
OData API Reference PUBLIC 151
3.2.17.1 Service Request
Overview
The ServiceRequest collection provides information about list of open, completed and in process tickets. Multiple
tasks can be performed on tickets such as creation, assignment of ticket, status change, adding notes, priority
change etc.
Properties
1- Not Started
3- In Approval
4- Approved
5 - Rejected
6 - In Revision
7 - Withdrawn
OData Services
152 PUBLIC OData API Reference
Name Type Description
4 - Internet
5 - E-Mail
6 - Social Media
7 - Chat
8 - Telephony
OData Services
OData API Reference PUBLIC 153
Name Type Description
1 - Open
2 - In Planning
3 - Ready
4 - Partially Ready
5 - Started
6 - Finished
7 - Not Relevant
OData Services
154 PUBLIC OData API Reference
Name Type Description
OData Services
OData API Reference PUBLIC 155
Name Type Description
1 - Immediate
2 - Urgent
3 - Normal
7 - Low
OData Services
156 PUBLIC OData API Reference
Name Type Description
1 - Open
2 - In Process
4 - Customer Action
5 - Completed
6 - Closed
Navigations
Folder Folder
OData Services
OData API Reference PUBLIC 157
Name FromEntity ToEntity Cardinality
Overview
The ServicePointLocationAddress Entity collection provides information about the service location where the
service has to be provided.
ServiceRequest
Properties
OData Services
158 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length $ Search Relevant
Overview
The ServiceRequestAttachmentFolder Entity collection provides information about various attachments like
Documents, and Images etc. associated to a particular ticket.
These attachment types can be created and viewed using this collection.
OData Services
OData API Reference PUBLIC 159
Top Level Entity
ServiceRequest
Properties
OData Services
160 PUBLIC OData API Reference
3.2.17.4 Service Request Business Transaction Document
Reference
Overview
ServiceRequest
Properties
ID Edm.String true 35
nelCodeText
OData Services
OData API Reference PUBLIC 161
Navigations
3.2.17.5 ServiceRequestDescription
Overview
The ServiceRequestDescription collection provides information and allows you to view and add more information
related to the ticket. All details such as any email, interaction are mentioned here and used for further processing.
ServiceRequest
Properties
OData Services
162 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length $ Search Relevant
Overview
The ServiceRequestItem collection provides information about the products mentioned in the tickets, which are
open, completed, and in process. Multiple items can be created and it can be updated.
ServiceRequest
Properties
OData Services
OData API Reference PUBLIC 163
Navigations
Overview
ServiceRequest
Properties
OData Services
164 PUBLIC OData API Reference
Navigations
Overview
The ServiceRequestServiceRequestHistoricalVersion collection provides information and allows you to view and
information about Historical data related to the ticket. It provides information such as start and end time,
processor party, teams involved previously.
ServiceRequest
Properties
OData Services
OData API Reference PUBLIC 165
Name Type Nullable Max Length Fixed length $ Search Relevant
Navigations
OData Services
166 PUBLIC OData API Reference
3.2.17.9 Service Issue Category Catalogue
Overview
The ServiceIssueCategoryCatalogue collection provides reference to the Catalogue which contains the Category
selection for the Service Request. It contains a hierarchical structure and is used to define various categories on
Service Request. These categories may change over a period of time and thus can have multiple versions but only
one active version is used for a particular day
ServiceIssueCategory
Properties
Navigations
OData Services
OData API Reference PUBLIC 167
Name FromEntity ToEntity Cardinality
Overview
ServiceIssueCategoryCatalogue
Properties
OData Services
168 PUBLIC OData API Reference
Navigations
Overview
ServiceIssueCategoryCatalogueCategory
Properties
OData Services
OData API Reference PUBLIC 169
Navigations
The Task related collections allow you to read and maintain business relavant measures that need to be taken and
parties involved in these measures.
3.2.18.1 Task
Overview
The Task collection provides information about all business relevant measures that one or more employees of an
organization need to take care within a specified date
OData Services
170 PUBLIC OData API Reference
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/TaskCollection
Properties
$Search Rele
Name Type Nullable Max Length Fixed length vant
OwnerUUID Edm.Guid
OData Services
OData API Reference PUBLIC 171
$Search Rele
Name Type Nullable Max Length Fixed length vant
NORMALISED_Da
teTime
Navigations
OData Services
172 PUBLIC OData API Reference
3.2.18.2 Task Attachment
Overview
The TaskAttachment collection provides information about existing attached documents in the Task.
Task
Properties
$Search Rele
Name Type Nullable Max Length Fixed length vant
OData Services
OData API Reference PUBLIC 173
$Search Rele
Name Type Nullable Max Length Fixed length vant
Overview
The Task Involved Parties collection provides information about all the parties involved in a particular task.
Task
Properties
OData Services
174 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length $ Search Relevant
Navigations
Overview
The Task Notes collection provides key information notes created during the task creation.
Task
Properties
$Search Rele
Name Type Nullable Max Length Fixed length vant
OData Services
OData API Reference PUBLIC 175
$Search Rele
Name Type Nullable Max Length Fixed length vant
3.2.19 TimeEntry
The TimeEntry Entity Type has three entities namely the TimeEntry, TimeEntryItem and the TimeReport. These
entities are used in time recording.
The Time Entry collection is used to maintain time entry of employees. Time entry is an object where an employee
can record his time against his activities for a particular day.
OData Services
176 PUBLIC OData API Reference
Properties
AutoTimeRecordingIndicator Edm.Boolean
BusinessTransactionDocu Edm.String
mentTypeCode
Date Edm.DateTime
ItemReferenceUUID Edm.Guid
1. In Preparation
2. Approval Pending
3. Approved
4. Rejected
5. Released
6. In Approval
OData Services
OData API Reference PUBLIC 177
Name Type Description Search Relevant
1. Working Hours
2. Non-Working Hours
Navigations
3.2.19.2 TimeEntryItem
The Time Entry Item collection is used to maintain time entry items related to the particular time entry. We can
have multiple time entry items for a time entry.
Properties
OData Services
178 PUBLIC OData API Reference
Name Type Nullable Creatable Updatable Filterable
Navigations
3.2.19.3 TimeReport
The Time Report collection is used to maintain time reports of employees. You can use it to group time entries for
an employee for a time period.
Properties
Description c4codata.EXTENDED_Name
OData Services
OData API Reference PUBLIC 179
Name Type Description $ Search Relevant
• In Preparation
• Approval Pending
• Approved
• Rejected
• In Approval
Navigations
The User Entity Type collection is a Single Entity Type. The EntityGroup description are not required.
OData Services
180 PUBLIC OData API Reference
3.2.20.1 User
Overview
The User collection provides information about all the user details.
Request Elements
URL
https://<CloudTenant>/sap/c4c/odata/v1/c4codata/UserCollection
Properties
OData Services
OData API Reference PUBLIC 181
Name Type Nullable Max Length Fixed length
TimeZoneCodeText Edm.String
OData Services
182 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length
The Vist related collections allow you to read and maintain customer site visits, parties involved in the visits and
related business transaction reference documents.
OData Services
OData API Reference PUBLIC 183
3.2.21.1 Visit
Overview
Properties
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
ID Edm.String true 35
OData Services
184 PUBLIC OData API Reference
Max
Lengt
Name Type Nullable h Fixed length $Search Relevant
Note
The properties such as GroupCode and TypeCode have default values that cannot change.
Navigations
OData Services
OData API Reference PUBLIC 185
3.2.21.2 Visit Attachment
Overview
The Visit Attachment collection provides information about attached documents in Visits.
Visit
Properties
OData Services
186 PUBLIC OData API Reference
Name Type Nullable Max Length Fixed length
Overview
The Visit Party collection provides information of all the customers who visits the site.
Visit
Properties
OData Services
OData API Reference PUBLIC 187
Navigations
Overview
The Visit Reference collection provides information about the preceding and succeeding reference documents.
Visit
Properties
OData Services
188 PUBLIC OData API Reference
Navigations
Overview
The VisitText Collection provides information about notes entered during site visit.
Visit
Properties
OData Services
OData API Reference PUBLIC 189
Name Type Nullable Max Length Fixed length
Marketing attributes are associated to master data objects like accounts and contacts. They allow users to define
and maintain name value pairs for master data. They are similar to marketing attributes in SAP CRM.
Attribute definition
Properties
Search Rele
Name Type Nullable Max Length Fixed length vant
OData Services
190 PUBLIC OData API Reference
Search Rele
Name Type Nullable Max Length Fixed length vant
Navigations
Properties
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
OData Services
OData API Reference PUBLIC 191
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
Properties
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
Properties
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
OData Services
192 PUBLIC OData API Reference
3.2.22.5 Marketing Attribute Set (BusinessAttributeSet)
Properties
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
Properties
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
OData Services
OData API Reference PUBLIC 193
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
Properties
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
Properties
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
OData Services
194 PUBLIC OData API Reference
Note
Object Type Code has been removed in the 1711 release and the solution adds the required default value for this
property.
Properties
Max
Lengt
Name Type Nullable h Fixed length Search Relevant
400 Bad Request The server could not understand the request due to malformed
syntax.
403 Forbidden Access to the resource you are trying to connect to is forbid
den. This may be due to either a user authentication failure or
to the user having insufficient privileges to perform the action.
404 Not Found The server cannot find the specified resource. This is typically
due to an unrecognized resource ID (such as userId, groupId,
or contentId).
405 Method Not Allowed The method specified in the Request Line is not allowed for the
resource identified by the Request URI.
OData Services
OData API Reference PUBLIC 195
HTTP SUCCESS CODE DESCRIPTION
429 Too Many Requests The user has sent too many requests in a given period of time.
This error message is typically encountered if API rate limits,
set to protect against DoS attacks and to preserve server re
sponsiveness, have been exceeded. See Rate Limits to view the
established limits.
500 Internal Server Error The server encountered an unexpected condition, which pre
vented it from fulfilling the request.
501 Not Implemented The server does not support the functionality required to fulfill
the request.
Overview
The ServiceAssignment OData service enables the external application or user to perform the following actions:
Properties
OData Services
196 PUBLIC OData API Reference
Name Type Description Search Relevant
1. Fixed Time
2. Fixed Time & Technician
1. Released
<space> - Not Released
X – True
<space> - False
OData Services
OData API Reference PUBLIC 197
Name Type Description Search Relevant
1. Open
2. In Process
3. Completed
4. Canceled
1. Immediate
2. Urgent
3. Normal
4. Low
OData Services
198 PUBLIC OData API Reference
Name Type Description Search Relevant
Navigation
OData Services
OData API Reference PUBLIC 199
3.2.24.1 Business Context and Use
The Service Assignment OData service enables you to connect external applications to your SAP Cloud for
Customer system and to read and query assignment data within your system.
https://<C4C-tenant>/sap/c4c/odata/v1/c4codata/$metadata
Assignment OData Service enables the external application or user to perform the following action:
This topic provides you with property values for the ServiceAssignmentNotes object.
Overview
ServiceAssignmentNotes provides information about the assignment. The text can be viewed, created, and
updated.
Properties
Properties of ServiceAssignmentNotes
OData Services
200 PUBLIC OData API Reference
Name Type Description
AuthorName Edm.String
AuthorUUID Edm.Guid
We have updated our API strategy based on feedback received from customers.
1. The following APIs are deprecated (as of the release August 2018) and will be obsolete as of the release
February 2020.:
• Standard synchronous inbound SOAP web services (A2X)
• SAP Cloud for Customer OData API v1
Note
OData Services
OData API Reference PUBLIC 201
4 OData Service Explorer
This document provides an overview of the OData Editor and how you can use this editor to create OData services.
The OData Service Explorer view in the Administrator work center allows you, as an end user to create, edit, and
manage your OData services.
This view also lists the services that are created by you and the standard OData services offered by SAP. To view the
services created by you, select Custom OData Services from Show.
To view SAP OData Services, select SAP OData Services from Show.
In the Custom OData Services view, you can also download an OData service, by selecting a service and clicking
Download. Additionally you can download services in patches for testing by clicking Patch Download. This
functionality can be used if a patch solution exists in the system. The following table explains the criteria for
Download and Patch Download
Only if an original solution exists in the source system, down The patch solution can be used only if it exists in the source
load the service using theDownload button. system, for all the original solution business objects and fields
of an OData service.
During a download, the fields of the patch solution are replaced During a Patch Download, only the patch solution fields are
with fields of the original solution. downloaded. If there are fields from the original solution, they
are renamed to point to the patch solution.
1. 1.In the SAP Cloud for Customer system, navigate to the Administrator work center, OData Service Explorer
view and select Custom OData Services from Show.
Note
The SAP OData Services are default services that are provided by SAP and can only be viewed but not
edited. You can only edit Custom OData Services.
Note
If this option is selected, the External Keys for the various entities for the service is enabled.
OData Services
202 PUBLIC OData Service Explorer
3. Click New and enter the OData Service Name in the Quick Create dialog box.
4. Click Save and Close to save the service or Save and Open to complete the service or Save and New to save this
service and create a new service. The OData service is set to Inactive after the service has been created.
Note
When you create custom OData services, it is important to ensure that necessary authorizations are enabled
for the services. For more information, see Authorization [page 6].
1. From the OData view, select the OData service that you created and click Edit.
2. Select the Include Code Descriptions and select the checkbox, if you want to add the description of the code list
to your OData service. Enter the Work Center View for users with this work center view to see the OData
service.
Note
The Include Code Descriptions setting applies to the entire OData Service. The Work Center View selection
applies only to this entity.
3. Click Select Business Object and enter the BO Name and BO Node Name . Click OK.
OData Services
OData Service Explorer PUBLIC 203
Note
Standard business objects do not include nodes to create new entity types. However, field extensions are
available.
4. Select the relevant node for the entity from the Entity Types tab.
5. Select the relevant elements that are listed under the node.
Note
The selected nodes elements are automatically populated under the OData Service structure. The entity
has a default property called ObjectID, which is the node ID of the corresponding business object.
Additionally, you can delete an entity type by selecting it and clicking Remove.
Create Associated Entity A create associated entity that cannot be merged with any
other entity and is shown as a separate entity below the host
entity.
OData Services
204 PUBLIC OData Service Explorer
Node Element Description
Merge Association A merge association entity can be merged with the active
entity. However merging entities is optional. If you do not
want to merge the entity, the system automatically creates
an entry below the host entity.
Dependent Object Association A dependent object association creates a new entity that
corresponds to the respective dependent object. The prop
erties under this object cannot be edited. For example, Text
Collection and Attachment Folder .
If you create a new entity using an association, the navigation between the entity and element is added
automatically to both, it is bidirectional. If the association is between cross business objects, the navigation is
not bidirectional.
If you have selected Data Workbench, while creating a service, you can see two additional properties
ExternalKey and ParentExternalKey added to the entity structure.
If you create an entity by clicking the Select Business Object, the navigations are created automatically
between existing entities and the newly created entity.
OData Services
OData Service Explorer PUBLIC 205
6. Enter the following information under the Properties and Navigation Properties respectively:
UI Element Description
Delete Selecting this option would delete the selected entity type.
Name Enter the name of the entity type. This field can be edited
and a new name can be given.
Work Center View Enter the work center or view to which the end user should
have authorization, in order to view the data.
Title Property (Entity) The title can be mapped to the property of an entity that can
be mapped to elements and attributes of an entry or to cus
tom elements of an entry in the feed.
Entity Set Name of the entity set entered in the OData service.
Entity Set Name of entity sets are relevant for fields of type Code. It in
cludes code and description that references the entity type
Codelists
Null Select this option if you want the property to have a null
value.
Name Enter the name of the property. One entity type cannot have
two properties with same name.
Scale Enter the number of digits to the right of the decimal place
for the property value.
OData Services
206 PUBLIC OData Service Explorer
UI Element Description
Default Value Enter the default value of the property. In the case of READ,
only those records that have this default value are returned.
In the case of WRITE , if no value is provided, then this de
fault value is used.
Note
ComplexTypes are no longer supported for a new serv
ice.
Title (Property) Select this option to specify the title property in the entity
type.
Enable Search Include the selected property in the search results. This op
tion is only for $Search.
External Key Scheme Code Select a scheme code for the ExternalKey of the entity. The
list appears based on scoping.
7. Select Add Row from the Function Imports tab and enter the following details. However this step is optional. If
you want to call a BO Action enter the following:
Note
OData Services
OData Service Explorer PUBLIC 207
4.1.2 Result
Once the service is saved successfully, the status of the OData service changes to Active and the Service URL is
generated. This contains the metadata information of the OData service.
The OData Console is available on click of the test button in OData Service Explorer. It lists all the SAP delivered and
custom services available in the respective SAP Cloud for Customer tenant.
Actors / Users
Actors / Users:
• Key Users: Key users are the system administrators who are responsible for managing OData Services.
• Business Users: Business users are the users with assigned roles and perform tasks on certain defined
components.
Key Features
1. Exploring OData Services: This feature lets a user see all the entities that are available in the service and also
presents the properties of the entities in an intuitive way.
2. Testing OData Services: This feature simplifies the process of testing the OData service, wherein the user can
perform HTTP operations like Get, Post without getting into the finer details of syntax or authentication.
An OData service is composed of a number of entity sets (collections), their properties, and associations
(navigation). An association describes the relationship between two entity sets. The user can select a service from
the selection help for the field Service. The list contains all the SAP delivered and custom services available in the
respective SAP Cloud for Customer tenant
When you select an entity set from the list, its properties and associations (if any) are listed under the Entity Details
tab and the Navigation Properties tab respectively.
OData Services
208 PUBLIC OData Service Explorer
The users can see the attributes of the property like type, label etc. An Expand Sign “>” is visible in front of the
Complex Type properties. The composition or sub-properties of the complex type property can be viewed by
clicking the expand icon.
The navigation properties section display all the direct associations of the entity.
You can test the OData services through HTTP requests, for retrieving, adding and updating data for the selected
entity set. You need to select the Entity of a service and then click on the Test tab to begin testing.
OData Services
OData Service Explorer PUBLIC 209
The test tab contains the Request and Response sections and these sections can be expanded and collapsed
1. Get
2. Post
3. Patch
4. Put
5. Delete
The HTTP methods can be selected from the method drop down in the request section. Steps to Execute a Get
Request:
1. Select a Method from the selection help, under the Request section.
2. In the field next to the dropdown, the URL referencing the selected OData service collection is automatically
populated. You can further customize the request with the OData system query options, such as $filter,
$search, and so on by editing the URL.
3. There are three formats in which the user can provide the body or the payload :
1. Form: This tab presents the user with the properties of the entity, the user can fill the values of the
properties in the text boxes in front of the labels.
2. XML: This tab lets the user enter the payload in XML data format.
3. JSON: This tab lets the user enter the payload in JSON format. In the Form tab, enter values for Object ID
according to the properties of the collection and press execute.
You can add headers to the request using the headers tab in the request section. The application fetches an X-
CSRF token automatically when executing OData requests, and it is not necessary to provide this token manually.
The XML and JSON format are ideal for the key users who have created their payloads already or have got them
from some other application. The form format is very useful for business users who just want to casually test and
explore OData services.
OData Services
210 PUBLIC OData Service Explorer
The Form tab in the Request section also supports maintaining Complex Types. As soon as the user clicks in a text
box corresponding to a complex type property, a dialog screen is displayed with all the sub properties for the
complex type property . When you click on OK button, the values that you enter are saved onto the complex type
property .For example: . AccountName Property in Opportunity entity.
Also the Form tab provides the Code List help for the “Code” type properties that can have a set of defined values.
For example: .: Approval Status Code in Opportunity Entity.
OData Services
OData Service Explorer PUBLIC 211
The outcome of the HTTP requests will be displayed in the Request section. The Response can be seen in three
formats as well:
• Data: This presents the user with an excel view of the data. The values of Complex type properties is displayed
in curly braces with a comma. For example: . {USD,200.000000}
• XML: This tab can be used to see the response body in XML format.
• JSON: This tab can used to view the Response in JSON format.
The XML and JSON format and ideal for the key user as they can directly copy and use these payloads in other
applications. The Data format is ideal for they key users as it is very readable for lesser data and can be made sense
of very quickly. The Response sections also gives an option to download data in CSV format which was retrieved as
response from executing a Get Request. Also the user can see the response headers from the headers tab in
Response section.
OData Services
212 PUBLIC OData Service Explorer
As explained above , Other HTTP requests can be executed similarly by providing all the necessary details.
Note
You will find the description of various HTTP methods in the Appendix.
4.2.3 Favorites
To reuse payloads, the payload for a particular request can be saved as a favorite template. In order to do so, you
need to provide a name and a description for the template to be saved. Saved favorites can later be loaded by
selecting under the Favorites tab.
You can easily create favorites by clicking on the Save as Favorite (adjacent to Execute button) in the Test tab. When
you click tthe button, you are prompted to provide the name and description of the favorite; Click on OK to confirm.
OData Services
OData Service Explorer PUBLIC 213
You can also delete the favorites with the help of the Delete Selected and Delete All buttons. The Delete selected
deletes all the selected rows and the Delete All clears all the favorites for the logged in user.
4.2.4 History
The last one hundred unique requests are stored in the history so that they can be accessed and executed again
later. The history entries are accessible under the History tab.
OData Services
214 PUBLIC OData Service Explorer
You can also delete the history with the help of the Delete Selected and Delete All buttons. The Delete Selected
deletes all the selected rows and the Delete All clears all the history rows for the logged in user.
4.2.5 Appendix
Method Description
GET The GET method is used to retrieve using a given URI. Requests
using GET should only retrieve data and should have no other
effect on the data.
OData Services
OData Service Explorer PUBLIC 215
5 OData API Monitor
You can monitor inbound OData calls with OData API Monitor.
Monitor the status of incoming calls and view the request and response payloads. This feature is useful when
troubleshooting different integration scenarios.
Scoping
OData API Monitor is available in your tenant by default. If you want to remove it, you can adjust it in your business
configuration:
Logon to SAP Cloud for Customer and go to Administrator General Settings OData API Monitor and launch.
Once activated, all inbound calls, requests and responses are logged for one hour. You can view the HTTP status
code of incoming calls, time of call, user of call, HTTP method used and the path of the call. You can also select an
entry and view the request and response payload.
You can deactivate the trace and filter results by defining the desired search.
OData Services
216 PUBLIC OData API Monitor
6 (Deprecated) Setting Up OData
Notifications
Configure notifications and inform external systems when there are changes to SAP Cloud for Customer business
objects.
Prerequisites
Note
The feature OData: Event Notification to External Systems is deprecated. Event Notifications is now available. For
more information, see SAP Cloud for Customer > Integration > Event Notifications
You have scoped Event Notification in business configuration. To perform this step, follow these instructions:
Context
This functionality notifies external systems of changes to business objects in SAP Cloud for Customer. Use this
procedure to register your end points and set up authentication details. A typical use for this functionality is to send
a notification to SAP Commerce Cloud when a new employee is created in your C4C system, or to notify custom
applications of changes to business objects.
Procedure
1. If your HTTPS enabled endpoint uses certificates, add certificates used to the solution certificate list. Find this
list under Administrator Common Tasks Edit Certificate Trust List .
Your consumer end points must be in the public domain, must use HTTPS protocol, and must be in front of any
firewalls in your network. Additionally, consumer end points must be running an application that can
OData Services
(Deprecated) Setting Up OData Notifications PUBLIC 217
understand and persist the following four fields: businessObject, businessObjectID, odataServiceEndpoint,
event.
Remember
If the consumer end point is behind a firewall the connection check will fail.
Results
When business objects listed under any of the subscriptions are modified, the external consumer is called
asynchronously.
The external system can call back to your C4C tenant using the URL format: https://
my123456.ondemand.com/sap/byd/odata/v1/c4codata/
AccountCollection('00163E08BFEC1ED785AE497656AAXXXX')
OData Services
218 PUBLIC (Deprecated) Setting Up OData Notifications
7 SAP Cloud for Customer OData Developer's
Guide
The SAP Cloud for Customer OData API Developer’s Guide complements theSAP Cloud for Customer OData API
Reference with usage details and provide examples for easy convenience to developers
For more information, see SAP Cloud for Customer OData Developer’s Guide
OData Services
SAP Cloud for Customer OData Developer's Guide PUBLIC 219
8 Additional Resources
Related Information
OData Services
220 PUBLIC Additional Resources
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.
OData Services
Important Disclaimers and Legal Information PUBLIC 221
www.sap.com/contactsap
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.