On IFS Applications 10, a read-only custom field on Purchase Order Lines was defined to return the latest arrival date from receipt_info. Arguments used were order_no, line_no, and release_no with select: SELECT MAX(ifsapp.receipt_info.arrival_date) FROM ifsapp.receipt_info WHERE ifsapp.receipt_info.source_ref1 = :ORDER_NO AND ifsapp.receipt_info.source_ref2 = :LINE_NO AND ifsapp.receipt_info.source_ref3 = :RELEASE_NO. Data type was Date. Detailed view receipt_info_alt was added. Synchronize then failed (exact synchronize error text was not posted). How should the custom field be defined so synchronize succeeds?
Technical details
LU/window: Purchase Order Lines. Custom field type: read-only Date. Detailed view: receipt_info_alt. Original select used :ORDER_NO, :LINE_NO, :RELEASE_NO against receipt_info.source_ref1/2/3. Register Arrival is a general object keyed by source_ref1, source_ref2, source_ref3 rather than order_no, line_no, release_no. Exact synchronize exception text was not included in the community post.
Any attachments are visible to signed-in members.
1 answer
0
✓ Accepted answer
Confirmed fix (validated by the original poster): drive the custom field from v.objkey and resolve PO line keys inside the SQL. Use argument v.objkey. Select statement: SELECT MAX(r.arrival_date) FROM receipt_info r WHERE 1=1 AND r.source_ref1||r.source_ref2||r.source_ref3 = (SELECT p.order_no||p.line_no||p.release_no FROM purchase_order_line p WHERE p.objkey = :objkey). Method signature: Purchase_Order_Line_Cfp.Get_Cf$_Last_Rec_Date(v.objkey). Root cause: mapping order_no/line_no/release_no arguments into receipt_info source references does not match the general Register Arrival key model.
Prerequisites and limitations
IFS Applications 10 custom fields on Purchase Order Lines. Exact synchronize error text was never posted. A later community question about publishing into Register Arrivals was left unanswered in this thread and is out of scope for this draft.