public static final class PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder extends Object
@Nonnull public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder purgPrcgCndnRecdSuplmnt(PurgPrcgCndnRecdSuplmnt... value)
value - The PurgPrcgCndnRecdSuplmnts to build this PurgPrcgCndnRecdValidity with.@Nonnull public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder purgPrcgConditionRecord(PurgPrcgConditionRecord value)
value - The PurgPrcgConditionRecord to build this PurgPrcgCndnRecdValidity with.public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder conditionRecord(@Nullable String conditionRecord)
Original property name from the Odata EDM: ConditionRecord
The system uses the condition record number to store and retrieve information during processing (pricing, for example).
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder conditionValidityEndDate(@Nullable LocalDateTime conditionValidityEndDate)
Original property name from the Odata EDM: ConditionValidityEndDate
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder conditionValidityStartDate(@Nullable LocalDateTime conditionValidityStartDate)
Original property name from the Odata EDM: ConditionValidityStartDate
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder conditionApplication(@Nullable String conditionApplication)
Original property name from the Odata EDM: ConditionApplication
example, sales & distribution or purchasing).public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder conditionType(@Nullable String conditionType)
Original property name from the Odata EDM: ConditionType
The condition type indicates, for example, whether, during pricing, the system applies a price, a discount, a surcharge, or other pricing elements, such as freight costs and sales taxes. For each of these pricing elements, there is a condition type defined in the system.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder conditionReleaseStatus(@Nullable String conditionReleaseStatus)
Original property name from the Odata EDM: ConditionReleaseStatus
If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status for conditions.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder purgDocOrderQuantityUnit(@Nullable String purgDocOrderQuantityUnit)
Original property name from the Odata EDM: PurgDocOrderQuantityUnit
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder conditionContract(@Nullable String conditionContract)
Original property name from the Odata EDM: ConditionContract
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder materialConditionGroup(@Nullable String materialConditionGroup)
Original property name from the Odata EDM: MaterialConditionGroup
The condition group of the supplier is entered in the purchasing info record.Using the condition group, you can create conditions relating to a certain material and a certain supplier. Conditions defined for a condition group are taken into account in computing the effective price of the purchase order item.Enter the description of the condition group for which you want to define conditions. Your input can be alphanumeric.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder purchasingOrganization(@Nullable String purchasingOrganization)
Original property name from the Odata EDM: PurchasingOrganization
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder purchasingInfoRecordCategory(@Nullable String purchasingInfoRecordCategory)
Original property name from the Odata EDM: PurchasingInfoRecordCategory
You can create purchasing info records for:Normal procurementSubcontractingPipelineConsignment
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder purchasingDocument(@Nullable String purchasingDocument)
Original property name from the Odata EDM: PurchasingDocument
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder purchasingDocumentItem(@Nullable String purchasingDocumentItem)
Original property name from the Odata EDM: PurchasingDocumentItem
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder 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 PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder purchasingInfoRecord(@Nullable String purchasingInfoRecord)
Original property name from the Odata EDM: PurchasingInfoRecord
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder accountTaxType(@Nullable String accountTaxType)
Original property name from the Odata EDM: AccountTaxType
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder billToParty(@Nullable String billToParty)
Original property name from the Odata EDM: BillToParty
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder country(@Nullable String country)
Original property name from the Odata EDM: Country
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder 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 PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder invoicingParty(@Nullable String invoicingParty)
Original property name from the Odata EDM: InvoicingParty
This number denotes the supplier (creditor) invoicing the ordered material or services performed, to whom the amount due is payable.When the invoice is received, the number of the invoicing party is inserted in the invoice in place of the actual supplier.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder destinationCountry(@Nullable String destinationCountry)
Original property name from the Odata EDM: DestinationCountry
As a general rule, it is best to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on).The system uses the country key identifier to:Help determine the appropriate taxes during pricingDetermine important country-specific standards (the length of postal codes and bank account numbers, for example)When you process billing documents collectively, you can use the destination country as one of the selection criteria.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder activeSupplierSubrange(@Nullable String activeSupplierSubrange)
Original property name from the Odata EDM: ActiveSupplierSubrange
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.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder 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 PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder materialType(@Nullable String materialType)
Original property name from the Odata EDM: MaterialType
The material type defines certain attributes of the material and has important control functions.
trading goods.public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder taxCode(@Nullable String taxCode)
Original property name from the Odata EDM: TaxCode
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
the tax authorities.public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder region(@Nullable String region)
Original property name from the Odata EDM: Region
The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder stockSegment(@Nullable String stockSegment)
Original property name from the Odata EDM: StockSegment
the strategy is assigned to the material in the material master.public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder acctAssgmtTaxClassification(@Nullable String acctAssgmtTaxClassification)
Original property name from the Odata EDM: AcctAssgmtTaxClassification
The tax indicator is used in the automatic determination of the tax indicator in Purchasing.If you have taxable and non-taxable account assignments, you can define two tax indicators with the aid of which different tax codes can be determined.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder importTaxClassification(@Nullable String importTaxClassification)
Original property name from the Odata EDM: ImportTaxClassification
The tax indicator is set in purchasing documents if the country of origin differs from the country of destination of the goods.Specify the transaction to which the tax code is to apply. In doing so, make use of the "possible entries" facility.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder taxIndicator(@Nullable String taxIndicator)
Original property name from the Odata EDM: TaxIndicator
The tax indicator is used in the automatic determination of the tax code in Purchasing.The tax code can be determined automatically within the framework of price determination (via the conditions).Tax indicators are used to facilitate this process. They can be derived from the material master record, Customizing, or the purchasing document. The system determines the tax code from the combination of these tax indicators.In a service procurement scenario, you can apply different tax rates, based on the type of service.Automatic determination of the tax code is useful, for example, if different tax rates apply depending on whether a material is placed in stock or consumed directly.If the tax code can be determined automatically via conditions, it takes precedence over the tax code that has been maintained in the purchasing info record.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder regionTaxClassification(@Nullable String regionTaxClassification)
Original property name from the Odata EDM: RegionTaxClassification
The tax indicator is set in purchasing documents if the region of origin differs from the region of destination.Specify the transaction to which the tax code is to apply. In doing so, make use of the "possible entries" facility.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder plantTaxClassification(@Nullable String plantTaxClassification)
Original property name from the Odata EDM: PlantTaxClassification
The tax indicator is used in the automatic determination of the tax code in Purchasing.If you have some plants that are liable to tax and others than are not, you can define two tax indicators with the aid of which different tax codes can be determined.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder tradingContract(@Nullable String tradingContract)
Original property name from the Odata EDM: TradingContract
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder variantCondition(@Nullable String variantCondition)
Original property name from the Odata EDM: VariantCondition
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder valueAddedServiceChargeCode(@Nullable String valueAddedServiceChargeCode)
Original property name from the Odata EDM: ValueAddedServiceChargeCode
You can use the charge code to specify your customer's or vendor's surcharge per value-added service type for the execution of value-added services.You can define a charge code in the sales or purchasing document itself. If you have defined this in your VAS conditions per value-added service, the system determines the charge code along with the other value-added service details in the document.For example, you can create charge codes for each VAS-type. That means, the key and short text of the codes show which codes you want to use for ticketing/labeling, packing or special services.You should only delete a charge code if you no longer use it in valid VAS-conditions.
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder iN_GSTSupplierClassification(@Nullable String iN_GSTSupplierClassification)
Original property name from the Odata EDM: IN_GSTSupplierClassification
The different categories include:RegisteredNot RegisteredCompounding SchemeEconomic Zone
Tax regime.public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder plantRegion(@Nullable String plantRegion)
Original property name from the Odata EDM: PlantRegion
public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder taxJurisdiction(@Nullable String taxJurisdiction)
Original property name from the Odata EDM: TaxJurisdiction
authorities you must pay your taxes. It is always the city to which the goods are supplied.public PurgPrcgCndnRecdValidity.PurgPrcgCndnRecdValidityBuilder eTag(@Nullable String eTag)
Original property name from the Odata EDM: ETag
public PurgPrcgCndnRecdValidity build()
Copyright © 2019 SAP SE. All rights reserved.