Long Text Data Loading into BI using Table STXH

[former_member779625]

Hi Gurus,

I have got some requirement regarding Material Sales Long Text Data Loading into BI using table STXH in Generic Extraction. Can somebody please guide me how to proceed with it as I have some how manage to find out that using READ_TEXT function module i can fetch Text Data.

Since Direct Loading into Extractor Internal Table (E_T_DATA) is not possible I need to fetch all the OBJECT of 'MVKE' and TEXTID '0001' using READ_TEXT and appending each long text into E_T_DATA.

This will cause overflow of data since it will cross default package size Limit while appending Data.

Please guide me how to avoid overflow of data.

Thanks,

Aalok .

Edited by: aalokg on Sep 27, 2010 6:13 PM

[Former Member · Accepted solution]

There is no support to store or display long text in BW. The maximum length of a characteristic InfoObject is 60. You will have to define multiple InfoObjects, divide the long text and store accordingly.

Your table definition for the DataSource should be MVKE. Bring in the whole key. Extend the structure to add long text fields, each with 60 length. In the user exit, call READ_TEXT, split the long text (there is an FM to do that), and assign to the text fields. Obviously there is a limit to how much text you can bring into BW.

Make sure your users understand that it is not going to be easy to search in the long text.

BTW, it is a good idea to convert the long text to upper case.

[former_member779625 · Accepted solution]

Hi Sudhi,

I did everything as described by you but my problem is, I have manually set package size in generic extractor as 8000 to avoid data overflow. Whenever i fetch using select query, 8000 records get fetched, apart from that I append other text lines as well.

So Whenever i run Infopackage it causes short dump or shows 0 records fetched since i am programatially appending other texts in generic extractor.

Thanks,

Aalok

[Former Member · Accepted solution]

That is the problem associated with bringing unlimited amount of text. My suggestion was to bring the text horizontally. You are bringing it vertically - that is OK, but you have to limit the number of rows.

Otherwise, you will have to implement FM based DataSource as someone else has suggested. A more complex solution and hard to maintain.

What you are doing is:

KeyField1  KeyField2  KeyField3  LineNumber  Text

What I am suggesting is:

KeyField1  KeyField2  KeyField3  TextSegment1  TextSegment2  TextSegment3

Bottom line is, users don't get what they really want.

[former_member779625 · Accepted solution]

Hi Sudhi, Thanks a ton, I got you now what are you trying to suggest... I will try implementing the same.. Offcourse yes, we cant always provide end user exactly what they demand..

Regards,

Aalok

[Former Member]

Aalok,

I worked on a similar requirement a while ago, the need was to extract 300 characters text field from CRM! Below doc is very helpful.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8d...

Follow the steps to build your generic datasource. Once you have this sorted out, you can build the BW model as per your needs. In your case, you have not defined maximum number of lines for DB table, you need to do this. Take help of some ABAP'er, if not let us know.

Hope this helps.

[former_member209032]

Hi,

Create a generic text datasource for this in RSO2 based on function module. In the function module use ur logic to fill the data and map this datasource to ur infoobject.

Regards,

Raghavendra.