Copyright © 2024, Oracle and/or its affiliates.
Field Index SQL Mapping

Class /tmp_unprocessed_events

This object contains temporary data of the unprocessed events. Example of its usage is processing of events by REL application. REL application inserts rows with intervals of events poids. IREL updater increments start_poid. As a result, the object contains only unprocessed events. This data could be used, for example, during calculation of deferred taxes in order to skip unprocessed events. Note that this example should be taken into consideration when this object is used for other purposes.

Notes

  • The system will assign poid ids above 1000 to objects of this class. The range below this is reserved for creating objects with well-known poid ids.
  • This object can be read by the owner or any billing group leader within the brand who is an ancestor of the owner.
  • This object can be modified by the owner or any billing group leader within the brand who is an ancestor of the owner.
  • This object can be created by anyone.

Links



Field Index

Type Field Name
poid PIN_FLD_POID
timestamp PIN_FLD_CREATED_T
timestamp PIN_FLD_MOD_T
string PIN_FLD_READ_ACCESS
string PIN_FLD_WRITE_ACCESS
string PIN_FLD_CREATE_ACCESS
poid PIN_FLD_ACCOUNT_OBJ
poid PIN_FLD_SESSION_OBJ
int PIN_FLD_ELEMENT_ID
decimal PIN_FLD_START_POID_ID0
decimal PIN_FLD_END_POID_ID0


Field Details

poid PIN_FLD_POID

Object Identifier for an instance of this class. Portal object ids have four pieces of information: database number, class type, sequence id, revision.

Notes

  • System defined on object creation
  • Can be modified only by System

Links

timestamp PIN_FLD_CREATED_T

Time the object was created.

Notes

  • System defined on object creation
  • Can be modified only by System

Links

timestamp PIN_FLD_MOD_T

Time the object was last modified.

Notes

  • System defined on object creation
  • Can be modified only by System

Links

string PIN_FLD_READ_ACCESS

Read Access level for object. Valid values are S(Self), G(Global), L(BrandLineage), B(BrandGroup), A(Ancestral).

Notes

  • System defined on object creation
  • Can be modified only by System
  • Maximum length is 255 bytes

Links

string PIN_FLD_WRITE_ACCESS

Write Access level for object. Valid values are S(Self), G(Global), L(BrandLineage), B(BrandGroup), A(Ancestral).

Notes

  • System defined on object creation
  • Can be modified only by System
  • Maximum length is 255 bytes

Links

string PIN_FLD_CREATE_ACCESS

Create Access level for object. Valid values are O(BrandOwner), R(Root), N(Any).

Notes

  • System defined on object creation
  • Can be modified only by System
  • Maximum length is 255 bytes

Links

poid PIN_FLD_ACCOUNT_OBJ

Link to the /account object.

Notes

  • Required on object creation
  • Can be modified

Links

poid PIN_FLD_SESSION_OBJ

This poid can contain, for example, a link to the batch_poid, which is processed by the multithreaded application.

Notes

  • Required on object creation
  • Can be modified

Links

int PIN_FLD_ELEMENT_ID

Numeric value, which can be used, for example, as a thread_id for the multithreaded application.

Notes

  • Required on object creation
  • Can be modified

Links

decimal PIN_FLD_START_POID_ID0

Portal object id of the first event un-processed.

Notes

  • Required on object creation
  • Can be modified

Links

decimal PIN_FLD_END_POID_ID0

Portal object id of the last event un-processed.

Notes

  • Required on object creation
  • Can be modified

Links



SQL Mapping


Type Field Name Table Column Name
base-class /tmp_unprocessed_events tmp_unprocessed_events_t
poid PIN_FLD_POID poid*
timestamp PIN_FLD_CREATED_T created_t
timestamp PIN_FLD_MOD_T mod_t
string PIN_FLD_READ_ACCESS read_access
string PIN_FLD_WRITE_ACCESS wrtie_access
string PIN_FLD_CREATE_ACCESS create_access
poid PIN_FLD_ACCOUNT_OBJ account_obj*
poid PIN_FLD_SESSION_OBJ session_obj*
int PIN_FLD_ELEMENT_ID element_id
decimal PIN_FLD_START_POID_ID0 start_poid_id0
decimal PIN_FLD_END_POID_ID0 end_poid_id0
Column names marked with * are actually column prefixes. For poid type fields, the column prefix is used to create the columns poid_id0, poid_db and poid_type if the prefix is "poid". For PIN_FLD_POID in the base table, an additional column named poid_rev is created to hold the poid revision. For buffer fields, two columns are created - one in the containing table and one in the buffer table. For example if the prefix is "buf", then the column name in the buffer table is buffer_buf and the column name in the containing table is buffer_size.

Field Index This Class