public static final class DebitMemoRequestItem.DebitMemoRequestItemBuilder extends Object
@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder debitMemoRequest(DebitMemoRequest value)
value - The DebitMemoRequest to build this DebitMemoRequestItem with.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder debitMemoRequest(String value)
Original property name from the Odata EDM: DebitMemoRequest
value - The debitMemoRequest to build this DebitMemoRequestItem with.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder partner(DebitMemoReqItemPartner... value)
value - The DebitMemoReqItemPartners to build this DebitMemoRequestItem with.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder pricingElement(DebitMemoReqItemPrcgElmnt... value)
value - The DebitMemoReqItemPrcgElmnts to build this DebitMemoRequestItem with.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder text(DebitMemoReqItemText... value)
value - The DebitMemoReqItemTexts to build this DebitMemoRequestItem with.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder debitMemoRequestItem(@Nullable String debitMemoRequestItem)
Original property name from the Odata EDM: DebitMemoRequestItem
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder higherLevelItem(@Nullable String higherLevelItem)
Original property name from the Odata EDM: HigherLevelItem
Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item.Enter the number of a higher-level item.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder debitMemoRequestItemCategory(@Nullable String debitMemoRequestItemCategory)
Original property name from the Odata EDM: DebitMemoRequestItemCategory
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.this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder debitMemoRequestItemText(@Nullable String debitMemoRequestItemText)
Original property name from the Odata EDM: DebitMemoRequestItemText
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.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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).this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder requestedQuantity(@Nullable BigDecimal requestedQuantity)
Original property name from the Odata EDM: RequestedQuantity
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder requestedQuantityUnit(@Nullable String requestedQuantityUnit)
Original property name from the Odata EDM: RequestedQuantityUnit
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder itemGrossWeight(@Nullable BigDecimal itemGrossWeight)
Original property name from the Odata EDM: ItemGrossWeight
The system calculates the gross weight based on the order quantity for the item and the gross weight proposed from the material master record.If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the gross weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the gross weight using the target quantity.You can change the value manually at the item level.
packaging.this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder itemNetWeight(@Nullable BigDecimal itemNetWeight)
Original property name from the Odata EDM: ItemNetWeight
The system calculates the net weight based on the order quantity for the item and the net weight proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the net weight. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the net weight using the target quantity.You can change the value manually at the item level.The gross weight of a refrigerator and its packaging (a cardboard box including protective padding) is 350 pounds. The packaging weighs 25 pounds. In this case, the net weight is 325 pounds.
packaging.this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder itemWeightUnit(@Nullable String itemWeightUnit)
Original property name from the Odata EDM: ItemWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder itemVolume(@Nullable BigDecimal itemVolume)
Original property name from the Odata EDM: ItemVolume
The system calculates the volume based on the order quantity for the item and the volume proposed from the material master record. If the item has more than one schedule line, the system uses the total order quantity of all schedule lines to calculate the volume. In sales documents where schedule lines are not allowed (contracts, for example), the system calculates the volume using the target quantity.You can change the value manually at the item level.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder itemVolumeUnit(@Nullable String itemVolumeUnit)
Original property name from the Odata EDM: ItemVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder netAmount(@Nullable BigDecimal netAmount)
Original property name from the Odata EDM: NetAmount
included. The value is expressed in the document currency.this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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.this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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)
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder batch(@Nullable String batch)
Original property name from the Odata EDM: Batch
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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).this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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").
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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:this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder referenceSDDocument(@Nullable String referenceSDDocument)
Original property name from the Odata EDM: ReferenceSDDocument
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder referenceSDDocumentItem(@Nullable String referenceSDDocumentItem)
Original property name from the Odata EDM: ReferenceSDDocumentItem
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder 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.
this.@Nonnull public DebitMemoRequestItem.DebitMemoRequestItemBuilder orderRelatedBillingStatus(@Nullable String orderRelatedBillingStatus)
Original property name from the Odata EDM: OrderRelatedBillingStatus
You determine whether an item is billed as an order-related or delivery-related item when you define item category defaults through the Customizing menus.Credit and debit memo items, for example, are billed as order-related items.
this.@Nonnull public DebitMemoRequestItem build()
Copyright © 2020 SAP SE. All rights reserved.