A mapper representing custom fields in an entity. Custom fields are represented by their field names and the corresponding values. A custom field can be added or updated using setCustomField method.
The current ETag version of the entity in the remote system. The ETag identified the version of the in the remote system. It will be automatically set in the "if-match" header of update requests and can be set as a custom header for delete requests. When no ETag is provided by the remote system the value of this variable defaults to "*".
Available (Deliverable) Until. Date until which the supplier can supply the material. 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.
Available (Deliverable) From. Date as of which the supplier can supply the material. 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.
Base Unit of Measure. Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure. 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. Maximum length: 3.
Date on Which Record Was Created.
Purchasing info: General data flagged for deletion. Indicates whether the general data of the info record is to be deleted. If the indicator is set, the data will be deleted in the course of the next reorganization run.
Business Purpose Completed. Indicates whether the end of purpose (EoP) has been reached. 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. Maximum length: 1.
Regular Supplier. Specifies that the material is to be procured from this supplier at client level, i.e. for the entire corporate group. 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.
UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun). The UTC timestamp displays date and time according to UTC (Universal Coordinated Time). 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.
Manufacturer. You can enter the name of the manufacturer of the material. This is then adopted in the purchase order and shown in the import data. If the name of a manufacturer has been entered in the material master record, this is pre-set. Maximum length: 10.
Material Number. Alphanumeric key uniquely identifying the material. Maximum length: 40.
Material Group. Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group. You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps. Maximum length: 9.
Number of Days for First Reminder/Expediter. Number of days representing the time interval at which reminders or urging letters/messages (may also be termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier. 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 ( " " " ).
Number of Days for Second Reminder/Expediter. Number of days representing the time interval at which reminders or urging letters/messages (may also be termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier. 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 ( " " " ).
Number of Days for Third Reminder/Expediter. Number of days representing the time interval at which reminders or urging letters/messages (may also be termed "chasers", "hasteners" (UK) or "expediters" (USA)) are to be issued to the supplier. 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 ( " " " ).
Denominator for Conversion of Order Unit to Base Unit. Denominator of the quotient expressing the ratio 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).
Numerator for Conversion of Order Unit to Base Unit. Numerator of the quotient for conversion of the order unit into the base unit. 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.
Prior Supplier. Key that uniquely identifies the prior supplier. 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. Maximum length: 10.
Number of Points. Number of points awarded by the granter of conditions for purchases of this material. 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.
Points unit. Dimension for units of measurement. In this field you can use only units of measurement with the dimension "points". Maximum length: 3.
Number of Purchasing Info Record. Specifies the number that uniquely identifies a purchasing info record. Maximum length: 10.
Short Text for Purchasing Info Record. Text describing a material without a material master record. Maximum length: 40.
Purchase Order Unit of Measure. Specifies the unit of measure in which the material is ordered. Maximum length: 3.
The remote state of the entity. Remote state refers to the last known state of the entity on the remote system from which it has been retrieved or to which it has been posted. It is stored as map, where the keys are stored in the format of VDM properties.
Vendor Account Number. Alphanumeric key uniquely identifying the document. 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. Maximum length: 10.
Supplier Material Group. Material group to which the material at the supplier belongs. Maximum length: 18.
Material Number Used by Supplier. Material number used by the supplier. 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. Maximum length: 35.
Supplier's Telephone Number. This entry is for information only. It is not copied into purchasing documents. Maximum length: 16.
Salesperson Responsible in the Event of Queries. This entry is for information only. It is not copied into purchasing documents. Maximum length: 30.
Supplier Subrange. Subdivision of a supplier's overall product range according to various criteria. 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. Maximum length: 6.
Sort Sequence Number. Number by which the materials in a supplier sub-range are sorted. 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. Maximum length: 5.
One-to-many navigation property to the PurgInfoRecdOrgPlantData entity.
Variable Purchase Order Unit Active. Activation of the variable purchase order unit. 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. Maximum length: 1.
ETag version identifier accessor.
All fields selector.
Static representation of the availabilityEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the availabilityStartDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the baseUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the creationDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isDeleted property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isEndOfPurposeBlocked property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isRegularSupplier property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the lastChangeDateTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the manufacturer property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the material property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the materialGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the noDaysReminder1 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the noDaysReminder2 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the noDaysReminder3 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the orderItemQtyToBaseQtyDnmntr property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the orderItemQtyToBaseQtyNmrtr property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the priorSupplier property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the productPurchasePointsQty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the productPurchasePointsQtyUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purchasingInfoRecord property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purchasingInfoRecordDesc property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purgDocOrderQuantityUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the supplier property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the supplierMaterialGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the supplierMaterialNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the supplierPhoneNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the supplierRespSalesPersonName property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the supplierSubrange property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the supplierSubrangeSortNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the one-to-many navigation property toPurgInfoRecdOrgPlantData for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the varblPurOrdUnitIsActive property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the PurchasingInfoRecord entity.
Default url path for the according service.
Technical entity name for PurchasingInfoRecord.
All key fields of the PurchasingInfoRecord entity.
Mapping of all key field names to the respective static field property PurchasingInfoRecord.
Returns a map of all defined fields in entity to their current values.
Entity with all defined entity fields
Custom field value getter.
The name of the custom field
The value of the corresponding custom field
Returns a map that contains all entity custom fields.
A map of all defined custom fields in the entity
Returns all updated custom field properties compared to the last known remote state.
A map containing all updated custom properties, with their new values
Returns all changed properties compared to the last known remote state. The returned properties does not include custom fields. Use getUpdatedCustomFields, if updated custom fields are needed.
Entity with all properties that changed
Validates whether a custom field exists in the entity.
The name of the custom field to update
A boolean value, that indicates whether a custom field is defined in entity
Sets all retrieved custom fields in entity.
Extracted custom fields from a retrieved entity
A boolean value, that indicates the existence of the field in entity
Validates whether a field name does not conflict with an original field name and thus can be defined as custom fields.
Field name to check
Boolean value that describes whether a field name can be defined as custom field
Sets a new custom field in the entity or updates it. Throws an error, if the provided custom field name is already defined by an original field in entity.
The name of the custom field to update
The value of the field
The entity itself, to facilitate method chaining
Initializes or sets the remoteState of the entity. This function is called on all read, create and update requests. This function should be called after initializeCustomFields, if custom fields are defined.
State to be set as remote state
The entity itself, to facilitate method chaining
Set the ETag version identifier of the retrieved entity.
The returned ETag version of the entity
The entity itself, to facilitate method chaining
Overwrites the default toJSON method so that all instance variables as well as all custom fields of the entity are returned.
An object containing all instance variables + custom fields.
Returns an entity builder to construct instances PurchasingInfoRecord.
A builder that constructs instances of entity type PurchasingInfoRecord.
Returns a selectable object that allows the selection of custom field in a get request for the entity PurchasingInfoRecord.
Name of the custom field to select
A builder that constructs instances of entity type PurchasingInfoRecord.
Returns a request builder to construct requests for operations on the PurchasingInfoRecord entity type.
A PurchasingInfoRecord request builder.
This class represents the entity "A_PurchasingInfoRecord" of service "API_INFORECORD_PROCESS_SRV". This service is part of the following communication scenarios: Purchasing Info Record Integration (SAP_COM_0145). See https://api.sap.com/api/API_INFORECORD_PROCESS_SRV for more information.