pricing

[Former Member]

Hello SAP Prof,

could u plz ask the probable questions in Pricing.(project related)

[Former Member]

Hi Rajesh,

These are the different questions related to pricing..

Difference between Condition Type

Accumulate the amt of cond. types in accting document

Hiding Price Condition Types on a Sales Document

Creating New Pricing Procedure

What is "alt cal type" & "alt base value" & "Requirement field" in Pricing Procedure

Re-pricing in a Quotation

Quantity Based Discounts in Bulk Quantities Sales

Determine sales price with shipping point

Pricing date based on Deliv. date, Sales Ord, Billing

Report to Check the Entered Pricing Condition Price

Mass Update of condition pricing

Material Master Price as Sales Price Automatically

Customer discounts on effort only

Steps to Create Commission for Agent

Pricing: Real Time Tickets

This is very specific & differs from client to client & may also differ based on scenario.

Write-up on Pricing -

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the necessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the necessary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

It is assumed that document pricing procedure, customer pricing procedure , ... are in place.

Sales Document not assigned to Sales Area:

SPRO --> Sales & Distribution --> Sales --> Sales Documents --> Sales Document Header --> Assign Sales Area To Sales Document Types --> Assign sales order types permitted for sales areas (do ensure to maintain combined Sales organization, combined Distribution channel & combined division. for eg: Sales org 1000 & sales org 1000, Sales org 2000 & sales org 2000, & so on ....

similarly for distribution channel & Division, so that the Sales area combination is available for assignment to Sales Document Type.)

Issues related to Customer Master data:

1. what is the impact of leaving customer pricing procedure & customer statistic group blank in customer master --> sales area data --> sales tab:

If Customer Pricing Procedure is left blank, Pricing will not be determined.

If customer statistic group is left blank, then data will not flow to standard reports.

2. Who maintains reconciliation account in customer master?

Ideally, reconciliation account is maintained by FI person, but if SD person is authorized & has the knowledge of which reconciliation account to be maintained, then even SD person can maintain the same.

3. Terms of payment appear in Company Code Data & sales Area Data. What is the impact of each? why is it not populated automatically, once it is maintained at either field?

Terms of payment from company code data is for reporting purpose & it is from sales area data that it flows to sales order.

It is a standard feature of SAP that it is not populated automatically if maintained at either of the field, but it is a must in sales area data & can be skipped in company code data.

4. Unable to select Sales Area for Customer Master Creation?

Most Probably either sales area is not defined or customization not done for common Sales Org & Common Distribution Channel. To maintain this configuration: SPRO --> Sales & Distribution --> Master Data --> Define Common Distribution Channels / Define Common Divisions

Other queries:

Where is the control for Automatic PGI?

For this you can set batch jobs. T-code SM36, 37 38 or you can use the userexit CSO_P_DLVRT_GOODS_ISSUE_CREATE - auto PGI

The above are few examples.

/message/3690162#3690162 [original link is broken]

/message/3690162#3690162 [original link is broken]

/message/3969535#3969535 [original link is broken]

Reward if it helps

Regards...

Praveen Kumar.D

[former_member227476]

dear Rajesh

What is the importance of requirement field in access sequence?

What makes the immediate delivery in cash sales?

Can you create sales order for 40 items if the quotation is sent for 30 items?

What is z transaction?

What are some pricing routines and SD functional specs?

What is meant by condition technique?

Where do we can find pricing procedure indicator in SD?

What is the standard group condition routine in condition type, what is its importance?

How do you control entry possibility of condition values at order through condition type settings?

What are the customizing settings in pricing procedure for tax condition type?

While creating a Sales Order, Pricing procedure is not determined automatically, what could be the reason?

What is the difference between condition type EK01 (costs), PR00 (basis price) and PB00 (gross price). Can we apply all the three condition type in single sales order?

Whether Free goods should be determined or not for a Sales Order?

How would you determine an output procedure other than the condition types? (Alternative method)

what is the relevance of vendor Tab in customer master and in which scenario you will use this tab?

What is backorder processing?

What is an ABAP Query? How is it different from ABAP reports?

While a Quotation is created, it has to be approved by some authorized person, how to configure

i hope i answer your question

rewards if it helps

siva

[Former Member]

Hi

Refer below

What are some pricing routines and sd functional specs?

Form routines for prcing and variuos other functions can be maintained form routines are something todo with ABAP code.

Go to (VOFM) where all requrements whcih are represented by form routines can be maintained. Requrements are available to be assigned where access sequenses are used (for determination procedures, here pricing).

Once the tcode VOFM is accessed you will see requrements and go select "pricing" again you need access key to create your own or copy a routine.

Say you want header price not to have effect the item pricing, you need to go to the program to change abap code to meet the requirement. this specific requirement you created will be assigned in the pricing proc. determination "requirements field"

usaully with a number beyond 600. Note: make sure you activate your routine for its effect to take place.

What do you do really in pricing determination, and what are the main deifferences between one pricing procedure determination to the others, which data control these differences

we determine how the prices are calculated, taking into account sales area(sales org, distribution channel, division), document type and customer(generally sold-to-party).

The main differences between pricing procedures would be the differences as I mentioned above, from the point of view of field entries.

Coming to the output and the procedure, I suppose the condition types used will be different and hence the following whole procedure.

i want to maintain the pricing with 4 decimal places which i bel can be maintained in the table TCURX for the currency. and this helps in maintainiga a condition record with upto 4 decimals but when it saved in the database, it gets saved with 2 decimals only since the field kbetr is of 2 decimals.

In the pricing conditions please main the price per 100 PCS, So if the price of the product is 100.2504 , maintain it as 10025.04 per 100PCS.

When you print this on SAP script, you can calculate the Unit proce by dividing the conditon value by the per value

What is Reqt in Pricing (control fields.)

It is a routine that is written by an ABAP consultant according to the business requirement.

By defining Requirement in condition technique we can restrict the access of condition type.

To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (incase of cut-off period for rebates).

For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is “Only in Billing Document”.

This Requirement will ensure that these condition types will appear only during the billing document processing.

What is alternative calculation type in pricing why is it used?

Alternative Calculation Type:

Normally if you want to calculate a value you have to use a calculation type for determinating the value. This calculation type is either addition, subtraction or multiplication. Similarly SAP also has got a default calculation type in the control data of the condition type. There you have the options of either Qty based , Fixed Amount Based or Percentage based.

Here what happens is suppose if you define Your condition type that calculates the base price of a material on Qty based. Then the calculation will be done based on the quantity of the material. If the customer orders 10 Nos and you have maintained a unit price of 100 Rs for each material then the value determined is 1000 INR. Similarly if the discount condition type , you maintain the calculation type as %. This means if you maintain the value of 10 % in the condition record. Then this percentage is taken as the calculation type and the condition value is determined.

In some cases you have to forego the default calculation types and use the customer specific method for calculating a value. For ex if you are calculating the Freight charges for a Material . it depends on so many criteria like, the weight, volume and also the minimum amount etc etc, in those cases, you forego the default value and then use the alternative calculation type in calculating the condition value against the particular condition.

What is condition base value in pricing procedure and why is it used?

Alternative formula for condition base value

Formula for determining the condition basis as an alternative to the standard.

Example

An absolute header discount is, for example, distributed in the standard system according to the cumulative value of the items.

If the system, however, distributes the absolute header discount according to volume, a header discount of $30 results in the following discounts:

Item Value Volume Discount

Stand. disc. Volume disc.

1 $1000 2 cbm $20 $10

2 $500 4 cbm $10 $20

http://sapsdforum.wordpress.com/

http://www.allinterview.com/Interview-Questions/SD.html

http://storage-search-swicki.eurekster.com/SAPSDfaq/

http://techpreparation.com/computer-interview-questions/sap-modules-interview-questions5.htm

Message was edited by:

SHESAGIRI.G