Oracle Business Intelligence Applications ships default domain value mappings that map the seeded Oracle BI Application domain values to the seeded configuration data in Oracle Procurement and Spend Analytics applications.
Manage Domains and Member Mappings for Purchase Order Status for JD Edwards
The Purchase Order types are configured using the FSM parameter JDE_PURCHASING_ORDER_TYPE_LIST. The default value for this parameter is OP, O4, OS, OD.
When you configure the above parameter to include any other Purchase Order types, you need to review the default mappings for domain values PURCHASE_ORDER_STATUS and the corresponding target domains W_PURCHASE_ORDER_CYCLE_STATUS and W_PURCHASE_ORDER_APPROVAL_STATUS, and if necessary update them to accommodate the mappings for the new purchase order types.
In Oracle Procurement and Spend Analytics, the domain member values for PURCHASE_ORDER_STATUS are Purchase Order type~ Line Status~Next Status.
For example: OP~220~240, OP~282~300
If you want to use the default purchase order types as per JDE_PURCHASING_ORDER_TYPE_LIST, then you do not need to make any changes to these domain mappings before you start your ETL processes.
If new order types are added to JDE_PURCHASING_ORDER_TYPE_LIST, then you must add the new domain members for PURCHASE_ORDER_STATUS. Next you will have to make changes to default mappings, using the Domain Mappings tab.
Manage Domains and Member Mappings for Purchase Order Document Subtypes for JD Edwards
Oracle Business Intelligence Applications ships default domain value mappings that map the seeded Oracle BI Application domain values to the seeded configuration data in Oracle Procurement and Spend Analytics applications. The default value for this parameter is OP, O4, OS, OD, OB, C, E, L, N, S, and T.
OP, O4, OS, OD are configured in JDE_PURCHASING_ORDER_TYPE_LIST FSM parameter and the rest OB, C, E, L, N, S, and T are configured in JDE_PO_AGREE_STANDARD_TYPE_LIST.
Manage Domains and Member Mappings for Purchase Order Shipment Type for JD Edwards
Oracle Business Intelligence Applications ships default domain value mappings that map the seeded Oracle BI Application domain values to the seeded configuration data in Oracle Procurement and Spend Analytics applications. The order which is released against any blanket, quotation etc. is considered for mapping of this configuration. The default value for this parameter is OB, OQ and STD.
FSM Parameters:
Configure these parameters:
JDE_PURCHASING_CANCELED_STATUS_CODE_LIST
The Purchase Order Cancelled Status Codes are configured using the FSM parameter. All the PO status codes which correspond to cancelled status are listed as values for this parameter. (When entering values in seed manager, remove quotes and spaces). In addition, you can edit the defaults for this parameter for the associated Fact Groups. For example, the default value for this parameter is 980,982,983,984,985,986,987,988,989 for Purchase Orders ETL tasks. However the default values list are 499,980,981,982,983,984,985,986,987,988,989,990,991 for Purchase Requisition ETL tasks.
JDE_PURCHASING_ORDER_TYPE_LIST
The Purchase Order types are configured using the FSM parameter JDE_PURCHASING_ORDER_TYPE_LIST. Default value for this parameter is OP, O4, OS, and OD. In addition, you can the defaults for this parameter for the associated Fact Groups. When you configure the above parameter to include any other Purchase Order types, you need to review/edit the default mappings for domain values PURCHASE_ORDER_STATUS and the corresponding target domains W_PURCHASE_ORDER_CYCLE_STATUS and W_PURCHASE_ORDER_APPROVAL_STATUS.
JDE_REQ_ORDER_TYPE_LIST
The Purchase Requisition document types are configured using the FSM parameter JDE_REQ_ORDER_TYPE_LIST. The default value for this parameter is OU, OR.
JDE_PO_QUOTE_TYPE
'Quote' type purchase order are used in deriving shipment type of purchase order. JDE_PO_QUOTE_TYPE is configured with the Quote types. Default value for this parameter is OQ.
JDE_PON_BID_QTN_PRICE_TYPE
Price types in Bid Questions are configured using the FSM parameter, JDE_PON_BID_QTN_PRICE_TYPE. The default value is P.
JDE_PON_RFI_TYPE
Sourcing RFI document types are configured using the FSM parameter, JDE_PON_RFI_TYPE. The default value is RF.
JDE_RCPT_LINE_TYPE
Freight line are not considered in the receipt fact. This is configured using the FSM parameter JDE_RCPT_LINE_TYPE. Default values is F.
JDE_PO_AGREE_BLOCKED_STATUS_CODE
The Purchase Agreement Blocked Status Code is configured using the parameter JDE_PO_AGREE_BLOCKED_STATUS_CODE. Default value for this parameter is 210.
JDE_PO_AGREE_BLANKET_TYPE
The Purchase Blanket Agreement type is configured using the parameter JDE_PO_AGREE_BLANKET_TYPE. Default value for this parameter is OB.
If you make changes to the default values of this parameter, then you need to review/edit the default mappings for domain values for the PO_DOCUMENT_TYPES and its corresponding target domain W_XACT_TYPE_PO_DOCUMENT_TYPES using the Domain Mappings tab.
JDE_PO_AGREE_STANDARD_TYPE_LIST
The Purchase Standard Agreement type is configured using the parameter JDE_PO_AGREE_STANDARD_TYPE_LIST. Default value for this parameter is C, E, L, N, P, S, T.
If you make changes to the default values of this parameter, then you need to review/edit the default mappings for domain values for the PO_DOCUMENT_TYPES and its corresponding target domain W_XACT_TYPE_PO_DOCUMENT_TYPES using the Domain Mappings tab.