IM Doc Head

this column holds the reim internal id of the document. these ids are generated by the system when new invoices are uploaded into the system or manually created by a user. the im_doc_id_sequence is used to generate these unique ids. this column is generally not displayed to the user, but is used internally by the application to provide a unique id. this column is mandatory not null.

Document type. Options are:MRCHI(Merchandising Invoice), NMRCHI(Non-merchandising Invoice), CRDNT(Credit Note), CRDNRC(Credit Note Request Cost), CRDNRQ(Credit Note Request Quantity), CRDNRT(Credit Note Request Tax), CRDNRA(Credit Note Request Allowance), DEBMEC(Debit Memo Cost), DEBMEQ(Debit Memo Quantity), DEBMET(Debit Memo Tax), DEBMEA(Debit Memo Allowance), CRDMEC(Credit Memo Cost, aka Payback Cost), CRDMEQ(Credit Memo Quantity aka Payback Quantity) and CRDMEA(Credit Memo Allowance aka Payback Allowance)

Document status. Options are:RMTCH(Ready to matchy), URMTCH(Unresolved match), MTCH(Matched), APPRVE(Approved), POSTED(Posted), DELETE(Deleted), VOID(Voided), DISPUT(Disputed), SUBMIT(Submitted), TAXDIS(Tax Discrepant), WKSHT(Worksheet), PROCESS(Processing), TAXREV(Tax Review) and ALLDIS(Allowance Discrepancy)

the order number that the invoice is for.

the location number that the invoice is for.

this column holds the type of the location associated with the document. this column is optional, but loc_type cannot have a value if location is null. valid values are s for store and w for warehouse.

this column holds the total of all discounts that have been applied to the document. this column is always stored in the currency of the invoice. this column is optional.

this column holds document group ids. if the invoice was manually entered through the document group (batch list) entry screens, it will belong to a document group. document groups are therefore optional. document group information is stored on the im_doc_group_list table. there is no foreign key to the im_doc_group_list table because document groups are only a data entry convenience and are therefore purged more regularly than documents themselves.

this column will hold the parent document id for multi-loc invoices that have been split from parent invoices to child invoices. if this column is not null, the document is the result of a parent to child split. if the column is null, the document is independent and not related to any parent invoices.

this column holds the document date. the document date is the date the document was created. when documents are created by an outside party, the doc_date can be different from the create_date (i.e. the doc_date on a merchandise invoice from a supplier will be the date the supplier generates the invoice - the create_date for this record will be the date the invoice was entered into reim). this column is mandatory not null.

The date a record was created.

The username identifier of the user who created a record.

this column holds type of vendor the document is associated with. valid values are: bk - bank ag - agent ff- freight forwarder im - importer br - broker fa - factory ap - applicant co - consolidator cn - consignee s1 - merchandising system supplier hierarchy level 1 s2 - merchandising system supplier hierarchy level 2 s3 - merchandising system hierarchy level 3 supp - supplier this column is mandatory not null.

this column holds the id of the vendor associated with the document. this id can be either a valid supplier or valid vendor in the merchandising system. this column is mandatory not null.

this column holds the id for the document that is used in communication with the vendor. this is the document id that will generally be displayed to the end user. ext_doc_id must be unique by vendor (meaning that each vendor can have a document with the id 1, but each vendor can have only one document with the id 1). if the vendor created the document (i.e. merchandise invoice, etc), this field will hold the vendors id for the document. if the retailer created the document in response to a client document (i.e. credit note request, etc), the ext_doc_id will be the original ext_doc_id prefixed or suffixed with the appropriate values from the im_system_options table (credit_note_req_prefix_cost, debit_mem)_prefix_qty , credit_memo_suffix_dp). for example, if this document is a credit memo is in response to a quantity mismatch on a merchandise invoice with the ext_doc_id 3456, this column will hold the im_system_options. credit_memo_prefix_qty concatenated with 3456. when ext_doc_id data is entered on a screen or uploaded via edi it will be limited to 27 characters so that a suffix or prefix could be added if needed. also, if this document were created as a result of a splitting a parent invoice, then the ext_doc_id will be the ext_doc_id of the parent with the location number appended to the end. therefore, the screen should still limit to 27 characters, however the database will allow up to 45 in order to account for the possibility of the location number being appended to the end. this column is mandatory not null.

this column indicates whether the document has been downloaded to a vendor (edi 812). only response documents (i.e. documents created in response to a merchandise or non - merchandise invoice like a credit note request) will be downloaded. documents will be downloaded in the next batch download run after they are approved. when documents are created, this column will be defaulted to n - no. when documents are actually downloaded, this column will be set to y. this column is mandatory not null.

this column holds the terms associated with the document. if the document is being manually entered and the document type is mrchi - merchandise invoice - this column will be defaulted to the terms associated with the purchase order. if the document is being manually entered and the document type is not mrchi - the document is not a merchandise invoice, the terms will be defaulted to the default terms associated with the vendor in the merchandise system. this column is mandatory not null.

this column holds the discount percentage associated with the term for the document. this information will be defaulted to the discount percentage for the term definition. this information will be defined in the merchandising system. this column is mandatory not null.

this column holds the due date associated with the document. for retailer created documents (i.e. merchandise invoice, non-merchandise invoice), this column holds the due date specified by the vendor. for documents created by the retailer, the due_date will hold the date that corresponds to the im_doc_head.create_date plus the number of due days associated with the term. this column is mandatory not null.

this column holds the payment method associated with the document. for retailer created documents, the payment method will default to vendors default payment method. if no payment method has been defined for the vendor, this column will be null. this column is optional.

this column holds the id of the user that matched the document. for documents matched by the automatch process, this column will be defaulted to automatch. for documents that are manually matched, this column will hold the users id. this column is optional.

this column holds the date that the document was matched. this column will be defaulted by both the manual and automatch processes. this column is optional.

this column holds the id of the user that approved the document. this column is optional.

this column holds the date that the document was approved. this column is optional.

the column will indicate whether the invoice was paid prior to matching. valid values are y yes and n no.

the column will hold the id of the user that paid the invoice. the field will be populated when a user pre-pays an invoice before matching has occurred.

this column holds the date the document was posted to the general ledger. this column is optional and will be populated by the application by the process that posts to the gl. this column is optional, but will be required by the application when the document is posted.

this column holds the currency code associated with the document. when the document is uploaded via edi, this currency will be specified. when the document is created via the single document entry screen, the user can choose a document. when the document is created via the document group screen, the currency for the document will be defaulted from the currency for the document group. this column is mandatory not null.

this column holds the exchange rate for the currency code.

this column holds the total cost of the document. this column is mandatory not null.

this column holds the total quantity of the document. this column is mandatory not null.

the column will indicate whether the invoice has been manually paid. valid values are: y yes and n no

this column holds any custom information that the retailer would like to hold at a document level. this column is optional.

this column holds any custom information that the retailer would like to hold at a document level. this column is optional.

this column holds any custom information that the retailer would like to hold at a document level. this column is optional.

this column holds any custom information that the retailer would like to hold at a document level. this column is optional.

The username identifier of the user who last updated a record.

The date a record was last updated.

this column holds the freight method associated with the document. this column is optional.

this column holds the id of any reference document that this credit note, credit note request or credit memo applies to.

this column holds the authorization number for the reference rtvs.

this column idicates whether the document has been cost pre-matched. valid values are y and n. documents with y have been cost pre-matched (i.e. cost matched to a po before the receipt is received). documents with n have not been cost pre-matched.

this indicates if the invoice has been detail matched before by auto-match.

this column holds the term determined to be best by the best terms calculation. the best terms calculation runs after an invoice has been matched. the best term is determined by comparing the order and invoice term. the term that has the highest ranking (as defined on the im_terms_ranking table) is determined to be the best term.

this column holds the source of the best terms. when the best terms calculation is performed, the ranking of order and document terms (on the im_terms_ranking table) are compared. the term with the higher ranking is the best term. if the order term is the best term, the best_terms_source will be order. if the document term is the best term, the best_terms_source will be doc.

this column holds the date associated with the best term chosen. this date is the date by which the invoice has to be settled based on the best term.

this column holds the source of the best terms date. if the best terms date is based on the invoice date, this column will contain the string doc. if the best terms date is based on the receipt of goods date, this column will hold the string rog.

this column contains the value (the extended cost) of the variance within tolerance. the variance within tolerance is defined as the difference between the extended cost of the receipts used to match with the invoice and the extended cost of the invoice. if the extended cost of the receipts is greater than the extended cost of the invoice, then the variance will be positive. if this invoice is apart of a match group, then the variance may represent the variance for the entire group of invoices and receipts.

this column will hold the total adjusted merchandise cost for the document. it takes into account any resolution action on the document.

this column will hold the total adjusted quantity for the document. it takes into account any resolution action on the document.

Consignment indicator. Valid values are: N - non-consignment, Y - consignment (self-billed), S - consignment (self-billed), V - consignment (vendor-billed)

the id of supplier deal Oracle Retail target column DEAL_ID on IM_DOC_HEAD.

the return-to-vendor indicator

the expiration date of the discount that can be applied based on the terms of the document.

the type of deal Oracle Retail target column DEAL_TYPE on IM_DOC_HEAD.

this column contains the hold status of the document. based on the supplier option im_supplier_options.hold_invoices, documents can be withheld from the posting process if they are considered to be in held status. valid values are: n - never held, h - currently held, r - previously held, now released, p - released and posted.

Total header cost on the document including any applicable tax amount

The timestamp when a tax discrepancy was created on this document

direct store delivery. default value n.

evaluated receipt settlement. default value n

supplier site id Oracle Retail target column SUPPLIER_SITE_ID on IM_DOC_HEAD.

Indicates if the items in the document are subject to reverse charge VAT at the vat region. Valid values are Y and N.

For a Merch Invoice,absence of details in IM_INVOICE_DETAIL.For a Non Merch Invoice,absence of details in IM_DOC_NON_MERCH.For other types of documents,If fixed deal related,absence of details in IM_FIXED_DEAL_DETAIL.If complex deal related,absence of details in IM_FIXED_DEAL_DETAIL.If non-deal document,absence of details in IM_DOC_DETAIL_REASON_CODES.

The version identifier for a record. Unique for each state of a single record.

This column identifies how the document was created on the system. Valid Values Include 'E'xternal, 'M'anual, 'D'eal and 'R'esolution.

Describes how this document was matched.

Deal component id Oracle Retail target column DEAL_DETAIL_ID on IM_DOC_HEAD.

Reference Credit Note Request vendor document number

Reference Invoice vendor document number

RTV Order Number the document has been created for.

Document gapless sequence number

Document gapless sequence prefix

The sequence group id used for generating the document sequence.

The transmission number for when the document was extracted for eInvoicing.

Oracle Retail target column EXTRACT_TIMESTAMPNTIMESTAMP(6)1176RECEIVING_AUTHORITY on IM_DOC_HEAD.

Third-party payee (supplier is used to identify the payee)

Invoice received date Oracle Retail target column INVOICE_RECEIVED_DATE on IM_DOC_HEAD.

Invoice prepayment date Oracle Retail target column PRE_PAID_DATE on IM_DOC_HEAD.

Fiscal Id Oracle Retail target column FISCAL_ID on IM_DOC_HEAD.

Indicates whether a document is pending fiscal approval. Determines if the doc would be picked up by Posting or EDI Download