|
Whatsnew -
AMUSE X30.doc Page 1 of 76
|
INDEX
GENERAL...................................................................................................................................... 4
q New
starting screens in AMUSE Menu System [Ph. 2] ......................................................... 4
q Unified
forms for Libraries and Project Activities................................................................. 6
q
Search
tool in Listbox........................................................................................................ 8
q
Windows
7 compatibility...................................................................................................
8
q
Resizable
Forms [Ph. 2]..................................................................................................... 9
q
Job
Opening Form........................................................................................................... 10
q
Link
to FW Ticket............................................................................................................
10
ENGINEERING............................................................................................................................ 11
q Engineering
Applications – NEW USER INTERFACE......................................................... 11
q Engineering
Libraries - User’s Manual [Ph. 2]..................................................................
11
q ECA
Description length increased to 80 char [Ph. 2].........................................................
11
q
ECA
Version –
New Table &
Application .......................................................................... 12
q Project
ECA List – Initialization by ECA versions..............................................................
13
q
Requisition
Sets – New Table & Application.....................................................................
14
q Piping
Classes – New Filter by Spec in DET and MACRO applications.............................. 15
q Piping
Classes – Search tool in MIDCHAR Listbox...........................................................
16
q FW
Unique Codes (table D001) – Filtering
Options and Full Decoding...............................
17
q
Client
Codes (table D002) –
New Filtering Options............................................................
18
q Client
Codes (table D002) – Full Decoding
and Editing...................................................... 20
q
Client
Codes (table D002) –
Export / Import through
Excel file [Ph. 2]................................. 21
q W/S/V
Library (table D292) – New
Filtering Options............................................................ 25
q MTO
– Enhanced Macro Explosion Process [Ph. 2]........................................................... 26
q Free
Reporting – Export CSV files saved with ; as separator.............................................. 28
q Free
Reporting – MR Comparison with PO & Received Qty................................................ 28
q Free
Reporting – Number of output records automatically calculated.................................. 28
q URS
005a - Extended Coding capability for piping material................................................ 29
q URS
038 - Enhanced Bulk Requisitions Title...................................................................... 32
q URS
005b - Increase digits for SPEC field [Ph. 2].............................................................. 33
q
URS
006 - Improved Management of Client Codes [Ph. 2].................................................. 33
q Automatic
email at MR Summary building for missing Weights [Ph. 2]................................ 34
q Automatic
email at MR Summary building for missing Client Codes [Ph. 2] ........................ 36
q
Mail
Monitor [Ph. 2] ......................................................................................................... 37
CAD INTERFACE.......................................................................................................................... 40
q URS
007 - AMUSE to SP3D interface [Ph. 2]..................................................................... 40
q
LIBRARY APPLICATIONS SCREEN [Ph. 2]........................................................................ 41
|
|
q
(CAD020
- Geometric Standards) [Ph. 2]................................................ 41
q
(CAD030 - Library ‘owner’ DET codes) [Ph. 2]...................................... 42
|
|
q
(CAD100
– MASTER Table) [Ph. 2].................... 43
|
|
|
|
|
|
|
|
q
(CAD121 – Rating
Cross Ref.) [Ph. 2]................ 45
q
(CAD121
– End Condition Cross Ref.) [Ph. 2].... 45
|
|
q
(CAD124 – Exceptions) [Ph. 2].......................... 46
|
|
q
(CAD200
– Allowed G/R Size) [Ph. 2]................. 47
|
|
q
(CAD370 – Selection Rules) [Ph. 2].............................................. 48
|
|
|
|
q
(CAD390
– SQL Versions) [Ph. 2]............................................................ 48
q
(CAD400 – SQL Codes) [Ph. 2]................................................... 49
|
|
q
PROJECT
ACTIVITIES SCREEN [Ph. 2]............................................................................. 50
q
(CAD121_JOB
– Project Ratings 00...99) [Ph. 2] .................... 51
|
|
|
|
(CAD122_JOB
– Project End Conditions 00...99) [Ph. 2]......... 51
(CAD124_JOB
– Project Exceptions 00...99) [Ph. 2]................ 51
(CAD370_JOB
– Project SQL Selection Rules) [Ph. 2]................. 52
(CAD401
– Project SQL Code Version) [Ph. 2]............................ 52
(CAD110
– Export Specs to CAD) [Ph. 2] .................................. 53
|
|
|
|
|
q
(CAD110_UC – UC
Creation) [Ph. 2].......................................... 56
PROCUREMENT........................................................................................................................... 57
q
Inquiry – Check
on Due Date existence [Ph. 2].................................................................. 57
q
Inquiry – Check
on consistency between Issue date and Due date [Ph. 2]........................... 57
q
Post Order - Enhanced display of Req. Item split by
Units and quantities [Ph. 2]................. 58
q
Post Order - Shipping Destination [Ph. 2].......................................................................... 64
q
Reporting: “PO List” -
Req. Alias [Ph. 2].......................................................................... 68
q
Reporting: “PO
Material Status” - Req. Alias
[Ph. 2]......................................................... 68
q
Reporting: “DELIVERY
STATUS” - New fields [Ph. 2]...................................................... 69
q
Reporting: “DELIVERY
STATUS” - Printing Options [Ph. 2]............................................. 70
q
Inquiry and PO data updated by eProcurement.................................................................. 71
CONSTRUCTION.......................................................................................................................... 72
q
Enhanced ALLOCATION Process – minimum % of Allocation............................................. 72
q
BOM Priority in Allocation Reports (URS 056).................................................................... 74
q
BIN Field increase on Reports (URS 055)........................................................................... 74
Tickets......................................................................................................................................... 75
q
Ticket No.
936451 - SQL Error when modifying sort fields on Delivery Status screen 75
q
Ticket No. 214434 -
Job Leading Zeros Dropped from Pricing Spreadsheet.. 75
q
Ticket No. 429864 -
G110 ECA type ? to B........................................................... 75
q
Ticket No. 586441 -
CSV Export of Table D561 ‘Exploded MTO (Cut File)’... 75
q
Ticket
No. 761676 - Copying Macros..................................................................... 75
q
Ticket No. 714032 -
Line List application does not close Excel........................ 75
q
Ticket No. 587410 -
Wrong size code in MTO import from PDS [Ph. 2]........... 75
q
Ticket No. 323653 -
Req. Index compared to previous Rev [Ph. 2]................... 75
q
Ticket No. 767313 -
Inconsistency between PO and MR data [Ph. 2].............. 75
q
Ticket No. 557461 -
Delivery Status Report [Ph. 2].............................................. 75
q
Ticket No. 397479 -
TAG REQ: calculation of tot. qty [Ph. 2]............................. 75
q
Ticket No. 690472 -
Change to Material Delivery Status [Ph. 2]....................... 75
q
Ticket No. 153169 -
Make Due Date a Mandatory Field in PUR120 [Ph. 2].... 75
q
Ticket No. 388037 -
TAG req. - Null TAG not allowed......................................... 75
Whatsnew
- AMUSE X30.doc Page 2 of 76
|
Whatsnew -
AMUSE X30.doc Page 3 of 76
|
J Ticket
No. 690472 - Change to Material Delivery Status [Ph. 2]........................................... 76
J Ticket
No. 153169 - Make Due Date a Mandatory Field in PUR120 [Ph. 2]........................... 76
J Ticket
No. 181710 - Requisition Alias print on reports [Ph. 2].............................................. 76
J Ticket
No. 901810 - Split qty by plant unit in post order [Ph. 2]........................................... 76
J Ticket
No. 353187 - Group material with same destination [Ph. 2]........................................ 76
J Ticket No. 989344 - Prevent save of TAG Req when out
of user ECA competence [Ph. 2] ..... 76
|
|
|
Whatsnew
- AMUSE X30.doc Page 4 of 76
|
Nouveaux écrans de départ en AMUSE
System Menu [Ph. 2] 2]
AMUSE écran initial
comprend maintenant la zone de connexion, sans écrans intermédiaires.
Il
a également été révisé pour refléter la réorganisation de l'entreprise récente.
.
sélection
de la section ca n être fait en
cliquant sur le drapeau BU.
NB dernières sélections de connexion
(Département, BU, Section et nom d'utilisateur) sont automatiquement préparés à
l'ouverture de AMUSE, de sorte que le mot de passe est la seule entrée
nécessaire (sauf si les informations de connexion doivent être modifiées).
L'écran
principal après la connexion a été révisé: l'accès aux bibliothèques générales
et activités du projet est maintenant grâce à des boutons uniques pour les
modules entiers E / P / C.
|
Whatsnew -
AMUSE X30.doc Page 5 of 76
|
|
Whatsnew -
AMUSE X30.doc Page 6 of 76
|
Ingénierie et
d'approvisionnement et de construction des
bibliothèques sont maintenant deux onglets de la même écran:
|
Whatsnew -
AMUSE X30.doc Page 7 of 76
|
Aussi E / P / C Activités du projet
sont maintenant disponibles en deux
onglets de la même fenêtre, à la fois ciblée pour le projet sélectionné à la
fenêtre supérieure.
|
|
|
Whatsnew -
AMUSE X30.doc Page 8 of 76
|
All applications adopting the standard AMUSE interface (typical for all
Procurement and Construction applications and for all Engineering applications
redesigned in this release) now provide a standard tool to search for a
specific string inside any text columns
in the look up table (numeric, date
or long text columns are not searched).
If a sample string is
input in the data field, at click on___________
(or Enter key) the table
is scanned starting from top and the first row containing that string in
any text columns will be highlighted and scrolled into view.
Further clicks will search for the next matching rows, down to the table
bottom.
Search will start again from table top with next click.
Editing of the sample string will restart search from table top.
Windows 7 compatibility
Windows 7 graphic request for more space in title/menu
bars was causing the appearance of unexpected scroll bars and, as a
consequence, some objects were pushed out of initial form size.
|
Whatsnew - AMUSE X30.doc Page 9 of 76
|
On monitors with resolution higher than 1024 x 768 it
is possible to extend height and width of forms: this provides a wider view on
table columns and rows.
Forms can be extended dragging borders (or even
maximized double clicking on form’s title bar) but cannot be reduced below the
initial size.
This functionality is available in all Procurement
& Construction applications and in all Engineering applications re-designed
to adopt the same standard interface (see dedicated bullet in ENGINEERING
section later in this document)
See the sample screen shots on PO Header table:
|
Whatsnew -
AMUSE X30.doc Page 10 of 76
|
|
|
Link to FW Ticket
System Libraries screen now provides a direct link to FW Ticket system.
|
Whatsnew -
AMUSE X30.doc Page 11 of 76
|
Engineering Applications – NEW
USER INTERFACE
Almost all applications in Engineering Library and some
applications in Engineering Project Activities have been re-designed to
adopt the standard AMUSE interface already used by all application in Procurement
& Construction modules.
Application interface re-design was also recommended due to the massive
updates required by “URS 005a -
Increase digits for MID” to Engineering Library applications.
This enhancement adds uniformity to AMUSE user interface across the
entire system and improves engineering applications which can now take
advantage of some typical functionality of the new interface, like:
·
direct editing in
table view. This ‘Excel like’ editing is more comfortable and
provides a better visibility of edited rows.
·
ability to insert,
delete or modify rows in a single transaction
·
modified application
structure, where applicable, to better fit db structure and increase ease of
data visibility and navigation (ex.: see MID Table / MID Char application,
[X-D270]).
·
new additional
filtering objects to make querying data easier
·
enhanced graphical
presentation of data, in line with the rest of AMUSE application, to have an
easier understanding of table content.
·
Resizable
forms
The only application not yet re-designed in Engineering Library is D440 – MACRO.
The applications already re-designed in Engineering Project Activities
are:
G130 – Prj ECA Codes
D720 – Units / Areas
G250 – Sub Accounts
S950 – eMail Settings
D274 – Prj Numeric MID
Characters
D512 – MTO Info List
Engineering Libraries
- User’s Manual [Ph. 2] User’s Manual has
been completely revised.
ECA Description length increased
to 80 char [Ph. 2]
|
Whatsnew -
AMUSE X30.doc Page 12 of 76
|
|
|
In Piping material library the basic Version – (matching GCCCA Rev.6) is related to ASME normative,
but other alphabetical ECA Versions can be added to allow preparation of
Piping libraries according to other Normative or even to manage all materials
as itemized (TAG).
Example of possible Versions:
D = DIN
E = Euronorm
F = French normative
T = All Tagged
materials (no bulk management for piping, all project materials itemized) This
new table lists the available Versions, with description and remarks.
Since the use of these alphabetical Versions has to be limited to
engineering module, they are not synchronized in Procurement ECA List and will
not affect Vendor qualification in Vendor List.
An H (Hold) flag must be set
in this table to all alphabetical Versions with the only exception of Version – (ASME): all Versions
will be available when initializing Project ECA list in Engineering, while only
not flagged Versions will be listed when initializing Project ECA list
in Procurement.
|
Whatsnew -
AMUSE X30.doc Page 13 of 76
|
When setting Project ECA codes (picking from ECA Library) a dialog box
allows the selection of the Version to be used to initialize the project:
For each ECA code the selected Version, when available, will be used to
initialize the Project ECA list (when not available Version – will be selected by
default).
|
|
|
Whatsnew -
AMUSE X30.doc Page 14 of 76
|
A new application is created to manage table ENG200 ‘Requisition Sets’,
where Req. Sets
are defined, with description and remarks.
Requisition Sets must be created
in this table prior to use them in table D512 – MTO Info.
|
INSTALLATION
NOTE
In already existing
projects the Req. Set list will be automatically populated (at release
installation) with the codes actually used in MTO info table: the Description
of each Req Set can then be added, if deemed necessary, in table ENG200 (at
least for on-going projects).
|
AMUSE – Release X.3.0
Piping Classes – New Filter by Spec in DET and MACRO applications
|
|
|
Whatsnew -
AMUSE X30.doc Page 15 of 76
|
|
Whatsnew -
AMUSE X30.doc Page 16 of 76
|
Looking ahead to the great number of codes that can be now defined in
each MID table (see URS 005a) a special tool has been developed to facilitate
MIDCHAR search when building MID composition: in the listbox for selection of
MIDCHAR when typing a sample string in the dedicated search field the pick list
content will be dynamically updated ‘asyou-type’ to show only the rows
including such string in description, driving this way the user to the required
MID characters, wherever they are located in the alphabetically ordered list of
codes.
|
Whatsnew -
AMUSE X30.doc Page 17 of 76
|
|
|
|
|
|
FW Unique Codes (table D001) – Filtering Options and Full
Decoding
The new redesigned
application allow on-screen easy querying of table content to show
|
|
only FW Global or Project
specific codes:
|
AMUSE – Release X.3.0
In addition to the standard querying tools the new
application allows on-screen easy querying of the table content,
setting/combining pre-defined filters:
A) Only codes actually used in Piping Classes of a
specific Job:
B) Only codes actually used in MTO of a specific
Job:
|
|
|
AMUSE – Release X.3.0
|
|
|
|
D) Only FW Global or
Project specific codes (in the
example only ‘FW Global Codes’ of Client ‘HELPE’):
|
|
|
|
E) Only rows
where Client Code is missing or where it already input:
|
|
Whatsnew
- AMUSE X30.doc Page 19 of 76
|
Client Code can be input in both Table view and Full-decoding view
Editing allowed
|
Whatsnew -
AMUSE X30.doc Page 20 of 76
|
|
|
|
|
|
Client Codes
(table D002) – Export / Import through Excel file [Ph. 2]
Rows
from this table can be exported to an Excel: Client Codes can be input in
the Excel file to be then uploaded back into this table.
|
|
|
|
Whatsnew
- AMUSE X30.doc Page 21 of 76
|
Export file is by default named Exported_ClientCodes.xls
and it is stored into folder C:\AMUSE\ClientCodes (but the
user can change both name and destination).
A sub-folder called \Inbox is also ready to store
return files. Import process will search by default in this folder for XLS
files.
At click on menu Item
the export process starts and asks for export file name definition:
And the just created Excel file is opened and it prompts for password
input to protect the worksheet (protection is strongly recommended, it will
prevent any modification of the Excel content except for the Client Code
column, where input is expected).
Remember to Save file after protection.
|
Whatsnew -
AMUSE X30.doc Page 22 of 76
|
AMUSE – Release X.3.0
The return file compiled with Client Codes should be
stored in \Inbox folder, and then a click on menu Item starts import
process.
At the end the following screen shows the result of
import:
Filtering
objects are available to show where a code is input, where is missing, where it
modifies the existing code (in case it was exported in the Excel file) and
where it has been cleared (in case it was badly input previously).
|
|
The content of the table can be printed to
get the following report:
AMUSE – Release X.3.0
|
|
|
|
|
The option buttons can easily filter the list to
retrieve only rows with missing values.
The drop down list allows selecting the
project requiring unitary weights input: only rows relevant to DET + Size
actually used in MTO of the selected project are displayed.
Combining the two
filters the list of rows to be updated is considerably reduced.
If Weight Library is regularly maintained the
number of rows without weight to be updated should be quite limited.
|
Maintenance of Unitary Weights in table D292 is mandatory in order to
have automatic weight calculation for piping material (several reports in
Engineering and Construction show Piping material weight and also Allocation
priority can be based on BOM weight).
Rows in table D292 are created during MTO explosion whenever a project
requires a component that is still missing in the weight library: the relevant
unitary weight can then be input in table D292.
Also Project Decoding tables (D591, D592 and D593) are updated during
MTO Explosion, but unitary weights for new materials cannot be retrieved at
this stage.
The lack of unitary weights input in table D593 becomes evident when
Requisitions are built and table D593 is queried by relevant reporting:
materials without unitary weight in table D593 will not show a valid weight in
reports.
Rows in table D593 without a valid unit weight can be easily
retrieved querying By Example... for NUNIT_W = 0:
At this point input in table D292 should be required, in order to then
run Project weights refresh process and make all weights available for
reporting.
The process that creates rows in table D292 starting from MTO input is
quite complex: it classifies components based on their geometry, material
weight class, size, thickness (converted into mm equivalent) and rating
and/or facing when required (see Eng. Library User’s Manual – D290 - Weight /
Surface / Volume Library for details).
For this reason it’s not easy to identify which rows in table D292 are strictly connected to the rows in project
table D593: the list of rows that exactly match those without weight in D593
cannot be reached with a simple query on table D292.
Anyway in the new D290 W/S/V Library application two filtering tools are
available: they can be used to restrict the number of rows in table D292 to be
completed with unitary weight:
|
Whatsnew -
AMUSE X30.doc Page 25 of 76
|
|
Whatsnew -
AMUSE X30.doc Page 26 of 76
|
Explosion process has been enhanced in order to better manage Macros.
|
|
|
|
|
In this case Explosion Process returns an Error
|
|
If MACRO is Found then Explosion process uses it has
defined in Bulk Spec Ref. (or Default Job = ‘*’ at last round)
|
|
NO
|
|
YES
|
|
If MACRO is NOT Found then the Explosion process searches
for that MACRO one last time inside Default Job = ‘*’
|
|
NO
|
|
Is
Search Job <> ‘*’
|
|
YES
|
|
Found ?
|
|
The Explosion process starts searching the MACRO
composition inside MTO project itself (Project customized Macro).
|
|
MTO Project: 9BD0100A
|
|
YES
|
|
Found ?
|
|
NO
|
|
MTO Project
|
|
If MACRO is NOT Found
then the Explosion process searches again that MACRO inside the Bulk
Spec Ref. Job
(as
defined in C410 - Job Settings).
|
|
If MACRO is Found then Explosion process uses it has
defined in MTO Project
|
|
Whatsnew -
AMUSE X30.doc Page 27 of 76
|
|
|
|
|
|
Example:
Project:
9BD0100A
|
The Explosion process starts
searching the Coupling Set composition inside MTO project itself (Project
customized Coupling Set).
|
|
Whatsnew -
AMUSE X30.doc Page 28 of 76
|
All exported text files (CSV) are now exported having ; (semicolon) as field separator, in
accordance with AMUSE standard for CSV export/import files.
Free Reporting – MR Comparison with PO & Received Qty
Comparison report for new MRs has been enhanced to show also PO qty
(reading from Actual PO) and MRS qty (received at site) for each Item.
Both complete and reduced (only MR qty changed) versions of this report
are available. The new report also shows, where existing, Client material code.
In case MRS Received (GOOD) qty was greater than MR qty a red check mark
is displayed beside MRS Qty
Free Reporting – Number of output records automatically calculated
No more need to tick the check-box, record count is automatically
performed at template selection:
AMUSE – Release X.3.0
“URS 005a - Increase digits for MID” asks to extend the number of codes
allowed for each MID Table in Bulk Piping Library: some MID Table already ran
out of coding possibility and for this reason the use of project specific
coding (numeric MIDCHAR) has become too extensive.
MIDCHAR code has always been 1 character long, allowing up to 53 possible codes in each MID Table (26 Uppercase alphabetical + 26 Lowercase alphabetical + . (dot) = ‘not applicable’ system code).
IMPLEMENTED SOLUTION
MIDCHAR code is now increased to 2 characters (mandatory, single
character not allowed): this extends coding possibility to 53 * 53 = 2809
different codes in each MID Table.
The introduction of such a basic update in Piping coding system (while
keeping the validity of all existing data and a seamless continuity of
operation) has been a big effort, requiring massive update in database
structure, existing data, applications and reports.
1) The first assumption was to modify all existing MIDCHAR adding a . (dot) to the existing code (ex.: C becomes C.): this allows, when deemed useful, to insert up to 52
different new codes between one already existing code and the next one.
This approach allows
insertion of the new codes in the most logical position inside the alphabetical
listing.
USAGE NOTE
N.B. it
is worth to remind that the new Search tool available for MIDCHAR selection
when building Piping Classes (see dedicated bullet earlier in this document)
helps finding anyway the required MIDCHAR quite easily wherever it is located
in the pick list).
|
Whatsnew - AMUSE X30.doc Page 29 of 76
|
Whatsnew -
AMUSE X30.doc Page 30 of 76
|
In case the MID Table content was to be totally redefined utilizing the
2 characters coding, the existing codes (those automatically updated with the
trailing . dot) cannot be deleted anyway, because this would invalidate all
already created codes in the existing projects.
A possible solution is to set a
‘C’ (Cancelled) flag to the existing codes
(so they will not be available anymore when building new Piping Classes) and
add to the list the new ‘2 characters’ codes in the preferred order
2) Also project specific MIDCHAR (numeric) have been
extended to 2 digits, and existing codes are automatically updated, adding a
leading 0 (zero), at release installation.
This extends project coding capability to 100
possible codes in each Project MID Table (from code 00 to code 99)
3) As a consequence of MIDCHAR extension also MID1 and MID2 codes have been
extended from 20/14 to 40/28 characters.
The same for FW Unique codes, increased from 9 to 10 characters.
|
INSTALLATION NOTE
All existing codes (MIDCHAR, MID, SIZETAB, SIZEK and UNIQUE CODES)
will be automatically updated at release installation to keep consistency
with the modified library codes).
|
A lot of applications, tables, batch processes and all related reporting
are affected by this URS.
Libraries:
·
MID Characters (D271)
·
DET List (D230)
·
MACRO Graphic codes (D441)
·
Coupling Sets (D442)
·
Size Library (D220)
·
Schedule -> mm Conversion (D222)
·
W/S/V
Library (D292)
·
FW Unique Codes (D001)
AMUSE – Release X.3.0
·
Client Codes (D002)
·
AMUSE
-> CAD Cross Ref. (D120, D121, D122, D123)
·
AMUSE -> CAD Exceptions (D124)
·
CAD
Allowed G/R Size (PDS100)
·
Project Control
Additional info (PCG400, PCG410, PCG420, PCG430)
Project
Activities:
·
Project MID Coding (D274)
·
MTO
Info Attribution Settings (D007)
·
Piping
Spec - DET (D301, D306, D311, D321)
·
Piping
Spec - MACRO (D401, D431)
·
Piping
Spec Release –
Batch
Process
·
MTO
(D505 – OOS components)
·
MTO
Explosion Process –
Batch
Process
·
Decoding
Maintenance (D591, D592, D593)
·
Project Weights (D593)
·
Bulk Summaries (D561, D570)
·
Bulk Requisitions (D610)
·
Requisition
Building –
Batch
Process
·
BOM Synchro (FLD571, FLD572)
·
MRS Material Receipts (FLD080)
·
TRS Material Transfer (FLD080)
·
MIR Material Issue (FLD080)
·
Allocation Process
|
Whatsnew -
AMUSE X30.doc Page 32 of 76
|
“URS 038 – More detailed MR
Description for Piping material” requires the possibility to enhance the Title of Material Requisitions for piping bulk material,
since sometimes such title is too generic
(it’s just the ECA code description) and do
not allow an immediate identification of the real type of material in MR.
Ex.: 45° ELBOW and 90° ELBOW can share the same ECA code (1551H) and
therefore the same MR title ‘C.S. REDUCING S.W. OR TH. FITTINGS’ not enough detailed to identify the type of
component.
IMPLEMENTED SOLUTION
The agreed solution was to allow the user to define, for each ECA code,
the technical information (MID Tech. Parameter) to be automatically decoded and
added to MR Title by Requisition Building process.
In order to get this result a column has been added in General ECA List
(table G110) in Engineering Library, to be filled picking one Parameter out of
all those included in that ECA structure (table D272).
USAGE NOTE
The selected Parameter can be different from ECA to ECA.
Only one Parameter is allowed for each ECA.
Input of Parameter is not mandatory: it should be
input only for ECA codes requiring a more detailed MR
Title.
INSTALLATION NOTE
The new column is empty just after AMUSE release installation: the
proper Tech. Parameters to be decoded in MR Title must be set, in each BU, by
the local Piping material managers.
During MR Building Process the Title of existing MR (those
already released to Actual) will stay unchanged.
The new Title will be assigned only to new MR.
Ex.: for ECA 1551H, in case the selected
Tech. Parameter was ‘DECODEFI’ then the MR Title would be different for 45° and 90° Elbows.
|
|
|
Whatsnew -
AMUSE X30.doc Page 33 of 76
|
“URS 005b – Increase digits for SPECs” requires extending to 16
characters both SPEC code and Client Spec code.
IMPLEMENTED SOLUTION
Both fields have been extended in all Tables, screens and reports.
“Client Spec” code has been renamed as “Spec Alias” code for uniformity
with the definition used for alternative code of Requisitions (“MR Alias”
code).
The MTO import process from PDS has been changed to manage the longer
Spec code, so the export files from PDS need to be modified accordingly.
This update requires that MTO files submitted to import process are from now on
in line with the extended SPEC code. Old type files cannot be imported since
they generate errors during import.
URS 006 - Improved Management of
Client Codes [Ph. 2]
REQUIREMENT
Creation of Unique Codes and Client Codes at Piping Class creation
stage.
IMPLEMENTED SOLUTION
See next point CAD INTERFACE - URS007.
AMUSE – Release X.3.0
When MR are created many reports are available that calculate and show
the weight of each MR Item and of the entire MR. In order to allow this it
is necessary that all materials
|
|
Whatsnew -
AMUSE X30.doc Page 34 of 76
|
Such mail is sent only in case at the end of Summary
refresh any materials exist in table
|
|
Once the mail is received the owner of the Unit Weight library can
utilize the new options available to filter the library table to view only the
rows relevant to the MTO of the subject project where weight is Missing (see W/S/V
Library dedicated bullet in this document).
|
|
S950) for the task WEIGHT_SUMMARY, with
recipients and input of optional mail texts:
|
Whatsnew -
AMUSE X30.doc Page 35 of 76
|
Log file will show the reason for message: in case the reason of failure
was the Summary Refresh process itself then the summary of errors in the batch
process is recorded in the Log file, while in case the only problem was in
sending the email then the Log file has only the following entry:
The details of the error can be read through Mail Monitor application
(see also next bullet) so that corrective actions can be taken and the email
can be re-sent without the need to run Summary Refresh again.
|
Whatsnew -
AMUSE X30.doc Page 36 of 76
|
Automatic email at MR Summary
building for missing Client Codes [Ph. 2]
Another automatic email can be optionally sent at MR summary building
request (table TD570) to inform the owner of the library that some Client Codes
has to be input to satisfy the MR of the subject project.
This applies only to Jobs where Client Code is requested (table C410_
Job settings).
|
|
D570
that cannot find the relevant Client Code in __________________ (table D002).
Once the mail is received the owner of the Client Code library can take
advantage of the new options to show only the rows relevant to the MTO of the
subject Job having Client Code still missing (see D002 dedicated bullet
in this document).
|
|
S950) for the task CLIENTCODE_MISSING,
with recipients and input of optional mail texts:
|
|
|
|
|
|
|
Mail Monitor [Ph.
2]
Currently
automatic emails can be sent at Spec Release and Summary Refresh; possibly
in the future other emails will be triggered by other events.
A new
application ‘Mail Monitor’ has been developed in order to allow a better
visibility and control of all emails sent by the AMUSE.
This application can be accessed from main screen
menu of Bulk Spec Management
|
|
(D201) and Summaries (D570) applications:
|
|
Whatsnew
- AMUSE X30.doc Page 37 of 76
|
|
|
|
|
|
Mails can be filtered by
Status
|
|
by Task
|
|
or by Sender (User) name
|
|
Whatsnew -
AMUSE X30.doc Page 38 of 76
|
The new application lists all emails sent (mails older than 30 days are
automatically deleted) with dates and sending result:
|
|
|
Whatsnew -
AMUSE X30.doc Page 39 of 76
|
|
Whatsnew -
AMUSE X30.doc Page 40 of 76
|
URS 007 - AMUSE to
SP3D interface [Ph. 2] REQUIREMENT
Scope of this URS is to define requirement to develop additional
interface functionalities of Amuse to other CAD systems such as SP3D.
This URS requires deep modifications the export process of Piping
Classes, introducing new functionalities like:
·
creation of a set of
new .CSV export files for ELENA (interface program to various CAD systems,
including SP3D)
·
keep
active the option for creation of dedicated .TXT files for PDS
·
split
of Spec size ranges into single sizes
·
management
of different Geometry Standard practices in size split
·
allow
the use of ‘DET groups’ for a simpler definition of size split
·
automatic
generation of all missing Unique Codes before MTO execution
·
management of a
number of additional data into export files (weight code, material grade, etc.)
·
modify the way some
data are defined and managed during export process (Table Suffix, Option code,
etc.)
·
management
of project MIDCHAR (00, ..., 99) across the entire process
·
exceptions
optionally applied based on 2 parameters match
·
warning about multiple applicable exceptions
IMPLEMENTED SOLUTION
The export process has been completely re-designed to satisfy the above
points and it required 11 new Library applications and 7 new
Project applications to be developed, all of them adopting the standard user
interface used by all application in Procurement & Construction modules.
|
|
|
Whatsnew -
AMUSE X30.doc Page 41 of 76
|
The following screenshots show where the new applications are located in
Engineering Library menu:
______________ (CAD020 - Geometric Standards) [Ph. 2]
This is the list of Practices for Geometry standards and the relative
code ranges: it will be used by export process to select the proper Practice,
based on Geometric code of
|
|
explosion.
|
Whatsnew -
AMUSE X30.doc Page 42 of 76
|
|
|
This table allows defining the ‘owner' DET code to be used when querying
three AMUSE=>CAD translation Libraries: Master Table (table CAD100),
Exceptions (table CAD124) or G/R size (table CAD200).
In the example above two DET for flanges (FL1, FL2) make reference to FLG
as ‘owner' of translation in all Master Table, Exceptions or G/R size: it
will be enough preparing the rows relevant to FLG in these libraries to manage
the translation of any of these DETs (they behave as a ‘Group of DETs’ in CAD
Library).
Other DET (FLGFF, FLGRF, FLGSO, FLGSP) meke reference to FLG for Master
Table and G/R size only, while they require their own rows in Exceptions.
USAGE NOTE
reference must not be made
to a DET that is not ‘owner' of that Library
‘owner' DET can be different, for
the same DET, in each Library
a DET can be ‘owner' in one
library and make reference to another DET for another Library
This table is automatically synchronized with DET List (table D230) to
show all type D DETs. At application
opening a warning message is shown in case Engineering has modified anything in
DET List, so that the synchro process can be run clicking on this button.
|
Whatsnew -
AMUSE X30.doc Page 43 of 76
|
|
|
|
|
This table provides rules and default values to be used for translation
of materials from AMUSE coding to CAD coding.
Full screen single record view is also available.
AMUSE – Release X.3.0
The only DET requiring input in
this table are those defined ‘owner’ of Master Table in
|
|
___________________________ (CAD120 – Size
/Thk Cross Ref.) [Ph. 2]
Here are prepared the conversion rules from AMUSE
Library codes to CAD codes for Sizes and Thicknesses.
AMUSE – Release X.3.0
___________________________________ (CAD121 – Rating Cross Ref.) [Ph. 2]
Here are defined the conversion rules for Rating from AMUSE Library
codes to CAD codes:
___________________________________ (CAD121 – End Condition Cross Ref.) [Ph. 2]
Here are defined the conversion rules for End Condition from AMUSE
Library codes to CAD codes:
AMUSE – Release X.3.0
|
|
|
|
|
In this table are listed all the exceptions to be
used to update the various default values defined in Master Table (Suffix,
Fabrication Categ., Model Code, Geometry Std, Modifier, Material Grade,
Weight Code) and in Equiv. DETs (Option Code).
Based on
the Library codes used in MID composition the relevant exception is
prepared where necessary.
Up to 2 possible
combinations of PARAMETER/MIDTAB/MIDCHAR can be used to determine the
proper exception.
|
|
|
|
Whatsnew -
AMUSE X30.doc Page 46 of 76
|
|
|
|
|
|
Decoding for the 2nd set of three codes
can be optionally shown/hidden (to save screen space):
|
AMUSE – Release X.3.0
|
|
All allowed Green and Red size pairs must be defined
in this table, for each DET, according to the various Practice codes.
The content of this table will be used during export
process when exploding Spec size range into all possible actual sizes of each
component.
The only DET codes available for in this table are those defined ‘owner’ of G/R Sizes in
|
table
|
|
In case of DETs having one size only the 2nd
size must be filled with * (asterisk)
|
Whatsnew -
AMUSE X30.doc Page 48 of 76
|
|
|
Here are defined the rules used to select the rows to be included in
export .CSV files for ELENA.
Reference is made to the field names of the final export scratch table
(CADB200).
Selection Criteria filed lists the value to be considered when exporting
(ex.: rows concerning Bolted Components must have ‘Y.’ in field B200_F_BOLTED
of table CADB200, etc.)
This table lists the versions of
SQL code available during export of .CSV files for ELENA.
Different versions
can be created in __________________ of the SQL code to be used to
build each export field content.
The version to be used in each Project must be defined in Project
initialization (see Project Applications)
INSTALLATION NOTE
Version 0 will be initialized at installation.
|
|
The final Select command used to create the export .CSV files for ELENA
can be customized to get the required content in each field.
Version 0 is prepared at new version installation; other versions can be
prepared later on, but a good knowledge of SQL language and of the structure of
the final export scratch table CADB200 is mandatory.
|
Whatsnew -
AMUSE X30.doc Page 49 of 76
|
AMUSE – Release X.3.0
The following screenshots show where the new applications are located in
Engineering Project Activities menu.
Unique Codes creation
|
|
|
Project codes( 00...99) translation
|
|
Export CSV files for ELENA
building rules
|
Export process of CSV files for PDS or ELENA
|
|
Whatsnew -
AMUSE X30.doc Page 50 of 76
|
|
|
|
|
|
Whatsnew
- AMUSE X30.doc Page 51 of 76
|
|
|
This table allows translating project specific
(numeric) rating codes.
The import process can be used to copy settings from
other projects when applicable.
_______________________ (CAD122_JOB – Project End Conditions 00...99)
[Ph. 2]
Same as Project Rating.
|
|
Same as Project Rating.
|
|
|
Whatsnew -
AMUSE X30.doc Page 52 of 76
|
|
|
The rules used to select the rows to be included in export .CSV files
for ELENA must be initialized: they can be copied from the Library table
(CAD370) or imported from another project.
They can also be customized in each project (even if should rarely
happen). Filling
is mandatory if export for ELENA is required.
______________________ (CAD401 – Project SQL Code Version) [Ph. 2]
Here is defined the version of SQL code used to fill each field of the
export .CSV files. Versions can be imported from General Library or form
another projects. Filling
is mandatory if export for ELENA is required.
|
Whatsnew -
AMUSE X30.doc Page 53 of 76
|
|
|
This table lists all Piping Classes.
It is automatically synchronized with the Actual list of Piping
Classes (table D201). Export
process can be run from table menu bar:
Two different Export processes are executed according to export
destination and different file types (.TXT for PDS, .CSV for ELENA) are created
and stored in sub-folders of AMUSE\[Project]\
default export folder:
Together with the export Spec files also the PDF file of the errors is
create.
|
|
|
|
|
Two columns show the timestamp of the last
performed Export or UC Creation process for each Spec: since
Export process also performs Creation of UC & Client codes, both
timestamps are updated at the end of export.
|
Another type of process can be run from table menu bar, with the only
purpose to create the missing Unique Codes (and Client Codes) only for all
materials generated after explosion of Spec size ranges:
|
|
|
Whatsnew -
AMUSE X30.doc Page 54 of 76
|
|
Whatsnew -
AMUSE X30.doc Page 55 of 76
|
These buttons allow easy querying of Spec List to show only the Specs
which have been released after the last Export or the last UC Creation process.
These Specs may require a re-run of the relevant process to be sure that
missing UC & Client Codes are created and CAD systems updated with the
latest Spec content.
At Form opening this check is anyway performed and the relevant warning
messages are displayed if necessary:
|
|
The UC creation process can be run also from this application.
This alternative way to run this process allows enabling Piping Spec
owners (or anyone else deemed necessary) to perform, with just few clicks, UC
creation whenever they want, through a free selection of Specs independently
from any real activities of involvement of CAD users group.
Any editing in this application is prevented, whatever the user’s Access
Level
|
Whatsnew -
AMUSE X30.doc Page 56 of 76
|
|
Whatsnew -
AMUSE X30.doc Page 57 of 76
|
Inquiry – Check on Due Date existence [Ph. 2]
Due Date is now a mandatory input in Inquiry Actual (table PUR120),
while it is still not mandatory in Temporary (table PUR120_T).
In case Due Date was not defined:
At ‘Save Edits’ in Actual or at Release from Temporary the following messages are shown, the
subject row is scrolled into view and Save / Release are prevented
Inquiry – Check on consistency between Issue date and Due date
[Ph. 2]
Also consistency between Issue date and Due date is now
checked: Due Date must be later than (or equal to) Issue date. In
case of inconsistent input the following message is shown and the Due date is
automatically cleaned:
|
|
|
|
|
Now table EXP220 (Main PO Materials) shows the
Plant Units relevant to each Item.
N.B. The same column listing Plant Units is
available also in applications EXPEDITING Visits (EXP500), INSPECTION
Visits (ISP500), IRN (EXP250) and SRN (EXP260) in screens where MR/Items
are listed, and also in application ROS Date (PCG200)
Since Plant Units are read directly from actual
tables of Engineering Requisitions (table D640 and D610) the latest
released MR rev is found: it provides the most updated info about Units,
regardless the MR rev that was actually purchased in each specific PO.
Expediters can therefore address available quantities based on the most
updated info to possibly optimize quantity in each delivery destination.
All Plant Units contributing to the final MR
quantity are listed (comma separated) in a dedicated new column:
|
Requisitions show the total qty required for each Item but do not
specify which Plant Unit the Item belongs to (for TAG materials) nor the
contribute of the various Plan Units to the total qty.
Knowing which Units are related to each Item and what is the contribute
of each Unit to the total MR qty can be useful during post-order activity since
Unit may affect delivery destination.
|
Whatsnew -
AMUSE X30.doc Page 58 of 76
|
AMUSE – Release X.3.0
|
|
|
|
|
This new column can be queried ‘By
Example’ to filter all Items having relation to a
|
|
specific Plant Unit:
|
USAGE NOTE
Due to the special technicality used to retrieve Unit codes from
Engineering tables, multiple Units cannot be specified in ‘By Example’
querying: only one individual Unit code can be input.
|
Whatsnew -
AMUSE X30.doc Page 59 of 76
|
|
Whatsnew -
AMUSE X30.doc Page 60 of 76
|
The following screenshot is typical of an itemized (TAG) material:
This is the same form in case of Bulk materials:
|
|
The button_________ can be used to show the total
quantity of any free selection of rows
in
the list.
|
USAGE
NOTE
This options can be useful to calculate
the total quantity in each Material Destination (when it is the same for
various Units) provided the destination is input in Unit ‘description’
field (table D720 – Plant
Units in Engineering module) like in the following example:
|
|
Whatsnew -
AMUSE X30.doc Page 61 of 76
|
AMUSE – Release X.3.0
|
USAGE
NOTE
Quantities are read
from Engineering tables (Actual) and are relevant to the latest MR rev
released.
It is important to
understand that the total quantity shown in this form are not necessarily
related to the Item PO qty as it is shown in the specific row in table EXP220
Main PO Materials, for various possible reasons:
MR quantity can be different from PO
quantity (latest MR revs still to be purchased or purchased qty was
partial/exceeding for some reason)
MR quantity may have been purchased in
different moments as MR revs were issued, thus in different PO revisions...
...or even with multiple POs to different suppliers
See the sample screenshots where Item 005
of Requisition 1541S/02 was purchased in three different PO
revisions (Rev 1, 5 and 6 of PO = P IT028) for a total purchased qty =
576 m.
|
|
Whatsnew -
AMUSE X30.doc Page 62 of 76
|
|
AMUSE – Release X.3.0
|
|
|
|
But still the latest MR qty
is different (582 m) as it shows in the qty split Dialog box:
|
|
Missing qty could have been
purchased in a different PO or not purchased at all.
|
|
Whatsnew -
AMUSE X30.doc Page 63 of 76
|
|
|
|
Whatsnew
- AMUSE X30.doc Page 64 of 76
|
During post order activity it may be useful to specify
the delivery destination of materials in advance to final inspection and
preparation for shipment.
Material Destination should be
input for each material (table EXP220 – Main PO Materials): this could help building Inspection Release (IRN),
Shipping Release (SRN) and Order for Shipment (OFS) for material with homogeneous
destination. Material destination has to be visible during selection of
materials to be included in each document.
USAGE NOTE
Material destination should not be input too much in advance to real
shipment: this to reduce the risk that input destination is no more valid when
real shipment occurs.
|
|
|
|
|
The existing field ‘Sub Lot
Description’, available for
each row of table EXP220, can be used to input Material Destination.
|
When a row is picked from the listbox the field is
compiled chaining Delivery Address Code, City and Country:
|
|
|
Whatsnew
- AMUSE X30.doc Page 65 of 76
|
|
|
|
|
|
Sub Lot Description (Material
Destination) field is then made available when selecting materials for IRN,
SRN or OFS:
|
|
|
AMUSE – Release X.3.0
|
|
|
|
|
Reporting: “PO List” - Req. Alias [Ph. 2]
Req Alias code is now shown when printing PO List
+ MR version:
|
|
Whatsnew -
AMUSE X30.doc Page 68 of 76
|
Reporting: “PO Material Status”
- Req. Alias [Ph. 2]
Req Alias code is now shown when printing PO Material Status
|
Whatsnew -
AMUSE X30.doc Page 69 of 76
|
Req. Alias code, Delivery Location (defined in PO), Sub Lot Description
(material destination) and Item Remarks (coming from table EXP220) are now
printed in DELIVERY STATUS report.
|
|
Sub Lot Descr.
(material destination) |
|
|
Item Remarks
|
MR Alias
|
location
|
AMUSE – Release X.3.0
|
|
|
|
Reporting: “DELIVERY STATUS” - Printing
Options [Ph. 2]
In DELIVERY
STATUS final screen some options are available which allow getting shorter
printout when deemed necessary.
Three check boxes can be un-ticked to suppress
printing of Estimate Delivery date, PO Delivery Location, Sub Lot
Description and Item remarks:
|
|
Example:
|
|
Whatsnew -
AMUSE X30.doc Page 70 of 76
|
Inquiry - Data Transfer from eProcurement to AMUSE
When eProcurement is used to Issue Inquiries and the following data is
updated in eProcurement, this data will be transferred as below, to AMUSE
Inquiry Actual (table PUR140) and Temporary (table PUR140_T) if the record is
in both:
|
eProcurement
Changes
|
AMUSE
Changes/Updates
|
|
|
•
|
Decline on Supplier
Side
|
Field: ‘Status’ –
Updated with ‘Declined’
|
|
•
|
FW side update Decline via QR details
|
Field: ‘Status’ –
Updated with ‘Declined’
|
|
•
|
FW side Decline via the Bid Status area
|
Field: ‘Status’ –
Updated with ‘Declined’
|
|
•
|
Sealed QR-Received Bid
(Un-Priced & Priced)
|
Field: ‘Status’ – Updated with ‘Received’ and
|
|
|
|
Field: ‘Received’ - Updated with received date
|
|
•
|
Sealed QR-Received Bid (Un-Priced)
|
No Data Transfer (Requires Un-Priced
and Priced)
|
|
•
|
Un-Sealed
QR - Received BidField: ‘Status’
|
Field: ‘Status’ – Updated with ‘Received’ and
|
|
|
|
Field: ‘Received’ Updated with received date
|
|
•
|
Yes
– Not Electronic QR
|
No Data Transfer (Bids not received
via eProcure)
|
|
•
|
Allow Bid Revision -
Decline
|
Field: ‘Status’ – data
Deleted
|
|
•
|
Allow Bid Revision -
Received
|
Field: ‘Status’ –
data Deleted and
|
|
|
|
Field: ‘Received’ – data Deleted
|
|
•
|
Supplier Advise Will
Quote
|
Field:
‘Promised’ – Updated with the
due date
|
|
•
|
Supplier Requests
Extension
|
Field: ‘Promised’ – Updated with the requested
|
|
|
|
Extension Date
|
|
•
|
Extension
Granted
|
Field: Extended
Due –Updated with the Granted
|
|
|
|
Extension
Date
|
Purchase Order - Data Transfer from eProcurement to AMUSE
When eProcurement is used to Issue PO’s and a PO has been acknowledged
in eProcurement (Supplier Side, FW side – Acknowledging individual and multiple
POs), this date will be transferred to AMUSE Actual (table PUR590), field: PO
Ackn.
|
Whatsnew -
AMUSE X30.doc Page 71 of 76
|
|
Whatsnew -
AMUSE X30.doc Page 72 of 76
|
Enhanced ALLOCATION Process – minimum % of Allocation
|
|
At click on_____________ the following dialog form
appears:
Click this button to accept any possible allocation (default setting)
To accept only 100% allocation of materials click on
..or input any user-defined value in the dedicated fields.
BOM(s) are then processed sequentially, according to the priority
defined in BOM table of Allocation screen: in case the required % was not
reached no material is allocated on that BOM and the process continues with the
next BOM.
|
USAGE NOTE
When minimum % are actually defined
different from 100% the Allocation process takes a longer time, due to the
sequential processing and the intermediate checks performed for each BOM at
allocation end.
|
|
Whatsnew -
AMUSE X30.doc Page 73 of 76
|
Target is to find BOMs that can be Completely allocated.
1) Allocation run accepting any quantity...
...ends with partial allocation only, no BOMs
can be allocated 100%
2) Allocation process run forcing Complete
allocation...
...ends with 2 BOMs that can be allocated 100%
AMUSE – Release X.3.0
All allocation reports now show Priority code. BOM are printed exactly
in the same order they have in allocation screen, thus by Priority (+
Alphabetical or BOM Weight or No. of Pieces as selected by the user).
Reports have been revised to provide more space to BIN code (max length
8 char)
|
Whatsnew -
AMUSE X30.doc Page 74 of 76
|
|
Whatsnew -
AMUSE X30.doc Page 75 of 76
|
u Ticket No. 936451 -
SQL Error when modifying sort fields on Delivery Status screen Order by functions has been fixed.
u Ticket No. 214434 - Job Leading Zeros Dropped from
Pricing Spreadsheet All XLS files have
been modified to treat Job No as a text even when it looks like a number
(instead as converting it to a number, as per Excel default formatting) Ex.: Job = 00123 will be considered text ‘00123’.
u Ticket No. 429864 - G110 ECA type ? to B
The new application ‘[X-G110] ECA General Library’ now allows changing undefined ECA types from ? to T or B
as required.
u Ticket No. 586441 -
CSV Export of Table D561 ‘Exploded MTO (Cut File)’
The new export has been modified to use semicolon (;) as field separator
in accordance with AMUSE standard for CSV file creation. This will prevent
misunderstanding of number symbols used as decimals/thousands separators.
u Ticket No. 761676 - Copying Macros
The problem has been identified and solved.
u Ticket No. 714032 - Line List application does not
close Excel The problem has been identified
and solved.
u Ticket No. 587410 -
Wrong size code in MTO import from PDS [Ph. 2]
An additional check has been added to highlight when a size coming from
PDS cannot be translated in table D120 (Matching Sizes). A question mark ? is
written in table D507 (MTO Items) in case of failed size translation.
u Ticket No. 323653 - Req. Index compared to previous
Rev [Ph. 2] The compare option was not
working and causing a SQL error.
u Ticket No. 767313 -
Inconsistency between PO and MR data [Ph. 2]
Item with Status = TBD in price PO Price List were wrongly dispatched to
E/I Main PO Materials (Table EXP220). TBD is not a
valid Status code to be considered as ‘purchased material’.
u Ticket No. 557461 - Delivery Status Report [Ph. 2]
Fixed error when comparing PO/IRN qty and MRS qty in case of Sublots.
u Ticket No. 397479 - TAG REQ: calculation of tot. qty
[Ph. 2] Fixed error when calculating qty from multiple units.
u Ticket No. 690472 - Change to Material Delivery Status
[Ph. 2] See dedicated bullet in PROCUREMENT chapter
u Ticket No. 153169 - Make Due Date a Mandatory Field in
PUR120 [Ph. 2] See dedicated bullet in
PROCUREMENT chapter
u Ticket No. 388037 - TAG req. - Null TAG not allowed Saving Item rows without a TAG name is no more
allowed.
u Ticket No. 154953 - TAG req. – Export MMS Data Table
as .DOC file
|
Whatsnew -
AMUSE X30.doc Page 76 of 76
|
Reporting: “DELIVERY STATUS” - New fields
u Ticket No. 153169 - Make Due Date a Mandatory Field in
PUR120 [Ph. 2] See bullet in Procurement:
Inquiry – Check on Due Date existence
Inquiry – Check on consistency between Issue date and
Due date
u Ticket No. 181710 - Requisition Alias print on reports
[Ph. 2] See bullet in Procurement:
Reporting: “PO List” - Req. Alias
Reporting: “PO Material Status” - Req. Alias
u Ticket No. 901810 -
Split qty by plant unit in post order [Ph. 2] See bullet in Procurement:
Post Order - Enhanced display of Req. Item split by
Units and quantities
u Ticket No. 353187 - Group material with same
destination [Ph. 2] See bullet in Procurement:
Post Order - Shipping Destination
u Ticket No. 989344 -
Prevent save of TAG Req when out of user ECA competence
[Ph. 2]
Creation of REQ out of ECA Competence is prevented
