Data type for long text messages

[bjorn-henrik_zink]

Anyone who knows a good DD-data type for long text messages (+255).

Thanks!

[eddy_declercq]

What about STRING or XSTRING (for hex)?

[bjorn-henrik_zink]

I tried out STRING and that one was not sufficient. I'll try out XSTRING.

Thanks.

[bjorn-henrik_zink]

No, XSTRING doesn't work.

[eddy_declercq]

Can you be more specific on what you want to achieve?

This is BTW the list of all built in types (with their length):

http://help.sap.com/saphelp_webas620/helpdata/en/fc/eb2fd9358411d1829f0000e829fbfe/content.htm

Message was edited by: Eddy De Clercq

[bjorn-henrik_zink]

I have a text field - just like this one - and would like to store the text in the backend. Problem is, some text a very long and cause a short dump when the system tries to assign the text to the value type (DSTRING, XSTRING).

[eddy_declercq]

What is the dump saying (use trx st22) and what exactly is the backend? Is it just the remote call to an FM?

If so, does the typing of the params match?

[Former Member]

Hello Elvez,

You are saying that you want to store the long text field in the backend. Does that mean you are trying to create a new table in the ABAP Dictionary?

If yes, then I'm afraid, you cannot do it without some concepts. If you are creating a table in SE11, then, you will have to go in for Cluster Tables. Instead of the normal SELECT Statements, you will now have to use the IMPORT Statements to get the data from this cluster table. And Instead of the normal INSERT statement, you will have to use the EXPORT statement to enter the data into the database table.

If you decide to go for the cluster table, please read the SAP documentation about the cluster tables carefully. It is explained very clearly (under ABAP Programming).

The following is a summary of the requirements to build a cluster table in the ABAP Dictionary.

======================================================

The tables used to perform EXPORT/IMPORT operations should have

the following structure:

   Fld name  Fld type

1. MANDT     CLNT           Key field
2. RELID     CHAR(2)        Key field
3. File-specific key (one or several CHAR fields)
4. SRTF2     INT4           Key field
5. Further fields, not part of the key
6. CLUSTR    INT2           (Length field for EXPORT/IMPORT data)
7. CLUSTD    VARC or LRAW   (Container for EXPORT/IMPORT data)

In tables that are not client-specific, you can omit the field MANDT. The field SRTF2 can (for compatibility's sake) also defined as type INT4.

======================================================

If you need further information, please do get back.

Regards,

Anand Mandalika.

P.S. : If you have found the information useful, Please do reward the points.

[bjorn-henrik_zink]

I'm developing portal applications that is communicating with the R/3 backend. The problem is that I try to use the standard framework as far as possible. Unfortunately, that implies that I do not have control over the entire process, i.e. I can only define the portal data type and the R/3 data type. What is happening inbetween is out of my control ...