This chapter covers the following topics:
In Oracle Applications, concurrent programs are system batch jobs that retrieve and push data between Oracle applications and the database. Concurrent programs can be comprised of a single request or a request set containing more than one concurrent program. Concurrent programs usually have logs associated them that provide details of the concurrent program data.
You can set up and start using Oracle Applications concurrent programs at any time in your implementation. Programs can be set to run on a schedule or only upon user request. For more complete information on Oracle Applications concurrent programs, see Oracle Applications System Administrator's Guide.
See the detail descriptions of the iStore concurrent programs. For a summary of the programs available, see: the section, "Overview of Oracle iStore Concurrent Programs", below.
See the section, "Running Concurrent Programs", below, for quick-steps.
See Oracle Applications System Administrator's Guide for complete details on Oracle Applications concurrent programs.
Several concurrent jobs are seeded in the Oracle Applications (Forms) iStore concurrent program manager setup. These include:
iStore Search Insert
iStore Section Search Refresh
iStore Cascade Section Layout Mapping
iStore - Express Checkout Order Submission
iStore Reports Fact Tables Refresh
Template Mappings Import/Export
Lead Import Concurrent Program
iStore Product Autoplacement
iStore Oracle Content Manager Integration Migration
Oracle Marketing Integration Concurrent Program
The following concurrent programs control the product search functionality.
iStore Search Insert is a single request concurrent program that you execute one time as a post-install step during your Oracle iStore implementation. Run this batch job after you have loaded Oracle Inventory items and set the Inventory organizations. This program populates Oracle iStore's category search table with product information from the Oracle Inventory tables.
Typically, you should not run the iStore Search Insert concurrent program more than once. However, you may need to rerun this program under one of the following three conditions:
If you add multiple items that do not appear in the search table
If you want to purge all items from the search table
If you change the setting of the fuzzy search functionality, by either enabling or disabling it
This concurrent program populates Oracle iStore's section search table with product information.
To enable section-level search on the Customer UI for the first time, run the iStore Search Insert first, then run the iStore Section Search Refresh program. To switch from category-level to section-level search, run only the iStore Section Search Refresh program.
If you have enabled a section-level search, rerun this concurrent program whenever you change the setting of the fuzzy search functionality.
This section lists the concurrent programs that duplicate sections and section layout mappings.
If you need to duplicate a section having more than 1,000 child sections, use the iStore Duplicate Section concurrent program. See the "Creating and Maintaining Sections" section in the chapter, Implementing the Catalog, for more information.
To copy the layout mappings from a parent section to all of the children sections underneath it, use the iStore Section Layout Mapping Concurrent Program. See the "Creating and Maintaining Sections" section in the chapter, Implementing the Catalog, for more information.
Note: This concurrent program only works with sections using Configurable Layout.
The following concurrent program submits orders for Express Checkout:
Schedule this program as a batch process that runs at pre-determined intervals. This program converts the Express Checkout shopping carts into orders.
The concurrent program, iStore Reports Fact Tables Refresh, populates the Oracle iStore reports' fact tables with data. Refer to the chapter, Implementing Reports, for more information.
Oracle iStore's Display Template Import/Export functionality within Template Manager allows you to export or import template mappings using XML files. The functionality is implemented as two concurrent programs:
iStore Template Mapping Import Concurrent Program
iStore Template Mapping Export Concurrent Program
For full details on these concurrent programs, please refer to the Advanced Display chapter.
The concurrent program request set, iStore Lead Import Set, pulls data matching certain parameters into the Oracle Sales leads database table.
The request set contains the following concurrent programs:
iStore Lead Import Quotes
iStore Lead Import Orders
For more information, see the chapter, Integrating Oracle iStore with Oracle Sales Applications.
The iStore Autoplacement concurrent program can be used to populate leaf sections with products from Oracle Inventory categories. The program also can remove products from sections that no longer match the criteria of the concurrent program and section-category mappings.
For more information, see the "Implementing Products" chapter.
Oracle iStore provides a migration script for customers who want to integrate Oracle iStore with Oracle Content Manager (OCM). The script is implemented as a concurrent program, iStore Oracle Content Manager Integration Migration.
Both existing customers and new customers who want to use the OCM integration must run the concurrent program as a mandatory step to migrate the seed and customer data.
See "Integrating Oracle iStore with Oracle Content Manager" chapter for more information.
If you are integrating Oracle iStore with Oracle Marketing's product screens, you must load the inventory categories information into Oracle Marketing database tables. To do this, run the concurrent program, AMS Load Inventory Categories. After this program is run, the categories information shows up in the Oracle Marketing UI.
See the "Integrating Oracle iStore with Oracle Marketing" chapter, for more information.
At the end of the installation patching process, Oracle Payments automatically runs an Oracle iStore concurrent program, iStore Program to Migrate Credit Card Data to Oracle Payments. This concurrent program migrates the iStore data for primary and preferred credit card to the Oracle Payments model.
Below are instructions for running any Oracle Applications concurrent program or program set. You can use these procedures to run or schedule any of the Oracle iStore concurrent programs.
See Oracle Applications System Administrator's Guide for complete details on Oracle Applications concurrent programs.
Responsibility
For Oracle Applications concurrent programs in general, it varies by module.
For Oracle iStore concurrent programs, use iStore Concurrent Programs Responsibility
Steps
Log in to Oracle Forms with the appropriate responsibility as described under Responsibility, above. The Submit a New Request form opens.
Choose Single Request (to run a single concurrent program) or Request Set (to run a set of concurrent programs).
Select OK. The Submit Request form opens.
Query for the appropriate concurrent program, if necessary.
Select the desired request or request set.
Either run immediately or select Schedule to schedule the batch jobs.
If scheduling, select the timeframe:
As Soon as Possible radio button -- To run the program(s) right away, select this option and then select OK.
Once radio button -- To run the program(s) once at a time that you will later specify, select this option and then select OK.
Periodically or On Specific Days radio buttons -- To run the program(s) on a schedule that you will later specify, select this option, enter information in the appropriate fields, and then select OK.
Select Submit to submit the request. You receive a confirmation that the request has been submitted.
Optional: You can monitor the progress of your request by looking at the request log and output files in $COMMON_TOP/admin/log/l<request ID>.log and $COMMON_TOP/admin/out/<request ID>.out, respectively.
Optional: You can also view the request status by selecting View > Requests and searching by the request ID.
Use the following procedure to check the status of a concurrent program.
Steps
Log in to Oracle Forms with the System Administrator responsibility.
Choose Concurrent > Requests.
The Find Requests window (defaulted to "All My Requests") opens.
In the Find Requests window, search for your concurrent program request.
If the server is not busy, then selecting Find may be the fastest way to find your request.
If your server is busy, it may be better to enter search criteria and look for Specific Requests.
The Requests window displays a list of submitted requests. The Oracle iStore concurrent programs should be listed.
Click Refresh Data occasionally to check the completion status.
Once in the "red" state or Phase = "Completed", the "View Output" and "View Log" buttons will become active if the log and output files have been setup correctly.