on 2022 Feb 03 6:46 AM
Dear All,
We have a requirement to set the texts for EHS substance numbers as bold when we are receiving the data from a third-party system. For creating the substance number, we are using the logic of standard BAPI_BUS1077_CREATE and for changing the substance data, we are trying to use logic of standard BAPI_BUS1077_CHANGE.
However, the standard BAPI is converting the character formats to a different one as the character format <H> (For Bold) is converted to <(><<)>H> due to which it is not getting identified by standard style EHS_STD.
Requesting a solution from everyone regarding this issue.
Request clarification before answering.
Hello
not clear why you would like to "format" the text. Do you would like to use the text in WWI context or for a different purpose?
C.B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
not "100%" sure what you would like to get. The style EHS_STD is linke to e.g. "identifiers", "Phrases" or "user defined text" but not specification numbers
PLease explain better what you would like to get
C.B.
PS: check e.g. https://answers.sap.com/questions/11016263/special-characters-in-phrase-typed-correctly-on-ms.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Christoph,
Thank you for the link.
The issue is regarding user defined text in the specification number.
Like when we are trying to create/change a specification`s user defined text, the character formats are not taken into consideration using the BAPI and the character format for bold <H> is converted to <(><<)>H> hence making the texts as not bold.
I found FM C14GN_TEXT_TRANSFER which changes this format. However I am not able to by-pass this FM in the standard BAPI logic.
Can you share any alternate possible approach for this please?
Best Regards,
Anuj
User | Count |
---|---|
3 | |
2 | |
1 | |
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.