SAP Enterprise Structure – A Case Study (part 7): Define Plant




This is the part 7 of the series of articles about SAP Enterprise Structure – A Case Study. Read part 1 here.

Define Plant

For the business scenario, we will create the following plants:

  • A001 for the west region of the ABCD company
  • A002 for the east region of the ABCD company
  • E001 for the office and warehouse of the EFGH company

There are two options to create company code:

  • Copy from other plant (or from SAP standard plant)
  • Create from the scratch

The advantage of copying from existing plant is SAP will also copy the existing plant-specific parameters, such as Consumption-Based Planning plant parameters, which include purchasing processing time, MRP Controller, etc. Then we can change certain data in the relevant application if necessary. This is much less time-consuming than creating a new plant.

But in this book we will create plant from the scratch so we have to define other parameters need in other relevant configuration process manually.

We create plant from the following menu path of “SPRO” t-code: IMG – Enterprise Structure – Definition – Logistics-General – Define, Copy, Delete, and Check Plant.

We can create plant by copying it from other plant or starting from the scratch. In this book, we will create plants from the scratch.

The above image is © SAP AG 2011. All rights reserved
The above image is © SAP AG 2011. All rights reserved
The above image is © SAP AG 2011. All rights reserved
The above image is © SAP AG 2011. All rights reserved

Do the same steps to create other plants.

In the next article, I will explain about hor to Define Valuation Level.

Notes:
You can read the full contents of the SAP enterprise structure – a case study as soon as you buy the e-book at: SAP Study Materials Store


Leave a Reply

Your email address will not be published. Required fields are marked *