Pricing Flashcards

1
Q

7 Steps of the condition technique

A
  1. Field Catalog
  2. Condition table
  3. Access sequence
  4. Condition type
  5. Pricing Procedure
  6. Pricing Procedure Determination
  7. Condition Record
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Field Catalog

A

The list of fields that can be used as a base for pricing. That is to say, a list of fields which are used for how a price is determined.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Condition Table

A

A subset of the fields from the field catalog which will comprise the particular fields for that specific pricing scenario

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Access sequence

A

The sequence in which the condition tables need to be accessed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Condition Type

A

The type of computation i.e. price, surcharges, discounts, taxes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Pricing Procedure

A

Place where all the condition types are together

  1. Pricing
  2. Discounts
  3. Taxes
  4. Freights
  5. Surcharge
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Pricing Procedure Determination

A

Sales Area + Document pricing procedure + Customer pricing procedure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Condition Records

A

The determining of the actual cost

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

VOK0

A

Pricing configuration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Condition Table namespace

A

1-600 Reserved for SAP Standard

6019-999 Customizable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

V/06

A

Condition type configuration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

5 types of condition types

A
Prices
Discounts
Taxes
Freights
Surcharges
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Pricing Procedure Field: Subtotals

A

A summation of multiple condition types. Used when you want to store the sum of certain condition types to then use later.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Pricing Procedure Field: Manual

A

Conditions that can only be inputted into the order manually

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Pricing Procedure Field: Required

A

Condition type is mandatory

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Pricing Procedure Field: Statistical flag

A

Not used in calculating the price

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Pricing Procedure Field: Requirement

A

Determines whether the condition type is applied or not

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Pricing Procedure Field: Calculation routine

A

Custom routine to compute the price or the value of the condition type

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Promotion

A

For generating higher sales in a specific time.
Particularly useful for retailers who sell in physical stores as well as e-commerce.
Defined for specific period
Can have multiple sales deals
Works like a condition type

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Sales Deal

A

A representation of a promotion
Defined as a group of two or more condition types executed during the order processing for the promotional period
Defines a marketing deal for a certain product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Rebates

A

Rebate agreement is a special agreement granted to the customer on a specific volume of sales over a specific period of time.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Sales deal assignment

A

You assign promotions in the “Assignment” section of Sales deals creation/change

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Sales deal assignment

A

You assign promotions in the “Assignment” section of Sales deals creation/change

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Sales deal break down

A

The type of sales deal i.e. Z8C1 annual sales

Condition types for the sales deal Z8C1 i.e.
Z8CK Freight Discount, Z8D7 A/S by Mat Group

The condition records for said condition type which is based on a key combination/condition table
i.e. Condition record 1 for Z8CK based on Material group, for sales deal type Z8C1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Rebate Configuration

A

Define agreement type
Define condition type group
Maintain the category of the condition type group
Assign condition types and condition tables to the condition type group
Assign agreement types to the condition type group

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

Condition types and condition records for rebates vs for discounts

A

Rebates have condition type groups, whereas discounts only have condition types

Rebates accrue whereas discounts are one time bangs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Pricing reports

A

Put together information from condition records, condition types and condition tables according to various different criteria.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Customer Hierarchy

A

Used to apply pricing elements to a collection of customers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Hierarchy partners functionality

A

The partners functions from the higher level customer get passed down to lower level customer at the sales document header level

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Customer Hierarchy Configuration

A

Configure Hierarchy type
Set partner determination for hierarchy categories
Assign account groups
Assign Sales areas
Assign Hierarchy type for pricing by sales document type

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

Hierarchy nodes placement

A

Hierarchy nodes are not put into the customer master, but are put into the sales document

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

Customer hierarchy partner functions source

A

Can only come from the sold-to

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

Condition Exclusion

A

There might be a scenario’s where system determines records for more than one condition type in the pricing procedure. In order to avoid this we can set up conditions or a group of conditions to be mutually exclusive.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

Condition Exclusion Configuration

A

Define condition exclusion groups
Assign condition types to exclusion groups
Maintain condition exclusion for pricing procedure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

Group conditions

A

Some conditions to be used as the scale base value or the condition value taking all related items of the business document into account.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

For a group condition to be effective..

A

the items must belong to a group

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

Reference condition types

A

Condition type that references another, thus only the main condition type requires condition records

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

Hierarchy Access

A

Using one condition table with one access

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

Hierarchy Access: Free fields

A

Fields which act as optional fields during condition record maintenance, allowing any number of combinations of characteristics for an access.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

Header condition

A

Does not have access sequence like item conditions (typical condition type) therefore, you don’t maintain condition records and thus are manual conditions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

Group conditions always work on…

A

Total order quantity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
42
Q

Exclusion group

A

A container for condition types that need to be compared during condition exclusion

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
43
Q

Exclusion method A

A

Multiple condition types compared and best condition record is chosen, the rest are discarded

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
44
Q

Exclusion method B

A

All condition records for 1 condition type are compared, the best is selected with the others deactivated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
45
Q

Exclusion method C

A

Best condition record between two exclusion groups

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
46
Q

Exclusion method D

A

If condition record is determined for the first exclusion group, then condition records for the second exclusion group are deactivated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
47
Q

Exclusion method E

A

Similar to method B, but now highest price will be chosen

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
48
Q

Exclusion method F

A

Similar to method C, but the highest price will now be selected

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q

Exclusion method L

A

Similar to A, but giving the highest price

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
50
Q

Free Goods

A

Free Goods in SAP is giving certain material/quantity as free of charge based on Order quantity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
51
Q

Types of Free Goods

A

Free Goods are of two types in SAP, Inclusive Free Goods and Exclusive Free Goods

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
52
Q

Inclusive Free Goods

A

If the Free Goods quantity is a part of Order quantity, it is said to be Inclusive Free Goods. Also, called inclusive bonus quantity.

Example: Buy 10 get 1 free is the Policy. Customer is charged for 9 qty. only and one is given free.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
53
Q

Exclusive Free Goods

A

If the Free Goods quantity is in addition to Order quantity, it is said to be Exclusive Free Goods. Also called exclusive bonus quantity.

Example: Buy 10 get 1 free is the Policy. Customer is charged for 10 qty. and one is given extra.

The material being given free could be different from Ordered material.

54
Q

Free good aspects

A

Can specify a validity period for the free goods agreement

can specify a minimum quantity for which free goods is to be granted

55
Q

Different rules for determining the free goods quantity

A

proportional (rule 1)
related to number of units (rule 2)
only for whole units (rule 3)

56
Q

Free goods proportional (rule 1)

A

You grant 10 pieces of a material as exclusive free goods for an order of 100 pieces.

A customer orders 150 pieces. They receive quantity of 15 free goods.

57
Q

Free goods related to number of units (rule 2)

A

You grant 10 pieces of a material as exclusive free goods for an order of 100 pieces.

A customer orders 150 pieces. They receive quantity of 10 free goods.

58
Q

Free goods only for whole units (rule 3)

A

You grant 10 pieces of a material as exclusive free goods for an order of 100 pieces.

A customer orders 150 pieces. They receive quantity of 0 free goods.

59
Q

Free goods Delivery controlling

A

you can control whether the free goods are processed independently or whether they are only copied to the delivery for partial delivery or full delivery

60
Q

PR00

A

Standard Price condition type

61
Q

K004

A

Material discount

62
Q

K005

A

Customer-specific material discount

63
Q

K007

A

Customer discount

64
Q

K020

A

Price group discount

65
Q

KF00

A

Freight surcharge

66
Q

UTX1

A

State tax

67
Q

UTX2

A

County Tax

68
Q

UTX3

A

City Tax

69
Q

Types of Scales

A

Graduated-To
From
To

70
Q

Graduated-To Scales

A

Start from a number and each level adds ontop of the next

10 qty for $10
20 qty for $12
30 qty for $13

So qty of 30 would be $35

71
Q

From Scales

A

Anything below is not considered

From 10 qty is $10
From 20 qty is $12
From 30 qty is $13

So 22 qty is $12

72
Q

To Scales

A

Everything below is considered. It is Graduated-To but without the adding of the previous

To 10 qty is $10
To 20 qty is $12
To 30 qty is $13

So 15 is $10

73
Q

Condition type config: Condition class

A

Used by the system to determine what conditions it must re-determine and when.

For example, a copying rule may indicate to copy pricing conditions unchanged and re-determine taxes; the system would then use this indicator to determine what condition types are taxes.

74
Q

Condition type config: Condition category

A

Used by the system to categorize condition types into like groups

75
Q

Condition type config: Rounding rule

A

Indicates the system is to use commercial rounding in discovering the value of the condition record

76
Q

Three rounding rules for condition types

A

Commercial Rounding - 1.2 = 1, 1.6 =2
Always round up - 1.2 = 2
Always round down - 1.9 = 1

77
Q

StrucCond.

A

Controls whether the condition type should be a duplicated or cumulated condition

duplicated condition, duplicated onto all assigned items

cumulated condition, contains the net value of all assigned items

78
Q

Condition type config: RoundDiffComp

A

Controls whether rounding difference is settled for group conditions with a group key routine

System compares the condition value at header leve with the total of the condition values at item level. Difference is added to the largest item.

79
Q

Condition type config: GrpCond.routine

A

Identifies a routine that calculates the basis for the scale value when a group condition occurs in pricing

80
Q

Condition type config: Manual entry has priority

A

Controls the priority within a condition type between a condition entered manually and a condition determined by the system

81
Q

Condition type config: Qty relation

A

determines if you can change the conversion factors for the units of measure

82
Q

Condition type config Changes which can be made options

A
Header condit.
Item condition
Delete
Value
Amount/percent
Qty relation 
Calculat.type
83
Q

Condition type config: valid from and valid to

A

The default proposed validity dates in condition records

84
Q

Condition type config: RefConType

A

Used if you want to refer to another condition type, thus only creating condition records for the reference

85
Q

Condition type config: delete fr. DB

A

Controls how system behaves when deleting condition records

86
Q

Condition type config: Obsolete

A

Controls how the system responds to when condition records are maintained

87
Q

Condition type config: Condition index

A

Specifies whether the system updates one or more condition indices when maintaining condition records

88
Q

Condition type config: Condit.update

A

You can make the use of a particular condition record dependent upon the total value of the document

89
Q

Condition type config: Scale basis

A

Determines how the scale must be calculated, i.e. value-based or quantity-based

90
Q

Condition type config: Scale formula

A

May be used with a routine to determine the scale base value

91
Q

Condition type config: Check value

A

Determines if the scale should always be ascending or descending.

Customer receives $10 discount for a purchase from 0 to 100 items, $20 for a purchase from 101 to 200 items, and $5 for a purchase from 201 to 999, 999

92
Q

Condition type config: Scale type

A

Left blank to indicate the scale can be set up in the condition record

93
Q

Condition type config: Unit of measure

A

System use this particular unit of measure when calculating the scale

94
Q

Condition type config: Currency conv.

A

System converts the condition currency to the document currency after multiplication of items

95
Q

Condition type config: Accurals

A

makes value determined by this condition type statistical

96
Q

Condition type config: Inv.list cond.

A

Makes the condition type as relevant for internal costing

97
Q

Condition type config: Int-comBillCond

A

Permits you to indicate that this condition type is used for internal costing

98
Q

Condition type config: ServiceChgeSe

A

Indicates that the trading contract conditions should be calculated using the vendor billing document

99
Q

Condition type config: Variant cond.

A

No longer used, was for variant conditions

100
Q

Condition type config: Qty conversion

A

Determines the quantity conversion during determination of the condition basis. Only relevant if the sales quantity unit and the condition quantity unit are identical.

101
Q

Condition type config: Exclusion

A

Indicates whether system automatically excludes the discounts that are proposed during pricing

102
Q

Condition type config: Pricing date

A

System date that must be used to determine a condition record’s validity

103
Q

Condition type config: Rel.Acc.Assig

A

Used to identify if standard account determination or specific account determination must take place

104
Q

Condition type config other fields

A

Plus/minus
Text determination
Text ID

105
Q

Cost Determination set up location

A

Item Category

106
Q

VPRS condition type

A

captures Cost of the material which is copied from Valuation segment from Material master Depending on customisation of Condition type - condition Category.

VPRS should have subtotal as B and requirement as 4

107
Q

Rebate Agreement type config: verification levels

A

determines the level of detail one sees when displaying totals for a rebate agreement

108
Q

Rebate Agreement type config: Different val. period

A

Controls whether condition records within a rebate agreement must have exactly the same validity period as the agreement itself

109
Q

Rebate Agreement type config Payment procedure

A

If you wish to make manual payments of the rebate to the recipient

110
Q

Rebate Agreement type config: Manual Accruals flag

A

Used if you want to be able to post manual accruals for this agreement type

111
Q

Rebate Agreement type config: Arrangement calendar

A

Defines the end of the validity period and controls their extension

112
Q

Rebate Agreement type config Reverse accruals flag

A

Should the accruals not be as high as the payment to be made, the system will reverse whatever accruals it h

113
Q

Rebate Agreement type config Reverse accruals flag

A

Should the accruals not be as high as the payment to be made, the system will reverse whatever accruals it h

114
Q

Rebate Agreement type config: Settlement periods

A

Define the periodic partial settlement is to be carried out for a rebate agreement

115
Q

Rebate Agreement type config: Settlement periods

A

Define the periodic partial settlement is to be carried out for a rebate agreement

116
Q

Rebate Agreement type config: Correction

A

Specifies the sales document that the system automatically uses to correct the values

117
Q

Rebate Agreement type config: Correction

A

Specifies the sales document that the system automatically uses to correct the values on which the rebate payment is based

118
Q

Rebate Agreement type config: Minimum status

A

Specifies the minimum status that a rebate agreement must have before the settlement can be calculated

119
Q

Rebate Agreement type config other fields

A

TextDetermProc.

Text ID

120
Q

Retroactive Rebate Processing

A

You can create a rebate agreement with a validity period starting in the past. The system does not post accruals for billing documents created in the past though.

121
Q

Rebate Index

A

Used to settle retroactive rebate agreements

122
Q

Changes which necessitate restructure of rebate index

A

New rebate relevance of sales orgs
New rebate relevance of billing types
New rebate relevance of payers
Creation or inclusion of new accesses for rebate processing

123
Q

Pricing limits

A

For condition types that may be altered manually, you ensure that there is no room for abuse.

124
Q

Condition Supplements

A

Group of conditions that you want to apply every time a certain condition is found

125
Q

Tax determined based on…

A

Org structure, Country, Region, City

Of delivering plants and country of receiving customer along with tax relevancy indicators on customer master and MM record

126
Q

Determination of the tax classification number Determination A

A

Tax number and Tax indicator classification is generally taken from sold-to party customer master record

127
Q

Determination of the tax classification number Determination B

A

Indicates the tax number and tax classification is generally taken from the customer master record of the payer

128
Q

Determination of the tax classification number Determination Blank (priority rule)

A

System determines the tax umber and the tax classification according to the following sequence

  1. If payer has VAT registration number and is identical to the sold-to party, tax number and tax classification are copied from the payer. Tax number is copied according to the “country of destination relevant for taxes”
  2. If ship-to party has a VAT registration number and the sold-to party does not, tax number, and tax classification are copied from the ship-to party
  3. If step 2 does not apply, Tax number and tax classification are copied from sold-to party
129
Q

Determination of the tax classification number Determination C

A

Same as the priority rule except the destination country is taken from the ship-to party

130
Q

VAT registration number

A

11 characters, and starts with the ISO code for the country

131
Q

Condition type config: RefApplicatio

A

Using condition types from other applications

132
Q

Different sections of pricing report

A

Page Header
Items
Group Header