Bluesky
- SAP Managed Tags
jeff.broodwar
After checking in our system, here is some more information specifically about VBBP entries for long texts.
For TDOBJECT "VBBP" (which is for sales document line items) the value in TDNAME is a concatenation of the 10-character long VBELN and the 6 digits of the line item. This is how entries in STXH look like with VBELN highlighted in yellow and the line item number in red:
In order to find the actual long text for this entry you have to provide exactly this information like shown here via SE37 for READ_TEXT:
If you don't include the "000010" you'll get a "NOT FOUND" error, likewise if you look for an entry with another language than "EN" or ID "0001". READ_TEXT does not accept wildcards in these fields.
Here is some code to get around this by using READ_MULTIPLE_TEXTS instead:
SELECT-OPTIONS: s_obj FOR stxh-tdobject OBLIGATORY,
s_id FOR stxh-tdid OBLIGATORY,
s_spras FOR stxh-tdspras OBLIGATORY,
s_tdname FOR stxh-tdname OBLIGATORY.
DATA: lt_name_ranges TYPE tspsrname,
ls_name_ranges LIKE LINE OF lt_name_ranges,
lt_object_ranges TYPE tspsrobj,
ls_object_ranges LIKE LINE OF lt_object_ranges,
lt_id_ranges TYPE tspsrid,
ls_id_ranges LIKE LINE OF lt_id_ranges,
lt_language_ranges TYPE tspsrlang,
ls_language_ranges LIKE LINE OF lt_language_ranges.
"Shift select-option content into FM-parameters
LOOP AT s_tdname.
ls_name_ranges-sign = s_tdname-sign.
ls_name_ranges-option = s_tdname-option.
ls_name_ranges-low = s_tdname-low.
ls_name_ranges-high = s_tdname-high.
APPEND ls_name_ranges TO lt_name_ranges.
ENDLOOP.
LOOP AT s_obj.
ls_object_ranges-sign = s_obj-sign.
ls_object_ranges-option = s_obj-option.
ls_object_ranges-low = s_obj-low.
ls_object_ranges-high = s_obj-high.
APPEND ls_object_ranges TO lt_object_ranges.
ENDLOOP.
LOOP AT s_id.
ls_id_ranges-sign = s_id-sign.
ls_id_ranges-option = s_id-option.
ls_id_ranges-low = s_id-low.
ls_id_ranges-high = s_id-high.
APPEND ls_id_ranges TO lt_id_ranges.
ENDLOOP.
LOOP AT s_spras.
ls_language_ranges-sign = s_spras-sign.
ls_language_ranges-option = s_spras-option.
ls_language_ranges-low = s_spras-low.
ls_language_ranges-high = s_spras-high.
APPEND ls_language_ranges TO lt_language_ranges.
ENDLOOP.
CALL FUNCTION 'READ_MULTIPLE_TEXTS'
EXPORTING
name_ranges = lt_name_ranges
object_ranges = lt_object_ranges
id_ranges = lt_id_ranges
language_ranges = lt_language_ranges
IMPORTING
text_table = gt_text_lh
error_table = gt_error_lh
EXCEPTIONS
OTHERS = 2.
Any of these ranges used as importing parameters in READ_MULTIPLE_TEXTS can contain wildcards so you can provide TDNAME = '0000000001*" and it'll find the entry you are looking as long as you properly restrict by TDNAME and TDID (otherwise you might also get many false hits for completely different entities).
The returned table GT_TEXT_LH contains one item per corresponding entry in table STXH with the TDLINES available in table form with this deep structure. So you'll need to loop through both to build your ALV-output, something like this:
DATA: ls_tdlines TYPE LINE OF text_line_tab.
LOOP AT gt_text_lh INTO gs_text_lh.
CLEAR gs_out.
gs_out-tdname = gs_text_lh-header-tdname.
gs_out-tdobject = gs_text_lh-header-tdobject.
gs_out-tdid = gs_text_lh-header-tdid.
gs_out-tdspras = gs_text_lh-header-tdspras.
gs_out-tdfuser = gs_text_lh-header-tdfuser.
LOOP AT gs_text_lh-lines INTO ls_tdlines.
IF ls_tdlines-tdline IS NOT INITIAL.
ADD 1 TO gs_out-linenum.
gs_out-tdline = ls_tdlines-tdline.
APPEND gs_out TO gt_out.
ENDIF.
ENDLOOP.
ENDLOOP.
Hope this helps!
Cheers
Bärbel
- SAP Managed Tags
The "2 zeros" are most likely caused by your number range for the document number only needing 8 digits but internally, it is still stored with 10 digits. If you have e.g. SE16 set to respect conversion exits, SAP will strip these leading zeroes from what gets displayed in the list. In a case like this it's often a good idea to switch off the conversion exits to see the raw data as this is what is relevant for the content in TDNAME and what needs to be specified in the input parameter(s). Go to "Settings --> User parameters --> Data Browser to remove the flag (or set it again).
With "respect conversion exit", the document number looks like this in SE16 in VBAP for the example shown above as VBELN is a character field with a length of 10 and the conversion exit ALPHA is active:
When I switch conversion exits off in the user options, it looks like this:
"Your" users will see the document number without the leading zeroes in their transactions and therefore look for the wrong entries for the long texts and you'll have to make them aware of the "missing leading zeroes". In the program I created which utilizes READ_MULTIPLE_TEXTS I try to explain this in the online documentation:
"The field "Text Name" contains the actual key for the data you are interested in. This can for example be a material or equipment number, a sales order or anything else for which long texts exist. The key will need to be entered in the internal format which means that for example a material number needs to be entered as "000000000012345678" instead of as "1.234-567.8"."
I also explain this:
"You need to know the technical keys for the long texts you want to retrieve. This information can sometimes be found from within the transaction where they are entered or displayed. If this is not available, check with the IT-specialist for your process area."
- SAP Managed Tags
Hello jeff.broodwar
If you don't know how to call READ_TEXT in a specific scenario .e.g to read a long text of an SD invoicing document, here is an approach that works for me. SAP standard transactions use READ_TEXT. So you can put a break-point in READ_TEXT and display a long text in a SAP standard transaction. Then the execution will stop on READ_TEXT and you can examine the input parameters under the debugger. That always helps me.
Best regards
Dominik Tylczynski
- SAP Managed Tags
Hi
Check with functional for the particular combinations are configured . So that text could be maintained . Check the Text ID value , Language, Text Name through display T code . Check text maintained for the combinations if not maintain .
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
