We are looking for some guidance or sample code on the best approach to implement dynamic phrase set assignment in SAP EHS module. We would like to dynamically change the phraseset assigned to a characteristic based on the value selected in another characteristic.
We saw that SAP enhancement C14X0001 is available to dynamically determine and assign phrase sets to characteristics based on the current value assignment usage.
Could we still leverage enhancement C14X0001 but drive the logic not on the assignment usage but on a value stored in another characteristic ?
What if this other characteristic is not even yet save in the database and has just been entered at the user interface level (SAP GUI) by the user, could we still use BAPI_BUS1077_GETDETAIL or another family of function needs to be use ? How can we access the current user interface context (SAP GUI) ?
Aside from enhancement C14X0001 would there be other recommended approach that we should try ?
Thanks
Request clarification before answering.
Hello
most of the "properties/"VAT" are "mixed" that means contain e.g. phrase based characteristic and other stuff (e.g. like "Density").
SAP EHS is enhanced a lot in the last 10 years. There is as well some useful "BADI" in place (may be check https://answers.sap.com/questions/135783/issue-of-bapibus1077change-in-atsavecheck-of-badi-.html)
The logic could be here: during the "save" process the data in the VAT is checked... and based on some "rule" you could "enter" a phrase in characteristic A during"save" process (based on data as identified in the VAT). It depends on your "rule".. but more or less this is the same like "MSDS maker" etc. the only difference; the data is enhanced in "save" part.
The "rules" are starting from hit list. E.g. a rule can be:
1.) create data record in e.g. "denisity" with usage "STANDARD/US" having this "phrase" and other data (you need a definition which data should show up; how many "variants" of data to be maintained is needed).
2.) Even if you have prepared the rule only to fill 80% of the "VAT" it is some benefit for the user as the user need only to adjust one "small piece" of data
I would prefer the use of "rule sets". You can stay on "hitlist" level and you need not to navigate to "specific VAT" etc.
Anyhow: The "dynamic phrase set" approach need clear "rules",.. and the set up of these rules is not easy and only if you have the rules you will see some reduction in maintenance time (and as mentioned: It should be a "VAT" which is used very often in maintenance process).
We do not have many "useful" rules to design such an approach. I have no clue if you have still your "rules" in mind
More or less: you need an "ABAPer" who knows by "heart" the data handling options in EHS (more or less: how EHS is "buffering" the data from "start of maintenance of something" until the "start of save process".
C.B.
PS: check e..g. BAPI_BUS1077_CLEARBUFFER; more or less any similar "BAPI" is helpful (e.g. https://answers.sap.com/questions/3623283/example-of-correct-bapibus1077create-call.html)
Check may be https://blogs.sap.com/2019/09/15/use-of-bapis-in-ehs-classic/
And there are some OSS Notes: https://www.stechno.net/sap-notes.html?id=1111161
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.