Adding CF in Shipment Available Lines

Hi Ed, 

No, It's not possible to have a custom field on Shipment available lines. 

Thanks 

Reddy

Hello

i am afraid i didn’t agree you can add a custom field on ShipmentSourceUtility entity and then publish it in the additional View SOURCE_LINE_SHIPMENT

then you have your field in available lines of the shipment

hello, I Add this in entity ShipmentSourceUtility, but I cant see it 

Hi ​@Ed22,

It is possible to add read-only custom field for Available Lines for Shipment Inventory screen in 26R1, however, not possible for earlier version.

Please check discussion below.

https://community.ifs.com/25r2-general-questions-employee-partner-only-326/custom-attributes-issue-in-available-lines-for-shipments-after-25r2-67035

Regards 

Abdul Rehman 

I Add this SQL query: SELECT c2.customer_po_no
FROM CUST_ORD_LINE_SHIPMENT_PUB c 
JOIN CUSTOMER_ORDER c2
ON c2.order_no = c.source_ref1
WHERE c.source_ref1 = :source_ref1 it is problem in sql query or no?

I use this SQL query: 

SELECT c2.customer_po_no
FROM CUST_ORD_LINE_SHIPMENT_PUB c 
JOIN CUSTOMER_ORDER c2
ON c2.order_no = c.source_ref1
WHERE c.source_ref1 = :source_ref1

so, its problem in query or no?

Hello

i am afraid i didn’t agree you can add a custom field on ShipmentSourceUtility entity and then publish it in the additional View SOURCE_LINE_SHIPMENT

then you have your field in available lines of the shipment

 

I use this SQL query: 

SELECT c2.customer_po_no
FROM CUST_ORD_LINE_SHIPMENT_PUB c 
JOIN CUSTOMER_ORDER c2
ON c2.order_no = c.source_ref1
WHERE c.source_ref1 = :source_ref1

so, its problem in query or no?

 

did you synchronize the entity after adding SORUCE_LINE_SIPMENT ?

 

did you synchronize the entity after adding SORUCE_LINE_SIPMENT ?

 

yes

Hello

i am afraid i didn’t agree you can add a custom field on ShipmentSourceUtility entity and then publish it in the additional View SOURCE_LINE_SHIPMENT

then you have your field in available lines of the shipment

 

I use this SQL query: 

 

SELECT c2.customer_po_no
FROM CUST_ORD_LINE_SHIPMENT_PUB c 
JOIN CUSTOMER_ORDER c2
ON c2.order_no = c.source_ref1
WHERE c.source_ref1 = :source_ref1

 

so, its problem in query or no?

hello

if you add the CF like i suggest you will see it in SOURCE_LINE_SHIPMENT_CFV view

yes, there it is, but I need this in entity ShipOrderSourceLines, view → SHIP_ORD_LINE_SHIPMENT_PUB

sorry, there: 

Entity (LU name): CustOrderSourceLines
Element name: AvailableCustOrdLinesList
Projection Entityset:
Projection Entity: CustOrderSourceLines
View: CUST_ORD_LINE_SHIPMENT_PUB

Hello

i am afraid i didn’t agree you can add a custom field on ShipmentSourceUtility entity and then publish it in the additional View SOURCE_LINE_SHIPMENT

then you have your field in available lines of the shipment

 

I use this SQL query: 

 

SELECT c2.customer_po_no
FROM CUST_ORD_LINE_SHIPMENT_PUB c 
JOIN CUSTOMER_ORDER c2
ON c2.order_no = c.source_ref1
WHERE c.source_ref1 = :source_ref1

 

so, its problem in query or no?

i guess it should works hereunder is the query i use

select  case sls.source_ref_type_db  when 'CUSTOMER_ORDER' THEN nvl((select co.Authorize_Code||' : '||co.district_code from customer_order co where co.order_no=sls.source_ref1),'? : ?')   when 'PURCH_RECEIPT_RETURN' THEN nvl((select po.buyer_Code from purchase_order po where po.order_no=sls.source_ref1),'?')  when 'SHIPMENT_ORDER' THEN nvl((select so.requisitioner_code from SHIPMENT_ORDER so where so.shipment_order_id=sls.source_ref1),'?') else '?' end as "Responsable : Secteur"  from SOURCE_LINE_SHIPMENT sls  where (sls.source_ref1=:source_ref1 and sls.source_ref2=:source_ref2 and sls.source_ref3=:source_ref3 and sls.source_ref4=:source_ref4 and sls.source_ref_type_db=:source_ref_type_db) or (sls.source_ref1=:source_ref1 and sls.source_ref2=:source_ref2 and sls.source_ref_type_db=:source_ref_type_db and :source_ref_type_db='SHIPMENT_ORDER')

no, it doesnt work, its probably not good entity. We have version 25.1

perhaps ...we are in a quite old version 23R1 , we are supposed to migrate end of 2026 to the last version

Hi, this is invalid link