标准的全球性发展英文

Information Technology Celestica Confidential Global ABAP Naming Standards Global SAP Development Architecture Document Revision History TABLE OF CONTENTS 1.AUTHORIZATION GROUPS6 2.BACKGROUND JOB7 3.BDC SESSIONS9 4.DATA ELEMENTS10 5.DEVELOPMENT CLASS.11 6.DOMAIN.12 7.DIALOG PROGRAM13 8.DIALOG INCLUDE 14 9.ENHANCEMENT PROJECTS15 10.FUNCTION GROUPS.16 11.FUNCTION MODULES17 12.FUNCTION MODULE INCLUDES18 13.EVENTS19 14.LAYOUT SET 20 15.LOCK OBJECT .21 16.LOGICAL DATABASE 22 17.MESSAGE CLASS.23 18.MESSAGE NUMBER24 19.MODULE POOL FOR SCREENS.25 20.PROGRAM NAME26 21.SCREENS28 22.STANDARD TEXT ID.29 23.STANDARD TEXT NAME: .30 24.STYLES.31 25.SUBROUTINE POOLS.32 26.TABLES 33 27.TABLE FIELDS.34 28.TABLE GROUP.35 29.TABLE INDEX.36 30.TABLE STRUCTURE.37 31.TABLE VIEWS38 32.TEXT ELEMENTS39 33.TRANSACTION CODES40 34.VARIANT .41 35.WORK ID42 36.FILE NAME43 37.SIGNAL FILE NAME.44 38.STANDARD FILE LAYOUT .45 39.INFOSET QUERY.46 40.USER GROUP47 41.IDOC FILE PORT.48 42.XML FILE PORT 48 43.SEARCH HELP49 44.LSMW PROJECT NAME.50 45.LSMW SUBPROJECT NAME.51 46.LSMW OBJECT 51 47.LOGICAL SYSTEM FOR INTERFACES52 48.CLASSES 53 49.BOR OBJECTS (BUSINESS OBJECT REPOSITORY) AND RELATED COMPONENTS.54 50.RFC CONNECTION FOR INTERFACE .54 51.ALE PORT FOR INTERFACE55 52.LS PARTNER PROFILE FOR INTERFACE55 53.ALE DISTRIBUTION MODEL.55 54.SAP USER ID FOR INTERFACE .56 55.SAP USER ID FOR BATCH JOB56 56.SAP USER ID FOR WORKFLOW56 1.Authorization Groups ABAP/4 Authorization Group is a means of assigning ABAP/4 Programs for access protection. The system checks that a user belongs to an authorization group when Starting or editing a program, Maintaining attributes, Using other program development utilities SAP R/3 Requirements: An Authorization Group name must begin with a Z. and may be a maximum of 8 characters long. Standard: Authorization group naming standards are controlled by the Security Administrator and will allow for easier maintenance of security profiles. Format: Z x n xxxxx |Unique Identifier |Sequential Indicator |Functional Descriptor Identifier Position DescriptionValuesMeaning 1IdentifierZIdentifies as a custom Authorization Group 2Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 3Sequential Indicator 1 - n1 is highest level of authority. Incrementing value decreases authority. 4-8Unique Identifier 00000 - ZZZZZ Assigned by Security Administrator. Example:1.ZG1 2.ZG2 The first group, ZGL1, would have the greatest access. It would include access specific to that group, as well as all the same accesses of the second, third, and fourth groups below it. Likewise, the access granted to group 4 would not have any of the authorization roles in those groups above it. 2.Background Job PositionDescriptionValuesMeaning 1-3Locationchar3 character standard Celestica location ALL Global AMR AMERICA EUR Europe PAC Pacific Asia CUK UK CIR Ireland CIT Italy CCA Canada CUS U.S.A Check the complete list in Celestica Intranet 4-6SystemFix valueAlways SAP 7-8Module or Functional Description BWBusiness Information Warehouse FIFinancial accounting GLGeneral Ledger HRHuman Resources IMInventory management COCost Accounting MSMerchandise management system (MMS) MMMaterial Management PCProduction (PPC) SPPersonnel Planning PMPlant maintenance PBPublishing PPProduction Planning QSQuality assurance (QSS) or Quality management SDSales UTGeneral System/Utility programs SMService Management CSCustomer Service AOAPO CMCRM ZZProgrammer work ABAP 9Separator_Always underscore 10Program TypeIInterface Program CConversion EEnhancement RReport FForm MSystem Maintenance USystem Update OOthers 11Data FlowIInbound OOutbound PositionDescriptionValuesMeaning BBoth NNot applicable 12Separator_Always underscore 13 - 15Customer Code3 chars3 chars customer name ALL- More than one or All customers XXX Not for any customer See the next section for list of customers, this list will be updated regularly. 16 - 19SAP Pant4 chars4 chars plant from SAP table T001W 20 - 32Job Description12 charsUp to 16 characters Example:1.CUKSAPSD_II_SUN4203NVOICE 2.CTOSAPMM_IO_LUC6102SALEORDER 3.BDC Sessions Standard: Naming convention for BDC sessions will vary depending on the needs of a customer. In many cases, the naming conventions for BDC sessions need to be worked in conjunction with the Security Administrator. Considerations: BDC session names do not require unique names. BDC security may be set up based on the name of the BDC session. A BDC session with a Company Code embedded in the name may be beneficial. In many circumstances, end-users will be required to process BDC sessions; this should be taken into account when establishing BDC naming conventions. 4.Data Elements Standard: DO NOT create new data elements, use standards SAP data elements where it is possible. New data elements must be activated for better tracking purposes. Where possible, use the same name as the domain associated with the data element. If there is a conflict, name the data element in a meaningful manner. SAP does create Data Elements that begin with a Z, so custom Data Elements should begin with ZZ. Data element names should have a maximum of 8 characters. SAP generated programs or functions may use this dictionary object definition for SELECT-OPTIONS and PARAMETERs, which may be up to 8 characters long. Format: ZZxxxxxx |description Identifier Position DescriptionValuesMeaning 1-2TypeZZUses ZZ 3-8descriptionX (upto 6 chars) A meaningful name describing the data element Example:1.ZZORDER 2.ZZNUMBER 5.Development Class Format: Zxxx | |Unique Identifier Custom Identifier Position DescriptionValuesMeaning 1Custom Identifier ZAlways Z 2Program Type BWBusiness Information Warehouse FIFinancial accounting GLGeneral Ledger HRHuman Resources IMInventory management COCost Accounting MSMerchandise management system (MMS) MMMaterial Management PCProduction (PPC) SPPersonnel Planning PMPlant maintenance PBPublishing QSQuality assurance (QSS) or Quality management SDSales UTGeneral System/Utility programs SMService Management CSCustomer Service AQABAP Query CRMCRM APOAPO ZZProgrammer work ABAP Example:1.ZMM 2.ZUT 6.Domain Standard: DO NOT create new domains where it is possible. New domains must be activated for better tracking purposes. Where possible, use an existing Domain. If that is not possible, name the Domain in a meaningful manner. SAP does create Domains that begin with a Z, so custom Domains should begin with ZZ. Domain names should have a maximum of 8 characters. SAP generated programs or functions may use this data dictionary object definition for SELECT-OPTIONS or PARAMETER and the allowable length for the variable is 8 characters. Format: ZZxxxxxx |Description Custom Identifier Position DescriptionValuesMeaning 1-2Custom Identifier ZZAlways ZZ 3-8DescriptionX (upto 6 chars) A meaningful name describing the data element Example:1.ZZDATE 2.ZZTIME 7.Dialog Program Standard: The name has to begin with SAPD. The fifth character must be a Z. Format: SAPDZxxx |Unique Identifier |Functional Descriptor Identifier Position DescriptionValuesMeaning 1-5IdentifierSAPDZCustom Module Pool for Dialog 6Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 7-8Unique identifier 00-ZZtwo digit alpha-numeric to uniquely identify Example:1.SAPDZV01 2.SAPDZH01 For HR only: MP99xxxxx |Unique Identifier |Functional Descriptor Identifier Position DescriptionValuesMeaning 1-3IdentifierMP9Custom Module Pool for Dialog 4Fix number9Always 9 5-7Number(0-999)Info Type 8-9Unique identifier 00-4010 program statement 20 PBO 30 PAI 40 Subroutine 8. Dialog Include Standard: INCLUDES for dialog programs have to begin with the last 5 characters of the module pool name. It should then be followed by a three digit identifier. Format: DZxxxxxx |Include identifier Indicates as custom Dialog Module pool Include Position DescriptionValuesMeaning 1-5IdentifierDZxxxIdentifies as custom Module Pool include 6-8Include Identifier TOPData Fields IxxScreen Input, where nn is a two-digit alpha-numeric OxxOutput, where nn is a two-digit alpha-numeric FxxForms, where nn is a two-digit alpha-numeric Example:1.DZM01I01 2.DZM01O01 9. ENHANCEMENT PROJECTS The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications. Standard Format: Enhancement project names should begin with Z followed by the application area and the last 4 digits of the module pools name. The last 2 digits should be a unique identifier. ZXXXXXXX | | | | | | | Last 4 of Module Pool Name Unique Identifier |Application Area Customer Position DescriptionValuesMeaning 1IdentifierZPermanent 2Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 3-6Last 4 of Module Pool Name XXXXModule pool name 7-8Unique Description (up to 29 chars) Describe the enhancement Example:1.ZSZM0101 2.ZMZM0201 10. FUNCTION GROUPS Considerations: When function modules are called, the system loads the whole function group into main memory. A maximum of six developers can maintain function modules within a function group at any one time. Standards: The naming standards will ensure the custom Function Groups will not conflict with present or future SAP delivered function groups, as well as serve to identify groups of related function modules by functional area. When a Function Group is created, SAP creates a program with the naming convention SAPLxxxx, where xxxx is the name of the function group. Format: Z x(up to 29 chars) |Unique Descirption |Functional Descriptor Identifier Position DescriptionValuesMeaning 1TypeZCustom function Group 2Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 3-31Unique Description (up to 29 chars) Describe the function module Example:1.ZFGETCUSTOMER 2.ZMDISPLAYTOTAL 11. FUNCTION MODULES Standards: Function module names should begin with Z Format: Z_ xx(26) |Primary Table name |Functional Descriptor |Always underscore Identifier Position DescriptionValuesMeaning 1IdentifierZPermanent 2Separator_Always underscore 3Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 4-30Descriptionx(26)Purpose of function module Example:1.Z_UFTP 2.Z_S_GET_SALE_ORDER 12. FUNCTION MODULE INCLUDES Standard: INCLUDES for custom programs have to begin with the last 5 characters of the module pool name, and end with a three digit combination identifying the type of include member. Uses include names as generated by SAP in workbench. 13. EVENTS Standard: SAP events are used to establish a dependency between two processes. Use an SAP Event to generalize types of jobs that will be released periodically; use the Event parameter to restrict Events to specific jobs. Format: Zx _(up to 29 chars) |Primary Table name |Separator |Program Type Identifier Position DescriptionValuesMeaning 1IdentifierZZ for custom EVENT 2Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 3Separator_Always underscore 3-32Description(up to 29 chars) Descriptive String - identifying the job being triggered Example:1.ZS_RUN_JOB 2.ZM_CREATE_SCHEDULE 14. Layout Set Standard Format: Z x _ x(12) |Descriptive Identifier |always underscore |Functional Descriptor Custom Indicator Position DescriptionValuesMeaning 1Custom Indicator ZCustom Indicator 2Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 3Separator_always underscore 4-15Descriptive Identifier Up to 12 chars SAP Layout set name Example:1.ZM_PO 2.ZS_SALE_ORDER 15. Lock Object Standard Format: EZX(7) |Primary Table Custom Identifier Position DescriptionValuesMeaning 1-2Custom Identifier EZAlways start with “EZ” for custom developed Lock Object 3-10Primary TableX (up to 7 chars) The name of the primary table entered in the primary table field of the Lock Object create screen Example:1.EZORDER 2.EZCHEQUE 16. LOGICAL DATABASE Standards: When creating a LDB, the entry field allows for 3 characters to be input. The first two characters are the name of the logical database and the third character is the application area the LDB belongs. When attaching an ABAP/4 Report to a LDB, the LDB consists of 2 characters and a separate field to identify the application area, which must be in table TAPLT. Format: Zx x |Application area from table TAPLT |Unique Identifier Custom Identifier Position DescriptionValuesMeaning 1Custom Identifier ZCustom developed 2Unique Identifier0-ZUniquely identifies the LDB 3Application Areaentry must exist in table TAPLT The Application Area the LDB is to be associated. Entry must be in table TAPLT Example:1.Z1M 2.ZIF 17. Message Class Standards: The message class will begin with a Z and the 2nd character will be the application ID. When a need arises to define a new message ID the following convention should be used. Format: Z x |Functional Descriptor Custom Indicator Position DescriptionValuesMeaning 1TypeZCustom developed 2Functional Descriptor (A-Z)(see functional descriptor of program naming standard) Example:1.ZS 2.ZU . 18. Message Number Standards: The message number range is 001-999. Format: Nnn Position DescriptionValuesMeaning 1-3Number Range 001-999Custom Message Number Example:1.100 2.200 19. MODULE POOL for SCREENS An ABAP/4 module pool is a group of ABAP/4 programs that accesses common processing modules, checks and processes user inputs during a transaction. The module pool is also a means of linking all the associated screens, menus and function keys of the interface as a transaction. Unlike an ABAP/4 program, a module pool consist entirely of Include programs. These Includes contain the appropriate processing logic. Include programs have a program attribute type of I. Standard Format: Screen module pool names should begin with SAPMZ followed by a 1 character functional descriptor. The last 3 digits of the name should be a unique alpha-numeric identifier. Includes form module pools should be generated by SAP and the name generated should not be changed. SAPMZxx |Alphanumeric Identifier |Functional Descriptor Indicates Dialog Module pool Position DescriptionValuesMeaning 1-5IdentifierSAPMZCustom Module Pool for Screen 6Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 7-8Alphanumeri c identifier 00-ZZtwo digit alpha-numeric to uniquely identify Example:1.SAPMZM01 2.SAPMZF01 20. Program Name Format: Zxxxx(4)x (up to 8) |User defined |Unique Identifier |Region Identifier |Program Type |Functional Descriptor Custom Indicator PositionDescriptionValuesMeaning 1Custom IndicatorZCustom Developed ABAP/4 Report 2Functional DescriptorBBusiness Information Warehouse FFinancial accounting GGeneral Ledger PHuman Resources LInventory management KCost Accounting WMerchandise management system (MMS) MMaterial Management CProduction (PPC) DCustomer Service HPersonnel Planning IPlant maintenance JPublishing QQuality assurance (QSS) or Quality management VSales SService Management TABAP/4 Shell programs UGeneral System/Utility programs XCross Modules AAPO RCRM ZProgrammer work ABAP 3Program TypeRReport Program IInterface Program CConversion EEnhancement FForm XCross Program Includes MOther 4Region IdentifierGGlobal EEurope AAmerica PAsia Pacific 5-8Unique Identifier0000-ZZZZUnique Identifier within the system. If necessary, use positions in the Unique Identifier to further differentiate ABAP development. Example: Position 4 could be a project indicator. 9-16Unique IdentifierX(up to 8)User defined Example:1.ZMRE001A 2.ZMREINVO 21. SCREENS Standard: The naming convention will ensure custom screens will not conflict with present or future SAP defined screensSee appropriate naming conventions to determine a program name. Screen numbers should begin with 9000 and increment by 10. Format: xxxx |Unique Identifier Identifies Custom Screen Position DescriptionValuesMeaning 1Custom Indicator 9Always 9 2-4Custom Number 000-999Custom Screen number. Screen numbers per program should be incremented by 10. Example:1.9000 2.9010 3.9020 22. Standard Text ID Standard Format: Z xxx |Unique Identifier Custom Indicator Position DescriptionValuesMeaning 1Custom Indicator ZAlways Z 2-4Unique Identifier 00-99, AA-ZZ Unique Identifier 23. Standard Text Name: Zx _ x(29) |Descriptive Identifier |always underscore |Functional Descriptor Custom Indicator Position DescriptionValuesMeaning 1Custom Indicator ZCustom Indicator 2Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 3Separator_always underscore 4-42Descriptive Identifier Up to 39 chars Standard text description Example:1.ZM_PO 2.ZS_SALE_ORDER 24. Styles Standard Format: Zx(7) | freely definable Custom Indicator Position DescriptionValuesMeaning 1Custom Indicator ZIdentifies as custom developed 2-8freely definable Up to 7User defined Example:1.ZBOLD 2.ZLINE 25. SUBROUTINE POOLS To make modularized subroutines available to other module pools, subroutines are grouped together in a separate ABAP/4 program. The use of Subroutine POOLS is not recommended. Subroutine Pools are becoming obsolete and are difficult to test. Modularization should be done using Function Modules only. Standard Format: SAPFZxxx | | | | | | |Unique Identifier |Functional Descriptor Identifier Position DescriptionValuesMeaning 1-5IdentifierSAPFZModule Pool for Subroutine 6Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 7-8Unique Identifier 00-ZZUniquely identifies Subroutine Example:1.SAPFZA00 2.SAPFZB00 26. Tables Standard Format: Each custom Table should begin with a Z followed by the application code to which it most closely fits. The remaining characters can be a description. Standard Format: Z xX(14) |Unique identifier |Functional Area Custom Indicator Position DescriptionValuesMeaning 1Custom IndicatorZCustom Indicator 2Functional Descriptor (A-Z)(see functional descriptor of program naming standard) 3-16Unique Identifier