Quotation Management

All,
I'm very new to SAP CRM. I have to work on a project where they wanted to bring the Quotes system to WEB UI. They have already done configuration in CRM but nobody really uses. Now I need to figure out what's available in CRM to present to the the business and also need to come up with some kind of documentation how we can go into WEB UI. Please help me out what will be my starting point. We are on CRM 2007. They already went live quotes on webui for one country. Now they wanted to move another country to WEB ui. How do we get the prot established or can we use existing quotes port?
Is there any technical and functional documentation / sap best practices available? I'm also new to sales.. Please help me.
Thanks,
Sri

Hi Sri,
Please go through below linkfor CRM 2007 Best Practices
http://help.sap.com/bp_crm70/CRM_DE/HTML/index.htm
After That goto Technical Information & Content Library.
Best Regards,
Rajendra Sonawane

Similar Messages

SD quotation managed through version control

Hello all,
How can I active the version control for a SD quotation? What I need is, check the changes made in a SD quotation using the version control.
Thnks in advanced.
RB

In our current J2EE environment an ant script builds a war and copies it to a staging file server, then there is a java app that deploys the war to weblogic with the weblogic scripting extensions. We are thinking of modifying this app to also deploy the PTE files that any portlets in the war depend on. Day one a jsp portlet requires a single session preference. The next day it needs a login token to use the PRC. How do you coordinate this? For us it will probably be done with custom scripting.
A developer modifies the jsp and checks that in along with a revised remote service pte file which has the new settings. The ant script will then build the war and package it into a tar with the pte file and finally drop it on the staging server. From there our existing java deployment web app can extract the tar, deploy the war and run a migration import on ALUI. Hopefully all this can happen in a transactional context so that that if the import fails, the new portlet is not deployed.
I don't want to run into the case where a new portlet is out on the QA box and the portlet service is misconfigured and isn't supplying the correct headers to the portlet tier.

Addon for RFQ and vendor quotation

Hi ,
We are looking for an addon for RFQ and vendor quotation .
Pls let us know about the same.

To my knowlege there are no addons available in India for RFQ, Vendor Quotation Management.
You may contact the Local Product Experts of B1 available in India for further information.
You can find their contact from the following link:
[https://websmp210.sap-ag.de/~sapidb/011000358700001455542004#India]

How to implement GIL programming for quotation managetment

Dear Expert:
We want to implement fund pool function in quotation management to give customers special discount from the fund pool.
It need add new assignment block of fund pool and price discount assigned for customer.
The data for that is stored in some customer Add-on tables, and we need to save the data to the tables when save the quotation.
So GIL programming is necessary.
Please help on how can I implement GIL programming in this condition?
Thank you very much in advance!
Best Regards
Lingxing Meng

Hi Lingxing,
What is GIL programming? Do you mean GenIL here?
Regards,
Shiromani

Replicating Quotation overall status from ECC to CRM

Hi,
we're using quotation management replication scenario A in ECC6 and CRM 5.
when the quotation is referenced to sales order in ECC, the overall status becomes "completed" in ECC. but somehow, the overall status of the quotation in CRM remains "not processed".
is there anyway i can get the overall status in ECC replicated to CRM for Quotation Management?
Regards
JD

Hi Susana,
i got reply from SAP mentioning that this is standard behavior. unless i replicate the referencing sales order document from ECC to CRM, then the CRM quotation system status won't be set to completed whenever it is referenced to sales order in ECC. we do not have any business need to have the sales order in CRM, but that's the way it is.
Regards,
JD

BW for Sales and Distribution.

Hi All,
Can you please provide me some insights into Sales and Distributions and Pricing.
I would like to know the functional aspects of Sales and Distribution.
Please provide me inputs regarding the functionalities of SD and Pricing.
Thanks in Advance,
Sravani
Edited by: sravani kandy on Jun 7, 2008 8:02 PM

Hi,
SD Process Flow
the sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customeru2019s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents u2013 the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge u2013 creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Transaction Codes:
Inquiry - VA11/VA12/VA13
Quotation - VA21/VA22/VA23
Sales Order - VA01/VA02/VA03
Delivery - VL01N/VL02N/VL03N
Billing/Invoicing - VF01/VF02/VF03
Refer
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/SD_tutorial.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCSD/CAARCSD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_SD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSD/BCBMTWFMSD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOLISPLN/LOLISPLN.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/dd/55f33e545a11d1a7020000e829fd11/frameset.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sap-img.com/sap-sd.htm
http://www.sapgenie.com/abap/tables_sd.htm
Hope this helps.
Thanks,
JituK

VACANCIES FOR OPM AND DISTRIBUTION

Hi,
We have positions available for the following functional consultants:
Soltre Technology, Inc., an RCM Technologies Company, is an Oracle Certified Advantage Partner specializing in implementation and outsourcing of Oracle applications.
POSITION SUMMARY:
Soltre Technology, Inc. is seeking an Oracle Process Manufacturing (OPM) Functional consultant for a position in our Los Angeles, California office
DUTIES AND RESPONSIBILITIES:
•     Support implementation of Oracle Process Manufacturing Inventory.
•     Document, validate, and test business process functionality in the OPM environment.
•     Identify and implement process improvements increasing organizational capabilities.
EXPERIENCE:
Qualified candidates will have 4 years of Oracle Process Manufacturing Inventory functional experience.
MINIMUM QUALIFICATIONS:
•     Strong background in Process Manufacturing Inventory (OPM) Functional implementation and support methodologies.
•     Excellent interpersonal communication and organizational skills to work with clients and team members.
•     Ability to effectively obtain, analyze and convey information.
•     Proficiency with Microsoft office tool set (e.g. Word, Excel, etc.).
POSITION SUMMARY:
We are currently seeking an Oracle Distribution Functional consultant for a position in our Los Angeles, California office.
DUTIES AND RESPONSIBILITIES:
Support the following modules of Oracle Distribution:
•     Order Management
•     Advanced Pricing
•     Incentive Compensation
•     Accounts Receivable
•     Advanced Collections
•     Document, validate, and test business process functionality in the Distribution environment.
•     Identify and implement process improvements increasing organizational capabilities.
EXPERIENCE:
Qualified candidates will have 4 years of Oracle Distribution functional experience.
MINIMUM QUALIFICATIONS:
•     Order Management, Advanced Pricing, Incentive Compensation, Accounts Receivable Advanced Collections
•     Strong background in Distribution Functional implementation and support methodologies.
•     Excellent interpersonal communication and organizational skills to work with clients and team members.

Hi,
SD Process Flow
the sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customeru2019s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents u2013 the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge u2013 creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Transaction Codes:
Inquiry - VA11/VA12/VA13
Quotation - VA21/VA22/VA23
Sales Order - VA01/VA02/VA03
Delivery - VL01N/VL02N/VL03N
Billing/Invoicing - VF01/VF02/VF03
Refer
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/SD_tutorial.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCSD/CAARCSD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_SD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSD/BCBMTWFMSD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOLISPLN/LOLISPLN.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/dd/55f33e545a11d1a7020000e829fd11/frameset.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sap-img.com/sap-sd.htm
http://www.sapgenie.com/abap/tables_sd.htm
Hope this helps.
Thanks,
JituK

SD and MM FLOW with example

Hi friends,
Can any one tell me the SD and MM Flow with respect to company and customer like what the company and customer will do in various stages?

hai Reddy,
SAP Sales and Distribution Processing Document Flow
Document Flow in Sales
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
The following graphic shows how the various types of sales documents are inter-related and how data subsequently flows into shipping and billing documents.
D Transaction Code Flow:
Inquiry / Document type IN
Tcode for creation VA11,VA12, VA13. Tables VBAK, VBAP
Quotation / QT
Tcode for creation VA21,VA22,VA23. Tables VBAK, VBAP
Purchase Order PO
Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.
Sales Order OR
Tcode for creation VA01,VA02,VA03. Tables VBAK,VBAP
Delivery LF
Tcode for creation VL01,VL02,VL03. Tables LIKP,LIPS
Billing MN
Tcode for creation VF01,VF02,VF03. Tables VBRK,VBRP
To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no.
To create vendor tcode is
xk01(create), xk02(change) , xk03(display)
Tables are lfa1.
To create custmer tcode is xd01, xd02, xd03.
Table is kna1.
After creating sales order using this no we can create delivery note tcode is vl01.
MM FLOW.
Tables
PO
EKKO---Header level
EKPO-Item level
PR
EBAN
GR/Material document
MKPF--Header
MSEG-Item
Invoice
RBKP-header
RSEG-Item
Accounting doc
BKPF--header
BSEG--Item
ServicesSSR--Header
ESLL-Item
It really depends on the company and their business process. Generally though:
Purchase Requisition (user reqests stuff, either for manuf/stock, or supplies). -> then the PReq would go through an approval process (Release Strategy). Once approved, one can either create a Request for Quote (RFQ) to multiple vendors to obtain the best prices - and/or create the Purchase Order (either directly from the PReq or from the RFQ).
Once the PO is created -> then a Goods Receipt is necessary (to indicate you received the goods ordered). Then Invoice Verification (again - if this is set up) - which basically prevents overpayment to a vendor (won't allow you to pay for goods not received through Goods Receipt). Then ultimately the payment to the Vendor.
So - Transaction flow for create (common):
PReq -> RFQ -> PO -> G/R -> Invoice -> payment (?)
ME51N -> ME41 -> ME21N -> MIGO -> MIRO -> payment (?)
Tables for Purchase Requisition:
EBAN -
EBKN - Account Assignment
Tables for Purchase Orders:
EKKO - Header
EKPO - Item
EINA - Purchasing Info Record (oops forgot to mention that above - PInfoRec has the vendor/material/price for future sourcing)
Tables for Request for Quote:
same as PO above
Tables for Goods Receipt:
MKPF - Material Document Header
MSEG - Material Document Item
EKBE - History of PO
Tables for Invoice Verification:
BSIS (good substitute for BSEG, which is a monster)
If Found Helpfull Do Reward.
Regards.
EShwar.

SD and Purchasing,Inventory...

Hi,
How to handle Purchasing data flow in BW?Inventory and SD flows also?
What processor used in after full load in inventory and purchasing?

Hi,
How to Handle Inventory Management Scenarios in BW (NW2004)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Loading of Cube
https://websmp205.sap-ag.de/~sapdownload/011000358700002121282004E/HowToInventory10.pdf
http://help.sap.com/saphelp_bw33/helpdata/en/5b/8dc73cee4fb55be10000000a114084/frameset.htm
u2022u2022 ref.to page 18 in "Upgrade and Migration Aspects for BI in SAP NetWeaver 2004s" paper
http://www.sapfinug.fi/downloads/2007/bi02/BI_upgrade_migration.pdf
Inventory Management BI Contents:
http://help.sap.com/saphelp_nw70/helpdata/en/fb/64073c52619459e10000000a114084/frameset.htm
Sales and Distribution (SD)
http://help.sap.com/saphelp_47x200/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm
SD Process Flow
the sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customeru2019s telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents u2013 the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge u2013 creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Hope this helps.
Thanks,
JituK

Regarding MM & SD flow

Can anyone explain me how the MM & SD business flow happens and what are the Tcodes comes into picture while these flows.

Hi,
MM Flow:
The dataflow as functional process below are the points:
1) Purchasing Requsition -> sent by inventory dept to purcharsing dept
2) Request for Quotation(RFQ)-> Purchasing Dept shall ask the vendors to give the quotation for the requested materials by inventory.
3) Quotation -> Quotation is sent by vendors to the company
4) Purchase order-> Based on all paramers of a quotation sent by vendors. Vendors are selected from whom the material has to be obtained. The company gives purchase order to the vendor.
5) Good's receipt -> vendors sends the goods to the company with goods receipt
6) Invoice verification -> this done based on good's receipt. this means that the ordered goods have reached or not.
7) Payment -> payment is done based on invoice verification. this is (FI/CO)   *-- Santosh Kumaar.M
Full MM Transaction Codes Flow:
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)
The FI - MM integration:
First you define the g/l master records.
1) Inventry raw material a/c
2) GR/IR clearing a/c
3) Raw material consumption a/c
Above like this you define all required g/l accounts then you will go to T.CODE - OBYC
Double click BSX (this is transaction key)
      "            GBB
      "            WRX
      "            PRD
These are transaction keys important.
Then you go to T CODE - OMSY (this is also important) then
Material creation T Code MM01
then
1) Purchase order T.code ME21N
2) Goods received     "       MIGO
3) Invoice verification "      MIRO
For transaction codes check the following link:
http://sap-img.com/materials/list-of-sap-mm-transaction-codes.htm
SD Flow:
Document Flow in Sales
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Important Tables for SAP SD
Sales and Distribution:
                  Table Description
Customers         KNA1   General Data
                  KNB1   Customer Master Co. Code Data (payment method, reconciliation acct)
                  KNB4   Customer Payment History
                  KNB5   Customer Master Dunning info
                  KNBK   Customer Master Bank Data
                  KNKA   Customer Master Credit Mgmt.
                  KNKK   Customer Master Credit Control Area Data (credit limits)
                  KNVV   Sales Area Data (terms, order probability)
                  KNVI   Customer Master Tax Indicator
                  KNVP   Partner Function key
                  KNVD   Output type
                  KNVS   Customer Master Ship Data
                  KLPA   Customer/Vendor Link
Sales Documents   VBAKUK VBAK + VBUK
                  VBUK   Header Status and Administrative Data
                  VBAK   Sales Document - Header Data
                  VBKD   Sales Document - Business Data
                  VBUP   Item Status
                  VBAP   Sales Document - Item Data
                  VBPA   Partners
                  VBFA   Document Flow
                  VBEP   Sales Document Schedule Line
                  VBBE   Sales Requirements: Individual Records
SD Delivery DocumeLIPS   Delivery Document item data, includes referencing PO
                  LIKP   Delivery Document Header data
Billing Document VBRK   Billing Document Header
                  VBRP   Billing Document Item
SD Shipping Unit VEKP   Shipping Unit Item (Content)
                  VEPO   Shipping Unit Header
For transaction code check the following link:
http://sap-img.com/sap-sd/sap-sd-transaction-codes-list.htm
Regards,
Bhaskar

Regarding Business Flow of PP,PM,PS,QS Modules

Hi,
Can anybody tell me the Business Process[Flow's] of PP, PM, PS, QS modules in SAP with their respective transaction codes[TCode's] and important tables for each of them.
Can anybody reply about the same.
Thanks in advance.
Thanks & Regards,
Prasad.

FI Financial Accounting
designed for automated management and external reporting of general ledger, accounts receivable, accounts payable and other sub-ledger accounts with a user defined chart of accounts. As entries are made relating to sales production and payments journal entries are automatically posted. This connection means that the "books" are designed to reflect the real situation.
The FI module has 8 sub modules:
FI-GL
General Ledger Accounting
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
for tables check out link..
http://www.sapgenie.com/abap/tables_fi.htm
MM Process flow:
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
Tcodes:
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 FLOW..
Main steps:
Creation of Inquiry - VA11
Creation of Quotation - VA21
Creation of Sale Order - VA01
Delivery - VL01
Billing - VF11
TAbles:
6 Sales and Distribution (SD) :
VBFA Document flow (alg.)
VTFA Flow shipping documents
6.1 Sales order :
VBAK Header data
VBAP Item data
VBPA Partners in sales order
VBKD Sales district data
VBEP Data related to line items, delivery lines
6.2 Billing document :
VBRK header data
VBRP Item data
6.3 Shipping :
VTTK Shipment header
VTTP Shipment item
VTTS Stage in transport
VTSP Stage in transport per shipment item
VTPA Shipment partners
VEKP Handling Unit - Header Table
VEPO Packing: Handling Unit Item (Contents)
6.4 Delivery :
LIKP Delivery header
LIPS Delivery item
6.5 Pricing :
KONH Conditions header
KONP Conditions items
KONV Procedure ( billing doc or sales order)
KOND
6.6 contracts :
VEDA Contract data
Refer this link:
http://www.sap-img.com/sap-sd.htm
Document Flow in Sales
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Technical Details
Inquiry - va11/va12/va13
Quotation - Va21/va22/va23
Sales Order - va01/va02/va03
Delivery - vl01n/vl02n/vl03n
Billing/Invoicing - vf01/vf02/vf03
PP FLOW..
SAP - Project Planning
Project Planning
PROJ
(Project Definition)
PRPS
(WBS Elements)
PRPS-PSPHI =
PROJ-PSPNR
PRTE
(Schedule Data for
Proj. Item)
PRPS-PSPNR =
PRTE-POSNR
and
PRPS-PSPHI=
PRTE-PSPHI
PRTX
(Texts(WBS))
PRTX-PRPSPNR =
PRTE-POSNR
PRHIS
(Proj. Hierarchy for
WBS Element)
PRPS-PSPNR =
PRHIS-POSNR
and
PRPS-PSPHI=
PRHIS-PSPHI
PSTX
(Project Texts
(Header))
PSTT
(Project Texts)
PRTX-PRTXTKY =
PSTX-PRTXTKY
PSTX-PRTXTKY =
PSTT-PRTXTKY
PP
Table Mapping
SAP PP - Project Planning
PROJECTS
Project and WBS element numbers have a domain with a conversion
function module which converts it from 8 numc input to 24 char on output.
PROJ
(Project definition)
Project Number (PSPNR)
Project Name (PSPID)
PRPS
(WBS (Work Breakdown Structure)
Element Master Data))
Project Number (PSPHI)
WBS Element Number (PSPNR)
WBS Name (POSID)
Project Number (PSPHI)
WBS Element Number (POSNR)
PRTE
(Scheduling Data for Project Item)
PRTX
(PS Texts (WBS)
Project Number (PSPHI)
WBS Element Number (POSNR) PSTX
(PS Texts (Header))
Text Identifier (PRTXTKY)
PS text description (PSTXTTI)
WBS Element Number (PRPSPNR)
Text Identifier (PRTXTKY)
PRHIS
(Standard WBS, Edges (Hierarchy
pointers))
PSTT
(PS texts (description))
Text Identifier (PRTXTKY)
PS text: Description(PTKTEXT)
Message was edited by: kishan negi

Different pricing procedure between CRM and ERP

Hello,
we`re using a CRM system which is connected to a ERP system. As not all pricing conditions from ERP are needed in CRM (an in addition the ERP pricing procedure is very complex), we would like to use a different (with less conditions) pricing procedure ind CRM.
But now, when we transfer an order from CRM to ERP, the pricing procedure from ERP gets downloaded into the order in CRM and the prices are lost. Therefore I have 2 questions:
1. Is it not possible to have a different pricing procedure in CRM than in ERP?
2. Is it possible to stop transferring the pricing procedure from ERP back to CRM when transferring orders?
Thank you in acvance for your help
Jan

Hi, Jan.
1. Is it not possible to have a different pricing procedure in CRM than in ERP?
Yes. You can use different pricing procedure for you business documents.
We use this for quotation management with inergation CRM-ERP.
But, You must use same Condition Types and other objects.
Denis.

Business scenarios on SD and MM modules for generic datasources and enhance

Hi,
Can anybody send some documents on SD and MM module on generic datasource and on enhancements.Pl send it to my MailID:[email protected]
Thanks,
Chinna

Hi,
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)
Also please check this links.
http://www.sapgenie.com/sapfunc/mm.htm
http://www.sap-basis-abap.com/sapmm.htm
SD Process Flow:
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Transaction Codes:
Inquiry - VA11/VA12/VA13
Quotation - VA21/VA22/VA23
Sales Order - VA01/VA02/VA03
Delivery - VL01N/VL02N/VL03N
Billing/Invoicing - VF01/VF02/VF03
Also please check this links.
http://www.sapgenie.com/sapfunc/sd.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sapgenie.com/abap/tables_sd.htm
Production Planning:
For example, consider a pump manufacturing plant, based on the customer requirement, planning is done for future months ( we plan for a qty on particular
date). Pump is an assembly - were main component would be manufactured in the plant and others would be procured. As PP, we are concerned only in the inhouse
manufacturing but the final assembly (considering BOM) can be done only if the procured components are available. MRP helps in planning the shortage, on
particular date based on the planned date. Work center (ex. lathe) place the components are machined/assembled (were the operation is done). Sequence of
operation is routing (lead time scheduling data is got from routing). In the MRP Run,basic or lead time scheduling (need to know when to start/finish date)
is done. On creation of the production order, system checks for which BOM and routing to be picked up (if there are many routings or BOM for that particular
finished product). Availabilty checks for material,PRT and capacity needs to be done. on release of the order, confirmation of the order can be done (on
completion of the order or after manufacturing the quantities). GI and GR have to be done.PP flow ends here
step 1: creation of master data (Material master,BOM,Work center,Routing)
step 2: Planning - can be done by Planned independent requirement (MD61), Independent requirement (MD81).
we plan for a quantity, on which date (it would be finish date).
step 3: MD04 -stock/requirement lsit (plan made can be viewed in MD04)
step 4: MRP run - MD02, PIR is converted into Planned order
step 5:Planned order to be converted production order - CO40, CO41
step 6: production order to be released - CA02
step 7: confirm the production order (order confirmation-CO15 (after which GI and GR is done)
assign pts if helpful...

Condition Types Are Missing After Sales Doc Replicated to R3

Hi
we're implementing quotation management replicated to R/3 system.
the replication from CRM works fine, pricing is determined in R/3 perffecly.
however, first item has condition records replicated back to CRM as we want it.
but the subsequent items has no condition type replicated at all.
any lead is really appreciated.
JD

Can you set a parameter-id PRC_TRACE in your user profile. This trace when activated will perform pricing condition analysis in CRM. If a different user id is used to replicate sales documents please set this parameter for the same.
Also make sure if your pricing procedure is in sync in both CRM and R3.
Naresh

Flow in SAP

HI,
I want some material that will show the process flow of modules SD and MM.
With Transaction Codes and FAQ's
Thanks
Jen

Hi Jen,
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)
Also please check this links.
http://www.sapgenie.com/sapfunc/mm.htm
http://www.sap-basis-abap.com/sapmm.htm
SD Process Flow:
The sales documents you create are individual documents but they can also form part of a chain of inter-related documents. For example, you may record a customers telephone inquiry in the system. The customer next requests a quotation, which you then create by referring to the inquiry. The customer later places an order on the basis of the quotation and you create a sales order with reference to the quotation. You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain of documents the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent delivery free of charge creates a document flow or history. The flow of data from one document into another reduces manual activity and makes problem resolution easier. Inquiry and quotation management in the Sales Information System help you to plan and control your sales.
Transaction Codes:
Inquiry - VA11/VA12/VA13
Quotation - VA21/VA22/VA23
Sales Order - VA01/VA02/VA03
Delivery - VL01N/VL02N/VL03N
Billing/Invoicing - VF01/VF02/VF03
Also please check this links.
http://www.sapgenie.com/sapfunc/sd.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sapgenie.com/abap/tables_sd.htm
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Quotation Management

Similar Messages

Maybe you are looking for