/SAPCND/CL_CUST_CONS_CHECK_SRV - Checks for CT customizing objects

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Functionality

This class has methods which are used for checking the customizing consistency of condition techniqueobjects like global field catalog, application field catalog, usage field catalog, condition tablesand condition maintenance groups. Error messages within the check methods are filled as BAPI messages and returned by the export parameter ET_BAPIRET.

ATTRIBUTES

• MR_REF_USG: Private Instance Attribute - Reference to the BAdI /SAPCND/IF_EX_TST_UNIT_USG.

• MV_BAPI_FLAG: Private Instance Attribute - Boolean value that marks if the method is run as standalone (using et_bapiret).

• MT_BAPIRET: Public Instance Attribute - Contains error messages (BAPI messages).

• MT_APPLNS: Private Instance Attribute - Contains the applications that are relevant for the checks. May depend on the user's entry, when the report is executed directly (not as unit test).

• MT_USAGES: Private Instance Attribute - Contains the usages that are relevant for the checks. May depend on the user's entry, when the report is executed directly (not as unit test).

• SV_GENERATION_EXECUTED: Protected Static Attribute - Boolean value that indicates, if the application specific objects that are generated on the fly are created.

METHODS

The public methods in this class are:

• ,,GLOBAL_FIELD_CATALOG_CHECK

This method checks the customizing consistency related to the Global Field Catalog. The following checks are performed in this method:

• Check if every rollname from the Global Field Catalog of Field Names (/SAPCND/T681FF) is also present in the Global Field Catalog (/SAPCND/T681F).

• Check if every fieldname from the Relationships Between Fields in Field Catalog table (/SAPCND/T681FR) is also present in the Global Field Catalog of Field Names (/SAPCND/T681FF).

• Check if every rollname from the Dependencies for Field Checks and Field Transports table (/SAPCND/T681FD) is also present in the Global Field Catalog (/SAPCND/T681F).

• ,,USAGE_FIELD_CATALOG_CHECK

This method checks the customizing consistency related to the Usage Field Catalog. The following checks are performed in this method:

• Check if every fieldname from the Fields for Usage table (/SAPCND/T681FV) is also present in the Global Field Catalog of Field Names (/SAPCND/T681FF).

• Check if every fieldname from the Presorted Usage-Specific Fields table (according to dependency # /SAPCND/T688FV) is also present in the Global Field Catalog of Field Names (/SAPCND/T681FF).

• ,, APPL_FIELD_CATALOG_CHECK

This method checks the customizing consistency related to the Application Field Catalog. The following checks are performed in this method:

• Check if every fieldname from the Application Field Catalog (/SAPCND/T681FA) is also present in the Global Field Catalog of Field Names (/SAPCND/T681FF).

• Check if every fieldname from the Sorted Field Catalog (according to dependency # /SAPCND/T688F) is also present in the Global Field Catalog of Field Names (/SAPCND/T681FF).

• Check if every fieldname from the Application Field Catalog (/SAPCND/T681FA) is also present in the DDIC runtime of working set (internal & external application working sets).

• Check if the depends_on field position from the Dependencies for Field Checks and Field Transports table (/SAPCND/T681FD) is less than the rollname field position.

• ,,CONDITION_TABLE_CONS_CHECK

This method checks the customizing consistency related to Condition tables. The checks are performed in the two methods T681_CONS_CHECK and T681E_CONS_CHECK.

T681_CONS_CHECK: Check consistency of Condition Table Structure (/SAPCND/T681):

• Check in the table T000 that the system is a P (Production), T (Test) or D (Demo) System. Otherwise skip all checks in T681_CONS_CHECK.

• Check if every active condition table in /SAPCND/T681 has an entry present in /SAPCND/T688c (Fields from Condition Tables Sorted Acc. To Dependency).

• Check if there is an active access report for the condition table.

• Check if the latest version of the access report is available for the condition table.

,,

T681E_CONS_CHECK: Check consistency of Condition Table Structure at field level (/SAPCND/T681E):

• Check if every active condition table in /SAPCND/T681E has an entry present in /SAPCND/T688c (Fields from Condition Tables Sorted Acc. To Dependency).

• Check for every active condition table in /SAPCND/T681E, if all the fields are present in the DDIC runtime of working set.

• Check for every active condition table in /SAPCND/T681E, if all the fields are present in the condition table access view.

• ,, COND_MAINT_GROUP_CONS_CHECK

This method checks the customizing consistency related to Condition Maintenance Groups. The following checks are performed in this method:

• Check if all condition maintenance groups have at least one group item.

• Check if all the condition tables in the group are active.

• Check if all condition types used in condition maintenance groups exist (in the application).

• Check if the condition tables in the condition maintenance groups are present in the access sequence of the condition types in the group.

• Check if every field from the condition table in the condition maintenance group is present in the DDIC runtime of working set (internal & external group working sets).

• ,,COND_TYPE_CHECK

This method checks the customizing consistency related to Condition Types.

In case the usage stores the condition types details in special tables and not in the generic conditiontechnique table (/SAPCND/T685), then additional consistency checks for the condition types are performed in the BAdI implementation for the usage. For details please refer to theInterface documentation.

The following checks are performed in this method:

• Check if scales are only used, when the usage is scales-relevant.

• Check if the access sequence assigned to the condition type is present in the Condition Access Sequence table (/SAPCND/T682).

• Check if the access timestamp field is filled for non-manual condition types (JAVA Determination Engine). If an access date exists, check if it is marked as an access time stamp.

• ,,ACCESS_SEQ_CHECK

This method checks the customizing consistency related to Access Sequences. The following checks are performed in this method:

• Check if the access sequence has at least one step (/SAPCND/T682).

• Check if the condition table used in the sequence exists.

• Check if the condition table used is active.

• Check if the number of field assignments is equal to the number of key fields and data fields of the table, and check if the keys are the same.

• Check for key fields, if at least the communication (source) structure or the constant is filled.

• Check if the field assignment is mapped to the communication structure.

• Check if the formula used in the acces sequence is present in the userexit tables.

• ,,PROCEDURE_CHECK

This method checks the customizing consistency related to Procedures. Procedures include Pricing Procedures, Free Goods Determination Procedures and Product Substitution Procedure.

In case the usage stores the procedure details in special tables and not in the generic condition techniquetable (/SAPCND/CTLIST), then additional consistency checks for the procedure are performed in the BAdI implementation for the usage. For details please refer to theInterface documentation.

The following checks are performed in this method:

• Check if there is at least one step for the procedure in the steps table (/SAPCND/CTLISTI).

• Check if the condition types for the procedure are present in the Condition Types table (/SAPCND/T685).

• ,,ADDN_OBJS_CHECK

This method provides further checks for the customizing consistency. These checks are mainly made within a BAdI implementation for the corresponding usages.

For details please refer to theInterface documentation.

The following checks are performed in this method:

• Check for userexit consistency (delegated to JAVA).

The private method in this class is:

• ,,SELECT_DB_OBJECTS_SRV

This method is used to select the table entries in database tables. This method is used as a service method for the other methods. above The following are the import and export parameters of this method:

Import Parameters

• IV_DERIVED_OBJECT (Optional)

• IV_BASE_OBJECT

Export Parameters

• ET_DERIVED_OBJECT

• ET_BASE_OBJECT

• ET_BAPIRET

For selecting entries only from one DB table only the IV_BASE_OBJECT parameter is filled.

TXBHW - Original Tax Base Amount in Local Currency   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.


Length: 11968 Date: 20120526 Time: 071638     triton ( 272 ms )