如何从STXL.CLUSTD解码SAP文本? [英] How to decode SAP text from from STXL.CLUSTD?

查看:384
本文介绍了如何从STXL.CLUSTD解码SAP文本?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我知道!读取STXL.CLUSTD的正确方法是通过SAP ABAP函数。但很抱歉,我们因性能问题而遭受重创。我们已经做出直接进入数据库(Oracle)的决定,并且由于到目前为止一切都变得好得多,我们还没有任何计划可以恢复我们的决定。

I know ! The "proper" way to read STXL.CLUSTD is through SAP ABAP function. But I'm sorry, we are suffering badly from performance problem. We have already make our decision to go directly to the database (Oracle), and we don't have any plan to revert our decision yet since everything goes so much better so far.

但是,我们遇到了这个问题。 STXL.CLUSTD字段中的文本以无法理解的格式存储。我们无法通过Google找到有关其编码格式的任何信息。有人可以提示我如何从STXL.CLUSTD解码文本吗?

However, we've came across this issue. The text in STXL.CLUSTD field was stored in an incomprehensible format. We cannot find any information about its encoding format via google. Anybody can hint me how to decode text from STXL.CLUSTD ?

谢谢

推荐答案

短版:您不需要。使用功能模块READ_TEXT。

Short version: You don't. Use the function module READ_TEXT.

长版:您正在寻找一个所谓的簇表。参见 http://help.sap.com/saphelp_47x200/helpdata/ zh_cn / fc / eb3bf8358411d1829f0000e829fbfe / frameset.htm 。您看到的数据是文本的内部表示,与ABAP内核在内部处理数据的方式有关。没有元数据,该数据将毫无意义。如果以不兼容的方式更改原始结构,则无法再读取数据。哦,我是否提到数据不包含对元数据的引用?在读取这些表的内容时,即使在ABAP中,也需要知道原始的源数据结构,否则注定要失败。没有元数据和内核如何在运行时处理这些数据类型的知识,您将很难解密内容。

Long version: You're looking at a so-called cluster table. See http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb3bf8358411d1829f0000e829fbfe/frameset.htm for the details. The data you see is an internal representation of the text, somehow related to the way the ABAP kernel handles the data internally. This data does not make any sense without the metadata. If you change the original structure in an incompatible way, the data can no longer be read. Oh, and did I mention that the data does not contain a reference to the metadata? When reading the contents of these tables, even in ABAP, you need to know the original source data structure, otherwise you're doomed. Without the metadata and the knowledge of how the kernel handles these data types at runtime, you'll have a hard time deciphering the contents.

个人意见:直接访问SAP R / 3系统下的数据库并不是一个好主意,因为这不仅绕过了所有安全措施,而且使您极易受到数据库的所有结构更改的影响。直接访问数据库的唯一真正原因不是缺乏性能,而是缺乏(ABAP)知识,这应该可以治愈:-)

Personal opinion: Direct access to the database below the SAP R/3 system is a really bad idea since this not only bypasses all safety measures, but it also makes you very vulnerable to all structural changes of the database. The only real reason for accessing the database directly is not lack of performance, but lack of (ABAP) knowledge, and that should be curable :-)

这篇关于如何从STXL.CLUSTD解码SAP文本?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆