RCV_SHIPMENT_HEADERS is the table used by Oracle Fusion to store the Shipment Header related info. So where does shipment comes in the picture? Well, answer lies if you have implemented P2P Cycle, you will send the purchase orders to the vendor/ Supplier. Supplier will then send you the goods and the shipment information of your purchase order will be given to you as well. This shipment information is stored in RCV_SHIPMENT_HEADERS Table.
But since RCV_SHIPMENT_HEADERS is a header table, it must have a child too. Name of the child is RCV_SHIPMENT_LINES. And the tables are connected using the column SHIPMENT_HEADER_ID which is also the primary key of parent table. In this blog, we will have a look at the table structure and the indexes of this table.
Now every row in this table can have multiple rows in the child table RCV_SHIPMENT_LINES tables. Difference is that shipment lines will have the details at item level. After all your one PO can have multiple items, and the RCV_SHIPMENT_LINES table can have the data for each of those items. Again, data in RCV_SHIPMENT_LINES is kind of planned data i.e supplier has told you that your goods will be delivered according to this plan. But real receiving ( physically goods receiving) data lies in RCV_TRANSACTIONS table which is the grandchild table of RCV_SHIPMENT_HEADERS table & Child table of RCV_SHIPMENT_LINES table.
To get the query to fetch you receiving details, click here.
RCV_SHIPMENT_HEADERS: Column Details
| COLUMN_NAME | DATA_TYPE | NULLABLE |
| SHIPMENT_HEADER_ID | NUMBER | N |
| LAST_UPDATE_DATE | TIMESTAMP(6) | N |
| LAST_UPDATED_BY | VARCHAR2(256) | N |
| CREATION_DATE | TIMESTAMP(6) | N |
| CREATED_BY | VARCHAR2(256) | N |
| LAST_UPDATE_LOGIN | VARCHAR2(128) | Y |
| RECEIPT_SOURCE_CODE | VARCHAR2(100) | N |
| VENDOR_ID | NUMBER | Y |
| VENDOR_SITE_ID | NUMBER | Y |
| ORGANIZATION_ID | NUMBER | Y |
| SHIPMENT_NUM | VARCHAR2(120) | Y |
| RECEIPT_NUM | VARCHAR2(120) | Y |
| SHIP_TO_LOCATION_ID | NUMBER | Y |
| BILL_OF_LADING | VARCHAR2(100) | Y |
| PACKING_SLIP | VARCHAR2(100) | Y |
| SHIPPED_DATE | DATE | Y |
| FREIGHT_CARRIER_ID | NUMBER | Y |
| EXPECTED_RECEIPT_DATE | DATE | Y |
| EMPLOYEE_ID | NUMBER | Y |
| NUM_OF_CONTAINERS | NUMBER | Y |
| WAYBILL_AIRBILL_NUM | VARCHAR2(80) | Y |
| COMMENTS | VARCHAR2(4000) | Y |
| ATTRIBUTE_CATEGORY | VARCHAR2(120) | Y |
| ATTRIBUTE1 – ATTRIBUTE20 | VARCHAR2(600) | Y |
| ATTRIBUTE_NUMBER1 – ATTRIBUTE_NUMBER10 | NUMBER | Y |
| ATTRIBUTE_DATE1 – ATTRIBUTE_DATE5 | DATE | Y |
| ATTRIBUTE_TIMESTAMP1 – ATTRIBUTE_TIMESTAMP5 | TIMESTAMP(6) | Y |
| GOVERNMENT_CONTEXT | VARCHAR2(120) | Y |
| REQUEST_ID | NUMBER | Y |
| ASN_TYPE | VARCHAR2(100) | Y |
| EDI_CONTROL_NUM | VARCHAR2(40) | Y |
| NOTICE_CREATION_DATE | DATE | Y |
| GROSS_WEIGHT | NUMBER | Y |
| GROSS_WEIGHT_UOM_CODE | VARCHAR2(12) | Y |
| NET_WEIGHT | NUMBER | Y |
| NET_WEIGHT_UOM_CODE | VARCHAR2(12) | Y |
| TAR_WEIGHT | NUMBER | Y |
| TAR_WEIGHT_UOM_CODE | VARCHAR2(12) | Y |
| PACKAGING_CODE | VARCHAR2(20) | Y |
| CARRIER_METHOD | VARCHAR2(8) | Y |
| CARRIER_EQUIPMENT | VARCHAR2(40) | Y |
| SPECIAL_HANDLING_CODE | VARCHAR2(12) | Y |
| HAZARD_CODE | VARCHAR2(4) | Y |
| HAZARD_CLASS | VARCHAR2(16) | Y |
| HAZARD_DESCRIPTION | VARCHAR2(320) | Y |
| FREIGHT_TERMS | VARCHAR2(100) | Y |
| FREIGHT_BILL_NUMBER | VARCHAR2(140) | Y |
| INVOICE_NUM | VARCHAR2(200) | Y |
| INVOICE_DATE | DATE | Y |
| INVOICE_AMOUNT | NUMBER | Y |
| TAX_NAME | VARCHAR2(60) | Y |
| TAX_AMOUNT | NUMBER | Y |
| FREIGHT_AMOUNT | NUMBER | Y |
| INVOICE_STATUS_CODE | VARCHAR2(100) | Y |
| ASN_STATUS | VARCHAR2(40) | Y |
| CURRENCY_CODE | VARCHAR2(60) | Y |
| CONVERSION_RATE_TYPE | VARCHAR2(120) | Y |
| CONVERSION_RATE | NUMBER | Y |
| CONVERSION_DATE | DATE | Y |
| PAYMENT_TERMS_ID | NUMBER | Y |
| SHIP_TO_ORG_ID | NUMBER | Y |
| CUSTOMER_ID | NUMBER | Y |
| CUSTOMER_SITE_ID | NUMBER | Y |
| REMIT_TO_SITE_ID | NUMBER | Y |
| SHIP_FROM_LOCATION_ID | NUMBER | Y |
| APPROVAL_STATUS | VARCHAR2(100) | Y |
| PERFORMANCE_PERIOD_FROM | DATE | Y |
| PERFORMANCE_PERIOD_TO | DATE | Y |
| REQUEST_DATE | DATE | Y |
| JOB_DEFINITION_NAME | VARCHAR2(400) | Y |
| JOB_DEFINITION_PACKAGE | VARCHAR2(3600) | Y |
| OBJECT_VERSION_NUMBER | NUMBER | N |
| LSP_FLAG | VARCHAR2(4) | Y |
| RA_OUTSOURCER_PARTY_ID | NUMBER | Y |
| RECEIPT_ADVICE_NUMBER | VARCHAR2(320) | Y |
| RA_DOCUMENT_CODE | VARCHAR2(100) | Y |
| RA_DOCUMENT_NUMBER | VARCHAR2(320) | Y |
| RA_DOC_REVISION_NUMBER | VARCHAR2(320) | Y |
| RA_DOC_REVISION_DATE | DATE | Y |
| RA_DOC_CREATION_DATE | DATE | Y |
| RA_DOC_LAST_UPDATE_DATE | DATE | Y |
| RA_OUTSOURCER_CONTACT_ID | NUMBER | Y |
| RA_NOTE_TO_RECEIVER | VARCHAR2(1920) | Y |
| RMA_BU_ID | NUMBER | Y |
| RA_DOO_SOURCE_SYSTEM_ID | NUMBER | Y |
| HEADER_INTERFACE_ID | NUMBER | Y |
| RA_ORIG_SYSTEM_REF | VARCHAR2(120) | Y |
| GL_DATE | DATE | Y |
| EXTERNAL_SYS_TXN_REFERENCE | VARCHAR2(1200) | Y |
Index Details
| INDEX_NAME | INDEX_TYPE | UNIQUENESS | COLUMN_NAME |
| RCV_SHIPMENT_HEADERS_N1 | NORMAL | NONUNIQUE | SHIP_TO_LOCATION_ID |
| RCV_SHIPMENT_HEADERS_N10 | NORMAL | NONUNIQUE | CREATION_DATE |
| RCV_SHIPMENT_HEADERS_N11 | NORMAL | NONUNIQUE | PACKING_SLIP |
| RCV_SHIPMENT_HEADERS_N12 | FUNCTION-BASED NORMAL | NONUNIQUE | SYS_NC00126$ |
| RCV_SHIPMENT_HEADERS_N13 | FUNCTION-BASED NORMAL | NONUNIQUE | SYS_NC00127$ |
| RCV_SHIPMENT_HEADERS_N14 | NORMAL | NONUNIQUE | EXTERNAL_SYS_TXN_REFERENCE |
| RCV_SHIPMENT_HEADERS_N15 | NORMAL | NONUNIQUE | CUSTOMER_ID |
| RCV_SHIPMENT_HEADERS_N2 | NORMAL | NONUNIQUE | SHIPMENT_NUM |
| RCV_SHIPMENT_HEADERS_N3 | NORMAL | NONUNIQUE | VENDOR_ID |
| RCV_SHIPMENT_HEADERS_N4 | NORMAL | NONUNIQUE | VENDOR_SITE_ID |
| RCV_SHIPMENT_HEADERS_N5 | NORMAL | NONUNIQUE | RECEIPT_SOURCE_CODE |
| RCV_SHIPMENT_HEADERS_N6 | NORMAL | NONUNIQUE | RECEIPT_NUM |
| RCV_SHIPMENT_HEADERS_N6 | NORMAL | NONUNIQUE | SHIP_TO_ORG_ID |
| RCV_SHIPMENT_HEADERS_N7 | NORMAL | NONUNIQUE | EMPLOYEE_ID |
| RCV_SHIPMENT_HEADERS_N8 | FUNCTION-BASED NORMAL | NONUNIQUE | RA_DOCUMENT_CODE |
| RCV_SHIPMENT_HEADERS_N8 | FUNCTION-BASED NORMAL | NONUNIQUE | SYS_NC00124$ |
| RCV_SHIPMENT_HEADERS_N9 | FUNCTION-BASED NORMAL | NONUNIQUE | SYS_NC00125$ |
| RCV_SHIPMENT_HEADERS_U1 | NORMAL | UNIQUE | SHIPMENT_HEADER_ID |
| RCV_SHIPMENT_HEADERS_U2 | NORMAL | UNIQUE | RECEIPT_ADVICE_NUMBER |
| RCV_SHIPMENT_HEADERS_U2 | NORMAL | UNIQUE | RA_DOO_SOURCE_SYSTEM_ID |
Related Posts:
RCV_SHIPMENT_HEADERS: Columns & Indexes
Query To Get The Shipment Details In Oracle Fusion
Item Shipment History Query in Fusion
Feedback:
Hope the article helped you. If it did, please rate the post. In case it didn’t, do leave a comment to let us know what did we miss.
Reference:
support.oracle.com
From: Mohit Saxena
Author of “Oracle Fusion: Unconventional Ways to Enhance the Performance of BI Reports“
3 thoughts on “RCV_SHIPMENT_HEADERS: Columns & Indexes”
Comments are closed.