Skip to Content
-1

Sales order is captured in Plant (A) but the same sales order should be processed from Plant (B)

May 08 at 05:37 AM

91

avatar image

Dear experts,

Please find the below scenario and guide further:

There are two plants (A and B).
A is into sales order capturing whereas B is into to production activities.

Below are the expected activities between these plants:

Plant A:
SO (12345) (with auto PR) -> PO (wrt PR). And this PO should be to Plant B.

Plant B:
1. SO Transfer (12345) from Plant A to Plant B (but material differs between these plants for the same item).
2. WBS BOM (using material code of Plant B)
3. BOM updation
4. MRP is run to create PR -> PO -> GRN from Vendor.
5. Outbound delivery to Plant A

Plant A:
GRN (wrt PO from Plant B)
Outbound delivery to Customer.


Please guide further.

10 |10000 characters needed characters left characters exceeded

"but material differs between these plants for the same item" - what is the reason for having two different materials?

Is one of the materials actually some semi-finished product or the materials represent exactly the same thing (in which case you should not have two codes) or the product is the same, but the packaging or labels are different?

Without understanding what is the exact process it is hard to suggest any solution.

Another question - is there a specific reason why the products for customer A should always go via plant A in terms of gods receipt?

You mentioned GR from Vendor - are you procuring materials from external parties in plant B, which you ship to plant A and then deliver to the customer?

Maybe it will be best if you start explaining in details the business process from the beginning - as you can see, your current explanation may have different interpretations and (probably) different solutions.

0
* Please Login or Register to Answer, Follow or Comment.

2 Answers

G Lakshmipathi
May 08 at 08:43 AM
0

Are you not aware of Intra-Plant Stock Transfer ?

Show 7 Share
10 |10000 characters needed characters left characters exceeded

Dear Lakshmipathi,

Yes. I am aware of Intra Company STO. But in my case, both the plants have different company codes.

Correct me if I am wrong, STO comes into picture when there already exists the same stock in Plant B.
But in my case, it is MTO requirement.

0

In that case, you can go with Inter Company STO as per OSS note 394481

1

Mmak,

folowing Mr. Lakshmipathi comments, in addition to SAP notes, check these links below:

There are a lot contents in SCN regarding this process. I think that with this content you will solve your doubt.

FM

0

Dear Veselina/Fausto/Lakshmipathi,

I really apologize as I checked with client on Veselina's asked questions (why different material codes between two plants? Why cant Plant B deliver goods to customer?) and found the requirement is different now. Below is the revised requirement:


Below is the AS-IS business process flow.


Expectations under this requirement:

1. With reference to Plant A’s PO (after PO approval - L1/L2), system should create auto SO in Plant B (material code differs between Plant A and Plant B).
Below are the material codes between these plants:
ABCDE in Plant A.
12345 in Plant B.
Reason for auto SO creation? There is no order booking team in Plant B. So everytime, Plant A team itself is manually creating this SO in Plant B system. But there exists Project building team in Plant B to take the requirement further.
I discussed with my ABAPer, he said, auto SO creation is possible. He also suggested, we will develop custom table to enter source (Plant A) and target (Plant B) material codes. So, whenever user creates SO in Plant A (using material ABCDE), auto SO in Plant B is created (using material 12345). And this can be achieved by enhancement.


2. Auto created SO (in Plant B) should be shown in Plant A’s SO flow (i.e., after Plant A's PO).
Before we go for automation, how do I create SO (Plant B) with reference to PO (Plant A)? Is it possible?
If system allows, will it show Plant B' SO in
Plant A’s SO flow (i.e., after Plant A's PO)?
I guess I can try creating SO (in Plant B) wrt SO (of Plant A). But user wants to see Plant B SO after Plant A PO. Need help here please??????????????


3. Email to be sent to respective people right after this auto SO creation.
My developer said, custom table will be developed to maintain email IDs in order to send this auto SO creation update. And this can be achieved by enhancement.



I need not worry about 1st and 3rd point. I need help only on 2nd point!!!!!!!

0

You forgot to answer my questions, so the best I can do is give some generic suggestions - read about IDOC, especially message type ORDERS. There is a nice blog series by Satish Babu which could help you understand the basics.

You said that you need not worry about 1. and 3., but if you are going to support the solution, you probably should... If I were you, I would try to avoid custom tables for material or e-mail mapping if possible and determine the needed information from master data/transactional data/customizing. #justmy2cents

0

Dear Veselina,

I regret I did not answer your questions. This is because anyhow the requirement has been completely changed, so there is no point discussing them further...

Since you asked, please find the answers below:
Why different material codes between two plants?
Plant B (co code BBBB) is older one and they have their own material codes.
Plant A (co code AAAA) had been established 2 years ago. They created their own materials without discussing with Plant B and followed accordingly. There is huge communication error between these two separate entities.

Why can not Plant B deliver goods to customer directly?
After the project is ready, it is customer’s demand to visits the plant (plant A) to do the inspection before physically receiving it. Plant A is in South India (Bangalore) whereas Plant B is in North India. All customers are from South India (Karnataka & Tamil Nadu) and they do not want to travel to North India to do inspection.

Thanks for 1st and 3rd point, I shall follow you as suggested.
But any idea on 2nd point please?

0

My remark on IDOC was mostly related to point 2 - creating a sales order from a purchase order.

Probably I don't need to tell you that, but anyway: if you can, try to persuade the business to unify the material codes or at least to have 1:1 relationship between codes in A and B.

1
Arputharaj Thomas May 10 at 12:27 PM
0

On this....

"I discussed with my ABAPer, he said, auto SO creation is possible. He also suggested, we will develop custom table to enter source (Plant A) and target (Plant B) material codes. So, whenever user creates SO in Plant A (using material ABCDE), auto SO in Plant B is created (using material 12345). And this can be achieved by enhancement."

Why shouldn't customer material info record be used here, rather going for a development? If you have decided to create SO automatically in plant B (for which mostly you will be using a standard BAPI), you will have to give the customer details while creating order, for which I guess you would be creating plant A as sold to and ship to as ultimately that is where you wanted the goods to be delivered. Therefore you can maintain that customer you are going to use in plant B in the CMIR where you can give plant A material as customer material and it equivalent plant B material under the material no field. This way while creating order for plant B, you can pass the customer material and the CMIR determines the plant B material.

Regarding your 2nd point on document flow....

You have decided to use PO to create auto sale order for plant B, in that case you cannot build that link in the document flow, rather you can create a new field in additional data B to update the sale order number of A by creating a new field, else it can be updated in any text type (reporting could be difficult), or you can use VBAK--IHREZ (po number field) if you are not planning to use this field to update with plant A po number.

Share
10 |10000 characters needed characters left characters exceeded