Why Does Release Management (RLM) Inbound Transactions (830, 862, 866) 830 Error Out With ORA-28115? (Doc ID 780944.1)

Solution

As per Reference: Bug.7676767 (32) RLM INBOUND TRANSACTIONS
ERROR ORA-28115 POLICY WITH CHECK OPTION VIOLATION.:

Please perform the below action in the TEST Instance:
.
A. Run the concurrent program "Seed Data Reconciliation" for SPSI, SSSI and PSQI transactions.

Please ensure that all the parameters are set to No for this concurrent program. As a result of this, the seeded code conversion categories get wiped out.
.
B. Now compile the below script present in RLM_TOP.

$RLM_TOP/patch/115/sql/RLMCDCTG.sql.
Above script will setup the code conversion categories for SPSI, SSSI and PSQI transaction. Which will re-seed the code conversion categories.

C. Once the script is compiled successfully, now run the RLM inbound transaction for SPSI/SSSI/PSQI flat file again and see if the concurrent program completes successfully.


Thanks
Srini

11.5.10/12: How To Deploy Custom JSP and JAR files for Oracle iStore? (Doc ID 468181.1)

Solution

JSP FILES

• The jsp pages should be deployed in $OA_HTML

CLASS FILES

• The iStore related class need to be deployed in $JAVA_TOP/oracle/apps/ibe
• Other product related files can be deployed in their respective product directories under $JAVA_TOP/oracle/apps/

JAR FILES

• R12:
  
  Edit $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/orion-application.xml
  Add an entry like this:
       <library path="/<your directory>/customstore.jar" /> If you plan to use "ojspCompile.pl" script to manually compile your custom JSP files, then edit $INST_TOP/appl/admin/ojspCompile.properties
  Add an entry like this
           /<your directory>/customstore.jar
  
• 11i:
  Edit $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.properties
  Add an entry like this:
           wrapper.classpath=<your directory>/customstore.jar

Thanks
Srini

Tips For Personalizing The E-Business Suite R12 Login Page (MainLoginPG)

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=214369544658003&parent=DOCUMENT&sourceId=732970.1&id=741459.1&_afrWindowMode=0&_adf.ctrl-state=6ssc3aqr2_102

Solution

1. Main attributes of the login page
In Release 12, the attributes of the login page are controlled thru the Framework personalizations.
To change them one can either:
  Enable the Personalize Region links by setting the 'Personalize Self-Service Defn' profile option to 'Yes' at Site level (or at user level for
GUEST user) then click on the desired links on the login page
  or:
  Go to 'Functional Administrator' responsibility => choose 'Personalizations' tab and enter the value
"/oracle/apps/fnd/sso/login/webui" in the 'Document Path' field then click on the Go button.
The document names available are:

/oracle/apps/fnd/sso/login/webui/MainLoginPG
/oracle/apps/fnd/sso/login/webui/loginRG
/oracle/apps/fnd/sso/login/webui/loginRN
/oracle/apps/fnd/sso/login/webui/LangImagesRN 
   Click on the pencil icon (Personalize Page) for the document you want to change. The 'Choose Personalization Context' will be displayed. Click on the 'Apply' button to display the personalization page. It will show the personalization structure and the item attributes. Select 'Complete View' radio button and click on the 'Expand All' link. At this stage one can choose the desired item attribute. Click on the pencil icon to edit.

a. Login zone
(document names: /oracle/apps/fnd/sso/login/webui/loginRG , /oracle/apps/fnd/sso/login/webui/loginRN)
The following table lists the attributes that you can change:

Attribute
Image: (corporateBrandingImage)
Image: people image
Image: globalTop image
Image: global image
Message Text Input: User Name
Message Text Input: Password
Submit Button: Submit
Submit Button: Cancel
Message Styled Text: Forgot your password
Message Styled Text: Register Here
Message Choice: Accessibility

One can edit the properties of an attribute. For instance, if one doesn't want an attribute to be displayed, set the property 'Rendered' to false (e.g. Cancel button or Accessibility field). 

b. Language zone
(document name: /oracle/apps/fnd/sso/login/webui/LangImagesRN)
For instance if one has one language and don't want to display this zone, then change the property 'Rendered' to false for the 'Table Layout'.

2. Message texts
A message text is used for certain attributes. The "Tip Message Name" property allows you to change
the message name and use a customized message. Please note that is considered as customization andmay be reverted by patches delivering new messages.

Below are the messages, with default value, used in the login page:

Message Name	Value
FND_SSO_USERNAME	User Name
FND_SSO_HINT_USERNAME	(example: michael.james.smith)
FND_SSO_PASSWORD	Password
FND_SSO_HINT_PASSWORD	(example: 4u99v23)
FND_SSO_FORGOT_PASSWORD	Login Assistance
FND_SSO_REGISTER_HERE	Register here

To change the value of a standard message:

1. Go to "Application Developer" responsibility
2. Select "Messages" from the menu
3. Query the message name (e.g. "FND_SSO_USERNAME") then change the message text
   in the "Current Message Text" field from "User Name" to "User" (as example).
4. Save changes and exit
5. Clear cache and bounce Apache to see the change

3. Corporate branding logo
The profile option "Corporate Branding Image for Oracle Applications" controls the
corporate branding image "ORACLE" displayed at the top of all OA Framework pages.
If no value is set for this profile, OA Framework renders the default corporate branding image
by using the $OA_MEDIA/FNDSSCORP.gif file.

If one changes the value of this profile with the name of the custom image file, it is recommended to keep the standard size
i.e. 155*20 pixels for the image. The new company logo will be displayed in all pages except in the login page because the "FNDSSCORP.gif " file name is hard coded in MainLoginPG.xml.

Hence if one wants to change the corporate branding image with a different logo and thus in all pages including the login page the simplest solution is to:

a. Rename the FNDSSCORP.gif file for backup
b. Edit the FNDSSCORP.gif with your preferred graphic software
c. Log out and log into the Applications
d. One should see the new logo at the top of all the page (including the login page)

In case one wants a different logo for the login page then the only (non supported) solution consists in editing the $FND_TOP/mds/sso/login/webui/MainLoginPG.xml file,

from:

<oa:image id="corporateBrandingImage" source="/OA_MEDIA/FNDSSCORP.gif" />

to:

<oa:image id="corporateBrandingImage" source="/OA_MEDIA/<your file name>" />

Of course one will need to import the customized MainLoginPG.xml into the MDS repositoryusing the XMLImporter tool (please review Note 344204.1  for the exact command line). 

You may also need to change the background color or motif of the top banner displaying the logo image.
For this modify the $OA_HTML/cabo/images/swan/headerBg.jpg to your own image and colors (the size is 1450*100 pixels)

4. Footer
Different elements are displayed at the bottom of the page:

About this page
- Go to System Administrator responsibility => Profile => System
- Change the value of 'FND: Diagnostics' profile option to "Yes" to display this link.


Privacy Statement and Copyright

As per Oracle's Privacy and Security policy, customers deploying Oracle Applications should add a Privacy Statement of their own.
If Oracle's Privacy Statement exists, it should be removed or replaced with the Company's own Privacy Statement.

You can do it using either of the following:
Using Functional Administrator

a. Select Functional Administrator responsibility
b. Click the Personalization tab
c. In Document Path, enter /oracle/apps/fnd/framework/webui/OAFooter
d. Click the Go button
e. Click the Personalize Page (pencil icon)
f. Click the Apply button
g. Select Personalize (pencil icon) in "Link: Privacy Statement"
h. In the this page "Personalize Region: Standard Footer" you can change the item Privacy (Destination URI and Text properties)
and the item Copyright (Prompt property)
i. Make sure "Rendered" is set to true, or to Remove the Privacy Statement, set the 'Rendered' property to 'False' at required level
j. Click Apply button
k. Logout

Using Personalize Page link

a. Set system profile "Personalize Self-Service Defn" to Yes
b. Use the Functional Administrator to clear the java cache as documented in Note: 742107.1 - reference: To clear middle tier cache in release 12:
c. Click the Personalize Page link
d. Click on the Choose Context button.
e. In the Scope LOV, select OA Footer
f. Click the Apply button
(the document name should be/oracle/apps/fnd/framework/webui/OAFooter)
g. Select Personalize (pencil icon) in "Link: Privacy Statement"
h. In the this page "Personalize Region: Standard Footer" you can change the item Privacy (Destination URI and Text properties)
and the item Copyright (Prompt property)
i. Make sure "Rendered" is set to true, or to Remove the Privacy Statement, set the 'Rendered' property to 'False' at required level
j. Click Apply button
k. Logout

You may also need to change the background color or motif of the bottom banner displaying the links.
For this modify the $OA_HTML/cabo/images/swan/footerBg.jpg to your own image and colors.
Note that these changes will apply on all pages.

5. Entering custom text with html code on login page for R12
To add text at the end of the login screen and before the footer, do the following:
a. Click on 'Personalize Table Layout' on the login page.
b. Under 'Personalization Structure', enable the radio button for 'Complete View' and click on 'Expand All'.
c. On the 'Cell Format: (region24)', click on the 'Create Item'.
d. Under 'Item Style' choose 'Raw Text'.
e. Enter the 'ID' and the 'Text'.  In 'Text', one can use <BR> for a carriage return.
f. Return to the application and view.

6. Other modifications
Using JDeveloper tool you can create Framework Extensions or own messages in the Messages Dictionary thru AOL responsibility, etc. This is considered a customization and thus not supported by Oracle.

Warning: the Login page being an access to E-Business Suite, be careful when doing personalizations and customizations.

 

Thanks

Srini

How to Map Source Files to Templates (Programmatic Access Names) in Oracle iStore?

Goal

The purpose of this document is to describe how to map source files to templates (Programmatic Access Names) in Oracle iStore.

Solution

A template is just a simple way to get the correct source file according to a couple of parameters, site and language.
When iStore users select a site or a language, or even if these get defaulted, iStore displays some jsp files according to those parameters. Templates can have more than one jsp file, and each file can use one or more combination of these parameters, but this combination of site and language cannot be used by any other file mapped to the template. iStore evaluates which source file to use from the most detailed parameters to the most genric option (All sites and All languages)

Example
If a custom jsp file (xxx_ibeCCtdTop.jsp) is mapped to STORE_CTLG_TOP_PAGE template with parameters: All Sites and US language, means that no other file can be mapped to STORE_CTLG_TOP_PAGE with those options.

If you try to map a custom file with a combination of parameters that is being used by other file you will get an error like the following one
Error

Error in saving logical to physical mapping 

1. Error in saving logical to physical mapping 
2. ORA-00001: unique constraint (IBE.IBE_DSP_LGL_PHYS_MAP_U2) violated in Package IBE_PhysicalMap_GRP Procedure save_physicalmap 
3. All sites and all language exists already exists for deliverable 7672 

Most of the templates have a seeded jsp file which uses the All site and All language combination, this mapping cannot be deleted, so you cannot use that combination  for these cases.


To map a file do as follows:

1. Responsibility: iStore Administrator
2. Navigation: Advanced > Template Manager
3. Search for the template
4. Click on Update
5. Then on Add Source File
6. Fill in the details
• Source File Name
• Description
7. Add the required combination of sites and languages
8. Save the changes
9. Bounce Apache (11i) or Oacore (R12)

The following SQL query will provide details about a source file or programmatic access name.

SELECT m.access_name,
m.file_name,
m.site_id,
DECODE(m.site_id, 1, 'All', s.msite_name) site_name,
m.default_msite,
m.language_code,
m.default_language
FROM IBE_DSP_ATTACHMENTS_V m, ibe_msites_tl s
WHERE m.site_id = s.msite_id
AND 'file_or_access_name' IN (access_name, file_name);

 

Thanks

Srini

How To Generate a Database Trace for Oracle iStore?11.5.10/12:

Goal

The purpose of this document is to describe how to gather database trace files from Oracle iStore application to debug a performance issue (for example, order submit flow) or to trace sql statement executed for a particular iStore flow (for example, sql statement along with bind variables used by iStore catalog search).

Solution

1. Login to iStore

2. Go to a point where you are ready to reproduce the issue, but just before that, enable trace as follows:

2.1. Login to EBS Apps Login as SYSADMIN or user with access to System Profile Form
2.2. Responsibility: System Administrator
2.3. Profile > System

Profile =  Initialization SQL Statement - Custom
Level = User (iStore user)
Value (This is one line and all single quotes):

begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG', 'ALTER SESSION SET EVENTS=''10046 TRACE NAME CONTEXT FOREVER, LEVEL 12'' tracefile_identifier=''ISTORET1'' max_dump_file_size=''unlimited'''); end;

IMPORTANT:
* Do NOT use "-" (hyphen) in the tracefile_identifier value. For example, tracefile_identifier=''ISTORE-T1'' is NOT valid.
* Please provide a unique tracefile_identifier value for each iteration of testing. Replace "'ISTORET1" with your own identifier that helps identifies trace files relevant for your test case.

3. Reproduce the issue in iStore

4. Erase the profile "Initialization SQL Statement - Custom" value set on iStore user level to stop the trace
This is an IMPORTANT step.

5. Locate the trace file in Unix on database node as follows:

location:SQL> select value from v$parameter where name = 'user_dump_dest'

file name:In step 2.3, if tracefile_identifier=''ISTORET1'', then you can check for file name:
$ ls -ltr *ISTORET1*.trc

NOTE: There may be more than one trace file generated for the flow, we need all files

6. tkprof using below syntax:

tkprof <filename.trc> <output_filename> sys=no explain=apps/<apps_password> sort='(prsela,exeela,fchela)'

7. Upload both raw and tkprof'd files in a zip file
IMPORTANT: raw trace file size may be too large, so please make sure you zip them before upload.

Thanks
Srini