Reg Save in VA21 & Va22

I have a simple requrement of checking Your reference(VBKD-IHREZ_E) field in table VBKD already exists or not when ever a User gives a new Your reference or changes an existing one.
is there any FM exit ot BADI for this...

check include MV45AFZZ abd badi ME_CHECK_SOURCES
user exits & BADI's for va21/va22
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
V46H0001 SD Customer functions for resource-related billing
V45W0001 SD Service Management: Forward Contract Data to Item
V45S0004 Effectivity type in sales order
V45S0003 MRP-relevance for incomplete configuration
V45S0001 Update sales document from configuration
V45P0001 SD customer function for cross-company code sales
V45L0001 SD component supplier processing (customer enhancements)
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45E0001 Update the purchase order from the sales order
V45A0004 Copy packing proposal
V45A0003 Collector for customer function modulpool MV45A
V45A0002 Predefine sold-to party in sales document
V45A0001 Determine alternative materials for product selection
SDTRM001 Reschedule schedule lines without a new ATP check
SDAPO001 Activating Sourcing Subitem Quantity Propagation
Business Add-in
BADI_SD_SCH_GETWAGFZ Scheduling Agreement: Read WAGFZ from S073
BADI_SD_V46H0001 SD Customer functions for resource-related billing[/code]

Similar Messages

Quotation VA21 - VA22 - Cannot change items or quantities

Dear Gurus,
I have created a quotation in VA21 and selected a Sold to Party as well as a Material, and saved the quotation. When I then went to VA22 to change both the quantities in the material and add another material to confirm the quotation, the system wouldn't allow me to do it.
Could you explain to me why and also tell me if I have missed somethig in the completion procedure?
Thanks
Regards
Chris

Hi,
Check the user exit for MV45AFZZ, i guess there may be some restriction in changin the quotation.
Thanks,
Raja

Reg: save exit and cancel buttons

Hi,
In normal report programs when we enable the back , exit and cancel buttons they work fine without writing any code.but its not in the case of Module pool why?
In thr normal reports where does the code come from?
regards
prasanth

Hi....
Module pool programs is nothing but screen flow + reports...
Here we designing the screens....
So we hav to to give every functionality.. for all buttons and menu items of the appeared screen...
Where as in reports...,
We are just using the standard screen (sellection screen and list output screen ) s mostly...,
Here also some times we hav to go for created screens.. nothing but.... interactive reports...,
There we need to give again all those functionalities...
And..,
To see the BACK button logic and other logics in the reports...,
Ex: PAI event of SAPLWBABAP program...,
You can find that name with...
By giving /H and enter before ur action...
Thanks,
Naveen.I

BADI for VA21/VA22

Hello everyone.!
I need to know if there is a BADI for Tx. mentioned above(Quotation). What i need to do is simple: Validation check in condition types (pricing & discounts).
If user selects a condition type (i.e. PR00), then i need to validate its amount.
I've read some about BADIs por Sales Order document, i.e. VA01/VA02.. but ¿can these BADIS help me with this?
Thanks in advance.!!!
Luis

Hi
you can use Standard User-exit program MV45AFZZ Provided by SAP for Sales, You can write ur
Code in following Section of This Above Program.
      FORM USEREXIT_PRICING_PREPARE_TKOMK                           *
      This userexit can be used to move additional fields into the *
      communication table which is used for pricing:                *
      TKOMK for header fields                                       *
      This form is called from form PREISFINDUNG_VORBEREITEN.       *
FORM USEREXIT_PRICING_PREPARE_TKOMK.
*{   INSERT         EEDK900305                                        1
We are executing this functionality through a different report
*}   INSERT
TKOMK-zzfield = xxxx-zzfield2.
ENDFORM.                    "USEREXIT_PRICING_PREPARE_TKOMK
*eject
      FORM USEREXIT_PRICING_PREPARE_TKOMP                           *
      This userexit can be used to move additional fields into the *
      communication table which is used for pricing:                *
      TKOMP for item fields                                         *
      This form is called from form PREISFINDUNG_VORBEREITEN.       *
FORM USEREXIT_PRICING_PREPARE_TKOMP.
*{   INSERT         EEDK900305                                        1
I Think This Will Help You.
Regards,
Shyam.

How to authorization sales office and sales group in VA21 and VA01 t-code

I need to authorization sales office and sales group in va21,va22,va23 and va01, va02, va03 to control users access the sales order.
I found some articles how to resolve this problem.I have created new authorization object Z_VBAK_ VKO, and add these fields to the object: VKORG: Sales Organization, VTWEG:Distribution Channel, SPART: Division, VKBUR:Sales Office, VKGRP: Sales Group, AUART:Sales Document Type, ACTVT:Activity
I have add the object Z_VBAK_VKO to va01, va02, va03 in SU24 translation.
I test the authorization , but fail, va01 and va02 do not check the authorization.
Why? what can i do? please help me .
thanks

Dear Wu
I think you are using the concept of Master Roles and Derived Roles.If ur using then create a master role and derived role for the authorisation group you want. And in the derived role assign the specifics to the respective logins ID. If you want to attach the authorisation to the T-Codes Va01 or VA21 etc then you have to use Exit.
Correct me if i am wrong.
Regards
Jyotsana

Update error, transaction VA21

Hi all,
when i want to save transaction Va21, i got this error update error, when i click where used list , i dunno which one program to set breakpoint. lots of list.
then i click the error message it display like this...when i go to SM13 the error details shows TD 423: CONTROL_FORM.
where and how i should solve this.. i'm really stuck.. donno how and why. Please xperts... help me...
Update error, transaction VA21
Message no. 00377
Diagnosis
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA21.
Update information
Return code:        009
Text       :        CONTROL_FORM is invalid, OPEN_FORM is missing
Procedure
Pleas analyse your Batch-Input data.
You can also examine your posting data using the transaction SM13.

You can delete the output from VA21 Transaction by EXTRAS-OUTPUT-HEADER-EDIT and then try to SAVE.May it will aloow you to save.
one more suggestion Check with Table TNAPR where KSCHL = ZN00 and NACHA = ? (Check in VA21) then you can get the Program and Name of routine Just Put a break point over there and find what is the issue.
Kanagaraja L

Reg:FI&CO and MM flow

Hi ,
any one send me FI&CO,MM flow and important table .Tcode.
Regards,
Sivaram

TABLES
SD.
VBAK - sales document header
VBAP - Sales document line item
VBEP - Sales document schedule lines
VBUK - Sales document header status
VBUP - Sales document line item status
VBFA - Sales document document flow
LIKP - Delivery header
LIPS - Delivery line item
VBRK - billing document header
VBRP - Billing document line item
MM
MARA - Material master
MARC - material master plant level
MVKE - Material master sales org details
EKKO - Purchasing document header
EKPO - Purchasing document line item
EKET - Purchasing document schedule lines
EKES - Purchasing document confirmations
EKBE - Purchasing document history
EBAN - Purchase requisition
EINE - purchase info record
MKPF - Material document movement header
MSEG - Material document movement line item
RBKP - Invoice document header
RSEG - invoice document line item
Sales related
VBAK: Sales Document(Header Data) (VBELN)
VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)
Enquiry, Quotation, Sales Order are differentiated based on Doc.
Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,
for Quotation 'B' & for Order it is 'C'.)
LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)
LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)
(LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)
VTTK: Shipment Table (Header Data)(TKNUM)
VTTP: Shipment Table (Item Data)( TKNUM,TPNUM,VBELN)
(VTTP-VBELN = LIKP-VBELN)
VTFA: Shipping Document Flow(TKNUM,VBELV,VBELN)
VTPA: Shipping Partners data(VBELN,PARVW,KUNNR,PERNR)
VTTS: Stages in Shipment(TKNUM,TSNUM,TSTYP)
VTSP: Transport Stage/Shipment Item Allocation(TKNUM,TSNUM,TPNUM)
VEKP: Handling Unit: Header(Packing)(VENUM,VSTEL)
VEPO: Handling Unit: Item (Packing)(VENUM,VEPOS,VBELN)
VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)
VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)
(VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)
Apart from these tables there are lot of other tables which starts with
V, but we use the following tables frequently.
VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)
VBTYP= C(Sales Order) VBTYP=J(Delivery) VBTYP=M(Invoice)
VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)
VBEP: Sales Doc. Schedule Lines Data(VBELN,POSNR,EDATU,WMENG)
VBKD: To get sales related Business data like Payment terms etc.(VBELN,ZTERM)
VBFA: sales document flow data(VBELV,VBELN,POSNV,VBTYP)
VBPA: Partner functions Data(VBELN,PARVW,KUNNR,LIFNR)
VEDA: Contract Data(VBELN,VPOSN)
VEDAPO: Contract Data(VB
Material Related
MARA--Material Master-General (MATNR,MTART,MATKL)
MARC--Material Master-Plant data(MATNR,WERKS,EKGRP)
MARD--Material Master- St.Location Data(MATNR,WERKS,LGORT,LABST)
MAKT--Material Descriptions(MATNR,MATKL,MAKTX)
MBEW--Material Valuation Data(MATNR,BWTAR)
MVKE-Material Master: Sales related Data(MATNR,VKORG,VTWEG)
Customer related tables with Important fields
KNA1: Customer Master-General(KUNNR,NAME1,LAND1)
KNB1: Customer Master(Company Code)(KUNNR,BUKRS,PERNR)
KNC1: Customer Master Data (Transaction Figures)(KUNNR,BUKRS,GJAHR)
KNVK: Customer Master Contact Partner(PARNR,KUNNR,NAME1)
KNVV: Customer Master sales data(KUNNR,VKORG,VTWEG,KDGRP)
KNBK: Customer Bank Details(KUNNR,BANKS,BANKL,BANKN)
KNVH: Customer Hierarchy (HITYP,KUNNR,VKORG,VTWEG,SPART)
KNVP: Customer Master Partner Functions(KUNNR,PARVW,KUNN2)
KNVS: Customer Shipment data(KUNNR,VSTEL,TRANS)
KNVI: Customer Tax data(KUNNR,ALAND,TATYP)
Vendor related
LFA1--Vendor Master-General (LIFNR,NAME1,ORT01)
LFB1--Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)
LFC1--Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)
LFM1-Pur.Orgn. Related Vendor Data (LIFNR,EKORG)
http://www.erpgenie.com/abap/tables_sd.htm
http://www.erpgenie.com/abap/tables_mm.htm
FI
U can find all d details regarding FI tables & their relations here....
http://www.sapgenie.com/abap/tables_fi.htm
You can find the details about the FI module here
http://www.sap-img.com/sap-fi.htm
tcodes
SD
http://www.sap-img.com/sap-sd/sap-sd-transaction-codes-list.htm
MM flow
http://www.sap-img.com/sap-mm.htm
FI flow
http://www.sap-img.com/sap-fi.htm
http://www.erpgenie.com/saptech/transactions.htm
Link Between SAP SD, MM & FI
1. In SAP you will always get integration with other modules. SD will interact with FI, MM will interact with SD :-
1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped
directly to your customer).
1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.
2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc.
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
Now the link between SD and FI :-
1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.
Sales Order
Integration Points Module
Availability Check - MM
Credit Check - FI
Costing - CO/ MM
Tax Determination - FI
Transfer of Requirements - PP/ MM
Delivery & Goods Issue
Integration Points Module
Availability Check - MM
Credit Check - FI
Reduces stock - MM
Reduces Inventory $ - FI/ CO
Requirement Eliminated - PP/ MM
Billing -
Integration Points Module
Debit A/R - FI/ CO
Credit Revenue - FI/ CO
Updates G/ L - FI/ CO
(Tax, discounts, surcharges, etc.)
Milestone Billing - PS
Return Delivery & Credit Memo -
Integration Points Module
Increases Inventory - MM
Updates G/ L - FI
Credit Memo - FI
Adjustment to A/R - FI
Reduces Revenue - FI
SD 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.
For all the transactions and reports related to them
http://www.easymarketplace.de/transactions-i-l.php
For all the tables:
Use link
http://www.erpgenie.com/abap/tables.htm[
integration points MM/FI
Fi,mm and sd docudments
Reward points please...

Link between Accounting Document and Sales Order

Dear SD Gurus,
How to find the Sales Order number and Sales Order Item from the accounting document- like document types DZ, DG, ID etc.
Kindly specify the table links and fields to fetch the above details
Regards
Vimal

Link Between SAP SD, MM & FI
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
Now the link between SD and FI :-
1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.
Sales Order
Integration Points                      Module
Availability Check             -       MM
Credit Check                   -       FI
Costing                        -       CO/ MM
Tax Determination              -       FI
Transfer of Requirements       -       PP/ MM
Delivery & Goods Issue
Integration Points                      Module
Availability Check             -       MM
Credit Check                   -       FI
Reduces stock                  -       MM
Reduces Inventory $            -       FI/ CO
Requirement Eliminated         -       PP/ MM
Billing -
Integration Points                      Module
Debit A/R                      -       FI/ CO
Credit Revenue                 -       FI/ CO
Updates G/ L                   -       FI/ CO
(Tax, discounts, surcharges, etc.)
Milestone Billing              -       PS
Return Delivery & Credit Memo -
Integration Points                      Module
Increases Inventory            -       MM
Updates G/ L                   -       FI
Credit Memo                    -       FI
Adjustment to A/R              -       FI
Reduces Revenue                -       FI
SD 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 F2
Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
<b>The SD & FI link is established through mapping of appropriate G/L accounts through T.Code: VKOA</b>
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

How to create Excise Invoice.

Hi SD Guru's
          How to create excise invoice and what is the use of this one and sd point what are the setting required.
Thanks
Rajendra

In Indian Manufacturing scenario, Excise Invoice is required when goods move out of factory premises. The process is as under:
Inquiry / Document type IN
Tcode: VA11,VA12,VA13. tables VBAK,VBAP
Quotation / QT
Tcode: VA21,VA22,VA23. tables VBAK,VBAP
Sales Order OR
Tcode: VA01,VA02,VA03. tables VBAK,VBAP
Delivery LF
Tcode: VL01,VL02,VL03. tables LIKP,LIPS
Billing F2
Tcode: VF01,VF02,VF03. tables VBRK,VBRP
Excise Invoice
Tcode: J1IIN
Configuration of CIN Settings:
1.1 Maintain Excise Registration
 Logistics general  SAP Ref. IMG SPRO Maintain Excise Basic setting India tax on Goods Movements Registrations
1.2 Maintain Company Code Settings
SPRO   Basic settingIndia  tax on Goods Movements Logistics general SAP Ref. IMG   Maintain Company Code Settings
1.3 Maintain Plant Settings
tax on Goods Logistics general  SAP Ref. IMG SPRO   Maintain Plant Basic setting India Movements Settings
1.4 Maintain Excise Groups
SAP Ref. IMGSPRO   Maintain Basic setting India  tax on Goods Movements Logistics general  Excise Groups
1.5 Maintain Series Groups
SAPSPRO  Basic setting India  tax on Goods Movements Logistics general Ref. IMG Maintain Series Groups
1.6 Maintain Excise Duty Indicators
tax on Goods Logistics general  SAP Ref. IMG SPRO   Maintain Excise Duty Basic setting India Movements Indicators
1.7 Maintain Subtransaction Type with Text
India  tax on Goods Movements Logistics general  SAP Ref. IMG SPRO   Maintain Subtransaction Type with TextBasic setting
1.8 Determination of Excise Duty
tax Logistics general  SAP Ref. IMG SPRO   Select Tax Calculation Determination of Excise DutyIndia on Goods Movements Procedure
1.9 Maintain Excise Defaults
SAP Ref.SPRO   Determination of ExciseIndia  tax on Goods Movements Logistics general IMG   Maintain Excise DefaultsDuty
1.10 Condition-Based Excise Determination
tax on Goods Logistics general  SAP Ref. IMG SPRO   Define Tax Code for Condition-Based Excise DeterminationIndia Movements Purchasing Documents
1.11 Condition-Based Excise Determination
tax on Goods Logistics general  SAP Ref. IMG SPRO   Assign Tax Code to Condition-Based Excise DeterminationIndia Movements Company Codes
1.12 Classify Condition Types
SAPSPRO   Condition-BasedIndia  tax on Goods Movements Logistics general Ref. IMG   Classify Condition TypesExcise Determination
1.13 Maintain Chapter IDs
tax on Goods Logistics general  SAP Ref. IMG SPRO   Maintain Chapter ids Master dataIndia Movements
1.14 Assign Users to Material Master Screen Sequence for Excise Duty
SPRO  Master dataIndia  tax on Goods Movements Logistics general SAP Ref. IMG Assign Users to Material Master Screen Sequence for Excise Duty
1.15 Specify Excise Accounts per Excise Transaction
tax on Goods Logistics general  SAP Ref. IMG SPRO   Specify Excise Accounts per Excise Account determinationIndia Movements Transaction
1.16 Specify G/L Accounts per Excise Transaction
tax on Goods Logistics general  SAP Ref. IMG SPRO   Specify G/L Accounts per Excise Account determinationIndia Movements Transaction
1.17 Incoming Excise Invoices
SAPSPRO   BusinessIndia  tax on Goods Movements Logistics general Ref. IMG   Incoming Excise InvoicesTransactions
1.18 Define Processing Modes Per Transaction
 Logistics general  SAP Ref. IMG SPRO   Define Processing Modes Business TransactionsIndia tax on Goods Movements Per Transaction
1.19 Define Reference Documents Per Transaction
tax on Goods Logistics general  SAP Ref. IMG SPRO   Define Reference Documents Per Business TransactionsIndia Movements Transaction
1.20 Maintain Rejection Codes
SAPSPRO   BusinessIndia  tax on Goods Movements Logistics general Ref. IMG   Maintain Rejection CodesTransactions
1.21 Specify Which Movement Types Involve Excise Invoices
Logistics SAP Ref. IMG SPRO   Specify Which Business TransactionsIndia  tax on Goods Movementsgeneral Movement Types Involve Excise Invoices
1.22 Outgoing Excise Invoices
tax on Goods Logistics general  SAP Ref. IMG SPRO Assign Outgoing Excise Invoices  Business TransactionsIndia Movements Billing Types to Delivery Types
1.23 Maintain Default Excise Groups and Series Groups
 Logistics general  SAP Ref. IMG SPRO  Outgoing Excise Invoices  Business TransactionsIndia tax on Goods Movements Maintain Default Excise Groups and Series Groups
1.24 Subcontracting Attributes
tax on Logistics general  SAP Ref. IMG SPRO   Subcontrac Subcontracting Business TransactionsIndia Goods Movementsting Attributes
1.25 Maintain Movement Type Groups
SPRO   BusinessIndia  tax on Goods Movements Logistics general SAP Ref. IMG   Subcontracting SubcontractingTransactions Attributes
1.26 Utilization Determination
SAPSPRO   BusinessIndia  tax on Goods Movements Logistics general Ref. IMG   Utilization Determination UtilizationTransactions
1.27 Specify SAPscript Forms
tax on Logistics general  SAP Ref. IMG SPRO   Specify Excise Registers Business TransactionsIndia Goods Movements SAPscript Forms
1.28 Number Ranges
SAP Ref. IMGSPRO   Number ToolsIndia  tax on Goods Movements Logistics general  Ranges
1.29 Message Control
 SAP Ref. IMG SPRO   Message ToolsIndia  tax on Goods MovementsLogistics general Control
Regards,
Rajesh Banka

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 Business Process

Hi,
Can someone help me out in getting some docs where i can find the Bussiness Process in SD.
Kindly let me know abt that??
Regards,
Sekhar

Link Between SAP SD, MM & FI
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
Now the link between SD and FI :-
1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.
Sales Order
Integration Points                      Module
Availability Check             -       MM
Credit Check                   -       FI
Costing                        -       CO/ MM
Tax Determination              -       FI
Transfer of Requirements       -       PP/ MM
Delivery & Goods Issue
Integration Points                      Module
Availability Check             -       MM
Credit Check                   -       FI
Reduces stock                  -       MM
Reduces Inventory $            -       FI/ CO
Requirement Eliminated         -       PP/ MM
Billing -
Integration Points                      Module
Debit A/R                      -       FI/ CO
Credit Revenue                 -       FI/ CO
Updates G/ L                   -       FI/ CO
(Tax, discounts, surcharges, etc.)
Milestone Billing              -       PS
Return Delivery & Credit Memo -
Integration Points                      Module
Increases Inventory            -       MM
Updates G/ L                   -       FI
Credit Memo                    -       FI
Adjustment to A/R              -       FI
Reduces Revenue                -       FI
SD 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 F2
Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Sd flow

what is the functional flow of SD ? what are the T-codes for the flow?

hi kaladhar,
Re: flow
http://abapprogramming.blogspot.com/search/label/ABAP%20WORK%20FLOW%20SCENARIOS%20IN%20SD
Flow is Inquiry -> Quotation -> SO -> Delivery -> Billing
SD Flow
SD 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.
http://www.sap-basis-abap.com/sd/sap-sd-processing-flow.htm
http://sapfunctional.com/SD/SDMainPage.htm
Transaction Codes:
Inquiry - VA11/VA12/VA13
Quotation - VA21/VA22/VA23
Sales Order - VA01/VA02/VA03
Delivery - VL01N/VL02N/VL03N
Billing/Invoicing - VF01/VF02/VF03
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)
Transaction input = VA01 (create sales order)
All the configurations made during customizing are validated and allows the sales order to be created.Then the R/3 Checks for the availability of the items and gives a schedule line on which you can deliver the goods.
step 2.
VL01N- Create delivery.
For a given shipping point on the due schedule line date create the delivery. Here we do the picking, packing, Loading and Goods Issue, ie., to say done with the shipping process the goods have physically left to the customer.
step 3. (what comes next ??)
VF01 - Create Invoice.
For the items issued ( PGI items ) we bill the customer depending on his billing plan. otherwise its a simple VF01 transaction to bill the items issued. Here the billing data is transferred to accounting so that the FI takes over from here.
So,
VA01 -- > VL01N -- > VF01. End of SD process.
please reward points if helpful,
shylaja

Link between SD MM FI HR PP

Hi All,
Can anybody tell me the links between SD, MM, FI, HR, PP modules with Table name and Field Name. It will be of immensly helpfull.
Thanks in Advance.
Ajoy

hi
good
PP-SD
Availability Check, MTO Scenario-MRP Run, Reqmt Types etc..
PP-MM
Goods mvmts -Backflush, Auto GR, Creation of Purch. Requisitions, Purchase orders during MRP etc..
PP-CO
Cost Center, Order Type - Settlement Profile, Product cost Collector, Cost Estimate, WIP etc..
Link Between SAP SD, MM & FI
1. In SAP you will always get integration with other modules. SD will interact with FI, MM will interact with SD :-
1a. Looking at MM and SD interaction first, take the scenario of a third party order process. This process uses a purchase order (which is sent to your vendor). Also invoice verification is used further along the process to check that the invoice you send to your customer is the same material and quantity as that which the vendor sends to you (but obviously shipped
directly to your customer).
1b. Billing is an SD function. But SAP needs to know, when processing a customer's payment, to which GL account the payment has to be processed. For instance payment of a UK based material would be placed in a different GL account to that of a non-UK based material. Furthermore, a UK based customer may have a different GL account to that of an Export customer. This is configured in Account Determination.
2. ABAPers are there to essential do some bespoke development. Your integration, or interaction, with them would be when specifying the tables, fields, input fields, a simple process explanation, data mapping (if doing an interface from one system to another) etc. *-- Shahee
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
Now the link between SD and FI :-
1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.
Sales Order
Integration Points Module
Availability Check - MM
Credit Check - FI
Costing - CO/ MM
Tax Determination - FI
Transfer of Requirements - PP/ MM
Delivery & Goods Issue
Integration Points Module
Availability Check - MM
Credit Check - FI
Reduces stock - MM
Reduces Inventory $ - FI/ CO
Requirement Eliminated - PP/ MM
Billing -
Integration Points Module
Debit A/R - FI/ CO
Credit Revenue - FI/ CO
Updates G/ L - FI/ CO
(Tax, discounts, surcharges, etc.)
Milestone Billing - PS
Return Delivery & Credit Memo -
Integration Points Module
Increases Inventory - MM
Updates G/ L - FI
Credit Memo - FI
Adjustment to A/R - FI
Reduces Revenue - FI
Tips by: Subha
SD 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.
reward point if helpful.
thanks
mrutyun^

Reg Save in VA21 & Va22

Similar Messages

Maybe you are looking for