public static final class ReturnsDeliveryItem.ReturnsDeliveryItemBuilder extends Object
@Nonnull public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder serialDeliveryItem(ReturnsDeliverySrlNmbr value)
value
- The ReturnsDeliverySrlNmbr to build this ReturnsDeliveryItem with.@Nonnull public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder documentFlow(ReturnsDeliveryDocFlow... value)
value
- The ReturnsDeliveryDocFlows to build this ReturnsDeliveryItem with.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder actualDeliveredQtyInBaseUnit(@Nullable BigDecimal actualDeliveredQtyInBaseUnit)
Original property name from the Odata EDM: ActualDeliveredQtyInBaseUnit
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder actualDeliveryQuantity(@Nullable BigDecimal actualDeliveryQuantity)
Original property name from the Odata EDM: ActualDeliveryQuantity
The delivery quantity may be proposed from a sales order item. You can change the quantity in the delivery, subject to any limitations that apply to over- and underdeliveries. If the delivery does not refer to a sales order, you can enter a delivery quantity manually.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalCustomerGroup1(@Nullable String additionalCustomerGroup1)
Original property name from the Odata EDM: AdditionalCustomerGroup1
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalCustomerGroup2(@Nullable String additionalCustomerGroup2)
Original property name from the Odata EDM: AdditionalCustomerGroup2
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryVersion(@Nullable String deliveryVersion)
Original property name from the Odata EDM: DeliveryVersion
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalCustomerGroup3(@Nullable String additionalCustomerGroup3)
Original property name from the Odata EDM: AdditionalCustomerGroup3
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalCustomerGroup4(@Nullable String additionalCustomerGroup4)
Original property name from the Odata EDM: AdditionalCustomerGroup4
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalCustomerGroup5(@Nullable String additionalCustomerGroup5)
Original property name from the Odata EDM: AdditionalCustomerGroup5
You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders.You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalMaterialGroup1(@Nullable String additionalMaterialGroup1)
Original property name from the Odata EDM: AdditionalMaterialGroup1
not used in the standard SAP System, you can use them as required, for example, for analyses.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalMaterialGroup2(@Nullable String additionalMaterialGroup2)
Original property name from the Odata EDM: AdditionalMaterialGroup2
not used in the standard SAP System, you can use them as required, for example, for analyses.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalMaterialGroup3(@Nullable String additionalMaterialGroup3)
Original property name from the Odata EDM: AdditionalMaterialGroup3
not used in the standard SAP System, you can use them as required, for example, for analyses.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalMaterialGroup4(@Nullable String additionalMaterialGroup4)
Original property name from the Odata EDM: AdditionalMaterialGroup4
not used in the standard SAP System, you can use them as required, for example, for analyses.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder additionalMaterialGroup5(@Nullable String additionalMaterialGroup5)
Original property name from the Odata EDM: AdditionalMaterialGroup5
not used in the standard SAP System, you can use them as required, for example, for analyses.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder alternateProductNumber(@Nullable String alternateProductNumber)
Original property name from the Odata EDM: AlternateProductNumber
It does not need to be created as its own material master in the ERP system.Within Logistics Execution in the ERP system, it is stored without validation. The translation to the internal material number needs to be provided in the external system or within an implementation of a Business Add-In (BAdI).
partner uses.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder baseUnit(@Nullable String baseUnit)
Original property name from the Odata EDM: BaseUnit
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
enter in other units of measure (alternative units of measure) to the base unit of measure.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder batch(@Nullable String batch)
Original property name from the Odata EDM: Batch
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder batchBySupplier(@Nullable String batchBySupplier)
Original property name from the Odata EDM: BatchBySupplier
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder batchClassification(@Nullable String batchClassification)
Original property name from the Odata EDM: BatchClassification
You are required by the authorities (for example, the Food and Drug Authority in the USA) to keep a record of the selection values used to locate a particular batch so that you are always able to compare these values with the original specifications. This internal number enables you to meet this requirement.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder bOMExplosion(@Nullable String bOMExplosion)
Original property name from the Odata EDM: BOMExplosion
and receives materials.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder consumptionPosting(@Nullable String consumptionPosting)
Original property name from the Odata EDM: ConsumptionPosting
The indicator is used in the case of goods receipts for purchase orders and is derived from the account assignment category of the purchase order.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder controllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder creationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder custEngineeringChgStatus(@Nullable String custEngineeringChgStatus)
Original property name from the Odata EDM: CustEngineeringChgStatus
The customer sends this number in with a material number to request an engineering change to take effect as of a certain delivery date or cumulative quantity.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryDocument(@Nullable String deliveryDocument)
Original property name from the Odata EDM: DeliveryDocument
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryDocumentItem(@Nullable String deliveryDocumentItem)
Original property name from the Odata EDM: DeliveryDocumentItem
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryDocumentItemCategory(@Nullable String deliveryDocumentItemCategory)
Original property name from the Odata EDM: DeliveryDocumentItemCategory
The delivery item category determines how the system processes an item.An item category for return items might be configured as not relevant for picking.The system proposes a delivery item category during delivery creation.
and text items).this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryDocumentItemText(@Nullable String deliveryDocumentItemText)
Original property name from the Odata EDM: DeliveryDocumentItemText
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
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryGroup(@Nullable String deliveryGroup)
Original property name from the Odata EDM: DeliveryGroup
The system uses delivery groups to check the availability of items that should be delivered together. The delivery date of the latest schedule line in the delivery group is taken as the general date for the whole group.During sales order processing, you can enter a number (up to three digits) that identifies a delivery group. The number is freely definable.If necessary, the system adjusts requirements that have already been created and changes the material availability dates for individual items to the delivery date that it has determined for the group.If a typewriter is usually delivered with a case, you can define the two items as a delivery group.If an item has more than one schedule line with a confirmed quantity, then the system deletes all undelivered schedule lines up to the last one. The system automatically carries over the quantities from the deleted schedule lines into the last one. If necessary, the system changes the delivery date of the last schedule line to that of the delivery group.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryQuantityUnit(@Nullable String deliveryQuantityUnit)
Original property name from the Odata EDM: DeliveryQuantityUnit
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryRelatedBillingStatus(@Nullable String deliveryRelatedBillingStatus)
Original property name from the Odata EDM: DeliveryRelatedBillingStatus
The status line tells you if the item is not yet billed, is partly billed, is completely billed, or is not relevant for billing.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryToBaseQuantityDnmntr(@Nullable BigDecimal deliveryToBaseQuantityDnmntr)
Original property name from the Odata EDM: DeliveryToBaseQuantityDnmntr
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.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder deliveryToBaseQuantityNmrtr(@Nullable BigDecimal deliveryToBaseQuantityNmrtr)
Original property name from the Odata EDM: DeliveryToBaseQuantityNmrtr
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.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder departmentClassificationByCust(@Nullable String departmentClassificationByCust)
Original property name from the Odata EDM: DepartmentClassificationByCust
marketing, etc.)this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder distributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: DistributionChannel
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
wholesale, retail, or direct sales.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder division(@Nullable String division)
Original property name from the Odata EDM: Division
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
areas and the business areas for a material, product, or service.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder fixedShipgProcgDurationInDays(@Nullable BigDecimal fixedShipgProcgDurationInDays)
Original property name from the Odata EDM: FixedShipgProcgDurationInDays
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder gLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder goodsMovementReasonCode(@Nullable String goodsMovementReasonCode)
Original property name from the Odata EDM: GoodsMovementReasonCode
Please do not change the entry in this field.Any changes made could lead to program errors or terminations.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder goodsMovementStatus(@Nullable String goodsMovementStatus)
Original property name from the Odata EDM: GoodsMovementStatus
The status provides the following information:For an outbound delivery, the status informs you whether the item has already left the warehouse or company premises, or still being processed.For an inbound delivery, the system shows you whether the goods have already been received, or are waiting to be received.The status also informs you whether or not an item is relevant for delivery. A text item is not relevant, for example.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder goodsMovementType(@Nullable String goodsMovementType)
Original property name from the Odata EDM: GoodsMovementType
warehouse) is allocated to a movement type in the system.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder 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
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder inspectionLot(@Nullable String inspectionLot)
Original property name from the Odata EDM: InspectionLot
The inspection lot number is assigned by the system.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder inspectionPartialLot(@Nullable String inspectionPartialLot)
Original property name from the Odata EDM: InspectionPartialLot
You can process partial lots by:Inspecting during production using inspection pointsRunning a batch split for the delivery note
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder intercompanyBillingStatus(@Nullable String intercompanyBillingStatus)
Original property name from the Odata EDM: IntercompanyBillingStatus
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder internationalArticleNumber(@Nullable String internationalArticleNumber)
Original property name from the Odata EDM: InternationalArticleNumber
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder inventorySpecialStockType(@Nullable String inventorySpecialStockType)
Original property name from the Odata EDM: InventorySpecialStockType
If you need to separately manage certain stock (for example, consignment stock) of a material, the stock type in question is defined using this indicator.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder inventoryValuationType(@Nullable String inventoryValuationType)
Original property name from the Odata EDM: InventoryValuationType
The valuation types allowed for a material are determined by the valuation category.If a material is valuated according to its origin (valuation category H), you can define the possible countries of origin as valuation types.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder isCompletelyDelivered(@Nullable Boolean isCompletelyDelivered)
Original property name from the Odata EDM: IsCompletelyDelivered
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder isNotGoodsMovementsRelevant(@Nullable String isNotGoodsMovementsRelevant)
Original property name from the Odata EDM: IsNotGoodsMovementsRelevant
When this indicator is set, goods movement is not posted for this item - regardless of the movement type assigned to it.
is still being created.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder isSeparateValuation(@Nullable Boolean isSeparateValuation)
Original property name from the Odata EDM: IsSeparateValuation
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder issgOrRcvgBatch(@Nullable String issgOrRcvgBatch)
Original property name from the Odata EDM: IssgOrRcvgBatch
The "receiving batch" is the number of the batch under which the quantity to be transferred is now to be recorded.The "issuing batch" (in the case of a reversal) is the number of the batch from which a quantity is to be deducted.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder issgOrRcvgMaterial(@Nullable String issgOrRcvgMaterial)
Original property name from the Odata EDM: IssgOrRcvgMaterial
The "receiving material" is the material number under which the quantity to be transferred is now to be recorded.The "issuing material" (in the case of a reversal) is the material from whose stock a certain quantity is to be deducted.NoteThe value of the transfer posting is determined not by the material entered here but by the material specified in the Material field.Note the following with regard to the receiving/issuing material:The material must existThe material must be managed in the same stockkeeping unit as the issuing material
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder issgOrRcvgSpclStockInd(@Nullable String issgOrRcvgSpclStockInd)
Original property name from the Odata EDM: IssgOrRcvgSpclStockInd
This indicator is used, for example, in the case of the physical transfer of a consignment material and when consignment material is transferred from the supplier's stock to the company's own stock.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder issgOrRcvgStockCategory(@Nullable String issgOrRcvgStockCategory)
Original property name from the Odata EDM: IssgOrRcvgStockCategory
returned stock, and so on.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder issgOrRcvgValuationType(@Nullable String issgOrRcvgValuationType)
Original property name from the Odata EDM: IssgOrRcvgValuationType
same material) to permit stocks of a transfer batch to be differentiated according to different criteria.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder issuingOrReceivingPlant(@Nullable String issuingOrReceivingPlant)
Original property name from the Odata EDM: IssuingOrReceivingPlant
The receiving plant is the plant or internal organizational unit that is to receive the goods.The issuing plant is the plant that issues the goods.NoteThe value of the transfer posting is determined not by the plant entered here but by the plant specified in the Plant field.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder issuingOrReceivingStorageLoc(@Nullable String issuingOrReceivingStorageLoc)
Original property name from the Odata EDM: IssuingOrReceivingStorageLoc
The receiving storage location is the storage location that is to receive the goods.The issuing storage location is the storage location that issues the goods.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder itemBillingBlockReason(@Nullable String itemBillingBlockReason)
Original property name from the Odata EDM: ItemBillingBlockReason
The system can automatically propose a billing block for sales documents that must be checked before billing (for example, returns, credit and debit memo requests).If the system proposes a block, you can change the block manually for each item. If the system does not propose a block, enter one of values predefined for your system. If the item has more than one schedule line, the block applies to each line. You can change the block for individual schedule lines.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder 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.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder 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.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder itemGdsMvtIncompletionSts(@Nullable String itemGdsMvtIncompletionSts)
Original property name from the Odata EDM: ItemGdsMvtIncompletionSts
The status provides information on how far the data required for billing the item is complete.A sales document item is incomplete for billing, for example, if price specifications are missing. You can only invoice the item if you have completed the missing data.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder 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.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder itemGrossWeight(@Nullable BigDecimal itemGrossWeight)
Original property name from the Odata EDM: ItemGrossWeight
The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order. If there is no related sales order, the system uses the gross weight from the material master record.You can change the gross weight manually in the delivery document.
weight of packaging.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder itemIsBillingRelevant(@Nullable String itemIsBillingRelevant)
Original property name from the Odata EDM: ItemIsBillingRelevant
' ': Not relevant for billingYou can use this category to prevent items from being included in billing.Item categories KLN (free item) and TAE (explanation) are set up with billing relevance ' ' in the standard system.A: Relevant for delivery-related billingBilling is based on the outbound delivery. The billing status is only updated in the outbound delivery.B: Relevant for order-related billingBilling is based on the sales document. The billing status depends on the requested delivery quantity.Item categories REN (returns) and BVN (cash sales items) are set up with billing relevance B in the standard system.C: Relevant for order-related billingBilling is based on the sales document. The billing status depends on the target quantity.Item categories G2N (credit memo) and L2N (debit memo) are set up with billing relevance C in the standard system.D: Relevant for pro formaTo create a pro forma invoice, the billing relevance indicator must not be blank.Indicator D is also used as follows for cross-company-code business processing:If there are free-of-charge outbound deliveries, the company code that is responsible for the delivery should be granted an internal settlement. You can use indicator D to enable this for free-of-charge deliveries.F: Relevant for order-related billing - Status based on invoice receipt quantityRelevant for order-related billing based on the invoice receipt quantity (third-party business transaction). The system does not transfer the order to the billing due list until the vendor invoice has been received and processed in the purchasing department. After the receipt of each invoice, a customer invoice is created for the quantity that appears on the vendor invoice. The order has status "Billed" until the next vendor invoice is received.Item category TAS (third-party business) is set up with billing relevance F in the standard system.This process can also be related to the goods receipt quantity.You can make the control setting as to whether the invoice receipt quantity or the goods receipt quantity is relevant for billing in the copy control for billing on the item level in the Billing Quantity field.G: Relevant for order-related billing of the delivery quantityThe order is relevant for billing; more specifically, the cumulated quantity that has already been delivered is relevant. You can use this category to bill for multiple partial deliveries in one process.H: Relevant for delivery-related billing – no zero quantitiesYou can use this category to prevent items with a value of zero from being included in billing.I: Relevant for order-related billing – billing planBilling takes place using the billing plan and its status. The status of the order item can be understood as the overall status of the billing plan billing statuses.Item categories WVN (maintenance contract item), MVN (lease item), and TAO (milestone billing) are set up with billing relevance I in the standard system.J: Relevant for deliveries across EU countriesThe outbound delivery is relevant for billing only in the following situations:The 'Plants Abroad' switch is active in Customizing (in the basic settings for Financial Accounting).The departure country (country of plant) and destination country (country of goods recipient) are different EU countries.Item categories KBN (consignment fill-up), KAN (consignment pick-up), and NLN (standard stock transfer item) are set up with billing relevance J in the standard system.K: Relevant for delivery-related partial quantity billingYou use this indicator if you want to select both items and partial quantities for billing.L: Relevant for pro forma – no zero quantitiesYou can use this category to prevent items with a value of zero from being included in the pro forma invoice.M: Relevant for delivery-related billing – no zero quantities (including batch main item)You can use this category to prevent items with a value of zero from being included in billing, even if the item is a batch main item.N: Relevant for pro forma – no zero quantities (including batch main item)You can use this category to prevent items with a value of zero from being included in the pro forma invoice, even if the item is a batch main item.O: Relevant for delivery-related partial quantity billing – no zero quantitiesYou use this indicator if you want to select both items and partial quantities for billing.You can also use the indicator O to prevent items with a value of zero from being included in a partial quantity billing document.P: Relevant for delivery-related billing (CSFG) – no batch split itemsThe basis is business processing with a cross-system flow of goods (CSFG).You can use the indicator P to prevent batch split items from being included in billing.Q: Relevant for delivery-related CRM billingYou use this indicator if you want to use CRM billing to bill the items that have been delivered and posted as goods issues in the ERP system.R: Relevant for delivery-related CRM billing – no zero quantitiesYou use this indicator if you want to use CRM billing to bill the items that have been delivered and posted as goods issues in the ERP system.You can also use this category to prevent items with a value of zero from being included in billing in CRM.T: Relevant for delivery-related CRM billing to create intercompany billing documentYou use this indicator if you want to use CRM billing to create an intercompany billing document to bill the items that have been delivered and posted as goods issues in the ERP system.U: Relevant for delivery-related CRM billing to create intercompany billing document - no zero quantitiesYou use this indicator if you want to use CRM billing to create an intercompany billing document to bill the items that have been delivered and posted as goods issues in the ERP system.You can also use this category to prevent items with a value of zero from being included in the intercompany billing document in CRM.V: Relevant for delivery-related CRM billing to create intercompany billing document of stock transport ordersYou use this indicator if you want to use CRM billing to create an intercompany billing document to bill the items that have been delivered and posted as goods issues in the ERP system for stock transport orders.W: Relevant for delivery-related CRM billing to create intercompany billing document of stock transport orders – no zero quantitiesYou use this indicator if you want to use CRM billing to create an intercompany billing document to bill the items that have been delivered and posted as goods issues in the ERP system for stock transport orders.You can also use this category to prevent items with a value of zero from being included in the intercompany billing document in CRM.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder itemNetWeight(@Nullable BigDecimal itemNetWeight)
Original property name from the Odata EDM: ItemNetWeight
The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order. If there is no related sales order, the system uses the net weight from the material master record.You can change the net weight manually in the delivery document.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder itemPackingIncompletionStatus(@Nullable String itemPackingIncompletionStatus)
Original property name from the Odata EDM: ItemPackingIncompletionStatus
The status indicates the degree to which the data required for billing the item are complete.For example, a sales order item is incomplete for billing if prices are missing. You cannot bill the item unless you have entered the missing data.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder itemPickingIncompletionStatus(@Nullable String itemPickingIncompletionStatus)
Original property name from the Odata EDM: ItemPickingIncompletionStatus
The status indicates whether the delivery-related item data is complete. You must enter these data if you want to further process the item.For example, a sales order item is incomplete for delivery processing if you do not specify a shipping point. You cannot deliver the item unless you have entered these data.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder itemVolume(@Nullable BigDecimal itemVolume)
Original property name from the Odata EDM: ItemVolume
The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order. If there is no related sales order, the system uses the volume from the material master record.You can change the volume manually in the delivery document.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder 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
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder 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
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder loadingGroup(@Nullable String loadingGroup)
Original property name from the Odata EDM: LoadingGroup
The system uses the loading group, as well as the shipping conditions and the delivering plant, to automatically determine the item's shipping point.Different loading groups could consist, for example, of materials that require the same:Equipment during loading (for example, a fork-lift truck)Amount of time for loadingLoading point (for example, loading bay #6)
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder manufactureDate(@Nullable LocalDateTime manufactureDate)
Original property name from the Odata EDM: ManufactureDate
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder materialByCustomer(@Nullable String materialByCustomer)
Original property name from the Odata EDM: MaterialByCustomer
The customer's own identifier for a material can be stored in a customer-material info record and can be used to enter data during sales order processing.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder materialFreightGroup(@Nullable String materialFreightGroup)
Original property name from the Odata EDM: MaterialFreightGroup
Freight codes and classes in a freight code set are determined by the material freight group. The freight code set is used to determine freight costs and for communication with service agents.Maintain the corresponding group for the material.
code and class.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder 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
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder materialIsBatchManaged(@Nullable Boolean materialIsBatchManaged)
Original property name from the Odata EDM: MaterialIsBatchManaged
This indicator can be set in the material master record manually or, if batches are valuated individually, it is set automatically for the plants concerned, in which case it cannot be changed.The indicator cannot be changed if stocks exist in either the current period or in the previous period. The reason for checking the previous period is because stocks can be posted to this period when goods movements are entered.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder materialIsIntBatchManaged(@Nullable Boolean materialIsIntBatchManaged)
Original property name from the Odata EDM: MaterialIsIntBatchManaged
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder numberOfSerialNumbers(@Nullable Integer numberOfSerialNumbers)
Original property name from the Odata EDM: NumberOfSerialNumbers
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder orderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder orderItem(@Nullable String orderItem)
Original property name from the Odata EDM: OrderItem
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder originalDeliveryQuantity(@Nullable BigDecimal originalDeliveryQuantity)
Original property name from the Odata EDM: OriginalDeliveryQuantity
When creating the inbound delivery, the notified quantity is transferred as the original quantity.Should you want to change the notified quantity at a later point in time, because the actual quantity delivered is different, you can decide whether or not you want this change to be displayed in the Original Quantity field.Should you want to change the delivery quantity in an inbound delivery that already exists in the system, then you will receive a dialog box with the following choices:If you choose Yes, the delivery quantity will be changed and the originally/previously notified quantity will continue to be displayed in the Original Quantity field.This will then document in the system that the vendor actually delivered a different quantity than that originally notified.If you choose No, the delivery quantity will be changed and the previously notified quantity shown in the Original Quantity field will be overwritten with the new delivery quantity.In this case, the delivery quantity that was changed by the vendor will not be documented in the system.In the confirmation overview of the scheduling agreement, the fields Quantity and Original Quantity show you whether or not the vendor actually delivered the quantity he originally notified you of.In a shipping notification, your vendor notifies you of the impending delivery of 450 pc Steel_01. When the inbound delivery is created, the 450 pc are recorded as delivery quantity and original quantity.However, you vendor actually delivers 500 pc. You therefore change the delivery quantity in the inbound delivery.A dialog box then appears, offering you the following options:Yes - Document originally notified quantityResultThe delivery quantity is changed to 500 pc and the quantity variance is documented, i.e. the originally notified quantity of 450 pc continues to be shown in the Original Quantity field.No - Do not document originally notified quantityResultThe delivery quantity is changed to 500 pc and the quantity variance is not documented, i.e. the originally notified quantity of 450 pc shown in the Original Quantity field is replaced by the quantity 500 pc actually delivered.NoteIf you use this function, then the GR assignment should be set in Customizing for Purchasing, in the confirmation control for the used confirmation categories.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder 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.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder overdelivTolrtdLmtRatioInPct(@Nullable BigDecimal overdelivTolrtdLmtRatioInPct)
Original property name from the Odata EDM: OverdelivTolrtdLmtRatioInPct
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.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder packingStatus(@Nullable String packingStatus)
Original property name from the Odata EDM: PackingStatus
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder partialDeliveryIsAllowed(@Nullable String partialDeliveryIsAllowed)
Original property name from the Odata EDM: PartialDeliveryIsAllowed
You use this field to control partial deliveries at the item level. If the customer allows partial delivery, you can choose from different partial delivery options. For example, you can specify whether the customer allows you to make one delivery attempt only on the requested delivery date or whether unlimited delivery attempts are possible.When partial delivery indicator 'D' is set, the order can never have status 'fully delivered'. You must complete each item by entering a reason for rejection. This could be applied to scheduling agreements, for example.You can enter a value in this field only if the customer allows partial deliveries for the entire sales document.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder paymentGuaranteeForm(@Nullable String paymentGuaranteeForm)
Original property name from the Odata EDM: PaymentGuaranteeForm
The form of payment guarantee specifies how a sales document item is guaranteed.Payment cardsLetter of creditStandby letter of creditBank guarantee
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder pickingConfirmationStatus(@Nullable String pickingConfirmationStatus)
Original property name from the Odata EDM: PickingConfirmationStatus
When you create a delivery with an item subject to pick/putaway confirmation, the item is assigned the status A (Subject to confirmation but not yet confirmed). Once you confirm the pick/putaway, the system assigns either status B (Partially confirmed) or C (Fully confirmed).Goods movement cannot be posted for items subject to pick/putaway confirmation until the pick/putaway quantities for the items have been fully confirmed.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder pickingControl(@Nullable String pickingControl)
Original property name from the Odata EDM: PickingControl
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder pickingStatus(@Nullable String pickingStatus)
Original property name from the Odata EDM: PickingStatus
The status message tells you whether the item is relevant for delivery. If the item is relevant for delivery, the status indicates whether picking/putaway has:BegunBeen partially carried outBeen completedPicking/putaway is not relevant for some items, for example, text items or service items.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder primaryPostingSwitch(@Nullable String primaryPostingSwitch)
Original property name from the Odata EDM: PrimaryPostingSwitch
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder productAvailabilityDate(@Nullable LocalDateTime productAvailabilityDate)
Original property name from the Odata EDM: ProductAvailabilityDate
The system uses the material availability date to generate automatic production and purchasing requirements. The system calculates the material availability date by working backwards from the customer's requested delivery date, taking into account how much time is needed for delivery-related procedures, such as picking, packing, loading, and transportation.The system proposes the material availability date. You can change the date manually in the sales document.The picking date is the same as the material availability date.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder productAvailabilityTime(@Nullable LocalTime productAvailabilityTime)
Original property name from the Odata EDM: ProductAvailabilityTime
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder productConfiguration(@Nullable String productConfiguration)
Original property name from the Odata EDM: ProductConfiguration
This number clearly identifies one particular configuration of a standard product.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder productHierarchyNode(@Nullable String productHierarchyNode)
Original property name from the Odata EDM: ProductHierarchyNode
In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.Level Number of characters allowed1 52 53 8You define a product hierarchy with the following levels:Level Example Description1 00005 Electrical goods2 00003 Wet appliances3 00000001 Washing machineIn this case, a washing machine belongs to the product hierarchy 000050000300000001.
is used for analyses and price determination.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder profitabilitySegment(@Nullable String profitabilitySegment)
Original property name from the Odata EDM: ProfitabilitySegment
Examples:Customer '123'/Product '4710' Profitability segment no. 1Customer '123'/Product '4712' Profitability segment no. 2Country 'USA'/Region 'NORTH' Profitability segment no. 3
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder proofOfDeliveryRelevanceCode(@Nullable String proofOfDeliveryRelevanceCode)
Original property name from the Odata EDM: ProofOfDeliveryRelevanceCode
The indicator can have the following settings:' ': not POD relevant'A' : always POD relevant'B' : only POD relevant when there are quantity differencesThe indicator is copied from the purchasing or sales document into the delivery, if control of POD relevance in the delivery item category is set to "Copy POD relevance from preceding document".
is to say, whether a delivery item is relevant for proof of delivery on the ship-to party side.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder proofOfDeliveryStatus(@Nullable String proofOfDeliveryStatus)
Original property name from the Odata EDM: ProofOfDeliveryStatus
The status message informs you whether the ship-to party reported a proof of delivery for this item.This status may have the following values for a delivery item:' ' Not relevant for the POD process'A' Relevant for the POD process'B' Differences were reported'C' Quantities were verified and confirmed
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder quantityIsFixed(@Nullable Boolean quantityIsFixed)
Original property name from the Odata EDM: QuantityIsFixed
Set this indicator if the quantity in a relational system does not change.If an item of a BOM is marked as being fixed and the quantity of the finished product to be manufactured is changed, the quantity of this item does not change.If a "materials to be provided" item is not marked as being fixed, and the quantity of the subcontracted item is changed, the quantity of the material to be provided to the subcontractor changes proportionately.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder receivingPoint(@Nullable String receivingPoint)
Original property name from the Odata EDM: ReceivingPoint
Several receiving points can be defined for each plant. The receiving points can then be assigned to individual departments.The receiving point can be printed on delivery documents (SD function).
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder referenceDocumentLogicalSystem(@Nullable String referenceDocumentLogicalSystem)
Original property name from the Odata EDM: ReferenceDocumentLogicalSystem
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder referenceSDDocument(@Nullable String referenceSDDocument)
Original property name from the Odata EDM: ReferenceSDDocument
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder referenceSDDocumentCategory(@Nullable String referenceSDDocumentCategory)
Original property name from the Odata EDM: ReferenceSDDocumentCategory
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder referenceSDDocumentItem(@Nullable String referenceSDDocumentItem)
Original property name from the Odata EDM: ReferenceSDDocumentItem
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder retailPromotion(@Nullable String retailPromotion)
Original property name from the Odata EDM: RetailPromotion
For each item of a purchasing document, you can specify the promotion to which the item belongs.Depending on your system settings, special prices and conditions that are maintained in the IS-R system (Retail) for this promotion are applied when a promotion number is entered.This field also allows you to create purchasing documents on a selective basis for a certain promotion. For example, you can create a purchase order containing only those items that are to be procured for one promotion.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder salesDocumentItemType(@Nullable String salesDocumentItemType)
Original property name from the Odata EDM: SalesDocumentItemType
The system processes items that refer to a specific material differently than items that do not refer to a material. For example, text items do not require processing for pricing, taxes, and weight calculations.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder salesGroup(@Nullable String salesGroup)
Original property name from the Odata EDM: SalesGroup
By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder salesOffice(@Nullable String salesOffice)
Original property name from the Odata EDM: SalesOffice
When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
products or services within a given geographical area.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder sDDocumentCategory(@Nullable String sDDocumentCategory)
Original property name from the Odata EDM: SDDocumentCategory
The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
sales orders, deliveries, and invoices.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder 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
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder shelfLifeExpirationDate(@Nullable LocalDateTime shelfLifeExpirationDate)
Original property name from the Odata EDM: ShelfLifeExpirationDate
You enter it yourself.You enter a date of production, and the system calculates the shelf life expiration date from the date of production plus the shelf life in days (from the material master record).NoteThis date can still be changed upon receipt of the usage decision for an inspection lot.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder statisticsDate(@Nullable LocalDateTime statisticsDate)
Original property name from the Odata EDM: StatisticsDate
Write a user-exit if you require the system to copy the statistics date to the billing document. The field definition may change depending on the user-exit.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder stockType(@Nullable String stockType)
Original property name from the Odata EDM: StockType
Possible stocks are:unrestricted-use stock (blank, F)stock in quality inspection (X, 2)blocked stock (S, 3)Select the corresponding indicator for the stock type required.It is due to earlier release levels that there are two valid values for each stock type. Each value has the same effect.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder storageBin(@Nullable String storageBin)
Original property name from the Odata EDM: StorageBin
A storage bin can be further sub-divided into bin sections. Several different materials (quants) can be stored in one bin at the same time.
identifies the exact location in the warehouse where goods can be stored.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder storageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
locations.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder storageType(@Nullable String storageType)
Original property name from the Odata EDM: StorageType
A typical warehouse could have the following storage types:Goods receipt areaPicking areaHigh-rack storage areaBulk storage areaOpen storage areaGoods issue area
identified by their warehousing technique, form of organization, or their function.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder subsequentMovementType(@Nullable String subsequentMovementType)
Original property name from the Odata EDM: SubsequentMovementType
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder transportationGroup(@Nullable String transportationGroup)
Original property name from the Odata EDM: TransportationGroup
Transportation groups are used for automatic route scheduling during sales order and delivery note processing.Suppose that you sell food products, some of which are perishable and require refrigeration. You create a transportation group that includes all the products that need refrigerated trucks for delivery.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder underdelivTolrtdLmtRatioInPct(@Nullable BigDecimal underdelivTolrtdLmtRatioInPct)
Original property name from the Odata EDM: UnderdelivTolrtdLmtRatioInPct
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder unlimitedOverdeliveryIsAllowed(@Nullable Boolean unlimitedOverdeliveryIsAllowed)
Original property name from the Odata EDM: UnlimitedOverdeliveryIsAllowed
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder varblShipgProcgDurationInDays(@Nullable BigDecimal varblShipgProcgDurationInDays)
Original property name from the Odata EDM: VarblShipgProcgDurationInDays
The system uses the variable during capacity planning for deliveries. The variable is determined from shipping information stored in the material master record. The system calculates the variable using the following formula:Variable = (Confirmed quantity x Processing time) divided by the base quantityYou specify in a material master record that the processing time for shipping the material is 1 hour (processing time) for every 100 pieces (the base quantity). During delivery processing, you ship a delivery item of 300 pieces (the confirmed quantity). In this example, the variable equals 3 hours.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder warehouse(@Nullable String warehouse)
Original property name from the Odata EDM: Warehouse
All activities within a warehouse, for example, goods movements and physical inventory, are assigned to a specific warehouse number. The physical warehouse where these activities take place is identified by the warehouse number.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder warehouseActivityStatus(@Nullable String warehouseActivityStatus)
Original property name from the Odata EDM: WarehouseActivityStatus
If your delivery processing includes the SAP Warehouse Management (WM) system, the system automatically indicates the WM status for each item in a delivery.
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder warehouseStagingArea(@Nullable String warehouseStagingArea)
Original property name from the Odata EDM: WarehouseStagingArea
Staging areas can be used for different purposes (at the same time, if necessary):o Goods issueo Goods receipto Cross-docking processeso Direct distribution
this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder warehouseStockCategory(@Nullable String warehouseStockCategory)
Original property name from the Odata EDM: WarehouseStockCategory
returned stock, and so on.this
.public ReturnsDeliveryItem.ReturnsDeliveryItemBuilder warehouseStorageBin(@Nullable String warehouseStorageBin)
Original property name from the Odata EDM: WarehouseStorageBin
This storage bin is only significant if you do not use SAP warehouse management. It appears on goods receipt/issue slips.However, if the warehouse management system is active, this value is merely for information.
this
.public ReturnsDeliveryItem build()
Copyright © 2020 SAP SE. All rights reserved.