SAP SD Notes

Processing status for SAP-SD :

1) Create organizational structure.
2) Create the customer master & the material master.
3) Create the condition records.
4) Create the sales order.
5) Create the delivery document.
6) Create the billing document.

While creating the organizational model following activities are performed on the system:

 Define the company (RCOMP)
 Define company code (BUKRS)
 Define the sales area (TVTA) : 1) Define the sales organisation (VKORG),
2) Define distribution channel (VTWEG),
3) Define division (SPART).
 Define plant (WERKS)
 Define Shipping point (VSTEL)
 Maintain sales office (VKBUR) & sales group (VKGRP).
 Define storage location (LGORT) under MM
 Define credit control area
 Define purchase organisation.
 Assign company code to company.
 Assign company code to sales organisation.
 Assign dchl to sales organisation
 Assign div to sales org
 Set up sales area.
 Set up sales line.
 Assign credit control area to company code.
 Assign purchase organisation to company code.
 Assign plant to company code.
 Assign shipping point to the plant.

Go to EC01 and check the organisational structure. Copy the data from company code 1000 to our
company code at trx EC01.

 Go to VKOA and define the GL a/c for our sales organisation.
 Go to OVKK to define the pricing procedures to the company code.
 Go to trx OBY6 to define the global data parameters for the company code.
 Go to trx OMWW to set the material management wizard.
 Go to OKKP to define the control indicators parameter.
 Go to OVL2 to define the shipping point determination for the plant.
 Go to the physical inventory management through the material management tab, to define the
plant parameters via path.
 Assign sales area to sales document types
 Combine dchls & combine div.

Create PDF files without this message by purchasing novaPDF printer (http://www.novapdf.com)

 Assign reference dchl.
 Assign reference division.
 Go to VOV4 & define item category determination.
 Go to OMWD trx & define the valuation code.
 Go to MB1C, movement type 561 & maintain the stock in the storage locations of plant.

 Go to OBD2 & define the customer a/c groups as Sp, Sh, Bp &, Py.
 Go to XDN1 & define the no. ranges to customer a/c group.
 Go to OBAR & assign no. ranges to customer a/c groups.

While defining the customer a/c groups, define the output determination procedure & one time
account holder.

The fields have 4 options: 1) Required,

2) Suppress,

3) Optional,

4) Display.

Customer master is made up of 3 structures or the structural components of customer master involves:

(a) General data section (KNA1)
(b) Company code data section (KNB1)
(c) Sales area data section (KNVV)

Sales Shipping Billing Partner Functions

Whether the customer no. needs to be assigned internally or externally that will be determined by the
external indicator in XDN1, while defining the number ranges for a/c groups.

MM (Material master) settings:

 Go to financial a/c ing & global data section & define open & close posting periods, open &
close posting period variants.
 Assign posting period variant to company code


 Assign chart of a/c to company code.
 Define & assign fiscal year variant to company code
 Go to MMPV & maintain the posting periods for the company code.
 Go to OMSY & maintain the company codes for material management.
 Go to OMS2 & maintain quantity/value update for material types in company codes.
 Go to the basic functions under sales & distribution & define & assign partner procedure
determination to our company code for customer master & sales document header as well.
 Go to V/08 & define pricing procedure for our company.
 Go to MM01 & choose industry sector & material type for creating material & then select
views:

(a) Basic Data 1
(b) Basic Data 2
(c) Sales: sales organisation data1
(d) Sales: sales organisation data2
(e) Sales: General/plant data
(f) General plant data/storage 1
(g) General plant data/storage 2
(h) Accounting 1.

& select the organisational levels & create the material.

 Go to XD01 & select the a/c group & maintain organisational data so as to create the
customer centrally in the system with company code data.
 Create pricing condition records for the material with the defined condition types in the
pricing procedure.
 Go to a/c payables & receivables under the basic functions tab of Sales & Distribution & go
to the revenue a/c determination & define a/c assignment group for customer master &
material master & assign it into the customer master & material master.
 Define Route determination procedure.

(Define the agent by the T code V-11, create service agent)
 Create CMIR.
 Define revenue a/c determination procedure.
 Define or perform TOR & availability check functions for the material under plant.
 Define the credit management for the company code.
 Then go to VA01 & raise the sales order for a line item with specific to a particular customer
with proper order reasons.

Note: Define sales districts for the customer under the customer master.

 Go to define output determination procedure.
 Go to VL01N & generate the delivery document. Click upon the picking items & do the PGI.
 Move to VF01 & generate/save the document so as to create the billing document.


 Define material determination Procedure.
 Maintain text determination procedure.
 Create BOM under CS01 : ERLA at main item level & LUMF at component level to which
subcomponents could be added for assembly. And assign the subcomponents to it’s main
item/product at CS01 with the required quantity.
 Define incompleteness procedure.*: Remember that it is not necessary to maintain the correct
input value in the fields but what is mandatory is only this that a value needs to be maintained
in the aforesaid field.
 Item proposal & dynamic product proposal : Item proposal needs to be defined under the trx.
code VA51, & needs to be submitted after creation to it’s respective customer at the customer
master under sales area data field whereas, in dynamic product proposal the customisation is
done in such a way that the moment the sp is defined at the sales order header, system itself
proposes the items of the customer’s interest dynamically.
 Cross selling : It is done for the purpose of the selling regarding the supplementary material
or the accessories with the main item.
 Material listing/Exclusion.
 Free goods determination : It is done to promote/encourage slow moving goods as well as a
market test for new launched product or may be a promotional campaign for the existing
product. There are two types of free goods promotion i.e. exclusive & inclusive where in case
of exclusive free goods the free good is customised in the form of 10+1 i.e. one good is free
with 10 goods & this may be the same material of the remaining 10 goods or may be a
different good other than the rest of the 10 items. Whereas in case of inclusive condition the
free goods are issued as 9+1 when it’s an order for 10 goods i.e. 1 item will be provided free
among the 10 goods & the price for that 1 good will be deducted out from the 10 items. The
calculation formula for free goods is being done under prorate & unit reference schemes or
methods.
 Copy Controls
 Outline agreements: (a) Scheduling Agreements.
(b) Contracts.

Customer complaints:

1. Credit memo request & customer compensation.
2. Debit memo request & business compensation.
3. Returns & customer compensations.
4. Invoice correction request/process (RK) : Here for every line item two rows are going to be
created, one for the credit & another for the debit, whereas the credit field is going to be disabled
& the debit record is going to be maintained in the procedure of assigning only the goods that
were issued/utilised by the customer i.e. for 10 goods of the line item if 2 were returned back then
the correction is made for the issue of 8 items showing 2 as debit items & the customer is going to
be billed for the 8 items unlike the credit memo request where for the two items one credit memo
is going to be issued or a subsequent free of charge delivery is being made for those two items.
But after the specification being made for those 8 items system itself generates the credit memo


for the remaining items. So here at RK user has to specify the qty. Being utilised by the customer
out of the qty. Being sold to him.

 Consignment: KB/CF, KE/CI, KR/CR, KA/CP.

VOV8:

Quantity contract Value contract Service contract Master contract

Sales doc. type KM WK1 WV GK
Sales doc. catgry G G 0
Scr. seq. grp. LP WK VT GK
Transacn. grp. 4 4 4 4
Doc. pric. proc. A Y V V
Pric.proc cond.head. PABR01
Pric.proc.cond.item PABR02
Contract profile 0001 001
Group ref. proc. ZSDK
No delivery Order rel. bilng
No billing Type F2

Inquiry Quotation

Sales doc. type AF AG
Sales doc. category A B
Probability 30% 70%
Scr. seq. grp. AG AG
F.code for overvw. scr. UER2 UER2
Transaction grp. 1 2
Doc. pric. proc. A A

Credit memo req. Debit memo req. Invoice correction req.

Sales doc. type G2 L2 RK
Sales doc. category K L K
Scr. seq. grp. GA GA GA
Transacn. grp. 0 0 0
Doc. pric.proc. A A A
Delv. type NIL NIL
Order rel.bilng.type G2 L2 G2


Billing block 08 09 08
Reference mandatory-M

Returns Consignment return Subsequent fr of delv.

Sales doc. type RE KR KL
Sales doc. catg. H H I
Scr.seq.grp. RE RE RE
Trans. grp. 0 0
Doc.pric.proc. A A C
Delv.type LR LR LF
Delv.rel.bilng.type RE
Order rel.bilng.type RE RE
Billing block 08 08

Consign.fillup Consign.issue Consign.pick up

Sales doc.type KB KE KA
Sales doc.categry C C C
Doc.pric.proc. A A A
Delv.relv.bilng.type F2
Ordr.relv.bilng.type F2
Delv.type LF LF LR

Returnable packaging Returnable Packaging

Sales doc. type LA LN
Sales doc. category C C
Doc.pric.proc. A A
Delv. type LR LF
Delv. rel.bling.type. = F2

VOV6:

Schd.ln. DN E0 C1 D0 F1 CB F3 C3 CS
categ. (returns) (consign. (indv. (Returnable (Returnable (IIIrd
return) Purchase packaging) packaging) party
order) sales
order)
Movmnt. 651 631 633 634 632 601 622 623
type No
Item rel. delv.,


for delv.  √ √ √ √ √ √ √ No
Availability √ √ √ √ √ ATP
Check

ASAP Methodology

 Phase 1: Project preparation
 Phase 2: Business blue print
 Phase 3: Realization in ASAP
 Phase 4: Finalization
 Phase 5: Go live & support.

Phase 1: Project preparation:

1) Project charter is issued.
2) Implementation strategy is outlined.
3) The project team as well as its working environment are established.

Enterprise area scope document helps as the primary source of drawing the rough graph of the project.

Phase 2: Business blue print:

1) Project team training
2) Developing the system environment.
3) Defining the organisational structure.
4) Completing the business blue print.

Phase 3: Realization in ASAP:

1) Configure the R/3 system

Baseline Final configuration.

Configuration

Activities: 1) Uploading the BPML scope to R/3

2) Customising R/3 with the IMG.


3) Configuring R/3 with the IMG.
4) Customizing functionality.
5) Customizing wizards.
6) Quality checks in the realization phase.

Phase 4: Final preparation:

1) Testing
2) End user training
3) System mgmnt.
4) Cut over activities.

Phase 5: Go live & support:

1) Production support facilities are defined.
2) Validation of business processes & their configuration.
3) Follow up training for users
4) Sign offs etc.

 Oss
 Remote consulting
 Early watch

System & release upgrade Implementing a new release

Continuous change Upgrade Upgrade Delta

roadmap roadmap customizing customizing

Rollout Project in ASAP : Roll out means the inauguration or initial exhibition of a new product.

As per SAP specific definition, rollout is the strategy for international SAP
implementation. Rollout strategy normally includes the following :

 Whether to implement SAP simultaneously (also known as big bang) in all the countries, or
 Go live in sequence of phased manner, or


 To go for the combination of both (phased manner implementation for some of the countries
and big bang for the others).

Rollout strategy is the most important decision that a client can make during SAP implementation.
Normally, steering committee decides the rollout strategy.

Configuration Tables:

1) VOV8:

T184 Sales document: item category determination (VOV4)

TVAKZ Sales document: allowed order types per sales org (OVAZ)

TVASP Sales document: blocking reasons (XD02)

TVCPA Sales document: copying controls (VTAA, VTLA, VTFA, VTFL, VTAF,
VTFF)

TVCPF Billing: Copying control (VTFA & VTAF)

TVCPL Deliveries: Copying control (VTLA)

TVAK Sales document types (VOV8)

2) VOV7:

TVAPT Sales document item categories item text

TVCPA Copying controls sales document

TVCPF Copying control billing documents

TVCPL Copy control delivery documents

TVEPZ Sales document: Schedule line category determination (VOV5)

TVLP Deliveries: item categories (OVLP)

TVPT Sales documents: item categories (VOVT)


3) Schedule line categories (VOV6):

TVCPA Copying control sales documents

Intercompany sales / Cross company sales:

1) Create intercompany customer in customer master of one sales area for another sales area &
assign it to that other sales area by going to :
IMG→S & D → Billing → Inter company billing → Define inter company number by sales
organisation.

2) Set up sales line with that other sales area, under enterprise structure.
3) Create transfer order (LT03)

Condition type will be PL01 as a cost price.

3rd party sales order:

TA + BANS + NIL + NIL = TAS

Individual purchase order: IN→ QT → OR → MIGO → LF → F2

TA + BANC + NIL + NIL = TAB

Item category for make to order is TAK.

LSMW:

There are 14 steps for LSMW & they are as follows:

1) Maintain object attributes.
2) Maintain source structures.
3) Maintain source fields.
4) Maintain structure relations.
5) Maintain field mapping & conversion rules.
6) Maintain fixed values, translations, user defined routines.
7) Specify files.
8) Assign files.
9) Read data.
10) Display read data.
11) Convert data.
12) Display converted data.
13) Create batch input session.
14) Run batch input session.


Basic Functions :

Condition technique based topics without condition technique based topics

1) Pricing 1) Partner determination
2) A/c determination 2) Route determination
3) Output determination 3) Incompletion log
4) Material determination 4) Credit management
5) Free goods 5) Availability check
6) Listing/Exclusion
7) Cross selling
8) Dynamic product proposal
9) Text determination procedure
10) Tax determination procedure
11) Rebate
12) Variant configuration
13) Batch management

Consignment Process:

Process Item category Schedule line category Movement type
KB/CF KBN E0 631
KE/CI KEN C1 633
KR/CR KRN D0 634
KA/CP KAN F1 632

Item category determination:

Sales doc. type + Item category + Usage + Higher level item category = Default item category.

Shipping point is determined based on : 1) The shipping condition, 2) Loading group, 3) Delivering
plant.


Storage location determination :

Plant + Storage location + Shipping point

Pricing procedure determination :

Sales area + Doc. pric. proc. + Customer pric. proc. = Pricing procedure.

Material Determination (VB11):

In the sales order:

Order item : Item category is TAX (non stock item) &, schedule line category CX (no inventory
management).

Swap item : Item category is TAPS standard item (product selection) &, schedule line category PP
(article selection with MRP).

Customer material info record (VD51):

It comprises of customers own description for material &, customers shipping data.

In VOV8, check read info record control, after its activation only the system will access the data.

BOM item category determination (CS01) :

General item category group: ERLA LUMF

Header: TAQ TAP

Item: TAE TAN

Copying controls routines:

1) Header:
a) Data transfer routine – 051 – general header data
b) Data transfer routine – 101 – business data header
c) Data transfer routine – 001 – partner header
d) Copying requirements – 001 – header-same customer

2) Item:
a) Data transfer routine – 151 – general item data
b) Data transfer routine – 102 – business data/item completion


c) Data transfer routine – 002 – partner item
d) Data transfer routine FPLA – 251 – conditions
e) Data transfer routine – 301 – item rejection reasons

Note: FPLA is a table that captures billing plan.

3) Schedule lines:
a) Data transfer routine – 201 – general schedule line data
b) Copying requirements 501 – scheduled quantity > 0 (This routine checks whether system is
copying unconfirmed schedule lines from source document line item to target document line
item, if so system rejects copying process).

Master Contract*:

When the customer enters all types of the contracts with the business for certain validity period, those
contracts can be assigned to one master contract (document type GK) as a lower level contracts so as
to maintain data consistency. Lower level contracts are going to be assigned to master contract by
using “group referencing procedure”, e.g. SDGK.

Group referencing procedure can be used to differentiate the fields from master contract to lower level
contracts. Fields can be categorised as:

1) Copy fields: The values of the copying fields can be changed at lower level contracts e.g.
business data.
2) Proposed fields: These are like copying fields but values cannot be changed at lower level
contracts e.g. business partner.
3) Identical fields : Fields cannot be changed at lower level contracts e.g. validity contract
period.

Tables: FPLA - Billing plan, VBKD – Sales document business data, VEDA – Contract data.

Item category determination:

Sales document type + Item category group + usage + higher level item category = Default item categ.

Landscape of the project:

It is the configuration of the servers that you are working with. It may vary from company to company
for e.g.

Development→ Quality → Back up → Production (most widely used)

Development → Testing (QA) → Production.

Storage location determination:


Plant + Storage condition + Shipping point.

Plant determination:

1) CMIR,
2) Customer master record of ship to party,
3) Sales: general/plant view of material master record.

Schedule line category:

Item category + MRP type of that particular material master.

Determination of requirement type:

Search strategy of system follows the checking of following:

1) Strategy group in the MRP foreview of the material master
2) MRP group of the MRP foreview
3) Material type
4) Schedule line category or in other words system assumes the special rule of item category +
MRP type
5) Checks the item category.

After these many checks system confirms that the transaction is not relevant for TOR & availability
check functions.

Transfer order:

Instructions to move the material from source storage bin to destination storage bin with in the
warehouse complex at a specified time.

It contains a list of : 1) Material number, 2) Material quantity, 3) Source storage bin, 4) Destination
storage bin.

In other words it contains the list of goods to be picked before going for picking the goods.

This order is created based on :

1) Customer delivery
2) A transfer requirement
3) A posting change notice.

Tax is calculated on net price (i.e. gross price – Discounts)

[(Base price) – (Discounts) = (Gross value)] + (Frieght) + (Taxes) = (Net price)


Shipping point determination:

Shipping conditions + Loading group + Delivering plant + Proposed shipping point + manual
shipping point.

The two fields that are transferred to the FICO module after saving invoice are :

1) Reference number
2) Allocation number.

Proforma Invoice* :

Proforma invoice doesn’t have a/c determination procedure. Because it need not to transfer billing
information from SD to FI. It only gives/shows the value of the articles being purchased by the
customer. The billing document type for proforma invoice is F8 (for the normal invoice it is F2).

Gaps in SAP-SD :

Adding new fields, new screens &, new programs.

Adding new fields e.g Passport number in the address tab & thereby creating those
new fields by creating the table & assigning the values to the database table.

This is done with the help of ABAPer, they in their turn do this through the help of BADI’s or ABAP
routines.

Billing types: Periodic billing plan

Milestone billing plan

1) Order related billing
2) Delivery related billing
3) Credit memo
4) Debit memo
5) Proforma invoice for order
6) Proforma invoice for delivery
7) Cash sales


Outbound delivery can be processed without shipping point in two cases :

A) Third party order processing
B) Rush order

In case of 3rd party order processing, goods are delivered to the customer by the vendor where as in
case of rush order, delivery will be automatically created once we will save the sales order of sales
document type RO, because system will take the shipping point from the shipping conditions being
defined under the shipping tab of customer master & material master.

Shipping conditions are stored at three levels:

a) Customer master record
b) Order document header in shipping view
c) Material master record

Business data = Sales data + Shipping data + Billing data.

ATP Quantities = Warehouse stock + Planned receipts – Planned issues.

3 types of availability checks:

1) Against ATP
2) Against product allocation
3) Against planning (Push cycle)

Availability Check is based upon : Checking group, requirement class, requirement type &, schedule
line category.

Static check in credit management = Open sales order + Open deliveries + Open billing + Open items

Dyanamic check in credit management = Static check + time horizon.

Cutover Strategy: depends upon how the organisations design their data load strategies.

Normally, sequence of data loads for configuration settings, master data, transaction data is done on
the criteria which follows whom. And the copy of this system of sequence of data loads, which is
known as Production system, is prepared a day before going live & after checking the data loads; we
go live, 100% or partial again depending upon organisational set up & policies.


Cutover planning is highly site specific. Stock being highly dynamic qty.

All the back dated transactions on
the stock needs to be loaded.

should be correctly entered on the day of

going live. Strategy for loading should be crystal clear.

Note: A document can have the reference status as partial or full at item level & can have the
reference status as full at header level.

Note: When system checks availability it uses backward scheduling.

The influencing factors for the determination of the availability date:

1) Route from the shipping point to the ship to party location.
2) Shipping point from which the goods are issued.
3) Loading group from the material master record.
4) Weight group determined from the order using the order quantity.

Several sales orders can be combined into one single delivery document when:

1) Availability of all items are confirmed &,
2) The SH & plant, both are same for all the orders.

We specify (1) loading time at shipping point determination level &, (2) pick/pack time at route
determination level.

The influence of route on the material availability date is because of the transit time & transportation
lead time.

Cancellation/Rejecting a sales order:

Reverse the a/c ing doc. or delete it → Cancel the invoice by using trx VF11 → Reverse the goods
issue using trx VL09 → Delete the delivery order/doc. using VL01N → Delete/Reject the sales order.

Making the picking qty. Zero in the delivery doc.


VK11 vs VK31:

In VK11 we can store condition records for more than one condition type ( one condition type at one
time).

But system is not allowing to store the record in the VK31 (Multiple condition types at one time) for
the condition type PR00 & access sequence PR02. This is because this access sequence contains two
accesses 20 & 30 having the same table number but there is the difference between the technical view
of it for transferring the data from doc. field & condition field, so you cannot maintain the data at
VK31.

IMPORTANT: If the header data & header partners for specified delivery or sales orders are
identical & if requirements for splitting do not apply then we can combine deliveries into one
invoice.

SAP Projects

SAP implementation projects SAP Support SAP migration project

project

Customer decides to move with the

new version i.e. older version to new

version.

Customers are moving towards

SAP software.

SAP project is supported by the consultants (Support team) in day to day business.

Restricting the number of items in the billing document:


1) We can restrict delivery with delivery tolerance, thereby causing invoicing of the desired.
2) SPRO→ IMG → S & D → Billing → Billing doc.→ Country specific features → maintain
maximum number of billing items.

Reverse the a/c ing document in case of cancelling the PGI:

1) Enter a returns order (order type RE) for the customer & the material involved
2) Create a return delivery for the returns order

The delivery quantities in the returns delivery must correspond to the goods issue quantities in the
incorrect goods issue document.

3) Post goods issue for the returns delivery.
4) Invoice the business transaction with a returns credit memo. The system proposes billing type.
The original billing document for the incorrect goods issue document is cleared by this credit
memo.

Country India Version (CIN) :
There are four scenarios in CIN, they are as follows :

1) Factory sales JFACTIN JINFACIN
2) Stock transfer JSTKTRIN JINSTOIN
3) Depot sales JDEPOTIN JINDEPIN
4) Export sales JEXPORIN JINEXPIN

TAXINJ TAXINN

TAXINJ: Condition or formula based excise determination.

TAXINN: Condition based excise determination.

Excise duty: On the manufacturing of goods.

Goods movmnt. : Manufacturing plant premises Plant storage

location

3 types

1) Basic excise duty (BED)
2) Special excise duty (SED)
3) Additional excise duty (AED)


CESS : Central government charges this

Purpose is to develop specific area.

Sales tax (VAT) : Levied on sale of product.

Gross price of goods { inclusive excise duty (CST or LST) }

With holding taxes :} according to the IT act 1961.

Payment to contracts & Insurance Rent Fees for professional interest other than
subcontracts commission (194I) or technical services interest on securities
(sec 194 C) (Sec 194 B) (Sec 194 J) (Sec 194 A)

Taxes imposed by the central & state government

Excise duty Sales tax Withholding tax

In formula based excise duty (TAXINJ) system takes certain tax indicators to determine the excise
duty like below :

a) Plant master data
b) Vendor master data
c) Customer master data
d) Material master data

Excise registers: Registers maintained by excise authorities relating to excise rates & material

movements.

1) Register RG1
2) Register 23A/23C Exemption Forms: 1) Form C
3) RG 23D 2) Form F
4) PL a/c 3) Form H


5) Register RP-12 4) Form ARE1, ARE2, ARE3.

“A Certificate” with depot sales

Should be registered in RG23 register under excess excise duty that should be recovered from
customer.

Types of exports : Excise bonds :

1) Exports under bond & no bond. 1) Fixed bonds.
2) Exports under claim for rebates. 2) Running bonds.
3) Deemed exports.

Register RG 1 : maintained by manufacturing plant for excisable finished product.

Shows

Goods movement from : Factory → Store

RG 23A/23C : Receipt & issue of excisable materials

consists of

2 parts

Quantity of the material How much excise duty on the material

Part I entries only for receipt of goods, except for issues to returns of vendor & issues for STO
between plants.

Part II registers incoming & outgoing excise invoices for manufacturing plant.

Serial numbers are assigned by the system.

RG23A → for raw material


RG23C → maintained for capital goods.

RG23D : Records goods receipt & issues of excisable materials by depots.

PL a/c : bank a/c from where business transfers the excise duty to the excise authorities.

Note : From 2011 financial year onwards LST is going to be abolished & only CST is going to be
charged.

Deemed exports: A sale of goods in India to a company that qualifies as an “EOU” (export oriented
units) or its located in the area of :

a) EPZ (export processing zone)
b) EHTP (Electronic hardware technology part)
c) STP ( Software technology part)

The materials which are exported, which are in their turn are used in
the manufacturing/production of materials that are again going to be exported, are exempted from
BED. These exports comes under or termed as ‘Deemed exports’.

Processing of CIN in SAP-SD:

I] Define organisational structure:

1. Define company
2. Define company code
3. Define plant : Define 2 plants i.e. 1st as manufacturing plant & 2nd as the depot plant
4. Define divison
5. Define sales organisation : Define 2 sales org., 1st for domestic sale & 2nd for export sale
6. Define Dchl. : Define 2 dchl, 1st for direct sale & 2nd for export sale.
7. Maintain storage locations
8. Define shipping points : Define 2 shipping points, 1st is plant & 2nd is depot.
9. Define purchase organisation (for the purpose of STO)
10. Maintain purchase organisation for depot.
11. Define purchasing groups.
12. Assign purchase organisation to company code & plant.

II] FICO configuration setting:

I]

1. Define & assign fiscal year variant : e.g. V3
2. Define, open & close posting period variant to company code.


3. Define document type e.g. RV (billing doc. transfer), WL (goods issue/delivery) under
company code.
4. Define maximum exchange rate differences per company code.
5. Maintain field status variant: a) define field status variants
b)Assign company code to field status variant to company code
c) Screen variants for document entry
d) define tolerance groups for employees
e) Maintain fast entry screen for G/L a/c items (SAP standard sufficient): i) enable fiscal year
default, ii) Default value date, iii) Archiving A/C type life.

II] General ledger accounting

a) Edit chart of a/c list
b) Assign company code to chart of a/cs.
c) Define retained earnings a/c.
d) Copy general ledger a/c to company code
 Define a/c for exchange rate differences
 Define tolerance groups for G/L a/cs
 Define house banks

Tax on sales & purchase:

a) Access sequences
b) Define condition types
c) Define procedures
d) Assign country to calculation procedure.

 Activate CIN for specific year.
 Define tax codes for sales & purchases.: a) define tax codes for sales & purchases.

SD configuration settings:

a) Create condition tables.
b) Maintain access sequences.
c) Define condition types.
d) Define customer pricing procedure
e) Define document pricing procedure
f) Assign document pricing procedure to order types
g) Define pricing procedure determination (OVKK).

Go to OVK2 & define regions. (Under SAP Netweaver)

SD tax determination rules:


a) Define tax determination rules
b) Define tax relevancy of master records
c) Go to VKOA.
d) Define foreign trade data.

Procurement settings:

I] Maintain excise registration
II] Maintain plant settings
III] Maintain excise groups
IV] MIGO settings
V] Maintain series groups
VI] Maintain excise duty indicators
Detrmination of excise duty: 1) Select tax calculation procedure, 2) Maintain excise defaults,
3)condition based excise determination

Master data:

 Maintain chapter Ids
 Assign users to material master screen sequence for excise duty.

Business scenario:

1) Factory sales.
2) STO
3) Depot sales
4) Export sales.

3rd party sales order:

To procure or purchase materials from external vendor, the business
has to raise “Purchase requisition”, with reference to purchase requisition
business has to raise the “Purchase order”(ME21N).

Once the purchase order has been sent to the vendor, vendor raises
the “sales order” and initiates outbound delivery.

With reference to this inbound delivery business has to post the
“goods receipt”(MIGO).

With reference to goods receipt the business has to verify
“Invoice”(MIRO). With reference to the invoice business makes the
“Vendor payment”.


Configuration settings for 3rd party sales order : Create material master with general item category
group BANS.

TA + BANS + NIL + NIL = TAS

Third party sales order : The vendor directly delivers the goods to the customer and invoice has to
be raised with reference to this outbound delivery in favour of the business.

Individual sales order : In individual purchase order vendor delivers the goods to the business &
business in turn delivers the goods to the customer.

Important events in SD-CIN:

If your company has only one set of excise registers, then you need to maintain only one
excise group.
1. Create one excise group for each set of registers that you need to keep.
2. Assign the excise groups to plants.
3. Maintain whether this Excise group is for a depot or not.
If you receive only one consignment for an Excise challan then you can leave GR's per EI as
blank. If you receive multiple GR's for a given Excise challan and would like to avail
multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple
credit'. Alternatively if you want to avail the credit only after all the goods receipts have
been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing
the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and
would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'.
This will post the selected records into RG23D automatically. You cannot cancel the
selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity
on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D
during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements
automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of
material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material
through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of
material into consumption stock. Excise Group Governs which set of excise registers a
business transaction will be included in.


Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for. On the
dialog box, Control Code means "chapter ID." So, for example, to create a condition record
for a tax that applies to a combination of country, plant, and chapter ID, select
Country/Plant/Control Code.
4. Choose .
5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have
defined.
6. Save the condition record.
Formula-Based Excise Determination - When you execute a business transaction involving
materials that are subject to excise duty, the system automatically calculates the duty for you.

In order for the system to be able to determine which rate of excise duty to apply, you must
have maintained all the data on the Excise Rate Maintenance screen, which you can Master
Data®access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate
Maintenance.

You maintain the following types of data:
- Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for
all the plants with the same excise status from a legal point of view, such as all those that are
in an exempt zone. See also the information about manufacturers that are only entitled to
deduct a certain portion of the duty (see Partial CENVAT Credit).
- Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an
excise duty indicator. You must also specify the vendor type – for example, whether the
vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the
vendor qualifies as a small-scale industry. For each permutation of plant indicator and
vendor indicator, you then create a final excise duty indicator.
- Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the
same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final
excise duty indicator.
- Material master data
Each material is assigned a chapter ID.
- Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system
accordingly.

Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for. On the
dialog box, Control Code means "chapter ID." So, for example, to create a condition record


for a tax that applies to a combination of country, plant, and chapter ID, select
Country/Plant/Control Code.
4. Choose .
5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have
defined.
6. Save the condition record.
Formula-Based Excise Determination - When you execute a business transaction involving
materials that are subject to excise duty, the system automatically calculates the duty for you.

Let us consider an example to illustrate how the system determines which rate of excise duty
to apply to a material. Assume you are posting a sale of ball bearings to a customer. The
system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant. Similarly,
your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what
the final excise duty indicator is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Let’s assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty
applies to chapter ID 1000.01 under status 7.

Condition Supplement in Pricing :

A condition supplement is a supplement for a particular condition type. For example, you can
include a supplement every time you apply a material price. The supplement can contain
various discounts. During pricing, the system automatically applies the discounts defined in
the supplement every time it accesses a material price. You define the condition types for
which you want to use condition supplements in Customizing for Sales.

To include a condition supplement choose:
Goto _ Condition supplement on the overview screen of the condition record. You can then
enter the data for each discount in the condition supplement.
You can only enter a condition supplement if the condition type you are working with
has already been defined in Customizing for Sales to include condition supplements.

Cash Sales: In this type of order CS, as soon as you save the sales order the delivery is
automatically created as same date and billing will also be generated at the same date as soon
as you save the delivery document.

In a rush order, the customer picks up the goods immediately, or you deliver them on the
same day as when the order was created. When you save the rush order, a delivery is


automatically created in the standard system. Billing the rush order takes place as normal,
afterthedelivery.
In the standard system, sales document type RO is saved for rush orders with immediate
delivery type LF. Once the goods have been removed from storage, the goods are picked, and
goods issue is posted. Once the billing documents are created (for example, in collective
processing), invoice papers are printed and sent to the customer.

Rush Order: In this type of Order RO , The delivery will be created as soon as you save the
sales order. But you bill the customer later.

In cash sales, you can process an order for when the customer orders the goods, picks them
up, and pays for them immediately. The delivery is processed at the same time as when the
order is created and a cash invoice is printed immediately: billing is therefore related to the
order, unlike rush and standard orders. Receivables are not created for the customer, as they
are for rush and standard orders because the amount in the invoice is immediately posted to a
cash a/c.
In the standard system, sales document type BV (CS) is saved for cash sales with immediate
delivery type BV. When the sales employee creates a cash sale, the system automatically
proposes the current date as the date for delivery and billing. Once the order has been posted,
a delivery with type BV is created immediately in the background and the system prints a
document that is used as an invoice for the customer. The invoice papers are controlled with
output type RD03, contained in the output determination procedure for order type CS.


Some notes on Customer Relationship Management

CRM Notes

Concepts of Middleware :

Defining client administration → SCC4

Creating an RFC user (SAP R/3) → SU01

Defining logical systems → SPRO

Assigning logical systems to client → SCC4

Creating RFC user → SU01

Creating RFC destination for the R/3 system → SM59

Checking table CRMCONSUM → SM30

Maintaining table CRMRFCPAR → SM30

Activating event control → SM30

Creating site for OLTP → SMOEAC (Admin. Console)

Creating subscription for OLTP → SMOEAC

Creating RFC destination for IPC server → SM59

Creating RFC destination for IPC dispatcher → SM59

CRM:

Master data (in SD) → Business objects (in CRM)

Transaction data (in SD) → Customizing objects (in CRM)

Condition data (in SD) → Condition objects (in CRM)


Steps :

1. Connectivity (SM59) Business objects → R3AC1
2. Object generation (Mapping of data) Customising obj.→ R3AC3
Condition objects → R3AC5
3. Replication (Migration of data)
4. Realignment

Initial Download Delta Download Synchronization
R3AS R3AC4 R3AS4
ECC→CRM ECC< > CRM CRM→CDB

Trouble shooting/Error handling.

A. RFC connections → SM59
B. Object generation monitoring R3AC1
R3AC3
R3AC5

C. Monitor IDoc’s – Bdoc’s → SMW01 SMWP
D. Monitor quees.

Inbound Quee Outbound Quee

(SMQ2) (SMQ1)

Base Customization :

Few of the important points to be remembered in context with R/3:

 The pricing procedure which we use in R/3 is RVAA01, whereas the procedure in use
for CRM is 0CRM01


 The pricing condition in R/3 is PR00 whereas in case of CRM, it is 0PR0.
 The sales document types in R/3 are known as, Transaction types in CRM.
 The output determination of r/3 is known as action profile in case of sap CRM.
 Material determination (R/3) → Product Substitution (CRM).
 The trx. code for creating an order is CRMD_ORDER
 The trx. code for creating a business partner is BP.
 The trx. code for creating material is COMMPR01.
 The trx. code for creating an organisational structure is PPOCA_CRM, for changing
the organisational structure is PPOMA_CRM &, for displaying the organisational
structure is PPOSA_CRM.
 The pricing in SAP CRM is done through IPC i.e. the internet pricing configurator &
it has got 3 engines for this task & they are : 1) SPE : sales pricing engine ; 2) SCE :
Sales configurator engine & ; 3) TTE : Transaction tax engine.
 Partner determination procedure is known as partner processing in SAP CRM.
 The action profile & the organisational determination, both are done with the help of
wizards.
 Here in SAP CRM we have got only the header data & item data. We don’t have the
schedule lines in SAP CRM hence there are no deliveries in SAP CRM & thereby no
billing also. For both of these functions we rely over the R/3
 As there is no delivery in SAP CRM, hence there is no inventory maintenance records
also, in SAP CRM. The availability check is done through the r/3 or the SAP APO i.e.
advanced planning optimiser. The ATP check is done through R/3 & the GATP check
is done through the SAP APO.
 There is no credit check being done under SAP CRM.
 In SAP CRM there are no rebates.
 There are two documents i.e. BDoc’s & MDoc’s. Bdoc’s are used for the
ECC→CRM, whereas Mdoc’s are used for synchronisation i.e. for CDB
(consolidated database, for mobile applications & sales)

Apart from this the SAP CRM has been classified into 9 modules of which the one’s I know
are :

 Base Customisation
 Marketing
 Sales
 Services
 Middleware
 CIC : or the winclient
 SAP User Interface : or the webclient
 Mobile Sales

I Doc : Intermediate document, B Doc: Business document, M Doc: Message document.


Here the data transfer is being done through middleware & XI system. SAP XI is for
transferring the data from non legacy systems to legacy systems.


SAP SD Notes

More Related Content

What's hot

Similar to SAP SD Notes

Recently uploaded

SAP SD Notes