Scribd
Upload
12 views

SAP Architecture

There are typically three clients in an SAP system landscape: a development client for customizations, a quality/testing client to test changes, and a production client for real transactions. Customizations are transported between clients using transport requests. Some customers use separate sandbox and golden clients for configuration instead of a single development client. The golden client contains approved designs only. Material requirements planning (MRP) generates planned production orders based on independent requirements and sales orders according to the selected planning strategy.

Uploaded by

Khadeer Ahamed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
12 views

SAP Architecture

There are typically three clients in an SAP system landscape: a development client for customizations, a quality/testing client to test changes, and a production client for real transactions. Customizations are transported between clients using transport requests. Some customers use separate sandbox and golden clients for configuration instead of a single development client. The golden client contains approved designs only. Material requirements planning (MRP) generates planned production orders based on independent requirements and sales orders according to the selected planning strategy.

Uploaded by

Khadeer Ahamed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

SAP Architecture

CLIENT DESCRIPTIONS:

The system landscape varies for each customer but will always have a minimum of three
clients: development, quality/testing, and production

The development client is where the customization and development work take place. After the
development work is completed, the customization object creates a transport request in the
development client, and the object is transported to the quality/testing client. Finally, after it
has been tested and found satisfactory, the object is moved to the production client. End users
interact with the production client; day-to-day operational transactional data is entered here.
Because the production client is used for real-time data, it’s very sensitive. Any test transaction
posted in the production client is posted in a real-time business transaction of the customer, so
you must be careful while working on the production client.

Some SAP customers create two separate clients (a sandbox client and a golden client)
instead of one development client. A sandbox client is mainly used for configuration ideas and
development, and it’s also where system design work takes place. When you are comfortable
with your configuration solution in the sandbox client, you must reconfigure your solution in
the golden client. If the configuration in the sandbox client isn’t appropriate, it isn’t
reconfigured in the golden client. Sandbox clients may contain many additional customizations
that haven’t been reconfigured in the golden client. The golden client is configured only for
approved designs, so it’s always a clean system.

The golden client is also known as the configuration client. Ideally, no transactions or
testing takes place in the golden client, which means it doesn’t have any master data or
transactional data. The golden client is used only for configuration and to transport the
configuration to the testing/quality and production clients.

TRANSPORT REQUESTS:

Transport requests are used to move configuration settings from one client to another
and are created automatically when you make any changes to configuration tables or programs.
When a transport request has been created, it can be moved to another client only if it’s
released. Basis consultants are responsible for transporting transport request from one client to
another.

Demand Management:

Consumption Mode:

Make to Stock:

Planning strategy – 10 (Net Requirement Planning)

Planned order will be generated for the independent planned requirement by taking into
consideration the stock available. Sales orders are not considered in this planning strategy. For
example if we have a stock of 200 units and the PIR is for 250 units, then the planned order will
be generated only for 50 units taking into consideration the stock available.

1. Create planned independent order/Maintain the data in Demand Management with T-


code MD61.
2. Check the stock/requirement list screen in MD04.
3. Execute MRP in MD02.
4. Convert the planned order into production order in MD04 screen.
5. Move stock using goods receipt in MIGO.
6. Create a sales order in VA01
7. Delivery to the customer using VL01N.

Planning strategy – 11 (Gross Requirement Planning)

Planned order will be generated for the independent planned requirement only excluding the
stock available. Sales orders are not considered in this planning strategy. For example if we
have a stock of 200 units and the PIR is for 250 units, then the planned order will be generated
for 250 units without considering the stock available.
1. Create planned independent order/Maintain the data in Demand Management with T-
code MD61.
2. Check the stock/requirement list screen in MD04.
3. Execute MRP in MD02.
4. Convert the planned order into production order in MD04 screen.
5. Move stock using goods receipt in MIGO.
6. Create a sales order in VA01
7. Delivery to the customer using VL01N.

Planning strategy – 40 (Planning with Final Assembly)

Planned order will be generated for the independent planned requirement by considering the
sales order also. For example if we have a PIR of 200 units and got a sales order for 200 units,
then the sales order will directly consume the independent planned requirement of 200.

1. Create planned independent order/Maintain the data in Demand Management with T-


code MD61.
2. Check the stock/requirement list screen in MD04.
3. Execute MRP in MD02.
4. Convert the planned order into production order in MD04 screen.
5. Move stock using goods receipt in MIGO.
6. Create a sales order in VA01
7. Delivery to the customer using VL01N.

Make to Order:

Planning strategy – 20 (Pure make to order Planning)

In this no planned independent requirements will be present. Production or manufacturing will


be carried out only when a sales order is available. For example if we have got a sales order for
100 units, then based on the sales order a planned order for the same quantity is generated
and is converted into the production order. In this strategy the raw materials, semi-finished
materials and packing materials are procured once the sales order is received. Hence the
delivery time is more in this strategy.

1. Create a sales order in VA01.


2. Check the stock/requirement list screen in MD04.
3. Execute MRP in MD02.
4. Convert the planned order into production order in MD04 screen.
5. Move stock using goods receipt in MIGO.
6. Delivery to the customer using VL01N.

Planning strategy – 50 (Planning without final assembly)

In this planned independent requirements will be present. Production or manufacturing will be


carried out only when a sales order is received. For example if we have got a sales order for 100
units, then before the sales order is received planned order for the raw materials, semi-finished
materials and packing materials are generated. In this strategy also the raw materials, semi-
finished materials and packing materials are procured before the sales order is received. Hence
the delivery time is less in this strategy.

1. Create planned independent order/Maintain the data in Demand Management with T-


code MD61.
2. Check the stock/requirement list screen in MD04.
3. Execute MRP in MD02.
4. Convert the planned order into production order in MD04 screen.
5. Move stock using goods receipt in MIGO.
6. Create a sales order in VA01
7. Execute MRP in MD02.
8. Move stock using goods receipt in MIGO
9. Delivery to the customer using VL01N.

Material Requirement Planning (MRP):

You might also like