Professional Documents
Culture Documents
Resource Planning
Man HR
Material MM
Machine Engineering
Money Finance
Method Planning
PC1 PC1
PC1 PC1 PC1
1 1
1 1 1
Client
s server
Application Application Application
layer layer layer
Is SAP a programming language: that runs in the SAP ABAP runtime environment, created and used
by SAP for the development of Application programs including Reports.
Package is a development object that stores the object such as menus, screens, functional modules,
transactions etc.
Purpose
This wiki page will discuss about SAP tables and structures used in SAP Sales and Distribution. This can be used a
ready reference for writing FS or for data analysis.
Sales Document
Table/Structur Description
e
VBPA Partners
VBEP Sales Document: Schedule Line / Data related to line items, delivery lines
VMVA Matchcodes
Logical Database
AK V Sales documents
Delivery Document
Table/Structure Description
Shipping
Table/Structur Description
e
Billing Document
Table/Structur Description
e
Material Master
Table/Structur Description
e
MVKE Sales data - for each sales organization and distribution channel
MCHA Batches
Pricing
Table/Structur Description
e
KOND Contracts
Output
Table/Structur Description
e
Text
Table/Structur Description
e
Others
Table/Structur Description
e
JSTO PP status
SADR Address
TCOD
E Description Functional Area
1 SE54 Generate table view BC - Table Maintenance Tool
2 SE11 ABAP Dictionary Maintenance BC - Dictionary Maintenance
3 SM30 Call view Maintenance BC - Table Maintenance Tool
4 SE16 Data Browser BC - Workbench Utilities
5 SE55 Internal table view maintenance BC - Table Maintenance Tool
call
6 SE56 table view display DDIC call BC - Table Maintenance Tool
7 SE57 Internal table view deletion call BC - Table Maintenance Tool
8 SE38 ABAP Editor BC - ABAP Editor
9 SE80 Object Navigator BC - Repository Browser
10 SE37 ABAP Function Modules BC - Function Builder
11 SE93 Maintain Transaction Codes BC - Workbench Tools: Editors, Painters,
12 VA01 Create Sales Order SD - Sales
13 ST22 ABAP Dump Analysis BC - Syntax, Compiler, Runtime
14 RSA3 Extractor Checker BC - BW Service API
15 SU01 User Maintenance BC - User and Authorization Managemen
16 SLIS FI-SL Spec.Purpose Ledg. FI - Information System
Info.System
17 ST05 Performance Trace BC - Performance Analysis (Transaction S
18 SE14 Utilities for Dictionary tables BC - Activation Program, Conversion Pro
MC, SPDD
19 SE16N General table Display CO - Controlling
20 SE51 Screen Painter BC - Screen Painter
21 SM31 Call view Maintenance Like SM30 BC - Table Maintenance Tool
22 MIGO Goods Movement MM - Inventory Management
23 MIRO Enter Incoming Invoice MM - Invoice Verification
24 CATS CATS: Cross-Application Time CA - Time Sheet
25 PFCG Role Maintenance BC - ABAP Authorization and Role Manag
TCOD
E Description Functional Area
26
2 VARA Archiving
13 OVFV C SD Tab.TVPR
4 VKM4 SD Documents
5 VKM5 Deliveries
2 VARA Archiving
5 VARA Archiving
12 VKM4 SD Documents
View the full list of SAP SD Electronic Data Interchange TCodes (SD-EDI)
Basic Data TCodes (SD-CAS-BD)
S.No Tcode Description
1 DL10 Download
View the full list of SAP SD Pricing and Conditions TCodes (SD-BF-PR)
Additional Material Functions TCodes (SD-MD-MM-CS)
S.No Tcode Description
View the full list of SAP SD Additional Material Functions TCodes (SD-MD-MM-CS)
POS Interface - Outbound TCodes (SD-POS-OUT)
S.No Tcode Description
View the full list of SAP SD POS Interface - Outbound TCodes (SD-POS-OUT)
Word Processing TCodes (SD-BF-TP)
S.No Tcode Description
1 S_EBJ_98000358
View the full list of SAP SD SD API Interface, LORD TCodes (SD-SLS-API)
Customer Scheduling Agreement TCodes (SD-SLS-OA-
SCH)
S.No Tcode Description
Movement types:
1.601-Goods issue
2.602-Reverse issue
3.651-Return order
4.631-Consignment Fill
5.633-Consignment issue
6.634-Consignment Return
7.632-Consignment Pickup
8. 561 - Receipt per initial entry of stock balances into unrestricted use
9.641-Stock transport order two step(Intra company) 671-Cross company
11.643- stock transport order for two step(Inter company) 673- Cross company
15.Goods Transfer-MB1B-453
16.161-Return MIGO
Movement Type: 102 is Reversal of Material Document created with Movement type:
101.
Movement Type: 161 is used when you return goods to vendor against a Purchase
Order for unknown reasons.
Movement Type: 321 is used to Transfer Goods From Quality to UnRestricted Stock.
Movement Type: 322 is used to Transfer Goods From UnRestricted Stock to Quality.
Movement Type: 349 is used to Transfer Goods From Blocked to Quality Stock.
Movement Type: 350 is used to Transfer Goods From Quality Stock to Blocked.
Movement Type: 561 is used for initial entry of stock (e.g., in SAP implementation
project).
Movement Type: 704 is used to do Goods Issue against Physical Inventory in Quality
Inspection.
Integration:
SD-MM-FICO-PP=Material Master
SD-FI=VKOA
SAP FI MM SD PP Integration
Step-1 Generating Purchase Requistion (PP AND MM involved)
Sales Order
Link Points Module Involved in the Link
Availability Check MM
Credit Check FI
Costing CO/MM
Tax Determination FI
Transfer of PP/MM
Requirements
Delivery and Goods Issue -
Integration Points Module
Availability Check MM
Credit Check FI
Reduces stock MM
Requirement PP/MM
Eliminated
Division SD, MM
Sales Order
Taxes SD, FI
Integration Points Module Involved
Delivery
Packing SD, MM
Introduction
A user exit is a place in a software program where a customer can arrange for their own tailor-made program to be
called. In R/3, some user exits use Include statements to include customer program enhancements that are called from
the program. Other user exits use tables that are accessed through customization.
Warning
Documentation below is copied from SPRO activities documentation and SAP library :
Relevant Information
CMOD Customer Exits
Include It is reserved for customers, for which you need a modification key
Routines
Sales Related Exits
Customer Exits
Include Routines
Include Description
MV45AOZ For entering additional installation-specific modules for sales document processing
Z which are called up by the screen and run under PBO (Process Before Output) prior
to output of the screen.
MV45AIZZ For entering additional installation-specific modules for sales document processing.
These are called up by the screen and run under PAI (Process After Input) after data
input (for example, data validation).
MV45AFZZ For entering installation-specific FORM routines and for using user exits, which may
and be required and can be used if necessary.
MV45EFZ1
For more details see Help link above.
Customer Exits
Enhancement Description
code
V05N0001 User Exits for Printing Billing Docs. using POR Procedure
Customer Exits
Enhancement Description
Code
V50R0004 Calculation of Stock for POs for Shipping Due Date List
V02V0003 User exit for gate + matl staging area determination (headr)
Include Routines
Include Description
MV50AFZ The user exits in this include can be used to fill the condition tables for material
K listing and material exclusion (KOMKG and KOMPG) and product selection (KOMKD
and KOMPD) with own data.
MV50AFZL In delivery creation process for sales orders there is the possibility to restrict the delivery
creation to some order items. If these order items are member of a delivery group, but not
all items of this delivery group are includes in the restriction range of the order item nubers,
you can specify in this routine what to do.
MV50AFZP This user exit can be used to modify change mode of pricing screens in delivery processing.
Include Routines
Include Description
MV56AOZ You can include your own modules in this program, to be processed in shipment processing
Z screens during PBO.
MV56AIZZ You can include your own modules in this program, to be processed in shipment processing
screens during PAI.
MV56AFZY You can include your own FORM routines in this program. They can contain your own
adjustments for shipment processsing.
MV56AFZZ This program contains pre-defined FORM routines, in which you can carry out your own
adjustments for transportation processing.
USEREXIT_FIELD_MODIFICATION SAPMV61A MV61AFZ You can use this user exit to adjust
Routine Module Include Description
Pool or
Function
Group
USEREXIT_CHANGE_PRICING_RULE SAPMV61A MV61AFZ You can use this user exit to change
A the pricing type that has been
Routine Module Include Description
Pool or
Function
Group
predefined in the
copying control table in billing.
USEREXIT_XKOMV_ERGAENZEN_MAN SAPLV61A RV61AFZB You can use this user exit to change
U the ready-for-input fields of the
manually entered
condition record in add mode in the
condition screen.
USEREXIT_PRICING_COPY SAPLV61A RV61AFZA You can change the KONV fields for
Routine Module Include Description
Pool or
Function
Group
Note: as of Release 4.6A, the display of the condition screen (screen 6201) has been converted from a full screen to a
subscreen. The full screen is included in the SAPMV61A module pool, the subscreen, however, in program SAPLV69A.
Therefore, instead of MV61AFZA and MV61AFZB, the user exits in LV69AFZZ should be used. For reference, see OSS
note 313569.
EXIT_SAPLV09A_00 You can use this user exit to control whether an address that was entered manually
1 and has already been used in other documents (referenced), should be referenced
again if it changes or whether a new address shold be created (duplicated).
EXIT_SAPLV09A_00 Call up this user exit if a customer has not been maintained in the current sales area.
2
EXIT_SAPLV09A_00 Use this user exit to control the origin of partners in the partner determination procedure
3 (origin X, Y or Z). If X, Y, or Z has been entered in the Origin field, this user exit is automatically
called up during partner determination.
EXIT_SAPLV09A_00 Use this user exit to integrate your own check in a program, that runs before the partner
4 is saved in the document.
For more detailed information, see the program documentation for each ofthe user exits.
LVKMPFZ USER_CREDIT_CHECK1
1
LVKMPFZ USER_CREDIT_CHECK2
2
LVKMPFZ USER_CREDIT_CHECK3
3
User Exit for availability check
User exit Include Description
USEREXIT_AVAIL_CHECK_CREDI MV45AFZF This user exit allows you to determine whether the system
T should or should not
carry out an availability check after a blocked document has
been released or after
a new credit check.
RVKMPUS Using this user exit, you can define new forms of payment guarantee.
2
BILLING_SCHEDULE_DELTA
For milestone billing a percentage value is fully invoiced for each billing deadline. In the case
of deviations between
the original item value and any later changes, you can use the user exit to determine
whether the difference should
be stored in the final invoice or sent to the next deadline.
USEREXIT_MOVE_FIELD_TO_FPLT : This user exit allows you to create your own
fields in table FPLT.
USEREXIT_MOVE_FIELD_TO_FPLA : This user exit allows you to create your own
fields in table FPLA.
USEREXIT_PRICING_PREPARE_TKOMX
This user exit is used to copy or create an additional field in the definitive communication
structure for pricing.
The user exit is also often used to change the duration of a billing plan deadline. You can do
this by overwriting
the following fields:
tkomp-anz_tage (Number of days in a deadline)
tkomp-anz_monate (Number of months in a deadline)
tkomp-anz_jahre(Number of years in a deadline)
tkomp-anz_wochen (Number of weeks in a deadline)
USEREXIT_DATE_PROPOSAL
User exit Include Description
In the standard release deadlines are set according to a template in the billing plan. This grid
entry list sets the deadlines
for each day but you can adjust the template with the user exit so that the grid entry list
could, for example, follow a monthly
pattern instead.
Modification report for billing plan SDFPLA02
This report enables you to update the header data for a billing plan with the result that new
billing plan deadlines are determined
and set in the billing plan.
In this way you can, for example, set the goods issue date as the starting date for the billing
plan.
Additions to billing plan with transaction SMOD
User exit SDVAX001
In the standard release the billing plan type is determined from the item category of the
sales document and set in the billing plan.
You can also use the user exit to determine the billing plan type dependent on data from the
order header, order item, etc.
User exit V60F0001
This user exit is for changing the deviating billing date (FPLT-AFDAT).
RV60FUS5 This userexit can be used to split date lines TKOMK for Header fields
USEREXIT_PLANT_SELECTION RV03VFZZ The user exits named here are planned for projects that are to
be carried out in agreement
with SAP development as they may only be used in
consultation with SAP. SAP provides no
guarantee if they are used without our advice in program is
an exception to this rule
USEREXIT_ADD_FIELD_TO_HEADE FV45VFZZ
R
USEREXIT_ADD_FIELD_TO_LINE
USEREXIT_DELIVERY_GROUPS FV45VFZY
USEREXIT_MVERF_INIT
USEREXIT_QUOTA_KEY_VALUE
USEREXIT_AVAILABILITY_IN RV03VFZZ This user exit is used to adjust the flow during plant transfer.
USEREXIT_AVAILABILITY_OUT A list of permitted plants, where
USEREXIT_DARA_REFRESH this material is created, is determined and checked in the
USEREXIT_PLANT_SELECTION standard R/3 delivery. A dialog box
appears where you can select the plants. The user exits allow
you to modify the plant table
so that plant selection takes place in advance for every
flagged selection and a dialog box
becomes unnecessary.
USEREXIT_CHECK_VBLB- MV45AFZC These user exits are available for checking customer reserve fields
USR01 from VBLB-USR01 to
USEREXIT_CHECK_VBLB- VBLB-USR05. The reserve fields are used in the component
USR02 supplier industry. The system
USEREXIT_CHECK_VBLB- calls them in the screen flow logic for header data in forecast and
USR03 JIT delivery schedules
USEREXIT_CHECK_VBLB-
USR04
USEREXIT_CHECK_VBLB-
USR05
Function module V450001 is available as an SAP extension for the component supplier industry. It contains the
following user exits:
EXIT_SAPLVED4_004 General - You can use this user exit to overwrite the standard method with which the
system determines the recipient of messages (either at sales document level or in the
customer master record). You can define a special recipient for an incoming document that
has just been processed.
EXIT_SAPLV45L_001 For delivery schedules - The system checks an incoming delivery schedule against the
current/old delivery schedule to determine if there are any differences.
EXIT_SAPLVED4_004 General - You can use this user exit to overwrite the standard method with which the
system determines the recipient of messages (either at sales document level or in the
customer master record). You can define a special recipient for an incoming document that
has just been processed.
EXIT_SAPLV45L_002 For delivery schedules - With this user exit, you can change the VBLB structure (sales
document: delivery schedule data), before the system copies delivery schedule data to the
corresponding internal table.
EXIT_SAPMV45L_001 Planned delivery schedules - This user exit allows you to process schedule lines generated
automatically in a planning delivery schedule..
EXIT_SAPMV45L_002 Planned delivery schedules - This user exit allows you to modify the calendar used in a
delivery schedule split.
EXIT_SAPMV45A_005 For delivery orders (MAIS) - This user exit enables you to control how the system copies
packing proposals into the outbound delivery order.
EXIT_SAPLVED4_001 For delivery orders (MAIS) - These user exits allow you to change the workflow
EXIT_SAPLVED4_002 parameters for processing inbound EDI messages.
EXIT_SAPLVED4_003
EXIT_SAPLVED4_005
EXIT_SAPLVED4_006
EXIT_SAPLVED4_001 For the self-billing procedure - You can use these user exits for the standard self-billing
EXIT_SAPLVED4_005 procedure.
EXIT_SAPLVED4_006
EXIT_SAPLVED5_002 For the self-billing procedure -You can use these user exits for the self-billing procedure
EXIT_SAPLVED5_003 with invoice creation.
EXIT_SAPLVED5_004
RV45HFZZ enhancement
USEREXIT_INV_REQ_ITEM
USEREXIT_INV_REQ_ITEM_PARTNER
You can use the following user exits for resource-related billing as of Release 4.5A:
V46H0001 enhancement
EXIT_SAPLV46H_001
EXIT_SAPLV46H_002User Exits For Billing
In this user exit additional fields for account determination that are not provided in the standard system are copied into
communication structure KOMKCV (header fields).
In this user exit additional fields for account determination that are not provided in the standard system are copied into
communication structure KOMPCV (item fields).
Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy).
USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
This user exit is only called when the billing document is created. It is used to provide the header and the item of the
new billing document with deviating or additional data.
USEREXIT_NEWROLE_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAP_AVBPAK
The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):
EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item
(such as quantity specifications) with this exit.
EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account
determination
You can use this exit to change inbound parameters in order to influence account determination. User Exits For
General Billing Interface
With this user exit for the general billing interface, deviating address data for different partner functions can be copied
from the interface.
With this user exit for the general billing interface, new partner functions can be copied from the interface.
With this user exit for the general billing interface, a key field can be added in the aggregrated flow.
Special user exit for the general billing interface with which a key field can be added in the aggregrated flow.
User Exits For Sales Support
In Sales Support, you can use the following SAP enhancements:
MCV2001 - Expand LIS fields for sales activities/sales promotions. This enhancement contains the following
user exit:
EXIT_SAPLMCV2_001
V43MLIS - Expand LIS fields for address lists. This enhancement contains the following user exit:
EXIT_SAPLV43M_007
V43K0001 - Enhancement for linking to calendar. This enhancement contains the following user exit:
EXIT_SAPLV43K_001
V43ADATA - Change sales activity data in dialog. This enhancement contains the following user exit:
EXIT_SAPMV43A_007
RVKPRFZ2 This allows the sort sequence for the first issue of the list to be defined.
There are two additional user exits for listing sales documents, which influence the way in which the communication
structure is filled. These user exits do not affect the structure of the list but the way in which the data is transferred and
how the new additional fields are filled.
CUSTOMER_FILL_1
CUSTOMER_FILL_2
sd
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:
Controlling:
Logistic General:
SD:
Material Management:
Logistics Execution:
2.Financial account-Financial account global setting-fiscal year-assign fiscal year to company code
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)
Material Master:MM01/MM02/MM03
MRP1: MRP type, MRP Controller, MRP group, Lot size, Max lot size
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
Pricing:
Condition record:VK11
Condition table:V/3, to save as package and workbench request
Condition type:V/06
Exclusion group:
Condition supplement:
Condition scale:
Pricing scale:
Minimum order:
Group condition:
Basic Functions:
1.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.
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
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()
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.
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:
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:
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
7.Assign GL A/C: Application(VC) condition type(CASH) chart of accounts() sales org() GL A/c()
4.Delivery Scheduling:
It is the process of determining Delivery dates and confirmed quantities into sales document.
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”.
.Define scheduling by shipping point: Maintain Pickpack and Loading time here
.Maintain Duration
4.Route determination:
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)
Allocate sales document Header: V/43: sale doc type(OR) and output procedure()
NAST=Output table
7.Text Determination:
IMG-SD-sales-sales documents-Maintain copy control for sales documents: Header, item & schedule
line
9.Incompletion Log:
IMG-SD-Basic functions-Log of incompletion items-define status group: OVA0: Which function will
carried out incompletion procedure in SD.
B-Sales Item
D-Partner
F-Sales Activity
G-Delivery Header
H-Delivery Item
Assign Procedure to Sales Header,sales Item, Sales schedule line, Delivery Header & item etc.
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.
11.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
Assign procedure to sales doc type: OV14: sales doc type(OR) and Procedure(A00001)
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)
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.
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.
You can enter list of materials and save. Go to VA01 and check.
XD02: check item proposal check box in customer master sales area section
Material(XXXX) Description
Logistics-SD_Master data-products-Listing/Exclusion:VB01
Cross selling: It is the process of selling additional products along with main products.
Customer Material Info Records: VD51: customer place the order with own material code, we can
create CMIR.
Every company has Credit Management Department, this credit Department will manage the credit
limits of the customers.
b. Monitoring the day to day transactions and any of the customer credit limits exceeds then they
block the next transaction.
Update group:12,15 & 18, Update group controls, which sales documents updated in credit
Management.
V/08: In pricing procedure,put net value of subtotal value is A, pricing will connected with credit
Management.
Define Groups:
Define automatic credit control: OVA8: Credit control area+risk category+credit group
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 %.
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 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.
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.
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.
It is the process of checking the stock availability of the material while creating sales order.
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.
4. Item category.
1.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
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 1 st 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.
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)
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
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.
Pricing:
Condition table will be placed in access sequence from most specific to most general.
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.
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.
Condition type: V/06, It control the type of the pricing components, i.e whether it is a base price
or discount or surcharge.
Discount (K004):500
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.
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.
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.
Cross client: The configuration and customization we do in one client will automatically update in
other clients within a server.
b. Define Access sequence: In access sequence we place the condition tables from
most specific to most general. Access sequence configuration is also cross client.
c. Define condition type:V/06
d. Define pricing procedure: V/08, these are 16 steps
e. Assign pricing procedure or pricing procedure determination: OVKK.
Sales are+customer pricing procedure+document pricing procedure+pricing
procedure+ condition type.
K005-Customer/Material discount
K007-Customer discount
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.
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.
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.
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:
Intercompany condition type: PI01 is intercompany price (amount) condition types determine in
intercompany sales order.
Exclusion Group: Grouping of multiple condition type into one and allow the system to propose best
discount or the least discount.
Configuration:
D-Exclusive
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 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”
The client requirement is any order if the total document value reaches 1000000 then they want to
propose 20000 discount.
Step3: Define condition type: calculation type(B), check group condition, Maintain group condition
routine(1), scale basis(B) Value scale –save it.
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
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.
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
Configuration eror:SCAT
FBL5N
F-28
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.
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.
1. Stock update
5. It update in LIS
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.
4. It update LIS
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 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.
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.
The goods are totally damage in customer place and which are not in a position to take back.
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.
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
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
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
f. Stcok will be reduced from consignment stock and inventory A/C will generate.
g. 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.
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
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.
Scenarios:
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.
Item category(5): Item category 5 control that even we do MIGO in 3 rd party with shipping
notification system will treated as dummy MIGO and stock will not be update.
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 3 rd party.
Billing quantity E and it will help to copy the quantity from MIRO to invoice while creating invoice to
customer in 3rd party.
In VF01,reference quantity will copy from order, but actual quantity will copy from MIRO.
T.code: Table:SE16N.
Item category group TASG,copy control RE-RE, copy requirement as (28) VBRK/VBRP:002
23.IPO: XD01>MM01>VA01>XK01>ME21N>MIGO>MIRO>VLO1N>VF01
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
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
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:
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.
Process 1: ME21N
4.VF01:Billing type F8
5.MIGO:
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.
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.
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.
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.
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.
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.
Answer:
Performa Invoice:
Normal invoice: Which is issued by the sellers to the buyer to request payment of goods
delivered.
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.
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.
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.
Indirect Tax: VAT , those paid by consumers when they buy goods and services.GST,sales Tax,Service
Tax,Custom Duty, Excise Duty.
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
11.Plant Determination: 1st- Customer material info records, 2nd Customer Master, 3rd Material
master.
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
ABAP :
SE41: PF status
SE71:SAP Script
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)
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
BD13:Get customer
BD14:Sned vendor
WE42:
5. Client 800,Se38: Do you have any error in IDOC, you can check here:SE38-BD74
BAPI: Business Application program interfaces: Transfer data from SAP to SAP, SAP to non sap, non
SAP. SE37.
2.
LSMW: upload data from only legacy system to SAP system, not possible to sap to sap, sap to non
sap
Master Data:
Customer Master: You can view customer list through transaction code VC/1.
Material Master:MM60
T.code: LSMW
6.Maintain Field mapping & conversion rule:select fields name & assign one by one
10.
ABAP:
SE09-Workbench organizer
SE10-Customizing organizer
GST Configuration:
8.Maintain Tax codes for excise duties using condition technique:SM30 table:J_1ICONDTAX
Message no.VK242.
This is because we did not maintain any Tax percent Rate in FTXP.This will not affect tax
determination in PO.
Copy Control: VOFM: Copy controls are used when we are creating a document with reference to
another document.
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.
IN-QT,QT-OR,RE-SDF,OR-RE,QC-OR,WK1-OR,WK2-OR
OR-LF,RE-LR,CF-LF,CI-LF,CP-LR,COND-LR,DL-LO,FD-LF,RO-LF,CS-BV,DS-LF,SDF-LF
CS-BV,RE-RE,CR-G2,DR-L2,OR-F2,OR-F5
Delivery to Invoice:VTFL
LF-F2,LF-F8,LO-F8
F2-RE,F2-CR,F2-RK
Invoice to Invoice:VTFF
F2-S1
21-Billing Header
303-Always an Item
501-Scheduled quantity
() copy item
() complete reference
2.VTLA:
3.VTFA:
Header:
002-Item/order related
003-Header/Delivery related
005-cancellation Header
006-Cancellation item
Reference number()
A-Purchase order
C-Delivery number
Assignment number()
Same as above.
() Copy item number: System indicate copy the item number from source doc to target doc
Item:
Data VBRK/VBRP(001):
001-Invoice split
003-Single invoice
005-Intercompany billing
Billing Quantity(F):
C-Order quantity
D-Delivery quantity
Pricing type():
Business Process:
SAP SD :
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] ticarcillin-clavulanate,[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]