on 2022 May 19 1:52 PM
Hello,
We are trying to achieve the below scenarios using CG37 standard BOMBOS,
1. We have Different BOMs per plant with different Components
Material ABC : BOM 1 (B-50 %, C- 50%) Plant A
Material ABC : BOM 2 (A -20%, B- 80%) Plant B
CG37 is showing these 2 BOMs with different plants in the worklist
When we run the CG37 worklist to transfer the BOM to BOS these BOMS should update in Exact Composition Based on Starting Mat. with 2 different instances and 2 different compositions with Validity areas as PLANT - A, PLANT - B.
This is not happening with standard BOMBOS transfer it is updating a single instance with composition and overriding the value every time.
If this is possible please let us know the configuration to do so.
2. Alternate BOMs for the Same material
Material ABC : BOM Alt -1 (B-50 %, C- 50%) Plant A
BOM Alt -2 (D-10 %, E- 90%) Plant A
CG37 is not showing these 2 Alt BOMs in the worklist,
When we run the CG37 worklist to transfer the BOM to BOS these BOMS should update in Exact Composition Based on Starting Mat. with 2 different instances and 2 different compositions with Validity areas as these are Alternate BOMs.
This is not happening with standard BOMBOS transfer it is updating a single instance with composition and overriding the value with Alt 2 all the time.
If this is possible please let us know the configuration to do so.
Best
Satya
Request clarification before answering.
Hi satyanarayana.reddy9,
I'm not sure if this is possible without some custom coding.
I think the reason for this might be, that it doesn't make really sense to have two compositions - that ultimately would create two "Standard Compositions" - which can't be handled in a meaningful way within SAP EHS.
If the BOMs are so different that they would lead to different classification or registration/notification requirements for the chemical mixture - then one would need to create different materials and assign them to different specifications.
If it would anyhow lead to the same classification and registration/notification for the mixture - what's the point of having different compos assigned to....
Best
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Satya
the "basic" idea of SAP approach is using the "identifier" to "differentiate".
You can use the plant code as validity area. I believe there are some useful exits here... so yes: you need custom code (and i belivee you must use custom code)
The discussion is "more" complex if you consider "all" topics of a BOM
1.) Per material / plant: we can have more than one alternative
2.) the BOM part can be handled using change numbers (so there is a versioning)
Please check on of my "blogs". long long ago i tried to summerize the discussions running for "BOMBOS".. (and honestly: my blog os "outdated" regarding "BOM" discussion). I believe (but not 100% sure): with some Enhancement package SAP extended the solution.
As you know: during "BOMBOS" transfer you can "switch" the property to store the data. You should select a property of type "Composition" which is not needed for "Verisk" like rule sets if you would like to use BOMBOS
Mark has pointed out the "regulation story".
To use "BOMBOS" transfer depends on "chemistry" and set up of SAP ERP system and philosophy of company using SAP EHS.. we stopped the discussion on our side because of the "complexity" (blue print is not easy to "write" down etc.).
C.B.
PS: https://blogs.sap.com/2013/07/28/bom-bos-interface/
PPS: pay attention. some years ago i tried to "count" the "BOMBOS" version of SAP. There are to "many".
We have a BOMBOS in "EHS Classic"; We have a BOMBOS" for "Component extension for SAP EHS Management"; a BOMBOS in the old "Reach and Compliance Suite" etc.t
PPS: a may be good reference for "exit" discussion: you will find here: https://answers.sap.com/questions/10987500/bombos-transfer-spro-settings-and-technical-detail.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
Thanks for your time and explanation,
Do we need a custom code to write the plant in the validity area as well cause i could not see this is being updated by the BOMBOS, I could see only the identifier BOM is showing the plant.
Best
Satya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.