oracle customer care technical reference manual

8/18/2019 Oracle Customer Care Technical Reference Manual

1/132

Oracle

Customer CareTechnical Reference

Manual

RELEASE 11i

April 2000


2/132

Oracle Customer Care Technical Reference ManualRelease 11i

To order this book, ask for Part No. A83678–01

Copyright 2000. Oracle Corporation. All rights reserved.

Major Contributors:

Contributors:

This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle Corporation; it isprovided under an Oracle Corporation agreement containing restrictions on use and disclosure and is also protected by copyright, patent, and

other intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care tosafeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information ora reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the ConfidentialInformation of third parties such as Oracle Corporation and instructing such employees and agents of these requirements for this TRM; (c)restricting disclosure of this TRM to those of your employees who have a ”need to know” consistent with the purposes for which this TRM wasdisclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legendsor markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form or

by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. You should not use thisTRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle Corporation products.

The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter,please report them to us in writing. Oracle Corporation does not warrant that this TRM is error–free. This TRM is provided to customer ”as–is”

with no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracle’s agreements.

Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with thisTRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee’sresponsibility to take all appropriate fail–safe, back–up, redundancy and other measures to ensure the safe use of such applications if thePrograms are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs.

Program Documentation is licensed for use soley to support the deployment of the Programs and not for any other purpose.Restricted Rights LegendThis TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are ’commercial computer software’ anduse, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in theapplicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the FederalAcquisition Regulations are ’restricted computer software’ and use, duplication and disclosure of the TRM and the Programs associated with thisTRM shall be subject to the restrictions in FAR 52.227–14, Rights in Data –– General, including Alternate III (June 1987). Oracle Corporation, 500Oracle Parkway, Redwood City, CA 94065.

Oracle is a registered trademark, and Oracle Customer Care, CASE*Exchange, Enabling the Information Age, Hyper*SQL, NLS*Workbench,Oracle7, Oracle8, Oracle 8i, Oracle Access, Oracle Application Object Library, Oracle Discoverer, Oracle Financials, Oracle Quality, Oracle WebCustomers, Oracle Web Employees, Oracle Work in Process, Oracle Workflow, PL/SQL, Pro*Ada, Pro*C, Pro*COBOL, Pro*FORTRAN,Pro*Pascal, Pro*PL/I, SmartClient, SQL*Connect, SQL*Forms, SQL*Loader, SQL*Menu, SQL*Net, SQL*Plus, and SQL*Report are trademarks orregistered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.


3/132

T

CAUTION

his Technical Reference Manual in any form –– software orprinted matter –– contains proprietary, confidential information

that is the exclusive property of Oracle Corporation. If you do nothave a valid contract with Oracle for the use of this Technical ReferenceManual or have not signed a non–disclosure agreement with Oracle

covering this Technical Reference Manual, then you received thisdocument in an unauthorized manner and are not legally entitled topossess or read it.

Use, duplication, and disclosure are subject to restrictions stated inyour contract with Oracle Corporation.


4/132


5/132


6/132

vi Oracle Service Technical Reference Manual

Oracle Proprietary, Confidential Information––Use Restricted by Contract


7/132

C H A P T E R

1T

1 – 1Introduction


Introduction

he Oracle Customer Care Technical Reference Manual provides theinformation you need to understand the underlying structure of

Oracle Customer Care. After reading this manual, you should be ableto convert your existing applications data, integrate your existingapplications with Oracle Customer Care, and write custom reports forOracle Customer Care, as well as read data that you need to performother tasks.

This chapter introduces you to the Oracle Customer Care TechnicalReference Manual, and explains how to use it.


8/132

1 – 2 Oracle Service Technical Reference Manual


Introduction

At Oracle, we design and build applications using Oracle Designer, oursystems design technology that provides a complete environment tosupport developers through all stages of a systems life cycle. Becausewe use a repository– based design toolset, all the information regardingthe underlying structure and processing of our applications is availableto us online. Using Oracle Designer, we can present this information toyou in the form of a technical reference manual.

This Oracle Customer Care Technical Reference Manual contains detailed,up–to–date information about the underlying structure of OracleCustomer Care. As we design and build new releases of Oracle

Customer Care, we update our Oracle Designer repository to reflectour enhancements. As a result, we can always provide you with anOracle Customer Care Technical Reference Manual that contains the latesttechnical information as of the publication date. Note that after thepublication date we may have added new indexes to Oracle CustomerCare to improve performance.

About this Manual

This manual describes the Oracle Customer Relationship Management(CRM) Applications Release 11i data model, as used by OracleCustomer Care; it discusses the database we include with a fresh installof Oracle CRM Release 11i. If you have not yet upgraded to Release11i, your database may differ from the database we document in this

book.

You can contact your Oracle representative to confirm that you havethe latest technical information for Oracle Customer Care. You can alsouse Oracle MetaLink which is accessible through Oracle’s Support WebCenter (http://www.oracle.com/support/elec_sup).

Finding the Latest Information

The Oracle Customer Care Technical Reference Manual contains the latestinformation as of the publication date. For the latest information weencourage you to use Oracle MetaLink which is accessible throughOracle’s Support Web Center (http://www.oracle.com/support/elec_sup).


9/132

1 – 3Introduction


Audience

The Oracle Customer Care Technical Reference Manual provides usefulguidance and assistance to:

•

Technical End Users• Consultants

• Systems Analysts

• System Administrators

• Other MIS professionals

This manual assumes that you have a basic understanding of

structured analysis and design, and of relational databases. It alsoassumes that you are familiar with Oracle Application Object Libraryand Oracle Customer Care. If you are not familiar with the aboveproducts, we suggest that you attend one or more of the trainingclasses available through Oracle Education (see: Other InformationSources: page 1 – 7).

How This Manual is Organized

This manual contains two major sections, High–Level Design andDetailed Design.

High–Level Design

This section, Chapter 2, contains database diagrams and lists eachdatabase table and view that Oracle Customer Care uses. This chapteralso has a list of modules.

Detailed Design

This section, Chapter 3, contains a detailed description of the OracleCustomer Care database design, including information about each

database table and view you might need for your custom reporting orother data requirements.


10/132



How to Use This Manual

The Oracle Customer Care Technical Reference Manual is a single,centralized source for all the information you need to know about theunderlying structure and processing of Oracle Customer Care. For

example, you can use this manual when you need to:

• Convert existing application data

• Integrate your Oracle Customer Care application with your otherapplications systems

• Write custom reports

• Define alerts against Oracle Applications tables

• Configure your Oracle Self –Service Web Applications

• Create views for decision support queries using query tools

• Create business views for Oracle Discoverer

You need not read this manual cover to cover. Use the table of contentsand index to quickly locate the information you need.

How Not To Use This Manual

Do not use this manual to plan modifications

You should not use this manual to plan modifications to OracleCustomer Care. Modifying Oracle Customer Care limits your ability toupgrade to future releases of your Oracle Customer Care application.In addition, it interferes with our ability to give you the high–qualitysupport you deserve.

We have constructed Oracle Customer Care so that you can customizeit to fit your needs without programming, and you can integrate it withyour existing applications through interface tables. However, shouldyou require program modifications, you should contact our support

team (see: Other Information Sources: page 1 – 7). They can put youin touch with Oracle Services, the professional consulting organizationof Oracle. Their team of experienced applications professionals canmake the modifications you need while ensuring upward compatibilitywith future product releases.


11/132


12/132



Attention: Oracle does not support any customization of Oracle Application Object Library tables or modules, not even

by Oracle consultants. (Oracle Application Object Librarytables generally have names beginning with FND_%.)

Accordingly, this manual does not contain detailed informationabout most Oracle Application Object Library tables used byOracle Customer Care.

A Few Words About Terminology

The following list provides you with definitions for terms that we usethroughout this manual:

Relationship

A relationship describes any significant way in which two tables may be associated. For example, rows in the Journal Headers table mayhave a one–to–many relationship with rows in the Journal Lines table.

Database Diagram

A database diagram is a graphic representation of application tablesand the relationships between them.

Module

A module is a program or procedure that implements one or more business functions, or parts of a business function, within anapplication. Modules include forms, concurrent programs and reports,and subroutines.

Application Building Block

An application building block is a set of tables and modules (forms,

reports, and concurrent programs) that implement closely–relateddatabase objects and their associated processing. Said another way, anapplication building block is a logical unit of an application.

QuickCodes

QuickCodes let you define general purpose, static lists of values forwindow fields. QuickCodes allow you to base your program logic on

lookup codes while displaying user–friendly names in a list of values


13/132

1 – 7Introduction


window. QuickCodes simplify name and language changes by lettingyou change the names your end users see, while the codes in yourunderlying programs remain the same.

FormA form is a module comprised of closely related windows that are usedtogether to perform a task. For example, the Enter Journals form inOracle General Ledger includes the Enter Journals window, the Batchwindow, and the More Actions window among others. The Enter

Journals window is the main window, and from it, you can use buttonsto navigate to other windows in the form. The form name usuallycorresponds to the main window in the form, and is frequently awindow you open directly from the Navigator.

Other Information Sources

Installation and System Administration

Training

Oracle Education offers a complete set of training courses to help youand your staff master Oracle CRM Applications. We can help youdevelop a training plan that provides thorough training for both yourproject team and your end users. We will work with you to organizecourses appropriate to your job or area of responsibility.

Training professionals can show you how to plan your trainingthroughout the implementation process so that the right amount of information is delivered to key people when they need it the most. Youcan attend courses at any one of our many Educational Centers, or youcan arrange for our trainers to teach at your facility. In addition, wecan tailor standard courses or develop custom courses to meet yourneeds.

Support

From on–site support to central support, our team of experiencedprofessionals provides the help and information you need to keepOracle Customer Care working for you. This team includes yourTechnical Representative, Account Manager, and Oracle’s large staff of consultants and support specialists with expertise in your business


14/132



area, managing an Oracle server, and your hardware and softwareenvironment.


15/132

1 – 9Introduction


About Oracle

Oracle Corporation develops and markets an integrated line of software products for database management, applicationsdevelopment, decision support, and office automation, as well as

Oracle Applications, an integrated suite of more than 75 softwaremodules for financial management, supply chain management,manufacturing, project systems, human resources, and sales andservice management.

Oracle products are available for mainframes, minicomputers, personalcomputers, network computers , and personal digital assistants,allowing organizations to integrate different computers, different

operating systems, different networks, and even different databasemanagement systems, into a single, unified computing and informationresource.

Oracle is the world’s leading supplier of software for informationmanagement, and the world’s second largest software company.Oracle offers its database, tools, and applications products, along withrelated consulting, education, and support services, in over 145countries around the world.

Thank You

Thanks for using Oracle Customer Care and this technical referencemanual!

We appreciate your comments and feedback. After the Table of Contents of this manual is a Reader ’s Comment Form that you can useto explain what you like or dislike about Oracle Customer Care or thistechnical reference manual. Mail your comments to the followingaddress or call us directly at (650) 506–7000.

Oracle CRM Applications Content Development ManagerOracle Corporation500 Oracle Parkway

Redwood Shores, California 94065U.S.A.


16/132




17/132

C H A P T E R

2T

2 – 1High–Level Design


High–Level Design

his chapter presents a high–level design for Oracle CustomerCare that satisfies the business needs we specify during Strategy

and Analysis. It contains database diagrams for Oracle Customer Careapplication building blocks, lists of database tables and views, and alist of modules.


18/132



Overview of High–Level Design

During High–Level Design, we define the application components(tables, views, and modules) we need to build our application. Wespecify what application components should do without specifying the

details of how they should do it.

You can refer to this High–Level Design chapter to quickly acquaintyourself with the tables, views, and modules that comprise OracleCustomer Care applications. And, you can prepare yourself tounderstand the detailed design and implementation of OracleCustomer Care.

Database Diagrams

The Database Diagrams section graphically represents all OracleCustomer Care applications tables and the relationships between them,organized by building block.

Use this section to quickly learn what tables each Oracle Customer

Care application building block uses, and how those tables interrelate.Then, you can refer to the Table and View Definitions sections of Chapter 3 for more detailed information about each of those tables.

Table Lists

The Table List sections list the Oracle Customer Care applicationstables. Because a product might not include at least one table for eachtype, this Technical Reference Manual might not include each of thefollowing sections.

Public Tables

Use the Public Table List section to quickly identify the tables you are

most interested in. Then, you can refer to the Table and ViewDefinitions sections of Chapter 3 for more detailed information aboutthose tables.

In addition, this manual may contain full documentation for one ormore of the following Application Object Library tables: FND_DUAL,FND_CURRENCIES, and FND_COMMON_LOOKUPS.


19/132



Internal Tables

This section includes a list of private, internal tables used by OracleCustomer Care; we do not provide additional documentation for thesetables.

View Lists

The View List sections list the Oracle Customer Care views, with onesection for each type of view. Because a product might not include atleast one view for each type, this Technical Reference Manual might notinclude each of the following sections.

Use this section to quickly identify the views you are most interestedin. Then, you can refer to the Table and View Definitions sections of Chapter 3 for more detailed information about those views.

Public Views

This section lists views that may be useful for your custom reporting or

other data requirements. The list includes a description of the view,and the page in Chapter 3 that gives detailed information about thepublic view.

Web Views

This section lists views that you may need to configure yourSelf –Service Web applications. The list includes a description of the

view, and the page in Chapter 3 that gives detailed information aboutthe web view.

Forms and Table Views

This section lists supplementary views that are not essential to theRelease 11i data model, but simplify coding or improve performancefor Oracle Developer.

Internal Views

This section includes each private, internal view that Oracle CustomerCare uses.


20/132



Multiple Reporting Currency Views

This list includes views that were created to support the MultipleReporting Currencies feature.

Module List

The Module List section briefly describes each of the Oracle CustomerCare applications modules. This section lists forms, reports, andconcurrent programs.

A form is a module comprised of closely related windows that are used

together to perform a task. For example, the Enter Journals form inOracle General Ledger includes the Enter Journals window, the Batchwindow, and the More Actions window. The Enter Journals window isthe main window, and from it, you can use buttons to navigate to otherwindows in the form. The form name usually corresponds to the mainwindow in the form, and is frequently a window you can open directlyfrom the Navigator.

The Reports and Concurrent Programs lists include processes you cansubmit from the Submit Requests window or other windows, as well asprocesses that are submitted automatically by Oracle Customer Care.Use your user’s guide to learn more about reports and concurrentprocesses.


21/132



Database Diagramming Conventions

We use the following notational conventions in our database diagrams:

Figure 2 – 1Database Diagram

Conventions

Mandatory and Optional Foreign Keys

A value entered in the column in the foreign keymust match a value in the primary key column.

Server Model Diagram Elements and Notation

A value entered in the column in the foreign keymust match either a value in the primary key column,or else it must be null.


22/132



Tables – are the basic unit of storage in the database. A hand symbolpreceding the title in the table’s title bar indicates that the table is notowned by this application but shared with another.

Foreign key constraint – is a type of referential integrity constraint for

checking the integrity of data entered in a specific column or set of columns. This specified column or set of columns is known as theforeign key.

Delete rule indicator – determines the action to be taken when anattempt is made to delete a related row in a join table. A line throughthe foreign key constraint, as shown on the above diagram, indicatesthat this action is restricted.

Arcs – specify that, for any given row in a table, a value must beentered in one of the arc columns. The remaining columns within thearc must be null.


23/132




24/132



Database Diagrams

This section graphically represents most of the significant OracleCustomer Care tables and the relationships between them, organized

by building block. Use this section to quickly learn what tables each

Oracle Customer Care application building block uses, and how thesetables interrelate. Then, you can refer to the Table and View Definitionssections of Chapter 3 for more detailed information about each of thosetables.

This section contains a database diagram for each of the followingOracle Customer Care application building blocks:

• Diagram 1: Plans

• Diagram 2: Profiles

Some tables, especially important reference tables, appear in more thanone database diagram. When several building blocks use a table, weshow that table in each appropriate database diagram.

Plans


25/132



Profiles


26/132



Profiles


27/132



Public Table List


28/132



Public Table List

This section lists each public database table that Customer Care uses andprovides a brief description of each of those tables. The page reference isto the table description in Chapter 3.

Note that ”public” tables are not necessarily intended for write access bycustom code; Oracle Corporation supports write access using onlystandard Oracle Applications forms, reports, and programs, or any SQLwrite access to tables explicitly documented as API tables. For moreinformation, see the How Not To Use This Manual section of this book’sIntroduction.

Customer Care uses the following Public tables:

Table Name Description

CSC_COLOR_CODES CSC_COLOR_CODES stores information about color and

rating association (See page 3 – 7)

CSC_CUSTOMERS CSC_CUSTOMERS stores parties that criticallity is being

overridden (See page 3 – 15)

CSC_CUSTOMERS_AUDIT_HIST CSC_CUSTOMERS_AUDIT_HIST is used to store changesin customers criticallity (See page 3 – 17)

CSC_CUSTOMIZED_PLANS CSC_CUSTOMIZED_PLANS stores the customer

information of a customized plan (See page 3 – 25)

CSC_CUST_PLANS CSC_CUST_PLANS stores the customer, plan association

(See page 3 – 26)

CSC_CUST_PLANS_AUDIT CSC_CUST_PLANS_AUDIT stores the history of allcustomer, plan association (See page 3 – 28)

CSC_PLAN_ENABLE_SETUP CSC_PLAN_ENABLE_SETUP table stores the names of the

form functions integrated with Relationship Plans module.

(See page 3 – 49)

CSC_PLAN_HEADERS_B CSC_PLAN_HEADERS_B table stores all the plan templates

and customized plan templates. (See page 3 – 53)

CSC_PLAN_HEADERS_TL CSC_PLAN_HEADERS_TL table stores the translated

name, description of the plan templates stored in

CSC_PLAN_HEADERS_B table. (See page 3 – 55)

CSC_PLAN_LINES CSC_PLAN_LINES stores the plan details of plan templates

stored in CSC_PLAN_HEADERS_B (See page 3 – 59)

CSC_PROF_BLOCKS_B CSC_PROF_BLOCKS_B stores the profile check variable


29/132



_ _ _ _ _ _ p

information (See page 3 – 65)

CSC_PROF_BLOCKS_TL CSC_PROF_BLOCKS_TL table stores the translated

columns of profile check variables stored in

CSC_PROF_BLOCKS_B table (See page 3 – 66)

CSC_PROF_BLOCK_RESULTS CSC_PROF_BLOCK_RESULTS stores the value of the

profile check variables per party and account (See page

3 – 67)

CSC_PROF_CHECKS_B CSC_PROF_CHECKS_B stores the profile check information

(See page 3 – 69)

CSC_PROF_CHECKS_TL CSC_PROF_CHECKS_TL table stores the translatedcolumns of profile checks stored in CSC_PROF_CHECKS_B

table (See page 3 – 70)

CSC_PROF_CHECK_RATINGS CSC_PROF_CHECK_RATINGS stores the rating and color

information (See page 3 – 71)

CSC_PROF_CHECK_RESULTS CSC_PROF_BLOCK_RESULTS stores the value of the

profile checks per party and account (See page 3 – 73)

CSC_PROF_CHECK_RULES_B CSC_PROF_CHECK_RULES_B stores the conditions used

by the profile check (See page 3 – 75)

CSC_PROF_CHECK_RULES_TL CSC_PROF_CHECK_RULES_B stores the conditions used

by the profile check (See page 3 – 76)

CSC_PROF_GROUPS_B Base Table to Store profile Group information (See page

3 – 77)

CSC_PROF_GROUPS_TL Translation Table to Store profile Group information (See

page 3 – 78)

CSC_PROF_GROUP_CATEGORIES Store the categories that are present in a profile group .

Categories are needed only for Dashboard Groups (See page

3 – 79)

CSC_PROF_GROUP_CHECKS Store the relation between profile groups and profile checks.

This table stores the Profile checks that are present in a

profile group (See page 3 – 81)

CSC_PROF_MODULE_GROUPS Relation between a form function and Profile groups. This

specifies the profile group , to be displayed in the profile

window when it is displayed in a form . (See page 3 – 83)

CSC_PROF_TABLE_COLUMNS_B Base table to Store Drilldown details for a profile variable.


30/132



p

This stores the column and table names for the drilldown

form. Also stores the object_code, which provides the

form_function to drilldown (See page 3 – 85)

CSC_PROF_TABLE_COLUMNS_TL Translation table to Store Drilldown details for a profilevariable. This stores the column and table names for the

drilldown form. Also stores the object_code, which provides

the form_function to drilldown (See page 3 – 86)

FND_COLUMNS Columns in all the registered application tables

FND_FORM_FUNCTIONS Functionality groupings

FND_TABLES Tables registered in applications

FND_USER Application users

OKC_CONDITION_HEADERS_B Defines a Condition to be evaluated upon the occurrence of

an Action. (See page 3 – 88)

Public View List


31/132



This section lists each public database view that Oracle Customer Careuses and provides a brief description of each of those views. Theseviews may be useful for your custom reporting or other data

requirements. The page reference is to the detailed view description inChapter 3.

Oracle Customer Care uses the following public views:

View Name Description

CSC_COLOR_CODES_V View of CSC_COLOR_CODES. This view is used in

Customer Profile Setup form – Preferences tab. (See page

3 – 8)

CSC_CONDITION_HEADERS_V Defines a Condition to be evaluated upon the occurrence of

an Action. (See page 3 – 9)

CSC_CONDITION_LINES_V view on okc_condition_lines_v (See page 3 – 11)

CSC_CONDITION_LINE_DETAILS_V Each Condition Line expresses a Boolean condition.

Multiple Condition Lines may be and’d or or’d together

and nested using parenthesis. (See page 3 – 12)

CSC_CONDITION_OUTCOMES_V Registration of a PL/SQL process or a workflow with the

application for use as an OUTCOME, CONTRACT

PROCESS, QA PROCESS, or FUNCTION in a CONDITION

LINE. (See page 3 – 14)

CSC_CUSTOMERS_AUDIT_HIST_V View of CSC_CUSTOMERS_AUDIT_HIST. This view is

used in Customer Override Criticallity form. (See page3 – 19)

CSC_CUSTOMERS_V View of CSC_CUSTOMERS. This view is used in Customer

Override Criticallity form. (See page 3 – 22)

CSC_CUST_PLANS_AUDIT_V This view is based on CSC_CUST_PLANS_AUDIT used in

lock row event of server side API’s (See page 3 – 30)

CSC_CUST_PLANS_V This view is based on CSC_CUST_PLANS used in lock row

event of server side API’s (See page 3 – 33)

CSC_GS_CUSTOMERS_V View used to perform search operation on customer

information in the contact center form. (See page 3 – 36)

CSC_LOOKUPS Group of Lookup Types and Lookup Codes used in

Customer Care (See page 3 – 47)

CSC_PLAN_ENABLE_SETUP_V This view is based on CSC_PLAN_ENABLE_SETUP used

l k f d ( )


32/132



in lock row event of server side API’s (See page 3 – 51)

CSC_PLAN_HEADERS_V This view is based on CSC_PLAN_HEADRES_B &

CSC_PLAN_HEADRES_TL used in the client code (See

page 3 – 56)

CSC_PLAN_LINES_V This view is based on CSC_PLAN_LINES used in lock row

event of server side API’s (See page 3 – 61)

CSC_PLAN_SEARCH_V This view is used to perfom serarch operation on the plans

module. (See page 3 – 63)

CSC_PROF_BLOCK_RESULTS_V View of CSC_PROF_BLOCK_RESULTS. This view will give

us information on the result of the Profile Check Variableswhen the Profile Engine is run. (See page 3 – 68)

CSC_PROF_CHECK_RATINGS_V View of CSC_PROF_CHECK_RATINGS. This view is used

in Customer Profile Setup form – Profile Checks tab. (See

page 3 – 72)

CSC_PROF_CHECK_RESULTS_V View of CSC_PROF_CHECK_RESULTS. This view will give

us information on the result and grade of the CheckVariables when the Profile Engine is run. (See page 3 – 74)

CSC_PROF_CHECK_RULES_VL This view is the MLSed view based on

CSC_PROF_CHECK_RULES_B and

CSC_PROF_CHECK_RULES_TL. This view is used in

Customer Profile Setup form– Profile Checks tab. (See page

NO TAG)

CSC_PROF_GROUP_CATEGORIES_V View of CSC_PROF_GROUP_CATEGORIES. This view is

used in Customer Profile Setup form – Profile Groups tab

and Dashboard Groups tab. (See page 3 – 80)

CSC_PROF_GROUP_CHECKS_V View of CSC_PROF_GROUP_CHECKS. This view is used in

Customer Profile Setup form – Profile Groups tab and

Dashboard Groups tab. (See page 3 – 82)

CSC_PROF_MODULE_GROUPS_V View of CSC_PROF_MODULE_GROUPS. This view is used

in Customer Profile Setup form – Preferences tab. (See page

3 – 84)

FND_LOOKUPS Oracle Application Object Library QuickCodes (See page

3 – 87)

Internal View List


33/132



This section lists each private, internal view that Oracle Customer Careuses.

Warning: Oracle Corporation does not support access to OracleApplications data using these views, except from standardOracle Applications forms, reports, and programs.

Oracle Customer Care uses the following internal views:

• CSC_CONDITION_EXPRESSION_V

• CSC_CONDITION_FUNCTION_V

• CSC_CONTACT_RESTRICTIONS_V

• CSC_CUSTOMER_ACCOUNTS_V

• CSC_CUSTOMER_ADDRESS_V

• CSC_CUSTOMER_PROFILE_DB_V

• CSC_CUSTOMER_PROFILE_V

• CSC_CUSTOMER_RESPONSE_CONT_V

• CSC_CUSTOMER_RESPONSE_V

• CSC_FND_ALL_COLUMNS_V

• CSC_PROFILE_CATEGORY_DB_V

• CSC_PROF_DRILLDOWN_V

Multilingual View List


34/132



This section lists each MultiLingual database view that Oracle CustomerCare uses. MultiLingual views were created to allow certain seed datato be available in multiple national languages simultaneously.

Oracle Customer Care uses the following Multilingual views:

• CSC_PLAN_HEADERS_VL

• CSC_PROF_BLOCKS_VL

• CSC_PROF_CHECKS_VL

• CSC_PROF_GROUPS_VL

•CSC_PROF_TABLE_COLUMNS_VL

• FND_APPLICATION_VL

• FND_FORM_FUNCTIONS_VL

Module List


35/132



Oracle Customer Care uses no additional forms, reports, or concurrentprograms.


36/132




37/132

C H A P T E R

3T

3 – 1Detailed Design


Detailed Design

his chapter presents a detailed design for implementing OracleCustomer Care. It contains detailed definitions of tables and

views that you may need to reference to write custom reports or use forother data extraction.

Overview of Detailed Design


38/132



During Detailed Design, we specify in detail how each applicationscomponent should work. We prepare detailed definitions of tables andviews.

You can refer to this Detailed Design chapter to gain a detailedunderstanding of the underlying structure and processing of OracleCustomer Care that enables you to:

• Convert existing application data

• Integrate your Oracle Customer Care application with your otherapplications systems

•

Write custom reports• Define alerts against Oracle Applications tables

• Create views for decision support queries using query tools

Table and View Definitions

The Table and View Definitions section contains a detailed definition of Oracle Customer Care applications tables. For each table, it providesinformation about primary keys, foreign keys, QuickCodes, indexes,triggers, and sequences. It also gives you a detailed description of eachcolumn and its characteristics. In addition, it provides the SQLstatement that defines each view. Review this section to get a detailedunderstanding of what tables your Oracle Customer Care application

contains, and how it uses them to hold and access the information itneeds.

Table and View Definitions

Thi i i d il d d i i f h O l C


39/132



This section contains a detailed description of each Oracle CustomerCare table and view that you may need to reference. For each table, itpresents detailed information about:

• Primary keys

• Foreign keys

• Column descriptions

• Indexes

• Oracle sequences

•

Triggers• View derivations

Because Oracle does not support customization of Oracle ApplicationObject Library tables, we do not provide you with detailed informationabout them. Consequently, this section does not document all theFND_% tables Oracle Customer Care uses.

The following sections appear in each table or view description:

Foreign Keys

To help you understand the relationships between tables, we list eachforeign key contained in a table. For each foreign key in a table, we listthe primary key table name (the table to which a foreign key refers), its

corresponding primary key columns, and the foreign key columns thatrefer to those primary key columns.

When the primary key table has a composite primary key, we list eachcolumn of the composite key sequentially.

If a table contains two or more distinct foreign keys that refer to thesame primary key table, we repeat the primary key table name and listeach of the distinct foreign keys separately.

QuickCodes Columns

When a database column contains a QuickCodes value, which weimplement using a foreign key to FND_LOOKUPS, MFG_LOOKUPS,or to some other lookup table, we list the QuickCodes type (lookup

type) to which the QuickCodes value must belong and a complete listof QuickCodes values and meanings. Some QuickCodes can bed fi d b i th li ti Th l d i t d


40/132



defined by you in the application. These values are designated asUser–defined.

Column Descriptions

We list the important characteristics of each column in a table or view.These characteristics include whether the column is part of the table’sprimary key, whether Oracle8i requires a value for this column, and thedata type of the column. We also give you a brief description of how

Oracle Customer Care uses the column.When a column is part of a table’s primary key, we append the notation(PK) to the name of that column.

To help you understand which columns Oracle Customer Care usesand which columns it does not use, we alert you to any unusedcolumn. When no module uses a database column, we show one of thefollowing legends in the Description column:

Oracle Customer Care does not use this column,although the column might be used in a futurerelease.

Oracle Customer Care no longer uses this column.AutoInstall installs this column. Subsequentversions of Oracle Customer Care might notinclude this column.

Oracle Customer Care no longer uses this column.If you upgraded your software from an earlierversion, you may still have this column, dependingupon whether you chose to delete it during anupgrade process. If you install Oracle CustomerCare, you do not have this column.

Standard Who Columns

Most Oracle Customer Care tables contain standard columns tosupport \ Row Who. When your program or SQL*Plus commandselects a row from a table, use these columns to determine who lastupdated the row. If your program or SQL*Plus command updates or

Not currentlyused

No longer used

No longerinstalled

inserts a row in an interface table, you must populate each of the fivestandard Who columns:


41/132



Date when a user last updated this row

User who last updated this row (foreign

key to FND_USER.USER_ID)Date when this row was created

User who created this row (foreign key toFND_USER.USER_ID)

Operating system login of user who lastupdated this row (foreign key toFND_LOGINS.LOGIN_ID). You should

set this to NULL, or to 0 if NULL is notallowed

Since every table containing Who columns has several foreign keys tothe tables FND_USER and FND_LOGINS, we do not include theforeign key columns LAST_UPDATED_BY, CREATED_BY, orLAST_UPDATE_LOGIN in a table’s list of foreign keys.

Additional Who Columns for Concurrent Programs

Some Oracle Customer Care tables also contain several additional Whocolumns to distinguish between changes a user makes with a form andchanges a concurrent program makes. When a concurrent programupdates or inserts a row in a table, the concurrent program populatesthe following additional Who columns:

Concurrent request ID of program that lastupdated this row (foreign key toFND_CONCURRENT_REQUESTS.RE-QUEST_ID)

Application ID of program that lastupdated this row (foreign key toFND_APPLICATION.APPLICATION_ID)

Program ID of program that last updatedthis row (foreign key to FND_CONCUR-RENT_PROGRAM.CONCURRENT_PRO-GRAM_ID)

Date when a program last updated thisrow

LAST_UPDATE_DATE

LAST_UPDATED_BY

CREATION_DATE

CREATED_BY

LAST_UPDATE_LOGIN

REQUEST_ID

PROGRAM_APPLICATION_ID

PROGRAM_ID

PROGRAM_UPDATE_DATE

Since every table containing these additional Who columns has severalforeign keys to the tables FND_CONCURRENT_REQUESTS,FND APPLICATION and FND CONCURRENT PROGRAM we do


42/132



FND_APPLICATION, and FND_CONCURRENT_PROGRAM, we donot include the foreign key columns REQUEST_ID,PROGRAM_APPLICATION_ID, or PROGRAM_ID in a table’s list of

foreign keys.

Indexes

If an Oracle Customer Care table uses an Oracle8i index, we list thedatabase columns that comprise that index, in sequential order.

Note: The indexes we document in this manual correspond tounique keys we specified during product development and testing.In some cases, we may add additional indexes during the portingprocess to fine–tune performance on specific platforms; therefore,there may be minor differences between the indexes documented inthis book and the indexes for production versions of OracleCustomer Care.

Sequences

Oracle Customer Care uses Oracle8i sequence generators to generateunique integers. If any table column gets its value from an Oracle8isequence generator, we list the name of the corresponding sequencegenerator and the name of the column that stores the unique integer.

Database Triggers

If a table has one or more active database triggers, we provide a brief explanation of each database trigger and when it fires.

View Derivation

For each Oracle Customer Care view you may need to reference, weinclude important elements from the SQL statement that defines orcreates a view. By studying this view definition, you can understandexactly how a view derives its contents.

CSC_COLOR_CODES

CSC COLOR CODES stores information about color and rating


43/132



CSC_COLOR_CODES stores information about color and ratingassociation

Column DescriptionsName Null? Type Description

COLOR_CODE (PK) NOT NULL VARCHAR2(30) The color code for the rating.

RATING_CODE (PK) NOT NULL VARCHAR2(30) The rating code in theCSC_LOOKUPS table withlookup_type = PROFILE_RATING.

LAST_UPDATE_DATE NOT NULL DATE Standard Who column

LAST_UPDATED_BY NOT NULL NUMBER(15) Standard Who column

CREATION_DATE NOT NULL DATE Standard Who column

CREATED_BY NOT NULL NUMBER(15) Standard Who column

LAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who column

Indexes

Index Name Index Type Sequence Column Name

CSC_LOOKUP_COLOR_CODES_U1 UNIQUE 4 RATING_CODE5 COLOR_CODE

CSC_COLOR_CODES_V

View of CSC COLOR CODES


44/132



View of CSC_COLOR_CODES

View Definition

CREATE VIEW CSC_COLOR_CODES_V

as SELECT

rowid ROW_ID

, color_code

, rating_code

, last_update_date

, last_updated_by

, creation_date

, created_by

, last_update_login

Where FROM csc_color_codes

Column Descriptions

Name Null? Type Description

ROW_ID NULL ROWID Row Id

COLOR_CODE NOT NULL VARCHAR2(90) The color code for the rating.

RATING_CODE NOT NULL VARCHAR2(90) The rating code in theCSC_LOOKUPS table with

lookup_type = PROFILE_RATING.LAST_UPDATE_DATE NOT NULL DATE Standard Who Column

LAST_UPDATED_BY NULL NUMBER(15) Standard Who Column

CREATION_DATE NULL DATE Standard Who Column

CREATED_BY NULL NUMBER(15) Standard Who Column

LAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who Column

CSC_CONDITION_HEADERS_V

Defines a Condition to be evaluated upon the occurrence of an Action.


45/132



p

View Definition

CREATE VIEW CSC_CONDITION_HEADERS_V

as SELECT

och.id condition_id ,

och.sfwt_flag sfwt_flag,

och.acn_id acn_id,

och.description description,

och.short_description short_description,

och.comments comments,

och.one_time_yn one_time_yn,

och.name condition_name,

och.condition_valid_yn condition_valid_yn,

och.before_after before_after,

och.template_yn template_yn,

och.date_active date_active,

och.date_inactive date_inactive,

och.cnh_type cnh_type,

oa.name Action_name,

oa.description Action_description,

oa.acn_type acn_type,

oa.counter_action_yn counter_action_yn,

oa.enabled_yn enabled_yn

from okc_condition_headers_v och,

okc_actions_v oa

Where och.acn_id = oa.id

Column Descriptions


CONDITION_ID NULL NUMBER Primary key column ofOKC_CONDITION_HEADERS_B.

SFWT_FLAG NULL VARCHAR2(30) Indicates a value was changedin another language. Not fullyimplemented in 11i

ACN_ID NULL NUMBER Primary key column ofOKC_ACTIONS_B

DESCRIPTION NULL VARCHAR2(4000) User entered free format textdescription.

SHORT_DESCRIPTION NULL VARCHAR2(4000) User entered free format textdescription.

COMMENTS NULL VARCHAR2(1995) User entered free format textcomment.

ONE_TIME_YN NULL VARCHAR2(3) Yes/No field.CONDITION_NAME NULL VARCHAR2(150) Condition name.

CONDITION_VALID_YN NULL VARCHAR2(3) Yes/No field.

BEFORE_AFTER NULL VARCHAR2(3) Before/After field.

TEMPLATE_YN NULL VARCHAR2(3) Refer to base table.

DATE_ACTIVE NULL DATE Date condition became active.

DATE_INACTIVE NULL DATE Date condition became inactive.

CNH_TYPE NULL VARCHAR2(30) Condition type

ACTION_NAME NULL VARCHAR2(150) Action name.

ACTION_DESCRIPTION NULL VARCHAR2(4000) User entered free format textdescription for an Action.

ACN_TYPE NULL VARCHAR2(240) Action type

COUNTER_ACTION_YN NULL VARCHAR2(3) Yes/No field.


46/132



ENABLED_YN NULL VARCHAR2(3) Yes/No field.

CSC_CONDITION_LINES_V

A Condition Line represents an expression that is one of three types:l f b d


47/132



general, counter, or function– based.

View DefinitionCREATE VIEW CSC_CONDITION_LINES_V

as SELECT

DISTINCT CNH_ID CNH_ID,

DECODE( CNL_TYPE ,’CEX’,’Counter’,’FEX’,’Function’,’GEX’,’Expression’) CONDITION_TYPE,

DESCRIPTION DESCRIPTION

FROM OKC_CONDITION_LINES_V

Column Descriptions


CNH_ID NULL NUMBER Primary Key ofOKC_CONDITION_HEADERS_B

CONDITION_TYPE NULL VARCHAR2(150) Condition type


CSC_CONDITION_LINE_DETAILS_V

Each Condition Line expresses a Boolean condition. Multiple ConditionLi b d’d ’d t th d t d i th i


48/132



Lines may be and’d or or’d together and nested using parenthesis.

View DefinitionCREATE VIEW CSC_CONDITION_LINE_DETAILS_V

as SELECT

ocl.aae_id AAE_ID,

decode( ocl.cnl_type,

’GEX’,’Expression’,

’FEX’,’Function’,

’CEX’,’Counter’ ) CONDITION_TYPE,

ocl.cnl_type CNL_TYPE,

ocl.description DESCRIPTION,

ocl.pdf_id PDF_ID,ocl.cnh_id CNH_ID,

ocl.sortseq SORTSEQ,

ocl.left_parenthesis LEFT_PARENTHESIS,

decode(cnl_type,’GEX’,oaa.name,

’CEX’,csc_core_utils_pvt.get_counter_name(nvl(ocl.left_ctr_master_id,

ocl.left_counter_id)),

’FEX’,decode(opd.package_name,NULL,opd.procedure_name,

opd.package_name||’.’||opd.procedure_name) )

LEFT_VALUE,

decode(cnl_type,’FEX’,NULL,ocl.relational_operator) relational_operator,decode(cnl_type,’GEX’,ocl.right_operand,

’CEX’,csc_Core_utils_pvt.get_counter_name(nvl(to_number(ocl.right_operand),

nvl(ocl.right_ctr_master_id,ocl.right_counter_id))) )

RIGHT_OPERAND,

ocl.right_parenthesis RIGHT_PARENTHESIS,

ocl.logical_operator LOGICAL_OPERATOR

FROM okc_action_attributes_v oaa,

okc_condition_lines_v ocl,

okc_process_defs_v opd Where oaa.id(+) = ocl.aae_id

AND ocl.pdf_id = opd.id(+)

Column Descriptions


AAE_ID NULL NUMBER Primary key ofOKC_ACTION_ATTRIBUTES_B.

CONDITION_TYPE NULL VARCHAR2(240) type of Condition Expression,

Function, Counter.CNL_TYPE NULL VARCHAR2(240) Surrogate key used for primary

unique identifiers.


PDF_ID NULL NUMBER Primary key ofOKC_PROCESS_DEFS_B.

CNH_ID NULL NUMBER Primary Key ofOKC_CONDITION_HEADERS_B

SORTSEQ NULL NUMBER Serial Numbers.

LEFT_PARENTHESIS NULL VARCHAR2(240) Left parenthesis.

LEFT_VALUE NULL VARCHAR2(4000) Refer to base table.

RELATIONAL_OPERATOR NULL VARCHAR2(240) Refer to base table.

RIGHT_OPERAND NULL VARCHAR2(4000) Right operand.

RIGHT PARENTHESIS NULL VARCHAR2(240) Right parenthesis


49/132



RIGHT_PARENTHESIS NULL VARCHAR2(240) Right parenthesis.

LOGICAL_OPERATOR NULL VARCHAR2(240) Logical operator.

CSC_CONDITION_OUTCOMES_V

Registration of a PL/SQL process or a workflow with the application foruse as an OUTCOME CONTRACT PROCESS QA PROCESS or


50/132



use as an OUTCOME, CONTRACT PROCESS, QA PROCESS, orFUNCTION in a CONDITION LINE.

View Definition

CREATE VIEW CSC_CONDITION_OUTCOMES_V

as SELECT

ID ID,

PDF_TYPE PDF_TYPE,

SFWT_FLAG SFWT_FLAG,

DESCRIPTION DESCRIPTION,

SHORT_DESCRIPTION SHORT_DESCRIPTION,

COMMENTS COMMENTS,

USAGE USAGE,NAME NAME,

DECODE ( PDF_TYPE,’PPS’,PROCEDURE_NAME,’WPS’,WF_NAME,’ALERT’,NAME,

’SCRIPT’, NAME) EXECUTABLE_NAME,

WF_NAME WF_NAME,

WF_PROCESS_NAME WF_PROCESS_NAME,

PROCEDURE_NAME PROCEDURE_NAME,

PACKAGE_NAME PACKAGE_NAME,

DECODE ( PDF_TYPE, ’PPS’ , ’PROCEDURE’ , ’WPS’ , ’WORK FLOW’ , PDF_TYPE )

PROCESS_DEFINITION_TYPE ,

BEGIN_DATE BEGIN_DATE,END_DATE END_DATE

FROM OKC_PROCESS_DEFS_V

Column Descriptions


ID NULL NUMBER Primary key column.

PDF_TYPE NULL VARCHAR2(240) Process definition type.SFWT_FLAG NULL VARCHAR2(240) Indicates a value was changed

in another language. Not fullyimplemented in 11i


SHORT_DESCRIPTION NULL VARCHAR2(4000) User entered free format textdescription.

COMMENTS NULL VARCHAR2(4000) User entered comment.

USAGE NULL VARCHAR2(240) Process usage.

NAME NULL VARCHAR2(240) Process definition name.

EXECUTABLE_NAME NULL VARCHAR2(240) Descriptive Process definitiontype.

WF_NAME NULL VARCHAR2(240) Workflow name.

WF_PROCESS_NAME NULL VARCHAR2(240) Workflow process name.

PROCEDURE_NAME NULL VARCHAR2(240) PLSQL process procedure name.

PACKAGE_NAME NULL VARCHAR2(150) PLSQL process package name.

PROCESS_DEFINITION_TYPE NULL VARCHAR2(240) Descriptive Process definitiontype.

BEGIN_DATE NULL DATE Begin Date

END_DATE NULL DATE End Date

CSC_CUSTOMERS

CSC_CUSTOMERS stores parties that criticallity is being overridden


51/132



Column Descriptions


PARTY_ID (PK) NOT NULL NUMBER(15) References PARTY_ID ofHZ_PARTIES

CUST_ACCOUNT_ID NULL NUMBER(15) References CUST_ACCOUNT_ID ofHZ_CUST_ACCOUNTS_ALL

ORG_ID NULL NUMBER(15) References ORG_ID ofHZ_CUST_ACCOUNTS_ALL

LAST_UPDATE_DATE NULL DATE Standard Who column

LAST_UPDATED_BY NULL NUMBER Standard Who column

LAST_UPDATE_LOGIN NULL NUMBER Standard Who column


CREATED_BY NOT NULL NUMBER Standard Who columnOVERRIDE_FLAG NOT NULL VARCHAR2(3) Inidcates if the criticallity

is being overidden

OVERRIDDEN_CRITICAL_FLAG NOT NULL VARCHAR2(3) Indicates if the customer iscritical or not

OVERRIDE_REASON_CODE NULL VARCHAR2(30) The reason why the criticallityis being overriden code andcomes from CSC_LOOKUPS withlookup_type =CSC_CRIT_CUST_OVERRIDE_REASONS

ATTRIBUTE1 NULL VARCHAR2(150) Descriptive Flexfield SegmentColumn















CONTEXT NULL VARCHAR2(30) Descriptive Flexfield StructureDefining column

Indexes


CSC_CUSTOMER_U1 UNIQUE 1 PARTY_ID


52/132



CSC_CUSTOMERS_AUDIT_HIST

CSC_CUSTOMERS_AUDIT_HIST is used to store changes in customerscriticallity


53/132



y

Foreign Keys

Primary Key Table Primary Key Column Foreign Key Column

CSC_CUSTOMERS PARTY_ID PARTY_ID

Column Descriptions


CUST_HIST_ID (PK) NOT NULL NUMBER Unique Identifier

PARTY_ID NOT NULL NUMBER(15) References PARTY_ID ofHZ_PARTIES

CUST_ACCOUNT_ID NULL NUMBER(15) References CUST_ACCOUNT_ID of

HZ_CUST_ACCOUNTS_ALLORG_ID NULL NUMBER(15) References ORG_ID of

HZ_CUST_ACCOUNTS_ALL

LAST_UPDATE_DATE NULL DATE Standard Who colum

LAST_UPDATED_BY NULL NUMBER Standard Who colum

LAST_UPDATE_LOGIN NULL NUMBER Standard Who colum

CREATION_DATE NOT NULL DATE Standard Who colum

CREATED_BY NOT NULL NUMBER Standard Who colum

CHANGED_DATE NOT NULL DATE Standard Who colum

CHANGED_BY NOT NULL NUMBER The user who change thecriticallity.

SYS_DET_CRITICAL_FLAG NOT NULL VARCHAR2(1) The criticallity value of thecheck variables for a customer.

OVERRIDE_FLAG NOT NULL VARCHAR2(1) Indicates if the criticallityis overriden.

OVERRIDDEN_CRITICAL_FLAG NOT NULL VARCHAR2(1) Indicates if the action iscritical or not.

OVERRIDE_REASON_CODE NULL VARCHAR2(30) The reason for overriding thecriticallity.

















54/132




Indexes


CSC_CUSTOMERS_AUDIT_HIST_N1 NOT UNIQUE 1 PARTY_ID

CSC_CUSTOMERS_AUDIT_HIST_U1 UNIQUE 2 CUST_HIST_ID


55/132

Column Descriptions



CUST_HIST_ID NOT NULL NUMBER Unique Identifier

PARTY_ID NOT NULL NUMBER References PARTY_ID ofHZ PARTIES


56/132



HZ_PARTIES

CUST_ACCOUNT_ID NULL NUMBER References CUST_ACCOUNT_ID of

HZ_CUST_ACCOUNTS_ALLORG_ID NULL NUMBER References ORG_ID ofHZ_CUST_ACCOUNTS_ALL

LAST_UPDATE_DATE NULL DATE Standard Who Column

LAST_UPDATED_BY NULL NUMBER Standard Who Column

LAST_UPDATE_LOGIN NULL NUMBER Standard Who Column

CREATION_DATE NOT NULL DATE Standard Who Column

CREATED_BY NOT NULL NUMBER Standard Who Column

CHANGED_DATE NOT NULL DATE The date when the change incriticallity was made.

CHANGED_BY NOT NULL NUMBER The user who change the

criticallity.SYS_DET_CRITICAL_FLAG NOT NULL VARCHAR2(1) The criticallity value of the

check variables for a customer.

OVERRIDE_FLAG NOT NULL VARCHAR2(1) Indicates if the criticallityis overriden.

OVERRIDDEN_CRITICAL_FLAG NOT NULL VARCHAR2(1) Indicates if the action iscritical or not.

OVERRIDE_REASON_CODE NULL VARCHAR2(30) The reason for overriding thecriticallity.







ATTRIBUTE7 NULL VARCHAR2(150) Descriptive Flexfield Segment

ColumnATTRIBUTE8 NULL VARCHAR2(150) Descriptive Flexfield Segment

Column









USER_NAME NULL VARCHAR2(100) The name of the user that madethe update.

FULL_NAME NULL VARCHAR2(240) The fullname of the user thatmade the update.

OVERRIDE_REASON_DESC NULL VARCHAR2(30) The description of the reasonwhy the criticallity is beingoverriden code and comes fromCSC_LOOKUPS with lookup_type =CSC_CRIT_CUST_OVERRIDE_REASONS


57/132



CSC_CUSTOMERS_V

View of CSC_CUSTOMERS

View Definition


58/132



View Definition

CREATE VIEW CSC_CUSTOMERS_V

as SELECT

cc.rowid ROW_ID

,cc.party_id

,cc.cust_account_id

,cc.org_id

,cc.last_update_date

,cc.last_updated_by

,cc.last_update_login

,cc.creation_date

,cc.created_by

,cc.override_flag

,cc.overridden_critical_flag

,cc.override_reason_code

,cc.attribute1

,cc.attribute2

,cc.attribute3

,cc.attribute4

,cc.attribute5

,cc.attribute6

,cc.attribute7

,cc.attribute8

,cc.attribute9

,cc.attribute10

,cc.attribute11

,cc.attribute12

,cc.attribute13

,cc.attribute14

,cc.attribute15

,cc.context

,hz.party_name

,hz.party_number

,hz.status

,decode(cc.overridden_critical_flag, ’Y’, ’N’, ’Y’) overridden_noncritical_flag

,decode(cc.override_flag, ’Y’, cc.overridden_critical_flag, NVL(pc.value, ’N’))

net_critical_flag

,pc.value sys_det_critical_flag

,cl.meaning override_reason_desc

from csc_lookups cl

,csc_prof_check_results pc

,hz_parties hz

,csc_customers cc

Where cc.party_id = pc.party_id(+)

and pc.check_id(+) = fnd_profile.value_wnps(’CSC_CRITICAL_CUSTOMER_CHECK’)

and cc.party_id = hz.party_id

and cc.override_reason_code = cl.lookup_code(+)

and cl.lookup_type(+) = ’CSC_CRITCUST_OVERRIDE_REASONS’

Column Descriptions



PARTY_ID NOT NULL NUMBER References PARTY_ID ofHZ_PARTIES

CUST_ACCOUNT_ID NULL NUMBER References CUST_ACCOUNT_ID ofHZ CUST ACCOUNTS ALL


59/132



HZ_CUST_ACCOUNTS_ALL

ORG_ID NULL NUMBER References ORG_ID ofHZ_CUST_ACCOUNTS_ALL


LAST_UPDATED_BY NULL NUMBER Standard Who column

LAST_UPDATE_LOGIN NULL NUMBER Standard Who column


CREATED_BY NOT NULL NUMBER Standard Who column

OVERRIDE_FLAG NOT NULL VARCHAR2(1) Inidcates if the criticallityis being overidden

OVERRIDDEN_CRITICAL_FLAG NOT NULL VARCHAR2(1) Indicates if the customer iscritical or not

OVERRIDE_REASON_CODE NULL VARCHAR2(30) The reason why the criticallityis being overriden code andcomes from CSC_LOOKUPS withlookup_type =CSC_CRIT_CUST_OVERRIDE_REASONS





Column












ColumnCONTEXT NULL VARCHAR2(30) Descriptive Flexfield Structure

Defining column

PARTY_NAME NOT NULL VARCHAR2(50) The name of the customer.

PARTY_NUMBER NOT NULL VARCHAR2(30) The number assigned to thecustomer.

STATUS NOT NULL VARCHAR2(1) The status of the customer fromHZ_PARTIES.

OVERRIDDEN_NONCRITICAL_FLAG NULL VARCHAR2(1) Indicates if the customer iscritical or not

NET_CRITICAL_FLAG NULL VARCHAR2(80) Indicates if the customer iscritical or not

SYS_DET_CRITICAL_FLAG NULL VARCHAR2(80) The criticallity value fromCSC_PROF_CHECK_RESULTS table

OVERRIDE_REASON_DESC NULL VARCHAR2(30) The description of the reasonwhy the criticallity is beingoverriden code and comes fromCSC LOOKUPS with lookup type =


60/132



CSC_LOOKUPS with lookup_type =CSC_CRIT_CUST_OVERRIDE_REASONS

CSC_CUSTOMIZED_PLANS

CSC_CUSTOMIZED_PLANS stores the customer information of acustomized plan


61/132



Foreign Keys


CSC_PLAN_HEADERS_B PLAN_ID PLAN_ID

HZ_CUST_ACCOUNTS CUST_ACCOUNT_ID CUST_ACCOUNT_IDORG_ID CUST_ACCOUNT_ORG

HZ_PARTIES PARTY_ID PARTY_ID

Column Descriptions


ID NOT NULL NUMBER(15) Unique identifier of customer

planPLAN_ID NOT NULL NUMBER(15) References PLAN_ID of

CSC_RSP_PLAN


CUST_ACCOUNT_ID NULL NUMBER(15) References CUST_ACCOUNT_ID inHZ_CUST_ACCOUNTS_ALL table.

CUST_ACCOUNT_ORG NOT NULL NUMBER(15) Operating Unit Identifier

Indexes


CSC_CUSTOMIZED_PLANS_U1 UNIQUE 5 ID

CSC_CUST_PLANS

CSC_CUST_PLANS stores the customer, plan association

Foreign Keys


62/132







Column Descriptions


CUST_PLAN_ID (PK) NOT NULL NUMBER(15) Unique identifier of customerplan

PLAN_ID NOT NULL NUMBER(15) References PLAN_ID ofCSC_RSP_PLANS



CUST_ACCOUNT_ORG NULL NUMBER(15) Operating Unit Identifier

START_DATE_ACTIVE NULL DATE Effective start date ofcustomer plan

END_DATE_ACTIVE NULL DATE Effective end date of customerplan

MANUAL_FLAG NOT NULL VARCHAR2(3) If ’Y’ then Assignment Enginecannot remove customer fromplan portfolio else if ’N’ itcan remove

PLAN_STATUS_CODE NOT NULL VARCHAR2(30) References LOOKUP_CODE ofCSC_LOOKUPS. Values are’’Applied’’, ’’Removed’’,’’Disabled’’

REQUEST_ID NULL NUMBER(15) Request identifier of lastconcurrent program to updatethis record

PROGRAM_APPLICATION_ID NULL NUMBER(15) Application identifier of lastconcurrent program to updatethis record

PROGRAM_ID NULL NUMBER(15) Program identifier of lastconcurrent program to updatethis record

PROGRAM_UPDATE_DATE NULL DATE Last update date of this recordby a concurrent program

LAST_UPDATE_DATE NOT NULL DATE Standard Who column




LAST_UPDATE_LOGIN NULL NUMBER(15) Standard Who columnATTRIBUTE1 NULL VARCHAR2(450) Descriptive Flexfield Segment

Column










63/132









ATTRIBUTE_CATEGORY NULL VARCHAR2(90) Descriptive Flexfield StructureDefining column

OBJECT_VERSION_NUMBER NOT NULL NUMBER(9) Version number of the record

CPN_CUST_ACCOUNT_ID NULL NUMBER(15)

CPN_ORG_ID NULL NUMBER(15)

Indexes


CSC_CUST_PLANS_U1 UNIQUE 1 CUST_PLAN_ID

CSC_CUST_PLANS_U2 UNIQUE 7 PLAN_ID11 PARTY_ID13 CUST_ACCOUNT_ID15 CUST_ACCOUNT_ORG

CSC_CUST_PLANS_AUDIT

CSC_CUST_PLANS_AUDIT stores the history of all customer, planassociation

F i K


64/132



Foreign Keys





Column Descriptions


PLAN_AUDIT_ID (PK) NOT NULL NUMBER(15) Unique identifier of customer

plans auditPLAN_ID NOT NULL NUMBER(15) References PLAN_ID of

CSC_PLAN_HEADERS_B




PLAN_STATUS_CODE NOT NULL VARCHAR2(30) References LOOKUP_CODE ofCS_LOOKUPS_B. Values are’’Applied’’, ’’Removed’’,’’Enabled’’, ’’Disabled’’





LAST_UPDATE_DATE NOT NULL DATE Standard Who columnCREATION_DATE NOT NULL DATE Standard Who column

















65/132






ATTRIBUTE_CATEGORY NULL VARCHAR2(90) Descriptive Flexfield StructureDefining column

OBJECT_VERSION_NUMBER NOT NULL NUMBER(9) Version number of the record

Indexes


CSC_CUST_PLANS_AUDIT_U1 UNIQUE 1 PLAN_AUDIT_ID

CSC_CUST_PLANS_AUDIT_U2 NOT UNIQUE 2 PLAN_ID3 PARTY_ID

CSC_CUST_PLANS_AUDIT_V

This view is based on CSC_CUST_PLANS_AUDIT used in lock rowevent of server side API’s

View Definition


66/132



View Definition

CREATE VIEW CSC_CUST_PLANS_AUDIT_V

as SELECT

CPNA.ROWID ROW_ID,

CPNA.PLAN_AUDIT_ID PLAN_AUDIT_ID,

CPNA.PLAN_ID PLAN_ID,

CPNA.PARTY_ID PARTY_ID,

HP.PARTY_NUMBER PARTY_NUMBER,

HP.PARTY_NAME PARTY_NAME,

HP.PARTY_TYPE PARTY_TYPE,

CPNA.CUST_ACCOUNT_ID CUST_ACCOUNT_ID,

CPNA.CUST_ACCOUNT_ORG CUST_ACCOUNT_ORG,

FL1.MEANING GROUP_NAME,

PNHV.NAME PLAN_NAME,

CPNA.PLAN_STATUS_CODE PLAN_STATUS_CODE,

FL2.MEANING PLAN_STATUS_MEANING,

HCAA.ACCOUNT_NUMBER ACCOUNT_NUMBER,

HCAA.ACCOUNT_NAME ACCOUNT_NAME,

CPNA.REQUEST_ID REQUEST_ID,

CPNA.PROGRAM_APPLICATION_ID PROGRAM_APPLICATION_ID,

CPNA.PROGRAM_ID PROGRAM_ID,

CPNA.PROGRAM_UPDATE_DATE PROGRAM_UPDATE_DATE,

CPNA.CREATION_DATE CREATION_DATE,

CPNA.LAST_UPDATE_DATE LAST_UPDATE_DATE,

CPNA.CREATED_BY CREATED_BY,

CPNA.LAST_UPDATED_BY LAST_UPDATED_BY,

FNDU.USER_NAME USER_NAME,

CPNA.LAST_UPDATE_LOGIN LAST_UPDATE_LOGIN,

CPNA.ATTRIBUTE1 ATTRIBUTE1,















CPNA.ATTRIBUTE_CATEGORY ATTRIBUTE_CATEGORY,

CPNA.OBJECT_VERSION_NUMBER OBJECT_VERSION_NUMBER

FROM

CSC_CUST_PLANS_AUDIT CPNA,

CSC_PLAN_HEADERS_VL PNHV,

FND_LOOKUPS FL1,

FND_LOOKUPS FL2,

FND_USER FNDU,

HZ_PARTIES HP,

HZ_CUST_ACCOUNTS_ALL HCAA

Where CPNA.PLAN_ID = PNHV.PLAN_ID AND

PNHV.PLAN_GROUP_CODE = FL1.LOOKUP_CODE AND

FL1.LOOKUP_TYPE = ’CSC_PLAN_GROUP’ AND

CPNA.PLAN_STATUS_CODE = FL2.LOOKUP_CODE AND

FL2 LOOKUP TYPE = ’CSC PLAN STATUS’ AND


67/132



FL2.LOOKUP_TYPE CSC_PLAN_STATUS AND

FNDU.USER_ID = CPNA.LAST_UPDATED_BY AND

CPNA.PARTY_ID = HP.PARTY_ID AND

CPNA.CUST_ACCOUNT_ID = HCAA.CUST_ACCOUNT_ID (+) AND

CPNA.CUST_ACCOUNT_ORG = HCAA.ORG_ID (+)

Column Descriptions


ROW_ID NULL ROWID Row identifier

PLAN_AUDIT_ID NULL NUMBER(15) Unique identifier of customerplans audit

PLAN_ID NULL NUMBER(15) References PLAN_ID ofCSC_PLAN_HEADERS_B

PARTY_ID NULL NUMBER(15) References PARTY_ID ofHZ_PARTIES

PARTY_NUMBER NULL VARCHAR2(30) Party number

PARTY_NAME NULL VARCHAR2(255) Party name

PARTY_TYPE NULL VARCHAR2(30) Type of party. This is limitedto person, organization, groupor relationship

CUST_ACCOUNT_ID NULL NUMBER(15) Customer Account Identifier


GROUP_NAME NULL VARCHAR2(80) QuickCode meaning for the plangroup code

PLAN_NAME NULL VARCHAR2(30) Plan name

PLAN_STATUS_CODE NULL VARCHAR2(30) References LOOKUP_CODE ofCS_LOOKUPS_B. Values are’’Applied’’, ’’Removed’’,’’Enabled’’, ’’Disabled’’

PLAN_STATUS_MEANING NULL VARCHAR2(80) QuickCode meaning for the planstatus code

ACCOUNT_NUMBER NULL VARCHAR2(30) Account numberACCOUNT_NAME NULL VARCHAR2(240) Account name





CREATION_DATE NULL DATE Standard Who column


CREATED_BY NULL NUMBER(15) Standard Who column

LAST_UPDATED_BY NULL NUMBER(15) Standard Who column

USER_NAME NULL VARCHAR2(100) Name of the user who added theplan to a customer







68/132


oracle customer care technical reference manual

Documents