Dialog programs have which naming convention?

Dialog programs have which naming convention?
a) ZPBOxxx
b) SAPMZxxx
c) ZDIAxxx
d) ZPAIxxx
e) Zxxx

b) SAPMZxxx
Dialog program's name start with SAPMZ and the report's name with Z.

Similar Messages

  • Code Inspector - Naming conventions &mExtended Naming conventions for Progs

    Hi experts,
    I had a look into the naming conventions enforced by 'DEFAULT' variant of code inspector (SCI).
    the relevant categories are: "Naming Conventions", and "Extended Naming conventions for Programs" under "Programing conventions".
    in the "Extended Naming conventions for Programs" category, for functions, (applicable while calling the functions) it says,
    importing parameter : I[:type:]_
    exporting parameter : E[:type:]_
    changing parameter  : C[:type:]_
    tables parameter    : T[:type:]_
    but in the "naming conventions" category, for functions (applicable while defining the functions), it says,
    importing parameter : P_*
    exporting parameter : P_*
    changing parameter  : P_*
    tables parameter    : P_*
    I felt, while defining the function too, its better to have beginning with  I_, E_, C_ or T_ instead of P_
    is the 'DEFAULT' variant of code inspector is provided and recommended by SAP?
    for easier maintenance and clearer understanding, which naming convention is more suitable, or is there any official guidelines released by SAP for ABAP developers.
    appreciate the opinions from experienced abap developers.
    thanks,
    Madhu_1980

    Frank,
    Thanks for your answer.
    But what about Entity Objects, View Objects, View Links, and Application Modules.
    I would like my developers to have an easy way to name them and also find them via intellisense.
    So I was thinking in naming them the following way :
    Entity Objects :
    EO_Employee
    EO_Department
    View Objects :
    VO_Employees
    VO_Departments
    View Links :
    VL_EmployeesToDepartments
    Application Module :
    AM_HRService
    However the use of "_" is not so "Java naming oriented".
    So other alternatives would be:
    1. take the "_" :
    1.1 EOEmployee (I don't like the fact of having 3 capital letters together).
    1.2 EoEmployee (I don't like the fact of having Entity Object with a lowercase "o").
    2. Use the prefix at the end, but this way I loose the intellisense feature I want:
    ex: EmployeeEO
    Which naming approach are you using for big projects ?
    Thanks,
    Claudio.

  • Dialog programming, data being washed out in TAB Control

    Hi,
         i am working on dialog programming , in which i am using Table Control  for user input (data is not coming from database table) . everything is going well till assignment of data to internal table but when
    control goes to PBO by any means like pressing ENTER etc. then data being washed out.
    PROCESS BEFORE OUTPUT.
      MODULE TC_CONTROL.
      LOOP AT it_data
             INTO wa_data
             WITH CONTROL tc_control
             CURSOR tc_control-current_line.
        MODULE tc_control_get_lines.
      ENDLOOP.
    PROCESS AFTER INPUT.
    LOOP AT IT_DATA.
        CHAIN.
          FIELD WA_DATA-FREPS_N.
          FIELD wa_data-TOEPS_N.
          FIELD wa_data-PRCH_A.
          FIELD wa_data-SRVC_AMT .
          FIELD wa_data-ACCNT_C.
          FIELD wa_data-AMT_D.
          FIELD wa_data-NARR_X.
          FIELD wa_data-CRPRD_N.
          MODULE tc_control_modify ON CHAIN-REQUEST.
        ENDCHAIN.
      ENDLOOP.
    *Abap program
    MODULE TC_CONTROL OUTPUT.
    DESCRIBE TABLE it_data LINES tc_control-lines.
    ENDMODULE.                 " TC_CONTROL  OUTPUT
    CONTROLS: TC_CONTROL TYPE TABLEVIEW USING SCREEN 1000,
              TC_CONTROL1 TYPE TABLEVIEW USING SCREEN 1000.
    DATA:     G_TC_CONTROLS_LINES  LIKE SY-LOOPC,
              G_TC_CONTROLS_LINES1  LIKE SY-LOOPC.
    *&      Module  tc_control_get_lines  OUTPUT
          text
    MODULE tc_control_get_lines OUTPUT.
    g_tc_controls_lines = sy-loopc.
    move-corresponding it_data to wa_data.
    ENDMODULE.                 " tc_control_get_lines  OUTPUT
    MODULE tc_control_modify INPUT.
    move-corresponding wa_data to it_data.
    MODIFY it_data
        FROM wa_data
        INDEX tc_control-current_line.
    append it_data.
    clear it_data.
    ENDMODULE.                 " tc_control_modify  INPUT
    Please suggest me any clue.
    Thanks in advance
    vijay dwivedi

    Hi ,
    I have understood the problem.
    In your ABAP code replace all the occurrrences of wa_data  with the structurename.
    Use the TABLES keyword to declare the structure .That structure will be same as
    reference table of the table control .
    Here the structure is SPFLI.
    Check the bellow code , it will resolve the issue.
    ABAP code - -
    program  zsdn.
    tables spfli.  " Declare the structure
    data : it_data like table of spfli with header line,
    *wa_data TYPE spfli,  " commented
    w_i type i.
    *CONTROLS TC_CONTROL TYPE TABLEVIEW USING SCREEN 100.
    controls: tc_control type tableview using screen 1000,
    tc_control1 type tableview using screen 1000.
    data: g_tc_controls_lines like sy-loopc,
    g_tc_controls_lines1 like sy-loopc.
    module tc_control output.
      describe table it_data lines tc_control-lines.
    endmodule. " TC_CONTROL OUTPUT
    module tc_control_get_lines output.
      g_tc_controls_lines = sy-loopc.
      move-corresponding it_data to spfli.
    endmodule. " tc_control_get_lines OUTPUT
    module tc_control_modify input.
      move-corresponding spfli to it_data.
      modify it_data
      from spfli
      index tc_control-current_line.
      append it_data.
      clear it_data.
    endmodule. " tc_control_modify INPUT
    module status_0100 output.
      set pf-status 'STAT'.
    *  SET TITLEBAR 'xxx'.
    endmodule.                 " STATUS_0100  OUTPUT
    module user_command_0100 input.
      case sy-ucomm.
        when 'BACK' or 'EXIT' or 'CANCEL'.
          leave to screen 0.
      endcase.
    endmodule.                 " USER_COMMAND_0100  INPUT
    *&      Module  POPLATE_TABLE  OUTPUT
    *       text
    module poplate_table output.
      if it_data is initial.
        select * from spfli into table it_data.
      endif.
    endmodule.                 " POPLATE_TABLE  OUTPUT
    Screen code (Scr no 1000) - -
    PROCESS BEFORE OUTPUT.
      MODULE status_0100.
      MODULE poplate_table.
      MODULE tc_control.
      LOOP AT it_data WITH CONTROL tc_control CURSOR w_i.
        MODULE tc_control_get_lines.
      ENDLOOP.
    PROCESS AFTER INPUT.
      MODULE user_command_0100.
      LOOP AT it_data.
        MODULE tc_control_modify ON CHAIN-REQUEST.
    *    ENDCHAIN.
      ENDLOOP.
    Regards
    Pinaki

  • Hi experts,    dialog program   no solution from forum

    hi all
    i would like to know if there any program other than alv or oops, where icon are used ( means how to bring functionality of icons) for example, sum, subtotal, filter, xxl, spreadsheet, word procesing doc, etc.
    i have developed dialog program in which i have above icons and now i want to have fuctionality of the above icons when they are clicked,( try to understand i want code to run fuctionality in dialogue prog and not how to display icons ).
    thanx
    rocky

    Hi,
    have a look to transactions LIBS BIBS
    Fred

  • XML Schema Component Naming Convention

    Is there a naming convention when you create an XML Schema? For example,
    When you create a Type component, then the first letter of its name should be upper case ie. BMW, Honda, AutombileEngine ...etc.
    When you create an Element component, then the first letter of its name is lowercase ie. engine, car, guestCar ..etc.
    Do we have such naming convention for XML Schema?
    Thanks

    I am giving this from my document which i prepared for one of my customer
    2     General Guidelines for design of XML schema documents
    The representation of data in an XML format will be a key component of development within SOA. Therefore, the design and development of XML schemas should be as rigorous an activity as designing and developing code or designing database schemas. As such, when creating an XML schema you should be working within a development process and working to a set of design guidelines and coding standards (when writing the XML schema file). XML schemas should be reviewed for accuracy and compliance with guidelines and standards. Each of the requirements in the list below is a general requirement for all XML schemas to be deployed in the SOA environment.
    •     Understandable: XML schemas should be clear, consistent and unambiguous. They should contain human readable documentation and, where appropriate, links to requirements or design documents.
    •     Semantically Complete: An XML schema should define, for one or more target XML documents, each and every element and attribute that is understood by your solution when processing target documents.
    •     Constraining: XML schemas are used as contracts between both publisher and consumer. As such, they must be able to be validated as concisely as possible. When designing an XML schema constraints should be identified for the values for all the elements and attributes that the application uses and relies on to the set of values that the application can handle. A valid document should imply valid data within the limits of what can be specified by the XML Schema language.
    •     Uniquely identifiable: XML schemas should import and include other XML schema files rather than duplicating types and elements locally.
    •     Reusable: XML schemas should be specified in such a way that types and other XML schemas can leverage elements. Every type defined in an XML schema that is the content type of an attribute or an element should be defined globally (i.e., at the top level in the Schema). Types that are defined globally can be reused in other XML schemas. Schemas should be separated into logical sections which can be included into the main schema file.
    •     Extensible: Schemas should be designed to be extensible—that is, new elements and attributes can be inserted throughout the document.
    Every schema should use at least two namespaces – the targetNamespace and the XML Schema (http://www.w3.org/2001/XMLSchema) namespace.
    Create typed elements that can be referred to by object elements:
    Example:
    <?xml version="1.0"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://www.soa.com"
    xmlns="http://www.soai.com"
    elementFormDefault="qualified">
    <xsd:complexType name="PersonType">
    <xsd:sequence>
    <xsd:element name="Name" type="xsd:string"/>
    <xsd:element name="SSN" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    <?xml version="1.0"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://www.company.org"
    xmlns="http://www.company.org"
    elementFormDefault="qualified">
    <xsd:include schemaLocation="Person.xsd"/>
    <xsd:include schemaLocation="Product.xsd"/>
    <xsd:element name="Company">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="Person" type="PersonType" maxOccurs="unbounded"/>
    <xsd:element name="Product" type="ProductType" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    •     Recognize that with XML Schemas you will not be able to express all your business rules.
    o     Express those business rules using XSLT.
    •     Use type definitions
    Elements vs Attributes
    •     Use attributes for metadata about the parent element.
    •     Use attributes for data that is semantically tied to the enclosing element.
    •     Use elements for data that have a meaning separate from the enclosing element.
    •     Use attributes when the value will be frequently present in order to improve the human readable form of an XML instance document or reduce its size.
    •     If you don't know which to use, then use the element form (which is more extensible).
    2.1.1     Element, Types and attribute names
    Create a descriptive name without it being excessively long (no more than 32 characters).
    Elements and Types should be named in Upper Camel Case. Upper Camel Case capitalizes the first character of each word and compounds the name (remove all whitespace).
    Attributes should be named in Lower Camel Case. Lower Camel Case capitalizes the first character of each word except the first word and compounds the name.
    Simple and Complex type names
    XML Schema has separate symbol space for elements and types so they may have the same name. The best practice is to append the word "Type" to all simple and complex type names to aid in human readability and comprehension.
    Element, attribute and type names MUST be in a singular form unless the concept itself is plural.
    2.1.1.1     XML Schema versioning
    Use major and minor version tracking:
    Major—completely different structure and semantics, most likely not backward compatible
    Minor—backward compatible changes which introduce new features without removing or changing the semantics of existing structures
    2.1.1.2     Indication of version in the namespace URI
    Specify a namespace URI as follows
    http://$domain/$groupSpecifier/$namespaceTitle/$version
    The groupSpecifier can include several levels, e.g., /www.soa.com/SOA/USA/.
    An example namespace could be:
    http://www.soa.com/SOA/order/2

  • Hi all   dialog program   experts no solution coming

    hi all
    i would like to know if there any program where coding for below icon is available (not in alv or oops), where icon are used ( means how to bring functionality of icons) for example, sum, subtotal, filter, xxl, spreadsheet, word procesing doc, etc.
    i have developed dialog program in which i have above icons and now i want to have fuctionality of the above icons when they are clicked,( try to understand i want code to run fuctionality of icons in dialogue prog and not how to display icons ).
    thanx
    rocky

    hi all
    i would like to know if there any program where coding for below icon is available (not in alv or oops), where icon are used ( means how to bring functionality of icons) for example, sum, subtotal, filter, xxl, spreadsheet, word procesing doc, etc.
    i have developed dialog program in which i have above icons and now i want to have fuctionality of the above icons when they are clicked,( try to understand i want code to run fuctionality of icons in dialogue prog and not how to display icons ).
    thanx
    rocky

  • Flatfile conversion with output file has a NAMING CONVENTION

    Dear SAP experts,
    I need some advise regarding my scenario.
    I am converting a message into flatfile. (customized .csv)
    But, the output .csv flatfile must have a naming convention.
    E.g.    Globus_20071020   (Customer name_YearMonthDate)
    Can somebody give me ideas/inputs on what will I configure in File Receiver (FCC) in order to have an output file having a naming convention indicated above.
    Or do i need additional configurations?
    Please advise.
    Thank you very much in advance.
    Fred

    Hi,
    You could pass this kind of File name from mapping at runtime or
    You could use the variable substitutions to create the fiel neame as per naming convention as adding date .
    With reference to Variables youcould set file name as Globus_%payload.<Date>%
    Pass the value in date field of payload 
    Refer
    Variable Substitution
    How to use Variable substituion
    /people/sameer.shadab/blog/2005/09/23/an-interesting-usage-of-variable-substitution-in-xi
    /people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
    how to use attributes in variable substitution???:(
    Dynamic file name
    /people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i --> Dynamic File Name using XI 3.0 SP12 Part – I
    /people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii --> Dynamic file name(XSLT Mapping with Java Enhancement) using XI 3.0 SP12 Part -II
    Dynamic File name in File adapter
    /people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
    1. In the sender file adapter , select Adapter Specific Attributes --> FileName.
    2. Use the code in this link to read the filename inside a UDF in your mapping.
    DynamicConfiguration conf = (DynamicConfiguration) container
    .getTransformationParameters()
    .get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create(
    “http://sap.com/xi/XI/System/File”,
    “FileName”);
    String filename = conf.get(key);
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/03612cdecc6e76e10000000a422035/content.htm
    Thanks
    Swarup

  • Naming Convention in IP

    Hi All,
    Request you to please share if you have any naming convention document for IP Projects.
    Regards,
    Deepti

    Hi Deepti,
    we have the following naming convention:
    Aggregation Level similar to Cube:
    e.g. Cube = ZPP_RC01 --> PP for Production Planning; RC for Real-time Cube and 01 just a sequential number
    than the Aggregation Level will become ZPP_AL01 --> AL for Aggregation Level
    Filter:
    starting with AL name and just a sequential number: e.g. ZPP_AL01_F1
    Planning function:
    e.g. ZPF_01 ... PF for Planning Function and sequential number
    Planning Sequence
    e.g. ZPS_01 ... PS for Planning Sequence and sequential number
    Best greetings,
    Peggy

  • Implement a technical naming convention for queries depending on user

    Hello,
    I'd like to implement a technical naming convention for queries depending on the user, because I want to make sure that the users are taking care of the naming conventions.
    For example a user defines a query and would like to save this query.
    During the save process he should only have the possibility to save the query with the name C_Name-of-Infoprovider_Text.
    The C should be unchageable for the user.
    The Name-of-Infoprovider should set automatically (if possible).
    The Text could be defined by the user.
    Another user would have this naming convention: X_Name-of-Infoprovider_Text
    Is there a possibility to implement such a function? (or just a part of this)
    Thank you.

    Thank you for your answer!
    Your answer helped me to implement a part of the naming conventions.
    Maybe some as an idea to implement the rest of the naming convention.
    --> Technical query name depending on technical name of the InfoProvider.
    Has anyone an idea?

  • Do you have suggestions for naming conventions within AIF?

    Hi Folks!
    Being new to AIF I'm currently in the information gathering phase for myself and colleagues as we are starting to think about implementing interfaces with the help of this toolbox. I already found and read (or at least skimmed!) through various of your discussions as well as the very helpful blog posts from Verena, Michal and Andrey.
    One of the first things we want to do - before we really get started for real - is to come up with some feasible naming conventions for the various customizable bits and pieces like
    Namespace
    Interface Name
    SAP Data Structure (if applicable?)
    We also have some general questions:
    Does it make sense to prepare for one namespace per SAP-module or is it better to have just one and do the separation on the Interface name "level"?
    Is it preferred - even though SAP doesn't seem to enforce this - to start our own names with a "Z"?
    Searching SCN for "naming convention aif" didn't find anything related and while scrolling through the discussion forum I also didn't see any titles which might go into this direction. In order for us to not re-invent the wheel - or to start off in the wrong direction - I'm hoping to get some helpful pointers from you.
    Thanks much for any feedback you have!
    Cheers from Germany
    Baerbel

    Hi Bärbel,
    Your question is very good. We had the same and decided for following own approach:
    Namespace
    A Namespace is a concatenation of business process and SAP module, e.g. O2C_AR, P2P_AP, P2P_MM, R2R_GL.
    We have one global namespace for global objects as checks on currency code, date format value mappings, etc.
    Interface NameEvery interface has its own name. To be honest for inbound interface the names are more a user friendly description, for outbound we follow a little rule that they start with OUT_.
    SAP Data Structure (if applicable?)
    We try to do the structure mapping in the middle-ware and AIF is only responsible for the functional mappings.
    The root structure name is different between raw data and SAP data. But the sub structure and field names are equal. Because of this we can use the move corresponding fields or in some only monitoring interfaces even move corresponding structures.
    We also have some general questions:
    Does it make sense to prepare for one namespace per SAP-module or is it better to have just one and do the separation on the Interface name "level"?Because AIF support and business users differ in different business processes we separated in these processes and modules. In addition the recipients groups are similar to the name spaces.
    Is it preferred - even though SAP doesn't seem to enforce this - to start our own names with a "Z"?For namespaces (six characters) and interface names (10 characters) we don’t.
    Best wishes
    Christoph

  • SAP naming conventions: customer DDIC objects, ABAP programming

    SAP Note 16466 Customer name range for SAP objects contains the SAP naming conventions for customer DDIC objects. Rule of thumb is that the names reserved for customer objects start with 'Y' or 'Z'. However, this note contains the naming convention for DDIC objects only.
    ABAP Code Inspector (transaction SCI) contains the following naming convention for ABAP programming:
    - Global types: T_
    - Global constants: C_
    - Global data: gv_
    - Global field-symbols: FS_
    - Global parameters: P_
    - Global select-options: S_
    - Global field-groups: FS_
    - Local types: LT_
    - Local constants: LC_
    - Local data: v_
    - Local field-symbols: LFS_
    This is the only place I know for ABAP programming naming convention. Does SAP has somewhere else any additional naming convention guidelines for ABAP programming?
    Thanks in advance for your help.
    Regards,
    Jarmo Tuominen

    Naming convention guidelines for ABAP programming is available in here: [Manage Successful Customer Development|https://websmp206.sap-ag.de/~sapidb/011000358700004444532001E].
    Naming Data Types and Objects
    The names of data types and objects have the form: <Classifier>_<Data type>_<Descriptor>.
    The names of data types and objects have up to 30 characters.
    Exceptions: names of input parameters and select options have up to 8 characters, and <Data type> and _ are omitted.
    First component: Classifier
    T Data type
    C  Constant
    G  Global data object
    L  Local data object
    FS Field symbol
    P  Input parameter
    S  Select option
    P  Formal parameter in form
    FM Formal parameter in function
    Second component: Data Type
    <t> Elementary data type, optionally followed by length
    C<n> Type C of length <n>
    N<l> Type N of length <n>
    X<l> Type X of length <n>
    D    Type D
    T    Type T
    I    Type I
    P<d> Type P with <d> decimals
    F    Type F
    WA  Work area
    IT  Internal table
    Third component: Descriptor
    Use meaningful English names. Later, your code may be maintained or analyzed by a programmer or support consultant who is not familiar with another language.
    Use only alphanumeric characters (A-Z and 0-9) and separate words with underscores (_). Hyphens are reserved for separating components in structured data types.
    Examples:
    G_I_COUNTER (global counter)
    T_IT_BOOKING_LIST (type for list of bookings)
    G_IT_BOOKINGS (global internal table of bookings)
    PSMOKER (input parameter for smoker flag: note omission of data type and _ for brevity)
    Edited by: Jarmo Tuominen on Feb 21, 2011 2:13 PM

  • Draft forms in Queue do not have naming convention

    When a form is saved as a draft, there isn't any naming conventions such as the Task Display Name, Process #, or Task #, etc. Is it possible to include some type of naming distinction in the draft forms?
    We have multiple forms in Draft and when I need to open a specific form, I must open each form to find the specific form.

    Search Templates should help here : LiveCycle ES2.5 * LiveCycle ES2.5 Administration Help
    It shows the tasks saved in Draft as well :
    Thanks,
    Wasil

  • Hello. I have iPod 1st generation. It's on recall program. Which kind iPod I receive for replacing?

    Hello. I have iPod 1st generation. It's on recall program. Which kind iPod I receive for replacing?

    Same model, with same capacity. Only certain serial numbers qualify. If your iPod is registerred, you should have received an email from Apple.

  • Implement F4 Value-Request Functionality in Dialog Programming

    Hi. Apologies in advance if this is the wrong forum.
    I'm on R/3 4.6c.
    What is the best way to implement this:
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR xxxx-low.
    in a dialog program?
    I have my selection screen defined in my TOP include, but since dialog programs don't support report events I am not sure what to do.
    Thank you for any assistance you could provide.
    Best Regards,
    Brett

    make a new include like
    include progname_screen_1001. at the top of your program.
    goto include.
    write the code below in your include.
    SELECTION-SCREEN BEGIN OF SCREEN 1001.
    write here your selection options and parameters.
    also but here the code you want:
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR xxxx-low.
    SELECTION-SCREEN END OF SCREEN 1001.
    call the screen from anywhere:
    call screen 1001.
    if you want the selection-screen as subscreen than write
    SELECTION-SCREEN BEGIN OF SCREEN 1001 as subscreen .
    write here your selection options and parameters.
    also but here the code you want:
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR xxxx-low.
    SELECTION-SCREEN END OF SCREEN 1001.
    when calling it
    write it to PBO of your screen in which you but an subscreen area named subsel.
    CALL SUBSCREEN SUBSEL INCLUDING 'PROGRAMNAME' '1001'.

  • How to create new check for SELECT* , Naming conventions etc..

    Hi all,
       I would like have a solution for the below checks are possible or not in ABAP - CODE INSPECTOR. If possible can you please give me the solution..
    a). Performance checks i.e, SELECT* , LOOP without field strings, FOR ALL ENTRIES IN SELECT STATEMENT.
    b). Custom naming conventions.
    c). to check if further modularization can be done in the program,
    d). also the coding standards.
    PLEASE help me , i am struck with it for long time in getting the solution...

    > a). Performance checks i.e, SELECT* , LOOP without field strings, FOR ALL ENTRIES IN SELECT STATEMENT.
    > b). Custom naming conventions.
    > c). to check if further modularization can be done in the program,
    > d). also the coding standards.
    the code inspector allows the creation of new checks, you should consult the documentation how to do it.
    The main problem of the code inspector are hits, which are actually no problem. And I think this is a problem with your checks:
    + SELECT*  this is no performance problem, only in cases when the table is really wide then a field list makes sense, i.e your check
       will find a lot of false hits
    + LOOP without field strings  ... you mean fs =field symbols, same as with SELECT *
    + FOR ALL ENTRIES IN SELECT STATEMENT   ???? FOR ALL ENTRIES is fine
    + Custom naming conventions  ... hmmm be more precise, I think it can be hard
    + to check if further modularization can be done in the program,
        before you want to program can you please explain how you check manually .... I would be interested
    +  also the coding standards.   .... what is that?

Maybe you are looking for