It is recommended to use a project specific specification type for the project specs. The advantage is that the standard specs do not interfere with the list of project specs.
You can also create new commodity codes from an existing piping class. For more information, see "Create New Commodity Codes from the Piping Class" in the How to Create Standard Piping Classes guide.
The spec type has to be created in S.50.02 Specification Types. It is very important that the spec type structures in this screen are filled with those spec types contained in the master specs. In this example "PROJECT_BP."
The copy job is started in screen S.50.05 Specification Copy.
After selection of the spec type, the first block allows you to create a new specification code that can be filled by the copy job. The first block can also be used to query for an existing spec which that can be updated or added by the copy job. Save the record in the first block before switching to the second block.
The second block allows selection of a source specification. The content of the source identified in the second block is copied into the spec identified in the first block.
As mentioned above, the second block is defining the source specification. Copy actions for individual items of the spec can be changed using the drop down lists for each field.
If a destination spec is empty, only the insert is possible and will be done if ‘both’ is selected.
The field "Comm Code" shown in Picture 3 does NOT control copy actions for the commodity codes of the spec items! It only copies spec item details used for the specification dependent commodity code creation. The use of this functionality is not part of this document.
The copy function is started by commodity code of the actual record. After copy is complete, the record is saved and can be queried. To start the copy job again, an update in the second block is necessary: for example, any character is inserted into the "comment" field and saved.