Embed Size (px)
Citation preview
ltInsert Picture Heregt
Understanding Technical Configuration of OSSSession 23671 March 14 2007Carlton Stroud Principal Product ManagerMaxine Chan Principal Product ManagerSimran Sawhney Senior Manager Student System Development
ltInsert Picture Heregt
Agenda
bull Personalization within Student Systembull Discoverer use for Dynamic PIGsbull One-to-One Fulfillment for Correspondencebull New User Registrationbull Appendix
ltInsert Picture Heregt
Personalization in Student System
Agenda
bull Levels of Personalizationbull Profile Optionsbull Troubleshooting Tips
Levels of Personalization
bull Functionbull Lowest levelbull Used solely in Admission for OSSbull Define a function and tie it to a menubull Menu is tied to responsibility
bull Responsibilitybull Organizationbull Site
bull Highest level
Profile Options
bull Turn on Personalizationbull Profile name Personalize Self-Service Defn
(FND_CUSTOM_OA_DEFINTION)bull Enables the option to Personalize on a page bull What responsibility or who has ability to personalize
bull Disable Personalizationbull Profile name Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS)bull Overrides the Personalization done Enables the default
behavior of the UIbull Helpful to development for determining if the personalization
causes the issue
Troubleshooting Tips
bull Issue Self-service page errors out after applying personalizationbull Set Profile option Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS) to lsquoNorsquo and see if page still errors out
bull Issue Default values are not showing up in self-servicebull Probable reason The wrong value is entered in the
personalization pagebull Verify Profile option FND OAEnable Defaults
(FND_OA_ENABLE_DEFAULTS) is set to lsquoYesrsquo
Troubleshooting Tips continued
bull Issue Link does not open in new pagewindowbull If the style of the item is of type link then set
Destination URI = httpltRequiredAddressgt For example httpwwworaclecomTarget Frame = _blank
bull If the style of the item is of type Static Styled Text then setbull Destination URI =
javascriptvoid(windowopen(httpltRequiredAddressgt))For example javascriptvoid(windowopen(httpwwworaclecom))For example javascriptvoid(windowopen(httpwwworaclecomnewtoolbar=nolocation=no directories=no status=no menubar=yes scrollbars=yes resizable=nowidth=400 height=400))
Troubleshooting Tips continued
bull Issue I am unable to personalize the menu sidebarbull Personalizing the menu sidebar is not an option bull Only supported through custom menu creation
bull Issue How do I delete Personalizationsbull Approach 1 Standard Personalization Page
bull Use lsquoClear Personalizationrsquo buttonbull Approach 2 Using a Script
bull Login to SQLPLUSbull Set servereoutput on exec
Jdr_utilslistCustomizations(lsquooracleappsigspersoncomponentswebuiPersSecInstEduInfoRN)
bull Exec jdr_utilsdeleteDocument(lsquoltxxxgtrsquo) commit
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
ltInsert Picture Heregt
Agenda
bull Personalization within Student Systembull Discoverer use for Dynamic PIGsbull One-to-One Fulfillment for Correspondencebull New User Registrationbull Appendix
ltInsert Picture Heregt
Personalization in Student System
Agenda
bull Levels of Personalizationbull Profile Optionsbull Troubleshooting Tips
Levels of Personalization
bull Functionbull Lowest levelbull Used solely in Admission for OSSbull Define a function and tie it to a menubull Menu is tied to responsibility
bull Responsibilitybull Organizationbull Site
bull Highest level
Profile Options
bull Turn on Personalizationbull Profile name Personalize Self-Service Defn
(FND_CUSTOM_OA_DEFINTION)bull Enables the option to Personalize on a page bull What responsibility or who has ability to personalize
bull Disable Personalizationbull Profile name Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS)bull Overrides the Personalization done Enables the default
behavior of the UIbull Helpful to development for determining if the personalization
causes the issue
Troubleshooting Tips
bull Issue Self-service page errors out after applying personalizationbull Set Profile option Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS) to lsquoNorsquo and see if page still errors out
bull Issue Default values are not showing up in self-servicebull Probable reason The wrong value is entered in the
personalization pagebull Verify Profile option FND OAEnable Defaults
(FND_OA_ENABLE_DEFAULTS) is set to lsquoYesrsquo
Troubleshooting Tips continued
bull Issue Link does not open in new pagewindowbull If the style of the item is of type link then set
Destination URI = httpltRequiredAddressgt For example httpwwworaclecomTarget Frame = _blank
bull If the style of the item is of type Static Styled Text then setbull Destination URI =
javascriptvoid(windowopen(httpltRequiredAddressgt))For example javascriptvoid(windowopen(httpwwworaclecom))For example javascriptvoid(windowopen(httpwwworaclecomnewtoolbar=nolocation=no directories=no status=no menubar=yes scrollbars=yes resizable=nowidth=400 height=400))
Troubleshooting Tips continued
bull Issue I am unable to personalize the menu sidebarbull Personalizing the menu sidebar is not an option bull Only supported through custom menu creation
bull Issue How do I delete Personalizationsbull Approach 1 Standard Personalization Page
bull Use lsquoClear Personalizationrsquo buttonbull Approach 2 Using a Script
bull Login to SQLPLUSbull Set servereoutput on exec
Jdr_utilslistCustomizations(lsquooracleappsigspersoncomponentswebuiPersSecInstEduInfoRN)
bull Exec jdr_utilsdeleteDocument(lsquoltxxxgtrsquo) commit
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
ltInsert Picture Heregt
Personalization in Student System
Agenda
bull Levels of Personalizationbull Profile Optionsbull Troubleshooting Tips
Levels of Personalization
bull Functionbull Lowest levelbull Used solely in Admission for OSSbull Define a function and tie it to a menubull Menu is tied to responsibility
bull Responsibilitybull Organizationbull Site
bull Highest level
Profile Options
bull Turn on Personalizationbull Profile name Personalize Self-Service Defn
(FND_CUSTOM_OA_DEFINTION)bull Enables the option to Personalize on a page bull What responsibility or who has ability to personalize
bull Disable Personalizationbull Profile name Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS)bull Overrides the Personalization done Enables the default
behavior of the UIbull Helpful to development for determining if the personalization
causes the issue
Troubleshooting Tips
bull Issue Self-service page errors out after applying personalizationbull Set Profile option Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS) to lsquoNorsquo and see if page still errors out
bull Issue Default values are not showing up in self-servicebull Probable reason The wrong value is entered in the
personalization pagebull Verify Profile option FND OAEnable Defaults
(FND_OA_ENABLE_DEFAULTS) is set to lsquoYesrsquo
Troubleshooting Tips continued
bull Issue Link does not open in new pagewindowbull If the style of the item is of type link then set
Destination URI = httpltRequiredAddressgt For example httpwwworaclecomTarget Frame = _blank
bull If the style of the item is of type Static Styled Text then setbull Destination URI =
javascriptvoid(windowopen(httpltRequiredAddressgt))For example javascriptvoid(windowopen(httpwwworaclecom))For example javascriptvoid(windowopen(httpwwworaclecomnewtoolbar=nolocation=no directories=no status=no menubar=yes scrollbars=yes resizable=nowidth=400 height=400))
Troubleshooting Tips continued
bull Issue I am unable to personalize the menu sidebarbull Personalizing the menu sidebar is not an option bull Only supported through custom menu creation
bull Issue How do I delete Personalizationsbull Approach 1 Standard Personalization Page
bull Use lsquoClear Personalizationrsquo buttonbull Approach 2 Using a Script
bull Login to SQLPLUSbull Set servereoutput on exec
Jdr_utilslistCustomizations(lsquooracleappsigspersoncomponentswebuiPersSecInstEduInfoRN)
bull Exec jdr_utilsdeleteDocument(lsquoltxxxgtrsquo) commit
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Agenda
bull Levels of Personalizationbull Profile Optionsbull Troubleshooting Tips
Levels of Personalization
bull Functionbull Lowest levelbull Used solely in Admission for OSSbull Define a function and tie it to a menubull Menu is tied to responsibility
bull Responsibilitybull Organizationbull Site
bull Highest level
Profile Options
bull Turn on Personalizationbull Profile name Personalize Self-Service Defn
(FND_CUSTOM_OA_DEFINTION)bull Enables the option to Personalize on a page bull What responsibility or who has ability to personalize
bull Disable Personalizationbull Profile name Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS)bull Overrides the Personalization done Enables the default
behavior of the UIbull Helpful to development for determining if the personalization
causes the issue
Troubleshooting Tips
bull Issue Self-service page errors out after applying personalizationbull Set Profile option Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS) to lsquoNorsquo and see if page still errors out
bull Issue Default values are not showing up in self-servicebull Probable reason The wrong value is entered in the
personalization pagebull Verify Profile option FND OAEnable Defaults
(FND_OA_ENABLE_DEFAULTS) is set to lsquoYesrsquo
Troubleshooting Tips continued
bull Issue Link does not open in new pagewindowbull If the style of the item is of type link then set
Destination URI = httpltRequiredAddressgt For example httpwwworaclecomTarget Frame = _blank
bull If the style of the item is of type Static Styled Text then setbull Destination URI =
javascriptvoid(windowopen(httpltRequiredAddressgt))For example javascriptvoid(windowopen(httpwwworaclecom))For example javascriptvoid(windowopen(httpwwworaclecomnewtoolbar=nolocation=no directories=no status=no menubar=yes scrollbars=yes resizable=nowidth=400 height=400))
Troubleshooting Tips continued
bull Issue I am unable to personalize the menu sidebarbull Personalizing the menu sidebar is not an option bull Only supported through custom menu creation
bull Issue How do I delete Personalizationsbull Approach 1 Standard Personalization Page
bull Use lsquoClear Personalizationrsquo buttonbull Approach 2 Using a Script
bull Login to SQLPLUSbull Set servereoutput on exec
Jdr_utilslistCustomizations(lsquooracleappsigspersoncomponentswebuiPersSecInstEduInfoRN)
bull Exec jdr_utilsdeleteDocument(lsquoltxxxgtrsquo) commit
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Levels of Personalization
bull Functionbull Lowest levelbull Used solely in Admission for OSSbull Define a function and tie it to a menubull Menu is tied to responsibility
bull Responsibilitybull Organizationbull Site
bull Highest level
Profile Options
bull Turn on Personalizationbull Profile name Personalize Self-Service Defn
(FND_CUSTOM_OA_DEFINTION)bull Enables the option to Personalize on a page bull What responsibility or who has ability to personalize
bull Disable Personalizationbull Profile name Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS)bull Overrides the Personalization done Enables the default
behavior of the UIbull Helpful to development for determining if the personalization
causes the issue
Troubleshooting Tips
bull Issue Self-service page errors out after applying personalizationbull Set Profile option Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS) to lsquoNorsquo and see if page still errors out
bull Issue Default values are not showing up in self-servicebull Probable reason The wrong value is entered in the
personalization pagebull Verify Profile option FND OAEnable Defaults
(FND_OA_ENABLE_DEFAULTS) is set to lsquoYesrsquo
Troubleshooting Tips continued
bull Issue Link does not open in new pagewindowbull If the style of the item is of type link then set
Destination URI = httpltRequiredAddressgt For example httpwwworaclecomTarget Frame = _blank
bull If the style of the item is of type Static Styled Text then setbull Destination URI =
javascriptvoid(windowopen(httpltRequiredAddressgt))For example javascriptvoid(windowopen(httpwwworaclecom))For example javascriptvoid(windowopen(httpwwworaclecomnewtoolbar=nolocation=no directories=no status=no menubar=yes scrollbars=yes resizable=nowidth=400 height=400))
Troubleshooting Tips continued
bull Issue I am unable to personalize the menu sidebarbull Personalizing the menu sidebar is not an option bull Only supported through custom menu creation
bull Issue How do I delete Personalizationsbull Approach 1 Standard Personalization Page
bull Use lsquoClear Personalizationrsquo buttonbull Approach 2 Using a Script
bull Login to SQLPLUSbull Set servereoutput on exec
Jdr_utilslistCustomizations(lsquooracleappsigspersoncomponentswebuiPersSecInstEduInfoRN)
bull Exec jdr_utilsdeleteDocument(lsquoltxxxgtrsquo) commit
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Profile Options
bull Turn on Personalizationbull Profile name Personalize Self-Service Defn
(FND_CUSTOM_OA_DEFINTION)bull Enables the option to Personalize on a page bull What responsibility or who has ability to personalize
bull Disable Personalizationbull Profile name Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS)bull Overrides the Personalization done Enables the default
behavior of the UIbull Helpful to development for determining if the personalization
causes the issue
Troubleshooting Tips
bull Issue Self-service page errors out after applying personalizationbull Set Profile option Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS) to lsquoNorsquo and see if page still errors out
bull Issue Default values are not showing up in self-servicebull Probable reason The wrong value is entered in the
personalization pagebull Verify Profile option FND OAEnable Defaults
(FND_OA_ENABLE_DEFAULTS) is set to lsquoYesrsquo
Troubleshooting Tips continued
bull Issue Link does not open in new pagewindowbull If the style of the item is of type link then set
Destination URI = httpltRequiredAddressgt For example httpwwworaclecomTarget Frame = _blank
bull If the style of the item is of type Static Styled Text then setbull Destination URI =
javascriptvoid(windowopen(httpltRequiredAddressgt))For example javascriptvoid(windowopen(httpwwworaclecom))For example javascriptvoid(windowopen(httpwwworaclecomnewtoolbar=nolocation=no directories=no status=no menubar=yes scrollbars=yes resizable=nowidth=400 height=400))
Troubleshooting Tips continued
bull Issue I am unable to personalize the menu sidebarbull Personalizing the menu sidebar is not an option bull Only supported through custom menu creation
bull Issue How do I delete Personalizationsbull Approach 1 Standard Personalization Page
bull Use lsquoClear Personalizationrsquo buttonbull Approach 2 Using a Script
bull Login to SQLPLUSbull Set servereoutput on exec
Jdr_utilslistCustomizations(lsquooracleappsigspersoncomponentswebuiPersSecInstEduInfoRN)
bull Exec jdr_utilsdeleteDocument(lsquoltxxxgtrsquo) commit
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Troubleshooting Tips
bull Issue Self-service page errors out after applying personalizationbull Set Profile option Disable Self-service Personal
(FND_DISABLE_OA_CUSTOMIZATIONS) to lsquoNorsquo and see if page still errors out
bull Issue Default values are not showing up in self-servicebull Probable reason The wrong value is entered in the
personalization pagebull Verify Profile option FND OAEnable Defaults
(FND_OA_ENABLE_DEFAULTS) is set to lsquoYesrsquo
Troubleshooting Tips continued
bull Issue Link does not open in new pagewindowbull If the style of the item is of type link then set
Destination URI = httpltRequiredAddressgt For example httpwwworaclecomTarget Frame = _blank
bull If the style of the item is of type Static Styled Text then setbull Destination URI =
javascriptvoid(windowopen(httpltRequiredAddressgt))For example javascriptvoid(windowopen(httpwwworaclecom))For example javascriptvoid(windowopen(httpwwworaclecomnewtoolbar=nolocation=no directories=no status=no menubar=yes scrollbars=yes resizable=nowidth=400 height=400))
Troubleshooting Tips continued
bull Issue I am unable to personalize the menu sidebarbull Personalizing the menu sidebar is not an option bull Only supported through custom menu creation
bull Issue How do I delete Personalizationsbull Approach 1 Standard Personalization Page
bull Use lsquoClear Personalizationrsquo buttonbull Approach 2 Using a Script
bull Login to SQLPLUSbull Set servereoutput on exec
Jdr_utilslistCustomizations(lsquooracleappsigspersoncomponentswebuiPersSecInstEduInfoRN)
bull Exec jdr_utilsdeleteDocument(lsquoltxxxgtrsquo) commit
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Troubleshooting Tips continued
bull Issue Link does not open in new pagewindowbull If the style of the item is of type link then set
Destination URI = httpltRequiredAddressgt For example httpwwworaclecomTarget Frame = _blank
bull If the style of the item is of type Static Styled Text then setbull Destination URI =
javascriptvoid(windowopen(httpltRequiredAddressgt))For example javascriptvoid(windowopen(httpwwworaclecom))For example javascriptvoid(windowopen(httpwwworaclecomnewtoolbar=nolocation=no directories=no status=no menubar=yes scrollbars=yes resizable=nowidth=400 height=400))
Troubleshooting Tips continued
bull Issue I am unable to personalize the menu sidebarbull Personalizing the menu sidebar is not an option bull Only supported through custom menu creation
bull Issue How do I delete Personalizationsbull Approach 1 Standard Personalization Page
bull Use lsquoClear Personalizationrsquo buttonbull Approach 2 Using a Script
bull Login to SQLPLUSbull Set servereoutput on exec
Jdr_utilslistCustomizations(lsquooracleappsigspersoncomponentswebuiPersSecInstEduInfoRN)
bull Exec jdr_utilsdeleteDocument(lsquoltxxxgtrsquo) commit
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Troubleshooting Tips continued
bull Issue I am unable to personalize the menu sidebarbull Personalizing the menu sidebar is not an option bull Only supported through custom menu creation
bull Issue How do I delete Personalizationsbull Approach 1 Standard Personalization Page
bull Use lsquoClear Personalizationrsquo buttonbull Approach 2 Using a Script
bull Login to SQLPLUSbull Set servereoutput on exec
Jdr_utilslistCustomizations(lsquooracleappsigspersoncomponentswebuiPersSecInstEduInfoRN)
bull Exec jdr_utilsdeleteDocument(lsquoltxxxgtrsquo) commit
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Troubleshooting Tips continued
bull Approach 3 From the Applicationbull Responsibility Functional Administratorbull Navigation Personalization tab gt Application Catalog
Pagebull Enter full path of document
bull Eg oracleappsigspersoncomponentswebuiPersSecInstEduInfoRN
bull lsquoCheckrsquo Personalized checkboxbull Click Manage Personalizationsbull Lists of personalizations on documentbull Select the personalization and click delete
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Troubleshooting Tips continued
bull Issue Unable to recall personalization(s) donebull Approach 1 using a Script
bull Refer to discussions in Bug 3797701 to extract the various personalization done on a page
bull The extracted xml file will list the regions items properties that were personalized
bull Approach 2 using Applicationbull Set Profile Option FND Personalization Root Path
(FND_PERZ_DOC_ROTT_PATH)bull Navigate to
bull Functional Administratorbull Personalization tabgtImportExportgtPersonalization
Repository
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Troubleshooting Tips continued
bull Approach 2 continuedbull Document Path
bull oracleappsigspersoncomponentswebuicustomizationsresponsibilitiy
Orbull oracleappsigspersoncomponentswebuicustomizations
responsibility24762bull Select pages regions or packages to export
bull Select Export to File Systembull The file system will create the complete directorybull The file will not contain complete definition the region
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Troubleshooting Tips continued
bull Issue Can I add new itemsbull Items that do not have mapping to Database column
bull Static Styled Textbull Items that do have mapping to a Database column
bull A VO must be associated to the region bull To find VO
bull About This PagegtPage tabgtExpand the Page Definition Hgrid
bull Click link on VO object bull Check required that required attribute is present in VO
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
ltInsert Picture Heregt
Discoverer use for Dynamic PIGs
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Agenda
bull Architecturebull Basic Setupbull Commonly Encountered Issues
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Architecturebull Enable automatic extractionbull Trigger fires on workbook savebull Trigger looks for PLSQL function
(eul_trigger$post_save_document)bull Triggers executed by default in Discovererbull EUL trigger only executed if
bull PLSQL function registered correctlybull PLSQL arguments are defined appropriately
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Basic Setup
bull OSS Provides a trigger to be registered with Discoverer to extract Workbook SQLs for use in Dynamic Person ID Group
bull Names do matter please use the exact name and case
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Commonly Encountered Issues
bull Issue Cannot access discoverer workbook while creating Dynamic Person ID Group
Check the Discoverer function (eul_trigger$post_save_document)Check the OSS function (IGS_POST_SAVE_DOCUMENT) and the package (IGS_PE_DYNAMIC_PERSID_GROUP)Check the parameter names and their data type
Discoverer allows ONLY one PLSQL function to be registered witheul_trigger$post_save_document If there is already a registered function before registering OSS function Delete that registration and then register OSS functionFor OSS Discoverer use we suggest to create one worksheet per workbook only
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Commonly Encountered Issues (contd)
bull The Discoverer SQL should have either PERSON_ID or PARTY_ID in the SELECT clause Otherwise the SQL will not be extracted from Discoverer The extracted SQL is stored in IGS_PE_DYN_SQL
bull Discoverer stores the workbook information in EULltvergt_DOCUMENTS table (For Discoverer 4 edition its EUL4_DOCUMENTS for Discoverer 10g edition its EUL5_DOCUMENTS) This information is valuable in debugging
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Commonly Encountered Issues (contd)
bull Issue Discoverer attaches ALIASES to complex SQLs
bull Refer discussions in Bug 4279031 4523868 and 4894751
OSS Security is not enforced during creation of workbooks in Discoverer
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
ltInsert Picture Heregt
One-to-One Fulfillment for Correspondence
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Agenda
bull Architecturebull Basic Setupbull Fulfillment Server Scriptbull Fulfillment Server Log Filesbull Event Log Filesbull Debugging Techniquesbull Commonly Encountered Issues
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Architecture
bull All objects stored in IBC or JTF data modelbull Cover letter is referred as content item IBC data modelbull Transactions stored in JTF data model
bull OSS passes Content Item ID to JTF APIbull New Content Item created when letter is modified on
workbench the first time Subsequent modifications increases the version
bull Activities that submit new Fulfillment requestbull New correspondence request submittedbull Letter modified from the workbench page
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Basic Setup
bull Define new serverbull Define a groupbull Set profile lsquoIGS CRM User IDrsquo to a CRM User IDbull Set profile lsquoSign-On Audit Levelrsquo
bull lsquoNONErsquo then User ID set in lsquoIGS CRM User IDrsquo is usedbull If any other value entered then logged in user is considered
CRM User
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Fulfillment Server Script
bull Jtffmctlsh is used to startstop the 1-to-1 Fulfillment Server
bull Usagebull Jttfmctlsh startbull Jtffmctlsh stop
bull Key Information in the scriptbull ServerID Indicates the server to be startedbull DengineLogLevel=9 and ndashDdebug=full These values are set
to enable the FF server loggingbull LOG_DIR Points to the directory where the EventError log
files will be generatedbull JTTFFMLOG Points to the jtffmctltxt log file location
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Fulfillment Server Log Files
bull Eventslog Captures configurationSetup informationbull Errorslog Captures the error detailsbull Jtffmctltxt Is a summary of Events and Errors file
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Event Log Files
Key Information obtained from this filebull New requests demarcated with lsquodequeued from queuersquobull Media channels used eg Email Print Email amp Print etcbull JTF Item Content ID bull Recipient email address and Printer namebull Query used to fetch values for tokensbull Values used in merging with template in generating letterbull Merge delimiters (ltlt gtgt) used
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Debugging Techniques
bull Information in status tab can be used for basic troubleshootingbull Issue lsquoOutcomersquo column has a value of lsquoSubmittedrsquo
bull Probable Reason Server is either busy or Server is not running
bull Issue lsquoServer Namersquo column has a value of lsquoNullrsquo bull Probable Reason CRM User ID is no associated to
Fulfillment Serverbull Issue lsquoOutcomersquo column has a value of lsquoFailedrsquo
bull Debugging Approach Search for lsquoFF Request IDrsquo in the Errorslog and jtfmctltxt file for the errors
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Debugging Techniques continued
bull FND Logging and Exception stack tracesbull Valuable information for development team
bull Enable FND Loggingbull FND Debug Log Enabled = Yesbull FND Debug Log Level = Statementbull FND Debug Log Module =
bull Set profile lsquoFND Diagnosticsrsquo = lsquoYesrsquo
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Debugging Techniques continued
bull Once FND logging enabledbull Log information stored in database table
bull FND_LOG_MESSAGESbull Use query to fetch log information
bull SELECT module message_text FROM fnd_log_messages WHERE timestampgtsysdate-1 ORDER BY log_sequence DESC
bull View Log Information in Self-Service bull Click lsquoDiagnosticsrsquo linkbull Select lsquoShow log on screenrsquobull Select lsquoStatementrsquo for Log Levelbull Enter lsquorsquo for modulebull Click lsquoGorsquo
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Commonly Encountered Issues
bull Issue Preview Page shows 4lt0 errorbull Probable Reason(s)
bull Request is not yet processedbull Server encountered error while processing
bull Issue Tokens not getting merged with templatebull Debugging Approach
bull For Example Set following profiles to below valuesbull FND NATIVE CLIENT ENCODING = UTF8bull ICX Client IANA Encoding = UTF-8bull JTO Merge Delimiter Left = ltltbull JTO Merge Delimiter Right = gtgtbull JTO Merge Delimiter Left Encrypted = (bull JTO Merge Delimiter Right Encrypted = )
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
ltInsert Picture Heregt
R12 New User Registration
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
New User Registration
bull Background in 11ibull Online Admission Application Prospect Inquirybull Built using FND and OSS
bull Current in R12bull Replace infrastructure with UMX registration processbull OSS maintains UI and logic around New User Registration
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
User comes to University Website to request for an
application
User must then retrieve a UsernamePassword
User presented with Application Logon
User Clicks on Register Here link
User presented with Q if they have previously attended the institution
User answers Yes Go to
Former StudentAlumni flow
User answers No Go to
Applicant flow
New User Registration Flow
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
New User Registration
bull Registration UI and matching process built by OSSbull Creation of the user accountpassword uses UMX
(User Management System) APIsbull Links on Logon page supported through UMX
bull Application Logon can be placed on other web sites
bull Logon Assistance linkbull Forgot Passwordbull Forgot Username
bull Register Here linkbull Applicant flowbull Former StudentAlumni flow
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
New User Registration - Logon
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Account Registration ndash Applicant Flow
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Account Registration
bull First question drives the rendering of the SS pageflowbull Person Details region fields
bull OA Personalizations can be used to remove and make fields mandatory
bull Exception First Name Last Name Gender and DOB are mandatory to search for a person record bull LastFirst Name are mandatory to create a person record in TCA bull These fields cannot be removed nor remove the mandatory
validationbull Contact Details region fields
bull Email is mandatory in order for user to receive confirmation of user creation
bull Zip Code is used for matching
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Account Registration
bull User Name and Password region fieldsbull Let the user create their own username and passwordORbull Use your own algorithm to create usernamepassword for the
user
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Account Registration
bull Matchingbull No Person Record Match
bull Create Person and User ID recordbull Exact Person record Match
bull No User ID exists ndash Create User ID and link to User IDbull User ID exists ndash An error message is displayed to use the
Forgot Usernamebull Multiple Person Record Matches
bull Use Postal Code as additional attribute to determine if a better match bull If a match is made then the Exact Person record match
is usedbull If no multiple matches exist then a user is created
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Account Registration
bull Approval Processbull Can opt not to create the person record automatically A
workflow process can be used to route for approval
bull Assignment of Responsibilitiesbull At the time of the user creation responsibilities are assigned
based on the personrsquos person type assignmentbull When a person is created by default OSS assigns the person
type of ldquoOtherrdquobull Mapping of Person Type to Responsibilities
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Account Registration ndashFormer StudentAlumni Flow
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Account RegistrationFormer StudentAlumni Flow
bull If first question is answered Yes then the Person Details fields are rendered with different fields than in Applicant flow
bull Person Details regionbull All fields are mandatory and cannot be removedbull Person Number is added
bull Can choose to use any Personal Identifier for this field This is a profile option
bull Contact Details regionbull Add phone number as contact information for the
administrator if a username cannot be found or created
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Account RegistrationFormer StudentAlumni Flow
bull Matchingbull No Match
bull A notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
bull Exact Matchbull If a User ID exists then the responsibilities are assigned as
per the types associated to the person and the user is given a confirmation
bull If no User ID exists then the system will create a user ID and associate the person record to the User ID
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Account RegistrationFormer StudentAlumni Flowbull Multiple Matches
bull If there is a match to the zip code the User ID is associated to the person record
bull If there are no matches or multiple records a notification is sent to the administrator and a message is displayed to the user that no match is found and heshe will be contacted by email or phone
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
ltInsert Picture Heregt
Q U E S T I O N SA N S W E R S
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
ltInsert Picture Heregt
Appendix
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
Have you attended this institution
Yes No
User enters Person Person IDtype Last name First name
Gender DOB email address zipcode Phone number user
name and pwd User submit theapp
System checksto see whetherperson alreadyexist in system
Enter details (Title GenderNickname DOB Prefix Last
name Middle name Firstname Suffix Email address
ziip code user name andpassword User submit the
app
No match
System createperson andFND_user
System checksto see whether
postcode isentered
Multi
Records
Yes
No
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
System checksfor FND_user
record insystem
Exact Match
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
System checksto see whetherperson alreadyexist in system
No match
Send annotification toadmin Giveuser a msg
that theirrecord is notfound and an
admin willcontact you
System checksto see whether
postcode isentered
Multi
Records
System checksfor FND_user
record insystem
Exact Match
YesNo
Take user backto page andask user to
enter inpostcode and
re-submit
System checksto see whetherperson returns
exact match
No
No
Yes
Yes
Yes
No
Systemreturns a
msg - loginlink or forgetuser name
pwd flow
CreateFND_user
for theperson
Login Page
Registration
link
Forget User Nameand Password Flow
Forget Username
flow
ApplicantFormer
StudentsAlumni
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
References
bull Fulfillment Services Implementation Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115igpdf
bull Fulfillment Services User Guidebull httpdownload-
westoraclecomdocscdB25284_01currentacrobatamf115ugpdf
bull Oracle Discoverer Installation and Administration Guide
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
For More Information
httpsearchoraclecom
ororaclecom
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
bull THE PRECEDING IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION IT IS INTENDED FOR INFORMATION PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT IT IS NOT A COMMITMENT TO DELIVER ANY MATERIAL CODE OR FUNCTIONALITY AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISION THE DEVELOPMENT RELEASE AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR ORACLES PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE
