Blog

Integration of E-Business Suite R12 with Oracle Database Vault 11gR2

June 7th, 2010

Oracle Database Vault helps us address some of the most difficult security problems such as protecting against insider threats and enforcing separation of duties. It provides a number of flexible features that can be used to apply fine-grained access control to our sensitive data. Most importantly, it protects our data from super privileged users but still allows them to maintain our Oracle databases.

Currently R12 with Database Vault 11gR2 is certified on the following platforms –

  • Linux x86
  • Linux x86-64 (64-bit)
  • Oracle Solaris on SPARC (64-bit)
  • Oracle Solaris on x86-64 (64-bit)
  • Microsoft Windows Server (32-bit)
  • Microsoft Windows x64 (64-bit)
  • IBM AIX
  • HP-UX Itanium

Starting with 11g Release 2 Oracle Database Vault is included as an installed program with Oracle Database. To make it functional, one just needs to register it with the database. So, for using Database Vault 11gR2 with R12, we can upgrade our R12 database to 11gR2.

After we install Oracle Database Vault 11gR2, we must register it with the database and then create its accounts. Oracle recommends certain security-related initialization parameter settings to better secure our database configuration. Some of these parameters are already set in Oracle E-Business Suite Release 12 database by default, with the values that Oracle Database Vault recommends.

We can use Database Vault to audit SYS operations for the R12 database for which we need to set the “AUDIT_SYS_OPERATIONS” parameter to “True”.

For preparing E-Business Suite for the integration, we need to apply the R12 Realm Creation Patch. If we have multiple application tiers, we can apply this patch to any one application tier. This patch delivers the necessary scripts through which we can create Database Vault realms and manage Oracle E-Business Suite Release 12 integration with Oracle Database Vault.

Also, we need to apply a patch to get an update version of adgrants.sql that will run when database vault is enabled. Though for 12.1.1, this patch is not needed.

The next step is to create restrictions known as a Realm around Oracle E-Business Suite Release 12 product schemas, for which we need to run the fnddbvebs.sql script that comes with the Realm Creation Patch. Following are the default realms created by the script –

  • E-Business Suite Realm – Protects all tables in Oracle E-Business Suite Release 12 Product Schemas
  • E-Business Suite Realm – Applsys Schema – Protects most tables in the APPLSYS Schema
  • E-Business Suite Realm – Apps Schema – Protects all objects in the APPS Schema (except the views)
  • E-Business Suite Realm – Applsyspub Schema – Protects objects required for E-Business Suite authorization
  • E-Business Suite Realm – MSC Schema – Protects tables in the MSC Schema – except those that require partitions to be exchanged
  • CTXSYS Data Dictionary – Protects Objects in the CTXSYS Schema

This script also adds APPS, APPLSYS and CTXSYS users in the realm authorizations for the Oracle Data Dictionary realm. This realm is created by default when we install Oracle Database Vault.

Integrating R12 with Database Vault has certain Patching and Administration implications, for instance, before applying a patch, the SYSTEM user must be granted the DV_ACCTMGR role to ensure successful patch application.

Also, while using the FNDCPASS utility, we need to Use Database Vault Account Manager user or any user with the DV_ACCTMGR Role assigned instead of SYSTEM user.

In addition to the Oracle-supplied realms, we may optionally create our own realms to specify certain named users.

One important consideration while integration E-Biz with Database Vault is that we may have Oracle or third party products installed and integrated with our Oracle E-Business Suite Release 12 environment which may need to access the APPS schema or product schemas directly from other external or third-party schemas. Such integrations may face issues when Database Vault is activated in an Oracle E-Business Suite Release 12 Database. Following are the applications that are compatible with Database Vault currently –

  • OracleAS 10g Single Sign-On
  • OracleAS 10g Oracle Internet Directory
  • OracleAS 10g Portal
  • OracleAS 10g Discoverer

Oracle Migration Workbench – An Introduction

May 19th, 2010

An Oracle database provides you with better scalability, reliability, increased performance, and better security than other third-party databases. For this reason, organizations migrate from their current database, to an Oracle database. Because a database migration can be a complicated process, Oracle provides you with Migration Workbench. Migration Workbench is a tool that helps you to migrate from third-party databases to an Oracle database.

Migration Workbench captures information from the source database and displays it in the Source Model, which is a representation of the structure of the source database that is stored in the Workbench repository. Migration Workbench enables you to migrate the data, including schema objects, triggers, and stored procedures. Migration Workbench uses its own repository, called the Workbench repository, to store migration information that is persistent for the life of the migration. It allows you to modify the Source Model and generate an equivalent Oracle Model. The Oracle Model is a representation of the structure of the destination database and is stored in the Workbench repository. Migration Workbench populates the Oracle Model using the information from the Source Model. You can then use the information in the Source Model and the Oracle Model to compare database objects, identify conflicts with Oracle reserved words, and manage the migration progress.

Following are the components of the Migration Workbench Architecture:

  • Migration Workbench
  • Plug-In
  • Workbench Repository

Migration Workbench

Migration Workbench provides a user interface, including wizards, that help you migrate third-party databases to an Oracle database. Migration Workbench includes the following wizards and scripts:

  • Capture wizard to capture the source database
  • Migration wizard to migrate the Source Model to the Oracle Model
  • Scripts to create a set of files that describe the database structure and also to copy data from the source database to the destination database

Individual plug-ins are available to migrate different third-party databases to an Oracle database. You must install at least one plug-in with Migration Workbench.

Plug-In

Migration Workbench uses a plug-in to:

  • Extract data from the data dictionary of the source database
  • Create the Source Model
  • Convert the Source Model to the Oracle Model

Individual plug-ins are available to migrate different third-party databases to an Oracle database.

Workbench Repository

The Workbench repository is a set of tables in an Oracle database that stores the Source Model and the Oracle Model and other information about the migration. By storing the Source Model and the Oracle Model in the Workbench repository, you can customize the migration without affecting the production environment. The Workbench repository saves dependency information about the database that you are migrating.
Oracle recommends that you use an Oracle Database 10g, Oracle9i, or Oracle8i database to store the Workbench repository. However, if you prefer, you can store the information in the default Workbench repository that is installed with Migration Workbench.

The stages of Migration Workbench process are as follows:

  • Capturing the Source Database
  • Accessing the Destination Database
  • Creating and Customizing the Oracle Model
  • Migrating from the Source Database to the Oracle Database

Capturing the Source Database
In this stage, you use Migration Workbench to extract the metadata from the data dictionary of the source database and populate the Source Model of the Workbench repository. There are two methods you can use during this stage, as follows:

  • Use the Capture wizard to connect to the source database, extract the database structure, and populate the Source Model.
  • Use Migration Workbench offline capture scripts to run against the source database and create a set of files that describe the database structure. You can then use Migration Workbench to populate the Source Model from these files.

Accessing the Destination Database

To access the destination database for migration purposes, you must have certain roles and privileges. You can create a user and give the following grants:

CONNECT, RESOURCE, CREATE PUBLIC SYNONYM, ALTER ANY ROLE, ALTER ANY SEQUENCE, ALTER ANY TABLE, ALTER TABLESPACE, ALTER ANY TRIGGER, COMMENT ANY TABLE, CREATE ANY SEQUENCE, CREATE ANY TABLE, CREATE ANY TRIGGER, CREATE ROLE, CREATE TABLESPACE, CREATE USER, DROP ANY SEQUENCE, DROP ANY TABLE, DROP ANY TRIGGER, DROP TABLESPACE, DROP USER, DROP ANY ROLE, GRANT ANY ROLE, INSERT ANY TABLE, SELECT ANY TABLE, UPDATE ANY TABLE

Creating and Customizing the Oracle Model

In this stage, you use Migration Workbench to map the source database metadata, displayed in the Source Model, to similar Oracle schema objects in the Oracle Model. The Capture wizard automatically creates the Oracle Model by default. You can customize both the Source Model and the Oracle Model at a later stage.

Migrating from the Source Database to the Oracle Database
In this stage, you use Migration Workbench to migrate the source database to an Oracle database. Migration Workbench extracts schema object information from the Oracle Model and creates these objects in the destination database. After it has created the schema objects in the Oracle database, it populates these objects with the data from the source database.

Benefits of Migration Workbench

Benefits of using Migration Workbench to migrate a third-party database to an Oracle database are as follows:

  • Reduces the effort and risks involved in a migration project
  • Allows you to make informed decisions based on the amount of automated migration you can achieve
  • Simplifies the process of migrating data and applications from third-party databases to an Oracle database
  • Allows you to migrate an entire third-party database, including triggers and stored procedures
  • Provides an integrated, visual environment to help you manage the migration process
  • Displays a representation of the Source Model and Oracle Model so that you can compare
  • Provides feedback of the migration through reports
  • Allows you to customize the Source Model and Oracle Model to maximize the automation of the migration process
  • Allows you to collect metadata from a third-party database without having to connect to that database with Migration Workbench
  • Eases the migration process by allowing you to perform the migration in stages using intuitive wizards

11g R2 New Features

May 10th, 2010

There are numerous new features in Oracle 11g R2. I have compiled a list to highlight the most important ones which will help boost performance and increase ROI for your implementation.

To help separate the features based on roles, I broke the features that pertain to the point of view of, Developers, and Database Administrators.

Developers

  • This release includes an improved framework for advanced Oracle Application Express developers to build and leverage custom Web 2.0 capabilities, improving performance and enabling developers to create more dynamic application widgets. Oracle Application Express also includes the ability to suppress standard JavaScript and CSS files. All included JavaScript files are now compressed to improve page load time.
  • The storing of binary large objects (BLOBs) within the database is growing in popularity due to the many advantages over storing content on disparate file systems. 11gR2 incorporates Declarative BLOB support, which greatly simplifies loading and manipulating of content.
  • Oracle Application Express offers a number of security enhancements. Key enhancements include the ability to declaratively encrypt session state and specify session time outs for maximum idle time and maximum session duration as well as create new password item types that enable users to enter passwords without ever saving them to session state.
  • For testing and production instances, Oracle Application Express now supports the ability to install a runtime version of Oracle Application Express. This minimizes the installed footprint and privileges. Scripts are also provided to remove or add the developer interface from an existing instance. The ability to implement a runtime-only environment improves application security as developers cannot inadvertently or maliciously update a production application.
  • The JDBC driver is updated to conform to the new time zone upgrading scheme. This feature provides a simplified time zone patching process. As a result, Java applications using the TIMESTAMP WITH TIME ZONE data type are immune to Daylight Saving Time (DST) changes.

Database Administrators

  • 11gR2 includes a feature called Automatic Block Repair, which allows corrupt blocks on the primary database or physical standby database to be automatically repaired, as soon as they are detected, by transferring good blocks from the other destination. In addition, RECOVER BLOCK is enhanced to restore blocks from a physical standby database. This reduces block recovery time by using up-to-date good blocks from a real-time, synchronized physical standby database as opposed to disk or tape backups or flashback logs.
  • Oracle now offers backup to Amazon S3, an internet-based storage service, with the Oracle Secure Backup (OSB) Cloud Module. This is part of the Oracle Cloud Computing offering. This feature provides easy-to-manage, low cost database backup to Web services storage, reducing or eliminating the cost and time to manage an in-house backup infrastructure.
  • DUPLICATE can be performed without connecting to a target database. This is particularly useful for DUPLICATE to a destination database where connection to the target database may not be available at all times.
  • Tablespace point-in-time recovery (TSPITR) has been enhanced to be repeated multiple times for the same tablespace. Previously, once a tablespace had been recovered to an earlier point-in-time, it could not be recovered to another earlier point-in-time.
  • Large, mission critical applications are often unavailable for long periods of time while database objects are patched or upgraded. In such cases, Edition-based redefinition can be used. Edition-based redefinition allows an application’s database objects to be changed without interrupting the application’s availability by making the changes in the privacy of a new edition.
  • The new STANDBY_MAX_DATA_DELAY session parameter can be used to specify a session-specific apply lag tolerance, measured in seconds, for queries issued by non-administrative users to a physical standby database that is in real-time query mode. This capability allows queries to be safely offloaded from the primary database to a physical standby database, because it is possible to detect if the standby database has become unacceptably stale.
  • Applications connected to a primary database can transparently failover to the new primary database upon an Oracle Data Guard role transition. Integration with Fast Application Notification (FAN) provides fast failover for integrated clients. Flexibility and manageability of disaster recovery configurations using Oracle Data Guard is improved.
  • Traditionally, parallel execution has enabled organizations to manage and access large amounts of data by taking full advantage of the I/O capacity of the system. In-memory parallel execution harnesses the aggregated memory in a system to enhance query performance by minimizing or even completely eliminating the physical I/O needed for a parallel operation. In-memory parallel query harnesses the aggregated memory in a system for parallel operations, enabling it to scale out with the available memory for data caching as the number of nodes in a cluster increases. This new functionality optimizes large parallel operations by minimizing or even completely eliminating the physical I/O needed because the parallel operation can now be satisfied in memory.
  • Fast refresh of a materialized view is now significantly faster due to reducing the time spent on log handling. This provides significantly reduced maintenance time and more fast refreshes are possible.
  • Additional functionality has been added to the Cluster Verification Utility (CVU), for Oracle RAC, in regard to checking certain storage types and configurations. Furthermore, it gives more consideration to user-specific settings. These enhancements provide easier implementation and configuration of cluster environments and improved problem diagnostics in a cluster environment.
  • 11gR2 now supports up to 5 copies of the Oracle Cluster Registry (OCR) for improved availability of Oracle RAC. OCR has been improved to incorporate faster relocation of services on node failure.
  • Grid Plug and Play (GPnP) eliminates per-node configuration data and the need for explicit add and delete nodes steps for Oracle RAC. Grid Plug and Play reduces the cost of installing, configuring, and managing database nodes by making their per-node state disposable. It allows nodes to be easily replaced with regenerated state.
  • The patching of Oracle Clusterware and Oracle Real Application Clusters can now be completed without taking the entire cluster down. Patchsets are now installed as out-of-place upgrades to the Oracle Grid infrastructure for a cluster software (Oracle Clusterware and Automatic Storage Management) and Oracle Database.
  • A new version of Oracle Clusterware is now installed into a separate home from the current installation. This reduces the downtime required to upgrade a node in the cluster and facilitate the provisioning of clusters within an enterprise. The benefit is a reduction in planned outage time required for cluster upgrades which assists in meeting availability service levels. This also makes it easier to provide a standard installation across the enterprise.
  • This release includes a feature called Instance Caging. Instance Caging allows the DBA to limit the CPU usage of an Oracle instance by setting the CPU_COUNT initialization parameter and enabling CPU resource management. With Instance Caging, users can partition CPU resources among multiple instances running on a server to ensure predictable performance.
  • Oracle Database 11g Release 2 (11.2) users can now get e-mail notifications on any job activity. This feature improves efficiency by enabling users to be notified of any job activity that is of interest to them without having to constantly monitor the job.
  • File watcher is a new feature that enables jobs to be triggered when a file arrives on a given machine. This feature improves efficiency and ease-of-use. Jobs with file dependencies are automatically triggered when the specified file is received instead of constantly monitoring for the file.
  • Enterprise Manager Support Workbench (Support Workbench) has been enhanced to help diagnose and package incidents to Oracle support for Automatic Storage Management (ASM) databases. This feature extends the benefit of Enterprise Manager Support Workbench to ASM by helping customers package all necessary diagnostic data for incidents.
  • New in Oracle Database 11g Release 2 (11.2), the Database Smart Flash Cache feature is a transparent extension of the database buffer cache using solid state device (SSD) technology. The SSD acts as a Level 2 cache to the (Level 1) SGA. Database Smart Flash Cache can greatly improve the performance of Oracle databases by reducing the amount of disk I/O at a much lower cost than adding an equivalent amount of RAM.
  • Today, disk drives have 512 byte sectors. Disk drive manufacturers are moving to 4 KB sector drives because it allows them to offer higher capacity with lower overhead. If customers use 4 KB sector drives as 512 byte sector drives, then there is likely to be a performance penalty (because they have to run in 512 byte emulation mode). 11gR2 allows Oracle to work with 4 KB (and 512 byte) sector drives without a performance penalty. There is also the capability in Automatic Storage Management (ASM) to allow migration of a disk group from 512 byte sector drives to 4 KB sector drives.
  • 11gR2 includes the ASM Cluster File System (ACFS) which extends Automatic Storage Management (ASM) by providing a robust, modern, general purpose file system for files beyond the Oracle database files. ACFS provides support for files such as Oracle binaries, report files, trace files, alert logs, and other application data files. With the addition of the Oracle ASM Cluster File System, ASM becomes a complete storage management solution for both Oracle database and non-database files.
  • Disk drives have higher transfer rates and bytes per track on the outer tracks. This makes it preferable to keep the hotter data closer to the edge of the disk; that is, the lower numbered blocks. 11gR2 includes a feature called ASM Intelligent Data Placement, which enables ASM to identify higher performance disk regions. Most frequently accessed ASM files can be marked to be moved into the hot region and take advantage of higher I/O performance (for example, hot tablespaces and indices) and able to better meet the application I/O demand.

OA Framework Basic Personalizations

March 6th, 2010

More often than not, most companies that use Oracle Applications self service modules in 11i or are currently on R12.x versions, have had the need to customize their self service pages. Some of the changes that I have seen clients request arechanges in the display of the field name, add additional fields to the page, remove fields from the page etc…

Personalizations done to the OA Framework are stored in the JDR% tables in the database. The important part to note about creating personalization is that once they are created, they do not get over written by patch applications.

The way it works is, when an Oracle user accesses a page, the OA framework first reads the original seeded page definition and then applies the personalizations. As long as the underlying page definition is not changed (Oracle rarely removes items from their pages), the personalizations will remain intact.

————————————————————————————————————

Personalization setups

To enable personalizations. Navigate to Profile options and set the following

Personalize Self-Service Defn – Yes

FND: Personalization region Link Enabled. – If set to no, users will see the Personalize link on the top of the page. If set to Yes, the user will see the Personalize link on every region on the page.

To disable personalizations. Navigate to Profile options and set the following

Disable Self-Service Personal – Yes

Note: You can set these Profile Options value at the Application, Responsibility or User Level based on the requirement. If the personalization is to be seen only for single users then these profile options should be set at the User level. If all the users using the responsibility require to see the change, you would set these profile options at the Responsibility Level.

————————————————————————————————————

Creating Personalizations

Once the profile options are set, personalizations can be performed in multiple ways

–Navigate to the self service page that needs the change and click on the Personalize Page link.

Or

–Use the Functional Administrator responsibility, click the Personalization tab and search for the document using the document name.

(Note: The document name may be alternatively obtained by clicking on a Link “About this Page at the bottom of the self service page.

To be able to see the About this Page link, the Profile option FND: Diagnostics should be set to Yes at preferably the user level, if not already set.)

Below is a screenshot of the iExpenses self service home Page through the Personalize Link.

Once the Personalize Page opens, you will see the complete hierarchy of the page. Below is a screenshot of what the personalization page looks like

In the Personalization Context, you can see the document name which can be used alternatively if the personalizations are created using the Functional Administrator Responsibility.

———————————————————————————————————————

Select Complete View and Expand All.

To show/hide a field on the page.

Locate the item you need to show/hide on the page

Click on the Personalize icon (pencil icon) next to the field.

When the personalization properties page opens up,

Look for the Property that says Rendered- The default value is set to ‘Inherit.

Change the value to True if you need to display the field on the page

Set the value to False if you do not want to display the field on the page.

Note: If you cannot locate the item you need to add in the list of items provided on the page, you will further need to check if the item you are looking for is available in the Select statement of the VO (View Object) query. This comes as part of Advanced Personalizations. For now we will just stick to the scope of Basic Personalizations.

To Change the Prompt of the field on the Page.

Basically change the display name of the field on the page.

Locate the item whose display name you need to change on the page

Click on the Personalize icon (pencil icon) next to the item.

When the personalization properties page opens up,

Look for the Property that says Prompt

Enter the display name in the text fields at the level you want it changed at either Function/Site/Responsibility….Click on Apply

With these personalizations, the Oracle self service page can now have additional fields and different display names for the fields.

If the Profile Options are set for End users, they can create their own personalizations without interfering with the underlying design of the Oracle Core pages. The Personalizations are easy to use and gives end users the flexibility to modify their page based on their needs.                           ———————————————————————————————————————

BI Publisher Integration with Oracle Apps

March 6th, 2010

Before BI Publisher was released as a Product that was integrated with Oracle Applications, Oracle Reports 6i was the most widely used Tool for generating Report outputs and print documents like PO’s, Invoices, statements etc…

Complex Report layouts often took longer to create and test using the Oracle Reports Tool. With the launch of BI Publisher (originally XML Publisher), Oracle has made a breakthrough with the ease and simplicity by which report outputs can be generated.

To be able to use BI Publisher with Oracle Apps, Patches need to be applied which are available for download from metalink.

This article provides an insight into the components involved in creating an end to end BI Publisher solution for Oracle Apps Concurrent Programs.

BI Publisher makes use of XML data files and templates to generate a PDF output.

XML Data file: The XML Data file can be generated in multiple ways from Oracle.

One way would be to set the option on the Concurrent Program Definition to generate an XML file. Another way would be to use plsql code to generate the XML. This XML file then becomes the input for the XML Publisher Concurrent Programs which processes it with the associated template to produce the output.

Pseudo XML data file

<?xml version=”1.0″?>

<!– Generated by Oracle Reports version 6.0.8.25.0 –>

<XX_PA_XML_INV_PRT>

<LIST_G_INV_HEADER>

<G_INV_HEADER>

<SOURCE></SOURCE>

<INVOICE_FORMAT></INVOICE_FORMAT>

<CUSTOMER>10000   ABC.</CUSTOMER>

<PRODUCT>000   ABC PRODUCT.</PRODUCT>

<DRAFT_INVOICE_NUM>1</DRAFT_INVOICE_NUM>

<INV_CURRENCY_CODE>USD</INV_CURRENCY_CODE>

XML Publisher templates: These templates can be any of MS Word (.rtf )RTF, Adobe Acrobat(.pdf)PDF, XML, eText, MS-Excel

PDF and RTF templates Creation

  • PDF templates:-

PDF templates require the Adobe Standard Software. An already existing .pdf file can be used to prepare a template for XML Publisher. In most cases there is little or no amount of work involved in designing the layout, as the form fields are placed on a predesigned available blank layout. It is important to note that no matter what the version of the Adobe Acrobat Standard software you use to create the templates, all templates must be converted to Acrobat PDF Version 1.4. As of date only PDF templates Version 1.4 are supported with XML Publisher. This can be achieved by Navigating to AdvancedàPDF Optimizer. Note the current version and use the option Make compatible with: Acrobat 5.0 and later.

No logic of any kind can be used on PDF templates, which makes it rigid and pushes back the task of including complex logic in the source generating the XML Data. However it is recommended to use PDF templates in standard Forms (Government or other eg W2,), where the template for the form is subject to very little or no change at all.

It is therefore imperative to analyze business requirements thoroughly and decide on the usability of  rtf or pdf templates at the outset of the implementation.

Creation of PDF Templates:

To create a pdf template for BI Publisher, form fields need to be added.

These form fields contain XML tags that assign XML data values to the fields at runtime.

To add form fields, open a .pdf file in Acrobat standard.

Navigate ToolsàFormsàText field tool.

Draw the text form field on the pdf where you want the data to appear. Double click on the form field and add the XML tag to the Name field in the Properties box. Note that the Name added should be available in the XML Data tree file.eg: If POH_PO_NUM is an XML tag that holds the Purchase Order Number in XML Data file, you will need to add POH_PO_NUM to the Name field in the Properties for that form field on the PDF template. If you wish to use names that are different from the XML file, a mapping feature is available in the Template Definition to map the PDF template form field names with the XML tag names.

Below is a screenshot of a PDF template. You can set the properties for the data that will be displayed by this form field. Some of the properties you can set are the font type, font size, multi-line…

  • RTF templates:-

RTF templates are easier to use and support complex logic. These templates can be created with any Version of MS Word. The template file should be of .rtf format.

Designing a complex template structurally can be a little more tedious as compared to PDF templates, as MS Word is primarily not a design tool and most rtf template designs would have to be created from scratch.RTF templates can be used where

–there are many groups and subgroups with data,

–conditional formatting of form fields is required

–conditional display of data is required

–spooling multiple pages with different header/footer.

The above is a list off of the many more uses of the rtf template.

Creation of RTF Templates.

To create a rtf template for XML Publisher, you need to first design the template placing tables, nested tables, assigning the header/footer, setting the type landscape/portrait, setting the margins…Once the layout design is ready form fields need to be added.

In MS Word 2008 version Navigate to Developer, the form fields can be found under the Control option.

These form fields contain XML tags that assign XML data values to the fields at runtime.

Draw the text form field on the rtf template. Double click on the form field to add the XML tag. You can enter in the XML tag name or any name in the Default Text field if you want to mask the actual XML name or if you want to give the xml tag a more meaningful name.

Click on Add help text to enter the XML tag in the format <?TRANSACTION_DATE?>, transaction_date being an xml tag in the input XML data file.

Note that this is also the area for adding any kind of logic to be applied on the data group.

However there is a limit on the number of characters that can be added to this area.

If the logic you intend to add has too many characters, the Help Key can be used.

Below is a screenshot of an RTF template. You can set the properties for the data directly from the MS word toolbar –Home which has Text font, size, colour etc…

Some of the properties you can set are the font type, font size, multi-line…All you need to do is select the form field and set the properties from the toolbar.

Note: As of now MS word does not allow to create form fields in the header or footer section of the .rtf template. The alternative is to write the XML tag the way it is in the header and footer as can be seen with <?CUSTOMER?>.The grey areas are the form fields on the template.

XML Publisher Concurrent Programs in Oracle APPS (Ebusiness suite):

The following programs are an out of the box solution provided for XML Publisher reports. These programs make a call to java class files to integrate the XML data file and the templates to produce an output. Based on the requirements, you may use either one of the following programs

1) Program: XML Report Publisher

Short Name: XDOREPPB

This program can be used when no delivery channel like email, fax,… is required. Using this program enables the user to view the output at will from the View Output tab of the concurrent Program that runs the Oracle report. The user can also print the output by setting the print options while submitting the Concurrent Program.

2) Program: XML Publisher Report Bursting Program

Short Name: XDOBURSTREP

This program is used when there are multiple delivery channels involved, for eg: the output document needs to be printed emailed as well as faxed to the requestor/vendor…

Or when there is a range of data to be printed. In this case Bursting reuses the same template to generate a new file for each data set in the XML file.

To implement bursting, a control file is created. This control file is an XML file that contains delivery channel information like email server, print server, email address, no of copies, template, printer name….

The values can be hard coded in the file but it is best to assign these values dynamically at run time. The bursting control file reads these values from the XML data files through variables. The bursting program creates the output based on the template and the xml data file and delivers it to the channels specified.

———————————————————————————————————————

XML Publisher Setups

1) Use an existing Concurrent Program like PO Print or Invoice Print or create a new one based on your requirement.

Ensure the following are set on the Concurrent Program Definition

System AdministratoràConcurrentàProgramàDefine

Query your concurrent program. If the executable is an Oracle Report,

In the output section, set the following

Format =  XML

Style= PDF Publisher

2) XML Publisher Administrator Responsibility- Create Data and Template Definitions

  1. Create a new data definition

XML Publisher AdministratoràData Definition

Name: Enter a name for the data definition.

Code: Enter the short_name of the concurrent program which generates the XML file.

The short_name associates XML Publisher setups with the Oracle Reports concurrent Program. The Code for the Data definition should always be the same as the short_name of the concurrent program for XML Publisher reporting to work.

Application: Enter the same application that the Oracle Report concurrent Program uses.

Click on apply to put this Data Definition into effect.

You can alternatively add the following files to the Data Definition based on your setup.

XML Schema: A .xsd file needs to be uploaded when using PDF templates where the custom form field names need to be mapped with the XML tag names.

Data Template: A sample data xml file can be uploaded to this field.

Preview Data: Adding a sample .xml data file enables to preview the output from the template Definition.

Bursting Control file:The .xml control file has to be uploaded to this field when using bursting of the XML data file for generating outputs. The XDOBURSTREP program uses this file to process the output.

Sample bursting control file (Skip this if not using Bursting)

Note: If using bursting, to use the out of the box XML Publisher Report Bursting Program,

You can use the FND_REQUEST.SUBMIT_REQUEST in the After Report trigger in Oracle Reports or in your plsql code  depending on your source file which generates the xml file to automate the complete process.

  1. Create a new Template Definition

XML Publisher AdministratoràTemplate Definition

Name: Enter a name for the template definition

Code: Enter a short name for the template definition, preferably but not mandatory, the same used for the Data Definition code.

Application: Enter the Application the same as the Data Definition and Oracle Report Concurrent Program.

Data Definition: Select the Data Definition created in the above step.

Type: Enter the template type, RTF if it is an MS word template, PDF if it is a PDF template.

File: Upload the template file to be used for generating the output.

Language: Enter the language as English

Territory: Enter the territory as United States

Apply the changes to activate the Template definition.

  1. Set Administration Properties

XML Publisher AdministratoràAdministration

Under Properties, Expand the General tab, specify a Temporary Directory Path from your file system. If this is not set, the XDOBURSTREP Program will error

3) Printer setup:-If Pasta printing is not enabled in your organization

System administratoràInstallàPrinter-àRegister

Query the printers- check the Type field for the Printers.

If Printer Type= ‘–PASTA Universal Printer Type’, for all your printers then you are set to use Pasta Printing and no further steps would be necessary.

If your printer type is for eg: HPLJ4SI you may proceed to follow the steps below

Add PDF Publisher style with PASTA_PDF as a driver for printer type

———————————————————————————————————————

Once the above setups are done, Navigate to the responsibility.

Submit the request.

When it completes click on View output to see the pdf generated by XML Publisher.

If using Bursting, the output will get emailed/printed/faxed based on the values provided for the bursting control file at run time.

Oracle R12 Multi-Org Access Control

March 2nd, 2010

Multi-Org Access Control (MOAC) is used to allow access to multiple operating units from a single application responsibility. Prior to Release 12, Oracle users would have to login to difference responsibilities to enter or process data within an operating unit.

A new feature for Release 12, MOAC, allows the creation of a Security Profile and assign as many operating units as required.

To assist with enabling this useful feature, see the video below.

CFO.com – Do You Have Too Much Software?

February 27th, 2010

We run into this a lot with our customers. Companies over the years have purchased many different software packages and do not have good tools in place to keep track of usage or the maintenance contracts.

So what do you do when you find your over licensed with your software? Good question… Most software companies make it difficult and cost prohibitive to reduce license counts under the terms of their maintenance agreement. In most cases they will want to charge you list price for the reduced number of seats and ends up costing more than your original contract. It sounds crazy but sometimes it is cheaper to purchase new licenses in the long run.

How successful have you been in your re-negotiation efforts or alternative approaches? We would love to hear from you.

Link to article - http://www.cfo.com/article.cfm/14475796