DType - The Central Element
The DType is one of the central elements of SAP ECTR. With DTypes, similar as the Document Type, it is possible to define different behaviors of documents in regards to processes, status network, default values, relations to other SAP business objects etc.. A DType is partition of granularity of the document type from SAP Document Management System (DC10). A document type can be used in serveral DTypes (1:n).
Use Case 1: One document type - different DTypes
In the SAP System there is one document type WRD for word documents, but you want to distinguish between specifications and documents for a material process.
This can be defined pretty simple with two DTypes with different settings for:
- icons
- with or without material link
- templates
- ...
Datamodel and Relationships
Use Case 2: Master - Non-Master Relationship
Based on a CAD-Model(3D) a drawing(2D) should be derived. The Drawing is dependent from the CAD-Model, so as you change geometry in the 3D model this needs to be updated on the drawing as well. This dependency can be managed with SAP ECTR.
There exist two possibilities to define the data model for CAD-Model(3D) and drawings(2D):
- Define the CAD-Model(3D) in the DType as type="master", define the drawings(2D) as type="master" as well.
- With this solution you have "full flexibility" in the data model, but no automatic support in any use cases or functions in ECTR.
- Please keep in mind, that a CAD drawing is not necessarily a "NonMaster". Of course it is possible to treat it simply as a single object (master), which has an assembly relation to another master. In cases in which a project requires total freedom, this is definitely legit.
- Use the "Master-Group" and define the CAD-Model(3D) in the DType as type="master", define the drawings(2D) as type="nonmaster".
- With this solutions there exists some restrictions in the data model, but you have lot of automatic support for this "master model group" in ECTR.
- The members of a master group are interconnected with distinct references. A NonMaster is always connected to only one master. Nevertheless it is allowed, that several versions of a NonMaster reference to the same Master. The resolving of this relationships is never subject of a restriction, it is always considered "as saved".
Master Group
In the ECTR context the term "master group" / "Master Non-Master relation" is used for an amount of document objects, consisting of exactly one master document and 0-n dependent NonMaster documents.The master group is needed to enable special treatment for the contained documents. This is the base for implemented complex functions in ECTR.
The master document is the 3D model, the dependent document called "non-master" is e.g. the related 2D drawing.
- Define the CAD-Model(3D) in the DType as type="master"
- Define the allowed dependent document "Non-Master"-Dtypes as type="nonmaster" in this DType
- In this NonMaster - DType it is possible to use elements of the Master (e.g. identical document number)
- Additional behavior like
- linking to same material master
- similar behavior when changing the document status
- creating new version, save as, attribute-transfer can be defined.
- Attention: As mentioned above, a dependent document "Non-Master" can be assigned to exact and only one master document.
- For so called "multi model drawings" either the Master - Non-Master relationship can't be used or one of the models have to be defined as the leading master document.
- The technical relation between the master and the "Non-Master" is saved in the field SORTF of table STPO with the value "D" behind the Application type and the ":".
- E.g. "UGS:DC"
Master - Non-Master Concept
Use Case 3: Simplification of DType configuration with templates
In order to use many different DTypes, mutual properties can be defined in templates. These DTypes inherit the properties of the embedded template e.g. a template for CAD parts and a template for drawings serving as base for different DTypes of CAD parts and drawings.
Heredity (Utilisation of templates)
