ABAP_to_the_Future

Recommendations

Info

8Business Object Processing Framework (BOPF)Recommended Reading왘 Design Patterns: Elements of Resuable Object-Oriented Software (Gamma et al., Addison-Wesley,1994)왘 Navigating the BOPF: Part 1—Getting Started: http://scn.sap.com/community/abap/blog/2013/01/04/navigating-the-bopf-part-1--getting-started (James Wood)왘 Project Objectify—Continued: http://scn.sap.com/community/abap/blog/2014/03/22/project-objectify--continued (Bruno Esperenca)356
Any fool can make a ruleAnd any fool will mind it.—Henry David Thoreau, Journal #149 BRFplusIt is one of the great truths in life that rules are with us always—just like deathand taxes—and the same is true in SAP. A business rule defines what outcomesshould occur based upon the values of one or more input criteria. An example isas follows: “Australians wh o do not have private health care have to pay 2.5%extra income tax.” In this case, the input criterion is whether any given individualhas such insurance; the outcome is whether or not that individual has to pay moretax.A business rules framework (BRF), also known as a business rule management system(BRMS), is a framework that enables you to express such rules within yourcomputer system. It consists of three components: a UI, a rules repository, and arules engine. An example of a business rules framework—and the subject of thischapter—is, of course, BRFplus.One of the purposes of a business rules framework is to isolate a process from thedecision logic that is a part of that process. A process is the high-level end goalachieved by a set of decisions—for example, the process of making monsters. Processestend to be the same for all companies and very rarely change; in OO programmingterms, the process is the abstraction, which cares not about the details.The decision logic, on the other hand, is the indivi dual decisions that go into thebigger process. This can be very di fferent between companies and can alsochange all the time. No two mad scientists can agree on what the best recipe is formaking a monster or which is the best so rt of hunchback to assist them. In OOprogramming terms, these are the details, which depend upon the abstraction.In Figure 9.1, you can see the differen ce between a process and the decisions inthat process.357
Page 1 and 2:
www.allitebooks.com
Page 3 and 4:
Paul HardyABAP ®to the Futurewww.a
Page 5 and 6:
To my mother, Mary, who would have
Page 7 and 8:
Notes on UsageThis e-book is protec
Page 9 and 10:
ContentsForeword ..................
Page 11 and 12:
Contents2.9 Unit Testing ..........
Page 13 and 14:
Contents7.3.2 Class Invariants ....
Page 15 and 16:
Contents11.1.2 Downloading ABAP2XLS
Page 17:
Contents15.3 Bottom-Up Development
Page 20 and 21:
Forewordtoolsets your company shoul
Page 23 and 24:
1It may be hard for an egg to turn
Page 25 and 26:
IntroductionSAP introduced ABAP Obj
Page 27 and 28:
Structure of the Booktechnologies d
Page 29 and 30:
Structure of the Book(BOPF), which
Page 31:
The Example ApplicationBaron Franke
Page 35 and 36:
It’s best not to stare at the sun
Page 37 and 38:
Installation 1.1very basics of how
Page 39 and 40:
Installation 1.1Figure 1.2 Installi
Page 41 and 42:
Installation 1.1Figure 1.4 Eclipse
Page 43 and 44:
Features 1.2Figure 1.6 ABAP in Ecli
Page 45 and 46:
Features 1.2Figure 1.8 Searching fo
Page 47 and 48:
Features 1.2oper to such an extent
Page 49 and 50:
Features 1.2to forget the exact nam
Page 51 and 52:
Features 1.2METHODS: main.ENDCLASS.
Page 53 and 54:
Features 1.2The definition and impl
Page 55 and 56:
Features 1.2ld_description1 = 'BONK
Page 57 and 58:
Features 1.2Figure 1.16 Extracting
Page 59 and 60:
Features 1.2ld_result = ld_use_this
Page 61 and 62:
Features 1.2Automatically creating
Page 63 and 64:
Testing and Troubleshooting 1.3Figu
Page 65 and 66:
Testing and Troubleshooting 1.3does
Page 67 and 68:
Testing and Troubleshooting 1.3by r
Page 69 and 70:
Testing and Troubleshooting 1.3Figu
Page 71 and 72:
Customization Options with User-Def
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Summary 1.5design UML diagrams insi
Page 81 and 82:
It's a beautiful thing, the Destruc
Page 83 and 84:
Database Access 2.1Figure 2.1 Micro
Page 85 and 86:
Database Access 2.1lower the sanity
Page 87 and 88:
Database Access 2.1account of secon
Page 89 and 90:
Database Access 2.1efficient way to
Page 91 and 92:
Declaring and Creating Variables 2.
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
String Processing 2.3LD_RESULT = |M
Page 99 and 100:
Calling Functions 2.4However, now y
Page 101 and 102:
Calling Functions 2.4sometimes the
Page 103 and 104:
Conditional Logic 2.52.5.1 Using Fu
Page 105 and 106:
Conditional Logic 2.5If the functio
Page 107 and 108:
Conditional Logic 2.5l_day = 'Tuesd
Page 109 and 110:
Internal Tables 2.6WHEN cs_monster_
Page 111 and 112:
Internal Tables 2.6unique hashed ke
Page 113 and 114:
Internal Tables 2.6In Section 2.2.2
Page 115 and 116:
Internal Tables 2.6a traditional RE
Page 117 and 118:
Internal Tables 2.6monster_name TYP
Page 119 and 120:
Internal Tables 2.6This saves you a
Page 121 and 122:
Internal Tables 2.6you want to modi
Page 123 and 124:
Internal Tables 2.6at a time; someh
Page 125 and 126:
Internal Tables 2.6DATA( lt_average
Page 127 and 128:
Object-Oriented Programming 2.7In 7
Page 129 and 130:
Search Helps 2.8to the end of the d
Page 131 and 132:
Unit Testing 2.9So, you can imagine
Page 133 and 134:
Unit Testing 2.9IF id_chemcial_type
Page 135 and 136:
Cross-Program Communication 2.10The
Page 137 and 138:
Code without tests is bad code. It
Page 139 and 140:
Eliminating Dependencies 3.13.1 Eli
Page 141 and 142:
Eliminating Dependencies 3.1WHEN 'N
Page 143 and 144:
Implementing Mock Objects 3.2mo_use
Page 145 and 146:
Implementing Mock Objects 3.2rd_ans
Page 147 and 148:
Writing and Implementing Unit Tests
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Automating the Test Process 3.4supp
Page 163 and 164:
Automating the Test Process 3.4whil
Page 165 and 166:
Automating the Test Process 3.4INSE
Page 167 and 168:
Automating the Test Process 3.4ld_c
Page 169 and 170:
Automating the Test Process 3.4cl_a
Page 171 and 172:
Behavior-Driven Development 3.5you
Page 173 and 174:
Summary 3.6Whatever you want to cal
Page 175 and 176:
If builders built buildings the way
Page 177 and 178:
Automatic Run of Unit Tests 4.14.1
Page 179 and 180:
Mass Checks 4.2program that was wri
Page 181 and 182:
Mass Checks 4.2Figure 4.5 ATC Confi
Page 183 and 184:
Mass Checks 4.2In the Description f
Page 185 and 186:
Mass Checks 4.2objects and set a va
Page 187 and 188:
Mass Checks 4.2Next, go into SE80 t
Page 189 and 190:
Mass Checks 4.2CASE statement, like
Page 191 and 192:
Mass Checks 4.2On the next screen (
Page 193 and 194:
Recent Code Inspector Enhancements
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Debugging is twice as hard as writi
Page 205 and 206:
Script Tab Overview 5.1Figure 5.1 D
Page 207 and 208:
Script Tab Overview 5.1rally, then
Page 209 and 210:
Coding the SCRIPT Method 5.25.2 Cod
Page 211 and 212:
Coding the SCRIPT Method 5.2For exa
Page 213 and 214:
Coding the SCRIPT Method 5.2call an
Page 215 and 216:
Coding the INIT and END Methods 5.3
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223:
Summary 5.4script, you can tell the
Page 226 and 227:
6The Enhancement Framework and New
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 255 and 256:
There is no exception to the rule t
Page 257 and 258:
Types of Exception Classes 7.1which
Page 259 and 260:
Types of Exception Classes 7.1dump
Page 261 and 262:
Types of Exception Classes 7.1decla
Page 263 and 264:
Designing Exception Classes 7.2mayb
Page 265 and 266:
Designing Exception Classes 7.2an e
Page 267 and 268:
Designing Exception Classes 7.2rela
Page 269 and 270:
Designing Exception Classes 7.2* Co
Page 271 and 272:
Designing Exception Classes 7.2Tech
Page 273 and 274:
Designing Exception Classes 7.2Mean
Page 275 and 276:
Design by Contract 7.3future. If I
Page 277 and 278:
Design by Contract 7.3To demonstrat
Page 279 and 280:
Design by Contract 7.3automatically
Page 281:
Summary 7.47.4 SummaryThis chapter
Page 284 and 285:
8Business Object Processing Framewo
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307: 8Business Object Processing Framewo
Page 358 and 359: 9BRFplusProcessResultsTake Orderfor
Page 360 and 361: 9BRFplus9.1 The Historic Location o
Page 362 and 363: 9BRFplusThe flowchart is shown to t
Page 364 and 365: 9BRFplus9.1.3 Rules in ABAPProgramm
Page 366 and 367: 9BRFplusFigure 9.6 Creating a BRFpl
Page 368 and 369: 9BRFplussort of object is what—fo
Page 370 and 371: 9BRFplusHere, there is only one res
Page 372 and 373: 9BRFplusIn the pop-up shown in Figu
Page 374 and 375: 9BRFplusdecision tree and a decisio
Page 376 and 377: 9BRFplusFigure 9.17 Adding a Decisi
Page 378 and 379: 9BRFplusis also a lot of text on ea
Page 380 and 381: 9BRFplusAt the bottom of the screen
Page 382 and 383: 9BRFplusanother explanation could b
Page 384 and 385: 9BRFplusFigure 9.26 Adding Formulas
Page 386 and 387: 9BRFplushave a Check button at the
Page 388 and 389: 9BRFplusIn case you don’t think y
Page 390 and 391: 9BRFplusTo find the appropriate per
Page 392 and 393: 9BRFplusues from the spreadsheet th
Page 394 and 395: 9BRFplusFigure 9.34 Overlap Check S
Page 396 and 397: 9BRFplusFigure 9.37 Simulation: 3 o
Page 398 and 399: 9BRFplustask that is about to be cr
Page 400 and 401: 9BRFplusFigure 9.42 Generated BRFpl
Page 402 and 403: 9BRFplus9.6.2 Application ExitsWhen
Page 404 and 405: 9BRFpluscase feature (which require
Page 407 and 408:
Computer science departments have a
Page 409 and 410:
Getting Started 10.12. Calling the
Page 411 and 412:
Getting Started 10.1The first probl
Page 413 and 414:
Getting Started 10.1FROM ztvc_monst
Page 415 and 416:
Designing a Report Interface 10.2Th
Page 417 and 418:
Designing a Report Interface 10.2Fi
Page 419 and 420:
Page 421 and 422:
Designing a Report Interface 10.2Se
Page 423 and 424:
Designing a Report Interface 10.2me
Page 425 and 426:
Designing a Report Interface 10.2if
Page 427 and 428:
Designing a Report Interface 10.2
Page 429 and 430:
Designing a Report Interface 10.2In
Page 431 and 432:
Designing a Report Interface 10.2ME
Page 433 and 434:
Designing a Report Interface 10.2IF
Page 435 and 436:
Page 437 and 438:
Designing a Report Interface 10.2Fi
Page 439 and 440:
Designing a Report Interface 10.2fo
Page 441 and 442:
Adding Custom Command Icons Program
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Editing Data 10.4id_title= 'Monster
Page 449 and 450:
Editing Data 10.4SAP class CL_SALV_
Page 451 and 452:
Editing Data 10.4it_user_commands =
Page 453 and 454:
Editing Data 10.4table containing t
Page 455 and 456:
Handling Large Internal Tables with
Page 457 and 458:
Q. How do you identify an extrovert
Page 459 and 460:
The Basics 11.1nity can benefit. Th
Page 461 and 462:
The Basics 11.1Figure 11.5 Workshee
Page 463 and 464:
The Basics 11.1Adding Desired Attri
Page 465 and 466:
The Basics 11.1ld_pathld_fullpathTY
Page 467 and 468:
Enhancing Custom Reports with ABAP2
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
Page 501 and 502:
Tips and Tricks 11.3"44300 is the s
Page 503 and 504:
Tips and Tricks 11.3However, it wor
Page 505:
Summary 11.4As an example, in Secti
Page 508 and 509:
12Web Dynpro ABAP and Floorplan Man
Page 510 and 511:
Page 512 and 513:
Page 514 and 515:
Page 516 and 517:
Page 518 and 519:
Page 520 and 521:
Page 522 and 523:
Page 524 and 525:
Page 526 and 527:
Page 528 and 529:
Page 530 and 531:
Page 532 and 533:
Page 534 and 535:
Page 536 and 537:
Page 538 and 539:
Page 540 and 541:
Page 542 and 543:
Page 544 and 545:
Page 546 and 547:
Page 548 and 549:
Page 550 and 551:
Page 552 and 553:
Page 554 and 555:
Page 556 and 557:
Page 558 and 559:
Page 561 and 562:
What if you could find brand new wo
Page 563 and 564:
Architecture 13.11. Use SAP Gateway
Page 565 and 566:
Prerequisites 13.2to SAP PI, direct
Page 567 and 568:
Backend Tasks: Creating the Model U
Page 569 and 570:
Page 571 and 572:
Page 573 and 574:
Page 575 and 576:
Page 577 and 578:
Page 579 and 580:
Page 581 and 582:
Page 583 and 584:
Page 585 and 586:
Page 587 and 588:
Page 589 and 590:
Page 591 and 592:
Page 593 and 594:
Frontend Tasks: Creating the View a
Page 595 and 596:
Page 597 and 598:
Page 599 and 600:
Page 601 and 602:
Page 603 and 604:
Page 605 and 606:
Page 607 and 608:
Page 609 and 610:
Page 611 and 612:
Page 613 and 614:
Page 615 and 616:
Adding Elements with OpenUI5 13.5Du
Page 617 and 618:
Adding Elements with OpenUI5 13.5Fi
Page 619 and 620:
Adding Elements with OpenUI5 13.5}"
Page 621 and 622:
Importing SAPUI5 Applications to SA
Page 623 and 624:
Page 625 and 626:
Page 627:
Summary 13.8Synactive must have bee
Page 631 and 632:
The worst part of holding the memor
Page 633 and 634:
The Promises of Shared Memory 14.11
Page 635 and 636:
Creating and Using Shared Memory Ob
Page 637 and 638:
Page 639 and 640:
Page 641 and 642:
Page 643 and 644:
Page 645 and 646:
Page 647 and 648:
Updating the Database and Shared Me
Page 649 and 650:
Troubleshooting 14.4send data from
Page 651 and 652:
Troubleshooting 14.4* updated, so w
Page 653 and 654:
Troubleshooting 14.4memory root obj
Page 655 and 656:
When you innovate, you’ve got to
Page 657 and 658:
Introduction to Code Pushdown 15.11
Page 659 and 660:
Top-Down Development 15.2CDS ViewAM
Page 661 and 662:
Top-Down Development 15.2Creating a
Page 663 and 664:
Top-Down Development 15.2You always
Page 665 and 666:
Top-Down Development 15.2To recap,
Page 667 and 668:
Top-Down Development 15.2SELECT *FR
Page 669 and 670:
Top-Down Development 15.2{ vbak.zz_
Page 671 and 672:
Top-Down Development 15.2SummaryIn
Page 673 and 674:
Top-Down Development 15.2USING zt_m
Page 675 and 676:
Top-Down Development 15.2-- declare
Page 677 and 678:
Bottom-Up Development 15.315.3 Bott
Page 679 and 680:
Bottom-Up Development 15.3Figure 15
Page 681 and 682:
Locating Code that Can Be Pushed Do
Page 683 and 684:
Page 685 and 686:
Page 687 and 688:
Page 689 and 690:
Page 691 and 692:
Other Modifications to ABAP for SAP
Page 693 and 694:
Page 695 and 696:
Page 697 and 698:
Page 699 and 700:
Page 701:
Summary 15.6SP 12. So SAP clearly h
Page 704 and 705:
16ConclusionThey want everything to
Page 707 and 708:
AImproving Code ReadabilityAs Rober
Page 709 and 710:
The What vs. the How A.2When it com
Page 711 and 712:
BMaking Programs FlexibleOne of the
Page 713 and 714:
Making Programs FlexibleBExampleThe
Page 715 and 716:
Making Programs FlexibleBThis appro
Page 717:
Making Programs FlexibleBBoth examp
Page 721 and 722:
IndexAABAP 7.02, 90, 96, 98, 103, 1
Page 723 and 724:
IndexEclipse (Cont.)connect to back
Page 725 and 726:
IndexSSALV, 408add custom icons, 44
Page 727 and 728:
IndexXXML, 460, 463XSDBOOL, 105ZZ c
Page 729 and 730:
About Us and Our ProgramThe website
Page 731:
TrademarksThe common names, trade n
show all

ABAP_to_the_Future

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?