【正文】 ntifierCustom IndicatorPosition Description Values Meaning1 Custom IndicatorZ Always Z24 Unique Identifier0099, AAZZUnique Identifier29 / 5623. Standard Text Name:Z x _ x(29)| | | Descriptive Identifier| | always underscore| Functional DescriptorCustom IndicatorPosition Description Values Meaning1 Custom IndicatorZ Custom Indicator2 Functional Descriptor(AZ) (see functional descriptor of program naming standard)3 Separator _ always underscore442 Descriptive IdentifierUp to 39 charsStandard text descriptionExample: 1. ZM_PO2. ZS_SALE_ORDER30 / 5624. StylesStandard Format:Z x(7)| freely definableCustom IndicatorPosition Description Values Meaning1 Custom IndicatorZ Identifies as custom developed28 freely definableUp to 7 User definedExample: 1. ZBOLD2. ZLINE31 / 5625. SUBROUTINE POOLSTo 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 remended. Subroutine Pools are being obsolete and are difficult to test. Modularization should be done using Function Modules only. Standard Format:SAPFZ x xx||||||| | Unique Identifier| Functional DescriptorIdentifierPosition Description Values Meaning15 Identifier SAPFZ Module Pool for Subroutine6 Functional Descriptor(AZ) (see functional descriptor of program naming standard)78 Unique Identifier00ZZ Uniquely identifies SubroutineExample: 1. SAPFZA002. SAPFZB0032 / 5626. TablesStandard 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 x X(14)| | Unique identifier| Functional AreaCustom IndicatorPosition Description Values Meaning1 Custom Indicator Z Custom Indicator2 Functional Descriptor(AZ) (see functional descriptor of program naming standard)316 Unique Identifier X(14) Unique DescriptionExample: 1. ZFSALE2. ZS00233 / 5627. Table FieldsStandards: Where possible, use the same name as the data element associated with this field. If multiple fields in the table use the same data element, name these fields in a meaningful manner.Where possible, use an existing SAP data element.Do not use spaces or special characters in a table field name.Format: X (10)Position Description Values Meaning110 Identifier X(10) Description identifying fieldsExample: 1. CUSTNAME2. CUSTNUM34 / 5628. Table GroupStandard Format:Type Pools are defined with transaction SE11, begin with a Z and are 5 characters long. TYPEPOOL should be associated with a particular functional area.Z x xxx| | Unique identifier| Functional AreaCustom IndicatorPosition Description Values Meaning1 Custom Indicator Z Custom Indicator2 Functional Descriptor(AZ) (see functional descriptor of program naming standard)35 Unique Identifier 0Z Unique identifierExample: 1. ZF0012. ZS00235 / 5629. Table IndexStandards: Begin with a Z and have a maximum length of 3 characters. Format: Zxx Position Description Values Meaning1 Identifier Z Always ‘Z’23 Number 0 9 Unique identifierExample: 1. Z012. Z0236 / 5630. Table StructureStandard Format:Z x x(8)| | Unique identifier| Functional AreaCustom IndicatorPosition Description Values Meaning1 Custom Indicator Z Custom Indicator2 Functional Descriptor(AZ) (see functional descriptor of program naming standard)34 Unique Identifier X(8) Unique DescriptionExample: 1. ZFSALE2. ZS00237 / 5631. Table ViewsStandard Format:Custom Views should begin with a Z followed by the View Type and a separator. The remaining fields should be used to identify the primary table for the view.Z x _ X(7)| | | Primary Table name| | Separator| View TypeCustom View IdentifierPosition Description Values Meaning1 Custom View IdentifierZ Custom created View2 View Type H Help ViewD Database ViewP Projection ViewS Structure ViewC Customizing View3 Separator _ Underscore410 Primary Table NameX(7) Primary Table used in the ViewExample: 1. ZD_CUST2. ZD_ZMAST38 / 5632. Text ElementsAlways attach a text symbol to a text element. This will ensure easy maintenance of multi language conversions without changing program source code.All text elements must be soft coded, without exception.All text elements must be in English.39 / 5633. TRANSACTION CODESStandard Format:Starting the transaction code with a Z followed by the application type and a numeric sequence number insures that the transaction code will be unique and won’t interfere with existing SAP code.Format: Z x (up to 8 chars)| | || | User defined| Functional DescriptorCustom View IdentifierPosition Description Values Meaning1 Type Z Custom Table2 Functional Descriptor(AZ) (see functional descriptor of program naming standard)310 Unique IdentifierUp to 10 charsUser defined Example: 1. ZF012. ZU013. ZUPAYMENT40 / 5634. VARIANTSAP R/3 Requirements:A Variant must be unique for an ABAP report and may be up to 14 characters long. 41 / 5635. Work IDThis is a unique identifier to define work unit. A custom transaction ZU02 has been created to maintain these number.Format:x yyyy z aaaaPosition Description Values Meaning1 Region A, E, P, G A – AmericaE – EuropeP – PacificG – Global 25 Company Code4 chars 9999 – Corporateuse one of the pany code6 Type R, I, C, E, FR – ReportI – InterfaceC – ConversionE – EnhancementF – Form7 Flow I, O, B, N I inboundO – outboundB bothN – no。Global ABAP Naming StandardsGlobal SAP Development Architecture 1 / 56Document Revision History2 / 56TABLE OF CONTENTS1. AUTHORIZAT