smartplant materials inside procedures - webutilspmat.hec.co.kr/marian_webentry/pdfs/sto-si.pdf ·...

SmartPlant Materials Inside Procedures

Version 2008 (6.3.1) June 2008 DMAR1-PE-200031F

Copyright Copyright © 2002-2008 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 below. For civilian agencies: This was developed at private expense and is “restricted computer software” submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations (“FAR”) and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense (“DoD”): This is “commercial computer software” as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished – rights reserved under the copyright laws of the United States. Intergraph 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, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools, MARIAN, PDS, and IntelliShip are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. Other brands and product names are trademarks of their respective owners.

Table of Contents

SmartPlant Materials Inside Procedures 3

Table of Contents Dependencies in Procurement According to Date Fields ...............................................4

Purchase Order..............................................................................................................4 Expediting / Item Shipments ........................................................................................5

Forecast & Delivery Type .................................................................................................7

Delivery Designation ....................................................................................................8

Inheritance of Attachments .............................................................................................10

Meaning of Expected QTY for Receiving ......................................................................11

How Does it Work with the QTY During Forecast? ....................................................12

Heat Number Logic .........................................................................................................13

Heat QTY Logic Receiving ........................................................................................13 Heat QTY Logic Issuing .............................................................................................15 Heat QTY Material Transfer ......................................................................................16

Dependencies in Procurement According to Date Fields

4 SmartPlant Materials Inside Procedures

Dependencies in Procurement According to Date Fields Purchase Order

Header Prompt in screen Column name in table Coming from ETA Site ORG_ETA_SITE_DATE Set manually when creating PO in P.50.01 / 02 /

03

Req On Site ORG_FLD_REQ_DATE Minimum ROS date of ER because ROS date is set for each ER line

PO First FIRST_PROM_CONTR_DATE Minimum PROM_CONTRACT of all Item Shipments (see below)

PO Last LAST_PROM_CONTR_DATE Maximum PROM_CONTRACT of all Item Shipments (see below)

Issued PO_ISSUE_DATE Set manually after PO has been created

Closed PO_CLOSE_DATE Set when pressing button ‘Close‘ in P.70.41

Recv Acknow RECV_ACKNOWLEDGE_DATE Set manually after PO has been created

Approved APPROVED_DATE Set when pressing button ‘Approve‘ in P.50.11 / 21 / 31 / 41

Line Items Prompt in screen Column name in table Coming from First Ship FIRST_SHIP Quote Details (Weeks)

Last Ship LAST_SHIP Quote Details (Weeks)

Rev Prom REVISED_PROMISE_DATE Set manually after PO has been created

Exp Lic Recv EXPORT_LICENSE_RECEIVED_DATE Set manually after PO has been created

Closed POLI_CLOSE_DATE Set manually after PO has been created



Expediting / Item Shipments Prompt in screen Column name in table Coming from

Prom Ship PROM_SHIP_DATE LAST_SHIP_DATE of quote details if value exists; LAST_SHIP (of quote details) * 7 + SYSDATE, if LAST_SHIP_DATE does not exist

Prom Contract PROM_CONTRACT_DATE Identical with ‘Prom Ship‘

Curr/Rev Prom Ship REV_PROM_SHIP_DATE Identical with ‘Prom Ship‘ when PO is created; can be changed afterwards

Pred On Site PRED_ON_SITE_DATE ‘Curr/Rev Prom Ship‘ + total transit days of routing method. Will also be used as date for forecast run. If ‘Pred Ship‘ is updated ‘Pred On Site’ is set to Pred Ship + total transit days of routing method. If ‘Actual Ship‘ is updated ‘Pred On Site‘ is set to Actual Ship + total transit days of routing method.

Req On Site REQ_SITE_DATE ROS date of requisition line item

Prom On Site FORECAST_ETA_SITE_DATE LAST_SHIP of quote details/ PO line items * 7 + SYSDATE + total transit days of routing method

(not displayed) REQ_SHIP_DATE ROS date of requisition line item – total transit days of routing method

Actual Ship ACTUAL_SHIP_DATE Set manually in expediting screens

Pred Ship PRED_SHIP_DATE Set manually in expediting screens

Actual On Site ACTUAL_ON_SITE_DATE Set manually in expediting screens

PO Actual ACTUAL_CONTRACT_DATE Set manually in expediting screens

Actual Fab Start ACTUAL_FAB_START_DATE Set manually in expediting screens

50% Comp FIFTY_PERCENT_FAB_COMP Set manually in expediting screens

Prom Fab Comp PROM_FAB_COMP_DATE Set manually in expediting screens

Actual Fab Comp ACTUAL_FAB_COMP_DATE Set manually in expediting screens

Ready Predicted READY_PREDICTED Set manually in expediting screens

Ready Actual READY_ACTUAL Set manually in expediting screens

Prom Inspect PROM_INSPECT_DATE Set manually in expediting screens

Final Inspect FINAL_INSPECT_DATE Set manually in expediting screens

Maj Matl Order MAJ_MATL_ORDER_DATE Set manually in expediting screens

Maj Matl Recv MAJ_MATL_RECV_DATE Set manually in expediting screens

Pred Stage Ready PRED_STAGE_READY_DATE Set manually in P.80.51



Prompt in screen Column name in table Coming from Actual Stage Ready ACTUAL_STAGE_READY_DATE Set manually in P.80.51

Pred Loaded PRED_LOADED_DATE Set manually in P.80.51

Actual Loaded ACTUAL_LOADED_DATE Set manually in P.80.51

Forecast & Delivery Type


Forecast & Delivery Type ForecastRun is checking against PredOnSite Date and is of course only checking those Shipments that fit the DeliveryType.



Delivery Designation Expediting and Site Module are working with Delivery Type and Designations.

Each Delivery Type has several Delivery Designation. A Delivery Type can be understood as a Site, a real place where the construction takes place. Delivery Designation can be understood as a place within one Site where the material has to be delivered to, e.g. Gate 2.

A.10.39 Delivery Types and Delivery Designations

Each Delivery Designation is assigned to a Routing Method. Also Delivery Designation will have a default Routing Method, which can be changes when they are assigned in Expediting. Each User is assigned to a Delivery Type, which means each user can only work at one Site.



Delivery Designations are assigned on Expediting. Depending on the default routing method of the Delivery Designation the field routing method will be filled, but can be changed.

During the Forecast Allocation run, only the Expediting Information that has a delivery designation that fits the Site will be considered.

Inheritance of Attachments


Inheritance of Attachments The following table provides an overview of the inheritance logic of the Attachments from Requisition to Expediting.

Requisition Inquiry Quotes Purchase Order

Expediting

Attributes To Quote/PO No Attributes

to PO to Expediting

Document-Sets

To Inq/PO No Doc-Sets to Expediting

Text & Terms To Quote ----------------

VDRs To Inq/PO To Quote to PO to Expediting

Other Costs --------------- To Quote1 to PO -----------------

1 but without Cost-Value

Meaning of Expected QTY for Receiving


Meaning of Expected QTY for Receiving • Expected QTY is always: Item-Ship QTY – Received QTY

• Default QTY for Receiving by PO: Expected QTY

• Default QTY for Receiving by Traffic: Traffic QTY – Received QTY

How Does it Work with the QTY During Forecast?


How Does it Work with the QTY During Forecast?

Example:

Purchase Order: 3

Expediting: 3

Traffic: 2

Received QTY: 1

The Forecast Run will find depending of the Level:

Traffic Traffic QTY - Rec.QTY = 1

Expediting Expediting QTY – Traffic QTY – Rec. QTY = 0

This means Received QTY will always be subtracted from Traffic and Expediting QTY.

Heat Number Logic


Heat Number Logic Heat QTY Logic Receiving

Within the Site Module, Material can be received with or without Heat Numbers.

When material is received with Heat Numbers, it will be stored with Heat Numbers and it must be issued with Heat Numbers.

It is for example, not possible to receive a total QTY of 100 where 50 is Heat Number ABC and then to issue 60 without Heat Numbers, because in stock only 50 without Heat Numbers are available.

This means SmartPlant Materials is handling Idents with Heat Numbers as they would have a different Ident.

MRR Revision 0 Posted Date is NULL • Heat Numbers can be inserted, updated and deleted.

• The total sum of the Heat Numbers must not be higher than the QTY of the MRR Line Items.

• Heat Numbers can be booked on different Warehouse Locations compared to the MRR Line Item.

When posting the MRR, the Heat will be booked into the Warehouse on the Heat-Number and not on the Warehouse of the MRR Line Item.

Only the QTY that is remaining after all Heat Numbers are booked will be put on the Warehouse Location of the MRR Line Item.

MRR Revision 0 Posted Date is NOT NULL • Heat Numbers cannot be inserted, updated or deleted.

MRR Revision 1 or higher Posted Date is NULL • Heat Numbers can be inserted, updated, and deleted.

• The total sum of the Heat Numbers must not be more than the QTY of the MRR Line Items.

• Heats can be booked on different Warehouse Locations compared to the MRR Line Item.

• When entering the Heat Numbers, there will be an LOV which shows all Heats in MAX (Revision posted) for this MRR Line Item.

Heat Number Logic


Processing Logic when posting MRR with revision >=1 • When posting the MRR, first the booking of the Heat from MAX

(Revision posted) will be cancelled if it was in a different Warehouse/Location, and then the MRR Line.

• Then the inventory for the MRR Line will be corrected.

• Heat Numbers from the Posted revision will be set to 0

• Then the new Heat Number will be booked into the inventory.

• Finally the delta QTY of the MRR Line will be booked.

If not all Heats are available as they were in the previous Revision, an Alert Message displays.

Heat Number Logic


Heat QTY Logic Issuing MIR Revision 0 or higher Posted date IS NULL • Only heats which have been received can be issued and only those heats

which are available at the Warehouse/Location of the MIR Line Item.

• Heats can be selected via LOV or manually input (There is a validation for Heat number).

• Subsets or rest QTYs of Heats can also be issued (There is validation of QTY).

• In LOV, only the ON HAND QTY of heats will be shown; if QTY is manually changed, it will be checked against ON HAND QTY.

MIR Revision 0 or higher Posted Date is NOT NULL • Heat numbers cannot be inserted, updated, or deleted.

Heat Number Logic


Heat QTY Material Transfer The same way Heat-QTY has to be specified during Issuing, Heat Numbers also have to be specified during making Material Transfer. This is only necessary if not enough QTY is available without a Heat Number.

smartplant materials inside procedures - webutilspmat.hec.co.kr/marian_webentry/pdfs/sto-si.pdf ·...

Documents