===========================================================================
PROBLEM DESCRIPTION
===========================================================================
** DESCRIPTION OF PROBLEM, INCLUDING ALL ERRORS:
There is no column that accepts the value for match_option (invoice
matching 'P'or'R') in PO_LINES_INTERFACE. (The enhanced PDOI now supports
standard PO import.) If there is a method to populate the matching
option value via the PDOI, it should be documented in the PDOI update
release note. "matching option" is stored in the following table in EBS.
PO_LINE_LOCATIONS_ALL.MATCH_OPTION
===========================================================================
ADDITIONAL DETAILS
===========================================================================
** TAR NUMBER (ALSO ENSURE BUG NUMBER FIELD IS UPDATED IN TAR):
** LIST ADDITIONAL DOCUMENTATION AVAILABLE (LOG FILE, REPORT, TRACE, ETC.):
N/A
** HOW WILL DEVELOPMENT RECEIVE THE ADDITIONAL DOCUMENTATION?:
Via Email or ess30 upon request.
** DESCRIBE ANY WORKAROUND(S) AVAILABLE TO THE CUSTOMER:
Open POXPOEPO and update the option for all imported POs, which is rediculous.
** LIST NAME & VERSION OF ALL MODULES INVOLVED (FORM,REPORT,PACKAGE,ETC.):
EBS 11.5.3
Please ask if you need specific file versions.
** IS THE PROBLEM OCCURRING IN TEST OR PRODUCTION?
Production.
** DOES THE CUSTOMER HAVE ANY CUSTOMIZATIONS OR 3RD PARTY PRODUCTS?
No.
===========================================================================
HISTORY
===========================================================================
** WAS THE CUSTOMER ABLE TO COMPLETE THE SAME PROCESS PREVIOUSLY?:
No.
** LIST PATCHES APPLIED RECENTLY WHICH COULD AFFECT THIS PROBLEM:
N/ADefaulting of match_option is as follows
1. From Supplier Site
2. From Supplier
3. From Financials System Parameters
The HLD for STD PO do not mention anything about this column.
Will be an ER to create the column in CASE and to add the necessary
validations.PREMCOR REFINING GROUP is requesting this ER be changed to a priority 3 bug so
a fix can be included in a future PO Family Pack. They have 100's of PO's
that they import from a 3rd party system (Maximo) using the PDOI. These
multi-line POs are primarily Service Type POs and whether the line can either
be Invoice Match Option to Receipt or Invoice Match Option to Purchase Order
needs to be controlled at the Line level when inserting into the PO Interface
tables.
Here is the solution for the invoice matching, someone needs to update the
bug to include this solution:
Invoice matching, populate the following columns in PO_LINES_INTERFACE table:
'2WAY' inspection_required_flag = 'N'
receipt_required_flag = 'N'
'3WAY' inspection_required_flag = 'N'
receipt_required_flag = 'Y'
'4WAY' inspection_required_flag = 'Y'
receipt_required_flag = 'Y'
Bug 1930586: MATCH_OPTION COLUMN/METHOD MISSING IN PDOI
Latest Posts
- R12 – How to Handle NULL for :$FLEX$.VALUE_SET_NAME In Oracle ERPAugust 25, 2023 - 1:20 pm
- R12 – How to Delete Oracle AR TransactionsMarch 22, 2019 - 8:37 pm
- How to Define Custom Key Flexfield (KFF) in R12January 19, 2018 - 5:43 pm
- AutoLock Box Concepts In R12November 10, 2017 - 8:30 am
- R12 – java.sql.SQLException: Invalid column type in OAFSeptember 15, 2017 - 9:39 am
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 | 31 |
Recent Comments