Using FNDLOAD with examples

This is a post which has been sitting in my “to-do” list for a LONG time 🙂  Every time I need to download or upload configuration files into eBusiness Suite, I either have to trawl through the internet, or the documentation, or hope that someone near me has got an example handy, because I can never remember immediately which script I need to run to do what I want it to!

So, in one easy to read place, here’s my quick guide to using FNDLOAD – note that each command should be entered all on one line.

Before looking at the examples, there are a few things to be aware of.

  1. Pay careful attention when downloading Menus or Responsibilities.  If there are several developers working on Responsibilities and Menus, then you should be even more careful.  If Menus and / or Responsibilities are migrated, then you may end up with forms and functions in the new environment which are not ready for use in that environment.
  2. Be very careful when downloading flexfields which reference value sets with independent values.  For example, if you are migrating GL Segment Codes, then you will extract all the test data in GL codes which might not be applicable for the new environment.
  3. FNDLOAD provides a number of variations for each extract – the examples below are not meant to be definitive, so please feel free to amend the examples as you find necessary.  For example, you can restrict the download and uploads to specific segments within Descriptive Flex Fields.
  4. Please test your FNDLOAD properly, to ensure that you do not get any unexpected data extracted.  Before uploading the extract into a new environment, make sure that the file only contains data that you want to migrate to the new environment.

So, here’s my examples on how to use FNDLOAD…

Read more

Deleting Accounts from Email Center

I recently had to remove some email accounts from Oracle Email Center, because the environment had been cloned from one instance to another and referenced obsolete accounts.  An easy task, one might think – if they have never worked with EMC before…  Oracle produce some guidance on how to clear the accounts out, but I’ve never had a complete list of instructions before, so thought I’d document it here.  I’m sure that there are ways to remove the accounts purely functionally, but if there is, I’ve not found it – the instructions here include a mix of functional changes and direct table updates, so as ever you use it at your own risk.

Step 1 – Ensure that there are no Agents assigned to the email account

Using the Email Center Administrator responsibility, navigate to the agents association page (path Email Center Administration > Administration > Email Accounts > Associations > Agents).  Choose the “Assign Agents to Accounts” drop-down, then choose the email account that you want to remove and click the Go button.  Remove the agents from the account(s) if you can.

If there are emails in the agent’s inbox, you will need to log in as that person, navigate to their in box and remove the emails that are sitting there.  Even if you do this, though, you may well find that you still can’t remove the agent from the account – so we’ll do a direct table update to ensure that there aren’t any emails there!

Identify the email account ID that you are looking for by running the following SQL:

SELECT email_account_id
FROM   iem_mstemail_accounts
Where  email_address =  '<enter mailbox address here>'

Then identify the agent by running:

SELECT agent_id
FROM   iem_agents
WHERE  email_account_id = <email_ account id from above SQL>

Before deleting the records, I would recommend creating a backup table at this stage, e.g.

CREATE TABLE xx_iem_agents_backup AS SELECT * FROM iem_agents;

Then force the removal of the agent from the account by running the following SQL:

DELETE FROM iem_agents
WHERE  email_account_id = <email account id>
AND    agent_id = <the associated agent id>;


So, whether you have reached this point from functional configuration or deleting the records in the Email Center tables, you should now have no agents associated with the account that you want to delete.

Step 2 – Remove the rules from the accounts

This is the one step where you should be able to do this functionally.  Navigate to the rules association page (Email Center Administration > Administration > Email Accounts > Associations > Processing Rules), and choose the account that you are deleting.  Make sure that there are no rules associated with the account – if there are, then expand the entry and remove them by clicking on the bin icon.

Step 3 – Empty the folders

Check whether Email Center is looking at the folders for that account – navigate to Email Center Administration >Monitoring > Download Processor and see whether there are any emails that the system is looking at.

If there are any messages on the server, then you should delete them if they are no longer needed – to do this, I open the account in my email client and remove the messages from the inbox, Oracle Processed and Oracle Retry folders.  Once they are empty, the Download Processor should show that there are no messages there.

Step 4 – Make the account inactive and delete it

Theoretically, this is the last step and should be straightforward.  To do this functionally, navigate to Email Center Administration > Administration > Email Accounts > Summary and find the account that you are trying to delete.  Edit the configuration and change it from Active to Inactive, then return to the summary screen.  If all is well, then the bin icon will be enabled and you can now delete the account.  If not, then we are back into the world of SQL updates to remove the account information…

Firstly, check whether there are emails being processed for the mailbox by running the following SQL:

SELECT email_account_id
,      message_id
FROM   iem_rt_proc_emails
WHERE  email_account_id = ( SELECT email_account_id
FROM   iem_mstemail_accounts
WHERE  email_address = '<enter mailbox address here>' );

If there are no rows returned, then identify the email account ID by running the subquery above:

SELECT email_account_id
FROM   iem_mstemail_accounts
WHERE  email_address = '<enter mailbox address here>';

Make a note of the account ID before moving onto the next section.

If there were any records returned, then delete them from the table (again, I recommend making a backup of the data first!):

CREATE TABLE xx_iem_rt_proc_emails_backup AS SELECT * FROM iem_rt_proc_emails;

DELETE FROM iem_rt_proc_emails
WHERE  email_account_id = <id you made a note of> ;


Next, check for any messages that are in the pre-processing stage:

SELECT email_account_id
,      message_id
FROM   iem_rt_preproc_emails
WHERE  email_account_id = <id you made a note of> ;

If no rows are returned do nothing, but if one or more rows are returned, then do the following:

CREATE TABLE xx_iem_rt_preproc_emails_backup AS SELECT * FROM iem_rt_preproc_emails;

DELETE FROM iem_rt_preproc_emails
WHERE  email_account_id = <id you made a note of> ;


That should be all that you need to do, and the accounts should now be able to be deleted.  Navigate to Email Center Administration > Administration > Email Accounts > Summary and check whether the bin icon for the email account is now enabled.  If it is, then delete the account from the front-end.  If not, then there is one final “force” that you can do from the back end:

UPDATE iem_mstemail_accounts
SET    deleted_flag = 'Y'
WHERE  deleted_flag = 'N'
AND    email_account_id = <id you made a note of> ;

The account is now removed from Email Center.

By continuing to use the site, you agree to the use of cookies. more information

In common with almost all professionally run websites, this website logs the IP address of each visitor in order to keep it running reliably. This is also essential for protecting the website and its visitors from malicious attacks, including infection with malware.

This website provides information as a service to visitors such as yourself, and to do this reliably and efficiently, it sometimes places small amounts of information on your computer or device (e.g. mobile phone). This includes small files known as cookies. The cookies stored by this website cannot be used to identify you personally.

We use cookies to understand what pages and information visitors find useful, and to detect problems such as broken links, or pages which are taking a long time to load.

We sometimes use cookies to remember a choice you make on one page, when you have moved to another page if that information can be used to make the website work better. For example:
- avoiding the need to ask for the same information several times during a session (e.g. when filling in forms), or
- remembering that you have logged in, so that you don’t have to re-enter your username and password on every page.

You can prevent the setting of cookies by adjusting the settings on your browser (see your browser Help for how to do this). Be aware that disabling cookies will affect the functionality of this and many other websites that you visit.