public class PurchasingInfoRecord extends VdmEntity<PurchasingInfoRecord>
| Modifier and Type | Class and Description |
|---|---|
static class |
PurchasingInfoRecord.PurchasingInfoRecordBuilder |
| Modifier and Type | Field and Description |
|---|---|
static PurchasingInfoRecordSelectable |
ALL_FIELDS
Selector for all available fields of PurchasingInfoRecord.
|
static PurchasingInfoRecordField<Calendar> |
AVAILABILITY_END_DATE
Use with available fluent helpers to apply the AvailabilityEndDate field to query operations.
|
static PurchasingInfoRecordField<Calendar> |
AVAILABILITY_START_DATE
Use with available fluent helpers to apply the AvailabilityStartDate field to query operations.
|
static PurchasingInfoRecordField<String> |
BASE_UNIT
Use with available fluent helpers to apply the BaseUnit field to query operations.
|
static PurchasingInfoRecordField<Calendar> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static PurchasingInfoRecordField<Boolean> |
IS_DELETED
Use with available fluent helpers to apply the IsDeleted field to query operations.
|
static PurchasingInfoRecordField<String> |
IS_END_OF_PURPOSE_BLOCKED
Use with available fluent helpers to apply the IsEndOfPurposeBlocked field to query operations.
|
static PurchasingInfoRecordField<Boolean> |
IS_REGULAR_SUPPLIER
Use with available fluent helpers to apply the IsRegularSupplier field to query operations.
|
static PurchasingInfoRecordField<Calendar> |
LAST_CHANGE_DATE_TIME
Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
|
static PurchasingInfoRecordField<String> |
MANUFACTURER
Use with available fluent helpers to apply the Manufacturer field to query operations.
|
static PurchasingInfoRecordField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static PurchasingInfoRecordField<String> |
MATERIAL_GROUP
Use with available fluent helpers to apply the MaterialGroup field to query operations.
|
static PurchasingInfoRecordField<BigDecimal> |
NO_DAYS_REMINDER1
Use with available fluent helpers to apply the NoDaysReminder1 field to query operations.
|
static PurchasingInfoRecordField<BigDecimal> |
NO_DAYS_REMINDER2
Use with available fluent helpers to apply the NoDaysReminder2 field to query operations.
|
static PurchasingInfoRecordField<BigDecimal> |
NO_DAYS_REMINDER3
Use with available fluent helpers to apply the NoDaysReminder3 field to query operations.
|
static PurchasingInfoRecordField<BigDecimal> |
ORDER_ITEM_QTY_TO_BASE_QTY_DNMNTR
Use with available fluent helpers to apply the OrderItemQtyToBaseQtyDnmntr field to query operations.
|
static PurchasingInfoRecordField<BigDecimal> |
ORDER_ITEM_QTY_TO_BASE_QTY_NMRTR
Use with available fluent helpers to apply the OrderItemQtyToBaseQtyNmrtr field to query operations.
|
static PurchasingInfoRecordField<String> |
PRIOR_SUPPLIER
Use with available fluent helpers to apply the PriorSupplier field to query operations.
|
static PurchasingInfoRecordField<BigDecimal> |
PRODUCT_PURCHASE_POINTS_QTY
Use with available fluent helpers to apply the ProductPurchasePointsQty field to query operations.
|
static PurchasingInfoRecordField<String> |
PRODUCT_PURCHASE_POINTS_QTY_UNIT
Use with available fluent helpers to apply the ProductPurchasePointsQtyUnit field to query operations.
|
static PurchasingInfoRecordField<String> |
PURCHASING_INFO_RECORD
Use with available fluent helpers to apply the PurchasingInfoRecord field to query operations.
|
static PurchasingInfoRecordField<String> |
PURCHASING_INFO_RECORD_DESC
Use with available fluent helpers to apply the PurchasingInfoRecordDesc field to query operations.
|
static PurchasingInfoRecordField<String> |
PURG_DOC_ORDER_QUANTITY_UNIT
Use with available fluent helpers to apply the PurgDocOrderQuantityUnit field to query operations.
|
static PurchasingInfoRecordField<String> |
SUPPLIER
Use with available fluent helpers to apply the Supplier field to query operations.
|
static PurchasingInfoRecordField<String> |
SUPPLIER_MATERIAL_GROUP
Use with available fluent helpers to apply the SupplierMaterialGroup field to query operations.
|
static PurchasingInfoRecordField<String> |
SUPPLIER_MATERIAL_NUMBER
Use with available fluent helpers to apply the SupplierMaterialNumber field to query operations.
|
static PurchasingInfoRecordField<String> |
SUPPLIER_PHONE_NUMBER
Use with available fluent helpers to apply the SupplierPhoneNumber field to query operations.
|
static PurchasingInfoRecordField<String> |
SUPPLIER_RESP_SALES_PERSON_NAME
Use with available fluent helpers to apply the SupplierRespSalesPersonName field to query operations.
|
static PurchasingInfoRecordField<String> |
SUPPLIER_SUBRANGE
Use with available fluent helpers to apply the SupplierSubrange field to query operations.
|
static PurchasingInfoRecordField<String> |
SUPPLIER_SUBRANGE_SORT_NUMBER
Use with available fluent helpers to apply the SupplierSubrangeSortNumber field to query operations.
|
static PurchasingInfoRecordLink<PurgInfoRecdOrgPlantData> |
TO_PURG_INFO_RECD_ORG_PLANT_DATA
Use with available fluent helpers to apply the to_PurgInfoRecdOrgPlantData navigation property to query operations.
|
static PurchasingInfoRecordField<String> |
VARBL_PUR_ORD_UNIT_IS_ACTIVE
Use with available fluent helpers to apply the VarblPurOrdUnitIsActive field to query operations.
|
| Constructor and Description |
|---|
PurchasingInfoRecord() |
PurchasingInfoRecord(String purchasingInfoRecord,
String supplier,
String material,
String materialGroup,
Calendar creationDate,
Boolean isDeleted,
String purchasingInfoRecordDesc,
String purgDocOrderQuantityUnit,
BigDecimal orderItemQtyToBaseQtyNmrtr,
BigDecimal orderItemQtyToBaseQtyDnmntr,
String supplierMaterialNumber,
String supplierRespSalesPersonName,
String supplierPhoneNumber,
String baseUnit,
String supplierMaterialGroup,
String priorSupplier,
Calendar availabilityStartDate,
Calendar availabilityEndDate,
String varblPurOrdUnitIsActive,
String manufacturer,
Boolean isRegularSupplier,
String supplierSubrange,
BigDecimal noDaysReminder1,
BigDecimal noDaysReminder2,
BigDecimal noDaysReminder3,
BigDecimal productPurchasePointsQty,
String productPurchasePointsQtyUnit,
String supplierSubrangeSortNumber,
Calendar lastChangeDateTime,
String isEndOfPurposeBlocked,
ErpConfigContext erpConfigContext,
List<PurgInfoRecdOrgPlantData> toPurgInfoRecdOrgPlantData) |
| Modifier and Type | Method and Description |
|---|---|
void |
addPurgInfoRecdOrgPlantData(PurgInfoRecdOrgPlantData... entity)
Adds elements to the list of associated PurgInfoRecdOrgPlantData entities.
|
static PurchasingInfoRecord.PurchasingInfoRecordBuilder |
builder() |
boolean |
equals(Object o) |
List<PurgInfoRecdOrgPlantData> |
fetchPurgInfoRecdOrgPlantData()
Fetches the PurgInfoRecdOrgPlantData entities (one to many) associated with this entity.
|
static <T> PurchasingInfoRecordField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
Calendar |
getAvailabilityEndDate()
Constraints: Not nullable, Precision: 0 Together with the field "Available from", this field delimits the period in which the supplier supplies the material, e.g. antifreeze from 10.01 to 03.31.The system checks whether the delivery date entered in the purchasing document falls within this period.
|
Calendar |
getAvailabilityStartDate()
Constraints: Not nullable, Precision: 0 Together with the field "Available to", this field delimits the period in which the supplier supplies the material, e.g. antifreeze from 10.01 to 03.31.The system checks whether the delivery date entered in the purchasing document falls within this period.
|
String |
getBaseUnit()
Constraints: Not nullable, Maximum length: 3 You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure.
|
Calendar |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
Boolean |
getIsDeleted()
Constraints: none
|
String |
getIsEndOfPurposeBlocked()
Constraints: Not nullable, Maximum length: 1 The EoP is the point in time for a data set when the processing of personal data is no longer required for the primary business purpose.
|
Boolean |
getIsRegularSupplier()
Constraints: noneIf you set this indicator, the regular supplier is suggested as the only source.If you wish to work with the source determination facility for purchasing documents, it makes sense not to set the indicator so that the system suggests all available sources, not just the regular supplier.If you try to enter a different supplier than the regular supplier in the source list or quota arrangement the system will issue a warning message.
|
Calendar |
getLastChangeDateTime()
Constraints: Not nullable, Precision: 7 In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone.
|
String |
getManufacturer()
Constraints: Not nullable, Maximum length: 10 If the name of a manufacturer has been entered in the material master record, this is pre-set.
|
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9 You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
|
BigDecimal |
getNoDaysReminder1()
Constraints: Not nullable, Precision: 3, Scale: 0 A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
|
BigDecimal |
getNoDaysReminder2()
Constraints: Not nullable, Precision: 3, Scale: 0 A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
|
BigDecimal |
getNoDaysReminder3()
Constraints: Not nullable, Precision: 3, Scale: 0 A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
|
BigDecimal |
getOrderItemQtyToBaseQtyDnmntr()
Constraints: Not nullable, Precision: 5, Scale: 0 base unit : order unit.To convert a quantity, whose unit of measure is not the same as the base unit of measure, into the base unit of measure, the system requires a quotient:Quantity (in alternative unit of measure) = quotient * quantity (in base unit of measure)Enter the number of units of the alternative unit of measure (denominator) that corresponds to the number of units of the base unit of measure (numerator).The alternative unit of measure is kilogram (kg).
|
BigDecimal |
getOrderItemQtyToBaseQtyNmrtr()
Constraints: Not nullable, Precision: 5, Scale: 0 If the order unit is kilogram, and the base unit is piece, and if one kilogram equals 4 pieces, the conversion factor is:4 KG (numerator) --> 1 PC (denominator).NoteYou can only enter whole numbers in the numerator and denominator fields.
|
String |
getPriorSupplier()
Constraints: Not nullable, Maximum length: 10 You can negotiate conditions with the prior supplier.
|
BigDecimal |
getProductPurchasePointsQty()
Constraints: Not nullable, Precision: 13, Scale: 3 Here you enter the number of points awarded by the supplier for purchases of this material.If, for the purposes of subsequent settlement with regard to conditions, you work with a points system instead of using business volume figures or percentages, the amount due according to conditions requiring subsequent (end-of-period) settlement is calculated on the basis of the total points awarded for the purchases of the material over the period in question.A points system allows the materials supplied by a supplier to be weighted independently of their price.Example:Material "Steel 1" costs $100 per ton from supplier ACME, whereas material "Steel 2" costs $5 per ton.
|
String |
getProductPurchasePointsQtyUnit()
Constraints: Not nullable, Maximum length: 3 In this field you can use only units of measurement with the dimension "points".
|
String |
getPurchasingInfoRecord()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getPurchasingInfoRecordDesc()
Constraints: Not nullable, Maximum length: 40
|
String |
getPurgDocOrderQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
List<PurgInfoRecdOrgPlantData> |
getPurgInfoRecdOrgPlantDataOrFetch()
Retrieval of associated PurgInfoRecdOrgPlantData entities (one to many).
|
com.google.common.base.Optional<List<PurgInfoRecdOrgPlantData>> |
getPurgInfoRecdOrgPlantDataOrNull()
Retrieval of associated PurgInfoRecdOrgPlantData entities (one to many).
|
String |
getSupplier()
Constraints: Not nullable, Maximum length: 10 With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.
|
String |
getSupplierMaterialGroup()
Constraints: Not nullable, Maximum length: 18
|
String |
getSupplierMaterialNumber()
Constraints: Not nullable, Maximum length: 35 In most cases, the supplier uses a different number for the material than the one used in this system.
|
String |
getSupplierPhoneNumber()
Constraints: Not nullable, Maximum length: 16
|
String |
getSupplierRespSalesPersonName()
Constraints: Not nullable, Maximum length: 30
|
String |
getSupplierSubrange()
Constraints: Not nullable, Maximum length: 6 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.
|
String |
getSupplierSubrangeSortNumber()
Constraints: Not nullable, Maximum length: 5 The sort number is used in the PO as a default value for the order item number.
|
Class<PurchasingInfoRecord> |
getType() |
String |
getVarblPurOrdUnitIsActive()
Constraints: Not nullable, Maximum length: 1 The information from the field in the material master record is adopted in the purchasing info record.
|
int |
hashCode() |
void |
setAvailabilityEndDate(Calendar availabilityEndDate)
Constraints: Not nullable, Precision: 0 Together with the field "Available from", this field delimits the period in which the supplier supplies the material, e.g. antifreeze from 10.01 to 03.31.The system checks whether the delivery date entered in the purchasing document falls within this period.
|
void |
setAvailabilityStartDate(Calendar availabilityStartDate)
Constraints: Not nullable, Precision: 0 Together with the field "Available to", this field delimits the period in which the supplier supplies the material, e.g. antifreeze from 10.01 to 03.31.The system checks whether the delivery date entered in the purchasing document falls within this period.
|
void |
setBaseUnit(String baseUnit)
Constraints: Not nullable, Maximum length: 3 You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure.
|
void |
setCreationDate(Calendar creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setIsDeleted(Boolean isDeleted)
Constraints: none
|
void |
setIsEndOfPurposeBlocked(String isEndOfPurposeBlocked)
Constraints: Not nullable, Maximum length: 1 The EoP is the point in time for a data set when the processing of personal data is no longer required for the primary business purpose.
|
void |
setIsRegularSupplier(Boolean isRegularSupplier)
Constraints: noneIf you set this indicator, the regular supplier is suggested as the only source.If you wish to work with the source determination facility for purchasing documents, it makes sense not to set the indicator so that the system suggests all available sources, not just the regular supplier.If you try to enter a different supplier than the regular supplier in the source list or quota arrangement the system will issue a warning message.
|
void |
setLastChangeDateTime(Calendar lastChangeDateTime)
Constraints: Not nullable, Precision: 7 In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone.
|
void |
setManufacturer(String manufacturer)
Constraints: Not nullable, Maximum length: 10 If the name of a manufacturer has been entered in the material master record, this is pre-set.
|
void |
setMaterial(String material)
Constraints: Not nullable, Maximum length: 40
|
void |
setMaterialGroup(String materialGroup)
Constraints: Not nullable, Maximum length: 9 You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
|
void |
setNoDaysReminder1(BigDecimal noDaysReminder1)
Constraints: Not nullable, Precision: 3, Scale: 0 A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
|
void |
setNoDaysReminder2(BigDecimal noDaysReminder2)
Constraints: Not nullable, Precision: 3, Scale: 0 A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
|
void |
setNoDaysReminder3(BigDecimal noDaysReminder3)
Constraints: Not nullable, Precision: 3, Scale: 0 A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
|
void |
setOrderItemQtyToBaseQtyDnmntr(BigDecimal orderItemQtyToBaseQtyDnmntr)
Constraints: Not nullable, Precision: 5, Scale: 0 base unit : order unit.To convert a quantity, whose unit of measure is not the same as the base unit of measure, into the base unit of measure, the system requires a quotient:Quantity (in alternative unit of measure) = quotient * quantity (in base unit of measure)Enter the number of units of the alternative unit of measure (denominator) that corresponds to the number of units of the base unit of measure (numerator).The alternative unit of measure is kilogram (kg).
|
void |
setOrderItemQtyToBaseQtyNmrtr(BigDecimal orderItemQtyToBaseQtyNmrtr)
Constraints: Not nullable, Precision: 5, Scale: 0 If the order unit is kilogram, and the base unit is piece, and if one kilogram equals 4 pieces, the conversion factor is:4 KG (numerator) --> 1 PC (denominator).NoteYou can only enter whole numbers in the numerator and denominator fields.
|
void |
setPriorSupplier(String priorSupplier)
Constraints: Not nullable, Maximum length: 10 You can negotiate conditions with the prior supplier.
|
void |
setProductPurchasePointsQty(BigDecimal productPurchasePointsQty)
Constraints: Not nullable, Precision: 13, Scale: 3 Here you enter the number of points awarded by the supplier for purchases of this material.If, for the purposes of subsequent settlement with regard to conditions, you work with a points system instead of using business volume figures or percentages, the amount due according to conditions requiring subsequent (end-of-period) settlement is calculated on the basis of the total points awarded for the purchases of the material over the period in question.A points system allows the materials supplied by a supplier to be weighted independently of their price.Example:Material "Steel 1" costs $100 per ton from supplier ACME, whereas material "Steel 2" costs $5 per ton.
|
void |
setProductPurchasePointsQtyUnit(String productPurchasePointsQtyUnit)
Constraints: Not nullable, Maximum length: 3 In this field you can use only units of measurement with the dimension "points".
|
void |
setPurchasingInfoRecord(String purchasingInfoRecord)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setPurchasingInfoRecordDesc(String purchasingInfoRecordDesc)
Constraints: Not nullable, Maximum length: 40
|
void |
setPurgDocOrderQuantityUnit(String purgDocOrderQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setPurgInfoRecdOrgPlantData(List<PurgInfoRecdOrgPlantData> value)
Overwrites the list of associated PurgInfoRecdOrgPlantData entities for the loaded navigation property to_PurgInfoRecdOrgPlantData.
|
void |
setSupplier(String supplier)
Constraints: Not nullable, Maximum length: 10 With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.
|
void |
setSupplierMaterialGroup(String supplierMaterialGroup)
Constraints: Not nullable, Maximum length: 18
|
void |
setSupplierMaterialNumber(String supplierMaterialNumber)
Constraints: Not nullable, Maximum length: 35 In most cases, the supplier uses a different number for the material than the one used in this system.
|
void |
setSupplierPhoneNumber(String supplierPhoneNumber)
Constraints: Not nullable, Maximum length: 16
|
void |
setSupplierRespSalesPersonName(String supplierRespSalesPersonName)
Constraints: Not nullable, Maximum length: 30
|
void |
setSupplierSubrange(String supplierSubrange)
Constraints: Not nullable, Maximum length: 6 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.
|
void |
setSupplierSubrangeSortNumber(String supplierSubrangeSortNumber)
Constraints: Not nullable, Maximum length: 5 The sort number is used in the PO as a default value for the order item number.
|
void |
setVarblPurOrdUnitIsActive(String varblPurOrdUnitIsActive)
Constraints: Not nullable, Maximum length: 1 The information from the field in the material master record is adopted in the purchasing info record.
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomFieldpublic static final PurchasingInfoRecordSelectable ALL_FIELDS
public static final PurchasingInfoRecordField<String> PURCHASING_INFO_RECORD
public static final PurchasingInfoRecordField<String> SUPPLIER
public static final PurchasingInfoRecordField<String> MATERIAL
public static final PurchasingInfoRecordField<String> MATERIAL_GROUP
public static final PurchasingInfoRecordField<Calendar> CREATION_DATE
public static final PurchasingInfoRecordField<Boolean> IS_DELETED
public static final PurchasingInfoRecordField<String> PURCHASING_INFO_RECORD_DESC
public static final PurchasingInfoRecordField<String> PURG_DOC_ORDER_QUANTITY_UNIT
public static final PurchasingInfoRecordField<BigDecimal> ORDER_ITEM_QTY_TO_BASE_QTY_NMRTR
public static final PurchasingInfoRecordField<BigDecimal> ORDER_ITEM_QTY_TO_BASE_QTY_DNMNTR
public static final PurchasingInfoRecordField<String> SUPPLIER_MATERIAL_NUMBER
public static final PurchasingInfoRecordField<String> SUPPLIER_RESP_SALES_PERSON_NAME
public static final PurchasingInfoRecordField<String> SUPPLIER_PHONE_NUMBER
public static final PurchasingInfoRecordField<String> BASE_UNIT
public static final PurchasingInfoRecordField<String> SUPPLIER_MATERIAL_GROUP
public static final PurchasingInfoRecordField<String> PRIOR_SUPPLIER
public static final PurchasingInfoRecordField<Calendar> AVAILABILITY_START_DATE
public static final PurchasingInfoRecordField<Calendar> AVAILABILITY_END_DATE
public static final PurchasingInfoRecordField<String> VARBL_PUR_ORD_UNIT_IS_ACTIVE
public static final PurchasingInfoRecordField<String> MANUFACTURER
public static final PurchasingInfoRecordField<Boolean> IS_REGULAR_SUPPLIER
public static final PurchasingInfoRecordField<String> SUPPLIER_SUBRANGE
public static final PurchasingInfoRecordField<BigDecimal> NO_DAYS_REMINDER1
public static final PurchasingInfoRecordField<BigDecimal> NO_DAYS_REMINDER2
public static final PurchasingInfoRecordField<BigDecimal> NO_DAYS_REMINDER3
public static final PurchasingInfoRecordField<BigDecimal> PRODUCT_PURCHASE_POINTS_QTY
public static final PurchasingInfoRecordField<String> PRODUCT_PURCHASE_POINTS_QTY_UNIT
public static final PurchasingInfoRecordField<String> SUPPLIER_SUBRANGE_SORT_NUMBER
public static final PurchasingInfoRecordField<Calendar> LAST_CHANGE_DATE_TIME
public static final PurchasingInfoRecordField<String> IS_END_OF_PURPOSE_BLOCKED
public static final PurchasingInfoRecordLink<PurgInfoRecdOrgPlantData> TO_PURG_INFO_RECD_ORG_PLANT_DATA
public PurchasingInfoRecord()
public PurchasingInfoRecord(@Nullable String purchasingInfoRecord, @Nullable String supplier, @Nullable String material, @Nullable String materialGroup, @Nullable Calendar creationDate, @Nullable Boolean isDeleted, @Nullable String purchasingInfoRecordDesc, @Nullable String purgDocOrderQuantityUnit, @Nullable BigDecimal orderItemQtyToBaseQtyNmrtr, @Nullable BigDecimal orderItemQtyToBaseQtyDnmntr, @Nullable String supplierMaterialNumber, @Nullable String supplierRespSalesPersonName, @Nullable String supplierPhoneNumber, @Nullable String baseUnit, @Nullable String supplierMaterialGroup, @Nullable String priorSupplier, @Nullable Calendar availabilityStartDate, @Nullable Calendar availabilityEndDate, @Nullable String varblPurOrdUnitIsActive, @Nullable String manufacturer, @Nullable Boolean isRegularSupplier, @Nullable String supplierSubrange, @Nullable BigDecimal noDaysReminder1, @Nullable BigDecimal noDaysReminder2, @Nullable BigDecimal noDaysReminder3, @Nullable BigDecimal productPurchasePointsQty, @Nullable String productPurchasePointsQtyUnit, @Nullable String supplierSubrangeSortNumber, @Nullable Calendar lastChangeDateTime, @Nullable String isEndOfPurposeBlocked, @Nullable ErpConfigContext erpConfigContext, List<PurgInfoRecdOrgPlantData> toPurgInfoRecdOrgPlantData)
public Class<PurchasingInfoRecord> getType()
getType in class VdmObject<PurchasingInfoRecord>public static <T> PurchasingInfoRecordField<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<PurgInfoRecdOrgPlantData> fetchPurgInfoRecdOrgPlantData() 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<PurgInfoRecdOrgPlantData> getPurgInfoRecdOrgPlantDataOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PurgInfoRecdOrgPlantData of a queried PurchasingInfoRecord 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<PurgInfoRecdOrgPlantData>> getPurgInfoRecdOrgPlantDataOrNull()
If the navigation property to_PurgInfoRecdOrgPlantData for an entity PurchasingInfoRecord has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setPurgInfoRecdOrgPlantData(@NonNull
List<PurgInfoRecdOrgPlantData> value)
If the navigation property to_PurgInfoRecdOrgPlantData of a queried PurchasingInfoRecord 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 PurgInfoRecdOrgPlantData entities.public void addPurgInfoRecdOrgPlantData(PurgInfoRecdOrgPlantData... entity)
If the navigation property to_PurgInfoRecdOrgPlantData of a queried PurchasingInfoRecord 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 PurgInfoRecdOrgPlantData entities.public static PurchasingInfoRecord.PurchasingInfoRecordBuilder builder()
@Nullable public String getPurchasingInfoRecord()
@Nullable public String getSupplier()
With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.
@Nullable public String getMaterial()
@Nullable public String getMaterialGroup()
You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
@Nullable public Calendar getCreationDate()
@Nullable public Boolean getIsDeleted()
@Nullable public String getPurchasingInfoRecordDesc()
@Nullable public String getPurgDocOrderQuantityUnit()
@Nullable public BigDecimal getOrderItemQtyToBaseQtyNmrtr()
If the order unit is kilogram, and the base unit is piece, and if one kilogram equals 4 pieces, the conversion factor is:4 KG (numerator) --> 1 PC (denominator).NoteYou can only enter whole numbers in the numerator and denominator fields. That is to say, if 3.14 m2 equals one piece, you must enter whole number multiples thereof (314 m2 = 100 pc). The quotient is thus 100/314, the numerator 100, and the denominator 314.
@Nullable public BigDecimal getOrderItemQtyToBaseQtyDnmntr()
base unit : order unit.To convert a quantity, whose unit of measure is not the same as the base unit of measure, into the base unit of measure, the system requires a quotient:Quantity (in alternative unit of measure) = quotient * quantity (in base unit of measure)Enter the number of units of the alternative unit of measure (denominator) that corresponds to the number of units of the base unit of measure (numerator).The alternative unit of measure is kilogram (kg). The base unit of measure is piece (PC). 5 kg correspond to 3 pieces.5 kg = 3 PC => 1 kg = 3/5 PCIn this case, the quotient is therefore 3/5 (the numerator being 3 and the denominator 5).You may enter only whole numbers in the numerator and denominator fields; that is, if 3.14 m² correspond to one piece, you must enter integer multiples (314 m² = 100 PC). In this case, the quotient is therefore 100/314 (the numerator being 100 and the denominator 314).
@Nullable public String getSupplierMaterialNumber()
In most cases, the supplier uses a different number for the material than the one used in this system. The supplier's material number can therefore also be quoted in a purchase order for identification purposes.
@Nullable public String getSupplierRespSalesPersonName()
@Nullable public String getSupplierPhoneNumber()
@Nullable public String getBaseUnit()
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
@Nullable public String getSupplierMaterialGroup()
@Nullable public String getPriorSupplier()
You can negotiate conditions with the prior supplier. If the price determination process is then set up appropriately in Customizing for Purchasing, the system will apply these conditions in determining the price in purchase orders.If you are creating the info record for a manufacturer part number, the manufacturer is inserted.
@Nullable public Calendar getAvailabilityStartDate()
Together with the field "Available to", this field delimits the period in which the supplier supplies the material, e.g. antifreeze from 10.01 to 03.31.The system checks whether the delivery date entered in the purchasing document falls within this period. If not, you will receive a warning message or an error message.If you make use of this field, you do not have to maintain numerous source list entries.
@Nullable public Calendar getAvailabilityEndDate()
Together with the field "Available from", this field delimits the period in which the supplier supplies the material, e.g. antifreeze from 10.01 to 03.31.The system checks whether the delivery date entered in the purchasing document falls within this period. If not, you will receive a warning message or an error message.If you make use of this field, you do not need to maintain numerous source list entries.
@Nullable public String getVarblPurOrdUnitIsActive()
The information from the field in the material master record is adopted in the purchasing info record. In the purchase order and in the source list, you can enter an order unit that differs from the one in the purchasing info record.If you wish to specify a different order unit for a requisition, you must assign a source with a different order unit to the requisition.The field also determines whether you work with conditions for each order unit.
@Nullable public String getManufacturer()
If the name of a manufacturer has been entered in the material master record, this is pre-set.
@Nullable public Boolean getIsRegularSupplier()
If you set this indicator, the regular supplier is suggested as the only source.If you wish to work with the source determination facility for purchasing documents, it makes sense not to set the indicator so that the system suggests all available sources, not just the regular supplier.If you try to enter a different supplier than the regular supplier in the source list or quota arrangement the system will issue a warning message.
@Nullable public String getSupplierSubrange()
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 BigDecimal getNoDaysReminder1()
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
@Nullable public BigDecimal getNoDaysReminder2()
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
@Nullable public BigDecimal getNoDaysReminder3()
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
@Nullable public BigDecimal getProductPurchasePointsQty()
Here you enter the number of points awarded by the supplier for purchases of this material.If, for the purposes of subsequent settlement with regard to conditions, you work with a points system instead of using business volume figures or percentages, the amount due according to conditions requiring subsequent (end-of-period) settlement is calculated on the basis of the total points awarded for the purchases of the material over the period in question.A points system allows the materials supplied by a supplier to be weighted independently of their price.Example:Material "Steel 1" costs $100 per ton from supplier ACME, whereas material "Steel 2" costs $5 per ton. Supplier ACME grants a rebate of 3% on the total business volume at the end of the year if materials worth at least 100,000 points were ordered from him during the course of the year. In the case of material "Steel 1", you are awarded 10 points for every ton ordered, whereas you get 20 points for each ton "Steel 2" ordered.When issuing your purchase orders, you can take into account how many tons of "Steel 1" or "Steel 2" you need to order to reach a total of 100,000 points and thus qualify for a retrospective volume rebate.
@Nullable public String getProductPurchasePointsQtyUnit()
In this field you can use only units of measurement with the dimension "points".
@Nullable public String getSupplierSubrangeSortNumber()
The sort number is used in the PO as a default value for the order item number. This enables purchase orders to be created with the items in the sequence which the supplier expects.
@Nullable public Calendar getLastChangeDateTime()
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
@Nullable public String getIsEndOfPurposeBlocked()
The EoP is the point in time for a data set when the processing of personal data is no longer required for the primary business purpose. After the EoP has been reached, the data is blocked and can only be accessed by users with special authorization
@Nullable public ErpConfigContext getErpConfigContext()
public void setPurchasingInfoRecord(@Nullable String purchasingInfoRecord)
purchasingInfoRecord - public void setSupplier(@Nullable String supplier)
With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.
supplier - public void setMaterial(@Nullable String material)
material - public void setMaterialGroup(@Nullable String materialGroup)
You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
materialGroup - public void setCreationDate(@Nullable Calendar creationDate)
creationDate - public void setIsDeleted(@Nullable Boolean isDeleted)
isDeleted - public void setPurchasingInfoRecordDesc(@Nullable String purchasingInfoRecordDesc)
purchasingInfoRecordDesc - public void setPurgDocOrderQuantityUnit(@Nullable String purgDocOrderQuantityUnit)
purgDocOrderQuantityUnit - public void setOrderItemQtyToBaseQtyNmrtr(@Nullable BigDecimal orderItemQtyToBaseQtyNmrtr)
If the order unit is kilogram, and the base unit is piece, and if one kilogram equals 4 pieces, the conversion factor is:4 KG (numerator) --> 1 PC (denominator).NoteYou can only enter whole numbers in the numerator and denominator fields. That is to say, if 3.14 m2 equals one piece, you must enter whole number multiples thereof (314 m2 = 100 pc). The quotient is thus 100/314, the numerator 100, and the denominator 314.
orderItemQtyToBaseQtyNmrtr - public void setOrderItemQtyToBaseQtyDnmntr(@Nullable BigDecimal orderItemQtyToBaseQtyDnmntr)
base unit : order unit.To convert a quantity, whose unit of measure is not the same as the base unit of measure, into the base unit of measure, the system requires a quotient:Quantity (in alternative unit of measure) = quotient * quantity (in base unit of measure)Enter the number of units of the alternative unit of measure (denominator) that corresponds to the number of units of the base unit of measure (numerator).The alternative unit of measure is kilogram (kg). The base unit of measure is piece (PC). 5 kg correspond to 3 pieces.5 kg = 3 PC => 1 kg = 3/5 PCIn this case, the quotient is therefore 3/5 (the numerator being 3 and the denominator 5).You may enter only whole numbers in the numerator and denominator fields; that is, if 3.14 m² correspond to one piece, you must enter integer multiples (314 m² = 100 PC). In this case, the quotient is therefore 100/314 (the numerator being 100 and the denominator 314).
orderItemQtyToBaseQtyDnmntr - public void setSupplierMaterialNumber(@Nullable String supplierMaterialNumber)
In most cases, the supplier uses a different number for the material than the one used in this system. The supplier's material number can therefore also be quoted in a purchase order for identification purposes.
supplierMaterialNumber - public void setSupplierRespSalesPersonName(@Nullable String supplierRespSalesPersonName)
supplierRespSalesPersonName - public void setSupplierPhoneNumber(@Nullable String supplierPhoneNumber)
supplierPhoneNumber - public void setBaseUnit(@Nullable String baseUnit)
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
baseUnit - public void setSupplierMaterialGroup(@Nullable String supplierMaterialGroup)
supplierMaterialGroup - public void setPriorSupplier(@Nullable String priorSupplier)
You can negotiate conditions with the prior supplier. If the price determination process is then set up appropriately in Customizing for Purchasing, the system will apply these conditions in determining the price in purchase orders.If you are creating the info record for a manufacturer part number, the manufacturer is inserted.
priorSupplier - public void setAvailabilityStartDate(@Nullable Calendar availabilityStartDate)
Together with the field "Available to", this field delimits the period in which the supplier supplies the material, e.g. antifreeze from 10.01 to 03.31.The system checks whether the delivery date entered in the purchasing document falls within this period. If not, you will receive a warning message or an error message.If you make use of this field, you do not have to maintain numerous source list entries.
availabilityStartDate - public void setAvailabilityEndDate(@Nullable Calendar availabilityEndDate)
Together with the field "Available from", this field delimits the period in which the supplier supplies the material, e.g. antifreeze from 10.01 to 03.31.The system checks whether the delivery date entered in the purchasing document falls within this period. If not, you will receive a warning message or an error message.If you make use of this field, you do not need to maintain numerous source list entries.
availabilityEndDate - public void setVarblPurOrdUnitIsActive(@Nullable String varblPurOrdUnitIsActive)
The information from the field in the material master record is adopted in the purchasing info record. In the purchase order and in the source list, you can enter an order unit that differs from the one in the purchasing info record.If you wish to specify a different order unit for a requisition, you must assign a source with a different order unit to the requisition.The field also determines whether you work with conditions for each order unit.
varblPurOrdUnitIsActive - public void setManufacturer(@Nullable String manufacturer)
If the name of a manufacturer has been entered in the material master record, this is pre-set.
manufacturer - public void setIsRegularSupplier(@Nullable Boolean isRegularSupplier)
If you set this indicator, the regular supplier is suggested as the only source.If you wish to work with the source determination facility for purchasing documents, it makes sense not to set the indicator so that the system suggests all available sources, not just the regular supplier.If you try to enter a different supplier than the regular supplier in the source list or quota arrangement the system will issue a warning message.
isRegularSupplier - public void setSupplierSubrange(@Nullable String 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 - public void setNoDaysReminder1(@Nullable BigDecimal noDaysReminder1)
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
noDaysReminder1 - public void setNoDaysReminder2(@Nullable BigDecimal noDaysReminder2)
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
noDaysReminder2 - public void setNoDaysReminder3(@Nullable BigDecimal noDaysReminder3)
A negative number of days means that a reminder is to be issued to the supplier n days prior to a certain date (for example, the delivery date or the deadline for submission of quotations).A positive number of days means that a letter or message urging delivery or submission of a quotation etc. is to be issued n days after the due date.In the case of purchasing documents, the time intervals are defaulted from the purchasing info record or, if one does not exist, from the material master record.The basis for the reminder intervals is the delivery date or deadline for submission of quotations etc.In the event of several reminder levels, the days must be set out in ascending order of time, without gaps.In the event of a delay in delivery, you can send messages urging the supplier to deliver ordered materials a total of three times, at intervals of 10 days:Reminder 1: 10 days (after delivery date)Reminder 2: 20 days ( " " " )Reminder 3: 30 days ( " " " ).
noDaysReminder3 - public void setProductPurchasePointsQty(@Nullable BigDecimal productPurchasePointsQty)
Here you enter the number of points awarded by the supplier for purchases of this material.If, for the purposes of subsequent settlement with regard to conditions, you work with a points system instead of using business volume figures or percentages, the amount due according to conditions requiring subsequent (end-of-period) settlement is calculated on the basis of the total points awarded for the purchases of the material over the period in question.A points system allows the materials supplied by a supplier to be weighted independently of their price.Example:Material "Steel 1" costs $100 per ton from supplier ACME, whereas material "Steel 2" costs $5 per ton. Supplier ACME grants a rebate of 3% on the total business volume at the end of the year if materials worth at least 100,000 points were ordered from him during the course of the year. In the case of material "Steel 1", you are awarded 10 points for every ton ordered, whereas you get 20 points for each ton "Steel 2" ordered.When issuing your purchase orders, you can take into account how many tons of "Steel 1" or "Steel 2" you need to order to reach a total of 100,000 points and thus qualify for a retrospective volume rebate.
productPurchasePointsQty - public void setProductPurchasePointsQtyUnit(@Nullable String productPurchasePointsQtyUnit)
In this field you can use only units of measurement with the dimension "points".
productPurchasePointsQtyUnit - public void setSupplierSubrangeSortNumber(@Nullable String supplierSubrangeSortNumber)
The sort number is used in the PO as a default value for the order item number. This enables purchase orders to be created with the items in the sequence which the supplier expects.
supplierSubrangeSortNumber - public void setLastChangeDateTime(@Nullable Calendar lastChangeDateTime)
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
lastChangeDateTime - public void setIsEndOfPurposeBlocked(@Nullable String isEndOfPurposeBlocked)
The EoP is the point in time for a data set when the processing of personal data is no longer required for the primary business purpose. After the EoP has been reached, the data is blocked and can only be accessed by users with special authorization
isEndOfPurposeBlocked - public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - public String toString()
toString in class VdmObject<PurchasingInfoRecord>public boolean equals(Object o)
equals in class VdmObject<PurchasingInfoRecord>public int hashCode()
hashCode in class VdmObject<PurchasingInfoRecord>Copyright © 2018 SAP SE. All rights reserved.