public static final class PurchasingInfoRecord.PurchasingInfoRecordBuilder extends Object
@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder purgInfoRecdOrgPlantData(PurgInfoRecdOrgPlantData... value)
value - The PurgInfoRecdOrgPlantDatas to build this PurchasingInfoRecord with.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder purchasingInfoRecord(@Nullable String purchasingInfoRecord)
Original property name from the Odata EDM: PurchasingInfoRecord
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder supplier(@Nullable String supplier)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder materialGroup(@Nullable String materialGroup)
Original property name from the Odata EDM: MaterialGroup
You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder isDeleted(@Nullable Boolean isDeleted)
Original property name from the Odata EDM: IsDeleted
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder purchasingInfoRecordDesc(@Nullable String purchasingInfoRecordDesc)
Original property name from the Odata EDM: PurchasingInfoRecordDesc
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder purgDocOrderQuantityUnit(@Nullable String purgDocOrderQuantityUnit)
Original property name from the Odata EDM: PurgDocOrderQuantityUnit
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder orderItemQtyToBaseQtyNmrtr(@Nullable BigDecimal orderItemQtyToBaseQtyNmrtr)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder orderItemQtyToBaseQtyDnmntr(@Nullable BigDecimal orderItemQtyToBaseQtyDnmntr)
Original property name from the Odata EDM: 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).
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder supplierMaterialNumber(@Nullable String supplierMaterialNumber)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder supplierRespSalesPersonName(@Nullable String supplierRespSalesPersonName)
Original property name from the Odata EDM: SupplierRespSalesPersonName
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder supplierPhoneNumber(@Nullable String supplierPhoneNumber)
Original property name from the Odata EDM: SupplierPhoneNumber
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder baseUnit(@Nullable String baseUnit)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder supplierMaterialGroup(@Nullable String supplierMaterialGroup)
Original property name from the Odata EDM: SupplierMaterialGroup
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder priorSupplier(@Nullable String priorSupplier)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder availabilityStartDate(@Nullable LocalDateTime availabilityStartDate)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder availabilityEndDate(@Nullable LocalDateTime availabilityEndDate)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder varblPurOrdUnitIsActive(@Nullable String varblPurOrdUnitIsActive)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder manufacturer(@Nullable String manufacturer)
Original property name from the Odata EDM: Manufacturer
If the name of a manufacturer has been entered in the material master record, this is pre-set.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder isRegularSupplier(@Nullable Boolean isRegularSupplier)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder supplierSubrange(@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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder noDaysReminder1(@Nullable BigDecimal noDaysReminder1)
Original property name from the Odata EDM: 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 ( " " " ).
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder noDaysReminder2(@Nullable BigDecimal noDaysReminder2)
Original property name from the Odata EDM: 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 ( " " " ).
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder noDaysReminder3(@Nullable BigDecimal noDaysReminder3)
Original property name from the Odata EDM: 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 ( " " " ).
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder productPurchasePointsQty(@Nullable BigDecimal productPurchasePointsQty)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder productPurchasePointsQtyUnit(@Nullable String productPurchasePointsQtyUnit)
Original property name from the Odata EDM: ProductPurchasePointsQtyUnit
In this field you can use only units of measurement with the dimension "points".
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder supplierSubrangeSortNumber(@Nullable String supplierSubrangeSortNumber)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder lastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: 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.
this.@Nonnull public PurchasingInfoRecord.PurchasingInfoRecordBuilder isEndOfPurposeBlocked(@Nullable String isEndOfPurposeBlocked)
Original property name from the Odata EDM: 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
this.@Nonnull public PurchasingInfoRecord build()
Copyright © 2021 SAP SE. All rights reserved.