Jan 26, 2013

MM Process flow in SAP


MM Process flow:

The typical procurement cycle for a service or material consists of the following phases:

1. Determination of Requirements:

Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.

2. Source Determination:

The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.

3. Vendor Selection and Comparison of Quotations

The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.

4. Purchase Order Processing

The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.

5. Purchase Order Follow-Up

The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.

6. Goods Receiving and Inventory Management

Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.

7. Invoice Verification

The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.

Common Tables used by SAP MM:
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types

Transaction Codes:
RFQ to Vendor - ME41
Raising Quotation - ME47
Comparison of Price - ME49
Creation of PO - ME21N
Goods Receipt - MIGO
Invoice (Bill PAssing) - MIRO
Goods Issue - MB1A
Physical Inventory - MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)

SD Process Flow in SAP

SD PROCESS FLOW:

1. Sales Inquiry.
2. Quotation.
3. Sales order.
4. Delivery/Shipping.
5. Billing.
6. Invoice.





Sep 13, 2012

Client copy


A client copy does not "generate a new system". It is used to transferinformation between clients within the same system or to another system atthe same release and db level.

Procedure to create:
If it is a fresh installation, do this --
1. SCC4 --> Create client no. and fill other details.
2. Logon to the newly created client with SAP* and PASS as password.
3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client .
4. Preferably do a test run initially to check if it can go well.
5. As a care check space in databases.

You can do Client copies remotely or do an export/import of data. Please study the dependancies of client dependant/independant data rel.notes.
Export: If you need to do a full client copy and database is more than 50 or 60gb, the import may tae little long time. Export of the full data can be done with SAP_ALLprofile in Source system. SCC4 >> Export the data with required profiles. It will create data and cofiles under os level. (usr/sap/trans/data, cofiles).The export may take of 8 to 20 hrs dependts on data.The import may take several days based on the size of the data. You need to set some parameters before you start the import. After the succefull import you need to do post processing for client copy with request in SCC8.

It depends upon what method you want to do client copy.
If you say remote client copy, i will suggest you against it because it takes hell lot of time to do client copy and any break for a moment in network connection will cause failure in client copy.If you are exporting the client then as such there is no problem, just remember the sequence in which you import the three (or two) transport requests.AND, keep enough free space in Tablespaces of Target server.

Procedure :
1.Check Sufficeint space at OS level to keep extracted data from source client
2.Export the client using following path or scc8Tools (r) Administration (r) Administration (r) Client Admin. (r) Client Transport (r) Client Export. Select the data to be copied using a profile. (if u wnat client specific and cross client data use profile sap_expc). before importing ensure that all table spaces have enough sapce for this check source system table spaces and allocate table space accordingly)
3.Now create new client in target system
4.now import those requests in target client using stms or scc6
5.Now perform post processingTools (r) Administration (r) Administration (r) Client administration (r) Client transport(r) Import editing

Sep 8, 2012

There are 3 standard clients in sap r/3 system. They are 000, 001 and 066. These three clients come with default users along with default passwords. I have listed in the following paragraphs.

What is a client: A client is an independent unit within the R/3 system or an area in the system with data on which a user works.
We have to do client copy right after installation of the software as our first job to begin the technical phase of implementation. We have to copy from one of the standard clients available. We can use copied clients for testing, training or for starting real customization.

We will discuss about what is data and what types of data is available in the sap R/3 system before going into the explaining of definition of the standard clients.

Data: The information residing in the database tables is called data. There are different types of data involved in the R/3 system. They are client dependent data, client-independent data and the client repository data.
Client dependent data: The data which is accessible through a particular client is called client dependent data. The user data is one of the examples of client dependent data.

Client-independent data: The data which can be accessible from any client or which is common to any client in the system is called client-independent data. The transaction code or t-code data is example of the client-independent data.

Client repository data: The different application programs which makes SAP runs is called client repository data. The transaction data, application data, customizing data are other different types of data of the sap r/3 system.
Standard clients of the SAP R/3 system:

000 Client: This client is called as master client in the r/3 system. This client is included in the sap r/3 system as default. We can find this client in the system as soon as we install sap r/3 software. Client 000 contains a simple organizational structure of a test company and includes parameters for all applications, standard settings, configurations for the control of standard transactions and examples to be used in many different profiles of the business applications. For these reasons, 000 is a special client for the R/3 system since it contains the client−independent settings. We can access the entire standard data with this client. We should not do any changes in the data through master client. The default users of this client are mentioned below along with default passwords.
  • User name: sap*
  • Password: This password will be set by the person during the sap r/3 installation
  • User name: ddic
  • Password: This password will be set by the person during the sap r/3 installation

001 client: This client is best example for customizing or development client and we can access entire customizing data. This client is a copy of the 000 client including the test company. This client’s settings are client-independent if it is configured or customized. This client is reserved for the activities of preparing a r/3 system for the production environment. The customers of the SAP normally use this client as a source for copying other new clients. The default users and passwords of this client are listed below.
  • User name: sap*
  • Password: 06071992
  • User name: ddic
  • Password: 19920706

066 Client: This client also called as early watch client which is reserved for sap access. SAP will access their customer systems using this client to perform the Early Watch service. SAP will generate the performance report of its customer system and this report is called as Early Watch report. The default users of this client are listed below.
  • User name: sap*
  • Password: 06071992
  • User name: earlywatch
  • Password: support

How to change Transport request from Released to Modifiable

Step 1: Go to SE38 – Execute Program RDDIT076.  Step 2: Give your released requests number and execute again. Step 3: After executing, yo...