This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Order Management
Order HeadersOE_ORDER_HEADERS_ALLHEADER_IDORG_IDORDER_NUMBERORDER_TYPE_ID OE_TRNSACTION_TYPES_ALL.TRANSACTION_TYPE_IDORDER_SOURCE_ID Order Source from OE_ORDER_SOURCES ORIG_SYS_DOCUMENT_REF Quote Number.Version for Sales & Mkting Quote
OE_ORDER_HEADERS_ALL<HEADER_ID> for OMSOURCE_DOCUMENT_ID Order Header ID from which order is CopiedPRICE_LIST_ID OE_PRICE_LISTS.PRICE_LIST_IDORDERED_DATEREQUEST_DATEBOOKED_DATETRANSACTIONAL_CURR_CODECUSTOMER_PO_NUMBER Mandatory id specified in Transaction TypePAYMENT_TERM_ID RA_TERMS.TERM_IDSOLD_TO_ORG_ID CUSTOMER_ID or HZ_CUST_ACCOUNTS.CUST_ACCOUNT_IDSHIP_TO_ORG_ID HZ_CUST_SITE_USES_ALL.SITE_USE_IDINVOICE_TO_ORG_ID HZ_CUST_SITE_USES_ALL.SITE_USE_IDCANCELLED_FLAGOPEN_FLAGBOOKED_FLAGSALESREP_ID JTF_RS_SALESREPS.SALESREP_IDORDER_CATEGORY_CODE ORDER, RETURN, MIXEDFLOW_STATUS_CODE ENTERED, BOOKED, CLOSED, CANCELLED
Order LinesOE_ORDER_LINES_ALLLINE_IDORIG_SYS_DOCUMENT_REF OE_ORDER_HEADERS_ALL50479SOURCE_DOCUMENT_ID 50462ORIG_SYS_LINE_REF OE_ORDER_LINES_ALL59908SOURCE_DOCUMENT_LINE_ID 59893HEADER_IDLINE_TYPE_ID OE_TRNSACTION_TYPES_ALL.TRANSACTION_TYPE_IDLINE_NUMBERORDERED_ITEM MTL_SYSTEM_ITEMS.SEGMENT1REQUEST_DATEPROMISE_DATESCHEDULE_SHIP_DATECANCELLED_QUANTITYSHIPPED_QUANTITYORDERED_QUANTITYINVOICED_QUANITITYSHIP_FROM_ORG_ID WAREHOUSE_ID or INVENTORY ORGANIZATION IDSHIP_TO_ORG_ID HZ_CUST_SITE_USES_ALL.SITE_USE_IDINVOICE_TO_ORG_ID HZ_CUST_SITE_USES_ALL.SITE_USE_IDSOLD_TO_ORG_ID CUSTOMER_ID or HZ_CUST_ACCOUNTS.CUST_ACCOUNT_IDPRICE_LIST_ID QP_LIST_HEADERS_B.PRICE_LIST_IDINVENTORY_ITEM_ID MTL_SYSTEM_ITEMS.INVENTORY_ITEM_IDPAYMENT_TERM_ID RA_TERMS.TERM_IDUNIT_SELLING_PRICE
Order Price Adjustments & Line Price AdjustmentsOE_PRICE_ADJUSTMENTSThis table is used to store price adjustments that have been applied to an order or a line. The column automatic flag indicates if the adjustment was applied automatically or manually. Manual discouts are created with applied_Flag = Y.
Order Sales CreditsOE_SALES_CREDITSSALES_CREDIT_IDHEADER_IDLINE_IDSALES_CREDIT_TYPE_IDQUOTA_FLAGSALESREP_IDPERCENT
Line Sales CreditsOE_SALES_CREDITS
Order Pricing AttributesOE_ORDER_PRICE_ATTRIBSLine Pricing AttributesOE_ORDER_PRICE_ATTRIBS
Order Adjustment AttributesOE_PRICE_ADJ_ATTRIBSLine Adjustment AttributesOE_PRICE_ADJ_ATTRIBS
Order Adjustment AssociationsOE_PRICE_ADJ_ASSOCSLine Adjustment AssociationsOE_PRICE_ADJ_ASSOCS
FROM FND_DOCUMENTS_TL FD ,FND_ATTACHED_DOCUMENTS FAD ,FND_DOCUMENTS_SHORT_TEXT FDST ,OE_ORDER_LINES_ALL OL
WHERE FAD.DOCUMENT_ID = FD.DOCUMENT_ID AND FDST.MEDIA_ID = FD.MEDIA_ID AND OL.LINE_ID = FAD.PK1_VALUE AND OL.LINE_ID = 59851;
Demand:
VISIBLE_DEMAND_FLAG in OE_ORDER_LINES_ALL.
In Order Management Application (Release 11i), Demand Interface is no longer available. Order lines will serve as demand in Order Management Applications. Every line which has the VISIBLE_DEMAND_FLAG = 'Y', will be made available as Demanded to planning. Every line which is Scheduled will be visible to planning as Demanded. So there is no Demand Interface Program, to put the order lines in the demand tables. The table MTL_DEMAND is obsolete. Demand is a process which makes an order line visible to MRP for planning purposes. From Release 11i, Scheduling is an engine owned by MRP. OE_ORDER_LINES will have a flag called VISIBLE_DEMAND_FLAG. If set to 'Yes', the MRP can see the line, if it is set to 'No' the line will just be ignored when performing Planning. When a line is scheduled it becomes visible to MRP, if the VISIBLE_DEMAND_FLAG is set to 'Yes'.
Once the Order is saved, data goes to MTL_SALES_ORDERS table:
MTL_SALES_ORDERS exists for the purpose of mapping sales orders between other applications and Inventory. MTL_SALES_ORDERS is a key flexfield table with no structure defining column or
set defining column. The flexfield code for this table is MKTS. Only one structure for the flexfield may be defined for any installation of Inventory. Inventory demand interface and demand manager will validate sales orders on segment values, and will create a new SALES_ORDER_ID when necessary.
MTL_SALES_ORDERS SALES_ORDER_ID NOT NULL NUMBER SEGMENT1 VARCHAR2 (40) => ORDER_NUMBER SEGMENT2 VARCHAR2 (40) => ORDER_TYPE_ID SEGMENT3 VARCHAR2 (40)
This table stores reservation information. Each record is a reservation that ties an item/organization combination with a demand source and a supply source. Demand source information comprises demand source type (Sales Order, Account, Account Alias, Inventory), demand source header, demand source line and demand source name. Supply source information comprises supply source type (Inventory, WIP jobs), supply source header, supply source line, supply source name and inventory controls (revision, lot, subinventory, locator).
Shipping:
Pick Release:WSH_PICKING_BATCHESThe information filled in the Pick Release form is inserted in this table. System creates one batch for the condition you specify in Pick Release Form. BATCH_IDCUSTOMER_ID HZ_CUST_ACCOUNTS.CUST_ACCOUNT_IDORDER_HEADER_ID
After Pick Release records goes to WSH_DELIVERY_DETAILS for each line, which is picked or backordered. If Autocreate Deliveries is set to set ‘YES’ then record also goes to WHS_NEW_DELIVERIES and WSH_DELIVERY_ASSIGNMENTS but Pick Release is only Reserving the Items against particular Sales Order Line. WSH_DELIVERY_DETAILS:DELIVERY_DETAIL_IDSOURCE_CODE ‘OE’SOURCE_HEADER_NUMBER Order NumberSOURCE_LINE_NUMBERSOURCE_HEADER_ID Order Header IDSOURCE_LINE_ID Order Line IDSOURCE_HEADER_TYPE_ID Order Type IDSOURCE_HEADER_TYPE_NAME Order Type NameCUST_PO_NUMBER Customer PO Number
REQUESTED_QUANTITY The qty. requested for Pick Release. If the program reserves partial qty. then it splits the Lines in the Order and also inserts two lines in WSH_DELIVERY_DETAILS. The qty. available for reservation will be REQUESTED_QUANTITY for First record and balance qty. will be REQUESTED_QUANTITY for other record.
PICKED_QUANTITYSHIPPED_QUANTITY After Ship Confirm Shipped qty. is updatedUNIT_PRICECURRENCY_CODE
N=Not ready for release, R=Ready to release,S=Released to Warehouse, X=Not Applicable, Y=Staged)
Reservations:
MTL_RESERVATIONS
This table stores reservation information. Each record is a reservation that ties and item/organization combination with a demand source and a supply source. Demand source information comprises demand source type (Sales Order, Account, Account Alias, Inventory), demand source header, demand source line and demand source name. Supply source information comprises supply source type (Inventory, WIP jobs), supply source header, supply source line, supply source name and inventory controls (revision, lot, subinventory, locator).
INVENTORY_ITEM_IDORGANIZATION_IDDEMAND_SOURCE_LINE_ID Order Line IDDEMAND_SOURCE_DELIVERYRESERVATION_QUANTITYSUBINVENTORY_CODE
Create Deliveries
After Auto creating the Delivery, records goes to WSH_NEW_DELIVERIES and WSH_DELIVERY_ASSIGNMENTS. If Autocreate Deliveries is set to set ‘YES’ then record goes to both the tables after Pick Release.
WSH_NEW_DELIVERIES: Stores the Delivery Information.
DELIVERY_ID
NAMESTATUS_CODE Delivery shipping status (OP=Open, CL=Closed,
IT= In-Transit)CUSTOMER_IDSHIP_METHOD_CODEDELIVERY_TYPE Type of delivery - STANDARD, CONSOLIDATEDORGANIZATION_ID
WSH_DELIVERY_ASSIGNMENTS: Link between WSH_DELIVERY_DETAILS & WSH_NEW_DELIVERIES. Assigns delivery details to a delivery and/or a parent delivery detail (LPN).DELIVERY_ASSIGNMENT_IDDELIVERY_ID Foreign Key to WSH_NEW_DELIVERIESDELIVERY_DETAIL_ID Foreign key to WSH_DELIVERY_DETAILS
Ship ConfirmAfter Ship Confirm, Deliveries gets Closed i.e. STATUS_CODE in WSH_NEW_DELIVERIES changes to ‘CL’ and CONFIRMED_BY field gets updated with Apps User Name. RELEASE_STATUS in WSH_DELIVERY_DETAILS changes to ‘C’. SHIPPED_QUANTITY in WSH_DELIVERY_DETAILS and SHIPPED_QUANTITY in OL_ORDER_LINES_ALL get updated with quantity shipped.
FROM FND_LOOKUP_VALUES_VL WHERE (nvl('', territory_code) = territory_code or territory_code is null) and (LOOKUP_TYPE LIKE 'SHIP_METHOD') and (VIEW_APPLICATION_ID=3) and (SECURITY_GROUP_ID=0) order by LOOKUP_CODEInventory Interface
Trips:WSH_TRIPSTRIP_IDNAMEPLANNED_FLAG Y if Trip is planned.STATUS_CODE OP - Open, IT - In -transit, CL - ClosedVEHICLE_ITEM_ID MTL_SYSTEM_ITEMS.INVENTORY_ITEM_IDVEHICLE_NUMBERCARRIER_IDSHIP_METHOD_CODEROUTE_IDWSH_TRIP_STOPSSTOP_IDTRIP_ID
Inventory InterfaceInventory Interface puts the Deliveries, which are Closed and Ship Confirmed in
MTL_MATERIAL_TRANSACTIONS_TEMP. Records are processed from this table into Inventory through the transaction processor. MTL_MATERIAL_TRANSACTIONSTRANSACTION_IDTRANSACTION_TYPE_IDTRANSACTION_SOURCE_TYPE_IDTRANSACTION_ACTION_IDINVENTORY_ITEM_IDSUBINVENOTRY_CODETRANSACTION_QUANTITY -ve Qty for Sales Order IssueTRANSACTION_REFERENCE ORDER HEADER IDSOURCE_LINE_ID ORDER LINE IDPICKING_LINE_ID DELIVERY_DETAIL_IDSHIPMENT_NUMBER DELIVERY IDINVOICED_FLAGSOURCE_CODE ORDER ENTRYFREIGHT_CODE SHIP METHOD
Receivables Interface & Data flow from Order Management to Receivables
RA_INTERFACE_LINES_ALL and RA_INTERFACE_SALESCREDITS_ALL
LINE_TYPE For Sales Order Line ‘LINE’For Freight Charges ‘FREIGHT’For Tax ‘TAX’
INTERFACE_LINE_ATTRIBUTE2 Order Type Name INTERFACE_LINE_ATTRIBUTE6 OE_ORDER_LINES.LINE_IDINTERFACE_LINE_ATTRIBUTE10 OE_ORDER_LINES.SHIP_FROM_ORD_IDINTERFACE_LINE_ATTRIBUTE12 OE_ORDER_LINES.shipment_numberINTERFACE_LINE_ATTRIBUTE13 OE_ORDER_LINES.option_numberINTERFACE_LINE_ATTRIBUTE14 OE_ORDER_LINES.service_number
Service Interface & Data flow from OM to Installed Base
PO_REQUISITION_LINES_ALLREQUISITION_LINE_IDREQUISITION_HEADER_IDLINE_NUMUNIT_PRICEQUANTITYITEM_DESCRIPTIONITEM_IDDESTINATION_TYPE_CODE INVENTORY, EXPENSE, SHOP FLOORDESTINATION_ORGANIZATION_IDDESTINATION_SUBINVENTORYDELIVER_TO_LOCATION_ID Internal Location which is attached to
Drop Shipment:Purchase Release inserts the records in Requisition Interface tables. Purchase Release picks the records from OE_ORDER_LINES_ALL for Booked order where SOURCE_TYPE_CODE is ‘EXTERNAL’. After running the Requisition Import (this is automatically run by Workflow Background Process for the Purchase Released Orders) record is inserted in OE_DROP_SHIP_SOURCES and PO_REQUISITION_HEADERS_ALL & PO_REQUISITION_LINES_ALL. Requisition Import Submits new request “Create Releases request” which Releases the Purchase Order i.e. putting the records in PO_HEADERS_ALL and PO_LINES_ALL.
INTERFACE_SOURCE_CODE in PO_REQUISITION_HEADERS_ALL refers to ‘ORDER ENTRY’ and INTERFACE_SOURCE_LINE_ID refers to DROP_SHIP_SOURCE_ID in OE_DROP_SHIP_SOURCES. Also PO_HEADER_ID in PO_HEADERS_ALL and PO_LINE_ID in PO_LINES_ALL is stored in OE_DROP_SHIP_SOURCES creating the Purchase Order from Requisitions. Material can be received on the PO after the PO approval. Records do not directly go to Receipt Table (RCV_SHIPMENT_HEADERS & RCV_SHIPMENT_LINE). Once the PO is approved, record goes to Shipment Schedule table (RCV_LINE_LOCATIONS_ALL). The LINE_LOCATION_ID is the Primary key for this table and it is also stored in OE_DROP_SHIP_SOURCES.After the Receipt of the Material in Logical Organization, 2 records gets inserted in MTL_MATERIAL_TRANSACTIONS. One record is of Receipt of the Material (+ve Qty.) and another record is of Sales Order Issue (-ve entry). The Order line automatically Ship Confirmed after successful receipt of the Material.
OE_ORDER_HEADERS_ALLOE_ORDER_LINES_ALLLINE_IDHEADER_IDORDERED_QUANTITYINVENTORY_ITEM_IDLINE_CATEGORY_CODE ORDERSOURCE_TYPE_CODE EXTERNALSCHEDULE_SHIP_DATESOLD_FROM_ORG_IDPO_REQUISITIONS_INTERFACE_ALLPO_REQUISITION_HEADERS_ALLREQUISITION_HEADER_IDSEGMENT1AUTHORIZATION_STATUSINTERFACE_SOURCE_CODE ORDER ENTRYPO_REQUISITION_LINES_ALLREQUISITION_LINE_IDREQUISITION_HEADER_IDITEM_DESCRIPTION & ITEM_IDUNIT_PRICEQUANTITYSOURCE_TYPE_CODE VENDORNEED_BY_DATE
from po_requisition_headers_all req_h ,po_headers_all ph
,oe_drop_ship_sources od ,oe_order_lines_all ol ,oe_order_headers_all oh
where req_h.interface_source_code = 'ORDER ENTRY' and req_h.interface_source_line_id = od.drop_ship_source_id and od.po_header_id = ph.po_header_id and od.line_id = ol.line_id and ol.header_id = oh.header_id;
Returns:
MTL_SO_RMA_INTERFACE & MTL_SO_RMA_RECEIPTS tables are obsolete. Once the RMA is booked, material can be received on RMA if OE_ORDER_LINES_ALL.BOOKED_FLAG is ‘Y’ and OE_ORDER_LINES_LINES.FLOW_STATUS_CODE is 'AWAITING_RETURN'. Also the Receipts are stored in table RCV_SHIPMENT_HEADERS & RCV_SHIPMENT_LINES.
OE_ORDER_LINES_ALLORDERED_QUANTITYSOLD_TO_ORG_IDSHIP_TO_ORG_IDINVOICE_TO_ORG_IDINVENTORY_ITEM_IDPRICE_LIST_IDLINE_CATEGORY_CODE RETURNRETURN_CONTEXT INVOICE, ORDER, PO,RETURN_ATTRIBUTE1...RETURN_ATTRIBUTE15RETURN_REASON_CODEREFERENCE_HEADER_ID HEADER_ID, which is being returnedREFERENCE_LINE_ID LINE_ID, which is being returnedREFERENCE_CUSTOMER_TRX_LINE_ID
OE_ORDER_LINES_ALLLINE_IDHEADER_IDLINE_TYPE_IDLINE_NUMBERORDERED_QUANTITYINVENTORY_ITEM_IDUNIT_SELLING_PRICEUNIT_LIST_PRICETOP_MODEL_LINE_ID LINE_ID of the Model stored for each line
including for Model that is same LINE_ID.(Identifier of configuration top parent line)
LINK_TO_LINE_ID LINE_ID of the CLASS to which the OPTION is linked. For MODEL it is NULL. (Identifier of immediate parent component line)
COMPONENT_SEQUENCE_ID Bill of materials component (option) or bill (top model)
COMPONENT_CODE Identifier of component within an exploded bill
ITEM_TYPE_CODE MODEL, CLASS, OPTION, CONFIGOPTION_NUMBER Identifier for an option or a class
within a model (1,2,3,4..) 0 for CONFIG.ATO_LINE_ID LINE_ID of the Model stored for each line
including for Model that is same LINE_ID.CONFIG_HEADER_ID System-generated identifier for Oracle
Configurator referenceCONFIG_REV_NBR System-generated identifier for Oracle
Price Lists:QP_LIST_HEADERS_BThis table stores the header information for all lists. List types can be, for example, Price Lists, Discount.LIST_HEADER_IDCURRENCY_CODEROUNDING_FACTORLIST_TYPE_CODE Price list = PRL, Promotion = PROPARENT_LIST_HEADER_ID
ACTIVE_FLAG QP_LIST_HEADERS_TLThis table stores the translatable columns, name and description of the list, in each of the available languages in the database. LIST_HEADER_IDNAMEDESCRIPTIONQP_LIST_LINESThis table stores all list lines for lists in QP_LIST_HEADERS_B.LIST_LINE_IDLIST_HEADER_IDLIST_LINE_TYPE_CODELIST_PRICELIST_PRICE_UOM_CODEINVENTORY_ITEM_IDORGANIZATION_ID
Interfaces (Import Orders):The Sales Order has been modeled as a business object that Oracle Order Management owns. The Sales Order business object comprises of several entities, namely, Header, Header Sales Credits, Header Price Adjustments, Header Pricing Attributes, Header Adjustment Attributes, Header Adjustment Associations, Lines, Line Sales Credits, Line Price Adjustments, Line Pricing Attributes, Line Adjustment Attributes, Line Adjustment Associations and Line Lot Serial Numbers.
Order Import can import new, change, and completed sales orders or returns from other applications such as a legacy system. The orders may come from any source such as EDI transactions that are processed by the Oracle e-Commerce Gateway or internal orders created for internal requisitions developed in Oracle Purchasing or returns.
Order Import features include validation and defaulting, processing constraint checks, applying and releasing of order holds, scheduling of shipments, then ultimately inserting, updating or deleting the orders in the base Order Management tables. Order Management checks all the data during the import process to ensure its validity within Order Management. Valid transactions are then converted into orders with lines, reservations, price adjustments, and sales credits in the base Order Management tables.
You can setup your defaulting rules which allow you to default columns in the same way as for orders entered online. You can pass the column value Null to Order Import if you want the defaulting rules to populate the column. However, if the column is defined as Not Null or Mandatory column and the defaulting rules fail to default the column, for any reason, Order Import displays an error message without importing the order.
Import Types:
ConfigurationsOrder Management provides you with the ability to import ATO and PTO configurations.
ChangesYou can import changes to orders that have been imported by passing all changed data through Order Import. You can update or delete orders, order lines, price adjustments, and sales credits. You can use change sequence numbers to control the sequence of changes you want to make to orders.
Order StatusYou can import new, booked or closed orders. If an order is imported with an entry status of Booked (OE_HEADERS_IFACE_ALL.BOOKED_FLAG=Y) the result after import is that a Action Request of BOOK_ORDER is initiated. You may also pass the Action Request to BOOK_ORDER; both methods are supported.
WorkflowsYou can import an order within any valid order workflow activity. The order must be at the initial activity of Entered, Booked, or Closed. Orders imported using Order Import cannot be in the middle of a workflow activity.
Manual and Automatic PricingPricing in process order API can be controlled using flag calculate_price_flag on order line record. When set to ‘Y ‘the process order API fetches the list price and applies adjustments and charges. When set to N, the process order API would fetch a list price if the list price is not passed and no adjustments would be applied. When set to P, all the modifiers which are associated with phases having override freeze flag set to Y are applied. That mainly includes freight charges.
SchedulingOrder Import allows you to reserve orders as they are imported, using the same rules as online order entry. If the scheduling request is unsuccessful on an imported order, the order will still be imported, and the scheduling exceptions can be viewed in the Error Messages of the Order Import Corrections window. You can use Schedule, Unschedule, Reserve or Unreserve as values for scheduling actions.
Return LinesProcess order can be used to create and update return lines also. To create a return line, you can either pass in the line category of RETURN on the order line record and the line type would default to the inbound line type of the order type. Alternatively, you can also provide a line type of the type Return on the order line record. Additionally, if you want to specify a reference for the return line, you can pass in the return flexfields (return_context, return_attribute1-2). Column Return_Context can have the following values to determine the referencetype:
Sales OrderCustomer POInvoiceSerial Number
Process Order Application Open Interface Return_Attribute1... Return_Attribute2 can have the following values depending on the reference type:
1. Sales Orderreturn_Attribute1: Header ID
return_Attribute2: Line ID2. Customer PO
return_Attribute1: Header IDreturn_Attribute2: Line ID
3. Invoicereturn_Attribute1: Invoice Header IDreturn_Attribute2: Invoice Line ID
4. Serial Numberreturn_Attribute1: Inventory Item IDreturn_Attribute2: Serial Number
If you wish to import an order as booked, you must set the OPERATION_CODE column in the actions interface table OE_ACTIONS_IFACE_ALL with a value of "BOOK_ORDER". Do not use the BOOKED_FLAG column in the OE_HEADERS_IFACE_ALL table. This will cause the order header to show as booked, but not the order lines. The order lines will not progress through workflow to the Pick Release/Shipping actions.
WHERE OH.ORDER_TYPE_ID = OTTA.TRANSACTION_TYPE_ID AND OTTA.TRANSACTION_TYPE_ID = OTTL.TRANSACTION_TYPE_ID AND order_number = 1130100008;
OE_WORKFLOW_ASSIGNMENTSThis table associates assignments to order types and line types.ORDER_TYPE_IDLINE_TYPE_IDPROCESS_NAMEASSIGNMENT_ID
Document SequenceFor Document Sequence record stores in FND_DOCUMENT_SEQUENCES. After creating the Transaction Type, automatically the Document Category gets created and record goes to table FND_DOCUMENT_CATEGORIES. FND_DOCUMENT_SEQUENCESDOCUMENT_SEQUENCE_IDNAMEINITIAL_VALUETABLE_NAME OE_TRANSACTION_TYPES_ALLFND_DOCUMENT_CATEGORIESAPPLICATION_IDCODENAME TRANSACTION TYPE NAMEDESCRIPTIONTABLE_NAME OE_TRANSACTION_TYPES_ALLFND_DOCUMENT_CATEGORIESDOC_SEQUENCE_ASSIGNMENT_IDAPPLICATION_IDDOCUMENT_SEQUENCE_IDCATEGORY_IDSET_OF_BOOKS_ID
Order Import SourcesOE_ORDER_SOURCESORDER_SOURCE_IDNAMEDESCRIPTIONENABLED_FLAG
HoldsOE_ORDER_HOLDS_ALL This table stores information of all the orders and lines that are on hold and the link to hold sources and hold releases.HOLD_SOURCE_IDHEADER_IDLINE_IDORG_IDRELEASED_FLAG
OE_HOLD_AUTHORIZATIONS Stores information about who has the authority to apply and release holds.– Retrofitted OE_HOLD_DEFINITIONS This table stores information about hold name and its validity period. OE_HOLD_RELEASES This tables stores information about all the holds that has been released.
WHERE CR.SALESREP_ID = SREP.SALESREP_ID AND CR.HEADER_ID = OH.HEADER_ID AND OH.ORG_ID = SREP.ORG_ID AND CR_TYPE.SALES_CREDIT_TYPE_ID = CR.SALES_CREDIT_TYPE_ID AND OH.ORDER_NUMBER = 1130100005;
Profiles
Credit Check RulesOE_CREDIT_CHECK_RULES This table stores information about the credit check rules.
Pricing QP_ATTRIBUTE_DEFNS QP_ATTRIBUTE_DEFNS is the table on which the Qualifierand Pricing Attribute Descriptive Flexfields are based. It is used for the entity and attribute definiton in attribute sourcing. QP_COUPONS QP_COUPONS stores any Coupons which have been issued. QP_EVENT_PHASES QP_EVENT_PHASES stores the mapping between pricing events and pricing phases. QP_LIST_HEADERS_B QP_LIST_HEADERS_B stores the header information for all lists. List types can be, for example, Price Lists, Discount QP_LIST_HEADERS_TL QP_LIST_HEADERS_TL stores the translatable columns, name and description of the list, in each of the available languages in the database. QP_LIST_LINES QP_LIST_LINES stores all list lines for lists in QP_LIST_HEADERS_B. QP_PRICE_FORMULAS_B QP_PRICE_FORMULAS_B stores the pricing formula header information. QP_PRICE_FORMULAS_TL This table stores the translatable columns, name & description of the pricing formulas, in each of the available languages in the database. QP_PRICE_FORMULA_LINES QP_PRICE_FORMULA_LINES stores each component that makes up the formula. QP_PRICE_REQ_SOURCES QP_PRICE_REQ_SOURCES stores the mapping between Pricing Request Types and Source Systems.
QP_PRICING_ATTRIBUTES QP_PRICING_ATTRIBUTES stores product information and pricing attributes.QP_PRICING_PHASES QP_PRICING_PHASES stores all pricing phases. QP_QUALIFIERS QP_QUALIFIERS stores qualifier attribute information. QP_QUALIFIER_RULES QP_QUALIFIER_RULES stores the header information for all qualifier rules QP_RLTD_MODIFIERS QP_RLTD_MODIFIERS stores the relationship between modifier lines. QP_UPGRADE_ERRORS QP_UPGRADE_ERRORS holds details of the errors which occured in upgrading pricing data.