This is yet another powerful tool in EBS to quickly new, changed, and completed Sales Orders or Returns from

• Legacy System
• EDI Gateway transactions
• Other EBS applications like purchasing, contracts etc
• Other front end applications (web based, 3rdparty )

Order Import Interface consists of Open Interface tables.

Order Import features include validation and defaulting, processing constraint checks, applying and releasing of order holds, scheduling of shipments, then ultimately inserting, updating or deleting the Orders in the base Order Management tables. Order Management checks all the data during the import process to ensure its validity within Order Management. Valid transactions are then converted into Orders with Lines, Reservations, Price Adjustments, and Sales Credits in the base Order Management tables.

Features of Order Import

• Have status of imported orders and Workflow
• use for Cancellation
• This update existing orders
• This importing closed orders
• This add customer
• This importing Price Adjustments
• this importing returns (referenced and non referenced)
• This is use Manual and Automatic Pricing
• This will do Price Comparison (with customer price)
• This also check Payment term comparison (with customer terms)
• Credit Checking , holds and releases
• Notes and attachments
• Validating data
• Defaulting rules
• Processing constraints
• Customer item number
• Corrections form
• Validate Only Mode
• Order Import Statistics Concurrent Program

Table

Interface tables for Order Import

• OE_HEADERS_IFACE_ALL
• OE_LINES_IFACE_ALL
• OE_PRICE_ADJS_IFACE_ALL
• OE_PRICE_ATTS_IFACE_ALL
• OE_CUSTOMER_INFO_IFACE_ALL
• OE_CREDITS_IFACE_ALL
• OE_LOTSERIALS_IFACE_ALL
• OE_RESERVTNS_IFACE_ALL
• OE_ACTIONS_IFACE_ALL

First timer

These are the steps associated in doing interfacing :

• Set up Order Source
• Populate data into interface tables for that source
• Run the order import concurrent request or Import using the corrections form
• Query the imported or updated order in Order Organizer

In any time if you encounter error you can use the Order Import Correction window to examine the Order and optionally correct data, if it fails the Import process. You can use the Error Message window to determine if your data failed to import.

Steps by step

Step 1 :Pre-Requisite setup

The following steps are prerequisites to importing Orders:

• You can set up every aspect of Order Management that you want to use with imported Orders, including Customers, Pricing, Items, and Bills.
• You can define and enable your Order Import sources using the Order Import Sources window.
• Determine if you should submit the Order Import Statistics concurrent program.

Before that , the following Profile Options must be set-up prior to importing Orders:

Step 2 :Populate data into interface tables for that source

Importing Order Header Information into OE_HEADERS_IFACE_ALL Table

• Populate your data into table OE_HEADERS_IFACE_ALL which is a multi-org table for Sales Order Headers Open Interface.
• This table stores Order Header information that is imported from a feeder system into Oracle Order Management using Order Import
• A record has be inserted into Order Headers Interface table, for any operation on the Order. The orig_sys_document_ref column is referred when submitting the Order Import Concurrent program

Importing Order Lines Information into OE_LINES_IFACE_ALL Table

• Populate your data into table OE_LINES_IFACE_ALL which is a multi-org table for Sales Order Lines Open Interface.
• This table stores Order Lines information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Customer Information into OE_CUSTOMER_INFO_IFACE_ALL Table

Importing Customer related information is optional. Use this step, only if Customer Accounts / Contacts / Addresses need to be imported, while importing Orders into Oracle Applications.

• Populate your data into table OE_CUSTOMER_INFO_IFACE_ALL is used to add new Customer, its Address and Contact information.
• New Customer can be added by populating the required columns in this table, for that Customer new Address can be added, and for these new Account and Addresses, Contact information can also be added using this table
• If you are importing make sure parent_Customer_Ref must be populated in case the current record needs to be linked to a Parent Customer record.
• In case the Customer is a Person, columns First_Name, Last_Name, etc. must be populated for Customer_Info_Type_Code = ACCOUNT.

Importing Pricing Adjustments into OE_PRICE_ADJS_IFACE_ALL Table

Importing Pricing Adjustments is an optional .This should be included in Order Import, only if Price Adjustments need to be imported

• Populate your data into table OE_PRICE_ADJS_IFACE_ALL is a multi-org open interface table for Sales Order/Line Price Adjustments.
• This table stores Price Adjustment information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Pricing Attributes into OE_PRICE_ATTS_IFACE_ALL Table

Importing Pricing Attributes is an optional . Include this step, if Pricing Attributes need to be imported for the Order.

• Populate your data into table OE_PRICE_ATTS_IFACE_ALL .
• This Table stores Pricing Attributes information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Lot Serial Information into OE_LOTSERIALS_IFACE_ALL Table

Importing Lot Serials is an optional step. Include this step, only if Lots/Serial Number information needs to be imported for the Order.

• Populate your data into table OE_LOTSERIALS_IFACE_ALL table .
• This table used for Return Line Lot Serials Open Interface.
• This table stores Return Line Lot Serial information that is imported from a feeder system into Oracle Order Management using Order Import.

Importing Reservation Information into OE_RESERVTNS_IFACE_ALL Table

This is an optional step. Include this step, only if Reservation information needs to be imported for the Order.

• OE_RESERVTNS_IFACE_ALL need to be populated.
• This table stores Reservation details that need to be imported.

Importing Sales Credit Information into OE_CREDITS_IFACE_ALL Table

Importing Sales Credits is an optional . use this step, only if Sales Credits information needs to be imported for the Order.

• This is a multi-org table for Sales Order/Line Credits Open Interface.
• This table stores Sales Credits information that need to be imported.

Step 3 :Populate data into interface tables for that source

You can initiated by submitting a Order Import Concurrent program.

Navigate to Order Management Super User : Orders, Returns : Import Orders : Order Import Request.

This program have these parameters:

• Order Source : Choose a specific Order Import source that you have defined in step 1 which you setup via Order Import Sources window.
• Order References: You can enter the System Document Reference, if you want to run Order Import for a specific Order.
• Validate Only (Yes/No): Choose whether to validate only the data in the interface tables. If 'Yes', the Order will be validated, but not imported into the base Orders tables. The default value is 'No'.

If you are first timer , you can run the Order Import process in the Validation-only mode. This mode allows the transaction to be validated against all the Order ManWelcome to It's All In OrderIt's All In Orderagement Rules, but does not pass valid transactions to the base Order Management tables.

If you choose, you can run production transactions in Validation-only mode for a preview of exceptions. This will allow you to make necessary corrections to the transactions in the Order Import window, then choose the Validate button to perform a validation check.

The Validation-only mode may also facilitate testing of transactions through Order Import even in a production environment to take advantage of all the setup in the production environment.

Step 4 :Corrections to Imported Data from Order Import Corrections Window

If is needed if you stuck or encountered error in the concurrent program. Navigation would be

Navigate to Order Management Super User : Orders, Returns : Import Orders : Corrections .

If any corrections to the imported data are required, changes to the data can be done from the Corrections window. Once the required changes are made, the same window can be used to launch the Order Import Process again.

You can use the request id of step 3 and click on find button to view the corrections window.

Step 5 :Verify the Imported Order Information

Once the Order Import process has been completed successfully, the same can be verified with the following screens :

Navigate to Order Management Super User : Orders, Returns : Order Organizer.

In the Find window, enter values in Order Source and Order Source Reference fields.

Understanding the profile options and some parameter is essential for autoinvoice execution. Understanding is especially helpful when trouble shooting is required to figure out why and where the processing has failed for certain data scenarios. Here is some informative information for profile Options and parameter required for autoinvoice.

As we know system setup can be done from system options, which is as below.

 1.Max Memory (in bytes)
  As marked 1 in above picture. This is memory setting for allocating autoinvoice program for validation. It is recommended to set Value to 3,000,000 Bytes.

2.Log File Message Level

This is at 2 in above picture. This is number represents the amount of detail we wish to display Auto Invoice log file.

• Message Level 0
  This will gives the following entries in the log file:
  Product Version, Program Name, Auto Invoice Start Time, AutoInvoice Concurrent request Arguments, Error and Warning Messages, AutoInvoice End Time, auto Invoice logical Steps.
•  Message Level 1
  This gives all of the above entries plus:  Time-Stamped function labels
•  Message Level 2
  This gives you all of the above entries plus:  Sizes of Allocated Arrays, Dynamic SQL Statements, Number of Rows Updated, Inserted and Deleted
•  Message Level 3
    This gives you all of the above entries plus: Method IV SQL Array Values.

3. Purge Interface Tables
This is marked 3 in above picture. If this is checked then

• Purges records that are successfully imported into receivables.

It recommended to avoid getting interface tables filled with data that is no more required

4.AR: Autoinvoice Gather Statistics
Specify whether AutoInvoice process analyzes the interface tables or not

• Null is taken as Yes
• This profile should be set to "Yes" if type of data populated in the interface tables changes

5.Number of Instances
This is for Load Balancing.

• Number of CPU -1
• Maximum allowed 500

6.AR: Maximum Lines per Autoinvoice worker
This is setting for let worker know how many records need to pick. This setting is more important, if you are loading very huge set of data. If any one is doing conversion, it is essential to check this value.

The default value is 100000,But the optimal value should be 10000.

Hope this will give a fair idea who is going to utilize autoinvoice First time.

Why set up is important for transaction flex field in autoinvoice? Does my Autoinvoice get failed if I would not do set up or not passing information for Transaction flex field? Yes, You can't. The way the auto invoicing works is designed it worked to Uniquely identify for each transaction.

Then what are those Transaction Flex Fields?

Transaction flexfields are descriptive flexfields that AutoInvoice uses to identify transactions and transaction lines. Oracle Receivables lets you determine how you want to build your transaction flexfield structure and what information you want to capture. There are four types of transaction flexfields:

• Line Transaction Flexfield
• Reference Transaction Flexfield
• Link-To Transaction Flexfield
• Invoice Transaction Flexfield

The key point is the Line Transaction Flexfield must be defined if AutoInvoice is being used. The Line Transaction Flexfield can be used to reference and link to other lines because the Line Transaction Flexfield is unique for each transaction line. AutoInvoice always uses the Line Transaction Flexfield structure for both the Link-to and Reference information when importing invoices. It is only necessary to explicitly define the Link-to, Reference, and Invoice Transaction Flexfield structures if this information is to be displayed on a custom window.

You must define both the line-level and header-level Transaction Flexfield. To define the line-level Transaction Flexfield, query 'Line Transaction Flexfield' in the Title field of the Descriptive Flexfield Segments window and enter the context and segments associated with this Transaction Flexfield. To define the Transaction Flexfield at the header-level, query 'Invoice Transaction Flexfield' and enter the context and segments associated with this Transaction Flexfield. All segments in the line level transaction flexfield that refer to header information must also exist in the header level transaction flexfield. For example if you define a line-level Transaction Flexfield with 4 segments and only the last 2 segments refer to line-level information, define the header Transaction Flexfield using the first two segments.

Where to setup
AR gives you the option of using QuickPicks to display reference information for imported invoices. You can use the System Profile Option AR: Transaction Flexfield QuickPick to select the Transaction Flexfield Segment you want to display in Invoice QuickPicks throughout Oracle Receivables.

Business Case:

Lets say my autoinvoice having two sources,

1.More4Apps - where data is coming from excel based More4apps.
2.PROJECTS INVOICES - for Creating Project invoices.

So to process these, we have set up like this:

If Source is More4Apps then required INTERFACE_LINE_ATTRIBUTE1 till 2 (Fig :2)
If source is PROJECTS INVOICES then required INTERFACE_LINE_ATTRIBUTE1 till 8 (Fig :3)

Fig 2: Setup for Fisrt source as above

Fig 3: Setup for second source as above

What is mean, pretty simple based out of source the respective column should be populated. At the time of validation auto invoice will try to validate first the DFF field, based out of Context Value, The value in context field would be the same which appears while defining. And the process should take the value as reference and create a transaction in the AR.

Here is note on one of most efficient tool used in Oracle application. It is Auto Invoice, most industry accepted tool in Oracle apps.

What is Auto Invoice??

Auto Invoice is a tool that can be used to import and validate transaction data from other financial systems from which one can create invoices, debit memos, credit memos, and on-account credits. It rejects transactions with invalid information to insure the integrity of the data.

Where its fits 

 This fits well with in Oracle ERP or to integrate with any third party application< ?xml:namespace prefix ="" o />

What Module data can be integrated?

• Oracle Order Management
• Oracle Project Accounting
• Oracle services

To make fully functional  what else required

• Loader program
• Validation program

Top 10 reasons for using Auto Invoice

1. Powerful Interface Tool

2. Supports Oracle & Non-Oracle Systems

3. Import Large Amount of Data

4. Calculate or Import Tax

5. Group Lines & Invoices

6. Online Error Correction

7 .Lines Validation

8. Derive GL Date

9 .Import Flex fields

10.Import or Derive Accounting Info

What is inside AutoInvoice

AutoInvoice is a tool consists of 3 main programs. Each program will have unique nature of work to do and they are called internally except Purge program whose execution is derived on the setup otherwise ready to execute stand alone.

§         Master (RAXMTR)

§         Import (RAXTRX)

§         Purge (RAXDEL)

1.       Auto Invoice Master program RAXMTR

Selects and marks records in the interface tables to  be processed based on the parameters the user entered and then calls the AutoInvoice Import program. Auto Invoice Master program has no report output.

 

•Gathers statistics, it means it gathers the stats on interface tables and set the stats on certain indices on interface tables

•Marks interface records for processing by marking request_id

•Submits multiple workers for Parallel Processing by creating instances for request.

 

2.       Auto Invoice Import Program Validates the selected record and creates transaction if it passes validation. Any record that fails validation is left in the interface table with an error code. Depending on the setup, related records may be rejected as well. This program has an output file called Auto Invoice Execution report, which you can view by clicking the View Report button in the Requests window.

 

• Workhorse of Auto invoice
• Validates data
• Inserts records
• Deletes interface data
• Only when system option purge set to ‘Y’

 

3.       Auto Invoice Purge Program Deletes records from the interface tables. If you set the Purge Interface Table system option to No in Define System Option window, Auto Invoice does not delete processed records from the interface tables after each run,and we must submit Auto Invoice Purge Program periodically to clean up the interface tables. This program only deletes transaction lines that have been successfully imported.

•Deletes all rows where interface_status =‘P’

•Ra_interface_lines

•Ra_interface_distributions

•Ra_interface_salescredits

How to start

As discussed above, oracle Receivable’s Auto Invoice program will be used to import and validate Invoices.

A custom feeder program is required to transfer data from the Advantage extract files and populate the Auto Invoice interface tables (RA_INTERFACE_LINES_ALL and RA_INTERFACE_DISTRIBUTIONS_ALL).If there is need to run populate sales credit into RA_INTERFACE_SALESCREDITS_ALL table.

When run, AutoInvoice produces the AutoInvoice Execution Report and the AutoInvoice Validation Report.

Any entries which failed validation can be reviewed in Oracle Receivables’ AutoInvoice Interface Exceptions window. Depending on the error, changes may need to be made in Receivables, the feeder program or the imported records in the interface tables.

How Autoinvoice Execution works

Normally, Auto Invoice can be divided into three major phases

• Pre-grouping: here the validates all of the line level data takes place
• Grouping: groups lines based on the grouping rules and validates header level data
• Transfer :validates information that exists in Receivables tables

 What happen when Auto invoice run

Once the Auto invoice Program gets called, the following activity takes place is part of execution process. This can be analyzed by debug options.

• Line, accounting, and sales credit information for each line populates 3 interface tables
• Lines are ordered and grouped
• Tax is calculated
• GL date is determined
• GL accounts are assigned using Auto Accounting
• Tax, freight, commitments, and credit memos are linked to transaction lines
• All transactions are batched
• Validated lines are used to create the transaction

 How Data is flowing

Select, insert and update and delete take place on certain tables once it is logged out.

Selects

            – RA_INTERFACE_LINES_ALL

            – RA_INTERFACE_DISTRIBUTIONS_ALL

            – RA_INTERFACE_SALESCREDITS_ALL

Updates/Insert

            – RA_INTERFACE_ERRORS_ALL

            – RA_CUSTOMER_TRX_ALL

            – RA_CUSTOMER_TRX_LINES_ALL

            – AR_PAYMENT_SCHEDULES_ALL

            – AR_RECEIVABLE_APPLICATIONS_ALL

Inserts

            – RA_INTERFACE_ERRORS_ALL

AutoInvoice Exception Handling

Records that fail validation are called ‘Exceptions’

• Exceptions stay in Interface Tables which is RA_INTERFACE_ERRORS_ALL
• Errors can be corrected in the Exception Handling window
• Once corrections are made, Auto invoice must be resubmitted
• Records that pass validation get transferred to Receivables tables 

AutoInvoice Exception Handling Windows

• Interface Exception window displays exception messages associated with all invalid records
• Interface Lines window displays records that fail validation, provides an error message and can be used to correct the errors
• The Line Errors windows displays errors associated with a specific line, and can only be opened from Interface Lines window
• Interface Exceptions window displays Interface Id, Exception Type, Error Message and Invalid Value associated to the error
• Data cannot be edited in this window, but error can be viewed and corrected by clicking the Details button
• Error Message and Column name with invalid data are displayed in the Message column, and the invalid value that needs to be corrected is displayed in the Invalid Value column

Next post, I would summarize more information for Transaction Flexfield,Grouping , profile options and parameter setting.

The business lifecycle is different for every organization because it is not a linear process. However, the business challenges at each point remain similar. ERP plays a key role throughout an organization's existence. Selecting the right tool must first and foremost address one’s key business problems and challenges, enabling one to meet the strategic business goals. And the more one knows the pros and cons of each deployment model, the more certain it is that one will embark on a path to success.

This blog/forum what I call the Epicenter for Oracle Apps is envisaged to address such issue as its focal point. In the oracle apps sphere, this platform is crafted with a clear intention of knowledge sharing from live experiences grounded in daily routine life so that i2i (idea to implementation) makes better sense to all the readers and contributors.

Why I called the Oracleapps "HUB"

"Hub"...with absolute reason, as this is my own repository of last 8 years of activities and the ongoing research in Oracle EBS Technology, which I am trying to put together for my quick reference as well as for others who may be exploring to know more about the oracle EBS product line. I would also like to share some of the key notes based on projects, experiences, research, prototyping outcome, client business cases with Functionality mapping information of EBS suite. Potentially, I would like to help some one who is very new to EBS technology product line, and secondly those managers who might be thinking of implementing ERP at their end. Hope some of notes and reference will handhold the needy into ERP evaluation process.

What I will do for You
Here I can and would love to share and contribute most of the things which are part of routine work. But you will also find links to matters I consider interesting on the web and occasionally some scribbling about techniques which I think are nice to share some thoughts about with whoever might be interested. And that’s not it. You would also notice enough food for thought from time to time. I hope this might be helpful for you. This would also act as a great platform to discuss things, seek suggestions/solutions for any related/relevant problems as I strongly believe there is nothing which cannot be done by sharing expertise/knowledge. .

Who I think are my best readers
Managers, persons looking at the Oracle Product in there Business world, new babies in Oracle application and anyone who just wants to know newer things as and when they pop up.

Who I am

My Name is Sanjit Anand and I am Funco-Techno consultant who brings to the table over 8.7 + years of specialized experience in Oracle Financials, manufacturing Modules and bit on HRMS(Shared Mode). My area of interest includes Transaction Management, Working Capital, Procure to Pay, Order to Cash, SOX, Upgrades, Implementations and System Integration. Besides all these I have also hands-on expertise in oracle EBS and has been involved in some of the big roll out in Asia, United States and Europe. I have worked in large oracle integrator such as: Computer Science Corp(CSC) and Rapidigm and TCG - United Airlines and for about a year I worked as an independent contractor adding value to customized Oracle apps needs. Currently Based in Singapore associated with Tata Consultancy Services , Singapore. I has worked with clients based in the US, Singapore and UK.

As a vivid student and an avid follower of instinct, I strongly believes that there has a lot to contribute to the tech world in terms of sharing and exchanging the knowledge and skills that has been hitherto learning.

For more details about me:Click here for Details

Your valuable comments and suggestions are most welcome

Contact me:
Feel free to contact me at sanjitanand@yahoo.com or sanjit@oracleappshub.com

Disclaimer
The opinions expressed here represent solely my own represent personal conjecture based upon experience, practice and observation and does not represent the thoughts, intentions, plans or strategies of my current & previous employers and their clients.

In Unix there are many ways to accomplish a given task. Given a problem to solve, we may be able to get to a solution in any number of ways.

Shell Script

A shell is an environment in which we can run our commands, programs, and shell scripts. There are different flavors of shells, just as there are different flavors of operating systems. Each flavor of shell has its own set of recognized commands and functions.

Shell scripts and functions are both interpreted. This means they are not compiled. Both shell scripts and functions are ASCII text that is read by the Korn shell command interpreter. When we execute a shell script, or function, a command interpreter goes through the ASCII text line by line, loop by loop, test by test and executes each statement, as each line is reached from the top to the bottom.

Different Types of Shells to Declare

#!/usr/bin/sh OR #!/bin/sh Declares a Bourne shell
#!/usr/bin/ksh OR #!/bin/ksh Declares a Korn shell
#!/usr/bin/csh OR #!/bin/csh Declares a C shell
#!/usr/bin/bash OR #!/bin/bash Declares a Bourne-Again shell

How to use ftp in a shell script

Sometimes we want to FTP a file from one machine to another. Usually, we can do the transfer interactively, but every so often, a shell script do the file transfer.

The problem we always encountered in scripting ftp transfers involved getting a password to the ftp server. Typical ftp client programs under Unix, Linux, Solaris and NetBSD all read the ftp password from /dev/tty.

Example Working Script
#!/bin/sh
HOST='ftp.users.company.net'
USER='yourid'
PASSWD='yourpw'
FILE='file.txt'

ftp -n $HOST <<END_SCRIPT
quote USER $USER
quote PASS $PASSWD
put $FILE
quit
END_SCRIPT
exit 0

Tips for you . In order to get the password to the ftp server without having the ftp client program read the password from /dev/tty requires two tricks:

• Using the -n option on the ftp client program to prevent the ftp client from trying to log in immediately. That way, the ftp client does not ask for a user ID and password. No use of /dev/tty.
• Use the ftp client program command quote to send user ID and password to the ftp server.

How to Submit Concurrent Program Using CONCSUB:

Syntax:

CONCSUB <ORACLE ID>
<ResponsIbility Application Short Name>
<ResponsIbility Name>
<User Name>
CONCURRENT
<Concurrent Program Application Short Name>
<Concurrent Program Name>
[START=<Requested Start Date>]
[REPEAT_DAYS=<Repeat Interval>]
[REPEAT_END=<Request Resubmission End Date>]
<Concurrent Program Arguments ...>

Example to shutdown the concurrent manager

CONCSUB APPLSYS/FND SYSADMIN 'System Administrator' SYSADMIN [WAIT={Y|N}]
CONCURRENT FND [SHUTDOWN|ABORT]

ORACLE ID: Enter the username and password of the ORACLE ID you want your concurrent program to run in. Enter the username and password without any spaces and separated by a slash ("/").

Responsibility Application Short Name: Enter the short name of the application for your responsibility.This name, along with your responsibility name, will be used to select a responsibility for Your concurrent request to run in.

Responsibility Name: Enter the name of your responsibility. This name, along with your responsibility application short name, will be used to select a responsibility for your concurrent request to run in.

User Name: Enter the name of your Application ObjectLibrary user. This name will be used to update the Who information for any data your concurrent program changes and to create report output File name for this request.

Concurrent Program Application Short Name: Enter the short name of the application for your concurrent program. This name, along with the concurrent program name, uniquely identifies the concurrent program for your concurrent request.

Concurrent Program Name: Enter the name of your concurrent program. This name, along with the concurrent program application short name, uniquely identifies the concurrent program for your concurrent request.

Start Date: Specify the token START and enter the date you want the concurrent request to run, in DD- MON-YY HH24:MI:SS format.

Request Resubmission End Date: Specify the token REPEAT_END and enter the date you want the request resubmission to stop, in DD-MON-YY HH24:MI:SS format. This argument is used in conjunction with "Repeat Interval".

Concurrent Program Arguments: Enter the arguments for your concurrent program.

Sample HOST File to Submit Two concurrent Programs Using CONCSUB:
########################################################################
# Set the variables for running concurrent program.
########################################################################
CONCPRG="XXPHARC_CONC_TEST"
CONCAPP="XXPHARC"
RESPAPP="XXPHARC"
RESP="XXPHARC-AR-CONC"
USERNAM=`echo $1 | cut -d ' ' -f 5 | cut -d '"' -f 2`

echo $CONCPRG
echo $CONCAPP
echo $RESPAPP
echo $RESP
echo $USERNAM
########################################################################
CONCMSG=`noarg CONCSUB $FCP_LOGIN \
$RESPAPP \
$RESP \
$USERNAM \
WAIT=10 \
CONCURRENT \
$CONCAPP \
$CONCPRG`
########################################################################
# Set the variables for running concurrent program.
########################################################################
CONCPRG="XXPH_CONC_TEST"
########################################################################
CONCMSG=`noarg CONCSUB $FCP_LOGIN \
$RESPAPP \
$RESP \
$USERNAM \
WAIT=10 \
CONCURRENT \
$CONCAPP \
$CONCPRG`
reqid=""
reqid=`echo $CONCMSG | cut -d " " -f 3`
CONCMSG=`echo $CONCMSG | cut -d'"' -f3`
y=""
y=`echo $reqid | grep "^[0-9]"`
if [ $? -ne 0 ]
then
echo "Failed to schedule SMARCONSS thru Control-M option ...\n"
exit 1
else
exit 0
fi

In the above script we have taken two concurrent programs named XXPHARC_CONC_TEST and PL/XXPH_CONC_TEST both consists simple PL/SQL code. These are assigned to "XXPHARC-AR-CONC" responsibility and its short name is "XXPHARC". Here we have taken two CONCSUB commands to submit the concurrent programs.

Very common thing, people get confuse why such type of naming convention oracle have used. Here is note for some of them:

• _ALL : Table holds all the information about different operating units. Multi-Org environment. You can also set the client_info to specific operating unit to see the data specific to that operating unit only.
• _TL are tables corresponding to another table with the same name minus the _TL. These tables provide multiple language support. For each item in the table without _TL there can be many rows in the _TL table, but all with different values in the LANGUAGE column.
• _B these are the BASE tables.
  They are very important and the data is stored in the table with all validations.
  It is supposed that these table will always contain the perfect format data.
  If anything happens to the BASE table data, then it is a data corruption issue.
• _F these are date tracked tables, which occur in HR and Payroll. For these there are two date columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE which together with the PK identifies a row uniquely. The date intervals cannot overlap. Many think they are Secured data. Guess someone from Oracle confirms.
• _V tables are the views created on base tables
• _VL are views for multi language tables which combines the row of the base table with the corresponding row of the _TL table where the LANGUAGE = USERENV('LANG').
• _S are sequences, used for finding new values for the primary key of a table.
• _A are Audit Shadow Tables
• _AVN and _ACN are Audit Shadow Views (when data was changed, and with what values