Hi All,
I'm trying to design and model purchase orders, requisitions and receipts in the RPD, but I’m coming stuck and need some help. My end goal is to be able to create the following reports in answers which report real time off an EBS database:
1. Return all Requisitions (it may not have a Purchase Order)
2. Return all Requisitions and Purchase Orders (whether or not the Requisition has a Purchase Order)
3. Return all Requisitions, Purchase Orders, receipts (whether or not the Requisition has a Purchase Order or receipt)
4. Return all Purchase Orders (it may not have a requisition)
5. Return all Purchase Orders and Requisitions (whether or not the Purchase Order has a requisition)
6. Return all Purchase Orders, Requisitions and receipts (whether or not the Purchase Order has a requisition or receipt)
7. Return all receipts
8. Return all receipts and Purchase Orders (whether or not the receipts has a Purchase Orders)
9. Return all receipts, Purchase Orders and Requisitions (whether or not the receipts has a Purchase Orders or requisition)
My dilemma is that I'm not sure where to start modelling these tables in the recommended star topology. It's never as easy as a simple 'Sales Fact' in the middle and 'Various Dimensions' around, as you would read in various places. How should we model po_headers_all, po_lines_all and po_distributions_all for example, which is contains a mixture of facts and dimension.
Here is some of the EBS Fact & Dimension Tables I believe would need modelled based on the above report requirements:
po_requisition_headers_all
po_requisition_lines_all
po_req_distributions_all
po_headers_all
po_lines_all
po_line_locations_all
po_distributions_all
rcv_transactions
rcv_shipment_headers
rcv_shipment_lines
po_vendors
gl_code_combinations
per_people_f
fnd_user
Any ideas where to start (or stop)?
Thanks,
Lance