Delivery Address not picking from OIS002 instead picking Customer Address from CRS610

Hey guys,

I am facing an issue here. Let me know if you could help.

While creating a customer order i am passing Address number as input in order to fetch the right delivery Address from OIS002. But the Address is always getting picked from CRS610 instead of OIS002. Any idea how to override this?

Find more posts tagged with

Accepted answers

All comments

Legacy Contributor

Can you try keying in 'address no' field in CRS610/G for the customer. This address no is defined in OIS002.

Legacy Contributor

Is the input manually or through API?

Legacy Contributor

Watch out for the city in the OIS002 address, may be empty.

Legacy Contributor

Are you supplying the address number in the ADID input in OIS100MI.AddBatchHead? This should work.

Legacy Contributor

Thanks for the response guys. Looks like we are creating the orders using API/WebService. I am not sure what exactly we are using. I am yet to get the details.

I am not facing this error when I try to create order manually. Order correctly picking up address from OIS002 based on the input we feed in OIS100. We can't set default Address type in CRS610 as the Address type will be decided only during order creation.

Legacy Contributor

Ok, there is no problem setting an address number if you create the order using the standard API. But since we don't have any details on how your integration is setup it is hard to see where the problem lies.

Catharine Linsbauer

Another thing to check would be customer order type settings (OIS014). If you want the address to be defaulted from the customer as Ajay mentions parameter should be *CUS.

Legacy Contributor

Confirm this steps

1. Please see if the address created in OIS002 is of the type 01 and if the dates are valid

2. The Check date parameter in (CRS720 - Settings - Customer Order Entry) is used to specify which date to use for delivery addresses validity check (order date or requested delivery date).

3. You can define a delivery address to be proposed by default when entering new customer orders

Legacy Contributor

We have had a similary issue, the API returned the ocusma address instead of the ocusad address, this was beacause the town of the ocusad address was empty.

Legacy Contributor

Thanks guys for the response. We have right delivery address(OIS002) at the Order level. But wrong delivery Address(OCUSMA) at the delivery level. It took a while to find out the reason. The issue is because the Order lines(OIS101) were not mapped with Address number from OIS002(Even though the header is correctly mapped), that makes the delivery picks the Address from OCUSMA instead of OCUSAD.

Copyright © 2025 Infor. All rights reserved.