Sap Sd End To End

SAP SD Overview: 1.Enterprise structure 2.Matser Data 3.Sales documents 4.Basic Functions 5.Business process 6.ABAP: IDOC,BAPI.LSMW,ABAP Debugging 7.FICO, GST 8.User exit and Customer exit 9.All Determinations in SAP 10.All Differences in SAP 11.Project work and BBP

Enterprise Structure: Definition: 1. Financial Accounts: Define company, credit control area, company code, Business area, Functional area, Maintain Consolidate Business Area, Profit Centre. 2. Controlling: Controlling Area, cost centers, operating concern 3. Logistic General: Define Valuation level,Plant,Location & Division 4. Sales & Distribution: Sales org,Distribution channel, maintain Sales Office & maintain Sales Group 5. Material Management: Maintain Storage Location & Purchase org 6. Logistic Execution: Define Warehouse, shipping point, maintain Loading group, Transportation planning point 7. Plant Maintenance: Maintain Plant Maintenance plant Assignment: Financial Accounting: 1. 2. 3. 4. 5.

Assign company to company code Assign company code to Credit control Area Assign company to Financial Management Area Assign Profit centre to company code Assign business area to consolidate business area

Controlling: 1.Assign company code to controlling area 2.Assign controlling to operating concern

Logistic General: 1. Assign plant to company code 2. Assign business area to plant/valuation area and Division. 3. Data comparison with sales plant/val area-Division-Business area SD: 1. 2. 3. 4. 5. 6. 7. 8. 9.

.Assign Sales organization to company code Assign Distribution channel to sales organization Assign Division to sales organization Setup sales area Assign Sales office to sales area Assign sales office to sales group Assign sales organization-Distribution channel-Plant Assign sales area to credit control area Business Area Account Assignment-Define rules by sales area, Assign business area to plant & Division, Assign Business area by sales area

Material Management: 1. 2. 3. 4.

Assign purchasing organization to company code Assign Purchasing organization to plant Assign Standard purchasing organization to plant Assign Purchase organization to reference purchase organization

Logistics Execution: 1. Assign warehouse number to plant and storage location 2. Assign Shipping point to plant Plant Maintenance: Assign Maintenance plant to Maintenance plant Company code assign to fiscal year and chart of accounts: 1.Financial account-GL accounts-Master data-preparation-Assign company code to chart of accounts. 2.Financial account-Financial account global setting-fiscal year-assign fiscal year to company code Create Account Groups: 1.Financial accounts-accounts receivable and payable-customer accounts-master data-preparing for creating customer master-define account groups,2.Define number ranges for customer master,3.assign number ranges to customer account groups. Standard Accounts Groups: 0001-Sold to party: Who place the order 0002-Ship to party: who receives the order 003-Bill to party: who receives the invoice 004-Payer: who settle the invoice

Accounts Groups for one time customer: CPD(Internal) & CPDA(External customer) Partner Determination procedure: T code VOPAN 1.IMG-SD-Basic functions-Partner Determination-Set partner determination-setup partner determination for customer master-Partner determination procedure-1.Partner function in procedure,2.Partner determination procedure & assignment,3.Account groups & functional assignment. SAP SD Fields: SE11, you can see fields SE11: create/change/Display Field Customer Master Fields: Company:RCOMP

AKONT:Reconciliation Account number

Company code: BUKRS

ZTERM: Payment terms

Customer Number: KUNNR

KONDA: Pricing Group

Sales organization: VKORG

VSBED: Shipping condition

Distribution channel:VTWEG

KKBER: Credit control area

Division:SPART Sales office: BKBUR Sales Group: VKGRP Plant: WERKS Shipping point: VSTEL Storage Location: LGORT SAP SD Tables: T code SE16,enter table name. Customer Master Tables: KNA1: Customer Master General Data KNB1: Customer Master Company code data KNVV: Customer Master sales area data KNVS- Customer Master shipping data KNVP: Customer Master Partner data Material Master Tables: MVKE: Material Master sales data MARA- Material Master General Data MARC- Material Master Plant data MBEW-Material Master accounting data

MARD-Material Master Storage location data Purchase order Table: EKKO-Purchase order Header EKPO-Purchase order item Sales documents tables: VBAK: Sales document Header VBAP: Sales document Item VBEP: Sales document schedule line category VBFA: Document flow VBUV: Incompletion Log Delivery document table: LIKP: Delivery document Header Data LIPS: Delivery document Item data Shipping Tables: VTTK: Shipping Header VTTP: Shipping item VTPA: Shippment partners Billing document tables: VBRK: Billing Header Data VBRP: Billing item Pricing table: KOMK: Pricing communication Header (Structure) KOMP: Pricing communication item (Structure) KONV: Condition transaction data KONH: Condition Header KONP: Condition item Output: NAST-Output Message status

Master Data: Keeping the records for long period of time. Master data is core data that is used as a base data for any transaction.

1.Customer Master Data,2.Material Master Data,3.Condition Master Data,4.Output Master data,5.CMIR data. Create customer Master: The customer Master data contains the information about business transaction and how transactions are recorded and executed by the system. Customer Master data consist three sections. These are 1.General data, 2.company code data3.sales area data. XD01/XD02/XD03/XD05/XD06(create/change/display/Block/Delete)-centraly XD07-Change account group, XD04-Display and change VD01/VD02/VD03—for sales FD01/FD02/FD03-for FICO Easy access-Logistics-SD-Master data-Business partner-Customer-create/change/display 1.General-Address/Control data/payment transaction/Marketing /Uploading points/Export data/contact persons 2.Company code: Account Management(Reconciliation account)/payment transaction(terms of paymet,payment method,payment history record check box,/correspondence/insurance 3.Sales area-Sales/shipping/Billing doc/Documents/partner function Sales-sales district/sales group/sales office/customer group/price group/customer pricing procedure/Item proposal/Cross selling Shipping-Delivery priority/shipping condition/Delivery plant, check box(POD, order combination, complete delivery req by law) Billing-Invoice Date, invoice listing date, inco terms, payment terms, credit control area,Account assignment group, MWST Tax, payment guarantee payment, check(rebate, price determination)

Maintain Material at company code level: OMSY Quantity/Value updating of Material: OMS2 Material Master:MM01/MM02/MM03 Material types: FERT: Finished Goods

NLAG: Non stock Material

HALB: Semi Finished Goods

LEIH- Returnable packing material

VERP: Packing Material

PIEP-Pipeline material

HAWA: Trading goods

ERSA-Spare parts

DIEN: Services

KMAT-Configurable material

Easy access-Logistics-Material Management- Material-Create

Material Master View: Basic data1:Base unit of measure, Division, product allocation,X-plant material status ,Item category group, Gross weight, Net weight, Material group pack material. Sales org 1: Base unit of measure,X-Disribution chain status,D-Specific Distribution status, Material Group, Delivery plant, Division, cash discount check box, MWST Tax, Min order Quantity, Min Delivery quantity. Sales org2:Material statistic group, Item category group, item category group, Material pricing group, Account assignment group, reference pricing material, Volume rebate group. Sales: General/plant: Availability check, Transportation group, Loading group, check (Batch Management and Appr.batch rec.req), Material freight group, Profit Center. Accounting1: Valuation class, price control, Moving price, standard price Purchasing: Purchasing group, Material group MRP1: MRP type, MRP Controller, MRP group, Lot size, Max lot size MRP2: procurement type MRP3: Total RLT, Strategy group MRP4: Replenishment quantity Plant Data 1: Min. rem. Shelf life

Sales documents Header: VOV8 IMG-SD-Sales-Sales documents-Sales documents Header Sales doc item category-VOV7 and item category determination: VOV4 Schedule line category-VOV6 and Schedule line category determination: VOV5

Inquiry:VA11 Quotation:VA21 Sales order:VA01 Scheduling Agreement-VA31 Contract-VA41 Back order-V_RA(SD),CO06(Material) Rescheduling-V_V2 Eassy access-Logistics-SD-Sales-Inquiry/Quotation/Order Basic Functions: 1.Pricing:

Pricing is based on condition technique. Condition technique is the process of determining condition records in sales documents. Condition technique is consist of condition records. Condition records will be stored in condition table. Condition table will be placed in access sequence from most specific to most general. Access sequence will be assigned to condition type. Condition type will be placed in pricing procedure. Condition Records (Vk11): Condition records is Master data of pricing, we also called as pricing Master. Condition table: V/03, Condition table is the combination of fields which will help to maintain the condition record. Combination: 1.Customer/Material, 2.Pricelist/Material, 3.Material Access sequence: V/07, It is a search strategy which will search for valid condition record from the most specific to most general. Exclusive indicator: If you check exclusive indicator, if system find valid condition record at any of the combination then system will immediately come out of the search strategy and determine the price in to sales document. If you uncheck exclusive indicator, if system find valid condition record, system will not come out of the search strategy. It will continues search in other combinations, if system find valid condition record in other combination then it will determine all the condition records into sales document. If it is a base price, active the last one deactivate previous one. If it is a discount then it will activate all. Condition type: V/06, It control the type of the pricing components, i.e whether it is a base price or discount or surcharge. Base price PR00:10000 Discount (K004):500 Gross price: 9500 Surcharge:200 Net price:9700 Net+Excise tax:100 Total:9800, Pricing Procedure: V/08, It is a procedure which consist of all the relevant condition types, which are placed in a sequence.

Configuration od Base price: PR00 a.Condition table: SPRO-SD-Basic functions-Pricing-pricing control-condition table: Manintain table number above 500(Up to 500 number is standard) . Field catalogue: Filed catalogue consist of allowed fields to create condition table, while creating condition table we need to select the fields from filed catalogue. Go to field catalogue, put crusher here and select(Customer/Material),(Pricelist/Material),(Material) one by one using page up and down select double click on technical and medium to move selected fields after selecting click on generate icon. We can save condition table in package. If you save in local object, it can not be transfer from server to another server and system will not generate transport request. Basis consultant will provide package. Cross client: The configuration and customization we do in one client will automatically update in other clients within a server. Cross client is also called as client independent. a. Define Access sequence: In access sequence we place the condition tables from most specific to most general. Access sequence configuration is also cross client. b. Define condition type:V/06 c. Define pricing procedure: V/08, these are 16 steps d. Assign pricing procedure or pricing procedure determination: OVKK. Sales are+customer pricing procedure+document pricing procedure+pricing procedure+ condition type. F. Maintain condition records:VK11 G: Maintain price list:IMG-SD-Basic fucntions-Pricing-Maintain price relevant master data filed-define price list: Discount: K004-Material discount K005-Customer/Material discount K007-Customer discount KF00: Fright charges(Surcharger), condition table: Inco term 1& 2 MWST- Tax, condition table: Select country-Departure-Generate and FTXP: Maintain Tax.

Header condition: Header condition is the condition which is applicable to all the line items in the sales document. HA00: Header discount% HB00: Header fixed amount HD00: Header fright

HM00: Order Value a.Header condition should be always processed manually b.Header condition doesn’t have access sequence C.It is always placed between base value and gross value. Group condition: If we check this header condition amount will be distributed among all the line items in proportionate to value of the line item. If we unckeck this then header condition amount will be proposed to all the line item in sales document. HA00: Header discount%, it is group condition as well as header condition HB00: Header fixed amount, it is group condition as well as header condition HD00: Header fright, only header condition HM00: Order Value, it is group condition as well as header condition Header fright condition: Fright condition type should be always placed between gross value and net value. It is only applicable for header condition. Order value: We use HM00 if we want to change total order value manually in sales document. Statistical condition type: Any condition type if it is statistical then it will have two effects. a.The value of condition type will not have any effect on net value. b.The value of condition type will not be posted into accounting. VPRS: The cost of the product which we maintain in material master, Accounting 1 view will be determined into sales document with the help of “VPRS” condition. SKTO: Cash discount, We maintain cash discount % in define payment terms, that cash discount% will be determined into sales document with the help of SKTO condition type. KUMU: Cumulative condition: It will be used in only BOM concept, KUMU condition type will help to cumulate the value of components and display the value in main item. Rebate condition: a. Group Rebate: Condition type: BO01 b. Material Rebate condition type: BO02 c. Customer Rebate condition type: BO03 d. Independent sales value: condition type: BO06 Intercompany condition type: PI01 is intercompany price (amount) condition types determine in intercompany sales order. PI02 is intercompany percentage IV01 is intercompany price condition type determine in intercompany invoice.

IV02 is intercompany percentage Some more condition type: EDI1-Customer expected price EDI2-Customer expected value AMIW-Minimum sales order value AMWZ-Minimum value surcharge Exclusion Group: Grouping of multiple condition type into one and allow the system to propose best discount or the least discount. Configuration: IMDG-SD-Basic functions-pricing-Pricing condition exclusion-condition exclusion for group of condition-define condition exclusion group:Z001 Assign condition exclusion group: exclusion group(Z001) condition type(ZR00) Maintain condition exclusion for pricing procedure: S.No(01) Cont excl pro(A) Exclusion group1() Exclusion group2() Condition exclusion procedure: A-Best condition between condition type B- Best condition with condition type C-Best condition between two exclusion groups D-Exclusive E-Least favourable with the condition F-Least favourable with the exclusion groups L-Least favourable with condition types Condition supplement: When Business wants to give certain discount irrespective of customer and material till certain period, then we can map the business scenario with condition supplement feature. Step 1: Define new pricing procedure and include conditions that are going to participate as a condition supplement for base price. PR00,K004,K005,K007 Step 2: Assign new pricing procedure in condition type Step 3: VK11:PR00 and select line item and go to ---condition supplement –Maintain condition records for K004,K005,K007. Step 4:VA01 raise sales order, you can check whether our condition supplement exit or not.

Group condition: If we check group condition then group condition amount will be distributed among all the line items in propionates to the value of line item. a.If we want to consider total document value then maintain group condition routine as “1” b.If we want to consider group of materials value then maintain group condition routine as “3” Ex 1: Configuration for group condition total document value: The client requirement is any order if the total document value reaches 1000000 then they want to propose 20000 discount. Step1: condition table: Sales organization-generate Step 2:Access sequence: click on exclusive Step3: Define condition type: calculation type(B), check group condition, Maintain group condition routine(1), scale basis(B) Value scale –save it. Step4: Pricing procedure: Placed condition type in pricing procedure Step5: Assign pricing procedure determination Step6: Maintain condition records:Vk11-condtion type-20000 and select this then go to scale and click on and scale value is 1000000 save it Go to Va01, you can check .

Ex 2: Group condition concept for group of materials: The client requirement is they have 3 materials X,Y,Z. While creating sales order if these material value reaches 1000000 then they want to offer 20000 discount. Step1: condition table: Select Material pricing group-generate Step 2:Access sequence: click on exclusive Step3: Define condition type: copy K004,calculation type(B), check group condition, Maintain group condition routine(3), scale basis(B) Value scale –save it. Step4: Pricing procedure: Placed condition type in pricing procedure Step5: Assign pricing procedure determination Create X,Y,Z material in material master,sales org 2 view maintain pricing procedure(01) Step6: Maintain condition records:Vk11-maintain -20000 and select this then go to scale and click on and scale value is 1000000 save it Step 7: VK11: Material X-10000,Y-10000 and Z-10000 save it. Go to Va01, you can check .

Dump error: ST05,ST22

Configuration eror:SCAT FBL5N F-28

2.Account determination: It is the process of determining G/L accounts while posting invoice values into accounting. While creating invoice in background system generate accounting document. The accounting document is Customer A/C Debit to………….Revenue A/C Credit. .For customer accounts system picks G/L A/C from Reconciliation A/C .For the revenue accounts system determine GL accounts from Revenue A/C determination. .Revenue A/C determination is Integration between SD and FI. .Revenue A/C determination is also based on condition technique. Configuration steps: Define account assignment group for customer and material: IMG-SD-Basic functions-account assignment/costing-Revenue account determination-check Master data relevant for account assignment-Define material/customer account assignment group. Create table:01,02,03,04,05 01: Sales org/chart of accounts/ Account assign of Customer/Account assign of Material Maintain access sequence for account determination: KOFI Define account determination type: KOFI Define account determination procedure: KOFI00 Assign account determination procedure: Step(10) counter(0) condition type(KOFI) Requirement(3) without CO Step(20) counter(0) condition type(KOFK) Requirement(2) with CO Define account keys:ERL,ERS,ERB,WMS.ERF etc Assign account Keys: Procedure(ZVAA01) step(80) counter(0) condition type(KOFI) account key(ERL) Assign GL accounts:VKOA Application(V) condition type(KOFI) chart of accounts(ACIA) sales or() account assign of customer(01) account assign material(01) Account keys(ERL) GL accounts() Provisional accounts() Provisional accounts will be use for settlement of rebate accounts. I e accurals. In customer Master Data , Billing section, maintain Account document Reconciliation A/C and payment Transaction tab, check Payment History record.

And sales are section, billing tab, check account assignment Group. Material Master- sales org 2-check account assignment goup. 3. Reconcialition account Determination: It is the process of determining Reconciliation accounts while posting invoice values into accounting. While creating invoice in background system generate accounting document. The accounting document is Customer A/C Debit to………….Revenue A/C Credit. For customer accounts system determines G/L A/C from customer master Reconciliation A/C. But if client requirement reconciliation account should not be determine from customer master, it should be determine based on some other combination like Plant & Division, then we will configure reconciliation A/C determination. Configuration: 1.SPRO-SD-Basic functions-account assignment coasting-Reconciliation A/C determinationManintain condition table(maintain condition table as per client req. plant & Division)Plant/Division-Generate-save it. 2.Maintain Access sequence:KOAB 3.Maintain condition type: KOAB 4.Maintain A/C determination procedure: KOFIAB 5. Assign A/C determination procedure: KOFIAB with F2 6. Assign GL A/C : Double click on our table(Plant/Division): Application(VB) Condition type (KOAB) chart of accounts() plant() Division() GL accounts() Provisional account() Provisional A/C will use for condition types are accurals, for rebate settlement. 7.Alternative Reconciliation accounts: GL A/c() and Alternative GL A/C() 4.Cash Settlement Account Determination: It is the process of determining GL accounts while creating case sale invoice. When we create cash sales invoice,Cash settlement account Dr to…………….Revenue A/C cr. Configuration: 1. Cash settlement A/C determination: Maintain condition table: create condition table with sales org 2. Maintain field catalog: 3. Maintain Access sequence: CASH 4. Maintain condition type: CASH 5. Maintain account determination procedure:KOFIAC

6. Assign Account determination procedure: Billing type(BV) and Account determination procedure(KOFIAC) 7.Assign GL A/C: Application(VC) condition type(CASH) chart of accounts() sales org() GL A/c() 5.Delivery Scheduling: It is the process of determining Delivery dates and confirmed quantities into sales document. System consider the below parameters while performing delivery scheduling. 1.Pick Pack time: It is the time taken pick the material from storage location and to pack it.(maintain in shipping point) 2.Loading time: It is the time taken to do the process of loading the goods into trucks for dispatch. ( maintain in shipping point) 3.RLT: It is the time taken Manufacturing the product. System consider RLT if stock is not available.(Replenishment Lead Time-Material Master, MRP3 view) 4.Transist Time: It is the time taken deliver the goods from plant to customer. (Maintain this in Route determination) 5.Transportation Lead time: It is the time taken to arrange the mode of Transportation for dispatching it to customer. Whenever we create a sales order, 1st system will perform “Backward Scheduling” If backward scheduling fails then system will perform “Forward Scheduling”. .Backward scheduling is always based on customer requested Delivery date. .Forward Scheduling is always based on Today’s date. If the propose date is beyond today date, backward scheduling fail. Configuration:IMG-SD-Basic fucntions-Delivery scheduling and Transportation scheduling .Define scheduling by sales documents type: Sales doc type(OR) Dlv scheduling() Transportstion scheduling() backward scheduling() .Define scheduling by shipping point: Maintain Pickpack and Loading time here .Maintain working hours .Maintain Duration 6.Route determination: Departure zone/country from Shipping point Shipping condition from Sold to party Transportation group from Material Master Transportation zone/Destination country from ship to party Delivery group of Material Master –If re determined in the delivery doc.

Define mode of transport: IMG-SD-Basic functions-Define route-Define mode of transport: Define shipment type: Define transportation connection point: Define route and stages: Create venoder:Logistics-SD-Master data-Business partner-Forwarding agent-create V.11 Define route determination: Maintain country and transportation zone for shipping point: Define transportation group: Maintain route determination: Go to VA01 and check route existed or not

7.Partner Determination procedure:

Define partner function:IMG-SD-Basic functions-Partner determination-setup partner determination: Define partner determination procedure: Assign partner functions in partner determination procedure: Partner determination procedure assignment: Assign partner functions to account group:

8.Output determination: IMG-SD-Basic functions-Output determination-Output determination using condition techniqueMaintain output determination for sales/delivery/billing documents:V/57 Maintain condition table: select sales org Maintain output type:V/30 Maintain access sequence: Output condition type;BA00(order) Access condition () If we check system will determine output type from condition technique, if we unckeck system will determine output from customer master with help of DB0001. Can not change: If we check, system will not change output type. Multiple issuing: If we check, system will allow multiple printout and mails in sales doc

Partner indep output: If we check, each output will be send to all partners(Quotation, & order will send sold to party, delivery will send ship to party ,invoice will send to bill to party) Do not write processing log: If we check system will not display the log info while issuing outputs. Change output: Only for output mail configuration, if we want to send different format of mail. Default values: Whether to send the output with some back ground job or some application of Transaction or send immediately while saving the transaction. Transmission medium: 1-Printout, 2-Fax, 5- External send (Email), 6-EDI(SAP to non sap) A-ALE(SAP to another SAP system)

Assign output types to partner functions: Maintain output determination: Step(10) counter() condition type() requirement(2) Allocate sales document Header: V/43: sale doc type(OR) and output procedure() Allocate sales document Item: V/69 Maintain condition records:VV11(sales),VV21(delivery),VV31(Billing) Easy access-Logistics-SD-Master data-output-Sales doc-vv11 T.code: NACE= Output control(V1-sales,V2-Delivery,V3-Billing) NAST=Output table

9.Text Determination: IMG-SD-Basic functions-Text control-Text types: Define Text determination procedure: Assign Text ID to Text determination procedure: Assign Text determination procedure for account group: Maintain Text in the customer Master:XD02,sales area-Extras-text Text determination procedure for sales doc Header: Define Text type: Define access sequence: Define Text determination procedure: Assign Text ID in text procedure: Assign access sequence for text ID’s: Assign document type to text determination procedure

10.Incompletion Log: IMG-SD-Basic functions-Log of incompletion items-define status group: OVA0: Which function will carried out incompletion procedure in SD. Here you can check, General, Delivery,Billing,Pricing,Goods Movement,Picking/Putaway,Pack Define incompletion procedure: OVA2 Group: A-Sales Header B-Sales Item C-Sales Schedule line D-Partner F-Sales Activity G-Delivery Header H-Delivery Item

Assign incompletion procedure for sales/delivery/billing: VUA2 Assign Procedure to Sales Header,sales Item, Sales schedule line, Delivery Header & item etc.

11.Bill of Material (BOM): Configure BOM item:CS01 Easy access- Logistics-production-Master data-Bill of Material Above structure: Item category:ERLA, item category: TAQ(Header level),TAE(sub item), delivery and billing carried at header level,sub item treated as text item Below structure:item category :LUMF, item category: TAP(header level),TAN(sub item),delivery and billing carried at sub item, header item is text item.

12.Material determination: It is the process of submitting one product in place of other product. Reason for substitution: a. If the product is discontinued and coming with new product b.If the product is not available C.Combo packs (Promotional activity) Item category System Header Pricing: TAX and TAPS Item category System Item Pricing: TAPA and TAN

Define condition table: Sales org & Material-Generate Access sequence: A001 Define condition types: A001 Define material determination procedure (A00001): Step(10) counter() condition type(A001) Requirement() Assign procedure to sales doc type: OV14: sales doc type(OR) and Procedure(A00001) Define substitution reasons: OVR0 Substitution reason (0005) strategy() outcome() substitution strategy() Strategy: (Blank-Automatic, A-Substitute products are displayed for selection,B-General material determination with selection, without ATP) Strategy: Product selection in the background is performed on the basis of availability check. Outcome: (Blank-Item will be replaced, A- Substitute products are displayed as sub items, B-As in A but only when creating the item in sales) substitution strategy-(A- Substituted by product services) Maintain the condition record for material determination: VB11 Logistics-SD-Master data-Products-Material determination: VB11 The result of MRP indicator: OVZ9 MRP indicator in Material determination: If we check MRP indicator, if stock of substituted item is not available then system will try to submit another material in sales doc. If you want to see MRP indicator in Material master, Go to VB11 and enter material, select line Material and double click, You will get new screen Alternative Material and MRP indicator. 13.Item Proposal: VA51 Listing of materials for which customer regularly place order, and calling the list while creating sales order. Item proposal will save the time of end users who is creating sales order. Logistics-SD-Master data-products-item proposal-VA51,create sales doc type PV. You can enter list of materials and save. Go to VA01 and check. Create product proposal: VOV8-MS XD02: check item proposal check box in customer master sales area section

14.Material Listing & Exclusion: Listing: Listing is Allowing customer to buy only listed materials Exclusion: Restricting materials which customer is not eligible to buy.

Maintain condition table for Listing & Exclusion: select customer/material-Generate Maintain access sequence:A001 for listing, B001 for exclusion Maintain Listing/Exclusion types: A001 for listing, B001 for exclusion IMG-SD-Basic fucntions-Listing/Exclusion-procedure for maintain Listing/Exclusion: A00001 for Listing, B00001 for Exclusion Active listing/Exclusion sales doc type: OV04: Sales order(OR) Listing(A00001) Exclusion(B00001) Maintain condition records for Listing/Exclusion:VB01: Material(XXXX) Description Logistics-SD_Master data-products-Listing/Exclusion:VB01 15.Cross selling: It is the process of selling additional products along with main products. IMG-SD-Basic functions-Cross selling-Define determination procedure for cross selling-create condition table: OV46:sales org/plant Maintain access sequence: OV41 Define condition types: OV42 Maintain procedure for cross selling: OV43 Define customer procedure for cross selling: Define document procedure for cross selling: Assign document procedure for cross selling to sales document: Define cross selling procedure: Assign cross selling procedure: Maintain condition records: VB41 Logistics-SD-Master data-products-cross selling-VB41 Go to XD02: Assign product proposal in sales area section in customer master. Customer Master-Sales Area section-sales tab-PP customer procedure(B-Cross selling)

16.Customer Material Info Records: VD51: customer place the order with own material code, we can create CMIR. Logistics-Logistics execution-Master data-Customer material information-create:

Credit Management: SD+FI

It is the process of managing credit limits of the customers. Every company has Credit Management Department, this credit Department will manage the credit limits of the customers. Role and Responsibilities of credit Management Department: a. They Fix credit limits to the customers b. Monitoring the day to day transactions and any of the customer credit limits exceeds then they block the next transaction. c. Releasing the order which is blocked for credit. Credit Management can be configured two ways: A.Simple credit check, B. Automatic Credit check

Simple credit check: OVAK IMG-SD-Basic functions-Credit Management/Risk Management-Simple credit limit check: sales doc type+credit check+credit group. Update group:12,15 & 18, Update group controls, which sales documents updated in credit Management. Define credit control area: OB45, Update group 12,15,18 Assign company code to credit control area: OB38 FD32:check payment history V/08: In pricing procedure,put net value of subtotal value is A, pricing will connected with credit Management.

B. Automatic credit check: Define credit control area: OB45 Assign permitted credit control area to company code: IMG-Financial accounting-Accounts receivable/payable-credit Management-credit control accounts-assign permitted credit control area to company code: Assign company code to credit control area: Define Risk categories: OB01(IMG-FI-Define Risk category):High,Medium & Low risk Define preliminary settings for credit Management: Define Text ID’s for credit Management: OBT3 Maintain Text ID’s for central text in credit Management: OBT3Z Define credit Representative Group: OB02

Define Groups: Define credit Representatives: OB51 FD32, Specify customer number and credit control area. Define credit limit check by sales documents type: OVAK(IMG-SD-Basic functions-credit Management) Define credit limit check by Delivery order: OVAD Define credit limit check by item category: OVA7 Define credit groups: OVA6(credit group for sales order,delivery,PGI) Define automatic credit control: OVA8: Credit control area+risk category+credit group VKM3-for release credit limit VKM4-for sales & delivery doc VKM5-for release delivery doc. Automatic credit control fields: OVA8: Item check= If we check this, then system will perform credit check while entering the line item in sales document. Diviation%= After releasing the order which is blocked for credit ,if user is changing the value in that order then system will again block the order for credit.The control is Diviation in %. If we want to allow increasing up to some% then maintain the % value. Number of days=After releasing the order which is blocked for credit, if there is no further process within the number of days mentioned here,then system will again block the order for credit. Credit limit seasonal factor: This will be used to increase or decrease the credit limits to the entire customers during a particular period. Statistic=If we check statistic, then system will update all open order, open delivery, open invoice and open item value in credit check(FD32). Reaction= This field controls how system should respond, if order is blocked for credit, i.e whether to give warning message or error message or no message. Status/Block= If we check this then while creating sales order if customer credit limit exceed then system will block the order for credit. If we uncheck this even a customer credit limit exceed system will not block the order for credit. Open orders: IF we check this then only system will perform credit check while creating order and if customer credit limit is exceed then system will block the order. If we uncheck this then system will not perform credit check in sales order and system will not block order. Open deliveries: If we check this then only system will perform credit check while creating delivery document. The blocked order value will not be update into credit Management(FD32).

Dynamic=If we check this , then system will update all open order, open delivery, open invoice and open item value in credit check, but any open order if the delivery creation date is exceeding horizon date that order will not be updated in credit Management(FD32). Document value=If we check this and if we maintain max document value then while creating sales order if sales order value exceeds Max.Doc value then system will block the order for credit, the reason is document value is exceeds. Critical fields=If we check this then while creating sales order,if user changes any of the critical fields then system will block the order for credit even though the customer have enough balance. Critical fields are(payment terms,fixed value date and additional value days) in credit Management. Next Review date=If we check this while creating sales order system will check order date with next review date if the sales order date is exceed next review date then system will block the order for credit .The reason is review date Has been passed.We maintain next review date in FD32 status view. Open items=If we check this then if we maintain max open item % then while creating order system will check is there any open item existing for this customer or not, if yes then it accumulate the value of open items and system will also check is any of the open item is overdue or not, if is there any overdue item then system will do accumulate the values of overdue item and calculate the % between overdue item and open item value.If this% exceed Max open item% then system will block the order for credit. Oldest open item=It is nothing but overdue item, if we check oldest open item then while creating sales order system checks for this customer is any one of the previous invoice is overdue or not, if yes then system will block the next transaction. Payer=Payer is checked, If customer have multiple payers. Payer check is only applicable only for open item and oldest open item. If we check payer, then system considers the invoices of only that particular payer while performing open item check and oldest open item check. If we uncheck payer then system consider the invoices of the all payers who are in a group, while performing open item and oldest open item. High dunn level=Dunning is the process of sending reminders to the customers, whose payment is delayed. Dunning configuration done in FI consultant. User1,user2 & user3=If client’s requirement related to credit Management is not fulfilling with standard configuration then we use user exits.

17.Transfer of Requirement/Availability check: Transfer or Requirement: SD+MM+PP TOR will help to transfer the sales order requirements to MRP.

If we don’t transfer the requirements, then the employees at the plant will not know the information of sales order requirement, and the result is even if stock is getting emptied they will not start the production. If we are not transfer the sales order requirement to MRP, system could not be able to perform availability check.  

When we create sales order, first system determines requirement type into sales document in procurement tab and requirement type will help to determine requirement class. Requirement class controls how to transfer the sales order requirements to MRP.

Prerequisite for Transfer of Requirement: 1. Schedule line category: Icheck Requirement & assembly availability check 2. Requirement class: Check Requirement and availability check 3.Requirement type should be determined into sales document.



Criteria to determine requirement type in sales doc: 1.Strategy group(MRP3 view), 2.MRP Group(MRP1), 3.Item category+MRP type(MRP1) 4.Item category.

ATP Quantity=Warehouse stock+ Planned Receipts-Planned issue System creates a demand with MRP by Requirement type 041. 1.Define Requirement classes: OVZG(IMG-SD-Basic functions-Availability check & Transfer of Requirements-Transfer of Requirements-Define Requirement classes=41/11/KE/KEB 2.Define Requirement type: OVZH:KE/41/11/KEB 3.Determination of Requirement type: Item category+MRP type 4.Define procedure for each schedule line category: Check requirement and availability check 5.Block quantity confirmation in delivery block: If we check confirmation block then while creating sales order system will cancel the confirmed quantity. 6. Maintain requirements for Transfer of Requirements: OVB8: Requirement number (101) in TOR,If order is blocked for credit, system automatically cancel the confirmation. 7.Maintain requirements for Assembly and purchase order: OVB5: Requirement number (102) in TOR, If order is blocked for credit in IPO & third party, system will not generate PR.

18.Availability check: SD+MM+PP+CO: It is the process of checking the stock availability of the material while creating sales order. Prerequisite to perform Availability check:

1.Availability check field in material master: General/plant Data view in material master: This filed also called as checking group. 01-Daily requirement: If we maintain 01 then system cumulates the sales order quantities on that particular date and update in single line in MD04. 02-If we maintain 02 the each sales order quantity will be update in MD04 along with the sales order number. KP: If we maintain KP in availability check the system will not perform availability check. 2. Schedule line category: If we check Requirement & assembly availability check in schedule line category then only system will perform availability check. 3. Requirement class: Check Requirement and availability check 4 .Requirement type should be determined into sales document.

Criteria to determine requirement type in sales doc: 1. Strategy group (MRP3 view), 2.MRP Group(MRP1), 3.Item category+MRP type(MRP1) 4. Item category.

Configuration for availability check: A. Availability check with ATP: B. Availability check with product allocation: When shortage of material C. Rule based Availability check: Many plants will perform Define checking group: OVZ2(IMG-SD-Basic-Availability check-Availability check with ATP Logic1.Checking group: In define checking group we have actual controls of how to update sales order quantities in MRP. I. e total records per day or single records For 01 we maintain “B” Total records per day For 02 we maintain “A” Single records 2.Define material block for other users:If multiple users are performing availability check for same material and in the same plant same time, then system will perform availability check for 1st user and block availability check for other users. A-order, B- Delivery 3.Define checking groups default values: if we maintain checking group system automatically determines it while creating material master. Material type with plant and availability check. 4.Carryout control for Availability check: OVZ9: Scope of check is also called as availability check control. We can configure scope check in the combination of (checking group+ checking rule)

If we want to configure availability check in order then checking rule is A. If we want to configure availability check in Delivery then checking rule is B. Stocks: Include safety stock, Stock in Transfer, Include quality inspection stock and include blocked stock In/Outward Movements: Include purchase order,Incl Purchase requisition, incl sales requirements, incl deliveries, inc planned order, incl production orders Replenishment lead time: () Check without RLT.

5. Define procedure by requirement class: OVZ0: We have to requirement and availability check here.41,KEB,40 etc… 6. Define procedure for each schedule line: In “CP” requirement and availability check 7. Determine procedure for each delivery item category: This configuration step controls whether to perform availability check in delivery or not. The below scenario we have to perform availability check in Delivery: a. When we create delivery W/O reference b. Adding new line item in delivery c. Increase the quantity in Delivery d. STO Delivery 8. Define default settings: If we check fixed date and quantity, system will not allow to change the delivery dates and confirmed quantities while creating sales order. Availability check rule: This field will help to propose POPUP in case of shortage of stock. 9. Checking rule for updating back orders: Copy Control: VOFM: Copy controls are used when we are creating a document with reference to another document. Purpose of copy control:  

It will help to copy the data from source document to target document. It controls whether to create a document with reference to another document or not.

Sales doc to sales doc:VTAA IN-QT,QT-OR,RE-SDF,OR-RE,QC-OR,WK1-OR,WK2-OR Sales doc to Delivery doc:VTLA OR-LF,RE-LR,CF-LF,CI-LF,CP-LR,COND-LR,DL-LO,FD-LF,RO-LF,CS-BV,DS-LF,SDF-LF Sales doc to Invoice:VTFA CS-BV,RE-RE,CR-G2,DR-L2,OR-F2,OR-F5 Delivery to Invoice:VTFL LF-F2,LF-F8,LO-F8 Invoice to sales doc:VTAF

F2-RE,F2-CR,F2-RK Invoice to Invoice:VTFF F2-S1

1.VTAA (Sales to sales) Copy requiremnets(001):Header same customer 002-Header different customer 003-Material reservation 21-Billing Header 302-do not copy item 303-Always an Item 501-Scheduled quantity () copy item () complete reference

2.VTLA: Copy requirements (003): Delivery to invoice standard req Same all req Requirement 11-without PGI, we can do invoice. 3.VTFA: Header: Copy requirement(001)-Header/Order related 002-Item/order related 003-Header/Delivery related 004-Delivery related item 005-cancellation Header 006-Cancellation item 007-Header/order proforma invoice 008-Item/ order proforma 009-Delivery rel proforma Header 010-Delivery rel proforma Item

011- Header/Delivery related W/O GI 012-Order related/third party item 14-Header Delivery rel Intercompany Billing 15-Item Delivery rel intercompany Billing 016-Invoice list

Reference number() A-Purchase order B-Sales order number C-Delivery number D-External delivery number E-Current Billing document number F-External delivery number if available. Assignment number() A-Purchase order number Same as above.

() Copy item number: System indicate copy the item number from source doc to target doc Item: Copy requirement(012) In order to Billing the item to copy requirement is(012) Data VBRK/VBRP(001): 001-Invoice split 002-Order related Credit Memo req 003-Single invoice 005-Intercompany billing Billing Quantity(F): C-Order quantity D-Delivery quantity E-Goods receipt quantity less invoice quantity F-Invoice quantity less invoiced quantity

Pricing type(): A-Order quantity less invoiced quantity B-Delivery quantity less invoiced quantity D-Copy pricing elements unchanged G-Copy pricing elements unchanged and redetermine tax

Business process: 1.Inquiry(IN): whenever Customer inquiry about the product, we create inquiry doc in SAP. Ex: Phone ,Email, walk-in,website,tender notice etc. 2.Quotation(QT): After creating inquiry doc in SAP, in return we create quotation doc with reference to inquiry and send this quotation to customer. Quotation doc consist of customer details, Material details,pricing, specification details,validity details and terms & conditions. 3.sales order(OR):Finally if customer satisfy, he will place the order. Order is an agreement between company and customer for supplying the goods to customer. Sales order is consist of customer details, material details, delivery details, quantity details, pricing, terms and conditions etc. While creating sales order system will perform various activities in the background. Partner determination, Availability check, TOR, Pricing, credit management, ouput determination, text determination etc. 4.Delivery: In delivery we have 3 activities: Picking, packing and PGI. When we do PGI system will perform various activities in background. 1. Stock update 2. Inventory Account document generates 3. It update in doc flow 4. It update in credit Management 5. It update in LIS 6. It update in Billing due list

5. Invoice: After PGI, we create invoice, and dispatch the goods to customer along with invoice copy. When we create invoice, in the background system will perform various activities.

1. Revenue account document generates 2. Profitability account document generates 3. Cost centre document generates 4. It update LIS 5. It update Document flow 6. It update in credit Management

6. Return order (RE): Customer will return the goods if the goods are damaged, expire or defective. Whenever customer finds damaged or defective goods, he will inform to sales office, sales office people will send the employee to cross check the damaged or defective goods. After cross checking sales employee will prepare return note. After preparing return note, the employee will submit the return note to sales office. Then SAP end user create return order with reference to invoice and Mention the reason for returns. When customer delivers the return goods, we create return delivery with reference to return order. We create return invoice with reference to return order.

7.Credit Memo request (CR): We use credit memo request, If we want to deduct the amount from customer outstanding without receiving the goods back from customer. Scenario: 1.Users mistakenly over charges the previous invoice, The goods are totally damage in customer place and which are not in a position to take back. Revenue A/C Dr………..Customer A/C Cr. 8.Debit Memo request (DR): We do debit memo request, If we want to add some amount to customer outstanding without physical movement of goods. Scenario: 1.Users mistakenly under charges the previous invoice 2.Charging interest to customer for late payment Customer A/C Dr……………..Revenue A/C Cr

9. Invoice correction request (RK): We use this if end-user do a mistake in previous invoice, the mistake can be overcharged or undercharged. By using this invoice correction request, we can either deduct the amount from customer outstanding or add customer outstanding. 10.Cash Sale(CS or BV): Cash sale process is also called as Counter sale process. i.e the customer will walk into outlets, pick the materials and go to the customer, pay the cash, take the bill and leave the counter.

11.Rush order(RO): Pay the money, pick the material and invoice later. 12.Free of charge Delivery(SD): Whenever we are sending sample to customers without raising invoice then we do free of charge delivery. 13. Subsequent free of charge delivery (SDF): Replacing the goods to customer Whenever customer returns the goods, we deduct the amount from customer outstanding. Instead of deducting the amount from customer outstanding. if we want to replace the goods to customer without charging then we do subsequent delivery free of charge. 14.Quantity contract(QC): It is an agreement between company and customer for supplying the goods for a particular quantity within a specific validity period. QC=VA41 15. Value Contract-WK1: 16.Value contract-WK2: 17.Scheduling agreement-SA:VA31: 18. Consignment Fill(CF): Consigning fill up is just dumping the stock at Consignment Agent place without transferring ownership and without raising invoice. CF KBN 631 E1 The effect of 631 is: a.I will reduce the stock from unrestricted stock and stock will be added to consignment stock. b.No inventory accounting doc generates because CF process is not relevant for invoice. 19.Consignment issue(CI): When consignment agent sell the goods to their customers then consignment agent will inform to company. CI KEN 633 CI The effect of 633 is:

e. Stcok will be reduced from consignment stock and inventory A/C will generate. f. Cost of goods A/C Dr to ……..inventory A/C Cr. 20.Consignmnet Return(CONR): When end customer returns the goods to Consignment agent , then consignment agent will inform same to company , then we do consignment returns. CONR KRN 634 DO The effect of 634 is: a. Stock will be reduced from Consignment stock b. Inventory accounting document will generate and accounting entry is Inventory A/C Dr to………..Cost of Goods A/C Cr.

21.Consignment Pickup(CP): If consignment agent request to take back the consignment stock, then we do consignment pickup .When we do return delivery in consignment pickup , the stock will be reduced from consignment stock and added back to unrestricted stock. CP KAN 632 F1 The effect of 632 movement type is: a.Stock will be reduced from consignment stock and added to unrestricted stock. b.Inventory accounting document will not generate because CP is not relevant for invoice.

22.Third party sales(SD+MM): Scenarios: a. Stock is not available, b. not manufacturing these products C. Problem in manufacturing unit

1.Third party sales with shipping notification: Item category: TAS Item category group: BANS, material type: HAWA Billing relevance F control that 3rd party without shipping notification, If MIRO is not created then system will not allowed to create invoice to customer, Item category TAS(order related billing according to invoice quantity) is MIRO. Billing Relevance G control that 3rd party with shipping notification, If MIGO is not created then system will not allowed to create invoice to customer, item category TAS (Order related billing according to Delivery quantity) is MIGO. Create PO automatically: If you maintain ALE data for purchase order in sales organization, while creating sales order in 3rd party and IPO, system automatically generate purchase order. In Schedule line category: CS Order type:NB: It will be help to generate purchase requisition automatically in the background while creating sales order in 3rd party. Item category(5): Item category 5 control that even we do MIGO in 3rd party with shipping notification system will treated as dummy MIGO and stock will not be update. Account Assignment category(1): It control that whether to generate inventory accounting document or not while doing MIGO and PGI. Copy Control order to invoice(OR-F2) :Billing quantity F and it will help to copy the quantity from MIRO to invoice while creating invoice to customer in 3rd party.

Billing quantity E and it will help to copy the quantity from MIRO to invoice while creating invoice to customer in 3rd party. 3rd party without shipping notification: XD01>MM01>VA01>XK01>ME21N>MIRO>VF01 In VF01,reference quantity will copy from order, but actual quantity will copy from MIRO. T.code: Table:SE16N. 3rd party with shipping notification: XD01>MM01>VA01>XK01>ME21N>MIGO>VF01 3rd party return order: Item category group TASG,copy control RE-RE, copy requirement as (28) VBRK/VBRP:002 Billing quantity (F) plus/Minus(+),pricing type (D).

23.IPO: XD01>MM01>VA01>XK01>ME21N>MIGO>MIRO>VLO1N>VF01 Sales order-purchase order-Goods receipt-Invoice receipt-Delivery-invoice to customer. Requirement type KEB,special stock indicator is E. Requirement class is KEB Item category is TAB(Billing relevance is A), Item category group is BANC. Schedule line category is CB(Movement type(601),order type is NB, Item category (0), Account assignment (E),check item relevant for delivery and purchase requisition delivery scheduling) 24.Make to order: When customer place the order with own requirement, will start the process of Manufacturing of products. Configuration: 1.XD01 MM01:Item category is 0001.Strategy group is 20(MRP3) VA01: Check Requirement type is KE in procurement tab. Requirement class is 40. Item category is TAK and Special stock indicator is “E”, controls that after manufacturing finished goods the stock will be reserved to particular sales order number. Account assignment category “E: control that when we take finished goods in stock and we do delivery in MTO then accounting doc will not generate.

VA01>MB1C>MMBE>VL01N>VF01 25.Stock Transfer order: A. Intra company STO process: Transferring the stock from one plant to another plant within the company. It is transfer from Depot to Depot.

One step process: Receiving plant will raise PO to supply plant, Supplying plant will do delivery with reference to PO, stock will be added to receiving plant. Two steps process: Receiving plant will raise PO to supplying plant, supplying will do delivery with reference to PO, Stcok will be showing as stock in transit, after doing MIGO, stock will be added to receiving plant. Configuration: 1.Receiving plant as customer in supplying sales area 2.Extended Material both plants with purchasing view 3.Define shipping data for plants: SPRO>MM>purchasing>PO>setup Stock Transport order>define shipping data for plants 4.Assign delivery type and checking rule: we assign delivery type NL and checking rule B to the combination of purchase order type UB and supplying plant. 5.Assign document type, one step procedure, under delivery Tolerance

Process 1: ME21N 2.VL01D: enter shipping point .Check MD04 in stock 3.VOV7: Item category NLN: Maintain billing relevance D(Performa billing) VOV8: Doc type (DL), maintain customer pricing procedure(A) Copy control-VTFL-position(F8-NL)-maintain copy requirement(009)delivery related proforma invoice for header. 4.VF01:Billing type F8 5.MIGO: Check stock MD04. Intra company STO

Inter company STO

Movement type two step

641

643

Movement type One step

647

645

Order type/PO type

UB

NB

Delivery type

NL

NLCC

Item category

NLN

NLC

Schedule line category

NN

NC

Intra company Return STO

Intercompany Return STO

Movement type two step

671

673

Movement type One step

677

675

Order type/PO type

UB

NB

Delivery type

NLR

NCR

Item category

NLRN

NCRN

Schedule line category

NR

NS

Two step: ME21N>VL10D>VF01>MIGO One step:ME21N>VL10D>VF01>MIRO is not require STO Return: ME21N>VL10D(without PGR)>MIGO>VL02N(PGR) Intercompany STO: ME21N>VL10D>VF01(intercompany billing type IV)>MIGO Inter STO Return:ME21N>VL10D>VF01(inter company billing type IG)>MIGO IG-Inter company credit Memo.

26. Intercompany sales: Customer place the order to the company, If stock is not available ordering company will send transfer of requirement to supplying company and supplying company will deliver the goods to customer, send invoice to the ordering company, ordering company will raise invoice to supplying company. XD01>MM01>VA01>MB1C>MMBE>VL01N>VF01>VF04 Configuration: 1.create customer with ordering company company code, sales org or, distribution channel and division. 2.Create Material Master with Finished Goods. And extended material both the plants. 3.Create internal customer with supplying company, sales org, Distribution channel and division. 4.Assign internal customer with ordering company sales organization: IMG-SD-Billing-Inter company billing-Assign internal customer with ordering company sales org. 5.Assign Delivering plant with ordering company sales line:IMG-Enterprise Strcuture-Assign plant, sales org and Division. 6.Create sales order:VA01-assign delivering plant in order. Check PI01 condition is determined or not. In pricing, maintain pricing procedure with PR00, Maintain condition records for PR00

Assign Supplying company sales area to pricing procedure ICAA01 with PI01,Maintain condition records for PI01.PI01 is reference condition for IV01. 7.Delivery:VLO1N, Picking, packing and PGI 8.VF04: Raise invoice from supplying company to ordering company , IV01 condition type, reference condition type is PI01.Biling type is IV, uncheck delivery related invoice, check Inter company billing. 9.VF01:normal invoice raised from ordering company to customer

1.Difference between Configuration and customization? Configuration: It is the process of mapping your business process/requirements with already existing SAP standards. i.e going in SPRO. Customization: It is the process of mapping your business process with some changes(as per your requirement) as against existing in standard SAP & there by developing your own customized screens/reports i.e Z reports. Customization is oftenly termed as a development or developed report(Z report).

S

2.Difference between Invoice and billing doc? Ans: Invoice is a document indicating to deliver goods and Billing is receipt of payment. Bill means we have to pay the amount against bill invoice means we have to receive the amount against the invoice. 3.Difference between alternative calculation type and base type? Profit margin:11: Alt cal Gross weight 12 & Net weight 13: Alt base type, Conditional base value: When a value is derived for a condition type, based on certain calculations this value is taken as base. Condition value: For the number of units ordered depending on the condition amount mentioned this value is derived.

4. Difference between Performa invoice and normal invoice? Answer: Performa Invoice:    

Performa invoice is a document that is used for the documentation purposes. This is the mirror image of the original invoice that would be created in future date. Performa invoices are used in export businesses for documentation purposes before goods movement, but the original invoice will be created during goods movement. Goods issue is not required before you created a delivery related pro forma invoice.

   

You can create as many pro forma invoices as you like for a sales order or a delivery because the billing status in the sales or delivery is not updated. Data from the pro forma invoice is not passed on to financial accounting. It is generally created in Export sales and mainly in STO. Exmaple:Quotation Normal invoice: Which is issued by the sellers to the buyer to request payment of goods delivered.

5.Difference between GL accounts and reconciliation account? GL: Ledger account Reconciliation: Sub Ledger account

6.Difference between Accounting key and accrual Key in Pricing procedure? Accounting Key: Different type of GL account, posting amount to revenue account Accrual key: Different type of GL accounts for accrual or provisional, which are posting certain type of rebate accurals. Accrual accounting which requires recording revenues when they are earned and not when they are received in cash, and recording expenses when they are incurred and not when they are paid. Rebate: Return of a portion of a purchase price by a seller to a buyer, usually on purchase of a specified quantity or value, of goods within a specified period 7. Difference between rebate and discount?. Discount: Discount is the reduction offered by a seller to the buyer from the purchase price of goods or services. Rebate: Rebate is refund or return of currency value that a seller of goods provides to the buyer for various different reasons. To promote high quantity purchases or receive early payments before a certain due date. 8.Difference between Direct and Indirect Tax? Direct Taxes are non-Transferable taxes paid by the tax payer to the government and indirect Taxes are transferable taxes where the liability to pay can be shifted to others. Direct Tax: Income Tax,corporate tax,wealth tax and inheritance tax Indirect Tax: VAT , those paid by consumers when they buy goods and services.GST,sales Tax,Service Tax,Custom Duty, Excise Duty. 9.Difference between Provisional accounts and accrual ? Provisional accounts: Provisional means that something is conditional or interim or subject to change or alteration. Therefore , the provisional financial statement are one that is subject to change. Ex Bad Debts, sales allowances and inventory obsolescence.

A provision is an amount that you put in aside in your accounts to cover a future liability. In accounting, accrued expenses and provisions are separated by their respective degrees of certainty, All accrued expenses have already been incurred but not yet paid. By contrast, provisions are allocated toward probable, but not certain, future obligations. Determinations: 1.Item category determination: Sales doc type+Item category group+item uasage+Higher level item category 2. Schedule line category determination: Item category+MRP type 3. Pricing determination: Sales area+customer pricing procedure+doc pricing procedure 4. Shipping point deter: Shipping condition+Loading group+plant 6.Storage location: Shipping point+ Storage condition+plant(Mala) 7. Storage Location: Situation+storage condition+plant(Reta) 8.Credit control area determination: Company code+credit group+risk category 9.Route determination: Departure zone of shipping point+shipping condition+Transportation group+Tranportation zone or destination point. 10.Account determination: Chart of accounts+sales org+customer account group(Customer Mastersales area-billing tab)+Material account group(MM-Sales org2)+Account key 11.Plant Determination: 1st- Customer material info records, 2nd Customer Master, 3rd Material master. 12.requirement type determination: item category +MRP type 13. Business Area determination: Plant/Valuation area or sales area or Item division+Plant 14.Output determination: Output determination at sales doc level, delivery level, billing level 15.Warehouse determination: Warehouse number+plant+storage location 16.Availability check determination: Customer requested delivery date 17.Tax Determination:Destination country of ship to party+Departure country of Shipping point+Tax classification for customer from customer master+Tax classification of material master 18.Batch Determination: Define condition table,Batch Determnation access sequence,Batch Strategy type,Batch search procedure,Batch search Procedure activation. Prerequisite for batch Determination process in MM: 1.Material must be Batch Managed (Purchasing view) 2.The Material should be classified with class 3.Batch level has to be set:Client/plant/Material level

ABAP :

SE11: Create table SE38: ABAP Editor SE37: Function builder SE91: Create Message SE93: Create T code SE80: Functional group SM30: Maintain table. SE41: PF status SE71:SAP Script SE24: Class/Change display

IDOC: Transfer data from sap to non sap, sap to sap and non sap to sap. Outbound IDOC: 1.Port create: SALE- Basic settings-Define Logical sys(T.code BD54)- create logical sys(SS800-Logical systems 800)& (SS810-Logical sys810) and assign logical systems(Assign to 800 & 810) 2.RFC Destination:SM59-ABAP connection-create-Technical setting & loon security , click-remote logon &connection text & save.-SSSS 3Create port-We21:Transactional RFC-create and enter(port no.A000000055) 4.BD64-DIstibution model-click on change-select Distribution model-create model view & save-add message type(sender-SS800 & Receiver-SS810-Message-DEBMAS- you can see below row in Distribution model, you can expend tree structure)-SSSS 5.partner profile:WE20: select partner type LS- click on create-SS810& save-go to outbound parameter and enter message,port , basic type etc.

Inbound IDOC: 1.Go to 810 client,.WE20-partner profile- select partner type LS- click on create-SS800& save-go to Inbound parameter and enter message type DEBMAS,Process code-DEBM 2.Go to 810 client,.WE42-Inbound process code-T codes-information purpose BD10: Send material BD11: Get Material BD12: Send Customer BD13:Get customer BD14:Sned vendor

BD15: Get Vendor BD16: Send cost center BD17:Get cost center BD87: Reprocess IDOC

3.Go to 800 client,BD12-To Transfer customer master data-customer no.195 WE42: 4.Go to 800 client,WE05-you can check IDOC status 5. Client 800,Se38: Do you have any error in IDOC, you can check here:SE38-BD74 We can reprocess error IDOC (status51) using program RBDAGAIN,BD87 Then process code, inbound process code is we42. Where can you solve IDOC issue: BD64 BAPI: Business Application program interfaces: Transfer data from SAP to SAP, SAP to non sap, non SAP to SAP. SE37. 1.Crate BAPI structure: SE11 2.

LSMW: upload data from only legacy system to SAP system, not possible to sap to sap, sap to non sap LSMW: Legacy system Migration Workbench: T.code: LSMW 1.To create project name:Project name:ZSSSS & execute 2.Go to click on recording-VA01 etc-enter-click on default all & save Process step: click on execute: 2.Maintain object attribute:Batch input recording click(VA01 will save) 3.Maintain source structure: click & change- create & save 4.Manintain Source field: enter fields and save 5.Maintain structure relation: change & save 6.Maintain Field mapping & conversion rule:select fields name & assign one by one 7.Maintain field value and transaction:

8.Specify file: click on Legacy and assign file and save 9.Assign file:click on assign file & save 10.

ABAP: SE01-Correction & Transport req SE09-Workbench organizer SE10-Customizing organizer How to change package name of an object:SE38,SE11- Go to from menu-Object dictionary entrydisplay and change icon-package no-create the TR by pressing create request-click yes.

GST Configuration: 1.Assign Tax Procedure to country: OBBQ 2.Define Tax Access sequence: OBQ2 3.Define condition types(Tax):OBYZ(CGST,UGST,SGST,IGST) 4.Create Account Keys:OBCN 5.Define Tax Procedure:OBQ3 6.Assign GL to account keys & GL:OB40 7.Create Tax codes in country IN:FTXP 8.Maintain Tax codes for excise duties using condition technique:SM30 table:J_1ICONDTAX 9.Maintain Tax condition Records:FV11 Tax ID G2 cannot be checked(there are Several/no tax records) Message no.VK242. This is because we did not maintain any Tax percent Rate in FTXP.This will not affect tax determination in PO.

Tax conditions for USA:UTX1,UTX2,UTX3

Business Process: SAP SD :

Customer Groups: Domestic Customer, Export Customer,Modern Trade,

GSK Pharmaceuticals: GlaxoSmithKline plc (GSK) is a British multinational pharmaceutical company headquartered in Brentford, London.[3] Established in 2000 by a merger of Glaxo Wellcome and SmithKline Beecham, GSK was the world's seventh largest pharmaceutical company as of 2015, after Johnson & Johnson, Pfizer, Novartis, Merck, Hoffmann-La Roche and Sanofi.[n 1][4]

Pharmaceuticals[edit] GSK manufactures products for major disease areas such as asthma, cancer, infections, diabetes and mental health. Its biggest-selling products in 2013 were Advair, Avodart, Flovent, Augmentin, Lovaza, and Lamictal; its drugs and vaccines earned £21.3 billion that year. Other top-selling products include its asthma/COPD inhalers Advair, Ventolin, and Flovent; its diphtheria/tetanus/pertussis vaccine Infanrix and its hepatitis B vaccine; the epilepsy drug Lamictal, and the antibacterial Augmentin.[7]:220 Medicines historically discovered or developed at GSK and its legacy companies and now sold as generics include amoxicillin[73] and amoxicillin-clavulanate,[74] ticarcillinclavulanate,[75] mupirocin,[76] and ceftazidime[77] for bacterial infections, zidovudine for HIV infection, valacyclovir for herpes virus infections, albendazole for parasitic infections, sumatriptan for migraine, lamotrigine for epilepsy, bupropion and paroxetine for major depressive disorder, cimetidine and ranitidine for gastroesophageal reflux disorder, mercaptopurine[78] and thioguanine[79] for the treatment of leukemia, allopurinol for gout,[80] pyrimethamine for malaria,[81] and the antibacterial trimethoprim.[79] Among these, albendazole, amoxicillin, amoxicillin-clavulanate, allopurinol, mercaptopurine, mupirocin, pyrimethamine, ranitidine, thioguanine, trimethoprim and zidovudine are listed on the World Health Organization's list of essential medications.[82]

Malaria vaccine[edit] In 2014, GSK applied for regulatory approval for the first malaria vaccine.[83] Malaria is responsible for over 650,000 deaths annually, mainly in Africa.[84] Known as RTS,S, the vaccine was developed as a joint project with the PATH vaccines initiative and the Bill and Melinda Gates Foundation. The company has committed to making the vaccine available in developing countries for five percent above the cost of production.[9] As of 2013 RTS,S, which uses GSK's proprietary AS01 adjuvant, was being examined in a Phase 3 trial in eight African countries. PATH reported that "[i]n the 12-month period following vaccination, RTS,S conferred approximately 50% protection from clinical Plasmodium falciparum disease in children aged 5-17 months, and approximately 30% protection in children aged 6-12 weeks when administered in conjunction with Expanded Program for Immunization (EPI) vaccines."[85] In 2014, Glaxo said it had spent more than $350 million and expected to spend an additional $260 million before seeking regulatory approval.[86][87] A second generation malaria vaccine is being evaluated in Phase 2 clinical trials.[88]

Consumer healthcare[edit] GSK's consumer healthcare division, which earned £5.2 billion in 2013, sells oral healthcare, including Aquafresh, Maclean's and Sensodyne toothpastes; and drinks such as Horlicks, Boost and a chocolate-flavoured malt drink sold in India. GSK also previously owned

the Lucozade and Ribena brands of soft drinks, but they were sold in 2013 to Suntory for £1.35bn.[55] Other products include Abreva to treat cold sores; Night Nurse, a cold remedy; Breathe Right nasal strips; and Nicoderm and Nicorette nicotine replacements.[89] In March 2014 it recalled Alli, an over-the-counter weight-loss drug, in the United States and Puerto Rico because of possible tampering, following customer complaints.[90]