APPSINFODB – Information Technology Group

Finding Solutions for DBA's to smile…….!!!!!!! DBA its just not Administration, its core of customer’s data integrity

  • Blog Stats

    • 36,440 hits
  • Visitors

    free counters
  • Vistors Access

  • Calendar

    June 2009
    M T W T F S S
    « May   Jul »
    1234567
    891011121314
    15161718192021
    22232425262728
    2930  
  • Archives

  • Authors

Unable to Create AME Approval Rules

Posted by appsinfo on June 13, 2009

AME Approval defining rules problem

Problem: Users are not able to create the approval rules for all the transactions using Approvals Management Business Analyst.       

Error: Contact system administrator, when enabled debugging the error was standard java error, further  enabled low level debugging using FND: Diagnostics and Jserv.properties file.  The end date was error out with different date format.

 Solution:

 Modified the date parsing logic, which is error out on production, with different date format.

 1. download and apply the Patch # 8593940 in your Test Environment first.

 2. Go through the Readme and Instructions for applying the patch before applying it in the Test Environment.

 3. Make sure that you have HRMS Family Pack K RUP3(6699770) OR Oracle Approvals Management B RUP2 (5708576) 

                Refer to the following links for additional information

                   a) Oracle HRMS Product Family – Release 11i Information

                       http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=135266.1          

                   b) HRMS Patch Install Frequently Asked Questions

                       http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=130369.1

 4. Ensure you are logged in as applmgr.

 5. Before applying this patch make sure that your Oracle Applications  environment has been set up. Make sure that your $PAY_TOP and   $PER_TOP environment variables have been setup correctly.

 6. After application of these prerequisites you must apply the patch by running adpatch for the driver files in the following order:

       u8593940.drv (This is the unified driver)

 7. Run adadmin to:

       Compile Apps Schemas

 8. POST-INSTALLATION STEPS: 

                 ( Check the adpatch log files for errors (search for the words “error” and “FAILED”) 

                   Type of Log File              Log File Name

                   ————————————————————————–

                   Log file from unified driver  Name entered when running adpatch

                   Log file from worker files    “adworkxx.log” (“xx” = “01””02″ etc.)           

9. To ensure that there are no invalid AME objects, after recompiling the APPS

   schema look for invalid packages with ‘AME_%’, there should not be any.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: