cancel
Showing results for 
Search instead for 
Did you mean: 

Plant 1800 does not belong to company code 1000, Message no. KO145

0 Kudos


hi all;,

this error is coming while creating a project in CJ20N...

even though the plant is assigned to the company code.

any idea???

Accepted Solutions (0)

Answers (5)

Answers (5)

0 Kudos

This is a Configuration Issue. Just try checking the list of company code and plant in SPRO

Menu Path-- SPRO--> Enterprise structure--> Assignment --> Logistic General --> Assign plant to company code .

There You find whether the plant 1800 is belonging to company code 1000 or not .

If not, Click on "New Entries" button and add the company code(1000) and plant name (1800) in respective fields and press enter.

Then if u check the list , this entry would be added.

All the best

Lakshmipathi
Active Contributor
0 Kudos

I appreciate your intention to help the members but at the same time, while responding, please also see that you respond to a latest discussion and not to an old one as like this which is 5 years old

nitesh_gawas
Participant
0 Kudos

Hi Suhas,

Please maintain the valuation area for the 1800 plant.

Please check the T0001W table for the valuation.

Regards

Nitesh Gawas

caram
Participant
0 Kudos

Hi Suhas,

Please check for the validation under OPSI, if any.

Thanks,

Sitaram

0 Kudos

nope...no validation as such..

JL23
Active Contributor
0 Kudos
0 Kudos

plant is assigned to the same company code in the customization... but still in cj20n this error is coming up.

sammar81
Employee
Employee
0 Kudos

Hi Suhas

Can you share the screen shots for the same? Displaying assignment of the Co.Cd and Plant and CJ20n.

Also can you check if this error is being wrongly displayed because of some custom code/ development.

This kind of error is very straight forward and if the assignment is correct this should not come..

Regards

Sammar

0 Kudos
varshal_kachole3
Active Contributor
0 Kudos

Hi,

The screen print of Transaction OX18 would have helped. Did you confirm the configuration in OX18 is as per your requirement?

Thanks and Regards,

Varshal Kachole

0 Kudos

yeah OX18 is correctly maintained but still facing this error that's why am surprised.

varshal_kachole3
Active Contributor
0 Kudos

Hi,

Please report the issue to SAP via an incident.

Thanks and Regards,

Varshal Kachole

sammar81
Employee
Employee
0 Kudos

Raise an OSS message doesn't seems to be a standard behaviour..