Page Comparison

This customizing transaction is used to customize address determination and storage for BP-based customers and vendors:

• specify how address sent to SAP FSM will be determined - including source and address type

• specify how address created in FSM will be stored in SAP ECC/S4

...

...

Use the tab ‘BP Address Types’ to specify which address types are allowed for FSM and which FSM address types they should be assigned to (bill-to, ship-to, other). ‘Standard’ addresses are sent as ‘default’ to FSM.  

...

Address created in FSM

You can decide whether addresses created for Business Partners in FSM should be stored in SAP ECC/S4 by adjusting the ‘Address from FSM’ setting in the ‘Address Detemination Settings’ tab:

...

• Store - inbound addresses will be saved in SAP ECC/S4

  • When Business Partners are enabled (see the field ‘Business Partner functionality enabled’ in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952515), the addresses will be stored as BP addresses, based on the mapping provided in the ‘BP Address Types’ tab.

    • If more than one relevant entry is found, the first found one is used. If none found, an error is thrown.  

    • ‘Default’ addresses are saved as ‘standard’ in SAP.  

    • If only one address of a given type is allowed in SAP, then the validity date of the former one ends and the new address becomes the only valid one

  • When Business Partners are disabled:

    • Addresses for Vendors will be stored only in a dedicated table - /PACG/ECM_BPOADR. Data from this table can be used by custom implementation of address storing.

    • Addresses for Customers will be stored in a new customer created during inbound processing of an address. The customer is then linked to the original customer via a partner role. If customer creation fails, the address is stored in the /PACG/ECM_BPOADR table.

...