Wednesday, 23 May 2012

How to purge e-mail notifications from the Workflow queue - after clone

Some times Due to large number of e-mail notifications to accumulated in the queue Workflow mailer will not start,To fix this issue we need purge the notifications from the Workflow queue.


The below outlines the steps, Please take proper backup before performing the below.

1) You need to update the notifications you do not want sent, in the WF_NOTIFICATIONS table.

2) Check the WF_NOTIFICATIONS table as below. Records where status = 'OPEN' and mail_status = 'MAIL' are notifications that will have an e-mail notification sent.

SQL> select notification_id,status,mail_status,begin_date from WF_NOTIFICATIONS where status = 'OPEN' and mail_status = 'MAIL';

3) This should show you which notifications are waiting to be e-mailed.

4) To update a notification so that it will not get e-mailed. Set the MAIL_STATUS = 'SENT'. The mailer will think the e-mail has already been sent and it will not send it again.

SQL> update WF_NOTIFICATIONS set mail_status = 'SENT' where mail_status = 'MAIL';

-> This will update all notifications waiting to be sent by the mailer.

5) Then run the script wfntfqup.sql to purge the WF_NOTIFICATION_OUT queue and rebuild it with data currently in the WF_NOTIFICATIONS table. This is what purges all notifications waiting in the queue to be sent.Only the ones where mail_status = 'MAIL' and status = 'OPEN' will be placed in the WF_NOTIFICATION_OUT queue and sent by the mailer.

SQL>sqlplus apps/apps_pwd @$FND_TOP/patch/115/sql/wfntfqup APPS APPS_PWD APPLSYS

6) Now you can start your WF Containers and then Mailer

Oracle Workflow Related.

Purge WF_NOTIFICATION_OUT queue cd $FND_TOP/patch/115/sql
sqlplus apps/ @wfntfqup.sql APPS (appspwd) APPLSYS
e.g sqlplus apps/apps @wfntfqup.sql APPS apps APPLSYS

This purges the WF_NOTIFICATION_OUT queue and rebuilds it with data currently in the WF_NOTIFICATIONS table. This is what purges all notifications
waiting in the queue to be sent. It will then populate the queue with the current data in the WF_NOTIFICATIONS table.
Only notifications with mail_status = 'MAIL' and status = 'OPEN' will be re-enqueued in the WF_NOTIFICATION_OUT queue and sent by the mailer.

Workflow TEST Address Update
sqlplus apps/ @$FND_TOP/sql/afsvcpup.sql

Enter Component Id: 10006

Enter the Comp Param Id to update : 10093

Enter a value for the parameter : WFdevUsers@abc.com

Setup Test address/override address for WF
Below is the script to update the override address from backend. You do not need the verification code to set the override address using the below script

update fnd_svc_comp_param_vals
set    parameter_value = '&EnterEmailID'
where  parameter_id =
( select parameter_id
 from   fnd_svc_comp_params_tl
 where  display_name = 'Test Address'
);


Workflow From Address Update :
sqlplus apps/ @$FND_TOP/sql/afsvcpup.sql

Enter Component Id: 10006

Enter the Comp Param Id to update : 10065

Enter a value for the parameter : Lenovo DEV Workflow Mailer"

set overriding address:
update FND_SVC_COMP_PARAM_VALS
set parameter_value = 'Configuration.Workflows@abc.com'
where PARAMETER_ID = 10057;


Scipt to see workflow configuration
SQL> select p.parameter_id,p.parameter_name,v.parameter_value value
from fnd_svc_comp_param_vals_v v,
fnd_svc_comp_params_b p,
fnd_svc_components c
where c.component_type = 'WF_MAILER'
and v.component_id = c.component_id
and v.parameter_id = p.parameter_id
and p.parameter_name in
('OUTBOUND_SERVER', 'INBOUND_SERVER',
'ACCOUNT', 'FROM', 'NODENAME', 'REPLYTO','DISCARD' ,'PROCESS','INBOX')
order by p.parameter_name;


SQL to monitor (check status) of Workflow Notification Mailer (Java)

SELECT COMPONENT_STATUS from APPS.FND_SVC_COMPONENTS where COMPONENT_ID=10006;

sqlplus -s system/${PASSWD}@${ORACLE_SID} << SQLEND >${script}/apps/wf_status.out
set linesize 90
col COMPONENT_NAME format a50
col COMPONENT_status format a20
spool ${script}/apps/wf_status.lst
select COMPONENT_ID,COMPONENT_NAME,COMPONENT_STATUS from apps.fnd_svc_components
where COMPONENT_ID not in (10000,10001,10020,10021,10022) and COMPONENT_STATUS <> 'RUNNING';

select mail_status, count(*) from apps.wf_notifications
where status = 'OPEN'
and mail_status in ('MAIL','ERROR')
group by mail_status;
spool off"



To see error message for a workflow notification
SQL> select ERROR_MESSAGE from wf_item_activity_statuses_v WHERE NOTIFICATION_ID = 7377659;

Here are steps/events for Oracle Workflow Notification Outbound Processing(eMail from Oracle Applications Workflow to Users)

1.When workflow Engine determines that a notification message must be sent, it raises an event in BES (Business Event System) oracle.apps.wf.notifications.send
Event is raised with Notification ID (NID) as event key
2. There is seeded subscription to this Event
3. Event is placed on WF_DEFERRED agent
4.Event is dequeued from WF_DEFERRED and subscription is processed
5. Subscription places event message to WF_NOTIFICATION_OUT agent.
6.Notification Mailer dequeues message from WF_NOTIFICATION_OUT agent and
6.1convert XML representation of notification into MIME encoded message (Multi-purpose Internet Mail Extensions) and
6.2 Send message by SMTP (Simple Mail Transfer Protocol) to intended user (If Test Address/Override Address is set then email is sent to Test Address

E-Mail Notification is sent if all below conditions are true
a) Notification status is OPEN or CANCELED and
b) Notification mail_status is MAIL or INVALID and
c) Recipient Role has a valid e-mail address and Notification Preference is in the format MAIL%
d) Workflow Deferred Agent Listener is running
e) Workflow Notification Mailer is running

To check a) & b) run below query
SELECT status, mail_status FROM wf_notifications WHERE notification_id = ‘&NID’;

mail_status >> SENT means mail has gone out of mailer to user

To check c) run below query
SELECT email_address, nvl(WF_PREF.get_pref(name, ‘MAILTYPE’),notification_preference)
FROM wf_roles
WHERE name = upper(’&recipient_role’);

To check d) & e) Use OAM (Oracle Application Manager)


Workflow version embedded in 11i
************************
Run following SQL from apps user ;
SQL>select TEXT from WF_RESOURCES where NAME='WF_VERSION';

You should see output like
TEXT
-----------------------
2.6.0
Which means you are on Workflow Version 2.6.0

You can also use script wfver.sql in FND_TOP/sql to find version of workflow in Apps.

To Configure Workflow Notification Mailer need below information

PARAMETER_NAME VALUE
------------------------------ ------------------------------
Inbound Server Name wfmailer.abc.com
Username wftst
Password oracle
Outbound Server Name wfmailer.abc.com
Reply-to Address wftst@abc.com


Taking a backup of the workflow configuration
cd $HOME/
sqlplus “/ as sysdba”
spool wf_mailer.log
set lines 130
set pages 200
col value format a30
select p.parameter_id,p.parameter_name,v.parameter_value value
from apps.fnd_svc_comp_param_vals_v v,
apps.fnd_svc_comp_params_b p,
apps.fnd_svc_components c
where c.component_type = 'WF_MAILER'
and v.component_id = c.component_id
and v.parameter_id = p.parameter_id
and p.parameter_name in
('OUTBOUND_SERVER', 'INBOUND_SERVER',
'ACCOUNT', 'FROM', 'NODENAME', 'REPLYTO','DISCARD' ,'PROCESS','INBOX')
order by p.parameter_name;


To schdule Gather schema stats and purge workflow runtime data

Login into application as sysadmin and schedule below Requests.
Gather Schema Statistics (ALL , 20% , degree 6 ) to run every SUN and WED
Workflow Background Process to run every 10 mts and Apply the interval as :From the completion of the prior run
Purge Obsolete Workflow Runtime data - Every week
Workflow Control Queue Cleanup - Every 12 hours


To update WF notification status
IMPORTANT STEP ! Connect to SQL*PLUS as APPS user and do the following steps
update applsys.wf_notifications
set status ='CLOSED', mail_status ='SENT', end_date ='01-JAN-01'
where mail_status='MAIL';
update wf_notifications set status=’CLOSED’;
commit;"
Select distinct status from wf_notification" this should return only one value CLOSED.
or simple do
update wf_notifications set status = 'CLOSED', mail_status = 'SENT';
commit;


Update workflow a/c pwd from backend
set define off
update APPLSYS.FND_SVC_COMP_PARAM_VALS set PARAMETER_VALUE= '_@#0@##^90@#!4^86#!$^68$#9$4#@@$6!!!9#0@`$B9+}*0&9&@0&8#|'
where
PARAMETER_ID=
( select parameter_id from APPLSYS.FND_SVC_COMP_PARAMS_B where parameter_name = 'INBOUND_PASSWORD');

To check WF mail status
select count(*), mail_status
from wf_notifications
where begin_date > sysdate - 1
group by mail_status;

There are 141 messages with status `MAIL¿, this status should remain very short and then progress to status `SENT¿.
: OAM Login > Site Map > Workflow > Service Components.
These same detail are also given in the output from script $FND_TOP/sql/wfver.sql


To check the WF status from backend

check the status of Agent Listeners:

set pagesize 400
set linesize 120
set pagesize 50
column COMPONENT_NAME format a45
column STARTUP_MODE format a15
column COMPONENT_STATUS format a15
select fsc.COMPONENT_NAME,fsc.STARTUP_MODE,fsc.COMPONENT_STATUS
from APPS.FND_CONCURRENT_QUEUES_VL fcq, fnd_svc_components fsc
where fsc.concurrent_queue_id = fcq.concurrent_queue_id(+)
order by COMPONENT_STATUS , STARTUP_MODE , COMPONENT_NAME;


Typical output from this

COMPONENT_NAME STARTUP_MODE COMPONENT_STATU
--------------------------------------------- --------------- ---------------
WF_JMS_IN Listener(M4U) AUTOMATIC RUNNING
Workflow Deferred Agent Listener AUTOMATIC RUNNING
Workflow Deferred Notification Agent Listener AUTOMATIC RUNNING
Workflow Error Agent Listener AUTOMATIC RUNNING
Workflow Inbound Notifications Agent Listener AUTOMATIC RUNNING
Workflow Java Deferred Agent Listener AUTOMATIC RUNNING
Workflow Java Error Agent Listener AUTOMATIC RUNNING
Workflow Notification Mailer AUTOMATIC RUNNING
ECX Inbound Agent Listener MANUAL STOPPED
ECX Transaction Agent Listener MANUAL STOPPED
Web Services IN Agent MANUAL STOPPED
Web Services OUT Agent MANUAL STOPPED
Workflow Inbound JMS Agent Listener MANUAL STOPPED

13 rows selected.


Steps to start/stop notification mailer

1.a Check workflow mailer service current status
sqlplus apps/

select running_processes
from fnd_concurrent_queues
where concurrent_queue_name = 'WFMLRSVC';

Number of running processes should be greater than 0

1.b Find current mailer status
sqlplus apps/

select component_status
from fnd_svc_components
where component_id =
(select component_id
from fnd_svc_components
where component_name = 'Workflow Notification Mailer');

Possible values:
RUNNING
STARTING
STOPPED_ERROR
DEACTIVATED_USER
DEACTIVATED_SYSTEM

2. Stop notification mailer
sqlplus apps/

declare
p_retcode number;
p_errbuf varchar2(100);
m_mailerid fnd_svc_components.component_id%TYPE;
begin
-- Find mailer Id
-----------------
select component_id
into m_mailerid
from fnd_svc_components
where component_name = 'Workflow Notification Mailer';
--------------
-- Stop Mailer
--------------
fnd_svc_component.stop_component(m_mailerid, p_retcode, p_errbuf);
commit;
end;
/

3. Start notification mailer
sqlplus apps/

declare
p_retcode number;
p_errbuf varchar2(100);
m_mailerid fnd_svc_components.component_id%TYPE;
begin
-- Find mailer Id
-----------------
select component_id
into m_mailerid
from fnd_svc_components
where component_name = 'Workflow Notification Mailer';
--------------
-- Start Mailer
--------------
fnd_svc_component.start_component(m_mailerid, p_retcode, p_errbuf);
commit;
end;
/


TO configure workflow
Workflow Mailer Notification settings.
Log on to OAM
Click on Workflow Administrator -> Business Event Local System
Change VIS.ABC.COM to PROD.ABC.COM

Click on Workflow Manager ->Notification Mailer -> Workflow Notification Mailer -> Edit
Edit outbound Email Account (SMTP) -> Server Name =Concurrent Tier
IMAP Server -> Server Name = xxx.xxx.x.xx
Username/password: wfvis/xxxxx :
Reply-To Address: wfvis@abc.com

Click on Advance -> Next->Next
Under General Tab
Mailer Node =WFVIS
Under IMAP: Enter server IP address, username and password of wfvis
Under Outbound Email Account
Outbound Server Name= concurrent tier
Click Next –>Next….Save and Apply

Workflow Version with Apps
Connect to Database as apps user
SQL> select TEXT Version from WF_RESOURCES where NAME = ‘WF_VERSION’;
Output like 2.6.0 means workflow version 2.6.0


Workflow logfile location
$APPLCSF/$APPLLOG with filename like FNDCPGSC[pid].txt

After executing autoconfig make sure Workflow System Administrator is NOT set to SYSADMIN .
Please set this to ""Workflow Administrator Web (New)""
Following script will take care of this .

sqlplus apps/""pwd""
SQL> update wf_resources set text = 'FND_RESP|FND|FNDWF_ADMIN_WEB_NEW|STANDARD' where name = 'WF_ADMIN_ROLE';

1 row updated.

SQL> commit;

Commit complete.

or xml changes can be done link this.
$ grep -i s_wf_admin_role PROD_mdsxaorit.xml
username oa_var=""s_wf_admin_role"">FND_RESP|SYSADMIN|SYSTEM_ADMINISTRATOR|STANDARD


To set the Workflow Administrator from Sys Admin to Workflow Administrator
Navigate to Responsibility -- Workflow Administarator
then Administrator Workflow -- Administration

On top we will find Workflow Configuration :

Workflow System Administrator :: This value we need to change to Workflow Administrator

Or we can update from backend
Update wf_resources set text='FND_RESP|FND|FNDWF_ADMIN|STANDARD' where name = 'WF_ADMIN_ROLE';

Or can be set in xml,
grep -i s_wf_admin_role TRAIN2_vcosxaor09.xml username oa_var=""s_wf_admin_role"">FND_RESP|FND|FNDWF_ADMIN|STANDARD


modify this profile option to have the value of an actual App Server
WF: Workflow Mailer Framework Web Agent : http://hostname.domainname:8000

Make sure following parameters are set for Workflow :
As system administrator –
Oracle Applications Manager
Workflow Manager

Inbound Server Name wfmailer.domain.com
Outbound Server Name wfmailer.domain.com
From The lenovo PROD Workflow Mailer
Reply-to Address wfvis@domain.com


Workflow smtp port 25 and imap port 143
[root@hostname]# telnet wfmailer 143

Tuesday, 22 May 2012

Performance Degradation when the Workflow Background Process is Running

Performance Degradation when the Workflow Background Process is Running [ID 743338.1]
Modified 21-JUL-2010 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References

Applies to:

Oracle Workflow Cartridge - Version: 11.5.10.0 to 12 - Release: 11.5 to 12
Information in this document applies to any platform.
Checked for relevance on April 21st 2010
FNDWFBG - Workflow Background Process
Symptoms

When the Workflow Background Process concurrent program is running, you notice a degradation of e-business suite performance. In the meantime, the database diagnostic script STATSPACK reports a very high number of Buffer Gets done by FNDWFBG module.

STATSPACK output shows FNDWFBG module as the top performer of Buffer Gets:

----------------------------------------------------------------

SQL ordered by Gets for DB:
Buffer Gets Executions Gets per Exec %Total Time (s) Time (s) Hash Value
--------------- ------------ -------------- ------ -------- --------- ----------
35,914,812 22 1,632,491.5 99.3 62.32 60.92 2076298416
Module: FNDWFBG
BEGIN WF_ENGINE.BACKGROUNDCONCURRENT( :errbuf, :rc,:A0,:A1,:A2,:
A3,:A4,:A5); END;

35,838,763 22 1,629,034.7 99.1 61.74 60.34 2254475455
Module: FNDWFBG
SELECT /*+ ORDERED USE_NL (WIASP WI WPAP WAP) INDEX
(WIASP WF_ITEM_ACTIVITY_STATUSES_N1) */ WIASP.ROWID ROW_ID FROM
WF_ITEM_ACTIVITY_STATUSES WIASP, WF_ITEMS WI, WF_PROCESS_ACTIVIT
IES WPAP, WF_ACTIVITIES WAP WHERE WIASP.ITEM_TYPE = :B2 AND WIAS
P.PROCESS_ACTIVITY = WPAP.INSTANCE_ID AND WPAP.ACTIVITY_ITEM_TYP
--------------------------------------------------------------------------------
Cause

The issue is caused by the following:

Workflow Background Process is launched every minute with the following parameters:

- Item Type=NULL
- Minimum Threshold = NULL
- Maximum Threshold = NULL
- Process Deferred = Y
- Process Timeout= Y
- Process Stuck = Y

Unpublished bug 5016036 "WF: HIGH BUFFER GETS IN FNDWFBG MODULE" explains that running the Workflow Background Process with "Process Stuck = Y" is extremely expensive and consequently this should be done sparingly.

This means the Workflow Background Process should run with parameter "Process Stuck = Y" much less frequently than the Workflow Background Process with parameter "Process Deferred = Y" or "Process Timeout = Y".

Solution

To implement the solution, please execute the following steps:

1) Using System administrator responsibility, navigate to Concurrent\Requests form.

2) In this screen, remove the scheduling for the existing Workflow Background Process.

3) Still using this screen, schedule a new Workflow Background Process to be executed every 5 minutes with the following parameters:
- Item Type = NULL
- Minimum Threshold = NULL
- Maximum Threshold = NULL
- Process Deferred = Y
- Process Timeout = N
- Process Stuck = N

This Workflow Background Process will run every 5 minutes and will process only the deferred activities.

4) Then schedule a new Workflow Background Process to be executed every 60 minutes with the following parameters:
- Item Type = NULL
- Minimum Threshold = NULL
- Maximum Threshold = NULL
- Process Deferred = N
- Process Timeout = Y
- Process Stuck = N

This Workflow Background Process will run every 60 minutes and process only the timed out workflow activities.


5) Schedule a new Workflow Background Process to be executed every week with the following parameters:
- Item Type = NULL
- Minimum Threshold = NULL
- Maximum Threshold = NULL
- Process Deferred = N
- Process Timeout = N
- Process Stuck = Y

This Workflow Background Process will run once a week and process only the stuck workflow processes. In addition it is better to schedule it so it runs when the load on the system is low.


Note: if a given item type has very high volumes of deferred activities to process, in addition to the above scheduling you may need to schedule an additional Workflow Background Process to handle the deferred activities of this item type.

Friday, 4 May 2012

Oracle Applications 11i eBusiness Suite DBA

AD Utilities Overview


AD Utilities (abbreviation from Applications DBA) are programs which perform a variety of tasks, including generating files, updating your system, merging and applying patches, installing off-cycle products.  

These AD Utilities are executable files in $AD_TOP/bin



Utility
Executable/ Interface
Role
AD Administration
adadmin
Oracle Application Manager 
Performs maintenance tasks on the Oracle Applications file system and database.
AutoPatch 
adpatch
Applies patches to the Oracle Applications and Oracle database (also you can add new languages and products as a patch).
AD Controller
adctrl
Which this utility you can restart, see the status of parallel workers in AutoPatch, AD Administration and AutoUpgrade.
AutoUpgrade
adaimgr
Upgrades your database code and objects from an old version to the last 11i version. This is a time consuming step. 
AD Relink
adrelink
Used to re-link apps executables with product libraries. This must be done if some library definition is changed or an executable is corrupted.
AD Merge Patch
admrgpch
Used to merge multiple patches into a single one. This is useful when we have to apply many patches to reduce the patching time.  
AD Splicer
adsplice
Used to register the off-cycle products (a new oracle released product which is not delivered with the initial package). 
File Character Set Converter
adncnv
Used to convert a file from one character set to another.
AD Configuration
$AD_TOP/sql/adutconf.sql
Shows information about the installed configuration of the APPS. 
AD Job Timing Report
$AD_TOP/admin/sql/adtimrpt.sql
Shows timing statistics about the parallel workers. 
AD File Identification
adident
Shows the header file of one Oracle Application file. In the header we can see the version and the timestamp of the file.  
License Manager
Oracle Application Manager
Licenses products, country-specific functionalities or languages.

Thursday, 3 May 2012

Configure the Account Analysis Report in SLA/GL :
 
In R12 the Account Analysis Report in applications Subledger Accounting
and General Ledger, have been completely written as XML Publisher programs. The data is extracted and generated into XML format using a Data Template extract via the JAVA program XDODTEXE.
The layout is then generated using the Output Post Processor concurrent manager. The problem for users of these reports is that they generate very large data sets so the Release 12 instance needs to be configured to handle these large programs.

A. Set the Scalable Option to on for these programs.
This prevents this error in the Subledger Accounting program's log:
Calling XDO Data Engine...
****Warning!!! Due to high volume of data, got out of memory exception...***
****Please retry with scalable option or modify the Data template to run in scalable mode...***
1. As System Administrator: Navigate to Concurrent->Program->Define.
2. Query up the report: Account Analysis Report
(do this for both the General Ledger and the Subledger Accounting program definitions).
3. Add a parameter:
ScalableFlag.
Value set should be yes_no
Default value should be Y.
Select checkboxes Enable and Required.
Do not select the check box Displayed, or users could turn this off at runtime.
Token needs to be ScalableFlag (this is a case sensitive value).

B. Configure the XML Publisher Administrator Configuration settings.
This prevents "java.lang.OutOfMemoryError" errors in the Output Post Processor log associated to the Subledger Accounting program.

1. As XML Publisher Administrator navigate to Administration->Configuration.
2. Under Temporary Directory pick a temporary file location on your concurrent processing node. This should be at least 5GB or 20x larger than largest XML data file you generate.
3. Under FO Processing:
Use XML Publisher's XSLT processor set to True
Enable scalable feature of XSLT processor set to False
Enable XSLT runtime optimization set to True

C. Configure the Output Post Processor's JVM.
These steps set the JVM to 2GB, depending upon your server's size you might find 3 GB (-mx3072m), 4GB (-mx4096m) or even 5GB (-mx5120m) is a better value. This setting prevents the error "java.lang.OutOfMemoryError: Java heap space" in the Output Post Processor's log associated to the Subledger Accounting Program.

1. Login to SQL*Plus as APPS.
2. SQL>update FND_CP_SERVICES set DEVELOPER_PARAMETERS =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2048m'
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');
3. Bounce the concurrent managers.

D. Test the reports.

Basic Steps to Enable Multi-Org

Define the Organization Structure.
=============================================================
Plan and define the entities in your organizational structure.A successful implementation of Multiple Organization Support in Oracle Applications primarily depends on correctly defining your organization structure in the hierarchy used by Oracle Applications. A careful analysis and design of a company’s organization structure is critical for future success.
===================================================================
The following points describe how the Multi-Org model relates organizations:
=============================================================
• A Business Group is the highest level of the structure and has no accounting impact.The Business Group determines which employees will be available to Sets of Books and Operating Units related to that Business Group.
• Set of Books is the highest level which impacts the accounting side of business.
• Set of Books is associated with a single Business Group, multiple Sets of Books may be associated with a single Business Group.
• Each Set of Books may have a different chart of accounts structure, calendar, or functional currency.
• Each Legal Entity is associated with a single Set of Books, multiple Legal Entities may be associated with a single Set of Books.
• Each Operating Unit is associated with a single Legal Entity, multiple Operating Units may be associated with a single Legal Entity.
• An Inventory Organization may be associated with any Operating Unit within the same Set of Books.
===============================================================
Convert to Multi-Org:
===============================================================
After defining at least one operating unit, use ADADMIN to convert to Multi-Org. This step only needs to be perform one time. After ADADMIN is run, the Seed Data Replication program copies the applicable setup data delivered with Oracle Applications for each defined operating unit. If you add additional operating units, you can run the See Data Replication program manually at any time. Note that seed data is only data that comes with the database and does not include any operating unit specific setups you may perform.Run ADADMIN to Convert to Multiple Org
• When you select the adadmin option, Convert to Multiple Organization architecture, the Multi-Org switch is automatically turned on; a flag called multi_org_flag, is set to Y. The seed data replication program is then executed and processes according to the value of the multi_org_flag.
Run Seed Data Replication Seed data is replicated under the following circumstances:
• Submit the Replicate Seed Data concurrent request using the System Administrator responsibility.
The seed data replication program works in two modes:
• Single organization: This mode applies when the seed data replication program is executed within the context of a particular operating unit (or Org_ID).
• All organizations: This mode applies when the seed data replication program is executed without an operating unit context.
===================================================================
The following steps are required to add new operating units to your Organizational Structure:
=============================================================
• Revise the Organization Structure
• Define Sets of Books (optional)
• Define Organizations and Relationships
• Define Responsibilities
• Set Profile Options for each Responsibility
• Define Inventory Organization Security (optional)
• Implement the Application products
• Secure Balancing Segment Values (optional)
• Run the Setup Validation Report (recommended)
• Implement Document Sequencing (optional)
• Define Intercompany Relations (optional)