Wednesday 25 June 2014

Duplicate Item Numbers Causing APP-FND-00906 When Quering Items

Incase of any Duplicate Item then it throughs error APP-FND-00906 When Quering Item master.

Run the following steps, Check incase of any duplicate item.

SELECT organization_id, segment1, segment2, segment3, segment4, segment5,
       segment6, segment7, segment8, segment9, segment10, segment11, segment12,
       segment13, segment14, segment15, segment16, segment17, segment18, segment19, segment20,
count(*)
FROM mtl_system_items_b
GROUP BY organization_id, segment1, segment2, segment3, segment4, segment5,
         segment6, segment7, segment8, segment9, segment10, segment11, segment12,
         segment13, segment14, segment15, segment16, segment17, segment18, segment19, segment20
HAVING count(*) > 1 ;


If it returns any rows then update the duplicate items.

update mtl_system_items_b
set segment1 = segment1 || '_N/A'
where organization_id = &organization_id
and inventory_item_id = &item_id;

commit

User is Not Getting Email for Oracle Notificati​on Such As Approval Kind of Mail.

Check notification_preference is ENABLED or DISABLED wf_local_roles for
that user?  If Disabled then run the below update

UPDATE WF_LOCAL_ROLES
SET STATUS ='INACTIVE' ,EXPIRATION_DATE = (SYSDATE-1)
WHERE NAME LIKE '&user_name'
AND PARENT_ORIG_SYSTEM ='WF_LOCAL_USERS'
AND NOTIFICATION_PREFERENCE ='DISABLED';


After that issue a commit and run the below program.
Synchronize WF LOCAL tables
 

Fails With Error UTIL0020 Invalid Concatenated Segment

1. Navigate to Setup -> Financials -> Flexfields -> Key -> Segments

2. Query for the structure (Chart of Accounts), by entering:
      Application = General Ledger
      Flexfield Title = Accounting Flexfield

3. Unfreeze the Flexfield Definition.

4. Confirm that all Segments in the structure are Displayed and Enabled.
     All segments must have the checkbox ticked.

5. Recompile the Structure.

6. Run the posting program again.

Thursday 12 June 2014

Remit-To Address Setup

Responsibility: Receivables Manager
Navigation:  Setup > Print > Remit To Address


Find the row or rows associated to your Operating Unit and check to see if the bill to address is covered by the "Receitps From" definition.

The most common cause of an error in deriving a Remit-To address is in this "Receipts From" mapping. 
 A best way to avoid problems is to set a default remit-to address for all countries where you transact.

 This allows you to avoid errors during AutoInvoice and transaction entry.  

Thursday 5 June 2014

An internal error has occurred in the program xla_accounting_pkg.complete_entries. Technical problem : Problem encountered in sequencing

To implement the solution, please execute the following steps:

Using a General Ledger responsibility, check the document sequencing setup under Accounting Setup Manager. In particular review :-

SEQUENCE CONTEXT DEFINITION

1. Sequence Context Name:
- Ledger Name:
- Sequence Entity:
- Sequence Event:
- Require Assignment:
- Validate Sequence By:

If a secondary ledger exists:

2. Sequence Context Name:
- Ledger Name:
- Sequence Entity:
- Sequence Event:
- Require Assignment:
- Validate Sequence By:

3. Also check that the Sequence has been defined with the correct dates so that it can be used by the Create Accounting program. i.e. the sequence assignment has to be active for the date of the transaction.

4. Retest the issue.