Version 2011 SP1 (7.0.1) Release Notesspmat.hec.co.kr/marian_webentry/Pdfs/701SP01_RelNotes.pdf100917 10978 11006 11155 11250 11280 11283 Bug Fix Bug Fix Bug Fix Bug Fix Bug Fix Change

SmartPlant MaterialsRelease Notes Service Pack 127-SEP-2010 Release

®

2011 (7.0.1)

1Page of

SmartPlant Materials® 2011 (7.0.1)

1 Release Notes Service Pack 56

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 properauthorization.

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 accordancewith 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 CorporationHuntsville, Alabama 35894-0001

Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment ofsuch 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.

Trademarks

Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools, MARIAN, PDS, and IntelliShip are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. Other brands and product names are trademarks of their respective owners.

Copyright 1988 - 2010, Intergraph Corporation. All Rights ReservedCopyright

2Page of



Release Notes Service Pack Version:1 7.0.1

MSC-No. Type Comment

100917

10978

11006

11155

11250

11280

11283

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

Bug Fix

Login ScreenFixed issue that user cannot login to the system when project default ZX_THEME uses color set which does not exist anymore in the screen A.30.15 Themes.

A.30.15 ThemesColor set cannot be deleted when assigned to the project default ZX_THEME.

When A2012 alone is copied, project defaults are copied.When A2012 and A2013 are copied, project defaults are not copied.

This problem is now solved.

revise LOV for project to only assigned projects.

Screen A200102 has been revised to correctly update and display field 'Default Nls'.

Changes of indicator API IND at Screen A.20.16.02 are now saved to database.

Lov on User group disciplines sorted alphabetically, block user group disciplines sorted, field user set to uppercase only.

Label of User ID set to User. Help text MARIAN User replaced with User.

when querying the menu items A2049 or A6071, and then

Cust.Ref.No.

GPU100917

TR-MA10978

TR-MA11006

TR-MA11155

TR-MA11250

CR-MA11280

TR-MA11283

Administration

A3015

A2012

A2013

A200602

A200102

A2015

A2041

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

3Page of




11303

11303_1

11336

11467

11468

11490

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

selecting the CIPs tab, the error message 'ORA-06502: numeric or value error ORA-01403 no data found' occured.

This has been resolved.

blockwidth of LOV for field: BLOCK NAME of Block APPLICATION ROLE MENU BLOCKS (Window2) was overworked to show appropriate width.

5 LOV’s, we have been additional sorted.

The setting of ZX_ORIGIN cannot be changed any longer once a requisition has been created via MTO job. This restriction is necessary to avoid that new requisition cyclesare opened when running further MTO jobs because the origin is part of the unique key of an engineering requisition.Whether you are allowed to change the setting on discipline level after the first run of an MTO job depends on the discipline. If no MTO requisitions exist within a discipline the value can still be set or changed on disciplinelevel although MTO requisitions exist in other disciplines.

An error message does not come any longer when openingthe window for entering valid values for an attribute in screen A.50.01.

Cursors in Package M_PCK_VERSION_CONTROL have been revised to take only data of SPMat schemas in account.

‘Module’ field on window 1 of A6007 will show the value ‘*’ only if no modules are assigned on window2.Otherwise the list of the assigned modules will be displayed.Changes on window 2 will be reflected on window1 after thecommit.

TR-MA11303

TR-MA11303

TR-MA11336

TR-MA11467

TR-MA11468

TR-MA11490

cont'dAdministration

A3006

A3003

A3003

A3005

A5001

A607013

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

4Page of




11496

11529

11530

11537

11590

11638

Bug Fix

Change Request

Bug Fix

Bug Fix

Change Request

Bug Fix

Script to delete the wrong entries was created.In A.60.06 as well as in A.60.05 helptext with the old product name MARIAN were deleted

- New option ‚Every 15 minutes‘ for Interval (in A.60.10 and A.60.45)

- New option ‘CURRENT’for Mail Content will include NEW and UNCHANGED alert messages into the mail.

The ‚Copy Attributes‘ button is now only enabled if the table is defined in the current login project, it is a geometrictable and the form is not in ‘Enter-Query’ mode.

The LOV on the project field when copying privileges in screen A.20.06.02 is now restricted to the projects to that the selected user has access. So far all projects were listed.

Instead of message 'LOV creation failed' the user will now see the message 'List of values contains no entries' when trying to enter a value for an attribute for that a 'Derived From' clause has been set up in screen A.50.01 if this clause (or better SELECT) does not find any records.

Generation of reports now also takes the login user ID into account in cases where the user is actually working within the e-Supplier environment.

Technical background: When logging on to SmartPlant Materials via Supplier Entry, the login information provided (user name and password) must match a record from A.10.23 Companies, tab folder 'Contacts' (block

TR-MA11496

CR-11529

TR-MA11530

TR-MA11537

CR-MA11590

TR-MA11638


A6007

A6005

A6006

A6010

A6045

A5003

A200602

A5021

D9021

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

5Page of




11648

11778

11846

25648

Bug Fix

Bug Fix

Bug Fix

Change Request

'Employees'), or P.20.02 Login Requests (block 'Contact Details'). However, after successful authentication this username is not used as SmartPlant Materials session user because it is not available in A.20.05 User; instead, a system-internal user is used. However, in order to be able to distinguish report runs and user parameter settings between different supplier logins, the user name used for logging on has been added to database tables 'm_appl_runs' and 'm_appl_user_parms' (column name 'client_user_id'), in addition to the session user column 'm_usr_id'. Column 'client_user_id' is filled if and only if column 'm_usr_id' is set to 'RMTE_COMP' or 'RMTE_SPLR'.

This may be of interest in cases where user-created reports retrieve information from the database tables mentioned above.

The visual attribute of the buttons in window 6 has been corrected.

Correction of LOV on physical attribute for tables of type ‘PHYSICAL’

A.60.63 Valid Settings Fixed internal problem concerning presentation.

A.10.23 Companies

This screen now has CWS functionality that enables amongst others adding attributes and CIP fields.The fastcalls are substituted as follows:

A.10.22 – Doubleclick on ‘Company Type’ in Window 2 folder ‘Company Types’A.10.25 – Doubleclick on ‘Address Type’ in Window 2 folder ‘Addresses’A.10.26 – Doubleclick on ‘Communication Type’ in Window2 folders ‘Addresses’ and ‘Contacts’

TR-MA11648

TR-MA11778

TR-MA11846

B25648


A6071

A1023

A5003

A6063

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

6Page of




25749

26481

29589

Change Request

Change Request

Change Request

A.10.34 – Doubleclick on ‘Country Code’G.10.01 – Doubleclick on ‘Symbol’ fieldP.20.01 – Doubleclick on ‘Company Name’

For further information see online help of that screen.

New workflow “Audit” is released.You can track and report changes made to users within new workflow. Changes, tracked in the current version, are:• User creation• Changes in user security for product groups or projects• Changes in user privileges.• User activationYou can start and stop audit in the screen A.60.04 DBA Settings using new DBA-Setting AUDIT_ENABLE. By default “Audit” is inactive.

New screen A.60.86 Audit Trail allows you to monitor tracked changes.

Screen A.60.37 Customer CIPs/Forms/ReportsNew customer package is available: M_PCK_BOM_CUSTOM.New CIP function: get_lp_req_ind.

This CIP function has been incorporated into this package in order to allow customers to define whenever requisition flag (requisition_ind) should be set or not after insert or update in the table m_list_pos.The function is called within triggers on the table m_list_pos, so don't use commit in the function body. Function has to return 'Y' when requisition flag should be set to 'Y' and 'N' when requisition flag should be set to ‘N’. Use ‘-‘ as return value when requisition flag should not be changed.

B-29589 [ CMS XML Import: Structures (A) ]

A facility is now provided to enable users to define standardnotations for a particular language. In order to create the

B-25749

B-26481

B-29589


A1023

A6086

A6037

A6085 B-25749.RELEASE NOTES.DOC

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

B-25749.RELEASE NOTES.DOC

7Page of





9507

10309

10957

10998

Change Request

Bug Fix

Bug Fix

Bug Fix

standard notation for a particular language, user needs to first open the screen A.10.01 Languages. User can then double-click on Nls or Description field corresponding to a particular language. The new window for NLS notation codes would open. User can maintain data in the new window. A standard notation code is unique across the languages.

CR-MA9507:property of field keeping Fax number was set no non mandantory. Now, Fax numbers can now be deleted

CR-MA11515:Privilege ASSIGN EXTRA ROLE is now taken in account, if users access Role LOV's

CR-MA11487:Role LOV's have been resized to open with full view to the visible information and are sorted.

The problem on the single position window was that the attribute value LOV truncated the short description.

It is now able to display 255 characters.

Functions B1007, B2001 can now be copied using A.60.02.07

BOM Import will not ask for file upload if the data source is 'Flat Load Config' and Load Option is 'CIP'.

Cust.Ref.No.

CR-MA9507

TR-MA10309

TR-MA10957

TR-MA10998


E&PI (BOM)

A1001

A2005

A200602

B2001

B1007

B2001

B4001

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

8Page of




11117 Bug Fix New Admin Message:

- MAR-20390: No job is assigned to the project defaults (A.20.12 or A.20.13 ). No valid Master List-Job with list check TSQ ( B.20.01.41 ) assigned to project default ZB_LJ_TSQ.', Assign a valid List-Job to project default ZB_LJ_TSQ. This job must be a valid Master List-Job with listcheck TSQ. B2001 ( When-Button-Pressed Trigger on CTRL.CALL_B200141_TSQ_ONLINE)

New project default:

-- ZB_LJ_TSQ List Job for TSQ: This parameter will be used in moduleB.20.01 to transfer site quantities for a node from within the screen. The parameter points to a defined Verification Job from B.20.01.41. This job must be a master. Is the assigned job gone an error message will occur at execution time. The functionality is almost the same as in B.20.01.41. In the first step the assigned job will be copied to a new job. The second step is to start the new job.

B2001-----

-- New checkboxes 'TSQ Required' on pages displaying node data or list positions. Values for the checkboxes are only set by the system and will be checked if there are positions with site quantities (issue/reserved) in a lower issue status than the highest issue status at a node. -- New field 'Site Status' on List Nodes page is displaying the issue status containing position data with site quantities. -- Changed item prompt from 'IS Stat' to 'Highest Iss.

TR-MA11117

cont'dE&PI (BOM)

9Page of




11133

11151

11153

Bug Fix

Bug Fix

Bug Fix

Status'. -- Both fields are displayed if project default ZB_INDICAT is set to 'Y' only. -- New button 'Call TSQ' on the toolbar. Users can directlystart a TSQ job (B.20.01.41 Job) for the current node.

B2003-----

-- New checkboxes 'TSQ Required' on pages displaying node data or list positions. Values for the checkboxes are only set by the system and will be checked if there are positions with site quantities (issue/reserved) in a lower issue status than the highest issue status at a node. -- TSQ jobs can be started by already available functionality of calling 'BOM Procedures'.

B4001-------

-- When finishing the import job successfully but with entries of type 'Warning' or 'Error' in the Import Protocol (window 2) a B40R01 report will be started automatically and offered to the user for download or view directly.

We have inserted a check for the temp table.

In the screen B.20.03, prevented update of position values in the tabs Single Bulk Material View and Single Tag Material View, when the positions are locked by an user other than the logged-in user.

As in the requirement the copy of the positions is based only on the highest issue status.

TR-MA11133

TR-MA11151

TR-MA11153

cont'dE&PI (BOM)

B2001

B2003

B4001

B2001LOVM

B2003

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

10Page of




11350

11359

11365

11499

11554

11584

11585

11587

11595

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

After installing this patch it is possible to delete OMI jobs (type FLC) by standard functionality.

Fixed the problems related to BOM lock mechanism.

BOM positions can now be copied from other project to thelogged-in project.

When ZB_DUP_LP = 'N', during the check for uniqueness, considered issue status also.

Mentioned the number of PLL Units/PLL Lines created fromBOM or copied to BOM.

The triggers M_LSTN_AUG_TRG and M_LSTNN_AUR_TRG were removed.

Fixed the problem. The "Add Root Node" will be enabled when project doesn't have any nodes displayed.

Now onwards LOV will be available on the attribute value field in the property window and also mandatory field will bemarked with green background.

Hereon SAVE button will be enabled after deleting a position.

Correction of find ident if commodity_id is included in the

TR-MA11350

TR-MA11359

TR-MA11365

TR-MA11499

TR-MA11554

TR-MA11584

TR-MA11585

TR-MA11587

TR-MA11595

cont'dE&PI (BOM)

B2003

B4001

B2003

B2001LOVM

B2001

B2001LOVM

B2003

B1003

B2003

B2003

B2003

Module

Module

Module

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

11Page of




11620

11673

11717

12949

25742

Bug Fix

Bug Fix

Bug Fix

Change Request

Change Request

parameter list.

A MAR message will come when user tries to create node with same name with same level.

Now onwards Error will not come when manually entering avalue which is not matching with the valid values.

Fixed the problem even in Multi Status View tab page.

The background color is set as display item.

Screen has been revised for better performance with 11g database release.

The following are the changes done as a part of this user story to prevent duplicate entries in BOM and PLL.

1. A button ‘Populate from BOM’ is introduced in the screen ‘L.20.01 Process Line Lists’. Clicking this button opens ‘B.20.03 Adv.Maintain BOM (LOV for multi select)’ where the user can select multiple nodes (with only node type mentioned for the project default ZB_LS_UNIT). After selecting the nodes, the user has to choose the status from the LOV showing status from the screen ‘L.10.01 PLL Status’. Once the selection is done, PLL Units are created with the same name of the selected nodes. For these PLL Units, the Process Lines are created with the names of those nodes which have the node type mentioned for the project default ZB_LS_LINE and are immediately under the selected nodes.If the PLL Units already exist with the same name of the selected nodes, then only the missing Process Lines are created.Assumption: In BOM, the nodes with Node Type mentioned for ZB_LS_LINE are defined immediately below the nodes with Node Type mentioned for ZB_LS_UNIT.

TR-MA11620

TR-MA11673

TR-MA11717

D-12949

B-25742

cont'dE&PI (BOM)

B200141

B2003

B2003

B200308

B2003

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

12Page of




25748 Change Request

2. A button ‘Populate from PLL’ is introduced in the screen ‘B.20.01 Edit BOM’.This button is not available for those nodes which are locked by user other than the logged-in user. If ZB_BOMHIER is ‘N’ then, the button is not available for those nodes whose node type is not the parent of the nodetype mentioned for the project default ZB_LS_UNIT as per the hierarchy defined in ‘B.10.07 Node-Type Hierarchy’.Clicking this button opens a small window for the user to select multiple PLL Units.Once the selection is done, all these PLL Units are createdas child nodes under the node chosen initially. These child nodes have the same name of the corresponding PLL unitsand have the node type mentioned for the project default ZB_LS_UNIT.The Process Lines (if exist) for the selected PLL Units are created as child nodes to the nodes created with PLL Units. These child nodes have the same name of the corresponding Process Lines and have the node type mentioned for the project default ZB_LS_LINE.Assumption: The Node Type mentioned for ZB_LS_LINE is immediately under the one mentioned for ZB_LS_UNIT as per hierarchy in ‘B.10.07 Node-Type Hierarchy’ when ZB_BOMHIER = ‘N’.

3. A right click popup menu option ‘Populate from PLL’ is introduced in the screen ‘B.20.03 Adv. Maintain BOM’.The behavior of this option is similar to the behavior of the button ‘Populate from PLL’ in the screen ‘B.20.01 Edit BOM’.

Note: It is mandatory that the project defaults ‘ZB_LS_LINE’ and ‘ZB_LS_UNIT’ are defined.

B-25748 (Change request for attaching document(s) to commodity codes in screen S3001)

The user will be allowed to attach documents for commodity codes owned by product group, on project level. However, it is must that the discipline should remain the same. That is, only if the discipline remains the same, it will be possible to attach documents to the commodity codes owned by product group, on project level.

B-25748

cont'dE&PI (BOM)

B2001

B2001LOVM

B2003

L2001

Module Document Name Comment

13Page of




26343

28518

Change Request

Change Request

B-26343 [Sync populate PLL and BOM (V3472) I]

The main features of this user story are as follows:

1. Similar to attributes assigned on Process Line and Nominal Diameters, attributes can be assigned on Branches also.2. Right-clicking on PLL Unit / Process Line opens B.20.03Adv. Maintain BOM.• If the field ‘Reference in BOM’ shows a BOM path, the corresponding node’s MPV is opened.• If the field ‘Reference in BOM’ shows duplicate, out of themultiple references found the last modified node’s MPV is opened.• If the field ‘Reference in BOM’ shows not found, main window of B.20.03 Adv. Maintain BOM is opened.

B-28518 (SAIPEM SPMat (3579) Part 2/2 B200308)

It is possible now to copy BOM data [structure and positions] from a source to a destination, with the destination issue status automatically determined by the copy process. This is controlled by a new list box ‘Type’ having values ‘Automatic’ and ‘Manual’ in the screen “B.20.03.08 Cut/Copy Nodes”. If the value selected by the user is ‘Manual’, the user needs to enter the issue status for the destination [.i.e. as already existing]. If the value setis ‘Automatic’ then the copy process will for each destination: 1. Copy the positions from the source into the destination with the destination issue status selected as the next highest issues status for the existing positions in the destination.2. If no positions exist in the destination, copy the positions into the destination with the lowest available highest issue status.3. If the destination has positions with issue status having the maximum available sequence, then it creates a new issue status and assigns the copied position to this newly created issue status. The protocol for naming the automatically created issue status is “AUTO” concatenatedwith the sequence for the status.

B-26343

B-28518

cont'dE&PI (BOM)

B200147

B2003

L2001

Module

Module

Document Name

Document Name

Comment

Comment

14Page of




28660

28661

28977

30216

Change Request

Change Request

Change Request

Change Request

B-28660 (DDMS CIP Call Screen B4001)

As a part of this user story, a new Load Option ‘Custom Screen’ has been introduced in the screen ‘B.40.01 BOM Import’ under the section ‘FLC’.

When the Data Source is ‘Flat Load Config’, choosing this option calls a custom screen, specified against the newly created Application Server Specific Setting 'FLC_CUSTOM_SCREEN' in the screen ‘A.60.04 DBA Settings’, to fill the FLC tables.

B-28661 (DDMS FLC to support Item Type)

It is possible to configure the different item types when loading BOM using the ‘Flat Load Config’. The user should use the item with the name ‘POS_ITR’ while creating configuration for the ‘Flat Load Config’ in the screen ‘B.10.41 FLC Configurations’. The user can also set the value for the item type by using the LOV on the column ‘Value’, when the ‘Item’ selected is ‘POS_ITR’.

B-28977 (Sync/populate PLL and BOM (V3472) II)

Now it is possible to control whether the node names for a node type shall be unique within the project or not. This feature is controlled by a project default ZB_NODE_UK. If the value is set to N (default) then the node name under a node type may not be unique within the project. If the valueis set to Y then the node name under a node type will be unique within the project.

B-30216 (SPMat backlog ID 85 Part I)

1. Now it is possible to lock the selected Issue Status and all the lower Issue Status of a BOM Node from the screen

B-28660

B-28661

B-28977

B-30216

cont'dE&PI (BOM)

B200308

B4001

B1041

B200105

B200106

B2003

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

15Page of





10811

11291

11413

Bug Fix

Bug Fix

Change Request

B.40.31 Manually Lock BOM. Right mouse click on the tree node in B.40.31 Manually Lock BOM and choose LockSelected Node / Lock Sub Tree to invoke B.40.31 ManuallyLock BOM: Window 2. A new option “Selected and Lower” is introduced for Issue Status in B.40.31 Manually Lock BOM: Window 2. Select the option “Selected and Lower” tolock the Issue Status and all the lower Issue Status.

2. Now it is possible to lock the nodes, node values, positions and position values imported using B.40.01 BOM Import. A new checkbox “Lock BOM” is introduced in the screen B.40.01 BOM Import for this purpose. Check this checkbox “Lock BOM” to automatically lock the nodes, node values, positions and position values imported.

Screen R.10.41 Nodes and TemplatesBackground color of the requisition node displayed was displayed incorrectly. Provided patch fixes this problem. Screen R.10.41 Nodes and Templates (LOV)Background color of the requisition node displayed was displayed incorrectly. Provided patch fixes this problem.

Screen R.10.51 MTO TypesFixed issue that requisition rule having tags #BOM_Setup#, #REQ_SPLIT_DETAIL# cannot be used forMTO type when MTO Option is Template Structure.

Button 'Test Mail' has been removed from screen R.30.01. It is not needed any longer as the development of the functionality that required this testing feature has long beencompleted.

Cust.Ref.No.

TR-MA10811

TR-MA11291

CR-MA11413

cont'dE&PI (BOM)

E&PI (REQ)

B4001

B4031

R1041

R1051

R3001

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

16Page of




11669

11672

26210

28779

Bug Fix

Bug Fix

Change Request

Change Request

Removed word MARIAN from description for the dispositionrule COMMON RULE.

Screen R.10.41 Nodes and TemplatesFixes issue that some meaningless error message was displayed when there are no requisition nodes exist.

B-26210 (SPMat Changes (3779) II)

Now it is possible to restrict material in the screen R.30.01Maintain Requisitions: Window 2 as per the where condition of the requisition template. This feature is controlled by a project default ZR_RES_MAT.When creating manual requisition line items, if the project default ZR_RES_MAT is set to ‘Y’ then only those materialis allowed that satisfies the where condition of the requisition template. LOVs on Group, Part, Commodity Code, and Ident are restricted accordingly. Also, creation of new material (tagged items) is prohibited.If it is set to ‘N’ (default) then there is no restriction on the selection of material.

Changes covered by this installation packageThis installation package contains various fixes in regards to the Balance Requisition Workflow.

Screen R.10.41 Nodes and TemplatesFixed bug in the validation of the Requisition Rule: Using requisition rule contained tags #BOM_SETUP#, #REQ_SPLIT_DETAIL# was not allowed.

Screen R.10.51 MTO TypesFixed bug in the validation of the Requisition Rule: Using requisition rule contained tags #BOM_SETUP#, #REQ_SPLIT_DETAIL# was not allowed.

Field Req Node cannot be modified by user and is empty when MTO Option is Template Structure or Balance.

Screen R.20.01 MTO Jobs: Window 4

TR-MA11669

TR-MA11672

B-26210

B-28779

cont'dE&PI (REQ)

R2001

R1041

R3001

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

17Page of





11104

11323

11601

11791

Bug Fix

Bug Fix

Bug Fix

Bug Fix

This window is available only for balance MTO job which is not started jet. Layout displays only requisitions related fields.

Screen R.30.01 Maintain RequisitionsButton New Supplement is not available for a requisition assigned to a balance requisition as long as a balance requisition is not released to procurement. Releasing balance requisition allows you to create a new supplement of the child requisition using button New Supplement.

Button New Supplement is not available for a balance requisition: it does not make sense.

Menu

Fixed the problem. Modified Customer number holding variable data type from Number to Varchar2 to fix the problem.

SPLM License Problem.The end version is modified from 6.X.X.X to 7.X.X.X in the license text.

The maximum path length for upload is now identical with the maximum length as defined in the DBA setting GRAPHIC_UPLOAD_DEST (255 characters).

License installation no longer uses autonomous transactions.

Cust.Ref.No.

TR-MA11104

TR-MA11323

TR-MA11601

TR-MA11791

cont'dE&PI (REQ)

General

Installation

R1041

R1051

R2001

R3001

MENU

G1001

G1002

G1003

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

18Page of




MSC-No.

MSC-No.

Type

Type

Comment

Comment

11556

04868

11341

11341_1

25343

Bug Fix

Change Request

Bug Fix

Bug Fix

Change Request

Wrong setting of grants in 7.0.0 fresh install was corrected.These Grants were correct for any type of upgrade.

It is now possible to use CMS Workloads defined in SmartPlant Reference Data Plus in the SAP materal transfer SAP.20.01.

The new option ‘Workload’ for transfer mode allows the selection of one or more workloads for a transfer job by selecting the workoads using the ‘Workload’ button. The idents belonging to the selected workloads will be shown by pressing the button ‘Workload Idents’.Starting a job using with transfer mode ‘Workload’ creates a where condition in A.60.06 together with the corresponding MV_WHERE-view automatically.

Exception handling when writing idocs to database table.

Correction in writing data to table m_sap_transfer_job_idocs (see window2 of SAP2001).

B-25343 [ Select Idents for putting them into an SAP workload table ]

This functionality provides a mechanism to transfer selected Idents to a specific database table which is referred as “Workload Table” from where SAP interface canread them and transfer them to SAP system. The group of selected Idents at a time will always be linked to a code name called as workload name. These workload names shall be defined first and made available for further use of transferring Idents. The workload name shall be defined through a separate UI identified as XC4010 Define Workload. Please note the following:1. Workload name will not be allowed for modification.2. Delete will not be allowed once a workload name is used.3. Workload names shall be unique.

Cust.Ref.No.

Cust.Ref.No.

TR-MA11556

B-04868

TR-MA11341

TR-MA11341

B-25343

cont'dInstallation

Integrator

SAP2001

SAP2001

SAP2001

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

19Page of





4. An inactive workload name cannot be used for transfer.Selection of idents for transferring can be done in both Multi Article View as well as Classification Tree View of XC20 CMS Component Manager of CMS module. The mechanism to select and transfer is supported by right mouse click menu of both the views. On selecting the Idents for transfer, a separate dialog appears where user can put the priority and reason for Ident transfer to SAP. User also selects the specific workload to which the Idents will be associated.

(B-25751) Changes covered by this installation package

Screen A.60.37 Customer CIPs/Forms/ReportsNew CIP packages added.

M_PCK_SP3DEXP_CUSTOM – Package called from the screen SP3D 20.01 Export Job after job is finished successfully and indicator “Run CIP” is set.

M_PCK_PDSEXP_CUSTOM – Package called from the screen PDS 10.12 Generate and View PMC/PDS after job is finished successfully and indicator “Run CIP” is set.

M_PCK_PDMSEXP_CUSTOM – Package called from the screen PDMS 10.02 Create PDMS Spec-File after job is finished successfully and indicator “Run CIP” is set.

Screen SP3D 10.05 DestinationsNew indicator “Run CIP” added to the screen. The value of the indicator is populated into indicator “Run CIP” in the screen SP3D 20.01 Export Jobs when you create new job. Publishing custom procedure is called when the export job is finished and the indicator “Run CIP” is checked-in. Screen SP3D 20.01 Export JobsNew indicator “Run CIP” added to the screen. The value of the indicator is populated from indicator “Run CIP” in the screen SP3D 10.05 Destinations when you create new job.When you create new supplement of the job using New Run button, the value of the “Run CIP” indicator is populated from previous supplement of the job.

Publishing custom procedure is called when the export job is finished and the indicator “Run CIP” is checked-in.

Screen PDS 10.12 Generate and View PMC/PCDNew indicator “Run CIP” added to the screen. Publishing

B-25751

cont'dIntegrator

XC4010


20Page of





26627

10212

Change Request

Change Request

custom procedure is called when generation of the output files, initiated by button ASCII, is finished and the indicator “Run CIP” is checked-in.

Screen PDMS 10.02 Create PDMS Spec-FileNew indicator “Run CIP” added to the screen. Publishing custom procedure is called when the generation of the output files, initiated by button Transfer Selected Specs, is finished and the indicator “Run CIP” is checked-in.

It is now possible to use CMS properties of a CMS class for the feature mapping in SAP.10.07.The new type ‘CMS’ will require the user to select a CMS class and select a CMS property of this class as value.This will transfer the value of the table detail code assignedto the ident or the attribute value (depending on the property definition).When checking the ‘Use NLS’ checkbox (only for CMS), the table detail description or attribute value for the SAP default language as defined in SAP.10.01 wil be used as value for the transfer instead. If an attribute is already defined as NLS dependent, then automatically the language dependent value for the SAP default language is used.

P.70.74 PackagesPT.20.21 Preliminary PackagesThe new field 'Supplier' is shown in both screens, but only filled in case of a PO. P.70.74 PackagesThe order of the fields in folder 'With Release Notes' changed to:Order NumberRelease Note NumberEMLSupplier

Cust.Ref.No.

B-26627

CR-MA10212

cont'dIntegrator

MSCM

A6037

PDMS1002

PDS1012

SP3D1005

SP3D2001

SAP1007 SAP1007 INT-SAP-MAT.DOCX

Module

Module

Document Name

Document Name

Comment

Comment

INT-SAP-MAT.DOCX

21Page of




10213

10293

10576

1061

Change Request

Change Request

Change Request

Change Request

MOT Code

P.70.74 PackagesPT.30.02 OSD for Packages

The field of the package description was expanded to 2000 digits.

It is no longer possible in P.10.25 Question List to specify the same mapping for more than one question (per company type).

It is now possible to add additional free text questions/answers in tab folder 'Qualification Questions' of P.20.01 Suppliers/Subcontractors, i. e. questions not available in P.10.25 Question List and therefore not visible in P.20.03 Questionnaire.

These questions and answers remain modifyable in P.20.01; however, updates and deletions will be protocolledin the supplier history (if enabled).

In order to be able to easily distinguish between questions added manually via P.20.01 and questions the answers to which have been submitted by the respective supplier/subcontractor via P.20.03, a new 'Manual' checkbox has been added to the 'Qualification Questions' folder. This checkbox is ticked for all questions/answers that have not been submitted via P.20.03.

The list of values of field 'Tag Number' has been reworked completely. It now offers all tagged items (TWM) available on bills of material as well as on manual requisitions.

CR-MA10213

CR-MA10293

CR-MA10576

CR-MA1061

cont'dMSCM

P7074

PT2021

P7074

PT3002

P1025

P1025

P2001

P2003

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

22Page of




10667

10716

10920

10921

Change Request

Change Request

Change Request

Change Request

When manually entering a known other cost in screens such as P.30.22 or P.50.07 (instead of using the LOV) the language dependent description is now also taken over from P.10.33 into these screens.

Display of tab folder 'Company Profile' on Window 2 of P.20.01 Suppliers/Subcontractors now depends on the setting of project default ZP_SUP_QLF (formerly named ZP_QL_MODE). In short, this tab folder will be visible if andonly if tab folder 'Qualification Questions' is visible too (i. e. if ZP_SUP_QLF is set to BOTH or to ESUP).

The field 'Delivery Place' in the multi-selection-LOV (Window 2) now is filled.

P.10.83 Package Types

A new screen is available to maintain package types.Now the combo boxes in P.70.74, PT.20.21 and C.20.05 tochoose the package types are substituted with LOVs.The following screens changed:

P.70.74 PackagesPT.20.21 Preliminary PackagesPT.30.02 OSD for Packages (in LOV)C.20.05 Prepare MRR by Packages

P.70.74 Packages

The templates for the Excel Import and Export changed. The columns ...PCK_TYPE for the package type changed to ... PCKT_CODE.

While importing data you can use all package types entered in P.10.83 Package Types.If an unknown package type is entered in the Excel file, it can be generated while importing the data.

The names of the new Excel templates are:

PCK-701.xls

CR-MA10667

CR-MA10716

CR-MA10920

CR-MA10921

cont'dMSCM

P6001

P3022

P5007

P2001

PT2021

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

23Page of




10922

10989

11002

11024_2

11122

Change Request

Bug Fix

Change Request

Change Request

Change Request

PCK-RN-701.xlsPCK-IMP-701-NEW.xlsPCK-IMP-RN-701-NEW.xls

The field 'Freight Ton' was renamed to 'Total Freight Ton'.

Screen P.70.74 Packages now detects totals (weight, volume, freight ton, transport costs) exceeding the number ranges of the underlying data structures prior to commiting changed records to the database. Thus, it is no longer possible to commit data that cannot be displayed after a requery due to calculated totals being out of range.

For agreement line items without predecessor that are based on a quote summary ident values that have been changed during the technical evaluation are now synchronized when approving an agreement. I.e. the valuesthat have been entered in screen P.30.23 Technical Evaluation are taken over to screen S.80.22 so that the information is available downstream.

When reversing the approval of an agreement the synchronization of ident values (result of the technical evaluation) is reversed for line items without predecessor.

In screen P.50.07 option 'Global update' is now also available for attributes on line item level.

P.20.02 Login RequestsAfter the eSupplier has created a new company the NLS entries will also be filled. The field 'Short Desc' will be filled with the company (code), the field 'Description' with the company name.

CR-MA10922

TR-MA10989

CR-MA11002

CR-MA11024

CR-MA11122

cont'dMSCM

C2005

P1083

P7074

PT2021

PT3002

P7074

P7074

P3023

P5007

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

24Page of




11316

11320

11344

Bug Fix

Change Request

Bug Fix

TR-MA11316Splitting of tags is now also possible for manually created requisitions if project default ZB_SPLI_WP has been set.

CR-MA4950The design of the screen changed. Below the order header block now you see the two blocks for the shipment groups and under it the details of the shipment groups, the item shipments.

The project default ZP_HIDE_MT now is also used in this screen. It controls what shipment groups of the order are visible.

If the project default is set to 'Y' the shipment groups whichonly contain master tags without any detail tag are hidden and the block 'Item Shipments' shows all item shipments ofthe selected shipment group except master tags (normal item shipments and detail tags). In this case you can split detail tags and the label of the split button changes to 'SplitMaster Tag'.

If the project default is set to 'N' all shipment groups of the order are visible and the block 'Item Shipments' shows all item shipments including master tags. In this case you canonly split master tags and the label of the split button is 'Split Tag'.

Field 'B/L (AWB) Date' has been added to the carrier-LOV of screen P.70.31.

In tab folder 'Download' of screen P.30.24 Download/Load Bids, only quotes of bidders may now be selected for mailing that have been downloaded right before. Furthermore, error reporting has been improved.

TR-MA11316

CR-MA11320

TR-MA11344

cont'dMSCM

P2002

P3001

P3004

P5007

P5019

P7031

P7031

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

25Page of




11393

11406

11408

11426

11440

11444

Bug Fix

Bug Fix

Change Request

Bug Fix

Bug Fix

Change Request

When working with milestones the creation of an agreement supplement via screen P.30.04 now works again.

Documents can now be attached again in screen P.70.52 Attached Inspection Documents.

Project default ZP_KEEPPOS is now also used in screen P.50.07 when adding a requisition to an agreement without summarizing line items or when adding a quote summary to an agreement.

I.e.. in these cases the application will try to keep the position numbers of the requisition if possible and if the project default has been set to 'Y'.

In case of adding a requisition to an agreement with summarizing line items this is done (already for a long time) regardless of the setting of the project default.

When splitting tags while importing packages from an Excel file the errors 'numeric or value error', 'ON-UPDATE trigger raised unhandled exception...' or 'No changes to save' will no more arise.

The reminder that is displayed when the user tries to close Window 2 of P.20.03 without having pressed the 'Submit' button first now appears without taking the revision of the Company Profile/Qualifications into account.

The new project default ZP_CHSUPCO is used to control whether the supplier may be updated on a change order or not (screen P.50.07).

If this project default is set to 'Y' (default) a supplier can be changed even on a CO. Please keep in mind that changingthe supplier on a CO affects all previous supplements. I.e. the complete agreement cycle will be switched to the new

TR-MA11393

TR-MA11406

CR-MA11408

TR-MA11426

CR-MA11440

CR-MA11444

cont'dMSCM

P3024

P3001

P7052

P5007

P7074

P2003

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

26Page of




11453

11459

11616

11633

11650

11719

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

supplier.

If this project default is set to 'N' you can change the supplier on the base (or first) supplement but not on higher supplements of type CO.

Implemented a more defensive treatment of associated ident structures when deleting PO line items.

For project default ZP_ALLSUPP (screen P.70.73) it is nowalso taken into account if a requisition belongs to the current agreement cycle or not. So far this was not the case which could lead to the effect that no data were available if a requisition cycle was split into different agreement cycles.

Data are now displayed correctly in the second window of screen P.50.07 if you click in the empty space in the tree window. Nevertheless we recommend to click on existing entries/supplements in the tree instead of just clicking anywhere.

When creating an agreement for an engineering requisition from an inquiry (option in screen P.30.01) this now covers all positions of the latest inquiry supplement even if a requisition line item can be found as being selected on several of the corresponding previous inquiry supplements.

Adding of a requisition to an agreement now works again if a requisition line item can already be found on an agreement and is added another time without summarizing.

Screen P.20.03 Questionnaire has been slightly modified inorder to speed up submission of company profiles and qualifications.

TR-MA11453

TR-MA11459

TR-MA11616

TR-MA11633

TR-MA11650

TR-MA11719

cont'dMSCM

P5007

P5007

P7073

P5007

P3001

P5007

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

27Page of




11749

11798

13562

Bug Fix

Change Request

Change Request

Upon return from S.80.25, refreshing the ident short description of the item shipment for which S.80.25 had been called is now achieved in a less time-consuming way,even for agreements with hundreds of item shipments.

When entering PO line items in P.50.07 Maintain Agreements, the quantity unit is no longer checked against'm_pck_req_custom.qty_unit' if a PO line item is a tagged item.

CR-MA10065 = Backlog Item B-13562Alternates and options can now be assigned to agreement line items. For this purpose field ‘Line Item(s)’ has been added in folder ‘Alternates/Options’ in screen P.50.07.In this field you can see whether any line items have already been assigned to an alternate or option. If no assignment has been done so far the field contains the value 'NONE'. If exactly one line item has been assigned you will see the position and sub position number of that line item. If more than just one line item has been assigned to the alternate/option the value 'MULTIPLE' is shown. Regardless of the current value in this field you can double-click on it to open a window where you can do the dispersement of the alternate/option price (in case of new records provided that all mandatory information has been entered).

In this new window you can assign agreement line item numbers to alternates and options. You can either set a percent value or a fix value to be associated with that line item for the selected alternate and option respectively.Setting the percent value automatically calculates the fix value and vice versa.

The sum of the percentages of all line items that have beenassigned must total up to 100.

The fix value is added to the extended price of the line itemand used to calculate a new unit price for the line item.

TR-MA11749

CR-MA11798

B-13562

cont'dMSCM

P2003

P7072

P5007

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

28Page of




You can only select agreement line items that are includedin the current supplement and that do not have a supply price or an install price. The quantity of the line item must be greater than 0 and in case the price base is "Weight" the unit weight must also be greater than 0.If a line item that you need is not yet included in the current supplement but was included in a previous supplement you can do a dummy update on any field, e.g. quantity unit or weight unit, to include the position in the current supplement.

The price of an alternate/option is only included in the total costs of an agreement if checkbox ‘Include’ has been ticked and if line items have been assigned.

Moreover field ‘Alternate/Option Costs’ has been added to folder ‘Line Items’ in screen P.50.07.Here you can see the costs that are included in the extended price caused by alternates and options.Only alternates and options for that checkbox 'Include' [in price] has been ticked are taken into account.

CR-MA11024Additional performance improvements have been realized for screen P.50.07.

TR-MA11265An Oracle exception is not raised any longer if the approvalof an agreement is not possible because of the result of CIP m_pck_po_custom.agreement_approval.

TR-MA11298Message MAR-30840 is now raised again when pressing button 'Execute CIP' in screen P.50.07.

TR-MA11300The check for the validity of the quantity unit in screen P.50.07 is not done any longer for new material.

TR-MA11189When entering quantities on requisition line item level in screen P.50.07 data must now be committed before leavingthat block in case of line items not yet included in the current supplement.

cont'dMSCM

29Page of




1822

25645

Change Request

Change Request

A new button 'Calc All Forecasted' has been added that allows for calculating the forecasted dates of all planned requisitions within the project to which the user is currentlylogged on.

The corporate warehouse functionality has been reworked.

The fields 'CWH Quantity' and 'FIM Quantity' have been added to folder 'Line Items' in screen R.30.01. This allows you to see at this early point in time whether material is available in one of these warehouses.

(Please note that the usage and availability of warehouses and their quantities is limited by the warehouse-to-user-concept.)

(FIM stands for free issue material and is material which is received from the EPC’s customer and made available for usage. This material can be used to reduce the purchasingquantity like corporate warehouse quantities.)

If you want that quantities that are available in the corporate or FIM warehouses are taken into account when creating inquiries you have to set the new project default ZP_RDQTYCF.Per default (value = 'N') quantities in these warehouses have no effect on the quantity placed on an inquiry.If this project default is set to 'Y' the quantity on the inquiry is reduced by the quantities in these warehouses. This means the inquiry will only contain the remaining quantity for that you need a quote. This can lead to quotes that onlycontain parts of the requisition and not all released lines if some positions are completely covered by corporate or FIMwarehouse quantities.

Please note that although the quantity on the inquiry is reduced these quantities remain in the warehouses. If you do not block them more or less immediately by creating an

CR-MA1822

B-25645

cont'dMSCM

P3001

P3004

P5007

P5019

P7031

P6003

Module

Module

Document Name

Document Name

Comment

Comment

30Page of





agreement for the corporate or FIM warehouses you run therisk that the quantities have been used by someone else inthe meantime. In that case you have to go through the inquiry cycle for the remaining quantities or create an agreement for a real supplier.

In screens P.30.01 and P.50.01 the new option 'Create from FIM warehouse'/'Based on FIM warehouse' has been added. Basically FIM warehouses are used in the same way as the corporate warehouse. Quantities that are retrieved from these warehouses are reserved and not available for other users unless the quantities are reduced or positions or even complete agreements are deleted. When approving such agreements the quantities are issued.

Please note that expediting (screens P.70.62 and P.70.72)has NO effect on the corporate or FIM warehouse quantities.

Modifications to screen P.10.57 Events to Levels:

• A new checkbox labeled 'Skip' has been added to the 'Events to Levels' block. It can be ticked for events the event start of which has been set to 'Order Approval' in order to prevent the system from scheduling this event on the day of order approval itself. Per default the checkbox remains unticked, thus preserving the traditional way of working.

Modifications to screen P.70.73 Order Reference:

• In tab folders 'Expediting Events' and 'Inspection Events', it is now possible to amend this specific expediting/inspection plan in individual cases by deleting events that turn out to be superfluous or by adding additional events of the expediting level assigned.

• On entry of the initial planned date for an event with frequency 'Once', the forecasted date is now automatically set to the same value.

• A new 'Comment' field has been introduced for both

B-25652

cont'dMSCM

P3001

P5001

P7062

P7072

R3001


31Page of




25697

26970

Change Request

Change Request

expediting and inspection events.

• Documents attached to expediting/inspection events (or tasks) can now easily be viewed using the new 'Open' button on the respective tab folders.

B-25697 CR4:------------The new button "Technical Evaluation" has been implemented into P.30.27. to call the screen P.30.23.If the screen is opened as E-Supplier, only the folder Ident Values with logged-in supplier data is shown.The E-Supplier is able to modify "TE Passed" , "Evaluation Text" and "Value", if the privilege "TECHNICAL EVALUATION" is given to the E-Supplier role.

TR-MA11261,CR-MA11119,CR-MA11120,CR-MA11121,CR-MA11122.

P.20.02 Login Requests

Fixed a password decryption problem that could arise in P.20.02 Login Requests and the Supplier Entry that resulted in notification e-mails related to a forgotten or changed password not being sent to the user (TR-MA11261).

After the eSupplier has created a new company the NLS entries will also be filled. The field 'Short Desc' will be filled with the company (code), the field 'Description' with the company name.

eSupplier Login

When an eSupplier has logged on successfully he gets a message about that and additionally a hint what to do next.A checkbox indicates whether the eSupplier is logged on or not.

B-25697

B-26970

cont'dMSCM

P1057

P7073

P3023

P3027

Module

Module

Document Name

Document Name

Comment

Comment

32Page of




30294

30492

5164

5277

Change Request

Change Request

Change Request

Change Request

P.20.03 Questionnaire

After the eSupplier has logged on successfully and afterwards he chooses 'Profile & Qualification', the qualification tree in P.20.03 Questionnaire expands immediately.

When an eSupplier enters an empty field that offers a list ofvalues it opens automatically.

Overworked report PT20R01P with install script as well as revised.PT20R01A and PT20R01F are also added, as there have been some small changes since last issue to MSC.

Due to the fact, that traffic module (PT) was redesigned, PT20R01A and PT20R01F were newly developed. Additional, a package and a temp table have been created to solve the redesign issue.

A new button 'Calc All Forecasted' has been added to P.60.01 Tagged Items Planning that allows for calculating the forecasted dates of all planned tagged items within the project to which the user is currently logged on.

For P.60.03 Requisitions Planning see CR-MA1822.For P.60.05 Milestone Explorer this has already been implemented before.

The legend of the tree has been enhanced with explanations of the icons used for detail milestones.A reduction of the height of the milestone tree for this purpose was not necessary in the end.

B-30294

B-30492

CR-MA5164

CR-MA5277

cont'dMSCM

P2002

P2003

PT20R01A

PT20R01F

PT20R01P

PT20R01A

PT20R01F

P6001

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

33Page of





5817

7995

8215

8967

10610

11531

11647

Change Request

Change Request

Change Request

Change Request

Bug Fix

Change Request

Bug Fix

It is now possible to attach attributes to planned requisitions.

This feature can be used to assign (non-standard) properties like, for example, a 'requisition title' to planned requisitions.

Fields 'Orig. Days' and 'Days' in all 'Milestones' blocks of screens P.60.01 Tagged Items Planning, P.60.03 Requisitions Planning and P.60.05 Milestone Explorer havebeen vertically indented (identically to field 'Span Days') in order to improve comprehensibility.

In screens P.70.62 and P.70.72 a warning is raised if an item shipment quantity is entered that is less than the quantity already received.

The length of the 'Plan Comment' and 'Forecast Comment' fields in the 'Milestones' blocks of screens P.60.01 Tagged Items Planning, P.60.03 Requisitions Planning and P.60.05Milestone Explorer has been increased to 255 characters.

The background color of the block label is now correct.

When an online job fails due to an invalid path this path is now listed in the log file to make it easier to find out wrong settings.

The colors of the symbol field are now displayed correctly.

Cust.Ref.No.

CR-MA5817

CR-MA7995

CR-MA8215

CR-MA8967

TR-MA10610

CR-MA11531

TR-MA11647

cont'dMSCM

Others

P6005

P6003

P6005

P7062

P7072

P6003

D3021

G1001

G1002

Module

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

Comment

34Page of




15827

25649

29590

Change Request

Change Request

Change Request

.NET:

This fix has implementation for CMS Global Properties (XC1020). The view MV_GLOBAL_PROPERTIES has beenchanged in order to fix this problem. Earlier partial unrestricted data was appearing though this view and hence data in the column "Class System - Revision" was not getting reflected properly. Data from other projects and even from product group shall not be visible through this view now as it does not realize any functionality in CMS.

D.50.21 Attached Comments

If you enter comments for objects with the ability to build supplements (requisitions, inquiries and agreements) there will be new elements visible in the screen to copy attachedcomments from the previous supplement. Dependent on the object you can copy comments from theprevious supplement on header level, on header and line level, only on line level or only the current line.

If you want to copy comments within quote summaries (P.30.22 Commercial Evaluation) and quote details (P.30.22 Commercial Evaluation: Window 2) the comments to be copied related to the previous supplement of the inquiry and the actual bidder.

B-29590 [ CMS XML Import: Structures (B) ]

The previous implementation of importing class system from XML data shall be changed. Now it is understood that the whole data corresponds to one language only. Hence inthe same file we do not have class system descriptions in different languages. Also, language itself cannot be an attribute of an XML element. It will always correspond to anXML Element only.

If class system revision is not provided in the XML data, then by default it is taken as 0. Similar to language,

D-15827

B-25649 CR-MA6811

B-29590

cont'dOthers

G1003

XC1020

D5021

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

35Page of





10332

10332_2

10616

10616_1

11073

11074

Change Request

Change Request

Bug Fix

Bug Fix

Bug Fix

Bug Fix

revision also cannot be an attribute of an XML element. It will always correspond to an XML Element only. Also data for revision should always occur after the data for class system code in the XML file.

In PDS 10.01 there will be a new option "only Spec Item Idents in project" for generation of SDL and SDD. Both will toggle synchronously between the new option and "only Spec Item Idents". So if it is changed for SDL it will be for SDD and vice versa.

In PDS 10.01 there will be a new option "only Spec Item Idents in project" for generation of SDL and SDD. Both will toggle synchronously between the new option and "only Spec Item Idents". So if it is changed for SDL it will be for SDD and vice versa.

An user friendly error message will be displayed when a table detail cannot be deleted because it is already used inpart table detail links.

Error handling for unexpected errors improved so that an error message is displayed constaining the complete error information.

When deletion of table detail is not allowed, a user friendly error message will now list all tables where the detail is already used.

Enabled glossary functionality for tab page ‚Specification Limits‘

‚No Display’ functionality for block items is now working

Cust.Ref.No.

CR-MA10332

CR-MA10332

TR-MA10616

TR-MA10616

TR-MA11073

TR-MA11074

cont'dOthers

SPRD

XC30

PDS1010

PDS1010

S2002

S2002

S5006

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

36Page of




11078

11079

11080

11126

11171

11184

11186

11187

Bug Fix

Bug Fix

Bug Fix

Change Request

Bug Fix

Bug Fix

Bug Fix

Bug Fix

also if the module is set to ‘Read Only’

Buttons on window1 disabled in enter-query mode.

Correction of background colour for prompts of dynamical attributes

Copy NLS button is now disabled in Enter-Query mode.

SP3D 10.12: m_pck_sp3d_lookup.find_in_cc function will now accept arbitrary mapping names, not only a fixed list of predefined values.

Correction of lock behaviour for geom details. If the project default ZS_FRAC is set to ‘Y’, then it is necessary to commit changes in window1 (Geometric Table Definition) first before navigating to window 2 (Geom Details).

The retrieval source "PipeNominalDiameters from spec ident sizes" now also returns results if one or more of the SI_%SHORT_CODE_LST values in SP3D 10.01 are not set.

-Correction of cursor statements to prevent Oracle error ORA-00979.

-Errors during processing will no longer be suppressed

Correction of update behaviour of Spec Copy.

TR-MA11078

TR-MA11079

TR-MA11080

TR-MA11126

TR-MA11171

TR-MA11184

TR-MA11186

TR-MA11187

cont'dSPRD

A3003

S1003

S2001

S1002

SP3D1012

S4010

SP3D1012

PDMS2001

S5005

Module

Module

Module

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

37Page of




11202

11225

11256

11277

11290

11313

11411

11428

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

Bug Fix

Correction of olet processing for spec item idents.

Enhanced message handling.The logfile will now indicate which spec item id threw the exception.

Correction of processing for spec item idents for parts defined as COUPLING in case the spec has been issued and the spec item idents have been stored permanently.

The navigation to the fields value and description in the attributes tab page in S.30.01 screen will work fine without any error.

Usage for option code will now be stored when using S1008 in non combo box mode.

PRE_EXP_SHT procedures will work when Extended Customisation is selected.

It is now possible to delete idents which have been already transferred to SAP (i.e. the ident is existing in m_sap_idents).

In this case the user will need to confirm an alert informing him that the ident/idents have already been transferred.This functionality is only available on window 1 of S.80.01, but not for the mass deletion of invalid idents on window 5.

In S.50.06, S.50.18, spec items are copied to the specs within the logged-in project itself.Hence, the checks for mandatory and optional pre-requisites are not considered.

TR-MA11202

TR-MA11225

TR-MA11256

TR-MA11277

TR-MA11290

TR-MA11313

CR-MA11411

TR-MA11428

cont'dSPRD

S3001

PDS1010

S5006

S3001

S1008

S8001

S5006

Module

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

Comment

38Page of




11465

11482

11489

11545

11576

11594

11600

11605

11618

11618_2

11665

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

If duplicate records are found then only one of those will be considered for creating spec item idents.

Error removed resulting in incorrect discipline security processing for S.20.02 when using queryable disciplines.

Field ‚User‘ is now defined in upper case.

Correction of calculation of deleted and created commoditygeometric relations

Length correction of internal variable to avoid datatype errormessage.

Performance of LOV on part improved.

Correction of variable definition for select against mvpr_spec_headers

Update of commodity layout when rule layout changes in s.10.01 will now consider the correct special attribute values.

Correction of online help for export functionality

Correction of online help for export functionality.

Exporting PartClasses in SP3D 20.01 will also filter for

TR-MA11465

TR-MA11482

TR-MA11489

TR-MA11545

TR-MA11576

TR-MA11594

TR-MA11600

TR-MA11605

TR-MA11618

TR-MA1618

TR-MA11665

cont'dSPRD

S5018

S5006

S2002

A6006

S4021

S1003

S8004LOV

S5006

S1003

P8051

P8051

Module

Module

Module

Module

Module

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

39Page of




11709

11723

11744

11760

24152

24556

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

Change Request

Project/ProductGroup if idents are not limited by spec selection.

Block synchronization for spec items corrected to avoid unwanted navigation to spec item notes.

Column headings of variable attributes are now using the label defined in A.50.01 for the attribute.

Fixed the problem. The error reported by the user is fixed and copy of the specs will be successfull with this fix.

Correction display of part symbol/commodity symbols

Improvement on analyzing the bulkload feedback logfile during transfer of data from SPRD to SP3D in screen SP3D20.01.

Recognition rate should now be 100%. Program is now capable of processing unskipped but modified rows.

B-24556 [ 83-Import job user Class Code ]

Data for all CMS logical structures shall be available in the XML file for structures. The distinct elements / attributes of the XML file will be mapped to a unique CMS logical structure. This user story deals with importing the Class Code, Keywords and Short / Long Descriptions of the Classes.

Following are the assumptions / behavior for this functionality.

Remarks

Class1 Elements, Attributes and Data for Class Systems (including Revision and Description) should appear before

TR-MA11709

TR-MA11723

TR-MA11744 TR-MA11784

TR-MA11760

B-24152

B-24556

cont'dSPRD

SP3D2001

S5006

S3001

S5051

S3001

SP3D2001

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

40Page of




the first element corresponding to Class Code.

2 The XML for structure should contain at least one Class Code.

3 Data for Class Code will always correspond to an Element in XML file.

4 Data for all Classes will be at same hierarchical depth. This does not mean that all elements for the Class Code will have same parent element.

5 All child or supporting data for a Class will appear below its corresponding element but before the element for next Class.

6 One of the Class Codes shall be supplied as Parent Class Code.

7 Class Commodity Group, Commodity Part or CommodityCode can either be specified as elements or as attributes of the element representing the Class Code.

8 It is assumed that provided Commodity Group, Commodity Part and Commodity Codes are already available in the system.Class NLS

9 If Class Short Description (and Long Description is also not available) is not found then it will be same as Class Code.

10 If Class Long Description is not found then it will be same as Class Short Description. Similarly If Class Short Description is not found then it will be same as Class LongDescription (if available).

11 Class Description (Short and Long) will always correspond to an Element (and not Attribute) in XML file.

12 Class Keyword will always correspond to an Element (and not Attribute) in XML file.

13 If Class Keyword is not provided then it will be same as Class Code.

14 If only Keyword is provided against the Class and both Short and Long Descriptions are not there in the data, thenShort and Long Descriptions will be same as Class Code.

15 Language Attribute / Element must accompany the

cont'dSPRD

41Page of




25739

25753

26209

Change Request

Change Request

Change Request

Short and Long Class Descriptions.

B-25739 (Codelist Consistency Hotfix)

The Code-lists can now be directly retrievable from Table Details. There is no need to store them in Templates. A new retrieval method ‘TABLE_DETAILS’ is introduced in the screen ‘SP3D.10.07 Sheet Configs’ to support retrieval of code-lists from the table details and the table groups.

The following are the limitations:1. At present the maximum hierarchy level supported by the retrieval method ‘TABLE_DETAILS’ is 7.2. The new retrieval method ‘TABLE_DETAILS’ supports only sheets with category as ‘CODE_LIST’.3. The ‘POST_EXP_SHT’ and ‘PRE_EXP_SHT’ procedureswill be available for this retrieval process.

¿ SP3D 10.02/6/7 and SP3D 20.01 have a new poplist item “Working with” on their top which lets the user choosean interface from A.70.01.¿ Changing the item will query for related data¿ LOVs and validations will only offer related data¿ Item will keep its value in all 4 participating screens, unless changed or application is closed¿ Default value for the item is “SP3D”¿ Migration will assign all data to “SP3D”. Interface “SP3D”will be created if not yet existing.¿ Btw. added autoquery functionallity to SP3D 10.02/6.

B-26209 (Destination Update cont. (Copy, check for pending)

Now, it is possible to copy manual destination data from one destination to the other from the screen SP3D 10.05 Destinations.Click on the button Copy Manual Dest. Data to invoke the copy dialog. Select the source destination from which you

B-25739

B-25753

B-26209

cont'dSPRD

SP3D1007

SP3D1002

SP3D1006

SP3D1007

SP3D2001

B-25739(CODELIST CONSISTENCY).DOCModule

Module

Document Name

Document Name

Comment

Comment

B-25739(CODELIST CONSISTENCY).DOC

42Page of




26335

26342

Change Request

Change Request

wish to copy the manual destination data and click on the button Copy. The destination on which the cursor is located when the button Copy Manual Dest. Data is clicked is the target destination.

Now it is possible that the export job will be cancelled and a new instance will be started automatically whenever thereare pending manual destination changes to be applied. When you start the export job in the screen SP3D 20.01 Export Jobs from FILL_IF_TABS stage the system checks for pending manual destination changes. If there are then an appropriate message is displayed and you can choose to apply the changes or ignore the changes. If you choose to apply the changes then the job will be cancelled and a new instance will be started automatically.

Also, fixed some of the bugs below in the screens SP3D 20.01 and SP3D 20.02• In SP3D 20.02 when the sheet data is queried the cursor is now positioned on the first item. • The error “Cannot set blocks data query” that comes when you open sheet data is fixed.• Update of ‘NULL’ to oracle NULL is now possible on manual destination data.

Screen S.30.11 Concept Commodity CodeIn the previous release you couldn’t work with the attribute based commodity because fields Type, Attribute Set and the tab-folder Attributes are not available in the screen.Provided patch fixes this problem.

B-26342 (Additional SP3D.10.15 changes for Technip incl. HotFix - 1)

It is now possible to comment an entry in the sp3d export process excel. The special character (!) will now be shown under the column ‘Head’ to indicate that the corresponding record is commented in the exported excel. The following gives a brief description of assumptions on which this functionality is based upon.

B-26335

B-26342

cont'dSPRD

SP3D1005

SP3D2001

SP3D2002

S3011

Module

Module

Document Name

Document Name

Comment

Comment

43Page of




26898

28999

Change Request

Change Request

• This functionality is available only if the sheet is configured in the screen ‘SP3D.10.07 Sheet Configs ‘with the checkbox ‘Extended Customization’ as checked.• The functionality is available for retrieval methods TEMPLATE_COPY, TABLE_DETAILS and SHT_STND_METHOD. • The user should enter the value ‘!’ under the item ‘Action’ as replacement information for a selected filter attached to a sheet and sheet config in the screen ‘SP3D.10.07 Sheet Configs ‘.• The records considered by the filter for whom the replacement information has ‘!’ in the column ‘Action’ will not be considered for uniqueness verification. No check willbe performed against the existing inventory. These records will be shown in the generated excel but will not be inserted into the inventory.

B-26898 [ Automatic set of Input and Output Columns ]

Presently when a CMS Ident is created, all the input (except INPUT_5) columns of table M_IDENTS have the value 0. Column INPUT_5 has value same as in column IDENT. Output columns have value NULL. Property values for Ident are store in the tables M_IDENT_PROP_VAL and M_IDENT_PROP_VAL_NLS. Presently, the class properties do not correspond to any input or output dimension.As per the proposed solution, we need to provide an additional column in the screen for Class Properties. User can select any of the listed input or output dimensions against the class properties:• INPUT_1..4• OUTPUT_1..15INPUT_5 will continue to be reserved for internal CMS usage and not be available to be assigned against any class property.When a CMS Ident is created / updated, the data of class property value will now also go into the corresponding columns of M_IDENTS as specified by the input or output dimensions. 26898

B-28999 (Additional SP3D.10.15 changes for Technip incl. HotFix - 3)

It is now possible to add manually entered records in the

B-26898

B-28999

cont'dSPRD

SP3D1015

SP3D2001


44Page of




3550_7 Change Request

exported excel during SP3D export process. The manual data should be entered in the screen SP3D.10.15 Add, Find and Replace based on a sheet under a sheet configuration. When exporting to excel or completing the job, this manually entered data will be appended to the sheet. 1. This functionality is available only if the sheet is configured in the screen SP3D.10.07 Sheet Configs with the checkbox ‘Extended Customization’ as checked.2. The functionality is available for retrieval methods TEMPLATE_COPY, TABLE_DETAILS and SHT_STND_METHOD. 3. The user should enter the manual data based on the sheet in SP3D.10.15 Add, Find and Replace under the tab page ‘Manual Data’.4. The manual records will be considered for uniqueness verification and against the existing inventory.5. The manual records will be stored in the inventory.6. The find and replace functionality is not applicable on themanual data.

New Features

B-04679

The Issue/Release Project Spec screen allows those who are responsible for maintaining specifications to manage specification revisions. This screen allows you to manage the revisions of specifications during a project. You can get to this screen by opening the Spec Editor and selecting the Issue/Release Project Spec view.

B-04621

As a User of the .NET client I want to automatically get an update of the client automatically every time I open the client. Server and Client (server based) Installation as it is in Dortmund.

B-04621

Copy and Paste in Basic Grid should NOT add any string like COPY to the copied values

V-ID3550

cont'dSPRD

SP3D1001

SP3D1015

SP3D2001


45Page of




B-12944

comment No 5 - 4.5 does not automatically apply one possible TD during COF.

When we have only one applicable detail for a mandatory table the system should fill it automatically in COF dialog.

B-12946

Comment No. 5 4.10 No automatic Company Commodity Code generation

When we generate the Commodity code using COF dialog,the software should automatically create company commodity code and/or interface commodity code also depending on the project default ‘ZS_ADD_CCB’ setting.

Bug Fixes

Fixed the following defectsD-12940: 1.1 Exception is raised (Object reference not set to an instance of an object) in General Page when clicking on Component Area button.1.3 Trigger (M_SYS.M_SPEC_HEADERS_BIUR_TRG) is fired when publishing an Issued specification and saving the specification.

D-12945: 4.6 Coding on the fly does not consider the Pipe Material reference documentWhen the Project Default ZS_CC_COF is set to Y and a Material Reference Document is defined for a specific material in the material grid. For Main Component Group (Piping component group) when we click on the generate button the Pipe Commodity Code, (containing the specific material in the material grid),that is generated using COF does not consider the Document code 4.7 Coding on the fly –Non Pipe Material reference documentWhen material Reference Documents have been defined in the spec material Product form dependencies the commodity code (containing the specific material defined inthe spec material product form dependencies) that is generated using COF does not consider the reference Document code.

D-12941:

cont'dSPRD

46Page of





Removing the Template Indicator in S1001 brings error in case, data already exists.

D-12942:

User tries to insert a table detail in the Filter line and an error is highlight.

B-25788:User is given a provision to select a bolt diameter series in spec general page. If there are any Bolt components in component area then the LOV on From and To sizes will list Bolt NPS values from Bolt diameter Grid. For rest of thecomponents NPS values from Nominal diameter will be listed.

B-26104:An additional privilege (XS10G68) is needed for creating, modifying or deleting link table details in ¿ The Filter line¿ Single Coding on the Fly Dialog ¿ General Page Filtering for Valve Component Groups

B-26108:

For Valve Commodity Codes generated by COF when the user tries to open the LOV for Commodity Codes the wrongLOV comes up for manual spec items.

B-28974:

The font has been changed to Segue UI in the Component Area.

B-26109 :

If user chooses to create a new CC using button ‘New Code from’, a new window is opened where it is possible tocreate a new valve CC. But if user decides to abort the CC generation, clicking on button ‘Cancel’, the CC should not be created. Actually the new valve CC is created anyway

B-26110:

V-ID3550

cont'dSPRD

X


47Page of




If user chooses to open the LOV with the available valve Commodity codes for a Spec Item Line, the system showsthe list of applicable valve CC but the already selected CC is not highlighted to help userB-26107:Tag number & Document Code should be mandatory data in SCOF. Controlled by project default “ZS_TGDC_IN”.

B-26105:SPEC - COMONENT AREA – CODING ON THE FLY [Generate Valve CC]On the single coding on the fly for valves, we need a way tocall custom DLL to modify or add additional tables for commodity code and build the commodity code based on new details once we return from the procedure. We defineda new project default “ZS_SE_CCDL” to hold the path for the custom DLL.

Bug Fixes

Fixed the following defects

D-13411:

Flavio Comment No 7 - 5.1 COF existing CC not found.After clicking the ‘Generate’ button in component area, the system is not showing the existing commodity codes in result line grid during COF.

D-13605:

Script for Foreign Keys on M_SPW_FILTER_GRP_LABELS.

D-13009:Problem with Modify Code button in SCOF dialogue. Someunhandled exception is coming

D-13410:Filter Defaults are saved again and again in project setup when they are modified on the Spec

Support Items:

SI-MA-11332:

Error in Copying Geometrics is resolved.

SI-MA-11333:

cont'dSPRD

48Page of





Error resolved in saving the control status in the GeometricGrid.

SI-MA11224

License Issue SI.In SPRD PLUS once you start and close the SPRD PLUS it counts the license and not releasing even if our not logged into the session.This cause the problem to user if one user open the session and closed several times; then another user can’t login to the system.

Access Control for Spec Issue/Release Screen

Access controls for Spec Issue/Release Project Spec.¿ Read-Only Both the Master and detail blocks are set to read-only.¿ Deactivate User is given a message about the access control.

B-28774Improve Performance on Generate Button for large Component Groups.

B-26117Filtering default – Table LOV -The Table Detail LOV shows up less values for filtering defaults in project level.

B-08536: [Select CMS Idents in Spec Item Grid]

Specification shall have a mean to select CMS Idents as well. This functionality is only applicable for non-template Specs.

B-25379: LOV for filtering defaults.

Functionality to selectively copy the project specific filtering defaults as spec filtering defaults.

B–25383: Makarand Test cases and Documents.

V-ID3550

cont'dSPRD

XS10G062


49Page of





10980_2 Bug Fix

Created Examples of creating Data needed to prepare a Specification(pre-requisite data).

B- 29682:Integration of Test Cases and Global Flowchart in the help menu of SPRD Plus.

B- 29711(TK-50099): Error fixed in updating the package M_PCK_SPEC_REV in CASE.

B-08702¿ Section 1:- Resolved the client and server version.¿ Section 2:- Resolved the problem of Configuration in Administration.¿ Section 3.2:-Added new field Short Description in all Notes Screen.¿ Section 5.1,5.26.1,6.2 :- Added Note Type ,Short Description fields in all notes screen and user can now specify for which note type while creating a new note code¿ Section 6.3:- Made the Table Detail Links window resizable.

B-25378Added three new fields ProjectId, Short Description,Description in the Filterline Copy dialog.

Bug Fixes

Fixed the following defects

D-13415 :- Resolved the issue of missing table detail duringCIP generation.

D-13764The saving of wrong thickness in SpecAutogen table and the invalid nominal sizes check are resolved.

Only if Job Status = „NEW“ the user is able to modify “assign warehouses” and “assign workpackages”.

Cust.Ref.No.

TR-MA10980

cont'dSPRD

Site

S5006

Module

Module

Document Name

Document Name

Comment

Comment

50Page of




11093

11133_2

11181

11230

11230_1

11282

11299

11321

Change Request

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Corrected the position of current record indicator, enable property of fields sub.trans_qty, sub.trans_qty2 and visual attributes.

We have corrected the transformation calculation for update of an existing inventory item.

We have inserted a check for the temp table and the problem was solved.

The calculation of the quantity fields for reserved and issued quantities will not taken the highest issue status into account!

It will be calculated against the status which has the site quantities.

We have corrected the calculation and the query for the details of that fields.

We have corrected the message handling for C2001.

Changed unpost button activation (KEY-ENTQRY on forms level)

Prevent error message if mir is unposted and the overissue warehouse is the same as the issue warehouse.

We have added a check before posting a MTR. The new function check_before_post_mtr is in the package m_pck_site_custom.

CP-MA11093

TR-MA11133

TR-MA11181

TR-MA11230

TR-MA11230

TR-MA11282

TR-MA11299

TR-MA11321

cont'dSite

C300101

C1019

B2001LOVM

C4001

C2001

C2001

C2023

C2021

Module

Module

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

51Page of




11363

11392

11470

11481

11509

11522

11582

11625

25159

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

We have corrected the update of the actual_on_site_date for master item shipments.

We have corrected the on-error triggers to avoid dbms_error_text error.

We have corrected the trigger on the Short Description andDescription in C2031.

We have corrected the query for the attached setup in C4001.

The setup you have seen in C4001 was a setup for C4002 (m_setup_c4001s, c4002_ind = ‘Y’).

The restriction for query only setups c4002_ind = ‘N’ in C4001 was missing.

We have corrected the unpost direct issue procedure for revisions > 0.

We have corrected the query to display only items with onhand quantity > 0.

Change color of size-fields at the bottom of the screen. Added tool tip to Seq field.

We have corrected the query for the BOM Issued quantity and the detail window.

B-25159:

TR-MA11363

TR-MA11392

TR-MA11470

TR-MA11481

TR-MA11509

TR-MA11522

TR-MA11582

TR-MA11625

B-25159

cont'dSite

C2015

C2004

C3011

C2031

C4001

C2023

C2015

C1019

C2014

Module

Module

Module

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

52Page of





An item with a Heat number can be supplied with multiple Certificate Number.The System accept the entry of same heat number with different Certificate Numbers.

Changed Screens:=================C.10.04C.10.24C.20.01C.20.01.02C.20.03C.20.04C.20.05C.20.08C.20.15.01C.20.16C.20.17.01C.20.17.02C.20.25C.20.25.02P.70.72

Unique Key of following tables are enhanced with field certificate_number:==========================================================================M_HEATSM_HEAT_DETAILS

Following calls are delivered within this release:B-25695, B-25697

cont'dSite

C1004

C1024

C2001

C200102

C2003

C2004

C2005

C2008

C201501

C2016

C201701

C201702

C2025

C202502

P7072


53Page of




==================================================CR-MA7501 : added pred on site column to C.40.01 Window5

SI-MA11474 : changed background color of fields total overissue qty and oi on hand qty (C.20.22.01)

SI-MA11716 : no error message comes up if short desc and description were not filled in (C.20.12)

C.50.11 Site Inspection=======================

At the first block inventory receipts, the idents of all inventory receipts are displayed that have the locoation in a quarantine location (Project default ZC_QUA_LOC), not located in a scrap warehouse (Project default ZC_SCR_WH) and the material is already received (receiving report is posted).It is not allowed to do any changes on this block. Only the ident code is queryable and can be selected with a LOV.In this LOV all idents are shown that are located in quarantine location.

Warehouse:If the ident is located in one warehouse, the warehouse is displayed at field warehouse. Otherwise "several" is displayed and the background color is red.

Inspection Status:Values of this field are "Inspection Pending", "Passed" and"Failed".

Inspection Pending: - Passed is not checked and status is not filled in (approved date and approved by is not filled in) - Deviations is not checked and status is not filled in (approved date and approved by is not filled in) - Deviations is checked and status is filled in and tech.usable is unchecked and vendor actual value is not filled in

Passed: - Passed is checked and status is passed - Deviations is checked, vendor actual value is filled in, tech. usable is checked and status is passed

Failed:

cont'dSite

54Page of




- Deviations is checked, vendor actual value is filled in and tech. usable is unchecked - Status is failed or not applicable

ButtonsExecute CIP:This button calls the custom package m_pck_site_custom.site_inspection with input parameter ident.

Documents:This button calls the module D.90.21 Attachments to attach or open a document to the ident code.

Approve:The approve-button is only active if the inspection status is passed or failed.If inspection status is failed, a warning is displayed. If user wants to continue, the material is transferred to the project-defined scrap warehouse. Screen C.20.09.01 OSD for receivings is opened to enter data for ident if receiving comes from PO.

If inspection status is passed, a warning is displayed.If user wants to continue, the material is transferred to the original location.

At the second block Ident Values, Group, Name and Valueare displayed. These items are not updatable.

Work process:A. The displayed value is the same as on given document - checkbox passed has to be checked (approved date and approved by is filled in automatically) - checkbox deviations, vendor actual value and tech usable is protected against update - List item status has to be filled in and a certification can be entered (Certification date is filled in automatically) - Press approve button, if all ident values are correctly filled in

B. The displayed value is not the same as on given document - checkbox deviation has to be checked (approved date and approved by is filled in automatically) - checkbox passed is protected against update - Vendor actual value has to be entered - checkbox tech. usable can be checked (if is technically usable or not), list item status has to be filled in

cont'dSite

55Page of




25961

26446

26446_1

Change Request

Change Request

Change Request

and a certification can be entered (Certification date is filled in automatically) - if checkbox tech. usable is checked, the vendor actual value is copied to the value field.

---

SI-MA11607: Problem was, that the overissue warehouse and overissue location in the MIR header was exactly the same as the warehouse and location on the details. We have fixed this problem with the post bprocedure and it will work now with the reworked package

see B-25695_release_notes.docx for more details

B-25691:

It is possible to undo a manual transformation in screen C.10.19 (Window2) by pressing the "Undo Transform" Button.

The transform onhand qty must be greater or equal than transform qty.

Dependent on Project Default ZP_HIDE_MT, at screen C.20.01 in LOV of field Shipment Group (MRR Header), all Shipment Groups are shown whether Default is net to N.

If this default is set to Y, Shipment Groups that have only Master Tags, are not shown in LOV.

Dependent on Project Default ZP_HIDE_MT, at screen C.20.01 in LOV of field Shipment Group (MRR Header), all Shipment Groups are shown whether Default is net to N. If this default is set to Y, Shipment Groups that have only Master Tags, are not shown in LOV.

B-25691

B-26446

B-26446

cont'dSite

C2012

C4001

C5011

C1019

C2001

C2001

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

56Page of





30341 Change Request B-30341(SPMat backlog ID 85 Part II)

As a part of this user story, a new checkbox ‘Next Issue Status’ has been introduced in the screen ‘B.40.01 BOM Import’ under the section ‘Runtime Options’.

When this checkbox is checked:• The issue status specified in the screen ‘B.40.01 BOM Import’ is ignored.• The issue status specified in the uploaded file is ignored.• BOM positions are created with the next highest issue status available for the node into which these are being imported. Let us look at the various cases.Case 1: If the node has positionsThe issue status next to the highest issue status used for the existing positions is considered for the new positions being imported.Case 2: If the node has no positionsThe minimum issue status from the screen ‘B.10.08 Issue Status’ is considered for the new positions being imported.Case 3: If the next highest issue status is not foundA new issue status created as ‘AUTO’||next_order_seq (E.g.: AUTO123 where 123 is its Order Seq) is considered for the new positions being imported.Note:While determining the next highest issue status, the issue statuses having Usage as ‘Not Selectable and Exclude Best QTY’ in the screen ‘B.10.08 Issue Status’ are not considered.

Cust.Ref.No.

B-30341

B4001
