Error Codes - Intergraph Smart Materials - Version 10.2 - Customization & Programming - Hexagon

Intergraph Smart Materials Classic API Configuration (10.2)

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

In the Error Number column, the packages replace yyy with the name of the column.

Error Number

Meaning

101 - yyy

Null value not allowed.

102 - yyy

Value too large.

103 - yyy

Value too small.

104 - yyy

Value not numeric.

105 - yyy

Invalid date.

106 - yyy

Invalid value.

107 - yyy

Date in future not allowed.

108

Unique key violation.

201

Object (inquiry, quote, quote detail, ...) does not exist.

202

NLS does not exist.

211 - yyy

Update of column/table or insert not allowed after approval.

212 - yyy

Update of column not allowed before approval.

213

Insert not allowed after approval of order.

214

Insert only allowed after approval of order.

215

Insert only allowed if no detail tags exist.

216

No update of order (or subsequent elements) without
the ‘ASSIGN BUYER’ privilege or with not
being the buyer of the order.

217

No insert/update because higher inquiry supplement exists already.

501

Account code cannot be changed because of the ZJ_USE_AC project default.

502

Supplier not updateable for change orders, manual orders
with an assigned BO,
and purchase orders based on NOCs.

503

PO_ISSUE_DATE cannot be changed because
technical evaluation of corresponding quote summary is not
yet completed.

504

PO_ISSUE_DATE cannot be changed because
order is already closed.

505

PERFORMANCE_SCORE can only be set after
order has been issued.

506

Indicator for evaluation cost cannot be set for
orders or their line items.

507

split_qd_seq must be populated for splits of quote details.

508

split_qd_seq must not be populated for
alternates of quote details.

509

Update/Insert of delivery designation requires
update/insert of routing method, too.

510

Delivery designation and routing method do not match.

511

Last ship must be greater than or equal to first ship.

512

Update of order quantity not allowed because more than one requisition line item is assigned to order line item.

513

ZP_DEVATTR project default not set.

514

Invalid combination of PARENT_ORDER and ORDER_TYPE.

515

Referenced order line item does not exist or belongs to different order.

516

Requisition line item does not exist, or requisition line item
has not been released to procurement, or requisition
cannot be used for purchase, or requisition belongs to different project.

517

Invalid order type.

518

Line items referring and not referring to a requisition line item
cannot be mixed up on the same order.

519

Insert for manual PO referencing a BO not allowed.

520

No default defined for delivery designation (ZP_DLV_DSG project default).

521

Creation of detail tag not possible (please see chapters A.3.3 Procedure:
ins_detail_qd, A.5.3 Procedure: ins_detail_poli, and
A.6.3 Procedure: ins_detail_ish, respectively, for reasons).

522

Update quantity of master tag not allowed.

523

Update of quantity not allowed because of MCS.

524

Quantity of a master tag can only be 1 or 0.

525

Update quantity of detail tag not allowed; master tag cancelled.

526

Update price of detail tag not allowed.

527

Update quantity unit only allowed for detail tags.

528

Update discount percent of detail tag not allowed.

529

Update discount amount of detail tag not allowed.

530

Alternates or splits cannot be created for master or detail tags.

531

Text and term already attached.

532

Ident of referenced requisition line item and of
new order line item do not match.

533

Position already used on any supplement of order cycle.

534

Update quantity not allowed because of multiple requisition line items

535

Update not allowed because of percentage setting

536

Corporate warehouse supplier not allowed.

537

Quantity update not allowed for order for corporate warehouse.

538

Insert not allowed on order for corporate warehouse.

539

Either unit price type or unit / supply / install price can be set.

540

Either unit price type or ‘Other Cost %’, ‘Cost Value per Unit’,
‘Cost Value Total’ can be set.

541

Insert not allowed on order for FIM (Free Issued Material) warehouses.

542

FIM supplier not allowed.

543

Quantity update not allowed for order for FIM warehouses.

544

Requisition line item cannot be assigned to the order line item because
the requisition line item has already been consumed completely.
Order line item was not imported.

545

Requisition line item does not exist.

546

Order approval is not possible. Requisition line item does not exist.

547

Quantity for requisition line item not available.

548

Requisition line item cannot be assigned to the order line item because
the requisition line item has already been consumed completely or order quantity is
not sufficient for requested cancelation.

549

At most, the specified quantity can be canceled.

550

The tag numbers of the referenced requisition line item and of the new order line item do not match.

601 - yyy

Column only updateable for purchase and change orders.

602 - yyy

Column only updateable for blanket orders and notices of commitment.

701 - yyy

Missing privilege for updating column.

702

Invalid user security.

703

Project of object and of user security do not match.

750 - ORA-20000: MAR-zzzzz

An error has occurred in an internal procedure; MAR-zzzzz stands for a message number that can be seen on screen A.60.31.

yyy

Column not supported by package.

In addition to these error numbers, the following messages raised by ORACLE® can occur:

  • ORA-01400: cannot insert NULL into ("M_SYS"."table_name"."column_name")

  • ORA-00001: unique constraint (M_SYS.table_short_name_UK) violated

  • ORA-00001: unique constraint (M_SYS.table_short_name_PK) violated

  • ORA-20000: MAR-25353 #1CREATE_SPLIT no data found 100 (please see chapters A.3.3 Procedure: ins_detail_qd, A.5.3 Procedure: ins_detail_poli, and A.6.3 Procedure: ins_detail_ish, respectively, for reasons).