AP Supplier Inquiry Form

Embed Size (px)

DESCRIPTION

AP Supplier Inquiry is allowing to create new supplier

Citation preview

  • PowerView is Off

    In this Document

    Symptoms

    Cause

    Solution

    References

    APPLIES TO:

    Oracle Payables - Version 12.0.0 and later Oracle Payments - Version 12.0.0 and later Information in this document applies to any platform.

    SYMPTOMS

    Created a Supplier Inquiry Responsibility using the steps detailed in Note:473346.1Excluded function Supplier Full Access: Buyer View (POS_HT_SP_ACCESS_FULL) from responsibilityStill able to create and update supplier banking details

    Expected Behavior Users should not be able to Update any attributes from Responsibility with Supplier Full Access: Buyer View listed as an Excluded function. Steps to Reproduce 1. Create a Custom Responsibility same as Payables Responsibility to serve as a Supplier Inquiry responsibility. 2. Exclude function Supplier Full Access: Buyer View (POS_HT_SP_ACCESS_FULL) from responsibility 3. Navigate to Supplier >Inquiry >Query Supplier >Click on Banking Details >End Date can be updated 4. Click on Banking Details >Additional Details > When you click on Pencil Icon "Additional Detail" can be updated5. Click on Banking Details > Click Account Number Link > It shows Account button on Next page, and when click on Update Account it has Apply ButtonEnable 6. Go to Address Book > Manage Sites >Identification Tab >Attachments > Add button '+' is Enable When you Click on clip to view attachment > Update and Delete button are Enable on View Attachment Page

    CAUSE

    This is explained in following bugs: Bug 8825795 - seeded supplier inquiry form allows updates to tax registration details Bug 9502876 - can update few attributes in payables inquiry responsibility Bug 9569041 - iby changes required for bug 9502876 Bug 9721354 - bug 9502876 still able to update some fields from supplier inquiry responsibility Bug 9801179 - able to add products & services from supplier inquiry responsibility Bug 11658267 - supplier inquiry fix still allows update on relationship tab

    R12: Still Able to Update Supplier Banking Data From Supplier Inquiry Responsibility with Excluded Function Supplier Full Access: Buyer View (Doc ID 1089925.1)

    Modified: Aug 10, 2012 Type: PROBLEM

    Dashboard Service Requests Patches & Updates CommunityKnowledge

    Page 1 of 4Document 1089925.1

    6/23/2014https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=193045894547880&i...

  • SOLUTION

    To implement the solution, please execute the following steps: 1. Please download and review the readme and pre-requisites for the following patches: For R12.0.x: Patch 9502876:R12.POS.A: This patch resolves the issue of "In iSupplier user can update few attributes in payables inquiry responsibility"Patch 9721354:R12.POS.A: In Oracle iSupplier Portal, this patch resolves the issue of pages becoming editable in read only mode after clicking survey link Patch 9056630:R12.POS.A: This patch resolves the issue "Product and Services is throwing an ORA Error" Patch 8825795:R12.POS.A: This patch resolves the issue "Tax details can be updated from Supplier Inquiry" For R12.1.x: Patch 9502876:R12.POS.B: This patch resolves the issue of "In iSupplier user can update few attributes in payables inquiry responsibility"Patch 9721354:R12.POS.B: In Oracle iSupplier Portal, this patch resolves the issue of pages becoming editable in read only mode after clicking survey link Patch 9056630:R12.POS.B: R12- SUPPLIER PRODUCTS & SERVICES LINK ORA-20013 APPS.POS_PRODUCT_SERVICE_UTL_PK Patch 8825795:R12.POS.B: This patch resolves the issue "Tax details can be updated from Supplier Inquiry" Patch 11658267:R12.IBY.B: SUPPLIER INQUIRY FIX STILL ALLOWS UPDATE ON RELATIONSHIP TAB

    Patch 9056630:R12.POS.B and Patch 11658267:R12.IBY.B requires password to download. Please log a Service Request with

    2. Ensure that you have taken a backup of your system before applying the recommended patch. 3. Apply the patch in a test environment. 4. Confirm the following file versions: For 12.0: java/supplier/webui/ByrMngSitesCO.class 120.19.12000000.13 java/supplier/webui/AddrIntvCO.class 120.0.12000000.2 pos patch/115/import/US posmenu.ldt 120.1.12000000.2 pos java/survey/webui SurveysCO.java 120.8.12000000.3 patch/115/sql/POSPSUTB.pls 120.5.12000000.16 java/supplier/webui/ByrTaxDtCO.java 120.27.12000000.10 For 12.1: pos java/survey/webui SurveysCO.java 120.9.12010000.2 pos patch/115/import/US posmenu.ldt 120.1.12010000.32 java/supplier/webui/ByrMngSitesCO.class 120.22.12010000.10 java/supplier/webui/AddrIntvCO.class 120.0.12010000.2 java/supplier/webui/ByrTaxDtCO.java 120.31.12010000.4 patch/115/sql/POSPSUTB.pls 120.5.12010000.16 You can use the commands like the following: strings -a $XX_TOP/filename |grep '$Header' 4. Stop all Application Services on the Instance 5. Regenerate all Jar Files using adadmin Utility

    Page 2 of 4Document 1089925.1

    6/23/2014https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=193045894547880&i...

  • 6. Clear Cache 7. Restart Application Services on the Instance 8. Please retest the issue. 9. If the issue is resolved, please migrate the solution as appropriate to other environments. Note: If supplier bank accounts can still be updated in inquiry responsibility, even after these patches, follow the personalization

    instructions in Note:1328525.1 to remove the update button.

    Note:If you are creating Custom Responsibility then you need to add Supplier Information Management(Buyer View) menuin order to Exclude function Supplier Full Access.

    Important: Whilst a patch may contain several hundred files the impact in your system is most likely far less. Patches contain hardintended to make a patch work on a very low code baseline. The Patch Wizard Utility will give you a detailed impact analysis for the patch above, please refer to the Note 976188.1

    Please consult as well the recommended patch lists for Payables, the list includes consolidated patches that contain fixes for issues For the 12.0.x codeline Note 557869.1 For the 12.1.x codeline Note 954704.1

    Join our growing Oracle Payables Community and learn from your peers and Oracle on how to address your unique issues in

    REFERENCES

    BUG:11658267 - SUPPLIER INQUIRY FIX STILL ALLOWS UPDATE ON RELATIONSHIP TAB BUG:8825795 - SEEDED SUPPLIER INQUIRY FORM ALLOWS UPDATES TO TAX REGISTRATION DETAILS BUG:9502876 - CAN UPDATE FEW ATTRIBUTES IN PAYABLES INQUIRY RESPONSIBILITY BUG:9569041 - UNABLE TO RESTRICT UPDATE BANK ACCOUNT DETAILS AT SUPPLIER SITE LEVEL BUG:9721354 - BUG9502876 STILL ABLE TO UPDATE SOME FIELDS FROM SUPPLIER INQUIRY RESPONSIBILITYBUG:9801179 - ABLE TO ADD PRODUCTS & SERVICES FROM SUPPLIER INQUIRY RESPONSIBILITY NOTE:1089925.1 - R12: Still Able to Update Supplier Banking Data From Supplier Inquiry Responsibility with Excluded FunctionView NOTE:1328525.1 - R12: Still Able Update The Supplier Bank Account After Patching As Advised in Note:1089925.1NOTE:473346.1 - R12: How Can You Prevent Suppliers From Being Created in Supplier Inquiry NOTE:557869.1 - EBS: R12.0 ORACLE FINANCIALS CRITICAL AND RECOMMENDED PATCHES NOTE:954704.1 - EBS: R12.1 Oracle Financials Recommended Patches NOTE:976188.1 - Patch Wizard Utility

    Related

    Products

    Page 3 of 4Document 1089925.1

    6/23/2014https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=193045894547880&i...

  • Oracle E-Business Suite > Financial Management > Procure to Pay > Oracle PayablesOracle E-Business Suite > Financial Management > Procure to Pay > Oracle Payments > FD Core

    Keywords

    ACCOUNT NUMBER; ADDRESS BOOK; BANK ACCOUNT; CHANGE; CUSTOM RESPONSIBILITY; DYNAMIC ADV SUPP BANK; INQUIRIESRESPONSIBILITY; SUPPLIER; SUPPLIER BANK ACCOUNT

    Errors

    ORA-20013

    Back to Top

    Copyright (c) 2014, Oracle. All rights reserved.

    Legal Notices and Terms of Use

    Privacy Statement

    Page 4 of 4Document 1089925.1

    6/23/2014https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=193045894547880&i...