public static final class SlsPricingProcedureItem.SlsPricingProcedureItemBuilder extends Object
@Nonnull public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder salesPricingProcedure(SlsPricingProcedure value)
value
- The SlsPricingProcedure to build this SlsPricingProcedureItem with.@Nonnull public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder slsPricingConditionType(SlsPricingConditionType value)
value
- The SlsPricingConditionType to build this SlsPricingProcedureItem with.@Nonnull public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder text(SlsPrcgProcedItemText... value)
value
- The SlsPrcgProcedItemTexts to build this SlsPricingProcedureItem with.public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder conditionUsage(@Nullable String conditionUsage)
Original property name from the Odata EDM: ConditionUsage
public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder conditionApplication(@Nullable String conditionApplication)
Original property name from the Odata EDM: ConditionApplication
example, sales & distribution or purchasing).public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder pricingProcedure(@Nullable String pricingProcedure)
Original property name from the Odata EDM: PricingProcedure
Procedures are used, for example, in the following applications:Pricing in Sales and DistributionAccount determinationCalculating taxes on sales/purchases
public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder pricingProcedureStep(@Nullable String pricingProcedureStep)
Original property name from the Odata EDM: PricingProcedureStep
public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder pricingProcedureCounter(@Nullable String pricingProcedureCounter)
Original property name from the Odata EDM: PricingProcedureCounter
During automatic pricing, the system takes into account the sequence specified by the counter.
public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder conditionType(@Nullable String conditionType)
Original property name from the Odata EDM: ConditionType
differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder prcgProcedItemFromRefStep(@Nullable String prcgProcedItemFromRefStep)
Original property name from the Odata EDM: PrcgProcedItemFromRefStep
If you specify a to-reference step at the same time, the condition values of the two steps specified and the conditions values of the steps in between are totaled. In this case, percentage surcharges are calculated on the basis of the total.Example:| Step | Condition Type | Description | From-Step | To-Step | Account Key |10 A-B1 Wages 20 A-B2 Salaries 30 A-B3 Overtime/Wages 40 A-Z1 Vacation bonus 10 30 E11The surcharge for step 40 is added to the total of steps 10 to 30.
public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder prcgProcedItemToRefStep(@Nullable String prcgProcedItemToRefStep)
Original property name from the Odata EDM: PrcgProcedItemToRefStep
If you specify a from-reference step at the same time, the condition values of the two steps specified and the condition values of the steps in between are totaled.Example:| Step | Condition Type | Description | From-Step | To-Step | Account Key |10 A-B1 Wages 20 A-B2 Salaries 30 A-B3 Overtime/Wages 40 A-Z1 Vacation bonus 10 30 E11The surcharge for step 40 is added to the total of steps 10 to 30.
Percentage surcharges are calculated on the basis of the total.public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder conditionIsManuallyDtmnd(@Nullable Boolean conditionIsManuallyDtmnd)
Original property name from the Odata EDM: ConditionIsManuallyDtmnd
(price determination, outputdetermination, batch determination) either if they are entered manually, for example, on the condition overview screen in Pricing or if they are transferred from an external process, such as costing.public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder prcgProcedItemSubtotal(@Nullable String prcgProcedItemSubtotal)
Original property name from the Odata EDM: PrcgProcedItemSubtotal
If the same fields are used to store different condition amounts, the system totals the individual amounts.These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
the cost of a material) are stored.public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder conditionIsForStatistics(@Nullable Boolean conditionIsForStatistics)
Original property name from the Odata EDM: ConditionIsForStatistics
altering the value).public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder accountKeyForGLAccount(@Nullable String accountKeyForGLAccount)
Original property name from the Odata EDM: AccountKeyForGLAccount
The account key enables the system to post amounts to certain types of revenue account. For example, the system can post freight charges (generated by the freight pricing condition) to the relevant freight revenue account.
public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder acctKeyForAccrualsGLAccount(@Nullable String acctKeyForAccrualsGLAccount)
Original property name from the Odata EDM: AcctKeyForAccrualsGLAccount
With the aid of the account key, the system can post amounts to certain types of accruals accounts. For example, rebate accruals which are calculated from pricing conditions can be posted to the corresponding account for rebate accruals.
public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder pricingProcedureItemPrintType(@Nullable String pricingProcedureItemPrintType)
Original property name from the Odata EDM: PricingProcedureItemPrintType
The following print types are available:' ' : Condition line is not printedThe other print types have the following settings and influence processing accordingly.'A' : in total: general'B' : in total: if value <> zero'C' : in total: if value <> value of predecessor'D' : in total: if value <> zero and value <> value of predecessor'a' : at item : general'b' : at item : if value <> zero'c' : at item : if value <> value of predecessor'd' : at item : if value <> zero and value <> value of predecessor
public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder conditionIsMandatory(@Nullable Boolean conditionIsMandatory)
Original property name from the Odata EDM: ConditionIsMandatory
If, for example, you always want to include a tax condition (VAT or sales tax) during pricing, you can set this indicator for the appropriate tax condition type.
procedure.public SlsPricingProcedureItem.SlsPricingProcedureItemBuilder cndnIsAcctDetnRelevant(@Nullable Boolean cndnIsAcctDetnRelevant)
Original property name from the Odata EDM: CndnIsAcctDetnRelevant
In the pricing procedure, the following settings for the price condition have been made:The price condition is used for statistics only, that is, you have selected the Statistics indicator.You have selected an Account key that defines two accounts.Note: The Accruals key is not taken into account.You use this indicator to define that the statistical price condition is posted to account-based Profitability Analysis (CO-PA) as journal entry to an extension ledger of Financial Accounting. You do this to increase and improve information relevant for management reporting:You can select the indicator in Customizing of a pricing procedure.You can display the indicator in a business document on the Condition Detail screen.You might want to post the following statistical price conditions to CO-PA:WarrantiesDelivery costsSurchargesDiscountCommissionRebateFor information about profitability and cost management, see http://help.sap.com/s4hana. Choose a release and then Product Assistance and choose your language. Then choose Finance -> Cost Management and Profitability Analysis -> Profitability and Cost Management.
public SlsPricingProcedureItem build()
Copyright © 2019 SAP SE. All rights reserved.