R12: AP: Invoice Ship To Is Populated From PO Header Instead From PO Shipments. (Doc ID 1465653.1)

Last updated on AUGUST 11, 2022

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
System defaults 'Ship to Location code' value from supplier site instead of PO shipments while importing PO matched invoice without providing the 'Ship to Location code' value in import tables.

EXPECTED BEHAVIOR
-----------------------
System defaults 'Ship to Location code' value from PO shipments instead of supplier site while importing PO matched invoice without providing the 'Ship to Location code' value in import tables.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Create a new PO for testing.
   1. Using Purchasing responsibility
   2. Create PO (PO 1122333) with the following attributes:
      
      • Supplier = XXSUPPXX
      • Site = XXSITEXX
      • Ship-To = Change it to 'XXSHIPTOPOHXX'
   3. Create Line with:
      • Type = Goods
      • Quantity = 10, Price = 100
   4. Create Shipment with:
      • Ship-To originally was 'XX'. Change it to 'XXSHIPTOLOCXX'
      • Click on the 'More' tab, change Invoice Match Option to PO
      • Click on 'Distribution' tab, enter PO Charge Account = 01-002-0004-0005-006
2. Approve the PO
3. Change to 'Payables' responsibility
4. Import a New Invoice Matched to PO 1122333
5. Verify ship_to_location_code of Invoice created via SQL*Plus.
   Notice the Invoice has ship-To-Location-Code 'XXSHIPTOPOHXX' which is the value used when creating the PO header. 

  
  
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot default correct ship to location id.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.