MARIAN 2007 (6.

2)
Release Notes
Release 6.2.1

Release Notes MARIAN 2007 (6.2.1)

1 of 26

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

Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Contractor Rights in Technical Data clause at DFARS 252.227-7013, subparagraph (b) of the Rights in Computer Software or Computer Software Documentation clause at DFARS 252.227-7014, subparagraphs (b)(1) and (2) of the License clause at DFARS 252.227-7015, or subparagraphs (c) (1) and (2) of Commercial Computer Software---Restricted Rights at 48 CFR 52.227-19, as applicable. Unpublished---rights reserved under the copyright laws of the United States. Intergraph Corporation Huntsville, 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 of such warranties. Intergraph believes the information in this publication is accurate as of its publication date. The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document. The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE

Release Notes MARIAN 2007 (6.2.1)

2 of 26

2007
Version: Initial Release 6.2.1

MSC-No. Cust.Ref.No Type

1083 CR-MA1083 Change Request

Comment
The loading of fab tracking data has been tuned significantly. An upload button is now provided in screen P.90.01 Load Fab Tracking to upload any file to the UTL file directory.

1084

CR-MA1084

Change Request

Now the highest requisition supplement released is shown in screen P.90.11 Maintain Fab Tracking. Location, warehouse and receiving status are found for material that has been received AND posted to the inventory. The load job has been tuned. So far the values of alternate 0 were always displayed in screen P.30.22 Commercial Evaluation, folder 'Awarding'. From now on the values of alternate 0 are only shown if alternate 0 or none of the alternates have been assigned to the bidder. If one of the alternates has been assigned (selected) the values of this alternate are displayed instead. Please note that all fields in the matrix are filled by CIPs. If you want to see different values it is up to you to modify the CIPs accordingly.

1340

CR-MA1340 / V-ID2643

Change Request

1354

CR-MA1354 / V-ID2644

Change Request

Now splits can either be assigned completely or partly to a bidder (screen P.30.22 Commercial Evaluation, folder 'Awarding'). To assign a split completely to a bidder you have to double-click on one of the matrix fields or you assign all positions to a bidder by double-clicking on the bidder or you select one of the alternates (as up to now). To assign a split partly to a bidder you have to doubleclick on checkbox 'Split' and mark checkbox 'Sel' in the window that is opened after the double-click. Splits can only be assigned partly to a bidder if - the commercial evaluation has been completed for this bidder (i.e., date 'Final Comm Eval' is set) and - a technical evaluation is not required or has already been passed (i.e., date 'Tech Eval Comp Date' is set in screen P.30.23 Technical Evaluation) and

Release Notes MARIAN 2007 (6.2.1)

3 of 26

2007
Version: Initial Release 6.2.1

- the quote has not been rejected and - a bid has been returned and - the approval process has not been started for the quote and - the quote has not been approved and - the line item has not been assigned to a different bidder whose quote has already been approved or for whose quote the approval process has been started. If the corresponding line item of a split has already been assigned completely to any other bidder this assignment is automatically revoked when committing the change. Only partly selected splits are kept.

If a split has been assigned partly to a bidder the background color of checkbox 'Split' is set to cyan in folder 'Awarding' and in the window showing alternates. 1382 CR-MA1382 / V-ID2595 Change Request For req line items with item rule TAB short description and description as delivered by m_pck_std_custom.ident_desc/ident_long_desc are stored at time of approval in table m_ident_nls_hists.After approval, for these req line items the description is shown as it was at the time of approval using m_pck_std_custom.ident_desc_hist. Please note that this functionality is only available for requisitions approved with MARIAN 6.2. 1526 TR-MA1526 Bug Fix Screen R.20.01, Column "MARIAN Log File" will be filled when log file is created. In the logon screen you can now see the description of a project or a product group in the multi-record area at the bottom of the screen. For having enough space to show this information fields 'Nls' and 'USID' have been removed.

1628.1

CR-MA1628/V- Change Request ID1888/PMSM020

Checkbox 'Avail. for Supplier' has been added to screen P.70.71 Expediter Workload. With this indicator you can control whether you want the supplier to be able to enter data for this order or not when using the supplier logon. Per default all orders are available. If a user logs in as a supplier, freight forwarder or packer he will only see his 'own' orders for that this checkbox is
Release Notes MARIAN 2007 (6.2.1)

4 of 26

2007
Version: Initial Release 6.2.1

set. Please note that this indicator is always set on order level. I.e., regardless of how many requisitions are associated with an order the order is either available for a supplier or not. You cannot allow modifications for a specific combination of order and requisition and not allow it for another combination of the same order with a different requisition.

Project default ZP_SUPROLE is now used in the following way: You can allow your suppliers, their freight forwarders or packers to log on into MARIAN so that they can enter item shipment related data such as MCS numbers or packing information. To limit the access of these users to their 'own' orders, i.e., to avoid that they can see the orders of other suppliers, you can define a role to which only a restricted number of modules is assigned. If you assign this special role to project default ZP_SUPROLE the expediter workload (module P.70.71) will allow a user who has logged in with this role only to query for his own orders. All other users which log in with a role that differs from that of the project default will be allowed to see the orders of all suppliers. Moreover if a user logs in with the role given by ZP_SUPROLE he can only see the orders that have been marked as being available for suppliers. This indicator can be set in screen P.70.71 Expediter Workload. The modules that should be assigned to the 'supplier role' at least are: MARIAN MENU PROC P700 P7071 P7072 P7074 It is up to you to decide to which other screens these users may have access as well. Freight forwarders and packers have to log in with the supplier's user name and password. To enable a supplier to log on into MARIAN you have to perform the same

Release Notes MARIAN 2007 (6.2.1)

5 of 26

2007
Version: Initial Release 6.2.1

steps as for any other user, too. I.e. you have to define a user group (screen A.20.41), a user (screen A.60.01.01) and finally maintain the user security for projects (screen A.20.06.02).

1830.1

V-ID1830

Change Request

Split tag functionality is now also available in screen P.70.74 Packages. Splits created by traffic (i.e. screens P.70.74, P.80.11, P.80.51) are not shown in screen P.70.72 Expediting Details.

1832 1889 1890 1891 1892

CR-MA1832/1- Change Request 43303339 1889 1890 1891 1892 Bug Fix Bug Fix Bug Fix Bug Fix

Screen S.10.05: sequence of fields swapped. Packages m_pck_report and m_pck_menu_sort revised. Packages m_pck_revision and m_pck_visual_attr revised. A.6063 - Update of the onlinehelp. Some modifications/enhancements of the LOVs of P.10.82 and P.80.51. Package m_pck_broadcast modified to be compatible with Oracle 10g Release 2. Screen P.10.81, LOV added. Screens R.30.07 and R.30.08 The new project default ZR_DUP_RLI (default 'N') enables the possibility to insert line of a requisition that uses the same commodity code/ident etc. If this is set to 'Y' the new line must be unique. BOM Integration with SmartPlant Enterprise Minor changes and fixes concerning SP3D integration. New column line item order on MTO-types (m_mto_types.order_by), used by CIP. List of ordering options definable with project-default ZR_RLI_ORD. Parm values of this project-default are shown in the LOV on this field. When this field is filled instead of the ordering e.g. defined in the requisition template a CIP is executed, m_pck_req_custom.order_req. Parameters are the primary key of the requisition, the default increment for the positions(project default ZR_RLIINC) and the order

1893

1893

Bug Fix

1894 1929.1

1894 TR-MA1929

Bug Fix Bug Fix

1993.2 2000 2033

V-ID1993 V-ID2000 V-ID2033 / MSC#12332

Change Request Change Request Change Request

Release Notes MARIAN 2007 (6.2.1)

6 of 26

2007
Version: Initial Release 6.2.1

criteria defined here. 2075 V-ID2075 Change Request The new folder 'Heat Numbers' has been added to screen P.70.72 Expediting Details. So far you could only assign one heat number to an item shipment. This heat number was defined in screen C.10.04. Now you can assign as many heat numbers to an item shipment as necessary. Fields 'Heat Number' and 'Certificate Number' have been removed from folder 'Item Shipments'. They have been replaced by two checkboxes: 'Heat' and 'Heat Complete'. Indicator 'Heat' shows whether any heat number information has already been entered for an item shipment. Indicator 'Heat Complete' shows whether the heat number information is complete. The heat numbers for an item shipment are regarded as being complete if for the item shipment quantity (or even more than that) heat numbers have been entered in folder 'Heat Numbers'. Moreover some material, for example valves, requires two heat numbers (fields 'Heat Number' and 'Heat Number 2' in folder 'Heat Numbers'). To identify this material project default ZP_HTWHERE has to be set. All where conditions that have been defined in screen A.60.06 for module 'P7072' can be selected for this project default. If the ident of an item shipment is covered by the view of this where condition two heat numbers have to be entered. If the ident is not covered by the view only one heat number is needed. If the project default has not been set, the view assigned to the project default has not been created or is invalid it is assumed that only one heat number is required for the material. If folder 'Heat Number' is opened by mouse-click on the folder you will see all item shipments. If this folder is opened by double-clicking on checkbox 'Heat' in folder 'Item Shipments' this specific item shipment is displayed. If this folder is opened by double-clicking on an MCS, IRC or release note number in folder 'Item Shipments' all item

Release Notes MARIAN 2007 (6.2.1)

7 of 26

2007
Version: Initial Release 6.2.1

shipments of this MCS, IRC or release note number are shown. The query context can be seen in field 'Context' at the top of this folder. Regardless of the current query context you can query for all item shipments by just executing a new query. The number of item shipments that are available also depends on the setting of project default ZP_ZEROISH. If you want to see all item shipments regardless of their quantity project default ZP_ZEROISH has to be set to 'Y'. To exclude item shipments with zero quantities from the display this project default has to be set to 'N'. If the project default is set to 'A' item shipments with zero quantities are displayed as long as indicator 'Acknow' has not been marked. Please note that features such as attached attributes or attached comments are only available for item shipments with heat numbers because attributes or comments dealt with here are associated with heat numbers, not with item shipments. For the management of attached attributes or comments for item shipments you have to go to folder 'Item Shipments'. Likewise, when deleting a record you do not delete an item shipment but only the heat number. Certificate number, manufacturer and file location are fields that were already available for heat numbers. As it is now possible to enter a second heat number fields 'Certificate Number 2' and 'Manufacturer 2' have been added. Over and above, fields 'Vendor Code' (identification or reference name for the item used by the supplier), 'Mark' and 'Mark 2' (marking that appears on the item with the first and second heat number) have been added. Moreover, in folder 'MCS' the field 'Complete Date' has been added. Future dates are not allowed. The date of completion must be equal to or greater than the MCS date. To be allowed to set this date you need to have privilege 'SET MCS COMPLETE DATE'.

Release Notes MARIAN 2007 (6.2.1)

8 of 26

2007
Version: Initial Release 6.2.1

An IRC can only be assigned to item shipments with an MCS if this date of completion is set. Once an IRC has been assigned to at least one of the item shipments associated with an MCS the date of completion cannot be modified any longer. 2092 TR-MA2092 Bug Fix Screen C.40.01 revised. "Setup Set assigned" now only affects the BOM Total quantities. Screen A.60.01.02: added missing tables to m_pck_user.delete_user Fields 'Last Contact' and 'Next Contact' have been added to screen P.70.71 Expediter Workload. They show the date of last and next contact with the supplier respectively and can be modified. Depending on whether requisitions are on display or not and whether different requisition codes (not just different supplements of the same requisition) have been assigned to an order cycle or not this date either refers only to the current requisition code (requisition data on display) or to all requisition codes (requisition data not on display). If just one requisition code has been assigned to an order this date always refers to that requisition, regardless of whether requisition data are on display or not. 2187.2 V-ID2187 Change Request Some minor bug fixes in connection with new screen P.60.05 MSCM Milestone Explorer. When entering values for 'Cost Value Total' on new records for other costs assigned to quotes, quote details, orders or order line items without coming through field 'Other Cost %' before saving the data these values are now kept. When message MAR-30850 "Shortage quantities have been detected." appears in screen P.30.04 Order Assignment and you doubt that this message is correct because there are no shortages you can take an additional look in the directory where log files are stored. There you will find a file named P3004_LOG_xxx.log. In this file you can see the true cause for the abortion of the supplement creation process. Screen P.70.71 Expediter Workload has been tuned.

2101.1

TR-MA2101

Bug Fix

2184

TR-MA2184

Bug Fix

2218.1

TR-MA2218

Bug Fix

2224.1

TR-MA2224

Bug Fix

2226.1

TR-MA2226

Bug Fix

Release Notes MARIAN 2007 (6.2.1)

9 of 26

2007
Version: Initial Release 6.2.1

2229

V-ID2229

Change Request

Screen P.90.11 Maintain Fab Tracking has been converted into a core workflow screen (CWS). Different from the other CWS, the configurations used for this screen depend on the fabrication type. For these purposes standard configurations (and all other configurations existing for that fabrication type) are automatically created and maintained each time an attribute is added to or removed from the fabrication type. The name of this standard configuration is composed of the name of the project (or product group) and the name of the fabrication type. This standard configuration consists of all fields available for this screen and the attributes of the fabrication type. Currently up to 30 attributes are supported. Each time you select a different fabrication type another configuration is applied. To facilitate the start of using the new CWS standard configurations are also created when installing this service pack. For field 'Tag Number' fastcalls to screens B.20.01, P.60.01 and P.60.05 have been provided in a pop-up menu. By double-clicking on the tag number you can also call screen B.20.01. Please read also the online documentation provided for screen P.90.11 to get to know all special features.

2233.1

TR-MA2233

Bug Fix

Attached comments are now available again in all folders of screen P.70.73 Reference Data. The following changes have been implemented for the fab tracking module: At the beginning of the import process CIP m_pck_fab_custom.pre_import is called; at the end of the loading process CIP m_pck_fab_custom.post_import (screen P.90.01 Load Fab Tracking). The primary key of the import job (fij_id) has to be passed to these CIPs. At the beginning of the loading process CIP m_pck_fab_custom.pre_load is called; at the end of the loading process CIP m_pck_fab_custom.post_load (screen P.90.11 Maintain Fab Tracking). The primary key of the fabrication type (ft_id) has to be passed to these CIPs.

2238

CR-MA2238 / V-ID2862

Change Request

Release Notes MARIAN 2007 (6.2.1)

10 of 26

2007
Version: Initial Release 6.2.1

Button 'Execute CIP' has been added to screen P.90.11. When pressing this button CIP m_pck_fab_custom.update_ft is called. The primary key of the fabrication type (ft_id) is the only argument for this CIP. In a MARIAN standard installation all these new CIPs do not do anything at all. 2264.2 TR-MA2264 Bug Fix Screen A.60.01.01: Item rfu_id has been added to avoid the error message. As Oracle can cause problems when querying for data containing '#' a check has been implemented in screens P.50.01 Orders and P.50.07 Maintain Orders. If an order number contains '#' a warning appears. It is up to you whether you want to change the order number or not. If data contain the character '#' you either have to query for all data or you have to use the wild card character '%' to retrieve data. If you try to perform a restricted query by using character '#' you will get the error message 'Unable to perform query'. 2303.2 TR-MA2303 Bug Fix Package M_PCK_PO revised to avoid error message when importing POs incl. APPROVED_DATE via OPI. Changes on Substitutions. For the details refer to documentation V-ID2307_Changes_on_Substitution.pdf. Screen P.50.07: package m_pck_po revised to solve approval problem. Screen P.50.07 revised, to avoid error message ORA04091: table M_SYS.M_PO_HEADERS is mutating when deleting a PO. The list of values is now also available for attributes with valid values depending on the language. Package M_PCK_MSCM revised. GET_RELEASED_QTY takes last_total_release_qty into account. Package m_pck_po revised to resolve approval problem. Screens B.20.01.35 and B.20.01.41 now can display job log file. License Agreement displayed on every license install.

2287.2

TR-MA2287

Bug Fix

2307.1

V-ID2307

Change Request

2333.1

TR-MA2333

Bug Fix

2339.2

TR-MA2339

Bug Fix

2343

CR-MA2343

Change Request

2375.1

TR-MA2375

Bug Fix

2388.1 2394

TR-MA2388 CR-MA2394

Bug Fix Change Request

2401.1

V-ID2401

Change Request

Release Notes MARIAN 2007 (6.2.1)

11 of 26

2007
Version: Initial Release 6.2.1

from 6.2.1 the user installing a license text will be prompted to accept a SLA. User can choose if his agreement is for evaluation purpose or standard level. He can also choose the region/scope where the agreement should be for. For the sake of our big customers who often install license texts, user does not have to step through all pages, and he does not need to choose the correct region/scope, but simply can press the "Accept" button to go ahead. 2413.1 TR-MA2413 Bug Fix Extraction of string of correct length from template data to avoid numerical error when importing packing list with release notes. Multiple selection of packages from a release note implemented. When changing the delivery designation the routing method is now reset in screen P.70.21 Global Order Line Update. Otherwise it is possible to save a wrong combination of delivery designation and routing method on item shipments. Multi Select LOV fr Role/Menus in A.30.03 ======================================= Choose in A.30.03 on tab page 'ROLE MENUS' between * copying appl roles menus including all security definitions (only possible, if role is "empty") * selecting menu items multiple via LOV, and reducing the display of possible menu items by "filling" the choosen menu items to the selected role. 2445.2 TR-MA2445 Bug Fix Package M_PCK_BOM_SETUP revised to make the copy of Discipline BOM Views working. Next block functionality is no longer available in the second block of screen A.60.31 Messages (NLS). To maintain unsubscribed users you have to double-click on the message number in the first block. There is no other way to reach the second window. New Project Default ZX_REP_FMX gives the user the possibility, to define an own "Start Reports" Form. Input the Formname (only praefix of the filename, not the suffix or extention) into the parameter value. Open A.30.01 Menus and recognize new checkbox Std. StartRep. Query all your reports (menu type = REPORT) and check this reports, you want to start, using your own

2429.1

V-ID2429

Change Request

2438.2

TR-MA2438

Bug Fix

2445.1

V-ID2445

Change Request

2446.1

TR-MA2446

Bug Fix

2450

V-ID2450 / CR- Change Request MA909

Release Notes MARIAN 2007 (6.2.1)

12 of 26

2007
Version: Initial Release 6.2.1

"Report Start Form". Please be advised, that your "Report Start Form" should transfer all information to the report, which help to identify user / project /project group/ dp_id, us_id etc. All MARIAN standard reports are using following programming, to transfer required data to the report: v_other_report_property := v_other_report_property||' p_user='||:global.user; v_other_report_property := v_other_report_property||' p_projekt='||user; v_other_report_property := v_other_report_property||' p_discipl='||:global.dp_id; v_other_report_property := v_other_report_property||' p_arun_id='||to_char(:arun.arun_id); v_other_report_property := v_other_report_property||' p_us_id='||:global.us_id; v_other_report_property := v_other_report_property||' scs_ind='||:arun.scs_ind; v_other_report_property := v_other_report_property||' p_readonly=yes'; v_other_report_property := v_other_report_property||' paramform=no'; It is recommended to use MARIAN reports as a base for userdeveloped reports. All MARIAN reports are delivered in source code. At least check Before-Report-Trigger, where the mpck_login.select_login(p_us_id) is used, to make sure that the view to the MARIAN tables is according your Project login.

2457.2

TR-MA2457

Bug Fix

When calling screen P.30.03 Inquiry Assignment twice for the same requisition the update of an inquiry does not work because the system tries to create records that exist already. This bug has been fixed. The order sequence for creating order line items for an order based on a bid evaluation has been corrected. S.50.15: - definition of nominal size table for each tabfolder - Lov for selection of tables shows only tables used in rules of the parts defined for the tabfolder S.50.16 - Direct input (without LOV) of table details now validated - Possibility to enter the TD_CODE instead of description by inclosing it in ' '. - Worklist shows group and part

2464.1

TR-MA2464

Bug Fix

2469.1

CR-MA2469

Change Request

Release Notes MARIAN 2007 (6.2.1)

13 of 26

2007
Version: Initial Release 6.2.1

2475

V-ID2475

Change Request

Install procedures revised. Included missing inserts for m_list_checks and m_item_types. Insert of fluid class keys with parameter dp_id instead of mpck_login.dp_id

2480

V-ID2480

Change Request

Part 1 of V-ID2480 as prerequisite for final implementation of this Change Request. If project default ZP_ISH_QTY has been set to 'KEEP' and only contractual dates (incoterm, delivery place, promised contract date) are changed for a position (no change in quantity) the additional item shipment that is created is deleted when approving the change order. To avoid that any changes are missed by an expediter feature 'Highlight Changes' in screen P.70.72 Expediting Details now compares item shipments with the last acknowledged previous item shipment and not with the last one.

2482

CR-MA2482 / V-ID2886

Change Request

2488.1

TR-MA2488

Bug Fix

When working with new expediting (ZP_NEW_EXP = 'Y') and summarizing change orders (ZP_SUM_CO = 'Y') the approval of a change order cannot be taken back if more than one revision has been created for a supplement. This bug has been fixed. Now the data created in the background for traffic use the revision instead of the supplement so that approvals can be taken back again. Please note that this change only works for orders that have been created after the implementation of this patch.

2489

CR-MA2489

Change Request

Screens P.50.01 Orders, P.50.07 Maintain Orders and P.70.73 Reference Data now use the new project default ZX_PRIVREQ and privilege 'ASSIGN EXPEDITER'. If the project default has been set to 'N' (default) you can assign an expediter to an order. If this project default has been set to 'Y' you can only assign an expediter when owning privilege 'ASSIGN EXPEDITER'.

2491.1

TR-MA2491

Bug Fix

Screen R.20.01: columns in m_tmp_att_vdrs and m_tmp_used_notes enlarged, added more log info in m_pck_mto KEEP_ATTACHMENTS code. Reload Isometric Drawings ========================= For the details of this new feature refer to document V-

2493.1

V-ID2493

Change Request

Release Notes MARIAN 2007 (6.2.1)

14 of 26

2007
Version: Initial Release 6.2.1

ID2493_Reload_Isometric_Drawings.pdf. 2496 2497 V-ID2496 CR-MA2497 Change Request Change Request 10 new Visual Attributes added to all forms Fastcalls to S.50.03/S.50.07 removed from Screens A.20.10, PDS.10.01, PDS.10.12, PDS.10.13, PDS.10.14, S.50.04, S.80.31 Screen A.60.06: Increase line number before every insert into m_adm_query_cond_details. Missing entries of A.30.01 added. Screen A.10.30: - In A.10.30 Account codes budget, original budget and currency are required - Insert in m_jobs will use project default ZX_CURCY when no currency_id supplied. If in screen P.50.01 Orders an order is created based on a requisition the account code of the requisition is now taken over per default. But this default can be overwritten. Commands CTRL+H (Online Help), DEBUG and TRACING removed from menu. To avoid waiting sessions if several users press button 'Automatic Number' before the other users have finally committed their changes to the data base a commit has now been implemented for this button. This commit does not affect the screen data. It only affects the number ranges of screen P.10.35. (Button 'Automatic Number' can be found in screens P.30.21 Prepare RFQ, P.50.01 Orders and P.50.07 Maintain Orders.) 2539 V-ID2539 Change Request Limit visibility in MSCM by Section =============================== The section that can be assigned to a user in screen A.20.06.02 User Security for Projects is now not only used by screen P.30.01 Requisition Workload but also by screens P.30.11 Inquiries, P.50.01 Orders, P.50.07 Maintain Orders and most expediting screens such as P.70.61, P.70.62, P.70.71, P.70.72 and P.70.73. In other screens such as R.30.11 or P.50.19 the availabilty of double-clicks, buttons or fastcalls can be restricted. In

2505

TR-MA2505

Bug Fix

2510.2 2520.1

TR-MA2510 TR-MA2520

Bug Fix Bug Fix

2525.1

TR-MA2525

Bug Fix

2526.1

TR-MA2526

Bug Fix

2528

TR-MA2528

Bug Fix

Release Notes MARIAN 2007 (6.2.1)

15 of 26

2007
Version: Initial Release 6.2.1

these cases you will get a message that informs you that you do not have the rights to see the selected inquiry or order. To limit the availability of requisitions, inquiries and orders you can not only assign a section to a user security (screen A.20.06.02) but you can also assign one or more sections to a user's role. For this purpose folder 'Sections' has been added to screen A.30.03 Roles/Menus. If no sections have been entered in screens A.20.06.02 and A.30.03 you can see all requisitions, inquiries and orders. In this case the section of a requisition, an inquiry and an order is of no interest. If a section has been entered in screen A.20.06.02 you can only see requisitions, inquiries and orders that have been assigned to that section or that have no section at all. Any entries of sections that have been made in screen A.30.03 are disregarded. If no section has been entered in screen A.20.06.02 but one or more sections have been entered in screen A.30.03 you can only see the requisitions, inquiries and orders that have no section or that have been assigned to these sections. 2547 2549 V-ID2547 TR-MA2549 Change Request Bug Fix PROJ_ID removed from Company Symbols. Screen S.50.06: spec delete now also deletes m_spec_compares, m_spec_func_mappings, m_spec_func_sections, m_pds_pdl_master_result. Performance of PDS.10.12 improved. Receiving enhancements to consider Heat Number and Certificate Number. Screen A.60.06: correct display of tab page names Screen PDS.50.01: reducing the length of block names. S.80.24 now writes tag history after changes to tag number Screens B.20.01 and B.20.03: The data in the LOV is filtered depending upon the project Default ZB_QRY_DP. If the Project Default is set to

2550 2555

TR-MA2550 V-ID2555

Bug Fix Change Request

2557 2558 2565

TR-MA2557 TR-MA2558 TR-MA2565

Bug Fix Bug Fix Bug Fix

2582

V-ID2582 / CR- Change Request MA994

Release Notes MARIAN 2007 (6.2.1)

16 of 26

2007
Version: Initial Release 6.2.1

1 that is the default setting the LOVs will show all the data irrespective of the Discipline I.e. the existing functionality will be applicable. If Project Default is set to 2 then LOVs will show data corresponding to Login and Query able Disciplines. . If Project Default is set to 3 then LOV s will show data corresponding to Login Discipline only. 2585.1 CR-MA2585 Change Request With the new project default ZP_DEF_SLI you can control the default setting of checkbox 'Summarize Line Items' in screen P.30.21 Prepare RFQ, folder 'Inquiry'. The default value of this project default is 'N'. 2587 TR-MA2587 Bug Fix Screen S.10.01: block property update changed columns only set to No to prevent Oracle Forms bug when updating CLOBs. The lookups for the two country code fields in the first window of screen P.20.01 Suppliers were identical. This resulted in always displaying the same values even if the two values were not really identical. This bug has now been fixed. Changes to S.50.06 ================= - Spec Item Notes can now be entered on window 2 in tabfolger Spec Item Notes - If a spec item has notes assigned, then the field commodity code is displayed with background color blue - Field 'This Note' is now optional - It is possible to enter new general notes (until now only definable in S.50.09) when entering spec item notes. This is only possible for users with insert rights for S.50.09. 2594 TR-MA2594 Bug Fix Screen S.40.10: update changed columns only in GD.OnUpdate-Trigger Preventing Duplicate Tag Numbers ================================ Existing functionality: While creating the position attributes of a node following was the existing functionality. For the item types TWM, TOM: The ident code and commodity code are getting copied if the same combination (group+ part + tag number) already exists. If this is a new combination a new commodity

2588

TR-MA2588

Bug Fix

2592.1

V-ID2592

Change Request

2594.1

V-ID2594

Change Request

Release Notes MARIAN 2007 (6.2.1)

17 of 26

2007
Version: Initial Release 6.2.1

code will be generated with the name same as tag number and a new ident is getting created. For item type TAB: Always a new ident is getting created whatever the group, part and tag number combination is (is it existing one or a new one). No commodity code will be created for this item type.

New functionality: For item type TAB also depending on the Project Default ZB_DUTAB the ident should be copied or created depending up on the combination (Group + Part + Tag Number + Commodity Code). If the combination is new an ident should be created. If the combination is already existing old ident code should be copied. If the Project Default ZB_DUTAB is set to N that is the default setting the existing functionality will work. If the Project Default ZB_DUTAB is set to Y, then new functionality will be applicable. 2595 TR-MA2595 Bug Fix Screen P.20.01: Field 'Total Amount Purchased' has been enlarged. Screen R.20.01. The keep attachment functionality was corrected. The deleted BOM positions, which was added as manual items will not created anymore. Fields 'Size 1' and 'Size 2' have been added to folder 'Line Items' in screen P.50.07 Maintain Orders. It is not longer possible to entera BOM position with Itemrule SOT and field tagnumber filled. B.10.21: ORA-6502 exception coming on WHEN-BUTTONPRESSED trigger. Corrected the problem by moving call to CLOB in DB procedure. The calculation of the released quantity has been corrected. Now all cases are covered regardless of whether one or more requisition line items are associated with an order line item or not, regardless of whether the requisition line items are coming from different supplements of the same requisition or not, regardless of whether the requisition line items have predecessors or not... Screen B.10.06: LOV on 'Copy from User View' corrected.

2596

TR-MA2596

Bug Fix

2597

CR-MA2597

Change Request

2600.1

CR-MA2600

Change Request

2602.1

TR-MA2602

Bug Fix

2613

TR-MA2613

Bug Fix

2618

TR-MA2618

Bug Fix

Release Notes MARIAN 2007 (6.2.1)

18 of 26

2007
Version: Initial Release 6.2.1

2621

TR-MA2621

Bug Fix

Screen B.40.31: Corrected the locking mechanism in case when only one node is locked. Delete of project doesn't try to delete non-existing tag number sequence. Screen S.50.06: records deleted from m_appl_menu_block_items to avoid error meesage FRM40105: Unable to resolve reference to item SI.DELETED_SPEC_ITEMS. Trouble Report revised. In screen D.40.12 VDR Sets data are now committed automatically before inserting details to a VDR set via multi-LOV (second window). So far you had to commit a new VDR set before you could assign any details. Screen S.50.15 revised, generation of geometric now using the correct nominal size table as defined in S.50.15. Screen B.20.03: Autofilter. The functionality has been corrected by correcting the view creation procedure which was producing wrong data. Constraint of table m_mcs_numbers changed to ON DELETE CASCADE. Package m_pck_inquiry revised to avoid duplicate items when creating a PO from Inquiry. If project default ZP_ISH_QTY has been set to 'KEEP' it may occur that more than just one item shipment exists for a master tag. So far this has not been taken into account. This can lead to an error when trying to approve an order. This bug has been fixed. New Feature implemented 'Attach documents to Positions and Nodes on BOM'. The main functionality of this task is to attach or link documents to the positions and to the nodes in BOM using the user interface B.20.03 Adv. maintain BOM. The functionality of attaching documents already exists in MARIAN for Requisitions. This task is also extended to replace the existing document attachments existing in the User interface B.20.01 and attaching the BOM documents to Requisition Lines.

2623

TR-MA2623

Bug Fix

2624

TR-MA2624

Bug Fix

2625 2626

TR-MA2625 TR-MA2626

Bug Fix Bug Fix

2629

TR-MA2629

Bug Fix

2630.1

TR-MA2630

Bug Fix

2631

TR-MA2631

Bug Fix

2632.1

TR-MA2632

Bug Fix

2634

TR-MA2634

Bug Fix

2640

V-ID2640

Change Request

Release Notes MARIAN 2007 (6.2.1)

19 of 26

2007
Version: Initial Release 6.2.1

2645.1

TR-MA2645

Bug Fix

When creating an inquiry supplement technical evaluation checklists are now only copied if they do not exist already. Up to now this was not checked which led to an error message concerning the violation of a unique key. It is now possible to build attribute-based-commoditycodes based on attribute-value-nls-data. That means when an attribute in A.50.01 is defined as nls-dependend the commodity-code and description are build on attribute-value-nls-records instead of attr-values. In case of nls-dependend attributes you can store the same attribute for different languages.

2647

V-ID2647

Change Request

2650 2661

TR-MA2650 TR_MA2661

Bug Fix Bug Fix

10g uses frmweb instead of ifweb90. Error in procedure Clipboard was fixed and the functionality was enhanced. Now you can attach MTO line items from one to another MTO Req as "in scope" items if they was not in scope of the destination Req. You can choose if you want to attach them as manual or "in scope" lines. Package M_PCK_PDS_BOM_IMPORT revised to use the correct variables. A.10.05 - Data type of column m_standards.header_default has been changed from CHAR to VARCHAR2. When deleting an order line the item shipment(s) of which are assigned to a sub order these subsequent data are now also deleted. on_logon_trigger - change length of P_USER to VARCHAR2(30).

2666.1

TR-MA2666

Bug Fix

2672

CR-MA2672

Change Request

2678

TR-MA2678

Bug Fix

2699

TR-MA2699

Bug Fix

2703.1

V-ID2703

Change Request

In in A.60.04 and A.20.12 existing values will return with their numeric or date value (transfered in character format). This avoids problems, when date format or punctuation is changed on the application server. Screen B.40.01. Issue Status will not be set to NULL as if SAC code is not given any Issue Status can be used it is not required that issue status has to be linked with the SAC Code in use. B.10.21. Fix implemented by changing the data type of

2704

TR-MA2704 / 1-50232741

Bug Fix

2706

TR-MA2706

Bug Fix

Release Notes MARIAN 2007 (6.2.1)

20 of 26

2007
Version: Initial Release 6.2.1

column trx_id of table M_BOM_LOG_HEADERS from VARCHAR2(240) to NUMBER(12). 2707 V-ID2707 Change Request When creating a new project default or changing the value of an existing project default a history is written and can be displayed by double-clicking on item 'Parameter' in A.20.12, A.20.13 or A.60.63 (this opens screen A.60.64 Project Default History). This screen shows the date and time a special value for this project default is (was) valid. If item 'Valid until' is empty means that this value is yet valid. If the value is changed for a special discipline in A.20.13 the code for the discipline is displayed in item 'Defined in'. If 'Defined in' is empty the value is defined for the project. If once a value was defined for a discipline and then deleted again in A.20.13 you only see records for this discipline with filled items 'Valid from' and 'Valid until'. This means that yet no value is defined for this discipline but you see the time intervals when values were defined. Item 'User of Change' displays the user who did the change.

2718

V-ID2718

Change Request

Fields work_directory, printer_name and automatic_printing have been removed from table m_users. Field work_directory has also been removed from table m_request_for_users. Due to these changes the layout has only changed in the logon screen and in screen A.60.01.01 Create User. In these screens field 'Work Directory' was available.

2720

TR-MA2720

Bug Fix

The new columns 'Type' and 'Linked with' of screen P.10.61 Milestone Labels are now also copied when using the functionality of screen P.10.01 Copy MSCM Setup. Defintion of bom_sa_ind on m_Bom_procedures corrected. Fields 'Fab Location' and 'Inspection Location' have been added to folders 'Item Shipments' in screen P.50.07 Maintain Orders. Field 'Inspection Location' has also been added to folder 'Item Shipments' in screen P.70.72 Expediting Details. Field 'Fab Location' was already available in this screen.

2723

TR-MA2723

Bug Fix

2728

V-ID2728

Change Request

2732

V-ID2731

Change Request

CWS Requisition (R.30.01) ======================= Screen R.30.01 Maintain Requisitions and its subsequent

Release Notes MARIAN 2007 (6.2.1)

21 of 26

2007
Version: Initial Release 6.2.1

screens such as R.30.07, R.30.08, ... have been converted into one new Core Workflow Screen, R.30.01 Requisition. 2734 2738 V-ID2734 V-ID2738 Change Request Change Request Database adjustments in preparation for V-ID2734. SP3D Mappings Follow up The main functionality of this task to update the SP3D mapping screen SP3D.30.01 with the updates that were made in the MARIAN user interface SP3D .10.04. This task also includes calling of the Table Details mappings in SP3D.10.04 from the User interface S.20.11 Table explorer. 2740 TR-MA2740 Bug Fix (1) Altered table M_OMI_IMPORT_JOBS so that column SA_EXPORT_TYPE in not NULL and previous NULL values will be set to N in migration. (2) Modified M_PCK_OMI_UTL.create_job to take care of change described in point 1 (3) Applied the constraints on M_BOM_MACROS, M_BOM_PROCEDURES because of domain usage in CASE . 1) Created primary key on M_PDSI_CL_ATTR_DMPS, M_PDSI_MODEL_PIPCOMMTYPE_DMPS, M_PDSI_ZYDEX_SHTCD_PART_DMPS, M_PDSI_CL_TD_DMPS (2) Re-worked on table M_APPL_ROLES_VIEWS 2.1: Droped the previous old constraints and recreated the required constraints. 2.2: Droped the previous old index and recreated the required index. 2.3: Dropped the trigger M_APPL_ROLE_VIEWS_TRG and recreated it. (3) Re-worked on table M_LIST_VIEWS3.1: Droped the previous old constraints and recreated the required constraints. 3.2: Droped the previous old index and recreated the required index. (4) Created FK and index for PROJ_ID in M_SA_NODES_DUP

2747

TR-MA2747

Bug Fix

2752

CR-MA2752

Change Request

- The data type of columns EXEC_START and EXEC_END of M_BOM_LOG_HEADER and M_SA_LOG_HEADERS are changed from TIMESTAMP(9) to DATE. - Data will also be migrated in the fix. - The package M_PCK_BOM_PROC is changed and now

Release Notes MARIAN 2007 (6.2.1)

22 of 26

2007
Version: Initial Release 6.2.1

SYSDATE will be recorded instead of SYSTIMESTAMP. 2760 TR-MA2760 Bug Fix Corrected the Online run procedure in B.40.01 to set the state correctly to STAGE when SAC code is given but Pit Stop is not required (checked). Updating price data in screen P.50.07 has been tuned. Commits are now processed much faster than before. When using sets for attaching technical evaluation checklists to an inquiry (button 'Copy' in screen P.30.21 Prepare RFQ in folders 'Tech. Eval. Checklists' -> 'Inquiry' and 'Line Items' respectively) the descriptions are now also copied. When deleting detail tags of a master item shipment the BOM is now reset correctly. Thus it is now also possible to create detail tags for that item shipment again later on. The show button has been removed from the online help. When immediately updating a record twice no message is issued any longer. Screen S.01.01 MLCL Explorer. Copied Part Code and renamed to Commodity Code. Now, checkbox 'Commodity Code' works correct. Screen S.01.01 MLCL Explorer. The following bugs have been fixed: - Null selection on "Display Options" possible. Preselection after first "search", without refreshing tree, possible. - After this, at second time, no search possible. - After preselecting, the search function does work only one time. Clipboardactions resulting in manual req line items are redone by the MTO. If the option keep attachments is checked, also other manual req line items are kept by the MTO. Screen S.01.01 MLCL Explorer. Changed help text, as meanwhile search options exist and use of wildcard is obsolate here. Screen S.01.01. Problems occure due to erase of necessary globals in different forms of module MLCL. This has been fixed.

2761

TR-MA2761 / Bug Fix 610-PRB-1201 TR-MA2767 Bug Fix

2767

2779

TR-MA2779

Bug Fix

2781 2785

TR-MA2781 TR-MA2785 / 1-50807975 TR-MA2786

Bug Fix Bug Fix

2786

Bug Fix

2789

TR-MA2789

Bug Fix

2791.1

V-ID2791 / CR-MA2190

Change Request

2794

TR-MA2794

Bug Fix

2799

TR-MA2799

Bug Fix

Release Notes MARIAN 2007 (6.2.1)

23 of 26

2007
Version: Initial Release 6.2.1

2812

V-ID2812

Change Request

In screens P.30.11 Inquiries and P.50.01 Orders you can now also see the inquiries and orders created in other projects than the log in project provided that you own privilege 'MULTI PROJECT'. Please note that you can only view the data of other projects. You cannot modify them. Implement A.30.15 MARIAN THEME / Possibility to change the colors of all forms objects within MARIAN. Expediting excel export and import adapted to new functionality for heat numbers. Folder ..\others\excel_templates contains new Template EP-TPL-621-1.xls. Either, user has the privilege to assign buyer or the user is the buyer of this po supplement.

2818

V-ID2818

Change Request

2822

V-ID2822

Change Request

2873

V-ID2873

Change Request

2901

V-ID2901

Change Request

Cronacle Replacement. Part 1: OMI. For the details refer to document V-ID2901_Cronacle_Replacement.pdf. Cronacle Replacement. Part 2: MTO, Forecast und Reservation Run. For the details refer to document VID2901_Cronacle_Replacement.pdf. Package m_pck_file_io.host will carry out an OS command. For windows, it will make a call to the WIN32 API function CreateProcess and start the cmd.exe, so it is possible to issue DOS commands. Be sure, that the called program will terminate without waiting for user's interaction/confirmation. In such a case, the process would wait forever. The program's output will be contained in the return value. Same is true for error messages. Performance scores can only be entered in screen P.20.01 Suppliers for the project you are currently logged on. If you own privilege 'EVAL ALL SUPPLIERS' you can enter scores for any order of the current project. If you do not have this privilege you can only enter scores for those orders that you are the buyer of.

2901.2

V-ID2901

Change Request

2910

V-ID2910

Change Request

359

CR-MA359/VID2439/133443097

Change Request

406

CR-MA406 / V- Change Request ID2402

You can now define number rules for the automatic generation of inquiry and order numbers. To do so you have to use screen P.10.35 Number Ranges and Rules. This screen now consists of two folders: one in that you

Release Notes MARIAN 2007 (6.2.1)

24 of 26

2007
Version: Initial Release 6.2.1

can define the number ranges (as up to so far) and one in that you can define number rules. The way these rules have to be composed is identical with the one for project defaults ZP_INQRULE and ZP_PORULE respectively. In screens P.30.21 Prepare RFQ, P.50.01 Orders and P.50.07 Maintain Orders the new field 'Number Rule' is available. If you enter one of the rules previously defined in screen P.10.35 this rule is applied for the generation of a number. If you do not fill this field the setting of project default ZP_INQRULE/ZP_PORULE is used instead. By double-clicking on field 'Number Rule' in screens P.30.21, P.50.01 and P.50.07 you can call screen P.10.35. 609 CR-MA609/VID2441/JLHCR-004 Change Request The layout of screen AS.10.01 Price Types has been modified slightly. The first two blocks (price types and the translated descriptions) have been merged into one block. Additionally the NLS-button of the toolbar is available for entering descriptions in other languages than the current one. Moreover the scrollable area in the last block has been removed. Now all fields are visible without having to move the slider.

In screen AS.10.02 Price Data the ident short description is now available not only for data that have already been saved but also for newly entered ident codes.

Project default ZP_INTDISC is now also used when using price agreements for quotes and orders. On price agreements the fields 'Factor' and 'Addend' can be used as discount percentages and discount amounts by entering values smaller than 1 and negative values respectively. Depending on the setting of project default ZP_INTDISC this discount is either integrated in the unit price (ZP_INTDISC = 'Y') or taken over into fields 'Discount %' and 'Discount Amount' respectively (ZP_INTDISC = 'N'). The discount base will be set accordingly. If both addend and factor are filled and factor is not 1 only the factor is used with ZP_INTDISC = 'N'. In this case the addend is ignored. (To use a price agreement for a quote you can assign it to a quote summary in screen P.30.22 Commercial Evaluation, folder 'Price Agreements', and press button 'Update Quote Details'.

Release Notes MARIAN 2007 (6.2.1)

25 of 26

2007
Version: Initial Release 6.2.1

To use a price agreement for an order you can press button 'Apply Prices' in screen P.50.07 Maintain Orders, folder 'Order', select a price agreement and press another button labelled 'Apply Prices.) 8500 8500 Change Request Screen PX.10.21 Display Configuration has been renamed to PT.10.21 Display Configuration. From now on only excel sheets are supported when downloading and loading bids. The old EIBP interface is no longer available.

8501

8501

Change Request

Release Notes MARIAN 2007 (6.2.1)

26 of 26