Monday Feb 10, 2014

Urgent! Change in the HTTP Proxy Service Used for OSN - Oracle Supplier Network Starting February 16th

Oracle Supplier Network currently uses the HTTP Proxy service - www-proxy.oracleoutsourcing.com - for document delivery.  The proxy service is due to be decommissioned on 16th Feb 2014 at 10:00 AM GMT and a new proxy service hosted by Oracle Managed Cloud Services - omcs-proxy.oracleoutsourcing.com - will be used instead.

What does this mean for Oracle Supplier Network customers?

Outbound requests from Oracle HTTP Server mid-tiers should go through the OnDemand HTTP proxy services, www-proxy.oracleoutsourcing.com and omcs-proxy.oracleoutsourcing.com, which are the BIG-IP virtual servers that load balance the actual physical devices.

To ensure continued connectivity, the subnets for the new proxy service must be allowed access in customer's firewall.  Please see 'What are the IP Addresses for OSN' (Doc ID 435409.1) for a listing of the required subnets.  You may open the firewall to receive requests from the subnets mentioned in the note.

These configuration changes need to be done by 16th Feb 2014, 10:00 AM GMT.  If you do not complete these changes before the mentioned time, the documents delivered by Oracle Supplier Network might fail to reach your ERP system."

For more information see the Procurement Community thread: 'Urgent!!! FAQ - Change in the HTTP Proxy Service Used for Oracle Supplier Network (Doc ID 1620906.1)'.

Additional Enhancements in 12.1.3: Procurement iSupplier Portal, Sourcing and Supplier Lifecycle Management (SLM) Rollup Patch: 17525552:R12.PRC_PF.B

Did you see these new additions to Doc ID 1591198.1, section Enhancements introduced in Patch 17525552:R12.PRC_PF.B?  Along with the rest of the enhancements the following information has been appended:

 Functional Area
Previous Behavior
Enhanced Behavior
Send Pre – Qualification Questionnaire  When action ‘Send Pre – Qualification Questionnaire’ is taken,  the notification that is sent to the supplier will be ‘Action Required: Please fill out the Supplier pre – qualification questionnaire’.  In the new process an ‘Invitation to Register’ should be first sent to the supplier, followed then by an ‘Action Required: Please fill out the Supplier pre – qualification questionnaire’ notification. This will be less confusing for the supplier to first see the invitation and then the notification for questionnaire.
Supplier Registration Actions  Buyer uses Notify button to ask any information from the supplier.  The ‘Notify’ button has been converted to ‘Supplier to Provide Details’ action in actions dropdown in Supplier request review page. 
During registration process, there won’t be any action like 'Supplier to Provide details’; instead there is 'Send Invitation to Supplier’. But after registration is complete, during the approval process, the buyer/approver will have the action 'Supplier to Provide details'.
New Supplier Registration Process  After the internal user clicks on ‘Register New Supplier’ button, the user will be guided to ‘Suppliers: Register New Supplier’ page. This page presently has only two buttons – ‘Cancel’ and ‘Save & Continue’.

 As per the new process this page will have three buttons – ‘Cancel’, ‘Send Invitation to Supplier’ and ‘Save Continue’. The buttons are described below:

  •  Save & Continue: This button will save the information and take the requester to the next page - 'New Supplier Request' page where user can then enter more information and take actions such as 'Register, Save, Cancel' etc.
    Note - this button will neither send any invitation to the supplier nor will it change the status of the request. i.e.., it keeps the request in DRAFT mode.
  • Send Invitation to Supplier (New Button): This button will save the information and sends an invitation notification to the supplier to register.  It additionally changes the status of the request to 'Supplier to provide details'.
Entering Profile Attributes  Currently all UDAs display in the same page, then it requires the buyer to also enter mandatory UDAs specific to supplier.

 When the requester takes action 'Send Invitation to Supplier' on request review page (not on the request creation page), all the mandatory UDAs to be entered by the internal user will be validated and error messages will be displayed. The request is sent to the supplier only if all the mandatory UDAs are entered by the internal user. To achieve this, UDA pages are segregated to 'attributes to be entered by supplier' and 'attributes to be entered by buyer'.

New Form to Identify Unexpected Tax Errors For Transactions and Ability To Rectify Through Concurrent Program!

Development have created a new form that will allow users with Unexpected Tax Errors to be able to run, via the familiar user interface, a diagnostic to determine the problem.  

This new functionality, which converts data detection and data fix scripts into packaged procedures, is made available with the application of patch 18108467:R12.ZX.B

The new form contains access to the following diagnostic programs:

• Transaction Tax Data Diagnostic
• Populate Legal Establishment
• Synchronize Summarization Column Values
• Rectify Tax Distributions
• Populate Regime to Rate Details
• Populate Recovery Rate Details
• Remove Orphan Tax Lines
• Remove Orphan Transaction Lines
• Create Missing Transaction Lines
• Create Missing Tax Distributions for Purchase Orders
• Update Configuration Owner
• Upgrade Missing Transaction Tax Data
• Set Migrated Tax Lines as Overridden
• Synchronize Migrated Tax Distributions Amounts
• Synchronize Tax Repository

Users can run the diagnostic detection process for a specific date range or for a specific transaction and they can run in either in "Analyze" or "Analyze and Fix" Mode.

The output can be viewed as a concurrent request output file and will make it much easier for end users to quickly run diagnostics on their erroneous tax transactions.


Note: It is recommended that you first run "Analyze" Mode and check the Data and then run in "Analyze and Fix" mode to rectify the issue.


All R12.1 customers should use this form when facing 'Unexpected Tax Errors' and submit all the data detection diagnostics on the transaction data.  The output can then be reviewed to determine recommendations and steps to resolve.


For full details please review the following My Oracle Support document:

R12.1.X: Tax Diagnostic Framework (Doc ID 1621617.1)

About

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected

Twitter

Search

Archives
« February 2014 »
SunMonTueWedThuFriSat
      
1
8
9
15
16
19
21
22
23
24
25
26
28
 
       
Today