How do I make a header column in a pivot table a field from the table
I am trying to reference a field for a header column in a pivot table. for example: 2006 - Cat, 2006-Dog
I am trying to get the following result:
2006-Cat January February March April May June July August September October November December Totals
Euthanise 159 203 188 252 376 501 393 315 304 276 212 207 3386
Intake 192 220 234 305 412 538 409 330 329 305 244 241 3759
Redeem 10 4 4 3 5 3 2 1 2 1 2 5 42
Rescue 0 0 2 10 0 0 0 1 0 2 0 4 19
2006-Dog January February March April May June July August September October November December Totals
Euthanise 306 375 347 341 458 484 385 441 317 384 325 318 4481
Intake 455 514 495 465 571 595 486 570 438 511 434 473 6007
Redeem 65 63 57 34 57 43 58 46 58 67 53 59 660
Rescue 0 0 0 1 0 0 0 0 3 1 0 0 5
2007-Cat January February March April May June July August September October November December Totals
Euthanise 223 265 229 275 569 508 451 359 310 318 231 225 3963
Intake 268 286 274 315 594 567 488 397 329 344 279 249 4390
Redeem 11 7 11 1 5 2 0 2 4 3 16 2 64
Rescue 7 0 0 1 0 1 2 1 1 0 1 0 14
2007-Dog January February March April May June July August September October November December Totals
Euthanise 436 374 313 343 395 362 422 403 394 350 275 343 4410
Intake 594 510 480 477 508 520 553 502 509 544 410 480 6087
Redeem 67 72 77 57 47 51 50 40 41 62 45 45 654
Rescue 2 3 0 1 0 0 4 0 3 0 1 1 15
Any help is greatly appreciated.
<?xml version="1.0" encoding="UTF-8" ?>
- <ROWSET>
- <ROW>
<header>2006 - CAT</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Euthanise</cue>
<anicnt>159.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Intake</cue>
<anicnt>192.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Redeem</cue>
<anicnt>10.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Euthanise</cue>
<anicnt>203.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Intake</cue>
<anicnt>220.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Redeem</cue>
<anicnt>4.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Euthanise</cue>
<anicnt>188.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Intake</cue>
<anicnt>234.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Redeem</cue>
<anicnt>4.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Rescue</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Euthanise</cue>
<anicnt>252.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Intake</cue>
<anicnt>305.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Redeem</cue>
<anicnt>3.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Rescue</cue>
<anicnt>10.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Euthanise</cue>
<anicnt>376.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Intake</cue>
<anicnt>412.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Redeem</cue>
<anicnt>5.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Euthanise</cue>
<anicnt>501.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Intake</cue>
<anicnt>538.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Redeem</cue>
<anicnt>3.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Euthanise</cue>
<anicnt>393.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Intake</cue>
<anicnt>409.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Redeem</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Euthanise</cue>
<anicnt>315.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Intake</cue>
<anicnt>330.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Redeem</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Euthanise</cue>
<anicnt>304.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Intake</cue>
<anicnt>329.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Redeem</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Euthanise</cue>
<anicnt>276.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Intake</cue>
<anicnt>305.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Redeem</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Rescue</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Euthanise</cue>
<anicnt>212.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Intake</cue>
<anicnt>244.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Redeem</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Euthanise</cue>
<anicnt>207.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Intake</cue>
<anicnt>241.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Redeem</cue>
<anicnt>5.0</anicnt>
</ROW>
- <ROW>
<header>2006 - CAT</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Rescue</cue>
<anicnt>4.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Euthanise</cue>
<anicnt>306.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Intake</cue>
<anicnt>455.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Redeem</cue>
<anicnt>65.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Euthanise</cue>
<anicnt>375.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Intake</cue>
<anicnt>514.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Redeem</cue>
<anicnt>63.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Euthanise</cue>
<anicnt>347.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Intake</cue>
<anicnt>495.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Redeem</cue>
<anicnt>57.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Euthanise</cue>
<anicnt>341.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Intake</cue>
<anicnt>465.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Redeem</cue>
<anicnt>34.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Euthanise</cue>
<anicnt>458.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Intake</cue>
<anicnt>571.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Redeem</cue>
<anicnt>57.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Euthanise</cue>
<anicnt>484.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Intake</cue>
<anicnt>595.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Redeem</cue>
<anicnt>43.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Euthanise</cue>
<anicnt>385.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Intake</cue>
<anicnt>486.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Redeem</cue>
<anicnt>58.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Euthanise</cue>
<anicnt>441.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Intake</cue>
<anicnt>570.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Redeem</cue>
<anicnt>46.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Euthanise</cue>
<anicnt>317.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Intake</cue>
<anicnt>438.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Redeem</cue>
<anicnt>58.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Rescue</cue>
<anicnt>3.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Euthanise</cue>
<anicnt>384.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Intake</cue>
<anicnt>511.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Redeem</cue>
<anicnt>67.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Euthanise</cue>
<anicnt>325.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Intake</cue>
<anicnt>434.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Redeem</cue>
<anicnt>53.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Euthanise</cue>
<anicnt>318.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Intake</cue>
<anicnt>473.0</anicnt>
</ROW>
- <ROW>
<header>2006 - DOG</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Redeem</cue>
<anicnt>59.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Euthanise</cue>
<anicnt>223.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Intake</cue>
<anicnt>268.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Redeem</cue>
<anicnt>11.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Rescue</cue>
<anicnt>7.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Euthanise</cue>
<anicnt>265.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Intake</cue>
<anicnt>286.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Redeem</cue>
<anicnt>7.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Euthanise</cue>
<anicnt>229.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Intake</cue>
<anicnt>274.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Redeem</cue>
<anicnt>11.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Euthanise</cue>
<anicnt>275.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Intake</cue>
<anicnt>315.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Redeem</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Euthanise</cue>
<anicnt>569.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Intake</cue>
<anicnt>594.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Redeem</cue>
<anicnt>5.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Euthanise</cue>
<anicnt>508.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Intake</cue>
<anicnt>567.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Redeem</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Euthanise</cue>
<anicnt>451.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Intake</cue>
<anicnt>488.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Rescue</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Euthanise</cue>
<anicnt>359.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Intake</cue>
<anicnt>397.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Redeem</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Euthanise</cue>
<anicnt>310.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Intake</cue>
<anicnt>329.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Redeem</cue>
<anicnt>4.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Euthanise</cue>
<anicnt>318.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Intake</cue>
<anicnt>344.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Redeem</cue>
<anicnt>3.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Euthanise</cue>
<anicnt>231.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Intake</cue>
<anicnt>279.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Redeem</cue>
<anicnt>16.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Euthanise</cue>
<anicnt>225.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Intake</cue>
<anicnt>249.0</anicnt>
</ROW>
- <ROW>
<header>2007 - CAT</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Redeem</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Euthanise</cue>
<anicnt>436.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Intake</cue>
<anicnt>594.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Redeem</cue>
<anicnt>67.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>January</MNTH>
<imonth>1</imonth>
<cue>Rescue</cue>
<anicnt>2.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Euthanise</cue>
<anicnt>374.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Intake</cue>
<anicnt>510.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Redeem</cue>
<anicnt>72.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>February</MNTH>
<imonth>2</imonth>
<cue>Rescue</cue>
<anicnt>3.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Euthanise</cue>
<anicnt>313.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Intake</cue>
<anicnt>480.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>March</MNTH>
<imonth>3</imonth>
<cue>Redeem</cue>
<anicnt>77.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Euthanise</cue>
<anicnt>343.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Intake</cue>
<anicnt>477.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Redeem</cue>
<anicnt>57.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>April</MNTH>
<imonth>4</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Euthanise</cue>
<anicnt>395.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Intake</cue>
<anicnt>508.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>May</MNTH>
<imonth>5</imonth>
<cue>Redeem</cue>
<anicnt>47.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Euthanise</cue>
<anicnt>362.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Intake</cue>
<anicnt>520.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>June</MNTH>
<imonth>6</imonth>
<cue>Redeem</cue>
<anicnt>51.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Euthanise</cue>
<anicnt>422.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Intake</cue>
<anicnt>553.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Redeem</cue>
<anicnt>50.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>July</MNTH>
<imonth>7</imonth>
<cue>Rescue</cue>
<anicnt>4.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Euthanise</cue>
<anicnt>403.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Intake</cue>
<anicnt>502.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>August</MNTH>
<imonth>8</imonth>
<cue>Redeem</cue>
<anicnt>40.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Euthanise</cue>
<anicnt>394.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Intake</cue>
<anicnt>509.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Redeem</cue>
<anicnt>41.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>September</MNTH>
<imonth>9</imonth>
<cue>Rescue</cue>
<anicnt>3.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Euthanise</cue>
<anicnt>350.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Intake</cue>
<anicnt>544.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>October</MNTH>
<imonth>10</imonth>
<cue>Redeem</cue>
<anicnt>62.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Euthanise</cue>
<anicnt>275.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Intake</cue>
<anicnt>410.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Redeem</cue>
<anicnt>45.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>November</MNTH>
<imonth>11</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Euthanise</cue>
<anicnt>343.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Intake</cue>
<anicnt>480.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Redeem</cue>
<anicnt>45.0</anicnt>
</ROW>
- <ROW>
<header>2007 - DOG</header>
<MNTH>December</MNTH>
<imonth>12</imonth>
<cue>Rescue</cue>
<anicnt>1.0</anicnt>
</ROW>
</ROWSET>
Similar Messages
-
Hi,
Just got the iphone 4s.
can't figure out how to make it request a password to install apps.
kid I babysit bought like 4 of them before I saw what he was doing... can't have that happen again.
thanksSettings > General > Restrictions > Installing Apps > OFF
Settings > General > Restrictions > In-App Purchases > OFF
Settings > General > Restrictions > Require Password > Immediately -
How can I make firefox move my images in development mode - it works from the web and with IE
Viewing web pages with Firefox from local files does not permit images to be moved. IE does allow this. Moving images from the web are fine. Why is this - code is shown below
== This happened ==
Every time Firefox opened
== I first tried it ==
== Troubleshooting information ==
Moving an Image
Hmove=-100;
function moveObjRight(obj)
obj.style.left=Hmove;
Hmove+=2;
if(HmoveDo you have that problem when running in the Firefox SafeMode?
[http://support.mozilla.com/en-US/kb/Safe+Mode]
''Don't select anything right now, just use "Continue in SafeMode."''
If not, see this:
[http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes] -
How can we delete value fields from the Table T237A?
Dear All,
We need to delete some value fields in CO-PA. We got a message that these value fileds are being used in the Table T237A.
This table is related to key figure scheme.
We have deleted in t.c. sm31 in the table/view V_RS_T237A elements which were assigned to value fields to be deleted.
But we still have a message value fields are being used. And after some searches we found out they are still being used in the table T237A.
COuld you please, help us?
Thank you in advance!
Best regards,
Kamila.Change the Table Control attributes such that user can only select a single record(row).
<u>Tip to delete a selected record</u>
1) write a module 'Mark' in the PAI as below
PROCESS AFTER INPUT.
MODULE cancel AT EXIT-COMMAND.
LOOP WITH CONTROL table_view.
MODULE read_table_control.
FIELD flag MODULE mark ON INPUT.
ENDLOOP.
MODULE user_command_0100.
2) Module Mark is below.
MODULE mark INPUT.
CHECK flag = 'X'.
x = table_view-top_line + sy-stepl - 1.
Delete itab INDEX x.
ENDMODULE. " mark INPUT
Table_view is the TableControl Name.
'flag' is of type char(1) available in the Internal table which was assigned to the select option in the table control.
<u>award if uesful</u>
Regards,
Sudheer -
Make my header columns tall and narrow and place the text sideways
I'd like the header columns to be very narrow and tall and the text to be sideways. I can't figure out how to make it work. My temporary fix is to place textboxes over the columns, but they don't "belong" to the column and don't move with the table. It also can't be share in this format. I'd like it to look like a grade book. please help!! I'm stymied!
You can add a graphic to the cell's background, and that graphic can be a PDF version of the rotated text box. Here's the routine:
Copy Text Box
Switch to Preview.app
Command-N
Command-C
Switch to Numbers
Select Header Cell
Command-V
Doing it this way the graphic will not only stay with the cell, it will scale if you change the size of the cell.
Jerry -
How do i make letter heads on all pages
How do I make letter heads on all pages in pages?
In the inspector, click the first icon, "Document.'
In that window, check 'Headers' and or 'Footers.'
Clicking in the area near the top (or bottom) will put the cursor in a box where you can create the page headers or footers.
Headers and Footers can appear:
On all pages,
All except the first page, and
Differently on right and left pages.
You can insert text boxes into the header and footer fields as well, and arrange fonts and alignments for each text box separately.
You can past images into the headers and footers. Drag the image into the page. Cut it. Click the header or footer box. Paste it. Resize it.
Good luck, and have fun! -
How do I make it so iWork docs don't have to reformat from Mac to iOS
How do I make it so iWork docs don't have to reformat from Mac to iOS?
When I edit docs and spreadsheets on my Mac with OSX Mountain Lion with documents in iCloud, they have to be reformatted when I go to open them on my iPad or iPhone. This is minor annoyance but an annoyance nonetheless. Is there a way to format docs on the Mac so this does not take place?Hello KatTreeRain,
And welcome to Apple Discussions!
Change the music video's *Media Type* to Video. To do this, right->click on the music video and choose *Get Info* and then head over to the Options tab. There you will see the *Media Type* option with a drop down list. This will move the music video to your Videos/Movies.
B-rock -
Reg:How to delete the column in table control also from database table.
Hi Experts,
Once again thank u all for giving the responses.
one more doubt is how to delete the columns of table control and also the record shold delete from ztable.
With Regards,
Saroja.P.Hi,
If you want to delete the rows in the table control and simultaneously delete it from the database table, then you can implement a 'DELETE' functionality specific to your table control. Have a MARK field (you will find that in the screen attributes of the table control -> give a name for the MARK field, you will find an additional MARK column at the beginning of your table control). You can check whatever rows you want to delete from the table control, call the delete module.
"This portion of code inside the LOOP...ENDLOOP.
IF sy-ucomm eq 'F_DELETE'.
gt_itab2-check = mark. " Store the MARK field status into your internal table's correspoding field 'check'
MODIFY gt_itab INDEX tabcontrol-current_line.
ENDIF.
iF sy-ucomm eq 'DELETE1'.
DELETE gt_itab WHERE check eq 'X'. "Your internal table does not have rows that you want to delete
ENDIF.
Now you can modify your database table using the MODIFY statement.
MODIFY ZDB FROM TABLE gt_itab. -
How to get additional field from the second list base on lookup information column ?
Hi everyone,
Currently I created a SharePoint hosted Apps project and I need to know how can I get additional field from the second list base on lookup information column. example List1 Have 2 columns column1 and column2(Lookup Information from list2 (category)),
List2 have 3 columns title, and category, and color. so how can get the title and color from list2 base on this lookup information column (SharePoint Hosted apps and Javascript code)? that is possible?
Best regards,
------------------------------------------------------------ ---Tola---You can build one custom lookup control. Refer to the following post
http://www.stuartroberts.net/index.php/2012/10/03/enhanced-lookup-field-part-1/
Alternatively, try the following solution from codeplex
http://sp2010filteredlookup.codeplex.com/
http://filteredlookup.codeplex.com/
--Cheers -
How to delete a column from the table control in module pool?
Hi,
can any one please tell How to delete a column from the table control in module pool?
thanks in advance
warm regards
HareeshKumar Nhi hareesh,
I think it is better to hide it.
How to hide: You can check this link
Dynamic Hide column in table control -
How can I make a global change so all controls and indicators labels on the front panel change to another colour?
I need to change the front panel so that it can be used in a dark environment.Hi
The only way I see, is to use the "Controls[]" property and iterate through all of them. But don't forget about nested elements (i.e. clusters, tab-controls, ...).
Thomas
Using LV8.0
Don't be afraid to rate a good answer... -
Hi! I just bought a new iPhone and I was wondering how i can make sure all my pictures and music will be transfered from my old iPhone to my new one?
Pictures are held in the iPhone backup. If you backup the old device just prior to the activation of the new one, then restore from that backup, the photos will be there. Music is in iTunes on the computer and when you do the restore, it will download the music from iTunes to the device during the restore. Make sure any music purchased on the iPhone that has not been transfered to iTunes on the computer is done before beginning the restore.
You can also view information in this support document http://support.apple.com/kb/HT2109 -
How to select the data efficiently from the table
hi every one,
i need some help in selecting data from FAGLFLEXA table.i have to select many amounts from different group of G/L accounts
(groups are predefined here which contains a set of g/L account no.).
if i select every time for each group then it will be a performance issue, in order to avoid it what should i do, can any one suggest me a method or a smaple query so that i can perform the task efficiently.Hi ,
1.select and keep the data in internal table
2.avoid select inside loop ..endloop.
3.try to use for all entries
check the below details
Hi Praveen,
Performance Notes
1.Keep the Result Set Small
You should aim to keep the result set small. This reduces both the amount of memory used in the database system and the network load when transferring data to the application server. To reduce the size of your result sets, use the WHERE and HAVING clauses.
Using the WHERE Clause
Whenever you access a database table, you should use a WHERE clause in the corresponding Open SQL statement. Even if a program containing a SELECT statement with no WHERE clause performs well in tests, it may slow down rapidly in your production system, where the data volume increases daily. You should only dispense with the WHERE clause in exceptional cases where you really need the entire contents of the database table every time the statement is executed.
When you use the WHERE clause, the database system optimizes the access and only transfers the required data. You should never transfer unwanted data to the application server and then filter it using ABAP statements.
Using the HAVING Clause
After selecting the required lines in the WHERE clause, the system then processes the GROUP BY clause, if one exists, and summarizes the database lines selected. The HAVING clause allows you to restrict the grouped lines, and in particular, the aggregate expressions, by applying further conditions.
Effect
If you use the WHERE and HAVING clauses correctly:
There are no more physical I/Os in the database than necessary
No unwanted data is stored in the database cache (it could otherwise displace data that is actually required)
The CPU usage of the database host is minimize
The network load is reduced, since only the data that is required by the application is transferred to the application server.
Minimize the Amount of Data Transferred
Data is transferred between the database system and the application server in blocks. Each block is up to 32 KB in size (the precise size depends on your network communication hardware). Administration information is transported in the blocks as well as the data.
To minimize the network load, you should transfer as few blocks as possible. Open SQL allows you to do this as follows:
Restrict the Number of Lines
If you only want to read a certain number of lines in a SELECT statement, use the UP TO <n> ROWS addition in the FROM clause. This tells the database system only to transfer <n> lines back to the application server. This is more efficient than transferring more lines than necessary back to the application server and then discarding them in your ABAP program.
If you expect your WHERE clause to return a large number of duplicate entries, you can use the DISTINCT addition in the SELECT clause.
Restrict the Number of Columns
You should only read the columns from a database table that you actually need in the program. To do this, list the columns in the SELECT clause. Note here that the INTO CORRESPONDING FIELDS addition in the INTO clause is only efficient with large volumes of data, otherwise the runtime required to compare the names is too great. For small amounts of data, use a list of variables in the INTO clause.
Do not use * to select all columns unless you really need them. However, if you list individual columns, you may have to adjust the program if the structure of the database table is changed in the ABAP Dictionary. If you specify the database table dynamically, you must always read all of its columns.
Use Aggregate Functions
If you only want to use data for calculations, it is often more efficient to use the aggregate functions of the SELECT clause than to read the individual entries from the database and perform the calculations in the ABAP program.
Aggregate functions allow you to find out the number of values and find the sum, average, minimum, and maximum values.
Following an aggregate expression, only its result is transferred from the database.
Data Transfer when Changing Table Lines
When you use the UPDATE statement to change lines in the table, you should use the WHERE clause to specify the relevant lines, and then SET statements to change only the required columns.
When you use a work area to overwrite table lines, too much data is often transferred. Furthermore, this method requires an extra SELECT statement to fill the work area. Minimize the Number of Data Transfers
In every Open SQL statement, data is transferred between the application server and the database system. Furthermore, the database system has to construct or reopen the appropriate administration data for each database access. You can therefore minimize the load on the network and the database system by minimizing the number of times you access the database.
Multiple Operations Instead of Single Operations
When you change data using INSERT, UPDATE, and DELETE, use internal tables instead of single entries. If you read data using SELECT, it is worth using multiple operations if you want to process the data more than once, other wise, a simple select loop is more efficient.
Avoid Repeated Access
As a rule you should read a given set of data once only in your program, and using a single access. Avoid accessing the same data more than once (for example, SELECT before an UPDATE).
Avoid Nested SELECT Loops
A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. You should therefore only use nested SELECT loops if the selection in the outer loop contains very few lines.
However, using combinations of data from different database tables is more the rule than the exception in the relational data model. You can use the following techniques to avoid nested SELECT statements:
ABAP Dictionary Views
You can define joins between database tables statically and systemwide as views in the ABAP Dictionary. ABAP Dictionary views can be used by all ABAP programs. One of their advantages is that fields that are common to both tables (join fields) are only transferred once from the database to the application server.
Views in the ABAP Dictionary are implemented as inner joins. If the inner table contains no lines that correspond to lines in the outer table, no data is transferred. This is not always the desired result. For example, when you read data from a text table, you want to include lines in the selection even if the corresponding text does not exist in the required language. If you want to include all of the data from the outer table, you can program a left outer join in ABAP.
The links between the tables in the view are created and optimized by the database system. Like database tables, you can buffer views on the application server. The same buffering rules apply to views as to tables. In other words, it is most appropriate for views that you use mostly to read data. This reduces the network load and the amount of physical I/O in the database.
Joins in the FROM Clause
You can read data from more than one database table in a single SELECT statement by using inner or left outer joins in the FROM clause.
The disadvantage of using joins is that redundant data is read from the hierarchically-superior table if there is a 1:N relationship between the outer and inner tables. This can considerably increase the amount of data transferred from the database to the application server. Therefore, when you program a join, you should ensure that the SELECT clause contains a list of only the columns that you really need. Furthermore, joins bypass the table buffer and read directly from the database. For this reason, you should use an ABAP Dictionary view instead of a join if you only want to read the data.
The runtime of a join statement is heavily dependent on the database optimizer, especially when it contains more than two database tables. However, joins are nearly always quicker than using nested SELECT statements.
Subqueries in the WHERE and HAVING Clauses
Another way of accessing more than one database table in the same Open SQL statement is to use subqueries in the WHERE or HAVING clause. The data from a subquery is not transferred to the application server. Instead, it is used to evaluate conditions in the database system. This is a simple and effective way of programming complex database operations.
Using Internal Tables
It is also possible to avoid nested SELECT loops by placing the selection from the outer loop in an internal table and then running the inner selection once only using the FOR ALL ENTRIES addition. This technique stems from the time before joins were allowed in the FROM clause. On the other hand, it does prevent redundant data from being transferred from the database.
Using a Cursor to Read Data
A further method is to decouple the INTO clause from the SELECT statement by opening a cursor using OPEN CURSOR and reading data line by line using FETCH NEXT CURSOR. You must open a new cursor for each nested loop. In this case, you must ensure yourself that the correct lines are read from the database tables in the correct order. This usually requires a foreign key relationship between the database tables, and that they are sorted by the foreign key. Minimize the Search Overhead
You minimize the size of the result set by using the WHERE and HAVING clauses. To increase the efficiency of these clauses, you should formulate them to fit with the database table indexes.
Database Indexes
Indexes speed up data selection from the database. They consist of selected fields of a table, of which a copy is then made in sorted order. If you specify the index fields correctly in a condition in the WHERE or HAVING clause, the system only searches part of the index (index range scan).
The primary index is always created automatically in the R/3 System. It consists of the primary key fields of the database table. This means that for each combination of fields in the index, there is a maximum of one line in the table. This kind of index is also known as UNIQUE.
If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVING clause, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
You specify the fields of secondary indexes using the ABAP Dictionary. You can also determine whether the index is unique or not. However, you should not create secondary indexes to cover all possible combinations of fields.
Only create one if you select data by fields that are not contained in another index, and the performance is very poor. Furthermore, you should only create secondary indexes for database tables from which you mainly read, since indexes have to be updated each time the database table is changed. As a rule, secondary indexes should not contain more than four fields, and you should not have more than five indexes for a single database table.
If a table has more than five indexes, you run the risk of the optimizer choosing the wrong one for a particular operation. For this reason, you should avoid indexes with overlapping contents.
Secondary indexes should contain columns that you use frequently in a selection, and that are as highly selective as possible. The fewer table entries that can be selected by a certain column, the higher that columns selectivity. Place the most selective fields at the beginning of the index. Your secondary index should be so selective that each index entry corresponds to at most five percent of the table entries. If this is not the case, it is not worth creating the index. You should also avoid creating indexes for fields that are not always filled, where their value is initial for most entries in the table.
If all of the columns in the SELECT clause are contained in the index, the system does not have to search the actual table data after reading from the index. If you have a SELECT clause with very few columns, you can improve performance dramatically by including these columns in a secondary index.
Formulating Conditions for Indexes
You should bear in mind the following when formulating conditions for the WHERE and HAVING clauses so that the system can use a database index and does not have to use a full table scan.
Check for Equality and Link Using AND
The database index search is particularly efficient if you check all index fields for equality (= or EQ) and link the expressions using AND.
Use Positive Conditions
The database system only supports queries that describe the result in positive terms, for example, EQ or LIKE. It does not support negative expressions like NE or NOT LIKE.
If possible, avoid using the NOT operator in the WHERE clause, because it is not supported by database indexes; invert the logical expression instead.
Using OR
The optimizer usually stops working when an OR expression occurs in the condition. This means that the columns checked using OR are not included in the index search. An exception to this are OR expressions at the outside of conditions. You should try to reformulate conditions that apply OR expressions to columns relevant to the index, for example, into an IN condition.
Using Part of the Index
If you construct an index from several columns, the system can still use it even if you only specify a few of the columns in a condition. However, in this case, the sequence of the columns in the index is important. A column can only be used in the index search if all of the columns before it in the index definition have also been specified in the condition.
Checking for Null Values
The IS NULL condition can cause problems with indexes. Some database systems do not store null values in the index structure. Consequently, this field cannot be used in the index.
Avoid Complex Conditions
Avoid complex conditions, since the statements have to be broken down into their individual components by the database system.
Reduce the Database Load
Unlike application servers and presentation servers, there is only one database server in your system. You should therefore aim to reduce the database load as much as possible. You can use the following methods:
Buffer Tables on the Application Server
You can considerably reduce the time required to access data by buffering it in the application server table buffer. Reading a single entry from table T001 can take between 8 and 600 milliseconds, while reading it from the table buffer takes 0.2 - 1 milliseconds.
Whether a table can be buffered or not depends its technical attributes in the ABAP Dictionary. There are three buffering types:
Resident buffering (100%) The first time the table is accessed, its entire contents are loaded in the table buffer.
Generic buffering In this case, you need to specify a generic key (some of the key fields) in the technical settings of the table in the ABAP Dictionary. The table contents are then divided into generic areas. When you access data with one of the generic keys, the whole generic area is loaded into the table buffer. Client-specific tables are often buffered generically by client.
Partial buffering (single entry) Only single entries are read from the database and stored in the table buffer.
When you read from buffered tables, the following happens:
1. An ABAP program requests data from a buffered table.
2. The ABAP processor interprets the Open SQL statement. If the table is defined as a buffered table in the ABAP Dictionary, the ABAP processor checks in the local buffer on the application server to see if the table (or part of it) has already been buffered.
3. If the table has not yet been buffered, the request is passed on to the database. If the data exists in the buffer, it is sent to the program.
4. The database server passes the data to the application server, which places it in the table buffer.
5. The data is passed to the program.
When you change a buffered table, the following happens:
1. The database table is changed and the buffer on the application server is updated. The database interface logs the update statement in the table DDLOG. If the system has more than one application server, the buffer on the other servers is not updated at once.
2. All application servers periodically read the contents of table DDLOG, and delete the corresponding contents from their buffers where necessary. The granularity depends on the buffering type. The table buffers in a distributed system are generally synchronized every 60 seconds (parameter: rsdisp/bufreftime).
3. Within this period, users on non-synchronized application servers will read old data. The data is not recognized as obsolete until the next buffer synchronization. The next time it is accessed, it is re-read from the database.
You should buffer the following types of tables:
Tables that are read very frequently
Tables that are changed very infrequently
Relatively small tables (few lines, few columns, or short columns)
Tables where delayed update is acceptable.
Once you have buffered a table, take care not to use any Open SQL statements that bypass the buffer.
The SELECT statement bypasses the buffer when you use any of the following:
The BYPASSING BUFFER addition in the FROM clause
The DISTINCT addition in the SELECT clause
Aggregate expressions in the SELECT clause
Joins in the FROM clause
The IS NULL condition in the WHERE clause
Subqueries in the WHERE clause
The ORDER BY clause
The GROUP BY clause
The FOR UPDATE addition
Furthermore, all Native SQL statements bypass the buffer.
Avoid Reading Data Repeatedly
If you avoid reading the same data repeatedly, you both reduce the number of database accesses and reduce the load on the database. Furthermore, a "dirty read" may occur with database tables other than Oracle. This means that the second time you read data from a database table, it may be different from the data read the first time. To ensure that the data in your program is consistent, you should read it once only and then store it in an internal table.
Sort Data in Your ABAP Programs
The ORDER BY clause in the SELECT statement is not necessarily optimized by the database system or executed with the correct index. This can result in increased runtime costs. You should only use ORDER BY if the database sort uses the same index with which the table is read. To find out which index the system uses, use SQL Trace in the ABAP Workbench Performance Trace. If the indexes are not the same, it is more efficient to read the data into an internal table or extract and sort it in the ABAP program using the SORT statement.
Use Logical Databases
SAP supplies logical databases for all applications. A logical database is an ABAP program that decouples Open SQL statements from application programs. They are optimized for the best possible database performance. However, it is important that you use the right logical database. The hierarchy of the data you want to read must reflect the structure of the logical database, otherwise, they can have a negative effect on performance. For example, if you want to read data from a table right at the bottom of the hierarchy of the logical database, it has to read at least the key fields of all tables above it in the hierarchy. In this case, it is more efficient to use a SELECT statement.
Work Processes
Work processes execute the individual dialog steps in R/3 applications. The next two sections describe firstly the structure of a work process, and secondly the different types of work process in the R/3 System.
Structure of a Work Process
Work processes execute the dialog steps of application programs. They are components of an application server. The following diagram shows the components of a work process:
Each work process contains two software processors and a database interface.
Screen Processor
In R/3 application programming, there is a difference between user interaction and processing logic. From a programming point of view, user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic. The screen flow logic controls a large part of the user interaction. The R/3 Basis system contains a special language for programming screen flow logic. The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process and the SAPgui, calls modules in the flow logic, and ensures that the field contents are transferred from the screen to the flow logic.
ABAP Processor
The actual processing logic of an application program is written in ABAP - SAPs own programming language. The ABAP processor executes the processing logic of the application program, and communicates with the database interface. The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrates the interaction between the screen and the ABAP processors when an application program is running.
Database Interface
The database interface provides the following services:
Establishing and terminating connections between the work process and the database.
Access to database tables
Access to R/3 Repository objects (ABAP programs, screens and so on)
Access to catalog information (ABAP Dictionary)
Controlling transactions (commit and rollback handling)
Table buffer administration on the application server.
The following diagram shows the individual components of the database interface:
The diagram shows that there are two different ways of accessing databases: Open SQL and Native SQL.
Open SQL statements are a subset of Standard SQL that is fully integrated in ABAP. They allow you to access data irrespective of the database system that the R/3 installation is using. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data. The tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of Standard SQL are performed in the R/3 System by the ABAP Dictionary and the authorization system. These provide a unified range of functions, irrespective of database, and also contain functions beyond those offered by the various database systems.
Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an application server. Where an R/3 System is distributed across more than one application server, the data in the various buffers is synchronized at set intervals by the buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change.
Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. Programs that use Native SQL are specific to the database system for which they were written. R/3 applications contain as little Native SQL as possible. In fact, it is only used in a few Basis components (for example, to create or change table definitions in the ABAP Dictionary).
The database-dependent layer in the diagram serves to hide the differences between database systems from the rest of the database interface. You choose the appropriate layer when you install the Basis system. Thanks to the standardization of SQL, the differences in the syntax of statements are very slight. However, the semantics and behavior of the statements have not been fully standardized, and the differences in these areas can be greater. When you use Native SQL, the function of the database-dependent layer is minimal.
Types of Work Process
Although all work processes contain the components described above, they can still be divided into different types. The type of a work process determines the kind of task for which it is responsible in the application server. It does not specify a particular set of technical attributes. The individual tasks are distributed to the work processes by the dispatcher.
Before you start your R/3 System, you determine how many work processes it will have, and what their types will be. The dispatcher starts the work processes and only assigns them tasks that correspond to their type. This means that you can distribute work process types to optimize the use of the resources on your application servers.
The following diagram shows again the structure of an application server, but this time, includes the various possible work process types:
The various work processes are described briefly below. Other parts of this documentation describe the individual components of the application server and the R/3 System in more detail.
Dialog Work Process
Dialog work processes deal with requests from an active user to execute dialog steps.
Update Work Process
Update work processes execute database update requests. Update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
Background Work Process
Background work processes process programs that can be executed without user interaction (background jobs).
Enqueue Work Process
The enqueue work process administers a lock table in the shared memory area. The lock table contains the logical database locks for the R/3 System and is an important part of the SAP LUW concept. In an R/3 System, you may only have one lock table. You may therefore also only have one application server with enqueue work processes.
Spool Work Process
The spool work process passes sequential datasets to a printer or to optical archiving. Each application server may contain several spool work process.
The services offered by an application server are determined by the types of its work processes. One application server may, of course, have more than one function. For example, it may be both a dialog server and the enqueue server, if it has several dialog work processes and an enqueue work process.
You can use the system administration functions to switch a work process between dialog and background modes while the system is still running. This allows you, for example, to switch an R/3 System between day and night operation, where you have more dialog than background work processes during the day, and the other way around during the night.
ABAP Application Server
R/3 programs run on application servers. They are an important component of the R/3 System. The following sections describe application servers in more detail.
Structure of an ABAP Application Server
The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server.
The following diagram shows the structure of an application server:
The individual components are:
Work Processes
An application server contains work processes, which are components that can run an application. Work processes are components that are able to execute an application (that is, one dialog step each). Each work process is linked to a memory area containing the context of the application being run. The context contains the current data for the application program. This needs to be available in each dialog step. Further information about the different types of work process is contained later on in this documentation.
Dispatcher
Each application server contains a dispatcher. The dispatcher is the link between the work processes and the users logged onto the application server. Its task is to receive requests for dialog steps from the SAP GUI and direct them to a free work process. In the same way, it directs screen output resulting from the dialog step back to the appropriate user.
Gateway
Each application server contains a gateway. This is the interface for the R/3 communication protocols (RFC, CPI/C). It can communicate with other application servers in the same R/3 System, with other R/3 Systems, with R/2 Systems, or with non-SAP systems.
The application server structure as described here aids the performance and scalability of the entire R/3 System. The fixed number of work processes and dispatching of dialog steps leads to optimal memory use, since it means that certain components and the memory areas of a work process are application-independent and reusable. The fact that the individual work processes work independently makes them suitable for a multi-processor architecture. The methods used in the dispatcher to distribute tasks to work processes are discussed more closely in the section Dispatching Dialog Steps.
Shared Memory
All of the work processes on an application server use a common main memory area called shared memory to save contexts or to buffer constant data locally.
The resources that all work processes use (such as programs and table contents) are contained in shared memory. Memory management in the R/3 System ensures that the work processes always address the correct context, that is the data relevant to the current state of the program that is running. A mapping process projects the required context for a dialog step from shared memory into the address of the relevant work process. This reduces the actual copying to a minimum.
Local buffering of data in the shared memory of the application server reduces the number of database reads required. This reduces access times for application programs considerably. For optimal use of the buffer, you can concentrate individual applications (financial accounting, logistics, human resources) into separate application server groups.
Database Connection
When you start up an R/3 System, each application server registers its work processes with the database layer, and receives a single dedicated channel for each. While the system is running, each work process is a user (client) of the database system (server). You cannot change the work process registration while the system is running. Neither can you reassign a database channel from one work process to another. For this reason, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. This has important consequences for the programming model explained below.
Dispatching Dialog Steps
The number of users logged onto an application server is often many times greater than the number of available work processes. Furthermore, it is not restricted by the R/3 system architecture. Furthermore, each user can run several applications at once. The dispatcher has the important task of distributing all dialog steps among the work processes on the application server.
The following diagram is an example of how this might happen:
1. The dispatcher receives the request to execute a dialog step from user 1 and directs it to work process 1, which happens to be free. The work process addresses the context of the application program (in shared memory) and executes the dialog step. It then becomes free again.
2. The dispatcher receives the request to execute a dialog step from user 2 and directs it to work process 1, which is now free again. The work process executes the dialog step as in step 1.
3. While work process 1 is still working, the dispatcher receives a further request from user 1 and directs it to work process 2, which is free.
4. After work processes 1 and 2 have finished processing their dialog steps, the dispatcher receives another request from user 1 and directs it to work process 1, which is free again.
5. While work process 1 is still working, the dispatcher receives a further request from user 2 and directs it to work process 2, which is free.
From this example, we can see that:
A dialog step from a program is assigned to a single work process for execution.
The individual dialog steps of a program can be executed on different work processes, and the program context must be addressed for each new work process.
A work process can execute dialog steps of different programs from different users.
The example does not show that the dispatcher tries to distribute the requests to the work processes such that the same work process is used as often as possible for the successive dialog steps in an application. This is useful, since it saves the program context having to be addressed each time a dialog step is executed.
Dispatching and the Programming Model
The separation of application and presentation layer made it necessary to split up application programs into dialog steps. This, and the fact that dialog steps are dispatched to individual work processes, has had important consequences for the programming model.
As mentioned above, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. The contents of the database must be consistent at its beginning and end. The beginning and end of a database LUW are defined by a commit command to the database system (database commit). During a database LUW, that is, between two database commits, the database system itself ensures consistency within the database. In other words, it takes over tasks such as locking database entries while they are being edited, or restoring the old data (rollback) if a step terminates in an error.
A typical SAP application program extends over several screens and the corresponding dialog steps. The user requests database changes on the individual screens that should lead to the database being consistent once the screens have all been processed. However, the individual dialog steps run on different work processes, and a single work process can process dialog steps from other applications. It is clear that two or more independent applications whose dialog steps happen to be processed on the same work process cannot be allowed to work with the same database LUW.
Consequently, a work process must open a separate database LUW for each dialog step. The work process sends a commit command (database commit) to the database at the end of each dialog step in which it makes database changes. These commit commands are called implicit database commits, since they are not explicitly written into the application program.
These implicit database commits mean that a database LUW can be kept open for a maximum of one dialog step. This leads to a considerable reduction in database load, serialization, and deadlocks, and enables a large number of users to use the same system.
However, the question now arises of how this method (1 dialog step = 1 database LUW) can be reconciled with the demand to make commits and rollbacks dependent on the logical flow of the application program instead of the technical distribution of dialog steps. Database update requests that depend on one another form logical units in the program that extend over more than one dialog step. The database changes associated with these logical units must be executed together and must also be able to be undone together.
The SAP programming model contains a series of bundling techniques that allow you to group database updates together in logical units. The section of an R/3 application program that bundles a set of logically-associated database operations is called an SAP LUW. Unlike a database LUW, a SAP LUW includes all of the dialog steps in a logical unit, including the database update.
Happy Reading...
shibu -
How to export some data from the tables of an owner with integrity?
Hi to all,
How to export some data from the tables of an owner with integrity?
I want to bring some data from all tables in a single owner of the production database for development environment.
My initial requirements are: seeking information on company code (emp), contract status (status) and / or effective date of contract settlement (dt_liq_efetiva) - a small amount of data to developers.
These three fields are present in the main system table (the table of contracts). Then I thought about ...
- create a temporary table from the query results table to contract;
- and then use this temporary table as a reference to fetch the data in other tables of the owner while maintaining integrity. But how? I have not found the answer, because: what to do when not there is the possibility of a join between the contract and any other table?
I am considering the possibility of consulting the names of tables, foreign keys and columns above, and create dynamic SQL. Conceptually, something like:
select r.constraint_name "FK name",
r.table_name "FK table",
r.column_name "FK column",
up.constraint_name "Referencing name",
up.table_name "Referencing table",
up.column_name "Referencing column"
from all_cons_columns up
join all_cons_columns r
using (owner, position), (select r.owner,
r.constraint_name fk,
r.table_name table_fk,
r.r_constraint_name r,
up.table_name table_r
from all_constraints up, all_constraints r
where r.r_owner = up.owner
and r.r_constraint_name = up.constraint_name
and up.constraint_type in ('P', 'U')
and r.constraint_type = 'R'
and r.owner = 'OWNERNAME') aux
where r.constraint_name = aux.fk
and r.table_name = aux.table_fk
and up.constraint_name = aux.r
and up.table_name = aux.table_r;
-- + Dynamic SQL
If anyone has any suggestions and / or reuse code to me thank you very much!
After resolving this standoff intend to mount the inserts in utl_file by a table and create another program to read and play in the development environment.
Thinking...
Let's Share!
My thanks in advance,
PhilipsThanks, Peter.
Well, I am working with release 9.2.0.8.0. But the planning is migrate to 10g this year. So my questions are:
With Data Pump can export data just from tables owned for me (SCHEMAS = MYOWNER) parameterizing the volume of data (SAMPLE) and filters to table (QUERY), right? But parameterizing a contract table QUERY = "WHERE status NOT IN (2,6) ORDER BY contract ":
1º- the Data Pump automatically searches for related data in other tables in the owner? ex. parcel table has X records related (fk) with Y contracts not in (2,6): X * SAMPLE records will be randomly exported?
2º- for the tables without relation (fk) and which are within the owner (MYOWNER) the data is exported only based on the parameter SAMPLE?
Once again, thank you,
Philips
Reading Oracle Docs... -
How to compare two fields from the same table in the select statement
Hi, friends
I try to compare tow fields from the same table, but no result,
For example, this
data: cptotchek tyep i.
select count(*) into cptotchek
from aufk where erdat = aufk-idat2 .
The result is cptotchek = 0, but there are the records in aufk , where, aufk-erdat = aufk-idat2.
Please, help me, i don't use the loop statement for optimize my program.
RegardsHi ,
it will not return any value when you are using column of same table
such as Date Field , Because while Using Aggregate Function it will not check with self column
. For that you have to take data in one internal table and then you can work on it .
And if you are worried about Performance it will not affect , untill you are selecting only required data .
you can try this way .
data: cptotchek type i.
types : begin of w_aufk.
include structure aufk .
types : end of w_aufk .
data : it_aufk type standard table of w_aufk with header line .
select * into corresponding fields of table it_aufk
from aufk .
loop at it_aufk .
if it_aufk-erdat = it_aufk-idat2 .
write : / it_aufk-erdat , it_aufk-idat2 .
else .
delete it_aufk .
endif .
endloop.
Regards
Deepak.
Maybe you are looking for
-
Performance issue with a particular query
Hi Experts, OS version : Sun solaris 5.10 DB version : 10.1.0.4 We have a report designed in SAP BO and for which we have below SQL query written SELECT SNOW_DIM.SERV_REP_INCIDENT.INCIDENT_NUMBER, ISAC_GL_APPL_HIERARCHY_SERVIMP.SOL_NAME ISAC_GL_APPL_
-
HP Pavilion dv6-7010us Entertainment Notebook PC
My motheroarbd went out on my DV6 7010. I had to wait awhile before I could get another MB so used the HD from it for another computer (HPG-60) Now I am putting it back in my DV6 7010US. The problem is it seems that the windows from my other computer
-
Displaying OAF Based Workflow notification outside E-Business suite
Hi All, We have a requirement of displaying a Workflow notification (OA based) on a portal without login into Oracle Applications. I am wondering if this is possible. The Oracle shipped Workflow notification Page is a Self-Secured page and I tried ac
-
Service entry sheet Release strategy Error
Hi Guys I have one scenario where Iam not able to post Service enrty sheet We have release strategies A1,A2,A3,A4,A5 Some service entry sheets are there in the system with each release strategy We have deleted A2,A3,A4,A5 and A1 remains there While r
-
Business rules storage location / directory ? Essbase server?
Do you know where the Business Rules in EAS are stored ? in what format?