cancel
Showing results for 
Search instead for 
Did you mean: 

Scenario to be mapped - URgent

Former Member
0 Kudos

My client got 2 plants.

<b>Scenario:</b>

Plant 1 send materials to Plant 2 for some specific services and the plant 2 sends back to plant 1 by raising the invoice.

Shall I try STO? if so explain in detail.

Please help me to map the scenario.

Regards,

Anbu

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

It can be mapped with STO with SD involvement.

Go to T.Code: V/08 and use pricing procedure ZIV002 with condition type "ZIVU".

Go to T.Code: OVKK Assign the pricing procedure to supplying plant sales area with Document Pric proc "N"

Go to T.code: VK11 and maintain condition record for ZIVU

Go to T.code: ME21N and raise PO

Go to T.Code: VL10B and create replenishment delivery

Create TO in T.code: LT03

Go to t.Code: VL02N and do PGI

Go to T.code: VF01 and use document type ZIVU

regards

AK

Reward points if helpful

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Anbusaravanan,

For your requirement as suggested by our friends STO seems to be a suitable one.

Stock transfer is a process where material is transferred from one plant to another plant within the same company e.g. Pune stock transfers to Mumbai within same company code.

- Also following types of Stock Transfer options are available:

•Manufacturing Plant to Depot

•Depot to Depot

•Depot to Manufacturing Plant

For doing a Stock transfer through SD the steps are as follows: -

• Creation of Stock tranfer order using T-code- ME21n (Here the Receiving Plant creates a STO on the Sending Plant)

• Creation of Delivery document against the STO using T-code VL04 (Here the Sending Plant creates the Delivery document against the STO created on it)

• After creation of Delivery document PGI (Post goods issue) is done for the Delivery document using T-code-VL02n.

• After PGI is done a Billing document is created against the delivery document – (Here the logic for creating a Billing document is that the same will be carried along with the Truck carrying the material). Here a Pro-forma document is created as against normal Billing doc used in Sales. The pro-forma document does not carry an subsequent accounting entries as the same is only tranfer of material from one plant to another and not a sale.

You can use F8 billing type for creating Performa Invoice for Delivery

• After Proforma invoice is prepared you can view the stocks in trasit using T-code- MB5T.

• Finally the Receving plant can do the goods receipts of the goods against STO created using T-code - MIGO.

Hope the above helps you.

REWARD if it helps you!!

Regards,

Ajinkya

Former Member
0 Kudos

hi,

this process can be mapped with STO.

Customization settings:

create material under one plant and extend it to other plant

go to mb1c and intalise the stock under supplying plant

Process flow:

1. create STO in receiving plant(1100) using document type UB in ME21N

2. carry out PGI in supplying plant (1000) by using movement type 351

3.carry out PGI in receiving plant (1100) by using movement type 101

Regards,

Murali

former_member183879
Active Contributor
0 Kudos

Anbu

Plant2 creates a PO to Plant1 for material X (me21n)

Plant2 receives material X(MIGO)

Plant2 receives invoice for material X(MIRO)

Now

Plant 2 works on material X and converts it to Y.

Plant1 creates a PO to plant2 for material Y(ME21N)

Plant1 receives the material Y(MIGO)

Plant1 receives invoice for material Y(MIRO)

You can decide whether 2invoices are needed or 1invoice is sufficient.

If both plants are of same company code, you can create stock transport orders instead of purchase orders of type UB in me21n and in that case, you can just avoid MIRO.

Rewards if this helps.

Message was edited by:

Navaneetha Krishnan

Former Member
0 Kudos

plz explain in detail about the EXCISE implications also