19-03-2024 20:15:47.436 INFO  [http-nio-8080-exec-7] c.m.r.s.i.ReturnsChannelServiceImpl.fetchReturnChannels [ReturnsChannelServiceImpl.java : 42] : Request Payload : {"OrderHeaderKey":"202401160745001399395156","OrderNumber":"301-0000260-5153389","CountryCode":"GB","OrderItemList":[{"UpcVariant":"08518170","Sku":"22550567001","ShipNode":"M05073","ProductType":"GM","salesOrderIndicator":"","levelOfService":"MS_STD_HOME_DEL","ItemDetails":{"DepartmentNumber":"T08","StrokeNumber":"T081106","ServiceItem":"Dropship","UnitPrice":null,"LineTotal":"44.99","PostalCode":"UB3 4FA"},"LineItemChannels":[]}]} 
19-03-2024 20:15:47.437 DEBUG [http-nio-8080-exec-7] c.m.r.s.i.ReturnsChannelServiceImpl.fetchReturnChannels [ReturnsChannelServiceImpl.java : 45] : Processing return channel request for country GB
19-03-2024 20:15:47.438 INFO  [http-nio-8080-exec-7] c.m.r.s.i.ReturnsChannelServiceImpl.fetchReturnChannels [ReturnsChannelServiceImpl.java : 69] : About to start iteration of payload...
19-03-2024 20:15:47.439 INFO  [http-nio-8080-exec-7] c.m.r.s.i.ReturnsChannelServiceImpl.fetchReturnChannels [ReturnsChannelServiceImpl.java : 99] : Fetching return channels for sku : 22550567001
19-03-2024 20:15:47.439 INFO  [http-nio-8080-exec-7] c.m.r.r.i.StrokeChannelRepositoryImpl.fetchStrokeData [StrokeChannelRepositoryImpl.java : 47] : About to query return channels -> strokeId :T081106 , deptId :T08, node :M05073
19-03-2024 20:15:47.440 DEBUG [http-nio-8080-exec-7] o.s.d.m.c.MongoTemplate.doFind [MongoTemplate.java : 2554] : find using query: { "$or" : [{ "strokeId" : { "$in" : ["T081106"]}}, { "deptId" : { "$in" : ["T08"]}}, { "nodes" : { "$in" : ["M05073"]}}]} fields: Document{{}} for class: class com.mns.returns.dto.dataobjects.StrokeChannelData in collection: stroke-return-channels
19-03-2024 20:16:10.765 INFO  [http-nio-8080-exec-7] o.m.d.connection.info [SLF4JLogger.java : 71] : Opened connection [connectionId{localValue:3, serverValue:80934}] to mns-return-mongo-dev-lb.kmh5m.mongodb.net:27017
19-03-2024 20:16:10.979 DEBUG [http-nio-8080-exec-7] c.m.r.r.i.ChannelAddressRepositoryImpl.fetchChannelAddress [ChannelAddressRepositoryImpl.java : 35] : Fetching address for channel : CH24
19-03-2024 20:16:10.981 DEBUG [http-nio-8080-exec-7] o.s.d.m.c.MongoTemplate.doFind [MongoTemplate.java : 2554] : find using query: { "channelID" : { "$in" : ["CH24"]}} fields: Document{{}} for class: class com.mns.returns.dto.address.ChannelAddress in collection: channel-address
19-03-2024 20:16:11.189 WARN  [http-nio-8080-exec-7] c.m.r.t.ReturnChannelTransformer.lambda$returnChannelsFormatter$0 [ReturnChannelTransformer.java : 61] : No mapping found for key parcelForce / unable to get object for key parcelForce
19-03-2024 20:16:11.190 WARN  [http-nio-8080-exec-7] c.m.r.t.ReturnChannelTransformer.lambda$returnChannelsFormatter$0 [ReturnChannelTransformer.java : 61] : No mapping found for key parcelForce / unable to get object for key parcelForce
19-03-2024 20:16:11.190 INFO  [http-nio-8080-exec-7] c.m.r.t.ReturnChannelTransformer.resolveCommonAddress [ReturnChannelTransformer.java : 183] : Resolve common address
19-03-2024 20:16:11.191 INFO  [http-nio-8080-exec-7] c.m.r.t.ReturnChannelTransformer.resolveOrderLevelReturnChannel [ReturnChannelTransformer.java : 108] : Resolve order level return channels.
19-03-2024 20:16:11.191 INFO  [http-nio-8080-exec-7] c.m.r.t.ReturnChannelTransformer.removeEVRIForBTPostCodes [ReturnChannelTransformer.java : 206] : Checking BT postcode scenario...
19-03-2024 20:16:11.191 INFO  [http-nio-8080-exec-7] c.m.r.t.ReturnChannelTransformer.removePostalForMinReturnTotal [ReturnChannelTransformer.java : 166] : Checking minimum return total ...
19-03-2024 20:16:11.192 INFO  [http-nio-8080-exec-7] c.m.r.c.ReturnChannelsController.fetchReturnChannelsv2 [ReturnChannelsController.java : 62] : Applying filer rule ITEM_CLICK_AND_COLLECT for order number 301-0000260-5153389
19-03-2024 20:16:11.192 INFO  [http-nio-8080-exec-7] c.m.r.s.i.FilterChannelResponseImpl.isPureSalesOrderWithClickCollect [FilterChannelResponseImpl.java : 52] : ITEM_CLICK_AND_COLLECT, order number 301-0000260-5153389 is not pure sales item

Where ,what and how to achieve code update below thing based on the above code flow ?

Modification in ReturnChannelsController -> /fetchReturnChannels/v2
Adding return shipnode in the channel api at header level
logic in ticket
see in the ticket comment section...
The design has been finalised. There are two activities from the Returns team-

Api team to send new field "returnShipNode" in channel API based on logic- check if child client id is 0 if present otherwise we need to see postcode at header level. We must send this new attribute when Ollerton is selected as the return address. Values for this field will be 8222, but it needs to be configurable.
The front end will use the attribute if the value is there and stamp in shipnode attribute in the confirm return API request.

 Operations Team is having difficulty tracking the return items for dropship orders
 the OMS Team has developed an approach
 
Modification in ReturnChannelsController -> /fetchReturnChannels/v2
 
Based on the information provided, here are the steps you can take to resolve the issue and summarize the necessary modifications:

Modify the Returns team's API: 
a. Introduce a new field named "returnShipNode" in the channel API. 
b. Implement logic to determine the value of "returnShipNode" based on the following criteria:

If the child client ID is 0, set the value to "8222" or a configurable value.
If the child client ID is not 0, use the postcode at the header level to determine the value. 

c. Ensure this new attribute is included in the API only when Ollerton is selected as the return address.

Adjust Frontend implementation: 

a. Modify the frontend to utilize the "returnShipNode" attribute if it is present. 
b. Stamp the "shipnode" attribute in the confirm return API request with the value received from the "returnShipNode" field.

Implement Operations Team's tracking solution: 

a. Update the ReturnChannelsController with modifications in the /fetchReturnChannels/v2 endpoint or any other relevant endpoints to facilitate better tracking of return items for dropship orders.

Summary:

Modify the Returns team's API to include the "returnShipNode" attribute with necessary logic and only when Ollerton is selected as the return address.
Update frontend implementation to utilize the new attribute and stamp it in the confirm return API request.
Implement improvements in the ReturnChannelsController to improve tracking of return items for dropship orders.

mongo=
{
orderRef:
"601-0000261-1333601"}