-
Generated by Jive on 2015-02-06+01:001
SAP ERP Sales and Distribution (SAP SD):Different business
scenarios and Sales BOMtechniques for header and item level
stockand prices
Posted by ' MoazzaM ' Sep 6, 2013Dear Fellows
I have been continuously contributing in SD forums from last
year and I have seen many threads about SalesBOM. Sometime users
want to modify sales BOM as per their own business scenarios so
here I am going toexplain how sales BOM helps us to meet different
requirements.Here, I assume that you know how Sales BOM, item
category, schedule line category and copy control worksin SD
process.If you google with search term "Sales Bom in SAP SD" system
will give you a lot of information about standardsettings of sales
BOM by using item category group ERLA and LUMF. This information
can be found onfollowing link.
http://help.sap.com/saphelp_erp2004/helpdata/en/dd/560234545a11d1a7020000e829fd11/content.htm
In standard settings you can control pricing, inventory and
delivery related indicator either on main item levelor sub item
level. If you use ERLA item category group in finished goods
material master data, it will controlpricing and inventory at
header level and sub items will work as text items. For sub item
level control you useitem category group LUMF.A very common and
easy to understand example which SAP's standard documents have used
is sale ofa computer. In a computer sale, we sell it with brand
name and specification. For instance if we sell a Dellpentium 4
desktop computer, it will have a mouse, keyboard, monitor and
speakers but as a whole this is aDell pentium 4 PC. So we will
enter only one material in sale order with material description
DELL Pentium 4Desktop PC and system will determine all compnents
automatically.Sometime we get some requirements which SAP standard
item categories and schedule line categories cannotmeet. So we need
to understand the basic concepts of item categories and schedule
line categories andchange them to fulfill our requirement. Let me
explain with some real business scenarios.
Scenario 1: In SAP free goods standard settings we can maintain
1 free good material against 1 main itemi.e. there is 1:1
combination. We can play with material's quantity but not with
number of materials. If we geta requirement from client that if
customer buys 5 quantity of material A then he will get 1 quantity
of materialB then it can be fulfill with standard free goods by
maintaining it in VBN1. But if customer will get 1 quantityof
material B and 1 quantity of material C on buying 1 quantity of
material A then we can get this done byusing Sales BOM.The settings
for main item and sub item will be as follows. I am assuming that
you want tocumulate cost prices of sub items in main item at the
time of billing. If you don't want this then simply dont mark
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:002
the check box in copy control from delivery to billing at item
level for cumulate cost. Also maintain BOM formaster data in CS01
with usage 5.
Main Item Settings
Billing Relevance APricing XSructure Scope AApplication
SD01Determin Cost CheckSchdule line Allowed Check
Standard Shedule line category (CP) is used and Item Category
Group in Material master sales view is Z001which is customized for
free goods main item materials. I will be using same material group
for other scenariosas well.
Sub Item Setting
Billing Relevance BlankPricing BlankSructure Scope
BlankApplication BlankDetermin Cost CheckSchdule line Allowed
Check
Standard Shedule line category (CP) is used and Item Category
Group in Material master sales view is NORM.
Item Category Assignment
SaTy ItCGr Usg. HLevItca DfItcZMZM NORM ZTS1 ZTS2ZMZM Z001
ZTS1ZMZM NORM TAN
Here ZMZM is my order type and Z001 is material group which I
have maintained only in main item material'ssales view field Item
category group from material master (MVKE-MTPOS). Here no need to
maintain inGeneral item category group (MARA-MTPOS_MARA). ZTS1 is
main item and ZTS2 is sub Item.
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:003
Scenario 2: Lets take another example of a split air
conditioner. We are selling split air conditioners tocustomers and
producing them in our plant. In split air conditioner Indoor,
outdoor and Remote control arethree separate materials. We sell
split air conditioner in finished goods with capacity and brand
name like 1Ton Samsung AC 2 Ton Mitsubishi AC and we can also sell
components individually. So we need to maintainprices at both level
header and item. Here we will maintain stock at item level and
price at item and headerboth. If we are selling a whole package of
split air conditioner then it will be at header level and if we are
sellingonly one component then there will be individual price of
component.
When we are selling a whole package
Main Item
Billing Relevance APricing XSructure Scope AApplication
SD01Determin Cost CheckSchdule line Allowed Check
For this You have to use schedule line CT with no movement type
and relevant for delivery if you want to usedelivery related
billing and copy the main item in delivery document. If you dont
want to copy it in delivery thenyou can simply use CD shedule line
category for main item but for this you have to use order related
billing. It isgood to copy main item in delivery just like a text
item.
Sub Item
Billing Relevance BlankPricing BlankSructure Scope
BlankApplication BlankDetermin Cost CheckSchdule line Allowed
Check
For Sub item we can use CP or CN as per your requirement.
Item Category Assignment
SaTy ItCGr Usg. HLevItca DfItcZMZM NORM ZTS3 ZTS4ZMZM Z001
ZTS3
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:004
ZMZM NORM TAN
When we are selling a component
When you will enter compnent material in order, system will
determin normal item category TAN and with billingand pricing
activated and price will be determined from condition record which
you have maintained for it. Soyou can sell a whole package or
component in same order type.
Scenario 3: If you are dealing with some business process in
which you need to maintain multi level BOMsthen you can achieve
this by changing item category settings of main item and assignment
of item categories.I don't have any real business scenario but lets
assume we are selling comupters and in our company weare
maintaining BOMs for computers and CPU separately. If we are
selling a desktop computer then systemwill explode BOM of Dell 780
Computer in which we have maintained Monitor, CPU, Key Board,
Mouseand Speakers materials and for CPU we have another BOM with
Mother Board, Power Supply, Hard Driveand Super drive etc. Now when
we enter Dell 780 material system will explode two BOMs. Prices
will bemaintained for Computer (Exluding CPU). For CPU we will
maintain seprate price. Stock and deliveries will bemaintain at sub
item level.From configuration point of view there will two
differences from scenario 2.
Main ITem
Billing Relevance APricing XSructure Scope BApplication
SD01Determin Cost CheckSchdule line Allowed Check
Sub Item settings and schedule line settings will be same as in
scenario 2.Item Category Assignment.ZMZM NORM TANZMZM NORM ZTS5
ZTS6ZMZM NORM ZTS6 ZTS6ZMZM Z001 ZTS5ZMZM Z001 ZTS5 ZTS5
With this you can sell whole package and also compnents
separately.
Note:
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:005
These are some basics and most common business processes and I
have shared these just to give you anidea. You can modify them as
epr your scenario. It is all about playing with item category and
schedule linesettings. If you have some other BOM related business
scenario or process which you are not able to configurewith sales
BOM, you can post your scenario in comment and let me help you in
that.There are many other controls like not to change quantity or
material of sub items, copy whole package indelivery or allow
single items too, creating automatic PR (third party sale) and
maintain prices for compnentsand whole package etc. I am not going
in detail of these as we can find a lot of links in SCN describing
thesecontrols.Value addition comments and suggestions will be
highly appriciated. TW Typewriter if there is any otherbusiness
scenario or example in your mind please share with me.
Thank$ 10023 Views Tags: sd, enterprise_resource_planning,
bom_pricing;, bom_process,sap_erp_sales_and_distribution
' MoazzaM 'Oct 1, 2014 12:23 PMvinod reddy Haresh Panara Thank
you guys for appreciating this effort.
Haresh PanaraOct 1, 2014 6:26 AMThanks, Great Work, Nicely
explain, Very userful document.
Once again thanks for sharing such useful document.
Regards,Haresh
vinod reddySep 30, 2014 3:53 PMHi Moazzam,
Thanks for making your time and efforts in making a good
document as always.
Regards,
' MoazzaM ' in response to Dibyendu Patra on page 6Sep 30, 2014
2:13 PMThank you Dev for such valueable remarks. Really
obliged.
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:006
Thank$
Dibyendu PatraSep 30, 2014 7:24 AMGood document.. I had given a
PDF for this document to my SD consultant. His review was 5 star
and yes youdeserve it. Keep sharing knowledge..
' MoazzaM ' in response to Shashi Thakur on page 6Mar 5, 2014
9:30 AMHi
This is valueable compliment for me. Thank you Shashi Thakur
Thank$
Shashi ThakurMar 5, 2014 7:56 AMExcellent Blog MoazzaM,
I have read it multiple times..Keep writing.
zaheer zaidi in response to TW Typewriter on page 6Mar 4, 2014
11:42 AMTW,
I didn't take any item cat group as a reference because there is
not much setting behind in the standard itemcat groups.
TW Typewriter in response to zaheer zaidi on page 6Mar 3, 2014
5:36 PMzaheer,
At the initial phase of the career, when practicing in IDES,
test systems, then configure as much as you can!Play with the
system - tear it apart and then assemble it again!
But while doing this keep your mind, think what each block
signifies both from business and technical points ofview. If I
create something what would be the effort vs. benefit.
Yes, you are correct, we should not change standard
configuration objects like sales document type, itemcategories
etc.
Related to item category group - you created new ZORM but how
did you create it? What did you take asreference item cat
group?
zaheer zaidi in response to ' MoazzaM ' on page 7
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:007
Mar 3, 2014 12:16 PMyes you are right there is no setting behind
the standard item cat groups and we can use them.
' MoazzaM ' in response to zaheer zaidi on page 7Mar 3, 2014
10:27 AMHi
You are right about item categories and document types but for
item category group we can use standardone for determination for
ouw own item categories and document types. There is no settings in
NORM itemcategory group so you can use it but there many settings
and control parameters in TAN or OR and that is whyit is
recommended that you create a separate one for your use.
Thank$
zaheer zaidi in response to TW Typewriter on page 7Mar 3, 2014
10:15 AMHi TW,
I have plan to create custom item categories to avoid touching
standards ones because it is not recommendedto change the standard
sales doc types, item cat etc. That is the reason I have created
custom item cat groups.Correct me if I am wrong.
Thanks
TW Typewriter in response to zaheer zaidi on page 8Mar 3, 2014
7:06 AMzaheer,
In your case, you could have also used the standard item
category group - ERLA and NORM (in place ofZORM, XORM)
In the material master record the item category groups do not
have to be changed to your custom itemcategory groups (if material
created already).
If you want to restrict these materials ONLY to this process
(and no other sales process) then also you arerestricting as the
sales document type is custom (and not OR etc.) so with standard
item category groups andcustom doc type it could have been
achieved.
Thanks for sharing!
TW Typewriter in response to Phanikumar V on page 8Mar 3, 2014
7:01 AMPhani,
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:008
zaheer used ZORM as item category group for the main item. (and
not the standard ERLA)Phanikumar V in response to zaheer zaidi on
page 8
Mar 3, 2014 4:52 AM""" Created 2 item category groups zorm and
xorm. I used zorm in the material master of main item and for
subitems I used xorm as the item category group""""
For The Main Item you used NORM But In Header level BOMs we will
use ERLA--How you managed??
Phanikumar
zaheer zaidi in response to ' MoazzaM ' on page 9Mar 3, 2014
12:10 AMHiThat is the solution of the problem which I had posted
few days ago about BOM. I would like to share it here inthis forum
so people can benefit from it.
There is a main item HP Laptop. Sub items can be sold with the
main items or as an individual component. Ifsub items are part of
HP laptop then the main items HP Laptop will be priced and sub item
will not be pricedbut price is applied in case if the sub items are
sold individually.
Here are the steps I followed to implement this business
scenario.I have created following main and sub materials.
Main ItemsMaterial: lPHP(Laptop HP), mat group LAPTOP, sales mat
group HP
Sub ItemsMaterial: COREI3 (Corei3 Processor)Material: Mhp17
(Monitor HP 17)Material: MA4WIRELESS (A4 tech wireless laptop
mouse)Material: KYBLAPTOP (Keyboard Laptop)Material: HDDRLP500
(Hard drive 500 GB)Material: RAM1GB (RAM 1GB)
1, Created a new sales document type zor12, Created 2 item
category groups zorm and xorm. I used zorm in the material master
of main item and for subitems I used xorm as the item category
group.3, Configured item categories TAQ for pricing, TAN for
pricing and TAE is not relevant for pricing.
I have done the item category determination for the main and sub
items.Main item: Sales doc type (ZOR1), Item category group ( ZORM)
default Item category (TAQ)
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:009
Sub item: Sales doc type (ZOR1), Item category group ( XORM),
higher level item category(TAQ) default Itemcategory (TAE)
For main item the item category TAQ will be determined which is
applicable for pricing and for sub items itemcat TAE will be
determined which is not relevant for pricing.
If the sub items are sold individually then the item cat
determination rule is as follow
Sales doc type (Zor1), item cat group (XORM) default item cat
(TAN)
In the above condition item cat TAN will be determined for sub
items and it is now relevant for pricing so nowsub items can be
sold as an individual component as well.
I have created material BOM and its working fine.
Thank you Moazzam and TW for the help.
Suresh SaiFeb 25, 2014 11:40 AMAwesome, Great work...Keep it
up!!!! Thanks fr sharing.
zaheer zaidi in response to ' MoazzaM ' on page 9Feb 25, 2014
10:54 AMThank you Moazzam and TW.
' MoazzaM 'Feb 25, 2014 6:12 AMzaheer zaidi
TW has already answered to all of your queries and TW is right
for BOM usages. I hope you got the idea howwe can use BOM
functioanlity in your business process. If you need some
clarification or help you can comehere again.
Thank$
Phanikumar V in response to zaheer zaidi on page 10Feb 25, 2014
5:33 AMDear Zaheer,
For this requirement you can go ahead with Variant
configuration( same material with Different variants)--Hopethis
helps you..
Pl follow
--http://help.sap.com/printdocu/core/print46c/en/data/pdf/lovc/lovc.pdf
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0010
Phanikumar
TW Typewriter in response to zaheer zaidi on page 10Feb 25, 2014
5:30 AMzaheer,
Yes, you can have BOM with the main and sub items you have
mentioned!
For all of these materials, material master record has to be
created.
Please note - Next step - BOM (master) has to be created in CS01
before it can be used in the sales order.
That means the material - main item and subitem combination is
already predefined in SAP as master data.Then the same is used in
sales transactions.
As explained in this document, the configuration in item
category and item category determination have to bedone.
zaheer zaidi in response to TW Typewriter on page 11Feb 24, 2014
11:58 PMHi TW,
Have a look to this scenario.
Accessories (can be sold as an individual piece or as a part of
PC)
IBU Intel Based CPUABU AMD Based CPUM17 17 MonitorsM19 19
MonitorsWM Wired MouseLM Wireless MouseWKB Wired KeyboardLKB
Wireless Keyboard
Materials which will be sold in a package987655 ABC Graphic
Desktop765432 ABC Portable Laptop987654 ABC Performance DesktopIn
the above scenario I am creating two material groups
1, Desktop2, Laptops
Three main items
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0011
1, Graphic Desktop 2, ABC Portable Laptop3, ABC Performance
Desktop
Eight sub items which can be sold as a part of main items in BOM
or as an individual piece if necessary
1. IBU Intel Based CPU2. ABU AMD Based CPU3. M17 17 Monitors4.
M19 19 Monitors5. WM Wired Mouse6. LM Wireless Mouse7. WKB Wired
Keyboard8. LKB Wireless Keyboard
Do you think this above configuration approach is right?
Thanks..
zaheer zaidi in response to TW Typewriter on page 11Feb 24, 2014
10:52 PM
You are right, Thanks TW
TW Typewriter in response to zaheer zaidi on page 11Feb 24, 2014
7:22 PMHi zaheer,
No it is not possible! Also, if there is one mmr for i3, i5 and
i7; then how would you maintain stock for these 3products
(materials) in SAP?
zaheer zaidi in response to TW Typewriter on page 11Feb 24, 2014
4:31 PMHi TW,
No, there is only one material master which is CPU and I am
trying not to create material master for i3, i5 andi7 and use sales
material group for further control, is it possible?
TW Typewriter in response to zaheer zaidi on page 11Feb 24, 2014
2:27 PMzaheer,
MoazzaM also touched upon this point - For core i3, i5 and i7,
are 3 different material master records createdin SAP?
Do you want to have different pricing for each of the above
materials?
zaheer zaidi in response to ' MoazzaM ' on page 12
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0012
Feb 24, 2014 1:49 PMHi Moazzam,
Thanks for your reply. You are absolutely right the item
category controls what a bill of material can do in asales order.
Let's come to the sales material groups. As I wrote you before, if
there is a material called CPUand it has different types core i3,
i5 and i7 and it is Intel based CPU. In this scenario if I create a
materialCPU and assign it a material group Intel (Basic data 1
view) and then for further classification I use the salesmaterial
groups (sales org 2 view) then how can I control pricing to the
extent of sales material groups becausefor pricing the only field
which is available in the field catalog is MVGR1 which is material
group 1 and for othermaterial groups there is no option in the
field catalog.
Thanks..
' MoazzaM ' in response to zaheer zaidi on page 12Feb 24, 2014
12:16 PMHi Zaheer
Yes this is possible. In SAP we don' maintain two materials for
one physical material. We can sell it as partof BOM or as separate
item in same sale order. Differnece will be there in item
categories. With BOM it willbehave like sub item and as separate
material it will come in TAN like normal item.
Thank$
' MoazzaM ' in response to Jayshree Pillai on page 13Feb 24,
2014 12:13 PMThank you Jayshree. Actually as you know English is
not my primary language so I can't write difficultsenteces. I
always try to use simple and easy words and sentences so that
people like me can understand it
easily
Thank$
' MoazzaM ' in response to TW Typewriter on page 13Feb 24, 2014
12:12 PMDear TW
There are always many ways to do one thing. My point was that if
main item is required only for printing inbilling then we can mark
it not relevant for billing and in invoice print out we can get a
link to sales order andget its price from there.Your point is also
valid and we can achieve this requirement from that as well. Thank
you for your valueaddition comment.
Thank$
zaheer zaidi
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0013
Feb 24, 2014 9:59 AMHi Moazzam,
Nice and simple explanation about BOM. I have one scenario,
suppose there are different types of CPU forexample Intel core 2
duo, core i3, core i5, core i7. These CPUs can be sold as a part of
PC or as an individualpieces. Is it possible to maintain just one
material as CPU and further classify it using sales material groups
insales org2 view in material master and then use it as main or sub
item as per requirement?
Jayshree PillaiFeb 24, 2014 9:15 AMThank you Moazzam!!
Special mention of your language and sentence formations, it
makes it so easy to understand andcomprehend.Also, business
examples are very helpful.
Sundar SFeb 24, 2014 7:58 AM
Good Job Moazzam
TW Typewriter in response to ' MoazzaM ' on page 13Feb 24, 2014
6:33 AMMoazzaM,
Interesting comment related to the requirement - Main item is
set not relevant for billing & print out of billingdocument (i
assume it is bill OR is it sales order, delivery?)
When main item is set not relevant for billing, then this does
not populate in the billing document but in theprintout of bill,
you have the main item. There is an inconsistency between bill in
SAP and its printout. Pleaseconfirm & why so?
By keeping pricing as statistical in the main item, you could
have populated it in the billing document also.
' MoazzaM ' in response to Patrick Imhen on page 13Feb 24, 2014
6:14 AMHi
Thank you for your compliment.For your query posting values of
sub items to different revenues account is something I never worked
on it. Wecan have value of main item just for statistic purpose or
print purpose. For this you just need to make main itemnot relevant
for billing. Get its price from sale order in your print smartform
of invoice.For more and better suggestions you may post it as a
discussion in SD forum.
Thank$
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0014
Patrick ImhenFeb 22, 2014 1:02 PMWelldone Mozzam for your
blog!
I am currently faced with a bit different scenario of BOM in
Sales Order. In this case, my client wants that whenthe Invoice is
released to FI, only the Values for the Sub-Items should post to
their Revenue Accounts and theirrespective Profit Centers while the
Value at the Main-Item will only be statistical for Printout. That
is if you haveSub-Item "A" (Revenue Account 40000001) with value
$100, "B" (Revenue Account 40000002) with value$70, "C" (Revenue
Account 40000003) with $30. So when invoice is released to FI,
these values will go to theirrespective Revenue Account and Profit
Centers while the Main-item ZZ will only be statistical for
printout.
How can this be achieved?
Regards,
Patrick
' MoazzaM ' in response to R Sgr on page 14Feb 6, 2014 8:14
AMDear R Sgr
Thank you for your suggestion. Topic of this blog is use of
sales BOM as per business scenarios and I tryied toexplain that.
How does item category explode in sales BOM is a different topic
and a user who is working withsales BOM should know explosion of
item categories.
From you comment it looks like you also know how item category
explodes and determines in SD
Thank$
R SgrFeb 5, 2014 1:12 PMDear MoazzaM,The extent of the explosion
of BOM depends upon the Item Categ and not Item Categ Gr. As TW
Typewriterrightly said that item categ gr is only a tool to pick
the correct Item Category. So I my views instead ofemphasizing on
Itm Categ gr you should have explained that how Item Categ
determines the extent of BOMexplosion.Hope you don't
mind.Thanks.
' MoazzaM ' in response to Santosh Panda on page 15Jan 27, 2014
5:38 AMHi Santosh
This can be done with ABAP customizing. There would be a lot of
ABAP work involve in it. Z table and andcode in MV45AFZZ program.
Sales BOM wont support this scenario.
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0015
Thank$
Santosh PandaJan 26, 2014 6:39 PMHi Moazzam,
Great,its really nice.But I want to know if my company wants to
provide free one material with 3 different materials.for
example:-If u buy material A,material B and material C then
Material D will be free.Could you help me for this.How to configure
this?
' MoazzaM ' in response to ratnam sri on page 15Dec 19, 2013
8:20 AMHi ratnam sri
Thank you for your nice remarks.
Thank$
' MoazzaM ' in response to Hussain Poonawalla on page 15Dec 19,
2013 8:20 AMThank you my friend Hussain Poonawalla
Thank$
Hussain PoonawallaDec 18, 2013 3:46 PMGreat, its helpful!
ratnam sriDec 18, 2013 1:35 PMHi Moazzam,
Good document and nicely explained.Keep posting...
RegardsRatnamsri
' MoazzaM ' in response to Ramanjaneyulu Korrapati on page 16Nov
4, 2013 12:19 PMThank you Raman for this compliment.
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0016
Thank$
Ramanjaneyulu KorrapatiNov 4, 2013 11:37 AMGreat explanation
with scenarios about BOM Techniques. Thanks for your efforts.
ThanksRaman
' MoazzaM ' in response to Srinu S on page 16Oct 29, 2013 11:33
AMThank you Srinu for liking this document.
Thank$
Srinu SOct 29, 2013 11:31 AM
Really useful document MoazzaM. Thanks for sharing.
' MoazzaM ' in response to manojkhumar panneerselvam on page
16Oct 6, 2013 4:14 PM
Really glad to know your feedback Manoj. Thank you manojkhumar
panneerselvam
Oct 6, 2013 3:05 PMHi Moazzam,
Thanks for sharing this. Now, I am able to appreciate the
capability of BOM.
Please keep sharing more like this, Its very good.
Thank you so much
Regards,Manoj
' MoazzaM ' in response to krishna murali on page 16Oct 3, 2013
6:33 AMThank you dear.
krishna muraliOct 3, 2013 5:43 AMDear Moazzam,
this is very good document
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0017
thanks for advice
Warm regardsmurali kirshna
' MoazzaM ' in response to * Ammarah * (Away) on page 17Sep 27,
2013 7:29 PM
Thank you * Ammarah * (Away) for these wonderful words* Ammarah
* (Away)
Sep 27, 2013 7:22 PMThis document is purely the crux of your
professional experience blended with perfect business
scenarios.
Thanks for sharing ' MoazzaM '
' MoazzaM ' in response to Pankaj Kharche on page 17Sep 26, 2013
7:12 PMThank you Pankaj
Pankaj KharcheSep 26, 2013 3:53 PMHi MoazzaM,
Very Helpful Document.
' MoazzaM ' in response to Phanikumar V on page 18Sep 24, 2013
1:57 PMPhanikumar
Did you read that document which I have shared in my blog?
Please check the behave of ERLA and LUMFitem category groups. In my
scenario main item and sub items both are delievery relevant,
valuated stock andmain iten is billing relevant too. Can we do this
with ERLa or LUMF?
Thank$
' MoazzaM ' in response to Pradeep Mani on page 18Sep 24, 2013
1:54 PMPradeep
Thanks
' MoazzaM ' in response to vinod reddy on page 18Sep 24, 2013
1:53 PMThank you Vinod
TW Typewriter in response to Phanikumar V on page 18
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0018
Sep 24, 2013 8:00 AMPhanikumar,
The control for whether relevant for inventory resides in the
schedule line category, field Movement type (601).
So what ever the requirement e.g. inventory relevant at sub item
level or at main level or at both levels, therelevant schedule line
category settings have to be done.
Phanikumar VSep 24, 2013 7:43 AMDear Moazzam,
Thanks for the post.
But by post-If we want to give B and C as free with A--then BOM
can be ideal solution.If it is done by BOM(ERLA/LUMF)-then the
sub-items are not relevant for Inventory In ERLA and main item
isnot relevant inventory in LUMF(because these two will act as Text
items in respective scenarios)--which is nottrue with free
goods
Please clarify me on this?
Phanikumar
Phanikumar
Pradeep ManiSep 24, 2013 6:08 AMVery good contribution to the
community
Thanks,Pradeep
vinod reddySep 22, 2013 9:09 AMHi Moazzam,
Thank you very much for the efforts.
Best RegardsVInod
' MoazzaM ' in response to Naresh Krishnamoorthy on page 19Sep
12, 2013 6:07 PM
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0019
Thank you Naresh
Naresh KrishnamoorthySep 11, 2013 10:42 AMVery Useful...Thanks
for your efforts.
Best Regards,Naresh K.
Srinu S in response to ' MoazzaM ' on page 19Sep 11, 2013 10:41
AMHi MoazzaM,
Thank you for your document nicely explained.thanks,Srinu.
' MoazzaM ' in response to Moshira Ismail on page 19Sep 11, 2013
10:26 AM
Thanks Moshira
Moshira IsmailSep 11, 2013 9:26 AMExcellent effort Moazzam
' MoazzaM ' in response to Nidhi Raman on page 19Sep 11, 2013
7:02 AM
Thank you Nidhi
Nidhi RamanSep 11, 2013 5:56 AMGood blog Sir!
TW Typewriter in response to venu gopal on page 19Sep 10, 2013
8:28 AMvenu,
Please think of item category gr as a "tool" to determine the
correct item category and nothing more.In other words, item
category gr name is not important but how it is used, to determine
which itemcategory(ies).
venu gopal in response to ' MoazzaM ' on page 20Sep 10, 2013
8:20 AMThank you moazzam .. for your replay
venu gopal in response to TW Typewriter on page 20Sep 10, 2013
8:18 AM
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0020
Thank you so much for your replay ..it means we can use ERLA
Also plz let me knowthanks a lot
' MoazzaM 'Sep 10, 2013 8:17 AMHi
I just used Z001 because i wanted to use it Seriously we can use
ERLA or LUMF or any other because this is our customized sales
document type ZXXXand customized item categories so item category
group will be used to determine item categories and it can beany Z
or standard group. But best practice is not to gamble with
standards and always create your own whenyou are testing
something.
Thank$
TW Typewriter in response to venu gopal on page 21Sep 10, 2013
8:10 AMvenu, D Sea,
I feel venu's point is valid, in Scenario 1, MVKE-MTPOS (item
cat group) ERLA could have been used also.In item category
determination, ERLA could be used even though business uses
customized item categories(Z***). Provided the pricing, billing is
done at main-item level.
In MoazzaM's example, he has used a customized item cat group,
that too is fine. In both the cases (ERLA orZ001), the important
thing is that the respective MMR should be populated with the
correct item cat gr.
Dee Sea in response to venu gopal on page 21Sep 10, 2013 7:54
AMHi,
Just a small input here
Anywhere you work on real SAP Environment if anything like a
:
Transaction Code Table Name Field Name Program Name Customizing
Values - Ex: the Item Category Group in this case Etc.
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0021
has a Z or Y [ in some cases] as the first alphabet in the code,
it is not a Standard SAP Name / Code andcreated by people like you
and me.
Thanks.
venu gopal in response to ' MoazzaM ' on page 21Sep 10, 2013
7:52 AMDear MoazzamIn scenario 1 For main item You have maintained
z001 own item category groupBut generally ( STANDERD one ) We have
to maintain ERLA ?
has nothing to do with ERLA
i am confused with this bz as i understood , in your case you
have used ur own customized item cat groupz001 But generally ERLAso
plz comment on thisThanks a lot for ur help
' MoazzaM ' in response to venu gopal on page 21Sep 10, 2013
6:27 AMHi Venu
No, Z001 is my own item category group. It is used to test these
scenarios. ERLA and LUMF are standarditem category groups used for
header level and item level BOMS but in my case I have created my
own andconfigured BOM as per my own scenario. It has nothing to do
with ERLA.
Thank$
venu gopal in response to ' MoazzaM ' on page 21Sep 10, 2013
3:52 AMDear Moazzam and T.W
Item Category Group in Material master sales view is Z001 which
is customized for freegoods main item materials. I will be using
same material group for other scenarios as well.
Z001 Means ERLA Right ?
thank you so much
' MoazzaM ' in response to TW Typewriter on page 22Sep 9, 2013
10:51 AMDear TW and Venu
These were three senarios in my mind and as I said these are
just to give you people an idea that how wecan modify BOM as per
our own requirement. If you have any other scenario you can
configure that by justchanging the settings of item categories and
schedule line categories. Its easy and simple.
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0022
Thank$
' MoazzaM ' in response to Madan Shetty on page 22Sep 9, 2013
10:49 AMThank you Madan
TW Typewriter in response to venu gopal on page 22Sep 9, 2013
10:11 AMvenu,
I have to think about scenario 3.
I feel one thing which could add value to this blog is for each
scenario the transactions (sales order, delivery,billing). The
configuration settings would be seen clearly in the sales
cycle.
Would you like to create transaction data for the above
mentioned scenarios and past those here?It might help you too.
venu gopalSep 9, 2013 6:18 AMDear MoazzamNice documentation
,what ever you shared it will be great and very beneficial to
persons who are most willingto learn some thing
And by the by thanks to T.Wplz explain me if you have another
business scenario with 3 ONEthanks a lot
Madan ShettySep 8, 2013 10:20 PMThank you Moazzam very helpful
document
' MoazzaM ' in response to Khushi Mughal on page 22Sep 8, 2013
2:07 PM
Thank you Khushi for nice comments
' MoazzaM ' in response to TW Typewriter on page 23Sep 8, 2013
2:06 PMThank you TW for the comment. I will check it tomorrow and
will post my findings.
Thank$
Khushi MughalSep 8, 2013 1:33 PMHi Moazzam,
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0023
Good document and nicely explained.Keep posting...
Best Regards,Khushi
TW TypewriterSep 8, 2013 10:44 AMMoazzaM,
Thank you for this blog!Just memorizing theoritical knowledge of
BOM..LUMF, ERLA etc. is not sufficient!(as with all SAP SD topics /
functionalities) Competently "connecting" the theory with the
various businessscenarios makes a consultant so much more
value-adding to its clients etc. etc.Your business examples are
priceless aids in the learning process (wrt BOM)!
After going through your blog, some comments -1. In all the
scenarios - ONLY one item (the main-item) flows to the billing
document.The client might want to have both the main and sub items
in the billing document. And also in the output of thebilling
document.
By having the field "Billing relevance" populated at both the
main and sub item categories, all the items couldbe populated in
the billing document.
2. Field "Statistical value", in item category, VOV7 - When a
item is not relevant for pricing, not only do Imaintain pricing =
blank, but also maintain field Statistical value = X
3. In Scenario 3 -3.a. Have you missed out the below entry in
T184 -ZMZM Z001 ZTS6
3.b Would the below entry, result in incorrect data in the sales
order?ZMZM Z001 ZTS5 ZTS5
If you activate pricing for ZTS5, then it would be activated for
main and sub item, therefore the price would bemore than (double)
of the price that should be.
Side comment - I would read, test and think about BOM (and your
document) and get back if I have morecomments.Keep up the good
work!
Karuna Ravuri in response to ' MoazzaM ' on page 24Sep 6, 2013
2:08 PM
-
SAP ERP Sales and Distribution (SAP SD): Different business
scenarios and Sales BOM techniques forheader and item level stock
and prices
Generated by Jive on 2015-02-06+01:0024
Definitely helpful, thank you for posting
' MoazzaM ' in response to Karuna Ravuri on page 24Sep 6, 2013
1:38 PM
Thank you. I believe its helpfull too
Karuna RavuriSep 6, 2013 1:31 PMGood blog MoazzaM !