Change in Bill To Address of customer card causing Bill TO address update for corresponding customer all sales transactions

(0) Share

Report

Posted on by Community Member Microsoft Employee

Hi,

I have come across scenario and observed in dynamics GP while updating Bill To address of customer card.

Scenario is as below :

i have customer C100 who had 01 address on his customer card and placed sales order ORD00001 and INV0001 with address 01.

later i went customer card open C100 customer and updated 01 address details like contact,city, etc.. when i do this update it was also getting updating Bill TO of ORD00001 and INV0001 which is already processed .
beacuse of this address are getting mess up with transactions.

Why bill to address getting updated in all corresponding Customer transactions when only update to the customer card happend. how can we stop this or is there method or alternative way of stopping the same.

*This post is locked for comments

All responses (4)

Answers (1)

Community Member Microsoft Employee on at

Like (0)

Report

RE: Change in Bill To Address of customer card causing Bill TO address update for corresponding customer all sales transactions

Thank you Tim..

that was understandable . thank you for your valuable inputs on the same.
Verified answer

Tim Wappat 5,701 on at

Like (0)

Report

RE: Change in Bill To Address of customer card causing Bill TO address update for corresponding customer all sales transactions

is there any configuration or settings or customization possibility for stooping auto roll down the address changes to all the transactions.

Just to clarify, it isn't rolling down the address change to the order records. The order records have a pointer to the address record you have changed, therefore whenever that record is changed it is changed for all orders that use it. I know its a little pedantic but for others reading this to properly understand, I thought it worth clarifying.

There is no way around this without creating unique address records.

For example in the past we had users by convention use letters from the contact name combined with the zip/postal code to generate a mostly unique key for the address ID and then save the address under than record.

You'd then set the BillTo Address ID to this address record.

If your bill to and ship to are always the same, you could alter the reports to use the other field.

I can't think of a way to do this by configuration without a decent amount of modification of code or reports, which of course you could do.

Tim
Community Member Microsoft Employee on at

Like (0)

Report

RE: Change in Bill To Address of customer card causing Bill TO address update for corresponding customer all sales transactions

Hi Tim,

Thank you for the quick response.

you are right "Only by creating unique address IDs for each order would you be able to create individual addresses per order". but i have business requirement where i want use single address id for all the orders for billing which was causing the overriding billing addresses on other orders with every new order created.

is there any configuration or settings or customization possibility for stooping auto roll down the address changes to all the transactions.

Regards,

Praveen
Tim Wappat 5,701 on at

Like (0)

Report

RE: Change in Bill To Address of customer card causing Bill TO address update for corresponding customer all sales transactions

Only the ship to address is captured and stored against the individual order.

All the other addresses are pointers back to that address in the customers "address book". The address in the address can be updated and all the documents that refer to it will then use that updated address going forward.

Normally this is a good thing as changing the address in one place changes it for all records that use it.

I don't get why this is causing you a problem, but it is normal behaviour for GP. Only by creating unique address IDs for each order would you be able to create individual addresses per order. - I would not think this is going to be manageable for very long.

Tim.