Monday, February 25, 2013

Debugging Configurator Batch Validation

When you do Book Order in Order Management, it will validate line Configuration using batch validation API. This process causes issues at times and the front end error message simply says like "Configuration validation resulted in errors." without any additional details. As this is background process, it makes debugging difficult.

Here are few important steps to debug Configurator batch validation error:

1) Generate OM debug log for batch validation process. That should reveal some detail about what is happening.

2) Generate sql trace for batch validation process. Useful in certain cases.

3) Check AltBatchValidateUrl parameter from cz_db_settings.

4) Check if above URL is reachable by Database using following script
  config_messages cz_cf_api.CFG_OUTPUT_PIECES ;
  finalURL VARCHAR2(500);
  finalURL        := '';
  config_messages := UTL_HTTP.request_pieces(url => FinalURL);
  dbms_output.put_line('message count = ' || config_messages.COUNT);
  FOR i IN config_messages.FIRST .. config_messages.LAST
    MESSAGE := config_messages(i);
    dbms_output.put_line('Message ' || i || ' : ' || MESSAGE);

5) Check if there any additional logs written in Configurator batch validation
select * from cz_db_logs 
where logtime is not null
and loguser = 'batchValidate'
order by logtime desc;

6) Check if you are using model based routing and try disabling it and see if it works.

7) If you are using https url for batch validation, you need check if Wallet setup is done correctly.


  1. I also tell my team members to spend qaulity time doing analysis of the work they do. Do not spend the entire day in just doing testing.
    Spending everyday sometime on Analysis will help them
    to move in the right direction in the work and also helps them to see in a bigger and broader perspective of the work.
    Finally, just spend good amount of time in planning, reviews and analysis, the execution will be done like in no time.

  2. I really like examining and also following ones write-up when i locate them incredibly beneficial and also fascinating.
    That write-up is usually just as beneficial along with fascinating.Verification and Validation both are independent type of testing. Obviously,
    If we look both of these activities as a whole, we can also call it testing.

    software validation

  3. In software project management, software testing, and software engineering,
    verification and validation (V&V) is the process of checking that a software system meets specifications and that it fulfills its intended purpose.
    It may also be referred to as software quality control.

    software validation

  4. Verification and validation techniques applied throughout the development process enable you to find errors before they can derail your project. they are involved in lot of process improvements which will actually help the clients to deliver best software.

    software validation