ABAddressBookRef addressBook = ABAddressBookCreate();
ABRecordRef person = ABPersonCreate();

ABRecordSetValue(person, kABPersonFirstNameProperty, @"Sudha" , nil);
ABRecordSetValue(person, kABPersonLastNameProperty, @"Reddy", nil);

ABMutableMultiValueRef phoneNumberMultiValue = ABMultiValueCreateMutable(kABPersonPhoneProperty);
ABMultiValueAddValueAndLabel(phoneNumberMultiValue, @"1234567890", kABHomeLabel, nil);
ABMultiValueAddValueAndLabel(phoneNumberMultiValue, @"9876543210", kABPersonPhoneMobileLabel, nil);
ABMultiValueAddValueAndLabel(phoneNumberMultiValue, @"04022222222", kABWorkLabel, nil);
ABRecordSetValue(person, kABPersonPhoneProperty, phoneNumberMultiValue, nil);

ABMutableMultiValueRef emailMultiValue = ABMultiValueCreateMutable(kABPersonEmailProperty);
ABMultiValueAddValueAndLabel(emailMultiValue, @"whatever@gmail.com", kABWorkLabel, nil);
ABRecordSetValue(person, kABPersonEmailProperty, emailMultiValue, nil);

NSDictionary *dictionary = [[NSDictionary alloc] initWithObjects: [NSArray arrayWithObjects:@"1234 Whatever Street", @"Hyderabad", @"AP", @"INDIA", @"500008", nil] forKeys: [NSArray arrayWithObjects: (NSString *)kABPersonAddressStreetKey, (NSString *)kABPersonAddressCityKey, (NSString *)kABPersonAddressStateKey, (NSString *)kABPersonAddressCountryKey, (NSString *)kABPersonAddressZIPKey, nil]];
ABMultiValueRef addressMultiValue = ABMultiValueCreateMutable(kABDictionaryPropertyType);
ABMultiValueAddValueAndLabel(addressMultiValue, (CFDictionaryRef *)dictionary, kABWorkLabel, nil);
ABRecordSetValue(person, kABPersonAddressProperty, addressMultiValue, nil); ABRecordCopyValue(person, kABPersonAddressProperty);

ABAddressBookAddRecord(addressBook, person, nil);
ABAddressBookSave(addressBook, nil);

CFRelease(person);
CFRelease(addressMultiValue);
CFRelease(phoneNumberMultiValue);
CFRelease(emailMultiValue);
[dictionary release];

@echo off
cls
echo Creating Accounts
echo ------------------
for /f "tokens=1-3" %%A in (userlist.txt) do (dsadd user "CN=%%A,ou=Network,dc=mailserver,dc=com" -fn %%B -ln %%C -display "%%B %%C" -upn %%A@thenguyen.local -pwd Passw0rd1 -mustchpwd No -disabled no)
echo ------------------
pause

ou -> Organization Unit (given as “Network” in the script, replace it with your Organization Unit name)
dc -> Domain Controller (given as “mailserver” in the script, replace it with your Domain Controller name, donot chnage the value dc=com)

Create a file with name “userlist.txt” and save all the user details in the below mentioned format.

raju    Raju    Rao
kalyan  Chakra  Naidu
chiru   Chiru   Reddy

First Column -> User Name
Second Column -> First Name
Thirm Column -> Last Name

Place both the batch and userlist.txt files in same folder.
Run the batch file. The users mentioned in userlist.txt will be created.

Note: User must have Administrator privilages to run this batch.

//@@@@@@@@@@@@@ XSLT snippet  @@@@@@@@@@@@@@@@

<?xml version="1.0" encoding="iso-8859-1"?>

<xsl:stylesheet version="1.0" xmlns:xsl="<a href="http://www.w3.org/1999/XSL/Transform">http://www.w3.org/1999/XSL/Transform</a>">

<xsl:template match="/">

<ul>

<xsl:for-each select="Collection/Content">

<li>

<a>

<xsl:attribute name="href">

<xsl:value-of select="QuickLink"/>

</xsl:attribute>

<xsl:value-of select="Title"/>

</a>

<p  >

<xsl:value-of select="" />

</p>

</li>

</xsl:for-each>

</ul>

</xsl:template>

</xsl:stylesheet>

//@@@@@@@@@@@@@ XSLT snippet ENDS @@@@@@@@@@@@@@@@

• When we have Data Targets where we are feeding most of the Info Objects with the Routine.

Note – When we implement Expert Routine it disables Star Routine, End Routine and Transformation Rules.

Example

Splitting one Record to Multiple Records.

SOURCE (INPUT)

Create these Info Objects

We can see in Screen-Shot 1 we are doing the Transformation.

In Screen-Shot 2 we can see that, the same screen of Transformation, We need to go to Edit and choose Export Routine.

Then Start Routine, End Routine and Transformations will get disabled.

Screen-Shot1

Screen-Shot2

In Screen-Shot3 we have to write the code.

Screen-Shot3

We can see in Screen-Shot4 Export Routine has been created.

Screen-Shot4

In Screen-Shot5 we can see how single Record is splitted in to Multiple Records

Screen-Shot5

There are four kinds of exceptions in PL/SQL they are

1)Named system exceptions.

2)Named programmer-defined exceptions.

3)Unnamed system exceptions.

4)Unnamed programmer-defined exceptions.

1)Named system exceptions.

Exceptions that have been given names by PL/SQL and raised as a result of an error in PL/SQL.For example, PL/SQL raises the predefined exception NO_DATA_FOUND if a SELECT INTO statement returns no rows.These Exceptions are raised automatically when an error condition occurs.

Following are few examples of Named system Exceptions

Exception Raised when

NO_DATA_FOUND A SELECT INTO statement returns no rows, or your program references a deleted element in a nested table or an uninitialized

element in an index-by table.

TOO_MANY_ROWS A SELECT INTO statement returns more than one row.

ZERO_DIVIDE A program attempts to divide a number by zero.

Here is an example of a procedure that uses a Named System Exception:

CREATE OR REPLACE PROCEDURE Employee_Details(pempno in Number) IS

-- declare record variable that represents a row fetched from the employees table

employee_rec emp%ROWTYPE;

BEGIN

SELECT ename,job,sal INTO employee_rec.ename,employee_rec.job,employee_rec.sal from emp WHERE empno=pempno;

Exception

when TOO_MANY_ROWS then

DBMS_OUTPUT.PUT_LINE('The following employee has Duplicate Records'||pempno);

when others then

DBMS_OUTPUT.PUT_LINE('Some other Error occured');

END;

/

In this example, we are trapping the Named System Exception TOO_MANY_ROWS . We are also using the WHEN OTHERS clause to trap all remaining exceptions.

2)Named programmer-defined exceptions.

Sometimes, it is necessary for us to name and trap our own exceptions – ones that aren’t defined already by PL/SQL. These are called Named Programmer-Defined Exceptions.

These Exceptions have to be declared in Declaration section of PL/SQL block.

Here is an example of a procedure that uses a Named Programmer-Defined Exception:

CREATE OR REPLACE PROCEDURE add_new_order
(order_id_in IN NUMBER, sales_in IN NUMBER)
IS
no_sales EXCEPTION;

BEGIN
IF sales_in = 0 THEN
RAISE no_sales;

ELSE
INSERT INTO orders (order_id, total_sales )
VALUES ( order_id_in, sales_in );
END IF;

EXCEPTION
WHEN no_sales THEN
raise_application_error (-20001,'You must have sales in order to submit the order.');

WHEN OTHERS THEN
raise_application_error (-20002,'An error has occurred inserting an order.');

END;

In this example, we have declared a Named Programmer-Defined Exception called no_sales in our declaration statement with the following code:

no_sales EXCEPTION;

We’ve then raised the exception in the executable section of the code:

IF sales_in = 0 THEN
RAISE no_sales;

Now if the sales_in variable contains a zero, our code will jump directly to the Named Programmer-Defined Exception called no_sales.

Finally, we tell our procedure what to do when the no_sales exception is encountered by including code in the WHEN clause:

WHEN no_sales THEN
raise_application_error (-20001,’You must have sales in order to submit the order.’);

We are also using the when others clause to trap all remaining exceptions:

WHEN OTHERS THEN
raise_application_error (-20002,’An error has occurred inserting an order.’);

3)Unnamed system exceptions.

Exceptions that are raised as a result of an error in PL/SQL or RDBMS processing but have not been given names by PL/SQL. Only the most common errors are so named; the rest have numbers and can be assigned names with the special PRAGMA EXCEPTION_INIT syntax.

4)Unnamed programmer-defined exceptions.

Exceptions that are defined and raised in the server by the programmer. In this case, the programmer provides both an error number (between -20000 and -20999) and an error message, and raises that exception with a call to RAISE_APPLICATION_ERROR. That error, along with its message, is propagated back to the client-side application.

UNDER MODELING WE HAVE ADMINISTRATION.

WE CAN SEE THAT IN SCREENSHOT 1.

CLICK ON ADMINISTRATION.

SCREENSHOT 1

NOW UNDER ADMINISTRATION WE CAN SEE REMODELLING WHICH IS MARKED.WE CAN SEE THAT IN SCREENSHOT 2.

CLICK ON THAT.

SCREENSHOT 2

AFTER CLICKING ON REMODELLING WE GET A POP UP.

WE CAN SEE THAT IN SCREENSHOT 3.

CLICK OK ON THE WARNING.

SCREENSHOT 3

WE CAN SEE IN SCREENSHOT 4.

GIVE THE REMODELING RULE NAME AND THE INFOPROVIDER FROM WERE

YOU WANT TO GET YOUR TARGET (CUBE).

THEN CLICK ON CREATE.A POP UP WILL COME.WE NEE TO GIVE THE DESCRIPTION AND THEN ENTER.

WE CAN SEE IN SCREENSHOT 5.

CLICK ON THE BUTTON WHICH IS MARKED IN RED.

THAT IS CALLED (ADD AN OPERATION TO LIST).

SCREENSHOT 4

SCREENSHOT 5

SCREENSHOT 6

WE CAN SEE IN SCREENSHOT 6.

WE GET A POP UP, IN THAT WE HAVE THE FLEXIBILTY TO

• ADD CHARACTERISTIC
• DELETE CHARACTERISTIC
• REPLACE CHARACTERISTIC
• ADD KEY FIGURE
• DELETE KEY FIGURE
• REPLACE KEY FIGURE

WE CAN SEE IN SCREENSHOT 7

HERE I AM ADDING ZK_REG TO CUBE.

ZK_REG IS A CHARACTER.

WE HAVE TO ASSIGN IT TO A DIMENSION.

SCREENSHOT 7

IF WE TAKE CONSTANT WE WILL BE GETTING FIXED VALUE TO THE FIELD WE ARE ADDING.

HERE ZK_REG (REGION) IS AN EXCLUSIVE ATTRIBUTE OF ZK_CNO.

WE CAN SEE THAT IN SCREENSHOT 8.

SCREENSHOT 8

SCREENSHOT 9

WE CAN SEE IN SCREENSHOT 9.

THE FIELD ZK_REG IS ADDED TO THE CUBE.

THE SAME WAY WE CAN DELTE AND REPLACE CHARACTERISTIC.