STO Process – MM STO/Intra /Inter STO (MM-SD Integration)

STO Process – MM STO/Intra /Inter STO (MM-SD Integration)

For Videos Explanation, please go to YouTube and Subscribe -  Studyuuu  SAPMM

STO- Stock transport order

Concept:

Every company will be having many plants and even they have same kind of materials for few kind of production activities, every time procuring from vendor is time consuming and even money because one of the other plant having those stocks without usage, so to save money for the company we use STO process.

SAP has been recommended STO type order “UB” for internal procurement purpose and we can have goods moment within company to company and plant to plant.

STO-There are 5 kinds of STO

1.     One step Method between two plants

2.     Two step Method between two plants

3.     Stock transfer between two plants without delivery (MM STO)

4.     Stock transfer between two plants with delivery without billing (Intra STO)

5.     Stock transfer between two plants with delivery with billing (Inter STO)

1.One step Method between two plants:

One step method means -the supplying plant will transfer the goods to receiving plant and posting goods movement accordingly by supplying plant,

Like using 301 movement in MB1B, the member will transfer the goods to other plant.

2.Two step Method between two plants:

Two step method means- the supplying plant will transfer the goods to receiving plant   and now once they transfer the goods to receiving plant it will get posted in Transit in order stock and when the receiver sees the stock in plant then receiver will post the other movement to move from in transit to plant stock.

Supplying plant will do 303 movement type in MB1B and receiving plant will do 305 movement type in MB1B.

3.Stock transfer between two plants without delivery (MM STO):

This process is also called as MM STO, but many of the companies will use intra or inter      process because of more features wrt stock.

In this case the respective receiving plant will creates a PO, with details mentioned as from which plant and stock required and all the details.

PO will be created with document category UB and item category as U, so that it’s a inter STO PO created for internal stock movement.

Once the PO is created will give to the supplying plant and the from the supplying plant there is a goods movement done by plant person.

Using movement type 351-MB1B, movement of goods will happen once we create PO.

Now the goods will be in in transit and the receiving plant person will be doing MIGO wrt PO, so that stock will show as unrestricted stock.

4.Stock transfer between two plants with delivery without billing (Intra STO)

Inter STO also have the same features as I mentioned below, whereas here the stock transfer is 2 different company codes with different plants and each from one company code.

Here we require help of SD Consultant, whenever you were creating STO PO, we need to take help of SD consultant. Stakeholders need to inform the receiving plant, so that they will be creating the customer code for that particular plant and maintain some distribution channel accordingly for that, As a SAP MM Consultant we need to maintain the backend settings for the receiving plant, so that will get shipping tab in the PO for that particular receiving plant.

This type of process is called MM-SD Integration

        **********We cannot perform 3^rd scenario if we are working 4^th as present, to work for 3^rd scenario we need to delete the settings for 4^th step and process always*********

Requirements

We need to ensure that material that we are shipping from 1 plant to other plant should be extended in material master for both the plants.

Both the materials should have sales and purchasing and accounting views mandatory.

Sales data will be given by SD Consultant and if not, we can request SD Consultant to give the sales data to update for the material master.

Ensure to select all the 3 sales views and maintain the important data required in all the 3 screens to avoid SD errors.

In Material master we need to maintain the standard language for those receiving plants-Additional Data-Languages, Maintain the language like DE_ Germany

Ensure stock is there in supplying plant, or else we will get error in OBD-Outbound delivery

Back-End settings for Shipping (Intra):

To get shipping tab details in PO, we need to maintain few backend settings for PO-STO

SPRO-

            Materials Management-      

                                                Purchasing-

                                                            Purchase Order-

                                                                        Setup STO

(!) Define Shipping data for Plants:

Here we need to define the shipping data for plants, maintain the receiving plant details like -double click on receiving plant-Enter Customer number, Sales organization, Distribution channel E.t.c.

All the Above information will be given by SD Consultant.

Enter all the details and save the screen.

(!!) Assign delivery type and checking rules:

We need to maintain the delivery type and some checking rules for this step.

Order type as Order type-UB

Supplying plant-

Delivery type- NL(Intra)

We have 2 delivery types NL and NLCC

Checking rule maintain as 01

(!!!) Assign Document type One step Procedure, Under Tolerance

SPL plant –

Rece plant-

Order type-

Once we done all this correct -PO will take shipping tab automatically for this scenario.

Process:

We have done with backend settings, now create PO- Me21n and mention the purchasing document as UB and item category as U.

Enter the material, shipping plant and receiving plant- enter the quantity and other data-PO will pop up a Shipping tab with NL order type.

Now let’s think shipping pant is having stock to create OBD.

OBD is the process where shipping plant will create a delivery invoice in which material will be adjusted to move out to receiving plant.

VL10D-Outbound Delivery

Open VL10D and Purchase orders- maintain the purchase order and check the dates the PO delivery is between that dates and execute -so that it will take to quantity screen and select line and go to background.

If you want to check the log- check and take the OBD number or else if any errors found, try to resolve.

PGI-

Once the OBD is done, the supplying plant should issue the goods to receiving plant, for that they require PGI-Post goods issue.

PGI will be done based on OBD quantity and same will be moved as intransit.

VL02N-PGI will be done with OBD reference number – just take the picking tab and mention the quantity as OBD posted and post PGI.

Once PGI is posted, goods will be moved to intransist and we can see in MMBE stock report-in transist.

If we check for movement type happening its 641 and once everything is done and goods received to plant, then post MIGO

Following with MIGO with OBD and not with PO, Post MIRO and this Intra goods concept has been end.

*****there will be no billing for with in company code transfers **********

5.Stock transfer between two plants with delivery with billing (Inter STO)

Inter STO is also same as intra STO, whereas we have little different because vendor (XK01) is involving in terms of supplying plant.

Why we are involving vendor, because they should be billing to be done to supplying plant from receiving plant.

Inter STO is also called as MM-SD Integration

Because higher level credits and debits will be involved for company code level, here two different company codes, so billing should TAKES PALCE.

We will be creating material as normally and maintaining in both the plants as we did for intra STO by maintaining sales data for both.

Now create maintain a vendor and inside purchasing data -maintain for plant as supplying plant-once you enter vendor in PO -it will take supplying plant backend.

Requirements

Material (SP+RP)

Vendor-Purchasing to plant as SP

Customer number from SD Consultant

Back-End settings

Define shipping data for plants

Maintain the receiving plant customer code and remaining data that received from SD Consultant

Assign Delivery type and checking rule

Here we re creating PO with Document type NB- because vendor is involving indirectly

NB document type

Item category -Standard

Assign Document type One step Procedure, Under Tolerance

Document type is NB-mention the shipping and delivery plant and save the back-end settings.

Process

Now we can create a PO, with NB document type and blank item category, whereas we already maintained vendor as plant in XK01.

Now as per the backend settings and XK01 vendor mater shipping tab will come automatically with delivery type NLCC

Now post OBD-Outbound delivery, VL10D-proceadure has been explained above

Now post the PGI-Post goods issue with respect the OBD and once PGI is posted goods will be in intransist.

Now do the billing for the plant to which we are sending through VF01 and this implies with billing from the respective cost center.

Now we can do the MIGO with respect to OBD and following with MIRO.

This Completes the process of Inter/Intra STO.

Consignment Procurement and Pipeline process in SAP MM

Consignment and Pipeline process in SAP MM

For Videos Explanation, please go to YouTube and Subscribe -  Studyuuu  SAPMM

Consignment:

Consignment is a process of material procurement from the vendor, but stock lies in plant premises, but owner of the product is vendor, even its same process of creating normal PO but item category is K.

Concept:

Normally we use to purchase the stock from vendor, in this case we will purchase the stock, but we don’t know when we will use that stock for the production. So, for that we have SAP recommended procurement process-Consignment, where stock keep in the plant and there is premises for vendor -we can call as vendor consignment stock, whatever the stock present in plant the owner will be vendor and when we require any stock then we can move that stock from vendor consignment stock to production stock and we will post MRKO instead of MIRO, so that report will be generated for the transfer stock and vendor will get paid for that.

If we withdrawal any stock from vendor consignment stock like 5 PC, then MRKO will be done with 5 quantity and vendor will get paid for 5 PC.

The refilling process will be done by creating a PO with account assignment K for only filling the gap stock.

PIR:

If we are creating consignment PO, then few mandatory things are PIR. Where price and tax code will be calculated from PIR itself, because we don’t have price in PO.

The reason we don’t have price in PO is -Price will get fluctuate every month and stock lying with us we will use, and we don’t know when we will use that stock.

Every month price will be given by the vendor for the material and purchasing team will update the price in PIR and when the stakeholders do MRKO, the price will be picked from PIR for that month.

One mandatory thing is PIR should be created to subcategory Consignment.

Process:

Create a material, vendor and PIR-mandatory and create a PR with this thing with item category K-consignment.

Once we create PO for the above PR, the stock in MMBE shown as In-order Consignment stock.

Then once you receive the goods to plant then do the MIGO for full quantity.

Now check the stock for the material and plant in MMBE, it will show as stock lying with vendor as vendor consignment stock.

When you do MIGO, the movement type will be taken automatically 101-K, where it’s a consignment.

Here coming to accounting data- there is material document created but there is no FI document posted.

Now as per your requirements we need to transfer the goods from vendor consignment stock to our own stock by movement type 411-K

Now will stock will be lying in unrestricted stock

If we do transfer for 5 PC then we need to do MRKO for 5 PC, so that Invoice will be posted automatically for 5 PC and vendor will get paid for 5 PC.

Whenever we do stock transfer from vendor consignment stock, we need to do MRKO.

If we want to move from vendor consignment stock to direct production/cost center and department, then we need to know their cost center so that we can transfer goods directly from vendor 

consignment stock to cost center by movement type 201 K or 261 K

While moving vendor consignment stock to direct production/cost center and department a material document as well financial document has been created with BSX and WRX.

Whenever there is financial document is created then GL account will hit for debit of their respective cost center GL account.

We can do initial posting of goods to any plant by T-code MB1A -561 movement type, normally we will do this when client is using different ERP and transferring to SAP.

Same as above we have MB1B for the goods movement from 1 place to other

We have MB1C for Goods issue, we can also have goods receipt without PO and for also free goods.

Running cycle for Consignment:

Let think now we have a requirement for some materials, but we don’t know when we use these materials fully, in that case requester has been ordered for Consignment -Created a consignment PR 1164 with 100 PC.

Now the purchasing team will create a PO 2264 for the PR 1164, few of the mandatory things are PIR with subcategory K -quantity 100 PC.

Once we create PO, the stock will show in MMBE-Consignment stock for that plant as 100 PC

Once we receive the material to plant the respective receiver will post the GR in MIGO-sating material has been received to plant and placed in consignment stock (Posting MIGO for full quantity-100 PC).

Now the stock will show in vendor stock in MMBE as 100 PC

Now check for FI postings- because vendor has been delivered goods to plant- in normal case a Material doc and FI doc will be created automatically.

In this case, we have only material stock gets posted, and FI doc will not be created because it’s a consignment- stock lying in vendor consignment stock.

Process has been completed for procurement, now the actual process will come into picture.

The purpose we ordered material is for production requirements, now the stock is in vendor consignment stock and we need to use for own purpose or industry purpose.

In this case, we need to use “Goods transfer” from one stock to other stock with the help of movement types.

We have already stock in vendor consignment stock in our plant, so just we need to move to our own stock by using movement type 541(vendor consignment stock to own stock)

We can also use 201 K and 261 K for directly move the stock from vendor consignment stock to cost center which are using those goods.

Once we do the goods transfer the stock will get moved to plant own stock, once we do this a material document has been posted along with that there is a financial document has been posted(because we are using vendor consignment stock and we need to pay to the vendor).

Just think we have moved only 10 PC instead of 100 PC.

Now we need to do the MRKO process, where we need to mention the material and plant the select the settle option which are not settled.

Once we do the MRKO for 10 PC, then APAY will run the cycle and match the reconciliation quantity and vendor gets paid for 10 PC.

Whenever we use the quantity from vendor stock, we need to do MRKO, so that vendor will get paid.

Why MRKO and Why not MIRO?

Because in MIRO, you cannot post the split price. We need to do full invoice.

Whereas in MRKO, we can do split invoice.

Pipeline Procurement:

Pipeline procurement is the process where, material will be flowing from the vendor premises to plant premises, and there is no material is listed in inventory and we cannot measure the stock anywhere in MMBE or other T-codes because its flow like petrol, current and coming to payment its similar to consignment.

There is no PR and PO required for pipeline.

But PIR is mandatory for Pipeline material and while creating material master we need to select the material type as Pipeline material.

Update the PIR price and tax code or else we can receive an error in MRKO posting

Coming to enterprise structure – Standard purchase organization must be linked to this plant, because we are doing special procurement and always for special procurement plants, it must be linked to standard purchase organization.

Process:

Whenever we require any quantity from pipeline and process the MRKO, just we need to release the quantity and coming to power usage, we need to maintain MRKO on monthly basis as used power watts and vendor gets paid for that.

We can take the goods directly in plant and coming to SAP we have movement type 201 P and 261 P to maintain the goods issue.

Once goods issue is done as per the usage, we need to post the MRKO as settled for unsettled usage.

Few Important points to be noted:

Tax code in PIR will be defined by SAP FI consultant, and if we require then raise a ticket for them and get the tax code and assign in PIR.

We will not do MIRO for consignment and pipeline and instead of that we use MRKO, where backend FI document has been created for the payment purpose.

Once the invoice is posted in normal PO’s then we need to do credit note only if any issues found and after cancel the GR and repost.

Any extra pay for vendor we needs to use the subsequent credit to vendor and directly we cannot maintain in MIRO.

Please like and comment the blog…………Only if you like the content in Blog

Difference between Purchase Organisation/Standard/Referenced along with Mass maintenance

Purchase Organisation-Standard P.org and referenced Purchase Organisation

For Videos Explanation, please go to YouTube and Subscribe -  Studyuuu  SAPMM

1.Purchase Organisation:

            Purchase organisation main responsibility is to maintain the proper purchase related activities and they will take care of all requirements for that plant/Company code as you assigned in the organisation structure.

Each purchase organisation has been linked to 1 plant (Plant wise) or 1 company code (Company code wise) or Client wise (1 purchase organisation for the client).

When do we maintain 1 Purchase organisation?

When we have the company worldwide and even vendors are also in worldwide who is supplying for all countries then we can maintain the centralised purchase organisation-where it controls all terms and negations for all the plants in the world.

This is the normal way for all the companies maintaining purchase organisation.

Cons: we cannot get the individual data of one country and if getting its too hard to calculate purchasing activities.

This is called centralised purchasing- once purchase organisation controls centrally for all the company codes.

When do we maintain 1 purchase organisation for 1 company code?

We will maintain the purchase organisations as per the company code, it means 1 purchase organisation = 1 company code.

Where we have many vendors, but they can provide with in the country and there was no import and export then we can maintain individual purchase organisation as per the company code.

In this case each company will be having 1 company code.

This purchase organisation will manage the all the plants in the respective company code, it means all the purchasing activities.

Same purchase organisation needs to be maintained for all the plants in that company code, in this case reporting will be easy and managing also easy but you will not get more discounts.

When do we maintain 1 purchase organisation for 1 plant?

We will maintain 1 purchase organisation for 1 plant, where purchase activities will take in the plant itself and it can control only that plant.

If we have 1000 plants around worldwide then we can have 1000 purchase organisations.

This is called distributed purchasing

When do we maintain 1 purchase organisation for 2 plants with different company codes?

As we know we cannot maintain 1 purchase organisation for 2 company codes.

Then we can get succeed through plant level, where company code A contains 1 and 2 plant with purchase organisation controlled by X.

Now, company B contains 3 and 4 plants with purchase organisation controlled by Y.

Now we need to assign 1 purchase organisation for 2 plants which was controlled by 2 company codes.

Assign plant wise, as systems allows that 1 plant can be controlled by 2 purchase organisations, then in plant wise maintain the 2-purchase organisation (Setup in enterprise structure)

So that 2 purchase organisations controls different plants with different company codes.

2.Standard Purchase organisation:

Standard purchase organisation is same as normal purchase organisation, where in normal purchase organisation the plants will not be used to other activities like consignment and pipeline procurement.

If the plants are using different procurement activities like consignment and pipeline then the plant should me maintained by other purchase organisations, in that case we can define that as standard purchase organisation.

Standard purchase organisation will control mainly for consignment, pipeline and other special procurement activities.

3. referenced Purchase Organisation:

Referenced purchase will be used for contracts and scheduled agreements purposes.

Lets think we have a contract that is having some company code and all the plants in that company code, now even some other purchase organisation also use this contract because you have some less prices in contract, then in that case we need to maintain the different purchase organisation, different company code plants we should use in contract.

We cannot maintain directly in that contract, because it will allow only 1 company code and 1 purchase organising plants only, now we need to maintain the referenced purchase organisations with purchase organisation.

Once we maintain that linking in enterprise structure then system will allow to maintain those plants in contract, and it can be released through contract to orders.

We need to do all this setting in enterprise structure.

Basics in Enterprise Structure for Learners

As a MM consultant we will not define full implementation, here client and company code will be created and maintained by FI Consultant

MM consultant will define only Plant, Storage location, Purchase organisation, Purchase group.

Plant: while we are defining new plant, system will ask for factory calendar settings number- defined by PP consultant.

Once we maintain all the assignment then we can check the flow in EC02, whether the flow has been maintained correctly or not.

If we are creating plant then we will create few plants which will be used for STO purposes then we need customer number to be maintained for Intra STO, in that case SD consultant will prepare and send it to us.

Plant: we must copy the plant as always from pre-defined plants by SAP, because we have many settings backend if we have created new but knowing is good for your knowledge.

Material Statues and Mass maintenance in SAP:

As we are creating material master will create many materials and all the tabs related to MM needs to be updated by us, in this case we have few tabs -controls the materials for many activities. For example, purchasing block, inventory block and many more.

We have options in 2 levels

1.     Purchasing level

2.     Client level

First, we need to define our own material status as per the client requirements in the path below.

SPRO-Logistics general- settings for key fields- define material status

Define our own name and select the level of block like only for purchasing or only for inventory or else both.

Its goods to have individual blocking codes, so that there is no clubbing.

Basic data- always in client level and if we maintain X-plant material status then it applies for whole plants in the client.

Purchasing tab- when we maintain X-plant material status then its will be applicable for only 1 plant as we maintained.

Mass Maintenance

We will create lot of materials and if we get requirement to update certain fields for all those materials then we cannot do all those manually.

For those things we have mass maintenance, where we have certain T-codes from where we can do that activity.

For these things we should aware of table names MM, so that we can maintain at a time.

As per tab wise table name will get change – Material master try -MM17

For vendor master try – XK99

Note: if we don’t know that from which table, we need to maintain these things then try for T-code MASS, where select the activity as per that and process accordingly.

Organization Structure/Enterprise Structure in SAP MM

Organization Structure/Enterprise Structure in SAP MM

For Videos Explanation, please go to YouTube and Subscribe -  Studyuuu  SAPMM

Organization structure:

Organization structure explains their structure/Hierarchy of the company they follow to run there business on daily basis, Every company will follow the same structure up to some level but every company which are in SAP family then they have 90% same structure and 10% may differ as per there rules/regulations/standards.

Organization structure contains may levels, where each level is having their own tasks/rules and no one can by-pass the hierarchy, because SAP is having those features where we cannot process further even, we miss one small hierarchy (Assignment).

Every level in the organization structure are inter linked with one other having relationship like Example below.

A=B=C=D (Just overview) as same as (D=B=A=C) (Just overview)

Requirement:

Let’s think A company is having ERP tool (Non-SAP) and thinks that production and sales activities are not as per the standards and profit centers are not calculating properly which may leading to losses in sales and business.

Now company would like to move to ERP-SAP, in which all the things should be correct to maintain the proper daily activities and even higher management no needs to ask anyone for reports or goods inventory or sales management details from the departments.

Higher management can see the reports/stocks/profit centers/sales in the SAP directly, with no support from anyone, and even employees and customers need to follow the process for sales as well as production from the organization. There is no such deviation in the company to flow the profits outside, so many companies are moving to SAP to increase the standards of there company even SAP is cost effective.

Now SAP consultants will come into picture, where SAP provides the standard settings to their customers once you buy the ERP-SAP to your company, now consultants in the company sit with higher management for the discussion for the flow and the process.

MM/FI/SD/PP will be supporting for functional process of SAP, ABAP/Basis will be supporting for technical and even we have many but company follows other modules as per there requirements, whereas mentioned modules are very important for them to design and make settings properly as per there company conditions.

Backend Settings:

SPRO- It’s the T-code for backend settings.

SAP reference IMG will take you to the path of the settings.

Defining Requirements:

As we spoke above enterprise structure contains many levels and each level will be having their own roles and responsibilities, they may maintain all these levels as per there business requirements or legal reasons.

Hierarchy.

1.     Client/Company

2.     Company Code

3.     Plant

4.     Storage Location

5.     Purchase Organization (Will speak in depth below)

6.     Purchase group

1.     Client/Company (FI Consultant will define this)

                                    A client is the highest level in the organization and its independent with having their own master data and can pull reports of all company codes under that client.

Whatever Master data maintained in the client level is valid for all the levels in the organization structure. Under one client we can have N number of company codes as per there requirements.

2.     Company Code (FI Consultant will define this)

                        Company code is maintained under the client, where company code is an independent accounting unit in the entire organization structure, where all the profit, loss and balance sheet accounts has been maintained by the company code.

Eg: let’s think for 1 country = 1 company code

If the client would like to know the profit loss accounts for one country Eg: India, then they can pull reports within few minutes you can have the exact data of profit loss balance sheets.

3.     Plant (MM Consultant will define this)

A plant is an organization unit within the company code, where all the production activities and make finished goods available in the plant for the sales purpose.

All the logistics will be taken place in the plant and even warehouse activities will take place. Every material valuation will take place at plant level only.

4.     Storage location

Storage location is the place where stock gets separated, where we have many types of stocks in plant and we need to separate the stocks as per there nature, like raw materials, packaging, semi-finished goods.

Each material types will take place one storage location and we can maintain N number of storage locations in one plant, and main thing is we can stock the physical stock. Material data can be maintained at storage location level and as well plant level also.

5.     Purchase Organization:

Purchase organization is the part of hierarchy, where they will be responsible for purchasing activities in the respective plants or Company.

Here we can assign 1 purchase organization to 1 company code and needs to assign to all the plants, so that that purchase organization will be responsible for all the plants in that company code.

Or else, we can assign the purchase organization to plant and every plant will be having their respective purchase organization, so that every plant is independent with their own purchase organization

****Purchase organization is responsible for all the purchasing activities in the respective plant, if we assign as decentralized-plants wise****

Even we can do like, 1 company will have 1 purchase organization, where it’s called centralized purchasing.

1.     Centralized purchasing

2.     Company specific

3.     Plant specific- decentralized

Example:

 lets think we have a company IIIM- where its having centers in all the countries like US, UK ,Germany(plants) and some countries, now we have company codes, plants and respective storage locations, as we have all these we need the production to be taken place on daily basis and so we need purchase organization to fulfill this activity, for example we need today some engines and required immediately for production purpose and 1) If we have centralized purchasing then headquarters in US company-Purchase department will take up the decision to buy that engine and 2) if we select company specific then let think each country will have 1 company code and respective department will take up the decision and last one 3) plant specific- lying in your plant and will provide approvals for purchase.

Cross purchase organization (1 Scenario):

As I told in above scenario, each company code will be having their own purchasing organization (Company specific), in this case if suppose you want 1 purchase organization to be responsible to 2 company codes.

Its not possible to link 1 purchase organization to 2 company codes but we have something like cross purchase organization, its possible in plant level, where we can link purchase organization to plant with 2 different company codes.

Reference purchase organization:

Reference purchase organization will come into picture only if your company is using centralized purchasing.

We can create a one referenced purchase organization, and we can link to company specific purchase organizations, such that we can use this purchase organization when you will create contract with different plants with different purchase organizations.

Reference P.Organization-----Contract---different P.Organizations-Different plants

Example: let’s think we are managing a company where we have 5 plants with different locations and every time we use to purchase individually let think monitors we will buy for 10000 and each plant individually buys for around 9900-10000 as per the purchasing organizations and markets in the state. Now lets think reference purchasing organization will come –we have contract with reference purchase organization where will create only 1 contract with 1 big vendor and maintain all the plants in the contract that which are belonging to different purchase organizations, will order in bulk for all the plants whenever its required, so that will get for less price. so that we can procure that monitors for only 9500-9900(Quantity scaling will come into picture if we buy more monitors).

Better negotiations will be possible with reference purchase organizations.

****Behalf of other purchase organizations referenced purchase organizations will come into picture for all activities for better production/pricing.

6.     Purchasing group

Purchasing group is an independent entity, where it explains the responsible buyer/ responsible group of buyers for those materials.

We can manage this in MM01, there was no assignment for the purchase group and MM persons will define this purchase group.

Backend settings-Definition and Assignment

Client

SPRO-Enterprise Structure-Definition-Define Company-New entries and maintain the client

Mention all the details in client like address and other things and save.

Company code:

            SPRO-Enterprise Structure-Definition-Edit, Copy, Delete, Check company code-New entries.

Mention all the details and save.

Plant:

            SPRO-Enterprise Structure-Definition-Logistics general-define plant

Maintain all the plant details as shown in their screen.

Always take copy org from 1000 plant, which is predefined by SAP.

Storage Location:

SPRO-Enterprise Structure-Definition-materials management-define storage location

We are maintaining plant while creating storage location and no need of other linking.

Purchase organization:

SPRO-Enterprise Structure-Definition-materials management-Define purchase organization

Assignment of all above Hierarchy:

Plant to Company code:

SPRO-Enterprise Structure-Assignment-Logistics General-Assign plant to company code

Purchase organization to company code:

SPRO-Enterprise Structure-Assignment-materials management-Assign Purchase organization to company code

Purchase organization to plant:

SPRO-Enterprise Structure-Assignment-materials management-Assign Purchase organization to plant code

Standard Purchase organization to plant

SPRO-Enterprise Structure-Assignment-materials management-Assign standard Purchase organization to plant code

Note: Next Blog will be Account Determination.