public static class CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder extends Object
public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder centralPurchaseContract(@Nullable String centralPurchaseContract)
Original property name from the Odata EDM: CentralPurchaseContract
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder centralPurchaseContractItem(@Nullable String centralPurchaseContractItem)
Original property name from the Odata EDM: CentralPurchaseContractItem
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder distributionKey(@Nullable String distributionKey)
Original property name from the Odata EDM: DistributionKey
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder procmtHubCompanyCode(@Nullable String procmtHubCompanyCode)
Original property name from the Odata EDM: ProcmtHubCompanyCode
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder procmtHubPlant(@Nullable String procmtHubPlant)
Original property name from the Odata EDM: ProcmtHubPlant
You use the plant key to determine, for instance, which plant is to receive ordered goods.
code).this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder procmtHubPurchasingOrg(@Nullable String procmtHubPurchasingOrg)
Original property name from the Odata EDM: ProcmtHubPurchasingOrg
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder procmtHubPurchasingGroup(@Nullable String procmtHubPurchasingGroup)
Original property name from the Odata EDM: ProcmtHubPurchasingGroup
Frequently, purchasing documents (such as purchase orders) are monitored by the purchasing group. Urging letters (in the case of overdue deliveries) fall also within the group's scope of activities.For each purchasing group, statistical analyses can be performed. The purchasing group can be used as a sort criterion when creating purchasing-specific reports.
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder cntrlPurContrDistrCurrency(@Nullable String cntrlPurContrDistrCurrency)
Original property name from the Odata EDM: CntrlPurContrDistrCurrency
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder paymentTerms(@Nullable String paymentTerms)
Original property name from the Odata EDM: PaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder cashDiscount1Days(@Nullable BigDecimal cashDiscount1Days)
Original property name from the Odata EDM: CashDiscount1Days
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder cashDiscount2Days(@Nullable BigDecimal cashDiscount2Days)
Original property name from the Odata EDM: CashDiscount2Days
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder netPaymentDays(@Nullable BigDecimal netPaymentDays)
Original property name from the Odata EDM: NetPaymentDays
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder cashDiscount1Percent(@Nullable BigDecimal cashDiscount1Percent)
Original property name from the Odata EDM: CashDiscount1Percent
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder cashDiscount2Percent(@Nullable BigDecimal cashDiscount2Percent)
Original property name from the Odata EDM: CashDiscount2Percent
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder distributionType(@Nullable String distributionType)
Original property name from the Odata EDM: DistributionType
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder externalReferenceDocument(@Nullable String externalReferenceDocument)
Original property name from the Odata EDM: ExternalReferenceDocument
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder externalReferenceDocumentItem(@Nullable String externalReferenceDocumentItem)
Original property name from the Odata EDM: ExternalReferenceDocumentItem
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder externalRefDocCategory(@Nullable String externalRefDocCategory)
Original property name from the Odata EDM: ExternalRefDocCategory
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder purchasingDocumentCategory(@Nullable String purchasingDocumentCategory)
Original property name from the Odata EDM: PurchasingDocumentCategory
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder purchasingDocumentType(@Nullable String purchasingDocumentType)
Original property name from the Odata EDM: PurchasingDocumentType
On the basis of the purchasing document type, you can, for example, distinguish between a purchase order, an RFQ and a scheduling agreement.The purchasing document type controls, for instance, the number assignment of a purchase order, as well as the selection of the fields to be maintained.
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder storageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
locations.this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder cntrlPurContrDistributionPct(@Nullable BigDecimal cntrlPurContrDistributionPct)
Original property name from the Odata EDM: CntrlPurContrDistributionPct
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder cntrlPurContrItmDistrQty(@Nullable BigDecimal cntrlPurContrItmDistrQty)
Original property name from the Odata EDM: CntrlPurContrItmDistrQty
agreement (contract or scheduling agreement).this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder cntrlPurContrItmDistrAmt(@Nullable BigDecimal cntrlPurContrItmDistrAmt)
Original property name from the Odata EDM: CntrlPurContrItmDistrAmt
You specify this value manually for each distribution at header level of the central contract.If the specified value is exceeded, the user sees a message when creating the contract release order.
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder procurementHubSourceSystem(@Nullable String procurementHubSourceSystem)
Original property name from the Odata EDM: ProcurementHubSourceSystem
The distribution of data between systems requires that each system in the network has a unique identification. Logical systems are used for this purpose.In SAP terms, the client refers to a logical system. You can specify which logical system is a client in the Client Maintenance (choose Goto -> Details).The logical system is relevant for the following SAP areas:ALE general: Communication takes place between two or more logical systems.ALE Business Processes (for example, Cost Center Accounting): Definition of the system in which a given application runs. Changes such as those to master data can only be made in this system.Workflow objects: The key of a workflow object always contains the logical system in which the object is located.When defining the logical system keep in mind the following:The logical system must be unique enterprise-wide. It must not be used by any other system in the ALE System group.The logical system must not be changed in the production system. If the logical system of a document reference is not set to initial and does not match your own, the system assumes that the document must be located on another system.
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder procmtHubProduct(@Nullable String procmtHubProduct)
Original property name from the Odata EDM: ProcmtHubProduct
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder procmtHubProductGroup(@Nullable String procmtHubProductGroup)
Original property name from the Odata EDM: ProcmtHubProductGroup
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 CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder procmtHubPurchaseContract(@Nullable String procmtHubPurchaseContract)
Original property name from the Odata EDM: ProcmtHubPurchaseContract
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder procmtHubPurchaseContractItem(@Nullable String procmtHubPurchaseContractItem)
Original property name from the Odata EDM: ProcmtHubPurchaseContractItem
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder itemDistributionStatus(@Nullable String itemDistributionStatus)
Original property name from the Odata EDM: ItemDistributionStatus
this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder isDeleted(@Nullable String isDeleted)
Original property name from the Odata EDM: IsDeleted
Each time you enter OR, you create a query that is independent of other queries. Use AND to connect queries.this
.public CntrlPurContrItmDistribution.CntrlPurContrItmDistributionBuilder purchasingInfoRecordUpdateCode(@Nullable String purchasingInfoRecordUpdateCode)
Original property name from the Odata EDM: PurchasingInfoRecordUpdateCode
The purchasing info record for this supplier and material is to refer to this PO item, andThe item is to be valid for the entire purchasing organization or just for the plant.The indicator determines which prices and conditions are suggested in future PO items.Prices and conditions can apply to an entire purchasing organization or to a single plant within a purchasing organization.For example, if you create a purchase order for a plant for which an info record has been defined at plant level, the purchase order is based on the conditions in the plant info record and not on the conditions that apply to the purchasing organization.Enter the relevant plant key:AUpdating of the document number is effected at plant level as long as there is a purchasing info record at plant level. Otherwise the document number is updated at purchasing organization level.BUpdating is effected at plant level if plant conditions are allowed for the plant.CUpdating is effected without plant data if plant conditions are not necessary for the plant.The level at which updating of the document number may be effected is defined for each plant.
this
.public CntrlPurContrItmDistribution build()
Copyright © 2020 SAP SE. All rights reserved.