120434715-sap-sd
DESCRIPTION
sdTRANSCRIPT
�-----------------------�Page�1-----------------------
ENTERPRISE�STRCTURE�
CLIENT�(Company)-A�client�is�a�self-contained�
technical�unit.�A�client�can�be�considered�to�be�a�
synonym�for�group.�
Company�Code�
•�A�complete�Accounting�unit�can�be�representing�as��
the�smallest�organizational�unit�of�external�
accounting.�
•�At�Company�Code�level�we�create�
..�Balance�sheet�required�by�law�
..�Profit�and�Loss�statement.�
•�Each�company�code�represents�an�independent��
accounting�unit.�Several�company�codes�can�use�the�
same�chart�of�account.�
Assignment�
..�Company�code�to�company�
..�Company�code�to�Credit�control�area�
..�Company�code�to�Controlling�area�
..�Company�code�to�financial�management�area�
•�(An�FM�Area�is�organizational�unit�which�Plans,��
Controls�and�Monitors�funds�and�commitment�
budgets)�
..�Controlling�area�to�financial�management�area�
..�Controlling�area�to�Operating�Concern�
-----------------------�Page�2-----------------------
Sales�Organization�
•�The�highest-level�of�organizational�unit�in�SD�is�
Sales�Organization.�
•�Responsible�for�Distributing�goods�and�services,��
Negociation�sales�conditions,�Product�liability�and�
other�customer�rights�of�recourse.�
•�Sales�organization�is�also�used�to�take�for�example��
a�regional,�national�or�international.�
•�A�sales�organization�assigned�to�a�company�code.�
Distribution�Channel�
•�Distribution�Channel�represents�strategies�to�
distribute�goods�and�services�to�customer.�
•�DC�is�assigned�to�a�sales�organization.�The��
assignment�is�not�unique.�
•�You�can�share�Customer,�Material�and�Condition��
master�data�by�maintaining�a�reference/common�
DC.�
Division�
•�A�Division�is�used�to�group�material�and�services.�
A�material�can�have�only�one�Division.�
•�We�can�make�Customer-�specific�agreements�for�
each�Division,�for�example�regarding�partial�
deliveries�or�pricing�within�Division.�(In�CMIR)�
•�You�can�share�Customer�and�Condition�master�
data�by�maintaining�a�reference/common�
-----------------------�Page�3-----------------------
Division�
•�A�Division�is�assigned�to�a�sales�organization.�The��
assignment�is�not�unique.�
•�You�can�use�cross�division�to�enter�multiple��
materials�with�various�divisions�in�a�sales�order.�
•�You�can�choose�division�specific�sales,�it�is�
controlled�by�customizing�for�sales�document�type.�
Sales�area�
•�A�Sales�area�is�a�combination�of�a�Sales��
organization,�DC�and�Division.�It�defines�the�
Distribution�channel�of�a�Sales�organization�uses�to�
sell�products�of�certain�Division�
•�By�defining�and�assigning�Sales�Organization,�DC��
and�division�a�Sales�area�not�automatically�formed,�
you�have�to�set�up�a�sales�area.�
•�A�sales�area�can�belong�to�only�one�company��
code.�Assigning�the�sales�organization�to�company�
code�creates�this�relationship.�
•�Each�sales�and�distribution�document�is�assigned��
to�exactly�one�sales�area.�This�assignment�cannot�be�
changed.�
•�Various�master�data�depending�on�the�sales�area,��
for�example�customer�master�data,�material�master�
data,�price�and�discount.�This�system�also�carries�
out�a�number�of�checks�concerning�the�validity�of�
certain�entries�according�to�the�sales�Area.�
-----------------------�Page�4-----------------------
•�Sales�area�assigned�to�Credit�Control�Area.�
•�Sales�office�assigned�to�Sales�Area�
•�Sales�group�assigned�to�Sales�office.�
•�Employee�of�a�sales�office�can�be�assigned�to�sales��
group.�
Business�area�
•�The�Business�Area�is�a�separate�business�unit�for��
which�internal�reporting�can�be�carried�out.�A�
company�code�may�be�divided�into�multiple�business�
areas.�A�business�area�may�also�be�shared�by�
several�company�codes.�
•�Business�area�is�not�limited�by�company�codes.��
For�this�reason,�the�business�areas�in�all�company�
codes�must�have�the�same�description.�Using�
organizational�unit�is�optional.�
•�Business�area�can�be�used�to�prepare�balance�
sheets�and�profit�and�loss�statements�not�only�for�
company�code,�but�also�for�other�internal�areas�
(E.g.,�division-related).�
•�The�relevant�business�area�is�determined�for�each��
order�item�according�to�defined�rule.�
•�Rules�for�Business�area�determination�
..�Business�Area�assignment�by�Plant�and�Item�
division�
..�Business�Area�assignment�by�sales�area�
..�Business�Area�assignment�by�Sales�Organization�
-----------------------�Page�5-----------------------
and�D.C,�Item�Division�
Plant�
•�The�Plant�is�a�location�where�material�is�kept.��
Represent�a�production�facilities�or�Material�
requirement�planning�in�the�System.�In�sales�and�
Distribution,�A�Plant�represents�the�location�from�
which�Materials�and�Services�are�distributed�and�
corresponds�to�a�distribution�center.�The�relevant�
material�stocks�kept�here.�
•�A�Plant�assigned�to�a�company�code.�
•�Inventory�valuation�is�done�either�at�company��
code�level�or�Plant�level,�however�the�stock�is�
managed�at�Storage�location�level.�
•�A�Delivering�plant�assigned�to�Combination�of��
Sales�organization�and�Distribution�channel.�
•�Delivering�Plant�Determination�in�sales�Document��
according�to�following�step�
1.�CMIR�
2.�Customer�Master-Ship�to�Party�(Sales�area-�
shipping�tab�page)�
3.�Material�Master-�Sales�Org.�1�View.�
..�CMIR�has�precedence�over�customer�and�material�
master.�
•�A�plant�is�essential�for�determine�the�Shipping��
Point.�
-----------------------�Page�6-----------------------
•�In�absence�of�a�Delivering�plant�determination��
there�can�be�no�automatic�determining�of�shipping�
point�or�automatic�tax�determination,�no�availability�
check�can�be�carried�out�and�no�outbound�delivery�
can�be�set�up.�
Shipping�Point�
•�Shipping�Point�highest�organizational�unit�in��
Shipping�
A�shipping�point�is�under�client�level.�
•�A�shipping�point�assigned�to�a�Plant.�A�Shipping��
point�can�be�assigned�to�multiple�plants.�
Various�Shipping�point�can�be�assigned�to�same�
plant.�
•�The�Shipping�point�can�be�a�loading�ramp,�a�mail��
depot�or�a�rail�depot.�It�can�also�be�a�group�of�
employees�responsible�only�for�organizing�urgent�
deliveries.�
•�The�shipping�point�is�responsible�for�processing�
shipping.�Each�Outbound�Delivery�is�processed�by�
exactly�one�shipping�point.�
•�The�shipping�point�is�normally�determined��
automatically�(At�item�level)�for�each�item�in�the�
sales�document.�The�automatic�default�value�can�be�
later�changed�manually�in�sales�order�if�we�have�
planned�for�a�different�shipping�point.�We�can�
change�shipping�point�in�delivery�document�only�at�
-----------------------�Page�7-----------------------
initial�create�screen�before�saving�the�delivery�
document.�
•�Shipping�point�determination�based�on�these��
combinations.�
..�Delivering�Plant�
..�Shipping�condition-�Sales�document�type�OR�
Customer�master�data-Sold�to�Party�
(Shipping�Tab�Page)�
..�Loading�group-Material�master�data�(Sales:�
Gen/plant)�
..�Shipping�condition�from�sales�document�type�has�
precedence�over�that�from�customer�master.�
Warehouse�
•�Warehouse�having�following�organizational�units��
for�efficient�processing�of�goods�receipt�and�goods�
issue.�
..�Warehouse�Number:�The�entire�warehouse�
structure�is�managed�under�one�warehouse�Number.�
This�number�represents�the�warehouse�complex.�
..�Warehouse�Number�assigned�to�a�combination�of�
Plant�and�storage�location.�
..�You�can�group�Transfer�Order�based�on�warehouse�
number.�
Storage�Type:�The�different�warehouse�areas,�which�
differ�with�respect�to�their�organizational�and�
technical�features,�are�defined�as�storage�types�(for�
-----------------------�Page�8-----------------------
example-high-rack�warehouse�with�random�storage,�
picking�warehouse�with�fixed�bins,�or�shipping�
area).�
..�Picking�area:�Below�the�storage�Type�level,�The�
Picking�area�group�together�storage�bins�from�a�
picking�point�of�view.�
..�A�delivery�can�be�split�up�into�different�picking�
areas�to�make�parallel�picking�possible.�
..�Staging�area:�The�staging�area�is�a�part�of�the�
warehouse�where�goods�are�stored�immediately�
after�unloading�or�shortly�before�loading.�
..�Door:�A�Door�can�be�used�for�both�the�inbound�
and�outbound�delivery�of�goods.�
(Door�determination�takes�place�at�the�delivery�
header�level.�Staging�area�determination�can�take�
place�at�the�delivery�header�level�and�item�level.�
Different�staging�area�at�the�delivery�item�level�lead�
to�a�transfer�order�split�because�the�staging�area�is�
a�header�level�in�the�Transfer�Order.)�
•�The�connection�of�the�organizational�unit�in�the��
warehouse�to�MM�Inventory�Management�results�
from�The�Assignment�of�Warehouse�No.�To�a�
combination�of�plant�and�storage�location�
•�You�can�Group�Transfer�order�based�on�the��
warehouse�number.�
MASTER�DATA�
-----------------------�Page�9-----------------------
Customer�master�data,�Customer�material�
information�record,�material�master�data,�Condition�
master,�Common�master,�Additional�master�data�
Customer�master�Data�
•�The�Customer�Master�data�divided�in�following��
categories.�
..�General�Data:�store�centrally-Client�specific,�valid�
for�all�organizational�Units.�
..�Sales�Area�data:�
..�Company�Code�data�
•�It�includes�all�necessary�data�for�processing�Order,�
Deliveries,�invoices�and�Cust.�Payment�
..�General�data�having�on�following�tab�
..�Address:�Name,�Address,�and�Language.�
..�Control�Data:�Tax�Information�
..�Payment�Transaction:�Bank�Details�
..�Marketing:�Industry,�Customer�Classification�
..�Unloading�Point:�goods�receiving�Hours�
..�Export�Data:�Data�for�export�control�
..�Contact�Person:�Address�of�business�partner�
..�Sales�Area�data�having�following�tab�pages�
..�Sales:�Sales�office,�sales�district,�currency,�
customer�group,�Customer�pricing�procedure,�Price�
list.�
..�Shipping:�Delivery,�Shipping�condition,�Delivery�
-----------------------�Page�10-----------------------
Plant,�POD�Relevance,�Partial�delivery-�
Check�Complete�delivery�by�law,�Transportation�
Zone.�
..�Billing:�Incoterm,�Term�of�payment,�Credit�control�
area,�Account�Assignment�Group,�Tax.�
..�Partner�Function:�(Can�different�or�Identical)�Sold�
to�Party,�Ship�to�Party,�Bill�to�Party,�
Payer�
..�Company�Code�data�having�on�following�tab�
..�Account�management:�Reconciliation�account�
..�Payment�transaction:�Payment�method�
..�Correspondence:�Dunning�Procedure,�Accounting�
clerk�
..�Insurance:�Amount�Insured�
•�Any�changes�in�the�customer�master�do�not�get��
reflected�in�documents�created�prior�to�the�change�
except�for�ADDRESS.�
•�Sales�organization�has�to�maintain�own�relevant�
sales�area�data�if�they�sell�product�to�customer�
those�belong�to�different�sales�organization.�
•�We�can�maintain�the�INCOTERM�in�customer��
master�record�in�various�ways,�depending�on�the�
sales�area�data.�
•�Account�group�controls�customer�master.�
•�Master�data�proposal�in�sales�document-�
..�Delivery�date�and�tax�information-�From�Ship�to�
-----------------------�Page�11-----------------------
Party�master�record�
..�Payment�terms,�Credit�limit�check-�From�Payer�
master�record�
..�Address�to�which�invoiced�to�sent-�From�Bill�to�
Party�master�record�
..�Shipping�conditions,�Pricing,�incoterms-From�Sold�
to�Party�
Customer�material�information�record�
•�Cross�reference�from�your�customer‟s�material�no.��
to�your�material�and�customer�material�
description.�By�this�sales�order�can�be�placed�with�
the�customer‟s�material�no.�by�using�Ordering�tab�
page�
•�It�keeps�information�about�Delivering�plant,��
Customer�material�no.,�and�Delivery�agreement-�
Complete/Partial�
Material�master�data�
..�Basic�data�1�(valid�all�module�area)-Old�Material�
no.,�Division,�Matererial�group,�Matererial�group�
packaging�material,�Base�unit�of�measure,�General�
item�category�group�
..�Sales:�sales�org.�1:�Delivering�Plant,�Material�
Group,�Division,�Condition,�Tax�data,�Cash�discount,�
Minimum�Order�quantity,�Minimum�Delivery�
Quantity�
..�Sales:�sales�org.�2:�Material�group,�Bonus�Group,�
-----------------------�Page�12-----------------------
Product�hierarchy,�General�item�category�group,�
Item�category�group,�Product�attribute�
..�Sales:�Gen/Plant�data:�Availability�Check,�
Transportation�group,�loading�group,�Batch�
Management,�Matererial�group�packaging�material,�
Serial�no.�Profile�
..�MRP�3:�Availability�Check�
..�Plant/data�storage�1:�Batch�management,�Storage�
condition�
..�Plant/data�storage�2:�Serial�no.�Profile�
..�Foreign�trade:�Export:�Export/�import�group,�
Region�of�origin�
..�Sales�Text:�Item�text�for�sale�
•�Material�Master�is�controlled�by�Material�Type�
TAB�PAGES�FOR�SALES�DOCUMENT�
Initial�screen-�Create�with�reference,�Sales,�Item�
Overview,�ordering�Party.�
Create�with�reference-�inquiry,�Quotation,�Order,�
Contract,�Scheduling�agreement,�Billing�Doc.�
Overview�screen-�Sales,�item�Overview,�Item�
details,�Ordering�Party,�procurement,�Shipping,�
Reason�for�rejection.�
SALES�
-----------------------�Page�13-----------------------
Sales�Document�
•�A�sales�Document�has�three�level-Header,�Item�
and�Schedule�Line�
•The�sources�of�data�in�a�sales�document�are-�
..�Master�data�
..�Customizing�
..�Other�SD�document/Existing�document�with�data�
..�Hard�coded�controls�
•�When�you�create�a�sales�document,�you�can�also��
enter�the�Ship�to�party�instead�of�sold�to�Party.�
The�system�then�determines�the�Sold�to�Party�from�
the�ship�to�party�customer�master�record.�If�there�
are�several�possible�sold�to�parties�for�ship�to�party,�
the�system�displays�a�selection�screen�with�possible�
alternatives.�
•�In�sales�order�with�fast�change�option�you�can��
change�–�Reason�for�rejection,�Delivery�block,�Billing�
block,�delivery�date,�delivery�priority�and�Plant.�
•�With�Mass�change�option�in�a�sales�document�list��
you�can�change-�Plant,�Materials,�currency�and�
Pricing.�
•�A�Billing�Block�can�assigned�at�sales�document��
header�level�and�item�level.�
•�A�delivery�block�can�assigned�at�sales�document��
header�and�schedule�line�level.�
•�An�item�status�is�deemed�completely�if�it�has��
-----------------------�Page�14-----------------------
rejected�by�giving�a�reason�of�rejection.�
Example�of�Sales�document�Type�
•�Important�Controls�of�Sales�Document�Type.�
..�Reference�mandatory�from�any�other�Document.�
..�Check�division-System�reaction�if�division�at�item�
level�is�different�from�header�level.�
..�Item�Division-�If�you�mark�this�field,�the�system�
propose�the�division�from�the�material�master�record�
of�the�item�else�the�division�in�the�sales�document�
header�also�count�for�all�items.�
..�Check�credit�limit�
..�If�the�system�reads�any�CMIR�or�Not.�
..�Incompletion�Procedure�Assignment.�
..�Document�Pricing�Procedure.�
..�Message�about�open�Quotation,�open�Outline�
agreement,�etc.�
..�Incomplete�message�switch-�when�ticked�doesn‟t��
allow�you�to�save�an�incomplete�document.�
When�unchecked�the�incompleteness�is�controlled�by�
status�groups�of�Incompletion�Log.�
..�Delivery�type.�
..�Delivery�block�
..�Shipping�conditions�
..�Immediate�delivery�switch�
..�Billing�plan�type�
..�Billing�Type�
-----------------------�Page�15-----------------------
..�Billing�Block�
•�You�can�limit�the�validity�of�your�sales�document��
type�at�the�level�of�sales�organization,�distribution�
channel�and�division�(i.e.�for�sales�area)�
Pre-sale�phase�
IN�=�Inquiry�
QT�=�quotation�
Out�Line�agreement�
QC�=�quantity�Contract�
DS�=�Scheduling�Agreement�
QP�=�Rental�Contract�
WK1�=�General�value�contract�
Sales�Phase�
OR�=�Standard�order�
RO�=�Rush�order�
CS�=�Cash�sales�
CF�=�Consignment�fill-up�
FD�=�Free�of�charge�delivery�
Complaints�
RE�=�Returns�
CR�=Credit�memo�request�
SDF�=�Free�of�charge�subsequent�delivery�
DR�=�Debit�memo�request�
Sales�document�Item�category�
Example�of�Sales�document�Item�category�
-----------------------�Page�16-----------------------
•�Important�Controls�of�Sales�Document�Item�
category�
..�Business�item-If�the�Business�item�at�item�level�
can�be�different�from�that�at�header�level�(For�
Example-�Sales�data,�shipping�data,�billing�data).�
..�Completion�Rule-�The�rule�for�establishing�when�a�
quotation�or�contract�is�complete.�
..�Special�Stock�indicator-�For�Ex-�Consignment�
stock.�
..�Billing�plan�type�
..�Billing�relevance-�Order�related,�Delivery�related,�
etc�
..�Billing�block�
..�Schedule�line�allowed-�Indicates�whether�you�can�
create�schedule�line�for�the�item.�
..�Different�Procedures-�Incompletion,�Partner�
determination�and�text�determination.�
..�Structure�Scope�for�BOM�
..�Pricing-�Indicates�whether�the�system�
automatically�carries�out�pricing�at�the�item�level.�
..�Automatic�batch�determination�
•�Item�Category�Determination-�
Sales�Document�type�+�Item�category�group�+�
Usage�+�Item�category�of�upper�level�item.�
•�A�Sub�Item�is�an�item�assigned�to�a�higher-�level�
item.�
-----------------------�Page�17-----------------------
Schedule�line�category�
Example�of�Sales�document�Type�
•�Controls-�
..�Delivery�Block�
..�Movement�type-�
..�If�the�material�relevant�for�delivery.�
..�Transfer�of�requirements�
Pre-sale�phase�
AFN�=�standard�item�Inquiry�
AGTX�=�Text�item�in�quotation�
Out�Line�agreement�
KMN�=�standard�item�in�quantity�contract�
WVN�=�Standard�item�in�maintenance�contract�
WKN�=�item�in�value�contract�
Sales�Phase�
TAN�=�Standard�item�
TAD�=�Service�in�standard�order�
BVNN=�Free�of�charge�item�in�cash�sale�
KEN�=�standard�item�in�consignment�issue�
Complaints�
REN�=�Returns�standard�item�
G2TX�=�Text�Item�in�returns�
KLN�=�Free�of�charge�item�
Pre-sale�phase�
AT�=�Inquiry�schedule�line�
BN�=�quotation�Schedule�line�without�MRP�
-----------------------�Page�18-----------------------
Out�Line�agreement�
CV=�scheduling�agreement�with�consumption-based�
MRP�
Sales�Phase�
CP�=�Order�schedule�line�with�MRP�
CO�=�Consignment�issue�without�availability�check�
Complaints�
DN�=�Schedule�line�in�Returns�without�MRP�
DO�=Consignment�returns�
..�Availability�Check�
..�Movement�type�in�normal-PGI-601�
..�Movement�type�in�returns-651�
•�Schedule�line�cat.�Determination-sales�doc.�item�
categories�+�MRP�(MRP�1-�Mat.�master)�
•�A�Purchase�requisition�for�purchase�order�can�be��
generated�automatically�from�sales�order.�
•�You�can�deactivate�requirements�of�transfer�(MRP)��
and�availability�check�at�schedule�line�level.�
Bill�of�Materials�
•�The�item�in�BOM�are�controlled�in�sales�order��
differently�by�Sales�document�Item�Categories�
•�All�Items�in�the�bill�of�material�(BOM)�that�you��
want�to�control�in�the�sales�document�must�be�
Flagged�as�relevant�for�sale.�Hence�you�should�
create�a�BOM�material�with�BOM�usage�5�(SD),�all�
The�items�in�bill�of�material�will�be�automatically�
-----------------------�Page�19-----------------------
flagged�as�relevant�to�sales.�
•�The�BOM�appears�in�the�sales�document�as�a��
structure�with�main�item�and�sub-items.�The�
system�
Explodes�the�BOMs�in�the�sales�order�by�
automatically�generating�sub-items�for�the�
components.�
•�Item�category�group�in�Material�Master�for�main��
item�–ERLA,�Main�item�is�priced�and�sub�item�is�
not�priced.�Item�category�of�main�item-�TAQ�and�
Sub�Item-TAE�
•�Item�category�group�in�Material�Master�for�main�
item�–LUMF,�Main�item�is�not�priced�and�sub�item�is�
priced.�Item�category�of�main�item-�TAP�and�Sub�
Item-TAN�
Availability�check�
•�An�Availability�check�is�carried�out�during�sales��
order�processing.�
•�An�availability�check�occurs�if-�
..�The�Material�requires�an�availability�check-in�
material�master�(Gen./Plant�or�MRP�3)�
..�The�Material�availability�checks�in�customizing-�
Delivery�item�Categories�and�Schedule�line�
categories.�
•�Availability�is�checked�on�material�availability�date.��
The�material�availability�date�is�determined�from�
-----------------------�Page�20-----------------------
delivery�scheduling,�on�this�date�enough�material�
has�to�be�available�in�time�for�
delivery�to�the�customer�for�their�requested�date.�
•�In�Customizing,�you�can�configure�which�inward��
and�outward�movements�are�to�be�considered�in�
availability�check.�
•�Communication�between�sales�and�distribution�and��
Procurement�is�carried�out�via�requirements.�The�
transfer�of�requirements�type�can�be�influence�the�
availability�check.�
•�Any�agreements�made�with�customer�about��
deliveries�also�affect�the�result�of�the�availability�
check.�
Example-complete/partial�deliveries.�
•�The�indicator�for�controlling�complete/partial��
deliveries�is�proposed�from�the�customer�master�
records.�The�proposal�for�the�item�level�comes�from�
the�customer-material�information�record,�if�
a�customer�and�material�agreement�maintained�
there.�These�indicators�can�be�changed�manually�
during�order�entry.�
•�The�availability�check�includes-�
..�Current�stock�
..�Inward�movement�
..�Outward�movement�
-----------------------�Page�21-----------------------
Backorder�processing�
•�An�order�item�is�backdated�if�
..�The�quantity�of�an�order�item�is�not�totally�
confirmed.�
..�The�request�delivery�date�for�an�order�item�cannot�
be�kept.�
•�There�are�two�type�of�backorder�processing�
..�Manually-�From�list�sales�order�processes�them�
manually�with�reference�to�confirmation�(Short�
fall�can�be�cleared).�
..�Via�Rescheduling-�We�can�use�the�delivery�priority�
(proposed�from�the�customer�master)�and�
make�new�order�and�confirmation�date�by�
scheduling.�
Shipment�or�Delivery�scheduling�
•�Different�Times�involved�in�delivery�scheduling-�
..�Pick/Pack�Time�
..�Loading�Time�
..�Transportation�Lead�Time�
..�Transit�Time�
•�Backward�scheduling-The�customer�request�
delivery�date�is�used�to�calculate�the�material�
availability�date�and�transportation�lead-time.�The�
delivery�must�be�created�on�the�earlier�of�two�
dates,�if�both�date�are�after�the�order�date,�the�
customer‟s�requested�delivery�date�can�be��
-----------------------�Page�22-----------------------
confirmed.�
•�Forward�scheduling-�If�both�of�dates�not�come�
after�order�date,�customer�request�delivery�date�
cannot�be�confirmed.�Now�system�confirm�the�
quantity�on�the�basis�of�New�Material�availability�
date,�the�earliest�date�at�which�the�material�is�
available�in�the�warehouse.�
..�Two�schedule�line�are�generated�for�the�sale�line�
itemo�
The�date�of�the�first�schedule�line�corresponds�to�the�
customer‟s�required�delivery�date�and�
has�no�confirmed�quantity.�
o�The�date�of�schedule�line�shows�the�confirmed�
delivery�date�and�the�confirmed�quantity.�
Assembly�processing�[Make�to�Order]�
Make�to�Order�without�assembly�processing-�
..Production�Order�is�generated�from�planned�order.�
..Make�to�order�without�assembly�processing�is�
characterized�by�the�fact�that�materials�are�not�
available�in�the�warehouse�but�produced�especially�
for�a�particular�sales�order.�
..An�individual�Customer�requirement�is�generated�
from�the�sales�order�item�and�transferred�to�
material�planning.�
..We�can�use�material�planning�run�to�plan�
requirements,�once�this�has�been�done�production�
-----------------------�Page�23-----------------------
is�
carried�out.�The�system�returns�the�confirmed�
quantity�and�delivery�date�from�production�order�to�
sales�order.�
..�After�the�product�has�been�manufacture,�goods�
receipt�is�posted�in�the�sales�order�stock�which�is�a�
special�stock,�and�which�can�only�be�used�for�a�
specific�sales�order.�
Make�to�Order�with�assembly�processing-�
..Production�Order�is�generated�from�sales�order�(No�
need�material�planning�run).�
..The�individual�components�for�the�final�product�
have�already�been�produced;�we�only�need�to�
assemble�the�component�according�to�the�
customer‟s�requirement.�
Complaints�processing�
•�You�can�create�The�Returns�or�a�Credit�memo��
request�or�a�Debit�memo�request�with�reference�
to�a�sales�order�or�a�Billing�document.�
•�A�Billing�Block�is�automatically�assigned�to�the��
credit�memo�request�or�debit�memo�request.�This�
prevents�immediate�billing.�
•�The�standard�returns�process�in�SAP�has�an�order��
related�Billing-Credit�memo.�Hence,�credit�memo�
generation�can�be�carried�out�independently�of�the�
inbound�delivery�of�returned�goods.�
-----------------------�Page�24-----------------------
•�You�create�the�Invoice�Correction�request�or��
credit/debit�memo�(without�credit/debit�memo�
request)�with�reference�to�the�Billing�Document.�
•�An�Invoice�correction�request�is�always�created��
with�reference�to�the�incorrect�billing�
document.�A�credit�memo�item�and�a�Debit�memo�
item�are�created�in�the�Invoice�correction�request�
for�every�item�in�the�incorrect�billing�Document.�
Change�can�only�be�carried�out�on�the�debit�memo�
items�(debit�memo�is�in�Change�mode,�you�can�put�
Correct�quantity�here).�It�always�delete�in�pair�
Sales�information�system�
•�With�Sales�Information�System�(SIS),�you�can��
compress�data�from�sales�document�to�obtain�
information.�
•�Sales�information�System�(SIS)�is�apart�of��
Logistics�information�systems�(LIS).�
•�List�fall�in�two�categories-�Online�List�and�Work�
list.�
..�Online�List-�
..�Provide�Data�for�document,�
..�Display�document�for�example-For�a�customer�or�
a�material,�with�a�specific�status.�
..�Allow�you�to�check�and�change�the�documents.�
..�Work�List-�
..�Display�activities�that�need�to�be�processed.�
-----------------------�Page�25-----------------------
..�Allow�you�to�organize�tasks�into�efficient�work�
units.�
..�Work�list�allows�you�to�select�certain�task�in�SD�
and�to�process�them�afterwards.�
..�You�select�the�task�according�to�area�of�
responsibility�on�various�selection�criteria�(such�
as�date,�organizational�element�or�customer).�
•�The�information�system�based�on�information��
structures.�These�are�special�statistic�table,�which�
contain�transactional�data�from�different�application.�
This�data�is�constantly�updated�by�system.�
•�Information�structure�contained�three�basic�type�of��
information:-�
Characteristics,�Period�Unit,�and�Key�Figures.�
•�Standard�information�structures�for�SD�available�in��
the�R/3�systems�are�from�S001�to�S006,�You�Can�
create�your�Own�Information�structure�in�
Customizing�using�the�name�range�S501�to�S999.�
•�Standard�Analysis:-�
..�A�variety�of�tools�are�available�that�allow�you�to�
analyze.�These�include,�for�example,�
Cumulative�Curves,�ABC�analysis,�time�series,�top-n�
evaluation,�and�comparison�option.�
..�The�analysis�is�based�on�the�information�structure.�
First,�you�select�the�required�data�scope�
depending�on�the�characteristics�and�period�of�
-----------------------�Page�26-----------------------
information�structure.�This�data�is�first�displayed�
in�basic�list,�which�can�be�drilled�down�to�display�
different�characteristics.�
•�Flexible�Analysis:-�
..�Flexible�analysis�in�LIS�allow�you�to�determine�
which�data�in�which�format�is�combined�to�
create�an�individual�report.�
..�With�Flexible�Analysis�you�can�combine�
characteristics�and�key�figures�from�different�
information�structure�in�one�list.�
Data�flow�
•�Information�is�transferred�from�the�preceding��
document�to�subsequent�document.�
•�Describes�the�mapping�of�business�process�in�sales��
by�creation�of�sales�document�with�reference�of�
preceding�document,�this�enable�document�flows�to�
be�built�up�that�describe�business�process.�
•�This�allows�you�to�copy�partial�quantities�or�all�the��
item�and�quantities�in�reference�document�
directly�by�choosing�Item�selection.�You�can�select�
certain�items�and�can�change�quantities�before�
they�are�copied.�
Document�Flow�
•�A�sales�process�is�made�up�of�the�sequence�of��
individual�process�steps,�recorded�as�documents;�
this�
-----------------------�Page�27-----------------------
process�chain�is�stored�in�the�document�flow.�
•�You�can�view�all�the�documents�within�the��
document�flow�in�a�list,�you�can�branch�to�individual�
documents�by�double�clicking�and�to�display�of�a�
document�and�then�return�to�document�flow.�
•�In�status�overview�in�document�flow,�you�can��
quickly�find�detailed�information�about�current�
status�
of�SD�process.�
•�Document�flow�updated,�when�indicator�“update��
doc.�Flow”�is�set�in�Copying�Control.�
Special�Business�transaction�
Rush�sale�
..�Sales�from�Plant�Scenario.�
..�Sales�document�type-RO�
..�Delivery�Type-LF�
..�Standard�item�category-�TAN�[RO+NORM]�
..�Billing�Type-F2�[Delivery�related]�
..�Immediate�Delivery�switch�Checked�
..�Once�the�goods�have�been�withdrawn�from�the�
warehouse,�Picking�and�posting�goods�issue�can�
begin.�
Cash�Sale�
..�Sales�from�Plant�Scenario.�
..�Sales�document�type-CS�
..�Delivery�Type-BV�
-----------------------�Page�28-----------------------
..�Standard�item�category-�BVN�[CS+NORM]�
..�Billing�Type-BV�[Order�related]�
..�Immediate�Delivery�switch�Checked�
..�Once�the�goods�have�been�withdrawn�from�the�
warehouse,�Picking�and�posting�goods�issue�can�
begin.�
Consignment�processing�
•�In�consignment�processing,�goods�are�delivered�to��
thr�customer�but�remain�the�property�of�company�
in�special�consignment�stock,�however�they�actually�
used.�
•�An�invoice�is�not�created�until�the�customer-�
withdrawn�goods�from�consignment�stock.�Up�Till�
that�
point,�the�customer�has�the�right�to�return�
consignment�stock.�
•�Scenario�
Order�Delivery�Picking�Goods�issue�Billing�
Fill�up�(CF)�YES�YES�YES�YES�NO�
Issue�(CI)�YES�YES�NO�YES�YES�
Pickup�(CP)�YES�YES�NO�YES�NO�
Returns(CONR)�YES�YES�NO�YES�YES�
Delivery�free�of�charge�and�subsequent�deliveries�
•�Delivery�free-�of-charge�[FD].�Item�category�is�
KLN�[with�FD�+�NORM].�KLN�is�not�relevant�for�
pricing�
-----------------------�Page�29-----------------------
•�Subsequent�Delivery�Free�of�charge�[SDF]�has��
reference�mandatory�to�a�preceding�sales�
document.�
Item�category�is�KLN�[with�SDF�+�NORM].KLN�is�not�
relevant�for�pricing�
Partner�Determination�
..�Customer�master�
..�Sales�document�header�
..�Sales�document�item�
..�Delivery�Type�
..�Shipment�Type�
..�Billing�Header�
..�Billing�Item�
..�Sales�Activities�
Incompleteness�
•�It�presents�the�function�of�the�incompleteness��
check.�As�part�of�editing�sales�documents,�the�
system�
can�check�whether�all�necessary�information�has�
been�defined�in�document,�if�not�document�is�
incomplete.�
•�Incompletion�Log-�The�incompletion�log�is�a�list�of�
containing�all�information�that�has�been�
defined�as�relevant�for�the�sales�document,�that�has�
not�been�processed�during�sales�document�
processing.�
-----------------------�Page�30-----------------------
•�This�list�can�be�called�and�processed�manually�or��
automatically�on�saving�the�sales�document.�
•�We�define�these�data�fields�in�customizing�for��
incompleteness�Log.�
•�Incompleteness�Log�Function�available�for-�
..�Sales-�Header�
..�Sales-�Item�
SAP�SD�IMP�NOTES�
Manoj�Kumar�
SAP�SD�Certified�Consultant�
E-Mail:�[email protected]�
..�Sales-�Schedule�Line�
..�Partner�
..�Sales�activities�
..�Delivery�header�
..�Delivery�Item�
Outline�agreement�
Two�types-�Contracts�and�Scheduling�agreements�
Scheduling�agreement�
•�The�Scheduling�agreement�contains�fixed�delivery�
dates�and�quantity�and�is�valid�for�a�certain�
period�of�time.�
•�When�you�enter�schedule�line�for�the�item�in�the��
scheduling�agreement,�the�system�adds�up�the�
-----------------------�Page�31-----------------------
quantities�that�have�already�been�entered�and�
compare�them�both�the�target�quantity�and�the�
quantity�already�shipped.�This�give�you�an�overview�
of�all�the�open�quantity,�if�the�quantity�in�
schedule�line�exceeds�the�target�quantity,�system�
issue�a�warning�message.�
Contracts�
Two�Types-Quantity�contract�and�value�contract�
•�The�contract�does�not�contain�any�schedule�line,�
delivery�quantities�or�delivery�date.�It�is�valid�
for�a�certain�period�of�time.�
•�Release�orders�are�created�with�reference�to�a��
contract.�Schedule�lines�are�created�in�the�release�
order�
when�it�is�placed.�You�can�choose�materials�directly�
or�by�exploding�an�assortment�module�(list�of�
valid�materials-Master�data�for�product).�
•�You�can�create�release�order�in�any�currency�and��
the�total�value�is�updated�in�the�currency�of�the�
contract.�
•�The�value�of�release�order�is�compared�with�value�
still�open�in�the�contract.�You�can�define�how�the�
system�responds�when�this�value�is�exceeded�(sales�
document�type)�
•�A�value�contract�defines�that�your�customer�agrees��
to�purchase�a�fixed�total�value�(target�amount)�of�
-----------------------�Page�32-----------------------
goods�and�services�during�the�defined�period.�
•�You�can�have�partner�function�AA�as�optional�sold��
to�party�and�AW�as�optional�ship�to�party�in�the�
standard�system.�
•�You�can�maintain�contract�data�at�both�header�and��
item�level�in�the�sales�document.�
•�If�you�assign�a�contract�profile�to�the�sales�
document�type,�the�system�automatically�determine�
default�
values�specific�to�the�contract.�These�could�be:�
..�Rule�for�determining�start�and�end�of�the�contract�
..�Duration�category�
..�Subsequent�activities�
..�Cancellation�procedure�
Material�Determination�
•�Material�determination�provides�you�with�a�tool�for��
automatic�exchange�of�material�in�sales�
document.�
•�Material�determination�is�carried�out�by�condition��
technique.�You�do�not�need�a�material�master�
record�for�the�material�number�that�you�are�
replacing.�
•�You�can�assign�a�substitution�reason�to�every��
master�record�in�material�determination�that�
defines�
how�the�material�should�be�determined.�
-----------------------�Page�33-----------------------
•�In�standard�system�reason�for�substitution�0005�is��
for�manual�product�selection�and�0004/0006�is�for�
automatic�product�selection.�If�automatic�product�
selection�is�used,�the�system�may�display�(based�
on�customizing)�the�entered�and�substitute�material�
as�main�and�sub-items�in�sales�order.�
•�Item�data�sales�A�contain�information�about�
material�that�was�originally�entered�and�reason�for�
substitution.�
•�You�can�use�product�attributes�in�material�master��
and�customer�master�records�to�exclude�a�
particular�material�from�product�list.�
•�You�can�re-run�material�determination�when�
delivery�is�created.�If�material�determination�is�
rerunning,�
the�result�of�the�substitution�may�change�due�to�
new�availability�situation.�
•�You�can�assign�a�material�determination�procedure��
to�each�sales�document�type.�
Listing�
•�Make�sure�that�your�customer�receives�only�
specific�materials.�You�enter�these�materials�as�a�
material�listing.�
•�The�material�listing�is�controlled�by�condition��
technique.�
•�You�define�in�sales�document�type�whether�the��
-----------------------�Page�34-----------------------
system�checks�the�material�listing�or�not.�
Exclusion�
•�Make�sure�that�the�customer�does�not�receive��
certain�materials.�You�enter�these�materials�as�a�
material�exclusion.�
•�The�material�exclusion�also�controlled�by�condition��
technique.�
Free�Goods�
•�Condition�technique�is�used�for�free�good�
determination.�
•�For�free�goods�determination�system�uses-�
..�Sales�area�
..�Document�determination�procedure�(Sales�
document�type)�
..�Customer�determination�procedure�(Customer�
master�data)�
•�Free�goods�can�be�part�of�the�order�quantity�not��
included�in�the�invoice.�This�is�called�an�inclusive�
bonus�quantity.�The�order�goods�and�the�free�goods�
both�involve�the�same�material.�The�quantity�
units�of�the�free�goods�and�ordered�goods�must�be�
same.�
•�In�inclusive�bonus�quantities,�the�extra�goods�are��
delivered�free�of�charge�and�not�typically�his�
included�in�the�invoice.�This�can�either�be�an�
additional�quantity�of�the�goods�ordered�or�it�can�be�
-----------------------�Page�35-----------------------
another�article.�The�exclusive�free�goods�appear�in�
the�sales�document�as�an�individual,�free-�ofcharge�
item.�
•�The�system�re-reads�the�free�goods�master�record�
in�the�sales�order�if�the�quantities�in�the�main�item�
change�or�if�the�pricing�date�changes.�The�system�
then�deletes�the�sub-items�and�re-creates�them.�
Any�manual�changes�to�the�free�goods�quantity�are�
lost.�If�pricing�is�re-run�in�the�sales�order,�it�
does�not�affect�the�free�goods�determination.�
DELIVERY�
•�Each�outbound�delivery�starts�at�a�shipping�point,��
continues�along�a�route,�and�has�ship�to�party�as�
the�destination.�These�elements�are�header�fields�in�
the�outbound�delivery.�
•�The�SAP�system�supports�the�following�function��
within�shipping�processing:�
..�Monitoring�of�deadlines�for�reference�document�
due�for�shipping�
..�Creation�and�processing�of�outbound�deliveries�
..�Monitoring�of�goods�availability�
..�Monitoring�of�capacity�situation�in�the�warehouse�
..�Support�for�picking�(With�link�to�the�warehouse�
management�system)�
..�Packing�of�outbound�delivery�
..�Printing�and�distribution�of�shipping�documents�
-----------------------�Page�36-----------------------
..�Processing�of�goods�issue�
..�Controlling�through�overviews�of�
..�-Outbound�deliveries�currently�in�process�
..�-Activities�still�to�be�performed�
..�-Possible�bottlenecks�
Logistics�Execution�
•�The�logistics�process�in�a�company�that�covers�the��
entire�process�chain�from�the�vendor�through�
the�company�warehouse,�production�facilities,�and�
distribution�centers�to�the�customer.�
•�LE�process�includes-�
..�The�goods�receipt�process�
..�The�goods�issue�process�
..�Internal�warehouse�process�
..�The�transportation�process�
Organizational�structure:�logistics�
Plant,�Storage�location,�Warehouse�number,�
Shipping�point�
•�You�can�model�the�structure�of�a�corporate�group��
by�using�Client�and�Company�codes.�A�client�is�
often�synonymous�with�a�corporate�group,�while�a�
company�code�represents�an�independent�
accounting�unit.�Company�codes�are�legally�
independent�from�one�another.�
•�The�plant�plays�a�central�role�in�logistics.�A�plant�is��
a�production�facility�or�a�location�that�handles�
-----------------------�Page�37-----------------------
material�stock.�It�could�be�a�collection�of�several�
locations�in�one�general�vicinity�with�material�stock,�
which�are�known�as�storage�location.�Stock�is�
managed�at�the�level�of�the�storage�location.�
•�Inventory�valuation�is�done�either�at�company��
code�level�or�Plant�level,�however�the�stock�is�
managed�
at�storage�location�level.�
•�Several�storage�locations�within�a�plant�can�refer��
to�the�same�warehouse�number.�As�a�result,�they�
form�the�warehouse�complex�from�the�point�of�view�
of�inventory�management�
•�The�connection�of�organizational�units�in�the��
warehouse�to�MM�inventory�management�results�
from�
the�assignment�of�warehouse�number�to�a�
combination�of�plant�and�storage�location.�
•The�organizational�unit�of�WM-�warehouse�number,�
storage�type,�picking�are,�staging�area�and�
door.�You�can�activate�lean�WM�in�customizing�at�
the�warehouse�number.�
•�A�shipping�point�is�an�independent�organizational��
unit�at�a�fixed�location�that�process�and�monitor�
outbound�deliveries�and�goods�issue.�The�shipping�
point�is�directly�under�the�client�level.�
•�An�outbound�delivery�is�processed�from�a�single��
-----------------------�Page�38-----------------------
shipping�point.�The�responsible�shipping�point�is�
determined�in�the�order�at�item�level.�
•�A�shipping�point�may�also�be�set�as�a�goods��
receipt�point,�which�means�it�can�also�be�used�for�
inbound�deliveries.�
Structure�Delivery�document�
•�A�delivery�Document�has�two�level-�Header�and�
Item.�There�is�no�schedule�line.�The�reason�is�
each�schedule�line�in�the�sales�order�can�become�an�
item�in�delivery�document.�
Delivery�type�control�
..�Rule�for�determining�storage�location-(MALA,�
RETA,�MARE)�
..�Text,�partner,�output�determination�procedure�
..�Route�re-determination�
..�Delivery�split�by�warehouse�number�
..�Delivery�split�by�partner�
..�Automatic�packing�
..�Order�reference�
Delivery�item�category�controls�
..�Check�zero�quantity�
..�Check�minimum�quantity�
..�Check�over�delivery�
..�Availability�check�control�
..�Picking�relevance�
..�Determine�storage�location�
-----------------------�Page�39-----------------------
..�Automatic�batch�determination�
..�Packing�control�
..�Text�determination�procedure�
Coping�control-Delivery�
•�Update�document�flow�
•�In�copying�control�table�you�specify:�
..�Which�sales�and�distribution�document�types�can�
be�copied�to�which�delivery�type?�
..�Which�item�categories�are�copied�from�reference�
document?�
•�You�can�also�specify�
..�Under�what�condition�data�is�copied�from�the�
order�to�the�outbound�delivery.�
..�Under�what�condition�several�orders�can�be�
combined�in�an�outbound�delivery.�
..�Which�data�to�be�transfer?�
..�Whether�the�reference�should�be�recorded�in�the�
document�flow.�
..�When�you�copy�an�order�item�to�a�delivery,�the�
system�copies�the�item�category�of�the�order�item�
to�the�delivery.�An�item�category�is�not�specified�for�
order-independent�items�in�the�delivery�(for�
example-�packing�material),�for�deliveries�without�
reference�to�an�order�(Delivery�type�LO).�In�
such�case�the�item�category�determine�take�place�on�
the�basis�of�customizing�setting�which�is�
-----------------------�Page�40-----------------------
same�as�that�of�sales�document�item�category.�
..�Delivery�item�category�det.�-�delivery�document�
type�+�item�category�group�+�usages�
[DLN�(standard�item�without�order)�-�LO+NORM]�
Route�determination�
•�Route�determination�is�carried�out�in�sales�order��
item�and�depends�on:�
..�The�departure�zone-�shipping�point�(customizing)�
..�Shipping�condition-sales�document�type�or�sold�to�
party�
..�The�transportation�zone-�ship�to�party�(shipping�
tab)�
..�The�transportation�group-material�master�
(general/plant)�
•�In�the�order�item,�you�can�manually�overwrite�the��
route�that�is�determined.�
•�You�can�re-determine�the�route�in�the�outbound�
delivery�based�on�the�weight�(weight�group).�
Whether�the�route�is�re-determined�depends�on�the�
configuration�of�the�delivery�type.�
Shipment�or�Delivery�scheduling�
•�Different�Times�involved�in�delivery�scheduling-�
..�Pick/Pack�Time�
..�Loading�Time�
..�Transportation�Time�
..�Transit�Time�
-----------------------�Page�41-----------------------
•�Shipping�point�calculate:�-�Pick/Pack�Time,�Loading�
Time�
•�Route�calculate:�-�Transportation�Time,�Transit�
Time�
Backward�scheduling-�system�confirms�the�quantity�
of�delivery�on�the�basis�of�customer�request�
delivery�date.�
Forward�scheduling-�system�confirms�the�quantity�
on�the�basis�of�New�Material�availability�date.�
Precise�scheduling-the�system�calculates�and�
displays�the�results�of�scheduling�down�to�minute.�If�
you�
have�maintained�the�working�times�of�the�shipping�
point,�the�system�performs�precise�scheduling.�
Daily�scheduling:�-�the�system�uses�days,�hours,�
and�minutes�for�calculation,�but�only�displays�the�
resulting�dates.�
Route�schedule:�-�the�route�is�used�to�determine�the�
transportation�lead-time�and�transit�time.�For�
Transportation�lead-time�precise�scheduling�uses�the�
working�times�of�the�shipping�point;�daily�
scheduling�
uses�the�factory�calendar�of�the�shipping�point.�For�
the�transit�time�both�types�of�scheduling�use�the�
factory�calendar�of�the�route�to�determine�when�
route�is�used.�
-----------------------�Page�42-----------------------
..�You�can�use�the�route�schedule�to�organize�
outbound�deliveries�from�a�particular�
shipping�point�to�different�ship�to�party.�
..�The�route�schedule�generally�contains:�Route,�
Departure�date�and�time,�list�of�ship�to�party�
and�itinerary�(optional)�
..�You�can�use�route�schedules�in�sales�order,�stock�
transfer�and�outbound�deliveries.�
..�In�customizing,�you�define�whether�a�route�
schedule�should�be�assigned�for�each�shipping�
point,�order�type,�purchasing�doc.�type�(Delivering�
plant)�and�delivery�type.�
Picking�location�/�storage�location�determination:�-�
MALA,�RETA,�MARE�
•�MALA:�-�determination�based�on�the�shipping�
point,�the�delivering�plant,�and�the�storage�
location�(Material�master-plant�data/storage�1)�
•�RETA:�-�Determination�based�on�the�delivering�
plant,�situation,�the�storage�condition.�
•�MARE:�-�First�MALA�then�RETA�
Options�for�creating�Outbound�Deliveries�
•�Each�outbound�delivery�starts�at�a�shipping�point,��
continues�along�a�route,�and�has�the�ship�to�party�
as�the�destination.�These�elements�are�header�fields�
in�outbound�delivery.�
•�You�can�store�delivery�agreements�using�the��
-----------------------�Page�43-----------------------
indicators�in�the�customer�master�record�of�sold�to�
party�
or�in�the�customer�material�information.�
•�If�the�customer�allow�order�to�be�combined,�the�
R/3�system�combines�orders�when�creating�the�
delivery�due�list.�For�this�the�following�
characteristics�should�be�same:�
•�Shipping�point,�Delivery�due�date,�Ship�to�party,��
Incoterm,�Route�
•�You�can�create�an�outbound�delivery�manually�
with�or�with�out�reference�to�a�particular�order.�
However,�if�you�create�a�delivery�manually,�you�
cannot�deliver�purchase�order�or�other�request.�
Delivery�due�list�
•�The�delivery�due�list�is�a�work�list�of�all�operations��
requiring�deliveries�
Shipment�
•�If�you�use�transportation�functions,�outbound��
deliveries�are�grouped�together�on�the�basis�of�
user-defined�criteria�in�a�document�called�the�
shipment�document.�
•�Shipment�function�is�optional.�You�can�create�a��
shipment�after�delivery�creation�or�after�PGI.�
You�can�invoice�the�customer�for�shipment�cost.�
Out�bound�delivery�monitor�
•�The�outbound�delivery�monitor�displays�all��
-----------------------�Page�44-----------------------
deliveries�that�are�still�to�be�processed�or�that�
have�just�been�processed.�
•�You�can�use�the�outbound�delivery�monitor�to�
execute�important�follow-on-functions�in�collective�
processing�in�the�background�(�for�example-transfer�
orde�creation�for�picking,�or�posting�of�goods�
issue).�
Transfer�order�
•�A�transfer�order�is�an�instruction�to�move�material��
from�a�source�storage�bin�to�a�destination�
storage�bin�within�a�warehouse�complex.�
•�The�transfer�order�include�the�information�like-�
material�number,�quantity�to�be�moved,�source�
and�storage�bin.�
•�With�WM�precise�inventory�management�at�the��
level�of�the�storage�bin�is�possible�and�used�for�
warehouse�with�random�storage.�This�is�not�possible�
with�lean�WM�and�hence�suitable�for�fixed�
bin�warehouse.�
•�You�can�Group�Transfer�order�based�on�the��
warehouse�number.�
•�Automatic�or�direct�creation�of�transfer�order�if�the�
systems�determine�output�type�WMTA�at�
the�header�level�of�outbound�delivery�when�delivery�
is�being�created.�
Batch�management�setting-�
-----------------------�Page�45-----------------------
•�Material�master-Plant/storage�1�view�and�
purchasing�view-�Activate�batch�management.�
•�In�customizing-�delivery�item�category,�sales�item�
categories�(automatic�batch�determination)�
when�delivering�a�sales�order,�this�batch�is�copied�to�
outbound�delivery.�Then�you�cannot�
change�batch�in�outbound�delivery.�
•�If�a�batch�has�not�been�specified�in�the�sales��
order,�you�can�enter�one�in�the�picking�overview�
screen�of�the�outbound�delivery.�You�must�specify�a�
batch�before�goods�issue.�
•�Batch�split�function�is�used�if�delivery�quantities�of��
an�item�are�to�be�taken�from�different�
batches.�It�can�be�done�manually�in�batch�split�
screen�of�delivery�item�or�automatically�using�
automatic�batch�determination,�for�this�customizing�
is�done�in�delivery�item�category.�
Serial�number�
•�You�can�assign�a�unique�serial�number�to�each��
material.�This�is�allows�you�to�monitor�goods�
movement�for�individual�materials.�
•�To�use�serial�numbers,�enter�serial�number�profiles��
in�the�material�master�record�(general/plant�
and�Plant�data/storage-2).�
•�Serial�number�is�specified�in�the�delivery�item�or��
the�order.�
-----------------------�Page�46-----------------------
•�You�must�specified�serial�number�before�posting�
goods�issue.�
Shipping�related�condition�
•�The�outbound�delivery�can�contain�shipping-�
related�condition�at�header�level.�
•�You�can�use�the�SD�pricing�technique.�
•�Assign�the�pricing�procedure�to�the�delivery�type�
Delivery�split�
•�When�you�split�a�delivery,�you�create�one�or�more��
new�deliveries,�called�result�and�the�reminder.�
•�When�you�call�the�delivery�split,�specify�a�split��
profile�to�determine�the�type�of�split.�Split�profiles�
are�
define�in�customizing,�and�assign�to�delivery�type.�
..�Delivery�split�by�warehouse�number�
..�Delivery�split�by�partner�
Packing�
•�The�packing�function�is�available�in�–Order�(as�
packing�proposal),�In�the�inbound�delivery,�In�the�
outbound�delivery,�In�the�shipment�document.�
Packing�control-�
•You�define�packaging�material�type�and�packaging��
material�group.�Assign�packaging�material�
type�to�packaging�material�group.�Choose�material�
type�VERP�for�material�master�and�maintain�the�
packaging�material�group�in�basic�data�1�and�sales:�
-----------------------�Page�47-----------------------
general/plant�views.�However,�if�this�field�has�
not�been�maintain�in�the�material�master,�this�
material�can�be�packed�in�any�packaging�material�
depending�on�the�weight�and�volume.�
•�The�system�can�generate�a�separate�item�in��
outbound�delivery�for�each�packaging�material.�For�
this-�
..�You�must�set�item�category�determination�in�
customizing.�In�this�context,�table�entries�with�
PACK�usage�are�relevant.�
..�The�delivering�plant�must�be�determined�using�the�
plant�determination�rule�in�the�
packaging�material�type�or�must�be�entered�
manually.�
..�If�you�want�to�bill�the�customer�for�packaging�
material,�item�category�should�be�determined�as�
DLN.�
..�If�you�use�returnable�packaging�material,�you�
must�create�them�in�the�material�master�with�item�
category�group�LEIH�(item�category�TAL�is�
determined).�When�goods�issue�is�posted,�the�
material�is�transferred�to�special�stock�for�the�
customer.�
Goods�issue�
•�Posting�goods�issue�involves�an�interface�with�FI��
as�stock�valuation�changes.�
-----------------------�Page�48-----------------------
•�After�goods�issue�has�been�posted,�there�is�limited�
scope�for�changing�the�outbound�delivery.�
•�The�prerequisites�for�posting�goods�issue�is�that��
picking-relevant�item�are�completely�picked�
(transfer�
order�is�confirmed).�This�means�that�the�delivery�
quantity�and�the�picked�quantity�in�the�outbound�
delivery�must�be�same.�
•�Goods�issue�can�be�posted�by�changing�a�single��
outbound�delivery,�by�collective�processing�
function�to�select�all�deliveries�for�which�goods�issue�
is�due�to�be�posted,�can�also�use�the�outbound�
delivery�monitor�to�do�this�and�at�the�time�of�
transfer�order�creation�(to�choosing�adobe�quantity�
2)�
•�Any�errors�are�logged�when,�for�example,�data��
such�as�the�batch�or�serial�number�is�missing�or�
when�picking�has�not�been�carried�out�fully�for�these�
items.�In�this�case,�goods�issue�is�not�posted.�
•�The�goods�movement�is�controlled�by�“Movement��
type-601”�(schedule�line)�
Effect�after�goods�issue-�
..�Reduce�warehouse�stock�
..�Post�the�value�change�to�the�stock�accounts�in�
inventory�accounting�
..�Enter�status�information�in�the�outbound�delivery.�
-----------------------�Page�49-----------------------
..�Reduce�delivery�requirement.�
..�Is�store�in�document�flow�and�update�status�of�
preceding�document�
..�Create�work�list�for�billing.�
Cancel�goods�issue�
•�If�goods�issue�for�an�outbound�delivery�is��
canceled,�the�goods�issue�posting�is�reset.�The�
system�
copies�the�quantities�and�value�from�the�original�
goods�issue�document�and�carry�out�an�inventory�
posting�based�on�these�quantities�and�values�with�a�
reversed�+/-�sign.�
•�If�the�outbound�delivery�has�been�fully�or�partially�
billed�you�must�first�cancel�the�billing�document,�
then�you�cancel�goods�issue.�
•�After�goods�issue�has�been�canceled,�the�goods��
movement�status�of�the�outbound�delivery�is�reset�
to�
“Not�yet�started”.�This�allows�you�to�further�process��
the�outbound�delivery�(Goods�issue)�as�usual.�
•�For�each�movement�type�in�inventory��
management,�you�must�define�a�reversal�movement�
type�
in�customizing.�No�additional�settings�are�required�
for�movement�types�used�for�goods�issue�posting.�
-----------------------�Page�50-----------------------
Quality�management�
•�You�specify�in�the�quality�management�view�of�the�
material�master�if�a�quality�inspection�is�to�be�
carried�out�for�the�material.�When�the�outbound�
delivery�is�created�in�SD,�QM�automatically�creates�
an�inspection�lot�for�the�delivery�items�that�are�
relevant�for�inspection.�The�usage�decision�
represents�
the�completion�of�a�QM�inspection.�Depending�on�
the�customer,�or�on�the�customer�and�the�material�
together,�you�can�specify�if�the�inspection�log�must�
be�accepted�before�goods�issue�can�be�posted.�You�
initiate�printing�of�a�certificate�of�quality�from�output�
control�of�the�outbound�delivery�at�item�level.�
POD�settings�
•�You�need�to�define�which�delivery�item�categories��
are�relevant�for�the�POD�process.�You�also�need�
to�define�reason�for�deviation,�and�in�the�customer�
master�data�(sales�area-�shipping�tab)�specify�
POD�relevance.�
•�The�system�creates�the�billing�document�based�on��
the�correct�(verified)�quantity.�The�creation�of�a�
billing�document�using�the�billing�due�list�is�blocked�
until�proof�of�delivery�has�been�confirmed.�
TAB�PAGES�IN�DELIVERY�DOCUMENT�
Overview:�-�Item�overview,�Picking,�Loading,�
-----------------------�Page�51-----------------------
Transport,�Status�overview,�Goods�movement�data.�
VARIOUS�COLUMNS�IN�PRICING�PROCEDURE�
(RVAA01)�
Step,�Condition�counter,�Condition�type,�Description�
(condition,�From,�To,�Manual,�mandatory,�
Statistic,�Print�(X-print�of�item�level),�Subtotal�
(reference�level),�Requirement,�AltCty�(Routine),�
AltCBV�(Routine),�Account�Key�(ERL,�ERS),�account�
key-�accruals�
Step-�
Condition�counter-�
..�Access�number�of�the�conditions�within�a�step�in�
the�pricing�procedure.�
..�During�automatic�pricing,�the�system�takes�in�to�
account,�the�sequence�specified�by�the�
counter.�
PRICING�
The�term�price�book�refers�to�a�price�determination�
strategy.�
Condition�records�
•�Condition�records�based�on�key�fields�(combination�
of�key�fields�called�condition�table)�
•�In�pricing�condition�records�you�can�have�a�validity��
period,�maintain�scale�and�specify�upper�and�
-----------------------�Page�52-----------------------
lower�limit�for�manual�changes.�Manual�changes�
only�in�this�specified�limit.�
•�You�can�define�unlimited�number�of�levels�in�a��
scale.�
•�You�can�do�mass�maintenance�of�conditions�which��
means�that�condition�records�can�now�be�
maintained�across�all�condition�type�and�condition�
tables.�
•New�condition�records�can�be�created�with�the�
reference�of�existing�condition�records.�Individual�
condition�records�can�be�maintained�manually.�
•New�price�function�allows�you�to�maintain�multiple��
condition�records�simultaneously.�
•�You�can�maintain�long�text�in�the�condition�records��
for�pricing�and�agreements�(rebates,�sales�deals�
and�promotions)�
Pricing�report�
•�To�provide�an�overview�of�existing�condition��
records.�You�can�generate�a�list�of�conditions�for�
analysis.�
•�When�you�creating�a�new�program�for�pricing��
report,�you�first�decide�in�which�views�you�want�to�
analyze�condition�records.�You�do�this�by�selecting�
specific�fields�from�the�existing�condition�tables.�
Depending�on�which�fields�are�selected,�the�system�
will�generate�a�list�of�tables,�which�contain�at�least�
-----------------------�Page�53-----------------------
one�of�the�selected�field�catalogues.�From�this�list�of�
tables,�select�which�tables�will�appear�in�the�
report.�
Condition�indexes�
•�You�can�create�and�use�condition�indexes�to��
search�for�condition�records�that�were�created�for�a�
variety�of�condition�type�and�condition�table.�Before�
you�can�use�the�indexes�that�are�delivered�in�
the�standard�version,�you�must�first�activate�them�in�
customizing�for�sales.�However,�if�you�create�your�
own�indexes,�the�system�automatically�activates�
each�new�index�when�you�generate�it.�
Condition�table�
•�Condition�table�is�a�combination�of�fields,�which��
form�key�for�a�condition�record.�
•�Each�condition�table�defines�under�access��
sequence.�
•�All�fields,�which�are�to�be�used�for�creating�a��
condition�table,�must�be�contained�in�the�field�
catalogue.�
It�is�possible�to�add�additional�fields�to�this�
catalogue.�
Release�procedure�
•�You�can�allow�a�release�procedure�to�be�used��
when�a�condition�table�is�created�by�selecting�the�
with�
-----------------------�Page�54-----------------------
release�status�checkbox.�This�adds�the�following�
fields�to�the�condition�table�automatically.�
..�KFRST-Release�status�as�last�key�field�
..�KBSTAT-�Processing�status�as�a�field�of�the�
variable�data�part�(non�key�field)�
•�“The�release�status�is�set�indirectly�by�defining�a��
processing�status�in�customizing�for�pricing�and�
assigning�a�release�status�to�the�processing�status”�
•�Different�statuses�are�
..�Released�
..�Blocked�
..�Released�for�price�simulation�
..�Released�for�planning�and�price�simulation.�
Access�sequence�
•�An�access�sequence�(search�strategy)�is�defined�
for�each�condition�type�(except�header�and�manual�
condition�type)�in�pricing�procedure.�
•�Each�access�performed�during�pricing�procedure,��
the�access�sequence�is�made�using�condition�table.�
•�Access�sequence�is�a�search�key�for�condition��
record,�which�made�up�of�key�fields.�
Condition�type�
•�The�condition�type�determines�the�category�of�a��
condition�and�describes�how�the�condition�is�used.�
•�The�calculation�type�and�scale�base�type�can�be��
controlled�for�each�condition�type.�
-----------------------�Page�55-----------------------
•�Conditions:�-�Price,�discount/surcharges,�freight,�
taxes�
•�Each�condition�type�you�can�be�set�as�an��
automatic�surcharge,�discount�or�either.�
•�As�well�as�being�determined�automatically,��
condition�can�also�be�entered�manually�in�the�sales�
document.�You�can�prevent�one�condition�type�from�
being�changed�manually�by�making�setting�in�
customizing.�
Header�condition�(E.g.�HM00,�AMIW)�
•�Header�conditions�are�valid�for�all�items.�These�are��
automatically�distributed�among�the�items�based�
on�net�value.�The�basis�for�distributing�the�header�
conditions�can�be�changed�in�the�pricing�procedure�
by�selecting�the�appropriate�routine�(e.g.�weight,�
volumes)�in�the�AltCBV�field�(alternative�formula�for�
condition�base�value)�
Special�pricing�functions�
•�Group�condition:-In�customizing�you�can�set�a�
condition�type�to�be�a�group�condition.�The�
condition�
base�value�(e.g.�weight)�is�then�calculated�as�the�
sum�of�the�individual�items�within�one�group.�E.g.-�
K029�
•�Group�condition�with�varying�keys:�-For�group�
conditions�with�varying�keys,�item�quantities�are�
-----------------------�Page�56-----------------------
accumulated�for�scale�point�determination�purpose�
but�the�rate�for�each�item�is�calculated�from�its�
individual�condition�record.�E.g.-K005�
•�Condition�update:�-Value�can�be�accumulated�in�
the�condition�records�and�tested�against�limits.�In�
this�
way,�you�can�set�a�maximum�condition�value,�
condition�base�value,�or�number�of�orders�for�a�
condition.�For�this�you�must�activate�condition�
update�switch�in�customizing�for�condition�type.�
[Then�
only�these�fields�visible�in�condition�records]�
•�Condition�supplements:�-Condition�supplements�
are�group�of�conditions,�which�are�accessed�
together�
during�pricing.�
•�Condition�exclusion�
..�Condition�exclusion�indicator�can�be�set�in�either�
the�condition�type�or�the�condition�
records.�
..�Condition�types�to�be�compared�are�first�placed�in�
an�exclusion�group.�During�pricing,�the�
conditions�which�result�in�the�best�price�(lowest�
charge�or�highest�discount)�are�selected�from�
this�group.�All�others�are�deactivated.�
-----------------------�Page�57-----------------------
Special�condition�type�
Manual�pricing:�-�(E.g.-HM00,�PN00)�
•�Header�condition�type�HM00�allows�you�to�enter��
the�order�value�manually.�The�new�order�value�is�
then�distributed�proportional�the�items,�taking�into�
account�the�previous�net�value.�Taxes�are�
determined�again�for�each�item.�
•�Item�condition�type�PN00�allows�you�to�specify�the�
net�price�for�an�item�manually.�The�original�
conditions�are�deactivated.�
Minimum�price:�-�(E.g.�AMIW,�PMIN)�
•�Header�condition�type�(AMIW):�-you�may�create�a�
minimum�value�for�each�order�using�condition�
type�AMIW.�If�the�value�in�the�order�header�is�less�
than�this�minimum�order�value�during�pricing,�the�
system�uses�the�minimum�as�the�net�order�value�
automatically.�The�minimum�order�value�is�a�
statistical�condition.�Condition�type�AMIW�is�a�group�
condition�and�is�divided�among�the�different�
items�according�to�value.�
•�Item�condition�type�PMIN:�-You�can�create�a�
minimum�price�for�a�material�using�type�PMIN.�If�
the�
minimum�price�is�not�met�during�pricing,�the�system�
determines�the�difference�using�condition�type�
-----------------------�Page�58-----------------------
PMIN�
Interval�scale�(PR02)-�Scale�pricing�
•�You�can�maintain�condition�records�with�interval��
scales�if�the�condition�type�is�set�to�scale�type�D�in�
customizing.�Interval�scales�cannot�use�for�group�
conditions.�
Rounding�Diff:�-�
•�You�can�maintain�a�rounding�unit�in�table�T001R�
for�each�company�code�and�currency.�
Condition�DIFF�determines�the�difference�amount.�
Condition�type�DIFF�is�a�group�condition�and�is�
distributed�among�the�different�items�according�to�
value.�
Customer�Hierarchy�Pricing�
•�Customer�hierarchy�are�available�in�sales�order��
management�so�that�you�can�create�flexible�
hierarchies�
to�reflect�the�structure�of�customer�organization.�
•�Use�Customer�hierarchy�during�sales�order��
processing�and�billing�to�determine�pricing�and�
running�
statistics.�
•�A�Customer�hierarchy�consists�of�nodes.�Which�are��
only�valid�for�a�certain�period�of�time.�They�also�
be�moved.�If�a�node�is�moved,�the�system�
automatically�reassigns�all�related�nodes�and�
-----------------------�Page�59-----------------------
customer�
master�data.�
•�Settings-�
..�Create�master�records�for�each�node�
..�Assign�node�to�each�other�
..�Assign�the�customer�master�records�to�the�
relevant�nodes.�
•�“With�customer�hierarchies,�you�can�assign�price��
or�rebate�agreements�to�a�higher�level�node”�
•�Customer�hierarchy�accesses�also�provide�clear�
and�easy�master�data�maintenance�because�the�
different�condition�records�for�a�condition�type�can�
be�created�together�in�the�quick�entry�screen�for�
maintaining�condition.�
Discount�and�surcharges�
•�Pallet�discount-KP00,�incomplete�pallet�surcharge�
KP01,�Mixed�Pallet�Discount�KP02,�Surcharges�for�
incomplete�mixed�pallets�KP03�
Statistical�condition�type�
•�Condition�type�VPRS-statistical�condition�used�to�
retrieve�the�standard�cost�of�the�material�has�
condition�category�G.�it�accesses�the�material�
valuation�segment�of�material�master.�
•�Condition�type�SKTO-�statistical�condition�used�to�
retrieve�the�cash�discount�rate.�It�has�condition�
-----------------------�Page�60-----------------------
category�E.�
Update�price�
•�Update�prices�on�the�condition�screens�is�available��
at�header�and�item�level�(�in�sales�order�and�billing)�
:�you�can�choose�the�pricing�time�in�a�dialog�box.�
Calculation�type�
•�The�calculation�type�for�a�condition�type�is�defined��
in�customizing.�This�calculation�type�determines�
how�prices�or�discounts�and�surcharges�are�
calculated�for�a�condition.�
Pricing�procedure�
•�The�sequence�in�which�the�system�accesses�the��
conditions�by�using�condition�technique�in�
business�document�is�determined�in�the�pricing�
procedure.�
•�“Requirements,�routine�and�formula�provide�a��
method�to�modify�the�standard�pricing�logic�to�meet�
unique�user�requirement”�
Pricing�procedure�determination-�
•�Sales�Org.+�DC+�Division�+Document�pricing��
procedure�+�Customer�pricing�procedure�
•�Pricing�determination�is�carried�out�using�the��
condition�technique.�
Requirements�(2-Item�with�pricing,�55-�free�goods�
pricing,�59-�Free�goods)�
•�You�need�to�determine�“how�the�system�should��
-----------------------�Page�61-----------------------
use�the�conditions�type”�by�specifying�the�
requirements.�
•�You�are�able�to�make�access�dependent�on��
requirements�to�avoid�unnecessary�access,�this�
reduce�the�
system�load.�
Reference�level�(Subtotal)�
•�Provides�a�method�to�specify�a�different�basis�to��
calculate�the�condition�type�and�to�group�condition�
for�subtotal.�
•�Pricing�procedure�can�contain�any�number�of��
subtotals.�
Condition�type�
•�Are�combined�in�the�require�sequence�in�pricing��
procedure.�
•�Mark�a�condition�type�in�the�pricing�procedure�as��
being:�
..�A�mandatory�condition-PR00�
SAP�SD�IMP�NOTES�
Manoj�Kumar�
SAP�SD�Certified�Consultant�
E-Mail:�[email protected]�
..�A�manually�condition-HM00,�PN00�
..�For�statistical�purpose�only.�-VPRS,�SKTO�
-----------------------�Page�62-----------------------
Pricing�type�
•�You�can�configure�the�pricing�behavior�in�the��
pricing�type.�
•�Pricing�types�are:�-�
A.�Copy�pricing�elements�and�update�scale�
B.�Carry�out�new�price�
C.�Copy�manual�pricing�elements�
G.�Re-determined�taxes�
H.�Re-determine�freight�
X,�Y�Reserved�for�customer�
1-9�Reserved�for�customer�
Tax�determination�
•�The�following�factor�play�a�role�in�tax��
determination�
..�Business�transaction-�Domestic�or�export�/�import�
..�Tax�liability�of�ship�to�party�
..�Tax�liability�of�material�
•�You�can�assign�a�Rule,�BLANK,�A,�B�at�the�sales��
organization�level�to�determine�tax�identification�
number�in�the�sales�order�and�billing�document.�
Sales�deal�and�promotion�
•�You�can�define�a�promotion�or�general�marketing��
plan�for�a�product�line�for�a�certain�period�of�time.�
You�can�then�link�this�promotion�with�specific�sales�
deals,�which�themselves�linked�to�special�
condition�records.�These�condition�records�can�be�
-----------------------�Page�63-----------------------
used�for�promotional�pricing�or�discounts.�
Rebate�processing�
Creating�rebates�agreement:�-�
•�You�may�define�rebates�at�as�many�levels�as�you��
require,�similar�to�any�pricing�condition.�
•�The�rebate�agreement�is�created�with�a�specific��
rebate�agreement�type.�The�feature�of�each�
agreement�type�set�in�customizing�(like�condition�
table�and�its�access�sequence).�
•�Condition�records�are�linked�to�the�rebate��
agreement�specifying�the�rebate�rate�and�the�
accrual�rate.�
Processing�rebates�
•�Rebates�are�different�from�other�discounts�in�that�
they�are�based�on�the�sales�volume�generated�
by�the�customer�within�a�specific�period�and�are�paid�
retrospectively.�
•�A�settlement�run�creates�the�required�credit�memo��
request�automatically.�
•�When�the�rebate-�relevant�billing�documents�are�
processed,�accruals�can�be�determined�and�posted�
to�
financial�accounting�automatically,�at�the�same�time,�
the�system�updates�the�rebate�basis�and�the�
accrual�amount�on�the�rebate�agreement�sales�
volume�screen.�
-----------------------�Page�64-----------------------
•�You�can�use�the�rebate�credit�memo�to�reverse�
these�accruals.�Accrual�are�cancelled�automatically�
when�a�credit�memo�is�created.�
•�To�function�properly,�rebate�processing�must�be��
active�for:�-�
..�Sales�organization�
..�The�payer�master�
..�The�billing�document�
Step�rebate�processing:�-�
..�Rebate�processing�begins�by�creating�a�rebate-�
relevant�billing�document.�
..�The�valid�rebates�condition�type�are�determined�
by�the�pricing�procedure�using�the�rebate�basis�
subtotal.�
..�Each�rebate�condition�type�has�an�assigned�access�
sequence�(set�in�customizing).�
..�The�system�uses�the�access�sequence�to�search�
for�the�valid�rebate�condition�records.�If�valid�
condition�records�are�found,�the�accrual�rate�is�
read.�
..�The�accrual�amount�is�calculated�using�the�rebate�
basis.�
..�The�system�posts�an�accrual�to�financial�
accounting�and�update�accrual�in�rebate�agreement�
same�
time.�
-----------------------�Page�65-----------------------
Retroactive�rebate�agreements�
•�Allow�you�to�take�into�account�billing�documents��
created�before�the�rebate�agreement�is�created.�
•�The�rebate�basis�for�the�billing�documents�created�
previously�is�accumulated�and�recorded�in�the�
rebate�agreement.�The�accrual�amount�is�not�
automatically�updated�for�billing�documents�created�
previously.�This�amount�must�be�entered�manually.�
Requirements�
Requirement�24�-�In�the�pricing�procedure�enforces�
that�the�rebate�conditions�are�used�only�in�billing�
documents.�
Requirement�25�–�In�the�pricing�procedure�enforces�
that�the�rebate�conditions�are�used�only�in�rebate�
relevant-billing�documents.�
BILLING�
Billing�overview�
•�A�Billing�document�has�two�levels-Header�and�
Item�
•�When�you�create�a�billing�document�in�account,��
the�R/3�system�carries�out�a�debit�posting�on�the�
customer�receivables�account�and�a�credit�posting�
on�the�revenue�account.�
•�An�important�part�of�billing�is�the�interface�to�
financial�accounting.�This�allows�documents�to�be�
creating�automatically�in�financial�accounting�and�
-----------------------�Page�66-----------------------
controlling�when�you�create�billing�documents.�
•�The�data,�which�can�be�changed�before�an��
accounting�document�created:�Billing�date,�pricing,�
account�determination,�output�determination.�After�
posting�accounting�you�can�change�only�
output�data.�
•�You�might�not�want�the�data�to�be�transferred��
automatically�for�certain�billing�types.�In�that�case�
you�
can�set�a�posting�block�for�the�billing�type�
concerned.�
•�Inter-company�billing-�a�sales�organization�can�
also�sell�products�supplied�by�a�plant�that�is�
assigned�
to�a�different�company�code.�
Controlling�the�billing�process�
Billing�type�control�
•�The�billing�type�controls�the�whole�document.�
•�The�billing�types�are�used�to�cover�the�full�range�of��
business�transactions�during�billing�processing.�
•�In�billing�type�if�“Text�Delivery”�is�switched�off,�the��
corresponding�SD�header/item�texts�are�taken�
from�the�order.�If�the�switch�is�on�then�it�is�taken�
from�outbound�delivery.�
•�Having�following�control.�
-----------------------�Page�67-----------------------
..�Cancellation�billing�type�
..�Number�assignment�(Internal)�
..�Partners�
..�Rebate�
..�Posting�block�
..�Account�determination�
..�Invoice�list�type�
..�Special�features�of�FI�interface�
..�Basic�function�(Text,�Output)�
•�In�customizing,�for�item�category�(sales�doc.),�you��
determine�whether�billing�is�to�be�carried�out�with�
reference�to�a�delivery�or�an�order.�The�system�
propose�a�relevant�billing�type�from�the�underlying�
sales�document�type.�For�example,�in�delivery�
related�billing,�a�standard�order�(Order�type�OR)�is�
invoiced�using�billing�type�F2.�
Invoice�combination�and�Invoice�split�
•�It�is�possible�to�include�both�order�related�and��
delivery�related�items�in�the�same�billing�document.�
•�If�the�header�partner�or�data�in�the�header�field��
are�not�identical,�the�system�will�automatically�
perform�
an�invoice�split.�
Invoice�list:�-�
•�Each�billing�type�to�be�included�in�an�invoice�list��
must�assign�an�invoice�list�type.�
-----------------------�Page�68-----------------------
•�You�also�need�to�maintain�the�following�master�
data:�
1.�Define�a�factory�calendar,�which�specifies�when�
invoice�list�are�to�be�created.�
2.�Enter�this�factory�calendar�in�the�payer�master�
record�(Billing�screen,�invoice�list�schedule�field).�
3.�Maintain�condition�record�for�condition�type�RL00�
for�the�payer.�
4.�Create�out�put�condition�records�for�condition�
types�LR00�and�RD01.�
Data�flow�and�coping�control�
•�You�can�automatically�fill�the�reference�number��
and�allocation�number�fields�in�the�accounting�
document�with�numbers�from�SD�documents.�The�
reference�number�is�in�header�of�the�accounting�
document�and�is�used�for�clearing.�The�allocation�
number�is�in�the�customer�line�item�and�is�
used�for�sorting�line�numbers.�
•�In�customizing�for�copy�control�in�billing,�you�can�
define�which�numbered�will�be�copied�as�reference�
or�allocations:�
A.�Purchase�number�
B.�Sales�order�number�
C.�Delivery�number�
D.�External�delivery�number�
E.�Billing�document�number�
-----------------------�Page�69-----------------------
F.�External�delivery�number�if�available,�other�wise�
delivery�number.�
•�When�the�invoice�list�is�created,�the�reference��
number�from�the�invoice�list�overwrites�the�
reference�
number�from�the�individual�billing�document.�
•�Copying�requirement�are�ABAP�routines.�Before��
data�is�copied�from�the�source�document�to�target�
document,�specific�requirements�must�be�satisfied�at�
each�level�of�the�document.�
Special�billing�type�
Billing�type�in�complaint�processing�
Cancellation:�
•�You�do�not�need�to�make�an�entry�in�coping��
control�for�billing�cancellations.�
•�When�you�select�cancellations,�you�branch�to�an�
overview�screen�containing�the�original�billing�
document�as�well�as�the�cancellation.�Before�
updating,�you�can�compare�both�documents�in�order�
to�
avoid�any�discrepancies�during�cancellation.�
Credit�and�debit�memos:�
•�You�can�create�credit�and�debit�memos�either�to��
credit�or�debit�memo�request�(sales�document),�or,�
if�
your�company�does�not�require�a�release�procedure�
-----------------------�Page�70-----------------------
in�case�of�complaints,�directly�with�reference�to�a�
billing�document.�
•�We�can�also�create�credit�and�debit�memo�request�
without�reference�to�a�previous�business�
transaction.�
•�You�can�control�in�customizing�whether�the�system��
is�to�set�a�billing�block�automatically�for�a�
credit�or�debit�memo�request.�
•�The�responsible�employee�can:�
..�Release�the�credit�or�debit�memo�request�after�
review�(by�removing�billing�block).�The�
employee�can�decide�the�amount�or�quantity�to�be�
credited�or�debited.�
..�Reject�item�in�the�credit�or�debit�memo�request�
and�enter�a�reason�for�rejection.�
Invoice�correction�request:�
•�The�invoice�correction�request�represents�a��
combination�of�credit�and�debit�memo�request.�
•�The�invoice�correction�request�must�be�credited��
with�reference�to�the�corresponding�billing�
document�
(no�reference�to�order�or�inquiry).�
•�The�credit�memo�item�cannot�be�changed.�The�
corresponding�debit�memo�item,�however,�can�be�
updated�according�to�new�characteristics�(E.g.�new�
pricing,�change�in�quantity)�
-----------------------�Page�71-----------------------
•�You�can�delete�the�credit�and�debit�memos�in�pairs��
(unchanged�pairs�of�items�can�be�deleted�all�at�
once�
in�this�way).�
Returns�
•�Returns�are�processed�in�the�same�way�as�credit��
memo�request.�
Pro�forma�invoice�
•�You�can�create�with�reference�to�order�or��
deliveries�
•�This�is�generally�used�for�export�transaction�
•�Do�not�need�PGI�before�creating�delivery�related�
Pro�forma�invoice.�
•�You�can�create�as�many�pro�forma�invoices�as��
required,�since�the�billing�status�in�the�reference�
document�is�not�updated.�
•�Data�from�pro�forma�invoice�is�not�transfer�to��
accounting�
Cash�sale�
•�Order�related�billing,�(BV)�the�order�and�delivery�
are�created�in�one�step,�although�you�receive�a�
document�for�each�other.�
•�The�goods�issue�is�posted�at�a�later�time�as�a��
separate�transaction�so�the�customer�does�not�have�
to�
wait.�
-----------------------�Page�72-----------------------
•�Order�type�CS�is�used�for�cash�sales.�It�has�its�own�
output�type�RD03�which�allows�you�to�print�an�
invoice�from�the�order.�
•�No�output�determination,�as�this�has�already�been��
carried�out�in�order.�
•�No�new�price�determination,�as�the�pricing�should��
not�differ�from�the�printed�invoice.�
•�Posting�in�financial�accounting�is�made�to�a�cash��
settlement�account,�not�to�the�customer.�
•�Billing�type�SV�is�used�for�cancellations�in�cash��
sales.�
Special�business�transactions�
Billing�plan-Periodic�billing�and�Milestone�Billing�
•�You�can�assign�billing�plan�at�header�level�{sales�
doc.�Type}�or�at�item�level�{sales�item�category�
with�
billing�relevance�1}�
•�Periodic�Billing�
..�Periodic�billing�is�used�to�spread�billing�of�full�
amount�over�several�dates�within�billing�plan.�
Generally�use�in�rental�and�in�service�contract.�
•�Milestone�billing:�-�
..�In�the�SAP�R/3�System,�milestone�is�stored�in�a�
network�along�with�planned�and�actual�project�
data.�
..�Milestone�are�assigned�to�the�billing�plan�dates�
-----------------------�Page�73-----------------------
and�blocked�for�billing�until�the�milestone�is�
confirmed�as�completed.�
..�The�date�proposal�is�used�exclusively�for�
milestone�billing.�It�determines�a�sequence�of�dates�
that�are�used�as�the�reference�for�date�
determination�during�order�processing.�
Down�payment�processing�in�SD�
•�Down�payments�are�already�created�in�the�sales�
order.�“�At�the�corresponding�due�date,�a�down�
payment�request�(Billing�Document)�is�sent�to�
customer.”�
•�The�down�payment�agreement�can�be�assigned��
directly�to�an�item,�or�it�can�be�defined�as�valid�for�
all�
items�in�the�order.�
•�As�soon�as�billing�date�for�down�payment�has�been��
reached�the�system�created�a�down�payment�
invoice�and�sent�it�to�the�customer.�
•�Tax�is�determined�and�displayed�automatically��
when�the�down�payment�request�is�created.�
•�The�down�payment�request�(SD)�is�automatically�
posted�in�financial�accounting�as�a�down�
payment�request�(Posted�as�a�noted�item).�The�item�
ha�special�general�ledger�(G/L)�indicator�F,�
which�insures�that�posting,�is�statistical.�Posting�is�
made�to�a�different�reconciliation�account,�which�
-----------------------�Page�74-----------------------
allows�you�to�differentiate�down�payment�requests�
from�other�receivables.�Billing�type�FAZ�is�
used�for�creating�the�down�payment�request.�
Installment�Payments�
•�Installment�plans�allow�the�customer�to�pay�in��
installments.�Only�one�billing�document�is�created�
for�
all�of�the�installment�payments.�The�printed�invoice�
is�created�on�the�basis�of�this�billing�document�and�
includes�a�list�of�individual�payment�dates�and�exact�
amounts.�Each�installment�payment�creates�an�
accounts�receivable�line�posting�in�FI.�
•�You�must�define�installment�payment�terms�in��
customizing�(number�and�amount�of�the�installment�
in�percentage�and�payment�terms).�
Account�determination�
•�Account�determination�is�carried�out�using�the��
condition�technique.�
•�The�slandered�account�determination�procedure�is�
KOFI00,�which�has�the�standard�condition�types�as�
KOFI�and�KOFK.�
•�Criteria�for�account�determination-�
..�Chart�of�account�
..�Sales�organization�
..�Account�assignment�group�for�payer�
(Customer�in�to�different�group,�such�as�domestic�
-----------------------�Page�75-----------------------
and�overseas.)�
..�Account�assignment�group�for�materials�
..�Account�key�
(Account�keys�are�assigned�to�condition�types�in�the�
pricing�procedure,�so�that�conditions�such�as�
freight�condition,�can�be�posted�to�special�freight�
revenue�accounts)�
SD/FI�interface�
•�Sales�organization�to�company�code�assignment�
•�Account�determination�
•�Copy�control.�
Condition�technique�is�used�for�
..�Pricing�
..�Account�determination�
..�Material�determination�
..�Listing�
..�Exclusion�
..�Free�goods�determination�
..�Tax�determination�
..�Text�determination�
..�Output�determination�
TAB�PAGES�FOE�BILLING�DOCUMENT�
Header�-�Header,�Header�Partner,�Conditions,�
Foreign�Trade/customs,�Head�text,�Global�trade.�
Item�–�Item�detail,�Item,�Partner,�Conditions,�
-----------------------�Page�76-----------------------
Foreign�Trade/�customs,�Item�text,�PO�date,�global�
trade.�
SD�QUESTIONS�&�ANSWERS�
I�BASIS�KNOWLEDGE�AND�SYSTEM�
NAVIGATION�
Name�two�ways�to�start�a�transaction.�
Dynamic�Menu�
Command�Field�
Why�do�you�create�user-specific�parameters?�
They�supply�defaults�to�R/3�fields.�If�a�field�is�
indicated,�the�system�automatically�fills�in�default�
value.�Depending�on�the�field�definition,�the�entry�
can�also�be�replaced�with�a�value�entered�by�the�
user.�(Concept�of�PARAMETER�ID)�
Name�the�three�different�kinds�of�messages�in�the�
R/3�system.�What�is�the�difference�between�them?�
A�message�can�have�five�different�types.�These�
message�types�have�the�following�effects�during�list�
processing:�
A�(=Abend):�
The�system�displays�a�message�of�this�message�type�
in�a�dialog�window.�After�the�user�confirms�the�
message�using�ENTER,�the�system�terminates�the�
entire�transaction�(for�example�SE38).�
E�(=Error)�or�W�(=Warning):�
The�system�displays�a�message�of�this�message�type�
-----------------------�Page�77-----------------------
in�the�status�line.�After�the�user�chooses�ENTER,�the�
system�acts�as�follows:�
While�creating�the�basic�list,�the�system�terminates�
the�report.�
While�creating�a�secondary�list,�the�system�
terminates�the�corresponding�processing�block�and�
keeps�displaying�the�previous�list�level.�
I�(=Information):�
The�system�displays�a�message�of�this�message�type�
in�a�dialog�window.�After�the�user�chooses�ENTER�,�
the�system�resumes�processing�at�the�current�
program�position.�
S�(=Success):�
The�system�displays�a�message�of�this�message�type�
on�the�output�screen�in�the�status�line�of�the�
currently�created�list.�
What�is�a�data�dictionary�or�repository?�
Central�catalog�that�contains�the�descriptions�of�an�
organization's�data�and�provides�information�about�
the�relationships�between�the�data�and�its�use�in�
programs�and�screens.�
The�data�descriptions�in�a�Data�Dictionary�is�also�
called�metadata,�i.e.,�data�that�describes�other�
data.�
The�ABAP/4�Dictionary�stores�system-wide�data�
definitions.�When�you�create�a�new�data�definition,�
the�Dictionary�tool�does�all�the�processing�necessary�
to�create�the�definition.�You�can�use�the�Dictionary�
tool�to�look�up�the�"definition"�of�objects�in�your�R/3�
-----------------------�Page�78-----------------------
System.�
What�is�a�matchcode?�
Comparsion�key.�A�matchcode�allows�you�to�locate�
the�key�of�a�particular�database�record�(e.g.�account�
number)�by�entering�any�field�value�contained�in�the�
record.�The�system�then�displays�a�list�of�records�
matching�the�specifications.�
If�you�want�an�end�user�to�see�a�specific�menu�after�
logging�on�the�R/3�system,�how�could�you�do�that?�
User�maintenance�transactions�allow�the�system�
administrator�to�create�and�maintain�user�master�
records.�This�includes�the�generation�and�
assignment�of�authorizations�and�authorization�
profiles.�
II�CORPORATE�STRUCTURE�
In�R/3�you�can�represent�a�company's�structure�by�
defining�and�assigning�corporate�structure�elements.�
What�is�the�purpose�of�doing�that?�
Enterprise�organization�diagram.�Chart�showing�the�
organizational�structure�of�an�enterprise,�its�
organization�units�and�how�they�are�related.�A�
combined�structure�can�be�created�from�the�point�of�
view�of�accounting,�MM,�SD.�This�structure�forms�a�
framework�in�which�all�business�transactions�can�be�
processed.�
-----------------------�Page�79-----------------------
Which�three�organizational�elements�make�up�a�
sales�area�and�briefly�explain�their�function?�
Sales�organization:�An�organizational�unit�that�sells�
and�distributes�products,�negotiates�terms�of�sale,�
and�is�responsible�for�these�transactions.�
Distribution�channel:�Channel�through�which�salable�
materials�or�services�reach�customers.�Typical�
distribution�channels�include�wholesale,�retail�and�
direct�sales.�You�can�assign�a�distribution�channel�to�
one�or�more�sales�organizations.�
Division:�Product�groups�can�be�defined�for�a�wide-�
ranging�spectrum�of�products.�For�every�division�you�
can�make�customer-specific�agreements�on,�for�
example,�partial�deliveries,�pricing�and�terms�of�
payment.�Within�a�division�you�can�carry�out�
statistical�analyses�or�set�up�separate�marketing.�
Name�the�three�internal�organizational�elements�
within�a�sales�organization�and�briefly�explain�their�
function.�
Sales�Office.�Geographical�aspects�of�the�
organization�in�business�development�and�sales�are�
defined�using�the�term�sales�office.�A�sales�office�
can�be�considered�as�a�subsidiary.�
Sales�offices�are�assigned�to�sales�areas.�If�you�
enter�a�sales�order�for�a�sales�office�within�a�certain�
sales�area,�the�sales�office�must�be�assigned�to�that�
area.�
Sales�Group.�The�staff�of�a�sales�office�may�be�
subdivided�into�sales�groups.�For�example,�sales�
groups�can�be�defined�for�individual�divisions.�
-----------------------�Page�80-----------------------
Salespersons.�Individual�personnel�master�records�
are�used�to�manage�data�about�salespersons.�You�
can�assign�a�sales�person�to�a�sales�group�in�the�
personnel�master�record.�
What�does�the�term�"business�area"�refer�to�and�
how�can�it�be�used?�
Business�Area.�The�system�posts�costs�and�revenue�
according�to�the�business�area.�The�business�area�
can�be�equivalent�to�the:�
sales�area�(if�the�accounts�are�to�be�posted�
according�to�sales)�
plant/division�(if�the�accounts�are�to�be�posted�
according�to�products)�
The�business�area�is�defined�in�Customizing�for�
Sales.�
•�Business�area.�A�unit�in�an�enterprise,�grouping��
product�and�market�combinations�as�homogeneously�
as�possible�for�the�purpose�of�developing�unified�
business�policy.�
•�Financial�Accounting�(FI).�A�business�area�is�an��
organizational�unit�within�financial�accounting�which�
represents�a�separate�area�of�operations�or�
responsibilities�within�an�organization.�Financial�
accounting�transactions�can�be�allocated�to�a�
specific�business�area.�
Briefly�explain�the�relationship�between�sales�
organizations�and�company�codes.�
Many�to�One.�
-----------------------�Page�81-----------------------
What�is�the�central�organizational�element�in�
purchasing?�
Purchasing�Organization.�
Explain�the�relationship�between�sales�organizations�
and�plants.�
Many�to�Many.�
Explain�the�relationship�between�sales�organizations,�
plants�and�company�codes.�
Many�to�Many�to�One.�
Can�one�business�area�be�assigned�to�several�
company�codes?�Which�(sub)�module�of�SAP�could�
make�business�areas�obsolete?�
Yes�in�CO�.�
What�is�a�credit�control�area?�What�relationship�
exists�between�credit�control�areas�and�company�
codes?�
Credit�control�area.�Organizational�unit�in�an�
organization�that�specifies�and�checks�credit�limits�
for�customers.�A�credit�control�area�can�include�one�
or�more�company�codes.�It�is�not�possible�to�assign�
a�company�code�to�more�than�one�credit�control�
areas.�
Which�organizational�element�is�central�in�shipping?�
Give�a�definition�of�it.�
-----------------------�Page�82-----------------------
Shipping�Point:�Organizational�unit�at�a�fixed�
location�that�carries�out�shipping�activities.�A�
shipping�point�could,�for�example,�be�a�company's�
mail�department�or�a�plant's�rail�depot.�Each�
delivery�is�processed�by�only�one�shipping�point.�
Give�a�definition�of�plant�(in�SAP).�
Organizational�unit�within�Logistics,�serving�to�
subdivide�an�enterprise�according�to�production,�
procurement,�maintenance,�and�materials�planning�
aspects.�
A�plant�is�a�place�where�either�materials�are�
produced�or�goods�and�services�provided.�
Classification:�Business�object�
Structure:�A�plant�can�assume�a�variety�of�roles:�
As�a�maintenance�plant,�it�includes�the�maintenance�
objects�that�are�spatially�located�within�this�plant.�
The�maintenance�tasks�that�are�to�be�performed�are�
specified�within�a�maintenance�planning�plant.�
As�a�retail�or�wholesale�site,�it�makes�merchandise�
available�for�distribution�and�sale.�
As�a�rule,�the�plant�is�the�organizational�unit�for�
material�valuation.�
The�preferred�shipping�point�for�a�plant�is�defined�as�
the�default�shipping�point,�which�depends�on�the�
shipping�condition�and�the�loading�condition.�
For�the�placement�of�materials�in�storage�(stock�put-�
away),�a�storage�location�is�assigned�to�a�plant.�The�
storage�location�depends�on�the�storage�condition�
and�the�stock�placement�situation.�
-----------------------�Page�83-----------------------
The�business�area�that�is�responsible�for�a�valuation�
area�is�determined�as�a�function�of�the�division.�As�a�
rule,�a�valuation�area�corresponds�to�a�plant.�
Can�you�assign�two�different�sales�organization�to�
the�same�company�code?�
Yes.�
To�what�do�you�assign�distribution�channels�and�
divisions?�
Sales�Organizations.�
What�are�the�highest�organizational�units�in�SD,�
MM.PP,FI,CO?�
SD:�Sales�Organizations.�
M:�Plant�
PP:�Plant�
FI:�Company�Code�
CO:�Controlling�Area�
Can�you�further�subdivide�a�plant?�If�yes�into�what�
?�
A�plant�can�be�subdivided�into�storage�locations,�
allowing�stocks�of�materials�to�be�broken�down�
according�to�predefined�criteria�(e.g.,�location�and�
materials�planning�aspects).�
A�plant�can�be�subdivided�into�locations�and�
operational�areas.�Subdivision�into�locations�takes�
geographical�criteria�into�account,�whereas�
subdivision�into�operational�areas�reflects�
-----------------------�Page�84-----------------------
responsibilities�for�production.�
Can�a�sales�organization�sell�from�a�plant�belonging�
to�a�different�company�code?�
Yes.�
How�many�shipping�points�can�you�assign�to�a�
plant?�
Many.�
How�many�shipping�points�can�you�assign�to�a�sales�
organization?�
None.�
If�you�have�a�warehouse�management�system�
active,�to�what�would�you�assign�the�warehouse�
number?�
Plant�&�Storage�Location.�
III�MASTER�DATA�
Why�does�the�customer�master�have�different�
views?�
In�addition�to�the�sales�and�distribution�data,�the�
accounting�data�is�also�important�for�a�payer.�
Therefore�one�can�create�a�customer�master�record�
centrally�for�the�following�partner�functions:�
For�the�payer�
For�the�sold-to�party�who,�in�addition�to�the�other�
-----------------------�Page�85-----------------------
partner�functions,�also�takes�on�the�function�of�the�
payer.�
Which�different�partner�functions�can�a�customer�
master�record�serve?�
Customer:�
•�sold-to�party�
•�ship-to�party�
•�payer�
•�bill-to�party�
•�One-time�customer�including�all�partner�functions.�
What�is�the�structure�of�data�in�the�customer�master�
record?�
Different�data�is�maintained�in�each�of�the�three�
areas:�
General�data,�like�address�and�telephone�number,�
etc.,�is�maintained�for�every�customer.�This�data�is�
only�identified�by�the�customer�number,�not�by�
company�code�or�sales�area.�Maintaining�the�data�is�
possible�from�both�the�accounting�view�and�the�
sales�and�distribution�view.�
Company�code�data�is�only�of�interest�for�the�
accounting�department.�It�includes,�for�example,�
information�on�insurance�or�account�management.�
This�data�applies�to�only�one�company�code.�
Sales�and�distribution�data�is�only�of�interest�for�the�
sales�and�distribution�department.�It�includes,�for�
example,�data�on�pricing�or�shipping.�This�data�only�
applies�to�one�sales�area,�and�therefore�is�
-----------------------�Page�86-----------------------
dependent�on�the�sales�structure�(sales�
organization,�distribution�channel,�division).�
Would�you�have�different�customer�numbers�if�your�
customer�was�serviced�by�more�than�one�company�
code?�
No.�
Would�you�have�different�customer�numbers�if�your�
customer�was�serviced�by�more�than�one�sales�
organization?�
No.�
A�material�is�produced�in�plant�Boston,�plant�Dallas�
and�in�plant�Chicago.�How�many�different�material�
master�number�do�you�need?�
Only�one.�
Is�it�possible�to�have�different�data�for�the�same�
customer�for�different�sales�areas?�
Yes.�
Give�examples�of�general�data�in�the�customer�
master�record�?�
Address,�Control�data,�Marketing,�Payment�
transactions,�Contact�person,�Unloading�points.�
Give�examples�of�general�data�in�the�material�
master�record�?�
This�level�contains�the�data�applicable�to�all�
-----------------------�Page�87-----------------------
individual�group�companies,�all�plants,�and�all�
warehouses/stores�belonging�to�an�enterprise�
(corporate�group).�Examples�of�general�data�are�
details�on�a�material's�design�(CAD�drawings,�for�
instance)�and�storage�conditions�(temperature�
range,�whether�the�material�is�explosive�or�
perishable,�and�so�on).�
Give�examples�of�company�-code-specific�data�in�the�
customer�master�record?�
This�data�is�only�of�importance�to�the�accounting�
department.�It�includes,�for�example,�data�on�
insurance�and�account�management.�Company�code�
data�only�applies�to�one�company�code.�If�you�edit�
the�customer�master�record�you�must�specify�
customer�number�and�company�code�in�order�to�
access�the�screens�containing�company�code�data.�
Which�plant-specific�data�do�you�find�in�the�material�
master�record?�
This�level�contains�the�data�for�each�branch�or�plant�
location�within�a�certain�company.�The�data�
important�to�Purchasing�is�stored�at�this�level.�
Examples�of�this�data�are�the�maximum�and�
minimum�order�quantities�of�a�material�and�the�
reorder�level.�You�access�the�plant�data�by�entering�
the�plant�key.�
If�a�customer�wishes�to�receive�goods�on�Tuesdays�
only,�how�could�you�ensure�that�in�the�SAP�R/3�
-----------------------�Page�88-----------------------
system?�
This�can�be�done�by�specifying�goods�receiving�
hours�-�Time�schedule�of�ship-to�party�which�
specifies�the�days�and�times�that�goods�can�be�
delivered.�
Do�you�find�any�sales�prices�in�the�material�master�
record?�
Yes.�
Name�at�least�five�different�partner�functions.�
Examples�of�partner�functions�in�Sales�and�
Distribution:�
sold-to�party,�ship-to�party,�bill-to�party,�payer.�
Examples�of�partner�functions�(roles)�in�Materials�
Management:�
ordering�address,�supplier�of�goods,�invoicing�party,�
different�payee.�
Which�are�the�two�partner�functions�in�SD�that�have�
to�be�maintained�in�FI�too�?�
sold-to�party,�payer.�
Can�you�assign�a�material�to�more�than�one�
division?�
No.�
If�you�want�to�create�language�specific�sales�texts�
for�your�material�master,�would�you�have�to�create�
a�new�material�master�record?�
-----------------------�Page�89-----------------------
No.�
What�is�a�material�type�and�which�material�types�do�
you�know?�
Raw�materials,�semi-finished�products,�finished�
products,�trading�goods,�operating�supplies.�
Name�the�four�standard�industry�sectors�in�SAP�for�
the�material�master.�For�what�do�you�use�them?�
Branch�of�industry.�
The�industry�sector�groups�together�companies�
according�to�their�activities�(for�example,�plant�
engineering�and�construction,�mechanical�
engineering,�the�chemical�industry,�and�the�
pharmaceutical�industry).�
Table-driven�program�support�is�provided�via�the�
industry�sector:�for�example,�for�the�selection�of�
data�fields�on-screen,�for�the�sequence�of�the�
screens,�and�for�the�allocation�of�a�material�to�a�
material�type.�
For�what�or�why�do�you�use�the�classification�system�
in�sales?�Give�examples�of�objects�you�can�classify�
in�R/3.�
For�e.g.,�Variant�Pricing�of�configurable�products.�
Objects�can�be�customers,�products,�condition�
types.�
Does�storage-location�specific�data�in�the�material�
master�record�apply�for�each�plant?�
-----------------------�Page�90-----------------------
This�level�contains�the�data�specific�to�a�storage�
location.�Stock�levels�are�an�example�of�the�data�
maintained�for�each�storage�location.�You�access�the�
storage�location�data�by�entering�the�plant�and�
storage�location�codes.�
This�data�structure�facilitates�the�organization�of�
material-related�information�within�the�entire�
enterprise.�It�prevents�redundant�storage�of�
material�data�when�the�same�material�is�used�in�
more�than�one�plant�or�stored�at�more�than�one�
storage�location.�
Example:�Suppose�the�same�metal�casting�is�stored�
at�two�different�locations.�The�design�and�
purchasing�data�for�this�material�would�be�identical.�
However,�the�data�on�the�stock�levels�at�each�
location�would�differ.�
Name�at�least�four�views�of�the�material�master�
record.�
Accounting�:�Valuation�and�costing�information.�
Examples:�standard�price,�past�and�future�price,�and�
current�valuation.�
Materials�planning�and�control:�Information�for�
material�requirements�planning�(MRP)�and�
consumption-based�planning/inventory�control.�
Examples:�safety�stock�level,�planned�delivery�time,�
and�reorder�level�for�a�material.�
Purchasing:�Data�provided�by�Purchasing�for�a�
material.�Examples:�purchasing�group�responsible�
for�a�material,�over-�and�underdelivery�tolerances,�
and�the�order�unit.�
-----------------------�Page�91-----------------------
Engineering:�Engineering�and�design�data�on�a�
material.�Examples:�CAD�drawings,�basic�
dimensions,�and�design�specifications.�
Storage:�Information�relating�to�the�
storage/warehousing�of�a�material.�Examples:�unit�
of�issue,�storage�conditions,�and�packaging�
dimensions.�
Forecasting:�Information�for�predicting�material�
requirements.�Examples:�how�the�material�is�
procured,�forecasting�period,�and�past�
consumption/usage.�
Sales�and�distribution:�Information�for�sales�orders�
and�pricing.�Examples:�sales�price,�minimum�order�
quantity,�and�the�name�of�the�sales�department�
responsible�for�a�certain�material.�
What�are�the�possible�units�of�measure�for�a�
material?�
A�material�can�be�stored,�transported�and�sold�in�
various�units�of�measure.�In�the�SAP�R/3�System,�
you�can�therefore�define�various�units�of�measure�
which�are�maintained�in�the�sales�and�distribution�
screens.�However,�you�only�need�to�maintain�the�
fields�of�the�units�of�measure�if�they�deviate�from�
the�base�unit�of�measure.�If�no�other�fields�with�
units�of�measure�are�maintained,�the�system�
automatically�takes�the�base�unit�of�measure�as�a�
basis�
for�its�calculations.�You�can�enter�the�following�units�
of�measure�in�the�sales�and�distribution�screens:�
-----------------------�Page�92-----------------------
Base�unit�of�measure�:�Stocks�of�a�material�are�
managed�in�the�base�unit�of�measure.�All�quantity�
movements�in�other�units�of�measure�are�converted�
automatically�by�the�system�into�the�base�unit�of�
measure.�
Alternative�unit�of�measure:�If�a�product�is�managed�
in�the�base�unit�of�measure�"Piece"�but�is�sold�in�the�
sales�unit�"Box",�you�must�define�the�conversion�
factor.�The�alternative�unit�of�measure�can�define,�
for�example,�that�1�box�of�this�material�contains�12�
pieces.�
Sales�unit�:�The�unit�of�measure�in�which�materials�
are�sold�is�referred�to�as�a�sales�unit�(for�example,�
piece�or�bottle).�The�value�you�define�in�the�material�
master�record�is�proposed�during�business�
transactions�relevant�for�sales,�such�as�the�sales�
order.�You�can�replace�them�with�other�alternative�
units�of�measure�in�the�sales�order.�
Delivery�Unit�:�The�delivery�unit�refers�to�the�unit�in�
which�materials�can�be�delivered.�Only�exact�
multiples�of�the�delivery�unit�can�be�delivered.�For�
example,�with�a�delivery�unit�of�30�bottles,�30,�60�or�
90�bottles�can�be�delivered,�but�not�100�bottles.�
Quantity�Specifications:�Two�different�quantity�
specifications�are�used:�
Minimum�order�quantity:�The�minimum�order�
quantity�refers�to�the�minimum�quantity�the�
customer�must�order.�A�warning�message�appears�if�
the�minimum�order�quantity�is�not�reached�during�
order�entry.�The�order�can�be�entered�in�spite�of�the�
-----------------------�Page�93-----------------------
warning�message.�
Minimum�delivery�quantity�:�The�minimum�delivery�
quantity�refers�to�the�minimum�quantity�you�must�
deliver�to�the�customer.�The�minimum�delivery�
quantity�is�automatically�checked�during�delivery�
processing.�A�warning�message�appears�during�
delivery�processing�if�you�enter�a�delivery�quantity�
lower�than�the�minimum�delivery�quantity.�The�
delivery�can�be�created�in�spite�of�this�warning�
message.�
What�is�a�Bill�of�material?�
A�bill�of�material�is�a�complete,�formally�structured�
list�of�the�components�that�make�up�a�product�or�
assembly.�The�list�contains�the�object�number�of�
each�component,�together�with�the�quantity�and�unit�
of�measure.�The�components�are�known�as�BOM�
items.�A�bill�of�material�can�only�refer�to�a�quantity�
of�at�least�1�of�an�object.�
Is�the�BOM�used�in�the�PP�module�only?�
No.�Also�used�in�SD.�
Explain�what�a�routing�is?�
Routing�contains�the�operations�required�in�
production,�and�the�production�resources/tools,�
material�components,�and�test�equipment�required�
to�produce�the�product.�
What�is�a�work�center?�
-----------------------�Page�94-----------------------
A�work�center�is�an�organizational�unit�where�a�work�
step�is�carried�out,�producing�an�output.�The�work�
center�defines�where�and�by�whom�an�operation�is�
to�be�carried�out.�A�cost�center�is�assigned�to�each�
work�center�in�the�work�center�master�record.�The�
work�center�has�a�particular�available�capacity.�The�
activities�performed�at�or�by�the�work�center�are�
valuated�by�charge�rates,�which�are�determined�by�
cost�centers�and�activity�types.�Work�centers�can�
be:�Machines,�People,�Production�lines,�Groups�of�
craftsmen�.�
IN�Personnel�Planning�and�Development�(PD)�work�
centers�are�the�physical�locations�where�tasks�are�
carried�out.�A�work�center�can�represent�anything�as�
general�as�a�geographic�location,�for�example,�the�
New�York�branch�office.�Or�work�centers�can�be�very�
precisely�defined.�For�example,�a�work�center�could�
represent�a�specific�workstation,�with�specific�tools�
and�equipment,�on�a�specific�floor,�of�a�specific�
building.�
IN�Workflow�Management�a�work�center�is�a�
particular�place�which�has�been�set�up�specifically�so�
that�employees�can�perform�their�duties�within�the�
corporate�work�system�using�working�materials.�
What�does�the�account�group�of�the�customer�
/vendor�control?�
A�collection�of�properties�of�accounts�which�
determine�the�creation�of�master�records.�
-----------------------�Page�95-----------------------
The�account�group�determines�the�data�that�is�
relevant�for�the�master�record�and�a�number�range�
from�which�numbers�are�selected�for�the�master�
records.�
Each�master�record�must�be�assigned�to�an�account�
group.�
Changes�to�the�account�group�and�the�
accompanying�partner�functions�can�only�be�made�
from�a�lower�level�to�a�higher�level.�For�example,�
this�means�that�a�sold-to�party�cannot�be�assigned�
the�function�of�a�payer�as�fields�which�have�already�
been�maintained�for�this�sold-to�party�would�have�to�
be�masked.�However,�you�can�assign�the�sold-to�
party�function�to�a�payer.�
The�account�group�ensures�that�for�the�different�
partner�functions�of�a�customer�only�the�necessary�
screens�and�fields�are�displayed�for�input.�
What�are�the�two�possible�ways�of�control�for�the�
cost�of�a�material�in�the�material�master�record?�
Standard�Price,�Moving�Average�Price.�
What�is�a�valuation�class?�
Allocation�of�a�material�to�a�group�of�G/L�accounts.�
Along�with�other�factors,�the�valuation�class�
determines�the�G/L�accounts�to�be�updated�as�a�
result�of�a�valuation-relevant�transaction�(for�
example,�a�goods�movement).�
Which�valuation�classes�are�valid�depends�on�the�
material�type.�Several�valuation�classes�can�be�valid�
-----------------------�Page�96-----------------------
for�one�material�type.�A�valuation�class�can�be�valid�
for�several�material�types.�
A�customer�master�record�in�SD�is�also�an�
A/R(accounts�receivables)in�FI.�When�you�create�a�
customer�master�record�you�also�have�to�specify�the�
reconciliation�account.�For�what�is�the�reconciliation�
account�used?�
Account�in�G/L�accounting,�to�which�automatic�
entries�are�posted�during�a�business�activity.�It�is�
generally�the�case�that�several�subledger�accounts�
post�to�a�common�reconciliation�account.�This�
ensures�that�the�developments�in�the�subledger�
accounts�are�accurately�reflected�in�the�general�
ledger�(i.e.�in�line�with�balance�sheet�conventions).�
You�can�set�up�a�reconciliation�account�for,�say,�all�
overseas�customers.�
IV�INRTRODUCTION�TO�ORDER�MANAGEMENT�
&�SALES�
Briefly�describe�the�types�and�structure�of�the�sales�
document�and�give�examples�of�data�that�you�find�
on�the�different�levels.�
Sales-related�business�transactions�are�recorded�in�
the�system�as�sales�documents.�There�are,�broadly�
speaking,�four�different�groupings�of�sales�
documents:�
Sales�queries,�such�as�inquiries�and�quotations�
-----------------------�Page�97-----------------------
Sales�orders�
Outline�agreements,�such�as�contracts�and�
scheduling�agreements�
Customer�problems�and�complaints,�such�as�free�of�
charge�deliveries�and�credit�memo�requests.�
Header�Data�
The�general�data�that�is�valid�for�the�entire�
document�is�recorded�in�the�document�header.�This�
data�includes�the:�
number�of�the�sold-to�party�
number�of�the�ship-to�party�and�the�payer�
document�currency�and�exchange�rate�
pricing�elements�for�the�entire�document�
delivery�date�and�shipping�point�
Item�Data�
Whereas�data�in�the�document�header�applies�to�all�
items�in�the�document,�some�data�applies�only�to�
specific�items.�This�data�is�stored�at�item�level�and�
includes�the:�
material�number�
target�quantity�for�outline�agreements�
number�of�the�ship-to�party�and�the�payer�(an�
alternative�ship-to�party�or�payer�can�be�defined�for�
a�particular�item)�
-----------------------�Page�98-----------------------
plant�and�storage�location�specifications�
pricing�elements�for�the�individual�items�
Schedule�Line�Data�
An�item�consists�of�one�or�more�schedule�lines.�The�
schedule�line�contains�all�the�data�that�is�needed�for�
a�delivery.�For�example,�a�customer�orders�20�
pieces�of�a�material�and�you�enter�this�as�an�item�in�
the�sales�order.�However,�you�can�only�deliver�10�
pieces�now�and�the�remaining�10�pieces�next�month.�
In�other�words,�you�need�to�schedule�two�deliveries.�
The�data�for�these�deliveries�(dates,�confirmed�
quantities)�are�stored�in�two�separate�schedule�
lines.�In�sales�documents�where�delivery�data�is�not�
relevant�-for�example:�contracts,�credit�and�debit�
memo�requests�-�the�system�does�not�create�any�
schedule�lines.�
Data�recorded�in�the�schedule�lines�includes�the:�
schedule�line�quantity�
delivery�date�
confirmed�quantity�
What�is�the�difference�between�an�inquiry�and�
quotation�?�
Inquiry:�Request�made�to�a�vendor�for�a�quotation�
for�required�materials�or�services.�
No�availability�check�is�done�for�inquiry.�
Quotation:�Offer�from�a�vendor�to�a�purchasing�
organization�regarding�the�supply�of�materials�or�
-----------------------�Page�99-----------------------
performance�of�services�subject�to�predefined�terms�
and�conditions.�
A�quotation�consists�of�a�number�of�items,�in�which�
the�total�quantity�and�delivery�date�of�an�offered�
material�or�service�are�specified.�
The�total�quantity�can�be�subdivided�into�several�
partial�quantities�with�different�delivery�dates�in�the�
lines�of�a�delivery�schedule.�
Do�you�always�have�to�have�a�material�master�
record�number�when�you�enter�an�item�on�a�sales�
document�(inquiry�and�quote)?�If�not�what�would�
you�have�to�use�to�be�able�to�enter�information�at�
item�level?�
No.�Customer�Material�Information�or�Material�
Description.�
If�a�customer�doesn't�place�an�order�with�you�after�
you�have�sent�him�a�quotation,�what�happens�to�the�
quotation�document?�
Remains�active�till�the�end�of�validity�period.�
Can�you�have�alternative�items�in�a�sales�order?�
Yes.�
If�you�reference�an�inquiry�when�creating�a�
quotation�,would�the�inquiry�be�updated?�
Yes.�
Can�you�copy�one�inquiry�to�many�quotations�?�
-----------------------�Page�100-----------------------
No.�
Can�you�copy�several�previous�documents�into�one�
sales�order?�
Yes.�
Do�you�always�have�to�copy�the�entire�quantities�at�
item�level�when�you�reference�a�previous�
document?�
No.�
Can�you�make�sure�that�business�data�in�a�sales�
order�is�only�possible�to�maintain�at�header�level?�
Yes.�
From�where�is�the�delivering�plant�transferred�into�
the�sales�order?�
Customer�Master,�Material�Master.�
Which�partner�function�is�relevant�for�the�delivering�
plant?�The�sold-to-party�,�bill-to-party,�payer,�
carrier�or�the�ship-�to-�party?�
Ship-to�party.�
Can�you�manually�change�the�delivering�plant�in�the�
sales�order�once�it�was�defaulted�from�the�master�
data?�
Yes.�
For�what�or�why�do�you�use�the�incompletion�log?�
-----------------------�Page�101-----------------------
To�have�a�complete�document�so�that�it�doesn‟t��
affect�subsequent�processes.�
Can�you�have�different�incompletion�logs�for�
different�item�categories?�Schedule�line�categories?�
Yes.�
If�a�document�is�incomplete�can�you�still�save�the�
document?�
Yes.�
Which�reference�statuses�can�a�document�have�at�
item�level?�Which�statuses�at�header�level?�
Item�level:�Partial,�Full.�
Header�level:�Full.�
What's�the�advantage�of�using�text�as�a�reference�
instead�of�duplicating�it?�
Can�be�modified�if�needed.�
What�three�sources�provide�data�for�the�creation�of�
a�sales�document?�
Material�Master,�Customer�Master,�Previous�
referenced�documents.�
Can�you�change�addresses�of�partners�manually�in�
the�sales�document?�
Yes.�
Name�several�input�tools�that�make�order�entry�
-----------------------�Page�102-----------------------
faster�and�give�a�definition�of�them?�
Customer�Material�Information,�Product�Proposal�,�
Referencing�Documents.�
In�which�business�environment�would�you�use�only�
the�single-line�entry�screen�to�create�and�save�the�
order?�
Telephone�Sales,�Simple�Business.�
If�you�do�not�specify�the�delivering�plant�in�the�sales�
order,�what�could�the�system�then�not�do?�
Delivery�Scheduling.�
For�what�would�you�use�the�fast�change�function�in�
sales�entry?�
Alternate�Plants,�Delivery�or�Billing�Blocks�
Name�two�ways�to�control�that�customers�can�
receive�only�certain�materials?�
Material�Listing,�Exclusion.�
What�does�the�item�category�control?�
General�Data�
-�Should�pricing�be�carried�out�for�the�item?�
-�When�should�an�item�be�regarded�as�completed?�A�
quotation�item,�for�example,�can�only�be�regarded�
as�completed�if�the�entire�quantity�has�been�copied�
into�a�sales�order.�
-----------------------�Page�103-----------------------
-�Is�it�an�item�that�refers�to�a�material�or�is�it�a�text�
item?�
-�Are�schedule�lines�allowed�for�the�item?�
-�May�general�business�data,�for�example,�the�terms�
of�payment�at�the�item�level,�deviate�from�those�at�
the�header�level?�
-�Should�a�system�message�appear�if�the�item�
cannot�be�fully�delivered?�
-�Which�fields�are�relevant�for�the�incompletion�log?�
-�Which�partner�functions�are�allowed�at�the�item�
level�and�which�are�mandatory?�
-�Which�output�(for�example,�an�order�confirmation)�
is�allowed�for�the�business�transaction�and�
which�output�determination�procedure�is�used?�
Shipping�Data�
-�Is�an�item�relevant�for�delivery?�
•�Should�the�weight�and�the�volume�of�an�item�be��
determined?�
Billing�Data�
-�Is�an�item�relevant�for�billing?�
-�Should�the�cost�of�the�item�be�determined?�
-�Is�it�a�statistical�item?�Pricing�is�carried�out�for�
statistical�items.�However,�they�are�not�added�to�the�
value�of�the�order,�that�is,�the�customer�is�not�
charged�for�them.�
-----------------------�Page�104-----------------------
-�Should�a�billing�block�be�set�automatically�for�an�
item?�For�example,�this�may�be�important�for�items�
whose�prices�have�to�be�clarified�before�billing.�
•�Is�it�a�returns�item?�
Name�the�influencing�factors�for�determining�the�
item�category�in�the�sales�document?�
Sales�Document�type,�Item�Category�Group,�Higher�
Level�Item,�Item�Usage.�
Name�the�influencing�factors�for�determining�the�
scehdule�line�category�in�the�sales�document?�
Item�Category,�MRP�Type.�
What�does�the�sales�document�type�control?�
General�Data�
-�Can�the�document�be�entered�only�with�reference�
to�a�preceding�document?�
-�Should�the�existing�customer-material�info�record�
be�taken�into�consideration?�
-�Should�the�delivery�date�be�proposed?�
-�Must�a�customer�number�be�entered�when�creating�
a�document?�For�example,�product�proposals�can�be�
entered�without�reference�to�a�particular�customer.�
-�Which�order�probability�is�defined?�
-�Should�the�division�be�taken�from�the�material�
master�record�for�every�item�or�should�an�
alternative�division�specified�in�the�header�take�
-----------------------�Page�105-----------------------
precedence�over�the�item�specifications?�
-�How�should�the�system�respond�if�the�division�
entered�in�the�header�deviates�from�the�division�in�
the�items?�
-�Should�a�credit�limit�check�be�made?�
-�From�which�number�range�should�the�document�
number�for�internal�or�external�number�assignment�
come?�
-�Which�fields�are�relevant�for�the�incompletion�log?�
The�validity�period,�for�example,�is�important�for�
contracts�and�must�therefore�be�specified�in�the�
document.�
-�Can�an�incomplete�document�be�saved�or�must�all�
data�be�complete?�
-�Which�partner�functions�are�allowed�and�which�
ones�are�mandatory?�
Shipping�Data�
-�Which�delivery�type�should�the�delivery�resulting�
from�the�order�have?�
-�Should�delivery�scheduling�be�carried�out?�
-�Should�transportation�scheduling�be�carried�out?�
-�Should�a�delivery�block�be�set�automatically�for�a�
specific�reason?�For�example,�a�delivery�block�may�
be�appropriate�for�a�free-of-charge�delivery.�
-�You�can�define�shipping�conditions�for�a�sales�
-----------------------�Page�106-----------------------
document�type.�These�are�copied�into�the�document�
regardless�of�what�is�defined�in�the�customer�master�
record.�
Billing�Data�
Which�billing�type�should�the�invoice�resulting�from�
the�order�or�the�delivery�have?�
Should�a�billing�block�be�set�automatically�for�a�
specific�reason?�For�example,�a�billing�block�may�be�
appropriate�if�a�credit�memo�request�should�first�be�
checked�before�it�is�used�as�the�basis�for�a�credit�
memo.�
Can�the�sales�document�type�be�determined�by�the�
system?�
No.�
In�R/3,�can�you�automatically�substitute�one�product�
for�another?�How?�What�would�you�have�to�create?�
Yes.�Product�Selection�/�Material�Determination.�
Give�a�definition�of�replenishment�lead�time?�
Total�time�for�the�in-house�production�or�for�the�
external�procurement�of�a�product.�In�in-house�
production�the�replenishment�lead�time�is�
determined�to�cover�all�BOM�levels.�
What's�the�difference�between�checking�availability�
with�or�without�replenishment�lead�time�(RLT)?�
-----------------------�Page�107-----------------------
With�RLT�:�Availability�check�is�done�only�upto�end�
of�RLT.�If�material�is�not�available�the�date�on�which�
RLT�ends�is�displayed�as�Material�Availability�Date.�
Without�RLT�:�Availability�check�is�unrestricted.�
Displays�Delivery�Dates�as�on�which�partial�
deliveries�can�be�made�with�available�stock.�
Name�at�least�three�item�categories?�
Standard�Items�:�AFN,�AGN,�TAN.�
Free�of�charge�Items:�AFNN,�AGNN,�TANN.�
Non-stock�Items�:�AFX,�AGX,�TAX.�
Text�Items�:�AFTX,�AGTX,�TATX.�
Why�would�you�use�different�item�and�schedule�line�
categories?�
Item�categories�are�defined�to�provide�additional�
control�functions�for�the�sales�documents�and�thus�
meet�the�demands�resulting�from�the�different�
business�transactions.�
The�items�in�a�sales�document�are�divided�into�one�
or�more�schedule�lines.�These�schedule�lines�differ�
from�each�other�with�respect�to�date�and�quantity.�
For�some�schedule�lines,�material�requirements�
planning�is�not�carried�out;�for�other�schedule�lines,�
it�is�carried�out.�Also�goods�receipt,�not�goods�issue,�
is�posted�for�a�schedule�line�defined�in�a�returns�
document.�
Can�you�change�existing�standard�item�categories?�
Yes.�
-----------------------�Page�108-----------------------
Can�you�create�new�sales�order�types?�
Yes�.�
Different�dates�will�be�calculated�in�order�entry�
scheduling�.�Can�you�name�the�lead�time�variables�
that�will�be�taken�into�account?�
Transportation�lead�time,�Pick/pack�time,�Loading�
time,�Transit�time�.�
If�you�run�out�of�stock�in�a�specific�plant�can�you�
check�if�there�are�quantities�available�in�other�
plants?�
Yes.�
When�you�carry�out�availability�check,�which�
quantities�or�movements�can�the�system�take�into�
consideration?�
The�following�elements�can�be�included�in�the�
availability�check:�
Stocks�:�safety�stock,�stock�in�transfer,�stock�in�
quality�inspection,�blocked�stock.�
Inward�and�outward�movements�:�purchase�orders,�
purchase�requisitions,�planned�orders,�production�
orders,�reservations,�dependent�reservations,�
dependent�requirements,�sales�requirements,�
delivery�requirements.�
Give�some�examples�of�sales�document�types�
(description,�not�necessary�the�short�code)�that�
-----------------------�Page�109-----------------------
already�set�up�in�the�standard�system?�
Indicator�used�to�control�the�processing�of�the�
various�sales�documents�which�are�defined�in�the�
system.�E.g.,�OR,�SO,�BV,�KR.�Document�types�allow�
the�system�to�process�different�kinds�of�business�
transactions,�such�as�standard�orders�and�credit�
memo�requests,�in�different�ways.�
Can�you�maintain�texts�for�a�specific�customer�and�
store�them�in�the�system?�If�yes,�where?�
Yes.�Customer�Material�Information.�
When�the�system�checks�availability�which�
scheduling�would�it�use�first?�
Backward�Scheduling.�
Name�the�influencing�factors�for�the�determination�
of�the�availability�date?�
The�following�data�is�required�for�determining�this�
date:�
-�Route�from�the�shipping�point�to�the�ship-to�party�
location�
•�Shipping�point�from�which�the�goods�are�issued�
•�Loading�group�from�the�material�master�record�
•�Weight�group�determined�from�the�order�using�the�
order�quantity.�
Name�the�three�delivery�possibilities�when�there�is�
not�enough�stock�available?�
One�Time�Delivery,�Complete�Delivery,�Partial�
Deliveries.�
-----------------------�Page�110-----------------------
Can�you�think�of�an�example�why�you�would�have�to�
create�a�text�for�a�customer�and�copy�it�to�the�sales�
order?�
Customer�specific�instructions.�
What�is�the�function�of�item�category�group?�
The�item�category�group�determines�how�a�material�
is�processed�in�the�sales�order.�It�defines,�for�
example,�that�pricing�does�not�take�place�for�a�free�
of�charge�item,�such�as�a�business�gift;�or�that�
inventory�management�is�not�carried�out�for�a�
service.�When�processing�sales�and�distribution�
documents,�the�system�uses�the�item�category�
group�to�determine�the�item�category.�The�system�
determines�the�item�category�based�on�the�item�
category�group�of�the�material�and�the�current�
business�transaction,�and�proposes�it�in�the�
respective�document.�
When�creating�the�material�types�non-stock�material�
and�services,�DIEN�is�proposed�in�both�cases�for�the�
item�category�group,�because�the�order�processing�
for�both�material�types�is�identical:�for�example,�
pricing�is�carried�out�for�both,�but�no�availability�
check.�
On�sales�order,�when�the�system�confirms�20�pieces�
to�be�available�at�a�certain�date,�would�these�20�
pieces�still�be�available�for�other�new�sales�order�
coming�in�later?�
No.�
-----------------------�Page�111-----------------------
What�is�a�delivery�group�and�why�would�you�use�it?�
The�complete�delivery�and�delivery�group�functions�
enable�you�to�combine�some�or�all�of�the�items�in�a�
sales�order�so�that�they�are�delivered�to�the�
customer�together.�The�system�determines�
automatically�the�latest�delivery�date�possible�for�
the�delivery�group�and�adjusts�the�schedule�lines�
accordingly.�Corresponding�requirements�for�
material�requirements�planning�(MRP)�are�changed�
or�re-determined.�
What�is�backorder�processing?�
The�backorder�processing�functions�enable�you�to�
list�relevant�sales�documents�for�specific�materials�
and�process�them�from�the�point�of�view�of�
availability.�You�can�assign�available�to�promise�
(ATP)�stock�to�outstanding�order�quantities.�In�
addition,�you�can�withdraw�already�confirmed�
quantities�and�reassign�them�to�different�items.�
Backorder�processing�is�only�available�for�materials�
with�individual�requirements.�
Can�you�link�items�in�a�sales�order?�If�yes,�when�
would�you�do�that?�
Yes.�Promotional�Items.�
For�what�would�you�use�BOM‟S�in�sales?�What�two��
methods�of�BOM�processing�do�you�have�in�sales�
order�entry?�How�can�you�control�if�the�system�
-----------------------�Page�112-----------------------
should/should�not�explode�a�BOM�in�the�sales�
order.�
A�bill�of�material�(BOM)�describes�the�different�
components�that�together�create�a�product.�A�BOM�
for�a�bicycle,�for�example,�consists�of�all�the�parts�
that�make�up�the�bicycle:�the�frame,�the�saddle,�
wheels,�and�so�on.�When�you�enter�the�material�
number�of�a�bill�of�materials�that�is�relevant�for�
sales�order�processing,�the�system�displays�the�
material�that�describes�the�whole�bill�of�materials�as�
a�main�item.�The�components�are�displayed�as�sub-�
items.�
•�Processing�by�Main�Item�:�ERLA�&�Processing�by��
Sub-Item�:�LUMF�
•�BOM�explosion�can�be�prevented�by�specifying��
Item�Category�Group�as�NORM.�
Credit�limit�checks�is�an�example�of�a�very�close�link�
between�which�two�SAP�modules?�
SD�&�FI.�
What�are�the�two�techniques�in�delivery�scheduling?�
Backward�Scheduling�&�Forward�Scheduling.�
How�does�a�third�party�deal�work?�Do�you�use�a�
special�sales�order�type�for�that?�How�could�the�
system�know�that�you�want�to�process�a�third�party�
deal?�
By�specifying�item�category�as�TAS�using�double-line�
entry�in�the�sales�order.�
-----------------------�Page�113-----------------------
No�special�order�type�is�available.�
By�the�item�category�group�and/or�material�type�in�
Material�Master�.�
Name�the�several�steps�in�consignment�processing.�
Consignment�fill-up,�Consignment�issue,�
Consignment�pick-up,�Consignment�return.�
What‟s�the�difference�between�consignment�pick-up�
and�consignment�return?�
•�In�consignment�pick-up,�customer�returns�
consignment�stock.�When�goods�issue�is�posted,�the�
relevant�quantity�is�deducted�from�the�customer's�
special�stock�and�is�added�back�to�regular�stock�at�
the�plant�where�the�goods�are�returned.�Total�
valuated�stock�remains�the�same�since�the�returned�
stock�was�regarded�as�part�of�inventory�even�while�
it�was�at�the�customer's�premises.This�transaction�is�
not�relevant�for�billing.�
•�In�consignment�return,�customer�wishes�to�claim�
on�consignment�goods�which�have�already�been�
issued.�When�goods�issue�is�posted,�the�relevant�
quantity�is�added�to�the�customer's�special�stock�at�
the�plant�where�the�goods�are�returned.�Since�the�
ownership�of�the�goods�is�passed�from�the�customer�
back�to�the�company,�the�transaction�is�relevant�for�
billing.�In�this�case,�the�customer�receives�a�credit�
memo�for�the�returned�goods.�
-----------------------�Page�114-----------------------
Can�you�control�that�an�end�user�cannot�copy�a�
quote�of�customer�A�to�a�sales�order�for�customer�
B?�If�yes,�where?�
Yes.�By�customizing�Copying�Control�for�header�
data.�
Give�some�example�for�data�that�is�copied�from�the�
customer�(sold-to,�payer,�ship-to)�to�the�sales�order�
as�well�as�for�data�that�is�copied�from�the�material?�
•�General�data,�payment�terms,�shipping�details,�
delivery�agreements,�delivering�plant.�
What�is�returnable�packaging�processing?�
Returnable�packaging�consists�of�materials�that�are�
stored�at�the�customer�location�but�which�remain�
the�property�of�the�company.�The�customer�is�only�
required�to�pay�for�the�returnable�packaging�if�he�
does�not�return�it�by�a�specified�time.�
Name�the�two�outline�agreements�in�R/3�standard�
and�explain�the�difference�between�them.�
Agreements�are�arrangements�between�business�
partners�regarding�the�granting�of�conditions�over�a�
specified�time�period.�The�agreement�contains�
conditions�which�apply�over�a�particular�time�period�
and�which�are�settled�together�at�the�same�points�in�
time.�An�agreement�can�be�settled�once�or�
periodically.�The�two�outline�agreements�include�
Contracts�and�Scheduling�Agreements.�
Unlike�a�contract�-�which�only�contains�an�overall�
target�quantity�or�value�-�a�scheduling�agreement�
-----------------------�Page�115-----------------------
also�contains�specific�order�quantities�and�delivery�
dates.�
How�many�documents�do�you�create�when�you�
release,�deliver�and�invoice�the�first�order�from�a�
contract?�
Three�:�Sales�order,�Delivery�note,�Invoice.�
What�types�of�output�can�you�have�in�sales?�
Printer,�Telex,�Fax,�Mail,�EDI.�
Can�you�automate�output�processing�?�Do�you�
always�have�to�specify�it�manually?�
yes.�No.�
Where�would�you�specify�which�data�should�be�
copied�(at�header,�item�and�schedule�line�level)when�
you�copy�from�one�document�to�another�one?�
Customizing�Copy�Control.�
SHIPPING�
Describe�the�flow�of�data�from�the�sales�order�into�
the�delivery�for�header�and�item�and�schedule�line�
level�data?�
Header�à�Header�
Item�à�Header,�Item.�
Schedule�line�à�Item.�
Can�you�combine�several�sales�orders�into�one�
delivery�document�?�If�no,�why�not?�If�yes,�would�
-----------------------�Page�116-----------------------
the�system�check�certain�criteria?�What�criteria?�
No.�When�ship-to�party�or�plant�is�different.�
Yes.�Availability�of�all�items�are�confirmed.�
Name�a�few�prerequisites�that�have�to�be�fulfilled�if�
you�want�to�create�a�delivery�for�the�order.�
Header�Level�
There�cannot�be�a�delivery�block�at�header�level.�
The�sales�document�must�contain�at�least�one�item�
due�for�delivery�before�a�delivery�can�be�created�for�
this�document.�
Item�Level�and�Schedule�Line�Level�
The�schedule�line�must�be�due�for�shipping�on�the�
specified�selection�date.�
A�schedule�line�becomes�due�for�shipping�as�soon�as�
the�material�availability�date�or�the�transportation�
scheduling�date�is�reached.�
The�schedule�line�cannot�be�blocked�for�delivery.�
The�delivery�quantity�must�be�greater�than�one.�
The�items�in�the�order�must�be�fully�processed.�
If�they�are�incomplete,�you�must�first�edit�the�
incompleteness�log�in�the�order.�You�will�find�
information�on�the�incompleteness�log�in�the�R/3�SD�
online�documentation�on�sales.�
The�product�status�of�the�material�must�permit�
delivery.�
For�example,�the�product�status�for�new�products�
which�have�not�been�released�for�delivery�does�not�
allow�them�to�be�included�in�a�delivery.�
Sufficient�quantity�of�the�material�must�be�
-----------------------�Page�117-----------------------
available.�
If�you�create�a�delivery,�would�this�automatically�
update�the�sales�order?�
Yes.�The�delivery�status�of�the�entire�order�results�
from�the�delivery�status�of�the�items.�Until�all�items�
in�the�order�have�been�fully�delivered,�the�order�has�
the�status�"Partially�delivered".�The�entire�document�
acquires�the�status�of�fully�delivered�once�all�the�
items�have�been�fully�delivered.�
Name�the�different�ways�of�creating�deliveries.�
Partial�Deliveries,�Complete�Deliveries,�Deliveries�
without�reference,�Grouped�Deliveries.�
How�does�the�system�determine�the�shipping�point�
and�the�route�in�the�sales�order?�
A�shipping�point�can�be�determined�for�each�order�
item.�How�the�shipping�point�is�determined�depends�
on�three�factors:�
The�shipping�conditions�from�the�customer�master�
record�(Shipping�screen).�A�condition�might�be�that�
the�goods�are�to�be�delivered�to�the�customer�as�
soon�as�possible.�
The�loading�group�from�the�material�master�record�
(Sales/Plant�Data�screen).You�could,�for�example,�
specify�a�loading�group�that�defines�that�the�goods�
must�always�be�loaded�with�a�crane�or�a�fork�lift.�
The�delivering�plant.�This�plant�is�determined�per�
order�item�either�from�the�customer�master�record�
or�from�the�material�master�record.�However,�you�
-----------------------�Page�118-----------------------
can�also�enter�it�manually�for�each�order�item.�You�
will�find�detailed�information�on�determining�the�
delivering�plant�in�the�sales�order�in�the�R/3�SD�
online�documentation�on�sales.�
Can�you�change�the�shipping�point�determined�in�
the�sales�order�manually?�
Yes.�
If�you�have�several�shipping�points�in�a�sales�order�
at�item�level.�What�would�that�have�on�the�
delivery?�
Each�item�will�individual�deliveries.�
Why�would�you�carry�out�route�determination�in�the�
delivery�again?�
To�reconfirm�the�weight�of�the�item.�
At�which�different�levels�can�you�specify�pick/pack�
and�loading�time?�
Shipping�point�determination�level�:�loading�time.�
Route�determination�level�:�pick/pack�time.�
Where�do�you�specify�the�departure�zone�and�the�
arrival�zone�for�route�determination?�
Shipping�point,�Ship-to�party.�
How�can�the�route�influence�the�material�availability�
date?�
Transit�time�&�Transportation�lead�time.�
-----------------------�Page�119-----------------------
Why�would�you�carry�out�availability�check�in�the�
delivery?�
The�availability�check�is�calculated�using�planned�
inward�and�outward�movements�of�goods.�Therefore�
the�delivery�situation�might�have�changed�in�the�
meantime�due�to�unforeseen�circumstances,�such�as�
lost�output.�The�availability�check�in�the�delivery�
takes�any�such�changes�into�account.�
Where�would�you�store�partial/complete�shipment�
agreements�and�over/under�delivery�tolerances?�
Customer�Master�and�Customer�Material�
Information.�
Explain�the�effects�of�printing�out�the�picking�list.�
Updates�the�picking�quantity�in�the�delivery.�
How�does�the�system�automatically�determine�the�
picking�storage�location�in�the�delivery?�
Storage�Condition.�
Shipping�Point.�
Plant.�
What�is�a�transfer�order�and�for�what�would�you�use�
it?�
Document�used�to�support�every�stock�movement�in�
the�warehouse.�
It�contains�all�the�important�movement�data,�such�
as�the�material�to�be�transferred,�the�quantity�to�be�
transferred,�the�storage�bins�involved,�and�so�on�
-----------------------�Page�120-----------------------
Define�a�shipping�unit?�
Combination�of�materials�which�are�packed�together�
in�a�shipping�material�at�a�particular�time.�
Shipping�units�contain�items�which�in�turn�are�made�
up�of�shipping�units�or�delivery�items.�
What�effects�does�goods�issue�have?�
When�the�goods�have�left�your�plant,�the�business�
transaction�is�regarded�as�completed�from�the�point�
of�view�of�shipping.�When�goods�are�issued,�the�
following�functions�take�place�in�the�system:�
The�material�stock�is�reduced�by�the�goods�issue�
quantity�and�the�corresponding�value�changes�take�
place�in�accounting.�This�ensures�that�the�quantity�
and�value�flows�are�parallel.�
Material�requirements�for�the�delivery�are�reduced�
The�delivery�status�is�updated�
If�you�bill�after�goods�issue,�the�delivery�enters�the�
billing�work�list�
How�can�you�delete�a�good�issue?�
You�cannot�cancel�a�goods�issue�posting�in�isolation.�
You�are�also�unable�to�change�goods�issue�
quantities.�If�you�make�a�mistake�when�processing�a�
delivery,�or�if�the�goods�are�damaged�leaving�your�
plant�and�cannot�be�delivered,�you�must�cancel�the�
entire�business�transaction.�
Procedure�
After�you�have�invoiced�the�delivery,�for�which�the�
-----------------------�Page�121-----------------------
incorrect�goods�issue�posting�was�carried�out,�
proceed�as�follows:�
1.�Enter�a�returns�order�(order�type�RE)�for�the�
customer�and�the�material�involved.�
2.�Create�a�returns�delivery�for�the�returns�order.�
The�system�proposes�the�delivery�type.�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.�The�
system�automatically�recognizes�the�returns�delivery�
as�goods�receipt�and�clears�the�original�goods�issue�
posting�by�carrying�out�reverse�posting.�
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.�
Is�it�possible�to�work�without�specifying�a�pick/pack�
or�loading�time�for�a�shipping�point?�
Yes.�
When�do�you�initiate�packing�activity-before�or�after�
goods�issue?�What�is�the�material�type�for�shipping�
material?�
Before�goods�issue�.�VERP.�
When�you�post�goods�issue�after�packing,�which�two�
documents�do�you�create?�
Picking�List,�Invoice.�
Can�the�delivery�quantity�and�the�picking�quantity�in�
the�delivery�document�be�-different?�
-----------------------�Page�122-----------------------
Yes.�
PRICING�
Could�you�explain�what�condition�technique�in�SAP�
is?�
Hierarchy�of�elements�defining�a�data�combination�
which�leads�to�certain�actions.�
In�pricing�the�condition�technique�refers�to�the�
method�by�which�the�system�determines�prices�from�
information�stored�in�condition�records.�In�Sales�and�
Distribution,�the�various�elements�used�in�the�
condition�technique�are�set�up�and�controlled�in�
Customizing.�During�sales�order�processing,�the�
system�uses�the�condition�technique�to�determine�a�
variety�of�important�pricing�information.�
Name�three�areas/processes�which�use�condition�
technique�in�SD?�
Material�determination,�Output�determination,�
Account�determination.�
What�are�the�four�basic�elements�of�condition�
technique?�
Condition�Types,�Condition�Tables,�Access�
Sequences,�Pricing�Procedures.�
Please�explain�graphically�the�relationship�between�
the�four�basic�elements�in�condition�techniques?�
Procedures�à�Condition�Types�à�Access�Sequence�à�
-----------------------�Page�123-----------------------
Condition�Tables�à�Condition�Records.�
Explain�what�a�pricing�procedure�is?�
The�primary�job�of�a�pricing�procedure�is�to�define�a�
group�of�condition�types�in�a�particular�sequence.�
The�pricing�procedure�also�determines:�
-�Which�sub-totals�appear�during�pricing�
-�To�what�extent�pricing�can�be�influenced�manually�
-�Which�method�the�system�uses�to�calculate�
percentage�discounts�and�surcharges�
-�which�requirements�for�a�particular�condition�type�
must�be�fulfilled�before�the�system�takes�the�
condition�into�account.�
Explain�what�a�condition�table�and�an�access�
sequence�is�and�the�relationship�between�them?�
A�condition�table�defines�the�combination�of�fields�
(the�key)�that�identifies�an�individual�condition�
record.�A�condition�record�is�how�the�system�stores�
the�specific�condition�data�that�you�enter�in�the�
system�as�condition�records.�For�example,�when�you�
enter�the�price�for�a�product�or�a�special�discount�for�
a�good�customer,�you�create�individual�condition�
records.�
An�access�sequence�is�a�search�strategy�that�the�
system�uses�to�find�valid�data�for�a�particular�
condition�type.�It�determines�the�sequence�in�which�
the�system�searches�for�data.�The�access�sequence�
consists�of�one�or�more�accesses.�The�sequence�of�
the�accesses�
-----------------------�Page�124-----------------------
establishes�which�condition�records�have�priority�
over�others.�The�accesses�tell�the�system�
where�to�look�first,�second,�and�so�on,�until�it�finds�a�
valid�condition�record.�You�specify�an�access�
sequence�for�each�condition�type�for�which�you�
create�condition�records.�
What�is�a�condition�type?�What�are�the�two�main�
groups�of�condition�types?�
A�condition�type�is�a�representation�in�the�system�of�
some�aspect�of�your�daily�pricing�activities.�For�
example,�you�can�define�a�different�condition�type�
for�each�kind�of�price,�discount,�or�surcharge�that�
occurs�in�your�business�transactions.�
Fixed�Amount�&�Percentage.�
Is�SD�the�only�module�that�uses�condition�
technique?�
No.�
What�is�a�condition�supplement�and�why�would�you�
use�it?�
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�
-----------------------�Page�125-----------------------
for�which�condition�types�you�want�to�use�condition�
supplements�in�Customizing�for�Sales.�
Which�partner�function�is�relevant�when�it�comes�to�
tax�calculation�in�the�sales�order?�
Ship-to�party.�
Name�at�least�three�different�condition�types�in�
pricing?�
Price,�Discounts,�Freight.�PROO,�K007,�KF00.�
You�can�create�scales�for�prices�and�discounts.�
Name�the�four�possible�scale�basis�in�R/3.�
Value,�Quantity,�Gross�weight,�Net�weight,�Volume.�
Where�would�you�specify�that�a�condition�type�is�a�
discount�or�a�surcharge?�
In�Condition�Type�Details�Screen.�
If�somebody�adds�price�elements�manually�in�the�
sales�order�or�if�somebody�changes�a�discount�the�
system�determined�automatically,�do�you�have�a�
possibility�to�see�that�in�the�sales�order?�
Yes.�
You�want�to�list�all�condition�records�for�a�certain�
material�or�a�certain�sales�organization.�
How�would�you�do�that?�
By�creating�Pricing�Reports.�
Does�the�pricing�procedure�apply�for�the�pricing�data�
at�item�level�or�for�the�pricing�data�at�header�level?�
Both.�
-----------------------�Page�126-----------------------
When�you�create�a�header�condition�manually�in�the�
sales�order�the�system�can�copy�the�values�in�
different�ways�to�the�items.�Where�would�you�
specify�how�the�system�should�process?�
Condition�Type.�
Which�data�do�you�have�to�maintain�in�SD�so�that�
the�system�can�determine�the�sales�taxes�in�the�
sales�order�automatically?�
Tax�rate�with�or�without�Jurisdiction.�
What�does�the�condition�exclusion�indicator�do�for�
you?�
The�system�can�exclude�conditions�so�that�they�are�
not�taken�into�account�during�pricing�in�sales�
documents.�
Can�you�explain�what�a�statistical�condition�is?�Give�
an�example�for�a�statistical�condition?�
VPRS.�
For�what�do�you�use�customer�hierarchies?�
Pricing�,�Rebate.�
Can�you�track�cumulative�values�in�R/3?�If�yes,�it�
could�be�based�on�what?�
Yes.�Maximum�Value,�Maximum�Orders,�Maximum�
Quantity.�
If�you�want�to�make�sure�that�conditions�records�
apply�for�a�certain�time�period�only�what�would�you�
have�to�do?�
Validity�Period�to�be�specified�in�condition�record.�
What�is�a�group�condition?�
Condition�which�can�be�used�to�determine�a�scale�
value�based�on�more�than�one�item�in�a�document.�
-----------------------�Page�127-----------------------
The�system�groups�the�items�using�either�the�
condition�key�for�the�appropriate�condition�record�or�
a�separately�defined�condition�key.�
Name�the�influencing�factors�for�pricing�procedure�
determination�during�sales�order�entry?�
Customer,�Sales�Document�Type�and�Sales�Area.�
Can�you�copy�condition�records?�If�yes,�are�there�
any�restrictions?�
Yes.�Field�specific.�
If�you�create�a�new�condition�type-do�you�also�have�
to�create�a�new�condition�table�and�a�new�access�
sequence?�
Yes.�
Where�can�you�specify�that�a�condition�is�
mandatory?�
In�Pricing�Procedure.�
Tax�jurisdiction�processing�is�a�close�link�between�
which�two�modules?�
FI�&�SD.�
Do�you�have�to�create�a�condition�record�for�taxes�in�
the�SD�application?�
Yes.�
BILLING�
Name�several�billing�types?�
F1�:�Order�related�Invoice�F2�:�Delivery�related�
invoice.�
-----------------------�Page�128-----------------------
F5�:�Proforma�Invoice�for�Sales�Order�F8�:�Proforma�
Invoice�for�Delivery.�
Can�you�delete�an�invoice?�
No.�You�can�cancel�it�and�create�cancellation�
document.�
When�you�create�an�invoice�in�SD,�how�do�you�post�
it�to�FI?�
Select�Billing�document�à�Release�To�Accounting.�
The�system�displays�a�message�that�the�accounting�
document�has�been�saved.�If�the�billing�document�
contains�an�error,�the�reason�for�not�forwarding�the�
document�is�displayed.�If�the�release�was�successful,�
the�posting�status�in�the�billing�document�is�set�to�C�
(accounting�document�has�been�created).�You�find�
the�posting�status�by�selecting�Header�à�Details�in�
the�billing�document.�
When�you�create�an�invoice�can�you�carry�out�
pricing�again?�
Yes.�
From�which�documents�can�you�create�a�proforma�
invoice?�
Based�on�sales�order�or�delivery.�
Do�you�transfer�a�proforma�invoice�to�FI�?�If�yes,�
how?�If�no,�how�do�you�customize�the�system�in�a�
way�that�the�proforma�invoice�is�not�transferred�to�
-----------------------�Page�129-----------------------
FI?�
No.�Billing�status�not�assigned�to�proforma�invoice.�
Posting�bock�in�the�billing�document.�
When�you�create�a�credit�memo�request�do�you�
always�have�to�refer�to�a�sales�order�or�any�other�
previous�document?�
Only�sales�order.�
In�R/3�how�can�you�make�sure�that�invoices�for�a�
customer�are�always�created�at�a�specific�date?�
Billing�Schedule.�
Can�you�combine�deliveries�into�one�invoice?�When�
would�you�do�that?�
Yes.�If�the�header�data�and�header�partners�for�
specified�delivery�or�sales�order�are�identical�and�if�
requirements�for�splitting�do�not�apply.�
Can�you�combine�orders�into�one�invoice?�
Yes.�
Can�you�split�deliveries�into�several�invoices?�When�
would�you�do�that?�
Yes�.�If�the�data�from�the�related�reference�
documents�differs�in�the�header�fields�of�the�billing�
document.�The�system�will�automatically�split�the�
invoice.�
For�what�do�you�use�the�billing�due�list?�What�
previous�step�in�the�process�is�necessary�that�a�
-----------------------�Page�130-----------------------
delivery�appears�in�the�billing�due�list?�
Selection�criteria�–�sold-to�party,�billing�date�or�
receiving�partner.�
a.�a)�separate�invoice�for�each�delivery�
b.�b)�split�one�sales�order�for�delivery�into�several�
invoices.�
c)�combine�several�sales�orders�for�delivery�into�one�
invoice.�
Name�the�five�possible�influencing�factors�for�
account�determination�for�invoices?�
Chart�of�accounts�of�the�company�code�
Sales�organization�
Account�assignment�group�of�the�customer�(from�
the�customer�master�record,�Billing�screen,�Account�
group�field)�
Account�assignment�group�of�the�material�(from�the�
material�master�record,�Sales�2�screen,�Account�
assignment�group�field)�
Account�key�(from�the�pricing�procedure)�
Can�one�business�area�be�valid�for�several�company�
codes?�
Yes.�
What�are�the�two�possible�ways�to�transfer�sales�
data�to�business�areas?�Where�do�you�specify�which�
way�you�want�to�use?�
sales�area�(if�the�accounts�are�to�be�posted�
according�to�sales)�
-----------------------�Page�131-----------------------
plant/division�(if�the�accounts�are�to�be�posted�
according�to�products)�
There�is�an�interface�between�SD�and�FI�in�invoicing�
.�can�you�think�of�another�interface�between�SD�and�
FI?�
Credit�check,�Tax�calculation,�Cost�estimate.�
What�is�rebate�processing?�
A�rebate�is�a�special�discount�which�is�paid�
retroactively�to�a�customer.�This�discount�is�based�
on�the�customer's�sales�volume�over�a�specified�
time�period�
What�is�an�invoice�list?�Which�prerequisite�are�
necessary�to�use�an�invoice�list?�How�does�an�
invoice�list�differ�from�a�collective�invoice?�
Invoice�lists�let�you�create,�at�specified�time�
intervals�or�on�specific�dates,�a�list�of�billing�
documents�(invoices,�credit�and�debit�memos)�to�
send�to�a�particular�payer.�
The�billing�documents�in�the�invoice�list�can�be�
single�or�collective�documents�(collective�invoices�
combine�items�from�more�than�one�delivery).�
The�standard�version�of�the�SAP�R/3�System�
includes�two�types�of�invoice�lists:�
-�for�invoices�and�debit�memos�
-�for�credit�memos�
If�you�wish,�you�can�process�invoices,�debit�memos,�
and�credit�memos�at�the�same�time.�The�system�
-----------------------�Page�132-----------------------
automatically�creates�a�separate�invoice�list�for�
credit�memos.�
Prerequisites�for�Invoice�Lists�
You�can�process�invoice�lists�providing�that�the�
following�prerequisite�data�is�defined�by�your�system�
administrator�in�Customizing�for�Sales:�
-�Condition�type�RL00�(factoring�discount)�must�be�
maintained�and,�if�required,�condition�type�MW15�
(VAT:�factoring�discount�tax)�
-�An�invoice�list�type�must�be�assigned�to�each�
billing�type�that�you�want�to�process�in�invoice�lists�-�
the�standard�version�of�the�SAP�R/3�System�includes�
two�invoice�list�types:�LR�for�invoices�and�debit�
memos,�LG�for�credit�memos�
-�Copying�requirements�must�be�defined�(for�
example,�the�payer,�terms�of�payment,�and�other�
fields�that�must�be�identical�in�the�documents�to�be�
included�in�the�invoice�list)�
In�addition,�before�you�process�an�invoice�list,�you�
must�maintain�the�following�master�data:�
-�A�customer�calendar�must�be�defined,�specifying�
the�time�intervals�or�dates�on�which�invoice�lists�are�
to�be�processed�
-�The�customer�calendar�must�be�entered�in�the�
Billing�view�of�the�customer�master�record�of�the�
payer�(field:�Inv.�list�sched.)�
-�Pricing�condition�records�for�the�condition�type�
RL00�and,�if�necessary,�MW15�
Output�condition�records�for�condition�types�LR00�
(invoice�list)�and�RD01�(single�invoice)�
-----------------------�Page�133-----------------------
Collective�Invoice�
If�the�header�data�and�the�header�partners�for�the�
specified�deliveries�or�sales�orders�are�identical�and�
if�the�requirements�for�splitting�do�not�apply,�one�
billing�document�is�created�for�all�the�deliveries�or�
sales�orders.�
What�is�a�product�hierarchy�and�for�what�can�it�be�
used?�
Alphanumeric�character�string�for�grouping�materials�
by�combining�various�characteristics.�The�product�
hierarchy�is�used�for�evaluation�and�pricing�
purposes.�
In�Product�Cost�Controlling�(CO-PC)�:�Structure�
consisting�of�the�plant,�product�group,�product,�and�
order.�Used�for�the�interactive�analysis�of�the�
product�costs�for�each�level�of�the�hierarchy.�
Can�you�name�the�two�types�of�billing�plans�in�the�
standard�R/3�system?�
Periodic�billing,�Milestone�billing.�
Can�you�partially�settle�rebate�accruals?�
Yes.�
For�what�would�you�use�a�lump�sum�payment?�
A�lump�sum�payment�is�a�special�condition�which�
does�not�depend�on�sales�volume�but�on�a�
promotional�performance�such�as�a�front�of�store�
display�or�a�local�advertisement.�
-----------------------�Page�134-----------------------
CUSTOMIZING�
Explain�what�the�IMG�is?�
Tool�for�configuring�the�SAP�System�to�meet�
customer�requirements.�Also�referred�to�as�the�
'Implementation�Guide'.�
Explain�how�you�can�use�the�R/3�project�
Management�in�an�implementation?�
For�each�business�application,�the�implementation�
guide�
explains�all�the�steps�in�the�implementation�process�
tells�you�the�SAP�standard�(factory)�settings�
describes�system�configuration�work�(activities)�and�
opens�the�activities�interactively.�
Implementation�guides�are�structured�as�hypertext.�
The�hierarchical�structure�reflects�the�structure�of�
the�R/3�business�application�components,�and�lists�
all�the�documentation�to�do�with�implementing�the�
R/3�System.�
Once�you�have�activated�the�company�IMG�can�you�
still�add�modules/areas?�
Yes.�
If�you�deactivate�the�module�CO�in�the�company�
IMG�could�you�still�select�the�CO�module�in�a�project�
you�create?�
No.�
-----------------------�Page�135-----------------------
Is�it�possible�to�link�R/3�projects�to�the�MS�project?�
Yes.�
What�is�the�procedure�model�and�how�can�it�be�used�
in�an�implementation?�
The�R/3�Procedure�Model�is�both�the�methodological�
framework�for�the�implementation�and�upgrade�
processes�and�a�powerful�tool�that�supports�you�at�
every�stage�of�the�implementation�process.�
The�R/3�Procedure�Model�provides�
all�the�fundamental�understanding�you�need�at�the�
cross-application�level�for�implementing�R/3�
application�components�successfully,�
a�hierarchically-structured�plan�of�the�activities,�
a�correct�sequence�of�the�activities�
the�link�to�the�system�setting�activities�
Explain�shortly�what�the�SAP�business�Navigator�is�
and�how�it�can�be�used�in�an�implementation.�
The�Reference�Model�integrated�into�the�R/3�
System�
The�various�ways�into�Business�Navigator�(the�
views)�help�you�call�just�the�models�and�list�displays�
you�need�in�the�R/3�Reference�Model�
You�can�access�other�R/3�System�components�
directly�from�the�models,�
for�example:�data�models,�transactions,�
documentation.�
What�two�ways�of�number�assignment�for�
documents�or�master�data�do�you�know?�Explain�the�
-----------------------�Page�136-----------------------
difference�between�them.�
Internal�&�External.�
Can�you�share�master�data�between�several�sales�
areas?�
Yes.�
What�does�the�account�group�of�the�customer�
control?�
Number�assignment,�Screen�Layout.�
What�are�the�two�influence�factors�for�field�selection�
for�customer�master�record�maintenance?�
Account�Group,�Transactions.�
Name�at�least�five�features�that�you�can�control�for�
the�sale�document�type?�
Text,�Partner,�Pricing,�Taxes,�Output,�Delivery.�
Give�an�example�of�when�you�would�specify�that�a�
sales�document�can�only�be�created�referencing�
another�sales�document?�
Returns�can�only�be�created�referencing�sales�
order.�
Why�do�you�have�different�sales�document�types�in�
R/3?�
For�business�transactions.�
Name�at�least�three�features�controlled�by�the�sales�
document�type?�
-----------------------�Page�137-----------------------
Pricing,�Taxes�,�Delivery.�
Name�at�least�five�features�that�you�can�control�for�
the�item�category?�
Pricing,�Relevance�for�delivery,�Relevance�for�billing,�
Incompletion�log,�Partner,�Tax.�
Name�at�least�five�features�that�you�can�control�for�
the�schedule�line�category?�
Relevance�for�delivery,�Availability�check,�Transfer�
of�Requirements,�Goods�Movement,�Purchasing�and�
Incompletion�log.�
Explain�how�the�system�can�automatically�determine�
the�item�category�in�the�sales�order.�
Sales�document�type�+�Higher�level�Item�category�+�
Item�category�group�+�Item�Usage.�
Explain�how�the�system�can�automatically�determine�
the�schedule�line�category�in�the�sales�order?�
Item�category�+�MRP�type.�
Once�the�system�determined�the�item�level�schedule�
line�category�automatically�in�the�sales�order,�can�
you�still�change�it�manually?�
Yes.�
At�which�levels�in�the�sales�document�can�you�have�
different�incompletion�procedures?�
Sales�Document�Type,�Item�Category,�Schedule�Line�
Category,�Partner�Functions,�Sales�Activities.�
What�is�the�item�category�group?�Where�do�you�
maintain�it?�
-----------------------�Page�138-----------------------
The�item�category�group�determines�how�a�material�
is�processed�in�the�sales�order.�It�defines,�for�
example,�that�pricing�does�not�take�place�for�a�free�
of�charge�item,�such�as�a�business�gift;�or�that�
inventory�management�is�not�carried�out�for�a�
service.�When�processing�sales�and�distribution�
documents,�the�system�uses�the�item�category�
group�to�determine�the�item�category.�The�system�
determines�the�item�category�based�on�the�item�
category�group�of�the�material�and�the�current�
business�transaction,�and�proposes�it�in�the�
respective�document.�
When�creating�the�material�types�non-stock�material�
and�services,�DIEN�is�proposed�in�both�cases�for�the�
item�category�group,�because�the�order�processing�
for�both�material�types�is�identical:�for�example,�
pricing�is�carried�out�for�both,�but�no�availability�
check.�
It�is�maintained�in�the�material�master.�
What�do�you�control�at�item�category�level�in�the�
delivery?�
Relevance�for�Picking,�Determination�of�Picking�
Location,�Minimum�Delivery�Quantity.�
Do�you�have�schedule�lines�in�the�delivery?�
No.�
Item�categories�from�the�sales�order�are�copied�into�
the�delivery.�What�happens�if�you�add�a�new�item�in�
the�delivery�–�how�can�the�system�still�automatically�
-----------------------�Page�139-----------------------
determine�the�item�category�for�the�delivery?�If,�
yes,�what�do�you�have�to�do?�
You�can�only�enter�an�item�that�is�not�dependent�on�
an�order�in�a�delivery�if�the�delivery�permits�the�
item�category�for�that�item.�The�item�category�is�
determined�on�the�basis�of�the�delivery�type�and�
item�category�group�in�the�material�master�record.�
Thus,�items�for�which�an�order�has�to�be�created�
first�cannot�be�added�to�a�delivery.�Which�materials�
can�be�included�in�a�delivery,�depend�on�your�
system�configuration.�In�the�standard�version�of�the�
SAP�R/3�System,�only�materials�with�the�item�
category�VERP�can�be�added�to�a�delivery.�
What�does�the�billing�type�control?�
The�document�number�
The�partner�functions�allowed�at�header�level�
The�partner�functions�allowed�at�item�level�
The�billing�type�that�can�be�used�to�cancel�the�billing�
document�
The�transfer�status�of�the�billing�document:�
Transferred�to�financial�accounting�
blocked�from�transfer�
not�transferred�
The�procedure�for�account�assignment�in�Financial�
Accounting�
The�allowed�output�for�a�business�transaction�and�
the�procedure�for�output.�
-----------------------�Page�140-----------------------
When�you�think�of�the�document�flow�–�what�do�you�
control�for�it�in�customizing?�
You�can�specify�for�a�particular�sales�document�type,�
which�document�type�is�to�be�assigned�to�copied�
reference�documents,�and�which�item�categories�or�
schedule�line�categories�are�to�be�copied.�
You�must�also�make�specifications�for�copying�
requirements�and�data�transfer,�as�well�as�quantity�
and�value�updates�in�document�flow.�This�must�be�
done�for�each�copying�procedure�at�header,�item�
and,�if�necessary,�schedule�line�level�on�a�detail�
screen.�
You�can�specify�partner�procedures�for�the�customer�
master�(linked�to�the�account�group)�and�you�can�
specify�partner�procedures�for�the�sales�document.�
Can�you�have�different�partner�procedure�at�sales�
document�type�and�item�category�level?�If�yes,�why�
would�you�want�to�have�different�procedures�for�the�
item�category?�
Yes.�Different�Ship-to�party.�
What�is�a�partner�type?�Give�some�example?�
The�partner�type�is�an�indicator�which�informs�you�
of�the�type�of�partner,�for�example,�partner�type�
customer�"KU".�
You�want�to�set�up�a�new�condition�type.�Name�the�
necessary�steps�you�have�to�do�If�you�want�the�
system�to�determine�the�new�condition�type�
automatically�during�sales�order�entry?�
-----------------------�Page�141-----------------------
Check�to�what�extent�you�can�use�the�condition�
types�contained�in�the�standard�SAP�R/3�System.�
Create�new�condition�types�by�copying�a�similar�
conditions�type�and�changing�it�according�to�your�
requirements.�One�reason�for�creating�a�new�
condition�type�is�you�may�require�a�calculation�rule�
for�a�discount�which�is�not�available�in�the�standard�
system.�
Specify�an�alphanumeric�key�which�can�have�up�to�4�
digits,�and�a�textual�description.�
Specify�an�access�sequence�for�the�condition�types.�
You�do�not�need�to�specify�an�access�sequence�for�
header�conditions.�
-�Maintain�the�detail�screen�of�the�condition�type.�
You�can�also�assign�a�reference�condition�type�if�the�
condition�types�you�are�working�with�are�similar.�
Then�you�will�only�have�to�maintain�condition�
records�for�the�reference�condition�type.�
In�addition,�you�can�define�the�upper�and�lower�
limits�for�the�value�of�a�condition�at�condition�type�
level.�This�way,�you�limit�the�amounts�or�the�scale�
values�in�the�corresponding�condition�records.�
When�you�think�of�the�five�possible�elements�
necessary�for�the�account�determining�during�
posting�of�a�sales�invoice�–�where�from�does�the�
system�get�the�information?�
Chart�of�Accounts,�Sales�Organization,�Payer,�
Material�Master,�Account�Key.�
Name�the�necessary�steps�to�setup�a�route?�
Define�the�transportation�connection�points�which�
-----------------------�Page�142-----------------------
mark�the�beginning�and�end�of�a�leg�
Define�the�leg�by�specifying�the�transportation�
connection�points�at�the�beginning�and�end�
Define�the�modes�of�transport�and�shipping�types�
which�are�dependent�upon�the�mode�of�transport.�
Define�the�routes�by�listing�the�individual�legs�one�
after�another.�The�sequence�of�legs�constituting�the�
route�determines�the�itinerary.�When�you�string�
together�the�individual�legs�of�the�route,�you�must�
also�specify�the�shipping�type�for�each�leg.�
As�a�simple�alternative�you�can�also�define�routes�
without�specifying�them�more�precisely�by�defining�
legs.�Note�that�in�this�case�the�system�cannot�
propose�the�office�of�exit�for�export.�
During�route�determination�the�system�also�needs�to�
know�the�departure�Zone�of�the�goods�to�be�
shipped.�How�does�this�information�come�into�the�
sales�order?�
Customer�Master.�
What�is�the�scope�of�check�during�availability�check�
and�what�do�you�specify�with�it?�
Stocks�
Safety�stock,�stock�in�transfer,�stock�in�quality�
inspection,�blocked�stock.�
Inward�and�outward�movements�
purchase�orders,�purchase�requisitions,�planned�
orders,�production�orders,�reservations,�dependent�
reservations,�dependent�requirements,�sales�
requirements,�delivery�requirements.�
Where�do�you�assign�text�determination�procedures�
-----------------------�Page�143-----------------------
for�customer�master�records�and�for�documents?�
Account�Group,�Item�Category.�
Can�you�make�texts�mandatory�for�a�customer�
master�or�a�sales�document?�
Yes.�
Give�examples�for�standard�output�types�in�SD.�
Order�Confirmation,�Delivery�Note�,�Invoice.�
Can�you�specify�when�output�should�be�created?�If�
yes,�what�possibilities�do�you�have?�
Yes.�Print�out,�Mail,�EDI,�Fax.�
What�does�the�material�type�control�?�
The�material�type�determines�a�material's�
procurement�type.�It�also�controls�
-�screen�sequence�
-�field�selection�
-�number�assignment�type�in�material�master�
maintenance�
-�inventory�management�type�
•�account�determination�
Credits�
SAP�CERTIFICATION�IMPORTANT�MATERIAL�!!�
1�
Please�excuse�the�funny�words�infront�of�the�determinations�
like�ex:cat,�this�was�my�way�of�memorizing�for�the�certification�exam.�
Master�Data�
Master�Data�
Cat---Customer�Master�
-----------------------�Page�144-----------------------
Mouse---Material�Master�
Chase---Customer�M.�Info�Record�
Octopus---Output�Master�Data�
In---Incompletion�Log�
C---Customer�Master�in�Pricing�
Customer�Master�vary's�by�the�
Sales�Organization�/distribution�channel�/division�
Company�Code�
Customer�Master�groups�data�into�
General�Data�
General�data�is�relevant�to�Sales�and�Accounting.�General�data�is�valid�for�all�
sales�area.�
Marketing�and�Export�
Sales�Data�
Sales�Area�data�is�relevant�to�Sales,�Delivery�and�Billing.�Sales�Area�is�valid�
for�
Sales�Area.�
Shipping,�Billing,�and�Partners�
Company�Code�Data�
Company�data�is�relevant�to�Accounting.�Company�data�is�valid�for�company�
code�
Account�Management,�Payment�Transactions�
*If�you�have�3�sales�organizations,�2�divisions,�and�2�distribution�channels�and
�
you�want�to�use�
each�of�the�divisions�and�distribution�channels,�how�many�customer�records�do�
you�need�to�create�
for�each�customer?�1�
*If�you�have�3�sales�organizations,�2�divisions,�and�2�distribution�channels�and
�
you�want�to�use�
each�of�the�divisions�and�distribution�channels,�how�many�sales�area�views�need�
to�be�created�for�
a�customer?�12�
*�When�creating�a�customer�master�record�through�the�menu�path,�the�default�
value�in�the�account�
group�field�depends�on�the�Business�Partner�
Account�Group�Controls:�
Not---Number�Range�
If---Internal�or�External�number�Assignment�
I---Input�Screens�and�filed�for�partner�functions�
Fail---Field�Selection�
One---One�Time�Account/Customer�
-----------------------�Page�145-----------------------
Of---Output�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
2�
It---It�can�be�automatically�proposed�
Mandatory�in�customer�master�
Sold�to�Party---Pricing,�Incoterms,�and�Shipping�Conditions.�Payer---Terms�of�
Payment�and�Credit�Limit�Check.�
Ship�to�Party---Shipping�Address,�Goods�Receiving�Hours,�and�Tax.�Billing�
Address---Bill�to�Party.�
Partner�Types�
AP-Contact�Person�
KU-Customer�
LI-Vendor�
PE-Personnel�
Partner�Determination�Procedure�
Super---Customer�Master�Slam---Sales�Doc�Header�
Seven---Sales�Doc�Item�Basket---Billing�Header�
Ball---Billing�Item�
Dunk---Delivery�
Contest---Customer�Master�
Assigning�of�Partner�Procedures�
Partner�Object�Assignment�of�Partner�Procedures�
Customer�Master�>�Account�Group�Sales�Doc.�Header>Sales�Doc�Type�
Sales�Doc�Item>�Item�Cat�in�Sales�
Delivery>Delivery�Type�
Shipment>Shipment�Type�
Billing�Header>Billing�Type�
Billing�Item>Billing�Type�
Sales�Activities�(CAS)>Sales�Activity�Type�
Outline�Agreements�
Two�Types�of�Outline�Agreements.�1.�Scheduling�agreements�2.�Contracts�
Three�Types�of�Scheduling�Agreements.�1.�SA�Scheduling�agreement�2.�BL�
Scheduling�
Agreement�with�delivery.�3.�Del�Scheduling�Agreement�for�external�line�agent.�
*Scheduling�Agreements-�Between�you�and�customer�sold�to�party.�[Valid�for�a�
-----------------------�Page�146-----------------------
certain�period�of�
time,�Fixed�Delivery�Qty�and�dates,�and�Dates�are�contained�in�the�Schedule�
Lines.]�Difference�between�S.A.�and�sales�order�is�in�S.A.�you�work�on�the�
schedule�lines�and�is�made�manually.�
Two�Types�of�Contracts.�1.�Quantity�Contract�2.�Value�Contracts�
Quantity�Contract-�Is�between�you�and�customer.�[Valid�for�certain�period�of�
time,�No�schedule�
lines�in�contract,�No�delivery�date,�and�no�delivery�quantities.]�
Value�Contract-�Is�between�you�and�customer.�(Like�the�quantity�will�be�
reserved�and�as�you�
consumed�you�will�pay�on�the�same�price�in�contract.)�Schedule�lines�are�
created�in�the�release�order�when�it�is�placed.�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
3�
Two�Types�of�Value�Contract-�WK1=General�value�contract,�WK2=Material�
related�value�contract/Contains�exactly�1�material.�
[In�Contract�you�don't�know�when�you�have�to�delivery/release.�In�Scheduling�
Agreement�
you�do.]�
Material�Determination�
Tool�for�automatically�exchanging�materials�in�the�sales�document.�When�you�
process�a�
document�the�system�automatically�Searches�for�valid�master�records.�You�
don't�need�a�
master�record�for�the�material�number�that�you�are�replacing.�During�order�
entry�the�material�ordered�by�the�customer�is�replaced�by�the�substitute�defined
�
in�the�master�record.�
Two�Types�of�Material�Determination�
1.�Manual�Product�Selection-[The�system�does�not�automatically�replace�the�
product.�
Displays�a�list�of�all�the�substitution�materials.�There�is�1�reason�for�
substitution.�1.�For�
manual�product�selection=0005.]�
2.�Automatic�product�selection-[The�system�replaces�the�entered�material�
automatically.�
Reruns�material�determination.�Fill�the�quantity�of�the�order�with�the�first�
-----------------------�Page�147-----------------------
material;�if�not�enough�material�it�will�fill�the�remaining�quantity�with�the�ne
xt�
material.�Two�reasons�for�
substitution�0004,�0006.]�
*Material�Determination�is�assigned�in�condition�Technique.�
Material�Type�controls�
Views�
Default�Item�Category�Group�
Number�Ranges�
Determines�Material�Master�Views�
Material�Type�
Material�Master�varies�by�
Sales�Organization/Distribution�Channel�
Plant/Storage�Location�Division�is�at�the�Client�Level�
Material�Master�Tabs�
The�Basic�data�on�the�material�master�is�valid�for�all�organizational�units�and�
relevant�to�all�areas�
The�Sales:�S/org�data�on�the�material�master�is�valid�for�Sales�Organization�/�
Distribution�channel�and�relevant�to�Sales.�
The�Sales:�General/Plant�data�and�Foreign�Trade�data�on�the�material�master�is�
valid�for�
delivering�plant�and�relevant�to�Sales�
*Certain�fields�such�as�sales�units�can�have�multiple�sales�units�depending�on�
the�Sales�org�/�Distribution�channels.�
*Certain�fields�such�as�loading�group's�can�have�multiple�loading�groups�
depending�on�the�plant.�*A�company�sells�2�materials�out�of�10�plants.�You�
need�2�material�master�records.�
Material�Types�
VERP---Packaging�
HAWA---Trading�Goods�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
4�
FERT---Finished�Product�
LEIH---Returnable�packaging�
NLAG---Non�Stock�Item�
-----------------------�Page�148-----------------------
*You�want�to�create�a�material�for�an�externally�produced�material.�The�
material�is�kept�in�stock�
and�is�used�in�the�bill�of�materials.�It�is�not�sold�directly.�Which�material�ty
pe�do�
you�select?�ROH.�
*Which�of�the�following�data�is�proposed�for�the�sales�process�from�the�material
�
master?�
Weight�and�volume�
Delivering�plant�
Text�and�availability�
Pricing�
Customer�Material�Info�Record�
Cookies---Customer�Material�Come---Customer�Description�
Slow�---Search�Term�
Peanut�B.�---Plant�
Doesn't----Delivery�Priority�
Monkeys---Minimum�Delivery�Quantity�
Play---Partial�Delivery/item�
On---Over�Delivery�Tolerance�
Bed---Batch�Split�Allowed�
Money�---Maximum�Partial�Delivery�
In�---Item�Usage�
UBL---Unlimited�Tolerance�
Uvault---Under�Tolerance�
*What�is�maintained�in�the�customer�/�material�info�record?�
Information�that�is�specific�to�when�a�certain�customer�orders�a�certain�product
.�
Customer�material�number�and�description.�Texts.�
*You�can�set�specific�shipping�information�for�a�customer�/�material�such�as:�
Partial�Delivery�
Indicators,�Default�Delivery�Plant,�and�Delivery�Priority�and�delivery�tolerance
s�
Output�Types�
Pizza---Partner�Functions�
Tacos---Transmission�Medium�
Tortilla---Time�
Lasagna---Language�
Output�Type�Controls�
Timing�
Output�Perimeters�
Medium�
Layout�Set�
-----------------------�Page�149-----------------------
*Output�determination�takes�place�using�the�condition�technique.�
*In�the�output�master�data�you�define�the�Medium,�Time�and�Partner�function�
per�output�type.�
*Output�types�can�be�set�up�for�Inquiries,�Quotations,�Sale�Order�documents,�
Delivery�and�billing�documents.�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
5�
*Transmission�data�include�EDI,�Printers,�Mail�and�Fax.�
Determining�incompletion�log�Sales�Doc�Type�(Sales�Header)�
Item�Category�(Item)�
Schedule�Line�Category�(Schedule�Line)�
Partner�Function�(Partner�Function)�
Delivery�Type�(Delivery�Header)�
Delivery�Item�Category�(Delivery�Item�Level)�
*The�system�determines�which�fields�will�be�displayed�in�the�incompletion�log.�
These�fields�can�
be�changed�in�customizing�to�suit�a�customer's�unique�requirements�
*The�incompleteness�log�function�is�available�in�the�Sales�order,�Delivery�and�
the�Billing�document.�
Assign�Incompleteness�Procedures�To�
Daniel---Delivery�Types�
So---Sales�Document�Types�Dumb---Delivery�Item�Types�
Person---Partner�Functions�
Sitting---Schedule�Line�Categories�
In---Item�Categories�
Store---Sales�Activities�
Condition�Master�
Please---Prices�
Subscribe---Surcharge�&�Deals�
For---Freight�The---Taxes�
Diary---Discounts�
*You�can�maintain�values�in�condition�records�according�to�a�scale�and�there�is�
no�limit�to�the�number�of�scale�levels.�
*You�can�restrict�a�price�agreement�by�using�validity�periods.�
*You�can�have�a�percentage,�Quantity�dependent�or�Amount�dependent�
discount�or�surcharge,�depending�on�the�condition�type.�
-----------------------�Page�150-----------------------
SALES�
Sales�Order�Types�Standard�Order�OR�
Contract�
Cash�Sales�BV�Rush�Order�SO�
Free�Of�Charge�Delivery�FD�
Returns�RE�
Consignment�Fill�Up�KB�Consignment�Pickup�KA�Consignment�Issue�KE�
Credit/Debit�Request�CR/DR�
Sales�Order�Document�Type�Control�
D---Default�Functions�Date,�Delivery�Type,�Billing�Type,�Blocks�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
6�
E---Enhancement�for�Contracts�
A---Allowed�Item�Categories�
D---Determining�Materials�M---Mandatory�Reference�
O---Output�Types�Available�P---Partner�Determinations�
F---Free�Date�
I---Incompleteness�
N---Number�Assignment�
P---Pricing�
C---Checks�Division,�open�quotes/contracts/Info�Record�
*In�Sales�Document�Type�you�can�block�the�delivery�and�billing.�
Sales�Order�Processing�
Within�a�document�you�can�fast�change�the�Delivery�date,�delivery�block,�
delivery�priority,�billing�block,�reason�of�rejection,�and�plant.�
In�more�than�1�document�you�can�mass�change�the�Plant,�material,�pricing,�and�
currency.�
In�sales�order�you�can�block�the�delivery�at�header�and�schedule�line.�In�sales�
order�you�can�block�the�billing�at�header�and�Item�line.�
During�Sales�Order�Processing,�it's�Basic�Functions�
C---Calculating�pricing�&�Taxes�
C---Checking�Credit�limits�
A---Availability�check�
-----------------------�Page�151-----------------------
T---Transferring�requirements�to�materials�planning�(MRP)�
D---Delivery�Scheduling�
O---Outputs�
T---Text�
S---Sales�Information�Systems�
*When�you�click�the�Delivery�Block�in�the�order�you�can�BLOCK:�
Order,�Confirmation,�Print�Out,�Delivery�Pull�List,�Picking,�and�PGI.�
Determine�pricing�procedure�
Soda---Sales�Area�
So---Sales�Document�Type�
Cold---Customer�Master�
Pricing�Types�in�Sales�Order�
A---Copied�from�REF�updated�with�scale�
B---Perform�New�Pricing�
C---Manual�elements�copied�others�are�redetermined�
G---Only�tax�redetermined�
H---Only�freight�redetermined�
Determination�of�Sales�Item�Category�Auto.�Examples�of�Item�Categories�
Sales�Document�Type�AFN-Standard�Item�in�Inquiry�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
7�
Item�Category�Group�(M.M)�AGTX-Text�Item�in�Quotation�
Item�Usage�KMN-Standard�Item�in�Quantity�Contract�
High�Level�Item�(BOM)�TANN,�BVNN,�KEN,�REN,�TAN,�KLN�
Basically�from�order�type�n�Material�
Sales�Order�Item�Category�Controls�
P---Pricing�Relevancy�carried�or�not�
B---Billing�Relevancy�Carried�out�or�not�
O---Output�
M---Message�if�item�cannot�fully�delivered�
B---BOMS�
C---Completion�Rule�
I---Is�difference�allowed�from�header�levels�
T---Text�Determination�
I---Incompleteness�B---Billing�Block�
I---Item�level�Partner�Determination�
-----------------------�Page�152-----------------------
D---Delivery�Relevancy�material�or�text�item�
S---Schedule�lines�allowed�
*In�Item�Category�you�can�block�the�Delivery�and�Billing.�
Copy�Control�Procedure�
Data�Transfer�Routines---Control�how�fields�are�copied�from�the�preceding�
document.�Copying�Requirements---Like�incompletion�Log�if�copy�from�
reference�is�not�100%.�
Switches---Set�specific�controls�for�each�transaction.�Ex:�Activate�or�deactivat
e�
transfer�of�item�numbers�from�pre-�docs.�
Sources�of�Information�(Document�Data)�
Maria---Master�Data�
Enters---Existing�Document�Data�
Church---Customizing�
Hourly---Hard-coded�controls�
Information�Structure�is�composed�of:�
Chicago---Characteristics�
Times---Time�Units�
Key�Figures�
Determine�Availability�Check�at�
Schedule�Line�Category�
Material�Master�
Availability�Checking�for�
Sales�Order�
Material�Availability�Date�
Plant�
Controls�
Determination�of�Schedule�Line�Category�Auto.�
Item�Category�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
8�
MRP�Type�
Schedule�Line�Category�has�an�effect�on�
Ant---Availability�Check�
-----------------------�Page�153-----------------------
Goes---Goods�Movement�Type�for�GI�
Down---Delivery�Relevance�
Town---They�are�assigned�to�Item�Categories�
Round---Requirements�Transfer�to�MRP�
Park---Purchasing�(PR�auto�created)�
Controlling�Schedule�lines�in�Sales�Documents�
Quotation�Schedule�Line---�Not�Relevant�for�delivery,�No�Req.�Transfer�BN,�No�
Movement�Type�
Requirements�planning�in�order---Relevant�for�delivery,�Requirements�Transfer�
CP,�Movement�
Type�601�
Returns�Schedule�Line---Relevant�for�delivery,�No�Requirements�Transfer�DN,�
Movement�Type�
651(Block�Stock�Return)�
Cash�Sale�(BV)�
Pull---Payment�made�at�the�time�of�the�order�(invoice�printed)�
Out---Order�&�delivery�created�at�the�same�time�
Gun---GI�posted�at�a�later�date�to�avoid�delays�
Unit---Uses�billing�doc�type�CS�sends�the�invoice�to�the�printer�using�RD03�
Nine---No�output�determination�
Nine---No�price�determination�
Four---FI�posting�made�to�cash�settlement�
Rush�Orders�(SO)�When�saved�creates�Delivery�Type�LF�Auto.�
Consignment�Processing�
CF-Consignment�Fill�up-�Stay�in�valuated�stocks�of�delivering�plant.�[Order,�
Delivery,�Picking,�
PGI]�
CI-Consignment�Issue-�When�goods�are�issued�both�customers�stock�n�stock�in�
delivering�Plant�
are�reduced.�[Order,�Delivery,�PGI,�Billing�Doc]�
CP-Consignment�Pick�up-�Return�goods�to�you�so�you�credit�them.�[Order,�
Inbound�Delivery,�
Goods�Receipt].�No�billing�
CR-Consignment�Return-�The�goods�issue�puts�stock�back�in�customers'�special�
stock�and�issue�a�credit�memo.�[Order,�Inbound�Delivery,�Goods�Receipt,�Billing�
Doc].�
Determine�Free�Goods�TANN�
Sun---Sales�Area�
Desert---Document�Pricing�Procedure�
Cold---Customer�Pricing�Procedure�
Frost---Free�Goods�Procedure�
-----------------------�Page�154-----------------------
Inclusive�Bonus�Quantity-�Free�goods�that�involve�the�same�material.�Quantity�
units�must�be�the�same.�
Exclusive�Bonus�Quantity-�Are�extra�goods�delivered�free�of�charge.�Not�
displayed�on�invoice.�
3�calculation�rules�
1.�Prorated�
2.�Unit�Related�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
9�
3.�Whole�Unit�
Determination�of�Tax�Rate�in�a�document�
Business�transaction-�domestic�or�export/import�
Tax�Liability�
Tax�Liability�of�the�material�
What�controls�Delivery�item�scheduling?�
Transit�Time�
Pick/Pack�Time�
Loading�Time�
Transportation�Lead�Time�
Determination�of�Delivering�Plant�Customer�Material�Info�Record.�
Customer�Master�from-�ship�to�party�
Material�Master�
How�do�we�handle�customer�complaints?�
Returns�request�
Credit/Debit�memo�request�
Invoice�correction�
Invoice�Cancellation�
Delivery�
Delivery�Types�
EL---Inbound�Delivery�
LB---Delivery�for�subcontract�order�
LD---Decentralized�Shipping�
LF---Outbound�Delivery�
-----------------------�Page�155-----------------------
LO---Delivery�without�Reference�
LP---Delivery�from�Project�
LR---Returns�Delivery�
NL---Replenishment�Delivery�
The�Delivery�Type�Controls�W---Which�Screens�to�Present�
O---Output�
R---Route�Re-Determination�
D---Delivery�Split�by�Warehouse�Number�
Puerto---Picking�Determination�Rule?�
Rico---Relevant�for�Shipment�or�Transportation�Processing�
Puerto---Partner�
Rico---Reference�to�Order�
Too---Text�
Night---Number�Assignment�
Outbound�Delivery�Functions�
M---Material�Substitution�
C---Credit�&�Risk�Management�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
Donald---Delivery�Split�by�Warehouse�Number�
Eats---Export�Control�
Tacos---Text�
Gorditas---Group�of�Outbound�Deliveries�
Cookies---Controllable�Error�Messages�
Donuts---Dangerous�Goods�Check�Quarter�Pounder---Quantity�Checks�
Determination�of�Delivery�Item�Category�Auto�(When�not�copied�from�sales�
doc.)�
Delivery�Type�
Item�Category�Group�(m.m.)�
Item�Usage�(additional�Usages)�
The�Delivery�Item�Category�Controls�
P---Picking�Relevancy�A---Availability�Check�
C---Check�for�OverDelivery�
P---Packing�Control�
C---Check�Minimum�Delivery�Quantity�
P---Picking�Location�Determination�
-----------------------�Page�156-----------------------
A---Auto�Batch�Determination�
R---Relevant�for�Proof�of�Delivery�
T---Text�
What�Determines�the�Delivery�Schedule?�
Oh---Order�Date�
My---Material�Availability�Date�(Sufficient�Goods�Available)�
Lord---Loading�Date�(picking/packing�completion�date)�
Great---Goods�Issue�Date�(From�Delivery�Plant)�
Directions---Delivery�Date�(Arrival�Date�at�Customer)�
Determination�of�Route�
Ducks---Departure�Zone�from�customizing�for�shipping�point�
Swimming---Shipping�Conditions�from�Sold�To�Party�Customer�Master�
Thru---Transportation�Group�from�Material�Master�
Toronto---Transportation�Zone�from�Ship-To�Party�Customer�Master�
Route�Schedule�contains�
A�Route�
A�Weekday�as�departure�date�along�with�a�depart�time�
A�list�of�ship-to-parties�An�Itinerary�(optional)�
What�we�find�or�see�in�a�route?�
Transit�Time,�
Transportation�Planning�Time,�and�Forwarding�Agent�
Picking�Location�determined�by�(MALA�rule)�
Shipping�Point�
Plant�
Storage�Condition�from�MM.�
10�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
Copy�Control�in�Delivery�Specifies�
Which�Sales�Doc�Types�are�to�be�copied�into�deliveries�
Which�Item�Categories�are�copied�into�deliveries�
What�conditions�data�is�copied�into�deliveries�Rules�for�combining�orders�into�
one�delivery�
Which�Data�is�to�be�transferred�
-----------------------�Page�157-----------------------
Whether�the�referenced�doc�in�recorded�in�the�document�flow�
Shipment�Type�Controls�No---Number�Assignment�
To---Texts�
Ocean---Output�
Sea---Shipping�type�(Truck,�Train,�Etc)�
Lion---Leg�Determination�
Cause---Copying�Rule�
Lion---Leg�Indicator�
Probably---Planning�Profile�
Seen---Split�Profile�
Corps---Completion�Type�
Shipping�Processing�Functions�
Making---Monitoring�of�Deadlines�
Chips---Creation�&�Processing�of�outbound�deliveries�
Making---Monitoring�of�goods�availability�
Money---Monitoring�of�capacity�situation�in�warehouse�
Stacking---Support�for�picking�Paper---Packing�of�the�Delivery�
Putting---Printing�&�Distribution�of�Shipping�Documents�
Pocket---Processing�goods�issue�
Shipping�Document�Functions�
Cargo---Combining�inbound�deliveries�to�form�inbound�shipments�
Passing---Partner�Information�
Atlantic---Assigning�Service�Agents,�Modes�of�Transport,�Shipment�Types�
Ocean---Output�
Down---Deadlines�
Too---Texts�
Shiny---Shipping�Stages�South---Shipping�Units�
Carolina---Combining�outbound�deliveries�to�form�outbound�shipments�
Determination�of�Shipping�Point�Auto.�(Normally�determined�in�sales�doc)�
Shipping�condition�field�from�sales�doc�type�or�sold�to�party�C.M.�(shipping�
requirements)�
Loading�Group�from�M.M�(loading�Equipment)�(Sales/Plant�Data�screen)�
Delivering�Plant�from�CM,�or�MM�
What�do�we�find�in�a�shipping�point?�
Loading�Lead�Time�Pick/Pack�Lead�time�
11�
-----------------------�Page�158-----------------------
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
12�
Post�Good�Issue�
Updates�the�quantities�in�inventory�management�and�delivery�requirements�in�
material�planning.�
Updates�the�value�change�in�the�balance�sheet�accounts�for�inventory�
accounting�(cost�of�
Material)�
Generates�additional�documents�for�accounting.�Generates�the�billing�due�list.�
Updates�the�status�in�all�relevant�sales�docs.�
Warehouse�consist�of�the�following�organizational�units�
Warehouse�Number�
Storage�Type�
Picking�&�Staging�Area�
Movement�Type�Controls�
Change�in�stock�quantity�
Change�in�stock�type�or�material�number�
Goods�Issue�
Goods�Receipt�
Transfer�order�includes�the�following�info.�
Material�Number�
Quantity�to�be�moved�
Source�&�Destination�bins�
Billing�
Billing�Types�
F2---Invoice�
F8---Pro-Forma�Invoice�
G2---Credit�Memo�L2---Debit�Memo�
RE---Returns�
S1---Cancellation�Invoice�
S2---Cancellation�Credit�Memo�
LR---Invoice�List�
LG---Credit�Memo�List�
IV---Intercompany�billing�(invoice)�&Delivery�
IG---Intercompany�billing�(credit�Memo)�
BV---Cash�Sale�
-----------------------�Page�159-----------------------
Billing�Type�Controls�
No---Number�Assignment�
Pay---Partner�Functions�
Till---Texts�
Received---Rebates�Overtime---Outputs�
Properly---Posting�Block�
In---Invoice�List�Type�
Company---Cancellation�Billing�Type�
At---Account�Determination�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
Seven---Special�features�of�the�FI�interface�
Billing�Document�
Contains�item�line�and�header�no�schedule�lines�
Header�contains�info�of�Billing�date,�customer�number�of�payer,�Net�value�of�
entire�doc.�
Item�line�contains�info�on�Material�and�Billing�quantity�
System�shows�delivery�number�and�sales�order�number�at�item�line�
Order�Item�Category�determines�if�it�is�delivery�related�or�order�related�billin
g.�
Pricing�Types�in�billing�document�determined�by�
Billing�Type�
Item�Category�
Pricing�Types�in�Billing�Doc�
A-Copied�from�REF�updated�with�scale�
B-Pricing�redetermined�
C-Manual�elements�copied�others�are�redetermined�
D-All�Copied�with�no�changes�
G-Only�tax�redetermined�
H-Only�freight�redetermined�
Determination�of�Credit�Control�Area�User�Exit�(only�header�data�considered)�
Sales�Area�segment�from�payer�master�record�
Sales�Area�
Company�Code�
Credit�Check�can�be�carried�out�at:�
Sales�Order�(blocked)�
-----------------------�Page�160-----------------------
Outbound�Delivery�(blocked)�Goods�Issue�(error�Message)�
Data�flow�from�reference�docs�controlled�by�
Billing�Types�
Copying�Control�
Data�Transfer�Routines�
Business�Area�
Blue---By�Plant/Item�Division�
Berry---By�Sales�Area�
Boy---By�Sales�Organization.�Distribution�Channel,�Item�Division�
Revenue�Account�Determination�use�to�find�the�General�Ledger�Account�
Chart�of�Accounts,�Sales�Organizations,�Account�Assignment�group�of�the�payer,�
Account�
assignment�group�for�materials,�Account�Key�(assigned�to�condition�types)�
*These�things�can�be�changed�before�an�accounting�document�is�created.�
1.�Billing�Date�2.Billing�Value�3.Account�Determination�4.Output�Determination�
13�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
14�
*Reference�field�is�in�the�accounting�document�header.�Allocation�number�is�in�
the�customer�line�item�and�is�used�for�sorting.�
*The�Goods�receipt�number�and�Goods�Issue�number�cannot�be�used�as�a�
reference�or�allocation�number�for�the�accounting�document�type.�
Billing�Date�
Billing�Date�can�be�changed�in�the�billing�document.�
You�maintain�the�calendar�if�billing�is�to�be�done�on�specified�days�in�the�
customer�master.�It's�proposed�auto.�But�can�be�overridden.�
If�using�delivery-related�billing�the�billing�date�is�based�on�goods�issue.�If�u
sing�
order-related�billing�the�billing�date�is�based�from�the�order.�
Periodic�Billing�is�often�used�for�rental�&�service�contracts�for�agreements�in�
order�to�bill�the�amount�periodically�at�certain�dates.�
-----------------------�Page�161-----------------------
Milestone�Billing�is�often�used�in�plant�engineering�&�construction�in�order�to�
spread�billing�of�the�full�amount�over�several�dates�within�the�billing�plan.�
Milestone�can�be�blocked�for�billing.�When�created�updates�the�status�of�the�
billing�plan�dates.�In�
sap�milestone�is�stored�in�a�network�along�with�planned�and�actual�project�data.
�
M.�are�assigned�to�the�billing�plan�dates�&�blocked�for�billing�until�the�milest
one�
is�confirmed�as�completed.�
In�Milestone�billing�you�can�control�whether�a�billing�date�is�a�*fixed�date�
*required�to�be�
updated�with�the�actual�date�of�the�m.�*Update�with�the�actual�date�of�the�
milestone,�if�production�is�completed�before�the�planned�billing�date.�
Determining�the�billing�value�needs�a�billing�rule,�in�order�to�determine�the�
value�to�be�billed�on�
a�particular�date�or�not.�Ex:�Net�Value�X�(%)�of�billing�plan�=�Billing�value�
Determining�billing�plan�type�
Document�item�category�
Relevance�for�billing�(relevant�for�order-related�billing-billing�plan)�
Date�categories�defined�have�a�control�function�at�billing�date�level.�(They�
determine�which�
billing�rule�is�used�to�settle�the�date,�whether�the�billing�date�is�a�fixed�dat
e�and�
whether�a�billing�block�is�set�for�this�date.)�Date�rules�are�needed�in�the�bill
ing�
plan�in�order�to�define�the�start�date�&�end�date.�
To�differentiate�between�milestone�and�periodic�billing�you�use�billing�plan�
type.�
Down�Payments�Request�are�usually�arranged�with�plant�engineering,�
construction,�and�capital�good�customers.�
*Down�Payment�Agreements�in�the�sales�order�
When�processing�down�payments�the�billing�plan�functionality�is�utilized.�
Control�is�carried�out�via�the�billing�rule:�
Billing�rule�4:�Down�P.�for�percentage�milestone�billing.�Billing�rule�5:�Down�P
.�
for�percentage�milestone�billing.�
Down�payment�agreement�can�be�assigned�to�an�item�or�for�all�the�items�in�the�
orders.�
Special�Condition�Type�AZWR�is�used�for�down�payment�items�in�sales�doc.�
Condition�Category�E�&�Calculation�rule�B�(fixed�amount)�are�assigned�to�
condition�type�AZWR.�When�AZWR�is�determined�all�other�condition�types�are�
set�to�inactive.�
-----------------------�Page�162-----------------------
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
15�
As�soon�as�the�billing�date�(in�the�billing�plan)�for�the�down�p.�has�been�
reached,�the�
system�creates�a�sown�payment�invoice�&�sends�to�the�customer.�Billing�Type�
FAZ�used�
for�down�payment�request.�This�request�can�be�created�auto.�Via�billing�due�list
�
processing�in�a�collective�run�or�explicitly�by�specifying�the�order�#�via�the�
transaction�create�billing�doc.�
Installment�Plans�only�1�billing�document�is�created�for�all�of�the�installment�
payments.�You�have�to�define�installment�payment�terms�in�customizing.�And�
when�you�define�the�
payment�terms�you�must�specify�the�number�&�amount�of�the�installment�in�
percentage�&�payment�term�for�each�installment�payment.�
*Sales�Account�Determination�is�carried�out�using�the�condition�technique�
depending�on�the�billing�type.�
Pricing�
Pricing�Procedure�can�contain�any�number�of�subtotals�between�gross�&�net�
price.�
You�can�mark�a�condition�type�in�the�pricing�procedure�as�being:�
Mandatory�condition�
Manually�entered�condition�For�statistical�purposes�only�
Pricing�Procedure�is�determined�by:�
Sales�Area�Sales�Area�
Customer�pricing�procedure�field�in�the�customer�master.�SD�Document�
Sales�Doc�Type,�Document�pricing�procedure�field�Sold�to�party�
*The�system�reads�the�condition�type�of�the�first�step.�It�determines�the�
assigned�access�sequence�
for�the�condition�type.�The�system�then�reads�the�access�sequence.�The�
sequence�of�condition�tables�represents�the�search�strategy�for�finding�the�
relevant�condition�record.�Each�condition�
table�represents�one�access�which�can�be�made�for�a�condition�record�with�the�
specified�key.�The�
system�searches�for�valid�condition�records�with�the�key�specified�key.�The�
system�searches�for�
-----------------------�Page�163-----------------------
valid�condition�records�with�the�key�specified�by�the�condition�table�(Accesses)
.�
If�the�first�access�does�not�find�a�valid�condition�record,�then�the�system�
searches�for�the�next�access�using�the�next�
condition�table.�Once�the�system�finds�a�valid�condition�record�and�copies�the�
value�that�
corresponds�to�the�scale�into�the�sales�order�doc.�The�whole�process�is�repeated
�
for�each�condition�type�until�the�system�has�finished�the�entire�pricing�
procedure.�
Group�Condition�
In�customizing�you�can�set�a�condition�type�to�be�a�group�condition.�For�group�
conditions�with�
varying�keys,�item�quantities�are�accumulated�for�scale�point�determination�
purposes�but�the�rate�for�each�item�is�taken�from�its�individual�condition�recor
d.�
Ex:�discount�if�u�purchase�10-20lb�of�ice�cream�5%�discount,�30-40lb�10%�
discount.�
Control�data:�Entry�for�condition�type�
Group�condition:�X�
Unit�of�measure�for�accumulation,�e.g.�pieces�
GrKey�Number:�1,�2,�or�3�(see�explanation�below)�
1.�Complete�document:�
All�quantities�with�the�same�condition�type�are�accumulated.�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
2.�For�all�condition�types:�
All�quantities�are�accumulated�which�belong�to�condition�type�routine�2.�
3.�Material�pricing�group:�
All�quantities�with�the�same�condition�type�and�material�pricing�group�are�
accumulated�
Condition�Exclusion�Indicator�
In�pricing�Procedure�there�can�be�requirements�on�the�conditions.�This�
requirement�can�look�at�the�condition�exclusion�indicator�&�ignore�the�condition
�
if�set.�Condition�types�to�be�compared�are�first�placed�in�an�exclusion�group.�
16�
*During�pricing�the�conditions�which�result�in�the�best�price�(lowest�charge�or�
highest�discount)�
are�selected�from�this�group.�All�others�are�deactivated.�(19-8)�
There�are�several�comparison�methods�which�may�be�used:�
-----------------------�Page�164-----------------------
A�All�conditions�found�within�the�first�exclusion�group�are�compared�and�the�
condition�with�
the�best�price�is�chosen.�All�others�are�deactivated.�
B�All�condition�records�found�for�one�condition�are�compared.�The�best�price�is�
chosen.�All�
others�are�deactivated.�This�method�can�be�used�with�condition�type�PR00,�for�
example.�
C�The�total�of�condition�records�found�in�the�first�exclusion�group�is�compared�
to�
the�total�
of�condition�records�found�in�the�second�exclusion�group.�The�group�resulting�in
�
the�best�price�is�chosen.�The�conditions�of�the�other�group�are�deactivated.�
D�If�a�condition�record�is�determined�for�the�condition�types�of�the�first�
exclusion�group,�all�
condition�records�for�the�second�exclusion�group�are�deactivated.�
E�As�for�method�B,�except�the�worst�(highest�charge�or�lowest�discount)�price�is
�
chosen.�
F�As�for�method�C,�except�the�group�with�the�worst�overall�price�is�chosen.�The�
conditions�
of�the�other�group�are�deactivated.�
*The�condition�exclusion�indicator�can�be�set�in�either�the�condition�type�or�th
e�
condition�record.�
Condition�Supplements�
*Group�several�conditions�together�in�a�condition�supplement�procedure�if�you�
want�these�
conditions�to�be�accessed�together�during�pricing.�
Hierarchy�Access�1�
Hierarchy�accesses�optimize�pricing�for�hierarchy�data�structures,�such�as�the�
product�hierarchy.�
Hierarchy�Access�2�
To�define�the�condition�table�key�for�hierarchies�like�this,�you�might�have�to�
include�partial�
quantities�for�a�pre-defined�quantity�of�characteristics.�
Without�hierarchy�accesses,�you�would�need�to�create�a�condition�table�for�each�
combination�
and�assign�all�the�accesses�to�these�tables�in�an�access�sequence.�
This�requires�a�lot�of�maintenance�and�will�reduce�system�performance.�The�
sequence�of�the�
accesses�will�also�be�fixed.�
This�is�particularly�disadvantageous�for�hierarchy�data�such�as�product�or�
customer�hierarchies.�
Hierarchy�Access�3�
-----------------------�Page�165-----------------------
The�functions�in�hierarchy�accesses�enable�you�to�solve�these�problems�by�using�
a�single�
access�to�a�condition�table.�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
17�
In�condition�record�maintenance,�when�you�create�the�access�sequence�for�
using�this�condition�
table�at�field�level,�you�have�to�define�whether�each�field�is�a�fixed�component
�
of�the�key�or�whether�it�is�an�optional�field.�
Priorities�are�assigned�to�the�optional�fields.�
During�pricing,�the�system�sorts�the�records�found�with�this�access�according�to
�
priority�and�
displays�the�record�with�the�highest�priority.�
Hierarchy�accesses�also�provide�clearer�and�easier�master�data�maintenance�
because�the�
different�condition�records�for�a�condition�type�are�created�together�in�the�qui
ck�
entry�screen�for�maintaining�conditions.�
Data�determination�in�Access�
*For�pricing�you�can�determine�&�use�data�that�isn't�contained�in�the�document.�
These�can�be�
performed�in�2�steps:�1.�Data�Determination�2.�Data�Use�
The�two�steps�for�determining�and�using�the�data�differ�in�the�way�that�they�
collect�data,�which�
means�that�a�distinction�must�be�made�between�three�data�determination�
procedures:�
Data�determination�using�the�communication�structure�KOMPAZD�
Data�determination�using�routines�(condition�202,�base�value�calculation�
formula�202)�
Data�determination�for�sales�deals�(condition�class�H)�
Data�determination�in�Access-Price�Book�
The�term�price�book�refers�to�a�price�determination�strategy.�
Pricing�procedure�RVAA02�was�delivered�in�the�SAP�standard�system�as�an�
example�of�this�
The�aim�here�is�to�set�certain�prices�for�a�group�of�customers.�
Special�agreements�are�also�to�be�set�for�these�prices,�depending�on�the�
material.�
This�can�be�achieved�using�two-step�data�determination:�
Step�1:�A�sales�deal�number�(condition�type�PBU)�is�determined,�depending�on�
-----------------------�Page�166-----------------------
the�customer�
group,�for�example.�
Step�2:�Using�the�material�group�as�a�basis,�for�example,�special�agreements�
are�determined,�
which�take:�
Pricing�date�
Scale�quantity�Item�price�list�
Into�account�(condition�type�PBUD).�
In�the�following�condition�type�PBBS,�the�special�agreements�determined�are�
used�and�base�
prices�therefore�read.�
On�the�basis�of�these�prices,�the�gross�price�is�calculated�in�the�following�
condition�type�
PBUP�using�the�percentage�value�from�condition�type�PBUD.�
You�can�configure�the�pricing�behavior�in�the�pricing�type.�
Controlling�the�New�Pricing�
Update�prices�on�condition�screens�is�available�at�header�&�Item�level.�
To�use�the�new�pricing�document�function�for�sales�or�billing�document�Edit�New�
Pricing�
Document,�assign�a�new�pricing�type�to�the�pricing�procedure.�If�you�do�not�use�
the�entry�it�will�use�(B)�carry�out�new�pricing.*these�functions�are�supported�f
or�
billing�&�Sales�Order.�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
Pricing�type�
A)�Copy�pricing�elements�and�update�scales�
B)�Carry�out�new�pricing�
C)�Copy�manual�pricing�elements�
G)�Redetermine�taxes�
H)�Redetermine�freight�conditions�
X,Y)�Reserved�for�Customer�1-9)�Reserved�for�Customer�
18�
-----------------------�Page�167-----------------------
*Condition�record�are�always�created�using�a�specific�key.*Use�tables�for�help�i
n�
defining�the�
structure�of�condition�record�keys.*The�key�fields�of�a�condition�table�must�
appear�at�the�start�of�the�table,�in�other�words,�non-key�fields�must�not�appear
�
between�any�two�key�fields.*An�Access�sequence�is�composed�of�one�or�more�
condition�tables.�
Creating�Access�Sequence�(Search�Strategy)�
You�can�define�prices,�discounts,�and�surcharges�at�various�levels.�Each�field�i
s�
defined�by�a�
combination�of�fields�or�by�a�field�in�a�condition�table.�Access�Sequence�is�
assigned�to�condition�type.�
*Access�Sequence�is�defined�for�each�n�every�condition�type�except�for�header�
&�Mandatory�Condition�Types.�
*A.S.�is�the�way�the�sap�system�reads�the�condition�records�for�the�condition�
type.�
*In�each�A.S.�you�have�condition�tables.�Condition�Table�is�combination�of�field
s�
which�make�the�
key�for�a�condition�record.�(Each�table�represents�one�access�which�can�be�
made�for�a�condition�
record�with�a�specific�key�
Condition�Types�
*Header�condition�HM00�allows�you�to�enter�the�order�value�manually,�and�this�
price�will�be�distributed�proportionally�across�the�items�based�on�previous�net�
value.�
*�Item�Condition�PN00�allows�you�to�enter�a�net�price�per�Item.�This�will�
deactivate�any�other�pricing�for�that�item.�
*Rounding�can�be�down�up�or�down�depending�on�the�setting.�Condition�DIFF�is�
group�condition�and�is�distributed�across�all�items�according�to�value.�
*Condition�VPRS�is�used�for�cost�of�sales�in�the�pricing�procedure.�*Condition�
MWST�is�used�for�tax.�
Special�Condition�Types�
*HM00�and�PN00�are�also�included.�
*Condition�AMIW�allows�you�to�create�a�minimum�value�for�each�order.�(If�the�
value�in�the�order�
header�falls�short�of�this�minimum�order�value�in�pricing,�the�system�will�take�
this�price�and�replace�the�net�order�value�automatically).�
*Condition�AMIZ�Has�calculation�formula�13�assigned�to�it�in�the�pricing�
procedure.�This�
calculates�the�minimum�value�surcharge�by�subtracting�the�net�item�value�from�
the�minimum�order�value�AMIW.�
*Condition�PR02�(Internal�Price)�allows�you�to�maintain�condition�records�with�
interval�scales�if�
the�condition�type�is�set�to�scale�type�D�in�customizing.�Interval�scales�can't�
be�
-----------------------�Page�168-----------------------
used�for�group�conditions.�
*Condition�KP00�(Pallet�Discount)�grants�the�customer�discount�for�whole�units�
of�measure�only.�Ex:�Controlled�by�basic�formula�22�in�p.p.�which�takes�
complete�whole�pallet�into�account.�
*Condition�KP01�(incomplete�pallet�surcharge)�if�customer�has�incomplete�pallet�
they�have�to�pay.�Ex:�order�70�but�50=1�pallet.�Condition�record�$50�per�pallet.
�
Use�formula�24�in�p.p.�
*Condition�KP02�(Mixed�Pallet�Discount)�Adds�the�quantities�of�the�individual�
items,�and�then�
calculates�the�discount�for�complete�pallets�only.�This�is�controlled�by�conditi
on�
type�KP02�(group�condition�=�X,�unit�of�measure�=�PAL)�and�the�corresponding�
condition�record.�
*Condition�KP03�(Surcharge�for�incomplete�mixed�pallets)�adds�the�quantities�of�
the�individual�
items.�It�then�calculates�the�surcharge�on�any�fractional�portion�of�the�total�
quantity.�This�is�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
19�
controlled�by�condition�type�KP03�(group�condition�=�X,�unit�of�measure�=�PAL�
and�scale�formula�23,�which�calculates�the�fractional�proportion�of�the�total�
quantity).�
*Rounding�DIFF�You�can�maintain�a�rounding�unit�in�Table�T001R�for�each�
company�code�and�currency.�If�the�final�amount�in�the�order�header�differs�from�
the�rounding�unit,�the�system�will�round�the�amount�up�or�down�as�specified.�
Condition�DIFF�determines�the�difference�amount.�
Condition�type�DIFF�is�a�group�condition�and�is�distributed�among�the�different�
items�according�to�value.�
Statistical�Condition�Types�
When�processing�a�pricing�procedure,�it�is�often�necessary�to�determine�and�
make�values�in�the�
procedure�available�for�various�purposes.�These�however,�do�not�change�the�net�
value�of�the�item.�This�can�be�done�by�marking�a�condition�type�as�"statistical"
.�
*Cost�(VPRS)�is�used�to�retrieve�standard�cost�of�the�material.�This�is�used�for
�
information�value�
purposes�only�by�the�pricing�procedure.�In�the�condition�category�G,�of�VPRS,�
accesses�the�
valuation�segment�of�the�material�master�locating�either�the�standard�cost�of�
the�moving�average�
cost.�Condition�category�S�Always�accesses�the�moving�Average�Cost.�Condition�
category�T�Always�accesses�the�moving�average�cost.�
-----------------------�Page�169-----------------------
*Cash�Discount�(SKTO)�is�used�to�retrieve�the�cash�discount�rate.�Used�for�info.
�
Purposes�only.�
*Customer�Expected�Prices�(EDI1�&�EDI2)�can�be�entered�manually�in�the�order�
or�retrieved�
from�the�incoming�IDOC�in�an�EDI�environment.�EDI1�is�used�to�compare�the�
net�price�for�each�item.�EDI2�is�used�to�compare�the�overall�item�value�(net�
price�x�quantity).�
Condition�Types�are�combined�in�required�sequence�in�pricing�procedure�
1.�Price�
2.�Material�Discount�
Customer�Hierarchy�
Can�be�used�during�sales�order�&�Billing�for�determining�pricing.�Customer�
Hierarchy�consists�of�
nodes�(A�point�in�a�network�at�which�lines�cross�or�branch.)�
*To�create�Customer�Hierarchy:�1.Create�Master�Records�per�node.�
2.�Assign�nodes�to�each�other.�
3.�Assign�Customer�Master�to�relevant�nodes.�
*Hierarchy�nodes�are�only�valid�for�a�certain�period�of�time.�They�may�also�be�
moved.�If�node�is�
moved,�system�automatically�reassigns�all�related�nodes�&�customer�master�
records.�Basically,�you�can�assign�price�or�rebate�agreements�to�higher�level�
nodes.�These�agreements�will�be�valid�for�all�subordinate�levels�to�this�node.�
Each�node�can�also,�have�pricing�condition�records�which�
are�relevant�for�pricing.�If�one�or�more�node�in�the�hierarchy�path�of�sales�
orders�contains�pricing,�
info�system�then�takes�them�into�account�automatically.�Condition�HI01�Ex:�
customer�****�is�from�Pakistan�give�8%�discount.�
*Condition�Table-Define�key�fields�of�the�condition�records.�
*Access�Sequence-Contains�Hierarchy�for�condition�record�access.�
*Condition�Type-Represents�properties�of�the�pricing�conditions.�*Pricing�
Procedure-Defines�how�condition�types�are�linked.�*Procedure�Determination-�
Selects�correct�pricing�procedure.�
Determining�Condition�Records�
1.�Customer/Material�
2.�Price�List�Type/Currency/Material�
3.�Price�List�Type/Currency/Material�Foreign�Currency�
4.�Material�
Creating�Condition�Records�with�Reference�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
-----------------------�Page�170-----------------------
20�
New�condition�Records�can�be�created�with�reference�to�existing�condition�
records.*Changes�can�
be�made�to�the�Rate,�Validity�Period,�and�additional�sales�data.�<---This�is�goo
d�
for�efficiently�updating�condition�records�simultaneously.�Changing�condition�
records�*Can�be�changed�using�price�change�function�which�will�allow�you�to�
maintain�multiple�condition�records�simultaneously.�Copying�Condition�Records�
*Multiple�condition�records�can�be�creating�copying�existing�condition�records.�
If�
you�are�copying�a�Customer-Specific�Price�condition�record�the�system�offers�2�
possibilities:�1.�Create�the�target�conditions�over�a�specified�range�of�custome
r�
numbers.�2.�Create�the�target�conditions�over�a�specified�range�of�material�
numbers.�Searching�for�Condition�Records�using�Condition�Indexes�You�can�
create�and�use�condition�indexes�to�search�for�condition�records�that�were�
created�for�a�variety�of�condition�types�&�condition�tables.�Ex:�Want�to�see�all
�
C.R.�for�particular�cust�or�prod.�The�activation�function�displays�a�list�of�all
�
available�condition�indexes�&�indicates�which�are�active.�The�system�can�only�
use�the�condition�indexes�when�there�active.�Note:�Before�you�can�use�condition�
indexes�you�must�first�ACTIVATE�them.�However�if�you�create�your�own�index�
the�system�activates�them�when�you�generate�them.�But�you�must�specify�an�
update�requirement�for�each�index.�You�can�specify�if�the�system�updates�the�
cond.�Index�when�you�post�cond.�Records�for�the�corresponding�condition�type.�
Release�Procedure�for�Conditions�When�a�condition�table�is�created�you�can�
allow�a�release�procedure�to�be�used,�by�selecting�the�with�release�status�
checkbox.�This�then�adds�2�functions�to�the�condition�table:�1.�KFRST-Release�
status�as�last�key�field.�2.�KBSTAT-Processing�status�as�a�field�of�the�variable
�
data�part�(Non�Key�Field).�The�release�status�is�set�indirectly�by�defining�a�
processing�status�in�customizing�for�pricing�and�assigning�a�release�status�to�i
t.�
Also,�you�can�convert�old�records�to�new�ones.�Now�you�can�choose�a�
calculation�type�when�creating�condition�records�at�the�same�time.�Pricing�
Condition�Tables�Additional�Condition�tables�can�be�created�for�specific�
requirements�They�are�used�to�determine�the�key�in�the�condition�records.�You�
can�add�fields�to�the�field�catalog�in�order�to�create�new�condition�records�bas
ed�
on�different�criteria.�It�is�important�to�list�the�fields�in�a�condition�table�i
n�the�
proper�order.�*Long�text�can�be�added�to�Rebate�Agreements,�Promotions,�and�
Sales�Deals.�*Long�text�in�the�rebate�agreement�can�be�copied�into�a�credit�
memo�request�for�rebate�payments�and�then�into�the�credit�memo.�*Text�is�not�
copied�when�you�create�condition�records�with�reference.�*A�condition�type�can�
be�classified�as�a�group�condition.�Price�Update�Values�can�be�accumulated�in�
condition�records�to�test�against�those�limits.�Condition�type�must�be�set�for�
"condition�update"�in�IMG.�Condition�update�can�be�set�for�maximum�condition�
value.�FALSE�Study�guide�prepared�by�Manoj�Kumar�
[email protected]�21�Cumulative�values�cannot�be�displayed.�
Condition�update�cannot�be�set�for�number�of�orders.�*Condition�supplement�do�
not�have�their�own�access�sequence�but�is�based�on�other�conditions.�They�are�
-----------------------�Page�171-----------------------
found�with�the�underlying�condition�records.�*�Multiple�conditions�can�be�
grouped�together�in�a�group�supplement�procedure.�*�The�system�will�allow�you�
create�conditions�based�on�customer�or�material�hierarchy.�The�system�process�
however�requires�a�lot�of�maintenance�and�reduces�system�performance�and�is�
considered�a�disadvantage.�*�Without�hierarchy�accesses�you�need�to�create�a�
condition�table�for�each�combination�and�assign�all�accesses�to�these�tables�in�
the�access�sequence.�Taxes�*You�can�assign�a�rule�(Blank,�A,�or�B)�at�the�sales�
organization�level�to�determine�sales�tax�id#�in�the�order�&�billing.�For�the�
status�'BLANK',�the�standard�priority�rules�are�as�follows:�1.�If�PY�has�a�sales
�
tax�ID�and�a�different�SP�-�The�tax�number�and�tax�classification�are�taken�from
�
PY�(the�SH�is�then�no�longer�relevant).�The�tax�number�is�determined�according�
to�the�'tax�destination�country'.�2.�If�1.�does�not�apply:�-�If�the�SH�has�a�sal
es�
tax�ID�or�the�SP�has�NO�sales�tax�ID,�the�tax�number�and�tax�classification�are�
taken�from�the�SH.�3.�If�2.�does�not�apply:�Tax�number�and�tax�classification�
are�transferred�from�the�sold-to�party.�With�status�'A',�the�tax�number�and�tax�
classification�are�generally�transferred�from�the�sold-�to�party.�The�tax�number
�
is�transferred�according�to�the�'tax�destination�country'.�With�status�'B':�Data
�is�
transferred�from�the�payer�in�the�same�way�as�rule�A.�The�following�factors�play
�
a�role�in�tax�determination:�Business�transaction�-�domestic�or�export/import�
Tax�liability�of�the�ship-to�party/comes�from�the�customer�master�Tax�liability�
of�
the�material/comes�from�the�Material�Master�The�system�determines�a�tax�rate�
in�the�document�(order/billing�document)�on�the�basis�of�these�three�criteria.�
*Taxes�are�determined�with�the�normal�5�step�condition�technique�*Condition�
type�for�tax�will�be�part�of�the�normal�pricing�procedure�Agreements�
(Promotions�&�Sales�Deals)�*You�can�define�a�promotion�or�general�marketing�
plan�for�a�product�line�for�a�certain�period�of�time.�You�can�then�link�this�
promotion�with�specific�sales�deals,�which�are�linked�to�special�condition�
records.�These�condition�records�can�be�used�for�promotional�pricing�or�
discounts.�The�sales�deal�number�and�the�promotion�number�will�be�displayed�in�
the�detail�of�the�billing�document�item�line�and�will�then�also�update�SIS�
accordingly.�Study�guide�prepared�by�Manoj�Kumar�
[email protected]�Release�Status�for�Sales�Deals�The�release�status�
of�a�sales�deal�controls�where�you�can�find�the�condition�records�for�a�sales�
agreement.�__=Released,�A=Blocked,�B=Released�for�price�simulation,�
C=Released�for�price�simulation�and�Planning.�Rebates�The�following�must�be�
activated�for�rebate�processing�to�function:�Sales�Organization�(If�not�needed�
deactivate�for�better�performance)�The�Payer�Master�Billing�Document�Type�22�
Rebates�are�discounts,�which�are�granted�subsequently�to�rebate�recipients,�
based�on�defined�sales�volumes�within�certain�periods�of�time.�To�determine�the�
values�required�for�a�rebate�settlement�within�the�validity�period,�you�create�
rebate�agreements.�The�system�uses�the�accumulated�amounts�in�the�rebate�
agreement�to�create�a�rebate�settlement.�Rebate�Agreement�Types�0001---�
>Material�Create�
0002--->Customer�Rebate�
0003--->Customer�Hierarchy�Rebate�
0004--->Material�Group�Rebate�
-----------------------�Page�172-----------------------
0005--->Independent�of�Sales�volume�
Rebate�Agreement�is�created�with�a�specific�Rebate�Agreement�types.�Rebate�
Agreement�types�contain�all�the�rules�and�control�that�will�influence�the�
behavior�/�features�of�a�rebate�agreement.�
Rebate�condition�records�are�linked�to�rebate�agreements�specifying�the�Rebate�
rate�&�Accrual�rate.�You�can�specify�in�the�agreement�type�1)�Condition�types�
used�with�this�rebate�agreement�type.�2)�Validity�period�proposal.*Rebate�
agreements�can�be�settled�partially.�
*The�payer�must�be�relevant�for�rebate�processing.�Rebate�processing�begins�
by�creating�a�rebate�relevant�billing�document.�The�valid�rebates�are�
determined�by�the�pricing�procedure�using�rebate�basis�total.�Each�rebate�
condition�type�has�an�assigned�access�sequence.�The�system�then�uses�the�
Access�Sequence�to�look�for�valid�rebate�condition�records.�If�found�then�the�
accrual�rate�is�read.�Requirement�24�in�pricing�procedure�says�that�the�rebate�
condition�are�used�only�in�billing�doc.�
Requirement�25�in�p.p.�says�that�rebate�conditions�be�used�only�in�rebate-�
relevant�billing�doc.�The�
rebate�accrual�amount�is�calculated�using�rebate�basis�in�billing�doc.�The�syste
m�
posts�an�accrual�to�FI-Accounting�as�soon�as�the�rebate-relevant�billing�doc.�is
�
released�to�accounting.�The�system�then�updates�the�rebate�basis�&�accrual�
amount�in�the�rebate�agreement�sales�volume�screen.�
Rebate�Settlement�
The�system�uses�the�accumulated�amounts�in�the�rebate�agreement�to�create�a�
rebate�settlement.�
Status�A�refers�to�an�open�rebate�agreement.�The�system�generates�a�rebate�
credit�memo�request�for�the�rebate�payment�amount�specified.�You�can�display�
the�sales�volume�and�drill�down�in�the�rebate�agreement.�
You�can�carry�out�a�final�settlement�for�the�rebate�agreement�either:�
*manually�
*automatically�
*in�the�background�(batch�programs:�RV15C001�and�RV15C002)�
Accruals�are�reversed�as�soon�as�the�rebate�agreement�is�settled�by�credit�
memo.�
Retroactive�rebate�agreements�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
23�
Retroactive�rebate�agreements�allow�you�to�take�into�account�billing�documents�
-----------------------�Page�173-----------------------
created�before�
the�rebate�agreement�is�created.�The�rebate�basis�for�the�billing�documents�
created�previously�is�
accumulated�and�recorded�in�the�rebate�agreement.�The�accrual�amount�is�not�
automatically�updated�for�previously�created�billing�documents.�This�amount�
must�be�entered�manually.�
Rebate-relevant�billing�documents�created�after�the�rebate�agreement�has�been�
created,�will�update�both�the�rebate�basis�and�accrual�fields�automatically.�
Partial�Rebate�Settlement�
Partial�rebate�settlements�can�be�limited�for�each�rebate�agreement�type�as�
follows:�
*up�to�the�accumulated�accrual�amount�
*up�to�the�calculated�payment�amount�for�the�current�date�
*Unlimited�
Accruals�are�cancelled�automatically�when�a�credit�memo�is�created,�provided�
that�the�rebate�
agreement�type�is�set�accordingly�in�Customizing�
Settlement�Material�
You�may�have�a�rebate�that�does�not�refer�to�a�particular�material,�but�rather�t
o�
a�group�of�
materials�or�to�a�customer.�In�this�case,�you�must�refer�to�a�settlement�materia
l�
in�order�to�provide�
information�at�the�material�level.�Maintain�the�rebate�material�in�the�material�
master�in�the�Sales�
and�Accounting�views.�When�creating�a�credit�memo,�the�settlement�material�is�
the�source�for�important�material�master�data.�For�example,�account�
determination.�
Free�Goods�
You�have�created�an�exclusive�free�goods�agreement�and�you�would�like�the�
ordered�item�to�
absorb�the�cost�of�the�free�goods.�In�order�to�transfer�the�correct�information�
to�
CO-PA�from�SD�
billing,�you�have�to�deactivate�pricing�in�the�item�category�of�the�free�item,�a
nd�
Set�the�cumulative�indicator�in�copying�control�for�the�billing�item.�
Solution�Manager�
The�system�landscape�does�include�solution�manager.�
Solution�manager�is�needed�to�efficiently�and�effectively�only�implement�and�
operate�an�
enterprise�sap�solution.�False�
In�implementation�soleman�covers�more�than�one�of�the�following�areas:�
functional�implementation,�technical�implementation,�and�implementation�of�
operations.�
-----------------------�Page�174-----------------------
Sap�soleman�is�a�customer�platform�that�enables�representation�and�
documentation�of�the�entire�customer-specific�solution,�including�sap�and�non-�
sap�components.�
Soleman�enables�process-oriented�versus�component-orientated�configuration�&�
Testing.�
Sap�roadmap�5�phases:�Project�preparation,�Business�Blueprint,�Realization,�
Final�Preparation,�and�Go�live�&�support.�
Phase�2--->Finalizing�the�project�scope,�Defining�and�documenting�all�business�
requirements,�both�functional�and�technical.�
Phase�3--->Configuring�the�system,�testing�the�system�to�ensure�that�it�meets�
the�specified�business�requirements,�and�developing�training�materials.�
*It�is�an�integrated�platform�that�controls�both�implementation�and�operation�of
�
the�live�system.�
*Supports�customers�in�ALL�project�phases,�from�creating�a�blueprint�to�
configuring�business�processes�and�testing�through�support�of�the�live�
environment.�
Study�guide�prepared�by�Manoj�Kumar�[email protected]�
24�
*Accelerators�are�found�in�the�Knowledge�Warehouse�in�SAP�Solution�Manager�
in�the�form�of�templates.�
Document�Management�Systems�in�soleman�have�these�key�highlights:�
*Central�Storage�of�all�
project�documentation.�*Provides�functionality�for�creating,�editing,�storing,�
uploading�and�
downloading�documentation.�*Reporting�features�(by�assignment-�
>Documentation)�allow�you�to�track�and�filter�all�available�documents.�
Soleman�as�the�technical�and�operations�infrastructure�has�more�than�the�
following�
components:�Services�for�operations,�Solution�monitoring,�and�Support�
Sap�Soleman�is�more�than�*A�Proactive�Methodology�*Business�Process�
Orientated�*Software�
Solution�landscape�Oriented�*Configurable�
Sap�marketplace�can�be�accessed�thru�Solution�Manager�whenever�needed.�
-----------------------�Page�175-----------------------
*A�new�business�process�procedure�can�be�created�from�a�standard�template.�
*The�Knowledge�Warehouse�contains�numerous�accelerators.�
MATERIAL�YOU�MUST�STUDY�FOR�ESTABLISHING�YOUR�SAP�CAREER�
!!�
Important�Tips�for�Interview�for�SAP�SD�
Let�me�share�some�important�tips�for�interview�for�SAP�SD:�
1.�Please�be�through�with�the�projects�you�have�mentioned�in�your�resume.�
2.�Remember�all�the�versions�you�have�worked�upon.�
3.�If�your�projects�are�in�Indian�scenario�be�thorough�with�CIN/Excise�VAT�and�
pricing�procedure.�
4��For�offshore�client�specially�in�Europe�and�NASA�prepare�yourself�for�
Warehouse/Lean�warehouse�
5.�Third�party�billing�/�Intercompany�/�Make�to�order�are�important�topics.�
6.�Cost�booking�that�is�accounting�enteries�after�PGI�and�Billing�should�be�
known�to�you.�
7.�Mug�up�all�the�determinations.�
8.�Remember�your�last�ticket.�
9.�Have�general�awareness�about�ALE/EDI/IDOC,�as�this�provides�added�
advantage.�(not�very�tough)�
10.�Please�be�through�with�your�basics,�the�process,�the�pricing�and�the�master�
data.�
11.�People�who�are�thorough�with�route,�transportation,�shipping�always�have�
an�added�advantage.�
The�MOST�IMPORTANT�THING:�
Do�not�try�to�fool�your�interviewer,�say�exactly�and�only�what�is�asked�do�not�
show�your�excitement�and�do�not�speak�too�much�if�you�know�the�topic�too�
well,�and�say�a�straight�NO�if�you�have�not�worked�on�something,�or�don't�know�
about�something,�pls�pls�pls�don't�not�go�for�flukes�otherwise�you�will�end�up�i
n�
soup.�
What�I�understand�is�most�of�the�companies�especially�in�the�US�are�
looking�for�a�candidates�with�
1)�good�communication�skills�(SAP�is�all�about�interacting�with�the�
client,�users�and�team)�
2)�good�business�knowledge�
3)�are�you�able�to�convince�the�client�
That�comes�in�next�round�when�you�are�interviewed�to�be�deputed�for�any�
US/Europe�project,�in�this�round�take�care�of�the�
following:�
1.�Speak�slow,�I�mean�normal,�because�usually�Indians�speak�english�too�fast.�
2.�Listen�to�them�carefully,�if�you�are�not�able�to�understand�their�question�
request�them�to�repeat�it,�rather�than�assuming�it�to�be�something�else�and�
giving�a�wrong�reply.�
3.�Again�I�should�repeat�prepare�yourself�for�warehouse,�I�mean�even�general�
knowledge�will�help.�
-----------------------�Page�176-----------------------
4.�Say�a�straight�no�when�you�don't�know�or�have�not�worked�on�the�topic.�
5.�Always�be�strong�on�SD�MM�FI�integrations�
What�the�job�responsibilites�would�be�for�the�Support�Consultant?�If�
the�Consultant�is�working�in�Offshore�Support,�How�the�business�
interaction�would�be�there�between�the�Consultant�and�Customer?�How�
the�Customer�Queries�were�handled�successfully�sitting�from�his�
location.�
Job�responsibility�of�a�Support�consultants�is�to�handle�routine�tickets,�which�
can�be�incident�(routine�problems),�change�tickets�(need�configuration�change,�
therefore�a�change�request),�normally�a�support�consultant�can�only�advice�a�
change�but�can't�do�it�,�because�there�is�always�a�change�advisory�board�on�
client�end�to�evaluate�and�implement�the�adviced�change.�
Business�intercation�between�users�and�customer�can�be�through�mail�box�
utilities,�outlook,�even�telecons�and�some�companies�also�allow�chat.�
Usually�the�customer�provides�with�the�number�of�the�document�and�
client/company�code�and�other�necessary�info.�about�the�process�which�is�facing�
problem,�the�consultant�tracks�the�project�by�logging�in�to�development�server�
and�search�out�for�causes,�the�solution�is�then�sent�to�user,�maybe�with�
snapshot�if�required.�
For�those�people�who�asks�for�for�tickets:�
1.�Tickets�are�normally�raised�by�end�user�and�carry�a�priority.�
2.�Those�who�are�asking�SAP�gurus�to�tell�them�about�tickets,�pls�note�that�
most�of�the�problems�except�for�the�basic�questions�discussed�in�this�group�are�
the�tickets�themselves,�tickets�are�nothing�but�the�routine�incidents�the�SAP�
consultants�get,�if�you�regularly�read�the�mails�in�the�group�you�will�soon�star
t�
recognizing�tickets.�
And�the�most�important�thing�"Believe�in�yourself�and�God,�as�there�is�always�
somebody�there�to�help�you".�
Tips�by�:�Nitin�
What�is�the�team�size?������Duration�of�the�project.�
Hardly�the�team�of�the�sd�will�be�4�to�5�and�entire�team�of�the�project�will�be�
around�20-24�(all�modules�like�fi/co,�sd,�mm,�pp,�hr,�qm,�pm).��If�its�big�
project,�it�will�be�around�40.��Team�size�means�the�employees�who�you�are�
working�on�sap�r/3�implementation.�
For�the�project�completion�it�will�take�around�8-10�months�to�get�into�golive.�
After�that,�post�implementation�for�3�months.����After�that�supporting�it�depend
s�
as�project�time�line�for�every�company�is�different.���*--�Suresh�Kumar�
SAP�SD�Interview�Questions�
-----------------------�Page�177-----------------------
Following�are�some�SD�Interview�questions�that�might�be�asked.�
1.��What�is�the�purpose�of�text�determination,�account�determination,�
partner�determination,�output�
����determination,storagelocation�determination�
2.��What�are�the�five�imp�fields�to�be�maintained�in�account�
determination�
3.��How�to�create�excise�invoice�and�what�is�it�
4.��What�is�meant�by�transfer�of�data�from�legacy�code�to�sap�
5.��What�do�you�do�really�in�pricing�determination,�and�what�are�the�
main�deifferences�between�
����one�pricing�procedure�determination�to�the�others,�which�data�
control�these�differences�
6.��What�type�of�reports�generally�a�support�consultant�maintain�and�
report�
7.��What�are�interfaces�used������generally�an�indian�organisation��which�is�
in�retail�business�
����and�and�which�is�in�banking�business�and�oil�business.�
8.��What�is�the�purpose�of�shipping�point�determination�not�menu�path�
9.��What�and�where�types�of�copy�controls�we�change�
10.�How�to�and�where�to�maintain�copy�controls�
11.�What�is�purpose�of�maintaining�common�distribution�channels�and�
common�divisions�
Q.No.11�
Common�Distribution�Channel�and�Common�Divison�are�maintained�so�that�if�
any�master�data�like�customer�or�material�maintained�with�respect�to�one�
distribution�channel�can�be�used�in�other�DCh.�It�prevents�the�multiplication�of
�
master�records.�
Eg:�A�customer�is�created�for�say�sales�area�1000/20/00�then�the�same�
customer�can�be�used�in�sales�area�1000/30/00�if�we�maintain�20�as�common�
distribution�channel.�Hence�no�need�for�extending�the�customers...the�same�for�
materials�also.�
Rajendra�Babu�
As�of�what�I�know�answer�to�question�5�would�be:�
5.�we�determine�how�the�prices�are�calculated,�taking�into�account�sales�
area(sales�org,�distribution�channel,�division),�document�type�and�
customer(generally�sold-to-party).�
The�main�differences�between�pricing�procedures�would�be�the�differences�as�I�
mentioned�above,�from�the�point�of�view�of�field�entries.�
Coming�to�the�output�and�the�procedure,�I�suppose�the�condition�types�used�will�
be�different�and�hence�the�following�whole�procedure.�
Uday�
1.�What�is�the�purpose�of�text�determination,�account�determination,�partner�
determination,�output�determination,�
����storage�location�determination�
Text�determination:�For�transferring�information�from�material�or�customer�to�
order/delvery�or�invoice�(and�anything�inbetween)�
-----------------------�Page�178-----------------------
Account�determination:�For�transferring�financial�and�costing�information�to�
proper�financial�docs�
Partner�determination:�For�determing�who�is�is�legally�resposible�for�A/r,�who�
the�goods�are�going�to�and�whatever�else�you�waana�drive�through�this�
functionality.�
Output�determination:�What�kinda�output�does�a�sales/delivery/billing�document�
create�and�who�gets�it,�where?.�For�example�A�partner�might�get�an�EDI�
notification�for�a�sales�order�just�confirmed,�whereas�a�financial/leasing�
company�gets�the�invoice!�
2.�What�are�the�five�imp�fields�to�be�maintained�in�account�determination�
Go�to�IMG�and�find�out�
3.�How�to�create�excise�invoice�and�what�is�it.�
I've�never�worked�in�india�so�I�dunno�
4.�What�is�meant�by�transfer�of�data�from�legacy�code�to�sap�Legacy�Code�?�
It�should�be�legacy�data�to�SAP.�What�it�means�is�you�want�to�transfer�all�the�
customer�and�materials�and�all�other�information�from�Older�(legacy�system)�to�
new�SAP�system.�You�can�do�it�using�many�tools,�most�noticeably�MDMs.�
Vivek�
Regarding�q-3,�
As�per�Indian�tax�system,�Excise�duty�(16%)�is�payable�by�each�manufacturing�
unit�on�the�value�of�manufactured�goods�/�on�the�value�added.�The�
manufacturing�plant�is�supposed�to�submit�an�excise�duty�report�on�fortnightly�/
�
monthly�basis.�Various�registers�(RG1,�RG23A,�RG23C,�PLA)�are�maintained�for�
that�purpose,�which�record�all�the�transactions�including�movement�of�goods,�
cenvat�credit�available�and�cash�balance�available.�
In�SAP,�we�use�transaction�j1id�for�configuration�and�j1iin,�j2i7,�j1i5,�j2i5,�j
2i6,�
j1ip�for�creating,�extracting�and�printing�excise�invoice.�
Jitesh�
1.�(a)�Text�Determination:�Any�Texts�in�Masterial�Master/Material�
Determination/Order/Delivery�,�etc�is�meant�to�convey�messages�to�the�
subsequent�documents�for�compliance.�e.g.�"Give�Top�Priority"�message�
mentioned�in�Order�is�meant�for�Production�Dept.�
���(b)�Account�Determination:is�integration�between�Finance�and�SD.�The�A/P�
along�with�Account�Keys�need�to�be�allocated�accordingly�with�combination�of�
Account�Determination�Group�for�Customer�and�Material�if�required.�
���(c)�Partner�Determination:To�identify�which�type�of�Partner�it�is�so�that�if�
required�for�same�Customer�different�Partner�Functions�may�be�required�e.g�
Only�One�Sold�To�Party�per�Customer.�More�than�One�Ship�to�Party/�Bill�to�
Party/�Payer�possible.�Accordingly�different�Masters�will�have�to�be�created.�
Useful�for�despatch�of�Material�in�casae�of�Ship�to�Party,�sending�Bill�in�case�
of�
Bill�to�Party�and�payment�followup/Dunning�in�case�of�Payer.�
���(d)�Output�Determination:�What�type�of�Output�(Fax/Mail,�etc)�is�required,�
where�and�in�what�Format(ABAP�Customisation�may�be�required�in�some�cases�
especially�Invoices).�
���(e)�Storage�Location�Determination:�depends�on�Plant,�������Shipping�Point�an
d�
Storage�Conditions�
-----------------------�Page�179-----------------------
(2)�Account�Determination:�Sales�View,�Sales�Organisation,�Distribution�Chanel,�
Chart�of�Accounts,�Account�Assignment�Group�for�Customer�and�Material�and�
Account�Keys.�
(3)�I�will�check�and�let�you�know�within�week.�
(4)�Before�installation�of�SAP,�Data�maintained�by�Company�is�called�Legacy�
Data.�At�the�time�of�instalation,�it�is�required�to�transfer�Data�from�Legacy�to
�
SAP�like�Masters�(Material/Customer,�etc).�It�can�be�done�in�various�ways�like�
BDC,�LSMW,�etc.�
(5)�Pricing�is�determined�by�combination�of�Sales�Organisation,�Distribution�
Channel,�Division,�Customer�Pricing�Procedure�and�Document�Pricing�
Procedure.�
(6)�Depends�on�Customer�requirements.�
(7)�Its�not�clear.�
(8)�So�that�Shipping�Point�is�determined�automatically�once�the�settings�for�the
�
same�are�done.�
(9)�Copy�Control:�is�basically�meant�so�that�Data�is�copied�from�preceding�
Document�to�subsequent�one.�What�subsequent�Document�is�required�is�to�
some�extent�determined�by�Customer�Requirements�as�well�as�Document�
Types.�e.g.�In�general�case�of�Standard�Order,�it�will�be�Copy�Control�(Order�to
�
Delivery)�from�OR�to�LF�.�
(10)�Check�for�yourself�in�IMG�(Sales�Document�types�and�Delivery�Document�
Types)�
Shailesh�
What�is�the�difference�between�the�Avaialbility�check�01�(Daily�
requirement)�and�02�(Individual�Requirement)�in�material�master?�
01�and�02�are�the�checking�group.�Availability�check�is�carried�out�with�the�hel
p�
of�these�checking�group�and�checking�rule.�Checking�group�01�and�02�are�
maintained�on�the�material�master.�
01�-�Individual�requirement�-For�this�system�generates�transfers�the�
requirement�for�each��order�to�the�MRP�.So�that�MM�can�either�produce�or�
procure.�
02-�Collective�requirement.-In�this�all�the�requirements�in�aday�or�in�a�wek�are
�
processed�at�a�time.��System�stores�all�req�and�passes�on�to�the�MRP�in�MRP�
run.In�this�system�performance�is�high�however�you�can�not�do�the�backorder�
processing�whereas�in�other�you�can�do.��������*--�Vishwajit�
Some�SAP�SD�Interview�Questions�1�
1.�What�exactly�is�automatic�posting�can�you�explain?�
1.�Automatic�posting�could�be,�posting�of�accounting�documents�to�FICO�once�
invoice�is�created�which�can�also�be�controlled�manually.�Automatiaclly�
detremine�the�freight�while�pricing�in�ship�doc.�and�post�to�the�relevant�accoun
t�
to�fico.�usually�automatic�posting�is�posting�of�documents�to�FICO�based�on�
variuos�account�keys�and�account�groups.�
2.�How�many�clients�we�will�create�in�land�scape�(like�in��development�
-----------------------�Page�180-----------------------
server,�quality�server,�production�server�)�
���if�we�are�creating�more�than�one�in�each�server�what�is�exact�use�of�
that�client.�
2.�Client�landscape�:�Basic�layout�:�dev�-testing-�production�also�
-�Sandbox�env.�for�trial�and�error�
-�Development�env.�for�actaully�creating�transports(CTS)�
-�Global�env.��If�you�have�global�implementations�at�different�client�locations�
(eg;canada,�US,�UK)�(for�testing�purposes�with�actual�master�dataas�well)�
-�Testing�env.(for�regression�testing�purposes�before�moving�to�prodcution,�
integration�etc..)�
-�Prod.�env.�the�actual�production�system�
The�clients�could�be�variable�and�could�be�created�to�a�specific�env.�usually�a�
dev.�where�abap,�functional�would�mess�around.�say�:�
���client�100-functinal�consultants�
���client�300-�abapers�
���client�400-�other�users(like�super�etc)�
3.�How�we�will�configure�export�sales�in�sd�(respect�to�plants�assign�
and�sales�process)?�
4.�How�we�can�do�invoice�split�depending�on�item�category�in�which�
scenario�we�will�use?�
4.�You�first�need�to�go�for�copying�controls�either�from�sales�to�billing�(invoi
ce)�
or�delivery�to�billing�or�billing�to�billing�
use�transactions�(vtaa,vtaf,vtla,vtfa,vtfl,vtff)�all�possibilities�for�copy�cont
rols.�
this�basicly�is�flow�of�doc�to�doc.�(may�it�be�sales�to�billing,�del�to�bil,�or�
bil�to�
bil�etc..)�
->�this�is�where�you�see�the�Item�category�and�you�control�whether�split�is�
possible�or�not�with�the�indicator"B".�eg:��������representing�split�in�invoice�
based�on�
item�category.��The�field�here�"data�VBRK/VBRP"�(headre/item)whcih�actually�is�
used�for�splits�or�combining�different�deliveries.�create�a�splitting�rule�using
�
VOFM�(you�need�access�key�to�get�here).������������Here�you�define�comparisions�
for�the�
fields�at�header�table�and�item�tables�and�the�comparision�fields�say�
SPART"division".�"purchase�order�"BSTKD�Instance:�5�sales�orders�combined�
into�2�deliveries�and�the�split�at�the�invoice�would�be�5�individual�billing�wit
h�
respect�to�fields�PO�and�DIv.�of�each�sales�order�would�let�you�create�5�billing
s.�
You�need�to�define�the�exact�"field"�in�the�comparisions�both�at�header�and�item
�
level�that�could�lead�to�invoice�split.�the�key�here�is�the�field�that�is�differ
ent�
from�header�to�item�will�cause�split�at�the�item�level.�
5.�Can�any�one�explain�how�we�will�configure�milestone�billing�,�periodic�
billing�and�which�scenario�we�will�use?�
5.�Menu�path:�
IMG->sales�&distr->Billing->billing�plans->define�billing�plan�types.�
You�set�the�start�date�and�end�dates�if�applicable�to�the�type�of�billing�you�ar
e�
using.�What�time�to�be�billed�(end�of�month,�start�of�month�etc..)�
Milestone�is�a�billing�plan�type�where�a�customer�is�billed�for�the�amount�
distributed�between�the�dates�until�total�value�is�reached�eg:�if�the�total�bill
ing�
amountis�1000�USD�for�a�year.��You�will�bill�the�customer�in�different�amounts�
-----------------------�Page�181-----------------------
say�200,�500,�300�at�different�intervals�as�per�customer�agreement.�
On�the�other�hand�Periodic�billling�is�billing�the�customer�for�the�total�
amount(here�1000�USD)�at�regular�intervals�peridically�until�the�customer�
agreement�is�reached.�eg:�1000/12�for�a�1�year�agreement�and�say�billed�at�the�
1st�day�of�every�month.�
6.�What�are�some�pricing�routines�and�sd�functional�specs?�
6.�Form�routines�for�prcing�and�variuos�other�functions�can�be�maintained�form�
routines�are�something�todo�with�ABAP�code.�
Go�to�(VOFM)�where�all�requrements�whcih�are�represented�by�form�routines�
can�be�maintained.�����Requrements�are�available�to�be�assigned�where�access�
sequenses�are�used�(for�determination�procedures,�here�pricing).�
Once�the�tcode�VOFM�is�accessed�you�will�see�requrements�and�go�select�
"pricing"�again�you�need�access�key�to�create�your�own�or�copy�a�routine.�
Say�you�want�header�price�not�to�have�effect�the�item�pricing,�you�need�to�go�to
�
the�program�to�change�abap�code�to�meet�the�requirement.�this�specific�
requirement�you�created�will�be�assigned�in�the�pricing�proc.�determination�
"requirements�field"�
usaully�with�a�number�beyond�600.��������Note:�make�sure�you�activate�your�routi
ne�
for�its�effect�to�take�place.�
SAP�SD�Tips�by�:�Sunil�David�
Some�SAP�SD�Interview�Questions�2�
Some�of�the�interviewed�questions�and�answers�are�as�follows:�
What�is�the�movement�type�you�used�in�consignment�process?�
�###�632,�633,�634,�631�
Can�team�size�be�40�in�a�project?�Is�there�any�generalized�team�size�no.�
for�any�project?�If�we�tell�my�team�size�is�40�in�that�what�no.�we�can�
say�sd�people�are?�
�##�Team�size�cant�be�forty,�Theres�no�genralized�size�of�team.�Never�
40�sd�consultants�work�together�on�same�project.�
What�is�ALE?�
�##�Application�Linking�and�Enabling�-�Generally�ABAPers�work�on�it.�
What�is�meant�by�condition�technique:�can�we�say�it�is�the�combination�
of�condition�types,�access�sequence�and�condition�tables?�
�##�yes�
Where�do�we�can�find�pricing�procedure�indicator�in�sd�?�
�##�Pricing�procedure�is�where�we�maintain�all�Conditions�(like�PR00,�K004,�
mwst,�kp00,�etc)�
-----------------------�Page�182-----------------------
Where�do�we�assign�calender�in�the�master�records?�
�##��In�IMG�screen�Global�Settings.�
What�is�the�importance�of�customer�account�groups?�
�##�We�maintain�the�customer�account�to�maintain�payment�terms�and�
incoterms.�Lets�say,�if�SP�is�only�booking�order�but�the�goods�should�deliver�in
�
foreign�country�and�for�which�SP�is�not�going�to�bare�the�excise�and�other�taxes
�
then�the�SH�party�or�payer�will�tke�teh�responsibity�then�the�tax�is�calculated�
based�on�account�groups.�
What�are�incoterms?�Where�do�we�fix�them?�Where�do�you�find�in�
regular�process?�
�##�Incoterms�or�international�comm.�terms�and�u�find�in�CMR�-�Sales�area�
Data�-�billing�Tab.�
How�can�you�make�some�of�the�fields�as�key�field�in�generic�tables?�
�##�Some�fields�in�all�tables�have�a�indicator�on�it.To�see,�then�go�to�SE11,�
display�VBAK,�u�will�find�MANDT�on�top,�if�you�see�after�description�2�tick�
marks,�those�are�key�fields.���Gernerally,�these�key�fields�are�used�in�writing�
any�
Program�or�Interface.�The�key�fields�will�extract�data�of�non�key�fields�.�
What�is�the�standard�group�condition�routine�in�condition�type,�what�is�
its�importance?�
�##�Its�better�u�read�Group�Conditions�in�PR00.�
How�do�you�control�entry�possibility�of�condition�values�at�order�
through�condition�type�settings?�
�##�You�can�maintain�the�maximum�and�minimum�value�for�all�conditions.�
What�are�the�customizing�settings�in�pricing�procedure�for�tax�condition�
type?�
�##�Check�out�the�standard�pricing�procedure�RVAA01�-�MWST.�
A�bunch�of�data�need�to�be�imported.�A�huge�no.of�creations�are�
required,�how�it�is�possible�in�SAP?�
�##�thru�LSMW,�BAPI.�
What�is�the�difference�between�PGI�cancellation�and�returns�order?�
�##�PGI�cancellation�is�done�before�the�transportation�of�goods.�But�return�
order�means�its�already�transported�reached�customer�during�transit�if�materil�
is�spoiled�or�broke�or�the�goods�r�not�delivered�as�per�customer�requested�
date.then�customer�send�the�goods�baack�to�company.�
What�is�the�integrated�areas�in�SD�AND�FI,�SD�AND�MM,�SD�AND�PP�in�
both�implementation�and�support�projects?�
�##�SD�&�FI�-�Possible�in�Account�Determination,�for�posting�the�conditions�to�
-----------------------�Page�183-----------------------
revelant�G/l�account�like�all�prices�goes�to�one�particular�g/l�account.�Also�in
�
Credit�Management,�Taxes.�
��SD�&�MM�-�Possible�in�Batches,�Material�Requirement�Planning.�
��SD�&�PP�-�Possible�in�Material�Requirement�planning.�
��Link�Between�SAP�SD,�MM�&�FI�
Tips�by:���Kumar�
Availability�Check�on�Quotation�
SAP�standard�does�not�do�an�availability�check�on�the�quotation,�as�it�is�
not�a�definite�order,�usually�just�a�pricing�quote.�
When�it�is�converted�to�an�order,�the�first�availability�check�is�carried�out,�a
s�
well�as�credit�checks.��The�system�will�check�stock�in�the�plant,�plus�what�is�
contained�in�the�availability�checking�rule�(scope�of�check)�eg:�can�add�POs�for
�
replenishment,�purchase�reqs,�different�planned�orders,�and�subtract�sales�
orders,�deliveries�etc�already�created�against�that�material�in�that�plant�(and�
possibly�Storage�location).�
If�there�is�enough�stock�in�the�plant/SLoc,�the�system�will�give�you�a�confirmed
�
date,�or�give�you�a�date�based�on�the�production�time�or�purchasing�time�from�
the�material�master.��The�date�the�system�proposes�is�based�on�the�customer's�
requested�delivery�date.�
SAP�first�backward�schedules�looking�at�the�required�delivery�date,�less�
transportation�time,�less�transportation�lead�time,�less�pick�and�pack�time,�les
s�
production/purchase�time�if�applicable.��If�the�date�it�calculates�is�equal�or�l
ater�
than�today‟s�date,�then�it�will�confirm�the�customer‟s�required�date.����If�it�falls
�in�
the�past,�SAP�will�then�forward�schedule�for�today‟s�date,�plus�the�times�listed��
above�to�get�the�date�when�the�customer�can�actually�have�it.�
ATP�is�the�single�most�complex�part�of�the�SD�module,�depending�upon�how�PP�
and�MRP�is�set�up.�
MRP�works�semi-separately,�depending�on�how�it�is�set�up.�������Basically,�MRP�l
ooks�
at�the�demand�on�the�plant,�and�if�it�the�stock�does�not�meet�expected�sales�
orders�and�deliveries,�it�will�create�a�purchase�requisition�(outside�purchase)�
or�
requirement�or�planned�
Interview�Question�and�Answers�on�SAP�SD�
1.What�are�the�responsibilities�of�a�functional�consultant�in�an�
implementation�project?�
a)�Responsibilities�in�implemention�project�
-�Preparing�the�functional�specification�documents.�
-�Review�and�approval�of�functional�specifications.�
-�Designing�a�road�map�and�setting�approval�from�client.�
-�Changing�existing�configuration�whenever�needed.�
-�Setting�up�configuration�for�new�enhancements.�
-�Handling�basic�issues�of�MM�module.�
-----------------------�Page�184-----------------------
b)Responsibilities�in�support�project�
-�Handling�customization,�configuration,�and�enhancement�related�issues�
-�Handling�tickets�on�Day�to�Day�basis�
-�Monitoring�S&D�reports�on�daily�basis�required�by�clients�
-�Preparing�functional�specification�documents�
-�Preparing�end�user�training�Documents�
2.What�are�the�responsibilities�of�a�technical�consultant�in�an�
implementation�project?�
Preparation�of�techinical�specifications,�getting�apporvals�from�functional�
consultant�and�PM,assitance�to�functioal�consultant.�
3.What�are�the�main�and�sub�modules�in�SAP?�
MM,FICO,PP,ABAP�
4.What�is�ERP�and�SAP?and�why�inplementing�SAP�in�an�organization?�
Explain�the�special�features�of�SAP�over�other�
ERPs?�
SAP�is�an�ERP�package.����SAP�can�be�fit�it�any�language.��It�is�used�to�get�exa
ct�
data�with�a�fraction�of�section�which�will�be�use�fully�for�management�to�take�
correct�decision�in�a�short�span�of�time.��Using�of�sap�means�there�is�no�need�t
o�
maintain�the�
middle�management�in�the�organization�because�the�CEO�of�the�company�is�
able�to�direct�the�executives�direcltly�with�the�system.��SAP�is�able�to�integra
te�
all�functional�organizational�units�togethere�and�retrieve�exact�data�needed�by�
management.�Therefore,�investing�on�middle�management�will�become�less.�
and�the�user�will�be�able�to�acess�instance�reports�using�the�logistic�informaio
n�
systems�in�SAP.�
5.Explain�the�business�flow�of�an�implementation�project?�
-�Project�prepration�
-�Business�blue�prints�
-�Fit�gap�analysis�
-�Realization�
-�Golive�
-�Support�
6.Explain�breifly�about�your�role�in�current/previous�project?�(If�you�
have�one)�
Team�member�
7.Explain�your�functional�experience�prior�to�SAP?�
For�this�you�will�give�explanation�depends�of�your�previous�experience.�
8.Can�you�explain�the�modern�technologies�in�SAP?������������Do�you�use�this�in�
your�current�project?�
I�think�the�ans�is�APO,�BW,�CRM,�if�its�wrong�pls�guide�me�any�body.�
9.Explain�the�terms�"AS�IS"�and�"FIT�GAP�ANALYSIS"?�
Business�blue�print�stage�is�called�as�is�process.��Fit�gap�means,�before�
implementing�the�SAP�all�the�business�data�is�in�the�form�of�documents,�we�
cannot�keep�this�data�as�is�in�the�SAP.��There�should�be�a�gap.����So�by�filling
�this�
gap,�we�make�configuration�with�the�help�of�these�documents.��This�is�called�as�
fit�gap�analysis.�In�this�stage,�we�should�analysis�the�gap�between�as�is�and�is
�
-----------------------�Page�185-----------------------
as�process�
10.What�are�the�responsibilities�of�"CORE�TEAM"�and�"FUNCTIONAL�
TEAM"�in�an�implementation?�
Core�Team�are�the�power�users�who�are�selected�for�the�SAP�implementation.�
The�Functional�Team�gather�the�initial�implementation�requirement�from�these�
core�team�users�who�will�be�the�bridge�between�the�SAP�Functional�Team�and�
their�department�users�with�the�expert�work�knowledge.�
Tips�by�:�Uday�Hyderabad�
Important�Tables�for�SAP�SD�
Sales�and�Distribution:�
������������������Table��Description�
Customers���������KNA1���General�Data�
������������������KNB1���Customer�Master�–�Co.�Code�Data�(payment�method,�
reconciliation�acct)�
������������������KNB4���Customer�Payment�History�
������������������KNB5���Customer�Master�–�Dunning�info�
������������������KNBK���Customer�Master�Bank�Data�
������������������KNKA���Customer�Master�Credit�Mgmt.�
������������������KNKK���Customer�Master�Credit�Control�Area�Data�(credit�
limits)�
������������������KNVV���Sales�Area�Data�(terms,�order�probability)�
������������������KNVI���Customer�Master�Tax�Indicator�
������������������KNVP���Partner�Function�key�
������������������KNVD���Output�type�
������������������KNVS���Customer�Master�Ship�Data�
������������������KLPA���Customer/Vendor�Link�
Sales�Documents���VBAKUK�VBAK�+�VBUK�
������������������VBUK���Header�Status�and�Administrative�Data�
������������������VBAK���Sales�Document�-�Header�Data�
������������������VBKD���Sales�Document�-�Business�Data�
������������������VBUP���Item�Status�
������������������VBAP���Sales�Document�-�Item�Data�
������������������VBPA���Partners�
������������������VBFA���Document�Flow�
������������������VBEP���Sales�Document�Schedule�Line�
������������������VBBE���Sales�Requirements:�Individual�Records�
SD�Delivery�DocumeLIPS���Delivery�Document�item�data,�includes�referencing�PO�
������������������LIKP���Delivery�Document�Header�data�
Billing�Document��VBRK���Billing�Document�Header�
������������������VBRP���Billing�Document�Item�
SD�Shipping�Unit��VEKP���Shipping�Unit�Item�(Content)�
������������������VEPO���Shipping�Unit�Header�
SD�Tcodes�
An�Introduction�to�SAP�
-----------------------�Page�186-----------------------
SAP�was�founded�in�1972�in�Walldorf,�Germany.�It�stands�for�Systems,�
Applications�and�Products�in�Data�Processing.�Over�the�years,�it�has�grown�and�
evolved�to�become�the�world�premier�provider�of�client/server�business�
solutions�for�which�it�is�so�well�known�today.�The�SAP�R/3�enterprise�applicatio
n�
suite�for�open�client/server�systems�has�established�a�new�standards�for�
providing�business�information�management�solutions.�
SAP�product�are�consider�excellent�but�not�perfect.��The�main�problems�with�
software�product�is�that�it�can�never�be�perfect.�
The�main�advantage�of�using�SAP�as�your�company�ERP�system�is�that�SAP�
have�a�very�high�level�of�integration�among�its�individual�applications�which�
guarantee�consistency�of�data�throughout�the�system�and�the�company�itself.�
In�a�standard�SAP�project�system,�it�is�divided�into�three�
environments,Development,�Quality�Assurance�and�Production.�
The�development�system�is�where�most�of�the�implementation�work�takes�
place.�The�quality�assurance�system�is�where�all�the�final�testing�is�conducted�
before�moving�the�transports�to�the�production�environment.��The�production�
system�is�where�all�the�daily�business�activities�occur.���It�is�also�the�client
�that�
all�the�end�users�use�to�perform�their�daily�job�functions.�
To�all�company,�the�production�system�should�only�contains�transport�that�have�
passed�all�the�tests.�
SAP�is�a�table�drive�customization�software.����It�allows�businesses�to�make�rap
id�
changes�in�their�business�requirements�with�a�common�set�of�programs.���������Us
er-�
exits�are�provided�for�business�to�add�in�additional�source�code.��Tools�such�as
�
screen�variants�are�provided�to�let�you�set�fields�attributes�whether�to�hide,�
display�and�make�them�mandatory�fields.�
This�is�what�makes�ERP�system�and�SAP�in�particular�so�flexible�.��The�
table�driven�customization�are�driving�the�program�functionality�instead�of�thos
e�
old�fashioned�hard-coded�programs.��Therefore,�new�and�changed�business�
requirements�can�be�quickly�implemented�and�tested�in�the�system.�
Many�other�business�application�software�have�seen�this�table�driven�
customization�advantage�and�are�now�changing�their�application�software�based�
on�this�table�customizing�concept.�
In�order�to�minimized�your�upgrading�costs,�the�standard�programs�and�
tables�should�not�be�changed�as�far�as�possible.����������The�main�purpose�of�
using�a�standard�business�application�software�like�SAP�is�to�reduced�the�
amount�of�time�and�money�spend�on�developing�and�testing�all�the�programs.�
Therefore,�most�companies�will�try�to�utilized�the�available�tools�provided�by�
SAP.�
What�is�Client?�What�is�the�difference�between�
Customization�and�Configuration?�
The�difference�between�cutomizing�and�configuration�is:�
-�CONFIGURATION:�we�will�configure�the�system�to�meet�the�needs�of�your�
business�by�using�the�existing�data.�
-�CUSTOMIZING:�we�will�customise�or�adapt�the�system�to�your�business�
requirements,�which�is�the�process�of�mapping�SAP�to�your�business�process.�
-�CLIENT:�A�client�is�a�unique�one�in�organizational�structure,�can�have�one�or�
-----------------------�Page�187-----------------------
more�company�codes.�Each�company�code�is�its�own�legal�entity�in�finance.�
Configuration��vs.�Customization�
When�considering�enterprise�software�of�any�type,�it�is�important�to�understand�
the�difference�between�configuration�and�customization.The�crux�of�the�
difference�is�complexity.�Configuration�uses�the�inherent�flexibility�of�the�
enterprise�software�to�add�fields,�change�field�names,modify�drop-down�lists,�or
�
add�buttons.�Configurations�are�made�using�powerful�built-in�tool�sets.�
Customization�involves�code�changes�to�create�functionality�that�is�not�availabl
e�
through�configuration.�Customization�can�be�costly�and�can�complicate�future�
upgrades�to�the�software�because�the�code�changes�may�not�easily�migrate�to�
the�new�version.Wherever�possible,�governments�should�avoid�customization�by�
using�configuration�to�meet�their�goals.Governments�also�should�understand�
their�vendor's�particular�terminology�with�regard�to�this�issue�since�words�like
�
"modifications"�or�"extensions"�often�mean�different�things�to�different�
vendors.�������*--�Sivaprasad,�Sonali�Sardesai�
What�is�SAP�R3?�
We�know�that�SAP�R/3�is�software,�it�particular�it�is�client-server�software.�Th
is�
means�that�the�groups/layers�
that�make�up�a�R/3�System�are�designed�to�run�simultaneously�across�several�
separate�computer�systems.�
When�you�install�Microsoft�Excel�on�your�PC,�each�component�of�Excel�(printing�
components,�graphing�components,�word�processing�components,�and�etc.)�is�
stored,�managed,�and�processed�via�the�hardware�of�your�PC.��������When�a�
company�installs�SAP‟s�software�each�component�(or�"layer”�in�R/3‟s�case)�is��
stored,�managed,�and�processed�via�the�hardware�of�separate�and�specialized�
computer�systems.�Each�of�the�various�layers�is�capable�of�calling�upon�the�
specialty�of�any�of�the�other�installed�layers�in�order�to�complete�a�given�task
.�
Those�components/layers�that�are�requesting�services�are�called�“clients”,�those��
components/layers�that�are�providing�services�are�called�“servers”.��Thus�the�
term�
SD�material�Determination�based�on�
availability�check�
For�SD�material�Determination�you�can�create�a�Substitution�reason�and�
on�the�Strategy�field,�the�following�info.�is�available:�
Product�selection�in�the�background�is�performed�on�the�basis�of�the�
availability�check.�
We�want�to�have�the�material�determination�only�in�case�on�material�
shortage.�We�expect�the�Substitution�reason�to�give�us�this�
functionallity.���It�does�not�hovever�take�the�availabilty�into�account�
before�substitution.�
We�thought�the�worse�case�is�to�create�a�ABAP�which�is�linked�to�the�
"requirement"�field�in�the�Procedure�(OV13).�
Has�anyone�had�the�same�requirement?�Is�this�a�bug�or�just�incorrectly�
documented?�
-----------------------�Page�188-----------------------
I�also�encountered�this�abnormally�recently�using�material�determination.�In�
order�to�combat�the�problem,�the�first�product�substitution�should�be�for�the�
original�material.�I've�illustrated�this�below:�
Original�Product:�ABC�
Substitutes:�DEF,�XYZ�
In�order�to�perform�product�substitution�ONLY�in�the�case�of�ATP�failure�for�
product�ABC,�structure�the�Material�Determination�record�as�follows:�
Material�Entered:�ABC�Substitutes:�ABC�
DEF�
XYZ�
There�seems�to�be�a�devaition�at�availability�check�and�or�on�a�
conceptual�note�still.�
Availability�check�can�be�configured�both�at�requiremnt�class�and�at�the�
schedule�line�categories�level.�
Whilst�the�availabilty�check�at�the�requirement�class�level�via�global�and�
mandatory�configuration�the�schedule�line�catgry�availability�check�deals�with�
the�order.�
It�is�mandatory�that�the�reqmnt�class�is�flagged�off�for�avlblty�check�and�the�
schdelu�line�cat�need�not�be.�
The�following�are�the�mandatory�for�Availability�check�to�happen--�
1.�Must�be�swithced�on�at�the�requirment�class�level�and�at�the�schedule�line�
level.�
2.�Reqmnt�type�must�exist�by�which�a�requiremnt�class�can�be�found�
3.�There�must�exist�a�plant�and�is�defined�
4.Checking�group�must�be�defined�in�Material�Master�records(it�controls�whthr�
the�system�is�to�create�individual�or�collective�reqmnt)�
A�combination�of�checking�gropup�and�checking�rule�will�determine�the�scope�of�
availbaility�check.�
With�Compliment�by:�Srini�
Fast�Links:�
Creating�Multiple�Materials�in�Material�
Determination�
Material�Determination�is�used�to�swap�one�material�for�another.It�is�possible�t
o�
get�a�list�of�materials�for�substituiton,but�remember�you�can�substitue�only�one
�
material�from�the�list.�
This�can�be�done�through�substituiton�reason�T�Code�[OVRQ]�
See�the�substitution�reason�number�for�Manual�Material�Selection�
-�check�the�Entry�box�
-�check�the�Warning�box�
-�select�A�for�Stategy�
-�save.�
Go�To�VB11�to�create�Material�Determination�(taking�into�consideration�that�all�
the�previous�steps�for�material�determiantion�i.e.�maintaining�condition�
types,maintaining�procedures�for�material�determination�and�assigning�
procedures�to�sales�doc.�types�have�been�done)�
-----------------------�Page�189-----------------------
Create�one�material�determination,dont�forget�to�give�the�Subst�reason�on�top�
and�also�on�the�line.�
Click�the�Variants�Icon�on�top�left-Sreen�opens�
Specify�different�materials�you�want�to�swap�with�the�material�you�have�enterd�
Note�that�the�subst�reason�is�already�copied�on�the�screen�
Remember�materials�should�be�of�the�same�sales�area,atleast�Divisions�should�
be�same.�
Backward�and�Forward�Scheduling�
Backward�scheduling�is�the�calculation�of�deadline�dates:�the�arrival�time�at�th
e�
customer�site�is�calculated�as�the�earliest�possible�goods�receipt�time�at�the�
customers�unloading�point�on�the�requested�delivery�date.�All�four�of�the�
delivery�and�transportation�scheduling�lead�times�are�subtracted�from�the�
customer's�requested�delivery�date�to�determine�if�this�date�can�be�met.�
The�transit�time,�loading�time,�and�pick/pack�time�are�subtracted�from�the�
customer‟s�requested�delivery�date�to�calculate�the�required�material�availability
��
date.�
The�system�calculates�backward�scheduling�as�follows:�
Requested�delivery�date�minus�transit�time����=�Goods�issue�date�
Goods�issue�date�minus�loading�time�=�Loading�date�
Loading�date�minus�transportation�lead�time�=�Transportation�scheduling�date�
Loading�date�minus�pick/pack�time�=�Material�availability�date�
By�default,�the�system�will�calculate�delivery�dates�the�closest�day,�taking�int
o�
consideration�the�working�days�of�the�shipping�point�and�a�rounding�profile.�In�
this�case�the�system�assumes�a�24�hour�work�day�and�lead�times�can�be�
entered�in�days�up�to�2�decimal�points.��This�is�referred�to�as�daily�scheduling
.�
Precise�scheduling�calculated�down�to�the�day,�hour�and�minute�is�supported.�
This�allows�the�scheduling�of�a�delivery�within�a�single�day.��It�is�activated�b
y�
maintaining�the�working�hours�for�a�particular�shipping�point.�
Backward�scheduling�is�always�carried�out�first.��If�the�material�availability�d
ate�
or�transportation�scheduling�date�is�calculated�to�be�in�the�past,�the�system�
must�then�use�forward�scheduling.�
Forward�scheduling�is�also�done�if�no�product�is�available�on�the�material�
availability�date�calculated�by�backward�scheduling.�The�system�does�an�
availability�check�to�determine�the�first�possible�date�when�product�will�be�
available.�This�new�material�availability�date�forms�the�starting�point�for�
scheduling�the�remaining�activities.��The�loading�time,�pick/pack�time,�transit�
time,�and�transportation�lead�time�are�added�to�the�new�material�availability�
date�to�calculate�the�confirmed�delivery�date.�
*--�Manoj�Mahajan�
Settlement�Downpayment�with�Installment�
payment�Term�
-----------------------�Page�190-----------------------
Scenario�:-�Problem�with�Down�payment�settlement�using�installment�payment�
term.�
1.��When�we�create�Sales�order,�(sales�item�value�=�100)�use�payment�term�:�
����0009�(Installment�Payment�term,�30%,�40%,�30%).�In�the�Billing�Plan,�I�
specify�2�records,�1st�record�is�
����Downpayment�����request�30%�of�Order�value,�billing�type�is�FAZ�.�the�2nd�
record�is�Final�invoice�100%,�billing�
����type�is�F2.�
2.�Create�Billing�type�Down�payment�request�,�it�will�document�as�Noted�item�in�
the�accounting�document.�
3.�Receive�Downpayment�from�customer�via�FI�screen�,�at�this�stage�the�
asccounting�document�is�created�as�following�
�����Dr.�Cash/Bank�30�
�������Cr.�Advance�from�customer�30�
4.�When�I�create�Billing�document�for�the�sales�item,�the�down�payment�value�
will�be�proposed�for�settlement�at�Billing�
���Creation,�I�then�accept�the�default�value�of�down�payment�clearing.��The�
accounting�document�is�as�below�
����Dr.�AR�30��(*split�AR�by�installment�payment�term)�
��������AR�40�
��������AR�30�
�������Cr.�Sales�100�
�����Dr.��Advance�from�customer�30�
�������Cr.�AR�9��(DP.�30%�*�30)�
�������Cr��AR�12��(DP.�30%�*�40)�
�������Cr��AR�9��(DP.�30%�*�30)�
It�seems�SAP�settlement�Down�payment�by�Installment�Payment�term.�����������I�wa
s�
wondering�that�is�there�are�alternative�or�an�option��to�setup�the�Down�payment�
settlement�independent�of�Installment�term.�I�meant,�I�don't�want�to�have�the�
last�3�Credit�item�as�above,�I�want�only�1�line�item�of�credit,��the�accounting�
should�be�
����Dr.�AR�30��(*split�AR�by�installment�payment�term)�
��������AR�40�
��������AR�30�
�������Cr.�Sales�100�
����Dr.��Advance�from�customer�30�
�������Cr.�AR�30�(Not�separate�by�Installment�payment�term)�
Solutions�:�Suggesstions�on�how�I�could�proceed?�
Your�problem�with�Down�payment�settlement�is�common.�Many�users�object�to�
the�down�payment�or�security�lodgement�mechanism.�In�our�case�we�often�park�
and�apply�the�advance�manually�to�final�invoice.�
However,�following�the�above�case�we�sometimes�use�this�with�our�PS�orders:�
1.�Create�Sales�order,�(sales�item�value�=�100)�with�billing�plan�with�three�ste
ps�
30%�down�payment,30%�std�billiing�on�
���order�completion�and�70%�on�delivery.�A�little�different�to�your�original�
Billing�Plan,�but�1st�record�is�Downpayment�
-----------------------�Page�191-----------------------
���request�30%�of�Order�value,�billing�type�is�FAZ�.�the�2nd�&�3rd�records�are�
std�F2�invoices�30%�,70%.�
2.�Create�Billing�type�Down�payment�request�,�it�will�document�as�Noted�item�in�
the�accounting�document.�
3.�Receive�Downpayment�from�customer�via�FI�screen�,�at�this�stage�the�
accounting�document�is�created�as�following�:-�
���Dr.�Cash/Bank�30�
�����Cr.�Security�deposit�payment�30�(�In�many�countries�this�may�be�subject�
to�TAX�laws)�
4.�Create�the�First�Billing�documents�,�the�down�payment�value�will�be�proposed�
for�settlement�at�Billing�Creation,�then�
���accept�the�default�value�of�down�payment�clearing�as�these�equal�each�
other.��The�accounting�document�is�as�below�
���Dr.�AR�30�
������Cr.�Sales�30�
���Dr.��Advance�from�customer�30�
������Cr.�AR�30�
5.�Create�the�Second�Billing�document�(�down�payment�value�has�expired�and�
will�not�be�proposed)�The�accounting�
���document�is�as�below�is�then�standard�for�the�last�installement.�
����Dr.�AR�60�
������Cr.�Sales�60�
This�alternative�provides�a�cleaner�option�with�the�Downpayment.�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
http://www.sap-img.com�
Sales�and�Distribution�-�Upload�Condition�
Pricing�
RV14BTCI�-�Batch�Input�for�Uploading�Condition�Pricing�
After�executing�the�program,�you�have�to�use�SM35�to�process�the�update�
program.�
Envirionment�:�4.6x�
Require�flat�file�:-�
ROW�1�BGR00�
ROW�2�BKOND1�
ROW�3�BKOND2�-�no�scale�
ROW�4�BKOND2�-�no�scale�
ROW�5�BKOND3�-�with�scale�
ROW�6�BKOND2�-�no�scale�
Sample�flat�file�for�uploading�table�A305�-�Customer/Material�with�release�statu
s�
:-�
-----------------------�Page�192-----------------------
0BIPRICE�����123SAPABAP�������������X�
1VK15������������A305V�PR00�
2ALL�
990000123456SAP8204142100�
2002043020020401�������������50USD����100PC�
2ALL�
990000123456SAP8217168100�
2002043020020401�������������50USD����100PC�
3�����������100PC�����������2�
3�����������200PC�����������1�
2ALL�990000123456SAP8220133910�
There�a�total�of�4�flat�file�format�:-�
BGR00�-�Session�Header�Record�
-----------------------------------------------------------------------------�
-------------�
|�Field�name�|�Description�����������|�Report�header��������|�Cat.������|�
Length�|�Dec.����|�
-----------------------------------------------------------------------------�
-------------�
|�STYPE�������|�Record�type����������|�0��������������������|�CHAR������|�
000001�|�000000�|�
|�GROUP�������|�Group�name�����������|�BI�Session�Name������|�CHAR������|�
000012�|�000000�|�
|�MANDT�������|�Client���������������|�Your�client�no�������|�CLNT������|�
000003�|�000000�|�
|�USNAM�������|�User�ID��������������|�Queue�user�ID��������|�CHAR������|�
000012�|�000000�|�
|�START�������|�Lock�until:����������|�Queue�start�date�����|�DATS������|�
000010�|�000000�|�
|�XKEEP�������|�Keep�indicator�������|�X�-�don't�delete�SESS|�CHAR������|�
000001�|�000000�|�
|�NODATA������|�No�batch�input�������|�/��������������������|�CHAR������|�
000001�|�000000�|�
-----------------------------------------------------------------------------�
-------------�
BKOND1�-�Header�Record�
-----------------------�Page�193-----------------------
-----------------------------------------------------------------------------�
-------------�
|�Field�name�|�Description�����������|�Report�header��������|�Cat.������|�
Length�|�Dec.����|�
-----------------------------------------------------------------------------�
-------------�
|�STYPE�������|�Record�type����������|�1��������������������|�CHAR������|�
000001�|�000000�|�
|�TCODE�������|�Transaction�code�����|�TCode�=�VK15���������|�CHAR������|�
000020�|�000000�|�
|�KVEWE�������|�Usage����������������|�U��������������������|�CHAR������|�
000001�|�000000�|�
|�KOTABNR�����|�Table����������������|�Table�e.g.�305�������|�CHAR������|�
000003�|�000000�|�
|�KAPPL�������|�Application����������|�App��e.g�V�����������|�CHAR������|�
000002�|�000000�|�
|�KSCHL�������|�Condition�type�������|�CTyp�e.g�PR00��������|�CHAR������|�
000004�|�000000�|�
-----------------------------------------------------------------------------�
-------------�
BKOND2�-�Main�Data�Record�
-----------------------------------------------------------------------------�
-------------�
|�Field�name�|�Description�����������|�Report�header��������|�Cat.������|�
Length�|�Dec.����|�
-----------------------------------------------------------------------------�
-------------�
|�STYPE�������|�Record�type����������|�2��������������������|�CHAR������|�
000001�|�000000�|�
|�VAKEY�������|�VarKey���������������|�VarKey���������������|�CHAR������|�
000100�|�000000�|�
-----------------------�Page�194-----------------------
|�DATBI�������|�Valid�to�������������|�Valid�to�������������|�DATS������|�
000010�|�000000�|�
|�DATAB�������|�Valid�on�������������|�Valid�on�������������|�DATS������|�
000010�|�000000�|�
|�KBETR�������|�Amount���������������|�Amount���������������|�CHAR������|�
000015�|�000000�|�
|�KONWA�������|�R/2�table������������|�R2tab����������������|�CHAR������|�
000005�|�000000�|�
|�KPEIN�������|�R/2�table������������|�R2tab����������������|�CHAR������|�
000005�|�000000�|�
|�KMEIN�������|����������������������|����������������������|�CHAR������|�
000003�|�000000�|�
|�MWSK1�������|�Tax�code�������������|�Tx�������������������|�CHAR������|�
000002�|�000000�|�
|�KONMS�������|�Scale�UoM������������|�UoM������������������|�UNIT������|�
000003�|�000000�|�
|�MXWRT�������|�Amount���������������|�Amount���������������|�CHAR������|�
000015�|�000000�|�
|�GKWRT�������|�Amount���������������|�Amount���������������|�CHAR������|�
000015�|�000000�|�
|�STFKZ�������|�Scale�type�����������|�S��������������������|�CHAR������|�
000001�|�000000�|�
|�KZNEP�������|�Exclusion������������|�CndEx����������������|�CHAR������|�
000001�|�000000�|�
|�LOEVM_KO����|�Deletion�indic.������|�D��������������������|�CHAR������|�
000001�|�000000�|�
|�SKONWA������|�R/2�table������������|�R2tab����������������|�CHAR������|�
000005�|�000000�|�
-----------------------------------------------------------------------------�
-------------�
BKOND3�-�Scale�Data�Record�
-----------------------------------------------------------------------------�
-------------�
|�Field�name�|�Description�����������|�Report�header��������|�Cat.������|�
Length�|�Dec.����|�
-----------------------�Page�195-----------------------
-----------------------------------------------------------------------------�
-------------�
|�STYPE�������|�Record�type����������|�3��������������������|�CHAR������|�
000001�|�000000�|�
|�KSTBM�������|�Quantity�������������|�Quantity�������������|�CHAR������|�
000018�|�000000�|�
|�KONMS�������|�Scale�UoM������������|�UoM������������������|�UNIT������|�
000003�|�000000�|�
|�KBETR�������|�Amount���������������|�Amount���������������|�CHAR������|�
000015�|�000000�|�
-----------------------------------------------------------------------------�
-------------�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
http://www.sap-img.com�
Sales�Order�Changed�History�Display�
*�
*�Sales�Order�Changed�History�Display�
*�
*�You�can�execute�the�report�by�:�
*�1.��Change�Date�
*�2.��User�Name�
*�3.��Sales�Order�Number�
*�
*�Submitted�by�:�SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
*����������������http://www.sap-img.com�
*�
REPORT�ZSDCHANGE�LINE-SIZE�132�NO�STANDARD�PAGE�HEADING�
�����������������LINE-COUNT�065(001)�
�����������������MESSAGE-ID�VR.�
TABLES:�DD04T,�
��������CDHDR,�
��������CDPOS,�
��������DD03L,�
��������DD41V,�
��������T685T,�
��������VBPA,�
��������TPART,�
��������KONVC,�
��������VBUK.�
DATA:�BEGIN�OF�ICDHDR�OCCURS�50.�
-----------------------�Page�196-----------------------
����������INCLUDE�STRUCTURE�CDHDR.�
DATA:�END�OF�ICDHDR.�
SELECT-OPTIONS:�XUDATE�FOR�ICDHDR-UDATE,�
��������������������XNAME���FOR�ICDHDR-USERNAME,�
��������������������XVBELN�FOR�VBUK-VBELN.�
SELECTION-SCREEN�SKIP.�
SELECTION-SCREEN�BEGIN�OF�BLOCK�BLK1�WITH�FRAME�TITLE�TEXT-001.�
PARAMETERS:�SUDATE�RADIOBUTTON�GROUP�R1,�
���������������SNAME��RADIOBUTTON�GROUP�R1,�
���������������SOBID��RADIOBUTTON�GROUP�R1.�
SELECTION-SCREEN�END�OF�BLOCK�BLK1.�
DATA:�WFLAG,�
�������WCHANGENR�LIKE�CDHDR-CHANGENR,�
�������WUDATE�LIKE�CDHDR-UDATE,�
�������WNAME����LIKE�CDHDR-USERNAME,�
�������WVBELN�LIKE�VBUK-VBELN,�
�������WDEC1�TYPE�P�DECIMALS�3,�
�������WDEC2�TYPE�P�DECIMALS�3,�
�������WDEC3�TYPE�P�DECIMALS�3,�
�������WDEC4�TYPE�P�DECIMALS�3.�
DATA:�UTEXT(16)�VALUE�'has�been�changed',�
�������ITEXT(16)�VALUE�'has�been�created',�
�������DTEXT(16)�VALUE�'has�been�deleted'.�
DATA:�BEGIN�OF�ICDSHW�OCCURS�50.�
����������INCLUDE�STRUCTURE�CDSHW.�
DATA:�END�OF�ICDSHW.�
DATA:�BEGIN�OF�ITAB�OCCURS�10.�
����������INCLUDE�STRUCTURE�CDSHW.�
DATA:�����UDATE�LIKE�CDHDR-UDATE,�
����������USERNAME�LIKE�CDHDR-USERNAME,�
����������CHANGENR�LIKE�CDHDR-CHANGENR,�
����������VBELN(10),�
����������POSNR(6),�
����������ETENR(4),�
����������INDTEXT(200),�
��END�OF�ITAB.�
SELECT�*�FROM�VBUK�WHERE�VBELN�IN�XVBELN.�
��CLEAR�CDHDR.�
��CLEAR�CDPOS.�
��CDHDR-OBJECTCLAS�=�'VERKBELEG'.�
��CDHDR-OBJECTID�������=�VBUK-VBELN.�
��PERFORM�READHEADER.�
��PERFORM�READPOS.�
��LOOP�AT�ITAB.�
�����CASE�ITAB-TABNAME.�
�������WHEN�'VBPA'.�
����������IF�ITAB-FNAME�=�'KUNNR'�OR�
��������������ITAB-FNAME�=�'LIFNR'�OR�
��������������ITAB-FNAME�=�'PARNR'�OR�
��������������ITAB-FNAME�=�'PERNR'�OR�
-----------------------�Page�197-----------------------
��������������ITAB-FNAME�IS�INITIAL.�
������������MOVE�ITAB-TABKEY�TO�VBPA.�
������������SELECT�SINGLE�*�FROM�TPART�WHERE�SPRAS�=�SY-LANGU�
���������������������������������������������AND�����PARVW�=�VBPA-PARVW.�
������������IF�SY-SUBRC�=�0.�
��������������REPLACE�'&'�WITH�TPART-VTEXT�INTO�ITAB-INDTEXT.�
������������ENDIF.�
���������ENDIF.�
������WHEN�'VBAP'.�
���������IF�ITAB-FNAME�IS�INITIAL.�
������������REPLACE�'&'�WITH�'Item'�INTO�ITAB-INDTEXT.�
���������ENDIF.�
������WHEN�'KONVC'.�
���������MOVE�ITAB-TABKEY�TO�KONVC.�
���������SELECT�SINGLE�*�FROM�T685T�WHERE�SPRAS�=�SY-LANGU�
�������������������������������������������AND�����KVEWE�=�'A'�
�������������������������������������������AND�����KAPPL�=�'V'�
�������������������������������������������AND�����KSCHL�=�KONVC-KSCHL.�
���������IF�SY-SUBRC�=�0.�
������������REPLACE�'&'�WITH�T685T-VTEXT�INTO�ITAB-INDTEXT.�
���������ENDIF.�
������ENDCASE.�
�������IF�ITAB-INDTEXT(1)�EQ�'&'.�
���������REPLACE�'&'�WITH�ITAB-FTEXT(40)�INTO�ITAB-INDTEXT.�
������ENDIF.�
�������IF�ITAB-CHNGIND�=�'I'.�
���������REPLACE�'%'�WITH�ITEXT�INTO�ITAB-INDTEXT.�
������ELSEIF�ITAB-CHNGIND�=�'U'.�
���������REPLACE�'%'�WITH�UTEXT�INTO�ITAB-INDTEXT.�
������ELSE.�
���������REPLACE�'%'�WITH�DTEXT�INTO�ITAB-INDTEXT.�
������ENDIF.�
�������CONDENSE�ITAB-INDTEXT.�
������MODIFY�ITAB.�
����ENDLOOP.�
ENDSELECT.�
IF�SUDATE�=�'X'.�
���SORT�ITAB�BY�UDATE�VBELN�POSNR�ETENR.�
ELSEIF�SOBID�=�'X'.�
���SORT�ITAB�BY�VBELN�POSNR�ETENR�UDATE.�
ELSE.�
���SORT�ITAB�BY�USERNAME�VBELN�POSNR�ETENR�UDATE.�
ENDIF.�
LOOP�AT�ITAB.�
���CLEAR�WFLAG.�
���IF�SUDATE�=�'X'.�
�����IF�WUDATE�NE�ITAB-UDATE.�
��������SKIP.�
��������WRITE:/001�ITAB-UDATE,�
�����������������023�ITAB-USERNAME,�
�����������������037(10)�ITAB-VBELN.�
��������WFLAG�=�'X'.�
��������WUDATE�=�ITAB-UDATE.�
��������WCHANGENR�=�ITAB-CHANGENR.�
�����ENDIF.�
-----------------------�Page�198-----------------------
���ELSEIF�SOBID�NE�'X'.�
�������IF�WVBELN�NE�ITAB-VBELN.�
����������SKIP.�
����������WRITE:/001�ITAB-VBELN.�
����������WVBELN�=�ITAB-VBELN.�
������ENDIF.�
���ELSE.�
�������IF�WNAME�NE�ITAB-USERNAME.�
����������SKIP.�
����������WRITE:/001�ITAB-USERNAME.�
����������WNAME�=�ITAB-USERNAME.�
������ENDIF.�
���ENDIF.�
���IF�WCHANGENR�NE�ITAB-CHANGENR.�
������WRITE:/023�ITAB-USERNAME,�
������������������037(10)�ITAB-VBELN.�
�����������WFLAG�=�'X'.�
�����������WCHANGENR�=�ITAB-CHANGENR.�
������ENDIF.�
�������IF�WFLAG�=�'X'.�
����������WRITE:�013�ITAB-CHNGIND,�
���������������������049�ITAB-POSNR,�
���������������������057�ITAB-ETENR,�
���������������������065�ITAB-INDTEXT(60).�
������ELSE.�
����������WRITE:�/013�ITAB-CHNGIND,�
�����������������������049�ITAB-POSNR,�
�����������������������057�ITAB-ETENR,�
�����������������������065�ITAB-INDTEXT(60).�
������ENDIF.�
���WRITE:/065�ITAB-F_OLD.�
���WRITE:/065�ITAB-F_NEW.�
ENDLOOP.�
FORM�READHEADER.�
���CALL�FUNCTION�'CHANGEDOCUMENT_READ_HEADERS'�
�����������EXPORTING�
��������������������DATE_OF_CHANGE���������������=�CDHDR-UDATE�
��������������������OBJECTCLASS������������������=�CDHDR-OBJECTCLAS�
��������������������OBJECTID���������������������=�CDHDR-OBJECTID�
��������������������TIME_OF_CHANGE���������������=�CDHDR-UTIME�
�������������������USERNAME����������������������=�CDHDR-USERNAME�
�����������TABLES�
��������������������I_CDHDR����������������������=�ICDHDR�
�����������EXCEPTIONS�
�������������������NO_POSITION_FOUND�=�1�
��������������������OTHERS�����������������������=�2.�
���CASE�SY-SUBRC.�
������WHEN�'0000'.�
������WHEN�'0001'.�
����������MESSAGE�S311.�
����������LEAVE.�
������WHEN�'0002'.�
����������MESSAGE�S311.�
����������LEAVE.�
���ENDCASE.�
-----------------------�Page�199-----------------------
ENDFORM.�
FORM�READPOS.�
���LOOP�AT�ICDHDR.�
������CHECK�ICDHDR-UDATE�
�����������������������������������IN�XUDATE.�
������CHECK�ICDHDR-USERNAME�
��������������������������������������IN�XNAME.�
������CALL�FUNCTION�'CHANGEDOCUMENT_READ_POSITIONS'�
�������������EXPORTING�
��������������������CHANGENUMBER��������������=�ICDHDR-CHANGENR�
��������������������TABLEKEY������������������=�CDPOS-TABKEY�
��������������������TABLENAME�����������������=�CDPOS-TABNAME�
�������������IMPORTING�
��������������������HEADER��������������������=�CDHDR�
�������������TABLES�
��������������������EDITPOS�������������������=�ICDSHW�
�������������EXCEPTIONS�
��������������������NO_POSITION_FOUND�=�1�
��������������������OTHERS��������������������=�2.�
������CASE�SY-SUBRC.�
���������WHEN�'0000'.�
������������LOOP�AT�ICDSHW.�
���������������CHECK�ICDSHW-CHNGIND�NE�'E'.�
���������������CLEAR�ITAB.�
��������������MOVE-CORRESPONDING�ICDHDR�TO�ITAB.�
��������������MOVE-CORRESPONDING�ICDSHW�TO�ITAB.�
���������������CASE�ITAB-TABNAME.�
�����������������WHEN�'KONVC'.�
��������������������MOVE�ICDHDR-OBJECTID�TO�ITAB-VBELN.�
��������������������MOVE�ICDSHW-TABKEY(6)�TO�ITAB-POSNR.�
�����������������WHEN�OTHERS.�
��������������������MOVE�ICDSHW-TABKEY+3(10)��������������TO�ITAB-VBELN.�
��������������������MOVE�ICDSHW-TABKEY+13(6)��������������TO�ITAB-POSNR.�
��������������������MOVE�ICDSHW-TABKEY+19(4)��������������TO�ITAB-ETENR.�
��������������ENDCASE.�
��������������MOVE�'&�%'�TO�ITAB-INDTEXT.�
��������������APPEND�ITAB.�
���������������CLEAR�ITAB.�
������������ENDLOOP.�
���������WHEN�OTHERS.�
������������MESSAGE�S311.�
������������LEAVE.�
������ENDCASE.�
���ENDLOOP.�
ENDFORM.�
TOP-OF-PAGE.�
WRITE:/�SY-DATUM,SY-UZEIT,�
����������50�'SALES�ORDER�CHANGE�HISTORY',�
���������120�'Page',�SY-PAGNO.�
WRITE:�/�SY-REPID,�
�������������60�'SALES�ORDERS�STATISTICS'.�
SKIP.�
ULINE.�
IF�SUDATE�=�'X'.�
-----------------------�Page�200-----------------------
��WRITE:/001�'Change�Date',�
�����������013�'Time',�
�����������023�'User�Name',�
�����������037�'Sale�Order',�
�����������049�'Line',�
�����������057�'Sch�No',�
�����������065�'Changes'.�
ELSEIF�SOBID�=�'X'.�
��WRITE:/001�'Sale�Order',�
�����������013�'Line',�
�����������021�'Sch�No',�
�����������029�'Change�Date',�
�����������041�'Time',�
�����������051�'User�Name',�
�����������065�'Comment'.�
ELSE.�
��WRITE:/001�'User�Name',�
�����������015�'Time',�
�����������025�'Change�Date',�
�����������037�'Sale�Order',�
�����������049�'Line',�
�����������057�'Sch�No',�
�����������065�'Changes'.�
ENDIF.�
ULINE.�
*---�End�of�Program�
�All�the�site�contents�are�Copyright�©�www.sap-img.com�and�the�content�authors.�Al
l�rights�
������������������������������������������reserved.�
����All�product�names�are�trademarks�of�their�respective�companies.�����The�site
�www.sap-�
������������������������img.com�is�in�no�way�affiliated�with�SAP�AG.�
Every�effort�is�made�to�ensure�the�content�integrity.��Information�used�on�this�
site�is�at�your�
������������������������������������������own�risk.�
�The�content�on�this�site�may�not�be�reproduced�or�redistributed�without�the�exp
ress�written�
����������������������������������������permission�of�
��������������������������www.sap-img.com�or�the�content�authors.�
Difference�between�Condition�Type�
Please�explain�the�difference�between�Ek01�(�Actual�Cost)�and�EK02�
Calculated�Cost.�
These�are�the�condition�type�that�will�display�the�results�of�the�unit�costing�f
or�
certain��type�of�sales�document.�
EK01�:�
If�you�use�this�condition�type,�the�result�of�unit�costing�is�issued�to�the�firs
t�
position�on�the�conditions�screen�for�the�item.�The�value�can�be�used�as�a�basis
�
for�price�determination.�
EK02:�
If�you�use�this�condition�type,�the�result�of�unit�costing�is�simply�a�statistic
al�
-----------------------�Page�201-----------------------
value�which�you�can�compare�with�the�price.�
Please�note�the�following�points������:�
1)�The�condition�type�must�have�condition�category�'Q'�(costing).�
2)�The�condition�type�must�agree�with�the�condition�type�defined�for�unit�
costing�in�the�pricing�procedure.�
I�have�a�customer�who�is�being�offered�two�discounts�ie�k007�and�k005,�
now�I�want�to�exclude�k007�for�the�next�2�
orders�or�so?�I�have�set�the�exclusion�indicator�for�the�condition�
type,but�still�the�condition�is�being�accepted�when�I�create�a�sales�
order.��Am�I�missing�something,�how�do�I�do�it?�
I�think�u�need�to�change�the�validity�of�the�condition�record�for�the�condition�
type�K007�defining�it�not�valid�for�that�particular�2�months.��And�also�the�
settings�of�the�Requirements�as�it�is�correct�that�it�overrules�the�exclusion.�
Arvind�Rana�
Related�SD�Queries:�
�������SD�Questions�About�Pricing�Condition��������Add�a�Field�To�New�Condition�Table�in�Pricing�Get�help�for�your�SAP�SD�problems�
SAP�SD�Forums�-�Do�you�have�a�SAP�SD�Question?�
SAP�Sales�and�Distribution�Books�
SAP�SD�Books�-�Certification,�Interview�Questions�and�Configuration�
SAP�Sales�and�Distribution�Tips�
SAP�SD�Discussion�Forum�and�Sales/Distribution�Tips�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
http://www.sap-img.com�
�All�the�site�contents�are�Copyright�©�www.sap-img.com�and�the�content�authors.�Al
l�rights�
�����������������������������������������reserved.�
����All�product�names�are�trademarks�of�their�respective�companies.���The�site�w
ww.sap-�
�����������������������img.com�is�in�no�way�affiliated�with�SAP�AG.�
Every�effort�is�made�to�ensure�the�content�integrity.��Information�used�on�this�
site�is�at�your�
�����������������������������������������own�risk.�
�The�content�on�this�site�may�not�be�reproduced�or�redistributed�without�the�exp
ress�written�
���������������������������������������permission�of�
�������������������������www.sap-img.com�or�the�content�authors.�
Creating�New�Pricing�Procedure�
What�is�the�transaction�code�for�creating�new�pricing�procedure�and�
how�to�attach�it�to�specific�plant?�
-----------------------�Page�202-----------------------
You�create�PP�in�spro�>�Sales�and�Distribution�>�Basic�Functions�>�Pricing�>�
Pricing�Control�>�Define�and�Assign�Pricing�Procedures�>�Maintain�Pricing�
Procedures�
You�can't�attach�PP�to�specific�plant.�Pricing�Procedure�is�determined�thru�trx�
OVKK.�The�defining�parameters�for�pricing�procedure�determination�are:�
1.�SalesOrg�
2.�Distribution�Channel�
3.�Division�
4.�Document�Procedure�(defined�in�Sales�doc\Billing�doc�maintenance)�
5.�Pricing�procedure�assigned�to�customer�(defined�in�customer�master)�
Hope�this�helps.�
Sabir�
Reg�pricing�procedure.�
1.�Use�transaction�code�v/07�to�create�a�access�sequence�and�assign�tables�
based�on�which�you�want�to�carry�on�
���pricing�as�accesses.�
2.�Use�transaction�code�v/06�to�define�condition�type.�It�can�be�for�base�price,
�
discount,�freight�etc.,�
���(Do�assign�relevant�access�sequence)�
3.�Use�transaction�code�v/08�to�define�pricing�procedure.�
4.�Assign�this�to�your�relevant�sales�area+�dpp+cupp.�
While�specifying�requirement,�we�can�give�reqt�no.22�which�specifies�that�plant�
has�to�be�set.��This�is�generally�done�for�output�taxes�since�output�taxes�depen
d�
upon�the�delivering�plant.���But�directly�there�is�no�assignment�between�plant�
and�pricing�procedure.�
Hope�this�helps,�
Re-pricing�in�a�Quotation�
How�can�I,�or�am�I�able�to�find�anything�on�a�way�of�RE-Pricing�be�done�
in�a�QUOTATION?�
You�can�always�'Update"�pricing�manually�in�a�quotation�the�same�way�you�do�
in�a�sales�order,�either�in�create�or�change�modes.�Menu�path�Edit�-->�New�
Pricing�or�press�the�'Update�pricing'�button�on�the�item�conditions�tab.�
If�you�are�asking�how�to�reprice�a�quotation�when�it�converts�into�a�sales�order
,�
that�can�be�done�with�the�copy�controls�of�the�Item�Category.�IMG:�Sales�&�Dist�
-->�Sales�-->�-->�Maintain�Copy�Control�for�Sales�Docs�-->�Sales�Doc�to�Sales�
Doc�(transaction�vtaa).�Just�choose�the�combination�of�documents�and�the�
respective�item�category.�The�field�you�need�to�be�concerned�with�is�"Pricing�
type".�
However,�from�a�business�process�perspective�it�makes�absolutely�NO�sense�to�
reprice�a�quotation�when�converting�to�a�sales�order.�After�all,�the�entire�poin
t�
-----------------------�Page�203-----------------------
of�using�quotations�is�to�firm�up�details�like�pricing�before�creating�the�sales
�
order.�
Do�you�have�a�SAP�SD�Question?�
SAP�Sales�and�Distribution�Reference�Books�
Quantity�Based�Discounts�in�Bulk�Quantities�
Sales�
You're�looking�to�implement�quantity�based�discounts�in�4.6c.�You�are�
trying�to�sell�items�in�specific�bulk�quantities,�and�only�give�the�
discount�for�specific�quantity�intervals.�
For�example,�if�a�customer�orders�1�piece,�2�pieces,�3,�etc.�of�part�ABC,�
the�price�is�$100.�
If�the�customer�orders�10�pieces�of�part�ABC,�the�price�is�$50.�
However,�this�is�not�only�a�standard�minimum�quantity�discount.�If�the�
customer�tries�to�order�11�pieces,�12,�13,�etc.�it�should�return�$100�
again.�
The�only�values�for�which�$50�should�apply�are�10,�20,�30,�etc.�-�
multiples�of�the�bulk�quantity�10.�
You�have�discussed�changing�your�part�number�to�reflect�a�bulk�qty�of�
10,�however�you�have�in�house�consumption�that�is�allowed�to�consume�
only�1�part�at�a�time.�You�would�vastly�prefer�to�keep�one�part�number�
that�you�order�from�the�supplier,�consume�internally�and�ship�
externally.�
You�are�fairly�certain�there�is�basic�functionality�that�covers�this,�but�
you're�just�not�sure�where�to�start.�
Taking�your�requirements�literally.�Standard�SAP�scale�pricing�will�not�do�it�in
�
that�you�only�want�the�reduced�price�to�come�into�effect�when�the�order�
quantity�is�multiple�of�some�bulk�factor.�
It�is�agreed�with�that�creating�a�separate�material�number�is�not�a�good�idea.�
You�can�try�this�:-�
Determine�Sales�Price�with�Shipping�Point�
You�are�trying�to�use�shipping�point�as�a�key�field�(with�sales�org.�
distribution�channel�and�ship-to�party�together)�to�determine�the�sales�
price.���You�created�a�condition�table�with�the�above�key�fields,�and�
maintained�the�relevant�setting�(access�sequence,�condition�type�and�
pricing�procedure).�
There�is�an�error�message�in�the�sales�order�pricing�analysis�("access�
not�made"�in�the�shipping�point�field).�
-----------------------�Page�204-----------------------
In�the�access�sequence,�you�found�that�the�shipping�point�field's�
document�structure�is�KOMK.�
Can�you�put�to�item�level�field�in�the�condition�table�and�access�
sequence?�
Structure�KOMK�refers�to�header�of�the�sales�order,�but�shipping�point�of�
course�is�on�item�level.�
You'll�have�to�do�some�settings�to�reach�your�goal,�it�is�possible.�
Step�1�
Append�structure�KOMP.�Do�this�by�changing�through�SE11�the�
table�KOMPAZ.�
This�is�the�include�for�structure�KOMP.�
Add�a�component�e.g.�ZZVSTEL�with�component�type�VSTEL.�
Save,�activate.�
If�you�want�to�make�more�points,�assign�search�help�H_TVST�to�the�
component.�
Ask�a�programmer�if�you�don't�understand�this�part.�
Step�2�
Change�user�exit�MV45AFZZ.�Say�there�that�field�ZVSTEL�should�be�filled�with�
information�from�your�shipping�point.�
Do�this�under�part�FORM�USEREXIT_PRICING_PREPARE_TKOMP.�
The�coding�should�be�like�tkomp-zzvstel�=�vbap-vstel.�
Save,�generate.�
Step�3�
Make�a�new�table�as�you�did�before,�but�first�maintain�your�new�field�in�
Condition:�allowed�fields.�
When�you�create�your�new�table�you�will�see�you�have�two�shipping�points.�
With�the�button�technical�view�you�can�check�which�one�ZZVSTEL�or�VSTEL.�
Step�4�
Finish�with�the�steps�you�did�before.�That�was�ok.�
Now,�you�will�see�in�your�sales�order�that�the�shipping�point�is�filled�with�
information.�
Pricing�date�based�on�delivery�date�
Used�transaction�VOV8.�
This�configuration�is�by�order�type.�
There�is�a�field�called�proposal�for�pricing�date.�
There�you�can�select�pricing�date�as�requested�delivery�date.�
A�-�Proposed�pricing�date�based�on�the�requested�dlv.date�(Header)�
This�control�is�set�at�the�document�level�as�oppose�to�the�condition�type�level�
(PR00).�
-----------------------�Page�205-----------------------
That�means�your�other�condition�types�such�as�surcharges�and�discounts�are�
also�determined�using�the�requested�delivery�date.�
If�your�requirement�is�for�PR00�to�alone�to�be�priced�at�delivery�date�then�this
�
will�not�work.�
How�pricing�date�is�determine�in�the�sales�
order�and�billing�document?�Where�is�the�
setting?�
The�pricing�date�is�proposed�based�on�the�setting�you�make�in�the�Sales�
document�configuration.�(�T�code�:�VOV8)�
You�have�a�field"�Prop.f.pricing�date�"�in�the�Requested�delivery�date�/�������p
ricing�
date�/��purchase�order�date��segment.�
Then�you�can�choose�the�follwoing�options:�
Blank�-�Indicates�the�current�date�as�the�pricing�date�
A�-��Indicates�the�date�based�on�the�requested�delivery�date�
B�-�Indicates�the�date�based�on�the�order�validity�start�from�date�
And�the�pricing�in�the�billing�document�is�copied�from�thte�sales�order�/�Delive
ry�
document..�
It�again�depends�on�the�setting�u�have�in�the�copy�control�from�order�-�billng�o
r�
delivery�-�billing.�
In�the�copy�control,�in�the�item�settings�you�have�two�fields�relavant�for�this.
�
One�is�pricing�source�and�the�other�is�pricing�type.�
The�pricing�sources�are�generally�the�order.������But�if�you�want�you�can�change
�it�
to�other�values�mentioned�in�the�drop�down,�
but�this�values�have�no�effect�if�the�pricing�type�is�B.�
Any�other�value�other�than�B�in�the�pricing�type�will�take�the�reference�
document�price�mentioned�in�the�pricing�source�field.�
but�for�the�pricing�type�B.��The�new�price�is�determined�in�the�billing�order.�
SAP�Tips�by:�Sreenivas�
Report�to�Check�the�Entered�Pricing�Condition�
Price�
Which�is�the�best�transaction�code�to�check�the�Pricing�condition�price�
entered�in�"VK11"?�
Other�than�"VK13",�to�display�the�price,�you�can�use�V/LD�-�Execute�Pricing�
-----------------------�Page�206-----------------------
Report�to�check�the�prices�entered�into�the�Pricing�Master.�
Normally�Pricing�Report�-�"07�Cust.-specific�Prices�with�Scale�Display"�will�do.
�
Other�Pricing�Reports�you�can�tried�are�these:�
---------------------------------------------------------------------------�
|LR|Report�title���������������������������������������������������������������|
�
--�------------------------------------------------------------------------�
|01|Comparison�of�Price�Lists�Without�Scale�Display����������������������������|
�
|02|Comparison�of�Price�Groups�Without�Scale�Display���������������������������|
�
|03|Incoterms�with�Scale�Display�����������������������������������������������|
�
|04|Incoterms�Without�Scale�Display��������������������������������������������|
�
|05|Price�List�Types�Without�Scale�Display�������������������������������������|
�
|06|Price�List�Types�with�Scale�Display����������������������������������������|
�
|07|Cust.-specific�Prices�with�Scale�Display�����������������������������������|
�
|08|Cust.-specific�Prices�W/out�Scale�Display����������������������������������|
�
|09|Material�List/Material�Pricing�Group�with�Scale�Display��������������������|
�
|10|List�Mat./Mat.Pricing�Groups�Without�Scale�Display�������������������������|
�
|11|Price�Groups�With�Scale�Display��������������������������������������������|
�
|14|Taxes����������������������������������������������������������������������|
�
|15|Material�Price�������������������������������������������������������������|
�
|16|Individual�Prices����������������������������������������������������������|
�
|17|Discounts�and�Surcharges�by�Customer���������������������������������������|
�
|18|Discounts�and�Surcharges�by�Material���������������������������������������|
�
|19|Discounts�and�Surcharges�by�Price�Group������������������������������������|
�
|20|Discounts�and�Surcharges�by�Material�Group���������������������������������|
�
|21|Discounts�and�Surcharges�by�Customer/Material������������������������������|
�
|22|Discounts�and�Surcharges�by�Customer/Material�Group������������������������|
�
|23|Discounts�and�Surcharges�by�Price�Group/Material���������������������������|
�
|24|Discounts�and�Surcharges�by�Price�Group/Material�Group���������������������|
�
|25|VAT/ATX1�������������������������������������������������������������������|
�
|26|Canada/USA�����������������������������������������������������������������|
�
|27|I.E.P.S�Mexico�������������������������������������������������������������|
�
|28|Conditions�by�Customer�����������������������������������������������������|
�
|30|Conditions�by�Customer�Hierarchy�������������������������������������������|
�
|31|Price�List�with�Release�Status���������������������������������������������|
�
|AC|���������������������������������������������������������������������������|
�
|AD|���������������������������������������������������������������������������|
�
---------------------------------------------------------------------------�
Mass�Update�of�condition�pricing�
You�can�update�the�condition�pricing�for�a�range�of�sales�order.�
For�e.g.�if�you�create�sales�order�for�15�months�or�so,�and�at�the�beginning�of�
each�year,��you�have�to�update�the�prices�for�lots�of�sales�orders.�
Other�than�using�VA02�and�make�an�Update�of�the�conditions�at�item�level�
which�is�a�big�work�because�you�will�have�lots�of�open�sales�order�after�so�many
�
months.�
Use�VA05,�select�your�Orders�and�on�the�result�screen�:-�
click�Edit-�>�Mass�Change�->�New�Pricing�(menu).�
or�
if�you�don't�want�to�do�that�Online,�write�your�own�abap�report�and�use�
-----------------------�Page�207-----------------------
FunctionSD_BULK_CHANGE�(check�where-Used�at�SE37,�Trace�VA05�on�how�
to�fill�the�parameters,�Function�MPRF�=>�New�Pricing)�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
Make�Material�Master�Price�of�a�material�as�
sales�price�automatically�
The�first�method�is�not�to�set�the�pricing�condition�VPRS�as�statistical.�
Simply�remove�PR00�and�it�will�work�fine�if�you�always�use�VPRS�as�your�
pricing�base�inside�the�pricing�procedure.�
VPRS�will�reads�both�prices�based�on�the�price�control�in�the�material�master.�
Price�control�S�for�standard�price.�
Price�control�V�for�moving�average�price.�
It�is�this�simple�if�you�do�not�have�any�other�"Prices"�in�the�price�procedure.�
However,�if�you�are�using�one�pricing�procedure�where�for�some�items�you�price�
using�VPRS�and�some�others�using�PR00,�then�you�should�use�requirement�
routines�to�enable�the�correct�price�condition�type�at�the�right�time.�
The�second�method�involves�more�work�as�you�need�to�write�a�formula�(VOFM)�
to�get�that�information.�
This�is�how�it�goes�:-�
1.�Set�VPRS�to�be�the�first�step�in�the�pricing�procedure�and�to�be�subtotal�B�
(as�standard).�
2.�Set�PR00�with�alt.�calc.�type�formula,�which�sets�the�value�of�PR00�to�be�
equal�to�the�subtotal�B.�
���The�routine�(created�with�transaction�VOFM)�is:�
RV64A901�
FORM�FRM_KONDI_WERT_600.�
���XKWERT�=�KOMP-WAVWR.�
ENDFORM.�
The�pricing�procedure�than�looks�like�that:�
Step�1�VPRS�statistical,�subtotal�B,�reqt�4�
Step�2�PR00�Altcty�600�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
http://www.sap-img.com�
-----------------------�Page�208-----------------------
Customer�discounts�on�effort�only�
-----Original�Message-----�
Subject:�Customer�discounts�on�effort�only�
Hi�All,�
We�have�a�requirement�of�giving�a�discount�to�customer�based�on�the�total�
amount�invoiced�so�far�(across�financial�years).�
Where�do�we�set�this�up?�We�have�seen�so�far�the�discounts�are�calculated�
based�on�the�value�of�the�current�invoice.�
The�discount�should�be�on�a�graduated�scale�basis�for�example�
0�-�100000�No�discount�
100000�-�200000�5%�
200000�-�and�above�10%�
This�means�that�discount�would�only�start�after�the�customer's�net�sale�
value�crosses�100000.�
For�example,�if�the�customer�has�been�billed�for�99000�and�the�current�
invoice�is�for�3000,�a�discount�of�5%�should�be�given�on�2000�i.e.�100.�
Another�complication�is�that,�the�discount�is�not�based�on�the�total�amount�
billed�so�far,�but�only�on�the�effort�billed�and�not�on�reimbursements�(like�
airfares,�living�expenses,�visa�charges,�beeper�charges�etc).�The�discount�
applies�only�to�the�effort�and�not�to�the�reimbursements.�In�the�above�
example�(invoice�of�3000)�say�the�effort�billed�is�only�1500,�the�rest�being�
reimbursements.�The�discount�is�only�on�the�500.�(the�rest�being�taken�up�by�
the�lower�limit�for�eligibility�of�100000)�
For�example�the�customer�might�have�been�billed�say�150000�so�far�but�actual�
effort�billed�might�be�only�90000,�the�rest�being�reimbursements�of�actual�
costs�and�hence�the�customer�is�not�eligible�for�the�discount.�
Kindly�help,�
-----Reply�Message-----�
Subject:�RE:�Customer�discounts�on�effort�only�
Hi,�
The�solution�for�this�is�Using�rebate�condition�types�and�suitable�condition�
records.�
Of�this�to�handle�your�first�problem�that�is�the�rebate�has�to�be�applied�
only�on�the�"effort"�you�have�to�set�up�a�line�in�the�pricing�procedure�
which�gives�the�rebate�basis�i.e�the�value�to�be�used�for�rebate�cond�types.�
This�I�believe�solves�your�problem�of�rebate�only�on�effort.�
Your�second�problem�i.e�the�discount�should�start�getting�applied�
automatically�when�it�reaches�the�first�scale�for�which�the�values�span�few�
financial�years.�This�I�am�not�really�sure�whether�it�can�be�made�possible�
in�the�invoice�itself.�But�a�work�around�is�not�giving�the�discount�directly�
in�the�invoice�but�settling�it�against�the�rebate�agreements�by�Credit�notes�
periodically.�
Hope�it�helps.�
Thanks�
-----Reply�Message-----�
-----------------------�Page�209-----------------------
Subject:�RE:�Customer�discounts�on�effort�only�
Hi�
Arent�we�looking�at�rebate�agreeement.�That�appears�to�be�a�straightaway�
solution�to�your�problem.�You�activate�the�sales�organization�and�the�
payer�for�that�
Regards�
-----Reply�Message-----�
Subject:�RE:�Customer�discounts�on�effort�only�
I�am�in�SAP�R/3�rel.30F.�
We�have�2�options�to�meet�your�requirement.�
1.�Using�scale�in�condition�type�(�tcode�V/06�),�choose�scale�basis�
G.Scale�based�on�a�formula�(�be:�your�based�amount�is�invoice�).�Define�
scale�formula.�You�need�ABAPER�to�define�it.�
2.�Using�routine�in�Alt.calc.type�(�tcode�V/08�,�Maintain�Pricing�
Procedure�).�Here,�you�also�need�ABAPER�to�create�routine.�
hope�this�help�
-----End�of�Message-----�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
http://www.sap-img.com�
Steps�to�Create�Commission�for�Agent�
For�creating�commission�agent,�you�have�to�follow�below�steps.�
1)�Establish�Partner�Functions�for�the�Commissionee(s)�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PARTNER�DETERMINATION�->;�
DEFINE�PARTNER�FUNCTIONS�
Transaction�Code:�VOPA�
2)�Assign�the�Partner�Functions�to�Partner�Procedures�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PARTNER�DETERMINATION�->;�
DEFINE�PARTNER�FUNCTIONS�
Transaction�Code:�VOPA�
3)�Create�a�Partner�Procedure�for�the�Commissionees�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PARTNER�DETERMINATION�->;�
DEFINE�PARTNER�FUNCTIONS�
Transaction�Code:�VOPA�
4)�Create�New�Customer�Account�Group(s)�for�Commission�Agents�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�
LOGISTICS�GENERAL�->;�LOGISTICS�BASIC�DATA:�BUSINESS�PARTNERS�->;�
CUSTOMERS�->;�CONTROL�->;�DEFINE�ACCOUNT�GROUPS�AND�FIELD�
SELECTION�FOR�CUSTOMER�
Transaction�Code:�OVT0�
-----------------------�Page�210-----------------------
5)�Assign�the�Partner�Functions�to�the�Customer�Account�Group(s)�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PARTNER�DETERMINATION�->;�
DEFINE�PARTNER�FUNCTIONS�->;�GOTO�->;�PARTNER�FUNCTIONS�->;�
ENVIRONMENT�->;�ACCOUNT�GROUP�ASSIGNMENT�
Transaction�Code:�VOPA�
6)�Assign�the�Partner�Functions�to�the�Partner�Procedure�for�the�Sales�
Document�Header�
Menu�Path:�Tools�->;�Business�Engineer�->;�Customizing�->;�Sales�and�
Distribution�->;�Basic�Functions�->;�Partner�Determination�->;�Define�Partner�
Functions�
Transaction�Code:�VOPA�
7)�Assign�the�Partner�Functions�to�the�Partner�Procedure�for�the�Sales�
Document�Item�(OPTIONAL)�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PARTNER�DETERMINATION�->;�
DEFINE�PARTNER�FUNCTIONS�
Transaction�Code:�VOPA�
8)�Edit�the�Pricing�Communication�Structure�(KOMKAZ)�to�Hold�the�New�
Functions�(Client�Independent)�
Menu�Path:�Menu�Path:�TOOLS�->;�ABAP�WORKBENCH�->;�DEVELOPMENT�->;�
DICTIONARY�
Transaction�Code:�SE11�
9)�Edit�MV45AFZZ�–�userexit_pricing_prepare_tkomk�(Client�Independent)�
Menu�Path:�TOOLS�->;�ABAP�WORKBENCH�->;�DEVELOPMENT�->;�ABAP�
EDITOR�
Transaction�Code:�SE38�
10)�Edit�RV60AFZZ�-�userexit_pricing_prepare_tkomk�(Client�Independent)�
Menu�Path:�TOOLS�->;�ABAP�WORKBENCH�->;�DEVELOPMENT�->;�ABAP�
EDITOR�
Transaction�Code:�SE38�
11)�Edit�MV45AFZB�-�userexit_new_pricing_vbkd�changing�new_pricing�(Client�
Independent)�
Menu�Path:�TOOLS�->;�ABAP�WORKBENCH�->;�DEVELOPMENT�->;�ABAP�
EDITOR�
Transaction�Code:�SE38�
The�following�code�should�be�inserted�into�program�MV45AFZZ�to�allow�the�
system�to�re-execute�pricing�if�the�user�makes�a�change�to�the�relevant�partner�
function�(alteration,�addition,�deletion).�
13)�Add�the�KOMKAZ�Fields�to�the�Pricing�Field�Catalog�(Client�Independent)�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PRICING�->;�PRICING�
CONTROL�->;�DEFINE�ACCESS�SEQUENCES�->;�MAINTAIN�ACCESS�
SEQUENCES�
Transaction�Code:�OV24�
14)�Create�Condition�Tables�(Client�Independent)�
-----------------------�Page�211-----------------------
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PRICING�->;�PRICING�
CONTROL�->;�DEFINE�ACCESS�SEQUENCES�->;�MAINTAIN�ACCESS�
SEQUENCES�
Transaction�Code:�V/03�
15)�Create�an�access�sequence�containing�the�new�tables�(Client�Independent)�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PRICING�->;�PRICING�
CONTROL�->;�DEFINE�ACCESS�SEQUENCES�->;�MAINTAIN�ACCESS�
SEQUENCES�
Transaction�Code:�V/07�
16)�Create�a�new�condition�type�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PRICING�->;�PRICING�
CONTROL�->;�DEFINE�CONDITION�TYPES�->;�MAINTAIN�CONDITION�TYPES�
Transaction�Code:�V/06�
17)�Add�the�Condition�Type�to�the�Pricing�Procedure�
Menu�Path:�TOOLS�->;�BUSINESS�ENGINEER�->;�CUSTOMIZING�->;�SALES�
AND�DISTRIBUTION�->;�BASIC�FUNCTIONS�->;�PRICING�->;�PRICING�
CONTROL�->;�DEFINE�AND�ASSIGN�PRICING�PROCEDURES�->;�MAINTAIN�
PRICING�PROCEDURES�
Transaction�Code:�V/08�
11)�Create�Commsission�Report�ZZCOMMISSION�(Client�Independent)�
Menu�Path:�TOOLS�->;�ABAP�WORKBENCH�->;�DEVELOPMENT�->;�ABAP�
EDITOR�
Transaction�Code:�SE38�
With�Compliments�by:�Kamles�
Fast�Links:�
SD�Questions�About�Pricing�Condition�
The�Most�Important�Tips�in�Pricing�For�SAP�SD�Module�to�crack�
interviews...�
Whenever�we�define�our�pricing�procedures,�we�remain�least�interested�in�
creating�our�own�Condition�Types,Condition�
�Tables�&�Access�Sequences.�What�we�do�is,�we�just�define�our�own�pricing�
procedures�by�using�the�existing�condition�types�(i.e:�PR00,�K004,�K007,�KA02,�
KF00�etc.)�&�then�assign�that�Pricing�Procedure�with�"�Sales�Area,�Document�
Pricing�Procedure�&�Customer�Pricing�Procedure�"�.�
After�that�we�put�the�values�against�each�Condition�Types,�mentioned�in�our�
Pricing�Procedure�by�using�the�T-Code�"VK11".�But�we�also�need�to�know�about�
-----------------------�Page�212-----------------------
the�Condition�Tables,�Condition�Types�&�Access�Sequence�Creation.�So�for�that�
purpose�we�have�to�use�the�following�T-Codes�respectively�:�"V/05",�"V/06"�&�
"V/07".�Now�it�will�become�easy�to�create�the�same.�
Also�to�inform�that,�using�T-Codes�is�more�smarter�than�following�paths�through�
IMG�screen.�
Utsav�Mukherjee�-�utsavmukherjee143@hotmail.�
What�is�the�difference�of�VK11�and�VK31�(condition�records)?�
My�condition�type�is�PR00�and�Access�sequence�is�PR02.��And�in�this�
access�sequence�table�304�is�available.�������������Now�when�I�was�entering�the�
PR00�in�VK31�it�shows�error�Table�304�is�not�defining�for�the�condition�
type�PR02.������But�when�I�was�entering�the�PR00�at�VK11�it�is�accepting�
it.�
Difference�between�VK11�and�VK31�-�if�you�go�through�the�menu�path�you�will�
get�the�vk�31�as�condition�record�from�the�tamplets�whereas�vk11�as�simple�
condition�record.��In�VK11�you�can�store�condition�record�for�more�than�one�
condition�
type.��This�means�you�can�have�same�condition�record�for�different�condition�
types.This�feature�is�given�to�enhance�the�system's�performane�and�not�to�
create�the�duplcation�of�the�work�for�each�condition�type.�
Again�system�is�not�allowing�to�store�the�record�in�the�vk31�for�the�condition�
type�pr00�and�access�sequence�pr02.This�is�because�if�you�see�this�ac�seq�
cointains�two�accessses�20�and�30�having�the�same�table�no.But�you�see�there�
is�the�difference�between�the�technical�view�of�it�for�transfering�the�data�from
�
document�field�and�condition�field,so�you�can�not�maintain�the�data�at�VK31.�
What�is�the�difference�between�Header�condition�and�Item�condition?�������������
�����������I�
know�item�condition�applies�to�each�item�in�a�sales�document.�������������������
�Header�
condition�can�only�be�applied�to�an�entire�document.�
Difference�between�header�and�item�condition�-�as�YOU�CORRECTLY�SAID�
HEADER�CONDITION�IS�APPLICABLE�FOR�THE�WHOLE�DOCUMENT�where�as�
item�is�for�item.Ex-Say�fright�is�dependent�on�the�total�weight�of�all�the�items
�in�
the�documents�then�header�condition�adds�on�weights�of�all�items�and�
calculates�the�record�accordingly.�
You�have�two�different�types�of�the�header�conditions.�
a)�In�one�you�can�duplicate�the�same�value�throughout�the�document�for�each�
item.Say�discount�2%�at�header�level�which�is�also�applicable�to�all�the�items�
b)Second�is�the�accumulation�of�the�values�of�all�the�item�at�the�header�level,a
s�
earlier�explained�for�the�weight/fright.�
These�differenes�are�controlled�through�the�indicator�of�group�condition�in�the�
cond.type�configuration.�
And�so�obviously�header�condition�can�not�have�the�condition�record�and�hence�
access�sequence.�
SAP�SD�Tips�by�:�Vishwajit�
Disallowing�Condition�Types�-�How�I�can�accomplish�the�following:�
Be�able�to�DISALLOW�Z0BP�Condition�type�to�be�negative�(�Invoice�
-----------------------�Page�213-----------------------
Block)�
You�can�modify�condition�type�from�customising;�
Sales�and�Distribution->Basic�Functions->Pricing->Pricing�Control->Define�
Condition�Types->Maintain�Condition�Types�
Change�condition�type�ZOBP's�plus/minus�indicator�to�"A"�which�means�only�
positive�is�allowed.��*--�Arvind�Rana�
In�pricing�procedure�there�are�column�such�as�requirement,�sub�total�
altclty,�altbv,�accurals.�What�are�these�and�where�we�calculate�all�these�
values�which�we�put.�
1.�Requirement:�Denoted�by�nos�and�maintained�in�VOFM,�this�is�a�condition�
required�for�a�particular�condition�type��to�be�executed.�Eg.�PR00:�req�2�ie�ite
m�
relevant�for�pricing�
����VPRS/EKO1:�req�4�ie�cost�
�����Rebate�BAO1�Req�24/Req�25��etc�
2.�Subtotal:�this�represents�where�a�which�table�a�value�is�stored,�which�can�be
�
processed�for�further�calculation.�
Eg.�for�PR00,�if�this�value�is�to�be�used�for�credt�check�of�a�customer,�we�mark
�
the�subtotal�as�A.�
3�Alternate�Calculation�type:�this�is�also�denoted�by�numbers�and�maintained�in�
VOFM.�Eg.�Suppose�for�45�units�,�each�unit�is�charged�$100�per�unit,�the�order�
value�comes�out�to�be�$4500,�that�is�calculation�is�done�as�per�unit�price,�if�t
he�
client�wants�calculation�type��to�be�based�on�volume�or�wieght,�alternate�
calculation�type�can�be�configured.�
4.�Alternate�base�value:�Denoted�by�no.�and�maintained�in�VOFM.�
Eg,�if�the�pricing�scale�is�maintained�and�pricing�for�45�units�comes�under�the�
scale�of�$100�per�unit.,�the�base�value�is�45�units,�but�if�the�client�wants�a�
standard�base�value�in�some�casesto�be�assumed�inspite�of�maintaining�the�
scale,�an�alternate�base�value�is�confihured,�that�is�the�base�value�based�on�
which�the�order�value�is�to�be�calculated�changes.�
5.�Accruals:�Accruals�are�maintained�for�rebate�agreements,�it�constitutes�the�
total�accumulated�value�which�customer�has�earned�through�rebate,�one�the�
rebate�for�certain�amount�is�settled�the�amount�from�the�accruals�get�
deducted.�
Add�a�Field�To�New�Condition�Table�in�Pricing�
Add�a�field�to�a�new�condition�table�in�Pricing�(Condition�Technique):-�
I�will�explain�you�the�process�with�below�example...Please�follow�steps�in�below
�
sequence-�
Try�to�add�the�filed�from�the�field�catalog.�In�case�the�required�combination�
field�is�not�there,�you�can�add�the�field�through�the�following�process�to�filed
�
catalog�and�create�the�condition�table.����It�is�most�common�that�one�or�other�
time�we�need�to�use�this�function�while�configuring�multi�tasking�&�complex�
Pricing�Architecture.�
Here�I'm�giving�a�simple�guide�to�add�fields�to�the�Pricing�Field�Catalogues:�
For�example�you�want�to�use�field�PSTYV�('Sales�document�item�category')�that�
-----------------------�Page�214-----------------------
is�included�in�structure�KOMP�('Pricing�Communication�Item')�as�a�key�for�a�
condition�table.�
When�you�create�a�condition�table�(Transaction�V/03),�however,�the�system�
does�not�propose�the�field�in�the�field�catalog.�
Condition�access,�field�catalog,�allowed�fields,�KOMG,�KOMK,�KOMP,�KOMPAZ,�
KOMKAZ,�PSTYV�are�the�other�terms�which�we�need�to�know�about,�to�add�
Fields.�
Reason�and�Prerequisites:�
For�technical�reasons,�field�PSTYV�was�included�in�structure�KOMP,�however,�not�
in�structure�KOMG�('Allowed�Fields�for�Condition�Structures').�
Proceed�as�follows:�
1.�Call�up�the�ABAP�Dictionary�(Transaction�SE11)�and�create�data�type�
ZZPSTYV.�Choose�PSTYV�as�a�domain.As�a�short�text,�you�can�use,�for�example,�
'ZZ�-�sales�document�item�category'�and�as�a�field�label,�you�can�use�the�field�
labels�of�PSTYV.Save,�check�and�activate�your�entries.�
2.�Call�up�structure�KOMPAZ�in�the�ABAP�Dictionary�(Transaction�SE11)�in�the�
change�mode�and�make�the�following�entry:�
Component�Component�type:�
ZZPSTYV�ZZPSTYV�
Save,�check�and�activate�the�change�you�made.�
3.�Note:Because�of�the�change�in�structure�KOMPAZ,�field�ZZPSTYV�is�now�
known�in�structures�KOMG�and�KOMP�because�structure�KOMPAZ�is�included�in�
both�structures.�
4.�Call�up�Transaction�SPRO.�Navigate�to�'Sales�and�Distribution�->�Basic�
Functions�->�Pricing�->�Pricing�Control'�and�execute�'Define�Condition�Tables'.�
Choose�'Conditions:�Allowed�fields'�and�include�ZZPSTYV�as�a�new�entry.�
5.�Note:Now�you�can�use�field�ZZPSTYV�as�a�key�field�when�you�create�a�
condition�table�Axxx.�
6.�Supply�the�new�field�you�defined�by�including�the�following�source�code�line�
in�USEREXIT_PRICING_PREPARE_TKOMP:�
MOVE�xxxx-PSTYV�TO�TKOMP-ZZPSTYV.�
In�order�processing�you�find�the�user�exit�in�Include�MV45AFZZ,�and�in�billing�
document�processing�you�find�it�in�Include�RV60AFZZ.�
Consider�that�you�can�also�use�this�note�as�a�help�if�you�want�to�use�other�
customer-specific�fields�as�key�fields�in�a�condition�table.�
For�header�fields,�use�structure�KOMKAZ�instead�of�structure�KOMPAZ�and�
�USEREXIT_PRICING_PREPARE_TKOMK�instead�of�
�USEREXIT_PRICING_PREPARE_TKOMP.�
For�more�information,�see�Transaction�SPRO�via�the�path�'Sales�and�Distribution�
->�System�Modifications�->�Create�New�Fields�(Using�Condition�Technique)�->�
New�Fields�for�Pricing'�and�OSS�Note�21040.��������������*--�Manoj�Mahajan�
-----------------------�Page�215-----------------------
Billing�cannot�be�Release�to�Accounting�
This�SAP�message�will�appear�if�the�system�is�unable�to�find�the�G/L�codes�
match�from�the�configuration�in�transaction�VKOA�
No�account�is�specified�in�item�0000001001�
Message�no.�F5�670�
Diagnosis�
No�account�was�specified�for�account�type�"S"�in�item�"0000001001"�of�the�
FI/CO�document.�
System�Response�
The�Financial�Accounting�program�cannot�process�the�document.�
Procedure�
A�system�error�has�probably�occurred�in�the�application�you�called�up.�Check�
the�data�transferred�to�item�"0000001001"�of�the�FI/CO�document.�
Assuming�that�one�of�the�key�combination�is�Account�Assignment�Group,�you�
will�have�to�check�whether�have�the�Account�Assignment�Group�been�input�in�
the�Customer�Master�(Billing�tabstrips�-�Accounting�sections�-�Field�name:�Acct�
assgmt�group).�
The�Account�Assignment�Group�will�be�copied�automatically�into�the�sales�
order.�
Check�whether�the�configuration�in�transaction�VKOA�have�been�done�correctly.�
Check�whether�the�sales�order�(VA03�-�Goto�-�Header�-�Financial�Accounting�-�
Field�name:�AcctAssgGr)�have�been�filled�in�automatically.�
Check�whether�the�billing�document�(VF03�-�Goto�-�Header�-�Header�-�Field�
name:�AcctAssgGr)�have�been�filled�in�automatically.�
If�the�customer�master�have�not�been�maintained�and�the�user�have�already�
input�the�sales�order,�then�the�user�will�have�to�maintained�the�Account�
Assignment�Group�manually�either�in�the�sales�order�or�the�billing�documents.�
Take�note�for�One�Time�Customer,�the�user�have�to�input�the�Account�
Assignment�Group�manually�into�the�sales�order.��One�Time�Customer�can�be�
used�by�many�customer,�therefore,�the�system�will�not�be�able�to�determine�the�
Account�Assignment�Group�manually.�
Default�Start�Variant�for�VF04�
There�are�two�types�of�variant�in�VF04.�
One�is�the�selection�variant�before�clicking�the�Display�Billing�List�Button.�
You�can�set�the�start�variant�via�SE93�using�the�Change�mode.�
The�second�variant�is�the�Billing�Layout�display�variant.�
This�is�after�clicking�the�Display�Billing�List�Button.�
After�creating�your�layout�display�variant,�you�can�set�it�by�clicking�:-�
Settings�->�
��������Display�Variant�
����������������������->��Administration�
Select�the�layout�display�variant�you�want�and�click�:-�
-----------------------�Page�216-----------------------
Edit�->�
������Define�default�settings�
Best�regards,�
Condition�Exclusion�which�will�be�determined�
in�the�billing�document�
The�system�can�exclude�conditions�so�that�they�are�not�taken�into�
account�during�pricing.�
For�example:�
Material�4711�costs�150�USD.�Some�customers�receive�a�discount�of�10�
USD�per�100�pieces.�
However,�a�specific�customer�can�buy�the�material�for�100�USD.�Since�
this�is�a�particularly�good�price,�the�customer�should�not�also�have�a�
discount�of�10�USD�per�100�pieces.�Therefore,�this�discount�is�to�be�
excluded�from�pricing.�
To�create�a�condition�exclusion�procedure�which�will�be�determined�in�the�billin
g�
document.�
Assign�the�procedure�to�the�pricing�schema,�and�maintain�copy�control�so�that�
pricing�is�not�copied�from�Sales�Order.�
To�achieve�this,�copy�the�standard�pricing�to�a�ZXXXX�Pricing.�
Define�new�document�pricing�procedure�in�SM30�-�V_TVKV�for�billing.�
Assign�new�document�pricing�procedures�to�billing�types�in�SM30�-�
V_TVFK_PR�
Define�the�Condition�Exclusion�Groups�in�OV31.�
Assign�the�Condition�type�for�the�Condition�Exclusion�Groups�in�OV32.�
Assign�the�Billing�Pricing�Procedure�in�VOK8�for�the�Condition�Exclusion�
Groups.�
When�billing�document�is�being�created�just�enter�manually�your�new�price�and�
the�pricing�program�logic�will�include�only�the�higher�price�one,�excluding�the�
rest�that�are�lower�price.�
Related�Topics:�
Create/Modify�Billing�Document�Type�
Steps�for�creating�new�or�changing�existing�Billing�Doc�Type�
Get�help�for�your�SAP�SD�problems�
Do�you�have�a�SAP�SD�Question?�
SAP�SD�Books�
SAP�Sales�and�Distribution,�Certification,�Interview�Questions�Reference�Books�
SAP�Sales�and�Distribution�Tips�
SAP�SD�Discussion�Forum�and�Sales/Distribution�Tips�
Steps�for�creating�a�new�or�changing�an�
existing�Billing�Document�Types�
-----------------------�Page�217-----------------------
Create/Change�your�Billing�types�configuration�in�VOFA�.�
Some�of�the�IMG�stuff�are�:-�
1)�To�block�automatic�transfer�of�the�billing�document�to�accounting,�mark�the�
field.�
���Indicates�whether�the�system�blocks�automatic�transfer�of�the�billing�
document�to�
���accounting.�
���During�document�processing,�you�can�manually�transfer�blocked�billing�
documents�to�
���accounting�by�selecting:�
���Billing�->�Change�->�Release�accounting�
2)�Account�determination�procedure�
3)�Output�determination�procedure�etc.�...�
After�customizing,�use�transaction�VCHECKVOFA�to�check�your�configuration�:-�
1)�Proforma�billing�types:�If�it�is�a�proforma�billing�type,�(VBTYP�=�U),�the�fi
eld�
must�
���be�blank�and�the�account�determination�procedure�must�be�empty.�
2)�Cancellation�billing�document�types:�:�A�check�is�made�to�see�if�the�
cancellation�
���billing�document�type�has�the�right�VBTYP.�An�F2�invoice,�for�example,�
(VBTYP�'M')�
���can�only�be�canceled�with�billing�type�S1�with�VBTYP�'N'�.�A�billing�type�wit
h�
���VBTYP�'5'�can�only�be�canceled�with�the�VBTYP�'6'�and�vice�versa.�
3)�Cancellation�billing�document�type�partner�functions�A�check�is�made�to�see�i
f�
the�
���cancellation�billing�document�type�partner�functions�are�empty�or�if�those�
that�
���correspond�to�the�billing�type�used�are�empty.�
Next,�make�sure�that�you�maintain�the�copy�control�for�the�Billing�Types:�
Sales�documents�in�VTFA�
������Target�������������Source�
e.g.��F1�-�Invoice��������OR�-�Standard�Sales�Order�
�������F1�-�Invoice������ZOR�-�Your�Sales�Order�
Billing�documents�in�VTFF�
e.g.��G2�-�Debit�Memo��������F1�-�Invoice�
�������G2�-�Debit�Memo��������F2�-�Invoice�
Deliveries�in�VTFL�
e.g.��F1�-�Invoice��������LF�-�Delivery�
������F1�-�Invoice������ZOR�-�Your�Delivery�
Usually�for�copy�control,�you�let�the�rest�of�the�settings�remains�as�SAP�
defaults.�
You�only�assign�the�new�Billing�Document�Types.�
After�that�use�transaction�VCHECKTVCPF�to�check�your�Copy�control�
customizing.�
Related�Topics:�
-----------------------�Page�218-----------------------
Integration�between�SD,�MM,�FI�
Link�Between�SAP�SD,�MM�&�FI�
Get�help�for�your�SAP�SD�problems�
Do�you�have�a�SAP�SD�Question?�
SAP�SD�Books�
SAP�Sales�and�Distribution,�Certification,�Interview�Questions�Reference�Books�
SAP�Sales�and�Distribution�Tips�
Billing�Block�will�not�worked�if�you�did�not�
assign�it�
Define�the�possible�block�indicators�in�SM30�-�V_TVFS�
and�
allocate�them�to�the�billing�types�concerned�in�SM30�-�V_TVFSP.�
Your�Billing�Block�will�not�worked�if�you�did�not�assigned�it�to�the�desired�bil
ling�
types.�
You�can�auto�block�by�:-�
1.��sales�document�type�in�transaction�VOV8,�fields�Billing�Block,�
or�
2.��item�categories�in�SM30�-�V_TVAP,�by�filling�the�fields�Billing�Block.�
Billing�Plan�for�Milestone�Billing�
Milestone�billing�means�distributing�the�total�amount�to�be�billed�over�
multiple�billing�
dates�in�the�billing�plan.�
As�each�milestone�is�successfully�reached,�the�customer�is�billed�either�a�
percentage�of�
the�entire�project�cost�or�simply�a�pre-defined�amount.�
During�sales�order�processing,�the�system�determines�from�the�item�category�
whether�a�
billing�plan�is�required�and,�if�so,�which�type�of�plan�
The�type�of�billing�plan�that�is�determined�at�this�point�is�set�up�in�
Customizing�and�
cannot�be�changed�in�the�sales�document.�
Billing�plans�for�periodic�billing�and�milestone�billing�plans�for�project-�
related�milestone�
billing�have�different�overview�screens�so�that�you�can�enter�data�relevant�
to�your�
processing.�
For�example,�for�milestone�billing,�you�must�be�able�to�enter�data�to�
identify�the�
individual�milestones.�
IMG�configuration�requires�:-�
-----------------------�Page�219-----------------------
1.��Maintain�billing�plan�types�for�milestone�billing�in�OVBO�.�
2.��Define�date�description�in�SM30�-�V_TVTB�.�
3.��Maintain�Date�Category�for�Billing�Plan�Type�IN�OVBJ�.�
4.��Allocate�date�category�in�SM30�-�V_TFPLA_TY�.�
5.��Maintain�date�proposal�for�Billing�Plan�Type�in�OVBM�.�
6.��Assign�Billing�Plan�Type�to�Sales�Documents�Type�in�OVBP�.�
7.��Assign�Billing�Plan�Type�to�Item�Categories�in�OVBR�.�
8.��Define�rules�for�determining�the�date�in�OVBS�.�
Milestone�billing�is�typically�used�for�billing�projects,�such�as�plant�
engineering�and�
construction�projects.�Such�projects�often�include�a�series�of�milestones�
that�mark�the�
completion�of�different�stages�of�the�work.�In�the�SAP�R/3�System,�milestones�
are�defined�
in�a�network�along�with�planned�and�actual�dates�for�the�completion�of�work.�
The�milestones�
are�also�assigned�to�the�billing�dates�in�the�billing�plan.�
Each�milestone-related�billing�date�is�blocked�for�processing�until�the�
Project�System�
confirms�that�the�milestone�is�completed.�
Delivery-relevant�order�items�for�which�a�milestone�billing�plan�applies�are�
billed�on�the�
basis�of�the�requested�delivery�quantity�and�not�on�the�total�of�the�
confirmed�quantities.�
The�connection�between�the�project�and�the�sales�document�item�is�made�in�the�
individual�
schedule�lines�of�the�item.�Each�schedule�item�can�be�assigned�to�a�network�
in�a�project.�
To�display�the�project-related�data�for�a�schedule�line,�proceed�as�follows:�
In�one�of�the�overview�screens�of�the�sales�document,�select�
1.��Item�->�Schedule�lines.�
2.��Mark�the�schedule�line�and�select�Procurement�details.�
The�following�figure�shows�an�example�of�milestone�billing�where�only�the�
Contract�have�
been�billed�:�
-----------------------�Page�220-----------------------
Order���Item��Turbine������100,000�
Billing�Plan�
Billing�date�Description��������%��Value���Billing�Block�����Milestone����Billin
g�
Status�
01-10-94�������Contract��������10��10,000��������-��������������x�������������x�
01-03-95�������Assembly��������30��30,000�������x���������������x�
01-04-95�������Maintenance�����30��30,000�������x���������������x�
01-05-95�������Acceptance������30��30,000�������x���������������x�
01-06-95�������Final�invoice�..�������..��������x�
Network/Activities�
Milestone������Estimate�������Actual�
Assembly�������01-03-95��������01-03-95�
Maintenance����01-04-95�
Acceptance�����01-05-95�
For�each�billing�date�in�a�milestone�billing�plan,�you�can�specify�whether�
the�billing�
date�is:�
1.���fixed�
2.��always�updated�with�the�actual�date�of�the�milestone�
3.��updated�with�the�actual�date�of�the�milestone,�if�the�date�is�earlier�
than�the�
�����planned�billing�date�for�the�date�
SAP�Billing�-�Combine�Billing�for�deliveries�
with�different�date�
When�using�transaction�VF04�or�Billing�(background),�the�date�of�the�billing�
document�(e.g.�the�current�date)�must�be�entered�(In�VF04�:�settings,�default�
data.)�
In�VF06�or�background:�variant�with�parametrization)�to�avoid�an�unwanted�
split�due�to�the�billing�date.�
This�OSS�notes�is�very�helpful�:-�
11162�-�Invoice�split�criteria�in�billing�document�
36832�-�Invoice�split�in�fields�from�the�sales�order�
Best�regards,�
Billing�Spilt�by�Item�Category�
Is�it�possible�to�split�invoice�Item�category�wise.�I�mean������������If�in�sale
s�
order�there�is�TAN�and�TANN�then�the�invoice�should�split,is�it�
possible?�
Naina�
Yes,�it�is�possible.�Create�a�modification�of�copy�control�routine�for�billing�a
nd�
use�VBAP-PSTYV�as�an�additional�split�criteria�there.�
Martishev�Sabir�
-----------------------�Page�221-----------------------
Thank�you�for�your�reply.�������Can�you�please�tell�me�the�exact�steps�what�
should�I�add�under�that(additional�split�criteria).�
Naina�
In�trx�VTFA�(if�your�billing�is�sales�order�based)�choose�your�billing�type�and�
SO�
type,�there�select�your�item�categories�and�there�select�the�field�VBRK/VBRP�
data.�In�that�field�you�will�see�the�currently�used�routine.�With�the�help�of�yo
ur�
ABAP�guy�create�a�copy�of�that�routine�under�a�different�number�and�add�your�
lines�of�code.�Let's�say�you�use�routine�001.�
FORM�DATEN_KOPIEREN_001.�
*�Header�data�
*�VBRK-xxxxx�=�............�
*�Item�data�
*�VBRP-xxxxx�=�............�
*�Additional�split�criteria�
DATA:�BEGIN�OF�ZUK,�
MODUL(3)�VALUE�'001',�
VTWEG�LIKE�VBAK-VTWEG,�
SPART�LIKE�VBAK-SPART,�
END�OF�ZUK.�
ZUK-SPART�=�VBAK-SPART.�
ZUK-VTWEG�=�VBAK-VTWEG.�
VBRK-ZUKRI�=�ZUK.�
ENDFORM.�
This�is�how�it�should�look�after�modification:�
*�Header�data�
*�VBRK-xxxxx�=�............�
*�Item�data�
*�VBRP-xxxxx�=�............�
*�Additional�split�criteria�
DATA:�BEGIN�OF�ZUK,�
MODUL(3)�VALUE�'001',�
VTWEG�LIKE�VBAK-VTWEG,�
SPART�LIKE�VBAK-SPART,�
PSTYV�LIKE�VBAP-PSTYV,���������<-�New�line�
END�OF�ZUK.�
ZUK-SPART�=�VBAK-SPART.�
ZUK-VTWEG�=�VBAK-VTWEG.�
ZUK-PSTYV�=�VBAP-PSTYV.���������<-�New�line�
VBRK-ZUKRI�=�ZUK.�
ENDFORM.�
After�this�routine�is�created�and�activated�place�it�as�the�default�copy�control
�
-----------------------�Page�222-----------------------
routine�instead�of�the�old�ones.�
Martishev�Sabir�
Fast�Links:�
Dunning�Process�In�Credit�Management�
Explain�about�dunning�process�in�credit�management?�
Let�me�explain�in�simple�terms:�
1)�You�have�a�Customer�which�you�had�felt,�he�is�doing�good�business�and�
supplied�material�on�Credit�of�45�days.�
2)�Since�this�customer�is�good�as�you�felt,�you�have�not�managed�Credit�Checks�
as�well.�So,�he�had�comfortably�reached�to�the�fullest�credit�(or�even�more)�
which�you�can�afford�for�any�customer.�
3)�One�fine�day�you�got�realised�that,�there�is�very�bad�debt�with�this�customer
�
and�need�to�recover�from�him�and�till�then,�there�will�be�no�further�supply�to�
the�customer.�
4)�Your�company's�legal�department�has�laid�a�policy�that,�inorder�to�recover�
any�bad�debts,�like:�
a)�We�will�send�a�normal�payment�reminder.�
b)�In�case�customer�doesnt�respond,�we�will�send�at�least�further�reminder�
(dunning�notice)�may�be�9�times�
���(9�reminders)�(Dunning�level)�and�what�intervels�of�time�(dunning�
frequency)�
c)�Still�if�the�customer�doesnt�resopond�for�the�reminders,�you�will�file�a�law�
suit�
against�the�customer�for�recovering�
���the�Payments.�
d)�Finally,�after�getting�veridict,�you�may�proceed�for�auction�of�his�property�
or�
as�per�the�order�for�Law.�
Now�in�SAP,�the�definition�of�Dunning�procedure�is�a�pre-defined�procedure�
specifying�how�customers�or�vendors�are�dunned.�
For�each�procedure,�the�user�defines�
-�Number�of�dunning�levels�
-�Dunning�frequency�
-�Amount�limits�
-�Texts�for�the�dunning�notices�
In�SAP,�you�will�maintain�the�Dunning�Procedure�at�customer�master.��������Refer
ring�
to�this�your�SD�Team�/�FI�Team�(user�team)�will�effect�Dunning�
PS:�You�might�remembered�the�dunning�procedure�laid�by�Relaince�Mobile,�
sometime�back,�sending�street�rowdies�for�recovering�the�bad�debts�from�users.�
That�is�dunning.�Remember�Reliance,�you�will�not�forget�dunning�forever.�
Tips�by�:�Kumar�
Restricting�Number�Of�Items�In�Billing�Doc�
How�I�can�restrict�number�of�items�in�an�invoice?�
If�I�enter�more�than�8�items�in�a�sales�order�and�those�items�get�copied�
into�delivery�doc�then�to�billing�doc.������But�our�client�want�to�restrict�
number�items�to�8�(max)�in�an�invoice.�
-----------------------�Page�223-----------------------
You�can�restrict�delivery�with�delivery�tolerance,�thereby�causing�invoicing�of�
the�desired.�
or�
Go�to�SPRO>>>IMG>>>Sales�&�Distribution>>>Billing>>>Billing�
Documents>>>Country-specific�features>>>Maintain�Maximum�No.�Of�Billing�
Items.�
This�is�where�you�can�define�a�maximum�number�of�items�allowed�for�all�billing�
documents�within�a�given�sales�organization.�
However,�maintaining�data�here�is�not�enough�alone�to�bring�about�a�billing�spli
t�
by�number�of�billing�items.�
You�must�also�go�to�copying�control�for�order/delivery�to�billing�document�at�
item�level�under�"Data�VBRK/VBRP"�and�maintain�routine�006�"individual�invoice�
limited"�or�a�similar�routine�that�accesses�the�data�maintained�here.�
SAP�SD�Tips�by�:�Amol�
How�To�Do�Configuration�For�Credit�
Management�
Credit�and�risk�management�takes�place�in�the�credit�control�area.�According�to�
your�corporate�requirements,�you�can�implement�credit�management�that�is�
centralized,�decentralized,�or�somewhere�in�between.�
An�organizational�unit�that�represents�the�area�where�customer�credit�is�
awarded�and�monitored.������This�organizational�unit�can�either�be�a�single�or�
several�company�codes,�if�credit�control�is�performed�across�several�company�
codes.�One�credit�control�area�contains�credit�control�information�for�each�
customer.�
For�example,�if�your�credit�management�is�centralized,�you�can�define�one�
credit�control�area�for�all�of�your�company�codes.�
If,�on�the�other�hand,�your�credit�policy�requires�decentralized�credit�
management,�you�can�define�credit�control�areas�for�each�company�code�or�
each�group�of�company�codes.�
Credit�limits�and�credit�exposure�are�managed�at�both�credit�control�area�and�
customer�level.��You�set�up�credit�control�areas�and�other�data�related�to�credi
t�
management�in�Customizing�for�Financial�Accounting.�The�implementation�guide�
is�under�Enterprise�Structure�->�Definition�or�Assignment�->�Financial�
Accounting�and�then�Maintain�credit�control�area.�You�assign�customers�to�
specific�credit�control�areas�and�specify�the�appropriate�credit�limits�in�the�
customer�master�record.�
Tips�by�:�Kapilaa�
Settings�for�determining�the�credit�control�area�of�a�document.��The�settings�of
�
items�1�-�4�are�taken�into�account�according�to�their�priority.��The�credit�cont
rol�
area�found�is�stored�in�field�VBAK-KKBER.�
1.�Transaction�OB38�
��Check�which�credit�control�area�is�assigned�to�the�company�code.�
��Company�code:�
��Credit�control�area:�
2.�Transaction�OVFL�
-----------------------�Page�224-----------------------
��Check�which�credit�control�area�is�assigned�to�the�sales�area.�
��Sales�area:�
��Credit�control�area:�
3.�Transaction�XD02�or�VD02�
��Check�which�credit�control�area�is�assigned�to�the�payer.�
��Payer:�
��Credit�control�area:�
4.�Transaction�SE37�
��Is�user�exit�EXIT_SAPV45K_001�being�used?�
5.�Transaction�OBZK�
��For�the�settings�under�items�2�-�4,�field�"All�company�codes"�must�be�marked�
in�Transaction�
��OB45,�or�the�credit�control�area�must�be�entered�under�the�relevant�company�
code�in�table�
��T001CM�of�the�credit�control�areas�allowed.�
��Company�code:�
��Credit�control�areas�allowed:�
6.�Settings�for�the�credit�checks�
7.�Transaction�OVAK�
��Which�settings�do�exist�for�the�sales�document�type�used?�
��Sales�document:�
��Check�credit:�
��Credit�group:�
8.�Transaction�OVAD�
��Which�settings�do�exist�for�the�delivery�type�used?�
��Delivery�type:�
��Credit�group�for�delivery:�
��Credit�group�for�goods�issue:�
9.�Transaction�OB01�
��Credit�management/Change�risk�category�
��Definition�of�the�risk�category�for�each�credit�control�area.�This�risk�catego
ry�
can�be�
��assigned�to�a�credit�account�by�using�Transaction�FD32.�
10.�Transaction�OVA8�
���Here,�the�individual�credit�checks�for�key�fields�
���o�credit�control�area�
���o�risk�category�
���o�credit�group�are�set.�Take�these�key�fields�from�the�above�settings�and�go�
to�the�detail�
�����screen.�In�particular,�check�whether�fields�"Reaction"�and�"Status/block"�a
re�
set�
�����correctly.�To�carry�out�follow-up�actions�in�case�of�a�credit�block,�the�cr
edit�
check�
�����status�must�be�set�(field�"Status/block").�
11.�Transaction�FD32�
���Credit�master�data�for�the�payer�of�the�relevant�document.�
-----------------------�Page�225-----------------------
���Credit�account:�
���Credit�limit:�
���Risk�category:�
���Currency:�
12.�Settings�for�updating�the�credit�values�Update�of�the�credit�values�is�
required�for�the�limit�
���check�(static�or�dynamic�credit�limit�check).�
13.�Transaction�OVA7�
���Update�of�the�credit�value�is�active�for�the�corresponding�item�type�if�the�
check�box�is�marked.�This�field�corresponds�to�
���field�"Active�receivable"�in�Transaction�VOV7.�
���Item�type:�
���Active�receivable:�
14.�Transaction�V/08,�Pricing�
���In�the�pricing�procedure�used�for�pricing,�subtotal�"A"�must�be�entered�in�a�
line�for�
���determining�the�credit�value�(mark�the�pricing�procedure�and�doubleclick�on�
"Control").�
���Usually,�the�net�value�plus�taxes�is�used.�This�way�the�system�is�determined�
to�use�this�
���subtotal�for�credit�pricing.�The�credit�price�is�stored�in�field�VBAP-CMPRE�a
nd�
used�for�
���update�and�credit�check.�
���You�can�find�the�used�pricing�procedure�of�the�order�under�"Item�->�
Condition�->�Analysis".�
���Pricing�procedure:�
���Line�with�subtotal�=�'A':�
15.�Transaction�OB45�
���Which�update�group�(field�"Update")�do�you�use�in�the�relevant�credit�control
�
area?�The�
���default�setting�is�"12".�If�you�use�another�update�group,�check�whether�this�
is�fine�with�
���you.�If�you�open�an�OSS�message,�please�tell�us�the�alternative�update�
group.�
���Credit�control�area:�
���Update:�
16.�Transaction�OMO1�
���Which�kind�of�update�did�you�choose�for�structure�S066?�
����In�any�case,�"Synchronous�update�(1)"�has�to�be�chosen�as�the�kind�of�
update.�
����All�other�settings�will�lead�to�errors.�
MRP�block�for�Credit�limit�attained�
Customers�
-----------------------�Page�226-----------------------
How�to�block�the�requirement�(MD04)�generated�by�the�item�category�
in�a�sales�order�when�the�customer�has�attained�the�credit�limit?��The�
MRP�requirements�still�appear�even�though�the�schedule�is�zero.�
You�should�try�and�use�one�of�the�standard�requirements.�
See�in�transaction�"VOFM".�
Under�Requirements�/�Subsequent�Functions�/�Reqs.Availablity.�
Try�using�routine�103,�you�may�have�to�tweak�if�it�doesn't�work�exactly�as�
you'd�like.�
For�example,�you�can�write�a�routine�903�because�you�only�wanted�this�
reaction�for�certain�business�units.�Irregardless,�using�a�routine�similar�to�th
is�
will�prevent�the�requirement�from�appearing�in�MD04�for�orders�blocked�on�
credit.�
Code:�
DATA:�W_ZSDCRD�TYPE�ZSD_CREDITBLCK.�
DATA:�W_CMGST�LIKE�VBUK-CMGST.�
SELECT�SINGLE�*�INTO�W_ZSDCRD�
FROM�ZSD_CREDITBLCK�
WHERE�KKBER�=�VBAK-KKBER�
AND�CTLPC�=�VBAK-CTLPC.�
IF�SY-SUBRC�=�0�AND�VBUK-CMGST�CA�'B'.�
IMPORT�VBUK-CMGST�TO�W_CMGST�FROM�MEMORY�ID�'CREDIT'.�
IF�W_CMGST�=�SPACE.�
MESSAGE�I706(Z1).�
EXPORT�VBUK-CMGST�TO�MEMORY�ID�'CREDIT'.�
ENDIF.�
*}�REPLACE�
*{�INSERT�DEVK966908�1�
*}�INSERT�
*�Read�the�subsequent�function�information�for�the�message�
PERFORM�FOFUN_TEXT_READ�USING�GL_FOFUN�
CHANGING�FOFUN_TEXT.�
MESSAGE�ID�'V1'�TYPE�'E'�NUMBER�'849'�
WITH�FOFUN_TEXT�
RAISING�ERROR.�
*{�INSERT�DEVK966908�2�
*}�INSERT�
ENDIF.�
ENDFORM.�
Do�you�have�a�SAP�SD�Question?�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
Credit�Mgmt�Dynamic�checking�
-----Original�Message-----�
Subject:�Credit�Mgmt�Dynamic�checking�
-----------------------�Page�227-----------------------
From:�Richard�Dragani�
Hi�credit�experts,�
Does�anyone�know�how�I�can�automatically�re-execute�a�dynamic�credit�check�a�
few�days�prior�to�shipment�for�future�dated�sales�orders.�Any�ideas�would�be�
appreciated.�
Rich�Dragani�
-----Reply�Message-----�
Subject:�Re:�LOG:�Credit�Mgmt�Dynamic�checking�
From:�Swami�Subramanyan�
Program�RVKRED08?�Or�manually�execute�function�module�
SD_ORDER_CREDIT_RECHECK.�
Regards�
Swami�
-----Reply�Message-----�
Subject:�Re:�Credit�Mgmt�Dynamic�checking�
From:�Leslie�Paolucci�
We�check�credit�at�the�time�of�the�delivery�(at�delivery�creation�and�before�
picking)�and�use�the�blocked�sales�doc�process/list�to�release�them.�This�can�be
�
set�up�in�customizing�under�risk�management->�credit�management.�
-----End�of�Reply�Message-----�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
http://www.sap-img.com�
Sales�value�field�in�not�getting�updated�after�
creating�the�billing�
-----Original�Message-----�
Subject:�Sales�value�field�in�not�getting�updated�after�creating�the�billing�
we�are�on�4.6b.�we�are�going�for�credit�management�but�facing�one�problem.�in�
fd32-�
customer�credit�management�change�-�the�sales�value�feild�in�not�getting�
updated�after�
creating�the�billing.�
eg.�when�i�create�the�order�-�the�order�value�get�updated�in�the�sales�value�in�
fd32.�after�
creating�the�delivery�-�that�value�remains�same�in�the�feild�of�sales�value.�but
�
when�i�am�
going�for�billing�(delivery�related),�the�bill�value�is�appearing�in�'receivable
s'�but�
the�amount�
in�'sales�value'�is�not�getting�reduced.�because�of�this�the�credit�exposure�is�
increasing�
continuously.�
update�group�for�corrosponding�credit�ctrl�area�is�12.�also�the�item�is�mark�for
�
credit�
-----------------------�Page�228-----------------------
update.�
can�anyone�tell�the�missing�link?�
thanking�in�advance�
-----Reply�Message-----�
Subject:�RE:�Sales�value�field�in�not�getting�updated�after�creating�the�billing
�
Hi,�
You�need�to�check�couple�of�settings�like:�
1.�Your�customer�should�be�assigned�the�credit�control�area.�
2.�In�your�Item�Category�Credit�should�be�active.�
Regards,�
-----Reply�Message-----�
Subject:�RE:�Sales�value�field�in�not�getting�updated�after�creating�the�billing
�
customer�is�assign�to�concorn�CCA�and�item�category�is�mark�for�credit�active�
-----Reply�Message-----�
Subject:�RE:�Sales�value�field�in�not�getting�updated�after�creating�the�billing
�
Hi,�
Check�the�credit�update�group�in�the�transaction�OB45.�The�credit�update�group�
controls�
when�the�values�of�open�sales�orders,�deliveries�and�billing�documents�are�
updated.�It�
should�be�'000012'.�
Further�also�refer�to�the�OSS�note�18613.�
Have�fun�
-----End�of�Message-----�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
http://www.sap-img.com�
Difference�Between�Simple�and�Automatic�
Credit�Check�Types�
Explain�in�detail�difference�between�simple�and�automatic�credit�check�
types.���In�automatic�check,�difference�between�static�and�dynamic�
checks.�
SIMPLE�CREDIT�CHECK�:�Tr.Code�-�FD32�
It�Considers�the�Doc.Value�+�Open�Items.�
Doc.Value�:�Sales�Order�Has�been�saved�but�not�delivered�
Open�Item�:�Sales�Order�has�been�saved�,�Delivered,�Billed�&�Transfered�to�FI,�
but�not�received�the�payment�from�the�customer.�
Eg:�Customer�Credit�Limit�is����Rs.1,00,000/-�
�����Suppose�Doc.Value�+�Open�Item�Value�is�Rs.1,10,000/-�
Here�credit�limit�exceeds�then�system�reacts.�
Options�:�A)�Warning�Message�
��������B)�Error�Message�(Sales�Order�won't�be�saved)�
��������C)�Error�Message�with�Delivery�Block�
-----------------------�Page�229-----------------------
AUTOMATIC�CREDIT�CHECK�:�Give�extra�credit�facilities�to�the�particular�
customer.�
STATIC�CREDIT�LIMIT�DETERMINATION�:Checking�Group�+�Risk�Catageory�+�
Credit�Control�Area.�
A)�Credit�Checking�Groups�:�Types�of�Checking�Groups.�
��01)�Sales�
��02)�Deliveries�
��03)�Goods�Issue�
At�all�the�above�3�levels�orders�can�be�blocked.�
B)�Risk�Catageory�:�Based�on�the�risk�catageories�company�decide�how�much�
credit�has�to�give�to�the�customer.�
HIGH�RISK�(0001)�:�LOW�CREDIT�
LOW�RISK��(0002)�:�MORE�CREDIT�
MEDIUM�RISK(0003)�:�Average�Credit�
Static�Credit�Check�it�checks�all�these�doc�value�&�check�with�the�credit�limit�
1)�Open�Doc.Value�/�Sales�Order�Value�:�Which�is�save�but�not�delievered�
2)�Open�Delivery�Doc.Value�:�Which�is�delivered�but�not�billed�
3)�Open�Billing�Doc.Value�:�Which�is�billed�but�not�posted�to�FI�
4)�Open�Item�:�Which�is�transfered�to�FI�but�not�received�from�the�customer.�
DYNAMIC�CREDIT�CHECK�:�1)�Open�Doc�
�������������������������������������2)�Open�Delivery�
�������������������������������������3)�Open�Billing�
�������������������������������������4)�Open�Items�
�������������������������������������5)�Horizon�Period�=�Eg.3Months�
Here�the�System�will�not�consider�the�above�1,2,3&�4�values�for�the�lost�3�
months�
Then�assign�the�Sales�Doc�&�Del�Documents.�
Sales�Doc.Type(OR)�+�credit�Check(0)�+�Credit�Group�(01)�
Credit�Limit�Check�for�Delivery�Type�:�Del.Type�(LF)�+�Del�Credit�
Group���(02)�+�Goods�Issue�Credit�Group�(03)�
Set�Up�for�Credit�Card�Payment�Processing�
Given�below�is�the�set�up�for�credit�card�payment�processing:�
Set�Up�Credit�Control�Areas:�
Define�Credit�Control�Area�
Transaction:�OB45�
Tables:�T014�
Action:�Define�a�credit�control�area�and�its�associated�currency.���The�Update�
Group�should�be�„00012‟.��This�entry�is�required�so�the�sales�order�will�calculate�
the�value�to�authorize�
-----------------------�Page�230-----------------------
Assign�Company�Code�to�Credit�Control�Area�
Transaction:�OB38�
Tables:�T001�
Action:�Assign�a�default�credit�control�area�for�each�company�code�
Define�Permitted�Credit�Control�Area�for�a�Company�
Code�
Transaction:�
Tables:�T001CM�
Action:�For�each�company�code�enter�every�credit�control�area�that�can�be�used�
Identify�Credit�Price�
Transaction:�V/08�
Tables:�T683S�
Action:�Towards�the�end�of�the�pricing�procedure,�after�all�pricing�and�tax�
determination,�create�a�subtotal�line�to�store�the�value�of�the�price�plus�any�
sales�tax.��Make�the�following�entries:�
Sub�to:��“A”�
Reqt:��“2”�
AltCTy:��“4”�
Automatic�Credit�Checking�
Transaction:�OVA8�
Tables:�T691F�
Action:�Select�each�combination�of�credit�control�areas,�risk�categories�and�
document�types�for�which�credit�checking�should�be�bypassed.��You�need�to�
mark�the�field�“no�Credit�Check”�with�the�valid�number�for�sales�documents.�
Set�Up�Payment�Guarantees�
Define�Forms�of�Payment�Guarantee�
Transaction:�OVFD�
Tables:�T691K�
Action:�R/3�is�delivered�with�form�“02”�defined�for�payment�cards.�����Other�than�
the�descriptor,�the�only�other�entry�should�be�“3”�in�the�column�labeled��
“PymtGuaCat”�
Define�Payment�Guarantee�Procedure�
Transaction:�
Tables:�T691M/T691O�
Action:�Define�a�procedure�and�a�description.�
Forms�of�Payment�Guarantee�and�make�the�following�entries�Sequential�
Number��“1”�
Payment�Guarantee�Form�“02”�
Routine�Number�����“0”����Routine�Number�can�be�used�to�validate�payment�card�
presence.�
Define�Customer�Payment�Guarantee�Flag�
Transaction:�
Tables:�T691P�
Action:�Define�a�flag�to�be�stored�in�table.�
Create�Customer�Payment�Guarantee�=�“Payment�Card�Payment�Cards�(All��
Customers�can�use�Payment�Cards)”.�
-----------------------�Page�231-----------------------
Define�Sales�Document�Payment�Guarantee�Flag�
Transaction:�
Tables:�T691R�
Action:�Define�the�flag�that�will�be�associated�with�sales�document�types�that�
are�relevant�for�payment�cards�
Assign�Sales�Document�Payment�Guarantee�Flag�
Transaction:�
Tables�:�TVAK�
Action:�Assign�the�document�flag�type�the�sales�documents�types�that�are�
relevant�for�payment�cards.�
Determine�Payment�Guarantee�Procedure�
Transaction:�OVFJ�
Tables:�T691U�
Action:�Combine�the�Customer�flag�and�the�sales�document�flag�to�derive�the�
payment�guarantee�procedure�
Payment�Card�Configuration�
Define�Card�Types�
Transaction:�
Tables:�TVCIN�
Action:�Create�the�different�card�types�plus�the�routine�that�validates�the�card
�
for�length�and�prefix�(etc…)�
Visa�,�Mastercard,�American�Express,�and�Discover�
Create�the�following�entries�for�each�payment�card�
AMEX��American�Express�ZCCARD_CHECK_AMEX�Month�
DC���Discover�Card��ZCCARD_CHECK_DC��������Month*****�
MC���Mastercard��ZCCARD_CHECK_MC��������Month�
VISA��Visa���ZCCARD_CHECK_VISA�������Month�
The�Routines�can�be�created�based�on�the�original�routines�delivered�by�SAP.�
*****SAP�does�not�deliver�a�card�check�for�Discover�Card.�We�created�our�own�
routine.�
Define�Card�Categories�
Transaction:�
Tables:�TVCTY�
Action:�Define�the�card�category�to�determine�if�a�
payment�card�is�a�credit�card�or�a�procurement�card.�
Create�the�following�two�entries�
Cat�Description��One�Card��Additional�Data�
CC�Credit�Cards���No-check��No-check�
PC�Procurement�Cards�No-check�����Check�
Determine�Card�Categories�
Transaction:�
Tables:�TVCTD�
Action:�For�each�card�category�map�the�account�number�range�to�a�card�
category.��Multiple�ranges�are�possible�for�each�card�category�or�a�masking�
technique�can�be�used.���Get�the�card�number�ranges�from�user�community.�
Below�is�just�a�sample�of�what�I�am�aware�are�the�different�types�of�cards.�
-----------------------�Page�232-----------------------
Visa�Credit��Expires�in�7�days.�
�����400000����405500�
�����405505����405549�
�����405555����415927�
�����415929����424603�
�����424606����427532�
�����427534����428799�
�����428900����471699�
�����471700����499999�
�Visa�Procurement����Expires�in�7�days.�
�����405501����405504�
�����405550����405554�
�����415928����415928�
�����424604����424605�
�����427533����427533�
�����428800����428899�
�Mastercard�Credit�Expires�in�30�days�
�����500000����540499�
�����540600����554999�
�����557000����599999�
�Mastercard�Procurement�Expires�in�30�days�
�����540500����540599�
�����555000����556999�
�American�Express�Credit�Expires�in�30�days�
�����340000����349999�
�����370000����379999�
�Discover�Card�Credit�Expires�in�30�days�
�����601100����601199�
Set�Sales�Documents�to�accept�Payment�Card�Information�Transaction:�
Tables:�TVAK�
Action:�Review�the�listing�of�Sales�Document�types�and�enter�“03”�in�the�column��
labeled�“PT”�for�each�type�which�can�accept�a�payment�card�
Configuration�for�Authorization�Request�
Maintain�Authorization�Requirements�
Transaction:�OV9A�
Tables:�TFRM�
Action:�Define�and�activate�the�abap�requirement�that�determines�when�an�
authorization�is�sent.��Note�that�the�following�tables�are�available�to�be�used�
in�
the�abap�requirement�(VBAK,�VBAP,�VBKD,�VBUK,�and�VBUP).�
Define�Checking�Group�
Transaction:�
Tables:�CCPGA�
Action:�Define�a�checking�group�and�enter�the�
description.��Then�follow�the�below�guidelines�for�the�remaining�fields�to�be�
filled.�
AuthReq�Routine�901�is�set�here.�
-----------------------�Page�233-----------------------
PreAu��If�checked�R/3�will�request�an�authorization�for�a�.01�and�the�
authorization�will�be�flagged�as�such.�(Insight�does�not�use�pre-authorization�
check).�
A�horizon�This�is�the�days�in�the�future�SAP�will�use�to�determine�the�value�to�
authorize�
(Insight�does�not�use�auth�horizon�period).�
Valid��You�will�get�warning�message�if�the�payment�card�is�expiring�within�30�
days�of�order�entry�date.�
Assign�Checking�Group�to�Sales�Document�
Transaction:�
Tables:�TVAK�
Action:�Assign�the�checking�group�to�the�sales�order�types�relevant�for�payment�
cards�
Define�Authorization�Validity�Periods�
Transaction:�
Tables:�TVCIN�
Action:�For�each�card�type�enter�the�authorization�validity�period�in�days.�
AMEX�American�Express�30�
DC�Discover�card��30�
MC�Master�card��30�
VISA�Visa���7�
Configuration�for�clearing�houses�
Create�new�General�Ledger�Accounts�
Transaction:�FS01�
Tables:�
Action:�Two�General�Ledger�accounts�need�to�be�created�for�each�payment�card�
type.��One�for�A/R�reconciliation�purposes�and�one�for�credit�card�clearing.�
Maintain�Condition�Types�
Transaction:�OV85�
Tables:�T685�
Action:�Define�a�condition�type�for�account�determination�and�assign�it�to�acces
s�
sequence�“A001”�
Define�account�determination�procedure�
Transaction:�OV86�
Tables:�T683�/�T683S�
Action:�Define�procedure�name�and�select�the�procedure�for�control.����Enter�the
�
condition�type�defined�in�the�previous�step.�
Assign�account�determination�procedure�
Transaction:�
Tables:�
Action:�Determine�which�billing�type�we�are�using�for�payment�card�process.�
Authorization�and�Settlement�Control�
Transaction:�
Tables:�TCCAA�
Action:�Define�the�general�ledger�accounts�for�reconciliation�and�clearing�and�
assign�the�function�modules�for�authorization�and�settlement�along�with�the�
-----------------------�Page�234-----------------------
proper�RFC�destinations�for�each.�
Enter�Merchant�ID‟s�
Transaction:�
Tables:�TCCM�
Action:�Create�the�merchant�id‟s�that�the�company�uses�to�process�payment��
cards�
Assign�merchant�id‟s�
Transaction:�
Tables:�TCCAA�
Action:�Enter�the�merchant�id‟s�with�each�clearinghouse�account�
Implement�the�Product�Allocation�
Functionality�
We�are�required�to�implement�product�allocation�functionality�in�SAP�
R/3�(Enterprise�Version).�
We�tried�to�do�the�elaborate�steps�as�per�the�implementation�guide�but�
are�not�successful.�Can�you�kindly�help�by�giving�the�simple�steps�for�
implementation.�
Please�see�if�the�following�helps:�
Configuration�Overview;�Allocation�Specific�Usage�
1.Allocation�Procedure�(OV1Z)�The�product�allocation�procedure�is�the�parent�of�
the�entire�allocation�process.�All�materials�that�are�to�be�included�in�the�
allocation�scheme�are�required�to�have�an�allocation�procedure�assigned�to�it�in
�
the�material�master.�In�addition,�as�of�release�4.0,�it�is�in�the�procedure�that
�
the�method�of�allocation�is�defined.�The�user�has�the�opportunity�to�set�an�
indicator�to�identify�their�choice�of�two�different�methods�(discrete�and�
cumulative�allocation)�to�evaluate�the�quantities�to�be�considered�for�product�
allocation.�
2.Allocation�Object�(OV2Z)�The�allocation�object�is�the�root�level�of�the�
allocation�process�where�actual�data�is�entered�and�planned�in�LIS.�The�object�
allows�the�user�to�further�break�down�a�procedure�into�smaller�parts�for�future�
validation�of�components�comprising�a�specific�material�
3.Allocation�Hierarchy�Mapping�(OV3Z)�Primarily,�this�transaction�permits�the�
assignment�of�an�allocation�procedure�to�an�LIS�information�structure.�
Secondly,�a�character�is�assigned�to�the�information�structure�to�permit�
collective�planning.�Finally,�the�user�can�assign�a�step�level�to�the�procedure�
and�information�structure�to�sequence�the�order�in�which�allocation�quantities�
are�checked.�This�functionality�allows�the�user�the�opportunity�to�check�product
�
allocation�against�several�product�allocation�scenarios,�before�the�required�
quantity�is�confirmed�
4.Define�Consumption�Periods�(OV5Z)�The�allocation�consumption�periods�
functionality�is�only�valid�if�the�allocation�method�flag�has�been�set�(OV1Z).�I
f�
you�have�de-selected�the�method�field,�this�functionality�is�not�available.�The�
-----------------------�Page�235-----------------------
consumption�window�indicates�the�number�of�past�and�future�periods�to�be�used�
in�the�allocation�check.�
5.Control�Product�Allocation�(OV4Z)�In�order�for�the�allocation�process�to�
function�properly,�allocation�control�records�are�created�primarily�to�map�
allocation�procedure�steps�to�their�corresponding�objects�so�that�the�allocation
�
data�records�can�be�located�for�validation.�Secondly,�validity�periods�must�be�
established�to�indicate�when�the�allocation�control�records�are�active.�Finally,
�
the�user�has�the�option�of�establishing�a�conversion�factor�per�allocation�contr
ol�
record�to�accommodate�BOM�listings�of�constrained�materials�
6.Activate�Allocation�for�Requirement�Class�(OVZ0)�In�order�to�turn�on�
allocation�in�the�standard�order�processing�functionality,�the�requirements�clas
s�
must�have�a�flag�indicating�that�allocation�is�relevant.�
7.Activate�Allocation�for�Schedule�Line�Category�(OVZ8)�In�order�to�turn�on�
allocation�in�the�standard�order�processing�functionality,�the�schedule�line�mus
t�
have�a�flag�indicating�that�allocation�is�relevant�
8.Create�Planning�Hierarchy�(MC61)�In�order�to�adequately�establish�allocation�
quantities,�the�user�must�initially�determine�the�level�at�which�the�allocation�
is�
to�take�place�and�the�aggregation�factor�of�the�allocation�quantities.�In�this�
step,�the�levels�for�the�collective�allocation�search�procedure�are�also�
identified.�
9.Generate�Masking�Character�(OV7Z)�Upon�completion�of�the�level�
determination�for�the�planning�hierarchy,�the�collective�allocation�masking�
character�must�be�generated�to�allow�aggregation�indicators�to�be�established.�
This�transaction�simply�reads�the�hierarchy�established�in�the�planning�table�an
d�
then�generates�a�collective�mask�character�for�each�level�of�the�hierarchy�
10.Modify�Planning�Hierarchy�(MC62)�This�step�is�a�repeat�of�MC61�where�the�
initial�hierarchy�was�established.�In�order�to�complete�the�hierarchical�set�up,
�
the�collective�allocation�(mask�character)�hierarchy�must�now�be�maintained�
with�the�appropriate�aggregation�factors�
11.Allocation�Procedure�Assignment�to�Material�Master�(MM02)�At�the�root�level�
of�the�allocation�process�are�the�materials.�Each�material�that�is�to�be�
considered�in�allocation�scenario�must�be�mapped�to�an�allocation�procedure.�In�
order�entry,�then,�when�a�material�is�entered�with�a�valid�allocation�procedure�
in�the�material�master,�the�allocation�data�is�verified�prior�to�confirming�the�
line�
item�ordered�
12.List�of�Suitable�Structures�(OV9Z)�This�report�is�used�to�identify�potential�
LIS�
information�structures�that�can�be�used�in�the�product�allocation�process.�This�
report�simply�reads�through�the�data�dictionary�and�selects�all�the�active�
information�structures�that�contain�the�field�product�allocation�object�(KONOB)�
as�the�first�field.�This�data�can�then�be�utilized�in�the�mapping�transaction�
(OV3Z)�to�link�the�allocation�procedure�step�to�an�information�structure�
(previous�step).�
Fast�Links:�
Get�help�for�your�SAP�SD�problems�
Do�you�have�a�SAP�SD�Question?�
-----------------------�Page�236-----------------------
Sending�a�billing�document�by�e-mail�
First,�your�SAP�system�must�be�configure�by�the�basis�people�in�order�for�you�to
�
send�an�external�mail.�
Whether�it�can�send�pdf�or�other�file�format�will�depends�on�the�Mail�Server�you
�
are�using.�
The�basis�people�must�also�maintain�the�conversion�parameters�so�that�SAP�
knows�how�to�convert�the�billing�documents�to�be�send�as�a�pdf�file�or�other�
desired�format�specified�by�your�company.�
Finally,�you�have�define�the�IMG�in�Maintain�Output�Determination�for�
Billing�Documents�(Output�type�MAIL)�
�SAP�Customizing�Picking�Output�
From�Release�4.5A,�the�system�does�no�longer�display�the�actions�for�SD�
picking�in�the�implementation�guide.�
If�you�want�to�use�the�picking�list�according�to�the�"old"�procedure,��you�can�
maintain�the�list�as�follows:�
�o��Carry�out�Transaction�V/38�to�maintain�the�output�types.�
�o��Carry�out�Transaction�OVLT�to�assign�the�picking�list�types�to�the�
����shipping�points.�
�o��Carry�out�Transaction�V/53�to�assign�the�picking�lists�to�own�
����forms�and�programs.�
Program�for�Sales�Order�by�Customer,�Date,�
Sales�
Sales�Order�by�Organisation,�Customer�-�To�create�the�Sales�Order�by�
More�no�of�Date's�
User's�can�easily�take�the�Report�from�this�by�selecting�Different�kinds�like�
Customer�Specific�[And/Or]�Sales�Organisation�Specific�[And/Or]�duration�of�
date�but�Here�Date�is�Mandatory�Fields�user�must�have�to�give�date�as�a�
selection�criteria�
In�Second�level�this�report�will�interact�with�user�where�they�can�select�date�t
o�
see�the�full�Details�of�Sales�Order�
Selection�
-�Sales�Organisation�
-�Date�
-�Customer�this�will�be�usefull�when�Selecting�the�Checkbox�
Standard�Variants�
-�Output�
-�Sales�Order�
Example�
Date������������SalesOrderNo�����Material���Amount����Currency�
10.01.2007�����8530���������������732��������1000�������INR�
-----------------------�Page�237-----------------------
*&---------------------------------------------------------------------*�
*&�Report���ZCHE_SALES_ORDER�
*&--------Done�by�V.Chellavelu�on�11.01.2007�
--------------------------*�
REPORT���zche_sales_order���������������������������.�
****************************Declarations********************************�
TABLES:�vbkd,vepvg.",vbak,vbap,vbpa,vakpa,�vapma.�
DATA:�BEGIN�OF�sal�OCCURS�0,�
�������ch�TYPE�checkbox,�
������vbeln�LIKE�vbak-vbeln,�"�sales�document�
�������netwr�LIKE�vbak-netwr,�"Net�Value�of�the�SalesOrder�
������matnr�LIKE�vbap-matnr,�"material�no.�
������waerk�LIKE�vbak-waerk,�"curr.�
�������dat���LIKE�vbak-erdat,�"date.�
������END�OF�sal.�
DATA:�newsal�LIKE�sal�OCCURS�0�WITH�HEADER�LINE.�
DATA:�amount�LIKE�vbak-netwr,�date2(15),date3(8),date4(1),�
�������date5(2),date6(2).�
DATA:�lin�LIKE�sy-curow�VALUE�1,"Screens,�vertical�cursor�position�at�
������������������������������������"PAI�available�in�SYST�struc.�
�������checkbox���������TYPE�c�����������������,�
�������dat�LIKE�vbak-erdat.�
*******************Selection**Screen**Design****************************�
SELECTION-SCREEN�BEGIN�OF�BLOCK�blk1�WITH�FRAME�TITLE�text-001.�
PARAMETERS:�vkorg�LIKE�vepvg-vkorg,�
�������������vtweg�LIKE�vepvg-vtweg,�
�������������spart�LIKE�vepvg-spart.�
SELECT-OPTIONS�date�FOR�vbkd-bstdk�DEFAULT�sy-datum�TO�sy-datum�
������������������������������������������������OBLIGATORY.�
SELECTION-SCREEN�END�OF�BLOCK�blk1.�
SELECTION-SCREEN�BEGIN�OF�BLOCK�blk2�WITH�FRAME�TITLE�text-002.�
SELECTION-SCREEN�BEGIN�OF�LINE.�
SELECTION-SCREEN�POSITION�10.�
PARAMETERS:�chk1�AS�CHECKBOX.�
SELECTION-SCREEN�POSITION�20.�
PARAMETERS:�kunnr1�LIKE�vbpa-kunnr.�
SELECTION-SCREEN�END�OF�LINE.�
SELECTION-SCREEN�END�OF�BLOCK�blk2.�
********************First**Level**Operation*****************************�
IF�chk1�<>�'X'.�
��IF�vkorg�<>�''.�
����PERFORM�organisation.�
��ELSE.�
����PERFORM�organisation_else.�
��ENDIF.�
ELSE.�
��IF�vkorg�<>�''.�
����PERFORM�cus_orga.�
-----------------------�Page�238-----------------------
��ELSE.�
�����PERFORM�cus_orga_else.�
��ENDIF.�
ENDIF.�
*�Displaying�the�contents�which�is�selected�from�table�by�
*��-selection�conditions�
SORT�sal�BY�dat.�
LOOP�AT�sal.�
��ON�CHANGE�OF�sal-dat.�
*�����FORMAT�HOTSPOT�ON.�
�����IF�sy-tabix�=�1.�
�������WRITE:�sy-vline,�sal-ch�AS�CHECKBOX,sal-dat�.�
�������CLEAR�amount.�
����ELSE.�
�������WRITE:sy-vline,�amount,/�sy-vline,�sal-ch�AS�CHECKBOX,sal-dat.�
�������CLEAR�amount.�
����ENDIF.�
��ENDON.�
��amount�=�amount�+�sal-netwr.�
��AT�LAST.�
����WRITE:sy-vline,�amount.�
����ULINE.�
�����SUM.�
*�����FORMAT�HOTSPOT�OFF.�
�����FORMAT�COLOR�=�3.�
����WRITE:/�'�Total�Amount:',�sal-netwr�UNDER�amount.�
��ENDAT.�
ENDLOOP.�
**********************Interaction�with�report**************************�
SET�PF-STATUS�'BANU'.�"�To�create�Application�ToolBar�for�Display�
Button�
*�����������������������������To�verify�Double�click�on�BANU�
AT�USER-COMMAND.�"�This�will�execute�after�pressing�Display�Button�
��CASE�sy-ucomm.�
����WHEN�'DISP'.�
�����free�newsal.�
�������DO.�
���������READ�LINE�lin�FIELD�VALUE�sal-ch�INTO�checkbox.�
���������IF�sy-subrc�NE�0.�EXIT.�ENDIF.�
���������IF�checkbox�=�'X'.�
�����������PERFORM�datecon.�
�����������PERFORM�process.�
���������ENDIF.�
���������lin�=�lin�+�1.�
�������ENDDO.�
�������PERFORM�selection.�
��ENDCASE.�
************************�SUB�ROUTINE�Area�
******************************�
*This�Process�SubRoutine�will�assign�the�values�from�current�
-----------------------�Page�239-----------------------
*���-InternalTable�(sal)�into�other�IT(newsal),�by�date�which�is�
*����������-�selected�by�CheckBox�
FORM�process.�
��LOOP�AT�sal�WHERE�dat�=�dat.�
����newsal-ch������=�'X'.�
����newsal-vbeln�=�sal-vbeln.�
����newsal-netwr�=�sal-netwr.�
����newsal-matnr�=�sal-matnr.�
����newsal-waerk�=�sal-waerk.�
����newsal-dat�����=�sal-dat.�
����APPEND�newsal.�
��ENDLOOP.�
ENDFORM.�����������������������"process�
*&---------This�will�display�the�values�for�selected�dates�from�new�--*�
*---------------------internal�Table�(newsal)-------------------------*�
*&�������Form��SELECTION�
*&--------------------------------------------------------------------*�
*---------------------------------------------------------------------*�
FORM�selection.�
��ULINE.�
��FORMAT�COLOR�=�1.�
��WRITE:sy-vline,'Date',AT�14�sy-vline,�'Order�NO',�AT�27�sy-vline,�
'Order�Material',�AT�48�sy-vline,'Order�Value(AMT)�Currency��������'.�
��FORMAT�COLOR�OFF.�
��ULINE.�
��LOOP�AT�newsal.�
����ON�CHANGE�OF�newsal-dat.�
�������IF�sy-tabix�<>�1.�
���������WRITE:/�sy-vline,�AT�14�sy-vline,AT�27�sy-vline,AT�48�sy-vline.�
����WRITE:/�sy-vline,newsal-dat,sy-vline,AT�27�sy-vline,AT�48�sy-vline.�
�������ELSE.�
�����WRITE:�sy-vline,newsal-dat,sy-vline,AT�27�sy-vline,AT�48�sy-vline.�
�������ENDIF.�
����ENDON.�
����WRITE:/�sy-vline,�AT�14�sy-vline,newsal-vbeln,sy-vline,�
�������newsal-matnr,�sy-vline,�newsal-netwr,�newsal-waerk.�
����AT�LAST.�
�������SUM.�
�������ULINE.��FORMAT�COLOR�=�3.�
�������WRITE:/�sy-vline,�AT�15�'Total�Amount�for�selected�month:',�
����������������������newsal-netwr�UNDER�newsal-netwr.�
�������FORMAT�COLOR�OFF.�
�������ULINE.�
����ENDAT.�
��ENDLOOP.�
��lin�=�1.�
��FREE�newsal.�
ENDFORM.�����������������������"SELECTION�
*�This�Date�convertion�is�must�for�pick�the�particular�Date�from�the�
*�����-displayed�line,�and�here�we�are�reversing�the�Date�like�
YYYY/MM/DD�
*��-because�to�Check�or�assign�the�date�we�need�to�give�in�reverse�
order�
-----------------------�Page�240-----------------------
*&--------------------------------------------------------------------*�
*&�������Form��DATECON�
*&--------------------------------------------------------------------*�
*��������text�
*---------------------------------------------------------------------*�
FORM�datecon.�
��date2�=�sy-lisel(17).�
��SHIFT�date2�LEFT�BY�4�PLACES.�
��WHILE�date2�<>�''.�
����SHIFT�date2�RIGHT.�
����date4�=�date2+11.�
�����IF�date4�<>�'.'.�
�������CONCATENATE�date4�date3�INTO�date3.�
����ENDIF.�
��ENDWHILE.�
��date5�=�date3(2).�
��date6�=�date3+2.�
��date3�=�date3+4.�
��CONCATENATE�date3�date6�date5�INTO�date3.�
��dat�=�date3.�
*��SORT�dat�BY�dat.�
*��DELETE�ADJACENT�DUPLICATES�FROM�dat�COMPARING�dat.�
ENDFORM.�����������������������"DATECON�
*�Here�we�are�doing�different�kinds�of�selections�by�the�EndUser's�
needs�
*&---------When�user�selectiong�an�Sales�Organisation-----------------*�
*&�������Form��ORGANISATION�
*&--------------------------------------------------------------------*�
*��������text�
*---------------------------------------------------------------------*�
FORM�organisation.�
��SELECT�f~vbeln�p~matnr�c~netwr�c~waerk�p~audat�INTO�(sal-vbeln,�
sal-matnr,�sal-netwr,sal-waerk,�sal-dat)�FROM�(�vakpa�AS�f�INNER�JOIN�
�������vbak�AS�c�ON�f~vbeln�=�c~vbeln�)�INNER�JOIN�vapma�AS�p�ON�
f~vbeln�=�p~vbeln�WHERE��p~audat�IN�date�AND�p~vkorg�=�vkorg.�
����APPEND�sal.�
��ENDSELECT.�
ENDFORM.�����������������������"ORGANISATION�
*&---------Without�Sales�Organisation�i.e�All�Organisation------------*�
*&�������Form��ORGANISATION_ELSE�
*&--------------------------------------------------------------------*�
*��������text�
*---------------------------------------------------------------------*�
FORM�organisation_else.�
��SELECT�f~vbeln�p~matnr�c~netwr�c~waerk�p~audat�INTO�(sal-vbeln,�
sal-matnr,�sal-netwr,sal-waerk,�sal-dat)�FROM�(�vakpa�AS�f�INNER�JOIN�
����vbak�AS�c�ON�f~vbeln�=�c~vbeln�)�INNER�JOIN�vapma�AS�p�ON�
����f~vbeln�=�p~vbeln�WHERE��p~audat�IN�date.�
����APPEND�sal.�
��ENDSELECT.�
ENDFORM.�����������������������"ORGANISATION_ELSE�
-----------------------�Page�241-----------------------
*&------------When�Selecting�Customer�by�choosing�CheckBox------------*�
*&������Form��CUS_ORGA�
*&--------------------------------------------------------------------*�
*�������text�
*---------------------------------------------------------------------*�
FORM�cus_orga.�
��SELECT�f~vbeln�p~matnr�c~netwr�c~waerk�p~audat�INTO�(sal-vbeln,�
sal-matnr,�sal-netwr,sal-waerk,�sal-dat)�FROM�(�vakpa�AS�f�INNER�JOIN�
��������vbak�AS�c�ON�f~vbeln�=�c~vbeln�)�INNER�JOIN�vapma�AS�p�ON�
�������f~vbeln�=�p~vbeln�WHERE�p~audat�IN�date�AND�p~vkorg�=�vkorg�AND�
�������p~kunnr�=�kunnr1.�
����APPEND�sal.�
��ENDSELECT.�
ENDFORM.���������������������"CUS_ORGA�
*&------------Without�Customer�by�without�choosing�CheckBox-----------*�
*&������Form��CUS_ORGA_ELSE�
*&--------------------------------------------------------------------*�
*�������text�
*---------------------------------------------------------------------*�
FORM�cus_orga_else.�
��SELECT�f~vbeln�p~matnr�c~netwr�c~waerk�p~audat�INTO�(sal-vbeln,�
sal-matnr,�sal-netwr,sal-waerk,�sal-dat)�FROM�(�vakpa�AS�f�INNER�JOIN�
����vbak�AS�c�ON�f~vbeln�=�c~vbeln�)�INNER�JOIN�vapma�AS�p�ON�
f~vbeln�=�p~vbeln�WHERE�p~audat�IN�date�AND�p~kunnr�=�kunnr1.�
����APPEND�sal.�
��ENDSELECT.�
By�Chellavelu�.V�-�[email protected]�
Duplicate�customer�purchase�order�
If�you�are�facing�a�problem�with�duplicate�customer�purchase�order�as�your�
company�does�not�allowed�a�same�customer�purchase�order�with�the�same�sales�
order�type.�
You�can�activated�the�check�for�duplicate�purchase�order�with�"VOV8".�
In�the�General�Control�Section,�look�for�the�field�Check�Purchase�Order�
No�and�put�in�"A".�
Best�regards,�
Default�First�Date�is�not�Today�
When�end�user�created�a�new�sales�order�with�VA01,�default�First�Date�
wasn't�today,�why?�
Note:�
1.�Before�today,�default�First�Date�was�always�today.�
2.�Nobody�change�system�configuration.�
Although�you�mention�that�nobody�change�the�system�configuration,�it�is�very�
unlikely�that�the�system�will�mis-behaved�after�one�day.�
Usually,�after�checking,�you�will�find�that�someone�have�actually�change�the�
configuration�as�it�could�not�be�a�software�bug�since�you�have�been�using�it�for
�
-----------------------�Page�242-----------------------
quite�sometime�without�any�problems.�
The�date�is�control�by�each�Sales�Order�Type�for�each�Sales�Document�type�
whether�is�it�a�
-�OR�-�Standard�Order,�
-�RE�-�Returns�etc.�
Verify�the�Sales�order�type�configuration�with�the�following�path:�
IMG:�Sales�and�Distribution�-->�Sales�-->�Sales�Docs�-->�Sales�Doc�Hdr�-->�
Define�Sales�Doc�Types�(transaction�vov8)�will�let�you�control�this�by�sales�
document�type.�
There�is�one�field�(Lead�time�in�days)�which�"specify�the�number�of�days�after�
the�current�date�that�the�proposal�for�the�requested�delivery�date�in�the�sales�
document�should�be".�
This�should�be�blank�if�you�want�the�system�to�propose�current�day�for�delivery�
date.�
Auto�proposed�all�the�dates�when�creating�
Sales�Order�
How�can�I�make�the�system�auto�create�all�the�Sales�Order�date�during�
creation?�
Each�Sales�Order�can�have�different�date�proposal�settings.�
Follows�this�step�to�set�the�default�Sales�Order�Type�proposal�date:�
-�Goto�VOV8,�double�click�on�sales�order�type.�
-�Look�and�tick�the�fields�Propose�delivery�date�and�Propose�PO�date.�
After�making�the�necessary�IMG�changes,�you�need�to�input�the�Delivery�Plant�
field�for�each�Materials�that�you�want�the�system�to�propose�the�default�date.�
To�change�the�Materials�field�Delivery�Plant:�
Goto�MM02,�Select�the�View�Sales:�Sales�Org.�Data�1�and�fill�in�the�Delivery�
Plant.�
Testing:�
Now,�try�creating�a�new�sales�order�for�the�material�and�SAP�will�auto�proposed�
all�the�dates�in�the�sales�order.�
Define�whether�the�Material�can�be�used�at�which�Sales�and�
Distribution�process�
Here�you�define�how�the�system�responds�when�entering�a�sales�and�
distribution�document�
with�this�material�in�the�differenet�Sales�and�Distribution�Process�Flow..�
You�can�use�the�material�status,�for�example,�to�prevent�orders�from�being�
entered�for�
parts�to�be�discontinued.�
OR�
To�temporary�block�the�creation�of�Sales�Order�for�a�certain�materials.�
Set�the�material�status�parameters�in�transaction�SM30,�Table�
Views���V_TVMS.�
Click�Maintain�and�double�click�into�the�Materials�Status�code.�
-----------------------�Page�243-----------------------
You�can�set�three�types�of�reponse�for�each�Sales�and�Distribution�process�:-�
1.��no�dialog�
2.��warning�when�entering�the�document�
3.��error�message�(that�is,�the�sales�and�distribution�document�cannot�be�
entered�on�
����the�basis�of�the�material�status)�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
Assign�a�Cost�Center�manually�in�a�Sales�Order�(VBAK-�
KOSTL)�
The�Cost�Center�Determination�settings�is�in�OVF3�-��but�there�are�some�cases�wh
ere�
the�Cost�Center�must�be�exceptionally�changed.�
If�the�document�category�for�order�type�in�IMG�VOV8�is�defined�to�be�"I"�which�b
elong�to�
order�type�FD�-�Deliv.Free�of�Charge,�then�the�field�cost�center�is�active�for�i
nput�during�
transaction�VA01.�
Alternatively,�you�can�specify�an�order�reason�and�assign�a�cost�center�to�an�or
der�reason.�
However�the�standard�SAP�works�only�at�the�header�level�though,�so�it�would�not�
work�if�cost�
center�is�needed�on�the�line�item.�
The�cost�center�are�assign�for�such�business�transactions�as�:�
-�Free�deliveries�
-�Returns�
-�Deliveries�of�advertising�materials�
You�can�also�make�cost�center�allocation�dependent�on�the�order�reason,�for�exam
ple:�
Order�reason:�Damage�in�transit�
Order�reason:�Free�sample�
Both�the�IMG�settings�are�done�in�transaction�OVF3,�either�with/without�the�orde
r�reason.�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
http://www.sap-img.com�
�Sales�and�Distribution�-�Transfer�of�
Requirements�
The�MRP�department�is�informed�about�the�quantities�and�deadlines�by�which�
incoming�orders�
should�be�delivered.�The�system�checks�the�availability�of�the�goods�based�on�
the�requested�
delivery�date�of�the�customer�and�creates�MRP�records�which�contain�all�
necessary�information�
for�passing�on�to�planning.�It�ensures�that�the�goods�are�available�in�time�
for�the�delivery.�
Materials�planning�transfers�the�reported�requirements�and�creates�orders�or�
purchase�
-----------------------�Page�244-----------------------
requisitions�from�them�etc.�
For�controlling�transfer�of�requirements,�you�have�to�carry�out�the�following�
steps:�
1.�Each�requirement�type�has�to�be�allocated�to�one�requirement�class�only.�
2.�The�transfer�of�requirements�must�be�switched�on�at�requirements�class�
level,�the�sales�
���documents�at�schedule�line�level.�
3.�You�must�define�a�check�group.�It�is�possible�to�have�this�check�group�
proposed�for�the�
���initial�creation�of�a�material�master�record.�
4.�Note�that�a�plant�must�exist�for�transfer�of�requirements�to�be�carried�
out�at�document�
���item�level.�
OVZG������-�Requirement�class�
It�specifies�the�following�points:�
-�whether�an�availability�check�and�a�transfer�of�requirements�is�carried�out�
for�a�
��transaction�(for�sales�documents,�fine�tuning�using�the�schedule�line�
category�is�possible),�
-�whether�the�requirements�are�relevant�for�MRP,�
-�the�allocation�indicator�from�the�sales�view�which�controls�the�settlement�
of�customer�
��requirements�with�requirements�
-�whether�an�item�is�to�be�settled�to�an�auxiliary�account�assignment,�
-�the�settlement�profile,�
-�the�results�analysis�key.�
�(Use�transaction�SM30�for�V_*�configuration)�
OVZH������-�Requirements�type�
V_TVEPZ_V�-�Assignment�of�requirement�type�to�Transaction�
V_TVEP_V��-�Schedule�line�category�
OVZ2������-�Define�Checking�Group�
V_TMVFU���-�Define�the�checking�group�that�the�system�proposes�when�you�
create�a�new�material�
������������master�record.�You�can�overwrite�the�default�value�for�the�
checking�group�in�the�
������������material�master�record.�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
http://www.sap-img.com�
Define�Tax�Determination�Rules�
You�specify�the�valid�tax�types�in�transaction�OVK1.��More�than�one�tax�type�
can�be�defined�for�a�country�by�defining�the�sequence.�
The�SAP�System�determines�the�taxes�automatically�within�pricing.�
In�the�standard�SAP�R/3�System,�the�elements�of�tax�calculation�are�predefined�
(for�example,�tax�condition�type�"MWST"�for�taxes�on�sales�and�purchases).�
Assign�the�plant�for�Tax�Determination�in�OX10,�using�the�country�key,�the�SAP�
-----------------------�Page�245-----------------------
System�recognizes�which�tax�type�is�valid�for�a�plant�and�thus�which�taxes�are�
relevant�when�creating�an�SD�document.�
Define�the�Customer�Taxes�in�OVK3,�you�will�maintain�the�tax�code�in�
Customer�Master.�
Define�the�Material�Taxes�in�OVK4,�which�will�then�be�maintain�in�Material�
Master.�
For�example�:-�
MWST�������GST�����������0���Tax�Exempt�
MWST�������GST�����������1���Liable�for�Taxes�
Now,�you�define�the�Tax�Determination�in�VK12.�
VK12�-�Domestic�Taxes/Export�Taxes�
Condition�Type������MWST�
Customer�Taxes�������Material�Taxes������Rate�Taxes�
�������0������������������������0��������������0�%�
�������0������������������������1��������������0�%�
�������1������������������������0��������������0�%�
�������1������������������������1��������������9�%�
In�this�example,�if�both�the�Customer�Master�and�Material�Master�Tax�code�is�1,�
Tax�will�be�included�when�you�create�the�Sales�Order.�
Tax�Code�in�Customer�Master�/�Sales�Order�
How�can�we�maintain�the�Tax�Code�(Tax�code�-�which�we�maintain�in�
MWST�Condtion�Records)�in�Customer�Master�or�in�Sales�Order?�
There�are�few�points�which�I�would�like�to�remind�you:�
1)�MWST�is�a�tax�condition�which�is�applied�to�customer�to�whom�we�are�selling.�
The�rate�of�tax�is�depend�on�various�parameteres,�whether�is�fully�liable�for�ta
x�
or�expemted�(in�case�of�Defence�Customer)�
2)�There�are�few�parameteres�which�we�apply�tax�condition.�Whether�customer�
is�tax�liable?�Whether�material�is�tax�exempted?�
For�example,�if�you�are�selling�a�goods�which�are�free�for�tax�to�any�customer,�
put�the�Tax�Indicator�(at�MMR�as�'0').�If�your�
material�is�tax�liable�pur�the�Tax�Indicator�(at�MMR�as�1).�If�your�customer�is�
not�liable�for�tax�at�all�(like�the�case�of�Indian�
Defence�organisations)�put�the�Tax�Indicator�(at�CMR�as�0)�or�1�in�case�fully�ta
x�
liable.�
3)�Now,�at�VK11�you�need�to�mainatain�your�pricning�conditions�with�all�the�
combinations�like:�
1�0�
1�1�
0�1�
0�0�
4)�While�maintaining�your�Material�Master�Records�or�Cusotmer�Master�Records,�
you�must�identify,�which�are�tax�liable�and�which�are�tax�exempeted.�
5)�In�anycase,�as�a�SAP�standard�Best�Practises,�while�processing�a�sales�order,
�
you�must�retrieve�a�Tax�condition�record�from�SAP�database�only�and�not�
entered�Manually.�Accordingly,�at�V/06,�the�MWST�condition�Defintions,�the�field
�
for�'Manual�Entries',�it�would�be�marked�as�-�D�(Not�possible�to�process�
-----------------------�Page�246-----------------------
Manually).�
Due�to�this�setting,�normally,�you�cannot�maintain�Condition�tax�code�during�
sales�order�processing.�And�in�Cusotmer�Master,�you�can�only�maintain�Tax�
Indicator�and�not�Tax�Code.�
6)�In�case�your�client�insists�for�Manual�entry�of�Tax�code�during�Sales�Order�
processing,�you�can�change�the�field�at�point�5)�above�to�C-Manual�entry�is�
priority�instead�of�D.�
Taxation�Explain�with�an�example�
I'm�assuming�that,�the�country�is�India�and�based�on�its�requirement:�
Sales�tax�is�a�state�government�revenue.�There�are�two�types�of�sales�taxes,�
Local�sales�tax�&�central�sales�tax.�Local�sales�tax�is�intra�state�whereas�CST�
is�
inter�state.�
Example�of�LST�:�Point�of�sale�i.e.�delivering�plant�&�ship�to�party�are�within�
the�
same�state.�The�rates�are�defined�by�the�respective�state�governments.�
Example�of�CST�:�The�Delivering�plant�&�Ship�to�party�geographic�locations�are�
2�different�states.�At�the�point�of�sales�from�one�state,�the�ST�goes�to�that�st
ate�
govt.�&�consignment�is�despatched�to�the�Ship�to�party.�Once�that�consignment�
is�received�at�the�ship�to�party�state,�sales�tax�will�be�levied�once�the�sales�
is�
registered�there.�For�this�case,�the�LST�that�is�applicable�by�the�Ship�to�party
�
further�will�not�be�applicable�in�all�probability�to�be�captured�in�SAP.�
Stock�transfer�:�This�does�not�attract�any�sales�tax.�The�consignment�is�
transferred�from�one�D�plant�to�another�D�plant�irrespective�of�inter/intra�stat
e�
sales.�The�invoice�that�is�accompanied�with�the�consignment�thus�shall�not�have�
any�final�value.�It's�a�zero�value�invoice,�but�the�basic�prices�needed�to�be�
mentioned.�
The�selling�organisations�normally�needs�to�register�with�the�sales�tax�authorit
y�
of�the�respective�state�to�have�a�warehouse�or�D�plant�to�avoid�the�double�
taxation�for�their�dealers/distributors.�
Now,�the�pricing�procedure�that�is�there�in�4.7�is�Factory�sale�with�formula-�
JFACT,�in�which�the�CST�condition�type�is�JIN1�&�the�LST�is�probably�JIN2.�
There�may�be�surcharge�cond�types�as�well�which�will�calculate�the�amount�on�
either�JIN1�or�JIN2.�
For�config�:�
1.SPRO�>�S&D�>�Basic�fn.�>�Pricing�>�Pricing�control�>�Define�&�assign�Pric.�
procedure�>�Maintain�Pric�proc.�
2.�The�tax�rates�are�normally�driven�from�the�Tax�classification�of�Customer�&�
Material�access.�To�do�this�config,�S&D�>Basic�fn.�>�Taxes.�You�need�to�include�
the�condition�type�for�country�IN�in�'Define�tax�determin�rule'.�
3.�Same�path�:�But�go�to�Tax�relevancy�of�master�records�where�you�configure�
the�condition�type�&�options�of�rates�that�will�flow�to�these�masters.�One�needs
�
to�understand�here�properly�as�u�need�to�have�unique�combinations�for�picking�
the�sales�tax�rates.�I�will�try�to�demonstrate�the�smallest�example.�Let's�say,�
the�LST�rates�are�2%,4%�&�0%.�I�will�have�two�options�for�material�master�
here.�1�for�taxable�&�2�for�not�taxable.�
For�customer�master,�I�will�have�1-LST�2%,�2-LST4%�&�3-LST0%.�When�I�
-----------------------�Page�247-----------------------
create�master�records�for�LST�thru�VK11�for�JIN2,�I�will�chose�the�access�where�
the�combinations�of�customer�&�material�tax�classifications�are�available.�If�th
is�
access�does�not�exist�create�it�under�an�access�sequence.�But�normally�this�is�
standard.�The�condition�records�will�look�like,�
�Cust-Tax�classi.��������Material�tax�claasi.�����Rate��������Tax�code�
������1���������������������������1������������������2%������������A1�
������2���������������������������1������������������4%������������A1�
������3���������������������������1������������������0%������������A1�
Remember,�rates�are�flown�from�the�tax�codes.�Tax�codes�can�be�created�thru�T�
code�FTXP.�This�is�normally�a�FI�job.�
SAP�SD�Tips�by:�Soumya�
Return�material�From�customer�
You�need�to�receipt�the�rejected�goods�through�SD�Module�(VA01�-�Sales�Order�
type�RE).�
The�steps�are�as�follows�:�
1.�Create�a�return�request.�(Using�Sales�Order�in�SD)�
2.�Create�outbound�delivery�according�to�return�request.�
3.�If�the�setting�is�correct�in�the�outbound�delivery�screen�SAP�will�automatica
lly�
switch�post�goods�issue�button�into�post�goods�receipt.�The�setting�is�in�sales�
order�item�category�and�delivery�type.�
4.�In�the�standard�system�the�movement�type�used�is�651.�
5.�After�post�goods�issues�receipt�is�done�using�outbound�delivery,�the�quantity
�
is�placed�in�blocked�stock�without�value�updating.�
6.�You�will�then�decide�if�the�return�quantity�are�indeed�bad�stock�or�not.�
7.�Transfer�Posting�from�block�stock�to�unrestricted�stock�(mvt�type�453),�this�
will�have�accounting�effect�(Debit�Inventory,�Credit�COGS)�
8.�Goods�Issue�to�scrap�account�how�to�create�new�titles�which�can�be�used�in�
creating�the�"address"�view�on�the�Vendor�master.{T-Code:�XK01}�
In�config�go�to�Basis�Components�-->�basis�services�-->�Address�Management�-�
->�Maintain�title�texts�
Do�you�have�a�SAP�SD�Question?�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
SAP�SD:�Scheduling�Agreement�Vs�Contract�
A�schedule�agreement�contains�details�of�a�delivery�schedule�but�a�contract�just
�
contains�quantity�and�price�information�and�no�details�of�specific�delivery�
dates�
What's�the�difference�between�schedulling�agreement�with�normal�
order?�
What's�the�condition�for�us�to�choose�schedule�line�or�order?�
Both�of�them�contains�schedule�line,�price,�quantity.�
There�are�a�couple�major�differences:�
(1)�-�Schedule�agreements�allow�you�to�have�2�different�sets�of�schedule�lines�
-----------------------�Page�248-----------------------
(VBEP-ABART).����Standard�SAP�you�should�have�two�sets�of�tabs�-�of�schedule�
lines.�One�Forecast�&�the�other�JIT.��Forecast�forwards�the�schedule�lines�to�
planning�(seen�in�MD04)�and�JIT�passes�them�to�shipping�(VL10).�They�can�be�
identical�or�different.�Typically�these�are�used�for�component�supplier�customer
s�
(namely�Automotive).�The�customer�will�provide�you�4-10�weekly�buckets�
(usually�a�
Monday�date)�of�future�forecast�qtys.�Also�send�you�1-2�weeks�of�individual�
FIRM�ship�dates�-�which�are�entered�on�the�JIT.�It�comes�down�to�the�customer�
not�knowing�exactly�what�they�need�next�week,�but�they�don't�want�to�suprise�
you�with�a�large�order�qty,�where�your�lead�times�are�5+�days.�The�forecasted�
qtys�they�sent�last�week�should�account�for�this.�
(2)�Cumulative�Quantities�are�tracked�and�influence�how�the�schedule�
agreement�passes�requirements�to�both�forecasting�and�shipping.�These�qtys�
are�sometimes�requested�by�the�customer�on�ASNs.�Cumulative�qtys�reset�at�
year�end�unless�you've�got�a�customer�calendar�or�you've�modified�standard�
SAP�userexits�to�not�reset.�
Schedule�agreements�are�very�nice�when�the�customer�sends�EDI�data�(830s�=�
forecast�or�862s�=�JITs).�Outside�of�that�they�can�really�cause�trouble�regardin
g�
daily�maintenance,�missing�requirements,�cum�qty�corrections,�year�end�
processing,�etc.�
One�alternative�would�be�to�use�customer�independent�requirements�-�entering�
the�weekly,�monthly�forecasting�qtys�and�entering�standard�sales�orders�(with�
or�without�multiple�schedule�lines)�to�represent�the�true�firm�qtys.�
Do�you�have�a�SAP�SD�Question?�
Best�regards,�
SAP�Basis,�ABAP�Programming�and�Other�IMG�Stuff�
Sales�BOM�Implementation�
A�bill�of�material�(BOM)�describes�the�different�components�that�together�create
�
a�product.�A�BOM�for�a�bicycle,�for�example,�consists�of�all�the�parts�that�make
�
up�the�bicycle:�the�frame,�the�saddle,�wheels,�and�so�on.�
Process�Flow�
When�you�enter�the�material�number�of�a�bill�of�materials�that�is�relevant�for�
sales�order�processing,�the�system�displays�the�material�that�describes�the�
whole�bill�of�materials�as�a�main�item.�The�individual�components�are�displayed�
as�lower-level�items.�
There�are�two�ways�to�process�a�bill�of�materials�in�Sales.�Once�you�have�
entered�a�bill�of�material�in�a�sales�order,�the�system�runs�pricing,�inventory�
control,�and�delivery�processing�at:�
-�Main�item�level�if�the�material�is�assembled,�or�
-�Component�level�if�the�material�is�not�assembled�
The�type�of�processing�used�by�the�system�is�determined�by�the�item�category�
group�that�you�enter�in�the�material�master�record�for�relevant�materials.�
Processing�at�Main�Item�Level�
If�you�want�the�system�to�carry�out�pricing,�inventory�control,�and�delivery�
-----------------------�Page�249-----------------------
processing�at�main�item�level,�enter�ERLA�in�the�Item�category�group�
field�of�theSales:�sales�org.�2�screen�in�the�material�master�record�of�the�
finished�product.�This�means�that�the�components�only�function�as�text�items�
and�are�not�relevant�for�delivery.�The�following�graphic�shows�how�a�bill�of�
material�is�processed�at�main�item�level.�
Processing�at�Component�Level�
If�you�want�the�system�to�carry�out�pricing,�inventory�control,�and�delivery�
processing�at�the�component�level,�enter�LUMF�in�the�Item�category�group�
fieldof�the�Sales:�sales�org.�2�screen�in�the�material�master�record�of�the�
finished�product.�In�this�case,�only�the�components�are�relevant�for�delivery.�
During�processing�the�system�automatically�creates�a�delivery�group.�The�latest�
delivery�date�among�all�the�components�becomes�the�delivery�date�for�the�
entire�delivery�group.�
Fast�Links:�
How�to�Know�that�Sales�BOM�is�working�or�
not?�
I�have�set�up�a�sales�BOM.�How�do�I�know�or�test�that�is�is�working�or�
not?�
Once�you�enter�a�material�(for�whch�you�have�created�a�BOM�thru�CS01)�in�the�
sales�doc�another�material�pops�under�the�main�material�line�item�as�a�sub-item�
(s).�If�it�doesn't�then�your�BOM�isn't�working.�
In�my�experience�BOMs�work�if�all�maintenance�has�been�done�properly.�
A�number�of�things�to�check�is:�
1.�The�bom�hasn't�been�defined�for�the�plant�used,�or�you�haven't�defined�the�
plant�in�SO.�
2.�Main�item�category�-�has�BOM�application�SD01�been�assigned�to�it?�
3.�Item�categories�for�main�items�and�sub-items�have�not�been�mainteined�
properly.�
4.�Sales�items�maintenance�-�You�should�assign�item�categories�for�BOM�header�
items�and�sub-items�to�a�specific�sales�doc.�
5.�Has�the�BOM�itself�been�configured�properly�(i.e.�right�plant,�BOM�usage�
'5')?�
6.�Are�you�trying�it�out�on�an�order�created�after�all�BOM�maintenance�was�
done?�
7.�Also�,�what's�the�'Structure�scope'�set�as?�Anything�except�C�may�be�useful�
here?����We�have�that�set�to�A,�since�our�BOMs�are�all�single-level.�You�could�s
et�
it�to�B�if�BOM�are�configured�multi-level.�
Those�are�probably�main�reasons�why�BOM�shouldn't�work.�Apart�from�that,�just�
re-check�your�whole�config�-�the�truth�is�out�there�somwhere.�
Fast�Links:�
Implementing�the�Sales�BOM�
Sales�Order�Mass�Change�
-----------------------�Page�250-----------------------
I�am�a�SAP�SD�consultant�and�recently�faced�with�two�new�terms,�mass�
order�change�and�ALV�,�I�also�need�to�know�about�the�transaction�
code.�
There�is�transaction�MASS�which�can�be�used�to�carry�out�mass�changes�in�the�
sales�order�and�other�objects.�
Mass�Maintenance:�(Use�to�change�multiple�fields�in�multiple�documents�at�the�
same�time).���I�have�done�mass�change�for�customers;�and�orders�should�work�
the�same�way�too.�
1)�Try�t-code�[MASS]�and�select�sales�orders�&�execute�
2)�Choose�the�table�or�tables�for�your�selection�criteria�and�also�for�fields�yo
u�
want�to�change.�
Then�execute.�(suppose�your�selection�criteria�fields�are�from�"sales�order�
header�data"�table�and�the�field�you�want�to�change,�is�in�"item�data"�table)�
3)�Put�in�the�sales�documents(21000000,�21000001)�you�want�to�change�and�
also�the�items(10)�you�want�to�change.�
-�click�on�"�choose�selection�fields"�button�
-�From�the�Pool,�move�the�fields�you�want�to�the�"select�fields"�using�arrows.�
4)From�mass�maintenace�menu,�click�on�"Enter�new�field�values"�
-click�on�"sales�order�item�data"�tab�and�choose�the�field�you�want�to�change.�
(for�example.�I�want�to�change�plant�for�item�10)�
-enter�the�new�value�(of�the�plant�to�be)�
-click�on�"Adopt"�and�execute�
5)In�"sales�order�item�data"�tab,�you�see�the�new�value�of�the�plant�you�entered
�
at�the�top�and�the�old�values�of�item�10�are�below.�
-click�on�"change�field�values"�button.��you�see�all�the�old�values�are�changed�
to�
new�values.�
-save�
Note:��it�will�take�some�time�depending�on�how�many�records�you�have.�
Check:��Go�to�[SM37]�and�see�the�status�of�the�job�you�are�running�and�once�
finished,�export�the�spool�file�to�a�spreadsheet.�
Before�you�do�mass�maintenance,�go�to�the�particular�table�in�[se16]�and�get�
the�results.��Then�do�the�mass�maintenance�and�compare�the�results�with�this�
one.��If�they�match,�then�you�are�good�to�go.�
Note:��If�you�have�any�user�exits�that�affect�the�results,�ask�them�to�deactivat
e�
the�MODCHECKS�still�you�are�done�with�mass�maintenance�&�activate�them�
again.�
Is�there�a�way�to�change�the�billing�date�on�a�ton�of�sales�orders�with�
same�old�billing�date�to�a�same�new�billing�date?�
This�can�be�done�using�the�mass�transaction:�
Transaction:�MASS�
Object�Type:�BUS2032�
Tables:�SD�Document:�Business�item�data�
Sel�Field:�Billing�Date�(MASSSDHE�and�MASSSDPO)�
-�Or�you�can�just�select�by�document�numbers�(May�be�more�efficient)�
Execute�-�List�will�be�provide�for�changes�
Sel�Chg�Fld:�Billing�Date�
-----------------------�Page�251-----------------------
Set�new�billing�date�value�in�the�New�Values�field�
Click�on�lower�billing�date�column�
Click�on�Carry�out�a�Mass�Change�button�
Click�on�Save�button�
Suggestion�is�to�test�this�on�a�few�orders�in�your�development�system�to�get�a�
feel�on�how�this�works�before�applying�this�to�any�production�data.�MASS�is�a�
very�powerful�tool.�
I�have�100000�sales�orders�whith�an�incorrect�price�and�I�would�like�to�
do�a�massive�condition�update�with�pricing�type�"B"�(Carry�out�new�
pricing).�Is�there�a�transaction�or�program�for�this?�
Go�to�VA05�execute�the�report.�Select�all�sales�orders�you�want�to�update�the�
price,�Go�to�the�Menu�EDIT�-->�MASS�Change�--->�New�Pricing.�System�will�
display�all�the�re-pricing�options.�Select�B.�It�will�re-price�all�the�sales�ord
ers.�
You�can�try�for�one�or�two�order�initially�check�the�results�and�if�it�is�OK,�th
en�
you�can�do�for�others.�
Release�strategy�for�Sales�order�
Is�it�possible�to�have�release�strategy�for�sales�order?�
Satish�C�Jha�
As�such�SAP�standard�does�not�provide�release�strategy�for�sales�orders�similar�
to�purchase�orders.�����However�this�requirement�of�your�can�be�satisfied�throug
h�
authorisation�profiles;�what�I�mean�to�say�is�that�the�sale�order�to�be�kept�
incomplete�by�the�person�who�does�not�have�the�required�authorisation�&�the�
person�with�proper�authorisation�will�complete�
it�for�further�processing.�This�is�only�one�way�of�meeting�your�requirement.�
Balraj�G�Saigal�
In�order�to�emulate�a�release�strategy�similar�to�purchase�orders�you�can�use�
the�status�profile�in�sales�documents�(BS02).�IMG-Sales�and�distribution-Sales-�
Sales�documents-Define�and�assign�status�profile.�
Arturo�
Fast�Links:�
How�to�do�rebate�processing�
Rebates�Processs�in�SAP�is�divided�into�three�components�
1)�Configuring�Rebates�
2)�Setting�Up�Rebates�
3)�Managing�rebate�agreeeements�and�payments�
Pre-requsiistes-�Check�the�following:�
1.The�payer�partner�needs�toi�have�the�rebate�field�checked�in�the�customer�
master�on�the�sales�area-billing�doc�tab.�
2.The�Billing�type�must�be�marked�as�relevant�for�rebates.�
3.The�Sales�Organisation�must�be�marked�as�relevant�for�rebates.�
Condition�Technique�:�
Rebates,�use�the�condition�technique,�but�distinguish�themselves�from�pricing�in
�
applying�to�transactions�over�time,�versus�on�a�transaction�basis.�Rebates�have�
their�wn�field�catalog�and�their�own�condition�table�naming�convention.So�you�
could�have�two�condition�table�"001"�one�for�pricing�and�one�for�rebates,�which�
-----------------------�Page�252-----------------------
could�have�different�key�fields.�You�need�to�use�the�technical�names�A001�For�
pricing�and�KOTe001�for�rebates�when�you�use�the�query�type�using�transaction�
SE�16..�
Use�create�access�sequence�(AS).�����Enter�1�in�field�category�for�rebate�specif
ic.�
AS�after�going�thru�the�right�path�of�maintaining�access�sequence�for�rebates.�
The�big�difference�between�the�rebate�and�the�pricing�access�sequence�is�that�
there�is�no�exclsuion�flag�available�for�rebate�related�AS.�This�means�multiple�
tables�for�an�access�sequence�can�be�aplied�at�the�same�time.�
Rebate�related�condition�types�are�identified�by�codnition�class�-C.�
After�defining�and�creating�condition�types�for�rebated�include�them�in�the�
pricing�proceedure.�The�requirement�should�be�24�here�which�implies�that�the�
accruals�are�calculated�on�the�basis�of�invoice/bill.�
The�other�fields-�alctyp�and�altcbv�does�not�allow�you�to�manipulate�how�a�
rebate�is�calculated.�Also,�remove�the�requiremnt�24,�if�u�want�to�see�reabtes�a
t�
order�time.�
Now�payment�of�rebates:�
Payments�can�be�maunal�or�in�full�settlement.�When�you�do�manual�payments,�
it�defines�how�much�can�be�paid�out�during�a�partial�settlemetn.��You�use�partia
l�
settlement�only�when�rebate�agreement�is�defined�for�a�full�year�but�the�
paoyouts�are�supposed�to�happen�on�a�monthly,�quarterly�or�anyother�specified�
period.�
These�accurals�are�based�on�sales�volume�and�when�they�are�posted�billing�is�
created�int�eh�follwoing�manner.�Provision�for�accruals�is�debited�and�Sales�
revenue�is�credited.�When�rebate�credit�memo�is�created�
��Customer�account/�is�debited�and�
��Accrual�provision�account�is�credited.�
Also,�please�note�that�when�rebates�are�created�without�dependent�ona�material�
but�on�customer/material�you�need�to�refer�to�a�material�for�settlement.�
With�Compliment:�Srini�
I�have�this�same�problem�found�in:�
http://www.sap-img.com/sap-sd/rebate-process-with-ref-to-so.htm�
However,�can�somebody�explain�it�as�I�have�problem�in�understanding�
the�link.�
What�exactly�do�you�wish�to�know�in�Rebates?�The�total�outline�of�the�Rebate�
process�or�each�and�every�step�in�the�SAP�system?�
First�of�all�rebates�are�more�or�less�discounts�which�are�offered�to�customers.�
The�rebates�are�based�on�the�volume�of�the�business�the�customer�does�with�
you�within�a�specified�time.�for�eg�if�the�customer�agrees�for�Rs.1�Crore�worth�
of�business�with�u�in�1�year,�then�you�activate�your�rebate�porocess.�if�at�the�
end�of�the�year�the�customer�DOES�achieve�the�target�u�offer�him�say�2/3/4�%�
whatever�is�decided.�The�rebates�are�passed�on�to�the�customer�in�the�form�of�
Credit�notes.�
The�rebate�can�be�given�to�the�customer�at�one�time�or�in�installments�also.�
This�is�broadly�the�outline�of�the�rebate�process.�
R.Sreeram�
Note�:�I�recomend�you�to�study�the�theory�part�of�why�rebate�and�why�not�a�
-----------------------�Page�253-----------------------
discount.�
This�will�help�you�understand�better.�
May�be�I�can�help�you�with�rebate�process.(IN�-IMG)�
1.�define�a�rebate�agreement�type�
2.�define�a�condition�type�group�
3.�define�a�condition�type�and�place�this�condition�
Type�in�the�pricing�procedure.(REQUIREMENT=24)�
ALSO�IN�THE�PROCEDURE-�ACCRUAL�KEY�=�ERU�
YOU�ALSO�HAVE�TO�DO�THE�ACCOUNT�DETERMINATION�FOR�REBATES.�
Once�you�have�defined�all�the�3�and�assignment�starts.�
Assign�the�agreement�type�to�the�condition�type�group�
Assign�the�cond�type�group�to�the�condition�type.�
Condition�technique�is�also�used�in�rebates.�
REBATE�ACTIVATION-�IN�CUSTOMER�MASTER,�SALES�ORGANISATION�AND�FOR�
THE�BILLING�DOCUMENT.�
After�having�done�this�please�proceed�to�maintain�the�condition�record�for�the�
rebates�(transaction�code-vbo1)�
Note:�if�you�maintain�the�requirement�coloumn�with�the�requirement�as�24�-�the�
rebate�will�be�affected�in�the�billing�document�and�if�you�dont�give�the�
requirement�as�24�your�rebate�will�be�affected�in�the�sales�order.�
The�rebate�process�is�completed�when�you�have�created�a�credit�memo�to�the�
customer.�
The�document�type�for�the�partial�settlement�is�R3.�
Please�make�sure�you�open�two�screens�SO�THAT�YOU�CAN�COMPARE�THE�NEW�
ENTRIES�WHAT�EVER�YOU'RE�DEFINING�WITH�THAT�OF�THE�STANDARDS�or�
first�you�try�with�the�standard�condition�type�boo1,�boo2�
boo3�boo4.�
AFTER�YOU�HAVE�FINISHED�A�COMPLETE�SALES�CYCLE�OF�CREATION�ORDER�,�
DELIVERY�AND�BILLING.�
GO�TO�THE�CONDITION�RECORD�IN�CHANGE�MODE�(VB02)�AND�SETTLE�THE�
ACCOUNT�PARTIALLY.�
I�hope�this�will�be�of�any�help�to�you.�
Praveen�
In�a�simple�way,�
1.�First�you�need�to�create�a�Rebate�agreement.�
2.�Create�condition�record�for�rebate�giving�the�rebate�rate�and�accrual�rate.�
3.�when�the�rebate�relevent�billing�doc�is�generated,�the�rebate�and�accruals�ar
e�
determined�and�posted�in�a�seperate�GL�account�as�a�noted�item�-�amount�to�be�
settled.�Also�it�gets�copied�in�the�rebate�agreement.�
4.�create�settlement�run�using�credit�memo�request�and�then�credit�memo�to�
settle�this�amount�with�the�customer.�
This�is�what�the�link�says.�
Rebate�Process�with�Ref.�to�SO�
If�I�need�to�make�a�rebate�for�a�customer�what�is�the�process�involved.�
I�am�providing�some�info�on�rebates�which�I�know.�
-----------------------�Page�254-----------------------
Rebate�agreemnts�is�based�on�agreement�types.Conditon�records�which�are�
created�like�B001�and�B002�are�linked�to�the�rebate�agreeements�specifying�the�
rebate�rate�+�the�accrual�rates.condition�records�specify�the�rebate�rate�and�th
e�
accrual�rates.�
Consider�an�example..�
You�decided�to�give�a�rebate�of�3%�to�a�customer�whose�sales�vol�is�$1000�for�a�
particular�SO�
Then�the�rebate�value�is�$30..�
Now�when�you�make�the�rebate�settlement�by�doiing�the�Credit�memo�and�you�
decide�to�pay�$27,�then�the�accounting�will�be�generated�saying��������27$�paid�
towards�rebate�and�3$�is�the�accrual�which�you�owe�to�the�customer�
Procedure:�
Rebate�agreement:�Transaction�code:�VB01�
When�you�go�to�VB01,�choose�agreement�type�0002�and�then�in�conditions�
give�
Material�����rebate�
1�������������20�
20������������30�
Now�create�a�sales�order�with�a�material�say�M-11�for�SOrg�1000�12�00�with�
QTY�6�
Now�check�VB03�and�see�rebate�agreemtent�it�will�say�Accruals�120�and�
payments�0�
since�your�rebate�is�not�settled�still.�
Rebate�setllement�
Go�to�VB02�enter�ur�sales�deal�no,�and�change�the�agreemetn�status�to�B�then�
enter�Shift+F12�and�enter�the�amount�to�be�paid�for�example�u�say�$80�
Then�check�in�rebate�payments�rebate�doc�and�partial�setllemetn�since�you�
have�not�paid�in�full.�
View�the�credit�memo�request�
Remove�the�Billing�bloock�Go�to�VA01�and�put�order�type�G2�,,,go�to�create�with�
ref�and�enter�ur�Sales�order�no,,,save�the�doc�now...�
Then�go�to�VF01�and�enter�the�credit�memo�reqst�no�generated...save�the�doc�
no�and�go�to�VF02�and�say�release�to�accounting�
Now�the�final�settlement�will�be�this�way�
Accruals:120�
Accrual�reversed:80�
Rebate�pay:80�
Amount�payable:40�
So�the�balance�40�is�still�the�accrual�
This�is�an�example�how�a�rebate�will�be�processed�with�ref�to�a�SO�with�an�
example.�
SAP�SD�Tips�by:�Priyam�
How�to�do�a�rebate�agreement�for�a��specific�
customers�with�settings�details?�
1.�Create�a�condition�by�copying�a�a�standard�condition�like�BO03�in�V/06�
-----------------------�Page�255-----------------------
2.�Assign�this�condition�in�the�std�pricing�procedure�with�acct�key�as�ERB�and�
accural�key�as�ERU�-�V/08�
3.Create�a��Rebate�Agreement�in�VBO1�(It�is�O�=�Owl�and�not�zero).�No�will�be�
generated�
choose�003�-�Customer�rebates,�enter�the�customer�code,�the�validity�and�check�
for�the�status�shld�be�in�Open,�click�on�the�conditions�enter�the�percentage�and
�
accrual�amount.�You�also�can�have�scales�in�this.�Also�you�need�to�maintain�the�
material�for�the�settlement�
4.�Create�a�sales�order�for�that�customer�and�check�the�rebate�agreement.�
5.�You�can�see�the�rebate�condition�in�the�invoice�only.�
6.�Once�you�have�posted�the�invoices,�then�go�to�rebate�agrrement�no.�clicl�on�
verficayion�and�it�will�show�the�order�details.�
7.�For�settlement�change�the�status�of�the�rebate�to�B�-�release�for�the�
settlement.�
8.�Credit�memo�request�will�b�generated�copy�the�no.�and�go�to�VA02,�remove�
the�blocks�if�any�and�create�an�invoice�(credit�memo).this�will�show�u�the�
accrual�amount.�
9.�In�both�the�invoice�and�the�credit�memo�check�the�posting�-�accounting�
document�it�will�show�u�the�accrual�as�negative.�
10.�Again�go�to�rebate�aggreement�and�check�the�status�it�will�show�you�D�-�
Final�settlement�of�agreement�already�carried�out�
Consignment�Sales�Process�in�SAP�
The�consignment�process�in�SAP�standard�consist�of�four�small�
processes:�
Consignment�fillup�(send�materials�to�customer�consignment).�
Here�you�have�a�consignment�fillup�order�and�a�consignment�fillup�delivery.�
Consignment�issue�(issue�materials�from�customer�consignment�to�the�
customer).�
Here�you�have�a�consignment�issue�order,�consignment�issue�delivery�and�a�
consignment�issue�invoice.�(the�flow�is�very�similar�to�a�normal�OR�flow,�but�th
e�
materials�are�issued�from�the�consignment�stock�instead�of�plant�stock�
unrestricted).�
Consignment�return�(return�materials�from�customer�ownership�to�customer�
consignment).�
Here�you�have�a�consignment�return�order,�consignment�return�delivery�and�a�
consignment�return�invoice.�(the�flow�is�very�similar�to�a�normal�RE�flow,�but�
the�materials�are�returned�to�the�consignment�stock�instead�of�plant�stock�
returns).�
Consignment�pickup�(pickup�consignment�stock�and�move�it�to�plant�stock).�
Here�you�have�a�consignment�pickup�order�and�a�consignment�pickup�delivery.�
Note�that�in�consignment�fillup�and�consignment�pickup�there�are�no�invoices�
since�there�is�no�change�of�ownership�for�the�materials.�
How�to�perform�a�consignment�order?�
In�consignment�orders�you�are�allowing�the�stock�to�sit�in�your�customer�
-----------------------�Page�256-----------------------
location.�Once�he�informs�that�he�used�the�stock�you�will�invoice�him.�If�he�
returns�the�stock�you�will�accept�the�stock�to�take�it�back.�
It�is�defined�in�4�steps.�
1.�Consignment�fill�up:�
Sales�document�type�is�KB�
Item�category�KBN�
shedule�line�category�E1�
In�this�step,�you�are�not�invoicing�the�customer.�document�flow�is�sales�order�-
-�
--�delivery�item�category.�It�will�not�be�relevent�for�billing�and�pricing�becau
se�
you�are�not�charging�money�for�these�goods�in�this�step.�
In�schedule�line�category,�you�will�set�movement�type�631�&�set�for�availability
�
check�and�TOR.�
2.�Consignment�Issue.�
Once�the�customer�informed�you�that�he�used�all�the�goods�or�partial�goods�
then�you�will�create�consignment�issue�for�used�goods.�
Sales�document:�KE�
Item�category:�KEN�
shedule�line�category:�C0�or�C1�
Here�you�are�invoicing�the�customer(because�he�used�the�goods).�you�are�
assigning�the�delivery�documnt�and�billing�document�to�the�sales�document.�
In�item�category,�you�are�setting�relevent�for�billing,�pricing,�special�stock.�
In�schedule�line�category,�your�setting�is�633�movement�type,�relevent�for�
availability�check�&�TOR.�
3.�Consignment�Return:�
Customer�found�that�some�goods�are�damaged�or�he�not�able�to�sold�the�goods�
he�want�to�send�it�back.�that�you�are�creating�this�document.�
Sales�document�type:�KR�
Item�category:�KRN�
Shedule�line�category:�D0�
You�will�assign�delivery�document�and�billing�to�sales�document.�you�will�create
�
return�order,�return�delivery,�return�billing.�
Your�setting�item�category�relevent�for�billing,�returns,�pricing,�special�stock
.�
Your�setting�schedule�line�item�category:�634�movement�type,�NO�availability�
NO�TOR.�
4.�Consignment�Pick�up:�
Even�if�you�create�the�consignment�return�the�goods�are�not�come�to�direct�to�
your�plant.�For�that�you�need�to�create�consignment�pick�up.�here�the�owner�
ship�is�not�changing�so�you�do�not�need�to�create�billing.�
Assign�retrun�delivery�to�sales�document�type.�
Sales�document:�KA�
Item�category:�KAN�
schedule�line�category:�F0�&�F1�
Your�setting�item�category�relevent�for�returns.�any�shedule�line�category�
relevent�for�632�movement�type,�MRP,�availability�check,�delivery.�
Now�you�check�your�plant�stock.�Stock�will�increase.�����������������������*--�
Ugameswara�Rao�
-----------------------�Page�257-----------------------
Issue�free�goods�to�selected�Customers�
Client�wants�to�issue�free�goods�to�selected�customers�after�the�said�
customer�buys�a�specified�quantity�of�a�good�during�the�festive�season�
starting�02�December�to�mid�January.�for�example�customer�A�buys�34�
cartons�of�Corn�Ice-cream,�we�offer�him�12�free�corns.�this�should�then�
reflect�as�cost�in�our�accounts.�the�rest�of�the�system�is�already�up�and�
running�and�should�not�be�inconvinienced.�How�do�I�set�it�up?�
1.Run�trans.�VBN2�to�first�create�master�record�for�free�goods�as�follows:�
Enter�following�information�in�selection�screen:�
-�Free�goods�type:�NA00�
-�Sales�org,�distribution�channel,�customer�#�and�execute.�
Now�in�next�screen�create�the�record�as�follows:�
-�First�select�the�exclusive�button�and�verify�that�you�are�in�exclusive�view.�
��(that�is�if�you�want�exclusive)�
-�Material#,�Min�qty�-�Say�34�cartons.�(check�in�what�units�you�want�to�
manage)�
��From:�34�cartons�
��unit�of�measure:�
��Free�goods:�12�Pcs�
��Unit�of�measure:�Pcs�
��Calcualtion�type:�1�or�try�the�other�options�
��Deliver�control:�Blank�or�any�of�the�other�options�suitable�to�you.�
Now�save�and�exit.�
Now�run�VA01�for�34�cartons�and�press�enter.�The�system�will�automatically�
propose�the�free�goods�
item�at�no�additional�charge.�Try�higher�order�qtys�and�see�if�the�free�goods�qt
y�
are�scaling�up.�
If�not�adjust�the�calculation�parameters�in�the�master�record�screen�
It�should�be�transaction�VBN1.�Sorry�for�the�error.�
VBN2�is�to�change�the�record.�VBN1�creates�it.�
Kris�J�
If�you�want�to�give�free�goods�to�some�of�the�customers�than�
1.�create�a�customer�group�say�99�for�FREE�GOODS�
In�Free�Goods�Menu:�
2.�add�a�feild�catalog�for�CUSTOMER�GROUP�
3.�create�a�condition�table�(free�goods)�say�555�only�for�customer�group�
4.�create�a�sequence�say�FREE�with�condition�table�555�
5.�create�a�condition�type�say�FREE�with�
6.�maintain�pricing�procedure�say�ZFREE�with�condition�type�FREE�
Now�assign:�
7.�Active�Free�goods�Determination�or�Assign�with�your�sales�organisation�this�
procedure�ZFREE�
8.�Create�free�goods�determination�with�transaction�code�/nvbn1�for�FREE�with�
-----------------------�Page�258-----------------------
Key�Csuomer�Group�
99�for�exclusive�
Give�customer�Group�say�99�and�from�34�to�34�free�12�
Sandeep�budhraja�
Supressing�Fields�in�Sale�Order�
To�make�optional�/�mandatory�you�can�use�in�IMG�-�S&D->�Basic�>�Functions->�
Log�of�incomplete�Procedures�=>��select�the�fields�>�from�the�tables�and�the�
system�will�check�for�them�(OVA2/VUA2)�
To�make�a�filed�entry�enabled�or�grey�(non-entry�allowed):�
User�exits�in�the�program�MV45AFZZ-USEREXIT_FIELD_MODIFICATION�
This�user�exit�can�be�used�to�modify�the�attributes�of�the�screen�����fields.�
To�do�this,�the�screen�fields�are�allocated�to�so-called�modification�groups�1�-
�4�
and�can�be�edited�together�during�a�modification�in�ABAP.�
If�a�field�has�no�field�name,�it�cannot�be�allocated�to�a�group.�The�usage�of�th
e�
field�groups�(modification�group�1-4)�is�as�follows:�
Modification�group�1:�Automatic�modification�with�transaction�MFAW�
Modification�group�2:�It�contains�'LOO'�for�step�loop�fields�
Modification�group�3:�For�modifications�which�depend�on�check�tables�or�on�
other�fixed�information�
Modification�group�4:�is�not�used�
The�FORM�routine�is�called�up�for�every�field�of�a�screen.�If�you�require�change
s�
to�be�made,�you�must�make�them�in�this�user�exit.�This�FORM�routine�is�called�
up�by�the�module�FELDAUSWAHL.�
With�Compliments�by:�Taner�Yuksel�
Actually�suppressing�fielding�sales�orders�userwise�is�quite�easy.�We�are�doing�
it�
in�our�company.�For�this�we�use�userexit�FORM�
USEREXIT_FIELD_MODIFICATION�in�MV45AFZZ.�
Below�is�the�sample�code�
IF�SCREEN-NAME�=�'VBKD-ABSSC'.�
AUTHORITY-CHECK�OBJECT�'ZMV45AFZZ'�ID�'SCRFNAME'�FIELD�SCREEN-�
NAME.�
��IF�sy-subrc�=�0.�
���SCREEN-INPUT�=�1.�
��else.�
���SCREEN-INPUT�=�0.�
��ENDIF.�
endif.�
You�place�the�authority�check�object�in�authorization�profile�in�the�role�of�the
�
users,�who�should�have�access�to�the�field�(in�this�case�it�is�VBKD-ABSSC),�and�
there�assign�the�corresponding�fields�that�are�to�be�accessed�via�this�userexit.
�
With�Compliments�by:�Martishev�Sabir�
Some�Light�on�Batch�Determination�
-----------------------�Page�259-----------------------
On�batch�determination,�the�whole�process,�how�it�is�determined�
automatically�in�the�order.�
A1)�Normaly�we�use�batch�determination�at�delivery�level,�because�at�the�time�
of�order�material�may�or�may�not�be�created.for�this�material�should�be�
configured�with�batch�and�batch�determination�should�be�checked�in�sales�views�
of�material.�
A2)�Batch�Determination�during�order�Creation.�
For�this�you�need�to�maintain�a�Classes�d�for�you�Material.�Depending�on�the�
Manufacturing�process�you�can�define�the�characteristics�for�your�material.�
Ex:�Purity�for�Medicines,���Resistance�for�Electric�Items.�
You�need�to�create�a�class�(You�might�have�to�create�a�new�class�type)�which�
incorporates�the�characteristic.�
First�Create�the�Characteristic�Using�Ct04�and�then�using�Cl02�create�the�Class�
including�this�characteristic.�
Then�in�your�material�master�Classification�View�Enter�this�class.�
Then�Create�a�Batch�for�the�particular�plant�and�Stor�Loc�using�MSC1N.Give�the�
value�of�the�characteristics�in�this�batch.�
Then�go�to�SPRO�->Logistics�General�->Batch�Management�and�maintain�the�
Condition�Technique�(Procedure,�Strategy�Types�and�assignment�to�sales�docs�
etc).�
Then�Create�the�Batch�Determination�Record�using�VCH1.�
SAP�Tips�by:�Shaik�Zaheeruddin�
Fast�Links:�
Get�help�for�your�SAP�SD�problems�
Difference�between�Item�Proposal�and�
Material�Determination�
What�is�the�difference�between�the�item�proposal�and�material�
determination�product�proposal?�
Item�proposal�and�product�proposal�are�the�same.�
Item�proposal�is�the�list�of�materials�and�order�quantities�that�can�be�copied�
into�the�sales�order�from�the�customer�master�data.�
We�use�VA51�to�create�the�item�proposal.�Here�we�get�a�number.This�number�is�
then�linked�to�the�customer�master�data�in�the�sales�view.�This�is�very�
commonly�used.�
Material�determination�is�very�closely�related�to�item�proposal�/product�
proposal��and�is�used�to�swap�one�material�for�another�in�the�sales�order�using�
the�condition�technique.�I�have�not�seen�Material�����determination�procedures�
used�in�the�projects�I�have�worked.�
SAP�Tips�by:�Prashanth�Harish�
Item�Proposal�or�Product�proposal:�
"Item�proposal�is�same�as�product�proposal�&�SAP�uses�the�two�terms�
interchangeably.�
"An�item�proposal�is�a�list�of�materials�and�order�quantities�that�can�be�copied
�
-----------------------�Page�260-----------------------
into�the�sales�order.��Items�can�also�be�selected�from�a�list�and�copied�into�a�
sales�order."�
1)�Use�transaction�[VOV8]�to�configure�the�document�type�("MS"�for�product�
proposal).�
2)�Use�transaction�[VA51]�to�create�a�proposal.�
3)�Enter�the�item�proposal�on�the�sales�area�data�(sales�tab)�of�the�customer�
master�record.�
4)�In�[VA01]�to�create�a�sales�order,�Select�Edit�&�propose�items."�
Material�determination:�
"Material�determination�uses�the�condition�technique�to�swap�one�material�for�
another�when�certain�conditions�apply.�Material�
determination�is�triggered�by�the�material�entered�in�the�line�item�of�the�sales
�
order.�
Use�transaction�[VB11]�to�create�a�material�determination�condition�record.�
And�[OV12]�for�configuration�of�material�determination.�
Material�determination�is�useful�when�old�product�is�becoming�obsolete�or�a�new�
product�is�released�by�the�company�at�specific�date."�
SAP�Tips�by:�Minmini�
Fast�Links:�
Get�help�for�your�SAP�SD�problems�
Steps�for�SD�Variant�Configuration�
Some�light�on�Variant�Configuration�in�Detail.�
The�procedure�is�as�follows:�
�������Create�a�Material�-�KMAT�type�with�Item�category�(002)��������Create�Charateristics�in�CT04�-�Zbike,�where�in�values�mention�the�Color�of�the�bile�like�Red,�Blue�etc�
�������Create�another�characteristics�in�CT04�-�ZPrice,�where�directly�go�the�additional�data�tab�and�maintain�the�table�SDCOM�and�field�VKOND�(ABAP�
Dictionary�it�will�ask�for)�
�������Assign�these�two�characteristics�to�a�Class�in�CL01�-�ZBikeclass�(�Type�300)�in�characteristics�tab�page.�
�������Then�go�to�CU41�Configuration�profile�select�the�material�and�enter�the�description�click�on�the�class�assignment�ie�assign�Zbikclass.�
�������Now�go�back�to�CT04�-�enter�Zbike�-go�to�values-�select�Red-�go�to�extras�-�Other�Dependencies�-�Select�Procedure�enter�in�front�10�write�-�
$self.ZPrice='Red'�and�save�
�������Now�go�back�go�to�extras�-�Other�Dependencies�-�assignments�and�assign�
relationship�(�by�default�it�will�come�just�save)�
�������Now�select�Blue-�go�to�extras�-�Other�Dependencies�-�Editor�-�Select�Procedure�enter�in�front�of�10�write�-�$self.ZPrice='Blue'�and�save�
�������Now�go�back�go�to�extras�-�Other�Dependencies�-�assignments�and�assign�relationship�(�by�default�it�will�come�just�save)�
-----------------------�Page�261-----------------------
�������Now�go�to�VK11�-�Enter�VA00�(Condition)(For�Std�RVA001�Pricing�Procedure)�-�enter�variant�Red�and�Blue�give�the�rates�accordingly�and�create�
the�sales�order.���������������*--�Shaik�Zaheeruddin�
Tell�me�about�variant�configaration?�
What�are�the�type�of�questions�we�can�expect�in�that?�
Variant�configuration�is�used�where�you�have�a�configurable�material�like�
computer�(made�up�of�components�like�processor,�monitor,�keyboard,�mouse�
etc).�These�components�are�called�as�characteristics�in�variant�config.�Again�th
is�
will�be�having�values�like�processor�can�be�either�P4�or�P3,�monitor�can�be�15"�
or�17"�etc.�
Based�on�the�values�selected�the�variant�pricing�will�happen�using�the�condition
�
type�VA00.�
Possible�questions�you�can�expect�are:�
-�What�is�variant�configuration?�
-�What�is�characteristic?�
-�What�is�value?�
-�What�is�class?�
-�What�is�configuration�profile?�
-�What�is�dependency�and�what�are�the�types?�
-�What�is�a�variant�table?�
-�And�the�transaction�codes�for�the�above.����������*--�Balaji�
Process�Flow�for�3rd�Party�Sales�
Customize�the�third�party�sales�in�summary:�
�1.�Create�Vendor�XK01�
�2.�Create�Material�–�Material�Type�as�"Trading�Goods".�Item�category�group�as�
"BANS".�
�3.�Assign�Item�Category�TAS�to�Order�type�that�you�are�going�to�use.�
�4.�A�sale�order�is�created�and�when�saved�a�PR�is�generated�at�the�
background�
�5.�With�reference�to�SO�a�PO�is�created�(ME21N).�The�company�raises�PO�to�
the�vendor.�
�6.�Vendor�delivers�the�goods�and�raises�bill�to�company.�MM�receives�the�
invoice�MIRO�
�7.�Goods�receipt�MIGO�
�8.�Goods�issue�
�9.�The�item�cat�TAS�or�Schedule�line�cat�CS�is�not�relevant�for�delivery�which�
is�
evident�from�the�config�and,����therefore,�there�is�no�delivery�process�attached
�in�
the�whole�process�of�Third�party�sales.�
10.�Billing����*--�Seema�Dhar�
SD�-��3rd�party�sales�order�Create�Sales�Order�
VA01�
����Order�Type�
-----------------------�Page�262-----------------------
�����Sales�org,�distr�chnl,�div�
�����Enter�
�����Sold�to�
�����PO�#�
�����Material�
�����Quantity�
�����Enter�
�����Save�
SD�-���3rd�party�sales�order�View�the�PR�that�is�created�with�a�third�party�
sales�order�
VA01�
�����Order�Number�
�����Goto�Item�Overview�
�����Item�->Schedule�Item�
SD�-���3rd�party�sales�order�View�the�PR�that�is�created�
ME52N�
�����Key�in�the�PR�number�
�����Save�
SD�-���3rd�party�sales�order�Assign�the�PR�to�the�vendor�and�create�PO�
ME57�
�����Key�in�the�PR�number�
����Toggle�the�"Assigned�Purchase�Requisition"�
�����Execute�
�����Check�the�box�next�to�the�material�
����Assign�Automatically�button�
�����Click�on�"Assignments"�button�
�����Click�on�"Process�assignment"�
����The�"Process�Assignment�Create�PO"�box�,�enter�
�����Drag�the�PR�and�drop�in�the�shopping�basket�
�����Save�
SD�-���3rd�party�sales�order�Receive�Goods�
MIGO_GR�
�����PO�Number�
�����DN�Number�
�����Batch�tab�,�click�on�classification�
�����Serial�Numbers�tab�
�����Date�of�Production�
�����Flag�Item�OK�
�����Check,�just�in�case�
�����Post�
�����Save�
SD�-���3rd�party�sales�order�Create�Invoice�
MIRO�
�����Invoice�Date�
�����Look�for�the�PO�,�state�the�vendor�and�the�Material�
�����Check�the�box�
-----------------------�Page�263-----------------------
����Clilck�on�"Copy"�
����Purchase�Order�Number�(bottom�half�of�the�screen)�
����Amount�
����State�the�baseline�date�
����Simulate�&�Post�
����Invoice�Number�
����*Invoice�blocked�due�to�date�variance�
SD�-��3rd�party�sales�order�Create�a�delivery�order�
VL01N�
����In�the�order�screen�,�go�to�the�menu�Sales�Document�,�select�"Deliver"�
����Go�to�"picking"�tab�
����State�the�qty�and�save�
SD�-��3rd�party�sales�order�Create�a�billing�document�
VF01�
����Ensure�that�the�delivery�document�is�correct�in�the�
����Enter�
����Go�to�edit�->�Log�
Number�Ranges�In�Sales�Order�
This�is�regarding�number�ranges�defining�and�assigning�tips�which�you�can�
follow�as�below:�
Whenever�there�is�a�new�Sales�Org�being�created,�you�will�be�required�to�
maintainNumber�Ranges�for�Sales�Documents�which�are�allowed�for�your�New�
Sales�Area.�
Number�Ranges�can�be�maintained�Internally�by�the�system,�however�it�can�be�
maintained�externally�also�if�you�customize�it�accordingly.�
In�Standard�SAP�the�Transaction�code�for�Maintaiing�Number�ranges�externally�
is�VN01.�
Defining�-�The�same�can�be�reached�through�in�IMG�as��:�Sales�&�Distribution--�
>Sales-->Sales�Document�Header-->Define�Number�Ranges�for�Sales�
Documents.�
Here�you�provide�the�system�a�specific�Number�range�as�follows:�
Number�range�Key�+Start�Number�range+�End�Number�Range+Current�
Number�
For�Example:�If�you�want�to�propose�the�following�Number�Range�
*1����9000076000�������9000076999�������0�
The�Current�Number�field�will�be�kept�zero�as�you�are�proposing�new�number�
range�and�no�sales�documents�have�been�created�on�it�,�Obviously..�
*1�is�a�Unique�Two�digit�Alphanumeric�Key,�while�proposing�your�key,�you�
should�ensure�that�it�should�not�be�there�in�the�system�as�existing.�
If�you�propose�a�key�that�is�there�in�the�system�or�if�the�Number�Range�(Start�
and�End�Series)�is�there�in�the�system�already,�the�system�will�throw�a�message�
that�Interval�already�already�exists.�So�choose�a�key�that�is�unique,�and�which�
is�not�there�in�the�system.�
Here�,�by�making�this�,�you�are�assigning�a�Key�to�a�Number�Range�Series.�
All�the�symbols�can�be�used�along�with�numbers�from�0�to�9�and�Alphabets�from�
-----------------------�Page�264-----------------------
A�to�Z�and�in�any�order.�For�example:�!1,�^A,�BB,Z*,M2.........�
Assigning�-�In�Assigning,�you�assign�the�particular�Sales�Document�to�
the�NumberRange�you�have�already�proposed�as�above.�
The�Assigning�Part�is�done�as�follows:�
The�Two�digit�Alpha�Numeric�Key�is�maintained�or�Assigned�to�the�respective�
Sales�Document�type�in�V0V8.�
This�can�also�be�reached�in�IMG�by:�
Sales�&�Distribution-->Sales-->Sales�Document�Header-->Define�Sales�
Document�Types�
Locate�the�particular�Sales�Doc�Type,�and�double�click�on�it�to�display�it�
configuration.�Here�you�put�the�Two�Digit�Number�key�in�the�Field-�"Number�
range�External�Assignment"�
Besides�this:�
If�a�new�Shipping�Point�is�created�then�Delivery�Number�ranges�are�required�to�
be�maintained.�
Similarly,�
If�a�new�Plant�is�created�then�Billing�Number�Ranges�are�required�to�be�
maintained.�
Tips�by�:�Vivek�Sahni�
What�is�Debit�note�and�Credit�note�
What�is�Debit�note�and�Credit�note?��What�is�the�purpose?�������������How�we�
create?�
1.�A�transaction�that�reduces�Amounts�Receivable�from�a�customer�is�a�credit�
memo.�For�eg.�The�customer�could�return�damaged�goods.��A�debit�memo�is�a�
transaction�that�reduces�Amounts�Payable������to�a�vendor�because,�you�send�
damaged�goods�back�to�your�vendor.�
2.�Credit�memo�request�is�a�sales�document�used�in�complaints�processing�to�
request�a�credit�memo�for�a�customer.�If�the�price�calculated�for�the�customer�i
s�
too�high,�for�example,�because�the�wrong�scale�prices�were�used�or�a�discount�
was�forgotten,�you�can�create�a�credit�memo�request.�The�credit�memo�request�
is�blocked�for�further�processing�so�that�it�can�be�checked.�If�the�request�is�
approved,�you�can�remove�the�block.�The�system�uses�the�credit�memo�request�
to�create�a�credit�memo.�
You�can�use�credit�memos�in�Sales�and�Distribution�(SD)�for�assigning�credit�
memo�requests�to�the�open�invoices�and�in�Financial�Accounting�(FI)�for�
assigning��credit�memos�and�payments�to�the�open�invoices�and�carry�out�
clearing�with�them.���If�you�use�both�Financial�Accounting�(FI)�and�Sales�and�
Distribution�(SD),��there�is�a�1:1�relationship�between�the�credit�memo�request�
and�the�credit�memo�item�posted�in�Financial�Accounting�(FI).�As�soon�as�you�
bill�the�credit�memo�request�together�with�other�sales�orders,�or�distribute�the
�
items�of�one�credit�memo�request�to�several�billing�documents,�the�assignment�
is�no�longer�valid�and�the�system�will�not�process�it.�
For��credit�memos,�credit�memo�requests,�and�payments,�you�have�the�
-----------------------�Page�265-----------------------
following�assignment�options:�
-�Assignment�to�a�single�invoice�
-�Assignment�of�a�partial�amount�to�an�invoice�
-�Assignment�to�several�invoices�
When�you�post����credit�memos,�the�payment�programme�processes�them�
automatically.�If�the�credit�memo�is�specifically�related�to�a�particular�open�
invoice�item,�the�payment�program�automatically�attempts�to�offset�the�credit�
memo�against�the�open�item.�If�it�is�not�possible�to�completely�offset�the�credi
t�
memo�against�an�invoice,�you�can�post�a�debit�memo�to�the�vendor,�who�is�to�
reimburse�the�amount.��Then�you�can�apply�a�multilevel�dunning�program.�
3.��Debit�memo�request�is�a�sales�document�used�in�complaints�processing�to�
request�a�debit�memo�for�a�customer.�If�the�prices�calculated�for�the�customer�
were�too�low,�for�example,�calculated�with�the�wrong�scaled�prices,�you�can�
create�a�debit�memo�request.�The�debit�memo�request�can�be�blocked�so�that�it�
can�be�checked.�When�it�has�been�approved,�you�can�remove�the�block.�It�is�
like�a�standard�order.�The�system�uses�the�debit�memo�request�to�create�a�
debit�memo.�
4.��As�mentioned�above,�creating�a�credit�or�debit�memo�request�enables�you�to�
create�credit�or�debit�memos�based�on�a�complaint.�For�this�first�create�a�sales
�
document�with�the�order�type�for�a�credit�or�debit�memo�����request.�You�can�
create�the�debit��or�credit�memo�requests�in�the�following�ways:�
–�Without�reference�to�an�order�
–�With�reference�to�an�existing�order�
Here�you�enter�which�order�the�complaint�refers�to.�
�–�With�reference�to�an�invoice�
Here�you�enter�which�invoice�the�complaint�refers�to.�
In�all�cases,�you�specify�the�value�or�quantity�that�should�be�in�the�credit�or�
debit�memo�
5.�You�can�block�the�credit�or�debit�memo����request�from�being�billed�in�
Customizing.�Go�to�Sales�->�Sales�Documents�->�Sales�document�header�->�
Define�sales�document�type�and�select�the�billing�block�field�in�the�billing�
section.��This�request�can�later�be�reviewed�along�with�similar�ones,�-�if�
necessary,�by�another�department.�The�request�for�a�credit�or�debit�memo��can�
then�be�approved�or�rejected.�
Tips�by�:�Rajendran�
Configure�Intercompany�Stock�Transport�
Order�
Explain�STO.�
STO�is�Stock�Transport�order.�It�is�used�for�inter�company�transfer�of�goods.�
Plant�to�plant�transfer�and�even�transferring�raw�material�to�Third�party�
contractors�(Job�Work).�
-----------------------�Page�266-----------------------
The�Process�is�you�create�a�STO�do�delivery�against�the�STO�and�create�a�Billing
�
Document�against�the�STO.�
How�to�configure�the�inter-company�Stock�Transport�Order?�-�Prassee�
Material�should�exist�in�both�the�plants�(Delivering��&�Ordering),�
Internal�customer�should�be�assigned�to�the�ordering�plant�(�MM�->�Purchasing�
->�Purchase�Order�->�Setup�stock�transport�order�->�assign�the�internal�
customer�to�the�ordering�plant�and�assign�the�Sales�area�of�the�internal�
customer.�
Tcode�:�OMGN�
Assign�its�Sales�area�to�the�delivering�plant�
Assign�the�document�type�and�Delivery�type�������NB�and�NLCC�
Assign�the�Supplying�plant�-->�Receiving�Plant�-->�NB�
Take�the�delivering�plant�and�assign�the�sales�area.�
Vendor�master�has�to�be�created�and�assaign�the�supply�source�(�Delivering�
Plant).�
Create�a�puchase�order�ME21N�--->�Save�
Delivery�VL10�G�--->�Calculation�rule�(appropriate)�-->�Assaign�the�purchase�
order�number�here�and�execute.�
Select�the�Delivery�creation�line�and�do�the�back�ground�process.�
Start�the�log�display�and�see�the�delivery�document�number�by�the�documents�
button�
Goto�VL02N�-->�do�picking�and�PGI�-->�Then�do�the�MIGO�with�respect�to�the�
delivery�document.�
Billing�(Intercompany�pricing�conditions�should�be�set).�
SAP�SD�CIN�Configuration�
-----------------------�Page�267-----------------------
By�Shesagiri�
What�is�CIN?�
CIN�Means�Country�India�Version�
In�Indian�Taxing�procedure,�Excise�Duty�plays�a�vital�role�in�manufacturing�
cenario‟s.�Excise�related�configuration�is�known�as�CIN�configuration.�CIN��
Configuration�is�a�topic�in�itself.�
Some�info�on�CIN�Configuration�(it�may�not�appear�as�understandable�below,�
but�if�you�check�on�screen,�it�will�be�understood�better)�
Country�Version�India�comes�with�four�pricing�procedures�as�follows:�
-�JINFAC�(Sales�from�manufacturing�plants)�
-�JINEXP�(Export�sales)�
-�JINDEP�(Sales�from�depots)�
-�JINSTK�(Stock�transfers�
CIN:�IMG�>�Logistics�-�General�>�Tax�on�Goods�Movement�>�India�>�Basic�
Settings�>�Maintain�Excise�Registrations�
In�this�IMG�activity,�you�maintain�the�data�relating�to�your�excise�registration
s.�
-�Enter�each�of�your�excise�registrations,�specifying�a�four-character�code�for�
each�Excise�Registration�Ids�
In�this�activity,�you�maintain�excise�registration�IDs.�You�create�one�ID�for�ea
ch�
of�your�business's�excise�registrations.�
-�For�each�excise�registration�in�your�business�create�a�registration�ID,�and�
state:�
-�Which�taxes�the�registration�covers�(additional�excise�duty,�special�excise�
duty,�and�cess)�Fields�for�any�taxes�that�are�not�covered�will�be�hidden�in�
transactions�involving�excise�duty.�
-�The�maximum�number�of�items�to�be�printed�on�each�excise�invoice�
-�Whether�you�are�allowed�partial�CENVAT�credits�
Maintain�Registration�ID�NUMBER,�Excise�code�number,�excise�registration�
number�
ECC�Number:�Specifies�the�organization's�ECC�number.�
Excise�Registration�Number:��A�number�assigned�to�each�premises�or�location�
that�has�registered�as�a�manufacturer�with�the�excise�authorities.�
Every�entity�with�an�excise�registration�number�is�required�to�keep�its�own�
excise�books.�
Excise�range:�Specifies�the�excise�range�in�whose�area�the�excise�registration�i
s�
located.�
Excise�Division:�Specifies�the�excise�division�in�whose�area�the�excise�
registration�is�located.�
Excise�Collectorate:�The�code�of�the�excise�collectorate�in�whose�area�the�excis
e�
registration�is�located.�
Indicator�for�confirming,�AED�usage�Additional�Excise�duty�Percentage.�
These�are�livable�under�the�additional�duties�of�excise�act.�These�duties�are�in
�
addition�to�basic�excise�duty�and�special�excise�duty.�Example�-�Additional�
Excise�duty�is�livable�in�case�of�textile�products,�tobacco�and�sugar.�
Similarly�for�SED�CESS�Number�of�Items�in�Excise�Invoice�Shows�the�maximum�
number�of�line�items�that�the�authorities�allow�per�excise�invoice.�
-----------------------�Page�268-----------------------
Dependencies�-�This�information�is�used�when�you�create�an�excise�invoice�in�
Sales�and�Distribution�(SD)�for�factory�sales�and�for�other�movements.��This�
information�is�used�to�split�the�transfer�postings'�items�into�multiple�
subcontracting�challans.�
Excise�register�set�description:�Description�of�the�excise�registers�set.�
Partial�CENVAT�Credit:�Indicates�that�the�excise�registration�ID�is�allowed�to�
credit�only�a�portion�of�its�input�excise�duty�to�its�CENVAT�account�
Dependencies�-�When�you�post�a�goods�receipt,�the�system�splits�the�input�
excise�duty�on�the�material�into�its�deductible�and�nondeductible�amounts.�It�
posts�the�deductible�duty�to�the�appropriate�CENVAT�account,�and�adds�the�
nondeductible�duty�to�the�material�value.�
This�information�is�also�shown�when�you�post�the�vendor's�excise�invoice.�
Maintain�Company�Code�Settings.�
In�this�IMG�activity,�you�maintain�the�data�relating�to�your�company�codes.�
Document�Type�for�CENVAT�Postings.�
It�controls,�which�document�type�the�system�uses�when�making�CENVAT�
postings�in�Financial�Accounting�(FI).�Here�ED�is�document�type�for�cenvat�
posting.�
Indicator�for�providing�debit�account�overwriting�
Debit�Account�Overwrite�Indicator.�X�-�Indicates�debit�accounts�can�be�
overwritten.�Use�In�excise�journal�voucher�transaction.�It�provides�the�flexibil
ity�
to�the�user�to�enter�the�debit�account�of�his�choice�depending�on�the�nature�of�
transaction.�
Automatic�balance�Indicator�-�Excise�year�start�month.��The�calendar�month�
marking�the�beginning�of�the�excise�year.��This�start�month�represents�the�
month�for�the�start�of�the�excise�invoice�number�range.�The�month�04�is�
entered�here�indicating�April�of�the�calendar�year�as�the�start�month�for�excise
�
invoices.�Any�change�by�the�Excise�authorities�regarding�start�month�should�be�
taken�care�of�by�an�entry�in�this�field�and�initialization.�
Excise�invoice�selection�procedure�:Excise�invoice�selection�type.�To�indicate�t
he�
method�opted�by�the�company�for�selecting�the�excise�invoice.�It�can�be�either�
earliest�or�latest�invoices�that�were�received.�Number�of�excise�invoices�to�be�
selected�Indicates�the�number�of�excise�invoices�that�needs�to�be�selected�in�
the�excise�invoice�selection.�
Days�to�be�considered�for�excise�invoice�selection�Number�of�days�from�
document�date�for�excise�invoice�selection.�
Example�-�If�the�value�of�this�field�is�20�and�today�is�28-03-97.�The�excise�
invoice�selection�will�show�the�related�invoices�only�for�the�period�08-03-97�to
�
28-03-97.�
Document�type�for�TDS�FI�posting:�Financial�accounting�document�type�for�TDS�
posting.�
Document�type�for�FI�posting�on�Utilisation�Financial�accounting�document�type�
for�TDS�posting.�
Indicator�for�item�level�excise�duty�round�off�-�This�indicator�is�to�be�used�fo
r�
deciding�whether�Item�level�excise�
�duty�amount�rounding�off�is�required�during�procurement�cycle.�If�marked�'X'�
-----------------------�Page�269-----------------------
then�the�excise�duty�amount�will�be�rounded�off�to�the�nearest�rupee�at�the�
Purchase�order�level.�This�will�not�round�off�the�CENVAT�credit�to�be�taken.�If�
the�duty�amount�is�less�than�one�rupee�then�no�rounding�is�done�
Rounding�off�of�Excise�duty�for�outgoing�excise�invoice�-�You�can�round�off�the�
Excise�amount�to�be�paid�during�an�outgoing�
�Excise�invoice�by�marking�this�indicator�as�'X'.�The�rounding�is�done�at�the�it
em�
level�for�each�item�where�the�amount�is�greater�than�1�Rupee.�
Immediate�Credit�on�Capital�Goods�-�Instructs�the�system,�when�you�verify�a�
goods�receipt�for�capital�goods,�to�immediately�post�half�of�the�input�excise�du
ty�
to�the�appropriate�CENVAT�accounts.��The�rest�is�posted�the�CENVAT�on�hold�
account,�for�use�in�the�following�year.�
CVD�Clearing�Account�-�Specifies�which�G/L�account�the�system�credits�when�
you�take�a�CENVAT�credit�on�countervailing�duty�in�the�Incoming�Excise�
Invoices�transaction.�
Exchange�rate�type�-�Key�representing�a�type�of�exchange�rate�in�the�system.�
-�You�enter�the�exchange�rate�type�to�store�different�exchange�rates.�Example�-�
You�can�use�the�exchange�rate�type�to�define�a�buying�rate,�selling�rate,�or�
average�rate�for�translating�foreign�currency�amounts.�You�can�use�the�average�
rate�for�the�currency�translation,�and�the�bank�buying�and�selling�rates�for�
valuation�of�foreign�currency�amounts.�
Exchange�rate�type�to�be�used�for�Export�excise�duty�converts�-�When�you�are�
creating�an�Excise�invoice�for�export�sales�then�the�exchange�rate�for�duty�
calculation�will�be�picked�up�using�this�Exchange�rate�type.�
Maintain�Plant�Settings�-�In�this�IMG�activity,�you�maintain�excise�information�
relating�to�your�plants.�
Plant�Settings�-�In�this�activity,�you�maintain�excise�information�relating�to�y
our�
plants.�
For�each�plant:�
-�Specify�whether�it�is�a�manufacturing�site�or�a�depot.�
-�Assign�it�an�excise�registration�ID.�-�You�can�assign�the�same�ID�to�more�than
�
one�plant,�if�required.�
Depot�-�Indicates�that�the�plant�in�question�is�a�depot.�-�Depots�are�required�t
o�
prepare�register�RG�23D,�and�follow�different�procedures�for�goods�receipt�and�
invoice�generation.�
-�Number�of�goods�receipt�per�excise�invoice.�
-�Multiple�GR�for�one�excise�invoice,�Single�credit�
-�Multiple�GR�for�one�excise�invoice,�multiple�credit�
Maintain�Excise�Groups�-�In�this�IMG�activity,�you�define�your�excise�groups.�Fo
r�
each�excise�group,�you�can�also�control�how�various�excise�invoice�transactions�
will�work.�
Excise�Groups�-�In�this�activity,�you�define�excise�groups.�An�excise�group�
allows�you�to�maintain�a�separate�set�of�excise�registers�and�excise�accounts.�
The�RG�23A,�RG�23C�and�PLA�serial�numbers�are�created�for�an�excise�group.�
Recommendation�-�Under�normal�circumstances,�excise�authorities�require�
every�business�to�maintain�only�one�set�of�excise�registers�and�one�set�of�
accounts.���But�through�exemption�from�the�authorities,�multiple�books�can�be�
-----------------------�Page�270-----------------------
maintained.�
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�an
d�
would�like�to�avail�multiple�credit�mark�the�GRs�per�EI�as�'Multiple�GR's�for�on
e�
excise�invoice,�multiple�credit'.��Alternatively�if�you�want�to�availa�the�credi
t�
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�i
n�
the�pop-up.�
7.�If�the�indicator�'Folio�no�create'�is�marked�system�will�generate�Folio�numbe
rs�
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.�
Following�is�the�relation�between�excise�group,�plant�and�registration.�-�In�
define�excise�groups�in�Customizing.�
Then,�in�transactions�involving�excise�duty,�for�example,�when�you�post�a�
vendor's�excise�invoice,�you�specify�which�excise�group�you�are�using.�This�
information�tells�the�system�which�G/L�accounts�to�post�the�excise�to.��At�the�
end�of�the�period,�when�you�come�to�prepare�your�excise�registers,�you�create�
different�sets�for�each�excise�group.�
Indicates�that�the�plant�in�question�is�a�depot.�-�Depots�are�required�to�prepar
e�
register�RG�23D,�and�follow�different����procedures�for�goods�receipt�and�invoic
e�
generation.�
-�GR�Per�Excise�Invoice�
-�Multiple�GR�for�one�excise�invoice�,�Multiple�credit�
-�Multiple�GR�for�one�excise�invoice�,�Single�Credit�
Create�Excise�Invoice�Automatically�-�Instructs�the�system�to�automatically�
-----------------------�Page�271-----------------------
create�a�Sales�and�Distribution�(SD)�excise�invoice�immediately�you�create�a�
commercial�invoice�or�a�pro�forma�invoice.�
The�excise�invoice�is�created�in�the�background.�-�If�you�want�to�make�use�of�
this�function,�you�must�also�define�the�
�default�plant,�excise�group,�and�series�groups�in�Customizing�for�Sales�and�
Distribution�(SD),�by�choosing�Excise�Group�-�Series�Group�Determination.�
RG23D�Sales�Creation�and�posting�option�-�RG23D�Automatic�Option�if�selected�
will�create�Depot�excise�invoice�by����posting�the�selection�of�excise�invoices�
in�
single�step.���If�this�is�not�selected�then�you�need�to�separately�do�RG23D�
selection�
�followed�by�PGI�and�then�RG23D�verification�and�posting.��������If�you�need�
automatic�posting�of�RG23D�selection�then�the�Post�Goods�Issue�should�have�
been�completed�before�running�RG23D�selection.�
Default�excise�qty�in�GR�-�If�this�indicator�is�ticked�then�while�doing�Goods�
Receipt�using�'MB01'�system�will�default�the�excise�invoice�quantity�on�to�the�
Goods�receipt�document.�
Folio�number�for�depo�Posting�-�If�this�indicator�is�marked�then�while�creating�
Excise�invoice�for�other�movements�system�automatically�does�the�Verify�and�
Post.�You�need�not�separately�Post�the�excise�invoice�
Also�we�can�set�indicator�for�creation�of�part�1�for:�
-�Blocked�stock�
-�Stock�transport�order�
-�Consignment�stock�
Maintain�Series�Group�-�In�this�IMG�activity,�you�define�the�different�excise�
series�groups�within�your�company.�Series�groups�allow�you�to�maintain�
multiple�number�ranges�for�the�outgoing�excise�documents.���������Based�on�excis
e�
regulations�and�exemptions�from�the�authorities�you�can��������maintain�multiple
�
number�series�for�outgoing�documents.�But�each�of�these�series�has�to�be�
declared�to�the�excise�authorities.�
-�Define�excise�series�groups�based�on�type�of�outgoing�document�
-�Assign�series�group�to�excise�registration�ID�
-�If�no�financial�postings�are�required�for�an�Excise�invoice�in�this�seris�grou
p�
then�you�tick�the�'No�utilization'�indicator.�
-�If�the�CENVAT�has�to�be�paid�immediately�and�you�need�not�wait�for�the�Fort�
nightly�payment�then�mark�the�'Immediate�Utilization'�Iindicator.��������Example
�-�
You�could�define�two�series�groups,�group�001�for�excise�invoices,�and�group�
002�for�57�F4�documents.�
-�No�account�postings�for�CENVAT�in�sales�cycle�
-�No�utilization�Flag�
If�you�do�not�need�any�CENVAT�utilization�for�an�excise�invoice�but�would�like�t
o�
just�generate�an�excise�invoice�then�you�need�to�mark�this�indicator.�
If�the�flag�is�checked�then�system�will�create�an�Excise�invoice�in�the�given�
Series�group�but�there�will�not�be�any�account�postings�or�Part2�postings.�
Immediate�Utilization�of�CENVAT�-�Specifies�that�when�you�create�an�excise�
invoice,�the�system�immediately�pays�the�amount�from�CENVAT�and�creates�the�
Part�II�entry.�Such�invoices�will�not�be�listed�for�fortnightly�utilization.�
-----------------------�Page�272-----------------------
If�you�have�both�fortnightly�and�immediate�utilization�for�the�same�excise�
group,�the�account�determination�within�CIN�IMG�should�point�to�the�ED�interim�
account.�
Account�determination�for�immediate�payment�will�be�done�exactly�the�same�as�
being�done�for�fortnightly�utilization�program.�
Maintain�Excise�Duty�Indicators�-�In�this�IMG�activity,�you�maintain�the�excise�
duty�indicators.�
IMG�>�Logistics�-�General�>�Tax�On�Goods�Movement�>�India�>�Basic�Settings�
>�Determination�of�Excise�Duty�>�Select�Tax�Calculation�Procedure�
In�this�IMG�activity,�you�specify�which�tax�procedure�you�want�to�use�for�
determining�excise�duties�and�sales�taxes�on�input�materials�in����India.�
-�If�you�use�condition-based�excise�determination,�use�a�copy�of�the�tax�
procedure�TAXINN.�
-�If�you�use�formula-based�excise�determination,�use�a�copy�of�the�tax�
procedure�TAXINJ.�
This�tax�procedure�also�supports�condition-based�excise�determination,�so�that�
you�can�work�with�both�concurrently.�
We�strongly�recommend�that�new�customers�use�condition-based�excise�
determination.�Note�that�once�you�have�started�using�a�tax�procedure,�you�
cannot�switch�to�another�one,�otherwise�you�will�not�be�able�to�display�old�
documents.�
Maintain�Excise�Defaults�-�In�this�IMG�activity,�you�define�which�tax�procedure�
and�pricing�condition�types�are�used�in�calculating�excise�taxes�using�formula-�
based�excise�determination.�
If�you�use�condition-based�excise�determination,�fill�out�the�CVD�cond.�field�an
d�
leave�all�the�others�blank.�
If�you�use�formula-based�excise�determination,�fill�out�all�of�the�fields�as�
follows:�
-�Enter�the�tax�procedure�and�the�pricing�conditions�that�are�relevant�for�excis
e�
tax�processing.�
-�Specify�the�purchasing�and�sales�conditions�types�used�for�basic�excise�duty,�
additional�excise�duty,�special�excise�duty,�and�cess.�
-�Specify�the�conditions�in�the�sales�order�that�are�used�for�excise�rates.�
-�Specify�the�countervailing�duty�condition�type�used�for�import�purchase�
orders.�
See�also�:�SAP�Library�->�Logistics�->�Country�Versions�->�Asia-Pacific�-�
>�India�->�Materials�Management�(MM)�->�Condition-Based�Excise�
Determination�and�->�Formula-Based�Excise�Determination.�
IMG�>�Logistics�-�General�>�Tax�On�Goods�Movement�>�India�>�Basic�Settings�
>�Determination�of�Excise�Duty�>�
Condition-Based�Excise�Determination�
When�you�enter�a�purchasing�document,�for�example,�a�purchase�order,�the�R/3�
System�automatically�calculates�the�applicable�excise�duties�using�the�condition
�
technique.�
Features�:�The�standard�system�comes�with�two�tax�calculation�procedures.�
TAXINN�is�only�supports�condition-based�excise�determination,�whereas�TAXINJ�
-----------------------�Page�273-----------------------
supports�condition-based�excise�determination�and�formula-based�excise�
determination.�Both�tax�procedures�contain�condition�types�that�cover�all�of�the
�
excise�duties�and�sales�taxes�applicable.�
Since�the�exact�rates�of�excise�duty�can�vary�on�a�large�number�of�factors,�such
�
as�which�vendor�you�purchase�a�material�from,�or�which�chapter�ID�the�vendor�
stocks�the�material�under,�you�create�condition�records�for�every�sort�of�excise
�
duty.�
When�you�come�to�enter�a�purchasing�document,�the�system�applies�the�excise�
duty�at�the�rates�you�have�entered�in�the�condition�records.�
Customizing�:�Make�the�settings�in�Customizing�Basic�->�India�->�for�Logistics�–�
General,�by�choosing�Taxes�on�Goods�Movements�Account�->�Excise�Duties�
Using�Condition�Technique�and�…->�Settings�Determination.�
These�activities�include�one�activity�where�you�define�a�tax�code�for�condition-
�
based�excise�determination.�
Master�Data�-�Create�condition�records�for�all�excise�duties�that�apply,�and�ent
er�
the�tax�code�for�condition-based�excise�determination�in�each.�
Day-to-Day�Activities�-��When�you�enter�a�purchase�order�or�other�purchasing�
document,�enter�the�tax�code�for�condition-based�excise�determination�in�each�
line�item.�The�system�then�calculates�the�excise�duties�using�the�condition�
records�you�have�created.�
When�the�ordered�materials�arrive,�you�post�the�goods�receipt�and�the�excise�
invoice.�The�system�posts�the�excise�duty�to�the�appropriate�accounts�for�
deductible�input�taxes�when�you�enter�the�excise�invoice.�
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�
-----------------------�Page�274-----------------------
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�fina
l�
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.�
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.�
Define�Tax�Code�for�Purchasing�Documents�-��In�this�IMG�activity,�you�define�a�
tax�code�for�the�purposes�of�calculating�excise�duty�when�you�enter�purchasing�
documents.�Only�carry�out�this�activity�if�you�use�condition-based�excise�
�determination.�
-�Create�a�new�tax�code,�and�set�the�tax�code�type�to�V�(input�tax).�Do�not�
make�any�other�settings�for�it.�
-----------------------�Page�275-----------------------
-�Assign�Tax�Code�to�Company�Codes�
In�this�IMG�activity,�assign�the�tax�code�for�purchasing�documents�to�the�
company�codes�where�it�will�be�used.�
Only�carry�out�this�activity�if�you�use�condition-based�excise�determination.�
Classify�Condition�Types�-�In�this�IMG�activity,�you�specify�which�condition�typ
es�
you�use�for�which�sort�of�tax.�Note�that�this�only�applies�to�condition�types�th
at�
you�use�with�the�new�excise�determination�method.�The�system�uses�this�
information�when�you�create�a�document�from��another�one.�For�example,�when�
you�enter�an�incoming�excise�invoice�from�a�
�purchase�order,�or�when�you�create�an�outgoing�excise�invoice�from�a�sales�
order,�the�system�determines�the�various�excise�duties�in�the�excise�invoice�
using�the�information�that�you�have�entered�here.�In�addition,�when�you�create�
a�purchasing�document,�the�system�only�uses�the�condition�types�that�you�enter�
here.�
-�For�taxes�on�purchases,�use�the�condition�types�contained�in�the�tax�
procedure.�
-�For�taxes�on�sales,�use�the�condition�types�contained�in�the�pricing�
procedures.�
The�standard�system�comes�with�sample�settings�for�the�tax�calculation�
procedures�and�pricing�procedures.�
Use�these�settings�as�a�basis�for�your�own.�
IMG�>�Logistics�-�General�>�Tax�On�Goods�Movement�>�India�>�Account�
Determination�
Define�G/L�Accounts�for�Taxes�-�In�this�IMG�activity,�you�specify�which�G/L�
accounts�you�will�use�to�record�which�taxes.�
Requirements�-�You�have�set�up�G/L�accounts�for�each�of�the�processing�keys�
listed�below.�
-�Assign�an�account�to�each�of�the�following�posting�keys.�The�accounts�for�VS1,
�
VS2,�and�VS3�are�used�as�clearing�accounts�during�excise�����invoice�verificatio
n.�
-�VS1�(basic�excise�duty)�
-�VS2�(additional�excise�duty)�
-�VS3�(special�excise�duty)�
-�VS5�(sales�tax�setoff)�
-�MWS�(central�sales�tax)�
-�MW3�(local�sales�tax)�
-�ESA�(service�tax)�
-�ESE�(service�tax�expense)�
Specify�Excise�Accounts�per�Excise�Transaction�-�In�this�IMG�activity,�you�
specify�which�excise�accounts�(for�excise�
�duty�and�CENVAT)�are�to�be�posted�to�for�the�various�transaction�types.�����Ent
er�
all�the�accounts�that�are�affected�by�each�transaction�type.��If�you�use�sub�
transaction�types,�enter�the�accounts�for�each�sub�transaction�type�as�well.�
Transaction�type�UTLZ�is�used�for�determining�accounts�only�while�posting�
excise�JVs�and�also�if�the�payment�of�excise�duty�has�to�be�done�fortnightly.�
The�fortnightly�CENVAT�payment�utility�picks�up�the�credit�side�accounts�from�
the�transaction�types�of�GRPO,�EWPO,�and�TR6C�for�determining�the�CENVAT�
-----------------------�Page�276-----------------------
and�PLA�accounts.�There�is�no�separate�transaction�type�for�fortnightly�
payment.�
Example:�
-�Excise�TT�DC�ind�Account�name�
-�GRPO�CR�CENVAT�clearing�account�
-�GRPO�CR�RG�23�BED�account�
-�GRPO�DR�CENVAT�on�hld�account�
Specify�G/L�Accounts�per�Excise�Transaction�-�In�this�IMG�activity,�you�assign�
the�excise�and�CENVAT�accounts�to�G/L�
�accounts.�When�you�come�to�execute�the�various�transactions,�the�system�
determines�which�G/L�accounts�to�post�to�by�looking�at�the:�
-�Excise�group�
-�Company�code�
-�Chart�of�accounts�
Furthermore,�if�you�want�separate�account�determination�settings�within�an�
excise�group,�you�can�also�use�sub�transaction�types.�
Requirements�
You�have�already:�
-�Defined�the�G/L�accounts�
-�Defined�the�excise�groups�
-�Maintained�the�transaction�accounts�
Activities�-�For�each�excise�group,�assign�the�excise�and�CENVAT�accounts�to�
G/L�accounts.�For�most�businesses,�one�set�of�accounts�will�suffice�for�all�
transactions.�
Note�:�you�need�not�remit�the�CENVAT�to�the�excise�department�immediately,�
so�maintain�the�credit�account�for�transaction�type�DLFC�as�an�excise�duty�
interim�account.�This�will�be�set�off�when�you�remit�the�duty.��Config�setting�
needed�to�be�done�in�order�to�get�the�Excise�Details�Screen�in�Material�Master.�
Even�though�this�functionality�is�available�in�enterprise�version,�a�small�
configuration�step�has�to�be�made�in�Screen�Sequences�for�Material�Master.�
Following�document�helps�you�to�do�this�configuration.�
-�Material�Master�à�Logistics�General�
1.�Go�to�IMG�Define�Structure�of�Data�Screen�for�each�Configuring�the�Material�
master�Screen�Sequence.�
2.�Select�your�screen�sequence.�Usually�it�would�be�21.�Select�the�same�and�
click�on�Data�Screen�in�the�left�frame.�
3.�Once�the�data�screens�are�exhibited,�select�data�screen�no.�15,�ie.�SSq.�
21and�Scrn�15,�which�is�“Foreign�Trade:�Import�Data”.�Select�the�same�and��
click�on�Sub�screens�in�the�left�frame.�
4.�Go�to�the�last�sub�screen�i.e.�21-15-6�-�SAPLMGD1-�0001�and�select�the�
same.�Click�on�tab�view�sub�screen�and�ensure�that�the�sub�screen�is�blank.�
5.�Now�in�the�last�sub�screen�i.e.�no.6�you�delete�SAPLMGD1�–�0001�and�
instead�add�SAPLJ1I_MATERIAL_MASTER�and�in�the�screen�no.�2205.�
6.�Save�the�setting.�
7.�Create�a�Material�Master�and�check�whether�in�Screen�Foreign�Trade�
–�Import,�Excise�related�sub�screen�appears.�
-----------------------�Page�277-----------------------
Customizing�Customer�Hierarchy�in�SD�
How�to�configure�and�maintain�the�SD�Customer�Hierarchy?�
All�the�customizing�is�in�SD/Master�Data/Bussiness�
Partner/Customers/Customers�hierarchy�
1)�Define�hierarchy�type:�just�put�and�ID�and�a�name�to�the�new�hierarchy.�
2)�Set�partner�determination:�if�you�want�to�user�the�hierarchy�in�price�
determination,�then,�in�the�orders,�at�the�header�level,�you�have�to�have�a�
Partner�Procedure�with�a�partner�function�for�each�level.�In�the�partner�
procedure,�in�each�partner�function�you�must�indicate�the�source�partner�
function.�With�this�informacition,�in�the�order,�you�obtain�the�bussiness�partne
r�
for�each�partner�function.�
3)�Assign�acount�groups:�you�indicate�which�accounts�groups�are�allowed�for�
being�part�or�your�hierarchy.�
4)�Assign�sales�areas:�symple�you�indicate�wich�sales�areas�are�allowed�in�your�
hierarchy.�(Here�you�can�customize�common�sales�areas,�just�for�not�having�to�
build�de�hierarchy�in�all�the�different�sales�areas).�
5)�Assigning�hierarchy�type�for�pricing:�you�indicate�which�classes�of�
documentos�uses�hierarchy�in�pricing�determination.�
It�is�possible�to�maintain�so�called�customer�hierarchies.�This�might�be�useful�
when�for�example�you�create�a�condition�discount�for�a�customer�that�is�part�of�
such�a�hierarchy�structure.�All�subnodes�in�the�hierarchy�below�that�customer,�
will�thus�receive�the�same�discount.�
Customer�hierarchy�setup,�firstly�decide�the�hierarchy�type�to�be�used.�
The�standard�is�type�A.�
You�can�also�assign�a�partner�function�to�the�customer�so�that�the�higher�level�
customer�in�the�hierarchy�is�copied�into�a�sales�order�as�a�partner�function�-�b
ut�
you�don't�need�that�right?�
Next�assign�your�customer�account�group�to�the�hierarchy�type.�And�enter�the�
combinations�that�will�be�allowed�for�creating�the�hierarchy.�
You�want�to�assign�a�ship-to�to�a�payer.�So�enter�the�ship�to�account�group�and�
enter�the�payer�account�group�as�the�higher�level.�
You�must�also�make�an�entry�for�permitted�sales�area�assignments.�So�if�you�
want�to�a�hierarchy�for�customers�in�the�same�sales�area�then�enter�the�sales�
area�and�enter�the�same�one�as�the�higher�level�sales�area.�
All�these�settings�can�be�found�in�the�IMG.�Under�SD�-�master�data�-�business�
partners�-�customers�-�customer�hierarchy�
You�use�for�example�customer�hierarchy�when�you�have�an�company�like�
Unilever�and�you�agree�both�on�a�discount.�Unilever�does�have�different�
locations�/�businesses�and�you�have�to�maintain�the�discount�for�all�customers.�
If�you�use�a�customer�hierarchy�you�can�maintain�the�discount�for�the�partner�in
�
the�top�of�the�hierarchy�and�in�this�way�it�will�be�valid�for�all�customers�in�t
he�
hierarchy.�
SAP�SD�Tips�by�:�Sam�
Common�Distribution�Channel�and�Division�
-----------------------�Page�278-----------------------
How�to�configure�common�distribution�channel�and�division?�
You�can�define�common�distribution�channels�and�divisions.�This�is�possible�for�
two�areas�of�SAP,�for�all�master�relevant�data,�and�for�all�condition�relevant�
data.�
The�path�is�as�follows:�
IMG�->�Sales�and�distribution�->�Master�data�->�Define�common�distribution�
channels.�
IMG�->�Sales�and�distribution�->�Master�data�->�Define�common�divisions.�
Transaction�Code�-�The�code�here�is�[�VOR1�].�
After�creating�the�organizational�structure�and�relevant�master�records�you�
want�to�use�as�the�masters,�that�is,�in�the�distribution�channels�and�divisions�
you�are�going�to�use�as�a�reference,�you�can�group�distribution�channels�and�
divisions�separately�for�master�data�(which�combines�customer�master�and�
material�master�records),�group�condition�records,�or�both�master�data�and�
condition�records.�
Let‟s�say�you�have�a�product�range�that�is�not�different�for�the�four�different��
distribution�channels�you�have�(the�channels�could�be�telesales,�retail,�industr
y,�
and�wholesale.)�Neither�is�there�a�difference�in�the�customers‟�details�when�they�
�
purchase�through�one�or�the�other.�Thus,�you�will�not�want�to�create�a�multiple�
of�four�views�of�customer�master�and�material�master�records.�Merely�create�
the�customer�master�records�and�material�master�records�in�one�of�the�
distribution�channels,�such�as�retail.�Then�assign�the�other�distribution�channe
ls�
you�created�in�the�organizational�structure�setup�to�this�one.�
Don‟t�forget�this�means�you�can�only�create�or�change�master�data�in�the��
distribution�channel�that�is�being�referenced.�In�the�scenario�above,�this�means
�
you�can�only�change�data�for�the�retail�distribution�channel.�Even�if�you�should
�
access�a�customer�or�material�master�in�change�mode,�press�F4�(possible�
entries),�and�select�telesales,�industry,�or�wholesale,�you�will�receive�a�messa
ge�
“Sales�area�is�not�defined�.�.�.�”�
The�same�is�true�for�the�sharing�of�conditions.�If�conditions�are�shared,�you�
need�only�create�a�condition�in�the�distribution�channel�or�division�you�are�usi
ng�
as�the�reference.�Obviously,�this�only�pertains�to�conditions�that�have�the�
distribution�channel�and/or�division�in�their�key,�such�as�a�price�based�on�sale
s�
area."�
Edwin�
Define�Account�Assignment�Group�
How�to�configure�the�Sales�Account�Determination?�
Field�found�in�Material�Master�Sales�Organization�2.�
To�define�the�General�Leger�posting�:-�
IMG�->�Sales�and�Distribution�->�Account�Assignment/Costing�->�
Revenue�Account�Determination�
-----------------------�Page�279-----------------------
�������->�Assign�G/L�Accounts�
With�this�link,�the�material�that�used�this�account�assignment�group�will�be�
posted�with�the�desired�G/L�accounts�during�Billing.�
User�will�not�be�able�to�Release�the�billing�document�to�Accounting�if�this�is�n
ot�
setup.�
If�you�happend�to�assign�it�via�Cust.Grp/MaterialGrp/AcctKey,�then�you�can�
let�your�user�use�this�report�to�check�the�material�assignment.�
*�Transaction�code�VKOA�
REPORT�ZMATNR_AC_ASSIGN�LINE-SIZE������������132�NO�STANDARD�PAGE�HEADING�
��������������LINE-COUNT�044(001).�
TABLES:�MARA,�
������MVKE,����"Sales�Data�for�Material�
������C001.�����"Cust.Grp/MaterialGrp/AcctKey�
SELECT-OPTIONS:�S_MTART�FOR�MARA-MTART�DEFAULT�'DIEN',�
�������������������������S_MATNR�FOR�MARA-MATNR,�
�������������������������S_VKORG�FOR�MVKE-VKORG�DEFAULT�'ALL'.�
SELECT�*�FROM�MARA�WHERE�MTART�IN�S_MTART�
���������������AND�MATNR�IN�S_MATNR.�
��CLEAR�MVKE.�
��SELECT�SINGLE�*�FROM�MVKE�WHERE�MATNR�=�������������MARA-MATNR�
����������������������AND�VKORG�IN�S_VKORG.�
��CLEAR�C001.�
��SELECT�SINGLE�*�FROM�C001�WHERE�KTGRM�=�MVKE-KTGRM.�
��WRITE:/�MVKE-MATNR�UNDER�'Material',�
��������C001-KTGRD�UNDER�'Cust�Grp',�
��������MVKE-KTGRM�UNDER�'Matl�Grp',�
��������C001-KVSL1�UNDER�'Acct�Key',�
��������C001-SAKN1�UNDER�'G/L�From',�
��������C001-SAKN2�UNDER�'G/L�To�������'.�
ENDSELECT.�
TOP-OF-PAGE.�
FORMAT�COLOR�COL_TOTAL.�
���WRITE:�/�SY-DATUM,�SY-UZEIT,�SY-REPID,�
���������050�'Material�Sales�Account�Assignment',�
���������120�SY-UNAME,�SY-PAGNO.�
���SKIP.�
���WRITE:�/001�'Material',�
���������020�'Cust�Grp',�
���������030�'Matl�Grp',�
���������040�'Acct�Key',�
���������050�'G/L�From',�
���������060�'G/L�To��'.�
���SKIP.�
�SAP�SD,�PP,�CO,�FI,�PM,�MM,�PS,�QM,�SM,�HR,�BW,�APO,�Basis,��ABAP/4,�
�������������������������������Certification,�Books�
-----------------------�Page�280-----------------------
Block�Sales�Document�Type�/�Delivery�/�Billing�by�Customer�
When�there�is�a�temporarily�stop�of�business�with�a�customer,�you�can�block�
new�orders�to�be�created�for�this�customer.�You�can�have�the�options�of�
blocking�all�the�work�flow�or�let�the�delivery�and�billing�to�continue�for�any�o
pen�
orders.�
VD05�-�Block/Unblock�Customer�
OVAS�-�Sales�Order�Type�Blocking�reasons�
OVAL�-�Blocking�reasons�links�with�Sales�Order�Type�
OVZ7�-�Delivery�Blocking�reasons�
OVV3�-�Billing�Blocking�reasons�
In�4.6x,�if�you�found�that�your�Sales�Order�Billing�Block�is�not�working,�it�is�
because�you�need�to�build�the�Billing�Block�for�the�Billing�Type.�
SM30�-�Table/View�������V_TVFSP�
Return�to�:-�
Block�Material�in�Sales�Order�
Is�there�a�way�for�me�to�block�a�material�from�ever�being�entered�in�the�
Sales�Order,�if�so�how?�
--------------------------------------------------------------------------------
---------�
------�
If�you�want�a�material�to�be�blocked,�go�to�the�Basic�data�1�view�of�the�
material,there�in�the�genral�data�you�have�"�X-plant�material�status�".�Also�in�
Cost�estimate�1�view�of�the�material�you�have�Plant�Specific�Material�status.�Us
e�
the�options�available�to�block�the�material�in�these�two�views.�
You�cannot�use�the�material�in�sales�order�
Prakash.k�
--------------------------------------------------------------------------------
---------�
------�
Use�the�material�exclusion�function:�
FUNCTIONALITY:�
SD>�Master�data�>�Products�>�Listing/Exclusion>�Create�
(�Tcodes�VBO1,�VB02,�VB03)�
Enter�the�list/exclusion�type�B001:�For�the�required�
customer:�
Enter�Maintain�materials�>�Save�>�Exit�
Create�the�order�and�enter�material�excluded�to�test�exclusion.�
CONFIGURATION:�IMG�SETTINGS�
For�IMG�settings;�Go�to�IMG�>�SD�>�Basic�Functions>Listing/Exclusion�
ENsure�that�the�listing/exclusion�procedure�is�activated�for�your�order�type.�Yo
u�
can�also�create�your�own�condition�types�access�sequences�and�procedures�or�
use�the�SAP�provided�ones.�
Kris�J�
--------------------------------------------------------------------------------
---------�
------�
Additionally,�another�option�is�the�sales�block�in�the�material�master...�
It�is�in�one�of�the�two�sales�data�tabs�and�you�are�able�to�configure�specific�
-----------------------�Page�281-----------------------
blocks�that�allow�it�to�be�entered�on�credits�but�not�on�orders,�blocked�from�al
l�
activity,�allowed�for�quotes�only,�etc.��It�is�one�setting�that�becomes�sales�ar
ea�
specific�and�can�easily�be�removed�if�you�change�your�mind.��������It�also�has�a
n�
effectivity�date�that�can�be�used.�
Regina�DeMita�
Wrong/duplicate�RE�Created�
�������Check�Document�Flow�for�RE�Decision:-�
��������������������No�Goods�Issue�and�No�Credit�Memo�created����������������������������Reject�the�sales�order�item���������������������No�Goods�Issue�and�Credit�Memo�created����������������������������Cancel�Credit�Memo����������������������������Reject�the�sales�order�item���������������������Goods�Issue�and�Credit�Memo�created����������������������������Create�another�OR�to�offset�the�credit�memo�created.�Treat�this�as�a�normal�OR�process.�����Ensure�that�account�receivable�is�informe
d�
by�typing�in�the�item�text.���Please�do�not�send�invoice�to�customer�as�the�RE�i
s�
wrongly/duplicate.�
Note:�When�you�create�another�OR,�the�delivery�department�may�actually�go�
and�delivery�the�goods�to�customer.��Thus,�it�is�important�to�inform�them�that�
this�OR�is�for�internal�adjustment.��The�process�of�posting�the�goods�issue�must
�
be�done�by�the�delivery�side�for�proper�flow.�
Return�to�:-�
Sales�Order�Item�price�is�grey�
�������Retrieve�the�sales�order��������Click�the�sales�order�item��������Click�Environment�->�Document�flow��������If�there�is�any�Billing�Invoice�including�partial�deliveries,�price�cannot�be�
changed.�
Return�to�:-�
Partner�Procedures�
Sold-to-party�(Customer�Master)�-�Payment,�Tax�determination�
Bill-to-party�-�Address�to�send�the�invoice�to�
Ship-to-party�-�Deliver�the�goods�to�
Payer�-�Pay�to�who�(�a�company/person�name)�
VOPA�-�Maintain�Partner�Determination�
�������Click�Partner�Object��������Click�Partner�Procedures��������Double�Click�on�the�Procedures�Line�Items�To�pass�the�partner�function�contact�person�(CP)�data�to�the�ship-to-party�in�th
e�
delivery�document.�
-----------------------�Page�282-----------------------
�������Go�to�the�Partner�Determination�procedure�for�you�sales�order�type.�Look�for�the�column�that�is�labelled�SOURCE.�
Put�SH�against�partner�function�CP�and�it�will�assign�CP�from�ship-to-party�to�
aftewards.�
As�long�as�you�have�CP�in�your�delivery�document,�it�will�be�copied�from�SO�to�
Delivery�properly.�
Movement�type�determination�and�Availability�Check�
SM30�-�Table�View�-�V_TVEPZ�->�Assign�schedule�line�categories�
�������First�check�the�Proposed�schdule�line�category�(SchLC)��������-�double�click�on�
the�line�item�
VOV6�-�Maintain�the�schedule�line�categories�-�double�click�on�the�line�item�
�������For�example,�you�can�control�the�default�returns�movement�type.��������651�-�two�steps�-�with�a�transfer�posting�using�453��������653�-�one�steps�-�direct�post�to�unrestricted�used�Control�the�Transaction�Flow�(tick�to�activate�the�function)�
�������transfer�of�requirement��������for�availability�check�for�sales��������production�allocation�active�Return�to�:-�
Sales�reservation�
Sales�reservation�takes�place�automatically�through�availability�check�
The�setting�is�on�the�checking�group�(�OVZ2�-�Define�Checking�Groups�).�
You�must�set�the�"Accumul."�column.�Without�setting�this�it�will�only�check�
availability�but�not�reserve�it!�
SAP�recommend�Accumul.�=�3�->�Accumulate�the�requirements�quantity�when�
creating�and�accumulate�the�confirmed�quantity�when�making�changes.�
For�manual�reservation,�you�can�used�MB21,�movement�type�251�-�Goods�
Issue�for�sales.�
To�activate�the�Sales�Order�number�field,�do�the�followings�:-�
Activate�transaction�OMBW�
double�click�movement�type�251�
double�click�additional�acct.�assign.�
Tick�the�required/optional�button�as�per�your�requirement.�
The�user�have�to�manage�the�maual�reservation�using�MBVR.�
Reserving�material�without�sales�order�
In�Order�to�reserve�the�specific�materials�for�a�particular�customer,�use�
Strategy�50�to�plan�your�MRP�with�the�materials�getting�reserved�for�customer�
when�you�make�Ind/Collective�requirement(1)�in�MRP4�view�of�Material�Master�
or�you�can�create�a�manual�reservation�against�that�particular�material�and�give
�
the�customer�name�in�the�Receipent�Field�so�that�you�can�easily�identify�the�
Material�which�belong�to�the�Customer�
-----------------------�Page�283-----------------------
Return�to�:-�
SAP�ABAP/4�Programming,�Basis�Administration,�Configuration�Hints�and�Tips�
Sales�Order�Stock�
Sales�Order�Stock�are�stock�with�Special�Stock�type�E.�It�can�fall�into�the�usua
l�
stock�categories�such�as�unrestricted,�blocked�etc.�but�"belongs"�to�a�sales�
order.��For�example,�you�create�a�sales�order�for�a�part�and�assign�a�sales�item
�
category�that�generates�an�individual�requisition,�the�requirement�has�an�
account�assignment�linking�it�to�the�sales�order�schedule�line,�you�convert�that
�
requisition�to�a�Purchase�Order.�
When�you�receive�the�Purchase�Order,�the�stock�is�placed�in�sales�order�stock.�
It�will�show�against�the�sales�order/sales�order�line.�It�can�only�be�delivered�
against�that�sales�order�line.�Any�availability�check�etc�for�that�material�on�a
ny�
other�sales�order�will�not�take�it�into�account�as�it�is�not�available�except�to
�the�
sales�order�line�the�stock�is�assigned�to.�
Return�to�:-�
Analyze�the�difference�between�Forecast�and�Confirm�sales�orders�
MD73�-�Display�Total�Requirements�
Enter�theMaterial�or�MRP�controller�you�want�to�analyze.�
Assignment�field�options�:-�
1�-�If�you�with�to�look�at�how�the�planned�independent�requirements�have�been�
match�to�the�sales�order.��Sales�order�which�
����are�over�and�above�that�forecasted�are�not�shown.�
2�-�If�you�are�interested�primarily�in�seeing�what�sales�order�are�over�and�abov
e�
the�sales�forecast.�
3�-�If�you�are�interested�in�seeing�all�the�sales�order�with�indication�of�wheth
er�
or�not�they�have�been�anticipated�in�the�forecast.�
4�-�If�you�wish�to�see�all�the�three�reports�of�the�above�three�options�together
.�
��-�Blank�if�you�with�to�see�a�complete�list�of�sales�order,�without�any�indicat
ion�
of�whether�they�have�been�anticipated�
����in�the�forecast.�
Return�to�:-�
SAP�ABAP/4�Programming,�Basis�Administration,�Configuration�Hints�and�Tips�
Backorder�Processing�
Backorder�processing�is�a�functionality�in�SAP�where�you�can�change�the�
committments�and�over-ride�the�blockage�of�stocks�
marked�against�sales�documents/deliveries.�For�e.g.�you�receive�an�order�from�
a�very�important�customer�for�material�"A"�but�
the�entire�quantity�of�A�is�committed�to�another�customer�"B"�via�earlier�sales�
orders�and�this�is�where�BACKORDER�processing�helps�you�to�change�the�
committment�and�shift�stock�due�for�B�to�A.�This�is�the�benefit�of�this�
funtionality.�
OMIH�-�Checking�rule�for�updating�backorders�
OPJL����-�Define�new�checking�rule�
OPJJ����-�Define�scope�of�check�
V_RA�-�Backorder�Processing�
Data�selection:-�
-----------------------�Page�284-----------------------
Sold-to-party����������Customer�code�����������Mandatory�
Sales�Organization�������������������������������Mandatory�
Distribution�Channel�����������������������������Mandatory�
Division�����������������������������������������Mandatory�
Changed�confirmed�quantity�:-�
Tick�the�material�you�want�to�changed�and�click�the�Backorder�button�
Confirmed�quantity�that�still�can�be�changed�are�highlighted.�
V.15�-�Backorder�List�
Sales�Organization�������������������������������Mandatory�
Distribution�Channel�����������������������������Mandatory�
Division�����������������������������������������Mandatory�
Third�Party�Order�Processing�
Third�party�order�processing�is�as�follows:�
Assume�three�companies�X,�Y�and�Z�
X�-�The�company,�
y�-�The�customer�
Z�-�Vendor�
When�ever�X�gets�a�PO�from�Y�to�supply�some�goods,�X�has�an�option�of�either�
manufacturing�those�goods�or�procuring�those�goods.�
If�he�is�procuring�the�goods,�there�are�two�methods�that�are�generally�
followed:�
Method�1)�After�receiving�the�PO�from�Y,�X�creates�a�sales�order�against�Y.�
Now�at�the�same�time�he�also�creates�a�PO�to�a�vendor�Z�to�produce�the�goods�
Z�produces�the�goods�and�supplies�to�X�
X�receives�the�goods�from�Z�
Then�X�delivers�the�same�goods�to�Y.�
After�that�X�invoices�Y�and�Z�invoices�X.�
Note�:�Here�there�is�no�direct/�Indirect�relation�between�Z�and�Y.�
This�process�is�known�as�Trading�Process.�and�the�Material�here�is�created��with
�
Material�type�HAWA.�
The�other�method�is�a�Third�party�order�processing�method:�
Here�the�glaring�difference�is�that�instead�of�Z�supplying�the�material�to�X�and
�X�
in�turn�supplying�the�same�material�to�Y.�
X�authorizes�Z�to�supply�the�material�to�Y�on�his�behalf�and�notify�him�once�the
�
delivery�is�complete.�
Now�Z�supplies�the�material�to�Y�and�acknowledges�the�same�to�X.�
-----------------------�Page�285-----------------------
Z��will�send�a�copy�of�delivery�acknowledgement�and�invoice�to�X.�
After�receiving�the�delivery�confirmation�and�invoice�from�Z,�X�has�to�verify�th
e�
invoice�and�this�process�is�known�as�invoice�verification�and�is�done�in�SAP�
through�Tcode�MIRO.�
The�next�step�for�X���is�to�create�an�invoice�and�submit�to�Y�
Only�after�the�invoice�verification�document�is�posted��then�only�X�can�create�a
n�
invoice�for�Y.�
This�is�the�business�flow�that�is�followed�for�third�party�order�configuration.�
There�are�few�steps�that�have�to�be�configured�to�enable�the�system�to�function�
as�mentioned�above.�
Step1)�
If�you�are�always�followwing�a�third�party�process�for�a�material�then�you�have�
to�create�the�material�using�item�category�group�BANS.�
The�procument�type�should�be�marked�as�External�procurement�(F)�in�MRP�2�
view�of�the�material�master�record.�
if�you�are�not�always�allowing�third�party�order�processing�then�u�can�create�a�
material�master�record�with�item�category�group�as�NORM�and�the�procurement�
type�should�be�marked�as�(�X)�meaning�both�types�of�procurment�(�in�house�
manufacturing�and�external�procurement).�
step�2)�
the�item�category�in�the�order�should�be�manually�changed�as�TAS.�
For�that�you�need�to�confugure�the�item�category�determination�
ord�type�+�item�cat�grp�+�usge�+�Hiv�level�=�Item�cat�+�Manual�item�cat�
OR�+�NORM�+���������+������=�TAN�.�+�TAS�
OR�+�BANS�+���������+������=�TAS�
Step�3)�
make�sure�that�during�the�item�category�configuration�for�TAS��you�need�to�
mark�relevnat�for�billing�indicator�as�F�
step�4)�
The�schedule�line�cateogry�for�this�type�should�be�CS.�
make�sure�that�you�mark��subsequent�type�as�NB�-�purchase�requisition��in�this�
schedule�line�category�as�this�will�trigger�the�purchase�requision�order�
-----------------------�Page�286-----------------------
immediately�after�the�creation�of�the�sales�order�and�the�PO�to�vendor�is�
created�against�this�purchase�requiesion.�
Srinivas�Product�Group�and�Sales�BOM�
My�client�clubs�together�certain�products�with�quantities�in�something�
they�call�Product�Group.������The�customer�calls�in�and�orders�for�the�
product�group�and�automatically�gets�in�all�the�associated�materials.�
Do�we�need�a�Sales�Order�BOM�to�handle�this?�
Yes,�you�have�to�Confugure�the�Sales�BOM.�������But�the�confugaration�of�Sales�B
OM�
depends�upon�certain�conditions�like:�
If�you�want�to�create�the�product�group�and�price�it�at�header�level�or�
If�you�want�to�assemble�the�products�and�depending�upon�the�assemblies�you�
want�to�price�.�
For�eg.��if�the�customer�asks�for�a�certain�combinationa�of�Material�A,�B�and�C�
respectively,�
then�you�create�a�Material�Master�record�Material�D�with�item�category�group�as�
LUMF.�
While�the�Materials�A,�B�and�C�are�created�with�standared�item�category�groups�
NORM�only.�
Then�create�a�sales�BOM�using�Tcode�CS01�and�enter�the�following�details:�
Material�:�Material�D�
Plant�:�Plant�in�which�you�created�the�material.�
BOM�Usage�:�5�(Sales�and�Distribution)�
then�give�the�Materials�A,�B,�and�C�and�give�their�respective�quantities.�
Before�you�have�to�create�pricing�condition�records�for�Materials�A,�B,�and�C.�
Then�configure�the�item�categories�(�T�-�code�:�VOV4).�
When�processing�the�sales�order,�just�give�the�Material�D�and�the�system�will�
pick�up�the�corresponding�assemblies�for�that�material�and�populate�in�the�
order.�
The�item�category�for�the�header�item�will�be�TAP�
and�the�item�cateory�for�the�items�will�be�TAN,�
In�this�cas�the�Material�D�is�called�as�the�higher�level�Item�,�and�all�the�
assemblies�are�called�as�the�subitems.�
Here�the�subitems�are�relevant�for�pricing�and�delivery�where�as�the�header�
item�is�not�relevant�for�neither�pricing�nor�delivery.��It�just�acts�as�a�text�i
tem.�
This�type�of�configaration�of�BOM�is�known�as�pricing�at�item�level.������This�i
s�
used�when�you�dont�know�what�quantities�of�assemblies�the�customer�is�going�
to�order�and�if�the�price�of�the�assembly�keeps�varies.�
There�is�another�way�of�configaring�BOM�which�is�pricing�at�header�level.�
The�difference�is�that�the�Material�Master�D�has�to�be�confugured�using�the�item
�
category�group�ERLA.�
Creation�of�BOM�is�same.�
But�you�need�to�maitain�the�pricing�condition�record�for�the�header�item.�
-----------------------�Page�287-----------------------
The�item�categories�in�this�case�would�be�
Header�item�:�TAQ�
Sub�item�TAE;�
Where�the�header�item�is�relevant�for�pricing�and�delivery.�and�subitems�are�not
�
relevant�for�neither�the�pricing�nor�the�delivery.�
Depending�upon�your�requirement�you�configure�accordingly,�
SAP�Implementation�&�Blueprints�
Dhruv�Dalal�|�Jun�16,�2009�|�Comments�(24)�
inShare�
������4�
SAP�Implementation�Process�
What�is�ASAP�Methodology�
ASAP:�Accelerated�Systems�Application�and�Products�in�Data�Processing�
All�implementation�projects�have�the�following�phases:�
Scoping�-�What�is�to�be�implemented�i.e.�which�submodules�are�to�be�implemented�
some�clients�may�not�
require�credit�management�for�example.�Look�at�the�project�scope�document�carefu
lly�it�will�tell�you�what�
SAP�sub-modules�in�SAP�you�should�be�prepared�for.�Usually�the�sales�people�alon
g�with�project�
manager�do�it.�
As�is�-�Here�you�understand�the�existing�business�processes�of�the�client�.�Your
�BPOcollect�all�the�ISO-�
documentation�(if�client�is�ISO�certified),�reports�and�forms�at�this�stage�and�
you�analyse�how�and�when�
the�reports/forms�are�generated,�where�the�data�is�coming�from.�You�also�do�a�Le
vel�-2�training�for�your�
BPO�so�he�is�made�aware�of�all�the�required�transactions�in�SAP.�
Once�this�is�over�BPO�can�start�learning�with�the�consultants�help�more�about�SA
P.�This�is�crucial�
because�if�you�miss�out�any�transactions�the�BPO�may�forget�about�some�of�his�Bu
siness�processes�
which�may�come�up�later.�It�is�a�good�practice�to�ask�the�BPO�to�make�flow�chart
s�to�explain�business�
processes.�
To-Be�-�Parallely�you�map�these�processes�to�SAP.�Processes�that�you�are�not�sur
e�of�as�to�whether�they�
are�present�in�SAP�or�not�you�try�to�do�a�configuration�of�those�processes,�and�
along�with�the�
BPO(Business�process�owner�he�is�the�clients�employee�who�knows�about�the�client
s�business�
processes�probably�a�middle�management�guy,�ther�can�more�than�one),�BPO�involve
ment�is�required�as�
he�may�be�able�to�tell�you�his�requirements�better.�Once�you�do�the�business�mod
eling�you�
will�also�be�made�aware�of�the�gaps�between�as-is�and�to-be�,�here�decisons�have
�to�be�made�as�to�
whether�a�ABAP�development/system�modification�is�required�or�not�and�so�on.�Inv
olve�the�BPO�as�much�
as�possible�and�document�everything�it�is�good�practice�do�not�be�lazy�about�it.
�
Business�blueprint:�Here�the�as-is�and�to-be�and�gap�analysis�is�explained.�This
�is�the�document�that�you�
will�be�using�to�do�your�configuration�in�the�realization�phase.�
Realization�phase:�Here�you�do�the�configuration�in�the�development�server�(ther
e�are�three�clients�-�
development,quality,�production).�You�also�decide�on�the�master�data�format,�so�
that�BPO�can�go�collect�
the�master�data.�You�also�gove�ABAP�specifications�for�forms,�reports�etc,�syste
m�modifications�etc.�Unit�
testing:�Your�BPOs�and�a�few�key�users�sit�down�and�test�your�configuration�in�y
our�module�only.�It�is�
good�to�test�the�BDCs�that�you�need�for�uploading�data�at�this�stage�so�you�have
�more�realistic�data�and�
your�BDCs�are�tested.�
Integration�testing:�
Once�all�modules�unit�testing�is�over�then�the�configuration�is�trasported�to�th
e�Quality�server,�where�
testing�for�all�the�modules�is�done�by�BPOs�and�end�user,�this�is�to�check�if�an
y�problems�are�there�in�
-----------------------�Page�288-----------------------
integration�between�various�modules.�Once�all�is�okay�from�the�QA�server�config�
is�transported�to�the�
production�server.�
Go�live�preparation�
Data�uploading:�The�collected�master�data�is�checked�and�the�uploaded�into�produ
ction�server(sever�and�
client�I�have�used�interchangeably).�Now�you�are�ready�for�go�live�i.e.�users�ca
n�now�use�the�production�
server.�
ASAP�methodoligy�means�nothing�but�standard�process�for�implementation�of�SAP,�I
t�consists�of�5�
phases.�
1.�Project�preperation�-�consists�of�identifying�team�members�and�developing�str
ategy�as�how�to�go.�
2.�Business�Blue�print�-�consists�of�identifying�the�client�current�process,�req
eirement�and�how�SAP�
provides�solution.�
Consists�of�detailed�documentaion�
3.�Realization�-The�purpose�of�this�phase�is�to�implement�all�the�business�and�p
rocess�requirements�
based�on�the�
Business�Blueprint.�
4.�Final�Preparation�-�The�purpose�of�this�phase�is�to�complete�testing,�end-use
r�training,�
5.�Go�Live�and�Support�All�the�functinal�consultatns�need�good�rapo�with�Abapers
.�right�from�uploading�of�
legacy�data,�devoloping�customised�reports,�BDC's,�Forms�etc,�here�functinal�con
sultatns�need�to�give�
guidence�as�to�get�the�requried�data�for�reports�and�all..�like�the�table�name,�
fields�etc�
What�is�baseline�configuration�in�sap?�
Base�line�and�Final�config�is�the�third�phase�in�ASAP�methadology.�The�purpose�o
f�this�phase�is�to�
implement�all�the�business�&�process�requirements�based�on�business�blue�print.�
You�customize�the�
system�step�by�step�in�2�work�packages:�Base�Line�Configuration�&�Final�Configur
ation.�
-�Base�Line�Configuration:�this�phase�comprises�the�priority�requirements�of�the
�enterprise,�ensuring�that�
they�can�be�implemented�quickly.�This�phase�can�be�completed�without�programming
�or�enhancements�
to�SAP�systems.�
-�Final�Configuration:�in�this�phase�you�confirm�that�all�your�requirements�are�
met�in�the�R/3�system.�Final�
configuration�is�a�transportation�process�that�expands�that�base�line�solution�
Documentation�which�is�prepared�before�and�in�a�project:�
1)�Templates�
3)�Fit�Gap�or�Gap�Analysis�
4)�Business�Process�Design�
5)�Business�Process�Model�
6)�Business�Change�&�Impact�
7)�Configuration�Design,�which�is�just�5�%�of�Total�SAP-�have�different�names�-�
8)�Future�Impact�&�Change�Assessment�
9)�Functional�Design�(Module�Wise)�
10)�Risk�Assessment�
11)�Process�Metrics�and�Many�More--�Which�has�impact�on�Business�and�its�work�fl
ow�
Note�*�This�documents�are�prepared�in�Vanilla�SAP�Standards�--�Things�differ�fro
m�one�implementation�to�
another,�and�it�always�depends�on�the�type�of�business�which�is�opting�for�SAP.�
What�Are�SAP�End�User�Manual�
It�is�the�same�for�every�other�modules�although�here�I�reference�it�mainly�for�S
AP�HR.�
1)�You�should�understand�which�targeted�group�for�the�end-user�training�is�for.�
Do�they�have�any�
computer�background�or�not.�
2)�In�what�way�they�are�going�to�make�use�of�the�manuals�supplied�to�them�during
�the�course�of�training.�
How�to�prepare�manuals:�
In�the�client�side,�End�Users�are�not�permanent.�If�they�get�any�better�job�outs
ide�they�will�resign�and�go�
out.�Even�if�you�train�them�well,�again�the�end-user�team�disappears�after�some�
time.�That�is�why�
-----------------------�Page�289-----------------------
implementing�company(�Client�)�expects�SAP�Consultants�to�prepare�documents�whic
h�are�self�
explanatory�(even�to�a�layman�in�SAP)�and�study�themselves�and�use�the�sap�easy�
access�very�
comfortably.�
Hence�we�should�prepare�a�document�which�explains�the�following�things�comfortab
ly:�
A)�All�the�buttons�and�Screens�we�have�in�sap�and�its�importance�for�an�end-user
.�
B)�All�the�transaction�codes�used�by�end�user.�
C)�The�STEP�by�STEP�usage�methodology�with�screen�shots�and�explanatory�foot�not
es�for�each�
Transaction�code.�
D)�Prepare�a�book�a�table�and�columns�which�should�have�the�following�informatio
n:�
-�Sl.NO.�
-�Transaction�Code�
-�Navigation�path�
-�Use�of�the�Code�
-�Expected�Result�
-�Achieved�Result�
-�Remarks/Any�Comment�
E)�Highlight�the�common�troubles�during�the�usage�of�SAP�by�an�end-�user�and�giv
e�the�solutions�(ready�
to�use)�
These�problems�you�can�come�across�while�giving�the�in�house�training�for�the�en
d-users.�You�just�place�
them�at�one�place�and�publish�it�for�their�usage�in�future�for�any�of�their�new�
join�as�an�end-user.�
F)�Every�consultant�is�aware�that�the�entire�Organsiational�Management�is�with�e
nd�user�only.�Means�
consultant�should�train�the�end�user�in�entire�OM.�
G)�We�should�inform�the�importance�of�info�types�and�usage�for�our�purposes�at�e
xpert�mode,�PA30,�
PA40�etc.,�
H)�Each�field�in�the�international�infotypes�should�be�explained�very�clearly�an
d�ensure�that�they�are�
comfortable�with�the�fields�of�infotypes�which�have�been�configured�for�their�co
mpany.�
For�example�:�info�type�0001�Org�Assignment�insists�about�the�three�structures�o
f�the�HR.�We�should�
explain�each�sub�field�like�Emp�Group,�Emp�Sub�Group,�Personnel�Area�and�Sub�Are
a�and�its�
importance�and�relevance�to�their�company�so�as�to�understand�while�processing�t
hem�from�the�end-�
user�point�of�view�.�
When�an�employee�is�hired�into�the�company�,�now�the�end-user�in�a�position�to�u
nderstand�which�
employee�group�and�subgroup,�Personnel�Area�And�Sub�Area�etc.,�should�allotted..
�
Like�this�whatever�comes�across�in�SAP�Easy�Access�should�be�insisted�through�th
e�training�of�end�
users.�
I)�Demo,�exercises�and�solutions�should�be�provided�in�the�manuals.�
J)�Glossary�of�terms�and�expansion�of�Acronyms,�Abbreviations�should�be�given.�L
ike�this�each�
consultant�should�focus�on�end�user�training�and�prepare�the�documents.�
As�is�document:�
How�to�start�doing�the�project�in�'AS�IS'�?�
Are�you�working�as�a�technical�person�or�functional�person?�
This�work�is�of�a�functional�consultant.�It�involves�understanding�the�complete�
functionality�of�the�system.�
It�involves�detailed�understanding�of�how�the�HR�department�is�functioning�becau
se�based�on�that�only�
you�would�provide�a�solution�to�them.�Like�suppose�you�are�implementing�SAP�HR�m
odule�for�them�then�
in�the�AS-IS�and�TO-BE�phase,�you�need�to�prepare�all�the�documents�of�the�proce
ss�flow�(you�can�
prepare�them�in�word).�Like�suppose�you�are�implementing�for�PA�then�you�need�to
�identify�how�many�
personnel�areas�you�need�to�make,�how�many�subareas�you�will�make,�employee�grou
ps,�subgroups,�
based�on�what�you�are�classifying�them?�This�all�will�come�in�the�master�data�do
cument�which�has�to�be�
approved�from�the�client�whoever�he�is�.�
Like�if�the�current�system�is�on�mainframe�or�for�some�specific�applications�lik
e�for�recruitment�the�system�
is�on�mainframes�and�the�client�wants�to�keep�that�system�as�well�then�interface
s�need�to�be�identified�
which�will�be�there�because�you�will�have�to�upload�the�data�to�sap�system�using
�bdc.�
Like�this�for�every�process�there�will�be�a�document.�Even�for�actions�like:�
-�Hiring�
-�Newly�Hire�
-�Termination�
-----------------------�Page�290-----------------------
-Transfer�
-�Layoff�etc�
You�will�have�to�see�what�all�actions�your�client�wants,�like�if�there�is�an�act
ion�transfer�which�is�run�for�
employee�what�all�will�be�the�reasons�you�will�be�configuring�for�that�action.�T
his�will�be�told�by�the�client�
which�can�come�out�after�a�series�of�meetings�and�after�discussions�you�will�hav
e�to�come�out�with�the�
document�that�these�will�be�action�types.�These�will�be�the�action�reasons,�thes
e�will�be�the�action�codes�
for�that.�This�will�be�in�the�TO�BE�process�document.�
After�this�phase�is�over�complete�configuration�can�be�done.�
Actually�AS-IS�process�in�summary�involves�a�:�
1)�Series�of�meeting�with�the�client.�
2)�Gathering�complete�information�about�the�existing�system.�
3)�Preparation�of�the�blue�print�documents�describing�the�complete�AS-IS�process
�,i�mean�the�existing�
system.�
4)�Flow�charts�should�be�included�in�the�as-is�blue�print�process�flow�document�
describing�the�complete�
process.�
5)�After�this�is�finished�u�have�to�give�the�TO-BE�process�structure�that�will�b
e�implemented�in�SAP.�
6)�After�that�there�will�be�some�things�which�cannot�be�implemented�in�SAP�so�th
e�gaps�are�to�be�
identified.�
7)�These�gaps�are�to�be�documented�in�white�paper�for�the�client.�
It�is�a�lengthy�process�but�not�so�difficult�only�the�thing�is�that�the�function
ality�is�to�be�understood�
properly.�
SAP�BLUEPRINTING�
Defining�the�Business�Processes�
After�you�have�defined�your�organizational�structure�for�R/3,�the�definition�of�
the�business�process�for�
your�Business�Blueprint�is�the�next�step.�You�now�map�the�enterprise�requirement
s�onto�R/3�business�
processes,�in�order�to�create�the�conceptual�design�for�your�R/3�implementation.
�For�this,�the�following�
activities�need�to�be�carried�out:�
•�Conducting�business�process�workshops�
•�Completing�the�Business�Blueprint,�reviewing�it�and�obtaining�management�signoff
�
•�Setting�up�an�end�user�training�schedule�
Besides�determining�the�R/3�functionality�to�be�implemented,�the�following�types
�of�requirements�should�
be�identified�in�the�business�process�workshops:�
•�Reporting�requirements�
•�Interface�requirements�
•�Conversion�requirements�
•�Enhancement�requirements�
•�Authorization�requirements�
Since�all�the�results�gathered�during�the�workshops�will�subsequently�create�the
�Business�Blueprint,�the�
importance�of�this�step�cannot�be�underestimated.�The�main�tool�used�to�define�t
he�business�processes�
is�the�AcceleratedSAP�Question�&�Answer�Database�in�conjunction�with�the�R/3�Ref
erence�Model.�In�the�
process,�information�is�gathered�using�the�following�tools:�
•�Business�Process�Questions�(via�R/3�Reference�Model)�
•�Customer�Input�(CI)�Template�
•�Business�Process�Master�List�
•�Knowledge�Corner�
A�functional�spec�should�theoretically�mean�that�the�ABAPer�should�be�able�to�ta
ke�the�design�document�
you�have�prepared,�go�and�sit�in�a�dark�corner�of�the�office�and�build�the�whole
�report.....�this�rarely�if�ever�
happens,�but�I�think�that�the�theory.�
When�you�write�a�functional�spec,�you�are�meant�to�be�turning�the�clients�requir
ements�into�a�design�
document�that�a�techno�can�then�build�from.�
Some�of�the�things�you�may�want�to�think�about�are:�
Report�logic�-�What�information�is�the�report�trying�to�get,�what�logical�links�
are�required�to�link�the�data�
together�-�like�master�data�and�payroll�data,�and�org�mgt�data,�and�how�should�t
his�be�linked,�an�imp�
-----------------------�Page�291-----------------------
how�should�this�be�linked,�an�important�bit�to�remember�here�is�the�time�selecti
on,�do�you�want�all�the�
data�in�the�system,�or�only�the�data�relevant�on�the�day,�or�over�a�month�etc.�
Selection�screen�-�What�fields�are�required�as�selection�options�
Authorisations�-�Should�the�report�check�the�'runners'�authorisations�and�tailor
�the�output�accordingly�
Output�-�What�fields�are�required�to�be�output,�in�what�order,�in�what�file�type
,�for�example�this�could�be�a�
text�file,�or�just�out�to�the�screen�of�the�runner.�
Error�handling�-�What�should�the�report�do�when�it�encounters�a�problem�eg�what�
scenarios�would�
constitute�errors�-�what�should�happen�etc.�
Test�mode�-�does�the�report�require�running�in�test�mode�prior�to�a�file�being�p
roduced?�
What�are�the�roles�&�responsibilities�as�a�sap�hr�functional�consultant�
As�a�Functional�Consultant,�one�needs�to�first�understand�the�business�process�o
f�the�client�and�then�
map�it�in�SAP�to�accommodate�those�business�processes.�
In�the�Business�Blueprint�stage,�you�need�to�prepare�AS-IS�(which�is�a�detailed�
list�of�the�current�
business�practices�of�the�client)�and�then�,�you�need�to�prepare�a�QADB�(Questio
ns�and�Answer�Data�
Base)�questionnaire�and�send�it�to�the�client.�
Then,�based�on�client's�answers,�you�need�to�prepare�TO-BE�list�(�procedure�in�S
AP�to�match�the�client's�
business�process).�
You�need�to�map�AS-IS�process�and�TO_BE�process.�
What�are�the�differences�between�a�functional�and�business�consultant?�
The�difference�between�Functional�consultant�and�Business�consultant�are�as�foll
ows:�
1)�A�funcitonal�consultant�is�able�to�configure�the�system�unlike�business�consu
ltant.�
2)�Functional�consultant�know�more�about�business�process�unlike�Business�consul
tant�.�
3)�A�business�consultant�will�bring�business�process�knowledge�and�provide�it�to
�functional�consultant�
who�in�turn�used�this�knowledge�to�configure�the�system.�
4)�Functional�consultant�has�more�configuration�knolwledge�then�Business�consult
ant�
The�responsibilities�of�a�support�consultant�are:�
-�Primarily�responsible�for�Handling�tickets�and�application�support�to�the�endu
sers�
-�When�an�issue�comes�diagnose,�analyse�and�solve�the�issue�
-�Responsible�for�any�enhancements�
-�Writing�functional�specs�and�interacting�with�Abapers�to�develop�any�user�exit
s�
-�Training�the�end�users�and�preparing�end�user�training�material�
For�those�who�wished�to�know�the�role�of�a�functional�consultant.�Below�is�one�v
iew:�
A�functional�consultant�evaluates�the�demands�in�talking�with�the�customer\'s�re
presentatives,�transforms�
the�essence�into�an�abstract�and�algorithmic�business�model.�Hence,�he�identifie
s�the�use�cases�and�
transforms�them�into�logical�and�technical�views.�
Then�the�main�task�starts:�customizing�the�respective�business�area�and�making�s
ure�the�system�reacts�
in�the�manner�according�to�the�constraints�of�the�requested�use�case.�
The�consultant�documents�the�settings�and�prepares�proper�guidelines�that�allow�
other�consultants�to�do�
further�changes�or�repairs�with�due�efforts.�
The�consultant�takes�care�that�proper�training�is�given�to�the�users�and�that�th
e�system�is�usable,�
performing�appropriately�and�the�business�flow�is�complete�and�correct.�
During�go�live�he�assists�the�technical�staff�by�testing�the�behaviour�of�the�sy
stem.�
-----------------------�Page�292-----------------------
After�go�live�he�guarantees�that�the�procedures�remain�usable�and�consistent�in�
real�live�situation�and�
proposes�enh�
The�consultant�takes�care�that�proper�training�is�given�to�the�users�and�that�th
e�system�is�usable,�
performing�appropriately�and�the�business�flow�is�complete�and�correct.�
During�go�live�he�assists�the�technical�staff�by�testing�the�behaviour�of�the�sy
stem.�
After�go�live�he�guarantees�that�the�procedures�remain�usable�and�consistent�in�
real�live�situation�and�
proposes�enhancements.�
The�main�duty�of�a�consultant�is�to�transfer�external�know-how�to�the�client.�It
�is�not�manpower�that�
counts�but�intelligence,�understanding�of�processes,�a�feeling�for�defects�and�g
eneral�a�common�sense.�
Role�of�a�Functional�Consultant�in�an�End�To�End�Implementation�
1.�Functional�consultant�is�expected�to�generate�knowledge�about�the�current�bus
iness�process,�design�
current�business�flows,�study�current�business�processes�and�its�complication,�i
n�all�we�can�say�getting�
through�with�current�business�setup.�Flow�diagrams�and�DFD�are�prepared,�most�of
�the�time�in�Vision�
format,�all�this�forms�the�part�of�AS�IS�document.�
2.�Everything�configured�has�to�be�documented�as�per�their�categories�in�the�for
m�of�predefined�
templates,�these�have�to�be�then�approved�by�the�team�leads�or�who�ever�the�cons
ultant�is�reporting�to.�
3.�Mapping�and�GAP�analysis�is�done�for�each�module,�I�have�seen�people�defining
�integration�after�
mapping,�gap�analysis�and�configuration�is�done,�but�as�per�my�experience�in�imp
lementation,�it�is�a�
simultaneous�process.�
4.�Before�starting�configuring�future�business�processes�in�SAP,�the�DFD/ERD�are
�prepared,�this�
documentation�is�called�TO�BE,�which�can�be�also�siad�as�the�result�of�mapping�a
nd�gap�analysis.�
5.�Sometimes�Functional�consultants�are�also�expected�to�prepare�test�scripts�fo
r�testing�the�configured�
scenarios.�
6.�End�user�manual�and�user�training�is�also�expected�from�F.Consultants.�
The�project�normally�starts�off�with�a�Kick�off�meeting�in�which�the�team�size,�
team�members,�reporting�
system,�responsibilities,�duties,�methodlogy,�dates�and�schedules,�working�hours
�which�have�been�
predicided�are�
working�hours�which�have�been�predicided�are�formally�defined.�
SAP�Landscape�is�like�a�server�system�or�like�a�layout�of�the�servers�or�some�ma
y�even�call�it�the�
architecture�of�the�servers�viz.�SAP�is�divided�into�three�different�lanscape�DE
V,�QAS�and�PROD.�
-�DEV�would�have�multiple�clients�for�ex:�190-�Sandbox,�100-�Golden,�180-�Unit�T
est.�
-�QAS�may�again�have�mutiple�clients�for�ex:�300-�Integration�Test,�700�to�710�T
raining.�
-�PROD�may�have�something�like�a�200�Production.�
These�names�and�numbers�are�the�implementer's�discreet�on�how�they�want�it�or�th
ey�have�been�using�in�
their�previous�implementations�or�how�is�the�client's�business�scenario.�
Now�whatever�you�do�in�the�Sandbox�doesn't�affect�the�other�servers�or�clients.�
Whenever�you�think�you�
are�satisfied�with�your�configuration�and�you�think�you�can�use�it�moving�forwar
d,�you�RE-DO�it�in�the�
golden�client�(remember,�this�is�a�very�neat�and�clean�client�and�you�cannot�use
�it�for�rough�usage).�As�
you�re-do�everything�that�you�had�thought�was�important�and�usable,�you�get�a�tr
ansport�request�pop�up�
upon�saving�everytime.�You�save�it�under�a�transport�request�and�give�your�descr
iption�to�it.�Thus�the�
configuration�is�transported�to�the�Unit�Test�client�(180�in�this�example).�
You�don't�run�any�transaction�or�even�use�the�SAP�Easy�Access�screen�on�the�100�
(golden)�client.�This�is�
a�configuration�only�client.�Now�upon�a�successful�tranport�by�the�Basis�guy,�yo
u�have�all�the�
configuration�in�the�Testing�client,�just�as�it�is�in�the�Golden�client.�The�con
figuration�remains�in�sync�
between�these�two�clients.�
But�in�the�Testing�client�you�can�not�even�access�SPRO�(Display�IMG)�screen.�It'
s�a�transaction�only�
client�where�you�perform�the�unit�test.�Upon�a�satisfactory�unit�test,�you�move�
the�good�configuration�to�
the�next�SERVER�(DEV).�The�incorrect�or�unsatisfactory�configuration�is�correcte
d�in�Golden�(may�again�
as�well�be�practised�in�the�sandbox�prior�to�Golden)�and�accordingly�transported
�back�to�180�(Unit�Test)�
until�the�unit�test�affected�
by�that�particular�config�is�satisfactory.�
-----------------------�Page�293-----------------------
��The�Golden�client�remains�the�'database'�(if�you�wanna�call�it�that)�or�you�ma
y�rather�call�it�the�'ultimate'�
��reference�client�for�all�the�good,�complete�and�final�configuration�that�is�be
ing�used�in�the�
��implementation.�
��In�summary:�
��Landscape�:�is�the�arrangement�for�the�servers�
��IDES�:�is�purely�for�education�purpose�and�is�NOT�INCLUDED�in�the�landscape.�
��DEVELOPMENT�--->�QUALITY�---->�PRODUCTION�
��DEVELOPMENT�:�is�where�the�the�consultants�do�the�customization�as�per�the�com
pany's�requirement.�
��QUALITY�:�is�where�the�core�team�members�and�other�members�test�the�customizat
ion.�
��PRODUCTION�:�is�where�the�live�data�of�the�company�is�recorded.�
��A�request�will�flow�from�Dev->Qual->Prod�and�not�backwards.�
��These�three�are�landscape�of�any�Company.�They�organised�their�office�in�these
�three�way.�Developer�
��develop�their�program�in�Development�server�and�then�transport�it�to�test�serv
er.�In�testing�server�tester�
��check/test�the�program�and�then�transport�it�to�Production�Server.�Later�it�wi
ll�deploy�to�client�from�
��production�server.�
��Presentaion�Server-�Where�SAP�GUI�have.�
��Application�Server�-�Where�SAP�Installed.�
��Database�Server�-�Where�Database�installed�
��Popular�White�Paper�On�This�Topic�
�����Why�WebEx:�Ten�Customers,�Ten�Reasons���Related�White�Papers�
�����4�Keys�to�Aligning�Your�Business�and�IT�Efforts:�Business�...������Don't�Just�Manage�Your�Trade�Promotions�-�Optimize�Them������8�Winning�Strategies�for�Enterprise�Endpoint�Data�Continuity�...���More�White�Papers�
��Related�Products�