Long text table in sap

Long text table in sap DEFAULT

CATSDB-LONGTEXT Long text SAP Table field attributes inc. CATSLONGTE Data Element

LONGTEXT is a standard field within SAP Table catsdb that stores Long text information.

Below is the list of attribute values for this field including its length, data type, description text, associated , search help etc... You could also view this information on your SAP system if you enter the table name CATSDB or data element CATSLONGTE into the relevant SAP transaction such as SE11 or SE80.

Also check out the Contributions section below to add and view useful hints, tips and screen shots specific to this SAP table field. These details can also be found quickly in the future by simply searching on the SAP object name CATSDB-LONGTEXT or its description.


Main Table:catsdb

Example ABAP code to select data from table CATSDB field LONGTEXT

DATA: LD_LONGTEXT TYPE CATSDB-LONGTEXT.

SELECT single LONGTEXT
FROM CATSDB
INTO LD_LONGTEXT
WHERE...

Attributes from SAP Table field CATSDB-LONGTEXT




 

LONGTEXT - Long Text
LOGSYS - Logical system
LGART - Wage Type
LAETM - Time of Last Change
LAEDA - Date of Last Change
KOKRS - Controlling Area
All CATSDB Fields...




Sours: https://www.se80.co.uk/saptabfields/c/cats/catsdb-longtext.htm

“What about SAP Long Text?”

abaumannTechnology digital wave background concep

In data warehouse projects, integrating SAP data, one particular question usually pops up a couple of months into the project:

“What about SAP Long Text?”

Long Text (also referred to as SAPscript texts or text objects) are the containers attached to SAP ERP objects to accommodate long text in SAP systems. Users can put free text and even apply formatting and they are not blocked by common database or application restrictions. Users put long text on common SAP objects like sales orders, materials, or notifications. SAP created this functionality because old database systems had text columns limited to around 255 characters. The “new” database systems don’t have this restriction, but Long Text remained anyway.

Tiny tree in a cardboard boxSAP stores the Long Text in a particular format within a special structure in the application. The table STXL, for instance, saves the Long Text details in a blob similar to SAP’s cluster tables. This structure makes it hard for traditional ETL and more current data acquisition methods to get the data in a transparent format on a target system and requires a lot of SAP expertise.

“So what about Long Text?”

filtering data iconBack in the day, my first reaction was, “what value does this type of unstructured data add?” How would the Long Text fit within the defined structure of the data warehouse/data mart? This data was not harmonized and would need a lot of sanitizing before it could be of use. Further, seeing the effort required for integration, I gave the advice to use other fields to store information. For example, if a sales department was managing the sales order status in the Long Text, wouldn’t it be much better to use/configure the sales order status field?

So much for good advice…

SAP users liked the freedom the Long Text provided and using common fields to store the same information could require a long change process. In the end, all implementations, without exception, added Long Text structures to their extraction and data warehouses with experts’ help on the integration side. The requirement and use cases for this kind of data have lately only grown as analytical methods nowadays are more equipped to handle unstructured data. Text and ML analysis on tickets or maintenance orders can offer new insights.

Ok, so Long Text integration will remain a normal challenge?

Long Text integration has become easier this year because HVR can replicate Long Text directly from SAP ECC or S/4HANA. The blob containing the Long Text in STXL will be made transparent during the replication process without much additional effort. As a result, HVR users can source near real-time Long Text on all SAP objects with the same software and method as transparent or other cluster and pool tables.

HVR supports a significant number of targets from traditional databases (e.g., Oracle, SQL Server), data warehouse systems (Snowflake, Teradata), or file-based solutions like ADLS or KAFKA. This enables companies to use their SAP Long Text in many different target systems without much latency. Of course, the use case is dependent on how an organization uses Long Text. Still, the effort to integrate text, for example, on sales orders (for status analysis) or text on repair orders (for failure analysis), is no longer an argument for leaving this data in the SAP source.

If you’re interested in learning more about HVR’s SAP data replication capabilities, feel free to contact us or check out these additional resources:

Sours: https://www.hvr-software.com/blog/what-about-long-text/
  1. Replace honda civic door handle
  2. Wide band marquise diamond rings
  3. Double 20 gallon tank stand
  4. Oregon ducks football schedule 2017

SAP HANA: Material Classification Data with LongText into HANA

In this Blog, I want to show How to bring Material Classification Data along with LongText into HANA.

As per example below, I want to bring all the Classification Data for this Material along with LongText.

This Below screenshot is from MM03 and you can see how the Classification Data is defines with Longtext.

ECC Version: 618.

 

In order to build a calculation view in HANA, we need below SAP TABLES to bring Classification Data.

  • CABN – Characteristic
  • CABNT – Characteristic Descriptions
  • CAWN – Characteristic values
  • STXH –  SAPscript text file header
  • STXL –  SAPscript text file lines

As you can see below, to bring the Longtext, we cannot get the readable format text from these Tables STXH & STXL. These tables are in compressed format.

Oneway to bring this longtext in readable format is to create a custom program to convert the Data into readable format and store them into Z Table. That way we can use the Z table in our Calculation view.

Program to read the STXH & STXL tables and store the data in Z table. In this case I have created Table ZMAT_CLASS_TXT and Program ZMAT_CLASSIF_TXT.

Custom Table:

ABAP Code for Program to update the Classification LongText lines into Table:

*&———————————————————————*
*& Report ZMAT_CLASSIF_TXT
*&———————————————————————*
*&
*&———————————————————————*
REPORT ZMAT_CLASSIF_TXT.
TABLES: ZMAT_CLASS_TXT, STXH.
TYPES: BEGIN OF TY_STXL,
TDNAME TYPE STXL-TDNAME,
CLUSTR TYPE STXL-CLUSTR,
CLUSTD TYPE STXL-CLUSTD,
END OF TY_STXL.
DATA:  T_STXL TYPE STANDARD TABLE OF TY_STXL.
FIELD-SYMBOLS:

SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-t01.
SELECT-OPTIONS:
S_OBJECT FOR STXH-TDOBJECT NO INTERVALS OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.

SELECT TDNAME TDOBJECT TDID
FROM STXH
INTO CORRESPONDING FIELDS OF TABLE T_STXH
WHERE TDOBJECT = S_OBJECT-LOW AND
TDSPRAS = SY-LANGU.
*AND THEN
* select compressed text lines in blocks of 3000 (adjustable)
SELECT TDNAME CLUSTR CLUSTD
INTO TABLE T_STXL
FROM STXL
PACKAGE SIZE 3000
FOR ALL ENTRIES IN T_STXH “WITH APPLICATION DATA AND TDNAME
WHERE RELID    = ‘TX’          “standard text
AND TDOBJECT = T_STXH-TDOBJECT
AND TDID     = T_STXH-TDID
AND TDSPRAS  = SY-LANGU.
LOOP AT T_STXL ASSIGNING

W_STXL_RAW-CLUSTR =

After completion of the program execution in Dialog mode, you can see below screen.

Check the Table if the Longtext is uploaded.

Now, I have created a Calculation View in HANA to bring all the Material Classification Data along with LongText based on these Tables.

  • CABN – Characteristic
  • CABNT – Characteristic Descriptions
  • CAWN – Characteristic values
  • ZMAT_CLASS_TXT – LongText

Join_1:

Join_2 :

 

Join_3:

Projection_4: I have concatenated all the 10 Lines text into 1 calculated Column CA_LONG_TEXT with length 1333.

Note: The Max length we can use is 1333.

 

To read all the 10 Lines LongText, I have to create multiple joins with ZMAT_CLASS_TXT table with filters on Lines. For example, to read 1st line of text, I need to filter on ZLINES = ‘00000001’.

 

Join_6:

 

Similarly, we need to add more joins to bring all the 10 Text lines.

Join_7:

Join_8:

…..

……

Create Joins until you reach Join_15 with all the 10 Text Lines.

Join_15:

Full Hana View DataFlow Diagram:

 

Output of the Hana View:

Would you like to access Full Article?
If you are already a member in this website, Please Click here to loginIf you are not yet a member, Please Click here to Sign up  
if you have any questions don’t hesitate to contact us from the Button bellow

Contact US

New NetWeaver Information at SAP.com

User Rating: Be the first one !
Sours: https://learntips.net/sap-hana-material-classification-data-with-longtext-into-hana/
4 Text type in sap abap smartforms

She moaned and touched his head. Her lips were hardening, her juices poured and poured, and a pleasant spasm swept through her legs. - It should be. I was very excited.

Text in sap table long

She freaked out even more. I smiled and began to suck again. Soon I, pushing my panties aside, saddled Dimka. The jump lasted about 15 minutes, when I finished, Dima roughly took me off my dick and approached Irka.

Mass change of SAP Materials Long text using WORD

What are you, Ksyunya, can you forget such a thing. But: It's not okay. - Mom, forget you decency at least for this night. You're on fire.

You will also be interested:

Mom also updated her wardrobe. In the evening we sat in the kitchen. I listened to my mother's lectures, did not mind and promised to be obedient.



437 438 439 440 441