different prices for ship to(Not Sold to) -?

[Former Member]

Hi Experts

Any body please explain the difference between the prices to different Ship - To's.

Ex:

Can I sell a product to different ship to's for different prices?( Like if any customer (one sold )has meny --->ship to's)

Normally any client will sell like that?

Is it psosible by Standard SAP? adding ship-to To access sequence?

Or

Does it supported by any other IS(Industry specific)- sap ?

Any thoughts will be help full!

Thanks

Kris

[Former Member · Accepted solution]

Yes. You can certainly map the price based on Ship-to-party, instead of Sold-to-party. For this to work, Identify if any satandard table (V/04) is helpful. If yes, you can assign the same to the access sequence (V/07) being used in relevant condition type. If No, then you can generate a new table based on fields available in field catelog & assign the same to the relevant Access Sequence.

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 neccessary 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 neccesary 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. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.

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

Regards,

Rajesh Banka

Reward suitable points.

• How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

[former_member183879]

Hi Kris,

Ship to is one of the allowed fields in teh field catalog. So you can very well base your prices depending on teh ship to party.

Create a condition table having material and ship to party as the fields(additional fields based on your criteria)

Include this as the condition table in the access sequence of the condition table.

Now maintain the condition records for this condition type, for various ship to parties for a specific material in VK11

If you create transactions now, you can see the changes getting effected in the condition screen based on the ship to party.

If you change the ship to party in open order and then reprice the order, you can notice the price also getting changed.

Reward if this helps.