Additional Windchill Capabilities > Service Information Management > About Windchill Service Information Manager — S1000D Module > S1000D Business Processes > Data Interchange > Create a New Data Module List
  
Create a New Data Module List
To manage a Data Module List (DML) from an information structure, you must first create a placeholder for it at a prescribed location. Its entries will then be autogenerated when a package is created for data interchange.
* 
From Issue 4.1 of the S1000D specification the data module list was renamed to data management list. The term data module list continues in use in the UI for 4.01, 4.1, and 4.2 products, for purposes of consistency.
To create a DML object in the information structure:
1. Select an information structure node, at the Model Identification Code level of the SNS
* 
By default, the option to create to create a DML object is limited to the Product Manager role.
2. Create this node hierarchy under the Model Identification Code:
Data Module Lists
Sent
[CAGE code of receiver]
Use Insert New > Insert New Group functionality to create the hierarchy:
a. Select the Model Identification Code node and create a group of Type Data Module Lists, named for example DML
b. Select the Data Module Lists node and create a group of Type Sent, named for example Sent To
c. Select the Sent node and create a group of Type Cage Code, selecting the required receiver organization to populate the attributes of the node
3. Select the Cage Code node and select Insert New > Insert New Data Module List
The Insert New Data Module List dialog box is displayed.
For more information, see Insert New Data Module List Dialog Box.
4. Select the required language from the Authoring Language pull-down list
5. Select the required template from the Template pull-down list
This list is populated with the DML templates from the product’s Information Code Library that match the selected Authoring Language.
6. In the Attributes section:
Select the appropriate Location option — Autoselect Folder or Select Folder
By default, the DML object is saved to the S1000D folder.
Select the appropriate StateWork in Progress or Ready for Packaging
Choose Ready for Packaging if you do not plan to make any changes to the DML.
7. In the S1000D section:
Select the appropriate sender organization code from the Sender pull-down list
Select the required DML type from the DML Type pull-down list
You can choose c (Complete) or p or (Partial).
Specify the year of issue in the Year of Data Issue field
Select the appropriate security class from the Security Classification pull-down list
If you are working with an S1000D 4.1 or 4.2 product, select a BREX data module to associate with the DDN in the Brex Data Module field.
The BREX data module will be listed in the Related Objects table for the DDN.
* 
Some information cannot be edited:
Model Identification Code — populated from the Information Structure
Sequence Number (autogenerated) — set to 00001 for first issue, or first issue in a single Year
The sequence number is incremented when a DML for the same receiver in the same year is added to the same location.
8. Click OK.
A confirmation message is displayed and the DML object is created in the information structure.
Its name is based on information from the creation process:
DML-[Model Identification Code]-[CAGE code of sender]-[DML Type]-[Year of Data Issue]-[Sequence Number]
You can edit the content of the identAndStatusSection section of the DML using Arbortext Editor, if required.
Items to note when creating a DML placeholder object:
Only one DML based on a set of details is permitted in the information structure location. You can add multiple DML if their details differ, for example they are from different senders or have different autogenerated sequence numbers.
A DML object is created under the default wt.series.HarvardSeries.S1000D versioning scheme.
For more information about versioning schemes, see Object Numbering and Versioning.
You can manage the lifecycle of the DML from the information structure. For more information, see Lifecycle of Data Interchange Objects.