Standard Content Models for Records Management  

Structure of a Content Model

A content model is a definition for documents with a common structure. You characterize a content model by assigning values to particular attributes when storing individual documents. The documents can be stored either in the SAP database, or in external storage systems. For more information on content models, see the Document Modeling Workbench documentation.

A content model consists of the following parts:

·            A logical information object class (LOIO class)

Determines the properties (including the attributes) of the logical information object.

A logical information object (LOIO) does not have any content, but it groups together all physical information objects (see below) of a document. The LOIO represents the whole document and is identified by an ID generated by the system.

·            A physical information object class (PHIO class)

Determines the properties (including the attributes) of the physical information object.

A physical information object (PHIO) is an information object with content. More than one PHIO can be related to a logical information object. PHIOs represent the versions and variants of a document.

·            A connection area

Determines possible relations.

·            Associated relation classes

Determine the semantics of possible relations.

·            Associated information object attributes (IO attributes)

Attributes that can be used for both the LOIO and the PHIO classes.

Attributes of an LOIO class (in short: LOIO attributes) apply to the whole document. For each LOIO attribute there is only one LOIO attribute value. If an LOIO attribute value is changed by the user in one version of the document, the value is also changed in all previous versions of the document.

Attributes of a PHIO class (in short: PHIO attributes) are saved for each PHIO. If a PHIO attribute value is changed by the user in one version of the document, the value is also changed in all previous versions of the document.

All classes are virtual as well as real classes. The virtual classes are identified by a V on the end of the name. The virtual class is a template class that can transfer properties to other virtual classes and to real classes.

When creating element types, the name of the LOIO class must be entered as a value for the connection parameter DOCUMENT_CLASS.

Content Models Supplied

SAP supplies standard content models for elements that are based on the back end of the generic service provider. You can either use these content models unchanged, or create your own content models. For more information on creating your own content models, see Creating and Editing a New Content Model.

The table below provides an overview of the content models for Records Management that are supplied by SAP. You can view the standard content models in the Document Modeling Workbench (see Displaying Standard Content Models for Records Management).

Content Model  Name	Contents	M	T	LOIO class name	Name of virtual LOIO class from which properties are inherited	PHIO class name	Name of virtual PHIO class from which properties are inherited
SRM_REC00	Records	+	-	SRM_REC00	SRM_RECORDS_V	SRM_RECP00	SRM_RECORDS_PH_V
SRM_REC01	Demo records	-	+	SRM_REC01	SRM_DEMO_RECORDS_V	SRM_RECP01	SRM_DEMO_RECORDS_PH_V
SRM_RCD08	DOMEA records	+	-	SRM_RCD08	SRM_RECORD_DOM_V	SRM_RCDP08	SRM_RECORD_PH_V
SRM_RCP06	Personnel records	+	-	SRM_RCP06	SRM_P_RECORD_V	SRM_RCPP06	SRM_P_RECORD_PH_V
SRM_DOC04	Documents	+	-	SRM_DOC04	SRM_DOCUMENTS_V	SRM_DOCP04	SRM_DOCUMENTS_PH_V
SRM_DOC05	Demo documents	-	+	SRM_DOC05	SRM_DEMO_DOCUMENTS_V	SRM_DOCP05	SRM_DEMO_DOCUMENTS_PH_V
SRM_DCD09	DOMEA documents	+	-	SRM_DCD09	SRM_DOCUMENTS_DOM_V	SRM_DCDP09	SRM_DOCUMENTS_DOM_PH_V
SRM_MOD02	Record Models	-	+	SRM_MOD02	SRM_MODEL_V	SRM_MODP02	SRM_MODEL_PH_V.
SRM_FPL03	File Plans	-	+	SRM_FPL03	SRM_FILEPLAN_V	SRM_FPLP03	SRM_FILEPLAN_PH_V

Key:

·        M: Client-specific

·        T: Elements based on this content model are transportable (content models themselves are transportable).

·        DOMEA records/DOMEA documents: Contain attributes required by DOMEA. (The DOMEA concept is a German standard for the paper-free processing of electronic records in public authorities.)

·        Demo records/Demo documents: Supplied by SAP as examples. Do not change these.

Note:

There are no specific content models for notes or for administration data of paper documents, because you can use the same content model as normal documents for notes and administration data.