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 "*".
Account Assignment Category. Specifies whether accounting for an item is to be effected via an auxiliary account (such as a cost center). The account assignment category determines which account assignment data (such as cost center, account number and so on) is necessary for the item. Maximum length: 1.
Company Code. The company code is an organizational unit within financial accounting. Maximum length: 4.
No Transmission of Cumulative Quantities in SA Release. Defines whether cumulative quantities are sent in scheduling agreement (SA) releases when SAP APO is used. Setting this flag for a scheduling agreement item has the following consequences:When a scheduling agreement release is created in SAP APO, no cumulative quantities are sent to the vendor for this item on release.No agreed cumulative quantity is calculated in the Set/Reset Agreed Cumulative Quantities and Reconciliation Date function (transaction ME88).No vendor cumulative quantity is expected in an advanced shipping notification item that is related to the scheduling agreement item.On creation of an inbound delivery, no cumulative quantity is calculated for items that are related to the scheduling agreement item.No Cumulative Quantity Imbalance Alert is raised in Inventory Collaboration Hub (ICH) for an inbound delivery item that is related to the scheduling agreement item.You can define whether or not cumulative quantities are sent in the SA release, regardless of the control type that you have chosen.This flag is transferred to SAP APO and is displayed there in the master data.
Currency Key. Currency key for amounts in the system. Maximum length: 5.
Evaluated Receipt Settlement (ERS). Specifies that evaluated receipt settlement (ERS) or the automatic generation of invoices according to an invoicing plan is to be possible in relation to materials supplied or services performed (respectively) with regard to this supplier or this document item. If you wish to settle up with regard to PO or scheduling agreement items involving this supplier using Evaluated Receipt Settlement (ERS), this indicator must be set.This indicator must also be set if you wish to work with purchase orders used in conjunction with invoicing plans when procuring external services.
Firm/Trade-Off Zones Binding with Regard to Mat. Planning. Specifies whether or not the schedule lines lying within the firm and trade-off zones can be changed during the planning run. Maximum length: 1.
Goods Receipt Indicator. Specifies whether the item involves a goods receipt. DependenciesIn the processing of production and process orders, the indicator specifies whether a goods receipt is allowed and expected for the order item.If the indicator is set, the order item is relevant to inventory management. The indicator is set during the creation of the order if the order is settled in respect of a material or a sales order item.
Goods Receipt, Non-Valuated. Specifies that the goods receipt for this item is not to be valuated. Set the indicator if goods receipts involving this material are not to be valuated. The valuation of the purchase order item will then take place at the time of invoice verification.NoteIf the indicator has been set for an item with the material type non- valuated, the quantity recorded in Inventory Management can differ from the value in Financial Accounting during the period between goods receipt and invoice receipt, since the value is not updated until the invoice is posted in Financial Accounting.
Incoterms (Part 1). Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC). Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example. Maximum length: 3.
Incoterms (Part 2). Additional information for the primary Incoterm. If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston"). Maximum length: 28.
Invoice Receipt Indicator. Specifies whether an invoice receipt is linked to the purchase order item. If the indicator is not set, the goods are to be delivered free of charge.
Indicator: GR-Based Invoice Verification. Indicator specifying that provision has been made for goods-receipt-based invoice verification for a purchase order item or invoice item.
Indicator: Action at Registration. This indicator is usually set by MRP controllers. It indicates that the MRP controller would like to be notifies when inbound deliveries for this item are registered in the goods receipt office. This indicator is transferred to method FUNCTION_AFTER_REGISTRATION of BADI BORGR_REGISTRATION during registration and can be used to trigger actions (for example, Workflow, e-mail to the MRP controller). Maximum length: 1.
Indicator: Update Info Record. Determines whether: The purchasing info record for this supplier and material is to refer to this PO item, andThe item is to be valid for the entire purchasing organization or just for the plant.The indicator determines which prices and conditions are suggested in future PO items.Prices and conditions can apply to an entire purchasing organization or to a single plant within a purchasing organization.For example, if you create a purchase order for a plant for which an info record has been defined at plant level, the purchase order is based on the conditions in the plant info record and not on the conditions that apply to the purchasing organization.Enter the relevant plant key:AUpdating of the document number is effected at plant level as long as there is a purchasing info record at plant level. Otherwise the document number is updated at purchasing organization level.BUpdating is effected at plant level if plant conditions are allowed for the plant.CUpdating is effected without plant data if plant conditions are not necessary for the plant.The level at which updating of the document number may be effected is defined for each plant. Maximum length: 1.
Order Acknowledgment Requirement. Determines whether the purchasing document (purchase order, outline purchase agreement, etc.) is to be acknowledged by the supplier.
Indicator: Item Relevant to JIT Delivery Schedules. Determines whether it is possible to generate JIT delivery schedules in addition to forecast schedules for a material specified in a purchase scheduling agreement. Maximum length: 1.
Last Transmission. Date on which the schedule for the item was last transmitted.
Net Weight. Net weight of item per unit of weight. The weight is expressed in terms of the unit of measure you specify in the field "unit of weight".
Manual address number in purchasing document item. Maximum length: 10.
Material Number. Uniquely identifies a material. This field is also used for MPN materials. Maximum length: 40.
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.
Material Type. Key that assigns the material to a group of materials such as raw materials, operating supplies or trading goods. The material type defines certain attributes of the material and has important control functions. Maximum length: 4.
Minimum Remaining Shelf Life. Minimum amount of time for which the material must keep upon goods receipt for the goods receipt to be accepted by the system. The period (day, week, month, year) depends on the entry in the Period indicator field.
Net Price in Purchasing Document (in Document Currency). Net price per price unit.
Price Unit.
Next Forecast Delivery Schedule Transmission. Date on which the next forecast delivery schedule is to be transmitted to the supplier. This date is taken into account in the process of automatic release (delivery schedule) generation. If the indicator is set to "With next creation date", only those scheduling agreement items with respect to which the creation date is earlier than the current date are chosen for release generation.
Next JIT Delivery Schedule Transmission. Date on which the next JIT delivery schedule is to be transmitted to the supplier. This date is taken into account in the process of automatic release (delivery schedule) generation. If the indicator is set to "With next creation date", only those scheduling agreement items with respect to which the creation date is earlier than the current date are chosen for release generation.
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 Conv. of Order Price Unit into Order Unit. Denominator of the quotient representing the ratio order unit: purchase order price unit.Enter the quantity in the order unit that applies for the quantity in the purchase order price unit.You want to order 200 l of a liquid. However, the supplier sells the liquid by the kilogram. 1 kg of this liquid corresponds to 4 l.As conversion factor, enter:Order quantity/order unit Order price qty./order price unit4 l --> 1 kg.
Order Price Unit (Purchasing). Indicates the unit of measurement to which the purchase order price relates. Invoices are created using price units and purchase order price units which constitute the basis for value postings.They can be stored in the purchasing info record.A material or commodity (for example, oil) can be ordered by the liter, but the supplier's invoice shows a price of 2 dollars per kilogram.You enter 10 l as the order quantity and order unit, but specify 2 dollars per kg as purchase order price and purchase order price unit.In addition, you enter the conversion factor "order unit -> purchase order price unit" (for example 2 l per 1 kg) in the "details" data of the purchase order item. Maximum length: 3.
Numerator for Conversion of Order Price Unit into Order Unit. Numerator of the quotient representing the ratio order unit : purchase order price unit. Enter the quantity in the PO price unit that applies for the quantity in the order unit.You want to order 200 l of a liquid. However, the supplier sells the liquid by the kilogram. 1 kg of this liquid corresponds to 4 l.As conversion factor, enter:Order quantity/order unit Order price qty./order price unit4 l --> 1 kg.
Purchase Order Unit of Measure. Specifies the unit of measure in which the material is ordered. Maximum length: 3.
Overdelivery Tolerance. Percentage (based on the order quantity) up to which an overdelivery of this item will be accepted. If you have set the indicator in the Partial delivery/Item field to 'D' (partial delivery allowed), this takes priority. It makes no sense to define a tolerance limit for overdelivery in such case.
Plant. Specifies the key for a production facility or branch office within the company (that is, the company code). You use the plant key to determine, for instance, which plant is to receive ordered goods. Maximum length: 4.
Price Printout. Determines whether or not the price is to be included in the purchase order printout.
Product Type Group. Superordinate term that covers products that can be procured, for example materials and services. In the product type group you choose to either procure a material (by entering blank or 1) or a service (by entering 2).The procurement process is different for materials and services. For example, you can only maintain the field Service Performer when you purchase a service.If you enter a material number in a purchase order item, the product type group is derived automatically from the material type. In this case you can no longer maintain the product type group in the purchase order manually. If you do not enter a material number, you can maintain the field manually.This functionality is available for the following item categories:- Standard- Third-Party. Maximum length: 2.
Purchase Requisition Number. Alphanumeric key uniquely identifying the document. Maximum length: 10.
Item Number of Purchase Requisition. Specifies the number that uniquely identifies an item in . Maximum length: 5.
Purchasing Document Category. Allows a distinction to be made between the various purchasing documents. Maximum length: 1.
Deletion Indicator in Purchasing Document. Determines whether the item in the purchasing document is deleted or blocked. You can set the deletion indicator by choosing Edit -> Delete if:You want to cancel an itemAn item is closed and can be archivedYou can set the blocking indicator by selecting the item and then choosing Edit -> Block if you do not want to allow subsequent functions for the item. Note that you must manually remove the indicator as soon as subsequent functions are allowed again.You have entered a purchase order item by mistake. You cancel it by setting the deletion indicator.A purchase order item has been delivered, invoiced, and paid for, and can now be archived. You can set the deletion indicator. Maximum length: 1.
Short Text. Short description of the material. Maximum length: 40.
Number of Purchasing Info Record. Specifies the number that uniquely identifies a purchasing info record. Maximum length: 10.
Indicator: Estimated Price. Indicates that this net price is merely an estimated price. If you do not know the exact net price of a material, you can indicate that the price is an estimated price. In consequence, a greater price variance is tolerated during invoice verification than would be the case in the event of an exact net price.
Order Acknowledgment Number. Number of the supplier's order acknowledgment. If you work exclusively with order acknowledgments and the supplier sends you one, enter an identifier defined within your firm (e.g. number assigned to incoming mail or date of receipt).NoteIf you work with several confirmation categories and a confirmation control key, you enter the confirmation data in the confirmation overview. This field is then for information only. Maximum length: 20.
Certificate Type. Defines the content of a quality certificate. In procurement, you can use the certificate type to control a number of functions that have been defined for the processing of certificate receipts. The certificate type is specified in the QM data of the material for this purpose.The entry of a certificate type in the Quality Management view of the material only takes effect if you also set the indicator for QM in procurement. Maximum length: 4.
Control Key for Quality Management in Procurement. This key determines which conditions are valid for quality management in procurement. If you activate the indicator for QM in procurement in the material master record at the client level, you must also store a control key at the plant level for quality management in procurement.Depending on the control indicators in the control key, you may have to maintain additional data. Maximum length: 8.
Number of delivery address. Maximum length: 10.
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.
Requirement Tracking Number. Number that facilitates the monitoring of the procurement of required materials or services. This number can relate to a requisition note (or requirement notice/slip) that was not generated in the system. The requirement tracking number from the purchase requisition is copied to the purchasing documents (for example: RFQ or purchase order) created with reference to a purchase requisition.The requirement tracking number thus enables you to group together the purchasing documents that exist for a certain material requirement. Maximum length: 10.
Agreed Cumulative Quantity. Cumulative quantity of all delivery schedule lines relating to a scheduling agreement item, which has been agreed between Purchasing and the supplier and is valid as of a certain date as the basis for the further ongoing computation of the cumulative quantities. If, in the case of procurement by means of scheduling agreements, differences should arise between the cumulative quantities recorded by your supplier and those determined by the SAP system, you can reconcile the figures with the supplier.As of the reconciliation date, Purchasing and the supplier then both work on the basis of the same, agreed figures.If no reconciliation date has been entered and an agreed cumulative quantity has been maintained, the latter serves as a starting value. This may be useful, for example, if you are creating a new scheduling agreement and wish to start with the cumulative quantity of a previous scheduling agreement with the supplier.Calculation:Starting value = cumulative received quantity + agreed cumulative quantityIf a reconciliation date has been entered and an agreed cumulative quantity maintained, the latter quantity enables you to represent the situation at the change of the fiscal year.Calculation:Cumulative scheduled quantity = cumulative received quantity - agreed cumulative quantity.
Reconciliation Date for Agreed Cumulative Quantity. Date as of which the cumulative delivered quantity agreed with the supplier is valid. If no reconciliation date has been entered and an agreed cumulative quantity has been maintained, the latter quantity serves as a starting value.This may be useful, for example, if you are creating a new scheduling agreement and wish to start with the cumulative quantity of a previous scheduling agreement with the supplier.If a reconciliation date has been entered and an agreed cumulative quantity maintained, the latter quantity is a means of representing the situation at the change of the fiscal year. You can thus reset the cumulative scheduled quantity to 0 after the change of the year.
CQ Control Type. Determines how cumulative quantities (CQ) are calculated. You can use the Control Type to define how cumulative quantities in the scheduling agreement release are determined:Based on inbound deliveriesBased on goods receipts. Maximum length: 1.
Trade-Off Zone (Go-Ahead for Materials Procurement). One of two periods specifying the degree to which the delivery schedule lines of a scheduling agreement release are classified as firm or semi-firm. ! Firm zone I Trade-off zone I!------------------!-----I------------------------I--> Days! ! I I! !SA release creation date Schedule line dateFirm zone: (go-ahead for production)If the date of a schedule line lies within the firm zone, the supplier has the go-ahead to produce the relevant quantity with the assurance that the orderer will bear any and all material and production costs associated with the scheduled quantity in the event of subsequent cancellation by the latter.Trade-off zone: (go-ahead for procurement of input materials)If the date of a schedule line lies within the trade-off zone, the supplier has the go-ahead to purchase any input materials necessary to produce the scheduled quantity. The orderer will recompense him in full for such outlay (but not for any other production costs) in the event that he should subsequently cancel the scheduled quantity.Schedule lines that lie beyond the firm and trade-off zones fall within the planning zone (forecast zone) and are for rough guidance only, being without any commitment on the part of the orderer.In the "Firm zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the firm zone ends and the trade-off zone begins.In the "Trade-off zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the trade-off zone ends.If the firm zone ends in one month, enter 30 in the "Firm zone" field.If the trade-off zone ends one month after the firm zone, enter 60 in the "Trade-off zone" field.In the standard system, the end date for production go-ahead is calculated at the time of SA release creation from the firm zone. The end date for material go-ahead is calculated from the trade-off zone. These dates are displayed in the header of the relevant scheduling agreement release.When an SA release is transmitted to the supplier via IDoc, the end dates for production and material go-ahead are determined from the firm and trade-off zones and the SA release creation date. These dates are shown in the sales scheduling agreement in the SA release header in the relevant fields (End of Production Go-Ahead, End of Material Go-Ahead).
Release Creation Profile. Controls: The creation periodicity of the releases (scheduling agreement delivery schedules), i.e. the period in which releases against a scheduling agreement are created and transmitted to the supplier, andThe way in which the quantities transmitted to the supplier are aggregated (starting from the current creation date of the release)Example:The creation periodicity for a scheduling agreement for which delivery schedule lines have been maintained over two years provides that releases are created weekly from 1.1. to 12.31 of the first year.The release quantities are to be aggregated as follows:For a period of 10 days starting from the current date of release creation, no aggregation; from the tenth to the thirtieth day, on a daily basis; and from the thirtieth day to the sixtieth day, on a monthly basis. Maximum length: 4.
Firm Zone (Go-Ahead for Production). One of two periods specifying the degree to which the delivery schedule lines of a scheduling agreement release are classified as firm or semi-firm. ! Firm zone I Trade-off zone I!------------------!-----I------------------------I--> Days! ! I I! !SA release creation date Schedule line dateFirm zone: (go-ahead for production)If the date of a schedule line lies within the firm zone, the supplier has the go-ahead to produce the relevant quantity with the assurance that the orderer will bear any and all material and production costs associated with the scheduled quantity in the event of subsequent cancellation by the latter.Trade-off zone: (go-ahead for procurement of input materials)If the date of a schedule line lies within the trade-off zone, the supplier has the go-ahead to purchase any input materials necessary to produce the scheduled quantity. The orderer will recompense him in full for such outlay (but not for any other production costs) in the event that he should subsequently cancel the scheduled quantity.Schedule lines that lie beyond the firm and trade-off zones fall within the planning zone (forecast zone) and are for rough guidance only, being without any commitment on the part of the orderer.In the "Firm zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the firm zone ends and the trade-off zone begins.In the "Trade-off zone" field, enter the number of calendar days (calculated from the SA release creation date) after which the trade-off zone ends.If the firm zone ends in one month, enter 30 in the "Firm zone" field.If the trade-off zone ends one month after the firm zone, enter 60 in the "Trade-off zone" field.In the standard system, the end date for production go-ahead is calculated at the time of SA release creation from the firm zone. The end date for material go-ahead is calculated from the trade-off zone. These dates are displayed in the header of the relevant scheduling agreement release.When an SA release is transmitted to the supplier via IDoc, the end dates for production and material go-ahead are determined from the firm and trade-off zones and the SA release creation date. These dates are shown in the sales scheduling agreement in the SA release header in the relevant fields (End of Production Go-Ahead, End of Material Go-Ahead).
Purchasing Document Number. Alphanumeric key uniquely identifying the document. Maximum length: 10.
Item Number of Purchasing Document. Specifies the number that uniquely identifies an item in . Maximum length: 5.
Shipping Instructions. Specifies the packaging and shipping instructions issued to the supplier. Enter the key for the relevant shipping instructions. Maximum length: 2.
Stock Type. Specifies the stock to which the material is posted upon goods receipt (or from which it is posted upon goods issue). If the material is subject to quality inspection, a goods receipt is posted to stock in quality inspection. Maximum length: 1.
Storage Location. Maximum length: 4.
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.
Target Quantity. Total quantity, agreed with the supplier, that can be released or scheduled against the relevant agreement (contract or scheduling agreement).
Tax on Sales/Purchases Code. The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities. Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist. Maximum length: 2.
One-to-many navigation property to the SchAgrmtAcCnt entity.
One-to-many navigation property to the SchAgrmtSchLine entity.
Underdelivery Tolerance. Percentage (based on the order quantity) up to which an underdelivery of this item will be accepted.
Indicator: Unlimited Overdelivery Allowed. Indicator that specifies whether unlimited overdelivery can be accepted for the item.
ETag version identifier accessor.
Unit of Weight. Unit in which the gross or net weight of this item is expressed. If you specify a gross or net weight, you must enter the relevant unit of weight here. Maximum length: 3.
Static representation of the accountAssignmentCategory property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields selector.
Static representation of the companyCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the cumulativeQuantityIsNotSent property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the documentCurrency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the evaldRcptSettlmtIsAllowed property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the firmTradeOffZoneBindMrp property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the goodsReceiptIsExpected property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the goodsReceiptIsNonValuated property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the incotermsClassification property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the incotermsTransferLocation property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the invoiceIsExpected property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the invoiceIsGoodsReceiptBased property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isInfoAtRegistration property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isInfoRecordUpdated property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isOrderAcknRqd property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isRelevantForJitDelivSchedule property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the itemLastTransmissionDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the itemNetWeight property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the manualDeliveryAddressId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the manufacturerMaterial 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 materialType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the minRemainingShelfLife property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the netPriceAmount property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the netPriceQuantity property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the nextFcstDelivSchedSendingDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the nextJitDelivSchedSendingDate 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 orderPriceUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the orderPriceUnitToOrderUnitNmrtr property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the orderQuantityUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the ordPriceUnitToOrderUnitDnmntr property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overdelivTolrtdLmtRatioInPct property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the plant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the priceIsToBePrinted property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the productType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purchaseRequisition property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purchaseRequisitionItem property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purchasingDocumentCategory property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purchasingDocumentDeletionCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purchasingDocumentItemText 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 purgDocEstimatedPrice property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purgDocOrderAcknNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the qualityCertificateType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the qualityMgmtCtrlKey property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the referenceDeliveryAddressId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the requirementTracking property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedgAgrmtRelCreationProfile property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the scheduleLineFirmOrderInDays property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedulingAgreement property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedulingAgreementItem property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedAgrmtAgreedCumQty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedAgrmtCumulativeQtyControl property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedAgrmtCumQtyReconcileDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedLineSemiFirmOrderInDays property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the shippingInstruction property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the stockType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the storageLocation 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 targetQuantity property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the taxCode 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 toSchAgrmtAcCnt 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 toSchAgrmtSchLine for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the underdelivTolrtdLmtRatioInPct property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the unlimitedOverdeliveryIsAllowed property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the weightUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the SchAgrmtItem entity.
Default url path for the according service.
Technical entity name for SchAgrmtItem.
All key fields of the SchAgrmtItem entity.
Mapping of all key field names to the respective static field property SchAgrmtItem.
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 SchAgrmtItem
.
A builder that constructs instances of entity type SchAgrmtItem
.
Returns a selectable object that allows the selection of custom field in a get request for the entity SchAgrmtItem
.
Name of the custom field to select
A builder that constructs instances of entity type SchAgrmtItem
.
Returns a request builder to construct requests for operations on the SchAgrmtItem
entity type.
A SchAgrmtItem
request builder.
This class represents the entity "A_SchAgrmtItem" of service "API_SCHED_AGRMT_PROCESS_SRV". This service is part of the following communication scenarios: Purchase Scheduling Agreement Integration (SAP_COM_0103). See https://api.sap.com/api/API_SCHED_AGRMT_PROCESS_SRV for more information.