public static final class MaterialDocumentItem.MaterialDocumentItemBuilder extends Object
@Nonnull public MaterialDocumentItem.MaterialDocumentItemBuilder materialDocumentHeader(MaterialDocumentHeader value)
value - The MaterialDocumentHeader to build this MaterialDocumentItem with.public MaterialDocumentItem.MaterialDocumentItemBuilder materialDocumentYear(@Nullable String materialDocumentYear)
Original property name from the Odata EDM: MaterialDocumentYear
public MaterialDocumentItem.MaterialDocumentItemBuilder materialDocument(@Nullable String materialDocument)
Original property name from the Odata EDM: MaterialDocument
Number of the material document with which a goods movement was posted.Together with the material document year, the document number constitutes the key via which a material document is accessed.
public MaterialDocumentItem.MaterialDocumentItemBuilder materialDocumentItem(@Nullable String materialDocumentItem)
Original property name from the Odata EDM: MaterialDocumentItem
public MaterialDocumentItem.MaterialDocumentItemBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
public MaterialDocumentItem.MaterialDocumentItemBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
public MaterialDocumentItem.MaterialDocumentItemBuilder storageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
locations.public MaterialDocumentItem.MaterialDocumentItemBuilder batch(@Nullable String batch)
Original property name from the Odata EDM: Batch
public MaterialDocumentItem.MaterialDocumentItemBuilder goodsMovementType(@Nullable String goodsMovementType)
Original property name from the Odata EDM: GoodsMovementType
warehouse) is allocated to a movement type in the system.public MaterialDocumentItem.MaterialDocumentItemBuilder inventoryStockType(@Nullable String inventoryStockType)
Original property name from the Odata EDM: InventoryStockType
NoteThe system determines the stock on the basis of stock identifiers.The following keys are possible for this field:01: Unrestricted-Use Stock02: Stock in Quality Inspection03: Returns04: Stock Transfer (Storage Location)05: Stock Transfer (Plant)06: Stock in Transit07: Blocked Stock08: Restricted-Use Stock09: Tied Empties10: Valuated Goods Receipt Blocked Stock
public MaterialDocumentItem.MaterialDocumentItemBuilder 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.
public MaterialDocumentItem.MaterialDocumentItemBuilder inventorySpecialStockType(@Nullable String inventorySpecialStockType)
Original property name from the Odata EDM: InventorySpecialStockType
public MaterialDocumentItem.MaterialDocumentItemBuilder supplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
With the supplier number, information from the supplier master record (such as the supplier's address and bank details) is copied into a purchasing document (such as a request for quotation or a purchase order).You can use the supplier number to keep track of requests for quotation, purchase orders and outline agreements.
public MaterialDocumentItem.MaterialDocumentItemBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
This customer number is used for managing customer special stocks.
public MaterialDocumentItem.MaterialDocumentItemBuilder salesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
The selection of postprocessing records via the sales order number is only possible for non-valuated sales order stock.
public MaterialDocumentItem.MaterialDocumentItemBuilder salesOrderItem(@Nullable String salesOrderItem)
Original property name from the Odata EDM: SalesOrderItem
public MaterialDocumentItem.MaterialDocumentItemBuilder salesOrderScheduleLine(@Nullable String salesOrderScheduleLine)
Original property name from the Odata EDM: SalesOrderScheduleLine
public MaterialDocumentItem.MaterialDocumentItemBuilder purchaseOrder(@Nullable String purchaseOrder)
Original property name from the Odata EDM: PurchaseOrder
1Number of the purchase order to which the entry of services performed relates.
public MaterialDocumentItem.MaterialDocumentItemBuilder purchaseOrderItem(@Nullable String purchaseOrderItem)
Original property name from the Odata EDM: PurchaseOrderItem
public MaterialDocumentItem.MaterialDocumentItemBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
public MaterialDocumentItem.MaterialDocumentItemBuilder manufacturingOrder(@Nullable String manufacturingOrder)
Original property name from the Odata EDM: ManufacturingOrder
public MaterialDocumentItem.MaterialDocumentItemBuilder manufacturingOrderItem(@Nullable String manufacturingOrderItem)
Original property name from the Odata EDM: ManufacturingOrderItem
public MaterialDocumentItem.MaterialDocumentItemBuilder goodsMovementRefDocType(@Nullable String goodsMovementRefDocType)
Original property name from the Odata EDM: GoodsMovementRefDocType
public MaterialDocumentItem.MaterialDocumentItemBuilder goodsMovementReasonCode(@Nullable String goodsMovementReasonCode)
Original property name from the Odata EDM: GoodsMovementReasonCode
example, reason for a return delivery).public MaterialDocumentItem.MaterialDocumentItemBuilder accountAssignmentCategory(@Nullable String accountAssignmentCategory)
Original property name from the Odata EDM: AccountAssignmentCategory
public MaterialDocumentItem.MaterialDocumentItemBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
public MaterialDocumentItem.MaterialDocumentItemBuilder 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.
public MaterialDocumentItem.MaterialDocumentItemBuilder costObject(@Nullable String costObject)
Original property name from the Odata EDM: CostObject
Cost objects are the activity units of business whose costs are assigned based on the cost origins. The R/3 System distinguishes between the following types of cost objects:Cost objects represented by a cost object IDCost objects represented by objects from other components, such as production orders or sales order itemsCost objects in the following areas are represented by cost object IDs:Activity-Based Costing (CO-OM-ABC)In Activity-Based Costing, overhead is first assigned to cost centers and then to business processes. From there, the overhead is assigned to cost objects as process costs.Costs for Intangible Goods and Services (CO-PC-OBJ)In Costs for Intangible Goods and Services, costs can be analyzed on general cost objects.Product Cost by Period (CO-PC-OBJ)In Product Cost by Period you can create a cost object hierarchy to record actual costs that cannot be recorded at the material or order level. You can distribute the costs assigned to the nodes of a cost object hierarchy directly to the individual objects in the lowest cost object nodes at period-end closing (for example, product cost collectors) or you can settle the costs directly from the cost object hierarchy to a price difference account.Product Cost Controlling Information System (CO-PC)You can create further cost object IDs in the Product Cost Controlling Information System for CO product groups. You can create a cost object ID for each group, and assign materials to the cost object ID. The costs of the assigned materials appear in summarized form in the information system by product group.You can use CO product groups for product drilldown reports.The cost object type determines which functions can be used with the cost object. Functions for cost object hierarchies are performed on the assumption that the given cost object indicates the top node of the hierarchy.
public MaterialDocumentItem.MaterialDocumentItemBuilder profitabilitySegment(@Nullable String profitabilitySegment)
Original property name from the Odata EDM: ProfitabilitySegment
public MaterialDocumentItem.MaterialDocumentItemBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
public MaterialDocumentItem.MaterialDocumentItemBuilder gLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
public MaterialDocumentItem.MaterialDocumentItemBuilder functionalArea(@Nullable String functionalArea)
Original property name from the Odata EDM: FunctionalArea
Use for Cost-of-Sales AccountingThe functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting. The following are examples of structure criteria:ManufacturingAdministrationSalesResearch and developmentUse for GovernmentThe functional area is needed for Funds Management to meet legal requirements for reporting with functional aspects. You can use the functional area to represent the global targets and goals (such as public safety or city development), in particular the expenses of your organization.Use in cost-of-sales accountingSee the documentation on Filling the Functional Area Field.For comprehensive information on cost-of-sales accounting and on the functional area, see the SAP Library under Accounting -> Financial Accounting -> General Ledger -> Cost-of-Sales Accounting.Use in governmentFor more information on the functional area, see the implementation Guide for Funds Management Government in the section Activate Account Assignment Elements.
public MaterialDocumentItem.MaterialDocumentItemBuilder materialBaseUnit(@Nullable String materialBaseUnit)
Original property name from the Odata EDM: MaterialBaseUnit
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.public MaterialDocumentItem.MaterialDocumentItemBuilder quantityInBaseUnit(@Nullable BigDecimal quantityInBaseUnit)
Original property name from the Odata EDM: QuantityInBaseUnit
The quantity entered determines which portion of the costs you wish to distribute to this account assignment item.
public MaterialDocumentItem.MaterialDocumentItemBuilder entryUnit(@Nullable String entryUnit)
Original property name from the Odata EDM: EntryUnit
Enter a unit of measure here only if it differs from the default unit of measure.There are the following default units of measure:the order unit for goods receipts with reference to purchase ordersthe production unit for goods receipts with reference to production ordersthe unit of issue for other goods movementsIf the default unit of measure has not been defined in the material master record, the system will suggest the stockkeeping unit.
public MaterialDocumentItem.MaterialDocumentItemBuilder quantityInEntryUnit(@Nullable BigDecimal quantityInEntryUnit)
Original property name from the Odata EDM: QuantityInEntryUnit
Enter the quantity to be moved in any unit of measure for the material.If the relevant unit of measure has not been defined in the material master record, the system uses the stockkeeping unit.If you do not enter a unit of measure, the system uses the following units of measure:order unit in goods receipts against purchase ordersproduction unit in goods receipts against production ordersunit of issue in other goods movements
stockkeeping unit (base unit of measure).public MaterialDocumentItem.MaterialDocumentItemBuilder companyCodeCurrency(@Nullable String companyCodeCurrency)
Original property name from the Odata EDM: CompanyCodeCurrency
public MaterialDocumentItem.MaterialDocumentItemBuilder gdsMvtExtAmtInCoCodeCrcy(@Nullable BigDecimal gdsMvtExtAmtInCoCodeCrcy)
Original property name from the Odata EDM: GdsMvtExtAmtInCoCodeCrcy
The value of the movement is calculated automatically by the system. However, it is possible to enter an amount manually if the item is to be valuated at a different price.
public MaterialDocumentItem.MaterialDocumentItemBuilder slsPrcAmtInclVATInCoCodeCrcy(@Nullable BigDecimal slsPrcAmtInclVATInCoCodeCrcy)
Original property name from the Odata EDM: SlsPrcAmtInclVATInCoCodeCrcy
public MaterialDocumentItem.MaterialDocumentItemBuilder fiscalYear(@Nullable String fiscalYear)
Original property name from the Odata EDM: FiscalYear
fiscal year can be the same as the calendar year, but does not have to be.public MaterialDocumentItem.MaterialDocumentItemBuilder fiscalYearPeriod(@Nullable String fiscalYearPeriod)
Original property name from the Odata EDM: FiscalYearPeriod
public MaterialDocumentItem.MaterialDocumentItemBuilder fiscalYearVariant(@Nullable String fiscalYearVariant)
Original property name from the Odata EDM: FiscalYearVariant
You can define the following using a fiscal year variant:How many posting periods are in a fiscal yearHow many special periods you requireHow the system determines the posting periods when postingIn the definition, you allocate your posting periods to the calendar year.Allocation control requires the same number of posting periods in the company code and in the assigned controlling area.This means that the number of posting periods in the fiscal year variants must be the same in the company code and in the controlling area. The period limits for the two fiscal year variants must also coincide.You must define which fiscal year variant is to be used for each company code. To do this, you must define the appropriate fiscal year variant. It must contain no more than 16 periods.Note:The company codes delivered with the standard system are allocated to the fiscal year variant that corresponds to the calendar year and which also uses four special periods.You define fiscal year variants as well as the allocation of fiscal year variant to the company code in Financial Accounting customizing.
public MaterialDocumentItem.MaterialDocumentItemBuilder issgOrRcvgMaterial(@Nullable String issgOrRcvgMaterial)
Original property name from the Odata EDM: IssgOrRcvgMaterial
public MaterialDocumentItem.MaterialDocumentItemBuilder issgOrRcvgBatch(@Nullable String issgOrRcvgBatch)
Original property name from the Odata EDM: IssgOrRcvgBatch
public MaterialDocumentItem.MaterialDocumentItemBuilder issuingOrReceivingPlant(@Nullable String issuingOrReceivingPlant)
Original property name from the Odata EDM: IssuingOrReceivingPlant
public MaterialDocumentItem.MaterialDocumentItemBuilder 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.
public MaterialDocumentItem.MaterialDocumentItemBuilder issuingOrReceivingStockType(@Nullable String issuingOrReceivingStockType)
Original property name from the Odata EDM: IssuingOrReceivingStockType
public MaterialDocumentItem.MaterialDocumentItemBuilder issgOrRcvgSpclStockInd(@Nullable String issgOrRcvgSpclStockInd)
Original property name from the Odata EDM: IssgOrRcvgSpclStockInd
public MaterialDocumentItem.MaterialDocumentItemBuilder issuingOrReceivingValType(@Nullable String issuingOrReceivingValType)
Original property name from the Odata EDM: IssuingOrReceivingValType
same material) to permit stocks of a transfer batch to be differentiated according to different criteria.public MaterialDocumentItem.MaterialDocumentItemBuilder isCompletelyDelivered(@Nullable Boolean isCompletelyDelivered)
Original property name from the Odata EDM: IsCompletelyDelivered
public MaterialDocumentItem.MaterialDocumentItemBuilder materialDocumentItemText(@Nullable String materialDocumentItemText)
Original property name from the Odata EDM: MaterialDocumentItemText
Line item texts can be used internally and externally. To be able to distinguish between these, you must begin texts for external use with "*". These texts can then be printed on all correspondence, dunning notices, payment advice notes, etc. The asterisk is removed when the text is printed.This function is only available in the FI component. It cannot be used in Materials Management.
public MaterialDocumentItem.MaterialDocumentItemBuilder unloadingPointName(@Nullable String unloadingPointName)
Original property name from the Odata EDM: UnloadingPointName
public MaterialDocumentItem.MaterialDocumentItemBuilder 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.
public MaterialDocumentItem.MaterialDocumentItemBuilder manufactureDate(@Nullable LocalDateTime manufactureDate)
Original property name from the Odata EDM: ManufactureDate
public MaterialDocumentItem.MaterialDocumentItemBuilder reservation(@Nullable String reservation)
Original property name from the Odata EDM: Reservation
public MaterialDocumentItem.MaterialDocumentItemBuilder reservationItem(@Nullable String reservationItem)
Original property name from the Odata EDM: ReservationItem
public MaterialDocumentItem.MaterialDocumentItemBuilder reservationIsFinallyIssued(@Nullable Boolean reservationIsFinallyIssued)
Original property name from the Odata EDM: ReservationIsFinallyIssued
public MaterialDocumentItem.MaterialDocumentItemBuilder specialStockIdfgSalesOrder(@Nullable String specialStockIdfgSalesOrder)
Original property name from the Odata EDM: SpecialStockIdfgSalesOrder
public MaterialDocumentItem.MaterialDocumentItemBuilder specialStockIdfgSalesOrderItem(@Nullable String specialStockIdfgSalesOrderItem)
Original property name from the Odata EDM: SpecialStockIdfgSalesOrderItem
public MaterialDocumentItem.MaterialDocumentItemBuilder specialStockIdfgWBSElement(@Nullable String specialStockIdfgWBSElement)
Original property name from the Odata EDM: SpecialStockIdfgWBSElement
public MaterialDocumentItem.MaterialDocumentItemBuilder isAutomaticallyCreated(@Nullable String isAutomaticallyCreated)
Original property name from the Odata EDM: IsAutomaticallyCreated
public MaterialDocumentItem.MaterialDocumentItemBuilder materialDocumentLine(@Nullable String materialDocumentLine)
Original property name from the Odata EDM: MaterialDocumentLine
public MaterialDocumentItem.MaterialDocumentItemBuilder materialDocumentParentLine(@Nullable String materialDocumentParentLine)
Original property name from the Odata EDM: MaterialDocumentParentLine
Lines that do not contain an initial value in this field may be, for example:Components of a subcontracting itemAutomatic lines for a stock transferEmpties items for the full productAt present we do not plan to fill this field in the interface structure IMSEG (except if it is called up in MM-IM). Filling the field would cause an error.Documentation of the data elements MB_LINE_ID and MB_LINE_DEPTH.WarningThis indicator is used for internal program control.Please do not change the entry in this field.Any changes made could lead to program errors or terminations.
public MaterialDocumentItem.MaterialDocumentItemBuilder hierarchyNodeLevel(@Nullable String hierarchyNodeLevel)
Original property name from the Odata EDM: HierarchyNodeLevel
Documentation of data elements MB_LINE_ID and MB_PARENT_ID.WarningThis indicator is used for internal program control.Please do not change the entry in this field.Any changes made could lead to program errors or terminations.
an automatically created line of the same level (for example, for stock transfers of a full product).public MaterialDocumentItem.MaterialDocumentItemBuilder goodsMovementIsCancelled(@Nullable Boolean goodsMovementIsCancelled)
Original property name from the Odata EDM: GoodsMovementIsCancelled
public MaterialDocumentItem.MaterialDocumentItemBuilder reversedMaterialDocumentYear(@Nullable String reversedMaterialDocumentYear)
Original property name from the Odata EDM: ReversedMaterialDocumentYear
public MaterialDocumentItem.MaterialDocumentItemBuilder reversedMaterialDocument(@Nullable String reversedMaterialDocument)
Original property name from the Odata EDM: ReversedMaterialDocument
public MaterialDocumentItem.MaterialDocumentItemBuilder reversedMaterialDocumentItem(@Nullable String reversedMaterialDocumentItem)
Original property name from the Odata EDM: ReversedMaterialDocumentItem
public MaterialDocumentItem build()
Copyright © 2019 SAP SE. All rights reserved.