Basic Flow of SD for Abapers to know to develope any SD Object.
Masters and Customizing -
1. Customer Master - XD01
i) General Data - General Data is maintained like Name, Address.
Details are stored in KNA1 table.
ii) Sales Area Data - We define Sales Org, Dist Channel, Division for which the customer belongs
a. In Shipping we will define the Delivery Plant
b. In Billing we will define Incoterms, Terms of Payment, Taxes
c. In Partner Functions we will define Sold to Party, Bill to Party, Payer, Ship to Party
Sales Data are stored in KNVV table.
Partner Functions are stored in KNVP table.
Customer Master Tax details are stored in KNVI
Customer Master Tax details are stored in KNVI
iii) Company Code Data - We will define the Company Code
a. In Account Management we will define Recon Account
b. In Payment Transactions we will define Payment methods for Automatic Payment, Block key for Payment, Terms of Payment
c. In Correspondence we will define bank statement based on which F.27 report can be run for Statement of Accounts
Details are stored in KNB1 table.
2. Material Master - MM01
a. In Sales: General/Plant we can maintain Profit Center
3.Pricing
a) Order -
i) Define Condition Type. For the Condition Type define Access Sequence for the condition type.
ii) For the Access Sequence, define the Condition tables. If the condition table is 7 then the table name is A007.
iii) Define Pricing Procedure in V/08. The details are stored in T683S table.
In the Pricing Procedure the sequence of the Condition types are maintained. Their value calculation will be based on
a) From and To
b) VOFM routine
c) Both a) and b)
If Account Key is maitained for Condition Type, then a line item will be created for that Condition Type while creating an Account Document.
The GL's will be determined by
a) For Non Tax, in VKOA it will be defined in a table. If the Table no is 1 then the details are stored in C001.
b) For Tax, in OB40 the GL is defined. For Tax Condition Type, the Account Key and OB40 Transaction are same. The details are stored in
T030K table.
iv) Define Customer Pricing Procedure
v) Define Document Pricing Procedure
vi) Assign Document Pricing Procedure to Order Types
vii) Assign Document Pricing Procedure to Billing Types
viii) Define Pricing Procedure Determination - It is defined for Sales Area, Document Pricing Procedure and Customer Pricing Procedure.
The details are stored in T683V table
b) Delivery - Logistic Execution - Shipping - Basic shipping functions - Pricing - Define pricing procedure for delivery
The pricing procedure is assigned to delivery type
c) Billing - VTFL
The pricing can be copied from Order or Delivery or can carry out new pricing
4.Price Master - VK11
For a Material, for a Condition Type value can be maintained based on Access Sequence.
The data is stored in Condition Table with Condition Record Number. The condition Record details are stored in KONH KONP tables.
5.Credit Control -
i) Credit Limit for a customer can be created in FD32. Here we can assign Risk Category for a customer. If Credit Limit exsists
for a customer, system checks whether the Sale Order Value and Total Open Items of the Customer is Exceeding the Credit Limit. If it exceeds,
then based on Risk Category Customization, it will either throw an Error Message or throws an Warning message and blocks the order so that
delivery cannot be done or just throws an information message. The Credit Check for a Sales Area can be done in 3 important places ie
Order, Delivery, Post Goods Issue.
The configuration is done in OVA8.
Credit Management details are available in KNKA, KNKK, S066, S067 tables. KNKK - FI Open, S066 - Order, S067 - Delv and Invoice
Transaction -
1. An Inquiry can be created in VA11.
It can be created for an Sales Area and Document Type.
Based on the Sales Area and Document Type Pricing Procedure is determined.
Details such as Incoterms, Terms of Payment will be coming from Customer Master.
For the Item Level, for an Material condition type values willl be coming from VK11.
Details about Inquiry are stored in VBAK VBAP VBEP table with Document Category as A(Inquiry) and Transaction Group as 1(Inquiry)
Details about Conditions are stored in KONV table. Status of Order is shown in VBUK and VBUP
2. An Quotation can be created in VA21.
It can be created for an Sales Area and Document Type.
Details about Quotation are stored in VBAK VBAP VBEP table with Document Category as B(Quotation) and Transaction Group as 2(Quotation)
Details about Conditions are stored in KONV table
3. An Order can be created in VA01.
Details about Order are stored in VBAK VBAP VBEP table with Document Category as C(Order) and Transaction Group as 0(Order)
Details about Conditions are stored in KONV table
4. A Delivery can be created in VL01N.
For the Items, Picking is done. For the item, Plant, Storage Location, Batch from which it is picked is entered. (Both Delivery and Picking
Quantity should be same).
Then Goods Issue will be done. Once Goods Issue is done, then a Material Document will be created with Movement Types 601. For a Material
Document, an Accounting document will be created with two Posting Keys ie One is 99 - Stock Outward Movement - Credit and Second is
81 - Costs - Debit.
The GL codes for the accounting documents are determined by Material's Valuation Class. For a Valuation Class, GL's are assigned in OBYC
transaction. For Example, For Posting Key 99 in OBYC, it is BSX - Inventory Posting and For Posting Key 81 in OBYC, it is GBB - Offsetting entry
for Inventory Posting. These details will be available in T030 table. For FI and MM documents, the values wil be determined by Material's Price in
Accounting View.
The delivery details are available in LIKP and LIPS tables. The Material Document details are availabe in MKPF MSEG. Accounting Document
details are availabe in BKPF, BSEG. Costs item is available in BSIS and Stock Outward movement item is available in BSIM.
The Delivery Due Index is available in VEPVG
The Delivery Due Index is available in VEPVG
5. An invoice can be created in VF01 based on delivery.
When an invoice is created, a corresponding Accounting Document is created.
In the Accounting Document, the first line item is created with posting key 01 for Customers and GL is the Reconcillation Account based on
Customer Master. Then the remaining items will be created with posting key's 40 and 50 (based on Debit and Credit) for all the items from the
Pricing Procedure for which Account Key is maintained.
Invoce details are available in VBRK, VBRP tables.
Accounting details are available in BKPF BSEG.
Posting key 01 Line item will be available in BSIK (and BSIS)
Posting key 40 and 50 are available in BSIS
6. An Excise Invoice can be created in J1IIN based on Invoice.
A corresponding Accounting document will be created.
Excise Invoice details will be available in tables J_1IEXCHDR, J_1IEXCDTL.
General -
1.Sheduling Agreement can be created in VA31.
Sheduling Agreement will be created if there are Terms and Conditions on Delivery like 10 Days 20 Items.
2.Sales Contract can be created in VA41.
Details about Contract are stored in VBAK VBAP table with Document Category as G(Contract) and Transaction Group as 4(Contract)
3.Item Proposal can be created in VA51.
Item proposals are created, if certain material combinations are often ordered and delivered in certain quantities. When creating item proposals, different materials with proposed quantities can be entered. When creating an order, you can take items from the item proposal.
4.ARE1 can be created in J1IA101.
5.ARE3 can be created in J1IA301.
6.Stock transfer - PO raised - Delivery done in background using Tcode VL10B - Sales invoice is done - Goods receipt done done aganist Delivery
7. Make to order tables - MSSA, MSKA
Tables -
1. VBFA - Sales Document Flow
T code -
VOV8 - Maintain Sale order Types
MCSI - Standard Analysis for Info Structure
MC21 - Create Info Structure
MC24 - Create Update Info Structure.
No comments:
Post a Comment