Friday, April 17, 2009

PO Tables and Relation


Requisitions
  • PO_REQUISITION_HEADERS_ALL    [ Segment1 is Req number and Req header become po Header]                                
  • PO_REQUISITION_LINES_ALL  [ Req lines become PO Lines]             
  • PO_REQ_DISTRIBUTIONS_ALL [Req Distributions become PO Distribution]
  • Use Workflow item type and item key to review approval workflow

Purchase Orders
  • PO_HEADERS_ALL       [ Segment1 is PO number ]
  • PO_LINES_ALL             [ Not at used for Contract PO's ]
  • PO_RELEASES_ALL     [Release shipments for blanket & planned POs
  • PO_LINE_LOCATIONS_ALL  [Shipments – 1 record per schedule or price break ]
  • PO_DISTRIBUTIONS_ALL      [Accounting information for Standard & Planned POs and Releases]
Receiving

  • RCV_TRANSACTIONS    [Historical transaction detail forevery transactions]
  • RCV_SHIPMENT_HEADERS [Source is Supplier or Internal]
  • RCV_SHIPMENT_LINES ==> PO_LINE_LOCATIONS_ALL

Archive Purchase Order 

  • PO_HEADERS_ARCHIVE_ALL
  • PO_LINE_ARCHIVE_ALL
  • PO_LINE_LOCATIONS_ARCHIVE_ALL
  • PO_DISTRIBUTIONS_ARCHIVE_ALL

2 Way Matching

  • PO_DISTRIBUTIONS_ALL
  • AP_INVOICE_DISTRIBUTIONS_ALL

3 Way Matching

  • RCV_TRANSACTIONS           ----->   AP_INVOICE_DISTIBUTIONS_ALL
  • PO_DISTRIBUTIONS_ALL   ----->    [rcv_transaction_id,po_distribution_id]

Approvals/Buyers

  • PO_AGENTS              ===> PER_ALL_PEOPLE_F
  •          ||                            ===> PER_ALL_ASSIGNMENTS
  •          ||                            ===> PER_JOBS_PER_ALL_POSITIONS
PO_HEADERS_ALL                                         ||
PO_RELEASES_ALL                                        ||
PO_REQUISITION_LINES_ALL                ||
                                                                                  ||
  •                                                           PO_CONTROL_GROUPS_ALL
  •                                                           PO_POSITION_CONTROLS_ALL                                                                                                 [position_id, Job_id ]

No comments: