Beruflich Dokumente
Kultur Dokumente
Sales flow
Quotation inquiry Sales order Delivery Post goods issue Invoice
Accounting document
This is the Main flow and in between there are many integrations with other Modules like MM, FI, PP
So first get familiarize with the SD stuff and then you can learn the Integration.
You have to know the functionality of each field , then it will be easy to understand the End to End flow.
load master data of SD, MM , HR and FI-CO from R/3
Step 1: Activate the Master Data Data Source in R/3 using RSA5 transaction.
Step 2: Replicate the Data Source to BI.
Step 3: Craete Transformation using the above data source.(Before this step make sure that your
InfoObject is in the InfoProvider menu as a data target. If not make this. To do this go to the InfoArea
under which you wnated this InfoObject, Right Click and Insert Characteristic as InfoProvider)
Step 5: Create DTP.
Step 6: Create InfoPackage and load the data upto PSA.
Step 7: Then run the DTP and load to the InfoObject.
Then activating and attribute change run are commonly...
SD Data Sources:
Document Header: 2LIS_11_VAHDR
Document Item: 2LIS_11_VAITM
Document Condition: 2LIS_11_VAKON
Document Schedule Line: 2LIS_11_VASCL
Document Item Allocation: 2LIS_11_V_ITM
Allocation Schedule Line: 2LIS_11_SCL
Order Delivery: 2LIS_11_SSL.
MM Data Sources:
Goods Movements: 2LIS_03_BF
Stock Revaulations: 2LIS_03_UM.
The preconfigured Financial Data Mart scenario contains the following objects:
Extractors
Transfer of aggregated transaction data from the Analytics Layer of the Bank Analyzer
subledger
Six InfoCubes
Balance sheet, income statement, ERP GL, Financial Data Mart, and three virtual
providers
o
o
Process chains
Queries
Balance sheet, income statement, and notes
The data from the Bank Analyzer subledger adn general ledger are reconciled
using a rule-based logic defined in the transformations. This ensures that the level
of detail used in the subledger is retained, and that none of the amounts that exist
in both sources are duplicated in reporting.
What are the Business content Cubes, ODS and some other objects in SD,MM,
FI-Co modules we use regularly in implementation.
I can give the process fllow of different modules!
SD Flow
You create a sales document to enter information about different sales transactions. R/3 provides a
number of predefined sales document types. However , these can be customized to suit your company's
needs when R/3 is installed.
Some examples of sales documents include:
sales queries
sales orders
outline agreements
complaints
You use sales queries to enter information about potential sales into R/3.Types of sales query
documents include:
inquiries
quotations
free-of-charge deliveries
An inquiry is used to record any general queries a customer may have about goods or services they
are thinking of buying from your company. An inquiry is one of the first possible documents you can
create in the customer order management cycle. An example of the type of information contained in an
inquiry is whether your company stocks a certain product line. Along with entering general customer
queries, you can use inquiries to record the goods or services that a customer is interested in. And you
can enter descriptions of goods or services that your company should research in order to answer
customer queries. You can carry out automatic pricing for any goods or services you enter in an inquiry.
This will enter the price of goods or services into the inquiry for you. You can also check whether any
goods you entered in the inquiry are available in your company's warehouse. The order probability
function enables you to determine the likelihood that a customer will buy from you. To increase the
probability of a sale, you can offer the customer alternative goods and services.
Quotations are sales query documents that you create when a customer requests specific information
about a product. For example, you can use a quotation if a customer makes a query regarding how much
goods or services cost or you can use a query if a customer asks when goods will be available for
shipping.
You can create quotations from scratch or you can create them by copying inquiries. If a customer is
interested in the products or services after they have made an inquiry, you can provide a quotation
based on the original inquiry. R/3 allows you to copy the information directly from an inquiry to a
quotation.
Let's say an inquiry was created when a customer inquired whether your company, could manufacture
twenty motorcycles. Assume a quotation was created by copying this inquiry when the customer called
back to inquire how much twenty motorcycles would cost. You can use quotations to enter information
and descriptions for goods and services that are to be researched. You can also use them to carry out
automatic pricing and to check goods availability. You can use quotations to calculate the probability
that a customer will buy the goods or services entered on a quotation. This function is called order
probability. You can also use quotations to enter details about alternative goods or services. These are
goods or services that a customer did not inquire about but that you think they will consider purchasing.
Once you have created a quotation for a query in R/3, you send the quotation to the customer who
made the query. The quotation represents a binding offer made to the customer that includes quantity
and cost details.
You create a free of charge delivery when you send free samples of any goods that your company
produces to customers. These contain information about the goods that are delivered but they don't
include the corresponding pricing information for them.
Let's look at the sales orders that exist in R/3.You create a sales order when a customer has ordered
goods or services from your company. They are a part of the customer order management cycle.
You can carry out automatic pricing in sales orders to enter the price of goods or services.
R/3 will also run a credit check on the customer to see if they will be exceeding their credit limit.
You can also check whether ordered goods will be available in your company's warehouse for delivery.
Examples of types of sales order include
standard orders
consignment orders
cash orders
rush orders
You create standard orders for goods and services that will be delivered or rendered according to
the standard R/3 sales cycle. This means that goods are ordered, picked from the warehouse, and
then shipped before customers are billed for them. Likewise, services are rendered before customers
are billed for them.
Your company may store its goods in its customers' warehouses. You create a consignment order when
a customer is ready to retrieve stock from the warehouse.
SAP can propose the most suitable stock to retrieve, including third-party stock.
A consigment order is like a standard sales order for goods but it doesn't have any delivery
information.
You create cash orders and rush orders for the sale of goods only.
You create a cash order when a customer picks up and pays for a delivery as soon
as it is ordered. And you create a rush order when the customer picks up the goods on the
same day as the order is placed. In this case, the invoice is created later.
You can arrange to deliver goods or render services in installments. To do this, you create an
outline agreement. Examples of some types of outline agreement include :
quantity and value contracts
master contracts
scheduling agreements
service contracts
You create a quantity contract if a customer has agreed to order a certain quantity of goods from your
company during a specified period.
And you create a value contract if a customer has agreed to order goods of a certain cumulative value
from your company during a specified period.
Quantity and value contracts do not include delivery dates, so releases are made using a sales order.
You can unite multiple contracts in a single master contract.
Let's say you create a quantity contract because a customer has agreed to order 500 engines in the first
six months of the current year. If the customer orders 100 of these engines in January, you create a sales
order called a release order.You refer to a quantity contract in a release order. So you refer to the
quantity contract created for the 500 engines in each release order created for these engines. R/3 will
then update the quantity contract automatically so it contains the correct number of remaining engines
to be ordered.
Scheduling agreements specify the installments in which goods will be delivered to a customer. They
include the quantity of a product that will be delivered in each installment. And they include the delivery
date of each installment. You process a delivery for each installment contained in the scheduling
agreement in the same way that you process a delivery for a regular sales order.No sales documents,
such as release orders, are created before the products included on a scheduling agreement are
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 under deliveries 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.
Pur info record is nothing but a master data like thing which will be maintained for different materials to
determine the prices etc.It Specifies the number that uniquely identifies a record.
For Example: an info record is based on Plant Vendor and Material Based on these three the Material
Prices will be calculated for different combinations different values are taken into consideration.
During pricing it brings these values automatically based on this info record.
Use ME11 Tcode to create this record.
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
FI-LC: Consolidation
FI-AP : Accounts Payable
FI-AR : Accounts Receivable
FI-BL : Bank Accounting
FI-AA :Asset Accounting
FI-SL : Special Purpose Ledger
FI-FM : Funds Management
CO Controlling
represents the company's flow of cost and revenue. It is a management instrument for organizational
decisions. It too is automatically updated as events occur.
The CO module has following sub modules:
CO-OM : Overhead Costing (Cost Centers, Activity Based Costing, Internal Order Costing)
CO-PA : Profitability Analysis
CO-PC : Product Cost Controlling