Hi Priyanjala,

I haven't got that error yet and did a quick background search and you might already noticed that there's case with same error and they have sent the UPD with a script just to recompile Shop_Material_Alloc_API.Post_Installation_View if this error occurs in customer's environment.
Seems like this error occurring in many environments as there are more cases with the same error. But not for all customer’s applying UPD11

Bug 158151 itself has been created for the error and they have moved the "WHERE" clause outside and included "AND" inside the conditional tag for the VIEW Ctp_Supply_Demand. Since there's no database invalid objects have been created, issue may be related to the conditional compilation included in the view.

 SELECT
          part_no                                              part_no,
          contract                                             contract,
      .....
 FROM custord_supply_demand
 WHERE 1=1
 $IF Component_Order_SYS.INSTALLED  $THEN
 AND (order_no, line_no, rel_no, line_item_no, order_supply_demand_type ) NOT IN 
   (SELECT  order_no, line_no, rel_no, line_item_no, order_supply_demand_type
       FROM CUSTOMER_ORDER_LINE_DEMAND_OE
       WHERE rel_mtrl_planning = 'FALSE')
 $END;

Since this error is not occurring for every customers but foe some who have applied UPD11, are there any customization or extensions applied to your customer related to this view?

Best Regards,

Prabhavi.

Hi @Prabhavi Wijayaweera,

Thanking for your input !

Customer’s solution consists of MEE, IFS Global Extension and UK HMRC/CIS VAP.

But these extensions have no impact on the above recompilation/revalidation type error. 

Currently I’m awaiting feedback from the bug tracker. 

Cheers,

Priyanjala

Solution : 

This issue could be resolved with the Bug 159144 (Severity 2, UPD12). 

(It removes the conditional compilation introduced from the previous UPD11 bug 158151).

• Please note that currently this bug belongs to the category  of “Business Logic”. Since it wasn’t marked as of type “Deployment” or “Supplementary”, it wasn’t fetched to the quick reports during UPD Apply. This has been informed IFS PD and they’ll modify the  bug description related tags accordingly.
• As per the information received from the bug tracker, we can can safely proceed with the UPD without applying above correction, as the error resolves itself later in the process (Next UPD Level).
• Since it is a requirement to clear the _ERROR_install.log upon completion of the installation, we can apply the patch 159144 (Severity 2, UPD12) once it is tagged as type Deployment and Supplementary patch of 158151.

Cheers,

Priyanjala

Hi,

Following error appears in the “_ERROR_install.log” after installing UPD11 in customer’s DEV environment. However this doesn’t create any database invalid objects. (Customer’s environment updated from IFSAPP10 UPD10 to UPD11)

 

!!!Error deploying file SHPORD.module at 18-JUN-21 19:10:38
!!!Error occurred while executing Plsql Block
BEGIN
   Dbms_Output.Put_Line('Start running Shop_Material_Alloc_API.Post_Installation_View at ' || TO_CHAR(SYSDATE,'YYYY-MM-DD HH24:MI:SS'));
   Shop_Material_Alloc_API.Post_Installation_View;
   COMMIT;
END;
ORA-04045: errors during recompilation/revalidation of IFSAPP.SHOP_MATERIAL_ALLOC_API
ORA-06540: PL/SQL: compilation error
ORA-06508: PL/SQL: could not find program unit being called: "IFSAPP.SHOP_MATERIAL_ALLOC_API"
ORA-06512: at line 3

 

The deployment bug 158151 (Severity 3 , Deployment, UPD11) Of solution 290971 is included in the UPD. In the ShopMaterialAlloc.views, the changes from the bug has been applied correctly.

 

I would like to know if there’s a solution / work around to resolve recompilation/revalidation type of errors during installation.

 

Cheers,

Priyanjala

 

Solution : 

This issue could be resolved with the Bug 159144 (Severity 2, UPD12). 

(It removes the conditional compilation introduced from the previous UPD11 bug 158151).

 

 

• Please note that currently this bug belongs to the category  of “Business Logic”. Since it wasn’t marked as of type “Deployment” or “Supplementary”, it wasn’t fetched to the quick reports during UPD Apply. This has been informed IFS PD and they’ll modify the  bug description related tags accordingly.
• As per the information received from the bug tracker, we can can safely proceed with the UPD without applying above correction, as the error resolves itself later in the process (Next UPD Level).
• Since it is a requirement to clear the _ERROR_install.log upon completion of the installation, we can apply the patch 159144 (Severity 2, UPD12) once it is tagged as type Deployment and Supplementary patch of 158151.

 

Cheers,

Priyanjala

Hi Priyanjala, 

If Bug 159144 is required to resolve the issue with Bug 158151, shouldn’t it be added in the ‘Supplementary Bug’ section or ‘Bug Source Reference’ column of Bug 158151.

Best regards,
Nimaz

Hi @Nimaz Sheik ,

Currently we have informed IFS PD to mark the 159144 as a supplementary bug of 158151 and also to change its category as “Deployment”. Hope it will be done soon :)

Thanks,

Priyanjala