Procurement and Spend

This section lists the upgrade changes after 11.1.1.9.2 to 11.1.110.1 upgrade.

Purchase Requisition

Following are the upgrade changes:
  1. Tables truncated and reloaded:
    • W_PURCH_RQSTN_LINE_F (only if any release of PSFT or JDE is used as a source adaptor)

    • W_RQSTN_LINE_COST_F (only if any release of PSFT or JDE is used as a source adaptor)

  2. Tables with records updated:

    Fusion9 (On Premises)
    • W_PURCH_RQSTN_LINE_F: FULFILLMENT_STATUS_WID

    EBS (any release)
    • W_PURCH_RQSTN_LINE_F: FULFILLMENT_STATUS_WID, FULFILLED_ON_DT, FULFILLED_ON_DT_WID

    • W_RQSTN_LINE_COST_F: FULFILLED_ON_DT_WID

  3. New features introduced:

    FUSION9 (On Premises)
    • Modified Requisition Fulfillment Status to support the purchase process for consigned inventory item.

    EBS (any release)
    • Modified Requisition Fulfillment Status and Requisition Fulfillment Date to support the purchase process for consigned inventory item.

  4. Issues and bug fixes covered:
    • PSFT (any release)

      Bug 20217859: Fixed to have W_RQSTN_LINE_COST_FS.LINE_AMT populated from the amount value of Requisition Distribution Table

      Bug 21387777: Fixed to remove the possibility to filter out some requisition lines, which have inactive vendor location, when loading W_PURCH_RQSTN_LINE_F.

    • JDE (only if MSSQL is used for JDE DB, any JDE release)

      Bug 20178756: Fixed to remove the possibility of causing duplicate records and unresolved dim WIDs in W_PURCH_RQSTN_LINE_F and W_RQSTN_LINE_COST_F, when MSSQL is used for JDE DB.

Purchase Agreement

Following are the upgrade changes:
  1. Tables with records updated:

    Fusion9 (On Premises)

    • W_PURCH_AGREEMENT_LINE_F: CONSIGNED_AGRMNT_LINE_FLG

  2. Tables with data model changes:
    • New column added in W_PURCH_AGREEMENT_LINE_F: CONSIGNED_AGRMNT_LINE_FLG (used for only FUSION adaptors)

  3. Dimension Attributes calculated differently (RPD calculation-wise) or added newly

    Presentation level:
    • Consigned Agreement Line Flag: located under "Procurement and Spend - Purchase Agreement"."Agreement Details".

  4. New features introduced:

    FUSION9 (On Premises)
    • Introduced "Consigned Agreement Line Flag" to indicate if an agreement was created as a part of the purchase process for consigned inventory item.

Purchase Order

Following are the upgrade changes:
  1. Tables with records added:
    • W_XACT_TYPE_D (records with W_XACT_CODE='PO_CONSIGNED_TYPE' only if any release of FUSION is used as a source adaptor)

    • W_DOMAIN_MEMBER_G (records with DOMAIN_CODE='PO_CONSIGNED_TYPE', or 'W_XACT_TYPE_PO_CONSIGNED ')

    • W_DOMAIN_MEMBER_MAP_G (records with SRC_DOMAIN_CODE='PO_CONSIGNED_TYPE')

  2. Tables with records updated:

    Fusion9 (On Premises):
    • W_PURCH_SCHEDULE_LINE_F: CONSIGNED_TYPE_WID

    • W_PURCH_COST_FS: CONSIGNED_TYPE_WID

    EBS (any release):
    • W_PURCH_SCHEDULE_LINE_F: FULFILLED_ON_DT

    • W_PURCH_COST_FS: FULFILLED_ON_DT

  3. Dimension Attributes calculated differently (RPD calculation-wise) or added newly:

    Logical level:
    • "Dim - Purchase Order Consigned Type"." Source Id"

    • "Dim - Purchase Order Consigned Type"." Source PO Consigned Transaction Type Description"

    • "Dim - Purchase Order Consigned Type"." PO Consigned Transaction Type Desc"

  4. New features introduced:

    FUSION9 (On Premises):
    • Modified "Consigned Type" dimension to support the purchase process for consigned inventory item.

    EBS (On Premises):
    • Modified "Fulfilled Date" to populate the closed date for receipt to "Fulfilled Date" for Consignment Order Schedule

Purchase Receipt

Following are the upgrade changes:
  1. Tables with records updated:

    Fusion9 (On Premises) :
    • W_PURCH_RCPT_F: CONSIGNED_TYPE_WID

  2. New features introduced:

    Fusion9 (On Premises):
    • Modified FK column to "Consigned Type" dimension to support the purchase process for consigned inventory item. But, 'Consigned Type' dimension is not exposed to Presentation Layer for Receipt subject area, so there is no feature change in OOTB(out of the box) setting.

Employee Expense

Following are the upgrade changes:
  1. Tables truncated and reloaded:
    • W_EXPENSE_F (only if any release of EBS or PSFT is used as a source adaptor)

    • W_EXPENSE_CC_F (only if any release of EBS or PSFT is used as a source adaptor)

    • W_EXPENSE_VIOLATION_F (only if any release of PSFT is used as a source adaptor)

  2. Issues and bug fixes covered:

    EBS (any release):
    • Bug 20045515: Fixed the issue that RQSTN_AMT and PREPAYMENT_AMT of W_EXPENSE_F are 100 times bigger than the actual amount. (applicable to only EBS R12 and above release).

    • Bug 19903729: Modified EXPENSE_INVOICE_POSTED_DT of W_EXPENSE_F to have the correct expense payment date.

    • Bug 20540645: Fixed to remove the possibility of marking DELETE_FLG='Y' for records which were loaded in the previous load, but not updated in this load, if a customer enabled Soft Delete feature using Soft Delete Preprocess.

    • Bug 20345879: Fixed EXPENSE_STATUS_ID/WID columns of W_EXPENSE_F to make expense status 'CANCELLED' when the corresponding invoice is cancelled.

    • Bug 21092558: Fixed ETL calculation logic for document currency, ledger currency, exchange rate, and any amount columns of W_EXPENSE_F and W_EXPENSE_CC_F, so that ultimately all amount metrics of Employee Expense and Employee Expense Credit Card subject areas shows correct values in correct currency code.

    PSFT (any release):
    • Bug 21356472: Fixed the wrong ETL logic for INTEGRATION_ID of W_EXPENSE_F, W_EXPENSE_CC_F, and W_EXPENSE_VIOLATION_F.

    • Bug 21419177: Fixed INTEGRATION_ID of W_EXPENSE_CC_F_PE to add missing ITEM_SEQ_NBR, so that it prevents W_EXPENSE_CC_F records from being marked with DELETE_FLAG =Y , if a customer enabled Soft Delete feature using Soft Delete Preprocess.

    • Bug 21438832: Fixed to remove CDC filter in Expense Violation Primary ODI mapping, so that it prevents W_EXPENSE_VIOLATION_F records from being marked with DELETE_FLAG =Y , if a customer enabled Soft Delete feature using Soft Delete Preprocess.

    • Bug 21439668: Fixed the wrong target table of Expense Violation Primary ODI mapping, so that it prevents W_EXPENSE_F and W_EXPENSE_VIOLATION_F records from being marked with DELETE_FLAG =Y table, if a customer enabled Soft Delete feature using Soft Delete Preprocess.

    • Bug 21316779: Fixed to handle spaces in PSFT business unit column when populating INTEGRATION_ID of W_EXPENSE_F_PE, so that it prevents W_EXPENSE_F records from being marked with DELETE_FLAG =Y, if a customer enabled Soft Delete feature using Soft Delete Preprocess.