smartplant materials - hyundai...

SmartPlant MaterialsRelease Notes Service Pack 014-JUN-2010 Release

®

2011 (7.0.0)

1Page of

SmartPlant Materials® 2011 (7.0.0)

0 Release Notes Service Pack 54

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 - 2011, Intergraph Corporation. All Rights ReservedCopyright

2Page of



Release Notes Service Pack Version:0 7.0.0

MSC-No. Type Comment

10056

10441

10487

10507

10607

10615

10639

Change Request

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Checkbox 'Default' has been added in folder 'Configurations'in screen A.30.03. It is an indicator whether a configurationis to be used as default.

You can only mark one configuration per screen at most asdefault. If a configuration is marked as default this one is used when the associated screen is called and no configuration has been selected so far.

All mandatory fields must be filled before you can press button 'Create new Project' in screen A.60.02.01.

Assignment of documents was revised. Standard documents will now have standard_ind = 'Y', non standard documents will remain with standard_ind = 'N'.

Corrected the following problems in A5004:

When logged-in to a project, for an attribute set in Product Group- Layouts could be created at the project level .- Layouts created at the Product Group level were not visible.

In A.60.11 check included whether active alert users exist when the button ‘Start Alert’ is pressed.Error in internal alert processing fixed to avoid cursor error.

We have made a correction for the errormessage. Parameter HELP_DOC_URL is that one, which is not set, if user tries to open document and MAR-10219 comes up.

Screen will now also handle all package bodies correctly if they exceed 32k limit.

Cust.Ref.No.

CR-MA10056

TR-MA10441

TR-MA10487

TR-MA10507

TR-MA10607

TR-MA10615

TR-MA10639

Administration

A3003

A600201

A607021

A5004

A6011

A6063

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




10642

10652

10655

10657

10658

10660

10690

Change Request

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

A.20.49 Approval Sequence

The new project default ZP_RFA_CHG (default value = 'Y') controls whether an approval list is changeable even when the RfA checkbox is set. If ZP_RFA_CHG is set to 'N' and the RfA checkbox is set, the approval list cannot be changed (of course this does not apply to the Approved and Rejected checkboxes and also the Comment field). For users who already have approved within the approval list, this project default has no affect. In this case you cannot change anything except the fields Approved, Rejected and Comment.

From now on the source path for documents (screens D.10.11 and D.90.21) must be defined completely in the setup screen A.10.38. I.e. depending on the kind of destination the path must end with either '/' or '\'. So far '/' was automatically added in D.10.11 and D.90.21. This is no longer done.

Correct starting of alternate report screen depending on setting of project default ZX_REP_FMX and field ‘Alt. Start Rep’ in A.30.01.

Correction of processing for nominal trigger data.

Due to the changes in Oracle DB11, table m_sess_rep_infoshas been increased in order to match the changed data length requirements.

Correction of background colour for NLS window.

Theme handling for block prompt revised

CR-MA10642

TR-MA10652

TR-MA10655

TR-MA10657

TR-MA10658

TR-MA10660

TR-MA10690

cont'dAdministration

A6037

A1038

D1011

D9021

A3001

A60R01

A5001

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

4Page of




10695

10695_1

10700

10702

10838

10883

10942

10997

24326

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

Bug Fix

Bug Fix

Change Request

If a user is assigned to different roles for an alert, then the email is sent only once.

Alerts are only processed by one dbms job if multiple jobs are running parallel to prevent the sending of duplicate emails.

Hint Texts with 'MARIAN' deleted from fields: User, Locked

Various messages revised (delete MARIAN) and hint text for KILL SESSION button corrected

In A.60.10 you can now define queries for direct link form P5001 with the column base_poh_id (from m_po_headers).This will enable the system to select the correct agreementin P.50.01 when the ‘Call’ button in A.60.12 is used.

The copy process that is started when creating a new language in screen A.10.01 has been reworked and improved to avoid unnecessary error messages.

User friendly message for constraint violation of SPWTID_D_FK.

The background color of the project information field has been corrected.

B-24326 (Automatic User Logoff)

TR-MA10695

TR-MA10695

TR-MA10700

TR-MA10702

TR-MA10838

CR-MA10883

TR-MA10942

TR-MA10997

B-24326


A5021

A6012

A6011

A2005

A6082

A6010

A1001

A5002

A1052

P7081

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

5Page of




5606_1 Change Request

The main purpose of this user story is to automatically log off the user from Smart Plant Materials application after a specified idle time so that acquired licenses can be released.

This idle time (in minutes) can be specified against the newDBA setting ‘IDLE_TIME’, created in the screen ‘A.60.04 DBA Settings’, with a value set to 0 by default, which indicates that the idle time allowed is unlimited.

Specifying a positive value for this Setting indicates that the user is allowed to stay idle for the specified number of minutes. For example, if a value 6 is specified, the idle time allowed is 6 minutes.

After the idle time is crossed, the corresponding sessions are marked ‘SNIPED’ in v$session. Now, when the user tries to perform any action in the application, he/she will bealerted to re-login.

If the user wants to kill these sessions automatically without his/her interference, the DBA has to set SQLNET.EXPIRE_TIME to a value in minutes to enable to dead connection detection.

Note:

Any change in the value for this DBA Setting will come intoeffect only when:• The user re-logs in.• The parameter resource_limit is set to ‘TRUE’.

Extended table 'Project':- PROJ_MANAGER VARCHAR2(256 CHAR)- PROJ_ENGINEER VARCHAR2(256 CHAR)- PROJ_TECHNICIAN VARCHAR2(256 CHAR)

These are fields with free format text. Many companies require certain information about persons in charge.This information can be added from now on per project.

- PROJ_STATUS VARCHAR2(1 CHAR)

PROJ_STATUS (Project Status) can either be Open, Close

B-05606


A6063

Module Document Name Comment

6Page of




9176

9799

9976

Change Request

Change Request

Change Request

oder „nothing“.

After creation of a project, the icon on the message telling that a project was created successfully came up in "error" style. This did not match with an successful creation. We have changed the icon to the appropriate "information" style.

After button 'Include all Disciplines' is pressed, the newly copied data for the appropriate combination of user/project/product group/discipline and role is requeried.

A.20.49 Approval Sequence

The button <Reverse Approval> gets active immediately after one user within the approval list has approved or rejected.

New project default:

ZP_STOPREJIf this project default is set to 'Y' (default value), the approval stops after a user within the approval list has rejected. If the project default is set to 'N', the next user willget an invitation to approve even if the last user rejected.

CIPs :

Within the package M_PCK_MAIL_CUSTOM you find the new procedure SEND_NOTIFICATIONS as well as the two new functions GET_REVERSE_SUBJECT_TEXT and GET_REVERSE_BODY_TEXT. Here you can change the email text for all emails within A.20.49 Approval Sequence.

P.50.07 Maintain Agreements

New privilege:

SM APPROVAL

CR-MA9176

CR-MA9799

CR-MA9976, 10113


A200102

A600201

A200603

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

7Page of





10397

10397_1

Bug Fix

Bug Fix

If this privilege has been assigned you will be able to approve a subcontract in screen P.50.07 Maintain Agreements.

New project defaults:

ZP_APRBO Default approval template used for the approval of blanket orders. The approval template is used to populate the approval sequence when setting checkbox 'Ready for Approval' in screen P.50.07, folder 'Agreement'. Furthermore the first person in the approval template/sequence will be informed by email that the agreement is ready for approval.

ZP_APRNCDefault approval template used for the approval of notices ofcommitments. The approval template is used to populate the approval sequence when setting checkbox 'Ready for Approval' in screen P.50.07, folder 'Agreement'. Furthermore the first person in the approval template/sequence will be informed by email that the agreement is ready for approval.

We have corrected the trigger mutation on cascade delete.

This patch implements the necessary changes for TR-MA-10397.The revised functionality affects screens B.20.01, B.20.03 and B.20.01.11.It is now prevented that BOM positions with zero site quantities on BOM list positions but with issue quantities existing on site get deleted.This data could be produced by BOM loads for positions that had site quantities in a lower issue status and are missing in the highest issue status.Also unposted issues would cause the same behavior of

Cust.Ref.No.

TR-MA10397

TR-MA10397


E&PI (BOM)

A2045

A2046

A2049

P5007

B2001

Module

Module

Document Name

Document Name

Comment

Comment

8Page of




10745

10825

10856_1

13061

Bug Fix

Bug Fix

Bug Fix

Change Request

unwanted deletions.Trying to delete a BOM structure will additionally list all records that prevent deletion in the log file.

When copying a configuration from a template it could happen that the new configuration was not named properly.This was because the name generator did not look up the the complete project for the name already existing. The result was that the primary key was used as a name if the generated name already existed.

Changed the sorting order of the block 'BLKATTRIB' in B2003.

This patch corrects the button handling of screen B.40.12 in case of locked master records.

B-13061 (Manual BOM Positions with incomplete specs)

The following are the changes in ‘B.20.01 Edit BOM’ and ‘B.20.03 Adv. Maintain BOM’ with respect to spec handlingin BOM position windows:

1. A new project default ‘ZB_IN_SPEC’ has been introduced. This provides the default value to the new switch (checkbox) ‘Use Incompl. Specs’.

If this checkbox is checked then• Specs which do not contain Spec Items, also, can be used in creating a BOM position. • All Short Codes, Option Codes from ‘S.10.08 Short Codes’ independent of the specified Spec can be used in creating a BOM position.• All Sizes from ‘S.40.01 Nominal Sizes’ for the nominal size table (from Spec Header Geometrics) in the specified Spec can be used in creating a BOM position.• Once a Short Code is filled, the user is forced to specify the corresponding Sizes.

TR-MA10745

TR-MA10825

TR-MA10856

B-13061

cont'dE&PI (BOM)

B2001

B200111

B2003

B1041

B2003

B4012

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

9Page of




15277

4874

4905

Change Request

Change Request

Change Request

2. Once a Short Code is filled, the field ‘Unit’ will be updated with the corresponding Quantity Unit.

3. The user can include a new configurable field into the BOM views which displays the ‘Short Code Short Desc’. This new field is available only for the multi-positions.

The user can now assign issue status at the BOM node level. Once a BOM Node is assigned an issue status at the node level, the following will happen:• All the child of the BOM nodes will be assigned with the same issue status • The existing manual positions for the node and its child nodes will get copied with the assigned issue status at node level.

However, it will not be possible to assign the issue status at node level if:-

• The existing manual positions for the node and its child nodes have an issue status higher than the one assigned to the node.

• The existing manual positions for the node and its child nodes have one or more positions having reserved quantity or issued quantity greater than zero or have un-posted MIRs.

In previous version of SPMat it was a problem when importing a quantity of -1 in BOM loads.Failed unit-to-unit conversions would not be raised properly in this case.This has been solved now.

This installs B-04905 Unique Tag Numbers.

In former versions of SPMat - more than one ident could exist for the same tag number,- subsequent BOM loads into the same Issue Status couldnot guarantee to assign the same ident for a tagged item

B-15277

B-04874

B-04905,TR-MA10962

cont'dE&PI (BOM)

B1006

B2001

B2003

B2001

B200105

B200106

B2003

Module

Module

Document Name

Document Name

Comment

Comment

10Page of





6463

8424

10555

10555_1

Bug Fix

Change Request

Bug Fix

Bug Fix

loaded.

Changes for 7.0.0

- After creating an ident for a tag number the first time this information is now stored in a new background table.- BOM loads, requisition an PO line items now refer to the new table to check uniqueness.- Project Default ZB_DUTAB has been removed.

Correction processing of find ident for equal branch.

The following are the changes done in ‘B.20.01 Edit BOM’ and ‘B.20.03 Adv. Maintain BOM’ as a part of this CR.

A new project default ‘ZB_DUP_LP’ has been introduced. This project default controls the duplication of manual BOMpositions with the same Ident, Unit, Tag Number and Position Attributes.

If this project default is set to ‘Y’ (default), then duplicate manual BOM positions are allowed.If this project default is set to ‘N’, then duplicate manual BOM positions are not allowed.

Please note that only those Position Attributes, which are used in the project defaults ZX_BOM_UK1..4, will be a partof this duplication check.

Attribute values are now displayed and saved correctly when entered via a core workflow screen. So far this did notwork in all cases.

Attributes in core workflow screens are again handled and

Cust.Ref.No.

TR-MA6463

CR-MA8424

TR-MA10555

TR-MA10555

cont'dE&PI (BOM)

E&PI (REQ)

B2001

B2003

P5007

B2001

B2001

B2003

R3001

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

11Page of





10571

10966

10991

13056

10120

Bug Fix

Bug Fix

Bug Fix

Change Request

Bug Fix

processed correctly.

When the field Origin displayed in the scrolled area, wrong LOV was displayed. This issue is fixed. LOV for the field Origin displays data from A.10.33 Origins.

This patch is to change field 'Cause' of message MAR-25323 to 'Field "ROS Date" in screen R.30.01, Window 2 has not been filled for all line items.' for NLS ID 1 and an according translation for NLS ID 2.

Under certain circumstances you can get error message ORA-01012: fetch out of sequence, ORA-06512: at “M_SYS.M_PCK_REL_TO_PROC” when you press button Release and the release context is not set to “All Quantities”. This installation fix this issue.

see documentation

Customer Menu was overworked, symbols and icons are deleted, functionality was adjusted.

Cust.Ref.No.

TR-MA10571

TR-MA10966

TR-MA10991

B-13056

TR-MA10120

cont'dE&PI (REQ)

General

R3001

R3001

R3001

R3001

R1041

R1046

R1047

R1048

R1049

R1051

R2001

R3005

R4011

S1001

MENU

B-13056-01.RELEASE NOTES.DOC

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

B-13056-01.RELEASE NOTES.DOC

12Page of




10617

10648

10688

10714

10876

10954

11010

4907_1

8902

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

Bug Fix

Bug Fix

Change Request

Change Request

Menu functions: CLOSE ALL and CLOSE (File menu) are set inactive in future, to avoid confusion, presenting senseless menu functions.

Excel templates may now contain macros; execution of macros during processing is disabled.

Theme handling overworked

Enabled functionality to handle themes

It is now possible to prevent the upload of files in P2003 having names containing special characters.The default installation will exclude the & character. The list of excluded characters can be maintained by adding or removing records from table CG_REF_CODES with the following values:RV_DOMAIN: INVALID_FILE_CHARACTERRV_LOV_VALUE: Character which is not allowed in filenames

The display indicator in screen A.30.03 is now also taken into account when working with stackable roles.

The Supplier Entry has undergone some performance tuning measures in order to reduce response time after pressing the 'Logon' button.

Setting of version to 7.0.0

This installation fix issue regarding migration existing formsto Oracle Forms 11G: Some database objects cannot be used in forms under Release 11G.

TR-MA10617

TR-MA10648

TR-MA10688

TR-MA10714

CR-MA10876

TR-MA10954

TR-MA11010

B-04907

V-ID8902

cont'dGeneral

MENU

P2003

PT2001

A3003

A2045

A2046

A2047

A2049

A600103

P1024

P2001

P2004

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

13Page of




MSC-No.

MSC-No.

Type

Type

Comment

Comment

10474

10646

10799

10096

Bug Fix

Bug Fix

Bug Fix

Change Request

Prompt "MARIAN Settings" is changed to "SPMat Settings"

The version will be taken from the MTI installed version and will be displayed in the main page of MTI application.

Removal of obsolete block item entries for SAP2001.

Modifications to screen P.70.74 Packages:

• A new project default ZP_PCK_DIM has been introduced the value of which is used as default dimension unit for newly created packages (CR-MA10096).• Deleting obsolete preliminary packing via button 'Delete Obsolete PPLs' now also takes parent tags into account once all of their respective detail tags have been removed from preliminary packages (CR-MA10663). Of course, this also applies in cases where button 'Delete Obsolete PPLs' is invisible because of ZP_PPL_DEL = 'Y' and the preliminary packing clean-up is triggered by the approval of release notes.• The error message that appeared when the user modified the weights of a package such that its gross weight was less than its (calculated) net weight has been reduced to a warning, i. e. the weight values will now be accepted upon commit (CR-MA10958). The alert window showing the

Cust.Ref.No.

Cust.Ref.No.

TR-MA10474

TR-MA10646

TR-MA10799

CR-MA10096.10662,10663,10958

cont'dGeneral

Integrator

MSCM

P3027

S1008

SM1022

SM2011

SM3002

SM3005

SM3008

SM4001

SM4002

SP3D1014

IN1001

SAP2001

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

14Page of




10102 Change Request

warning message contains the well-known 'Show never again' button that may be hit for suppressing this warning in the future.

Modifications to screen PT.20.01 Traffic Tree:

• When deciding on oversize/overweight of a preliminary package, its quantity is no longer taken into account (TR-MA10662).

Modifications to screen PT.20.21 Preliminary Packages:

• A new project default ZP_PCK_DIM has been introduced the value of which is used as default dimension unit for newly created packages (CR-MA10096).• When deciding on oversize/overweight of a preliminary package, its quantity is no longer taken into account (TR-MA10662).• The error message that appeared when the user modified the weights of a preliminary package such that its gross weight was less than its net weight has been reduced to a warning, i. e. the weight values will now be accepted upon commit (related to CR-MA10958). The alert window showing the warning message contains the well-known 'Show never again' button that may be hit for suppressing this warning in the future.

SM.40.02 Change Order Requests

To be able to decrease subcontract cost and schedule in P.50.07 Maintain Agreements you can enter negative values for Material Total, Labor Total (by doubleclicking on field Labor Total and entering negative values for Hours or Unit Rate), Construction Equipment Total, Consumables Total and Others Total. After you have assigned that COR to the agreement you have to adjust and remove the negative values in P.50.07 Maintain Agreements folders Line Items and Schedule of Values. Otherwise you neither can approve the agreement nor leave the screen.

P.50.07 Maintain Agreements

Folder Line Items:If there exist negative values for the line items generated by

CR-MA10102

cont'dMSCM

P7074

PT2001

PT2021


15Page of




10214

10340

Change Request

Change Request

a COR, you have to adjust and remove these values by setting the value 0 or by deleting the line item after the negative values have been applied to other line items. Otherwise you neither can approve the agreement nor leavethe screen. Folder Schedule of Values:If there exist negative values generated by a COR, you have to adjust and remove these values. Otherwise you neither can approve the agreement nor leave the screen.

Note!We strongly recommend NOT to delete the line items with negative values after you have adjusted the negative values to other line items. In that case the COR will be available again in SM.40.04 COR Workload to create another CO. Just leave the line items with values 0 instead of negative values.

Modifications to screen PT.20.01 Traffic Tree:

• In the 'Actual' branch of the traffic tree, means of conveyance (MOCs) are now associated with date ranges in a slightly different way:A MOC that represents the end of a transport chain – i. e. its unloading point is equal to its delivery designation – is now shown in the date range corresponding to its ATA (or, if this is not available, ETA) date (instead of its ATD/ETD date, which was taken into account before).The same applies to 'Workload' nodes created by MOCs that do not represent the end of a transport chain. This allows for easier identification of the month in which the next MOC has to be booked.

Modifications to screen P.20.01 Suppliers/Subcontractors:

• The 'Level 2', 'Level 3', and 'Level 4' fields (cmp. P.10.25 Question List) have been added to tab folder 'Qualification Questions' in window 2 to facilitate running meaningful queries in this block (CR-MA10340).

Modifications to screen P.20.02 Login Requests:

CR-MA10214

CR-MA10340,10328

cont'dMSCM

P5007

SM4002


16Page of





• When attempting to close the screen after having committed new or updated data to the database without finally pressing button 'Submit', an alert will pop up now reminding the user to press the 'Submit' button in order to file the changes. It is then up to the user to decide upon leaving the screen nevertheless or pressing button 'Submit' prior to exiting. Of course, this reminder only shows up if the screen is called via eSupplier Portal (CR-MA10328).

Modifications to screen P.20.03 Questionnaire:

• The new reminder alert described above for P.20.02 has also been added to P.20.03 (CR-MA10328). However, the alert will only pop up if all mandatory questions related to either branch "Company Profile" or "Qualifications" have been answered (i. e. the 'Submit' button is enabled).

Modifications to screen P.20.01 Suppliers/Subcontractors:

• Similar to tab folder 'Qualification Questions', an iconic button has been added to tab folder 'Company Profile' indicating the availability of uploaded documents with a green background color. Pressing the button for a specific question will then open the 'Documents' window that allowsfor viewing all documents that have been uploaded in addition to the answer provided to that question (CR-MA10414).

Modifications to screen P.20.02 Login Requests:

• A new checkbox labelled 'Submitted' has been added to the 'Login Requests' block. It allows for selective queries forlogin requests that have been submitted already (checkboxticked in enter-query mode) or that have not been submitted yet (checkbox ticked twice in enter-query mode)(CR-MA10411).


• The material/work group multi-selection LOV (P.20.03 Window 8) has been revised completely. It now displays a tree-like structure where the top-level nodes represent the material/work group types that can be expanded to show all material/work groups of the respective type that are available for selection by the user (CR-MA10410).

CR-MA10410,10411,10414,10416

cont'dMSCM

P2001

P2002

P2003


17Page of





• The company selection window that pops up initially when calling this screen from the main menu has been enhanced by a radio group that allows for predefining restrictions on the companies displayed by the list of values (LOV) of the 'Company' field with respect to the specific level of completion of the qualifications part of the questionnaire. Thus, by selecting the appropriate option theuser may focus on companies that did not submit their qualifications yet, or on companies that have submitted their qualifications already. The LOV also indicates the availability of submitted qualifications for each company (CR-MA10411).

• The 'Answers' block has been provided with an iconic button indicating the availability of uploaded documents with a green background color. The button can be pressed to launch the Upload/View dialogue (alternatively the user can press the 'Upload Files' button for this purpose) (CR-MA10416).

Modifications to screen P.20.04 Company Profile:

• A radio group has been added to the 'Company' block to allow the user to decide whether companies having submitted their company profile already (original behavior) or companies that did not submit their company profile yet shall be queried (CR-MA10411). In case of the second alternative being chosen, the user will be able to view the unsubmitted company profile, but of course without the possibility to approve or reject it. Choosing the first alternative yields the original behavior of the screen (i. e. the latest submitted revision of the company profile is displayed), however, a checkbox will appear in the 'Company Profile' block indicating the availability of a newerrevision of the company profile still being worked on and therefore not submitted yet. The user may then tick this checkbox in order to glance at the revision being worked on, but again without the possibility to approve or reject it.

The 'Engineering Requisition' field in the header block of window 2 of screen P.60.03 Requisitions Planning has been replaced by a drop-down list that allows for easily switching between all planned requisitions you have previously queried in the main window of the screen (prior to opening window 2). This is especially useful with respect

CR-MA10467

cont'dMSCM

P2001

P2003

P2004


18Page of




10472

10549

10556

10562

10573

10600

Change Request

Change Request

Bug Fix

Bug Fix

Bug Fix

Bug Fix

to milestone planning across multiple requisition links.

You can now apply changes in screen D.90.21 even if called from the latest approved agreement if the next agreement supplement (not yet approved) already exists.

Please note that changes that are done under these circumstances must also be applied to the supplement notyet approved. Otherwise the changes will get lost for the next supplement(s).

The call of CIP m_pck_po_custom.delete_order has been moved from a trigger into a package to allow customers to read table m_po_headers.

Prior to this change you could not retrieve data from that table but received an error message instead ("ORA-04091: table M_SYS.M_PO_HEADERS is mutating, trigger/function may not see it").

Data are now found in screens such as P.30.11 and P.50.01 even after changing the project by pressing button 'Set Project/Discipline' in the menu.

Data are available again in screen P.70.72.

Startup processing for default template corrected to preventerror ORA-6502.

Inquiry supplements can now also be created via screen P.30.03 if parts of the involved requisition can already be found on the previous inquiry supplement.

CR-MA10472

CR-MA10549

TR-MA10556

TR-MA10562,10591,595

TR-MA10573

TR-MA10600

cont'dMSCM

P6003

P5007

MENU

P3011

P5001

P7072

P3024

P3003

Module

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

Comment

19Page of




10611

10633

10656

10673

10694

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

When creating agreements from inquiries (option 'Create from Inquiry' in screen P.30.01) only quantities that are outstanding are taken into account. This change is of interest if you create your requisitions for PO by pressing button 'Create PO Req' in screen R.30.01 (and not in P.30.22).


• When being called from the Supplier Entry, the screen now displays an additional reminder to submit the anwers provided in Window 2 when the user tries to close that window (CR-MA10633). The reminder distinguishes between answers related to the Company Profile part of thequestionnaire, and answers related to the Qualifications part. However, in order to avoid annoying users, each reminder does not show up more than once per session, and, of course, only as long as the respective part of the questionnaire has not been submitted.

• The problem reported as TR-MA10579 occurred in cases where a document was uploaded while there were still pending changes in the 'Answers' block (i. e. button 'Upload Files' has been pressed without saving answers first). Although uploading the document also committed thechanged answers to the database, the relation between that document and the associated answer could get lost if the answer had been provided for the first time. The screen now ensures that changed answers are available in the database by the time when a document is uploaded.

Attributes can now again be modified in screen P.70.72 in all cases.

Lower-tier subcontracts can now be entered and modified again in screen SM.20.11.

The Excel import now considers the columns RPCKI_ISH_POS and RPCKI_ISH_SUB_POS.The item shipment ID now will be written again to column 256.

TR-MA10611

CR-MA10633,TR-MA10579

TR-MA10656

TR-MA10673

TR-MA10694

cont'dMSCM

P3001

P3022

R3001

P7072

SM2011

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

20Page of




10717

10718

10720

10728

10742

10743

10773

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

Change Request

The tag number coming from the LOV for blanket order line items is now kept.

Queries can now be performed in screen P.50.09 for all types of agreements.

The progress values are now displayed correctly in screen P.60.05.

The background color of field 'Ident Short Description' has been corrected in screen P.70.51.

The database views used by screens P.70.71 and P.70.72 have been reworked to achive better performance. The final results have been tested on several databases, with perceptible reduction of response times of the two screens.

To suppress the alert "Project default for template not set."in screen P.50.07 you can now either unsubscribe message MAR-30344 or you can reset the warning indicator for this message in screen A.60.31.(This message appears when you set checkbox 'Ready for Approval' and the project default for the corresponding approval template - ZP_APRBO, ZP_APRPO, ZP_APRNC,ZP_APRSM - is not set.)

Contractual data are now kept in case an item shipment has been assigned to a release note. So far this was controlled by the setting of project default ZP_ISH_QTY and was therefore not done necessarily for all change orders.

TR-MA10717

TR-MA10718

TR-MA10720

TR-MA10728

TR-MA10742

CR-MA10743

CR-MA10773

cont'dMSCM

P7074

P5007

P5009

P6005

P7051

P7071

P7072

P5007

P5007

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

21Page of




10804

10816

10858

10869

10877

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

SM.20.11 Subcontract Administration Folder 'Invoice':After the invoice has been approved you could not mark thecheckbox "Paid" and enter values in the fields "Paid Value"and "Invoice Actions".This issue is fixed.

Folder 'Closeout Checklist':After the closeout item has been approved you could not mark the checkbox "Ready for Close".This issue is fixed.

SM.30.06 Turnover Package

If you assign a new agreement for a turnover package and then enter a turnover event, you could get an error while saving the new values.This error is fixed.

Import of split tags for Expediting will now update data correctly.

Administration settings for screen P.50.07 have been corrected to avoid error messages.

In cases where reports were launched via screens that had been called from the Supplier Entry, the determination of the user name appeared to be erroneous. This has been corrected.

Furthermore, P.20.03 has been slightly modified to ensure that the value for the 'company_id' report parameter is taken from the appropriate block of the screen.

Performance in tab folders 'Company Profile' and 'Qualification Questions' of P.20.01 Suppliers/Subcontractors has been improved significantly.

TR-MA10804,10805,10806

TR-MA10816

TR-MA10858

TR-MA10869

TR-MA10877

cont'dMSCM

SM2011

SM3006

P7071

P5007

P2003

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

22Page of




10887

10893

10898

10900

10937

10952

10977

10979

Change Request

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

Change Request

Country of Origin and Manufacturer are now taken over fromthe quote when adding a quote summary to an agreement via button 'Add ...' in screen P.50.07.

Data are now visible again in screen P.70.62.

For the Excel Bid import for quote detail the tag number is not required anymore. An empty tag number will be interpreted as value ‘---‘.

Excel BID load now sets the logfile name during import so that the logfile can be viewed using the ‘View Online Log’ button.

MARIAN replaced with SPMat in spool scripts

When transferring alternates/options (e. g. upon creation ofa change order), the original order sequences are now preserved where possible.

When P.20.03 Questionnaire is called from the Supplier Entry and the user tries to close Window 2, the submission reminder now only pops up if all mandatory questions of the questionnaire branch the user is currently working on (i. e. company profile or qualifications) have been answered already.

The display of the position number information has been improved for quote details in case more than just one requisition line item is associated with a quote detail.

CR-MA10887

TR-MA10893

TR-MA10898

TR-MA10900

TR-MA10937

TR-MA10952

CR-MA10977

CR-MA10979

cont'dMSCM

P2001

P5007

P7062

P3024

P3024

PDMS1002

P5007

P2003

P3022

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

23Page of




10982

11024

13563

14792

Bug Fix

Change Request

Change Request

Change Request

Updating attribute values in screen P.70.72 does not raise error messages any longer when the screen is called from screen P.70.61.

Saving data in screen P.50.07 has been tuned for some cases. This can be experienced especially when working agreements with thousands of lines.

Modifications to screen P.10.33 Other Costs:

• A default indicator has been added on tab folder 'Other Cost Sets' for both set types (delivered site costs/price comparison costs). Marking an other cost set as default will cause this set to be preselected for the other cost set of the respective type that can be specified in the data selection window of screen P.30.26 Awarding II.

Modifications to screen P.30.26 Awarding II:

• In the data selection window that precedes the actual awarding, the other cost sets that may be specified for delivered site costs and price comparison costs will be predefined by the respective other cost sets marked as default in P.10.33 Other Costs. If no default has been defined, the corresponding field will be left blank initially.• The 'Items' tab folder will now show one more line per detail tag containing its ident short description.• The 'Summary' tab folder now highlights inquiry positions for which at least one bidder has created detail tags with an orange-like background color (similar to P.30.25 Awarding). The user may then double-click on the colored fields for directly accessing Window 4 of P.30.25 Awarding in order to re-align the detail tags for facilitating comparisonof the different bids.

In screen P.30.21 Prepare RFQ you can now set the quantity to be quoted in folder 'Requisitions'. So far the increased quantity of a requisition line item was used as quoted quantity. This is now the default for the new field 'Quote Quantity' which is now used as quoted quantity for

TR-MA10982

CR-MA11024

B-13563

B-14792

cont'dMSCM

P7061

P7072

P5007

P1033

P3025

P3026

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

24Page of





the quote summaries. So you can now influence before approving an inquiry the quantity to be quoted. Up to now this had to be done after all quotes had already been created.

Moreover a multi-selection LOV has been implemented in screen P.30.21 for the assignment of requisitions to an inquiry.

Depending on the setting of project default ZP_IRCAPRQ data can be changed at any point in time and by every useror not.

If ZP_IRCAPRQ is set to 'N' (default) data can be changed at any time by any user. An approval of the IRC is not required to continue the workflow, i.e. to place an item shipment on a release note.

If ZP_IRCAPRQ is set to 'Y' only users that have been assigned to the current order as inspector (screen P.70.73)can create and modify IRCs as long as indicator 'Ready for Approval' has not been set.Once the IRC has been marked as ready for approval no one can apply changes to the IRC. In the next step the IRCmust be approved by pressing the corresponding button. Privilege 'IRC APPROVAL' is required to be allowed to do so.After an IRC has been approved only users that have been assigned to the current order as expediter (again screen P.70.73) can modify the IRC. Moreover the item shipments of an approved IRC can then be placed on a release note.

To reverse the approval of an IRC you also need privilege 'IRC APPROVAL'.

When setting checkbox 'Ready for Approval' an email is automatically sent to the expediter(s) of the order to inform him (them) that the IRC is ready for approval.For the system to be able to send out this mail you need to set up an email template in screen A.10.51 for template type 'EXPEDITING' and assign this template to project default ZP_EMT_IRC.

Please note that you have to work with screen P.70.72 if you want to work with ZP_IRCAPRQ = 'Y'. Screen P.70.75 does NOT support this feature.

B-14799

cont'dMSCM

P3021

Module

Module

Document Name

Document Name

Comment

Comment

25Page of




14799_1 Change Request A.60.61 User Preferences

The behavior of maintaining the user preferences changed.

If you are logged in without SUPER USER rights you can only change your own preferences. This is the behavior as usual. If you are logged in as a SUPER USER you can change allpreferences of all users. In this case you can enter a queryand use all fields for your search condition. Additionally while entering a query the field 'Preferences forUser' offers a list of values with all available users.

P.70.73 Order Reference

Project Default ZP_VPAPRQ

If the project default ZP_VPAPRQ is set to 'N' (default), all users can change the data of the vendor progress and approve it.If the project default ZP_VPAPRQ is set to 'Y', the approvalfor the vendor progress must be executed by the inspector,who sets the 'Ready for Approval' checkbox (RfA) and the expediter, who must approve the vendor progress. Before the vendor progress is marked as ready for approval (RfA), the inspector, entered in the folder 'Order Reference', can change any data. After the checkbox RfA was set, all data are protected and the expediter, also entered in the folder 'Order Reference', gets an invitation via email to approve thevendor progress. To be able to approve or to reverse the approval he must have the privilege VENDOR PROGRESS APPROVAL. After the vendor progress is approved, only the expediter can change the data.

Project default ZP_EMT_VP

With this new project default you are able to assign an email template when an email will be sent to the expediter after setting the 'Ready for Approval' checkbox in the folder 'Vendor Progress'.

First define an email template in A.10.51 Email Templates for the invitation to approve the vendor progress. After that go to screen P.70.73 Order Reference and assign this

B-14799

cont'dMSCM

P7072


26Page of





template to ZP_EMT_VP in A.60.63 Valid Settings as usual (or use A.20.12 or A.20.13 to assign the template).

P.70.72 Expediting Details

Project default ZP_EMT_IRC

With this new project default you are able to assign an email template when an email will be sent to the expediter after setting the 'Ready for Approval' checkbox in the folder 'IRCs'.

First define an email template in A.10.51 Email Templates for the invitation to approve the IRC. After that go to screenP.70.72 Expediting Details and assign this template to ZP_EMT_IRC in A.60.63 Valid Settings as usual (or use A.20.12 or A.20.13 to assign the template).

B-19711, CR-MA10355, CR-MA10356, CR-MA10357)

P.20.02 Login Requests

If an eSupplier wants to create a login request and tries to leave the screen without entering and saving all data completely he will get a warning message that all data entered so far will be deleted after the screen was closed.

The eSupplier now will get also an email with user ID and password after the password has been changed, not only after a new password has been created.To maintain the email message text for a changed password there is a new CIP in the package M_PCK_COMPANY_CUSTOM called CHANGED_PW_USER_EMAIL_TEXT.

After a new login request was submitted, the eSupplier gets a message, whether he wants to continue with the next step, which opens screen P.20.03 Questionnaire (button 'Yes') or whether he wants to go back to the Login screen (button 'No'). This is only applied to the approval processes 1-Step and 2-Step.

B-19711

cont'dMSCM

A6061

P7072

P7073

Module

Module

Document Name

Document Name

Comment

Comment

27Page of




4897

5595

Change Request

Change Request

eSuppliers will now first aquire MSCM-SUPP seats. Only ifthere is no more supplier seat available it will take MSCM license.

Integration of SDTA - Backlog Item B-05595

Some features have been added to screen P.70.81 VDR Submittal and Status.

With project default ZP_VSSMODE you determine in whichmode screen P.70.81 is started.If you wish to work with a multi-record layout you have to set this project default to 'MULTI' (default).If you prefer to start with the single-record layout getting more information at first glance you should set this project default to 'SINGLE'.

When double-clicking on field 'Agreement Number' when starting in multi-record mode a second window is opened containing mainly contact and address details on the agreement.When double-clicking on either field 'Agreement Number' or'Pos' when starting in single-record mode the multi-record window is opened. Depending on the field selected for the double-click you will either see the VDRs of all positions of the agreement (and the agreement itself if VDRs have beenassigned on header level) or only the VDRs of the selected/current position.

The number of documents that are available in screen P.70.81 VDR Submittal and Status depends on the setting of project default ZP_VSS_DOC.If it has been set to 'ALL' (default) all documents stored in D.10.11 are available.If the project default has been set to 'AGREEMENT' you can only select from the documents that have already beenassigned to the agreement or any of its line items.

An approval code and a returns button have been added. The approval codes are set up in the new screen P.10.71. When pressing the returns button first CIP m_pck_vdr_custom.return_transmittal is called and then the report screen for that report that is given by CIP m_pck_vdr_custom.returns_report. In a standard installation report P.70.R.88 is returned by this CIP.For example you can use this button to send an email to the supplier informing him that some documents have to bereworked.You should select at least one VDR to that a document

B-04897

B-05595

cont'dMSCM

P2002


28Page of




has been assigned before you press this button.

If you double-click on field 'Distribution Category' screen A.10.52 is called for the current distribution category.

Field 'Reviewer' has been added to the details block for distribution categories.

In contrast to all other fields related to distribution categories and their details the value of this column is given by the distribution category that has been marked as master.

Only one distribution category per project can be marked as master. This information is only of interest with respect to field 'Reviewer' in the distribution category details.

Whenever the reviewer of the master is updated this value is taken over to ALL distribution categories of the current project with the same email.

If data are copied from another project (either by copying the procurement setup or by pressing the copy button at the top of this screen) the reviewer is NOT taken over from the source project but from the master distribution categoryof the current (= target) project.

If no master is available the field remains empty.

There is no further functionality or workflow behind this field. It has been introduced in connection with screen P.70.81. If a VDR document needs to be reviewed you can enter the persons responsible for this review here. By assigning a distribution category to a VDR and by double-clicking on the corresponding field in screen P.70.81 you can view and maintain the reviewers.

Please see the online help for screen P.70.81 to learn about the full functionality of this screen.

CR-MA8514If the new total costs of a currency total up to 0 on a change order the currency record is now kept.

CR-MA10976Screen A.30.05 is now only closed automatically if Intergraph creates project defaults. For customers the screen remains open.

cont'dMSCM

29Page of




5606_2 Change Request From the 8 new reports, 7 reports are based on new form P.70.81 VDR Submittal and Status and 1 report (P.70.R.84Open Projects is based on A.20.01.02 Project Information).The reports give various overviews about the - performance of VDR handling in general regarding VDR re- and submittals- performance of suppliers VDR handling in detail, regardingVDR regarding VDR re- and submittals (within several days), - VDR resubmittals (within several days), - number of returned VDR’s, - days slipped per tag_number / PO Number, - exceptions past due

New reports are:P70R80.rdf

B-05606

cont'dMSCM

A1052

A200602

A2012

A2013

A3005

A6085

D2011

P1001

P1042

P1043

P1051

P1053

P3001

P3011

P3022

P5016

P6001

P6003

P7031

P7061

P7062

P7081

P8011

P8051

P9011

SM2011


30Page of





7354

7460

8963

10485

10710

Change Request

Change Request

Change Request

Bug Fix

Bug Fix

P70R81.rdfP70R83.rdfP70R84.rdfP70R85.rdfP70R86.rdfP70R87.rdfP70R88.rdf

P.70.71 Expediter Workload / P.70.72 Expediting Details

Dependent on the project default ZP_ZEROISH the Excel export will only export item shipments with quantity > 0 (ZP_ZEROISH = 'N') or all item shipments regardless of their quantity (ZP_ZEROISH = 'Y').

P.10.59 Guarantee Document Types

This new screen is used to maintain document types for guarantees, used in P.50.07 Maintain Agreements folder Guarantees as a LOV in field Doc Type.

Field 'Comment' has been added in folder 'Line Items' in screen P.50.07 Maintain Agreements.

It is a free text field. If a comment has been entered on the requisition line item based on that an agreement line item has been created this comment is taken over into this field.

The toolbar icon for the list of values is now only active for the structure element fields in screen J.10.02 if an LOV is indeed available.

Fixed update to the PLL checks

Cust.Ref.No.

CR-MA7354

CR-MA7460

CR-MA8963

TR-MA10485

TR-MA10710

cont'dMSCM

Others

P7071

P5007

P5007

J1002

L2003

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

31Page of




10712

10729

10730

10731

10737

Bug Fix

Bug Fix

Bug Fix

Change Request

Bug Fix

Cursor position revised to position in first field of record when user has choosen to insert a new record.Revised Currency field to be not mandatory (deleted errormessage ‘MAG-00013 This Currency does not exist’ )

The background color of field 'Order by' has been corrected.

A double-click on the context and order by field is not required. If you want to call screen A.60.61 you can use the fastcall. Therefore this CR has not been implemented.

The background color of field 'Order by' has been corrected.

Screen A.60.61 User Preferences has been added to the fastcall.

The list of values on field 'Account Code' is now displayed in alphabetical order.

It is now possible to set in the formsweb.cfg the parameter terminal_server. This parameter can have the values Y or N.

Define the parameter in the otherparams line:

Example: terminal_software=N

By using different sections for access with/without terminalsoftware you can determine the directory used for display of files stored in the database:

If the parameter is set to N, then in D1011 the download directory is determined by the DBA setting WEBUTIL_DIR_ASIf the parameter is set to Y, then in D1011 the download directory is determined by the DBA setting WEBUTIL_DIR_TS

If no entry in the formsweb.cfg is available, the DBA setting WEBUTIL_DIR_AS will be used.

TR-MA10712,10713

TR-MA10729

TR-MA10730

CR-MA10731

TR-MA10737

cont'dOthers

AS1002

J2001

J2002

J2003

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

32Page of




10738

10749

10769

10793

10820

10821

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

If no value is selected for the DBA settings, the default directory will be C:\tmp.

This functionality can be used for the standard login, the supplier login, web approval and link login.

The problem with installing the license through SPLM mentioned in this TR is resolved. (ORA-06502)

Correction in upload of files to database to ensure correct functionality. If the upload fails, an error message will be displayed.

The length of the hostname is increated to resolve the problem.

Correction of file upload processing if upload/view CIP functionality is used.

Fixed the problem. Replaced the function win_api_utility.copy_file with the host command.

The error message while exporting data does not occur anymore.

TR-MA10738

TR-MA10749

TR-MA10769

TR-MA10793

TR-MA10820

TR-MA10821

cont'dOthers

A2049

B200147

D1011

D1012

D9021

P2001

P2003

P2004

P3027

SM2011

SM3001

SM3002

SM4005

D9021

A6081

D9021

AS1005

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

33Page of




10903

10912

11011

11041

11461

11858

Bug Fix

Bug Fix

Change Request

Bug Fix

Change Request

Change Request

The error will not occur for the catalog sections from 10-20 having price name attribute as required and price indicatorschecked-on.

Attributes that have been attached to a requisition and that may be updated even after approval can now be modified again also after approval in screen D.90.21.

URL's for Discoverer startup adjusted to satesfy Oracle 11gVersions needs.

MTI version will be displayed properly in the main screen ofMTI application.

D-11461(LOV on AS1004 and WhereConditions)The following are the changes in the screen AS.10.04 Catalogs:

1. The LOV on the column ‘Where Condition’ in ‘AS.10.04 Catalogs Window 2’ will show the where condition for the module ‘AS1004’ only.2. The LOV on the column ‘Tablename’ in ‘AS.10.04 Catalogs Window 3’ will show all the tables from the screen ‘A.50.02 Tables’ which are of table type “COMMATTR” all the time.

B-11858: see documentation

TR-MA10992:The problem with error "spec does not exists" is resolved. The LOV for spec should remain as it is and still display records according to the rules given by project defaults ZX_ALLSPEC and ZX_HI_SPEC.ZX_DP_SPEC has no effect in this screens.

TR-MA10903

TR-MA10912

CR-MA11011

TR-MA11041

D-11461

B-11858,TR-MA10992

cont'dOthers

J2011

AS1004

D9021

AS1004

B4051

L1003

L2001

RELEASE NOTES - B-11858.DOC

Module

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

Comment

RELEASE NOTES - B-11858.DOC

34Page of




13065

14809

Change Request

Change Request

Two new DBA settings will allow for sending emails with a password-protected SMTP server:

SMTP_USER - The system user account who connects to the SMTP_HOST in order to send emails. Only required if SMTP_PASS is set.

SMTP_PASS - Optional password of the system user account who connects to the SMTP_HOST in order to send emails. If no password is given, the email is sent out without transmitting user/password. This is possible at smtp servers which do not require authentication. If you try to deliver emails with null password to a protected server, you will receive an “SecurityException: Access to default session denied” while if user/password is unknown or incorrect, you will get an “AuthenticationFailedException”.

System now provides the facility for user to define and review table details. A new grid is provided to facilitate the same. User can create, modify and delete the table details through this grid. The grid has following fields to define the Table Details1. Table Detail ( the TD Code)2. Short Desc3. Description4. Parent Table Detail (Parent TD Code)5. Parent Short Desc (read-only field that would be populated on re-load of the grid)6. Control Status (both the main and Nls table)7. User Defined Attributes (both the main and Nls table)

The user can now also define the hierarchy for Table Details. This means that the Table Details can be organized in a hierarchical manner also. For realizing the

B-13065

B-14809

cont'dOthers

L3002

A1023

A6055

A6072

P2002

P2003

P3021

P3024

SM2011

SM3005

SM4002

Module

Module

Document Name

Document Name

Comment

Comment

35Page of




22905

24552

7029

8352

8905

Change Request

Change Request

Bug Fix

Change Request

Change Request

same, user needs to fill the Parent Table Detail. All the existing Table Details will be available for specifying it as Parent Table Detail except those Table Details which are child of the corresponding Table Detail.

Please note that Table Details only from the same Table Group are made available to be specified as Parent Table Detail.

User cannot add or modify or delete table details corresponding to a table group which has not been created in the logged-in discipline.

In order to support the functionality of importing data from XML files into CMS data structures, we need to create supporting tables. This user story deals with creating all the tables, view and other related data structures.

see documentation

Screen function to upload documents and appropriate DII Document were revised to identify correct DBA setting.

A new provision is provided for maintaining the Class Independent Properties in CMS. It is similar to the functionality of defining Global Properties for A Class System, the only difference is Global Properties are defined for a Class System where as these Class Independent Properties are depend on any Class System or Class. They are applicable for all Classes. The user shall be able to Query / Insert / Update Delete data. These properties and their values will appear as other properties inmulti article view. Adding a new Class Independent Property will result in adding the same in all the Classes ofall the Class Systems. Also, deleting the Class Independent Property will result in the same property getting deleted from all the Classes of all the Class Systems.

This report SM40R02.rdf reports the data of SM.40.02 Change Order Requests. The user, starting this flexible report can choose individually to not print or print: - submitted data- price breakdown data- labor hours data- approved data

B-22905

B-24552

TR-MA7029

B-08352

V-ID8905

cont'dOthers

D1001

Module

Module

Document Name

Document Name

Comment

Comment

RELEASE NOTES - B-24552_7000.DOCRELEASE NOTES - B-24552_7000.DOC

36Page of





9946

10193

10278_1

10551

Change Request

Bug Fix

Change Request

Bug Fix

- rejected dataon the report.

SM.20.11 Subcontract Administration

The fields 'Forecasted Start' and 'Forecasted End' in screenMilestone Summary Details (Window 14) now are ordered between the fields 'Planned Completion Date' and 'Expected Progress (%)'.

• On creating NLS during ident generation, #in# and #mm# loose their hash symbols. Result: in and mm • In dynamic NLS display #in# and #mm# is replaced by ZX_NS_UNIT. Conversion of related attr value is done independently. If obj parm nls is e.g. #attr1#in (traditional way), unit symbol will not be replaced during conversion.

To decrease the amount of data in the selected ident table it is recommended to remove older job runs (that were canceled or completed) from time to time. Go to SP3D 20.01, execute query and press delete record on runs no longer needed. Any detail job data will also be removed, while destination data (SP3D 20.02) will not be touched.

D-11028 [ Able to add class while in project to a Class Syscreated in PG ]

It was possible that, if we are currently logged-in to a Project, then we were able add a Class to a Class System that has been created in the Product Group. This is now rectified.

Further implementation is also done such that we shall now not be able to modify a class which is created under aClass System from a Product Group when being logged in to the project. For that the following would now not be modifiable (for product group data and when we are currently logged-in to a project):

Cust.Ref.No.

CR-MA9946

TR-MA10193

CR-MA10278

TR-MA10551

cont'dOthers

SPRD

SM2011

S1005

SP3D2001

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

37Page of




10563

10574

Bug Fix

Bug Fix

• Class Code• Short and long descriptions• Keywords• Commodity Group / Part / Commodity Code associated with Class• Class Properties• Class Layout• Table Groups / Table Details associated with Class• Deleting a classAlso If the Ident belongs to (PROJ_ID) the logged-in projectthen we can modify the Ident property values (irrespective of whether it is associated with a PG Class or Project Class) in the same project. The system would also not allow a PG Ident being classified by a Project Class.

The problem that was reported as “Idents created in Product Group are not prperly displayed in MAV” was a data related problem and is resolved.

SP3D.20.01 Export JobsTab-folder ProgressFix issue with progress field overflow. Progress field can keep up to 32767 characters. After the upper limit is reached you will get error FRM-40831: Truncation occured: value too long. Provided fix controls the upper limit and stop writing into progress field after the upper limit is reached. Furthermore the progress messages are redirected into current log file.

Tab-folder Selected SheetsYou can add only sheets which are part of Sheet Config associated with the current job. If the project default ZI_SP3D_CT is set you can also add sheets from sheet configuration associated with the template pointed by ZI_SP3D_CT.

Please note that the sheets which are not included into sheet configuration of current job will not be added even configuration items AUTO_SELECT_GENERIC_SHEETS, AUTO_SELECT_SHTS_FOR_PARTS, AUTO_SELECT_VALVEOP_CLASS_SHTS are set to Y.

When export job finished with status “ERROR”,Job Goal “PRE_IF_TABS”, the records in SP3D_EXP_DST_SHTS will be released. As such continuity of the process remains intact.

TR-MA10563

TR-MA10574

cont'dSPRD

SP3D2001

Module

Module

Document Name

Document Name

Comment

Comment

38Page of




10587

10601

10603

10636

10654

10665

10666

10689

Bug Fix

Bug Fix

Bug Fix

Change Request

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Length correction of internal variable to avoid datatype errormessage.

Correct initialisation of rule when validating short code to show correct tables in S3001LOV.

Correction of Complete Indicator functionality for SP3D export:

- Rename of spec code is now recognized- Correction behaviour when job is cancelled

In S.10.08 the functionality of the windows for ‘Parts to Short Codes’, ‘Allowed Option Codes’, ‘SP3D Short Codes’, ‘Group Short Codes’ and ‘Sheets to Short Codes’ has been merged into a window with several tab pages.

Correction in functionality of NLS window when form has been called from S3001 to prevent error FRM-41045.

The changes deal with providing SDB custom functions also in standard delivery.

Correction canvas display

1) Corrected Online Help2) Renamed GO to GEOM_S40113) Now, Calling the form from FASTCALL / right mouse click now works proper4) Added legend for the icons5) Implemented expand all and collapse all functionality6) For table types GEOM_% added a third in the tree to

TR-MA10587

TR-MA10601

TR-MA10603

CR-MA10636

TR-MA10654

DI-MA10665

TR-MA10666

TR-MA10689

cont'dSPRD

SP3D2001

S2002

S3001LOV

S5006

SP3D2001

S1008

S3001

SP3D2001

S1008

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

39Page of




10691

10703

10734

10739

10781

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

display the Geometrics for the table in the second level7) Fixed the query problems when calling the screens A.50.02,A.50.03,S.20.02,S.20.I.02,S.20.I.03,S.50.10,S.50.11

The log messages were improved. Check for missing sheetalso implemented.

TR-MA10703 , TR-MA10676, TR-MA10675, TR-MA10709, TR-MA10705

obsolete fastcall entries deleted

Invalid sort statement removed.

While populating spec items using S.50.06, only the current role is checked for the access to the project by the logged-in user.

Removed dispensable fastcalls

TR-MA10691

TR-MA10703

TR-MA10734

TR-MA10739

CR-MA10781

cont'dSPRD

A5002

A5003

S2002

S2011

S20I02

S20I03

S4010

S5010

S5011

SP3D2001

S0101

SP3D2001

S5006

SP3D1001

SP3D1002

SP3D1003

SP3D1004

SP3D1005

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




10788

10812

10822

10834

10834_2

10870

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Correction startup processing of SP3D1008 when called from SP3D2001.

Tree icons in SP3D 10.09, 20.01/2 now also displayed when read from java archive.

Correct setting of Unit1 when creating new spec item depending on project default ZS_UNIT_SI.

Correction of query processing

Correction of query processing

We have changed spec transfer.

TR-MA10788

TR-MA10812

TR-MA10822

TR-MA10834

TR-MA10834

TR-MA10870

cont'dSPRD

SP3D1006

SP3D1007

SP3D1008

SP3D1008

SP3D2001

SP3D2002

S5006

S1001

S1002

S1003

S3001LOV

S400401

S400402

S400403

S400404

S400405

S4021

S5017

A5001

A5002

S1005

S4022

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

41Page of




10872

10875

10899

10916

10931

10943

10986

10990

11057

13054

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

Double click on object parameter in S8001 will query the correct record in S1005.

Correction of complete indicator functinality when revising specs.

Corrected the duplicate processing of post sheet procedures when extended customization is checked.

Validation of commodity code of spec item will fill the description field.

Error removed causing message ORA-1403 when cancelling query

Group code set to upper case.

Automatic query of spec item notes when navigating to another spec item

Navigation after build idents in window 3 corrected.

Screen name changed to SP3D 10.14 (without . after SP3D) to make it consistent with the other SP3D screens.

B-13054 (SP3D Change for Nuts, Gaskets and Washers during export/import from/into SP3D)

Some systems require that for Gasket commodity code gasket thickness value need to be appended, for Nut

TR-MA10872

TR-MA10875

TR-MA10899

TR-MA10916

TR-MA10931

TR-MA10943

TR-MA10986

TR-MA10990

TR-MA11057

B-13054

cont'dSPRD

PDMS1002

S8001

SP3D2001

SP3D2001

S5006

S3001

S2002

S5006

S5006

SP3D1014

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

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

42Page of




commodity code bolt diameter and nut height values need to be appended and for Washer commodity code bolt diameter and washer thickness values need to be appended separated by an underscore.Now, it is possible to append the values to the commodity code as per the above mentioned logic when we export Gasket, Nut, and Washer commodity code from SPRD. Appending values to the commodity code is controlled by three new config items TRANS_CC_GASKET to control Gaskets, TRANS_CC_NUT to control Nuts and TRANS_CC_WASHER for Washers. This new logic of appending the values to the Gasket / Nut / Washer commodity code is implemented in the CIP M_PCK_SP3D_CUSTOM. GET_TRANS_CC_GNW. This function is set as Retrieval Source for the attribute IndustryCommodityCode of the sheets GasketPartData / NutPartData / WasherPartData and for the attribute ContractorCommodityCode of the sheet PipingCommodityMatlControlData and for the attribute CommodityCode of the sheet PipingCommodityProcurementData

GasketPartData / NutPartData / WasherPartData

GasketsIf the config item PD_GASKET_TRANS_LEVEL is set to IDENT then the Commodity Code will be appended with theGasket Thickness value (separated by an underscore). The Gasket Thickness value will be fetched from the Ident input 2. NutsIf the config item PD_NUT_TRANS_LEVEL is set to IDENTthen the Commodity Code will be appended with the Bolt Diameter and Nut Height values (separated by an underscore). The Bolt Diameter and Nut Height values will be fetched from the Ident input 1 and input 2 respectively.

WashersIf the config item PD_WASHER_TRANS_LEVEL is set to IDENT then the Commodity Code will be appended with theBolt Diameter and Washer Thickness values (separated byan underscore). The Bolt Diameter and Washer Thickness values will be fetched from the Ident input 1 and input 2 respectively.

Also, when you export the part data sheets the new code with values appended is stored as company Ident against the company given by the project default ZI_SP3D_CO so

cont'dSPRD

43Page of





that during BOM import specifying the company the BOM data can be imported into SPRD. The logic of building company Idents for Gasket / Nut / Washer Part Data sheets is integrated into the CIP M_PCK_SP3D_CUSTOM.SET_CATALOG_PART_NUMBER.

PipingCommodityMatlControlData/ PipingCommodityProcurementDataIf the config item PF_TRANSLATION_LEVEL is set to IDENT or CC_OR_IDENT then we append the values for theGasket / Nut / Washer Commodity Code from the Ident inputs as per the logic mentioned above for part data sheets. When the config item is set to CC_OR_IDENT this new logic will apply only to the records at Ident level. The Commodity Code will be identified as the Gasket / Nut / Washer by the association of parts in SP3D 10.04 against the sheet GasketPartData / NutPartData /WasherPartData respectively.

Screen S.10.04 Object ParameterDropdown box Ports added to the screen. Following values are available:• 1 Port• 2 Ports (Default)The item allows you to specify how many connection points the item has.

For example a pipe typically has one nominal size in SPRD but has two nominal sizes in PDS/SP3D because it has two ports. So the nominal size from SPRD will be duplicated for export to PDS/SP3D. If the item has only one port (e.g. for a cap), duplication is not required.

Please note that during data migration default value 2 Portswill be applied to all existing data.It means that after applying this installation package you have to check all object parameters and change ports when required.

Screen S.10.05 Object Parameter DetailDropdown box Ports added to the screen.

SP3D.10.08 TemplatesSheetsData with empty mandatory fields or with all optional fields empty will be displayed when indicator ‘Show incomplete records’ checked. Indicator ‘Show records with empty mandatory fields’ renamed to ‘Show incomplete records’.

B-14977

cont'dSPRD

44Page of




15140

15257

Change Request

Change Request

SP3D.20.01 Export Jobs

Improvements and fixes in the export of the Generic sheetsGeneric data will be generated only for idents specified in the screen SP3D.20.01 Export Jobs, tab folder Selected Idents.

Generation for sheet DINWallThickness is implemented. You have to define table translation ‘GMIS’ in the screen A.50.I.01 Interface Table for all tables with DIN-data. You can user sequence number, e.g. GMIS1, GMIS2, etc…

Data in the screens SP3D1001, SP3D1006, SP3D1007, SP3D1008 are now project depending.Existing non project data are propagated to each product group.

Now, it is possible to update the destination data directly. This can be done from both SP3D 20.01 and SP3D 20.02.After FILL_IF_TABS in SP3D 20.01, when button Show Results was pressed you can update the export job data inWindow 3 (Invoked by right mouse click on the tree node / sheet in the Tree / List tabs).After modification, the job can be cancelled and in the nextrun the manual changes will be applied in the FILL_IF_TABS and this changed data will go into destination.Also, you can do the modifications directly in the screen SP3D 20.02 and in the next export job run the manual changes get reflected.Modification is allowed only on the non unique key columns. If no unique key is defined for the sheet, then update of none of the columns are allowed.Manual modifications are indicated by different colour i.e. the data for the current updates is indicated by the RED colour and the manual changes that have already gone intothe job in the previous run are indicated by GREEN colour.

B-15140

B-15257

cont'dSPRD

S1004

S1005

SP3D2001

SP3D1001

SP3D1006

SP3D1007

SP3D1008

Module

Module

Document Name

Document Name

Comment

Comment

45Page of




22700

24155

3550_5

Change Request

Change Request

Change Request

Also SP3D 20.02 is enhanced to show sheets in a List view like in SP3D 20.01.

Filter tables on spec header level of type ‘Nominal Size’ and ‘Nominal Reducer’ can now be used for spec items with a geometric filter on item level.A nominal size filter table will only work for items with one nominal size, while the nominal reducer table will work for items with two nominal sizes.To activate the filter, check the ‘Size Filter’ checkbox for the specification item.

Note: When first using this new functionality, you will need to assign the ‘Size Filter’ checkbox in S500601 (S5006 Configurations) to the ‘Geometric’ tab page.

- The project default ZS_UNIT_S2 can now be used to fill Unit2 of a specification item automatically.- The project default ZS_SP_HGP can now be used to restrict entries in spec header geometrics to tables definedin the project only (default Project + Product Group).

New Features

B-04623

With this user story, we shall provide a mechanism to attach a branch table to a branch component group (with identifier ‘B’) . The attached branch table components would also be considered during generation for searching for commodity codes and inserting spec Items.

B-04709

In the spec component area when user selects Limit to part field on the filter line, then the LOV on ShortCode lists all the ShortCodes assigned to this Part in the Component group. If limit to part was not selected then no LOV on ShortCode is available.

B-13300

B-22700

B-24155

V-ID3550

cont'dSPRD

SP3D2001

SP3D2002

S5006

S5006

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

46Page of




Hooked up the Anti-Piracy and Tech Support buttons to topics in the online Help (.chm).

B-04688

From now onwards when user tries to enter some invalid option code on filter line then he will be prevented to save the filter line.Case 1 No LOV on Option Code is defined: All values are allowedCase 2 LOV on Option Code is allowed: All values from LOV plus 1is allowed.

B-04708

1. Relation between Commodity Groups & Parts is implemented on the filter line.2. Corrected the errors of Excel copy/paste data into the grid of Geom Types/Geom Names. Also solved this problem in all the basic grids throughout the product.

B-13354(ATP for D-2826)This ATP Copies the thickness to Schedule In thickness grid In Spec Editor if schedule is empty and validates the copy.

B-06880The branch table area is enhanced with the points mentioned below.

1. When generating XY use DNs from Nominal Sizes from Front Sheet 2. Have a mean to select only Part which are a Branch (By add a value in M_PARTS) 3. Second Preference should be easier, after adding preference matrix should re-query 4. In Specification Branch Table should have a visual Indication which sizes match the Spec Sizes 5. Magnify on Branch does not work, when existing does not work

B-13371

When user tries to copy filter lines from other spec then if at all filter lines records count is more than 6 then errors

cont'dSPRD

47Page of




3550_6

4878

8856_1

Change Request

Change Request

Change Request

are coming up. These errors are rectified now with this userstory.

B-04687

In Filter Label Defaults at the time of saving, size ranges of same components are verified for conflicts. During this process records with Def as checked are only need to taken into consideration. Previously all the records were taken into consideration for size range conflict verification.

B-04707With this user story Nominal Sizes should not be updateable in the thickness grid of spec general page.

B-04686The list of applicable diameters now is not a mix of all diameters defined for all Diameters series with the same standard.

Bug Fixes

Fixed the following problems• D-11059: LOVs on Limits to Group & Part.

see documentation

SP3D Analyze log will handle more different log messages.Also if BULKLOAD_MODE config item is set to AUTOMATIC_DIRECT, and if there is no proper bulkkload logfile, the bulkload stage will error out.

Overworked due to new corporate branding guidance for 2010. - replaced Intergraph icon with new high-color Intergraph icon - adjusted fond and fond size- overworked license text to match with Oracle 11g software

V-ID3550

B_04878

CR-MA8856

cont'dSPRD

S1003

SP3D2001

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

GENERATIONWORKFLOW.DOC

RELEASE NOTES_INNOVATORS_SPRINT14.DOC

GENERATIONWORKFLOW.DOC

RELEASE NOTES_INNOVATORS_SPRINT14.DOC

48Page of





8911

9609

10195

Bug Fix

Change Request

Bug Fix

The option C has been removed from project default ZB_BLDIDVJ. Now the only options for this project detfault are:N FIND_IDENT Verification Procedure does not build Ident if no matching Ident is found.Y FIND_IDENT Verification Procedure builds Ident if no matching Ident is found.

Together with the project default ZS_BLDIDMD the behaviour of find ident verification is the following:

ZB_BLDIDVJ = N => value of ZS_BLDIDMD is of no relevance.

ZB_BLDIDVJ = Y: ZS_BLIDIDMD = S Standard build ident is used

ZS_BLIDIDMD = E Enhanced build ident (using spec header geometrics) is used.

If the position is a CALC item (from line list), then in both cases the build ident procedure for Calc Idents (before active with ZS_BLDIDVJ=C) is used.

This patch installs Backlog Item B-13062:

This allows users of S.50.06 Specification Management to customize the creation of ident codes when idents get created from within this screen.

A new procedure CIP POST_BUILD_IDENTS_CIP( IN p_commodity_ID) has been implemented in package M_PCK_STD_CUSTOM.CIP execution will take place after idents are build and obsolete idents are removed.

On direct issue, over issue warehouses are taken into account.

Cust.Ref.No.

TR-MA9811

CR-MA9609

TR-MA10195

cont'dSPRD

Site

S8001

S5006

C202302

Module

Module

Module

Document Name

Document Name

Document Name

Comment

Comment

Comment

49Page of




10475

10478

10637

10715

10735

Bug Fix

Bug Fix

Change Request

Change Request

Change Request

We have corrected the unique key violation of the assign OIlogic.

Changed query of order totals detail screen.

Changed position of field „Issued Quantity“ in Screens C.20.21 and C.20.23.01.

We have added the custom check m_pck_forecast_custom.check_before_rr to the forecast run (was only included in the reservation run). We have added the fah_id to the custom procedure m_pck_forecast_custom.check_before_rr.

We have added the get data procedure for the table m_actual_polis to the site api. We have added the automatic quantity update of heat details in case of inserting increased receiving quantity.New procedure:m_api_site.get_actual_polis_data

PROCEDURE get_actual_polis_data(p_last_date IN DATE,g_proj_id IN m_user_securities.proj_id%TYPE,p_actual_polis_data OUT actual_polis_array);

TYPE actual_polis_rec IS RECORD ( esi_status m_esi_updates.esi_status%TYPE ,APOLI_ID m_actual_polis.apoli_id%TYPE ,PROJ_ID m_actual_polis.proj_id%TYPE ,POH_ID m_actual_polis.poh_id%TYPE ,POLI_ID m_actual_polis.poli_id%TYPE ,DP_ID m_actual_polis.dp_id%TYPE ,BASE_POLI_ID m_actual_polis.base_poli_id%TYPE ,USR_ID m_actual_polis.usr_id%TYPE ,LMOD m_actual_polis.lmod%TYPE

TR-MA10475

TR-MA10478

CR-MA10637

CR-MA10715

CR-MA10735

cont'dSite

C202202

C4001

C2021

C2023

C3001

C3011

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

50Page of




10753

10753_1

10755

10845

10856

10857

10880

10884

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

,INT_REV m_actual_polis.int_rev%TYPE ); TYPE actual_polis_array IS TABLE OF actual_polis_rec;

If fill in button at screen c.20.17 Window4 is pressed, now better performance.

We have fixed the performance problem with the fill in of data in window4. We have also corrected the LOV on field warehouses.

The project default ZC_MULT_WH is used for the warehouses which have the indicator Use for Issues in C10.02 Warehouses.

We have improved the performance of FR/RR.

eWe have corrected the mark all functionality. Now all records will be inserted after the use of the fill in button.

We have corrected the screen C1005. Now you cannot insert nodes by button Nodes if the locked indicator was set.

We have corrected the trigger on the nls table. After that the reallocate worked without errors.

We have corrected the screen for a detailed error message and the undo procedure of C3021. This error was only occurred in case of splits.

We have corrected the forecast/reservation in case of assemblies.

TR-MA10753

TR-MA10753

TR-MA10755

TR-MA10845

TR-MA10856

TR-MA10857

TR-MA10880

TR-MA10884

cont'dSite

C2017

C2017

C3001

C2017

C1005

C1015

C2021

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

51Page of




10901

10907

10980

11001

11016

11028

11032

11034

14790

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Bug Fix

Change Request

We have corrected the calculation and the detail information for the over issued quantity in C4001.

We have corrected the trigger to update the status in case of voucher for posted transfers.

We have corrected the screens. Now you are not able to insert, update or delete assigned warehouses and assigned workpackages of forecast and reservation runs, after the run was started.

No error occurs if deleting MRRs with attached tags.

We have changed the point of commit in C2017.

The old history entries will be deleted now after unpost a MIR.

We have deleted the update of m_fah_lns in case of same list nodes in several work packages. The first entry in m_fah_lns will not updated any longer.

We have corrected the LOV title of LOV for MRR Number.

C.20.16.02 Heat Number Query Screen

Displays heat numbers with quantities and warehouse information. If a qty field at the first block is doubleclicked, a new window opens with detailed information about the qty.

TR-MA10901

TR-MA10907

TR-MA10980

TR-MA11001,TR-MA11000

TR-MA11016

TR-MA11028

TR-MA11032

TR-MA11034

B-14790

cont'dSite

C3001

C4001

C2003

C300101

C300102

C2001

C2017

C2026

C3001

C2004

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




14791

24995

4880_1

Change Request

Change Request

Change Request

The document field (code field) can also be used by a double click. It shows the screens where the documents are created. The second block at C.20.16.02 shows the warehouse, location and all onhand inventory quantities with or without heat numbers.

Window5 in screen C.20.01 MRR by PO (using SWT) displays only the available received quantity of tags

If C.20.01 BOM Positions (LOV) is opened, there are only positions shown that have TAG quantities. The displayed quantity in this screen refers to the quantity on the BOM. If a position is taken over to C.20.01, at Window5 the Tag Number is displayed with the available received quantity.At the quantity calculation, only the highest revision of a MRR is considered.

Now the user is able to manage scrap in the issue screens.

Following changes are made:

Add new field "Scrap Warehouse" to the header of all issuescreens.

Add new Project default:

ZC_SCRAP_MThis project default is used to attach a mv_where view to control the idents, which are transfered into a scrap warehouse. If this default is set and a scrap warehouse is entered in the issue screens, overissued materials that matches the mv_where view will be transferred into the scrap warehouse.

Add Tag Number field to screen C.40.01.

B-14791

B-24995,CR-MA10523

B-04880

cont'dSite

C2001

C2001LOV

C2021

C202111

C2022

C202202

C202204

C4001

Module

Module

Document Name

Document Name

Comment

Comment

53Page of




4890

5598

8901

Change Request

Change Request

Change Request

If Checkbox "Query with Tag Number" in C.40.01 Setup is checked, Tag Number field is displayed on main window.After requery, the tag number is taken into account at every calculation and called screens.

If two people are trying to create a new MRR at the same time, they might receive the same MRR number and then when saving run into a UK violation.Numbers in MRR/MIR/MTR are checked before insert row.

Changed the exception handling for all inventory actions to get a better message in case of error.

Requery issue solved in the receiving screens.

B-04890

B-05598

V-ID8901

cont'dSite

C2014

C4001

C2001

C200102

C2003

C2004

C2005

C200901

C200905

C200906

C2015

C2017

C2019

C2021

C202111

C2022

C202202

C202204

C2023

C202302

C2028

PT3001

PT3002

PT3003

C2021

C202111

Module

Module

Module

Module

Document Name

Document Name

Document Name

Document Name

Comment

Comment

Comment

Comment

54Page of




cont'dSite

C2001

C200102

C2003

C2004

C2005

C2008
