Staging table data errors

Error: <key column name> = <key column value> has invalid <error column name> = <error column value>. Transaction not imported.

Explanation: This transaction contains an invalid value for <error column name>. The most common reason for this error is that <error column value> references a non-existent object. For example, a user transaction requires reference to a cost center code. If the specified cost center code is not in Expense Management, this error is reported. Other causes for this error are invalid Boolean value (for example, active status) and invalid user social security number.

Error: <key column name> = <key column value> is invalid. <key column name> = <error column value> is inactive. Transaction not imported

Explanation: This transaction contains an invalid value for <error column name>. <error column value> references an object that is inactive. For example, a user transaction requires reference to a cost center code. If the specified cost center code is inactive in Expense Management, this error is reported.

Error: <key column name> = <key column value> is invalid. Error in transaction during previous processing. Transaction not imported

Explanation: Transactions with errors during primary processing are ignored during reprocessing for group memberships, user approvers and cost center approvers. They are logged as error transactions with the above message. For example, if a user transaction receives an error during user import, the transaction is also logged as an error during reprocessing for user approvers.

Error: Table Type: <table type>. <key column name> = <key column value> is invalid. Child row without parent row in staging table must correspond to an existing parent Bob. Transaction not imported

Explanation: This transaction has row(s) only in the child staging table, without a corresponding row in its parent staging table, and the transaction does not correspond to an existing business object (bob). For example, department membership rows in the staging table for memberships, alex_user_group, must have corresponding rows in the staging table alex_department when inserting a new department into the system. For existing departments, updates of department memberships do not require rows in alex_department.

Warning: Table Type: <table type>. <key column name> = <key column value>. Child transaction of type: <bob type> aborted because parent transaction has failed

Explanation: There are two types of additional transactions that are executed along with the main user transaction. These are referred to as child transactions: (1) user access to the roles defined using the application parameters HRBkgERRole, HRBkgTSRole and HRBkgPRRole (bob type: 999060300), and (2) user credit card (bob type: 50000). If the main user transaction has errors, this warning is logged for the child transactions.

Warning: <key column name> = <key column value>. credit_card_number = <credit card number> has been assigned to another user. Credit card not assigned to this user

Explanation: This user transaction contains a credit card number that has already been assigned to another user.

Error: <key column name> = <key column value> has invalid <error column name> = <error column value>. Top project code and parent project code must be null for a level 1 project code. Transaction not imported

Explanation: Top project code and parent project code should not be specified for level 1 project codes. This transaction contains a value for <error column name>.

Error: <key column name> = <key column value> is invalid. <n> bobs instead of one were returned from the database with type = <bob type>, <bob element name> = <bob element value>. Transaction not imported

Explanation: This transaction has a reference to a business object (bob) of type <bob type>. However, the referenced value (<bob element name> = <bob element value>) corresponds to more than one bob. Since Standard Import cannot identify a unique object, it reports this error. For example, a project code transaction may contain the employee number of the approver of the project. If the specified employee number corresponds to more than one user in the system, this error is reported. This error occurs because although users imported through Standard Import have unique employee numbers, you can enter users with non-unique employee numbers through Infor SAT or during initial load of the database with the load tool. The solution is either to change the employee numbers of all users entered outside of Standard Import and referred to in Standard Import to unique values, or to not refer to these users in Standard Import.

Error: <key column name> = <key column value> is invalid. key element value (<null>). Transaction not imported.

Explanation: The transaction contains one or more key columns with null values. All key column values must be specified. This error should not occur if the key column(s) identified in the table alhr_interface_definition corresponds to the primary key of the staging table, as is the case with Standard Import before any customizations.

Warning: <key column name> = <key column value>. You cannot update the column <column name> that is defined as unmodifiable.

Explanation: Applies only to update transactions. <column name> is defined as unmodifiable in the table alhr_interface_definition, and this transaction contains a value for this column that is different from the existing value in Expense Management. The existing value is not updated for this column. Any other allowable updates do occur.