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_SEQUENCE●Absolute section sequence.
ALLOW_ATTACHMENT_CODE●Code identifying the allow attachment.
ALLOW_COMMENTS●Allow comments.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DATATYPE●Datatype.
DATETIME_VALUE●Datetime value.
DATE_VALUE●Date value.
DISPLAY_TARGET_FLAG●Indicator (Y/N) for the display target.
HINT●Hint.
KNOCKOUT_SCORE●Knockout score.
MAX_SCORE●Max score.
NUMBER_VALUE●Number value.
QUESTION_ID●Identifier for the question.
REQUIREMENT_IDPK?●Identifier for the requirement.
REQUIREMENT_NAME●Name of the requirement.
REQUIREMENT_TEXT●Requirement text.
REQUIREMENT_TYPE●Type of requirement.
REQ_DISPLAY_NUMBER●Req display number.
RESPONSE_TYPE●Type of response.
REVISION_NUMBER●Revision number.
SCORING_METHOD●Scoring method.
SUPPLIER_LEVEL●Supplier level.
TEXT_VALUE●Text value.
WEIGHT●Weight.

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. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed 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