TRANSACTION_ID

The Primary Key for this table; its value must be generated from the sequence EGO_IUA_TRANSACTION_ID_S.

PROCESS_STATUS

Whether this row has yet to be processed, is currently being processed, encountered an error, or was successfully processed; its value should correspond to the following constants in EGO_ITEM_USER_ATTRS_CP_PUB: G_PS_TO_BE_PROCESSED, G_PS_IN_PROCESS, G_PS_ERROR, and G_PS_SUCCESS.

DATA_SET_ID

The identifier for a group of rows to be processed together; all rows being processed as part of a single request must share the same DATA_SET_ID, whose value must be generated from the sequence EGO_IUA_DATA_SET_ID_S.

The following column values will be validated and used to populate the ORGANIZATION_ID, INVENTORY_ITEM_ID, ITEM_CATALOG_GROUP_ID, and REVISION_ID columns.

ORGANIZATION_CODE

The organization to which the Item belongs; currently, user-defined attributes are supported only for master organizations, and the organization code is validated to ensure that it refers to a master organization.

ITEM_NUMBER

The item number (such as, concatenated segments) for the item.

REVISION

The three-letter code for the current revision of the item (only used if the attribute group is associated at the item revision level; for attribute groups associated at the item level, leave NULL).

Because the user-defined attributes framework is so flexible, its structure must be flattened out for this interface table. To understand this flattening it is useful to first define a logical attribute group row. For single-row attribute groups, the logical attribute group row is just the collection of attributes in the attribute group, but for multi-row attribute groups, each row in the attribute group is a logical attribute group row. For example, the single-row attribute group "Dimensions," with Attributes "Width" and "Height," has only one logical attribute group row, but multi-row attribute group "Orders," with attributes "Date" and "Price" has as many logical attribute group rows as there are separate orders to be recorded.

Every interface table row contains data for one attribute in a logical attribute group row, and a logical attribute group row spans as many interface table rows as there are attributes in the logical attribute group row. To keep these flattened-out logical attribute group rows in order, there is the ROW_IDENTIFIER column, which uniquely identifies each logical attribute group row (for example, all attributes with the same ROW_IDENTIFIER value will belong to the same logical attribute group row). Thus, if a multi-row attribute group has ten attributes and three rows of values (for example, three logical attribute group rows), then there will be thirty interface table rows for the attribute group and three distinct ROW_IDENTIFIER values in those thirty rows.

ROW_IDENTIFIER

The grouping identifier for a logical attribute group row; its value must be the same for all interface table rows in the logical attribute group row, and no two logical attribute group rows in the same data set may share the same ROW_IDENTIFIER value.

ATTR_GROUP_INT_NAME

The internal name of the attribute group to which the current interface table row's attribute belongs.

ATTR_INT_NAME

The internal name of the attribute for which the current interface table row holds a value.

ATTR_VALUE_STR

The value for the current interface table row's attribute if its data type is string.

ATTR_VALUE_NUM

The value for the current interface table row's attribute if its data type is number.

ATTR_VALUE_DATE

The value for the current interface table row's attribute if its data type is date. Values will be converted to and from date data types using the format specified in EGO_USER_ATTRS_DATA_PVT.G_DATE_FORMAT.

ATTR_DISP_VALUE

The value for the current interface table row's attribute (as a string, regardless of its data type) if the attribute has a value set with separate display and internal values (for example, value sets with validation type of independent or table). In all other cases, use the preceding three columns.

ATTR_UOM_DISP_VALUE

The description of the unit of measure associated with the attribute.

ATTR_VALUE_UOM

The internal value of the unit of measure associated with the attribute.

TRANSACTION_TYPE

The mode of processing for a logical attribute group row; its value should correspond to the following constants in EGO_USER_ATTRS_DATA_PVT: G_DELETE_MODE, G_UPDATE_MODE, G_SYNC_MODE (which either creates or updates, as appropriate), and G_CREATE_MODE. Note that rows will be processed in the order they were just presented (for example, deletion first, followed by updates and synchronization, with creation last), in accordance with Oracle Applications standards. Typical values of these constants are: CREATE, SYNC, UPDATE, or DELETE.

ORGANIZATION_ID

This column is for internal use, and any user-entered values are ignored.

INVENTORY_ITEM_ID

This column is also for internal use, but the user may enter the inventory item ID if known. If the inventory item ID is passed for a given item number, it will save conversion time from item number into inventory item ID; the inventory item ID will still be validated internally, because it will be used with the organization ID to find the item catalog group ID (so rows with invalid inventory item IDs will time-out during the item catalog ID fetching step).

ITEM_CATALOG_GROUP_ID

This column is for internal use, and any user-entered values are ignored.

REVISION_ID

This column is for internal use, but the user may enter the revision ID if known (and if this interface table row belongs to an attribute group that is associated at the item revision level). Doing so will save conversion time.

ATTR_GROUP_ID

This column is provided in case the user knows the attribute group ID for this interface table row's attribute group. If left blank, the attribute group internal name is used to identify the attribute group.

REQUEST_ID

This column is for internal use (to record the concurrent program request that ordered the processing of this row).

PROGRAM_APPLICATION_ID

This column is for internal use (to record the application ID of the concurrent program that processed this row).

PROGRAM_ID

This column is for internal use (to record the ID of the concurrent program that processed this row).

PROGRAM_UPDATE_DATE

This column is for internal use (to record the time the concurrent program processed this row).

The remaining columns are the standard "Who" columns, and their values must be entered when you load the interface table.