Central address management for Release 4.0
Description
A new central address management (CAM) will be delivered for Release 4.0, to be implemented in the areas listed below.
In the medium to long term it is planned to change all applications to this central address management.
In the new CAM the data will be managed in its own database tables. All
application objects will only store a reference to the address key.
The following lists the applications in which CAM will be active from Release 4.0A:
The list is split up into
a) Addresses changed to CAM for 4.0A
b) Applications in which the address function is new in 4.0
c) Applications in which the CAM was used in a Release before 4.0
a) Addresses changed to CAM for 4.0A (including data conversion, see below):
- All addresses for customizing objects, that is in the R/3 standard the addresses for:
- Transportation planning point
- Transportation connection point
- Sales/purchase tax groups (address and address of tax office)
- Company code - reply addresses (balance confirmation)
- Table T5G52 (tax district and reference details)
- Table J_1BBRANCH (CGC branch)
- Shipment documents (SD/WS)
- KANBAN (differing delivery addresses)
- Delivery addresses for reservation/dependent requirements
- User addresses and addresses for SAPoffice users (office users): The
addresses in USR03 or SADRP are integrated in a common data structure with a common maintenance interface and functions.
- Addresses for external exchange partners (firms and contact persons) for SAPoffice
- All subsequent functions in SAPoffice which contact addresses directly,
such as external send and receive, distribution lists with addresses, substitutes (external)
- SAPconnect (on the basis of SAPoffice)
b) Address functions are new in 4.0:
- Other addresses in customizing:
- Company code - EC tax numbers/notification of authorities
- Lockboxes for house banks
- Address determination from plant and storage location
- Addresses in purchase requisitions (as for purchase orders)
- Address in site master (Retail)
c) Applications in which CAM was already used in a Release before 4.0:
- Materials management/purchasing: Permanent delivery addresses for purchase orders
- Central business partner entry in several industry solutions
- IS-Utilities (business partners, link objects)
- IS-OIL (physical business locations)
- Foreign trade (credit processing)
Data conversions:
The data for all addresses listed under a) is converted automatically
into the CAM tables during the 4.0 upgrade. A where-used list, which is required for reorganization, is created at the same time.
Only data is transferred to the CAM tables during the data conversion.
No table contents are deleted. logtype (Full screen, dialog box, Include screen)
The data conversion only writes data into the CAM tables. No table contents are deleted.
Which (new) functions are active in the CAM for 4.0?
- Extended attribute set (internationally required address fields)
- Print function that determines the data dynamically from the address file
- All current communication types
- Language-specific titles, name parts (for persons/contacts)
- Where-used list, archiving class for the Archive Development Kit (ADK)
- Classification of the addresses by application for specified selections
Consequences for customer programs
In which cases is the customer affected directly by the changes, and when do customer programs or forms have to be changed?
1. Direct accesses to table SADR in user programs
- Direct access must be replaced For the addresses listed above under a),
particularly addresses of SAP customizing objects. The function module
ADDR_GET can usually be used to read the address. See the documentation of the function module and its parameters.
- For addresses of other SAP objects: even for SAP objects whose
addresses are not yet stored in the table SADR, SAP recommends that you
encapsulate the direct accesses in customer programs for 4.0A/B to prepare for further changes in subsequent Releases.
- For addresses of customer objects:
As the table SADR is not being developed any further, SAP recommends
that the addresses of customer objects should also be converted to CAM.
Only the address data needs to be converted for SADR addresses. The
address numbers can be retained, so that conversion of the application
table whose field the SADR references is not necessary. See OSS Note 85676.
2. Direct access to table USR03 (user addresses) in user programs:
These direct accesses must also be replaced. The function module SUSR_USER_ADDRESS_READ can usually be used instead. See the
documentation of this function module.
If you have based your programs on SAP programs, the direct accesses have already been replaced in the SAP programs.
If necessary, adapt your program to the new SAP program status.
1. Direct accesses to table EKAN (address one-time vendors in purchasing) in user programs:
Such direct accesses must be replaced. The address must be read with
the function module ADDR_GET. The corresponding address number is
stored in the field EKKO-ADRNR. See the documentation of the function module ADDR_GET.
1. Customer batch input programs for purchase orders or inquiries with one-time vendors or delivery addresses:
The interface has changed in this area during the changeover to 4.0.
Your batch input programs must be adapted to the new interface.
Addresses in Purchasing Linked to the Central SAP Address Management
1. Forms with address windows:
If you have copied SAP forms with address windows, check whether a
change of the ADDRESS ... ENDADDRESS call in the original form needs to be transferred to your form.
Damage caused to data by errors
There is no danger of data losses since no table contents are deleted during the data conversion.
Change system parameters in customizing
Additional customizing settings can be made for the central address management. They can be found in the IMG under the component
Cross-application functions
--> General application functions
--> Address management
Execute function
Effect on batch input
see above
Changes to the interface
see above
Dependent functions
The application areas in which the central address management is used in 4.0 are listed above.
Further notes