cancel
Showing results for 
Search instead for 
Did you mean: 

Changed address using Address proposal button functionality in SAP CRM WebUi

Former Member
0 Kudos

CRM WebUI has a standard feature of "Address proposal " in sales order/transaction level.This feature allow to change address for partner at sales order in case partner has multiple address using this button (address proposal in parties involved AB , refer attached screenshot) user can select the required address and save .

The sale order when replicates to SAP ECC the change address is not replicated hence at CRM level we have a changed new address for partner but in ECC sales order partner still hold the old address as the replication failed here in this case .

Can anyone provide any input on this as "address proposal " is a standard feature which SAP provides to have new address entered manually at the sales order/transaction level .

This should ideally replicate to connect SAP ECC system via middle ware as mostly CRM works with integration to SAP ECC and hence there should be middle ware replication also happening in this case .

Accepted Solutions (0)

Answers (1)

Answers (1)

spencer_liang
Active Contributor
0 Kudos

There are several notes about address replication issue, say,

1068460 Manual address data lost after upload to R/3
622327 Upload R/3: Master for document addresses, billing split
756154 Item partner with alternative address not transferred
756131 Alternative addresses and transfer of orders to R/3
535122 Wrong partner address data in order from CRM to R/3
598269 Upload sales order: Address is not transferred
576067 Upload Salesorder:Master data addrsss become doc addresses
1009716 Address change in R/3 although address is not changed
764874 Initial or request load: No document addresses transferred
522641 Download sales order: Transfer of address data

You may search note on SAP launchpad for the BBPCRM release.

You may also debug for the root cause.

Refer to note below and debug crm_r3_salesdocument_upload to check if address is correctly mapped to bapi and sent to r3.

656823 FAQ: Tips and tricks for transfer debugging