public static class CntrlPurContrHeaderPartner.CntrlPurContrHeaderPartnerBuilder extends Object
@Nonnull public CntrlPurContrHeaderPartner.CntrlPurContrHeaderPartnerBuilder centralPurchaseContract(@Nullable String centralPurchaseContract)
Original property name from the Odata EDM: CentralPurchaseContract
this
.@Nonnull public CntrlPurContrHeaderPartner.CntrlPurContrHeaderPartnerBuilder distributionKey(@Nullable String distributionKey)
Original property name from the Odata EDM: DistributionKey
this
.@Nonnull public CntrlPurContrHeaderPartner.CntrlPurContrHeaderPartnerBuilder partnerCounter(@Nullable String partnerCounter)
Original property name from the Odata EDM: PartnerCounter
When you create a sales order for a particular customer, there may be more than one ship-to party defined. The different ship-to parties are numbered sequentially.
partner function.this
.@Nonnull public CntrlPurContrHeaderPartner.CntrlPurContrHeaderPartnerBuilder partnerFunction(@Nullable String partnerFunction)
Original property name from the Odata EDM: PartnerFunction
Enter the original German key of the partner function for which you want to provide a language-specific key.The customer who orders goods, the sold-to party, is called the "Auftraggeber" in the German system. The original German key is "AG". You could, for example, convert this to an English key: "SP".
language-specific keys. The converted keys then appear according to the language in which the user logs on.this
.@Nonnull public CntrlPurContrHeaderPartner.CntrlPurContrHeaderPartnerBuilder extPlantForPurg(@Nullable String extPlantForPurg)
Original property name from the Odata EDM: ExtPlantForPurg
this
.@Nonnull public CntrlPurContrHeaderPartner.CntrlPurContrHeaderPartnerBuilder supplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
this
.@Nonnull public CntrlPurContrHeaderPartner.CntrlPurContrHeaderPartnerBuilder supplierSubrange(@Nullable String supplierSubrange)
Original property name from the Odata EDM: SupplierSubrange
For each supplier sub-range:The master data is kept on a common basisCertain conditions applyIn the supplier master, you can create different purchasing data and different partner functions for each supplier sub-range.You can also maintain and change the conditions for each supplier sub-range. You assign a material to a supplier sub-range in the info record.In the supplier master, you can maintain different data for particular supplier sub-ranges, such as ordering addresses or terms of payment, for example.When creating a purchase order with a known supplier, different data is only determined if the supplier sub-range is entered in the initial screen.Your supplier Smith in Houston has two sub-ranges: paint and glue.All materials from the "paint" sub-range are ordered in Houston.You have maintained an alternative ordering address in Detroit for the "glue" sub-range.If you order materials from the "glue" sub-range, the supplier sub-range finds the Detroit ordering address.
this
.@Nonnull public CntrlPurContrHeaderPartner.CntrlPurContrHeaderPartnerBuilder purchasingOrganization(@Nullable String purchasingOrganization)
Original property name from the Odata EDM: PurchasingOrganization
this
.@Nonnull public CntrlPurContrHeaderPartner build()
Copyright © 2021 SAP SE. All rights reserved.