Shulou(Shulou.com)06/01 Report--

This article introduces how to analyze the storage principle of SAP CRM accessories on the application server, the content is very detailed, interested friends can refer to, hope to be helpful to you.

Content management (CM) is introduced in BasisRelease6.10 and implemented in CRM 3.0. Before using CM, CRM applications used Business document Services (BDS) or Common object Services (GOS) to implement document management requirements. BDS is used for most applications, such as business partners, products, product catalogs, solution databases, and activities. GOS is used only for first-order objects, such as events and opportunities. All BDS applications are changed to CM in 3. 0, and first-order objects are only in 3. 1.

A document in CM consists of multiple objects. The two most important are so-called "logical information objects" (LOIO) and "physical information objects" (PHIO). LOIO is a logical folder or parenthesis that puts PHIO together, while PHIO represents the contents of a specific version of the document. Let's take the real-world word "editor" as an example. If you work with an Word document and change the document over time, each saved version will be represented by PHIO. LOIO is the word document itself. This is very similar to SE38 in ABAP: the program name is LOIO and each transport version of the code is PHIO.

Let's look at an example. I have a product ZCM_ demo, guid is 0090FA0D8DC21ED395FD7C687F99BFF7BOR type = BUS1178. I created an attachment for it:

Go to the table SKWG_BREL, enter the product guid 0090FA0D8DC21ED395FD7C687F99BFF7, and we see two entries that belong to this product. The first entry represents a folder instance, which is actually a logical container that holds all attachments for a given product.

The contents of the Instit_B column have a naming convention. The guid in the first row can be found in the table CRM\ U folder:

The guid 0090FA0D8DC21ED395FD830F8DD9DFFF in the second row, along with the attachment name, can be found in the table BDSLIO22.

Are you asking me how to know the name of the BDSLIO22 table? If an application wants to use CM to store documents, it should provide specialized classes for physical and logical objects, or use a default CRM_L_ document. The relationship between the application and its classes is maintained in tcode DMWB:

In the table BDSPHIO22, we can get a list of all physical objects by specifying the logical information object ID.

After you get the physical object id 0090FA0D8DC21ED395FD830F8DD9FFFF, you can find the corresponding entry in the table BDSCONT22.

The real content of the attachment is stored in a simpler way, so you can't see its details in SE16.

How do I know the database table name BDSCONT22?

(1) get the storage class BDS_DB22 by physical class name.

(2) execute the function module SCMS_SDOKSTRE_LIST to get all the lists of database tables. You can then find the table name BDSCONT22 that stores the category BDS_DB22.

On how to analyze the storage principle of SAP CRM attachments on the application server is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.