Regarding Long Text

Former Member — Tue, 26 Jun 2007 12:23:55 GMT

Hi All,

Can anyone pls let me know in which table the long text values of a object is stored.

thanks

Sathish

Re: Regarding Long Text

Former Member — Tue, 26 Jun 2007 12:26:37 GMT

Hi,

STXH tables stores the Long texts

Long text are stored in CLUSTER tables, so selecting or fetching the data from this table will be little difficult so try to use the FM READ_TEXT as shown in this link below

http://www.sap-basis-abap.com/sapac002.htm

To find the attributes to be passed to the FM go to the transaction for which you want to read the long text and double click on the text object and from the menu use GOTO--> HEADER DATA.

Regards,

Padmam.

Re: Regarding Long Text

Former Member — Tue, 26 Jun 2007 12:26:56 GMT

Hi Sathish,

DOKHL table.

Reward if useful!

Re: Regarding Long Text

Former Member — Tue, 26 Jun 2007 12:26:57 GMT

Long Text values are stored with some parameters in table STXH

with OBJECT,ID,NAME and LANG parameters

You have to use READ_TEXT fun module to fetch the data

READ_TEXT

READ_TEXT provides a text for the application program in the specified work areas.

The function module reads the desired text from the text file, the text memory, or the archive. You must fully specify the text using OBJECT, NAME, ID, and LANGUAGE. An internal work area can hold only one text; therefore, generic specifications are not allowed with these options.

After successful reading, the system places header information and text lines into the work areas specified with HEADER and LINES.

If a reference text is used, SAPscript automatically processes the reference chain and provides the text lines found in the text at the end of the chain. If an error occurs, the system leaves the function module and triggers the exception REFERENCE_CHECK.

Function call:

CALL FUNCTION 'READ_TEXT'

EXPORTING CLIENT = SY-MANDTsa

OBJECT = ?...

NAME = ?...

ID = ?...

LANGUAGE = ?...

ARCHIVE_HANDLE = 0

IMPORTING HEADER =

TABLES LINES = ?...

EXCEPTIONS ID =

LANGUAGE =

NAME =

NOT_FOUND =

OBJECT =

REFERENCE_CHECK =

WRONG_ACCESS_TO_ARCHIVE =

Export parameters:

CLIENT

Specify the client under which the text is stored. If you omit this parameter, the system uses the current client as default.

Reference field: SY-MANDT

Default value: SY-MANDT

OBJECT

Enter the name of the text object to which the text is allocated. Table TTXOB contains the valid objects.

Reference field: THEAD-TDOBJECT

NAME

Enter the name of the text module. The name may be up to 70 characters long. Its internal structure depends on the text object used.

Reference field: THEAD-TDNAME

Enter the text ID of the text module. Table TTXID contains the valid text IDs, depending on the text object.

Reference field: THEAD-TDID

LANGUAGE

Enter the language key of the text module. The system accepts only languages that are defined in table T002.

Reference field: THEAD-TDSPRAS

ARCHIVE_HANDLE

If you want to read the text from the archive, you must enter a handle here. The system uses it to access the archive. You can create the handle using the function module ACHIVE_OPEN_FOR_READ.

The value '0' indicates that you do not want to read the text from the archive.

Reference field: SY-TABIX

Default value: 0

Import parameters:

HEADER

If the system finds the desired text, it returns the text header in this parameter.

Structure: THEAD

Table parameters:

LINES

The table contains all text lines that belong to the text read.

Structure: TLINE

Exceptions:

The text ID specified in the parameter ID does not exist in table TTXID. It must be defined there together with the object of the text module.

LANGUAGE

The parameter LANGUAGE contains a language key that does not exist in table T002.

NAME

The parameter NAME contains the name of a text module that does not correspond to the SAPscript conventions.

Possible errors:

The field contains only blanks.

The field contains the invalid characters ‘*’ or ‘,’.

OBJECT

The parameter OBJECT contains the name of a text object that does not exist in table TTXOB.

NOT_FOUND

The system did not find the specified text module.

REFERENCE_CHECK

The text module to be read has no text lines of its own but refers to the lines of another text module. This reference chain can include several levels. For the current text, the chain is interrupted, that is, one of the text modules referred to in the chain no longer exists.

WRONG_ACCESS_ TO_ARCHIVE

The exception WRONG_ACCESS_TO_ARCHIVE is triggered if an archive is accessed using an incorrect or non-existing archive handle or an incorrect mode (that is, read if the archive is open for writing or vice versa).

Reward points for useful Answers

Regards

Anji

Re: Regarding Long Text

Former Member — Tue, 26 Jun 2007 12:33:30 GMT

Hi,

The text is stored in STXL, but you can read it. You need to read the text using the READ_TEXT function module.

Regards

Re: Regarding Long Text

Former Member — Tue, 26 Jun 2007 12:34:44 GMT

Right now i am using the FM read_text..but here they want me to use tables instead of direct read..bcos they want to check performance issue by directly reading the table.

thanks

Sathish

topic Re: Regarding Long Text in Application Development and Automation Discussions

Regarding Long Text

Re: Regarding Long Text

Re: Regarding Long Text

Re: Regarding Long Text

Re: Regarding Long Text

Re: Regarding Long Text