Tags for Orders - Intergraph Smart Materials - Version 10.2 - Help - Hexagon

Intergraph Smart Materials Classic Help

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.2

You can include an unlimited number of orders in the XML file.

<POH_PROC_TYPE>

Mandatory.

Processing type.

Allowable values: I, U, and N.

'I' means that the object is to be inserted; 'U' means that an update is to be performed. 'N' stands for 'not to be processed'; that is, the order is not inserted or modified. Nevertheless, the order information is needed to show the path for underlying objects. For example, if you have already created an order with one line item and now you want to add another item shipment, Smart Materials needs to know which order the line item belongs to and the location on the order at which to insert this additional item shipment.

<PO_NUMBER>

Mandatory.

Name (code, number) of the order.

Depending on the setting of the ZP_PO_UNIQ project default, either the combination of order number, supplement, order type, AND origin or the combination of just order number, supplement, AND order type (but not of origin) must be unique within a project.

If ZP_PO_UNIQ is set to N (default value), the same order number / supplement / order type can be created for different origins. Otherwise, (ZP_PO_UNIQ = Y) the combination of order number, supplement, and order type can only be used once in a project regardless of the origin.

In this case, Smart Materials does not distinguish between manual purchase orders (type MP) and purchase orders (type PO).

<PO_SUPP>

Optional.

Supplement of the order.

This tag is only of interest if the processing type for the order is ‘N’. The tag is needed and used to identify a change order the supplement of which is always > 0.

Generally, the supplement and revision of an order are identical. You must set the ZP_SUM_CO project default to Y if you want the supplement and revision to be different in the case of change orders.

Here the value of the po_supp database field is required, not the value of the revision_id database field. This is not to be confused as on most screens the revision_id column is displayed in the ‘Suppl’ field.

<ORDER_TYPE>

Mandatory.

Type of the order.

Allowable values: PO, MP, CO.

‘PO’ stands for purchase orders, ‘MP’ for manual purchase orders (not referencing any engineering requisition), ‘CO’ for change orders.

<CLIENT_PO_NUMBER>

Optional.

The number of the client's associated order.

<POINT_OF_ORIGIN>

Optional.

Point of origin for the supplier.

<SUP_CODE>

Mandatory when inserting an order of type ‘PO’ or ‘MP’; optional for updating orders, not used for change orders.

Name (code) of the supplier.

Depending on the setting of the ZP_PROJSUP project default, either only suppliers defined as project suppliers (ZP_PROJSUP <> N) or all suppliers (ZP_PROJSUP = N) are valid.

Only suppliers allowed for 'PO & Inquiry' (P.20.01) and the status of which is approved (P.20.01) are valid.

<ORIGIN>

Optional when inserting an order; must be included when updating an order.

The origin of an order reflects which office is responsible for it.

All origins defined on A.10.33 Origins are accepted by the interface.

If the file does not contain the <ORIGIN> tag, the value of the ZX_ORIGIN project default is used instead.

<ISSUED_BY>

Optional when inserting an order; must be omitted when updating an order.

Name of the office that has issued the order.

All origins defined on A.10.33 Origins are valid.

If the file does not contain the <ISSUED_BY> tag, the value of the ZX_ORIGIN project default is used instead.

<PO_CURRENCY>

Mandatory.

All currencies defined on A.10.12 Units of Measure in the 'currency' unit group are valid.

<PO_RM_CODE>

Mandatory.

Name (code) of the routing method defined on P.10.53 Routing Methods.

<PO_COUNTRY>

Optional.

Name (code) of the country. Any country that has been defined on A.10.34 Countries/States/Provinces can be used.

<EXPED_ILV_CODE>

Optional.

Name (code) of the level of expediting defined on P.10.55 Expediting/Inspection Levels.

<ILV_CODE>

Optional.

Name (code) of the level of inspection defined on P.10.55 Expediting/Inspection Levels.

<EV_CODE>

Optional.

Name (code) of the expediting view. This feature is no longer supported by Smart Materials.

<CCP_CODE>

Optional.

Contact person in the supplier's company. Any contact person defined for a supplier on the A.10.29 Company Contacts screen can be used.

<PO_ACCOUNT_CODE>

Optional.

Not to be used when working with the account code module (project default ZJ_USE_AC = Y).

Name (code) of the account code defined on A.10.30 Account Codes.

<ORG_ETA_SITE_DATE>

Optional.

Date for which the delivery to site has originally been forecasted.

<TECH_EVAL_COMP_DATE>

Optional.

Date when the technical evaluation of all line items has been completed.

This date can only be updated, not inserted. Update is only allowed if the user has the ‘TECHNICAL EVALUATION’ privilege. The privilege can be assigned on A.20.06.04 User Privileges.

<BUYER>

Mandatory.

The buyer attached to the order.

All users who have the 'BUYER' privilege for the project and the discipline you are logged in to are valid. The privilege is assigned on A.20.06.04 User Privileges.

<EXPEDITER>

Optional.

The expediter assigned to the order.

All users who have the 'EXPEDITER' privilege for the project and the discipline you are working in are valid. The privilege can be assigned on A.20.06.04 User Privileges.

<TRAFFIC>

Optional.

The person responsible for the traffic part of the order.

All users who have the 'TRAFFIC’ privilege for the current project and discipline are valid. The privilege is assigned on A.20.06.04 User Privileges.

<READY_FOR_APPROVAL_IND>

Optional.

Indicates whether the order is ready for approval.

Allowable values: Y, N.

This tag can only be used along with the ‘U’ and ‘N’ processing types.

<APPROVED_DATE>

Optional.

Date the order was approved.

Note the following important points:

If you are working with the basic expediting module (the ZP_NEW_EXP project default is set to N), an order can only be approved if a routing method has been provided for all item shipments.

When you use the extended expediting module (the ZP_NEW_EXP project default is set to Y), orders can only be approved if incoterm and delivery place are not empty for any order line item. Also, the promised contract date must be populated for all item shipments.

If the ZP_SUM_CO project default is set to Y, you can only approve an order if for all of its line items the Accepted check box is checked.

If the ZP_ADV_APP project default is set to Y, an order can only be approved if the Ready for Approval check box is checked.

After an order has been approved, it cannot be modified. After an order has been approved, it is available for expediting, traffic, and site.

<APPROVED_BY>

Optional.

The person who approved the order.

Allowable values:

All Smart Materials users who own the PO APPROVAL privilege for the project and discipline, respectively, where the OPI job is defined.

If the tag <APPROVED_DATE> is included and the tag <APPROVED_BY> is missing, the value of the ZP_APPRVER project default is used for the person to approve the order. This user must have the PO APPROVAL privilege.

<PARENT_ORDER>

Mandatory when inserting a change order; not used in any other cases. Primary key of any approved order of type ‘PO’ or ‘MP’.

Instead of this tag, you can also use the tags <PARENT_PO_NUMBER>, <PARENT_PO_SUPP>, <PARENT_ORIGIN_CODE>, or <PARENT_ORDER_TYPE> if you are not able to determine the value for <PARENT_ORDER>.

For retrieving the primary key of an order, the poh_id function has been provided in the m_pck_uk package.

If a negative value is returned, the order cannot be found.

Specification of the function:

Argument Name Type In/Out

P_PROJ_ID m_po_headers.proj_id IN

P_ORIGIN_CODE m_origins.origin_code IN

P_ORDER_TYPE m_po_headers.order_type IN

P_PO_NUMBER m_po_headers.po_number IN

P_PO_SUPP m_po_headers.po_supp IN

<PARENT_PO_NUMBER>

Optional when inserting a change order; not used in any other cases.

This tag is needed along with the tags <PARENT_PO_SUPP>, <PARENT_ORIGIN_CODE>, and <PARENT_ORDER_TYPE> if you do not use the tag <PARENT_ORDER>.

Name (code) of the parent order that is to be referenced by the change order to be inserted.

<PARENT_PO_SUPP>

Optional when inserting a change order; not used in any other cases.

This tag is needed along with the tags <PARENT_PO_NUMBER>, <PARENT_ORIGIN_CODE>, and <PARENT_ORDER_TYPE> if you do not use the tag <PARENT_ORDER>.

Supplement of the parent order that is to be referenced by the new change order.

<PARENT_ORIGIN_CODE>

Optional when inserting a change order; not used in any other cases.

This tag is needed along with the tags <PARENT_PO_NUMBER>, <PARENT_PO_SUPP>, and <PARENT_ORDER_TYPE> if you do not use the tag <PARENT_ORDER>.

Name (code) of the origin of the parent order that is to be referenced by the change order.

<PARENT_ORDER_TYPE>

Optional when inserting a change order; not used in any other cases.

This tag is needed along with the tags <PARENT_PO_NUMBER>, <PARENT_PO_SUPP>, and <PARENT_ORIGIN_CODE> if you do not use the tag <PARENT_ORDER>.

Type of the parent order that is to be referenced by the change order.