扬子石化ABAP Naming Convention2.0.docVIP

Prepared by : Rachel Yu Date : 2002-2-21 Reviewed by : Date : Approved by : Date : Approved by : Date : Approved by : Date : Approved by : Date : Approved by : Date : Approved by : Date : Change Control 版本 日期 描述 1.0 Feb 21, 2002 Initial Draft 2.0 June 13, 2003  Table of Contents 1. Introduction 5 1.1. Purpose 5 1.2. Intended Audience 5 2. General 5 3. Naming Standard 7 3.1. ABAP Programs 7 3.2. Authorization Group 7 3.3. Data Elements, Domains 7 3.4. Lock Objects 7 3.5. Match Code 8 3.6. Tables/Structure 8 3.7. Table Fields 8 3.8. Function Groups 8 3.9. Function Module 9 3.10. Enhancement Projects 9 3.11. Message Class 9 3.12. Message Number 10 3.13. SAP Script 10 3.14. Transaction Code 10 4. Coding Standard 11 4.1. Forms 11 4.2. Text Element 11 4.3. Constants 11 4.4. Parameters 11 4.5. Select-Options 11 4.6. Radio buttons 12 4.7. Checkboxes 12 4.8. Global Variables 12 4.9. Internal Tables 12 4.10. Local Variables 12 4.11. Working Areas 12  Introduction Purpose The purpose of this document is to provide naming standard of SAP ABAP development units for Sinopec ERP Project. Intended Audience The information in this document is relevant for individuals who are working as ABAP programmers for Sinopec project . General The name of a SAP object is crucial to allow its identification from thousands of objects. Also in a shared development environment separation of object name space must take place so all projects can work alongside each other without overwriting each other’s efforts. In the naming standards below, the following conventions are followed: Table 2.1 Standards components of naming standard FUNC character code identifying functional area. Possible values are: A – Asset Management B – Basis F – Financial Accounting G – General Ledger H – Human Resource Planning I – Maintenance K – Cost Accounting L – Warehouse Management M – Material Management O – Project Syste