There is a table in our BRF+ which has a language field
The language is shown as single character with a description when you display the table.
When you export the table you only get the single character without description.
When you maintain the value you are asked to enter 2 digits.
We have some exotic languages installed ( European Portuguese and Brazilian Portuguese for example) where this single character leaves a lot room for guesses.
The single character for one of these languages is P while the other is 느
Of course I know that the language is stored in table T002 and it has the internal 1 character language and the 2 character long external value which is presented to the users via the conversion exit.
Now a user asked if it is possible to get the 2 character language field into the extract
In SE16N a user can decide whether he wants to see the values with conversion exit or without. Is there a similar function in BRF+ ?
I hope I explained the situation well enough as I'm not at all a BRF+ guy, just trying to help this user, even I think it is just a cosmetic request and that someone who is able to work with BRF+ should be able to remember that 느 represents Portuguese ;-)
I saw this blog https://blogs.sap.com/2016/04/22/creation-of-procedure-call-in-sap-brf/ and guess this is a way that could be used to make it happen, but a setting with a single x in a box like in SE16N is certainly preferred. Do you have any information if such simple setting is somewhere hidden? or is the way from the blog the only option to make the user happy?
I just checked in a quite up-to-date system (NW 750 SP05). There is neither an application exit for this scenario nor any other BRFplus extension mechanism that would allow you to fulfill the requirement without a modification.
I do not recommend to modify the SAP source code. However, if the requirement must be fulfilled at any price (i.e. with all downsides a modification brings with it) the class CL_FDT_XL_SPREADSHEET (Method CREATE_DOCUMENT) is the one where the Excel magic happens.
P.S. There are quite some ToDo comments in the code, so maybe some future releases might cone up with a out-of-the.box solution.