Release Bulletin - WebUtilspmat.hec.co.kr/marian_webentry/Pdfs/SPMat Release Bulletin 6.3.8... · Administration ... SP3D - Consistency ... SmartPlant Materials and SmartPlant Reference

SmartPlant Materials and SmartPlant Reference Data Release Bulletin

Version 2008.7 (6.3.8) March 2010 DMAR1-PE-200042F-Updated

Copyright Copyright © 2003-2010 Intergraph Corporation. All Rights Reserved. Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.

U.S. Government Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished - rights reserved under the copyright laws of the United States. Intergraph Corporation P.O. Box 240000 Huntsville, AL 35813 Street address: 170 Graphics Drive, Madison, AL 35758

Terms of Use Use of this software product is subject to the End User License Agreement and Limited Product Warranty ("EULA") delivered with this software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution.

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software or applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this publication is accurate as of its publication date. The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document. The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT. Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.

Trademarks Intergraph, the Intergraph logo, PDS, SmartPlant, SmartMarine, FrameWorks, I-Convert, I-Export, I-Sketch, IntelliShip, INtools, ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are trademarks of their respective owners.

SmartPlant Materials and SmartPlant Reference Data Release Bulletin i

Contents

Introduction ................................................................................................................................................ 1

Highlights of this Release ........................................................................................................................... 2

General ........................................................................................................................................................ 3

New Documentation ............................................................................................................................... 3 Core Workflow Screens ......................................................................................................................... 3

Administration ............................................................................................................................................ 4

Product Documentation .......................................................................................................................... 4 Interface Attributes ................................................................................................................................. 5 Roles ....................................................................................................................................................... 5

SmartPlant Reference Data ....................................................................................................................... 6

Hide Table Detail ................................................................................................................................... 6 S.10.08 Short Codes changes ................................................................................................................. 6 Show all Geometric Tables .................................................................................................................... 7 Create Idents with different Tag Numbers ............................................................................................. 7 Spec Header Description/Short Desc increased ..................................................................................... 7 New option Project and Released........................................................................................................... 7 SP3D - Consistency between Codelist and PartClasses ......................................................................... 8 SP3D - Generic Tables enhancements ................................................................................................... 8 SP3D - Find and Replace in Export process ........................................................................................ 16 SP3D - Codelists .................................................................................................................................. 18 SP3D – PipeNominalDiameters Sheet ................................................................................................. 18 SP3D – Entire Project (Complete Indicator) ........................................................................................ 18 SP3D – Consistency Check/Results ..................................................................................................... 21 SP3D – Load API, GUID load ............................................................................................................. 22 SP3D - Custom Interface, use Attribute more than once ..................................................................... 22 SP3D – PipingCommodityProcurementData changes ......................................................................... 23 SP3D – Short Code Mapping ............................................................................................................... 23 Report enhancements ........................................................................................................................... 23

SPRD Plus ................................................................................................................................................. 25

SPRD Component Manager ................................................................................................................. 25 SPRD Spec Editor ................................................................................................................................ 25

Document linking .......................................................................................................................... 25 Material LOV ................................................................................................................................ 27 Material System ............................................................................................................................. 29 Material Productform Dependencies ............................................................................................. 30 Attach and detach branch tables .................................................................................................... 30

Contents

ii SmartPlant Materials and SmartPlant Reference Data Release Bulletin

Table detail links ........................................................................................................................... 32 Valve Commodity Codes ............................................................................................................... 33 Valve Flanged Components ........................................................................................................... 33 Generate Spec Items CIP ............................................................................................................... 34 Copy Defaults ................................................................................................................................ 34 Thickness Grid changes ................................................................................................................. 34 Further Enhancements ................................................................................................................... 35

Component Management System (CMS) ............................................................................................ 35 Functional Improvements of CMS ................................................................................................ 35 Link Idents to CMS Classes .......................................................................................................... 36 Mapping Attributes for Properties propagated .............................................................................. 36 Select NLS in Multi Article View without re-login ...................................................................... 36 CMS - Re-Classify single or multiple Articles .............................................................................. 37 CMS – Support Mandatory Properties .......................................................................................... 38 CMS – NLS Dependent Attributes ................................................................................................ 38

E&PI (BOM) ............................................................................................................................................. 39

Report enhancements ........................................................................................................................... 39 Manually Lock BOM Node by Issue Status ......................................................................................... 39

E&PI (Requisitions) ................................................................................................................................. 41

Approval Sequence eMail notification ................................................................................................. 41 Requisition Status................................................................................................................................. 41 Report enhancements ........................................................................................................................... 41

MSCM ........................................................................................................................................................ 42

Expediting - Master/Detail Tag changes .............................................................................................. 42 Expediting/Inspection tasks/events ...................................................................................................... 44 Expediting Changes ............................................................................................................................. 44 New CIPs for Shipment Groups ........................................................................................................... 45 Split Tag Issues .................................................................................................................................... 46 Expediter Workload Enhancements ..................................................................................................... 47 Traffic Changes .................................................................................................................................... 47 Contact Phone Number ........................................................................................................................ 49 P.20.01 Qualifications Folder .............................................................................................................. 50 P.20.01 Material/Work Group Folder .................................................................................................. 50 Update of Company Code .................................................................................................................... 50 Submit of Login Request ..................................................................................................................... 51 Resubmittal email for Rejected Company Profile ................................................................................ 51 Uploaded Documents Identifier ........................................................................................................... 52 Revising Qualification resets Approval ............................................................................................... 52 Create Agreement from Inquiry ........................................................................................................... 53 P.30.21 - Addenda Folder changes....................................................................................................... 53 Check of Bidders’ email Address ........................................................................................................ 54 Material Aggregation from multiple Requisition Cycles ..................................................................... 54 PO Approval Issues .............................................................................................................................. 56 Forecast Predicted Pay Dates ............................................................................................................... 57

Contents

SmartPlant Materials and SmartPlant Reference Data Release Bulletin iii

Other Cost Description increased ......................................................................................................... 57 Scope of Work (SOW) Revision .......................................................................................................... 58 CO Summary Box ................................................................................................................................ 58 Agreement Issue Date .......................................................................................................................... 59 Quantity Cancellation ........................................................................................................................... 59 Milestones Auto-populating ................................................................................................................. 59 VDR Expediting ................................................................................................................................... 59 Bid Excel Export/Import Enhancements .............................................................................................. 63

Site .............................................................................................................................................................. 65

Field Material Control .......................................................................................................................... 65 Warehouse to User restricted to Project Users .............................................................................. 65 Actual on Site being populated before posting MRR .................................................................... 65 MRRs limited to Items on Release Note ....................................................................................... 66 Heat Number Change .................................................................................................................... 66 WebService Functions/Procedures for Site APIs .......................................................................... 68

Subcontract Management ..................................................................................................................... 68 Recalculation of Period Actual Hours ........................................................................................... 68 NCR Disposition ............................................................................................................................ 68

Others ........................................................................................................................................................ 69

eSupplier Login .................................................................................................................................... 69 Sort Order of Attached Comments ....................................................................................................... 69 Upload/Open Documents ..................................................................................................................... 69 Repeated Upload of Files ..................................................................................................................... 70

Contents

iv SmartPlant Materials and SmartPlant Reference Data Release Bulletin

SmartPlant Materials and SmartPlant Reference Data Release Bulletin 1

The purpose of this document is to give a technical overview of the major new features of the SmartPlant® Materials and SmartPlant Reference Data 2008.7 (6.3.8) software. The features are also described in the Release Notes delivered with the product. This release of the software contains a number of valuable functions that increase productivity for users. This document presents a list of the major features, grouped by module. This document does not include workflow or end-user information. You can send your documentation comments or suggestions to [email protected].

Introduction

mailto:[email protected]�

Highlights of this Release

2 SmartPlant Materials and SmartPlant Reference Data Release Bulletin

SmartPlant Reference Data SP3D Interface – Generic Table enhancements Enhancements were made to the SmartPlant 3D interface to simplify the handling of generic sheets. SP3D Interface – Consistency Check/Result The new Consistency Check tab was implemented in SP3D.20.01 Export Jobs screen to allow the user to review the results of the consistency check. SPRD Plus Document Linking You can link documents to commodity codes in order to extend the description of the component Material LOV You can use autofilter and other functionality to narrow down the selections in the LOV for material in the Spec Editor. Material System In the Spec Editor you can now select a material system on the General page, and this filters the materials available for selection in the materials grid, the filter line and the filtering defaults. SmartPlant Materials Material Aggregation from multiple Requisition Cycles The material of multiple Requisitions with the same material scope can now be accumulated to on Inquiry. VDR Expediting For the expediting of VDRs the Attachments screen was enhanced, it allows now assigning documents to VDRs. To facilitate the expediting of VDRs, the new screen P.70.81 VDR Submittal and Status was introduced. It provides a flat view of the attachments data of screen D.90.21.

Highlights of this Release

General


New Documentation (B-02827, B-04172) New documents were added to the Printable Guides library:

eSupplier This document describes the eSupplier features of SmartPlant Materials. The eSupplier provides Suppliers and Subcontractors with the capability to get direct access to the SmartPlant Materials application of an EPC or O/O company, for self-registering their company, bidding electronically on quotations, or handling their subcontractor workload. How to add new components for SP3D

This document describes the required actions to add a new component in SmartPlant Reference Data based on the SDB dataset, ready for SmartPlant 3D. The basic requirements are explained and a comprehensive example is given in order to provide a sufficient understanding of the necessary steps.

Core Workflow Screens (CR-MA10042) From now on in the core workflow screens, the only configurations that are available are those which either contain no attributes at all or which only contain attributes that have been created in the project you are currently logged in or that have been created in the product group connected with the project you are logged in.

General

Administration


Product Documentation Enhancements in A.60.70.21 Product Documentation (B-07044) The new list item Document Type was implemented in block Product Documentation of A.60.70.21. The screens A.60.70.01 Service Pack Registry and A.60.63 Valid Settings also show the Document Type.

All former documents in this area are documents attached to a certain Reference Number of a Service Pack. These documents and all future documents, which have information about certain Patches of Service Packs, are from now on of document type Released Documents. The new document type Printable Guides allows you to add a new category of documents in A.60.70.21 Product Documentation. In order to improve information about the product, the documents of the Printable Guides library, currently accessible from SPMat via Help -> Printable Guides, will now be linked with their corresponding modules. If a user is positioned in a screen, he can use the menu button Valid settings to open screen A.60.63 Valid Settings. Within the tab page Product Documentation, all Released Documents with information about any topic connected to that form will be displayed. Each document is directly accessible by double-clicking on the Document Name.

Administration

Administration


A.60.70.01 Service Pack Registry and A.60.63 Valid Settings also show information Document Type.

Interface Attributes A.50.I.02 Interface Attributes (B-04893) It is now possible to use different attribute translations for an interface in different projects/product groups. If the same translation is defined in a project and the product group, the corresponding attribute in the project is selected (if logged into the project). The M_AI_UK_TRANS_IIS unique constraint violation error will not occur anymore.

Roles A.30.03 Roles/Menus (CR-MA10188) When opening the screen, the cursor is now positioned on the role in the first block.

SmartPlant Reference Data


Hide Table Detail (B-04898) The table detail for which the checkbox Disused is checked in the screen S.20.02 Tablenames with Details, will no longer be used in building new Commodity Codes. Commodity Codes that already exist based on this table detail will not be impacted.

S.10.08 Short Codes changes (B-04872 / CR-MA9175) The length of the field Comment in the screen S.10.08 Short Codes: Window 3 is increased to 255. Manual entry of Option Code in the screen S.10.08 Short Codes: Window 3 is now allowed.




Show all Geometric Tables (B-04876) The Geometric Screens S.40.10 - .13 and S.50.20 - .22 usually display only the corresponding geometric tables, such as S.40.10 Standard Geometrics only displays the geometrics of type GEOM_S4010. With the new tickbox ‘Show all geometrics’ you can control if the query will retrieve all geometrics of all types (checked) or just the associated geometries (unchecked). The field ‘Type’ shows the source of the geometric.

Create Idents with different Tag Numbers (CR-MA9940) With this functionality, you can create Idents with the same sizes and same commodity code but with different TAG Numbers. This functionality is applicable only when building rule-based Ident codes from S.50.06 Specification Management. You can create spec item Idents as per the following combinations: Commodity Code / TAG Number / Size1 / Size2 / Ident Code CommCode1 / TAG1 / .5 / .5 / Ident1 CommCode1 / TAG2 / .5 / .5 / Ident2 CommCode1 / / .5 / .5 / Ident3

Spec Header Description/Short Desc increased (CR-MA8653) The length of the Description/Short Desc of table m_spec_header_nls was increased from 60/20 characters to 256 characters.

New option Project and Released (V-ID3704) Corresponding to the already implemented changes in PDS.10.12 Generate and View PMC/PCD, a new selection option (Project and Released (A.20.10)) was implemented in screen I-SKETCH 20.05 Export Jobs Window 2 Block S.50.06 Specification Headers. The background of the Spec Code in this block is light yellow if the SPEC CODE is created in the PRODUCT GROUP.



SP3D - Consistency between Codelist and PartClasses

(B-04871 / CR-MA7953) All export destinations defined in screen SP3D 10.05 Destinations now get a project identifier (PROJ_ID). A migration script is provided in order to fill the PROJ_ID for all existing destinations. It is now possible to export the code list data for the following codelists using table details:

• EndStandard • GeometricIndustryStandard • PressureRating

The user should use the standard sheet config ‘1- CONFIG_V2009’ for this purpose.

SP3D - Generic Tables enhancements (B-04876)

This new feature is currently not available for DIN Wallthickness sheet. If the (new) general configuration item AUTO_SELECT_GENERIC_SHEETS is set to Y generic sheets will be added automatically in case short codes are associated with the spec code/spec items assigned to the generic sheets. The attributes of generic sheets have to be distinguished in commodity attributes, ident forming attributes (input), and other ident attributes (output). For each category a specific functionality was implemented, this is described in detail below.



Commodity Attributes To map Commodity Code properties to specific SP3D attributes/sheet columns, the SP3D Interface table translations must be defined in A.50.I.01 Interface Tables for Commodity Attribute tables, for example:

SP3D Attribute Translation EndPreparation ENDP End Standard ENDS Pressure Rating PRAT

The translation can be extended by a sequential number.

If the property value for End Preparation, End Standard, or Pressure Rating cannot be fetched from the commodity code details because it is stored in an attribute, the SP3D Interface attribute translations must be defined in A.50.I.02 Interface Attributes for the attributes holding these values, for example:

SP3D Attribute Translation EndPreparation ENDP End Standard ENDS Pressure Rating PRAT

The translation can be extended by a sequential number.



Ident Forming Attributes (Input) The values of Ident Attributes, which are used to build the idents and consequently are part of the unique key (defined in SP3D.10.07), will be automatically identified on the basis of the object parameter details as defined in S.10.05 Object Parameter Details.

SP3D Attribute Kind of Detail NominalPipingDiameter 1. /2. Nominal Size Schedule 1. /2. Schedule NominalDiameterUnits Unit of 1. /2. Nominal Size

S.10.08 Short Codes The new window 6 was implemented. Here you can maintain assignments of SP3D generic sheets to the short codes. This can be useful in order to speedup SP3D export process. The LOV for the sheets is restricted to sheets marked as generic.



Other Ident Attributes (Output) The new screen SP3D.10.14 Sheets and Attributes Mapping has been implemented. You can maintain mapping between geometric tables and generic sheets in this screen. In the first block, you can assign a geometric table to one or more SP3D Excel sheets, independent of any sheet config. In the second block, you can see all available sheet configurations. The attribute mapping in the 3rd block will be defined depending on the selected sheet config. The Generate Attributes button can be used for the record generation in the third block. When you click this button, the application will create one record for every available SP3D attribute of the selected sheet. Only the attributes that are not part of the unique key defined on SP3D.10.07 Sheet Configs will be considered, which means only output attributes are considered. If an SP3D attribute is already mapped, it will be not used during record generation. That means existing records will not be overwritten. The Table Attribute field will remain empty; it has to be filled manually using the LOV. When the name of the SP3D attribute matches the name of the table attribute, the application will assign the SP3D attribute to this table attribute automatically.

Only generic sheets can be assigned to the geometric tables, the LOV on Sheet field is

restricted to sheets marked as generic. Miscellaneous SP3D.10.02 Sheets A user-friendly error message is displayed when you try to delete a sheet that is already used in the screen SP3D.10.14 Sheets and Attributes Mapping.



A new check box Generic has been added. The templates for all sheets marked as generic will be created by the new procedure FILL_GENERIC_TEMPLATE_SHEET as described under SP3D.10.13 Create Procedures. Known generic sheets are:

PipingGenericDataBolted PipingGenericDataFemale PipingGenericDataMechanical PlainPipingGenericData BoltExtension

This check box is also implemented in SP3D.10.07 Sheet Configs, SP3D.10.08 Sheet Templates, and in SP3D.20.01 Export Jobs. SP3D.10.03 Attributes A check that SP3D Attribute is already used in the screen SP3D.10.14 Sheets and Attributes Mapping has been implemented. SP3D.10.08 Templates A new tick box Show records with empty mandatory fields in the Data block allows you to filter the displayed data in such a way that only records with empty mandatory fields are displayed. The empty mandatory fields are highlighted with a pink background color, which significantly eases the search for missing mandatory data.

This new feature is available for all types of sheets; it’s not restricted to generic sheets.

A new check box Generic has been added; see comment above under SP3D.10.02.



A new field ‘Modified By’ has been added to the Data block (spec. independent data). The value ‘SP3D1008’ is displayed when the record is created or modified in the screen SP3D.10.08, and the value ‘SP3D2001’ is displayed when the record is created or modified by an export job in the screen SP3d.20.01 Export Jobs. Export jobs will not modify records when the value is ‘SP3D1008’.

SP3D.10.13 Create Procedures The new procedure type PRE_FILL_SHT has been added. A procedure of type PRE_FILL_SHT will run at the PRE_IF_TABS stage of an export job when assigned to the sheet in sheet config.

The procedures of type PRE_FILL_SHT will be started before the FILL_IF_TABS stage and can be used for example, for filling up templates data (SP3D.10.08 Templates). The placeholders &EJ_ID, &TPL_ID and &SHT_ID are replaced with the actual values at runtime. The new standard procedure FILL_GENERIC_TEMPLATE_SHEET has been introduced. This procedure should be assigned to the generic sheets in SP3D.10.07 Sheet Configs screen on folder Attached Procedures in order to use the SP3D Export enhancements. Template data for generic sheets will be prepared by this procedure.



SP3D.10.01 General Configs A new configuration item EXPORT_PRE_IF_TABLES_STOP has been introduced. This item specifies the job behavior when the new stage PRE_ IF_TABS_DONE is reached; it controls whether the export job, having generic sheets assigned, will stop processing. Generic sheets will be created or modified in the templates first. When the template sheet is completed, it will be copied over. The new item can have one of the following values:

• STOP_ERROR • STOP_ALWAYS • STOP_NEVER

STOP_ERROR – The job will stop execution when the stage PRE_ IF_TABS_DONE is reached and only when a data consistency error occurred. An example of such an error would be empty mandatory fields in the SP3D.10.08 Templates. STOP_ALWAYS – The job will stop execution every time the stage PRE_ IF_TABS_DONE is reached. STOP_NEVER – The job will continue execution up to the current job goal without stopping at the stage PRE_ IF_TABS_DONE, even if data errors occur. The new configuration item AUTO_SELECT_GENERIC_SHEETS has been introduced. This item specifies whenever generic sheets will be added to the job automatically. The new item can have one of the following values:

• N • Y

N – Generic sheets will not be added automatically. The user is responsible for adding generic sheets manually or using appropriative transfer type. Y - Generic sheets associated with the short codes assigned to the spec code/spec items will be added automatically. SP3D.20.01 Export Jobs The new job goal PRE_IF_TABS was added. This job goal is now the first goal in the process. Consequentially, the new job stage PRE_IF_TABS_DONE was introduced. It’s now the first stage in job progress.



Acknowledge this message with Yes to open window 5. It will display the generated templates with their status. If the Error check box is checked, it means that data is inconsistent.

Double-clicking on the sheet will open SP3D.10.08 Templates, which displays the generated sheet with its data. Using the option Show records with empty mandatory fields in SP3D.10.08 will help you to quickly find errors in the configuration.



Double-click on the sheet in folder Selected Sheets of SP3D.20.01 Export Jobs will open SP3D.10.08 Templates for all generic sheets. For other sheet categories, a message is displayed. A new Generic check box has been added; see comment above under SP3D.10.02.

Job Validation If the general configuration item AUTO_SELECT_GENERIC_SHEETS is set to Y, generic sheets will be added automatically in the case that short codes are associated with the spec code/spec items assigned to the generic sheets. Validation produces a new log file. The name of the log file is constructed similar to the log files for the job stage with one exception: Instead of the stage name, the text VALIDATE_JOB is used. You will see the log file produced by validation in the tab-folder Logfiles.

SP3D - Find and Replace in Export process (B-04884) The SP3D export process in SPRD does not allow the user to view and change the data that will be exported. This new feature introduces the ‘Find and Replace’ functionality in the SP3D export process wherein the user can view the data that will be exported and can make changes to the data before it is exported. New screen SP3D.10.15 Find and Replace



The purpose of this screen is to allow the user to view and modify the data in the sheet(s) before they are exported. This screen, when called from SP3D 20.01 Export Jobs, shows the user the data from a selected sheet being exported. Here, the user can define certain filters for this sheet to retrieve only the required data on which modifications need to be done. The user can also see the results of every filter after it may be applied. On the filtered data, the specified replacement values replace the actual values. This screen, when called from the menu directly, shows only the related filters and replacement values. The Use in Filter button copies the selected record in the section ‘Data based on Sheet’ as a filter to the block 'Filters'. The Apply Filter button shows the results in the block 'Results' after applying the selected filter to the data in the section ‘Data based on Sheet’. To use this Find & Replace functionality you must tick the checkbox Extended Customization in the SP3D 10.07 Sheet Configs screen for all those sheets whose data needs to be viewed/modified before they are exported.

The new job goal PRE_IF_TABS and the corresponding stage PRE_IF_TABS_DONE were added to the export procedure of SP3D.20.01 Export Jobs screen.

When the export job reaches the job stage PRE_IF_TABS_DONE, double-click on the sheet name at the Selected Sheets tab to call the new screen SP3D 10.15 Find and Replace. This screen is called only for those non-generic sheets which have ‘Extended Customization’ checked as described above. In SP3D.10.15 screen you can add filters and replacement values, using the Use in Filter and Apply Filter buttons, and entering the Replacement value in the ‘Replacement Information’ block as required. When needed, this has to be done for each sheet.



When filters and replacement values are defined for all required sheets, proceed with the export job.

The data is stored into ORACLE global temporary tables in the PRE_IF_TAB_DONE job stage. If the user logs out and closes the SPRD session at this stage, these data will be lost. The user needs to start the job again from PRE_IF_TABS after deleting/cancelling the previous job.

SP3D - Codelists (CR-MA9992) Exported code lists (sheet category CODE_LIST) will be retrieved from the template specified in the new project default ZI_SP3D_CT. If not specified, export takes the template assigned to the job. LOVs and validations in SP3D 10.04/8 will also read the project default first. The Synchronize references feature in SP3D 10.08 will work as follows: If the updated codelist is in the template that was specified in ZI_SP3D_CT, all templates that are in the actual ZI_SP3D_TP or that are attached to a job in the current project will be updated. Additionally, all item mappings of the same project are updated if they use one of the templates mentioned in the previous sentence. Also included is S.10.08 Short Codes; the short code assignment also reads ZI_SP3D_CT first.

SP3D – PipeNominalDiameters Sheet (CR-MA10181) SP3D.40.21 Import Jobs With this functionality, if the Spec Code is > 8 characters, then the Nominal Size table will be the first eight characters of the Spec Code. If a Nominal Size table with the first eight characters of the Spec Code already exists, then the check will be performed appending _1, _2 and so on until an unused name is found for the Nominal Size table. The same holds true for Branch Tables and Filter Geometrics. But in this case, if the Spec Code is > 58 characters, then the name will be the first 58 characters of the Spec Code. Although the Spec Code can be 256 characters, only the first 60 characters of the Spec Code will be stored in the description of Nominal Size Table, Branch Table and Filter Geometric table as this is the maximum capability.

SP3D – Entire Project (Complete Indicator) (SP3D.20.01 Transfer Jobs (B-04873) “Complete” means the export job contains all specifications that are subject to SP3D usage. In other words, the Export job contains all the data that are part of the inventory. The meaning of this flag is that the content or number of Idents of this job is a complete set of Specs and Idents. In other words: Idents that are part of the Job and not part of the inventory need to be exported as NEW Idents not part of the Job but part of the inventory need to be exported as DELETED This new logic can then be applied to all the relevant sheets of the following type:

• PART_DEFINITION



• SPEC_RULE • SPEC_ITEM_FILTER • PART_FILTER

The new config setting EXPORT_SCOPE allows you to define a job as ENTIRE_PROJECT. In this case, running a SP3D export job will cause the system to synchronize the inventory with the definitions in the folders ‘Selected Spec Items’ and ‘Selected Idents’ of SP3D2001. Deleted inventory data will be exported in the Excel sheets with row status D. SP3D.10.01 General Configs

A new Config Item EXPORT SCOPE has been created with the options ENTIRE PROJECT and INDIVIDUAL. ENTIRE_PROJECT has to be activated. SP3D.20.01 Transfer Jobs – Define a new job with the above config assigned.



Running the job will create the PipeStock sheet below.

When the spec changes now, for instance, the size range of the spec item is reduced from 10-48 to 10-36, these removed spec items will be deleted from the Inventory and exported in the Excel sheets with the row status D as shown below.



SP3D – Consistency Check/Results SP3D.20.01 Export Jobs (B-04879) The results of the consistency check will be displayed on the new tab folder ‘Consistency Results’.

Clicking the button Show Results or double-clicking on a record in the consistency results folder opens a second window showing the sheets in the verification results for the selected record.

The display can be restricted to sheets listed in the consistency results by activating the radio button ‘Verification Result’.



In the sheet list, export data for each sheet can be seen by either double-clicking on the selected record or by using the menu associated with the right mouse button.

If the sheet list has been opened by double-click in the tab folder ‘Consistency Results’, the display of the export data is automatically restricted to the detail information (Commodity Code, Ident, Spec Code) listed in the selected record of the ‘Consistency Results’.

SP3D – Load API, GUID load SP3D.20.01 Export Jobs (B-04879) The general setting BULKLOAD_SP3D gets the new option AUTOMATIC_DIRECT. When this option is selected, the export job will start the SP3D bulkload without user interaction and use the SP3D bulkload API, so no workbooks will be generated. The bulkload API is used to be directly fed with the SPRD job data, and to receive the bulkload logfile. This logfile will be loaded and analyzed at job stage ANALYZE_LOG. Depending on the result of the bulkload logfile analysis, the inventory will automatically be synchronized with the SP3D data, because only SPRD data that loaded successfully into SP3D will be stored in the inventory on COMPLETE_JOB stage. That makes sure that the inventory in SPRD is always in sync with the data in SP3D. SPRD will also receive changed GUIDs back from SP3D.

SP3D - Custom Interface, use Attribute more than once

(B-04904) The interfaces and interface attribute mapping data can now be loaded successfully from the SP3D worksheet ‘CustomInterfaces’ into the screen SP3D 10.03 Attributes during the SP3D one-time import.



With this enhancement, two new standard SP3D import conf items have also been introduced, namely BOOLEAN_TRUE, with the default item value ‘TRUE’, and BOOLEAN_FALSE, with the default item value ‘FALSE’.

SP3D – PipingCommodityProcurementData changes (B-04885) The exported Excel for the sheet ‘PipingCommodityProcurementData’ using the SP3D export process will have the sizes and thickness data in the appropriate columns in the exported sheet. The user should either use the standard sheet configuration ‘1ST_CONFIG_V2009’, or a configuration copied from it, which has the changes applied to the sheet ‘PipingCommodityProcurementData’ as per this task. The user should include the part name in the function ‘is_part_1size_only’ within the package M_PCK_SP3D_CUSTOM, if the part is only a one size component like ‘CAP’, for example.

SP3D – Short Code Mapping (B-04885) SP3D Short Codes mapped to SPRD Short Codes at the Product Group level can be re-used at the project level as well.

Report enhancements (CR-MA8653)

S.50.R.01 Spec Types and their Codes

The new parameter MY_COMPANY was added to the report parameter list to allow you to select a company from A.10.23 LOV. If the selected company has a symbol/logo assigned in A.10.23 Companies, this symbol will be printed on the upper right corner of the report.



If in A.20.12 Project Defaults a company is assigned to the project in the Company field of the first block (The Use Company Idents button doesn’t have to be pressed) and the company has a symbol/logo assigned in A.10.23 Companies, this symbol will be printed on the upper left corner of the report.

S.50.R.07 Spec Items with Idents

The new parameter MY_COMPANY was added to the report parameter list to allow you to select a company from A.10.23 LOV. If the selected company has a symbol/logo assigned in A.10.23 Companies, this symbol will be printed on the upper right corner of the report. If in A.20.12 Project Defaults a company is assigned to the project in the Company field of the first block (The Use Company Idents button doesn’t have to be pressed) and the company has a symbol/logo assigned in A.10.23 Companies, this symbol will be printed on the upper left corner of the report. The new parameter Show Company Idents? was added to the report parameter list. If Y is selected, the company idents will be printed. When no company idents are found, standard ident is printed instead. To indicate that a standard ident is shown when the option show company idents is selected, the standard ident will be printed in blue color. The existing Parameter In branch matrix? was modified to allow customers to be more flexible in the output on their report. The parameter affects the matrix output. The known option Abbrev. of part in branch part length allows the user to select an individual long abbreviation of the part code. Together with the parameter Branch part length an individual length selection is possible from 1 to 5 digits. The new options Part or Group/Part will print the Part or the combination of Group/Part regardless of their length in the matrix field of the branch matrix.

SPRD Plus


For more and detailed information about the enhancements of the SPRD Plus application, read the SPRD User's Guide.

SPRD Component Manager

SPRD Spec Editor Document linking

You can link documents to commodity codes or material in order to extend the description of the component. (B-04652) Project setup now includes document classes, numbering, and codes. A new project default, ZX_DOC_CLS, has also been added. This is part of the new document handling functionality. (B-04651, CR-MA10038) You can link documents to data in the following ways: Document number linked to data at the project level Document number linked to a material (table detail) at the specification level (product form) Document number included in a commodity code (for example, a document related to the

object or to the material applied to the object)

Document number at project level This functionality is a custom development, and the standard product only includes a CIP.

Document number linked to a material at specification level You must specify the material document table under Spec Templates/Item/Item Details. This table is used as the source of reference documents on the General page in the Spec Editor.

The main Material grid on the General page in the Spec Editor has a Ref field, which contains the reference document table detail.

SPRD Plus

SPRD Plus


In addition, the main Material grid on the General page has an MPD (Material Productform Dependencies) field. By clicking this button, you can assign details to product forms or link reference documents.

The reference document detail from the main material is included in the generation search criteria for component groups. For pipe component groups, the main material plus the reference document table detail are

included in the generation of commodity codes. For non-pipe component groups, if material product form dependencies exist for a

specification, these dependencies are considered during generation. In addition, if there are any documents defined for the material detail, the software considers these documents while searching for commodity codes.

Document number included in a commodity code In the Tables grids, you can specify whether or not a table is a document table.

The LOV on document tables does not show table details; instead, it shows documents from D.10.11.

When a document is selected from the LOV, if the document is already associated to a table detail, that table detail is re-used. If not, then a table detail is created with that document and is used. The table detail is created based on the information supplied by a CIP named M_PCK_DOC_TYPE_CUSTOM.GET_TABLE_DETAIL_INFO. When the software creates the new table detail, if the table group is not specified, the table detail is created under the table group DOCU_GROUP. If a table group named DOCU_GROUP does not exist, the software creates it. If the table group is specified, the table detail is created under the specified table group.

SPRD Plus


To link document classes to document tables, you go to Project Setup.

When you link a document class to a document table, the LOV on the document table is filtered by the document class to which it is linked.

If the project default ZX_DOC_CLS is set to N, the Document Classes, Document Numbering, and Link Document Classes nodes in Project Setup are opened in read-only mode.

Material LOV You can use AutoFilter and other functionality to narrow down the selections in the LOV for material in the Spec Editor. An example is provided. (B-06927) It is often helpful to restrict the List of Values on the General page so that only certain material is shown, such as piping material. One way to limit the materials shown is to use the first row as an AutoFilter for that column. This behavior is similar to Microsoft Excel.

Example This example shows you how to restrict the main Material LOV on the General page to only pipe material. In the template, open the MATERIAL-ARCHIVES table.

SPRD Plus


In the Component Group column, choose UTMMREST.

In the Component Group, choose Group/Part UTMMREST/PART1.

On S.20.03 Parts with Tablegroups, specify for Group/Part UTMMREST/PART1 and the Table MATERIAL – ARCHIVES a restriction to the table group P_SCS_API.

SPRD Plus


The end result is that the Material LOV is restricted to three entries.

Material System (B-12104) Changes in Material System selection and LOV handling. In the Spec Editor, you can now select a material system on the General page, and this filters the materials available for selection in the materials grid, filter line and filtering defaults. In addition, you can now sequence the tables displayed in the filter line and Coding on the Fly dialog box. When you choose a material system in the Material System box, the software filters the details of the material table in the Material grid. The visibility of the Material System box is controlled by the specification template main material dependency. If the specification template main material is dependent on a material system table, then the Material System box is visible.

Materials If the Material System value is entered in the filter line, the Material table details are filtered depending on this value. This applies to all component groups.

SPRD Plus


For component groups with identifier=M (Piping component group), when you do not enter a value for Material System in the filter line, the Material table is filtered depending on the values entered on the General page for the material system.

Material Productform Dependencies • The dependency between product form and material is now available on the specification

item level, as well as in the filter line area and coding-on-the-fly area (B-05280). • The Add Multiple Material Details and LOV buttons have been added to the toolbar

in the Material Product form Dependencies grid, so you do not have to select an entire row before adding multiple table details (B-05348). You can add multiple material details to a product form by selecting an entire row (click to the left of the grid), right-click the row, and select Add Multiple Material Details.

Or, you can just click Add Multiple Material Details on the toolbar to create a new, blank row. Then, use the LOV to choose a product form for that row. These material table details are used in Filter lines, in Coding on the Fly, and in the results grid or specification items grid on the Component Area page. For example, if you assign ten materials to a product form, all of these materials are included in the search criteria when retrieving commodity codes during the generation of specification items.

Attach and detach branch tables You can now attach and detach branch tables on a specification directly on the Component Area page in the Spec Editor. (B-04622) The branch table functionality has been enhanced. You must select a short code for the branch when creating a branch or attaching a branch. (B-12340) Attach a Branch 1. In the Spec Editor, on the Component Area page, click Open for Edit .

2. Then, click Attach Branches.

The software displays all existing branches created on the product group/project level.

3. Select a branch.

SPRD Plus


The software displays a message asking if you want to use an existing branch, a copy of a branch, or if you want to cancel the process.

Existing branch - If the branch you selected is a project branch, that branch is loaded

in the grid, and you can edit it. If the branch you selected is a product group branch, the branch is loaded in the grid in read-only mode.

Copy of a branch - The software creates a new branch with the name in the format COPY_Branchname, where Branchname is the name of the branch you selected.

When creating a branch or attaching a branch, you must fill in the short code. You can use the LOV, which displays S.10.08 Short Codes. Once the branch is attached to the spec, the short code provided in the Branch Editor is copied into the Spec Header Geometric grid shown on the General page.

4. Click Save . To attach multiple branches to a specification, click New in the Branch Editor. The

Branch Code dropdown box shows all the branches that are attached to the specification.

In addition, you can see the multiple records of table type Branches in the Spec Header Geometric grid on the General page.

Detach a Branch 1. In the Spec Editor, on the Component Area page, click Open for Edit .

2. Then, click Detach Branch. The Attach Branch button becomes the Detach Branch button, and vice versa,

depending on which situation applies. 3. Click Save .

SPRD Plus


Table detail links The View Configuration for Table Detail Link LOV will now be stored by table and not in general. (B-06937) Table detail links are now created for entries on each specification. (B-07823) When you save the details entered on the filtering grids, the software creates the appropriate table detail links on S.20.02.

Example

Project Setup 1. Click SPRD > XS20 Spec > XS2020 Project Setup.

2. Under Filter Group Labeling, assign a master table for a filter group.

3. Under Filter Setup, assign some tables to that filter group, and select Table

Detail Link Ind for the tables where table details links will be created.

Specification 1. In a specification, enter details in the same filter group grid and to the same tables.

SPRD Plus


2. Save the specification. The software creates the table detail link in S.20.02, within the table which is associated with the filter group Area1. The group name is ALL1 by default.

Valve Commodity Codes

The functionality for creating valve commodity codes (using single coding on the fly) has been enhanced. (B-04635, CR-MA-10029)

The title on the Document Code dialog box has been updated. The message text for when you try to use the same tag number and document code

has been updated. If you have an entry on the General page for a filter default, this entry is protected

against modification on the single Coding on the fly dialog box. If you have a filter line entry on the Component Area page, this entry is protected

against modification on the single Coding on the fly dialog box.

Valve Flanged Components Several changes in Project Setup have been made. (B-04634, CR-MA-10050)

The Components > Spec > Spec Setup command has been renamed to Project Setup to more accurately reflect its purpose.

The Table Setup node in the Project Setup tree has been renamed to Filter Setup. This node includes two new columns: Filter Group and Use for TDL Generation.

The Filtering Defaults node is now split up into areas. You can define the filter criteria for each area. Two new columns have been added: Def (Default) and Option.

SPRD Plus


The General page in the Spec Editor now has a Filtering Defaults area with a grid for each area defined in the project setup. The Fitting Rated grid has been removed from the General page.

A new node, Filter Group Labelling, has been added to the Project Setup tree. You can define filter groups for the current project using this node.

Generate Spec Items CIP (B-12339) The software now includes a CIP that you can set to run during the generation of specification items in the Component Area. The new project default ZS_SE_CGL has been added. It has to be set if you want to have the CIP run. If the entry is “None” for this project default, then the software does not run a CIP during generation of spec items. For detailed information about the CIP, read the SPRD Plus User’s Guide.

Copy Defaults (B-12783) The Copy Defaults button on the General page in the Spec Editor has new behavior. When you click Copy Defaults, the software copies the defaults from Project Setup > Filtering Defaults grids. Also, saving a template spec causes the software to copy from the Filtering Defaults grids on the General page into Project Setup > Filtering Grids, based on the Spec to Project behavior.

Thickness Grid changes (B-09280) Changing Thickness Grid when changing anything else. The new project default ZS_TG_MOD has been added. This specifies whether to allow or prevent Thickness grid reconstruction when Diameter Series or Preferred Thickness or Material grid is changed. If set to Y (default), then Thickness grid modification is allowed. If set to N, then Thickness grid modification is not allowed. (B-09279) Do not overwrite Thickness Grid manually. The new project default ZS_TG_MAN has been added. This project default allows or prevents manual editing of the thickness and schedule in the Thickness grid on the General page. If set to Y (default), then manual editing of thickness and schedule in the Thickness grid is allowed. If set to N, then manual editing of thickness and schedule in the Thickness grid is not allowed.

SPRD Plus


Further Enhancements (B-08930) In Spec template creation, except for M Indicator all other Indicators are allowed more than once. (B-09281) Create Idents when multiple Objects assigned. Build Idents is now possible if an object is not associated against the Commodity Code and there are multiple part object parameters. LOV will be displayed wherein the user can choose one to build Idents. (B-04682) Fill Geometric for Result Line. Filling the default Geometric and Sizes from Commodity Geometric Relation is possible now. The project ZS_SP_CCSI controls this behavior. If Geometric is empty and the project default ZS_SP_CCSI is set to ‘Y’, then the Geometric and sizes are filled from the Commodity Geometric relation. Regardless of the project default value, for Template Spec Items during the initial fill the Geometric will be populated from the Commodity Geometric Relation and sizes will not be affected. After the generated Items are saved, then the behavior will be controlled by project default. (B-09282) Wrong Alias during COF Now, if the table is optional, the system will not select automatically the table detail even if there is only one possible match in the Coding On the fly dialog and generation workflow.

(B-08168) A list of database tables used in the SPRD Plus software has been added to the appendix of the SPRD Plus User’s Guide.

A new project default, ZS_UNIT_SI, has been added. This project default specifies the unit for the result lines on the Component Area page.

Component Management System (CMS) Functional Improvements of CMS

(B-04774, B-04775, B-04776, B-04777) A separate User Interface (UI) has been provided to facilitate defining Class Systems. The UI can be called via SPRD Plus main menu, menu item CMS. For the details, read the document SPRD CMS User's Guide.

SPRD Plus


Link Idents to CMS Classes

(B-04779) The classical Idents (M_IDENTS.CMS_IND = ‘N’) can now be linked to the respective CMS Classes automatically during the creation of the Idents. This can be done with the help of the project default ZX_CMSIDMP. If the value of ZX_CMSIDMP is 'Y', then the system determines the Class(es) against which the Idents can be associated and associates with the Class(es). This is done using all the available Common Rules. Please note that the Process Timestamp (of Common Rules) will be considered for determining the association of Ident with Class(es). The functionality is applicable for newly created classical (CMS_IND = ‘N’) Idents only. If the value ZX_CMSIDMP is 'N' or './.', then the Idents are not associated automatically with any Class while getting created.

Mapping Attributes for Properties propagated

(B-13046) The Class Properties has four fields that corresponds to the functionality for mapping classical Idents (CMS_IND=’N’) to CMS Classes. They are the following: • Mapping Type • Mapping Hierarchy • Mapping Table • Mapping Attribute The above mentioned four fields also get copied along with the properties to the child class from parent class when: 1. A new child class is created and all the properties from the parent class are copied to it. 2. A new property is added to the parent class and is automatically propagated to all the child classes.

Select NLS in Multi Article View without re-login

(B-04781) This functionality deals with changing the NLS setting of the application without logging off the application and logging in again. The functionality is provided to allow the user to easily change the NLS while working on the Multi Article View (MAV) grid. After the user is done with one language, he/she can change the language and can continue the work in a different language. The MAV toolbar will have a button with an icon showing the flags of different countries.

SPRD Plus


Upon click of this button, the user is provided with a list of languages supported for logged in Project and Discipline. The user can choose one of them to change the NLS setting. Please note that this will change the NLS for the entire application, not only for the MAV grid. The availability of the toolbar button to change the NLS is controlled through access control rights of the user.

CMS - Re-Classify single or multiple Articles (B-04786) This functionality deals with both: • Additionally classifying the Ident – This means that the Ident is associated to the new Class

without getting disassociated from the existing Class. • Re-classifying the Ident – This means that the Ident is associated to the new Class and

disassociated from the existing Class. An additional popup menu “Re-classify Ident” is provided on the CMS Multi Article View left header. Selecting one or more Idents and clicking this option invokes a dialog with Class System and CMS Class Hierarchy tree. This dialog also has two radio options: • Additionally Classification • Re-classification The user needs to select one or more Classes in the tree. Two buttons are also provided on the dialog – Select and Cancel. If user clicks the Select button, then the Ident(s) will be re-classified or additionally classified depending on the option selected by the user. If the grid is in read-only mode (through the role), this functionality will not be available for the user. Also, this functionality is available only when the grid is in non-edit mode. Note that the classical Idents (M_IDENTS.CMS_IND = ‘N’) cannot be re-classified using this mechanism. (B-07646) This functionality deals with rebuilding the Ident NLS when the Ident is re-classified or additionally classified. For building the Ident NLS, the system now considers only the common properties of the classes with which the Ident is associated. Ident NLS will consist of descriptions of Ident property values for union of the properties of those classes where the Ident is associated. Also, the software considers only those properties whose corresponding ‘Ident NLS’ flag is checked on A.50.01 or A.50.02.

SPRD Plus


An Ident property value may already exist in the database for such properties that are not part of any class where the Ident is associated. Such Ident property values are not considered for building Ident NLS.

CMS – Support Mandatory Properties (B-04786) In the XC1020 Create Global Properties grid, the “Mandatory” field has been added for the user to indicate whether the value for this property is mandatory or not. The default will be unchecked, which means not mandatory. Similar to XC1020, a new column has been added to the Assign Properties grid. The behavioral aspects of the field remain same. A global property that is mandatory by definition can be set to non-mandatory after being assigned to a class. Similarly, a global property that is non-mandatory can be made mandatory for a class after it is assigned to that class. XC20 CMS Component Manager: The Save and Check Grid functions will utilize the mandatory indicator of a property to check whether a value is supplied for an ident for that property. If “MANDATORY_IND” for a property is set to “Y”, and no value is supplied for that property for an Ident, then the system will raise an error. Please note that this check will be done for either modified rows or newly inserted rows only in the grid during edit mode. The Show NLS child window displays values of all NLS-dependent properties of a selected ident in the MAV (Multi Article View). Since property values can be edited in this window, the “MANDATORY_IND” indicator also has an impact here. If an NLS-dependent property has the indicator set to “Y”, then the system will validate and ensure that a value is supplied for that property if an attempt is made in this window to change the value of the property.

CMS – NLS Dependent Attributes (B-07820) The NLS_ID field of table m_ident_prop_val_nls table has been made optional. This allows you to store character values without the NLS_ID indicating that this is NLS-independent. For any attribute of type char having the NLS dependency flag off, the corresponding property value will be stored without NLS and hence there can be only one value for this attribute which is visible all the time regardless of the login NLS.

The sample shows the NLS independent attribute JC with equal value 15 for all languages.

E&PI (BOM)


Report enhancements (CR-MA8653) New Report B.30.R.02.04 BOM MTO/Line. Selection of start node, issue status, and issue level lead to an output showing per list node the list positions with unit, quantity, header (Input_1), branch (Input_22) , client code (company ident), pipe spec (spec), item type (short code), ident description, and the tag number as remark. The parameter MY_COMPANY was added to the report parameter list to allow you to select a company from A.10.23 LOV. If the selected company has a symbol/logo assigned in A.10.23 Companies, this symbol will be printed on the upper right corner of the report. If in A.20.12 Project Defaults, a company is assigned to the project in the Company field of the first block (The Use Company Idents button doesn’t need to be pressed) and the company has a symbol/logo assigned in A.10.23 Companies, this symbol will be printed on the upper left corner of the report.

Manually Lock BOM Node by Issue Status B.40.31 Manually Lock BOM (CR-MA7791/B-04902) A right mouse click on any node in the tree opens the menu with options Lock Selected Node or Lock Sub Tree. Choosing any of these options opens window 2. The new radio group Issue Status allows to select either ‚All’ (current functionality, will lock the node for all Issue Status) or ‘Selected’. When choosing ‘Selected’, you have to select an Issue Status from the LOV. Pressing the button Continue will lock the node for the selected Issue Status only.

E&PI (BOM)

E&PI (BOM)


Super User can unlock (release) nodes which have been locked by other users.

E&PI (Requisitions)


Approval Sequence eMail notification (CR-MA9531) When an item is approved by a member of a sequence of approvers, the system sends an e-mail to the successor within the sequence asking him or her for approval. Previously, a cc of such e-mails was sent to the current approver; however, these cc e-mails have been discarded. Instead, when approving a requisition, a cc e-mail is sent to the originator of that requisition; when approving an inquiry or an agreement, a cc e-mail is sent to its respective buyer.

Requisition Status R.40.11 Requisition Tools (CR-MA9774) If the status of a requisition cannot be changed because of an incomplete requisition setup, this is now stated more clearly so that the user knows which other requisition is involved.

Report enhancements (CR-MA8653) R.30.R.14 List Positions without LI The report R.30.R.02 List Positions without LI was renamed to R.30.R.14 List Positions without LI to get an adequate sort sequence in the R30R menu. New Report R.30.R.03 Requisition / Logo+Companyident This report is a modification of R.30.R.01 Requisition and shows additionally the commodity code in the line items. The parameter MY_COMPANY was added to the report parameter list to allow you to select a company from A.10.23 LOV. If the selected company has a symbol/logo assigned in A.10.23 Companies, this symbol will be printed on the upper right corner of the report. If in A.20.12 Project Defaults, a company is assigned to the project in the Company field of the first block (The Use Company Idents button doesn’t need to be pressed) and the company has a symbol/logo assigned in A.10.23 Companies, this symbol will be printed on the upper left corner of the report. The parameter Show Company Idents? was added to the report parameter list. If Y is selected, the company idents will be printed. When no company idents are found, standard ident is printed instead. To indicate that a standard ident is shown when the option show company idents is selected, the standard ident will be printed in blue color.

E&PI (Requisitions)

MSCM


Expediting - Master/Detail Tag changes P.70.31 Shipment Groups (B-04891/CR-MA4950) The layout of screen P.70.31 Shipment Groups was changed. Instead of the old block 'Item Shipments', the two new blocks 'Item Shipments / Master Tags' and 'Item Shipments Detail Tags' were implemented. In the block 'Item Shipments / Master Tags', you see all item shipments of the order that are assigned to the selected shipment group and that are not detail tags of a master tag. Furthermore, all master tags that do not belong to the shipment group are displayed, but its detail tags belong to the actual shipment group. The block 'Item Shipments Detail Tags' shows all detail tags of the selected master tag in the block above.

P.70.62 Logistics Details/P.70.72 Expediting Details (B-04891/CR-MA6203) Two new project defaults have been introduced to control the behavior of creating and displaying Split Tags. ZP_CLR_DSC

MSCM

MSCM


With this project default (default = 'N'), you can control how the description of the detail tags will be generated when clicking Split Tag or Split Master Tag. If ZP_CLR_DSC is set to 'Y', the description of the new detail tags are generated differently: the first detail tag gets exactly the same description as the master tag itself, and all following detail tags get an empty description (-). When Project Default ZP_CLR_DSC is set to 'N', the descriptions of the detail tags are built as usual. Detail tags get the description of the Master tag with a suffixed sequential number. ZP_HIDE_MT This project default, used in P.70.62 Logistics Details and P.70.72 Expediting Details, enables you to hide the master tags. If ZP_HIDE_MT is set to 'Y', the master tags will not be displayed. Further, the label of the Split Tag button will change to Split Master Tag. If ZP_HIDE_MT is set to 'N', the master tag will be displayed. The Split Tag will only be activated when the cursor is on a master tag record or any other tag that can be split. The detail tags are shown in both cases. The screenshot below shows the result. With ZP_HIDE_MT=Y the master tag is not displayed and the button is labeled Split Master Tag. With ZP_CLR_DSC=Y the Ident short description of a detail tag is not copied from the master tag, but created with ‘-‘.

MSCM


Note: Detail tags are always created by using a sequential number for the position. Thus, it is ensured that detail tags are displayed in the sequence they have been created. To ensure that detail tags are not placed in unexpected shipment groups, it is up to the user to keep the data relevant for the creation of shipment group synchronously. Possibly the setting of project default ZP_COPY_MD should be changed to ‘N’ so that data of another detail tag and NOT of the master tag are taken over when creating additional detail tags.

Expediting/Inspection tasks/events (CR-MA9573) So far the project default ZP_RD_CRIT was used to define the range of days for critical expediting AND inspection tasks/events. This project default has been renamed to ZP_RDCRITE and is now only applied to critical EXPEDITING tasks/events. For critical INSPECTION tasks/events, the new project default ZP_RDCRITI has been created.

Expediting Changes P.70.31 Shipment Groups The actual ship date is no longer overwritten by the predicted ship date (CR-MA8246). P.70.61 Logistics Overview The PO Issue Date now remains the issue date of the original order, even if a change order for that order is issued (CR-MA8265). The screen now issues a requery upon commit (similar to P.70.62 or P.70.31). This is, amongst others, useful to display changes invoked by entering a carrier name (MOC) when working with ZP_POP_ETA = 'POP_MOC', because the effects of populating the MOC's ETA/ATA dates to the predicted/actual traffic arrival dates of the item shipment(s) become immediately visible (CR-MA8246). P.70.61 Logistics Overview, P.70.62 Logistics Details, P.70.31 Shipment Groups, P.70.72 Expediting Details including P.80.51 Traffic Fast: A new project default ZP_CO_TYPE has been introduced that can be used to change the display of the order type. If set to 'N' (which is the default) the type of the original order will be displayed (e. g. 'PO' or 'NC') even if an approved change order exists for that order. If set to 'Y', 'CO' is displayed instead of the original type of the order as soon as the first change order for that order has been approved. (CR-MA8265)

MSCM


The calculation of the predicted-on-site date has been unified. If an item shipment is associated with a means of conveyance (MOC), its predicted-on-site date is calculated as the ATA date of the MOC (or ETA date, if the ATA date is not available) plus the sum of transit days of those entries within the schedule of the item shipment's routing method located between the entries with date types 'Traffic Arrival' (which is included) and 'Arrival On Site' (which is excluded). If the ETA date of the MOC is empty, too, or if the routing method of the item shipment does not contain an entry of date type 'Traffic Arrival', the MOC is ignored, and the system looks for the actual ship date/predicted ship date/revised promised ship date/promised ship date of the item shipment (in this order, if the respective date looked for is empty) and adds the (total) sum of transit days of the routing method in order to calculate the predicted-on-site date. The latter variant also applies in cases where no MOC has been assigned to an item shipment. (CR-MA8249) The field 'Forecasted Delivery Date' in folder 'Item Shipments' in P.70.72 Expediting Details screen is now marked by a cyan background color if it has been entered manually (CR-MA10323). P.70.72 Expediting Details (CR-MA8589). Now all IRCs that have been created for an order are available in folder 'Item Shipments' in field 'IRC Number'. So far there was a limitation to those IRCs the date of which was greater than the order approval date. As this restriction was already removed from folder 'IRC Number' (and turned into a simple warning) it is only consequent to do the same in the item shipments folder.

New CIPs for Shipment Groups P.70.31 Shipment Groups (CR-MA9887/CR-MA7436/B-04894) Some CIPs are now provided for shipment groups and item shipments. All these CIPs are procedures in package m_pck_exp_custom and raise no errors in a standard installation. CIP check_create_sg is executed before shipment groups are actually created when clicking Create SG on screens P.70.31 and P.70.61. If this CIP raises no error, the shipment groups are created. CIP check_delete_sg is executed before shipment groups are actually deleted when clicking Delete SG on screen P.70.31. If this CIP raises no error, the shipment groups are deleted. CIP check_change_sg is executed each time any shipment group related fields (for example, routing method) are modified on an item shipment assigned to a shipment group. If this CIP raises no error, the item shipment can be updated. CIP check_create_ish is executed when pressing button Create Item Shipment in screen P.70.72. Only if this CIP raises no error an additional item shipment can be created.

MSCM


CIP check_split_tag is executed each time a detail tag is created by pressing button Split Tag in screens such as P.50.07 or P.70.72. Only if this CIP raises no error a detail tag is created.

Split Tag Issues P.70.74 Packages (CR-MA10045) The following changes have been applied to screen P.70.74 Packages: If detail tags are created on screen P.70.74, they are now automatically assigned to the MCS, IRC, and/or release note of the master tag and the other detail tags already created respectively. This change has been implemented because detail tags created in this screen shall have no impact on P.70.72. Due to this change, no more action is required by the expediter because the additional item shipments are already assigned to an MCS, IRC, ... Similar to creating detail tags on screen P.70.72, the master tag is now also removed from the MCS, IRC, and/or release note after the detail tags have been created and assigned instead.

If the first detail tags were already created by the buyer or the expediter, you were not able to create additional detail tags on screen P.70.74. So far you had to go to screen P.70.72, create another detail tag, and only then you could assign it to a package. Now you can also create detail tags without the master tag being part of the current package. Depending on whether the current record represents a master or a detail tag, the label of the button is either Split Tag or Split Master Tag. Split Master Tag indicates that you are positioned on a detail tag and will create another detail tag based on the master tag of the selected detail tag.

With the new project default ZP_ISHONCE, you control how many times an item shipment can be placed in packages on screen P.70.74. If the project default is set to 'N' (default), you can assign an item shipment to as many packages as you like as long as its quantity has not been used up. If the project default is set to 'Y', each item shipment can only be assigned to one package. P.70.72 Expediting Details/P.70.74 Packages (CR-MA10274) With the new project default ZP_EXCLTSS, you determine whether detail tags that have been created by traffic or site will be displayed on screen P.70.72 or not. If this project default is set to 'N' (default), all detail tags are displayed regardless of where they have been created. If this project default is set to 'Y', detail tags created by traffic or site are not available on screen P.70.72. Please note that despite its location within the menu tree screen, P.70.74 is regarded as a traffic screen in this context. If you delete a package item that is a detail tag that has been created by traffic on screen P.70.74, you are now asked if you want to delete the detail tag itself as well. So far you could only delete the package item but had to call screen P.70.72 to delete the detail tag itself.

MSCM


In the P.70.74 Packages screen you can now import data with split tags (CR-MA7636). To do so you must use one of the following new Excel templates:

PCK-638.xls (packages without release notes) PCK-RN-638.xls (packages with release notes) PCK-IMP-638-NEW.xls (new data without release notes) PCK-IMP-RN-638-NEW.xls (new data with release notes)

These templates are delivered with this release 2008.7 (6.3.8). For further information see online documentation "Excel Interface for Packages" (DOC_PACKAGES_EXCEL.PDF).

Expediter Workload Enhancements P.70.71 Expediter Workload (CR-MA9214/B-04888) The Populate downwards and Global update options are now available in the Expediter field on screen P.70.71. If a user has the privilege 'MULTI PROJECT', he can now move from one record to the next without the field focus getting lost. So far the cursor was always set in the first displayed field within a row when the user scrolled through the records.

Traffic Changes PT.20.01 Traffic Tree (B-05279) A new concept for calculating traffic totals (weight, volume, freight ton, and transport costs) has been implemented, ensuring that release notes (and, of course, detail data such as packages and unpackaged item shipments) are taken into account only once when calculating totals within the 'Actual' branch of the traffic tree. This also applies to supplements; however, in order to achieve correct results, a few slight modifications had to be applied to the procedure of freezing traffic data (including creation of supplements). For this reason, it is recommended (although not mandatory) to delete existing supplements in the database.

PPL nodes now have a new icon.

A bug has been fixed that prevented users from entering data into the 'B/L or AWB' field for approved release notes in detail window 2 that opens when selecting a 'Workload' node in the tree. Furthermore, the Release Note Number field is colored accordingly now. PT.20.21 Preliminary Packages (B-05279) When entering the gross weight of a preliminary package, this value is now only checked against the net weight specified by the user (previously, it had been checked against both the user-specified and the calculated net weights) P.70.74 Packages (CR-MA9711, CR-MA9838) When clicking 'Delete Obsolete PPLs' (visible only if ZP_PPL_DEL is set to 'N') on the tab folder 'With Release Notes', the user will now be informed in cases where no preliminary

MSCM


packing list (PPL) related to the item shipments on the current release note was found at all, or where at least one PPL was emptied completely and subsequently removed (CR-MA9711). A new field 'Quantity' has been added to tab folder 'Transport Costs' (on tab folder 'With Release Notes'). This field is mandatory when inserting price codes the price base of which is 'Other' (for details, see section 'Modifications to screen PT.10.02 Transport Costs’). The total price of such an attached price code is then calculated as the product of the price per base unit (as defined on PT.10.02) and the quantity specified here (CR-MA9838). PT.10.02 Transport Costs (CR-MA9837) When entering a price code with price base 'Weight', the user can now choose between project defaults ZX_WEIGHT and ZX_TON as the base unit of that price code (CR-MA9837). A new price base 'Other' has been introduced that allows the user to assign any unit that has been defined on A.10.12 Units of Measure as a base unit to a price code (also CR-MA9837). This is useful for handling special types of prices, for example, per km, per container, or demurrage (per hour, per day, and so forth). PT.20.11 Means of Conveyance (CR-MA9838, CR-MA9836) A new field 'Quantity' has been added to tab folder 'Transport Costs'. This field is mandatory when inserting price codes the price base of which is 'Other' (for details, see section 'Modifications to screen PT.10.02 Transport Codes'). The total price of such an attached price code is then calculated as the product of the price per base unit (as defined on PT.10.02) and the quantity specified here (CR-MA9838). Furthermore, a new field 'Release Note/Package Number' has been added to tab folder 'Transport Costs'. This field displays the release note or package number to which the current price code has been attached. If it is attached to the means of conveyance itself, this field remains empty (CR-MA9836). PT.20.21 Preliminary Packages (CR-MA9706, CR-MA9707 CR-MA9709, CR-MA9712 CR-MA9838) A new (optional) field 'Collection Point' has been added to block 'Preliminary Packing Lists' (CR-MA9706).

Field 'Freight Ton' in block 'Preliminary Packages' has been renamed to 'Total Freight Ton', which describes the value calculated more precisely (CR-MA9707).

The multi-selection LOVs for item shipments and requisition line items that are opened by pressing F9 on field 'Pos' on tab folder 'Preliminary Package Items' have been enhanced by a field containing the ident description (CR-MA9709).

If the volume of a preliminary package is entered directly (that is, instead of specifying x, y, and z dimension of the preliminary package for calculating the volume), the package is considered as a lot (as is customary when dealing with bulk material), and the coloring rules for oversized/exceptional packages do not apply (CR-MA9712).

Item shipments that have been placed on a release note already are no longer available for preliminary packing. As a consequence, an order the item shipments of which are all associated with a release note will no longer appear in the 'Orders' block. This feature implements CR-

MSCM


MA9842; however, the restrictions applied to item shipments are even more severe, thus preventing item shipments from appearing twice in the traffic tree (PT.20.01) – the first time below a PPL and the second time below a release note.

A new field 'Quantity' has been added to tab folder 'Transport Costs'. This field is mandatory when inserting price codes the price base of which is 'Other' (for details, see section 'Modifications to screen PT.10.02 Transport Codes'). The total price of such an attached price code is then calculated as the product of the price per base unit (as defined on PT.10.02) and the quantity specified here (CR-MA9838).

New screen PT.20.22 Preliminary Packing Delta (CR-MA9833) This screen has been designed in order to facilitate the detection of orders/preliminary packing lists that have undergone changes as compared with related expediting data. In detail, the screen displays all item shipments (together with the corresponding order and, if existing, preliminary packing list and preliminary package) for which at least one of the traffic group-by criteria (that is, forecasted delivery date, delivery designation, routing method, incoterm, and delivery place) differs from the corresponding information stored at PPL level (if any). All differing PPL-related fields are marked with a red background color; by double-clicking on one of them, you are immediately directed to PT.20.21 Preliminary Packages where you can rearrange the preliminary packing.

Contact Phone Number P.20.01 Suppliers/Subcontractors (B-04892 / CR-MA8371) The LOV on the field First Name on screen P.20.01 now shows the Phone Number in addition to the first name and last name. When selecting a contact from the LOV, the new Phone Number field in P.20.01 will automatically be populated with the selected value.

MSCM


P.20.01 Qualifications Folder P.20.01 Suppliers/Subcontractors (CR-MA10178) The two qualifications folders in screen P.20.01 now have different labels to distinguish them and to be able to use different labels using the glossary functionality. The Qualifications folder is used to assign qualifications to a supplier, selected from P.10.21 Qualifications. The Qualification Questions folder is used when working with eSupplier self-registration via P.20.03 Questionnaire.

P.20.01 Material/Work Group Folder P.20.01 Suppliers/Subcontractors (CR-MA8729) The values of the 'Classification' drop-down list field on the 'Material/Work Groups' tab folder in Window 2 are now subject to translation. Thus, they can be relabeled using the glossary functionality.

Update of Company Code P.20.02 Login Requests (CR-MA10036)

MSCM


When updating the company code in either screen A.10.23 Companies or P.20.02 Login Requests, a dialog box appears prompting the user for choosing supplier codes related to this company that should be updated accordingly. If there is only one supplier entry related to the company, the new supplier code proposed by either screen is now identical to the modified company code. Otherwise, the proposed supplier codes are generated as before, that is, by adding a consecutive three-digit number to the modified company code.

However, when updating a company code via P.20.02 Login Requests, this dialog box will no longer show up in cases where the screen has been called via eSupplier login; instead, a silent update to related supplier codes will be performed.

Submit of Login Request P.20.02 Login Requests (CR-MA10066) Submission of login requests sets field SUBMIT_DATE in table m_login_requests.

Resubmittal email for Rejected Company Profile P.20.03 Questionnaire (B-08417 / CR-MA10000) Submission of a new revision for company profile or qualification will now send an email to all users in the respective approval sequence informing them that the company profile/qualification has been updated. The text for the company information (name, address) is created by the CIP m_pck_company_custom.login_request_information_text (as is the case for the email when submitting the initial revision). For qualifications with multiple approval templates, no emails will be sent (this functionality remains unchanged).

MSCM


Uploaded Documents Identifier P.20.03 Questionnaire (CR-MA9791) A new check box labeled Document Attached has been added to the 'Answers' block on window 2, next to the Document Rqd indicator. This check box is selected if at least one document has been uploaded with respect to the question currently selected. The user does not have to click the Upload Files button and move to Window 6 to check whether documents were already attached to the question.

Revising Qualification resets Approval P.20.03 Questionnaire (CR-MA10202) After submission of the revised 'Qualifications' part of the questionnaire, associated approval sequences are now properly reset and email is sent to the first approver to re-approve. It should be noted, however, that this only applies to approval sequences related to questions the answers of which differ between revisions (in cases where an approval template has been specified for several 'Qualifications'-related questions per company type on P.10.25 Question List). In short:

• one single 'Qualifications'-related approval template defined on P.10.25 => approval sequence is reset

• multiple 'Qualifications'-related approval templates defined on P.10.25 => only sequences associated to answers that have been changed with the revision are reset.

Submit of a Qualifications revision resets the assigned approval sequence(s) and clears the ‘Accepted Date’ and ‘Accepted By’ fields on Qualification Questions tab of P.20.01.

MSCM


Create Agreement from Inquiry P.30.01 Requisition Workload (CR-MA9760) Using the Two Requisition Method, when creating an agreement from an inquiry in screen P.30.01, you now have the option of determining the type of the new agreement. So far the type was taken over from the inquiry with the user having no chance to change this value. After choosing ‘Create from Inquiry’ in the Agreement Cycle window, a new window 6 pops up where you can assign the type of the new Agreement.

After selecting the Agreement type from the list, click Continue to create the Agreement with the selected type.

P.30.21 - Addenda Folder changes Addenda Approval (CR-MA9771) Now you can approve an addendum in folder 'Addenda' directly by selecting the Approved check box, when no approval sequence was entered. If the approval sequence is filled, the check box cannot be selected.

MSCM


Email prompt from Addenda RFA (CR-MA9758) When submitting an addendum for approval by selecting ‘Ready for Approval’, you will be asked ‘Do you want to send an email to the approver?’. Acknowledging with Yes will send an email to the first approver of the approval sequence. When issuing an approved addendum with the Issue button, you will be asked ‘Do you want to send email to the bidders?’, and after sending the email(s), the message ‘Email(s) successfully sent out’ appears. The new project default ZP_EMT_AI is used to assign an email template for sending emails to the bidders after issuing an addendum. First, define an email template of template type ADDENDUM ISSUE on A.10.51 Email Templates for issuing an addendum. Then, assign this template to the project default ZP_EMT_AI. For further information, read the online help of A.10.51 Email Templates. Addenda Folder available for all inquiry types (CR-MA10132) The folder 'Addenda' is now available on screen P.30.21 for all types of inquiries. Depending on the new project default ZP_ADD_RQD, at least one addendum is required for the approval of inquiry supplements > 0. If this project default is set to 'Y', an inquiry supplement > 0 can only be approved if at least one addendum has been entered. If this project default is set to 'N' (default), no addendum is required for supplements > 0.

Check of Bidders’ email Address P.30.21 Prepare RFQ (CR-MA10314) The validity of bidders' e-mail addresses is now only checked on screen P.30.21 if the project default ZP_EN_ACT has been set to 'Y'.

Material Aggregation from multiple Requisition Cycles P.30.25 Awarding/P.30.27 Bidder Quotation (CR-MA9549) In case you need to create different Requisitions with the same material scope, the material of these requisitions can now be accumulated on one Inquiry. The Summarize Line Items check box on screen P.30.21 Prepare RFQ now does not only summarize identical requisition line items originating from different supplements of the same requisition but just checks in general if identical material can be found. Material is regarded as being identical if the ident code, tag number, unit of the released quantity, group-by, and summary attributes of the MTO are the same. The screenshots below show an example of an Inquiry with three requisitions assigned, with partly the same material on the line items.

MSCM


With the Summarize Line Items check box selected, it would result in a quote with these summarized details:

The comment ‘n DIFFERENT’ in the Engineering Requisition field indicates that the quantity of that item was summarized from different Requisitions. Double-clicking on Quoted Quantity shows the Req line items with their quantities.

MSCM


PO Approval Issues P.50.07 Maintain Agreements (CR-MA9957) If the setting of the Ready for Approval check box on screen P.50.07 is not allowed because of the result of CIP m_pck_po_custom.check_rfa, the check box is now reset automatically.

When acknowledging the message with OK, the check box is cleared P.50.07 Maintain Agreements (CR-MA9958) When clicking the Approval button on screen P.50.07, the error message that is returned by CIP m_pck_po_custom.agreement_approval is now displayed.

P.50.07 Maintain Agreements (CR-MA9959) Instead of locking down the approval sequence, two additional project defaults are now available: ZP_APRPO and ZP_APRSM. With these project defaults, you define the default approval template used for the approval of purchasing agreements (ZP_APRPO) and subcontract agreements (ZP_APRSM). The approval template is used to populate the approval sequence when setting the Ready for Approval check box on screen P.50.07, folder 'Agreement'. Furthermore, the first person in the approval sequence will be informed by email that the agreement is ready for approval.

MSCM


The approval sequence is automatically populated by the approval template that is assigned to ZP_APRPO.

If the project default is not set, you get a warning to prevent the Ready for Approval check box from being set before the approval sequence has been set up. For users who do not want to use this feature and want to approve an agreement by just clicking the approval button on screen P.50.07, the option exists to suppress this message.

Forecast Predicted Pay Dates (CR-MA9115) The predicted payment date of progress payment events (screen P.50.07) is now kept for change orders.

Other Cost Description increased (CR-MA9300) The length of the description field for other costs and attached other costs has been increased to 255 characters (m_other_cost_nls.description, m_used_other_cost_nls.description).

MSCM


Scope of Work (SOW) Revision P.50.07 Maintain Agreements (CR-MA9752) If you have generated a new supplement of an agreement on P.50.07 Maintain Agreements, the SOWs from the previous supplement will be taken over to the new supplement but cannot be updated on the new supplement. If you want to change the SOW of the new supplement, you must create a new revision of the SOW in the folder 'Scope of Work', using the Revision button.

CO Summary Box P.50.07 Maintain Agreements (CR-MA9756) When creating change orders, the contents of the field 'CO Summary' are no longer taken over from the previous supplement; the field remains empty.

When adding a COR to a change order manually on screen P.50.07, the CO summary is now filled in all cases and not only when it is not empty.

MSCM


Agreement Issue Date P.50.07 Maintain Agreements (CR-MA10235) When the date of the technical evaluation is checked when setting the issue date of an agreement, the date entered on the agreement itself is now also taken into account. This means that for agreements based on a quote and for which the Pass TE button has been clicked, the issue date can be set although the technical evaluation for the quote might not be complete. So far you got the message MAR-30805 (Technical evaluation is not yet completed.) and were not able to set the issue date.

Quantity Cancellation P.50.07 Maintain Agreements (CR-MA9550/B-04888) So far in screen P.50.07 you could already add requisitions with negative quantities to an agreement. But if the quantities available on the agreement were not sufficient for the cancelled quantities, the processing stopped and the requisition was not processed at all. Now all cancelled quantities that can be satisfied by the agreement are taken into account so that only the remaining lines still have to be processed (P.30.01 -> Agreement Cycle -> Create Supplement -> P.30.04). If this occurs, a corresponding message is raised to inform the user that the requisition is not purchased completely. Please note that you can also use screen R.30.14 (R.30.11 -> Outstanding Lines button) to see the positions with outstanding quantities.

Milestones Auto-populating P.60.03 Requisitions Planning (CR-MA9749) For newly created planned requisitions, the milestones will now show up automatically when double-clicking the Engineering Requisition field and switching to the Milestone Planning tab folder (as was already the case with existing planned requisitions).

VDR Expediting (B-04908)

MSCM


For the expediting of VDRs, screen D.90.21 Attachments has been enhanced. Now you can assign documents to VDRs. So far you could only assign either documents or VDRs directly to a business object such as a requisition, inquiry, or agreement. Now you can attach the VDRs in a first step and later on in the course of the project when you receive the document(s) from the supplier that satisfy these VDRs you can assign them to the matching VDR.

The new radio group Only Documents / Include VDR Documents was implemented at the top of the Documents block.

With this radio group, you can specify whether data that have been entered in folder 'Documents' are to be displayed independently from the data in folder 'VDRs' or not. Per default (Only Documents), data are shown independently from each other, that is, if you have assigned a document to an object and a VDR to that document, you will NOT see this VDR if you go to folder 'VDRs'. Vice versa, if you have assigned a VDR to an object and a document to that VDR, you will NOT see this document here in folder 'Documents'. If you select option Include VDR Documents, both folders are covered when displaying the data, that is, if a document has been assigned to an object and a VDR to that document, you will see this VDR also in folder 'VDRs'. Again vice versa, you will see a document that has been assigned to a VDR also in folder 'Documents'.

MSCM


Please note that in mode Include VDR Documents, inserts are not supported. Please switch back to the default display option Only Documents for doing so. The cyan background color of the Document field indicates that VDRs are attached to this document/package. The Include Document VDRs display option will additionally display the documents attached to VDRs on the VDR folder; these documents are marked with a magenta background color. The new radio group Only VDRs / Include Document VDRs was implemented at the top of the VDRs block.

With this radio group you can determine whether data that have been entered in folder 'VDRs' are to be displayed independently from the data in folder 'Documents' or not. Per default (Only VDRs) data are shown independently from each other. I.e. if you have assigned a document to an object and a VDR to that document you will NOT see this VDR if you go to folder 'VDRs'. Vice versa if you have assigned a VDR to an object and a document to that VDR you will NOT see this document in folder 'Documents'. If you select option Include Document VDRs both folders are covered when displaying the data. I.e. if a document has been assigned to an object and a VDR to that document you will see this VDR also in folder 'VDRs'. Again vice versa you will see a document that has been assigned to a VDR also in folder 'Documents'. Please note that in mode Include Document VDRs inserts are not supported. Please switch back to the default display option Only VDRs for doing so. The cyan background color of the VDR field indicates that documents are attached to this VDR. The Include Document VDRs display option will additionally display the VDRs attached to Documents on the Documents folder, these VDRs are marked with magenta background color. Furthermore, the new screen P.70.81 VDR Submittal and Status has been implemented. It is a flat view of the data that are maintained on screen D.90.21 Attachments. The purpose of this screen is the expediting of VDRs. It was designed as a CWS (Core Workflow Screen) with all known features.

MSCM


You can query for all agreements and agreement line items to which VDRs have been assigned and that have been approved. If privilege 'MULTI PROJECT' has been granted to you, you can see the data of all projects to which you have access. If you do not have this privilege, you can only query for and work on data that have been created in the project to which you have logged on. You can use this screen to assign one or more documents to a VDR, to create document revisions, or to transmit the VDRs. Please keep in mind that any changes applied to document-related fields on this screen affect the base data on screen D.10.11. Some features on this screen are handled by CIPs. More details can be found in the description on the block or item level depending on the purpose of the CIPs. Please see the help file provided for this screen for full details. The Duplicate VDR button can be used to copy a VDR record to attach a further document. The Revise Document button opens window 4 to create a new revision of the selected document.

MSCM


Bid Excel Export/Import Enhancements (B-08644) P.30.24 Download/Load Bids The Bid Excel Export/Import can now handle attributes defined in configs for quote and quote details by using the new template BID_template63_enh.xls.

The sample above shows the user-defined attributes Cable_Type, Component Family and Production Date, and the CIP Company Name. These values will be exported with the new BID template.

Also the attributes and CIPs defined on Quote Detail level will be exported; further the Ident Long Description can now be exported.

MSCM


The existing templates BID_template63_std.xls and BID_template63_comp.xls can still be used. A default Template for Bid export can be assigned using the new project default ZP_TP_BID. The used templates have to be defined in A.30.05 Parameter for parameter ZP_TP_BID. For the details read document DOC_BID_EXPORT.pdf.

Site


Field Material Control

Warehouse to User restricted to Project Users C.10.03 Warehouses to User (CR-MA10244) We have changed the LOV and the query condition for the user field on screen C.10.03 Warehouses to User. Now only users who have an active user security entry for the project are available.

Actual on Site being populated before posting MRR (B-04889) Expediters usually do not have access to the Site screens. Moreover, the MRRs are often posted days or weeks after the material was actually received on Site. Thus, it was requested to populate the Actual on Site in Expediting module already when the receiving date is set or updated in the Material receiving screens. To control the behavior of the population of Actual on Site date, the new project default ZC_AOS_DAT was introduced. If the project default is set to 'N' (default), the actual on site date on logistics screen (m_item_ships.actual_on_site_date) is updated when an MRR is posted. This is the existing functionality. If the project default is set to 'Y', the actual on site date on logistics screen is updated when the Material Receiving Date is set or changed at Inventory receipts on receiving screens.

Site

Site


MRRs limited to Items on Release Note C.20.01 Prepare MRR by PO (B-04900) The new check box ‘Only Release Note shipments’ was implemented on C.20.01. If this check box is ticked, only shipments of the entered Order that are also assigned to an approved Release Note will be populated .

With the ‘Only Release Note shipments’ check box ticked, Populate Order copies only the order line items that are assigned to approved Release Notes to the Inventory Receipts block , as shown on the screenshots above.

Heat Number Change C.20.21 MIR by Reservation (B-04903) The location-change logic was inserted into screen C.20.21 MIR by Reservation to issue Heat Numbers as required. A Location change is only possible if the MIR is not posted. The issue type of the report must be regular.

Site


A right mouse-click on the Ident Code field in the Inventory Issues block shows the popup menu Location Change. Clicking that item opens a window displaying all items that fulfill these requirements:

• On hand quantity > 0 • Item is not yet placed on the current MIR • Ident, Unit, Tag number must be identical with the original item • The location of the item may not be quarantined (marked as quarantine) • The Warehouse of the item must be assigned to the user • The Warehouse of the item must be assigned to the Reservation Run

Now mark the relevant items with the Sel check box and click Fill in to create a new record with issue qty = 0 at the current issue report.

Updating the Issued Quantity and then posting the MIR will finally replace/change the reserved material.

Please note that a location change reserves material in addition to the reservation run. This material will be released after posting the MIR.

Site


WebService Functions/Procedures for Site APIs (B-04906)

Created functions/procedures which can be called via WebService for Site Api. The functions and procedures are listed in HandleSite. The file B-04906.xlsx provides a list of the WebService Functions (HandleSite) for Site Api (M_WRAPPER_API_SITE).

Subcontract Management Recalculation of Period Actual Hours

SM.20.11 Subcontract Administration (CR-MA9907) Folder SOV Progress, Period Progress Number Details, Window 10. The value of actual hours is not affected anymore by changing the period completion percent. Folder Closeout Items You cannot modify data created in the project that is not the same as the project you are logged into.

NCR Disposition SM.30.07 Non Conformance Reports (CR-MA9757) Window 2, folders NCR Details and NCR Disposition The Contractor can modify NCR details and dispositions when screen SM.30.07 is called from the screen SM.30.09 Notice to Comply. In the previous version of the screen, the data was read-only. SM.30.09 Notice to Comply When the Contractor calls up SM.30.07 Non Conformance Reports, he is able to modify NCR data the same way as it can be done when calling SM.30.07 from the Menu.

Others


eSupplier Login (CR-MA10086) Using the eSupplier Login, these main menu items will not be available:

• Change Login • Where Condition • Ident Attributes • Preferences • Customer Menu • Printable Guides • Report Document Library • Subscribe to News • Universal Dialog

Sort Order of Attached Comments D.50.21 Attached Comments (CR-MA5752) The D.50.21 Attached Comments screen might be used to add various comments to all kind of information. Until now, these comments were sorted by their ORDER SEQ in ascending order. A new radio button on the D.50.21 screen allows you to switch from ascending to descending order.

Upload/Open Documents (CR-MA9987) With the new project default ZX_DOC_CIP, you control whether the standard code is used on screens D.10.11 and D.90.21 when using the Upload and Open buttons, or if the CIP code is to be used. Per default the standard code is used. If you want to use the CIP functionality, you must modify the CIPs upload_document and open_document in the library mar_custom.

Others

Others


When working with the CIP feature and upload_document, table m_used_files is used to store the file to be uploaded intermittently. It is then up to the CIP to write this file to whatever directory, share, or whatever is applicable. Field STATUS_CODE is available on table m_used_files to store the success or the failure of the upload. It is a numeric field. If it contains the value 0, this means a successful upload and fields 'Source Path' and 'File Name' are set. If any value other than 0 is returned, these fields will be empty. Regardless of whether the upload was successful or not, the message that is returned by the CIP will be displayed. It is up to you to decide if you want to delete the record in m_used_files after a successful upload. The standard feature does not need this record to work. When working with the CIP feature and open_document, a message will only be displayed to the user if the CIP returns a value.

Repeated Upload of Files D.10.11 Documents / D.90.21 Attachments (CR-MA9828) If the file that you want to upload on screen D.10.11 or D.90.21 already exists in the destination, a message now comes up to ask the user whether he wants to overwrite the existing file or not.