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:


SAP CRM 附件在应用服务器上的存储原理解析SAP CRM 附件在应用服务器上的存储原理解析SAP CRM 附件在应用服务器上的存储原理解析SAP CRM 附件在应用服务器上的存储原理解析SAP CRM 附件在应用服务器上的存储原理解析SAP CRM 附件在应用服务器上的存储原理解析SAP CRM 附件在应用服务器上的存储原理解析SAP CRM 附件在应用服务器上的存储原理解析SAP CRM 附件在应用服务器上的存储原理解析SAP CRM 附件在应用服务器上的存储原理解析

上一篇:Photoshop将制作出人像摄影妆面的修饰的最佳效果化妆教程


下一篇:Photoshop将室内美女图片调成光亮的粉紫色