Custom field from Purchase Order Line added to Register Arrivals

Trying to add custom field for Price/Curr from the Purchase Order Line to Register Arrivals screen, but these are not available:

 

Hi ​@rkurfman.vib,

The issue is due to how custom fields are handled in IFS.

 Custom fields created on PurchaseOrderLine are only available for that LU and won’t automatically appear in Register Arrivals, since it is based on a different LU (e.g., ReceiptInfo / ReceiptInfoAlt).

 What you need to do

Option 1: Create Custom Fields on Receipt LU

• Identify the LU used in Register Arrivals (e.g., ReceiptInfoAlt)

• Create the same custom fields there

• Approve and Publish them

Option 2: Use Custom Attribute Mapping / Logic

• If you need to bring values from PO Line:

  • Use event/action or projection logic

  • Populate the receipt custom field from PO Line during arrival

 Important

• Even though PO Line is the source, Register Arrivals does not directly use that LU

• So CFs must exist on the target LU (Receipt side)

 Tip

From your screenshot:

• RECEIPT_INFO_ALT is not yet approved/published

 Try:

1. Approve

2. Publish

3. Refresh metadata

 Summary

✔️ CF on PO Line ≠ visible in Receipt
✔️ Create CF on Receipt LU
✔️ Use logic if value needs to be copied

Let me know if you need help identifying the exact LU behind your screen.

Hello Update:

When I try again to add this view, I get the error message below when trying to Synch:

I was able to add the Price_Curr (FBUY_UNIT_PRICE) field from Purchase Order Lines to Receipts as a Read Only custom field

Logical Unit:    ReceiptInfo
View:        &AO.RECEIPT_INFO

with below Arguments and Select Statement 

But still not able to transfer or add this value for Price_Curr from Purchase Order Lines to 

Register Arrivals where I need it:

*Can you help me with the Custom Field Logical Unit needed, the Arguments and Select Statement needed for the Price_Curr field value from the Purchase Order Line to show up on Register Arrivals?

Hello Update:

When I try again to add this view, I get the error message below when trying to Synch:

 

I was able to add the Price_Curr (FBUY_UNIT_PRICE) field from Purchase Order Lines to Receipts as a Read Only custom field

Logical Unit:    ReceiptInfo
View:        &AO.RECEIPT_INFO

with below Arguments and Select Statement 

But still not able to transfer or add this value for Price_Curr from Purchase Order Lines to 

Register Arrivals where I need it:

 

*Can you help me with the Custom Field Logical Unit needed, the Arguments and Select Statement needed for the Price_Curr field value from the Purchase Order Line to show up on Register Arrivals?

​@rkurfman.vib ,

Hi,

You are very close, but the issue comes from mixing LUs and how Custom Fields are compiled/extended in IFS.

 Root Cause

• You are trying to extend PurchaseOrderLine LU using a detail view from Receipt (RECEIPT_INFO_ALT)

• This causes the compile error:

  Error -904 in CUSTOM_FIELD_CODE[RECEIPT_INFO_ALT_CFV.VIEW]
  

• Custom Fields must only reference views belonging to the same LU

 Correct Approach

✔️ 1. Use the correct LU (target screen)

For Register Arrivals, the correct LU is:

• ReceiptInfo (or ReceiptInfoAlt depending on screen)

 Custom Fields must be created on this LU, NOT on PurchaseOrderLine

✔️ 2. Use Source References correctly

From your screen:

• Source Ref1 = Order No

• Source Ref2 = Line No

• Source Ref3 = Release No

These map correctly to:

order_no
line_no
release_no

✔️ 3. Correct Select Statement (on Receipt LU)

Use this:

SELECT fbuy_unit_price
FROM purchase_order_line_all
WHERE order_no   = :source_ref1
  AND line_no    = :source_ref2
  AND release_no = :source_ref3

 This is correct and already working for Price

✔️ 4. For Price_Curr (Currency)

You need to fetch the correct column from PO line:

Example:

SELECT currency_code
FROM purchase_order_line_all
WHERE order_no   = :source_ref1
  AND line_no    = :source_ref2
  AND release_no = :source_ref3

 Use the exact column name from:

• PURCHASE_ORDER_LINE_ALL (e.g. currency_code, buy_currency, etc. depending on version)

 Important Fix for Your Error

From your screenshot:

• You selected RECEIPT_INFO_ALT as detail view under PurchaseOrderLine
  ❌ This is incorrect

 Fix:

1. Remove RECEIPT_INFO_ALT from PurchaseOrderLine CF setup

2. Create CF directly on:

   • ReceiptInfo or ReceiptInfoAlt LU

3. Approve → Publish → Sync

 Key Rule (Very Important)

✔ Custom Fields must be created on the target LU (screen LU)
✔ You can fetch data from other LUs using SELECT logic
❌ You cannot mix detail views across different LUs

 Why your Price worked but Currency didn’t

• Price worked because:

  • You created it correctly on ReceiptInfo LU

• Currency failed because:

  • You tried extending via wrong LU/view combination

 Final Solution Summary

• Create CF on ReceiptInfo / ReceiptInfoAlt

• Use SELECT with :source_ref1/2/3

• Do NOT attach Receipt views under PurchaseOrderLine

• Ensure correct column name for currency

If needed, I can help you identify the exact column name for Price_Curr in your environment 

Hello,
I had no issue creating the custom field on LU RECEIPT_INFO on the Receipt(s)

But still not able to get it to appear on Register Arrivals screen which is where I need it.  User wants to be able to see the Price/Curr value from Purchase Order Line before they do the Receive step

Hello,
I had no issue creating the custom field on LU RECEIPT_INFO on the Receipt(s)

But still not able to get it to appear on Register Arrivals screen which is where I need it.  User wants to be able to see the Price/Curr value from Purchase Order Line before they do the Receive step

 

​@rkurfman.vib ,

This explains the behavior 

You created the CF on ReceiptInfo, so it works on Receipts screen.
However, Register Arrivals uses a different LU/view, so it won’t automatically appear there.

 Key point:

• Receipts → ReceiptInfo

• Register Arrivals → based on a different LU (e.g. ReceiptInfoAlt / arrival-specific projection)

What to do:

• Create the same Custom Field on the LU used by Register Arrivals

• Use the same SELECT logic with :source_ref1/2/3

• Approve → Publish → Sync → Refresh metadata

Why:

Register Arrivals is pre-receipt step, so it does not use the same LU as finalized Receipts.

Tip:
Open Data Source Properties on Register Arrivals screen and confirm the exact LU, then extend that LU.

Thanks

Hello, I have tried this, but I am not seeing ReceiptInfoAlt as an option for LU in the Custom Fields screen:

and Register Arrivals screen Data source properties shows Logical Unit as PurchaseOrderLine

When I have created it from Purchase Order Line it just shows up as a duplicate on the PO line and still does not show up on Register Arrivals.

Hello, I have tried this, but I am not seeing ReceiptInfoAlt as an option for LU in the Custom Fields screen:

 

and Register Arrivals screen Data source properties shows Logical Unit as PurchaseOrderLine

When I have created it from Purchase Order Line it just shows up as a duplicate on the PO line and still does not show up on Register Arrivals.

 

Hello, I have tried this, but I am not seeing ReceiptInfoAlt as an option for LU in the Custom Fields screen:

 

and Register Arrivals screen Data source properties shows Logical Unit as PurchaseOrderLine

When I have created it from Purchase Order Line it just shows up as a duplicate on the PO line and still does not show up on Register Arrivals.

 

​@rkurfman.vib ,

I think the confusion here is that Receipts and Register Arrivals are not using the same thing underneath.

You already proved that your custom field works on ReceiptInfo because it shows correctly on the Receipts screen.
That part is fine.

But Register Arrivals is different. From your latest screenshot, its data source is based on PurchaseOrderLine. So a field created on ReceiptInfo will not automatically appear there.

That is why you are seeing this behavior:

• CF on ReceiptInfo → visible on Receipts

• Same CF does not show on Register Arrivals

So the next step is not to keep trying the Receipt LU.
You need to work with the LU / projection used by Register Arrivals.

What I would suggest

1. Treat Register Arrivals as a PurchaseOrderLine-based screen

2. If the value already exists on PO line, try to expose that attribute there instead of creating it again on ReceiptInfo

3. If you create a CF on PurchaseOrderLine, make sure that field is also available in the projection/page used by Register Arrivals, otherwise it may still not appear

In short

This does not look like a problem with your SQL for Price/Curr.
It looks more like a screen/LU/projection mismatch:

• Receipts = ReceiptInfo

• Register Arrivals = PurchaseOrderLine context

So the solution is to extend the side used by Register Arrivals, not the side used by finalized Receipts.

If you want, the next useful step would be to identify the exact projection behind Register Arrivals and check whether BUY_UNIT_PRICE / currency is already available there.