If there is no way. I will use a custom field to get the text.

You are correct. The only way is to use a custom field with the hardcoded value.

I think it is a bad way. But, there isn't any other choice which we know.

you can try External search URL

https://docs.ifs.com/techdocs/foundation1/050_development/022_user_interface/045_ee_dev/080_external_search/default.htm

There is a better way to achieve this using external search. 

as an example:  ifsapf:frmAvailabilityPlanning?EXTERNAL_SEARCH=CONTRACT%3D{&CONTRACT}%26PART_NO%3D123456

If we break this down into the relevant elements:

• ifsapf:windowname?EXTERNAL_SEARCH=
  • This sets the window name and the external search 
• CONTRACT
  • FIELD_NAME of the field on the destination screen
• %3D 
  • is the encoded value for the = sign
• {&CONTRACT}
  • is the name of the field in the current screen where to take data from, inside braces (these characters are NOT encoded)
• %26
  • is the encoded value for the & sign
  • used to add a second parameter to the search
• PART_NO
  • FIELD_NAME of the field on the destination screen
• %3D 
  • is the encoded value for the = sign
• 123456
  • Is the fixed value of the part. 

In your example it may be something like this 

ifsapf:frmPurOrdPaymentSchedule_Cust?EXTERNAL_SEARCH=ORDER_NO%3D{&CF$_ORD}%26CHG_ORDER_NO%3D*

Thank you for the detailed response. I think the same way. But, I did not know if I could pass a parameter from the custom menu. I will try it.

@Chriswharton22 It works. Thank you. You prevented us from using an unnecessary custom field. :)

Happy to help, 

it was driving me mad this week and it isnt well documented, hopefully this will help others too