Skip to main content

I am trying to create a Read Only custom field (P2P_EXEMPT) on the Posting Proposal screen that looks at another custom field (P2P_EXEPEMTION) on a different screen (Supplier)

 

select cf$_IR35_exemption as P2P_EXEMPT

from ifsapp.SUPPLIER_INFO_GENERAL_cfv

where supplier_id=:identity

 

As sql this runs and returns the CF2 value

However, when I put this code into the CF1 build, I get this error when I try to Approve the new field

 

 

I have tried both v and t in the Argument
I have tried everything I can think of and everything gives this error

I have tried this direct access
I have tried using an IAL
I have added a function to a an API
I have created a function

In all cases the object works and I can select the value I want BUT when I try to out it into the Custom field, I get the above error

Does anyone know what the issue is?
We are using Apps9 Upd 17

Any ideas? Is this a bug with IFS or have I missed something basic?
Thanks
Roger

@RogerB what is the error message you are getting? It’s not visible in the post.

One suggestion, could you try and get rid of the column alias ‘as P2P_EXEMPT’ → the CF Name will be displayed as column name so having a column alias in the SQL statement doesn’t serve any purpose.

Hi Marcel

Yes, I spotted that after I had created the case.

That was from the code I created in SLQ to test and was removed from the actual field

select cf$_IR35_exemption 
from ifsapp.SUPPLIER_INFO_GENERAL_cfv 
where supplier_id=:identity

Still get the same error though.

Roger

 

@RogerB do you have other CF on the PopstingProposalHead? Can you check that the POSTING_PROPOSAL_INVOICE_FINAL view is approved & published? Otherwise you cannot add any custom fields.

 

Hi Marcel

Thanks for that

There are other custom fields on that screen

I checked and the FINAL view was not published. I did that, but still get the error when I try to approve the new field.

There are only 4 of 10 approved views.

Is it worth enabling any others/all of them?

Thanks

Roger

Just to close this one off.
It turns out there is a feature on the Posting Proposals screen.

it HAS to have a Supplier_ID field in the head table.

Only then am I able to query anything else in another custom field.

Create Supplier_ID field as persistant.
This creates the field in the POSTING_PROPOSAL_TAB.
You don’t need to populate the field. You don’t even need to query the file in you real Reda Only Custom  Field. It just needs to exist
Don’t understand WHY, but it works. I was then able to create and publish my actual Custom field..

Reply


Terms & ConditionsCookie settings