How to create MVG?

How to create MVG?

First create parent BC and required fields, then create child BC and required fields (or) Select existing Parent and child BC's and check the relationship between them. For MVG relation should be 1:M or M:M.

If there isn’t an existing link between them, create a new link. In link object enter Name, Parent Business Component, Child business Component, Inter Table, Inter parent column, Inter Child Column properties.

Then go to parent BC, click Multi Value Link, It identifies the link that provides the field values from the multi-value group business component (child BC). In this enter Name, Destination Business Component, Destination Link and Use Primary Join (It will convert 1: M to 1:1 relationship). Use Primary Join identifies the foreign key field in the originating, or joined, business component. The foreign key field identifies the primary record in the set of records for one multi-value group.

Next select Multi Value Fields object, these fields are in the originating business component that are populated by the multi-value link. In Parent BC’s Multi Value Fields object enter Multi Value Field Name, Multi Value Link and Field properties.

Next which fields you created in MVF, add in Parent BC List Applet's List columns and edit web layout.

Then create a MVG Applet, in this enter Name, Business Component (Child BC) and Type as MVG. In the list columns enter Name, Field and Display Name. In list columns should enter "SSA Primary Field" as a field.

In MVG Applet go to Control object, enter

Name Caption HTML Row Sensitive HTML TypeMethodInvoke

PopupQueryPick-- OK -- Active-- MiniButton -- CloseApplet


Next go to Parent BC's List Column object. In this where you want to see popup applet, in that record enter MVG Applet name and Runtime Properties.

Then go to View object and edit web layout as View Detail (Parent with Pointer) template.

Next Add view name in screen, add screen in application.

Then Compile the Project.

Certification Questions

1. In order to change the fonts used by your Siebel application, what file(s) should you modify? Select one answer.

A.Siebel.exe file
B.Siebel template files
C.Cascading style sheets
D.SQL scripts to change the data model

2. Which Link property must be populated for a MVG with a M:M relationship, but is not populated for a MVG with a 1:M relationship?

A.Inter Table
B.Destination Field
C.Child Business Component
D.Parent Business Component

3. You have enabled the Workflow Management component group on the server through the Siebel user interface, but you are unable to run workflows using Workflow policies. Which step might have you forgotten to execute? (Choose two.)

A.restarting the Siebel Server service
B.running a Generate Triggers batch job
C.enabling the Generate Triggers component
D.setting the Workflow Policy properties in Tools
E.specifying the triggering event in the detail applet for the workflow step branch following the Start Step

4. Which three are true about a task in Siebel task UI? (Choose three.)

A.It implements process automation.
B.It must be invoked by a run-time event.
C.It consists of a sequenced set of views.
D.It does not support conditional processing.
E.It does not support transactional processing.
F.It is designed for novice users performing complex tasks.

5. Business rules consist, in part, of concepts. Which two are examples of concepts? (Choose two.)

A.Field
B.Entity
C.Value
D.Object

6. Which describes the role of Assignment Objects for Assignment Manager?

A.to identify the people that will be assigned to records
B.to describe when a record should be assigned to candidates
C.to identify the types of data to assign using Assignment Manager
D.to evaluate all people for a matching skill in order to assign records

7. Which statement is true regarding making changes to assignment rules?

A.To make changes you must first deactivate the rule.
B.If you make changes to a released assignment rule, you must release the rule again.
C.Changes to a released assignment rule take affect automatically when the record is saved.
D.Once an assignment rule is released it cannot be changed, it must be revised before it can be edited.

8. Which two statements concerning interface tables are true? (Choose two.)

A.An interface table can populate only one base table.
B.An interface table may populate more than one base table.
C.A base table may be populated by more than one interface table.
D.A base table is always populated by one and only one interface table.

9. When should you use implicit primaries through Enterprise Integration Manager?

A.any time you have more than one child record in the dataset
B.when you need to have multiple primaries associated with a record
C.when the external system defines which child record should be the primary
D.when the external system does not define which child record should be the primary

10. Your Accounts.ifb file appears as follows:
[Siebel Interface Manager]
USER NAME = "SADMIN"
PASSWORD = "SADMIN"
PROCESS = Import Accounts
[Import Accounts]
TYPE = Import
BATCH = 100
TABLE = EIM_ACCOUNT

After running the import, you find that the IF_ROW_STAT for all of your accounts is PARTIALLY IMPORTED, yet you can see the accounts in the Accounts Administration view.
What is the most likely cause of this?

A.Not all of the required flags were set.
B.The EIM job generated an internal error.
C.Some of the required flags were set incorrectly.
D.Not all of the base tables that EIM_ACCOUNT maps to were populated.
E.EIM_ACCOUNT did not contain required information for the S_ACCOUNT base table.

Answers

1. C
2. A
3. AB
4. ACF
5. BC
6. C
7. B
8. BC
9. D
10.D

Pre Default & Post Default

Post Default Value:

The value used for an empty field when the record is initially written to the database. This value is not used if the field is left empty on subsequent updates to the record. The post-default value for the field is used even when the field is not exposed in the user interface.
This property is not validated for a calculated field.

Pre Default Value:

The value used for an empty field when a new record is created through an Add New Record or Copy Record operation. The value can be changed by the user before the record is written to the database. The pre-default value for the field is used even when the field is not exposed in the user interface.
This is true for Copy Record operation only if the No Copy property is set to TRUE.
This property is not validated for a calculated field.

Long List:

A TRUE or FALSE value that specifies whether the Siebel application should attempt to position the cursor on the current value in a long list of values.
When you specify Long List = TRUE for a picklist list, the Siebel application does not keep focus on the current record.
A value of TRUE means that the picklist returns a large set of values, so to scroll through that list of values and position the cursor on the current value in the field could be very costly from a performance standpoint. For this reason, Long List does not keep focus.
TRUE = Recommendation is to set this attribute to TRUE if pick list is expected to contain more than 500 records.

Extension Tables

What is Extension table?

Base table has default columns. Preconfigured extension tables are called Static extension tables and includes generic columns ATTRIB_01 ATTRIB_02...., are the customizable columns which you can use for your purpose other than given by Siebel (ATTRIB_) that you can use to store custom attributes. Static extension tables are already part of the data model so using them does not require updating the physical database. Is it possible to add base and extension table for the same BC? You can also create your own extension tables using the New Table Wizard. Extension tables that you create are changes to the logical schema and therefore must be also be applied to the physical database. Creation of base table is not possible.

Difference between MVG and Dynamic Picklist

What is the difference between MVG & Dynamic PickList?

MVG applet displays the related child records for the parent record. MVG uses link object.

Dynamic picklist displays all the child records for the parent record. It uses join object.

How to create Drilldown in Form applet?

The situation like drilldown on form applet happens rare cases. Always we'll do in list applet. But we can't say that drilldown can't be done in form applet. As I've tried and it's working perfect.
If you've any doubt let me know & try this...

1) Create a control within the Account Entry Applet Or any Applet you want to try for drill down -
Create the following properties:
HTML Type = Link
Field = Name
Method Invoke = Drilldown

1) In the Account Entry Applet create new Drilldown object with the following properties:
Name ? GotoActivity
Hyper Link Field ? Name
View - Account Detail - Activities View
3) Add the control to the applet.

Flow of Siebel application

The data it will get to the application or UI with the help of layers.
The layers are given below,
1. Application layer
2. Business layer
3. Data layer.
The working function of Siebel is it will fetch the data from Data layer then it will give the fetched data to Application layer through Business layer.
(When we enter URL in web client and request send to web server, in the web server the virtual directory receives the request and checks against each installed application and if it finds the application [URL], then the request forward to SWSE (Siebel web server extension). SWSE creates and maintains TCP/IP connections with Siebel server. It obtains the connectivity parameters from eapps.cfg file. Then the object manager takes the request and gives it to the Siebel server, the Siebel server interns sends the request to data manager and data manager send response to Siebel server. The Siebel server interns response back to object manager. The object manager pushes the data on to the web client.)

Joins

Joins: A join object creates a relationship between a business component and table other than its base table.
This relationship allows the business component to use columns from other table.
A join is always 1:1 relationship and it is always between a business component and a table.
Joins are two types.
1. Implicit joins
2. Explicit joins
Implicit joins:
Implicit joins exist as part of the Siebel object architecture. They are not explicitly defined using Siebel tools.
Unlike joins that you define in Siebel tools user can update the columns from implicit joins.
Implicit joins exist for the following
1. All 1:1 (_X) extension tables and all relevant intersection tables.
2. Extension tables of S_PARTY, such as S_ORG_EXT, S_CONTACT, S_POSTN and S_USER.
Explicit joins:
We are explicitly defined using Siebel tools.
When creating a joined field in a BC, you can change the type property from the default DTYPE_TEXT to a more appropriate type. DTYPE_TEXT refers to the data as a string of length 2000 or less
The Type property of a Field object type definition corresponds to the physical type of the column in the underlying table.
For example, if you are joining a table column that contains phone numbers, you can change the type field to DTYPE_PHONE.
Set the “outer join flag” to “TRUE”, if you want to retrieve all the records in the business component even when the joined fields are empty.
 “Join specification” object definition identifies the foreign key field in the business component & the primary key column in the joined table.
 The “Source field property” identifies the foreign key column in the joined table.
 In rare circumstances, there can be multiple join specifications in a single join.
For example, the sub campaign BC has a join to the S_LANG table with two join specifications.
 A “Join constraint” is a constant-valued search specification applied to a column during a join. It is for use with outer join.
 “Foreign key column” represents in the base table, pointing to rows in a particular table used in joins.
 “Join table” provides the columns to the BC through the join. It is a master table.
 The “Primary key column” identifies the joined table. Every standard table in standard Siebel application has a ROW_ID column that uniquely identifies rows in the table.
Mapped Column: Columns in the joined table are available for use in the fields in the BC.
 When bring in party data into a nonparty BC, create a new join with the join specification based on PAR_ROW_ID.
 When bringing in party data into a party BC, use appropriate explicit join.
 When mapping fields in party BC, use the implicit join for the extension table.
 You cannot use a pre-default value in the regular way as a default field value if nothing is specified when a record is inserted.

Types of Siebel Applications

Siebel CRM Applications are built on a common architecture & allow you to implement business processes based on the standard functionality.
Types of Siebel enterprise application:
a) Employee Applications:
b) Customer Applications:
c) Partner Applications:
1. Siebel Sales: It is used by a company’s sales reps and manager to manage accounts, sales, opportunities and contacts.
2. Siebel Call Center: It is use by a company’s telesales & service representatives.
3. Siebel eSales: It is used by customer to purchase products over the web. Includes search & product comparison mechanisms and online ordering capabilities.
4. Siebel Partner Portal: It is used by a company’s partner to communicate, collaborate & conduct business with a web based interface

Diff b/w Retesting and Regression Testing

What is difference between Retesting and Regression Testing?

Retesting: It is conformation testing after a defect is fixed, developers will send that to testers as status changed to RPSIT. Then once again we will go for “retest” that test case for confirming the original defect has been successfully removed.

Regression Testing: Testing which ensures that existing build functionality remains same even a new build is released.

In Real Time: Suppose a version 2.1 is existing and a new requirement comes say 2.2 and this 2.2 works properly with existing 2.1 functionality.

What is CRM?

CRM Stands for “Customer Relationship Management“. CRM is a Process or Methodology used to learn more about customers needs and behaviors in order to develop stronger relationships with them.

It will help together lots of Pieces of information about Customer, Sales, Marketing effectiveness, and responsiveness and Market trends.CRM is the Business Strategy that aims to Understand, Anticipate, and Manage and personalize the needs of an Organizations Current and Potential Customer.

About Siebel CRM

Siebel is a brand name of Oracle Corporation. Siebel System Inc., founded by Thomas Siebel in 1993, was principally engaged in the design, Development, Marketing and support of CRM applications. On September 12, 2005 Oracle Corporation had agreed to buy Siebel System for $5.8 billion.

Major Releases:
Oracle Siebel 8.0
Oracle Siebel 7.8
Siebel 7.7
Siebel 7.5
Siebel 7.0
Siebel 6 (also known as Siebel 2000)
Siebel 99
Siebel 98

Siebel system is the worlds leading provider of “Customer Relation Management " software solutions and a leading provider of software applications for business intelligence and standard-based integration. Siebel provide CRM software solutions for any kind of organization, any type of business and any type of budget.

Priority & Severity

Priority: How important to fix the bug & it will be change according to situation.
P1- High-- No work around is possible. (Menu- New if not possible , need to fix immediately)
P2- Medium-- Before release we need to fix, work around is possible.
P3- Low-- If we have time, it will fix, otherwise it should move to deferred status.

Severity: How bad the bug is and impacts all the application. (OR) How serious the defect.
S1- Critical-- System crash (Data loss)
S2- Major-- Wrong result, loss of functionality (Like in calculator missing +, _, *, %,..)
S3- Medium-- Miss Spelled
S4- Minor

V- Model

Explain the process of V-Model?

Main theme of V-Model is Verification and Validation.
Verification represents “Are we building the product RIGHT?" i.e. Verification is a process to verify the software product or application is developed the right way.

Validation is a process of finding out if the product being built is right? i.e. whatever the software product is being developed, it should do what the user expects it to do.
All types of testing methods are basically carried out during the Validation process. Test plan, test suits and test cases are developed, which are used during the various phases of Validation process.

Requirement & Gap Analysis:

- Business analyst (BA)gathers the requirements from Client and prepares Business Requirement Document (BRD)
- User Acceptance Testers (UAT) go through the same BRD and Prepares UAT test case design/Checklist & UAT test plan document

System Design & Planning:

- SA review and go through the BRD and prepares SRS document
- System testers review and go through the SRS and prepare System test case
design & test plan documents

Architect & Module Design:

- Senior developers review and go through the SRS and prepares the HLD & LLDs
- Development team review and go through the HLD and LLDs then prepare the integration & Unit Test case design and test plan documents

Coding:
Once the Coding is done same programming team would validate the developed system code by performing the Unit, Integration testing based Unit & Integration test case design and plan.

System Testing: Testers validate the developed system by executing the design test cases against the application as per test plan
UAT testing: After System testing, UAT testers validate the developed application based UAT test case design & test plan.

V-Model Advantages:

1. An important aspect of this model is that testing activities like planning, test designing
happens well before coding
2. Its more flexible compare to Waterfall model

V-Model disadvantages:

1. It needs lot of resources and money.
2. it needs an established process to implement
3. It can be implemented by only some big companies

Waterfall Model

Explain the process of Waterfall Model?

The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Requirements, Design & Planning, Coding, Testing and Maintenance.

 In this model each phase has a well defined starting and ending point, with identifiable deliveries to the next phase
 The outputs from a specific stage serve as the initial inputs for the following stage.

Advantages (Pros):

In this model there would be proper design documentation
 Well defined tasks and deliverables
 This will be useful for large complex projects

Disadvantages (Cons):

Each phase should be completed before starting the next phase; it’s difficult to go back to the earlier phase if any problem is occurred.
Till the build is given for testing, the testers will be Idle. Hence man power is wasted.

System Testing

What is System testing?
The process of performing a variety of tests on a system to explore functionality or to identify problems.
In this three types of testing levels are there.
Usability Testing
Functional Testing
Non-Functional Testing
a. Usability testing/User Interface testing (UIT): The testing team validating the user friendliness of the application like
 Easy to use : Verifying that application screen are understandable to layman level
 Look and feel : Verifying that application screens are attractable
 Speed interface: verifying that the application is having short navigations to complete the tasks.
 Verifying the spelling of each word in every screen
 Verifying the background color of each screen
 Verifying the borders of each and every section available in the application screens
 Verifying the object alignment in every screen
 Verifying the line spacing uniform between all the objects through the screens
b. Functionality testing: In this phase testers are validating the developed application functionality against SRS document(It is a block box technique)
 Validating the application behavior against SRS doc
 Input & output validation ( Taking correct type and size i/ps and providing correct o/ps)
 Backend updating coverage (The impact of front end screen operations on data tables content)
c. Non functionality testing:
 Reliability / durability: measures the application stability under load and continuation usage
 Compatibility/Portability: Validating the application functionality in customer expected platforms like different browser & Operating systems
Ex1: Performing the system testing in IE, Mozilla Firefox, Opera, Google Chrome, etc is called Browser compatibility testing
Ex2: Performing the system testing in Windows XP, Vista, W7, and Mac etc is called Operating System compatibility testing

 Configuration testing : Validating the application functionality in customer expected hardware platforms like different hard ware’s & Networks
Ex: Technology networks, Topology Networks, Printers, high end & Low configuration systems (like 32 bits, 64 bits, RAM levels, Processor levels, etc)
 Internationalization testing: Validating the developed soft ware with multi language characters
 Patch installation testing: Once any patches installed in to application servers from Microsoft updates and Norton’s security updates testers would perform the smoke level of application testing
Performance testing: Validating the developed application under different levels of load and configuration
Note1: Performance testing the part of non functionality testing which would be tested by the separate performance testing team
Note2: Load, Stress, Endurance, Data volume testing are comes under part of performance testing
 Load Testing: Performing the application testing under customer expected configuration & load
Note: Load/ Scale means that no: of concurrent users are accessing the that software
 Stress testing: Performing the application testing under customer expected configuration and peak load to breaking point of load
 Endurance /Soak testing: Performing the application testing under customer expected configuration and multiple levels of load to determine if the application can sustain the continuous expected load

Unit Testing

What is Unit Testing or White Box Testing?

White Box testing means while the developer developing the code, they are testing the code of an application with different techniques.
White Box Testing using these techniques
Basic path coverage => whether the corresponding program is running/not without having runtime errors.
Control structure coverage=> verifies the correctness of taking i/ps and providing o/ps of that program.
Program technique coverage => to calculate the execution time of a program.
Mutation coverage=> verifying that whether our program correctly and completely tested/not.

Defect Life Cycle

What is defect life cycle?

While the tester logs the defect, he set the status of defect as new and assigns it to dev. Then developer will open and fix it, after change the defect status as RPSIT. After SIT build complete, Build master change defect status as RTV and assign to tester. Then tester will test it, if defect pass it will close otherwise it will be reopen and again assign to dev.
Duplicate? - When two bugs are same, which one is log first that is in open, another one is in duplicate status.
Deferred? - Which bugs are not affected by other functionality, these bugs are set in deferred status
Cancelled?
Rejected? - If the developer feels that the bug is not genuine (valid), he rejects the bug.
On hold? – Which bugs are depending on another bug, these bugs are set as “on hold”.

Design Test Cases

How to design Test Cases?

First BA will conduct “walk through”, it represents the meeting with STG team, dev team and testing manager for explaining business requirements one by one. Any one can have queries, BA will clarify. After complete the walk through, peer review meeting on requirements. Then STG team will prepare the test cases based on the F.R.S and using ECP (Equalence Class Partition), BVA (Boundary Value Analysis) techniques. Once complete the preparation of test cases, STG will conduct internal buddy review on prepared TCs and getting approval from architect, designer and BA. Then approved test cases will upload in QC.

Difference between 7.5 and 7.8

What is the primary difference between Siebel 7.5.2 and 7.7 Versions ?

Are having lot of differences between siebel 7.7 and 7.5.2. the primary difference among them is " Symbolic strings are available in Siebel 7.7 and not available in 7.5.2". hence the future scope for upgradation like things are high in siebel 7.7.

Optimization techniques in EIM
1) Limit base tables and columns to be processed by using : only base Tables,ignore base Tables,only base Columns,ignore base Columns.
2) Always delete batches from EIM tables upon completion. Leaving old batches in the EIM table wastes space and can adversely affect performance. For other suggestions on working with batches.
3) Run independent EIM jobs in parallel. Two or more EIM processes can be started simultaneously by using the Siebel Server Manager.
4) Trace Flag Settings, using Synonyms, primary key only Parameters
Limiting the Number of Records and Rows for Merge Processes.
like this many techniques are there which will optimize the EIM process

Campaign Management in Siebel

Campaign Management

Campaign Management helps to promote the product to current customers or to get new customers across channels of communication like phone, email, T.V, flexi, etc. The goal of a campaign management is to create an opportunity that results in a sale and brand recognition.

First login as a sales rep in to Siebel application and open sitemap, in that click on campaign management, select campaign list and create new campaign, in this enter campaign name, start & end dates and save the record. After creating the record, drilled (click) on the campaign list, then select “Design” view, in this click on "Segments/Lists" (and we can add segments here). In this screen status will make change from “In Planning” to “Launched”, then the color will change from yellow to green, it means your funding is approved and selects one wave (It’s a Siebel terminology) then save the record. In this we create a list for campaign.

Again you go to sitemap, click on List Management. Siebel Campaigns use List Management to create and manage lists of contacts and prospects within your applications for use in marketing campaigns. A list is defined as a grouping of contact or prospect records in the Siebel database. Select "My Lists" view in “List Management” then create a new list, then drilled on the list. In this you will see one column "File Name". When you did campaign, you got responses from customers these responses stored in excel sheets. These files are in outside of Siebel, you can select these files through “File Name” column. Select “Data type” as Tab Delimited and save the record.

Now in the "List Contacts and Prospects" view doesn't have records. Whatever files are selecting from outside, that files are in "List Import" view, in this records doesn't have column names. You will select one "List Import Format" from outside (you will ask company people which format we are using in real time) and save the record, then column names will be available for records. After click on “Launch Import” button, that will shows how many records are importing from file and how many prospects are created. Now whose customers are importing from outside, these are in "List Contacts and Prospects" view and here if u promote these customers, Siebel automatically can create an account for that customers.




Contacts are customers already in the Siebel database. Prospects are potential customers that have yet to be screened, qualified, and promoted to contacts.

Testing

hai

hai