public static final class SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder extends Object
@Nonnull public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder partner(SalesSchedgAgrmtItemPartner... value)
value - The SalesSchedgAgrmtItemPartners to build this SalesSchedgAgrmtItem with.@Nonnull public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder pricingElement(SalesSchedgAgrmtItmPrcgElmnt... value)
value - The SalesSchedgAgrmtItmPrcgElmnts to build this SalesSchedgAgrmtItem with.@Nonnull public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder salesSchedgAgrmt(SalesSchedgAgrmt value)
value - The SalesSchedgAgrmt to build this SalesSchedgAgrmtItem with.@Nonnull public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder salesSchedgAgrmtDelivSched(SalesSchedgAgrmtDelivSched... value)
value - The SalesSchedgAgrmtDelivScheds to build this SalesSchedgAgrmtItem with.@Nonnull public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder text(SalesSchedgAgrmtItemText... value)
value - The SalesSchedgAgrmtItemTexts to build this SalesSchedgAgrmtItem with.public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder salesSchedulingAgreement(@Nullable String salesSchedulingAgreement)
Original property name from the Odata EDM: SalesSchedulingAgreement
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder salesSchedulingAgreementItem(@Nullable String salesSchedulingAgreementItem)
Original property name from the Odata EDM: SalesSchedulingAgreementItem
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder salesSchedgAgrmtItemCategory(@Nullable String salesSchedgAgrmtItemCategory)
Original property name from the Odata EDM: SalesSchedgAgrmtItemCategory
The system proposes an item category. If alternatives are defined for your system, you can change the item category manually in the sales document.If, for example, you identify an item as a free or charge item, you tell the system, in this case, to ignore normal pricing procedures.
and text items) and determines how the system processes the item.public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder originallyRequestedMaterial(@Nullable String originallyRequestedMaterial)
Original property name from the Odata EDM: OriginallyRequestedMaterial
If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder materialByCustomer(@Nullable String materialByCustomer)
Original property name from the Odata EDM: MaterialByCustomer
If the customer uses a different identifier than the one you use for the material, you can include this information in a customer-material info record. You can also include in this record specific shipping details, such asMinimum delivery quantityPartial delivery conditionsEnter a value from an existing customer-material info record.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder 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
them to a particular material group.public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder materialPricingGroup(@Nullable String materialPricingGroup)
Original property name from the Odata EDM: MaterialPricingGroup
You can create condition records for a material price group using the following condition types:Material price group (for example, all non-food products)A combination of customer and material price groupA combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder productionPlant(@Nullable String productionPlant)
Original property name from the Odata EDM: ProductionPlant
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder storageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
locations.public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder plngDelivSchedInstrn(@Nullable String plngDelivSchedInstrn)
Original property name from the Odata EDM: PlngDelivSchedInstrn
To create or change a planning delivery schedule, you must first enter a valid instruction in the relevant sales scheduling agreement item. Then you can process planning delivery schedules just as you process forecast and just-in-time (JIT) delivery schedules.Schedule lines in the planning delivery schedule replace those schedule lines in the forecast delivery schedule regarding planning relevance, and if any, delivery relevance.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder salesSchedgAgrmtItemText(@Nullable String salesSchedgAgrmtItemText)
Original property name from the Odata EDM: SalesSchedgAgrmtItemText
Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations.The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder purchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
order).public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder underlyingPurchaseOrderItem(@Nullable String underlyingPurchaseOrderItem)
Original property name from the Odata EDM: UnderlyingPurchaseOrderItem
Enter the item number from the customer's document. The item number may vary from the item number that appears in your own sales document.
item.public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder orderQuantity(@Nullable BigDecimal orderQuantity)
Original property name from the Odata EDM: OrderQuantity
If there is more than one schedule line for the item, the total order quantity is taken from the rounded quantity of the total of all the schedule lines.If no rounding is carried out, then the order required quantity corresponds to a schedule line of the rounded quantity.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder orderToBaseQuantityDnmntr(@Nullable BigDecimal orderToBaseQuantityDnmntr)
Original property name from the Odata EDM: OrderToBaseQuantityDnmntr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder orderToBaseQuantityNmrtr(@Nullable BigDecimal orderToBaseQuantityNmrtr)
Original property name from the Odata EDM: OrderToBaseQuantityNmrtr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder orderQuantityUnit(@Nullable String orderQuantityUnit)
Original property name from the Odata EDM: OrderQuantityUnit
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder targetQuantity(@Nullable BigDecimal targetQuantity)
Original property name from the Odata EDM: TargetQuantity
The following list shows the use of target quantities in different types of sales document.Scheduling agreements: A target quantity represents the total quantity of an item that the customer has agreed to buy during the validity period of the agreement.Credit and debit memo requests: A target quantity represents the total quantity of an item for which you want to issue a credit or debit memo request.Product proposals: A target quantity represents the total quantity of an item that is suggested as part of a product proposal. After you have copied the product proposal into a new sales document, you can create schedule lines.
example, bottles).public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder targetQuantityUnit(@Nullable String targetQuantityUnit)
Original property name from the Odata EDM: TargetQuantityUnit
You may use a different unit of measure when you actually process the item.You can create a contract, for example, in which you enter a target quantity in pallets. Later, when you create release orders against the contract, you can specify any other units of measure defined in the material master (for example, cartons).
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder salesDocumentRjcnReason(@Nullable String salesDocumentRjcnReason)
Original property name from the Odata EDM: SalesDocumentRjcnReason
The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection:Inquiries and quotations: no further references by other documentsSales orders: no further delivery of itemsContracts: no further creation of release ordersCredit and debit memo requests: no further processing of credit or debit memosEnter one of the values predefined for your system.If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder netAmount(@Nullable BigDecimal netAmount)
Original property name from the Odata EDM: NetAmount
included. The value is expressed in the document currency.public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder netPriceAmount(@Nullable BigDecimal netPriceAmount)
Original property name from the Odata EDM: NetPriceAmount
The net price always refers to the condition unit and the condition pricing unit in the relevant pricing condition.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder netPriceQuantity(@Nullable BigDecimal netPriceQuantity)
Original property name from the Odata EDM: NetPriceQuantity
You want to create a condition record for a material price of US$8 for 1 piece. You enter "8" in the Rate field, "USD" in the Unit field, and "1" as the condition pricing unit in this field.You create a condition record that gives a fixed discount of $10 to a customer who buys 1000 bottles. In this case, the condition pricing unit is 1000.
example, bottles).public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder netPriceQuantityUnit(@Nullable String netPriceQuantityUnit)
Original property name from the Odata EDM: NetPriceQuantityUnit
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder transactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder pricingDate(@Nullable LocalDateTime pricingDate)
Original property name from the Odata EDM: PricingDate
You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder shippingPoint(@Nullable String shippingPoint)
Original property name from the Odata EDM: ShippingPoint
You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.
item.public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder shippingType(@Nullable String shippingType)
Original property name from the Odata EDM: ShippingType
During automatic shipment leg determination, all legs created or only the main, direct, or return legs are assigned to this shipping type, depending on the type of leg determination.You can enter the shipment type for the main, direct or return legs in the shipping header. The value is proposed depending on the requirement in the shipment type.By setting the status "planned", you have the shipping type copied from the respective deliveries into the shipment header, provided:The shipping type is identical in all the deliveries.The shipping type in the shipment header is not already filled.See also: Leg determination
for the shipment legs.public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder deliveryPriority(@Nullable String deliveryPriority)
Original property name from the Odata EDM: DeliveryPriority
You can assign delivery priority to either a particular material or to a combination of customer and material. When you process deliveries collectively, you can use delivery priority as one of the selection criteria.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder incotermsClassification(@Nullable String incotermsClassification)
Original property name from the Odata EDM: IncotermsClassification
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.
Commerce (ICC).public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder incotermsTransferLocation(@Nullable String incotermsTransferLocation)
Original property name from the Odata EDM: IncotermsTransferLocation
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").
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder incotermsLocation1(@Nullable String incotermsLocation1)
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder incotermsLocation2(@Nullable String incotermsLocation2)
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
customized appropriately). Note the following for the incoterms versions below:public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder customerPaymentTerms(@Nullable String customerPaymentTerms)
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder itemBillingBlockReason(@Nullable String itemBillingBlockReason)
Original property name from the Odata EDM: ItemBillingBlockReason
To block an item for billing, enter one of the values predefined for your system.You can block an item for billing so that, for example, terms of payment or prices can be checked before further processing takes place.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder sDProcessStatus(@Nullable String sDProcessStatus)
Original property name from the Odata EDM: SDProcessStatus
The system determines the overall status from all statuses (for example, delivery and billing) for this item. The status message tells you whether processing of the item is open, in progress, or complete.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder deliveryStatus(@Nullable String deliveryStatus)
Original property name from the Odata EDM: DeliveryStatus
The status line tells you if the item is not yet delivered, is partly delivered, is completely delivered, or is not relevant for delivery.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder itemGeneralIncompletionStatus(@Nullable String itemGeneralIncompletionStatus)
Original property name from the Odata EDM: ItemGeneralIncompletionStatus
The status line tells you if all item information, necessary for further processing this item, is complete.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder itemBillingIncompletionStatus(@Nullable String itemBillingIncompletionStatus)
Original property name from the Odata EDM: ItemBillingIncompletionStatus
The status line tells you to what extent the information necessary for billing the item is complete.A sales order item, for example, is incomplete for billing if prices are missing. You cannot bill the item until you provide the missing information.
public SalesSchedgAgrmtItem.SalesSchedgAgrmtItemBuilder itemDeliveryIncompletionStatus(@Nullable String itemDeliveryIncompletionStatus)
Original property name from the Odata EDM: ItemDeliveryIncompletionStatus
The status line tells you if delivery-related item information is complete. You must enter this information, if you want to process the item further.A sales order item is incomplete for delivery processing if, for example, you do not enter a shipping point. You cannot deliver the item until you provide this information.
public SalesSchedgAgrmtItem build()
Copyright © 2019 SAP SE. All rights reserved.