public static final class CustomerReturnItem.CustomerReturnItemBuilder extends Object
Modifier and Type | Method and Description |
---|---|
CustomerReturnItem.CustomerReturnItemBuilder |
batch(String batch)
Constraints: Not nullable, Maximum length: 10
|
CustomerReturnItem |
build() |
CustomerReturnItem.CustomerReturnItemBuilder |
cRMLogicalSystem(String cRMLogicalSystem)
Constraints: Not nullable, Maximum length: 10
|
CustomerReturnItem.CustomerReturnItemBuilder |
cRMObjectID(String cRMObjectID)
Constraints: Not nullable, Maximum length: 10
|
CustomerReturnItem.CustomerReturnItemBuilder |
cRMObjectType(String cRMObjectType)
Constraints: Not nullable, Maximum length: 10
|
CustomerReturnItem.CustomerReturnItemBuilder |
cRMObjectUUID(String cRMObjectUUID)
Constraints: Not nullable, Maximum length: 32
|
CustomerReturnItem.CustomerReturnItemBuilder |
customerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
customerRetMatlInspResultCode(String customerRetMatlInspResultCode)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
customerReturn(CustomerReturn value)
Navigation property to_CustomerReturn for CustomerReturnItem to single CustomerReturn.
|
CustomerReturnItem.CustomerReturnItemBuilder |
customerReturn(String value)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
CustomerReturnItem.CustomerReturnItemBuilder |
customerReturnItem(String customerReturnItem)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
CustomerReturnItem.CustomerReturnItemBuilder |
customerReturnItemCategory(String customerReturnItemCategory)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
customerReturnItemText(String customerReturnItemText)
Constraints: Not nullable, Maximum length: 40
|
CustomerReturnItem.CustomerReturnItemBuilder |
custRetItmFollowUpActivity(String custRetItmFollowUpActivity)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
custRetMatlAuthzn(String custRetMatlAuthzn)
Constraints: Not nullable, Maximum length: 20
|
CustomerReturnItem.CustomerReturnItemBuilder |
deliveryPriority(String deliveryPriority)
Constraints: Not nullable, Maximum length: 2
|
CustomerReturnItem.CustomerReturnItemBuilder |
higherLevelItem(String higherLevelItem)
Constraints: Not nullable, Maximum length: 6
|
CustomerReturnItem.CustomerReturnItemBuilder |
incotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
incotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
CustomerReturnItem.CustomerReturnItemBuilder |
incotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
CustomerReturnItem.CustomerReturnItemBuilder |
incotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
CustomerReturnItem.CustomerReturnItemBuilder |
itemBillingBlockReason(String itemBillingBlockReason)
Constraints: Not nullable, Maximum length: 2
|
CustomerReturnItem.CustomerReturnItemBuilder |
itemGrossWeight(BigDecimal itemGrossWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
itemNetWeight(BigDecimal itemNetWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
itemVolume(BigDecimal itemVolume)
Constraints: Not nullable, Precision: 15, Scale: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
itemVolumeUnit(String itemVolumeUnit)
Constraints: Not nullable, Maximum length: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
itemWeightUnit(String itemWeightUnit)
Constraints: Not nullable, Maximum length: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
material(String material)
Constraints: Not nullable, Maximum length: 40
|
CustomerReturnItem.CustomerReturnItemBuilder |
materialByCustomer(String materialByCustomer)
Constraints: Not nullable, Maximum length: 35
|
CustomerReturnItem.CustomerReturnItemBuilder |
materialGroup(String materialGroup)
Constraints: Not nullable, Maximum length: 9
|
CustomerReturnItem.CustomerReturnItemBuilder |
netAmount(BigDecimal netAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
nextFllwUpActivityForMatlInsp(String nextFllwUpActivityForMatlInsp)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
nextPlantForFollowUpActivity(String nextPlantForFollowUpActivity)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
partner(CustomerReturnItemPartner... value)
Navigation property to_Partner for CustomerReturnItem to multiple
CustomerReturnItemPartner.
|
CustomerReturnItem.CustomerReturnItemBuilder |
prelimRefundIsDetermined(Boolean prelimRefundIsDetermined)
Constraints: none
|
CustomerReturnItem.CustomerReturnItemBuilder |
pricingElement(CustomerReturnItemPrcgElmnt... value)
Navigation property to_PricingElement for CustomerReturnItem to multiple
CustomerReturnItemPrcgElmnt.
|
CustomerReturnItem.CustomerReturnItemBuilder |
processStep(CustomerReturnProcessStep... value)
Navigation property to_ProcessStep for CustomerReturnItem to multiple
CustomerReturnProcessStep.
|
CustomerReturnItem.CustomerReturnItemBuilder |
productionPlant(String productionPlant)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
productIsInspectedAtCustSite(String productIsInspectedAtCustSite)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
purchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
CustomerReturnItem.CustomerReturnItemBuilder |
referenceSDDocument(String referenceSDDocument)
Constraints: Not nullable, Maximum length: 10
|
CustomerReturnItem.CustomerReturnItemBuilder |
referenceSDDocumentCategory(String referenceSDDocumentCategory)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
referenceSDDocumentItem(String referenceSDDocumentItem)
Constraints: Not nullable, Maximum length: 6
|
CustomerReturnItem.CustomerReturnItemBuilder |
replacementMaterial(String replacementMaterial)
Constraints: Not nullable, Maximum length: 40
|
CustomerReturnItem.CustomerReturnItemBuilder |
replacementMaterialIsRequested(Boolean replacementMaterialIsRequested)
Constraints: none
|
CustomerReturnItem.CustomerReturnItemBuilder |
replacementMaterialQtyUnit(String replacementMaterialQtyUnit)
Constraints: Not nullable, Maximum length: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
replacementMaterialQuantity(BigDecimal replacementMaterialQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
replacementMatlSupplyingPlant(String replacementMatlSupplyingPlant)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
requestedQuantity(BigDecimal requestedQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
requestedQuantityUnit(String requestedQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
retMatlInspResultCode(String retMatlInspResultCode)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
retsMgmtItmCompnProcgStatus(String retsMgmtItmCompnProcgStatus)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
retsMgmtItmLogProcgStatus(String retsMgmtItmLogProcgStatus)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
retsMgmtItmProcgStatus(String retsMgmtItmProcgStatus)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
retsMgmtProcess(String retsMgmtProcess)
Constraints: Not nullable, Maximum length: 10
|
CustomerReturnItem.CustomerReturnItemBuilder |
retsMgmtProcessingBlock(String retsMgmtProcessingBlock)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
retsMgmtProcessItem(String retsMgmtProcessItem)
Constraints: Not nullable, Maximum length: 6
|
CustomerReturnItem.CustomerReturnItemBuilder |
returnReason(String returnReason)
Constraints: Not nullable, Maximum length: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
returnsDocumentApprovalStatus(String returnsDocumentApprovalStatus)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
returnsDocumentStatus(String returnsDocumentStatus)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
returnsMaterialHasBeenReceived(Boolean returnsMaterialHasBeenReceived)
Constraints: none
|
CustomerReturnItem.CustomerReturnItemBuilder |
returnsRefundExtent(String returnsRefundExtent)
Constraints: Not nullable, Maximum length: 3
|
CustomerReturnItem.CustomerReturnItemBuilder |
returnsRefundProcgMode(String returnsRefundProcgMode)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
returnsRefundRjcnReason(String returnsRefundRjcnReason)
Constraints: Not nullable, Maximum length: 2
|
CustomerReturnItem.CustomerReturnItemBuilder |
returnsRefundType(String returnsRefundType)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
returnsTransshipmentPlant(String returnsTransshipmentPlant)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
salesDocumentRjcnReason(String salesDocumentRjcnReason)
Constraints: Not nullable, Maximum length: 2
|
CustomerReturnItem.CustomerReturnItemBuilder |
scheduleLine(CustomerReturnScheduleLine... value)
Navigation property to_ScheduleLine for CustomerReturnItem to multiple
CustomerReturnScheduleLine.
|
CustomerReturnItem.CustomerReturnItemBuilder |
sDDocumentRejectionStatus(String sDDocumentRejectionStatus)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
sDProcessStatus(String sDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
CustomerReturnItem.CustomerReturnItemBuilder |
shippingPoint(String shippingPoint)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
storageLocation(String storageLocation)
Constraints: Not nullable, Maximum length: 4
|
CustomerReturnItem.CustomerReturnItemBuilder |
suplrRetMatlAuthznIsRequired(Boolean suplrRetMatlAuthznIsRequired)
Constraints: none
|
CustomerReturnItem.CustomerReturnItemBuilder |
supplier(String supplier)
Constraints: Not nullable, Maximum length: 10
|
CustomerReturnItem.CustomerReturnItemBuilder |
supplierRetMatlAuthzn(String supplierRetMatlAuthzn)
Constraints: Not nullable, Maximum length: 20
|
String |
toString() |
CustomerReturnItem.CustomerReturnItemBuilder |
transactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
@Nonnull public CustomerReturnItem.CustomerReturnItemBuilder customerReturn(CustomerReturn value)
value
- The CustomerReturn to build this CustomerReturnItem with.@Nonnull public CustomerReturnItem.CustomerReturnItemBuilder customerReturn(String value)
Original property name from the Odata EDM: CustomerReturn
value
- The customerReturn to build this CustomerReturnItem with.@Nonnull public CustomerReturnItem.CustomerReturnItemBuilder partner(CustomerReturnItemPartner... value)
value
- The CustomerReturnItemPartners to build this CustomerReturnItem with.@Nonnull public CustomerReturnItem.CustomerReturnItemBuilder pricingElement(CustomerReturnItemPrcgElmnt... value)
value
- The CustomerReturnItemPrcgElmnts to build this CustomerReturnItem with.@Nonnull public CustomerReturnItem.CustomerReturnItemBuilder processStep(CustomerReturnProcessStep... value)
value
- The CustomerReturnProcessSteps to build this CustomerReturnItem with.@Nonnull public CustomerReturnItem.CustomerReturnItemBuilder scheduleLine(CustomerReturnScheduleLine... value)
value
- The CustomerReturnScheduleLines to build this CustomerReturnItem with.public CustomerReturnItem.CustomerReturnItemBuilder customerReturnItem(@Nullable String customerReturnItem)
Original property name from the Odata EDM: CustomerReturnItem
public CustomerReturnItem.CustomerReturnItemBuilder 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.
public CustomerReturnItem.CustomerReturnItemBuilder customerReturnItemCategory(@Nullable String customerReturnItemCategory)
Original property name from the Odata EDM: CustomerReturnItemCategory
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 CustomerReturnItem.CustomerReturnItemBuilder customerReturnItemText(@Nullable String customerReturnItemText)
Original property name from the Odata EDM: CustomerReturnItemText
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 CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
public CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder requestedQuantity(@Nullable BigDecimal requestedQuantity)
Original property name from the Odata EDM: RequestedQuantity
public CustomerReturnItem.CustomerReturnItemBuilder requestedQuantityUnit(@Nullable String requestedQuantityUnit)
Original property name from the Odata EDM: RequestedQuantityUnit
public CustomerReturnItem.CustomerReturnItemBuilder 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.public CustomerReturnItem.CustomerReturnItemBuilder 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.public CustomerReturnItem.CustomerReturnItemBuilder 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.
public CustomerReturnItem.CustomerReturnItemBuilder 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.
public CustomerReturnItem.CustomerReturnItemBuilder 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.
public CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder netAmount(@Nullable BigDecimal netAmount)
Original property name from the Odata EDM: NetAmount
included. The value is expressed in the document currency.public CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder batch(@Nullable String batch)
Original property name from the Odata EDM: Batch
public CustomerReturnItem.CustomerReturnItemBuilder productionPlant(@Nullable String productionPlant)
Original property name from the Odata EDM: ProductionPlant
public CustomerReturnItem.CustomerReturnItemBuilder storageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
locations.public CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder retsMgmtProcess(@Nullable String retsMgmtProcess)
Original property name from the Odata EDM: RetsMgmtProcess
public CustomerReturnItem.CustomerReturnItemBuilder retsMgmtProcessItem(@Nullable String retsMgmtProcessItem)
Original property name from the Odata EDM: RetsMgmtProcessItem
purchase order, or a returns stock transport order.public CustomerReturnItem.CustomerReturnItemBuilder returnReason(@Nullable String returnReason)
Original property name from the Odata EDM: ReturnReason
You enter the return reason in the returns order.
public CustomerReturnItem.CustomerReturnItemBuilder retsMgmtProcessingBlock(@Nullable String retsMgmtProcessingBlock)
Original property name from the Odata EDM: RetsMgmtProcessingBlock
The further processing of a returns order is blocked if the user who is creating or modifying the returns order is not authorized to do so for the receiving plant. The system sets the block to Blocked for Release.If the authorized user at the next receiving plant does not approve the order, he or she can set the blodk to Item to Be Revised.
public CustomerReturnItem.CustomerReturnItemBuilder custRetItmFollowUpActivity(@Nullable String custRetItmFollowUpActivity)
Original property name from the Odata EDM: CustRetItmFollowUpActivity
You use logistical follow-up activities to move returned materials to their final destination.
Management.public CustomerReturnItem.CustomerReturnItemBuilder returnsMaterialHasBeenReceived(@Nullable Boolean returnsMaterialHasBeenReceived)
Original property name from the Odata EDM: ReturnsMaterialHasBeenReceived
public CustomerReturnItem.CustomerReturnItemBuilder returnsRefundType(@Nullable String returnsRefundType)
Original property name from the Odata EDM: ReturnsRefundType
You can specify Credit Memo to give the customer monetary compensation or Replacement Material to replace the returned material by the same or another material.
public CustomerReturnItem.CustomerReturnItemBuilder returnsRefundProcgMode(@Nullable String returnsRefundProcgMode)
Original property name from the Odata EDM: ReturnsRefundProcgMode
public CustomerReturnItem.CustomerReturnItemBuilder returnsRefundExtent(@Nullable String returnsRefundExtent)
Original property name from the Odata EDM: ReturnsRefundExtent
The system can determine the returns refund code automatically from the combination of inspection code and return reason, but the user can also select it manually.You define a returns refund code R01 with description 10% reduction = 90% refund.If the item value of the original order item were 100 euros, then the customer would receive a credit memo for 90 euros.
public CustomerReturnItem.CustomerReturnItemBuilder prelimRefundIsDetermined(@Nullable Boolean prelimRefundIsDetermined)
Original property name from the Odata EDM: PrelimRefundIsDetermined
public CustomerReturnItem.CustomerReturnItemBuilder returnsRefundRjcnReason(@Nullable String returnsRefundRjcnReason)
Original property name from the Odata EDM: ReturnsRefundRjcnReason
public CustomerReturnItem.CustomerReturnItemBuilder replacementMaterial(@Nullable String replacementMaterial)
Original property name from the Odata EDM: ReplacementMaterial
The replacement material is usually identical to the returned material. You can, however, specify a different material as the replacement.
public CustomerReturnItem.CustomerReturnItemBuilder replacementMaterialQuantity(@Nullable BigDecimal replacementMaterialQuantity)
Original property name from the Odata EDM: ReplacementMaterialQuantity
Normally, when you decide to compensate a customer for a returned material with a replacement material, you would replace the entire returned quantity. However, you can also just replace part of the returned quantity if, for example, you do not have the full quantity on stock. You could then refund the customer for the remaining quantity with a credit memo.The customer returns 7 pieces of Material A. However, you only have 5 pieces of this material on stock. You decide to compensate the customer with these 5 pieces and create a credit memo request for the remaining 2 pieces. In this case, the value in both the Replaced Quantity field and the Replacement Quantity field is 5. You would then enter 2 in the CMR Quantity (Credit Memo Request Quantity) field so that the customer is compensated for the remaining 2 pieces.
process created in Advanced Returns Management.public CustomerReturnItem.CustomerReturnItemBuilder replacementMaterialQtyUnit(@Nullable String replacementMaterialQtyUnit)
Original property name from the Odata EDM: ReplacementMaterialQtyUnit
public CustomerReturnItem.CustomerReturnItemBuilder replacementMaterialIsRequested(@Nullable Boolean replacementMaterialIsRequested)
Original property name from the Odata EDM: ReplacementMaterialIsRequested
public CustomerReturnItem.CustomerReturnItemBuilder replacementMatlSupplyingPlant(@Nullable String replacementMatlSupplyingPlant)
Original property name from the Odata EDM: ReplacementMatlSupplyingPlant
public CustomerReturnItem.CustomerReturnItemBuilder nextPlantForFollowUpActivity(@Nullable String nextPlantForFollowUpActivity)
Original property name from the Odata EDM: NextPlantForFollowUpActivity
public CustomerReturnItem.CustomerReturnItemBuilder returnsTransshipmentPlant(@Nullable String returnsTransshipmentPlant)
Original property name from the Odata EDM: ReturnsTransshipmentPlant
Transshipment plants can thus be listed in delivery documents, but they are not considered for follow-up documents, such as returns stock transport orders or returns purchase orders.
plants or to a supplier.public CustomerReturnItem.CustomerReturnItemBuilder supplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
public CustomerReturnItem.CustomerReturnItemBuilder supplierRetMatlAuthzn(@Nullable String supplierRetMatlAuthzn)
Original property name from the Odata EDM: SupplierRetMatlAuthzn
You can enter the RMA in the following documents:Initial returns documentLogistical follow-upReturns purchase orderYou must enter an RMA at the latest in the returns purchase order before the goods can be issued and a delivery can be created.You only have to enter an RMA if the supplier master or purchasing info record indicates so.
public CustomerReturnItem.CustomerReturnItemBuilder suplrRetMatlAuthznIsRequired(@Nullable Boolean suplrRetMatlAuthznIsRequired)
Original property name from the Odata EDM: SuplrRetMatlAuthznIsRequired
public CustomerReturnItem.CustomerReturnItemBuilder customerRetMatlInspResultCode(@Nullable String customerRetMatlInspResultCode)
Original property name from the Odata EDM: CustomerRetMatlInspResultCode
When you create a return order for the relevant material, the customer inspection code and the corresponding inspection comment provide you with useful information for making the appropriate decisions regarding logistical follow-up activities and refunding.
which he or she wants to return the material about the quality of the material.public CustomerReturnItem.CustomerReturnItemBuilder nextFllwUpActivityForMatlInsp(@Nullable String nextFllwUpActivityForMatlInsp)
Original property name from the Odata EDM: NextFllwUpActivityForMatlInsp
In the Next Follow-Up Activity field, you define a default value in the returns order for the next logistical processing step for the material inspection in the warehouse. When you call the Material Inspection in Warehouse transaction, the system proposes the value you entered here in the Follow-Up Activity field for the relevant item of the returns delivery. However, the inspector can overwrite this value if necessary.You would typically define a next follow-up activity if you have chosen the follow-up activity 0001 Receive into Plant in the returns order.You cannot enter any relevant parameters for the next follow-up activity entered in this field, such as the supplier for the next follow-up activity 0005 Ship to Supplier. You enter the relevant parameters in the material inspection.Note the following special cases for setting the default value in material inspection:Even if you have not selected the Material Received checkbox (because the customer contacted your company by phone, for example), you can still choose 0004 Ship to Other Plant, 0005 Ship to Supplier, or 0006 Ship to Supplier via Other Plant as the Follow-Up Activity.In this case, the system copies the value entered for the logistical follow-up activity to the material inspection as the default value. This enables you to enter the relevant parameters for the follow-up activity in the returns order, such as the supplier or the next plant, which are then copied to the appropriate fields in the material inspection.For a store return, if you choose 0004 Ship to Other Plant as the Follow-Up Activity in the returns order and also select the Material Received checkbox, the system uses this as the default value for the material inspection in the warehouse of the receiving plant.The system ignores the value in the Next Follow-Up Activity field if the entry does not make sense for the process flow defined by the logistical follow-up activity. This applies to immediate goods receipts, for example, that is if you choose 0002 Immediately Move to Free Available Stock or 0003 Immediately Move to Scrap, since the logistical process is then already completed. If you choose 0004 Ship to Other Plant, 0005 Ship to Supplier, or 0006 Ship to Supplier via Other Plant as the Follow-Up Activity, the system ignores any entry you make in the Next Follow-Up Activity field.In the Customizing activity Activate and Rename Follow-Up Activities, you can replace the standard descriptions with your own.According to the customer on the phone, the material is still originally packaged. When you create the returns order for the relevant material, you specify Transfer to Free Available Stock as the next logistical follow-up activity for the returns order item. After the material has arrived at your company and the inspector performs the Material Inspection transaction, the system uses Transfer to Free Available Stock as the default in the logistical follow-up field.
default in the Material Inspection in Warehouse transaction as part of Advanced Returns Management.public CustomerReturnItem.CustomerReturnItemBuilder retMatlInspResultCode(@Nullable String retMatlInspResultCode)
Original property name from the Odata EDM: RetMatlInspResultCode
public CustomerReturnItem.CustomerReturnItemBuilder productIsInspectedAtCustSite(@Nullable String productIsInspectedAtCustSite)
Original property name from the Odata EDM: ProductIsInspectedAtCustSite
public CustomerReturnItem.CustomerReturnItemBuilder custRetMatlAuthzn(@Nullable String custRetMatlAuthzn)
Original property name from the Odata EDM: CustRetMatlAuthzn
public CustomerReturnItem.CustomerReturnItemBuilder cRMLogicalSystem(@Nullable String cRMLogicalSystem)
Original property name from the Odata EDM: CRMLogicalSystem
public CustomerReturnItem.CustomerReturnItemBuilder cRMObjectUUID(@Nullable String cRMObjectUUID)
Original property name from the Odata EDM: CRMObjectUUID
public CustomerReturnItem.CustomerReturnItemBuilder cRMObjectID(@Nullable String cRMObjectID)
Original property name from the Odata EDM: CRMObjectID
public CustomerReturnItem.CustomerReturnItemBuilder cRMObjectType(@Nullable String cRMObjectType)
Original property name from the Odata EDM: CRMObjectType
public CustomerReturnItem.CustomerReturnItemBuilder retsMgmtItmLogProcgStatus(@Nullable String retsMgmtItmLogProcgStatus)
Original property name from the Odata EDM: RetsMgmtItmLogProcgStatus
public CustomerReturnItem.CustomerReturnItemBuilder retsMgmtItmCompnProcgStatus(@Nullable String retsMgmtItmCompnProcgStatus)
Original property name from the Odata EDM: RetsMgmtItmCompnProcgStatus
When selecting the refunding status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is not fully credited.Select Error if you want to select items that have at least one partial process that contains an error in a financial document.Select Completed if you want to select items for which all partial processes are fully credited.The selection criteria Process Status and Logistical Status also apply.A process item is only selected if it fulfills ALL status criteria.
quantities of a returns item are fully credited; otherwise refunding is open.public CustomerReturnItem.CustomerReturnItemBuilder retsMgmtItmProcgStatus(@Nullable String retsMgmtItmProcgStatus)
Original property name from the Odata EDM: RetsMgmtItmProcgStatus
The process can be completed, open, or can contain errors.When selecting the process status on the Returns Overview screen, you have the following options:Select Open if you want to select items that have at least one partial process that is open.Select Error if you want to select items that have at least one partial process that contains an error.Select Completed if you want to select items for which all partial processes are completed.
public CustomerReturnItem.CustomerReturnItemBuilder returnsDocumentStatus(@Nullable String returnsDocumentStatus)
Original property name from the Odata EDM: ReturnsDocumentStatus
A document item can have the following statuses:ActiveThe document item has been created without errors.Deletion Flag SetThe document item has been deleted.Document Was CancelledThe document item has been cancelled and a corresponding reversal or cancellation document exists.Reversal (Cancellation) DocumentThis is a cancellation or reversal document and a corresponding cancelled document exists.
public CustomerReturnItem.CustomerReturnItemBuilder returnsDocumentApprovalStatus(@Nullable String returnsDocumentApprovalStatus)
Original property name from the Odata EDM: ReturnsDocumentApprovalStatus
public CustomerReturnItem.CustomerReturnItemBuilder 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 CustomerReturnItem.CustomerReturnItemBuilder referenceSDDocument(@Nullable String referenceSDDocument)
Original property name from the Odata EDM: ReferenceSDDocument
public CustomerReturnItem.CustomerReturnItemBuilder referenceSDDocumentItem(@Nullable String referenceSDDocumentItem)
Original property name from the Odata EDM: ReferenceSDDocumentItem
public CustomerReturnItem.CustomerReturnItemBuilder referenceSDDocumentCategory(@Nullable String referenceSDDocumentCategory)
Original property name from the Odata EDM: ReferenceSDDocumentCategory
public CustomerReturnItem.CustomerReturnItemBuilder sDDocumentRejectionStatus(@Nullable String sDDocumentRejectionStatus)
Original property name from the Odata EDM: SDDocumentRejectionStatus
The system uses the rejection status of items to determine the rejection status at the header level. For example, if a customer rejects only one of several items in a quotation, the status of the header shows that the quotation is partly rejected.
public CustomerReturnItem build()
Copyright © 2019 SAP SE. All rights reserved.