Skip to main content
Question

Imported custom projections cannot be published

  • February 11, 2025
  • 3 replies
  • 143 views
S
Do Gooder (Customer)
Forum|alt.badge.img+2

Hi,

I found when trying to publish an imported custom projection (from ACP or item)  it gives an error when all the required other configurations in place.  This is in 24R2 3

“Database error occurred. Contact administrator.
Error details: [{"code":4050,"message":"ORA-04050: invalid or missing procedure, function, or package name"}] “.

When looking into further it is found that entry is not getting added into the table custom_projection_tab when importing hence it fails when publishing.

Any workaround for this?

 

Thanks,

Best Regards,

Methshika

 

 

 

 

I

3 replies

K
Hero (Partner)
Forum|alt.badge.img+10
  • kvbe
  • Hero (Partner)
  • February 11, 2025

​@SYBMETHSHIKA  I think this is a bug. I faced something similar. Seems the ACP import is not that reliable, For us this was on 24R2.SU2 

 
S
Do Gooder (Customer)
Forum|alt.badge.img+2
  • SYBMETHSHIKA
  • Author
  • Do Gooder (Customer)
  • February 11, 2025

It seems it is need to have related custom entities and corresponding custom projections together in the same ACP. Otherwise it is not generating the item xmls correctly when exporting. I mean there are two items exported as “CustomProjection-xxxx” and “ProjectionConfiguration-xxxxx” for a custom projection. If you only add the custom projections into the ACP then it is not generating the item “CustomProjection-xxxx”. 

 

So, the workaround is to add custom entities and custom projection together in an ACP.

Exporting the custom projection as a single item also seems not working. It only generates the item “ProjectionConfiguration-xxxxx”.

I
W
Hero (Partner)
Forum|alt.badge.img+7
  • WyrLeeLeW
  • Hero (Partner)
  • November 5, 2025

​@SYBMETHSHIKA 

I have experienced exactly the same issue with one of our customers who is on 24R2 SU6, and found that on import of the ACP it indeed doesn’t create the entry into custom_projection_tab. This prevents the Publishing. 

We confirmed this by querying the database for unpublished projections, then compared to the same list in IFS. In our case there was 1 DB entry and 6-7 showing in IFS. To test we did a database INSERT for one of the affected projections, 

The projection now Publishes without error. 

Cheers

Lee
Wyre Solutions

Terms & ConditionsCookie settingsAccessibility statement