Email templates and tokens - Intergraph Smart Materials - Version 10.1 - Help - Hexagon

Intergraph Smart Materials Web Help (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Web
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.1

Smart Materials provides tokens, for the body text of an email as well as for the subject, that will be replaced when an email is created. Depending on how you want to use your email template, you can use specific tokens that will be replaced when an email is generated. The following is the list of email types and the available tokens:

Tokens for requesting suppliers to make a quote:

Token

Description

#INQ_CODE#

Specifies the enquiry number.

#I_SUPP#

Specifies the supplement of the inquiry.

#SUP_CODE#

Specifies the supplier name (code).

#UE_ID#

Specifies the project ID.

#PROJ_ID#

Specifies the name of the project.

#QD_EMAIL#

Specifies the supplier email ID.

#BID_RET_DUE_DATE#

Specifies the last date by which a quote must be received from the supplier.

Tokens for Emails informing that a supplier does not want to bid for an inquiry:

Token

Description

#INQ_CODE#

Specifies the enquiry number.

#I_SUPP#

Specifies the supplement of the inquiry.

#SUP_CODE#

Specifies the supplier name (code).

#UE_ID#

Specifies the project ID.

#PROJ_ID#

Specifies the name of the project.

#NO_BID_DATE#

Specifies the date on which the supplier set the No Bid indicator, that is, the system date.

Tokens used in an email template for suppliers that finalize a quote:

Token

Description

#INQ_CODE#

Specifies the enquiry number.

#I_SUPP#

Specifies the supplement of the inquiry.

#SUP_CODE#

Specifies the supplier name (code).

#UE_ID#

Specifies the project ID.

#PROJ_ID#

Specifies the name of the project.

#QD_EMAIL#

Specifies the supplier email ID.

#BID_RET_DUE_DATE#

Specifies the last date by which a quote must be received from the supplier.

#NO_BID_DATE#

Specifies the date on which the supplier set the No Bid indicator, that is, the system date.

#FINALIZED_BY_SUP_DATE#

Specifies the date on which the supplier finalized a quote, that is, the system date.

Tokens used in an email template for punch list items:

Token

Description

#PUL_NUMBER#

Specifies the punch list name (code).

#PO_NUMBER#

Specifies the agreement number.

#SEQ#

Specifies the sequence number of the task.

#PROJ_ID#

Specifies the name of the project.

Tokens used in an email template for contractors and sub-contractors to inform about submission of a request for information:

Token

Description

#PROJ_ID#

Specifies the name of the project.

#SUBJECT#

Specifies the subject of the email.

#PO_NUMBER#

Specifies the agreement number.

#SEQ#

Specifies the sequence number of the task.

Tokens used in an email template for submission of an answer to a question from contractors and sub-contractors:

Token

Description

#PROJ_ID#

Specifies the name of the project.

#PO_NUMBER#

Specifies the agreement number.

#SUBJECT#

Specifies the subject of the email.

#SEQ#

Specifies the sequence number of the task.

#QUESTION#

Specifies the question attached to the request.

#ANSWER#

Specifies the answer to the question.

#ANSWERED_BY#

Specifies the name of the person who has submitted the answer.

#DATE_ANSWERED#

Specifies the date when the answer was created.

Tokens used in an email template that is used for informing originators of an engineering requisition about approval/rejection of the engineering requisition:

Token

Description

#PROJ_ID#

Specifies the name of the project.

#R_CODE#

Specifies the engineering requisition name.

#R_SUPP#

Specifies the supplement number for the engineering requisition.

#AR_DATE#

Specifies the date when the engineering requisition was approved/rejected.

#COMMENT#

Specifies the comment given by the approver/rejecter.

#M_USER#

Specifies the user who rejected or approved the engineering requisition.

#FIRST_NAME#

Specifies the first name of the user who rejected or approved the engineering requisition.

#LAST_NAME#

Specifies the last name of the user who rejected or approved the engineering requisition.

Tokens used in an email template that is used to provide approval/rejection information of an inquiry to the buyers:

Token

Description

#PROJ_ID#

Specifies the name of the project where the inquiry was created.

#INQ_CODE#

Specifies the inquiry number.

#I_SUPP#

Specifies the supplement number for the inquiry.

#AR_DATE#

Specifies the date when the inquiry was approved/rejected.

#COMMENT#

Specifies the comment given by the approver/rejecter.

#M_USER#

Specifies the user who rejected or approved the inquiry.

#FIRST_NAME#

Specifies the first name of the user who rejected or approved the inquiry.

#LAST_NAME#

Specifies the last name of the user who rejected or approved the inquiry.

Tokens used in an email template that is used to provide approval/rejection information of an agreement to the buyers:

Token

Description

#PROJ_ID#

Specifies the name of the project where the agreement was created.

#INQ_CODE#

Specifies the agreement number.

#I_SUPP#

Specifies the supplement number for the agreement.

#AR_DATE#

Specifies the date when the agreement was approved/rejected.

#COMMENT#

Specifies the comment given by the approver/rejecter.

#M_USER#

Specifies the user who rejected or approved the agreement.

#FIRST_NAME#

Specifies the first name of the user who rejected or approved the agreement.

#LAST_NAME#

Specifies the last name of the user who rejected or approved the agreement.

The following are some example templates:

We would like to ask you to make a quote for inquiry #INQ_CODE#, supplement #I_SUPP# for our project '#PROJ_ID#'.

We expect your quote to be received by #BID_RET_DUE_DATE#.

And the response, for example:

We would like to ask you to make a quote for inquiry INQ-101, supplement 0 for our project 'PROJ-1'.

We expect your quote to be received by 03-Mar-01.

Tokens used in an email template that is used to provide approval/rejection information of an agreement to the buyers:

Token

Description

#FIRST_NAME#

Specifies the first name of the user who rejected or approved the agreement.

#LAST_NAME#

Specifies the last name of the user who rejected or approved the agreement.

#USER_CODE#

Specifies the employee name.

#PASSWORD#

Specifies the password in clear text.

For example:

Dear #FIRST_NAME# #LAST_NAME#,

your password is changed. Your account name is <#USER_CODE#>, new password is <#PASSWORD#>

Tokens used in an email template that is based on the type Addendum Issue:

Token

Description

#ORDER_SEQ#

Specifies the addendum number (Add.No).

#INQ_CODE#

Specifies the inquiry number related to the addendum.

#I_SUPP#

Specifies the supplement of the inquiry.

#TITLE#

Specifies the title of the addendum.

#DETAIL#

Specifies the detail text of the addendum.

#ISSUE_DATE#

Specifies the date when the addendum was issued.

For example:

Addendum No #ORDER_SEQ# for inquiry #INQ_CODE# supplement #I_SUPP#

Add No: #ORDER_SEQ#

Title: #TITLE#

Detail: #DETAIL#

Suppl: #I_SUPP#

Issue Date: #ISSUE_DATE#

And the response, for example:

Addendum No 13 for inquiry 1895 supplement 1

Add No: 13

Title: Addendum 13

Detail: ./.

Suppl: 1

Issue Date: 18-JAN-10

Tokens used in an email template for vendor approval progress based on the type Expediting:

Token

Description

#PO_NUMBER#

Specifies the agreement number.

#R_CODE#

Specifies the name of the engineering requisition.

#POS#

Specifies the pos of the requisition line item.

#SUB_POS#

Specifies the sub-pos of the requisition line item.

#PROJ_ID#

Specifies the name of the project where the agreement was created.

The email template, for example:

Vendor progress for order #PO_NUMBER# requisition #R_CODE# of project #PROJ_ID#

The vendor progress of the following order / requisition is ready for approval:

Project: #PROJ_ID#

Order: #PO_NUMBER#

Requisition: #R_CODE#

Pos: #POS#

Subpos: #SUB_POS#

And the response, for example:

Vendor progress for order PO_1, requisition REQ_1 of project RS

The vendor progress of the following order / requisition is ready for approval:

Project: RS

Order: PO_1

Requisition: REQ_1

Pos: 1

Subpos: 1

Tokens used in an email template for Inspection Release Certificate (IRC) approval based on type Expediting:

Token

Description

#PO_NUMBER#

Specifies the agreement number.

#IRCT_CODE#

Specifies the name of the IRC.

#PROJ_ID#

Specifies the name of the project where the agreement was created.

The email template, for example:

Dear Expediter,

IRC #IRCT_NUMBER# for agreement #PO_NUMBER# in project #PROJ_ID# is ready for approval.

And the response, for example:

Dear Expediter,

IRC IRC-1127-A for agreement 1127 in project RS is ready for approval.

No tokens are used in an email template based on the type IDENT SHORTAGE NOTIFICATION but you can define fixed text:

For example:

Subject:

Shortage Notification

Body:

Dear user,

For the following idents / warehouses the minimum on hand qty is not available:

Tokens used in an email template based on the type FORECAST SHORTAGE MRR NOTIFICATION:

Tokens cannot be used more than once.

Token

Description

#PROJ_ID#

Specifies the name of the project.

#EVISION_ID#

Specifies the MRR Revision ID.

#MRR_NUMBER#

Specifies the MRR number.

For example, subject and body:

Body:

[Fsmn_Begin[

Master Section:

#MRR_NUMBER# - MRR Number

#REVISION_ID# - MRR Revision

#POSTED_DATE# - MRR posting date

#PROJ_ID# - Project

[Fsmn_Ident_Begin[

Ident Section:

#IDENT_CODE# - Ident Code

#SUM_RECV_QTY# - Total of received quantity

[Fsmn_Ivi_Begin[

Ivi Section:

#WH_CODE# - Warehouse Code

#LOC_CODE# - Location Code

#SMST_CODE# -

#IDENT_CODE2# - Ident Code

#RECV_QTY# - Receiving quantity

[Fsmn_Ivi_End[

[Fsmn_Ivpr_Begin[

Ivpr Section:

#FAH_CODE# - Forecast Run code

#RUN_NUMBER# - run number of the forecast run

#BOM_PATH# - BOM path of the list node

#LN_CODE# - list node code

#LP_POS# - BOM position

#FR_SHORT_QTY# - Forecast run shortage quantity

[Fsmn_Ivpr_End[

[Fsmn_Ident_End[

[Fsmn_End[

An example of an email template:

Subject:

FSMN MRR: #MRR_NUMBER#, Rev: #REVISION_ID#, Project: #PROJ_ID#

Body:

Dear Sir or Madam,

following Forecast Shortage Material was received:

[Fsmn_Begin[

MRR Number: #MRR_NUMBER# Revision: #REVISION_ID# Posted Date: #POSTED_DATE# Project: #PROJ_ID#

[Fsmn_Ident_Begin[

----------------------------------------------------------------------------------------

Ident:

Ident Code: #IDENT_CODE# Sum Received Qty: #SUM_RECV_QTY#

[Fsmn_Ivi_Begin[

Ident Code: #IDENT_CODE2# Received Qty: #RECV_QTY# Warehouse: #WH_CODE# Location: #LOC_CODE# Status: #SMST_CODE#

[Fsmn_Ivi_End[

[Fsmn_Ivpr_Begin[

Reservation:

Forecast Code: #FAH_CODE# Run Number: #RUN_NUMBER#

BOM Path: #BOM_PATH# List Node: #LN_CODE# List Position: #LP_POS# Forecast Shortage Qty: #FR_SHORT_QTY#

[Fsmn_Ivpr_End[

[Fsmn_Ident_End[

This E-Mail has been generated automatically. Please do not reply.

[Fsmn_End[

An example of how the email is received:

Dear Sir or Madam,

following Forecast Shortage Material was received:

MRR Number: ASW-0159 Revision: 0 Posted Date: Project: ASWSITE

----------------------------------------------------------------------------------------

Ident:

Ident Code: C32VXF Sum Received Qty: 50

Ident Code: C32VXF Received Qty: 50 Warehouse: MW-WH1 Location: MW1 Status: OK

Reservation:

Forecast Code: FR-FSMN-TEST Run Number: 4

BOM Path: /MATTHIAS/B-45241_2 List Node: B-45241_2 List Position: 15 Forecast Shortage Qty: 50

This E-Mail has been generated automatically. Please do not reply.