on 2019 Jul 05 5:38 AM
Dear SAP Retail Experts,
1. Request you please clarify my doubt on the importance of Components Tab for a Sales Set Article in Master data Screen of MM41/MM42/MM43.
2. What is the table name where I can see the components assigned to the Sales Set article.
3. How is this components tab in Article Master different from the BOM maintenance to this Sales Set Article created via T.Code: CS01?
4. What is the main significance of this Components tab for a Sales Set Article Master, If it is different from BOM?
Regards,
Sridhar Madiraju.
Request clarification before answering.
1. Request you please clarify my doubt on the importance of Components Tab for a Sales Set Article in Master data Screen of MM41/MM42/MM43.
Unlike Material Master, Article Master features integrated maintenance via MM41/MM42/MM43. In one T-Code it's possible to maintain a Purchase Info Record, certain condition records, a BOM in the case of structured Articles, and much more.
2. What is the table name where I can see the components assigned to the Sales Set article.
Start here: MAST - Material to BOM Link (look at MAST-STLNR) to find the BOM.
STKO - BOM Header
STPO - BOM Item (look here to find the assigned components)
3. How is this components tab in Article Master different from the BOM maintenance to this Sales Set Article created via T.Code: CS01?
Sales Set is only one of several types of structured Articles (Article Categories). It's never a good idea to use standard T-Codes that were meant for material master to attempt to maintain Retail Article masters.
4. What is the main significance of this Components tab for a Sales Set Article Master, If it is different from BOM?
See # 3. With that said, the same BOM concepts are used here. For example, the data migration scenario is to first create the Sales Set Article and all the component Articles using ARTMAS IDoc and then assign the components to the Sales Set using BOMMAT. While this all sounds like standard Material Master, it isn't always. The inbound processing of BOMMAT includes Retail functionality that can only be considered by inbound processing of BOMMAT (not fully available in any BAPI or released function module).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Paul,
Thanks for your response. I am able to understand the concept of BOM and that need to be maintained in CS01 and its tables. My question here is what is the purpose of components tab in Article Master Basic data screen for a Sales Set Category.
From my attached screenshots above, I can maintain one set of articles(A,B) as components for a Sales Set Article-X and another set of articles(C,D) for the same Sales Set article-X using the BOM.
If we have to maintain a BOM using CS01 for a Sales Set, then why does system allow us to maintain components in Article Master. Ideally system should display what ever is maintained in BOM CS01. (or) If I maintain components in Article Master, ideally it should create a BOM in the background. But neither is the case here.
Hope I explained my doubt in a better way now.
Regards,
Sridhar Madiraju..
Hi Sridhar:
This seems to be the misunderstanding: "If we have to maintain a BOM using CS01 for a Sales Set ..." No, the BOM is not to be maintained using CS01 for a Sales Set.
The purpose of the components tab in Article Master Basic data screen for a Sales Set Category is to maintain the list of components for the Sales Set. Do not use T-Code CS01 for this task because this is a Retail Article Master and not a standard Material Master.
The indication that the use of CS01 is an error is the fact, as you describe, that you can maintain one set of articles (A,B) as components for a Sales Set Article-X and another set of articles (C,D) for the same Sales Set article-X using the BOM. Only one of these things can be correct 🙂
If the Sales Set Article can be used in a business process then you will find that the behavior is only as expected when the components are maintained via MM41/MM42.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.