public class SupplierPartnerFunc extends VdmEntity<SupplierPartnerFunc>
Original entity name from the Odata EDM: A_SupplierPartnerFuncType
Modifier and Type | Class and Description |
---|---|
static class |
SupplierPartnerFunc.SupplierPartnerFuncBuilder |
Modifier and Type | Field and Description |
---|---|
static SupplierPartnerFuncSelectable |
ALL_FIELDS
Selector for all available fields of SupplierPartnerFunc.
|
static SupplierPartnerFuncField<String> |
AUTHORIZATION_GROUP
Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
|
static SupplierPartnerFuncField<String> |
CREATED_BY_USER
Use with available fluent helpers to apply the CreatedByUser field to query operations.
|
static SupplierPartnerFuncField<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static SupplierPartnerFuncField<Boolean> |
DEFAULT_PARTNER
Use with available fluent helpers to apply the DefaultPartner field to query operations.
|
static SupplierPartnerFuncField<String> |
PARTNER_COUNTER
Use with available fluent helpers to apply the PartnerCounter field to query operations.
|
static SupplierPartnerFuncField<String> |
PARTNER_FUNCTION
Use with available fluent helpers to apply the PartnerFunction field to query operations.
|
static SupplierPartnerFuncField<String> |
PLANT
Use with available fluent helpers to apply the Plant field to query operations.
|
static SupplierPartnerFuncField<String> |
PURCHASING_ORGANIZATION
Use with available fluent helpers to apply the PurchasingOrganization field to query operations.
|
static SupplierPartnerFuncField<String> |
REFERENCE_SUPPLIER
Use with available fluent helpers to apply the ReferenceSupplier field to query operations.
|
static SupplierPartnerFuncField<String> |
SUPPLIER
Use with available fluent helpers to apply the Supplier field to query operations.
|
static SupplierPartnerFuncField<String> |
SUPPLIER_SUBRANGE
Use with available fluent helpers to apply the SupplierSubrange field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
SupplierPartnerFunc() |
SupplierPartnerFunc(String supplier,
String purchasingOrganization,
String supplierSubrange,
String plant,
String partnerFunction,
String partnerCounter,
Boolean defaultPartner,
LocalDateTime creationDate,
String createdByUser,
String referenceSupplier,
String authorizationGroup,
ErpConfigContext erpConfigContext) |
Modifier and Type | Method and Description |
---|---|
static SupplierPartnerFunc.SupplierPartnerFuncBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> SupplierPartnerFuncField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getAuthorizationGroup()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: AuthorizationGroup
|
String |
getCreatedByUser()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CreatedByUser
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CreationDate
|
Boolean |
getDefaultPartner()
Constraints: noneOriginal property name from the Odata EDM: DefaultPartnerWhen you enter more than one partner for a particular partner function (for example, you define three different ship-to parties), you can select one partner as the default.
|
protected String |
getEndpointUrl() |
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
protected Map<String,Object> |
getKey() |
String |
getPartnerCounter()
(Key Field) Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PartnerCounterWhen you create a sales order for a particular customer, there may be more than one ship-to party defined.
|
String |
getPartnerFunction()
(Key Field) Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: PartnerFunction
|
String |
getPlant()
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: Plant
|
String |
getPurchasingOrganization()
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PurchasingOrganization
|
String |
getReferenceSupplier()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ReferenceSupplier
|
String |
getSupplier()
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Supplier
|
String |
getSupplierSubrange()
(Key Field) Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SupplierSubrangeFor each supplier sub-range:The master data is kept on a common basisCertain conditions applyIn the supplier master, you can create different purchasing data and different partner functions for each supplier sub-range.You can also maintain and change the conditions for each supplier sub-range.
|
Class<SupplierPartnerFunc> |
getType() |
int |
hashCode() |
void |
setAuthorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: AuthorizationGroup
|
void |
setCreatedByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CreatedByUser
|
void |
setCreationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CreationDate
|
void |
setDefaultPartner(Boolean defaultPartner)
Constraints: noneOriginal property name from the Odata EDM: DefaultPartnerWhen you enter more than one partner for a particular partner function (for example, you define three different ship-to parties), you can select one partner as the default.
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setPartnerCounter(String partnerCounter)
(Key Field) Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PartnerCounterWhen you create a sales order for a particular customer, there may be more than one ship-to party defined.
|
void |
setPartnerFunction(String partnerFunction)
(Key Field) Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: PartnerFunction
|
void |
setPlant(String plant)
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: Plant
|
void |
setPurchasingOrganization(String purchasingOrganization)
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PurchasingOrganization
|
void |
setReferenceSupplier(String referenceSupplier)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ReferenceSupplier
|
void |
setSupplier(String supplier)
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Supplier
|
void |
setSupplierSubrange(String supplierSubrange)
(Key Field) Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SupplierSubrangeFor each supplier sub-range:The master data is kept on a common basisCertain conditions applyIn the supplier master, you can create different purchasing data and different partner functions for each supplier sub-range.You can also maintain and change the conditions for each supplier sub-range.
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final SupplierPartnerFuncSelectable ALL_FIELDS
public static final SupplierPartnerFuncField<String> SUPPLIER
public static final SupplierPartnerFuncField<String> PURCHASING_ORGANIZATION
public static final SupplierPartnerFuncField<String> SUPPLIER_SUBRANGE
public static final SupplierPartnerFuncField<String> PLANT
public static final SupplierPartnerFuncField<String> PARTNER_FUNCTION
public static final SupplierPartnerFuncField<String> PARTNER_COUNTER
public static final SupplierPartnerFuncField<Boolean> DEFAULT_PARTNER
public static final SupplierPartnerFuncField<LocalDateTime> CREATION_DATE
public static final SupplierPartnerFuncField<String> CREATED_BY_USER
public static final SupplierPartnerFuncField<String> REFERENCE_SUPPLIER
public static final SupplierPartnerFuncField<String> AUTHORIZATION_GROUP
public SupplierPartnerFunc()
public SupplierPartnerFunc(@Nullable String supplier, @Nullable String purchasingOrganization, @Nullable String supplierSubrange, @Nullable String plant, @Nullable String partnerFunction, @Nullable String partnerCounter, @Nullable Boolean defaultPartner, @Nullable LocalDateTime creationDate, @Nullable String createdByUser, @Nullable String referenceSupplier, @Nullable String authorizationGroup, @Nullable ErpConfigContext erpConfigContext)
public Class<SupplierPartnerFunc> getType()
getType
in class VdmObject<SupplierPartnerFunc>
public void setSupplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
supplier
- Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.public void setPurchasingOrganization(@Nullable String purchasingOrganization)
Original property name from the Odata EDM: PurchasingOrganization
purchasingOrganization
- Denotes the purchasing organization.public void setSupplierSubrange(@Nullable String supplierSubrange)
Original property name from the Odata EDM: SupplierSubrange
For each supplier sub-range:The master data is kept on a common basisCertain conditions applyIn the supplier master, you can create different purchasing data and different partner functions for each supplier sub-range.You can also maintain and change the conditions for each supplier sub-range. You assign a material to a supplier sub-range in the info record.In the supplier master, you can maintain different data for particular supplier sub-ranges, such as ordering addresses or terms of payment, for example.When creating a purchase order with a known supplier, different data is only determined if the supplier sub-range is entered in the initial screen.Your supplier Smith in Houston has two sub-ranges: paint and glue.All materials from the "paint" sub-range are ordered in Houston.You have maintained an alternative ordering address in Detroit for the "glue" sub-range.If you order materials from the "glue" sub-range, the supplier sub-range finds the Detroit ordering address.
supplierSubrange
- Subdivision of a supplier's overall product range according to various criteria.public void setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
plant
- Key uniquely identifying a plant.public void setPartnerFunction(@Nullable String partnerFunction)
Original property name from the Odata EDM: PartnerFunction
partnerFunction
- The abbreviated form of the name that identifies the partner function.public void setPartnerCounter(@Nullable String partnerCounter)
Original property name from the Odata EDM: PartnerCounter
When you create a sales order for a particular customer, there may be more than one ship-to party defined. The different ship-to parties are numbered sequentially.
partnerCounter
- The sequential number that the system applies when there is more than one partner for a particular partner function.public void setDefaultPartner(@Nullable Boolean defaultPartner)
Original property name from the Odata EDM: DefaultPartner
When you enter more than one partner for a particular partner function (for example, you define three different ship-to parties), you can select one partner as the default. During sales or purchasing processing, if you have defined multiple partners for a partner function, the system prompts you to choose just one partner. The system presents the default partner as the first choice in the pop-up window.
defaultPartner
- Specifies a partner as the default for a particular partner function.public void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate
- Date on Which Record Was Createdpublic void setCreatedByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
createdByUser
- Name of Person Who Created Objectpublic void setReferenceSupplier(@Nullable String referenceSupplier)
Original property name from the Odata EDM: ReferenceSupplier
referenceSupplier
- Reference to other vendorpublic void setAuthorizationGroup(@Nullable String authorizationGroup)
Original property name from the Odata EDM: AuthorizationGroup
authorizationGroup
- The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.protected String getEndpointUrl()
getEndpointUrl
in class VdmEntity<SupplierPartnerFunc>
protected String getEntityCollection()
getEntityCollection
in class VdmEntity<SupplierPartnerFunc>
protected Map<String,Object> getKey()
getKey
in class VdmObject<SupplierPartnerFunc>
protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<SupplierPartnerFunc>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<SupplierPartnerFunc>
public static <T> SupplierPartnerFuncField<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 static SupplierPartnerFunc.SupplierPartnerFuncBuilder builder()
@Nullable public String getSupplier()
Original property name from the Odata EDM: Supplier
@Nullable public String getPurchasingOrganization()
Original property name from the Odata EDM: PurchasingOrganization
@Nullable public String getSupplierSubrange()
Original property name from the Odata EDM: SupplierSubrange
For each supplier sub-range:The master data is kept on a common basisCertain conditions applyIn the supplier master, you can create different purchasing data and different partner functions for each supplier sub-range.You can also maintain and change the conditions for each supplier sub-range. You assign a material to a supplier sub-range in the info record.In the supplier master, you can maintain different data for particular supplier sub-ranges, such as ordering addresses or terms of payment, for example.When creating a purchase order with a known supplier, different data is only determined if the supplier sub-range is entered in the initial screen.Your supplier Smith in Houston has two sub-ranges: paint and glue.All materials from the "paint" sub-range are ordered in Houston.You have maintained an alternative ordering address in Detroit for the "glue" sub-range.If you order materials from the "glue" sub-range, the supplier sub-range finds the Detroit ordering address.
@Nullable public String getPlant()
Original property name from the Odata EDM: Plant
@Nullable public String getPartnerFunction()
Original property name from the Odata EDM: PartnerFunction
@Nullable public String getPartnerCounter()
Original property name from the Odata EDM: PartnerCounter
When you create a sales order for a particular customer, there may be more than one ship-to party defined. The different ship-to parties are numbered sequentially.
@Nullable public Boolean getDefaultPartner()
Original property name from the Odata EDM: DefaultPartner
When you enter more than one partner for a particular partner function (for example, you define three different ship-to parties), you can select one partner as the default. During sales or purchasing processing, if you have defined multiple partners for a partner function, the system prompts you to choose just one partner. The system presents the default partner as the first choice in the pop-up window.
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public String getCreatedByUser()
Original property name from the Odata EDM: CreatedByUser
@Nullable public String getReferenceSupplier()
Original property name from the Odata EDM: ReferenceSupplier
@Nullable public String getAuthorizationGroup()
Original property name from the Odata EDM: AuthorizationGroup
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<SupplierPartnerFunc>
erpConfigContext
- public String toString()
toString
in class VdmObject<SupplierPartnerFunc>
public boolean equals(Object o)
equals
in class VdmObject<SupplierPartnerFunc>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<SupplierPartnerFunc>
public int hashCode()
hashCode
in class VdmObject<SupplierPartnerFunc>
Copyright © 2018 SAP SE. All rights reserved.