Monday, September 30, 2013

unable to see item in price list LOV in r12 order management

Issue:

Unable to see Inventory item in order management price list LOV

Solution:

Attach profile option "QP:Item Validation Organization" under your order management responsibility level  then reproduce the steps.

user defined exceptions in package oe_schedule_util procedure insert_into_mtl_sales_orders FND_FLEX_SERVER2.get_qualsegs() could not find any segment for the flexfield specified by application ID=401, code=MKTS and structure number=101

Issue:

user defined exceptions in package oe_schedule_util procedure insert_into_mtl_sales_orders

FND_FLEX_SERVER2.get_qualsegs() could not find any segment for the flexfield specified by application ID=401, code=MKTS and structure number=101

Solution:

Fnd_flex_server2.Get_qualsegs() Could Not Find Any Segments (Doc ID 797564.1)

Applies to:

Oracle Order Management - Version 12.0.4 and later
Information in this document applies to any platform.

Symptoms

-- Problem Statement:
On 12.0.4 in Production:
When attempting to enter the Sales Orders form, the following error occurs:

ERROR
"Program error. The data that defines the flex field on this field may be inconsistent.
Inform you system administrator that the routine FND_FLEX_SERVER2.get_qualsegs() could not find any
segments for the flex field specified by Application ID = 401, Code = MKTS and structure number = 101"

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
Configuring OM module in R12. Configure all parameters, then:
1. Start the Sales Orders Form
2. Fill all fields
3. Press "Line Item" tab.
4. The message error is displayed.

Cause

The Flex Field for "MKTS" and title "Sales Order" was not setup.

Document 93466.1 has the information that is needed to set up the Inventory - Sales Order flex field.
Document 236108.1 Oracle Applications Flex fields Guide Release 11i.

Solution

From Document 93466.1:

Check the setup for the Sales Order flex field and make corrections wherever required.

1. Check if you have the segments of the Sales Order flex field set to the following:

segment 1 - sales order
segment 2 - order type
segment 3 - order source
If the above values do not tally, change the values, freeze and recompile
the flex field.
System Administrator Responsibility: Application --> Flexfield--> Key

2. Use the following script to check the above values at the database level:

Select Sales_Order_ID, segment1, segment2, segment3
From MTL_SALES_ORDERS
Where segment1 = 'order number'

The correct entry should return the following result:

Sales_Order_ID segment1 segment2 segment3
Sales_Order_ID number Order Number Standard ORDER ENTRY

Select the Sales_Order_ID that does not have the above result. Update the
MTL_TRANSACTIONS_INTERFACE table with the Transaction_Source_ID that has the
correct result using the following script:

Update MTL_TRANSACTIONS_INTERFACE
Set Transaction_Source_ID = correct sales order id number;

3. Check if dynamic insert has been enabled for Sales Order flex field. If you have not enabled
it, unfreeze the flex field, enable dynamic inserts, freeze and compile the flex field.

4. Check the segment separator for the flex field. It should be set to '.' (dot)

5. Check for the Value Set attached to the segments of the sales order flex field. Check if the
actual value passed is within the maximum value allowed for the Value Set.

6. Check that you have set the profile option "Validate on Server" for the Sales Order flex field
to "No."




Error while opening r12 sales order form. EOERR: ORA-4062 "timestamp/signature

Issue: 

EOERR: ORA-4062 "timestamp/signature


Solution:

We have to compiled particular form using adadmin in database.

Check below Oracle Support Note for more details.

OERR: ORA-4062 "timestamp/signature of %s has been changed" (Doc ID 19851.1)


Error:  ORA-4062
Text:   timestamp/signature of %s has been changed
-------------------------------------------------------------------------------
Cause:  Attempt to execute a stored procedure to serve
        an RPC stub which specifies a timestamp/signature that is different 
        from the current timestamp/signature of the procedure.
Action: Recompile the caller in order to pick up the new timestamp/signature.

*** Important: The notes below are for experienced users - See Note:22080.1
 
Note: Simply re-executing the procedure that calls the remote one will cause
      it to be re-compiled.

      Note also that this error is only returned when calling remote procedures.
      The way to avoid it as far as possible is to only ever call remote
      *packaged* procedures, whose body may be re-built without affecting the
      timestamp (stored in the specification).

      It is also advisable to set <Parameter:REMOTE_DEPENDENCIES_MODE> to
      SIGNATURE on releases supporting this.





 

Saturday, September 21, 2013

Unable to See the Legal Entity List of Value in the Bank Account Owner Field in R12

Issue:

Unable to See the Legal Entity List of Value in the Bank Account Owner Field in R12

Solution:

1. Login as System Administrator user and then switch responsibility to User Management.
2. Click in Roles & Role Inheritance link
3. Do the following search:
- Type: Role and Responsibilities
- Category: Miscellaneous
- Application: Cash Management
Choose the Cash Management responsibility where you want to create and maintain bank accounts.
4. Click in the Update icon
5. Click in Security Wizard button
6. Run the Wizard for CE UMX Security wizard.
7. Click in Add Legal entities and add the legal entity you will give the selected role access to
the all bank accounts within this legal entity and choose grants that you want to assign to this
role on the bank accounts of this legal entity ( Use, Maintenance, Bank Account Transfers )
8. Click in the Apply button and then click in the save button.
9. Now try to create or update a bank account in the chosen Cash Management Responsibility  

Oracle Supplier name not listed in invoice FORM LOV in new implementation setup



Issue:
Supplier name not listed in invoice FORM LOV in new implementation setup

Solutions:

Make sure Payment check box are enabled on supplier site window.


Query the supplier and view supplier site enable the "Pay" check box