FormatBankTransferWord文档下载推荐.docx

1、The design document has to be available in the English language. Other languages are optional.Before the external review, this document should be reviewed by a native speaker.See also the document link Relation of PIL Documents for further information.About this TemplateThis template （Software Detai

2、led Design） replaces the former template for design.It should be used for the software design of:SAP components according to the solution builder （transaction ZSOLPROD in ISP） or the Product Planning Management System （PPMS, transaction BOPP in ISP）Subcomponents such as application components in the

3、 application component hierarchy （ACH）, Java packages, or other types of programs or subprogramsAuthor: Christian Schmidkonz - Template Owner: Christian SchmidkonzContact the template owner if you have any ideas to improve this template.Version: 2.0Before you start to work with this template read th

4、e instructions （see link） “How to Use this Template” on the first page Pieter BadenhorstReportingS10_ERP_GS_UAE_HCM HistoryVersionEnter document version; （see rules below）DateEnter document version date01-JUN-2005Status （Comments）Draft, For Review, Released.Comments are needed if a SDD has several “

5、releases”1.001.07.2010Draft2.028.09.2010New layout createdTable of Contents1 References 42 Organization 43 Glossary 44 Overview and Architecture 44.1 Overview/Introduction 54.2 Architecture 54.3 Reuse/Components Used/Use Dependencies 54.4 Alternative Design Ideas 54.5 Deviations and Constraints 55 D

6、etailed Design 55.1 General features 55.1.1 HAEXXXXX - Include for utilities - reading constants, tables, . 65.1.2 HAEXXXX1 - Include for ALV and Error messages 65.1.3 HAEXXXX2 - Include for File operations 65.2 HAEWPS00 WPS System 65.2.1 Selection screen 65.2.2 Layout Specification: 75.2.3 Program

7、flow 175.2.4 Subroutines 175.2.5 Output 175.2.6 Database Design 175.2.7 Example 195.3 HAECADR0 ADRPBF （Abu Dhabi Retirement Pensions and Benefits Fund） Report （REQ-PR-19874-0006） 195.3.1 T7AE13 Layout Configuration for ADRPBF Pension Fund Report. 215.3.2 Selection screen 225.3.3 Program flow 225.3.4

8、 Subroutines 225.3.5 Output 235.3.6 Template 235.3.7 Off-cycles: 245.3.1 Retro Calculation:5.4 HAEPTRD0 Travel Document Expiry Report （REQ-PR-19874-0011） 245.4.1 Selection screen 265.4.2 Program flow 265.4.3 Subroutines 275.4.4 Output 285.4.5 Template 285.4.6 Example 295.5 HAECLEAV0 Leave Passage Ca

9、lculation UAE （REQ-PR-19874-0016 295.5.1 Selection screen 295.5.2 Reporting Requirements: 305.5.3 Reporting Output Requirements: 315.5.4 Program flow 315.5.5 Methods 325.5.6 Output 325.5.7 Template 335.5.8 Example 335.6 HAECEDT0 Remuneration Statement 335.6.1 Selection screen 345.6.2 Program flow 34

10、5.6.3 Subroutines 355.6.4 Output 355.6.5 Template 355.6.6 Example 365.7 HAECGPS0 - Pension Fund Contribution （GPSSA） UAE Nationals 365.7.1 Reporting Requirements: 365.7.2 T7AE12 Layout Configuration for GCC National Pension Fund Reports. 365.7.3 Selection Screen 375.7.4 Program flow 385.7.5 Subrouti

11、nes 385.7.6 Output 395.7.7 Template 395.7.8 Example 395.8 HAECOMN0 - Pension Fund Contribution Report for Omani Nationals 395.8.1 Selection Screen 395.8.2 Program flow 395.8.3 Subroutines 405.8.4 Output 405.8.5 Template 405.8.6 Example 405.9 HAECBAR0 - Pension Fund Contribution Report for Bahraini N

12、ationals 415.9.1 Selection Screen 415.9.2 Program flow 415.9.3 Subroutines 415.9.4 Output 425.9.5 Template 425.9.6 Example 425.10 HAECSAR0 - Pension Fund Contribution Report for Saudi Nationals 425.10.1 Selection Screen 425.10.2 Program flow 425.10.3 Subroutines 435.10.4 Output 435.10.5 Template 435

13、.10.6 Example 436 Verification of SAP Product Standards 437 Industry Standards 448 Migration/Upgrade Aspects 448.1 Compatibility with Previous Versions 448.2 Upgrade Procedures/Data Volume 459 Test Programs/Test Cases/Test Environment 459.1 Unit Tests 459.2 Additional Tests and Check Programs 459.3

14、Test Data 4510 Patents/Intellectual Property 4511 Miscellaneous 4512 Open Issues 4513 Appendices 45ReferencesIn this table give a complete list of all documents （with ID if applicable） that are assigned to the design scope.Document No.If applicable: Enter document ID e.g. from cARC/ cProjects with l

15、inkDocument TitleFor example, enter SRS, UI-Spec, Architecture Guidelines, ERDs, work packages . with title and versionEnter document date CommentsEnter the author/publishing organization responsible/reason for referencePR-19874UAE: HCM-PR-Specification_19874Pieter Badenhorst/Epi-Use Africa/SDDNote:

16、 Specific hints on how to proceed with cARC/cProjects are described in （see link） How to work with this document on the first page of this template.OrganizationEnter all persons who worked on this document:NameProject Role（s）/CommentsDevelopment Architect Consultant IMS DeveloperUser Interface Desig

17、ner Info DeveloperKnowledge Management ContactSolution Management Experttopic specialist of areaTranslator Modeler Producer of training materialPieter BadenhorstEpi-Use AfricaAuthorChristof SchmollSAP Project LeadChristelle CollingsProject ManagerJans SteynSolution ArchitectFrancois BreedtSoftware D

18、eveloper Harry AbrahamsSoftware DeveloperDavid AllenKerstin SaelzerSAPQuality ManagerJessica BoutalebKnowledge ManagementAchan LandmanTest Case Authors/Professional Testers R: Required Entry; for Roles and Responsibilities see the Q&A in Project Weaver: Compare SAPNet quick link: /projectweaver - Bu

19、tton “Open ProjectWeaver”GlossaryUse generally-known expressions and those technical terms that are defined in the terminology database of SAP （SAPterm）.Enter all additional terms that have not yet been defined in the referenced SRS documents, but are of significance for this document/development do

20、cuments.Working together with your information development team, gather, standardize, and define all new or changed terms and abbreviations in German and English required to properly understand the SRS. Provide draft definitions of these terms. Refer to entries in the appendix of the SRS, to entries

21、 in the SAP term terminology database （Quick link sapterm in SAPNet）, or to other documents.Make sure that all abbreviations, initials and acronyms are clearly associated with their relevant terms. Define no more than one allowed abbreviation per term. For more information, see section “Abbreviation

22、s on the User Interface” in the general Standards and Guidelines for Writing at SAP （or in SAPNet, see link Product Standard Documentation）.English TermEnglish AbbreviationGerman TermGerman AbbreviationDefinitionEntryEnter whether it is new or already exists in saptermOverview and ArchitectureThe fo

23、cus of this document is NW and all Applications （non-ESA）.Overview/IntroductionThe guidelines given in ERD/Architecture Guidelines have to be considered.Provide a general but short description of the solution in this chapter.ArchitectureArchitecture This chapter should describe the architecture and

24、the behavior of the software to be designed. Recommended modeling techniques are described in the standards for modeling in the Software Detail Design.Please use block diagrams, package diagrams, UML class diagrams, and/or UML sequence diagrams to describe the structure and behavior of the software.

25、In addition, please describe each part of the architecture in a few words.If necessary, show the behavior using behavior diagrams such as UML activity diagrams or UML sequence diagrams. To depict the state transitions of a certain object use UML state chart diagrams and describe them.Do not forget to show the data model using UML class diagrams for example, and in object-oriented design please give an introduction to/overview of the （conceptual） classes using UML class diagrams.Integration in Application ArchitectureGive a rough overview