5-5-3-GEN-New 42C

MARIAN
5.5.3 New Features
Version 6.1 July 2004 DMAR1-PE-200042C

Copyright
Copyright © 2003-2004 Intergraph Corporation. All Rights Reserved.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license
agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by
copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available
without proper authorization.
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 USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Trademarks
Intergraph, and Intergraph logo, PDS, INtools and MARIAN are registered trademarks of Intergraph Corporation.
Microsoft and Windows are registered trademarks of Microsoft Corporation. Other brands and product names are
trademarks of their respective owners.
General
Table of Contents
General..............................................................................................................................33
MARIAN™ Service Packs (Release Management Change) ....................................................33
API Changes ............................................................................................................................33
1271 ID: New Entity Activities................................................................................................34
1280 ID: Multiple Selections for Documents ..........................................................................35
1457 ID: Report Parameters Saved by User.............................................................................35
Material Lifecycle Library (MLCL) ..............................................................................36

1132 ID: Two New Reports in MLCL Reports .......................................................................36
1385 ID: USY_ID for S.80.11 .................................................................................................36
1466 ID: Enhancement S3001 LOV ........................................................................................37
Engineering & Procurement Integration ......................................................................38

1320 ID: Change of SWT to SOT in BOM..............................................................................38
1382 ID: Execution of CIPs for Requisition Manually............................................................38
1368/1370 ID: Part Access Control (PAC)..............................................................................39
1437 ID: E-mail changes..........................................................................................................39
1348 ID: Weight, WeightUnit, and DeliveryDesignation Filled Automatically......................39
1485 ID: PartAccessControl for Ident-Values for TAB-Item Type.........................................40
1500 ID: Enable/Disable Templates ........................................................................................40
1441 ID: Ident Values Change Control....................................................................................41
Material Supply Chain Management.............................................................................44

1283 ID: Global Update on Inspection ....................................................................................44
1284 ID: SplitItemShip on Inspection......................................................................................44
1321 ID: MS PO Link without REQ Link ...............................................................................45
1345 ID: Attribute Origin ........................................................................................................45
1347 ID: Automatic Generation of Pos Number......................................................................45
1349 ID: Project Default for Delivery Designation .................................................................45
1350 ID Project Default for Currency......................................................................................45
1352 ID: Add Line to Change Orders ......................................................................................45
1353 ID: Add PO Line not Created on a Requisition ..............................................................45
1357 ID: P.50.14 TAG Lookup ...............................................................................................46
1358 ID: New PO Line Items...................................................................................................46
1361 ID: ROS in Expediting Updateable.................................................................................47
1389 ID: Technical Evaluation for Non Inquiry POs ..............................................................47
1427 ID: Assignment of Pertinent Area...................................................................................48
1428 ID: Default Date of for Forecast Date.............................................................................48
1429 ID: Changes in Tracking Details.....................................................................................48
1431 ID: Add Fields to Global Update ....................................................................................49
1445 ID: PO Milestones...........................................................................................................50
1468 ID: Enabling Comment in P.70.16 ..................................................................................50
1469 ID: Automatic Calculation of Date Files.........................................................................50
1470 ID: OPI Enhancements....................................................................................................51
1480 ID: Changes in MSCM ...................................................................................................51
1503 ID: Show Group by Attributes in Several Screens..........................................................51
1478 ID: Automatic FORCE RTP ...........................................................................................51
Close Order in new Expediting ................................................................................................52
MARIAN 5.5.3 New Features 31

General
1472 ID: Order Progress ..........................................................................................................55

1366 ID: Requisition Progress .................................................................................................56
Site Control.......................................................................................................................58
1196 ID: Material Transfers Between Warehouses .................................................................58
1471 ID: WinZIP Site Export Files..........................................................................................60
1541 ID: C2001/C2004 Report Button ....................................................................................60
Interfaces ..........................................................................................................................61
1323 ID: INtools: View for TAG Import Free Format with 6th Level ....................................61
1414 ID: PDS Procedures for Project Wide List .....................................................................62
1446 ID: BOM Import of Special Material with Tag No.........................................................62
1474 ID: Project Specific Spec Type Procedures ....................................................................63
Index..................................................................................................................................64
32 MARIAN 5.5.3 New Features

General
General
MARIAN Service Packs (Release Management Change)
Beginning with MARIAN® 5.5.3, Service Packs will replace individual patches.
Service Packs (SPs) ensure that all customers receive quick and easily-applied
updates. Service Packs replace the bi-annual maintenance releases. Customers should
contact Intergraph® Support or the MARIAN Service Center (MSC) to receive a
Service Pack.
Each Service Pack (SP) will include a list of the fixes and change requests it contains.
SPs will be cumulative for each full version of MARIAN. For example, a customer
working with SP 1 who installs SP 4 will also receive (in SP 4) all the necessary
modifications of included in SP 2 and SP 3. This way, customers can choose to not
install a SP that has fixes or changes that they do not need. Installing SPs will save
customers valuable time previously spent troubleshooting specific patches.
API Changes
For all procedures in the following APIs, an additional parameter p_commit_ind has
been added:
• m_api_ish
• m_api_poh
• m_api_poli
• m_api_uoc
This parameter allows you to control when changes are committed to the database. If
you omit this parameter or pass a Y to the procedure, data will be committed
immediately by the API procedure. If you pass an N, the data will not be committed
by the API procedure.

General
1271 ID: New Entity Activities
A new field for activities has been added on Requisition, Requisition Line Item, and
PO to facilitate the communication with PRISM.
Since all scheduling and planning systems like PRISM, PRIMAVERA, and SAP PS
are working with activities, this field makes it easier to link MARIAN with these
systems. The activities are loaded into the project with the appropriate ROS (required
on Site) date. Each Requisition line item will have an ROS date determined by the
activity stored at the requisition header level.
A new entity was created for activities. To each activity, you can enter a schedule that
can be considered as a ROS = Required on Site Date.
Activities can be loaded from ASCII File.
Requisition Line Item can be linked to a particular activity, causing the ROS Date for
the Requisition Line to be set to the date of the activity. If the ROS date is changed
after the activity was linked, the ROS Date is removed.

General
When loading the same activities again, MARIAN remembers the original Activity
date. A new screen is available to see which Requisitions are affected by a potential
change of the activity.
1280 ID: Multiple Selections for Documents
Multi-selection LOV for selecting single documents is now available in D.10.21,

D.10.12, D.40.12, and D.40.21.
1457 ID: Report Parameters Saved by User

Screen A6071 Start Reports, which opens when you start reports in MARIAN,
contains a new Save Settings button, which saves the user-specific report settings.

Material Lifecycle Library (MLCL)

1132 ID: Two New Reports in MLCL Reports
The MLCL comes with two new reports:
• PipeClass Overview (S.50.R10)

• PipeClass Details (S.50.R11)
With these new reports, the origin value of certain fields, such as Main Material for a
Piping Specification, can be configured by a CIP.
1385 ID: USY_ID for S.80.11

Changed OII to allow the import of USY_ID. For details, please refer to the OII
Documentation in the MARIAN Online Reference Library.

1466 ID: Enhancement S3001 LOV

A new S.30.01 LOV since 5.5.1 means that all Tables Details selected are handled as
a logical “and”.
This change applies to S.50.06 and B.20.01.

Engineering & Procurement Integration

1320 ID: Change of SWT to SOT in BOM
The SWT no longer becomes SOT automatically after MTO.
The problem in previous version was that a Valve, which is a standard valve with an
existing Ident, was given a Tagnumber and the Item Type SWT in B.20.01. After
running them MTO, this ItemType was lost and turned into SOT that is the one from
the Commodity Code.
1382 ID: Execution of CIPs for Requisition Manually

This enhancement provides for the manual execution of CIP. CIPs for requisition can
also be executed on demand after the MTO Job.

1368/1370 ID: Part Access Control (PAC)

Part Access Control can now be applied for List Pos Values.
With Part Access Control, it is now possible to completely control access to the
equipment by specific users. As a result of this, it is possible to allow users to
insert/update attribute values for only specific types of equipment, making the saving
of work between different operating centres or departments possible.
ZB_QTY_UPD was renamed to ZB_TAG_UPD. ZB_TAG_UPD determines whether

updates are allowed for tagged items.
• POS-No
• QTY
• QTY Unit
• ListStatus
• IssueStatus
If the value for ZB_TAG_UPD is Y, only users having appropriate rights according
to PAC are allowed to perform an update. The Project Default must be set to Y, and
PAC must be granted to a user before they can perform an update.
1437 ID: E-mail changes

The CIP calls in the e-mail template have been made generic so that an unlimited
number of CIPs are possible.
If the e-mail Body returns null, no mail is sent.
CIP procedures are available to return a report name. They can be entered in the
e-mail template.
You can now send test e-mails from R.30.01 to one recipient.
1348 ID: Weight, WeightUnit, and DeliveryDesignation Filled

Automatically
Use M_PCK_STD_CUSTOM to fill Weight, WeightUnit, and DeliveryDesignation
for manual Requisition Line Items.
For further information, refer to R.30.07 in the Online Help.
Delivery Designation (Deliv Desig)
Name (code) of the delivery designation defined in A.10.39 Delivery Designations.
ZP_DLV_DSG is set to the project default setting when you insert a new record, but
you can overwrite the default value, if necessary.

Unit Weight
The weight for this requisition position. This value is calculated by the MTO
(together with the weight unit) if the related check box was checked before the MTO
was started.
Remarks:
The procedure used to calculate the ident unit weight is a CIP. The name of the CIP is
M_PCK_REQ_CUSTOM.WEIGHT.
1485 ID: PartAccessControl for Ident-Values for TAB-Item Type

Beginning with MARIAN 5.5.1, it is possible to generate TAB Idents directly in the
BOM, for example, for equipment. All attributes and values can be directly modified
on the BOM, but will be stored with the ident. Previously, there was no access control
for these attributes as there was for the attributes specific for the position. This is now
introduced with the same rules as for the List Position values.
1500 ID: Enable/Disable Templates

Requisitions Templates created with the Requisition-Template Functionality are
enabled/disabled depending on a new project default setting. Previously, they were
always enabled. Now, however, if this project default setting has a value of N, all
Requisition Templates generated are disabled. If the value is set to Y, they are
enabled. The name of the project default mentioned here is :ZR_ENABLED

1441 ID: Ident Values Change Control

During an MTO Job, MARIAN copies all Ident-Values from the Ident of Item-Type
TAB as attached attributes of Type Ident-Values behind Requisition Line Items.
You can see these attributes by opening A.50.21.
Attribute Change Control also applies to attached attributes for Purchase Orders.
Change
This drop-down list shows whether an attribute or its value has changed compared
with the previous supplement.

The following list shows the available options and a description of each one.
New The attribute is attached for the first time.
Unchanged The attribute has already been attached to the previous

supplement of the object (such as the requisition or the order line
item); the value of the attribute has not changed since the
previous supplement.
Changed The attribute has already been attached to the previous

supplement of the object (such as the requisition or the order line
item); the value of the attribute has changed since the previous
supplement.
If no previous supplement exists, the value of this field is always New.
As there is no supplement handling for inquiries, quote summaries and quote detail
attributes for these objects are always displayed as New.
The previous supplement is determined as indicated in following paragraphs:
In the case of requisitions and requisition line items, the previous supplement is
clearly defined. It is the requisition with the same name and the supplement decreased
by 1.
In the case of orders, order line items, and item shipments, the type of the order is
taken into account for the determination of the previous supplement. Details for each
type of order are provided in the following sections.
Type 'PO' (Purchase Order)
If the order is not the first of an order chain, in other words, if it is not the one with
the lowest supplement, the system searches for the latest change order of the previous
Purchase Order supplement. If no change order exists, the attributes are compared
with those attached to the previous PO supplement.
It does not matter whether a change order has been approved.
Type 'CO' (Change Order)
The attributes of the immediately previous Change Order are compared with those
attached to the current CO. If the current CO is the only one or the first one of an
order, the parent PO order is the previous supplement for the comparison.
Type 'NOC' (Notice of Commitment)
A previous supplement does not exist.

Type 'MP' (Manual Purchase Order)
Type 'BO' (Blanket Order)
Supplement (Suppl) of last change
If the value of an attribute has changed in the course of the supplements, this field
shows the number of the latest supplement with a value not equal to the current value.
Value of last change
If the value of an attribute has changed in the course of the supplements, this field
shows the value of the latest supplement that is not equal to the current value.

Material Supply Chain Management

1283 ID: Global Update on Inspection
When you change the value of a field in P.70.55 (Inspectable, ReleaseNote, Waiver),
the system asks if this value should be populated to all ItemShipments, and when you
add a value for a date field, the system asks if the date should be populated to all
ItemShipments where suitable, those where this date field makes sense. For example,
only Item Shipments that can be inspected have a Release/Waiver.
1284 ID: SplitItemShip on Inspection

A new function has been added to split the ItemShipment from the P.70.55. Now, if
the inspector decides that only six of ten items passed the inspection, a new
ItemShipment can be created from P.70.55.

1321 ID: MS PO Link without REQ Link

When you click the Calculate Forecast button, the link between the PO and the
Planned PO is also set, as long as the PO was created without an existing link. Before
5.5.3, a link between the PO and the Planned PO was established only when the PO is
created. Now, the link is updated again when the Forecasted Dates are calculated,
because the PO could be created without an existing link.
1345 ID: Attribute Origin

Attribute Origin is a required entry on numerous forms in Requisitioning and
Procurement. A.20.12, Project Defaults, now allows an entry of a default value for
the Attribute Origin. This default value is automatically populated in all forms and
allows modification, as necessary. The existing project default setting ZX_ORIGIN
now applies to manual PurchaseOrders and Requisitions.
1347 ID: Automatic Generation of Pos Number

MARIAN Position and Sub-position numbers for manual Purchase Orders and
Requisitions are now created automatically.
1349 ID: Project Default for Delivery Designation

Delivery Designation, a required entry, can now be set as a project default,
ZP_DLV_DSG.
1350 ID Project Default for Currency

In P.50.02, you can now set a default currency with ZX_CURCY.
1352 ID: Add Line to Change Orders

In P.50.14, line items can now be added to change orders. This functionality is
available only for line items that are on the referenced PO.
1353 ID: Add PO Line not Created on a Requisition

MARIAN now supports the ability to add lines that are not on a Requisition to a
Purchase Order.

1357 ID: P.50.14 TAG Lookup

P.50.14 now has a look-up for existing tags provided for manually generated
Purchase Orders.
1358 ID: New PO Line Items

MARIAN now offers the ability to create additional line items in a Purchase Order.
The line items do not require a MARIAN commodity code or a Tag Number. This
functionality allows you to easily create service PO’s, installation and engineering,
spare parts, and other line items.
For Non-Receivable Items (such as warranties), Other Costs can be created on the fly,
in other words, without prior definition.
For Receivable Items, New Idents with descriptions can be created on the fly directly
on PO Line Items.
This functionality is available only for Purchase Orders.

1361 ID: ROS in Expediting Updateable

You can now update the ROS Field in Expediting. Project default settings determine
whether you can update the field. Additionally, you can use Expediting Dates to
update the actual or forecasted milestone dates.
1389 ID: Technical Evaluation for Non Inquiry POs
Previously, for Requisitions without Inquiry, the Technical Evaluation Required

field was meaningless, as Procurement can create a PO directly from a Requisition.
The TechnicalEvaluation is linked to the quote, meaning that if there is no quote, the
Technical Evaluation should be linked elsewhere, such as the PO. The solution is that
now Procurement can create a PO from a Requisition directly, even if
TechnicalEvaluation is required; however, they cannot approve it until the Technical
Evaluation is complete.

The following changes have been made concerning the Technical Evaluation.
• A new date field, TechEvalCompDate, was added on PO-Header

(P.50.11).
• Clicking the TechPassed button in P.50.11 will check all
TechnicalEvaluations on all PO-Lines. TechEvalCompDate will be set to
Sysdate.
• A new TecReqd check box was added on PO-Line Level (P.50.14 only)
to indicate if a TechnicalEvaluation is required for this PO-Line. This field
is not updateable. The default is derived from Req if at least one ReqLine
for this PO-line has a TecReqd value set to Y.
• A new TechPass check box on PO-Line level (P.50.14 only) indicates that
for this PO-Line a TechnicalEvaluation was completed. This field can be
updated by users with certain privileges (TECHNICAL EVALUATION).
• Only users with a certain privilege are allowed to perform a
TechnicalEvaluation, which means setting the CompleteDate on PO
Header, selecting the TechPass check box on PO-Line (P.50.14), or
clicking the TechPassed button on P.50.11.
• Approval of a PO is not possible before all PO-Lines with TechnEval
Required have passed the TechnicalEvaluation. If a TechnicalEvaluation
was completed on the quote already, the PO Line will have a TecReq
value of N, which means it is not necessary to complete the
TechnicalEvaluation again. The TecReqd check box cannot be modified
manually.
1427 ID: Assignment of Pertinent Area

Pertinent Area is now applied on the Item Ship Level. The default value is that found
in PX.20.11 OrderReference. For SplitTags, the Pertinent Area can be updated in
Expediting.
1428 ID: Default Date of for Forecast Date

By default the forecasted date is determined by the value of the planned date and can
be modified. This issue has now been corrected so that the planned date cannot be a
date that has already passed.
1429 ID: Changes in Tracking Details

The Last info Dater can be entered only if the forecasted Delivery Date had been
modified and populated with Sysdate by default.

1431 ID: Add Fields to Global Update
The following new fields have been added to Global Update, which can be accessed
by clicking the Update button in PX.20.24:
• Forecasted delivery date

• Completed OWL
• Completed NCR

1445 ID: PO Milestones

It is now possible to apply milestones on the PO Level.
1468 ID: Enabling Comment in P.70.16

Comment functionality is enabled in P.70.16.
1469 ID: Automatic Calculation of Date Files

In order to control automatic calculation of date fields, a new project default,
ZP_EXPDATE, was added. For further details, refer to the Online Help for Screen
P.70.1X.

1470 ID: OPI Enhancements

Any kind of ASCII file can now be loaded for OPI and then processed by an OPI pre-
processor.
This new OPI pre-processor functionality makes the import of purchase order
information much easier and faster. The pre-processor imports free format type files
into MARIAN by creating a translation CIP between the 3rd party procurement
system (which may be a client partner or contractor) and MARIAN.
1480 ID: Changes in MSCM

OPI
Each PO will be loaded completely. If one PO-Line fails, the whole PO will be
rejected. This option can be enabled or disabled through the use of a project default
setting. The name of the project default mentioned here is :ZI_OPI_COM.
UNITS-Codes are first compared directly and then in uppercase. For example, for the
units mm and MM, MARIAN first compares mm=MM and if it isn’t true, then
compares MM=MM.
Global Update
The Global Purchase Order Line (POLI) update can now also be used to make a
global update on Incoterm and Delivery Place.
1503 ID: Show Group by Attributes in Several Screens

Grouping by attributes are now available in the following screens:
• P3033
• P3071
• P3073
• P5016
• P5014
1478 ID: Automatic FORCE RTP

If you had a Requisition where only Documents, VDRs, or Attached Attributes are
changed, it was not possible to release this Requisition to Procurement, as there were
no changes in QTYs on the Requisition Line Items. No Requisition without changes
in QTY can be release to procurement, even if the changes occur on Attachments on
the header.

Close Order in new Expediting
This screen enables you to close a purchase order or notice of commitment or to

reverse the closing of a purchase order or notice of commitment.
An order can be closed only if all material has been received, and no open OS&Ds or
incomplete outstanding work lists exist.
For orders that have already been closed, the Closed check box is enabled. The
Reverse button is available for only for these orders.
Closing an order effects the data available in screen PX.20.01 Expediter Workload. In
the workload, only orders that have not been closed can be selected.
Since the data that has to be queried to perform the checks is constantly increasing in
the course of a project, you should restrict the query, particularly in the Order
Number field to reduce response time.

Orders
All purchase orders and notices of commitment that have been approved are available
in this module.
Notices of commitment are available only if they have not been converted into a
purchase order.
Order Number
This field is the number of the purchase order or notice of commitment.
Type
This type of the order is indicated in this field.
NC = Notice of Commitment
PO = Purchase Order
Supplier
This name (code) of the supplier appears in this field.
Origin
The name (code) for the origin (branch) of the order appears in this field
Buyer
This field contains the name of the MARIAN user who is the buyer for this order.
Received
This field indicates whether all material has been received.
This check box is enabled only if all material of the order has been received, meaning
that the quantity (or even more) of all item shipments has been received on site and
has been posted to the inventory.
If you used the split tag functionality, you can receive only the master tag or its detail
tags. Regardless, material is regarded as received if either the master or its details
were received completely.
OSD
This field indicates whether all OS&Ds have been closed.
If any open OS&D exists for the order (including all approved supplements of the
order) this check box is disabled.

All OS&Ds created by traffic and by site, either for a release note, a package, or a
package item, are taken into account.
OWL
This field indicates whether all outstanding work lists have been completed.
This checkbox is checked if no outstanding work list exists and is incomplete for any
item shipment of the order (including all approved supplements of the order.
An order cannot be closed if any outstanding work list has not been completed.
Closed
This field indicates whether an order has already been closed.
An order is regarded as closed if the closed date has been set for all approved
supplements of the order.
Close
This button is enabled if the order (including all approved supplements and approved
change orders) has not been closed, so long as the following conditions have been
met:
• All material has been received, and the Received check box is checked.
• No open OS&Ds exist, and the OSD check box is marked.
• No incomplete outstanding work lists exist, and the OWL check box is
checked.
When you click this button, the PO Close Date field is set to the current date for the
order, including all approved supplements and change orders.
If the order is based on an inquiry, this order is the last (or only) one that is based on
this inquiry, and it is to be closed, the PO Closed Date field in P.30.11 Create
Inquiries is also set to the current date.
Reverse
This button is active for all orders that have already been closed.
When you click this button, all changes that were applied when clicking the Close
button in this module are turned back. In other words, the date fields are reset to
NULL.

1472 ID: Order Progress
This screen provides an overview of the development of costs and ordered quantities.
The order level displays the amount of that material ordered along with this order,
including all previous supplements and the change in costs compared to the previous
supplement.
The line item shows the same information, this time related to the individual line
items.
Additionally, you can see what quantities have been ordered so far, up to and
including the supplement you are viewing, and what this means compared to the
previous supplement.
Costs always include not only the line item costs but also all attached other costs.
Other costs attached to the order header are also taken into account on the order level.

1366 ID: Requisition Progress
This screen provides an overview of the progress of a project.
The number of engineering requisitions, inquiries, quote summaries, and orders is

constantly increasing; budgets and order costs are growing. You can create and save
snapshots of your actual project progress by defining a DBMS job in screen A.60.45
DBMS Jobs.
You determine how often you want to take these snapshots. For example, you can
create snapshots daily, weekly, or monthly.
Your job definition in A.60.45 (field 'Executed PU') should look like this:
BEGIN
mpck_login.select_login(#US_ID#);
m_pck_req_progress.calc_req_progress;
END;
The number of requisitions of different statuses and the number of inquiries, quote
summaries, and orders are calculated.

For the budget, compare the original and total budgets of engineering requisitions,
and their associated orders are totalled. The totals that are calculated are grouped by
discipline and determined over all disciplines.
For all totals that are calculated, the discipline of the engineering requisition or the
associated engineering requisition(s) is decisive. Thus, requisitions are often created
in different disciplines, but the work in procurement is done in one overall discipline.
Only approved objects (requisitions, inquiries, and such) are taken into account.
This screen consists of two overview windows and several detail windows.
The first overview window shows the requisition progress. Double-clicking on any
"counter" field opens detail windows where you can see all requisitions, inquiries,
and so forth for the selected discipline.
Double-clicking on the discipline in the first window opens the detail window of the
budget compare.
The second overview window contains the budget compare and is opened by clicking
the Budget Compare button. Again, double-clicking on any record opens the detail
windows.
From each detail window, corresponding screens for the object are available by
double-clicking. For example, screen R.30.11 Requisition Cross Reference is opened
when you double-click on a requisition number, or screen P.30.32 Quote Summaries
opens if you double-click on a quote summary.
Please note that only the accumulated values are snapshots. When looking at the
details, you will always see the data that are actually in the database.

Site Control
Site Control
1196 ID: Material Transfers Between Warehouses
A material transfer between warehouses by ident (not on the basis of a reservation

run) is now possible. Because material could be lost in the transfer, the quantities
received in the warehouse to which the material is transferred can be updated before
posting.
This functionality is possible with the following two-step procedure:
1. Create a Material Transfer. Material is reduced from inventory.
2. Receive this material by Direct Receive. Material is booked into the inventory
again.

Site Control
Create Material Transfer

In screen C.20.15 Material Transfer, create an MTR/Voucher number in the first
block, leaving the Reservation code field blank. In the second block, idents that
belong to the MTR/Voucher No. are selected with LOV. Currently, the warehouse in
the second block represents the warehouse to which the material is transferred. In the
new functionality, it is the source warehouse (in other words, the warehouse from
which the material is to be transferred).
Receiving by Voucher Number

C.20.03 has a new receiving type 'By MTR/Voucher number'. The voucher number
can be selected from LOV.
The Propagate function causes the system to display all idents belonging to the
selected MTR/Voucher No. After posting the received quantities, you must update
the inventory in both warehouses (source and destination). Quantity discrepancies
between positions on the voucher and received quantities will generate an OS&D
report.

Site Control
1471 ID: WinZIP Site Export Files

Site Export files can now be compressed with WinZIP.
1541 ID: C2001/C2004 Report Button

In C.20.01 and C.20.04 the Report button has the ability to run a user-defined report
by using the project default ZC_REPORT.

Interfaces
Interfaces
1323 ID: INtools: View for TAG Import Free Format with 6th Level
A view for importing instruments from INtools is now a Free Format view and
supports up to six levels.
For further details, refer to the MARIAN INtools Documentation in the Online
Reference Library.

Interfaces
1414 ID: PDS Procedures for Project Wide List
Due to this new functionality, the PDS interface procedures can now be implemented
for different projects accordingly, enabling the companies to better serve from one
MARIAN instance several PDS instances with different settings in different projects.
This functionality is available using the following three types of procedures:
• SpecProcedures – the known procedures that are run after the generation.
• Standalone Procedures – executed at any time by clicking a button in
PDS.10.03.
• Project Wide Lists Procedures – executed after the generation of the
Project Wide Lists.
1446 ID: BOM Import of Special Material with Tag No.

PDS Import now imports Standard with TAG.
A new BOM Config Item (PDS.30.01) for Item-Rule was created that makes it
possible to determine the Item Type.

Interfaces
1474 ID: Project Specific Spec Type Procedures
The link between PDS Procedure and SpecType can differ between projects even if
Spec.Type is in the ProductGroup.

Index
Index
activities, 6 planned date, 20
API, 5 position numbers, 17
ASCII files, 23 PRIMAVERA, 6
Attribute Change Control, 13 PRISM, 6
Attribute Origin, 17 project progress, 28
attributes, 23 project-wide lists, 34
BOM, 34 receiviable items, 18
CIP, 10 report settings, 7
closing purchase orders, 24 requisitions templates, 12
comments, 22 reverse, 24
DeliveryDesignation, 11 ROS date, 7
Direct Receive, 30 SAP PS, 6
e-mail, 11 schedule, 6
expediting dates, 19 service pack, 5
Global Update, 21 site export files, 32
grouping, 23 SOT, 10
ident values, 13 statuses, 28
INtools, 33 sub-position numbers, 17
ItemShipments, 16 supplement, 14
line items, 18 SWT, 10
material transfer, 30 TechEvalCompDate, 20
milestones, 19, 22 technical evaluation, 19
MLCL, 8 TechPass, 20
MTO, 10 TechPassed, 20
MTR/Voucher No, 31 TecReqd, 20
multi-selection, 7 reports, 32
non-receiveable items, 18 user-defined report, 32
OPI, 23 USY_ID, 8
order progress, 27 Weight, 11
OS&D, 25 WeightUnit, 11
p_commit_ind, 5 ZB_QTY_UPD, 11
Part Access Control, 11 ZB_TAG_UPD, 11
PDS, 34, 35 ZC_REPORT, 32
Pertinent Area, 20 ZP_DLV_DSG, 12
PipeClass Details, 8 ZP_EXPDATE, 22
PipeClass Overview, 8
piping specification, 8

5-5-3-GEN-New 42C

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5-5-3-GEN-New 42C

Uploaded by

Copyright:

Available Formats

MARIAN

5.5.3 New Features

Version 6.1 July 2004 DMAR1-PE-200042C

Restricted Rights Legend

Warranties and Liabilities

Material Lifecycle Library (MLCL) ..............................................................................36

Engineering & Procurement Integration ......................................................................38

Material Supply Chain Management.............................................................................44

MARIAN 5.5.3 New Features 31

1472 ID: Order Progress ..........................................................................................................55

32 MARIAN 5.5.3 New Features

MARIAN 5.5.3 New Features 33

1271 ID: New Entity Activities

Activities can be loaded from ASCII File.

34 MARIAN 5.5.3 New Features

1280 ID: Multiple Selections for Documents

Multi-selection LOV for selecting single documents is now available in D.10.21,

1457 ID: Report Parameters Saved by User

MARIAN 5.5.3 New Features 35

Material Lifecycle Library (MLCL)

• PipeClass Overview (S.50.R10)

1385 ID: USY_ID for S.80.11

36 MARIAN 5.5.3 New Features

1466 ID: Enhancement S3001 LOV

This change applies to S.50.06 and B.20.01.

MARIAN 5.5.3 New Features 37

Engineering & Procurement Integration

1382 ID: Execution of CIPs for Requisition Manually

38 MARIAN 5.5.3 New Features

1368/1370 ID: Part Access Control (PAC)

ZB_QTY_UPD was renamed to ZB_TAG_UPD. ZB_TAG_UPD determines whether

1437 ID: E-mail changes

If the e-mail Body returns null, no mail is sent.

1348 ID: Weight, WeightUnit, and DeliveryDesignation Filled

For further information, refer to R.30.07 in the Online Help.

Delivery Designation (Deliv Desig)

Name (code) of the delivery designation defined in A.10.39 Delivery Designations.

MARIAN 5.5.3 New Features 39

1485 ID: PartAccessControl for Ident-Values for TAB-Item Type

1500 ID: Enable/Disable Templates

40 MARIAN 5.5.3 New Features

1441 ID: Ident Values Change Control

You can see these attributes by opening A.50.21.

MARIAN 5.5.3 New Features 41

New The attribute is attached for the first time.

Unchanged The attribute has already been attached to the previous

Changed The attribute has already been attached to the previous

If no previous supplement exists, the value of this field is always New.

The previous supplement is determined as indicated in following paragraphs:

Type 'PO' (Purchase Order)

It does not matter whether a change order has been approved.

Type 'CO' (Change Order)

Type 'NOC' (Notice of Commitment)

A previous supplement does not exist.

42 MARIAN 5.5.3 New Features

Type 'MP' (Manual Purchase Order)

A previous supplement does not exist.

Type 'BO' (Blanket Order)

A previous supplement does not exist.

Supplement (Suppl) of last change

Value of last change

MARIAN 5.5.3 New Features 43

Material Supply Chain Management

1284 ID: SplitItemShip on Inspection