SAP CRM附件在應用伺服器上的儲存原理解析
History:
Content Management(CM) was introduced in basis release 6.10 and implemented in CRM 3.0. Before CM was used, CRM applications was using the Business Document Service (BDS) or Generic Object Services (GOS) to implement Document management requirement. BDS was used in most applications like Business partners, products, product catalogues, solution database, campaigns. GOS was only used in the One Order objects like activities and opportunities. All BDS applications changed to CM in 3.0, the One Order objects only in 3.1.
A document in CM consists of several objects. The most important two are so called “logical info object” (LOIO) and a “physical info object” (PHIO). A LOIO as a logical folder or bracket which holds PHIOs together, while a PHIO represents the content of a specific version of a document. Let’s use the word edit in the real world as example. If one works on a Word document and changes the document over time, each saved version would be represented by a PHIO. The LOIO would be the word document itself. This is much like if one looks at SE38 in ABAP: The program name is the LOIO and each transported version of the code is the PHIO.
Let’s see an example. I have a product ZCM_DEMO with guid 0090FA0D8DC21ED395FD7C687F99BFF7, BOR type = BUS1178. I create one attachment for it:
Go to table SKWG_BREL, input product guid 0090FA0D8DC21ED395FD7C687F99BFF7, and we see two entries belonging to this product. The first entry indicates a folder instance which is actually a logical container to hold all attachments for the given product.
The content of column INSTID_B has naming convention as . The guid in the first row can be found in table CRM_FOLDER:
The guid 0090FA0D8DC21ED395FD830F8DD9DFFF in the second row can be found in table BDSLOIO22, together with the name of attachment.
You are asking how I get to know the name of table BDSLOIO22? If one application wants to use CM to store document, it should have its dedicated class for physical object and logical object, or use the default one CRM_L_DOC. The relationship between application and its class is maintained in tcode DMWB:
in table BDSPHIO22, by specifying logical information object ID, we can get all phyiscal object lists.
once you get phyical object id 0090FA0D8DC21ED395FD830F8DD9FFFF, you can find the respective entries in table BDSCONT22.
The real content of attachment is stored in a claster way, so you cannot see its detail in SE16.
How do I know the database table name BDSCONT22? (1) Get the storage category BDS_DB22 by physical class name.
(2) execute function module SCMS_SDOKSTRE_LIST to get all lists of database table. Then you can find the table name BDSCONT22 for your storage category BDS_DB22.
要獲取更多Jerry的原創文章,請關注公眾號"汪子熙":
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/24475491/viewspace-2709634/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 如何讓你的SAP CRM應用支援附件上傳
- SAP CRM附件模型的Authorization scope原理介紹模型
- 如何啟用SAP CRM附件UI上的advanced按鈕UI
- 如何阻止指定型別的SAP CRM附件被上傳到伺服器型別伺服器
- 一個伺服器輕鬆儲存上億資料,TDengine 在北京智慧建築邊緣儲存的應用伺服器
- 使用程式碼修改SAP CRM附件的屬性
- SAP CRM Survey調查問卷的儲存模型模型
- wordpress外掛在伺服器上的儲存位置伺服器
- 動態控制SAP CRM附件的可編輯性
- SAP CRM Fiori應用和SAP JAM的整合配置
- SAP MM 給合同的ITEM上傳附件以及附件查詢
- 動態隱藏某些特殊型別的SAP CRM附件型別
- 在vue中,localStorage本地儲存應用。Vue
- SAP CRM Survey調查問卷的模型設計原理解析模型
- 在風能和太陽能儲存中的新應用
- 使用ABAP程式碼給SAP CRM Business object建立附件AttachmentObject
- SQL Server 深入解析索引儲存(上)SQLServer索引
- CRM在物流公司的應用策略
- 如何延長儲存伺服器上資料的儲存時間?伺服器
- SAP CRM銷售訂單UI上的欄位對應的資料庫表儲存欄位:requested start date和end dateUI資料庫
- WordPress如何使用騰訊雲物件儲存COS儲存媒體庫附件物件
- 在 SAP BTP Kyma Runtime 上使用 Redis 讀取和儲存資料Redis
- SAP CRM點了附件的超連結後報錯的處理方式
- 在Kubernetes上執行SAP UI5應用(上)UI
- Git的儲存原理Git
- SAP CRM Fiori應用冗餘round trip的原因分析
- SAP UI5 應用的 OData 後設資料請求響應的解析原理分析UI
- 計算儲存分離在訊息佇列上的應用佇列
- 儲存網路在企業應用中的安全隱患
- 在伺服器建立 git 儲存庫伺服器Git
- SAP QM 如何將一個附件掛在一個Quality Notification單據上?
- RocketMQ架構原理解析(二):訊息儲存MQ架構
- MultipartFile上傳圖片儲存伺服器伺服器
- 使用 mock 資料在本地執行 SAP Fiori Elements 應用的工作原理Mock
- CRM系統在電商企業的應用
- 資訊科技在CRM軟體中的應用
- HarmonyOS:儲存你的應用資料
- 在快應用中整合華為AGC雲端儲存服務GC