STO Pricing Configuration

[Former Member]

Hi ,

I know there is lot of info available reg STO on this forums .But i am looking for detailed step by step configuration involved for Pricing in intercompany STO process.If its posted on this forum please provide the link.I will be thankful and full points will be awarded

Please guide me in doing Pricing configuration for intercompany STO process in detail steps. full points will be awarded.

Thanks

[Former Member · Accepted solution]

Configuration of Pricing Procedure will be same. It is determination which will play an important role. Incase of STO, generally in India we select Invoice Type JEX (Whether Using JEX or any other Billing Type) ensure to check the Document Pricing procedure in Billing Type (VOFA) & accordingly carry out configuation for determination of Pricing Procedure in T.code: OVKK.

Pricing Procedure:

Determination of Pricing Procedure:

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. 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.

Configuration of Pricing Procedure:

Step 1:

Condition table (T.Code: V/04): 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 (T.Code: V/07): 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 (T.Code: V/06): 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 (T.Code: V/08): 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 (T.Code: VOK0): 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 (T.Code: VK11 / VK12): 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.

Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.

Regards,

Rajesh Banka

[Former Member]

hi,

may be this will help you some what...

have following scenarios to map using SAP transportation module. I need suggestion/idea from you all as to how we can map it perfectly in SAP.

Requirements:

1. Scenario is of goods movement from One plant to another plant within same company code.

2. Receiving plant will create a stock transport order and maintain a freight cost. This freight cost is maintained in STO using a condition type. This is the contractual cost and calculation is based on dispatchedweight.

3. Dispatch plant will create a Replenishement delivery(VL10B) for above created STO. Dispatched weight will be captured in this delivery.

4.At the time of Post goods issue for above delivery following account posting should happen:

Inventory FG Cr. (At despatch Plant ) 48000 (cost of material)

Inventory FG Dr. (At Receiving Plant) 49000 (Cost of material + freight cost)

Freight STO FG Cr. (At Receiving Plant) 1000 (freight cost)

5. Receiving plant will do goods receipt (Received weight is captured).

6. Invoice verification: During this phase accounts department will verify the GR documents and does following determination:

6.1. Whether received weight is different from disptached weight.

6.2. Whether shipment is ontime, early or delayed.

6.3. Whether any transshipment happened or not (based on truck number).

7. After above determination is made an incoming invoice is created using following calculation:

7.1. Base freight = Received weight * contractual freight cost.

7.2. Penalty or incentive is levied based on whether shipment is delayed or early.

7.3. A penalty is levied if transshipment has happened (Transshipment are not allowed as per the contract).

8. payment is made and accounts are cleared.

What I have done so far:

1. Created an outbound shipment type.

2. Created a shipment cost document and shipment item category copying standard item category but with different rule for settlement date.Also, the account assignment category:K, General Modification: VBR, Auto PO generation.

3. Created one new freight condition type with Calculation type: Gross weight, calculation base: delivery. Assigned this condition type to a standard access sequence and created a new pricing procedure.

4. Created two more conditions for Penalty and incentive. Calculation base: All.

Proposed Solution:

1. Create STO. Insert a freight condition with contractual freight cost.2. Create Replenishment delivery.

3. Create an Outbound shipment and assign above delivery to it.

4. Shipment is put in 'Shipment start' when actual goods movement happens. As soon as shipment is saved after 'shipment start' auto goods issue will happen and following accounts will be posted.

Inventory FG Cr. (At despatch Plant ) 48000 (cost of material)

Inventory FG Dr. (At Receiving Plant) 49000 (Cost of material + freight cost)

Freight STO FG Cr. (At Receiving Plant) 1000 (freight cost)

5. Receiving plant will do Goods receipt (MIGO).

6. An custom job will be run after creation of GR document through MIGO which will update received weight in shipment document in a custom field.

7. Shipment status is moved to 'shipment end' and save. At this point a new code is built in userexit which will calculate the difference in 'shipment end' and 'shipment start' and compare this with planned duration of route (maintained in route). A determination of late or early shipment will be done by code and it will update 'special processing indicator' with specific values maintained earlier. Ex: 1 - shipment late by one day, 2- shipment late for two days. The penalty and incentive condition type records will be maintained against this indicator so thatcorrect condition record is called during shipment cost document creation.

8. A new pricing routine is built and assign to the new freight condition. It will look at the received weight maintained in a custom field at shipment level instead considering delivery weight.

9. Shipment cost document is created with reference to above created shipment and transfer of cost is