public class BusinessPartnerContact extends VdmEntity<BusinessPartnerContact>
Original entity name from the Odata EDM: A_BusinessPartnerContactType
Modifier and Type | Class and Description |
---|---|
static class |
BusinessPartnerContact.BusinessPartnerContactBuilder |
Modifier and Type | Field and Description |
---|---|
static BusinessPartnerContactSelectable |
ALL_FIELDS
Selector for all available fields of BusinessPartnerContact.
|
static BusinessPartnerContactField<String> |
BUSINESS_PARTNER_COMPANY
Use with available fluent helpers to apply the BusinessPartnerCompany field to query operations.
|
static BusinessPartnerContactField<String> |
BUSINESS_PARTNER_PERSON
Use with available fluent helpers to apply the BusinessPartnerPerson field to query operations.
|
static BusinessPartnerContactField<Boolean> |
IS_STANDARD_RELATIONSHIP
Use with available fluent helpers to apply the IsStandardRelationship field to query operations.
|
static BusinessPartnerContactField<String> |
RELATIONSHIP_CATEGORY
Use with available fluent helpers to apply the RelationshipCategory field to query operations.
|
static BusinessPartnerContactField<String> |
RELATIONSHIP_NUMBER
Use with available fluent helpers to apply the RelationshipNumber field to query operations.
|
static BusinessPartnerContactLink<BPContactToAddress> |
TO_CONTACT_ADDRESS
Use with available fluent helpers to apply the to_ContactAddress navigation property to query operations.
|
static BusinessPartnerContactLink<BPContactToFuncAndDept> |
TO_CONTACT_RELATIONSHIP
Use with available fluent helpers to apply the to_ContactRelationship navigation property to query operations.
|
static BusinessPartnerContactField<Calendar> |
VALIDITY_END_DATE
Use with available fluent helpers to apply the ValidityEndDate field to query operations.
|
static BusinessPartnerContactField<Calendar> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
Constructor and Description |
---|
BusinessPartnerContact() |
BusinessPartnerContact(String relationshipNumber,
String businessPartnerCompany,
String businessPartnerPerson,
Calendar validityEndDate,
Calendar validityStartDate,
Boolean isStandardRelationship,
String relationshipCategory,
ErpConfigContext erpConfigContext,
List<BPContactToAddress> toContactAddress,
BPContactToFuncAndDept toContactRelationship) |
Modifier and Type | Method and Description |
---|---|
void |
addContactAddress(BPContactToAddress... entity)
Adds elements to the list of associated BPContactToAddress entities.
|
static BusinessPartnerContact.BusinessPartnerContactBuilder |
builder() |
boolean |
equals(Object o) |
List<BPContactToAddress> |
fetchContactAddress()
Fetches the BPContactToAddress entities (one to many) associated with this entity.
|
BPContactToFuncAndDept |
fetchContactRelationship()
Fetches the BPContactToFuncAndDept entity (one to one) associated with this entity.
|
static <T> BusinessPartnerContactField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getBusinessPartnerCompany()
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BusinessPartnerCompany
|
String |
getBusinessPartnerPerson()
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BusinessPartnerPerson
|
List<BPContactToAddress> |
getContactAddressOrFetch()
Retrieval of associated BPContactToAddress entities (one to many).
|
com.google.common.base.Optional<List<BPContactToAddress>> |
getContactAddressOrNull()
Retrieval of associated BPContactToAddress entities (one to many).
|
BPContactToFuncAndDept |
getContactRelationshipOrFetch()
Retrieval of associated BPContactToFuncAndDept entity (one to one).
|
com.google.common.base.Optional<BPContactToFuncAndDept> |
getContactRelationshipOrNull()
Retrieval of associated BPContactToFuncAndDept entity (one to one).
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
Boolean |
getIsStandardRelationship()
Constraints: noneOriginal property name from the Odata EDM: IsStandardRelationshipIf several relationships of the BP relationship category contact person have been defined for, you can set the indicator standard relationship for one of these relationships.A relationship that is marked as a standard relationship can be used whenA certain scenario automatically selects a contact personThe contact person responsible is not knownYou can give this indicator to only one business partner relationship of a BP relationship category for a particular period.
|
String |
getRelationshipCategory()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: RelationshipCategoryA distinction is made between a one-way and an undirected business partner relationship category.
|
String |
getRelationshipNumber()
(Key Field) Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: RelationshipNumber
|
Class<BusinessPartnerContact> |
getType() |
Calendar |
getValidityEndDate()
(Key Field) Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityEndDate
|
Calendar |
getValidityStartDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityStartDate
|
int |
hashCode() |
void |
setBusinessPartnerCompany(String businessPartnerCompany)
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BusinessPartnerCompany
|
void |
setBusinessPartnerPerson(String businessPartnerPerson)
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BusinessPartnerPerson
|
void |
setContactAddress(List<BPContactToAddress> value)
Overwrites the list of associated BPContactToAddress entities for the loaded navigation property to_ContactAddress.
|
void |
setContactRelationship(BPContactToFuncAndDept value)
Overwrites the associated BPContactToFuncAndDept entity for the loaded navigation property to_ContactRelationship.
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setIsStandardRelationship(Boolean isStandardRelationship)
Constraints: noneOriginal property name from the Odata EDM: IsStandardRelationshipIf several relationships of the BP relationship category contact person have been defined for, you can set the indicator standard relationship for one of these relationships.A relationship that is marked as a standard relationship can be used whenA certain scenario automatically selects a contact personThe contact person responsible is not knownYou can give this indicator to only one business partner relationship of a BP relationship category for a particular period.
|
void |
setRelationshipCategory(String relationshipCategory)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: RelationshipCategoryA distinction is made between a one-way and an undirected business partner relationship category.
|
void |
setRelationshipNumber(String relationshipNumber)
(Key Field) Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: RelationshipNumber
|
void |
setValidityEndDate(Calendar validityEndDate)
(Key Field) Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityEndDate
|
void |
setValidityStartDate(Calendar validityStartDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityStartDate
|
String |
toString() |
getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField
public static final BusinessPartnerContactSelectable ALL_FIELDS
public static final BusinessPartnerContactField<String> RELATIONSHIP_NUMBER
public static final BusinessPartnerContactField<String> BUSINESS_PARTNER_COMPANY
public static final BusinessPartnerContactField<String> BUSINESS_PARTNER_PERSON
public static final BusinessPartnerContactField<Calendar> VALIDITY_END_DATE
public static final BusinessPartnerContactField<Calendar> VALIDITY_START_DATE
public static final BusinessPartnerContactField<Boolean> IS_STANDARD_RELATIONSHIP
public static final BusinessPartnerContactField<String> RELATIONSHIP_CATEGORY
public static final BusinessPartnerContactLink<BPContactToAddress> TO_CONTACT_ADDRESS
public static final BusinessPartnerContactLink<BPContactToFuncAndDept> TO_CONTACT_RELATIONSHIP
public BusinessPartnerContact()
public BusinessPartnerContact(@Nullable String relationshipNumber, @Nullable String businessPartnerCompany, @Nullable String businessPartnerPerson, @Nullable Calendar validityEndDate, @Nullable Calendar validityStartDate, @Nullable Boolean isStandardRelationship, @Nullable String relationshipCategory, @Nullable ErpConfigContext erpConfigContext, List<BPContactToAddress> toContactAddress, @Nullable BPContactToFuncAndDept toContactRelationship)
public Class<BusinessPartnerContact> getType()
getType
in class VdmObject<BusinessPartnerContact>
public void setRelationshipNumber(@Nullable String relationshipNumber)
Original property name from the Odata EDM: RelationshipNumber
relationshipNumber
- The business partner relationship number is an internal number that identifies the business partner relationship set.public void setBusinessPartnerCompany(@Nullable String businessPartnerCompany)
Original property name from the Odata EDM: BusinessPartnerCompany
businessPartnerCompany
- Key identifying a business partner in the SAP system. The key is unique within a client.public void setBusinessPartnerPerson(@Nullable String businessPartnerPerson)
Original property name from the Odata EDM: BusinessPartnerPerson
businessPartnerPerson
- Key identifying a business partner in the SAP system. The key is unique within a client.public void setValidityEndDate(@Nullable Calendar validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
validityEndDate
- Validity Date (Valid To)public void setValidityStartDate(@Nullable Calendar validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
validityStartDate
- Validity Date (Valid From)public void setIsStandardRelationship(@Nullable Boolean isStandardRelationship)
Original property name from the Odata EDM: IsStandardRelationship
If several relationships of the BP relationship category contact person have been defined for, you can set the indicator standard relationship for one of these relationships.A relationship that is marked as a standard relationship can be used whenA certain scenario automatically selects a contact personThe contact person responsible is not knownYou can give this indicator to only one business partner relationship of a BP relationship category for a particular period. Another relationship of the same relationship category can be indicated as the standard relationship only if the periods for the relationship do not overlap or coincide.
isStandardRelationship
- States whether the relationship is a standard relationship.public void setRelationshipCategory(@Nullable String relationshipCategory)
Original property name from the Odata EDM: RelationshipCategory
A distinction is made between a one-way and an undirected business partner relationship category. In a one-way relationship category, the relationship extends from one partner to another, but not vice versa.Marriage (undirected)Employee (one-way)Contact person (one-way)
relationshipCategory
- A relationship may exist between two business partners. The business partner relationship category characterizes the features of the relationship.public static <T> BusinessPartnerContactField<T> field(String fieldName, Class<T> fieldType)
fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.public List<BPContactToAddress> fetchContactAddress() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public List<BPContactToAddress> getContactAddressOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_ContactAddress of a queried BusinessPartnerContact is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public com.google.common.base.Optional<List<BPContactToAddress>> getContactAddressOrNull()
If the navigation property for an entity BusinessPartnerContact has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setContactAddress(@NonNull List<BPContactToAddress> value)
If the navigation property to_ContactAddress of a queried BusinessPartnerContact is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of BPContactToAddress entities.public void addContactAddress(BPContactToAddress... entity)
If the navigation property to_ContactAddress of a queried BusinessPartnerContact is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of BPContactToAddress entities.public BPContactToFuncAndDept fetchContactRelationship() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public BPContactToFuncAndDept getContactRelationshipOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_ContactRelationship of a queried BusinessPartnerContact is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public com.google.common.base.Optional<BPContactToFuncAndDept> getContactRelationshipOrNull()
If the navigation property for an entity BusinessPartnerContact has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setContactRelationship(BPContactToFuncAndDept value)
value
- New BPContactToFuncAndDept entity.public static BusinessPartnerContact.BusinessPartnerContactBuilder builder()
@Nullable public String getRelationshipNumber()
Original property name from the Odata EDM: RelationshipNumber
@Nullable public String getBusinessPartnerCompany()
Original property name from the Odata EDM: BusinessPartnerCompany
@Nullable public String getBusinessPartnerPerson()
Original property name from the Odata EDM: BusinessPartnerPerson
@Nullable public Calendar getValidityEndDate()
Original property name from the Odata EDM: ValidityEndDate
@Nullable public Calendar getValidityStartDate()
Original property name from the Odata EDM: ValidityStartDate
@Nullable public Boolean getIsStandardRelationship()
Original property name from the Odata EDM: IsStandardRelationship
If several relationships of the BP relationship category contact person have been defined for, you can set the indicator standard relationship for one of these relationships.A relationship that is marked as a standard relationship can be used whenA certain scenario automatically selects a contact personThe contact person responsible is not knownYou can give this indicator to only one business partner relationship of a BP relationship category for a particular period. Another relationship of the same relationship category can be indicated as the standard relationship only if the periods for the relationship do not overlap or coincide.
@Nullable public String getRelationshipCategory()
Original property name from the Odata EDM: RelationshipCategory
A distinction is made between a one-way and an undirected business partner relationship category. In a one-way relationship category, the relationship extends from one partner to another, but not vice versa.Marriage (undirected)Employee (one-way)Contact person (one-way)
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext
- public String toString()
toString
in class VdmObject<BusinessPartnerContact>
public boolean equals(Object o)
equals
in class VdmObject<BusinessPartnerContact>
public int hashCode()
hashCode
in class VdmObject<BusinessPartnerContact>
Copyright © 2018 SAP SE. All rights reserved.