|
.gif)
.gif)
.jpg)
Click here to download
the Fall/Winter 2009 catalog.
|
Architecting EDI with SAP IDocs
by Emmanuel Hadzipetros
|
.gif)
The pharmaceuticals industry does it, retail does it — even Hollywood does it: EDI using SAP. Written in an entertaining, narrative style, this book teaches developers and system architects everything needed to plan for, design, and — most importantly — implement a complex SAP-EDI scenario. Enter the glamorous world of Hollywood and see how they make their money through SAP-EDI architectures!
1 Designing the architecture
Follow the transition to the new world of EDI by analyzing processes and documenting the legacy systems. A detailed blueprint of the to-be architecture will prepare you for the project.
2 The technical standards
Learn everything about EDI data exchange, the SAP IDoc interface, and the tools for building custom IDocs and modifying the standard.
3 Building the SAP EDI system on IDocs
Watch the implementation step by step: You’ll benefit from functional and technical specifications for each interface used, mappings, custom development objects, and lots of code.
4 Preparing and ensuring production
Development is complete, now get ready for go-live: Chapters on testing, troubleshooting, and system recovery arm you for the intricacies of daily business.
5 The storyline: A real-world scenario
This book doesn’t just tell you what could be possible — it shows how you do it. Using a real-world order-to-cash scenario with three business partners that begins on the first page, you’ll follow the implementation phase by phase.
|
Highlights
- EDI and IDoc basics
- Architectural design
- Standards
- Adapters
- The IDoc interface
- IDoc tools
- Building Custom IDocs and IDoc Extensions
- Implementing order-to-cash
- Functional, technical, and mapping specifications for all interfaces
- EDI configuration in SAP
- Testing, troubleshooting, and recovery
- Test strategy
- Monitoring and recovery tools
- Identifying key points of failure
| $79.95 |
Product Code: H3003
Hardcover, 736 pages
ISBN 978-1-59229-227-1
|
|
About the Author(s)
Emmanuel Hadzipetros is an ABAP developer and IDoc and EDI specialist who has been fascinated with data flows and systems integration throughout his 15 years of SAP project experience.
»SAP and EDI together are the heart, bones, arteries, and brains of modern business organizations«
Table of Contents
... Prologue ... 19
1 ... Acme Pictures: Hollywood’s Queen of the B Movies Looks to SAP and EDI ... 29
... 1.1 ... SAP and EDI: Getting to Know Each Other ... 30
... 1.2 ... A Brief History of Fame: Our Imaginary Dream Factory ... 31
... ... 1.2.1 ... A Bird’s Eye View of the Business ... 33
... ... 1.2.2 ... Enter Plan Q: A New Project Is Born ... 36
... ... 1.2.3 ... We Define Our Scope ... 37
... 1.3 ... Defining Some Basic Ground Rules ... 38
... ... 1.3.1 ... The Technical Environment ... 39
... ... 1.3.2 ... The EDI System ... 39
... ... 1.3.3 ... Nothing But IDocs ... 41
... ... 1.3.4 ... Batch Processing of Large Files ... 43
... ... 1.3.5 ... File Ports ... 44
... ... 1.3.6 ... Partner Profiles ... 44
... ... 1.3.7 ... EDI Mapping Strategy ... 45
2 ... The Blueprint: Discovery and Documentation ... 47
... 2.1 ... A Business Process Overview ... 48
... ... 2.1.1 ... The As-Is Purchasing Process Flow ... 48
... ... 2.1.2 ... The As-Is Sales and Distribution Processing Flow ... 53
... ... 2.1.3 ... Selling the Dream with Vendor Management Inventory ... 56
... 2.2 ... Legacy Systems, Data Flows, and Interfaces ... 60
... ... 2.2.1 ... Title Master and DVD Repository ... 62
... ... 2.2.2 ... Release Planning and Promotions Systems ... 62
... ... 2.2.3 ... Legacy SD ... 63
... ... 2.2.4 ... Manufacturing ... 63
... ... 2.2.5 ... Finance ... 64
... ... 2.2.6 ... VMI ... 65
... ... 2.2.7 ... EDI ... 65
... 2.3 ... Legacy EDI Data Flows ... 66
... ... 2.3.1 ... Replicating Success: Outsourcing Production ... 67
... ... 2.3.2 ... Order-to-Cash and Legacy EDI ... 72
3 ... Designing the New SAP EDI Architecture ... 77
... 3.1 ... The To-Be Systems and Interfaces Emerge ... 78
... ... 3.1.1 ... The Resource Integration Manager ... 78
... ... 3.1.2 ... Let’s Get Technical: A More Intimate Look at the RIM ... 81
... 3.2 ... Laying the Foundations for EDI: Master Data ... 85
... ... 3.2.1 ... A Brief Word on Conversion Strategy ... 85
... ... 3.2.2 ... General Ledger Chart of Accounts and Cost Centers ... 86
... ... 3.2.3 ... Customer Master Sold-To ... 87
... ... 3.2.4 ... Customer Master Ship-To ... 88
... ... 3.2.5 ... Vendor Master ... 88
... ... 3.2.6 ... Material Master ... 89
... ... 3.2.7 ... Customer Material Info Records ... 90
... ... 3.2.8 ... Bill of Materials ... 91
... ... 3.2.9 ... Pricing Conditions ... 92
... 3.3 ... The Typical Life Cycle of an Order from Gordy ... 93
... ... 3.3.1 ... VMI Sales Orders ... 94
... ... 3.3.2 ... Catalog Planning ... 98
... ... 3.3.3 ... Purchasing/Manufacturing ... 101
... ... 3.3.4 ... Delivery ... 103
... ... 3.3.5 ... Billing ... 105
... ... 3.3.6 ... Payment ... 107
... 3.4 ... Interfaces in the Order-to-Cash Cycle ... 109
... 3.5 ... Considering the Project Plan ... 110
4 ... EDI: The Ugly Stepsister of E-Commerce ... 115
... 4.1 ... EDI Follows the Money ... 116
... ... 4.1.1 ... E-Commerce is Mostly Business Selling to Business ... 117
... ... 4.1.2 ... Big Numbers Booked for EDI ... 119
... ... 4.1.3 ... Manufacturing ... 120
... ... 4.1.4 ... Merchant Wholesale ... 121
... ... 4.1.5 ... What the Numbers Mean for EDI ... 122
... 4.2 ... A Brief History of EDI ... 123
... ... 4.2.1 ... The Berlin Airlift and the Supply Chain ... 123
... ... 4.2.2 ... Transportation and the Birth of Cross-Industry Standards ... 125
... ... 4.2.3 ... The Transportation Data Coordinating Committee ... 126
... ... 4.2.4 ... The Birth of ASC X12 ... 127
... ... 4.2.5 ... Global Trade and E-Commerce: UN/EDIFACT ... 129
... ... 4.2.6 ... Other EDI Standards ... 134
... ... 4.2.7 ... Value Added Networks, the Internet, and EDI ... 137
... 4.3 ... The Anatomy of an X12 Interchange ... 140
... ... 4.3.1 ... Building an Outbound EDI ... 142
... ... 4.3.2 ... Unwrapping an Inbound EDI ... 144
... ... 4.3.3 ... The Envelope Segments ... 145
... ... 4.3.4 ... Structure of the Transaction Set ... 149
... ... 4.3.5 ... Dissecting Gordy’s 850 to Acme ... 151
5 ... Real World Business Process Integration with EDI ... 167
... 5.1 ... The Basic EDI Interface ... 168
... 5.2 ... Trading Partner Management ... 169
... 5.3 ... The Impact of VMI Collaboration Through EDI ... 172
... 5.4 ... The Role of Acme’s EDI RIM ... 173
... ... 5.4.1 ... Outbound Services ... 173
... ... 5.4.2 ... Inbound Services ... 183
... ... 5.4.3 ... Archiving EDI Data ... 189
... 5.5 ... Reporting EDI Status to SAP ... 191
... ... 5.5.1 ... SAP Status Codes ... 191
... ... 5.5.2 ... Creating Custom Messages ... 194
... ... 5.5.3 ... Mapping the STATUS IDoc ... 195
... ... 5.5.4 ... So How Do We Get the Enveloping Data? ... 199
... ... 5.5.5 ... The Status Interface BPM ... 202
... ... 5.5.6 ... The 997 Functional Acknowledgement Interface ... 206
... 5.6 ... Putting All of the Pieces Together ... 210
... ... 5.6.1 ... Inbound ... 211
... ... 5.6.2 ... Outbound ... 213
6 ... EDI Architecture in SAP: The IDoc Interface ... 217
... 6.1 ... Intelligent Messages: The Anatomy of an IDoc ... 218
... ... 6.1.1 ... IDoc Terminology ... 218
... ... 6.1.2 ... Logical Message Type ... 219
... ... 6.1.3 ... IDoc Record Types ... 220
... ... 6.1.4 ... IDoc Basic Type ... 232
... ... 6.1.5 ... IDoc Extended Type ... 234
... ... 6.1.6 ... IDoc ... 234
... ... 6.1.7 ... IDoc File ... 235
... 6.2 ... Building IDoc Architecture in the Data Dictionary ... 236
... ... 6.2.1 ... Domains ... 236
... ... 6.2.2 ... Data Elements ... 238
... ... 6.2.3 ... Fields ... 238
... ... 6.2.4 ... Segments ... 239
... ... 6.2.5 ... IDoc Basic and Extended Types ... 239
... 6.3 ... Base EDI Configuration with IDocs in SAP ... 240
... ... 6.3.1 ... EDI User Name ... 241
... ... 6.3.2 ... Logical System ... 241
... ... 6.3.3 ... Connecting Systems to SAP ... 242
... ... 6.3.4 ... File Port ... 243
... ... 6.3.5 ... Message or Output Control ... 246
... ... 6.3.6 ... Partner Profiles ... 257
... 6.4 ... EDI Reference Data in SAP ... 262
... ... 6.4.1 ... Getting to Know EDPAR ... 262
... ... 6.4.2 ... EDSDC: Sales Org ... 267
... ... 6.4.3 ... KNMT: Customer Material Info Record ... 268
... ... 6.4.4 ... ZEDIXREF: EDI Trading Partner IDs ... 271
... 6.5 ... The SAP EDI Inbound Process Flow ... 272
... 6.6 ... The SAP EDI Outbound Process Flow ... 279
... ... 6.6.1 ... Building Output ... 280
... ... 6.6.2 ... Writing the IDoc to the Database ... 282
... ... 6.6.3 ... Sending the IDoc to the EDI RIM ... 285
7 ... Building Custom IDocs and IDoc Extensions ... 287
... 7.1 ... IDoc Development and Configuration Tools ... 288
... ... 7.1.1 ... SE11 — Data Dictionary ... 289
... ... 7.1.2 ... WE31 — Segment Editor ... 290
... ... 7.1.3 ... WE30 — IDoc Type Editor ... 291
... ... 7.1.4 ... WE81 — Logical Message Type ... 291
... ... 7.1.5 ... WE82 — Message to Basic Type Link ... 292
... ... 7.1.6 ... SE37 — Function Editor: Function Groups ... 292
... ... 7.1.7 ... SE37 — Function Editor: Function Modules ... 293
... ... 7.1.8 ... SE38 — ABAP Editor ... 298
... ... 7.1.9 ... SMOD — SAP Enhancements ... 299
... ... 7.1.10 ... CMOD — Project Management of SAP Enhancements ... 300
... ... 7.1.11 ... WE57 — Link Function to Message and Basic Type ... 300
... ... 7.1.12 ... BD51 — Define IDoc Attributes ... 302
... ... 7.1.13 ... WE42 — Inbound Process Code ... 302
... ... 7.1.14 ... Inbound Partner Profile ... 304
... ... 7.1.15 ... WE41 — Outbound Process Code ... 304
... ... 7.1.16 ... Outbound Partner Profile ... 304
... 7.2 ... IDoc Development Process Flow ... 304
... ... 7.2.1 ... Checklist for Developing Custom IDocs ... 305
... ... 7.2.2 ... Developing Extended IDocs ... 307
... 7.3 ... Custom IDoc: Inbound Inventory Report ... 312
... ... 7.3.1 ... Creating the Segments ... 312
... ... 7.3.2 ... Building an IDoc Basic Type ... 314
... ... 7.3.3 ... Create a Custom Message Type ... 316
... ... 7.3.4 ... Link Message to Basic Type ... 317
... ... 7.3.5 ... Create the Function Group ... 317
... ... 7.3.6 ... Code an IDoc Processing Function ... 318
... ... 7.3.7 ... Link the Function to Message and Basic Type ... 322
... ... 7.3.8 ... Set Attributes for the Function ... 323
... ... 7.3.9 ... Create a Process Code ... 323
... ... 7.3.10 ... Define the Partner Profile ... 324
... 7.4 ... IDoc Extension: Outbound ORDRSP with BOM ... 325
... ... 7.4.1 ... Create Segment Z1EDP01 ... 326
... ... 7.4.2 ... Build Extension ZORDRS01 ... 326
... ... 7.4.3 ... Link Message to Basic and Extended Types ... 328
... ... 7.4.4 ... Create the Modification Project ... 328
... ... 7.4.5 ... Coding the Exit ... 331
... ... 7.4.6 ... Define Message Control ... 333
... ... 7.4.7 ... Build Outbound Partner Profile ... 335
8 ... Building the 850–ORDERS Inbound ... 339
... 8.1 ... Functional Specifications ... 340
... ... 8.1.1 ... Process Overview ... 340
... ... 8.1.2 ... Requirements ... 340
... ... 8.1.3 ... Dependencies ... 341
... ... 8.1.4 ... Assumptions ... 342
... ... 8.1.5 ... Data Required to Create a Sales Order ... 343
... ... 8.1.6 ... Reconciliation Procedure ... 344
... ... 8.1.7 ... Enhancements to the Process ... 344
... ... 8.1.8 ... Enhancement Details ... 344
... ... 8.1.9 ... Errors and Error Handling ... 345
... 8.2 ... End-to-End Process Flow ... 345
... 8.3 ... Technical Specifications ... 351
... ... 8.3.1 ... Interface Summary ... 352
... ... 8.3.2 ... Technical Requirements ... 352
... ... 8.3.3 ... Dependencies ... 353
... ... 8.3.4 ... Assumptions ... 353
... ... 8.3.5 ... SDQ Processing in the ORDERS05 Translation ... 353
... ... 8.3.6 ... Duplicate Checking Enhancement ... 367
... 8.4 ... EDI Configuration in SAP ... 373
... ... 8.4.1 ... EDPAR Entries ... 373
... ... 8.4.2 ... EDSDC Entry ... 373
... ... 8.4.3 ... ZEDIXREF Entries ... 374
... ... 8.4.4 ... Partner Profile ... 375
9 ... Building the ORDRSP–855 Outbound ... 377
... 9.1 ... Functional Specifications ... 377
... ... 9.1.1 ... Process Overview ... 378
... ... 9.1.2 ... Requirements ... 378
... ... 9.1.3 ... Dependencies ... 379
... ... 9.1.4 ... Assumptions ... 380
... ... 9.1.5 ... Data That Will Be Passed to Order Confirmation ... 380
... ... 9.1.6 ... Enhancements to the Process ... 381
... ... 9.1.7 ... Enhancement Details ... 381
... ... 9.1.8 ... Reconciliation Procedure ... 382
... ... 9.1.9 ... Errors and Error Handling ... 383
... 9.2 ... End-to-End Process Flow ... 383
... 9.3 ... Technical Specifications ... 387
... ... 9.3.1 ... Short Description ... 387
... ... 9.3.2 ... Interface Summary ... 387
... ... 9.3.3 ... Technical Requirements ... 388
... ... 9.3.4 ... Dependencies ... 388
... ... 9.3.5 ... Assumptions ... 389
... ... 9.3.6 ... Extended IDoc Type ZORSDQ01 ... 389
... ... 9.3.7 ... SDQ Bundling and IDoc Output Program ... 396
... 9.4 ... Mapping Specifications — The ORDERS05_ZORSDQ01-855 Map ... 417
... 9.5 ... EDI Configuration in SAP ... 420
... ... 9.5.1 ... EDPAR Entries ... 420
... ... 9.5.2 ... ZEDIXREF Entries ... 421
... ... 9.5.3 ... Standard ORDRSP Configuration: No SDQ ... 421
... ... 9.5.4 ... Custom ORDRSP Configuration: SDQ Processing ... 425
10 ... Building the SHPORD–830 Outbound ... 431
... 10.1 ... Functional Specifications ... 432
... ... 10.1.1 ... Process Overview ... 432
... ... 10.1.2 ... Requirements ... 432
... ... 10.1.3 ... Dependencies ... 434
... ... 10.1.4 ... Assumptions ... 434
... ... 10.1.5 ... Data That Passes to the IDoc from the Delivery ... 436
... ... 10.1.6 ... Enhancements to the Process ... 437
... ... 10.1.7 ... Reconciliation ... 438
... ... 10.1.8 ... Errors and Error Handling ... 438
... 10.2 ... End-to-End Process Flow ... 439
... 10.3 ... Technical Specifications ... 442
... ... 10.3.1 ... Short Description ... 442
... ... 10.3.2 ... Interface Summary ... 442
... ... 10.3.3 ... Technical Requirements ... 443
... ... 10.3.4 ... Dependencies ... 444
... ... 10.3.5 ... Assumptions ... 444
... 10.4 ... Mapping Specifications — The SHPORD-830 Map ... 445
... 10.5 ... EDI Configuration in SAP ... 450
... ... 10.5.1 ... EDPAR Entries ... 450
... ... 10.5.2 ... ZEDIXREF Entries ... 450
... ... 10.5.3 ... SHPORD Configuration ... 450
11 ... Building the 856–SHPCON Inbound ... 455
... 11.1 ... Functional Specifications ... 456
... ... 11.1.1 ... Process Overview ... 456
... ... 11.1.2 ... Requirements ... 456
... ... 11.1.3 ... Dependencies ... 458
... ... 11.1.4 ... Assumptions ... 458
... ... 11.1.5 ... Data Required to Update a Delivery Document ... 459
... ... 11.1.6 ... Enhancements to the Process ... 461
... ... 11.1.7 ... Reconciliation ... 461
... ... 11.1.8 ... Errors and Error Handling ... 462
... 11.2 ... End-to-End Process Flow ... 462
... 11.3 ... Technical Specifications ... 465
... ... 11.3.1 ... Short Description ... 465
... ... 11.3.2 ... Interface Summary ... 466
... ... 11.3.3 ... Technical Requirements ... 466
... ... 11.3.4 ... Dependencies ... 467
... ... 11.3.5 ... Assumptions ... 467
... 11.4 ... Mapping Specifications — The 856-SHPCON Map ... 468
... 11.5 ... EDI Configuration in SAP ... 475
... ... 11.5.1 ... EDPAR Entries ... 476
... ... 11.5.2 ... ZEDIXREF Entries ... 476
... ... 11.5.3 ... Partner Profile ... 476
12 ... Building the DESADV–856 Outbound ... 479
... 12.1 ... Functional Specifications ... 480
... ... 12.1.1 ... Process Overview ... 480
... ... 12.1.2 ... Requirements ... 480
... ... 12.1.3 ... Dependencies ... 481
... ... 12.1.4 ... Assumptions ... 482
... ... 12.1.5 ... Data That Passes to the IDoc from the Delivery ... 483
... ... 12.1.6 ... Enhancements to the Process ... 485
... ... 12.1.7 ... Reconciliation ... 485
... ... 12.1.8 ... Errors and Error Handling ... 485
... 12.2 ... End-to-End Process Flow ... 486
... ... 12.2.1 ... Outbound DESADV Processing Flow ... 486
... ... 12.2.2 ... Output Control ... 488
... 12.3 ... Technical Specifications ... 493
... ... 12.3.1 ... Short Description ... 493
... ... 12.3.2 ... Interface Summary ... 493
... ... 12.3.3 ... Technical Requirements ... 494
... ... 12.3.4 ... Dependencies ... 495
... ... 12.3.5 ... Assumptions ... 495
... 12.4 ... Mapping Specifications ... 496
... ... 12.4.1 ... The DESADV-856 Map ... 496
... 12.5 ... EDI Configuration in SAP ... 500
... ... 12.5.1 ... EDPAR Entries ... 500
... ... 12.5.2 ... PUMA Entries ... 500
... ... 12.5.3 ... ZEDIXREF Entries ... 501
... ... 12.5.4 ... DESADV Configuration ... 501
13 ... Building the INVOIC–810 Outbound ... 507
... 13.1 ... Functional Specifications ... 508
... ... 13.1.1 ... Process Overview ... 508
... ... 13.1.2 ... Requirements ... 509
... ... 13.1.3 ... Dependencies ... 510
... ... 13.1.4 ... Assumptions ... 511
... ... 13.1.5 ... Data That Passes to the IDoc from the Delivery ... 512
... ... 13.1.6 ... Enhancements to the Process ... 513
... ... 13.1.7 ... Enhancement Details ... 514
... ... 13.1.8 ... Reconciliation ... 515
... ... 13.1.9 ... Errors and Error Handling ... 515
... 13.2 ... End-to-End Process Flow ... 516
... ... 13.2.1 ... Outbound INVOIC Processing Flow ... 516
... ... 13.2.2 ... Generating the Invoices ... 518
... ... 13.2.3 ... Output Control ... 519
... 13.3 ... Technical Specifications ... 525
... ... 13.3.1 ... Short Description ... 525
... ... 13.3.2 ... Interface Summary ... 525
... ... 13.3.3 ... Technical Requirements ... 526
... ... 13.3.4 ... Dependencies ... 526
... ... 13.3.5 ... Assumptions ... 527
... ... 13.3.6 ... PO Number Mass Change Report ... 527
... 13.4 ... Mapping Specifications — The INVOIC-810 Map ... 554
... 13.5 ... EDI Configuration in SAP ... 557
... ... 13.5.1 ... EDPAR Entries ... 557
... ... 13.5.2 ... ZEDIXREF Entries ... 558
... ... 13.5.3 ... INVOIC Configuration ... 558
14 ... Building the 820–REMADV Inbound ... 563
... 14.1 ... Functional Specifications ... 564
... ... 14.1.1 ... Process Overview ... 564
... ... 14.1.2 ... Requirements ... 565
... ... 14.1.3 ... Dependencies ... 566
... ... 14.1.4 ... Assumptions ... 567
... ... 14.1.5 ... Data Required to Update a Delivery Document ... 568
... ... 14.1.6 ... Enhancements to the Process ... 570
... ... 14.1.7 ... Reconciliation ... 570
... ... 14.1.8 ... Errors and Error Handling ... 570
... 14.2 ... End-to-End Process Flow ... 571
... 14.3 ... Technical Specifications ... 575
... ... 14.3.1 ... Short Description ... 575
... ... 14.3.2 ... Interface Summary ... 575
... ... 14.3.3 ... Technical Requirements ... 575
... ... 14.3.4 ... Dependencies ... 576
... ... 14.3.5 ... Assumptions ... 577
... ... 14.3.6 ... EDI Process to Split Very Large 820s ... 577
... ... 14.3.7 ... User Transaction Code for the SAP Split Program ... 583
... 14.4 ... Mapping Specifications — The 820-REMADV Map ... 583
... 14.5 ... EDI Configuration in SAP ... 589
... ... 14.5.1 ... EDPAR Entries ... 589
... ... 14.5.2 ... Link Sold-to Partner to Acme Company Code ... 589
... ... 14.5.3 ... ZEDIXREF Entries ... 590
... ... 14.5.4 ... Partner Profile ... 590
15 ... Extending the Interface: Custom IDoc Tools ... 595
... 15.1 ... Mass Upload of Partner Profiles to SAP ... 596
... ... 15.1.1 ... The Issue ... 597
... ... 15.1.2 ... The Solution ... 597
... ... 15.1.3 ... Dependencies ... 599
... ... 15.1.4 ... Program ZEDI_UPLDPP ... 600
... ... 15.1.5 ... Further Automating Partner Profile Processing ... 608
... 15.2 ... EDI Trading Partner to Control Segment ... 611
... ... 15.2.1 ... The Issue ... 611
... ... 15.2.2 ... The Solution ... 612
... ... 15.2.3 ... Program Flow ... 613
... 15.3 ... Mass Transfer of IDocs Between Systems ... 619
... ... 15.3.1 ... The Issue ... 619
... ... 15.3.2 ... The Solution ... 620
... ... 15.3.3 ... Dependencies ... 620
... ... 15.3.4 ... Program ZEDI_TRNSFIDOCS ... 620
... 15.4 ... Changing IDoc Status ... 626
... ... 15.4.1 ... The Issue ... 626
... ... 15.4.2 ... The Solution ... 626
... ... 15.4.3 ... Program ZEDI_CHNGSTATUS ... 627
16 ... Testing the EDI System in SAP ... 631
... 16.1 ... IDoc Test Tools ... 632
... ... 16.1.1 ... WE19 — IDoc Test Tool ... 632
... ... 16.1.2 ... WE16 – Inbound Processing of IDoc File ... 636
... ... 16.1.3 ... WE15 — Outbound from Message Control ... 636
... ... 16.1.4 ... WE14 — Outbound from IDoc ... 637
... 16.2 ... Interface Testing Strategy ... 638
... ... 16.2.1 ... Testing Environments ... 639
... ... 16.2.2 ... Break-Fix Procedures ... 641
... ... 16.2.3 ... Test Teams and Responsibilities ... 642
... ... 16.2.4 ... Documenting Tests ... 644
... 16.3 ... Unit Testing ... 647
... ... 16.3.1 ... Scope ... 648
... ... 16.3.2 ... Criteria for Success ... 648
... ... 16.3.3 ... Dependencies ... 648
... ... 16.3.4 ... Execution ... 649
... 16.4 ... String Testing ... 649
... ... 16.4.1 ... Scope ... 650
... ... 16.4.2 ... Criteria for Success ... 651
... ... 16.4.3 ... Dependencies ... 651
... ... 16.4.4 ... Execution ... 652
... 16.5 ... Interface Testing ... 656
... ... 16.5.1 ... Scope ... 657
... ... 16.5.2 ... Criteria for Success ... 658
... ... 16.5.3 ... Dependencies ... 659
... ... 16.5.4 ... Execution ... 660
... 16.6 ... Integration Testing ... 663
... ... 16.6.1 ... Scope ... 664
... ... 16.6.2 ... Criteria for Success ... 665
... ... 16.6.3 ... Dependencies ... 666
... ... 16.6.4 ... Execution ... 667
... 16.7 ... Stress Testing ... 676
... ... 16.7.1 ... Scope ... 676
... ... 16.7.2 ... Criteria for Success ... 677
... ... 16.7.3 ... Dependencies ... 677
... ... 16.7.4 ... Execution ... 678
17 ... Troubleshooting and Recovery ... 681
... 17.1 ... Identifying Issues ... 682
... ... 17.1.1 ... Definition of Success ... 682
... ... 17.1.2 ... Definition of Failure ... 684
... ... 17.1.3 ... Functional or Business Failure ... 687
... 17.2 ... Monitoring and Recovery Tools ... 690
... ... 17.2.1 ... Monitoring and Processing IDocs with BD87 ... 691
... ... 17.2.2 ... Listing IDocs with Transactions WE02 and WE05 ... 708
... ... 17.2.3 ... Processing Log for Output Control ... 709
... ... 17.2.4 ... Viewing Errors with Transaction WE07 ... 710
... ... 17.2.5 ... Searching for IDocs by Field Contents with Transaction WE09 ... 711
... ... 17.2.6 ... Identify an Interrupted File with Transaction WE08 ... 712
... 17.3 ... Identifying Key Points of Failure ... 713
... ... 17.3.1 ... Technical Troubleshooting ... 713
... ... 17.3.2 ... Functional Troubleshooting ... 720
... Epilogue ... 727
... The Author ... 731
|
.gif)
|
.gif){kind=small}
.gif){kind=small}
.gif){kind=small}
.gif){kind=small}
.gif){kind=icon}
.gif){kind=small}
.gif)
(ffffff)(19x14).gif){kind=small}