Tuesday, February 14, 2012

Supporting AME Issues and different Diagonistics steps

1. To find AME Installation Level :

select decode(bug_number, '2614213','2614213 (pre-11.5.10)'
,'2863619','2863619 - (pre-11.5.10)'
,'3858763','AME 11.5.10'
,'4433707','AME.A RUP'
,'4873179','AME.B RUP.1'
,'5708576','AME.B RUP.2'
,'3333633','HR FP J'
,'3500000','HR FP K'
,'5055050','HR FP K RUP1'
,'3140000','Apps Release 11.5.10'
,'3640000','Apps Release 11.5.10 CU1'
,'3480000','Apps Release 11.5.10 CU2'
from ad_bugs
where bug_number in ('2614213'

2. To Find AME related Packages

select,, src.text
from dba_source src, v$database db
where in ('AME_ENGINE'
) and src.line=2 order by 2;

3. To Identify Invalid AME Objects

select object_name,
from all_objects
where object_name like 'AME%'
and status = 'INVALID';

4. Identifying AME Exception Log

i) Note down the output of the following query.
select max(log_id) from ame_exceptions_log;
ii) Reproduce the issue.
iii) Provide the output following query in excel format.
select * from ame_exceptions_log
where log_id > {provide above max(log_id) here}
order by log_id;

Within the AME Administration screens, it is possible to review the exceptions linked to a specific transaction type. This is especially useful if the logs above do not help, or if the messages seem to be related to the core AME processing or setup.
Details on the steps to capture this log are given in Note 365471.1 - iProcurement AME Approvals Troubleshooting Guide, Section 2.

Also within the AME Administration responsibility, it is possible to run a test to check if the approval list builds successfully for a specific Transaction Type and Document (requisition_header_id). Detailed steps are given in Note 293233.1 - 11.5.10 Trouble Shooting Tips for Approvals Management (AME).

5. Identifying Transaction Failure Using Workflow and Scripts

Processing output from a specific transaction, and therefore more details on any failure encountered using the scripts wfstatus.sql and wfstat.sql (under $FND_TOP/sql/). Details on using these can be found in many notes, such as Note 134960.1.

6. FND debug log

Whilst most of the processing is done within Workflow, when issues are encountered due to user actions within the application user interface, it makes sense to get the debug log from these actions.

From 11.5.10 onwards this can be done by setting users FND debugging to write to a file. For earlier releases, the ssp_init.txt file parameters can be set to enable similar debugging for the instance. More detailed steps on enabling this can be found in Note 290614.1 - How To Get Log Files

7. PL/SQL Steps ( Only for AME issues for PO Workflow Debugging):

The code used to perform activities within the workflow processing writes additional debug output based on the user enabling PO Workflow debugging, using the following steps:

1. Set the following User-Level Profile Option PO: Set Debug Workflow to value: ON

2. Reproduce the issue fully until get error or problem. Note the Workflow Item Type and Item Key, often displayed within errors or can be readily found from checking the Workflow Monitor pages.

3. The debug data is stored in the table: PO_WF_DEBUG. To retrieve debug data select the rows for given itemtype and itemkey of the workflow processing in the testcase.
SELECT document_id, document_number, authorization_status, debug_message
FROM po_wf_debug
WHERE itemtype = '&item_type' AND itemkey = '&item_key'
ORDER BY execution_sequence

Within the debug output, the procedure names often give a good idea what the process is trying to do, and as such can help point towards areas to investigate, For example; attritibute values, transaction data, approver setup etc.

In addition, any PL/SQL code exceptions encountered are sent as a detailed email to the POERROR workflow process (see Note 224028.1 for setup). Check this notification for further details.

8. AME Document References

AME User Guides:
Note 227391.1 - Oracle Approvals Management Implementation Guide (Note 282529.1 for 11i10 and Note 336901.1 for AME.B)
Note 289927.1 - Oracle Approvals Management Developers Guide

Oracle Approvals Management Documentation Resources for Release 12 in Note 396808.1

Note 287255.1 - Approvals Management Reporting Utility Support Tool

Note 421207.1: An 11i10 script for reporting basic AME setup information, including all Rules and their Conditions and Attributes. The script accepts only the Application ID for the Document Type, and this can be found from the SQL

Note 338508.1 - Error "Oracle Approvals Management has found parallelization configuration..."
- This note contains a script (checkAME11510Setup.sql) which can be used to validate AME setups also.

Note 428552.1. Troubleshooting approval routing issues when using AME approval.

Note 312832.1 - Encountering Error When Trying to Approve Requisitions Using AME Approval Group With FND Users (Not Associated To HR Employees)

Thanks & Regards,
S.Grace Paul Regan

Troubleshooting AME Approval Routing

1. 11i.AME.B - Review the setup

a. Navigate to AME (Approvals Management Business Analyst) responsibility /
Business Analyst dashboard
b. Click Setup Report in the bottom right of the dashboard page
c. Select Purchase Requisition Approval transaction type (or similar) and
click Go
d. * Choose Printable Page. Review the setup details to verify all conditions on the requisition have
applicable rules and valid approvers specified. The report shows Attributes,
Conditions, Groups, and Rules details.

For the same detail in 11i.AME.A review the setup under each tab: Attributes,
Conditions, Groups, Rules

2. 11i.AME.A - Capture a new exception log from a testcase

a. Select the Admin tab
b. Select transaction-type administration and click Continue
c. Select Clear the current transaction type's exception log and click Continue / OK

d. * Navigate to iProcurement and reproduce the issue (Add items to cart, proceed through checkout, and reproduce the error that the approval list is not built.
e. Navigate to AME (ensure Transaction Type is still Purchase Requisition Approval)
f. Select the Admin tab
g. Select transaction-type administration and click Continue
h. * Select View the current transaction type's exception log and click Continue
i. Search Metalink based on the exceptions shown in the exception log, and adjust the rules and groups setup accordingly

3. Do a Test Transaction

a. Navigate to AME (Approvals Management Business Analyst) responsibility /
Business Analyst dashboard
b. Specify the transation type Purchase Requisition Approval (or similar)
c. Choose Test Workbench
d. Click Create
e. Specify conditions and select starting point person, org_id, and other details to match the case that has the issue

- Name and save the test if desired for future use

f. * Run the test and review the results to confirm whether or not an appropriate rule(s) is found

Thanks & Regards,
S.Grace Paul Regan

Monday, June 14, 2010

Stop Notification Cancelled E-Mails !

To avoid sending email for closed / canceled notifications, you must disable Mailer parameter "Send e-mails for canceled notifications" :

1- In OAM : Site Map / Notification Mailer / Edit / Advanced / Go to Step 4 (Message

2- Untick the "Send e-mails for canceled notifications" checkbox

3- Apply changes

4- Bounce Mailer

This will stop all the cancelled notification e-mail for your instance across modules.

Thanks & Regards,
S.Grace Paul Regan

Tuesday, May 25, 2010

How to find lost auto created RFQ ? (Manual Error)

Dear friends,

A simple error but a very critical one for consultants!

You know when you auto create a Purchase Requisition to a sourcing RFQ after you press the auto create button to standard or Blanket order a new HTML page will open with a New RFQ in the new RFQ you will have to enter the title and ship to location to save the document to make it available in draft negotiations column in the negotiations home page, But after the new page was open and if the users did not enter the title or mandatory field and if they closed the web page by mistake you will not find this RFQ anywhere in the system, this error looks very simple but unless you know the right place to get back the negotiation number you are in trouble.

Simple way to find this created RFQ is navigate to requisition summary window, Query the requisition for which RFQ was lost, go to lines >Folder(from menu)> Show Field> Select Negotiation Number and you can find the created RFQ number. Then go to Sourcing respo and go to draft negotiations function to find the RFQ and press edit to complete the task…

Thanks & Regards,
S.Grace Paul Regan

Monday, December 28, 2009

Required Setup Steps for Sourcing Implementation

1. Set the Enterprise Name (Required)

You can specify the Enterprise name that is used in notification e-mails that are sent from Oracle Sourcing. To specify this name, run the following script
This script prompts for an enterprise name and updates the relevant tables with this
information. If you do not run this script, any notifications sent to supplier users will have "Default enterprise name" as the company name in the subject and body of these notifications.

2. Define System Profile Options (Required)

Profile options are one way to control system processing. They can control resource
usage as well as enable or disable certain application features. The following system
profile options relate to Oracle Sourcing. Other profile options are involved with
enabling integrations between Oracle Sourcing and other applications such as Oracle
Procurement Contracts and Oracle Services Procurement.

• Setting the option PO: Allow Autocreation of Oracle Sourcing Documents to Yes
enables buyers to use AutoCreate to generate draft auctions and Sourcing RFQs that
can then be completed and awarded in Oracle Sourcing.

• Setting the option PO: Display the Autocreated Document to Yes allows Sourcing to launch automatically from Oracle Purchasing once your buyers have finished AutoCreating the draft sourcing document. Buyers must also have a responsibility that contains the Edit Draft Negotiation function.

• The Award Approval feature allows buyer to go through an approval process before
creating a Purchase Order. Before using this functionality, you need to implement
Oracle Approvals Management following instructions in the Oracle Approvals
Management Implementation Guide. Afterwards, set PON: Enable Sourcing Award
to Yes.

The system can search recent supplier transactions. Buyers can use this transaction
history to research a supplier’s performance, for example, when identifying suppliers
to invite to a particular negotiation. Set the PON: Supplier Transaction History
Time Period
to a number to indicate the number of prior days the system should search for supplier transaction details.

PON:External Application Framework Agent specifies a URL (typically outside your firewall) will be used for the links in notifications sent to suppliers. If this value is not specified, the system will use the applications frame work agent value assigned to the Sourcing Default Responsibility (See below).
• Setting the Sourcing Default Responsibility for External User profile option
specifies the applications framework agent that will be used if the PON: External Applications Framework Agent profile option is not set (See above). .

• In addition to the reports available from Oracle Sourcing, if you have Oracle Daily
Business Intelligence implemented, you can set POA: DBI Implementation to Yes to access additional reports from Oracle DBI.

• The POS: External URL profile option sets the URL included in notifications sent from the system

3. Assign Sourcing Responsibilities (Required)

During this step, you assign your users the responsibilities they need to perform their jobs. As you assign a user a responsibility, make sure that each buyer’s HR profile contains a first name, last name, and e-mail address.

The Sourcing Super User, Sourcing Buyer, and Sourcing Supplier responsibilities
come predefined with most of the necessary job functions. However, you can create
customized responsibilities using the job functions available. For a complete list of
the job functions defined, "Oracle Sourcing Responsibilities and
Functions.", will help you decide whether to create a customized responsibility, and if so, which job functions to assign to the new responsibility.

4. Register Suppliers and Supplier Users (Required)

Supplier companies must be registered with the system to access Oracle Sourcing and
participate in negotiations.
Once suppliers are registered, they can create profiles that supply detailed information on the products and services they provide. Buyers can search this supplier information to more efficiently target suppliers for negotiations they are creating. The system also tracks purchasing information on suppliers which can be used to generate many different reports for performance analysis.

The contacts at your supplier companies must also be registered with the system
and assigned the Sourcing Supplier responsibility before they can participate in any
Oracle Sourcing negotiations.

There are several other steps which are optional depending upon your specfic business requirements.

Thanks & Regards,
S.Grace Paul Regan

Tuesday, August 18, 2009

Tips for implementing i-Sourcing and -i-Supplier

Dear Friends,

These steps are created by me by my own experience, tips for implementation!

First go through all the functionalities available within the i-Sourcing and i-Supplier functionality and then decide what you can show up to the client as you already know your client business, never describe any functionality which will not be used by the client even though it may any simple one.
Try to give only the most required functionalities to the client!
The basic and most important functionalities are,
1. Auto Creating RFQ from Requisition.
2. Amending a RFQ

3. Playing with control functionality for RFQ
a. Register suppliers in i-Supplier, Its better you can send them a word document asking for their details and once they respond back you can register them from your side in oracle rather giving them an online link to directly register with you; this will bring lot of complications in registering process.
b. Then and there check for pending supplier approval and approve the suppliers you have qualified to let them take part in i-Sourcing.

4. Communicatting a RFQ to client through e-mail
5. Try to have on-line discussions with the supplier
6. Receive online quotations through mail from Registered Supplier’s
7. Award appropriate suppliers with the contract (Initially do not play with the score functionality)
8. Create Purchase Order from the awarded quote and get the approval for further procurement process.

These are the minimal process and most required process for any company who has implemented i-Sourcing and i-Supplier. Still there are lot of other useful functionalities available within the i-Sourcing and i-Supplier module, its better for any consultant to go with these basic steps. Once when the Key users and Key Suppliers are ok with the i-Sourcing basic functionality, then you can proceed with teaching them other functionality like

• Negotiation Configuration
• Reusable Attribute Lists
• Price Factors and Reusable Price Factor Lists
• Reusable Invitation Lists
• Negotiation Templates
• Tender From Approved List of Suppliers
• Major Tendering Process
• Reverse Auction

Too many functionalities thought to the client at the beginning stage will complicate the training process, implementation process and project phase as the users were using some other system for a long time and when they are comfortable using that system we are trying to introduce a expensive product which users are aware already, So they want the new expensive system to work very smoothly and it should be ease of their use. So it’s better for any experienced consultant to start with the minimal functionality and if required you can go with the others. In some case its better you even don’t explain them these other extra functionalities are available because client will start to confuse if I am not aware of this now then when will I and who will teach all these functionalities and they will ask you to teach all the available functionalities that will complicate everything and will make you life miserable.

To stay happy and leave others happy sometimes you need to take un-ethical decisions.

Thanks & Regards,
S.Grace Paul Regan

Monday, July 27, 2009

What is Oracle Sourcing?

Oracle Sourcing offers flexible negotiation capabilities to buyers and sellers,
enabling them to efficiently obtain the best possible prices for goods and services.

Prices are established based on actual supply and demand at the time the negotiation
is transacted.

The different types of sourcing documents available -
requests for quotations (RFQs),
requests for information (RFIs),
and buyer's auctions.

Buyers use real-time interaction to obtain information on suppliers' products and services, and then use that information to create negotiations that drive prices based not only on price, but on lead times, quantity, and item-specific attributes. Buyers and sellers, who might never meet face-to-face, can bypass intermediaries and establish relationships that might not have been possible using more traditional methods of buying and selling.

Thanks & Regards,
S.Grace Paul Regan