Analytics Catalog/Data dictionary/PON_REQUIREMENTS
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

PON_REQUIREMENTS

ProcurementUsed in 2 subject areas25 reporting columns

Sourcing / Negotiations (PON).

Likely primary key: REQUIREMENT_ID (inferred from Oracle naming conventions, verify against Tables & Views)

Columns

ColumnKeyIn reportsDescription (inferred)
ABSOLUTE_SECTION_SEQUENCEAbsolute section sequence.
ALLOW_ATTACHMENT_CODECode identifying the allow attachment.
ALLOW_COMMENTSAllow comments.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
DATATYPEDatatype.
DATETIME_VALUEDatetime value.
DATE_VALUEDate value.
DISPLAY_TARGET_FLAGIndicator (Y/N) for the display target.
HINTHint.
KNOCKOUT_SCOREKnockout score.
MAX_SCOREMax score.
NUMBER_VALUENumber value.
QUESTION_IDIdentifier for the question.
REQUIREMENT_IDPK?Identifier for the requirement.
REQUIREMENT_NAMEName of the requirement.
REQUIREMENT_TEXTRequirement text.
REQUIREMENT_TYPEType of requirement.
REQ_DISPLAY_NUMBERReq display number.
RESPONSE_TYPEType of response.
REVISION_NUMBERRevision number.
SCORING_METHODScoring method.
SUPPLIER_LEVELSupplier level.
TEXT_VALUEText value.
WEIGHTWeight.

Used by reports

No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.

Need the extract + dbt staging for PON_REQUIREMENTS?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern