Timeline

This unique sequence number is used to distinguish between different timelines.

This field contains the number which uniquely identifies the timeline number to which the timeline step is attached to.

This field will hold the module the timeline is referring to. Valid values are: PO - Purchase Orders at the Header Level POIT - Purchase Orders at the Item Level IT - Item Maintenance CE - Customs Entry LO - Logistics at the Header Level LOBL - Logistics at the Bill of Lading Level LOCO - Logistics at the Container Level LOPI - Logistics at the Purchase Order/Item Level LOCI - Logistics at the Commercial Invoice Level

Alphanumeric value that identifies the module that the timeline is attached to. For example, if the module is Purchase Orders, then key_value_1 would be the Order number.

Alphanumeric value that identifies an item if the module the timeline is attached to is a Purchase Order at the item level.

This field will hold the date that the timeline will be driven on.

This field contains the number which uniquely identifies the timeline step which will be attached to the corresponding order.

This field contains a number which will determine the display order of the steps. This will be directly copied from the DISPLAY_SEQ field on the TIMELINE_STEPS table. The reason this field must also be on this table is to actually put an Order By clause in an Oracle Form, the order by clause must be on the base table, which in this case would be the ORD_TIMELINE table.

This field contains the initial date that the step is set to be completed. This field will be automatically populated within Oracle Retail by the date criteria setup from the TIMELINE_BASE field on the TIMELINE table and the DAYS_COMPLETED on the TIMELINE_STEPS table. It is also allowable to manually enter this field when attaching a timeline to an order.

This field contains the revised date that the step is set to be completed. This field can be manually entered by the user while maintaining the timeline.

This field contains the actual date that the step is completed on. The date will have to be manually entered by the user while maintaining the order.

This field contains the code which explains the original date vs. actual date variance for each timeline step.

This field may contain a comment entered by the user while setting-up and maintaining the timeline on the order.

Date/time stamp of when the record was created. This date/time will be used in export processing. This value should only be populated on insert - it should never be updated.

Holds the date time stamp of the most recent update by the last_update_id. This field is required by the database.

Holds the Oracle user-id of the user who most recently updated this record. This field is required by the database.

This column holds the User id of the user who created the record.