release notes for sap netweaver 04 cross-application ... recommend that you first execute the report...

Release Notes for SAP NetWeaver '04 Cross-Application Components

______________________________________________________________

CopyrightCopyright(c) 2004 SAP AG. All rights reserved.

Neither this document nor any part of it may be copied or reproduced in any formor by any means or translated into another language, without the prior consent ofSAP AG. The information contained in this document is subject to change withoutnotice.

SAP is a registered trademark of SAP AG.

All other products which are mentioned in this documentation are registered or notregistered trademarks of their respective companies.

1 CA Cross-Application Components 11.1 CA-BP SAP Business Partner 11.1.1 Creating a Do Not Call List (New) 11.1.2 Mass Changes (New) 21.1.3 Duplicate Check (Extended) 31.1.4 Data Cleansing (Extended) 51.1.5 Additional check for BAPIs (Extended) 51.1.6 Easy Enhancement Workbench for SAP Business Partner (New) 61.1.7 Business Hours (New) 71.1.8 Separation of the Field Groups (Changed) 81.1.9 Business Partner Role (Extended) 91.1.10 High-Performing Search Name/Address (Changed) 111.1.11 Time Dependency for Addresses (New) 121.1.12 Time Dependency for Bank Details (New) 131.1.13 CA-BP-BP Data 141.1.13.1 Tax Jurisdictions (Changed) 141.1.14 CA-BP-GRH Group Hierarchy 141.1.14.1 Business Partner Group Hierarchy (New) 141.1.15 CA-BP-RS Relationships 151.1.15.1 Duplicate Check (Extended) 151.1.15.2 Easy Enhancement Workbench (Extended) 171.1.15.3 Relationships (Extended) 171.1.16 CA-BP-UI Dialog SAP-GUI 191.1.16.1 Search Helps (Extended) 191.1.16.2 Role Change for Required Entry Fields (New) 201.2 CA-GTF General Application Functions 201.2.1 BAdIs for DME Engine in Application Basis Layer (New) 201.2.2 CA-GTF-CSC Country-Specific Objects 211.2.2.1 Tax Jurisdictions (Changed) 211.2.3 CA-GTF-IL Relationships Betw GUID Identificat 211.2.3.1 Customizing Relationship Types (Changed) 211.3 CA-PRO Central Part of Product Master 231.3.1 Archiving Functionality for SAP Products (New) 231.3.2 CA-PRO-SET Set Types and Attributes 241.3.2.1 Multi-value attributes without Product Mod (New) 24

______________________________________________________________SAP AG iii

Release Notes Table of Contents SAP AG______________________________________________________________

1 CA Cross-Application Components

1.1 CA-BP SAP Business Partner

1.1.1 Creating a Do Not Call List (New)

Use

In the USA firms and private customers can register with the National Do Not Call Registry(similar to the so-called Robinson List in Germany) in order to avoid receiving unwantedtelemarketing calls. They can also have this list sent to them.

From Release 6.40 and 6.20 (SP 37) on, you can copy such a Do Not Call list to a databasetable using the report BUPA_DO_NOT_CALL and search for all telephone numbers in questionin the business partner master data. If a telephone number is found, then the flag Do Not Useis set for the relevant business partner in the communication data in the dialog. The followingapplication, such as Marketing in SAP CRM, must then react to the flag.

You can also suppress the setting of the flag in the dialog by means of a Business Add-In(BAdI) if, for example, you were recently in contact with a firm and your telephone call isdesired.

Note

You can only maintain the Do Not Call lists from America. All data formats of the NationalDo Not Call Registry are supported.The following is a list of the data formats:

- Flat Text File - Full List

- Flat Text File - Change List

- XML Tagged File - Full List

- XML Tagged File - Change List

Effects on Data Transfer

Since the indicator Do Not Use is not communicated to other systems, the reportBUPA_DO_NOT_CALL should be carried out separately in all relevant systems.

Effects on System Administration

To create a Do Not Call list and set the indicator in the dialog, carry out the following steps:

1. Decompress the files received

2. Write the data to the table BUT_DNC using the report BUPA_DO_NOT_CALL. This stepmust be carried out separately for each client.Note

______________________________________________________________SAP AG 1

Release Notes______________________________________________________________

We recommend that you first execute the report in test mode.

3. When you execute the report again, check whether the telephone numbers are in the tableBUT_DNC in the master data of the business partner.If the telephone numbers in the business partner master data are there, then theabove-mentioned indicator (field FLG_NOUSE) is already set.NoteSince the telephone numbers are determined using the field TELNR_LONG (which containsthe telephone number in full and without special characters), you should first check thatthis field has been correctly maintained throughout by using the reportZ_CHECK_PHONE_DATA.

4. Suppress the indicator if necessary by using the BAdI BUPA_DO_NOT_CALL.

Note

We recommend you schedule the report BUPA_DO_NOT_CALL to set the indicator to run atnight in the background.

See also

For more information on creating a Do Not Call list, see the SAP note 664382.

1.1.2 Mass Changes (New)

Use

From Release 6.40 SP2 you can maintain business partner data using the mass maintenancetool.You can find the tool in the transaction MASS or MASSD.

This function allows you to change data for several business partners in one processing step.You can use it, for example, to reassign Customizing attributes or external key fields (e.g. bankkey)

You can maintain the following business partner data:

- General data I (attributes from table BUT000)

- Bank details (attributes from table BUT0BK)

- Identification numbers (attributes from table BUT0ID)

- Industries (attributes from table BUT0IS)

- Roles (attributes from table BUT100)

The changes are carried out for the Business Partner by means of the APIs (ApplicationProgramming Interface). They are also used to check the authorizations, write change documentsand set user locks.

Note

______________________________________________________________SAP AG 2

Release Notes______________________________________________________________

It is not possible to change relationship data (application object BUPR) and address data. Thelatter can however be changed via the quarterly adjustment of the Business Address Services(BAS) (see the SAP Library under Business Services -> Business Address Services(BC-SRV-ADR) -> Address Check -> SAP Regional Structure -> QuarterlyAdjustment). It is not possible either to insert new records (e.g. new bank details orindustries).


You can integrate user-defined data into the mass maintenance tool. To do this, you mustimplement a class and register it in maintenance view V_TB053.Methods exist for all application exits of the mass maintenance tool. Make the settings forregistering table extensions and new application tables in transaction MASSOBJ.

See also

For more information on mass maintenance, see the SAP Library under SAP R/3 EnterpriseApplication Components -> Cross-Application Components -> Cross-Application MassMaintenance (CA-GTF-MS) (see Mass Update with the New Interactive Design for thenew features in transaction MASSD) , as well as in transaction MASSD under Display Help.

1.1.3 Duplicate Check (Extended)

Use

Duplicate Check for Relationships

As of Release 6.40 SP2 you can carry out a duplicate check of the address data for contactperson relationships (CP relationships) and employee relationships, in addition to the check ofthe business partner address data. In this way duplicates can be also be recognized when contactpartners and employees are created or changed.

A duplicate check is carried out in the following cases:

- Duplicate check of the central address data

- When a business partner is created with address data

- When a business partner is changed

- Duplicate address of the address data for relationships

- When a CP relationship (or an employee relationship) is created with a firm's addressThe check is carried out only if an address has been assigned.

- When a CP relationship or an employee relationship is changed

Duplicate Check Dialog

______________________________________________________________SAP AG 3

Release Notes______________________________________________________________

A new dialog replaces the dialog currently supplied by a third-party provider. If a duplicate isidentified during one of the above-mentioned activities, a dialog box appears containing therelevant options for processing duplicates.

You can use the following functions in this dialog:

- Navigation to the display of a potential duplicate

- Navigation to the relevant duplicate when you create a business partner or a relationship.You can choose whether you want to save the changes you have made to the businesspartner you are maintaining.

- Creation of a data cleansing case for further processing in transaction BUPA_CLEAR

- Navigation to the display of the relationship for a duplicate in the case of contact personor employee data

- Display of the similarity of the duplicate in percent

You can use the following standard functions of the SAP List Viewer SAP List Viewer (ALV)to adapt the display of the duplicates to your specific requirements:

- Sorting

- Filtering

- Searching

- Hiding columns

- Exporting

- Positioning on the last name

- Layout management

For more information, see the user documentation of the SAP List Viewer.

Hinweis

As is currently the case, a third-party provider tool must be connected to the certified interfaceof the Business Address Services (BAS) for the duplicate check.


The following BAPIs were adapted so that they provide a list of potential duplicates:

- CP relationships

- BAPI_BUPR_CONTP_CREATE

- BAPI_BUPR_CONTP_ADDR_ADD

- BAPI_BUPR_CONTP_ADDR_CHANGE

______________________________________________________________SAP AG 4

Release Notes______________________________________________________________

- Employee relationships

- BAPI_BUPR_EMPLO_CREATE

- BAPI_BUPR_EMPLO_ADDR_ADD

- BAPI_BUPR_EMPLO_ADDR_CHANGE

Effects on Customizing

Ensure that the duplicate check has been activated in both index pools (tables BUT000 andBUT052). For this purpose, make the necessary settings in the Implementation Guide (IMG) inCustomizing of the Address Management under SAP NetWeaver -> SAP Web ApplicationServer -> Basis-Services -> Address Management -> Duplicate Check -> Activate IndexPools for the Duplicate Check .

1.1.4 Data Cleansing (Extended)

Use

From Release 6.40 SP3 the following additional data is available for comparing the data in adata cleansing case:

- BP roles

- Time-dependent data for

- Addresses and address usages

- Bank details

- BP roles

______________________________________________________________SAP AG 5

Release Notes______________________________________________________________

1.1.5 Additional check for BAPIs (Extended)

Use

From Release 6.40 there is a Business Add-In (BAdI) for user-defined checks.

This is the following BAdI, which enables you to carry out consistency checks for the businesspartner data:

- BUPA_FURTHER_CHECKS

When you create or change a business partner, you can check the consistency of the centraldata, such as the business partner category, header data, person, organization and group data;and if necessary, you can prevent the business partner from being saved by issuing an errormessage in the return table.


The BAdI BUPA_FURTHER_CHECKS is contained in the BAPIsBAPI_BUPA_CREATE_FROM_DATA and BAPI_BUPA_CENTRAL_CHANGE.

1.1.6 Easy Enhancement Workbench for SAP Business Partner (New)

Use

The Easy Enhancement Workbench (EEW) is a tool that makes extensions to SAP businesspartner quick and easy to execute. You can extend SAP Business Partner (extension objectBUPA) as follows:

- Add new fields (extension type ADD_NEW_FIELD)

- Add new tables (extension type ADD_NEW_TABLE)

The EEW supports you with wizards where you can first define the basic conditions of theextension. Once you have defined the extension, the system generates all the necessary objectsand table entries for the dialog and the user interface SAP GUI.

The extensions executed using the EEW occur in the customer namespace and do not need tobe modified.


______________________________________________________________SAP AG 6

Release Notes______________________________________________________________

Using the EEW does not require Customizing. Depending on the required extension,postprocessing can be triggered in the EEW. From the EEW you can then carry out thingsdirectly, such as the Customizing of check tables that the system generated.

1.1.7 Business Hours (New)

Use

The business hours can be used from Release 6.40.

On the tab page Control in the business partner dialog, you can state when it is possible tocontact a business partner. You can enter various schedule types for a business partner.

The following schedule types are found in the standard system :

- Calling hours

- Goods receiving hours

- Visiting hoursYou can also define your own schedule types. SAP note 636427 tells you how to use themin the dialog.

You can create calling and visiting hours under Sales Data, but not define any other scheduletypes.

The business hours are based on the SAP appointment calendar, where you can defineappointment rules with the help of the rule editor. You can use various rule types (for example,regular daily or weekly visiting hours). Therefore you can state, for example, that a businesspartner can be visited on the first Tuesday and Wednesday of every month from 08.00 to10.00, with the exception of holidays.For more information on the appointment calendar, see the SAP Library under AppointmentCalendar (BC-SRV-GBT).

At the moment it is not possible to display the change history or analyze the change documentsfor the business hours.

Effects on Existing Data

You can undertake field modifications for the business hours per business partner role, businesspartner type and activity.


The business hours can be exchanged with the SAP R/3 System and the Mobile Client.You must set the usage of simplified appointment rules in the Customizing for data exchangewith the SAP R/3 System. For this reason you can use only two weekly rules when you enterbusiness hours. For more information, see the Implementation Guide (IMG).

Note

Only the visting hours of the contact person relationship and the goods receiving hours are

______________________________________________________________SAP AG 7

Release Notes______________________________________________________________

relevant for the SAP R/3 System. You can exchange all schedule types with the Mobile Client.


The following (B)APIs are available for creating, changing and deleting business hours:

- Central data

- BAPI_BUPA_HOURS_ADD/ BUPH_BUPA_HOURS_MAINTAIN

- BAPI_BUPA_HOURS_CHANGE/ BUPH_BUPA_HOURS_MAINTAIN

- BAPI_BUPA_HOURS_GETDETAIL/ BUPH_BUPA_HOURS_GETDETAIL

- BAPI_BUPA_HOURS_REMOVE/ BUPH_BUPA_HOURS_REMOVEThe API BUPH_BUPA_HOURS_MAINTAIN is called in both cases for the BAPImethods ADD and CHANGE. It establishes internally whether the business hours ofthe relevant schedule type for the business partner are created anew or changed(corresponds roughly to a MODIFY).

- Contact person relationship

- BAPI_BUPR_CONTP_HRS_ADD/ BUPR_CONTP_HOURS_MAINTAIN

- BAPI_BUPR_CONTP_HRS_CHANGE/ BUPR_CONTP_HOURS_MAINTAIN

- BAPI_BUPR_CONTP_HRS_GETDETAIL/ BUPR_CONTP_HOURS_GETDETAIL

- BAPI_BUPR_CONTP_HRS_REMOVE/ BUPR_CONTP_HOURS_REMOVEWhat applies to BUPH_BUPA_HOURS_MAINTAIN also then applies to APIBUPR_CONTP_HOURS_MAINTAIN.

Execute report CRM_CHECK_APP to check if the goods receiving hours and visiting hours ofthe contact person relationship, which are maintained in the system, can be exchanged with theSAP R/3 System.The hit list can be can be maintained in order to adapt the relevant rules to the necessaryformat.


Make the following settings in the IMG in the Customizing of the Basic Settings of the SAPBusiness Partner under Business Hours :

- Establish Dialog Form for Visiting Hours

Make the settings for field grouping in the Customizing of the basic settings under FieldGroupings.

1.1.8 Separation of the Field Groups (Changed)

Use

From Release 6.40 it is possible to control the field grouping for name fields separately.

For this purpose separate field groups were created for the following fields:

______________________________________________________________SAP AG 8

Release Notes______________________________________________________________

- First and last name of the person

- Date and place of birth

- Search term 1 and search term 2

- Name 3 and name 4 of the organization

- Name 1 and name 2 of the group

In addition, the fields for the first and last name are now found in different BDT views, whichmeans that these fields can also be configured using the Virtual Configuration Tool (VCT) atdifferent points of the screen layout.


Execute report BUPXPRA16 in order to adapt the field grouping for the separated field groups.

Note

If you have defined your own field grouping criteria, you must adapt these settings manually.


Make the necessary settings for the VCT in the Implementation Guide (IMG) in theCustomizing of the Basic Settings of the SAP Business Partner in the Screen Configurationunder Configure Screens.

Check the settings in the Customizing of the Basic Settings under Field Groupings.

1.1.9 Business Partner Role (Extended)

Use

From Release 6.40 there is a new concept for the business partner roles.

This means that the significance of the business partner role (BP role) has changed in somerespects. Up till now, the BP role was also used for screen control, which makes it possible toestablish a certain view of the data of a business partner based on the data sets assigned to arole. At the same time, the BP role was used to classify a business partner from a businesspoint of view.

The term, "BP role" is now significant only from a business point of view. This has been donein order to separate the BP role's function in terms of screen control from its business function.The BP role retains its previous significance, but will be used in future only in the context ofthe Business Data Toolset (BDT) and the screen sequence. It is now called the "business partnerview".Screen control then takes place by assigning a BP view to a BP role

______________________________________________________________SAP AG 9

Release Notes______________________________________________________________

In addition, the "BP role category" and the "BP role grouping category" are introduced,allowing you to program on the BP role or the BP role grouping.

You can define different attributes, such as a business transaction and a business partnercategory, to a BP role category.

You can use the classifying character of the BP role by defining permitted transitions betweenthe individual roles with the help of a "BP role exclusion group". The role exclusion group isalso used to establish that certain BP roles cannot be assigned at the same time to a businesspartner.

You can use the following additional functions for the BP roles in the business partner dialog:

- Overview of all the roles that have been assigned and that are valid on a key date

- Display and maintenance of a validity period for a role

- Deletion of a role assignment

- Where-used list for a roleThe where-used list allows you to check whether it is possible to delete the assignment ofBP roles to business partners, which are part of a business partner relationship. If theseroles are assigned to the relationship category and constitute a prerequisite for creating arelationship, then the assignment cannot be deleted.

- Change history of a role


The introduction of the BP role category means that it is now necessary to extend the interfacefor the corresonding BAPI or API methods.

For this reason, the following new (B)APIs for creating, changing, deleting, reading andchecking the existence of BP roles for a business partner were introduced:

- BUPA_ROLE_ADD_2 (BAPI_BUPA_ROLE_ADD_2)

- BUPA_ROLE_CHANGE (BAPI_BUPA_ROLE_CHANGE)

- BUPA_ROLE_REMOVE (BAPI_BUPA_ROLE_REMOVE)

- BUPA_ROLES_GET_2 (BAPI_BUPA_ROLES_GET_2)

- BUPA_ROLE_EXISTENCE_CHECK_2 (BAPI_BUPA_ROLE_EXIST_CHECK_2)

Since the present (B)APIs still have to be supported for a transitional period, but the inputparameter IV_PARTNERROLE/ BUSINESSPARTNERROLE is interpreted as a BP rolecategory, the new methods are called up by filling in the parameterIV_PARTNERROLECATEGORY (BP role category) within the API method.

The present methods are:

- BUPA_ROLE_ADD

- BUPA_ROLES_GET

______________________________________________________________SAP AG 10

Release Notes______________________________________________________________

- BUPA_ROLE_EXISTENCE_CHECK(Prefix "BAPI_" for the relevant BAPI methods)

The structure for the Direct Input (DI) was extended by adding the relevant fields, in order toenable extended processing of business partner roles from Release 6.40 (deleting or changing thevalidity of a role) also using the DI.The following fields were included in the structure BUS_DI for this purpose:

- RLTP (Role category)

- ROLE (Role)

- VALID_FROM (Start of validity)

- VALID_TO (End of validity)

- CHIND (Change category)


Make the following settings in the Implementation Guide (IMG) in the Customizing of the BasicSettings of the SAP Business Partner under Business Partner Roles:

- Define BP Roles

- Define BP Role Groupings

- Define BP Role Exclusion Groups

1.1.10 High-Performing Search Name/Address (Changed)

Use

From Release 6.40 or 6.20 (SP 19) you can use an improved search for business partners withaddress data.

During the search using the input help "partner by address", it took a long time to get a searchresult when the following conditions occurred:

- Systems that contain many business partners with address data

- Combinations of search criteria that were not refined enough

The performance for this search has now been improved.


If necessary, execute the following reports:

______________________________________________________________SAP AG 11

Release Notes______________________________________________________________

- BPADRSEARCH_FILL

- BPADRSEARCH_DEL

For more information, see SAP note 595442.

If you have used the search only in Release 6.20 up till now, then execute reportBPADRSEARCH_CLIENTSPEC_CONVERT in order to carry out the conversion during theupgrade to Release 6.40.For more information, see SAP note 677269.

1.1.11 Time Dependency for Addresses (New)

Use

From Release 6.40 you can establish validity periods for the following address data:

- Addresses

- Address usages

- Communication data

Time dependency replaces the planned changed function.

Standard addresses are now no longer established through the address overview list, but ratherthrough the time-dependent assignment to the address usage "standard address".

The following additional functions are available to you for the addresses in the business partnerdialog:

- Creating and changing validity periods for

- Addresses

- Address usages

- Communication data

- Creating and changing a standard address through the address usage

- Moving an existing address to a new target address


The BAPIs for the address data ensure that when you compare address data in a data cleansingcase, the validity periods for the address or address usage are transferred correctly.


You can use the following BAPIs for creating, changing, deleting and reading time-dependent

______________________________________________________________SAP AG 12

Release Notes______________________________________________________________

address data:

- BAPI_BUPA_ADDRESS_ADD

- BAPI_BUPA_ADDRESS_CHANGE

- BAPI_BUPA_ADDRESS_REMOVE

- BAPI_BUPA_ADDRESSES_GET

- BAPI_BUPA_ADDRESS_GET_NUMBERS

- BAPI_BUPA_ADDRESS_GETDETAIL

These BAPIs were adapted accordingly and can now also be used for time-dependent data.

The structures for the Direct Input (DI) were extended by adding the relevant fields so that itis also possible to maintain time-dependent address data using the DI.

1.1.12 Time Dependency for Bank Details (New)

Use

From Release 6.40 you can establish validity periods for bank details:

Time dependency replaces the planned changed function.

The following additional functions are available to you for the bank details in the businesspartner dialog:

- Creating and changing validity periods

- Transferring bank details


The BAPIs for the bank details ensure that when you compare bank details in a data cleansingcase, the validity periods are transferred correctly.


You can use the following BAPIs for creating, changing, deleting and reading time-dependentbank details:

- BAPI_BUPA_BANKDETAIL_ADD

- BAPI_BUPA_BANKDETAIL_CHANGE

- BAPI_BUPA_BANKDETAIL_REMOVE

- BAPI_BUPA_BANKDETAIL_GET

______________________________________________________________SAP AG 13

Release Notes______________________________________________________________

- BAPI_BUPA_BANKDETAIL_NUMBERS

- BAPI_BUPA_BANKDETAIL_GETDETAIL

These BAPIs were adapted accordingly and can now also be used for time-dependent data.

The structures for the Direct Input (DI) were extended by adding the relevant fields so that itis also possible to maintain time-dependent bank details using the DI.

1.1.13 CA-BP-BP Data

1.1.13.1 Tax Jurisdictions (Changed)

Use

As of Release 6.40, when you maintain a business partner master record, the systemautomatically proposes a tax jurisdiction.

This feature only applies in countries where taxes are calculated using tax jurisdictions.


To set up the system, carry out the IMG activities in Customizing for Cross-ApplicationComponents, by choosing SAP Business Partner -> Business Partner -> BasicFunctions -> Tax Jurisdictions.

You can still continue to use the tax jurisdictions as defined in view V_TTXJ_CORE_ABA.However, this view has been removed from the IMG, and we recommend that you migrate tothe new solution.

1.1.14 CA-BP-GRH Group Hierarchy

1.1.14.1 Business Partner Group Hierarchy (New)

Use

From Release 6.40 you can use the group hierarchy.

The business partner group hierarchy allows you to map complex organizational structures of a

______________________________________________________________SAP AG 14

Release Notes______________________________________________________________

business partner (for example buying group, cooperative or chain of retail outlets).

You should form groups of business partners (for example for purchasing groups) in order tocreate a hierarchy tree. These groups represent the hierarchy nodes in the hierarchy. Hierarchynodes can be constructed in several stages. You can assign any number of business partners toa hierarchy node. Both the assignment between nodes and the assignment of business partners tonodes is time-dependent.You can create hierarchy trees with different hierarchy categories, via which the usage of agroup hierarchy is established. A business partner can be assigned to several hierarchies.A hierarchy node is always clearly assigned to a hierarchy.

This does not mean that the hierarchy nodes of a business hierarchy are the same as businesspartners, but rather that business partners are merely attached to them. The separation of thehierarchy structure and business partner master data means that dummy business partners are notcreated when a hierarchy is constructed, and that performance is improved.


Make the following settings in the Implementation Guide (IMG) in the Customizing of the SAPBusiness Partner under Business Partner Group Hierarchy:

- Establish Hierarchy Type

1.1.15 CA-BP-RS Relationships

1.1.15.1 Duplicate Check (Extended)

Use

Duplicate Check for Relationships

As of Release 6.40 SP2 you can carry out a duplicate check of the address data for contactperson relationships (CP relationships) and employee relationships, in addition to the check ofthe business partner address data. In this way duplicates can be also be recognized when contactpartners and employees are created or changed.

A duplicate check is carried out in the following cases:

- Duplicate check of the central address data

- When a business partner is created with address data

- When a business partner is changed

- Duplicate address of the address data for relationships

- When a CP relationship (or an employee relationship) is created with a firm's address

______________________________________________________________SAP AG 15

Release Notes______________________________________________________________

The check is carried out only if an address has been assigned.

- When a CP relationship or an employee relationship is changed

Duplicate Check Dialog

A new dialog replaces the dialog currently supplied by a third-party provider. If a duplicate isidentified during one of the above-mentioned activities, a dialog box appears containing therelevant options for processing duplicates.

You can use the following functions in this dialog:

- Navigation to the display of a potential duplicate

- Navigation to the relevant duplicate when you create a business partner or a relationship.You can choose whether you want to save the changes you have made to the businesspartner you are maintaining.

- Creation of a data cleansing case for further processing in transaction BUPA_CLEAR

- Navigation to the display of the relationship for a duplicate in the case of contact personor employee data

- Display of the similarity of the duplicate in percent

You can use the following standard functions of the SAP List Viewer SAP List Viewer (ALV)to adapt the display of the duplicates to your specific requirements:

- Sorting

- Filtering

- Searching

- Hiding columns

- Exporting

- Positioning on the last name

- Layout management

For more information, see the user documentation of the SAP List Viewer.

Hinweis

As is currently the case, a third-party provider tool must be connected to the certified interfaceof the Business Address Services (BAS) for the duplicate check.


The following BAPIs were adapted so that they provide a list of potential duplicates:

- CP relationships

- BAPI_BUPR_CONTP_CREATE

______________________________________________________________SAP AG 16

Release Notes______________________________________________________________

- BAPI_BUPR_CONTP_ADDR_ADD

- BAPI_BUPR_CONTP_ADDR_CHANGE

- Employee relationships

- BAPI_BUPR_EMPLO_CREATE

- BAPI_BUPR_EMPLO_ADDR_ADD

- BAPI_BUPR_EMPLO_ADDR_CHANGE


Ensure that the duplicate check has been activated in both index pools (tables BUT000 andBUT052). For this purpose, make the necessary settings in the Implementation Guide (IMG) inCustomizing of the Address Management under SAP NetWeaver -> SAP Web ApplicationServer -> Basis-Services -> Address Management -> Duplicate Check -> Activate IndexPools for the Duplicate Check .

1.1.15.2 Easy Enhancement Workbench (Extended)

Use

From Release 6.40 SP4 you can also use the EEW to extend the business partner relationships(application object BUPR) for the user interface of the SAP GUI.

Using the EEW, you can add new tables to the data model of the BP relationships.

You can convert extensions to the Business Partner in the BDT, made prior to 6.40 andrestricted to the SAP GUI, to the People-Centric UI.

Note

A BW connection is not planned for the extension of relationships.

______________________________________________________________SAP AG 17

Release Notes______________________________________________________________

1.1.15.3 Relationships (Extended)

Use

Selection Area in the Relationship Overview

From Release 6.40 you can restrict the number of the selected relationships in the list displayin the relationship overview with the help of various selection criteria and combinations thereof,and also display additional data at the same time.

Only the first 200 relationships for a business partner are read by default. If the number ofrelationships exceeds the maximum number of hits, the selection fields are automaticallydisplayed if the user has not already displayed them himself. You can expand or collapse theselection area.

You can restrict the selection of relationships as follows:

- Per relationship category (per tab page in the dialog)

- In the complete list of the overview for all categories

The following selection criteria are available:

- Maximum number of hits

- Names

- Search terms

- ID type and ID number

- Validity (key date or period)

The following criteria are available for the contact person relationship:

- Function

- Department

- VIP data

The standard relationship and the standard communication data, such as fax, telephone ande-mail, are also displayed in the list for the contact person relationship.

Additional fields, which you can choose when you personalize the lists, are available for thedisplay.

Notes

When you switch to a different business partner or another tab page the settings for theselection area (e.g. expanding) are transferred per tab page from last transaction carried out onthe BP in question. When the transaction is called up the next time, the settings in the selectionarea are not transferred.

Personalization of the List Display

You can adapt the display of the relationships to your specific user requirements. The standardfunctions of the SAP List Viewer (ALV) can be used for this purpose.

You can do the following:

______________________________________________________________SAP AG 18

Release Notes______________________________________________________________

- Sort

- Filter

- Search

- Hide columns

- Export

- Position the cursor on the last name

- Manage the layout

For more information, see the user documentation for the SAP List Viewer.

BAdIs for User-Defined Fields

You can use the BAdI BUPR_RELSHP_OVR_EXT to extend the relationship overview byadding your own fields.


You can hide the selection fields in the Implementation Guide (IMG) in the Customizing of theSAP Business Partner under Field Modifications.From Release 6.20 it is possible to hide fields using the IMG activity Configure field attributesfor each client (application object BUPR). Up to Release 6.10 you can use the IMG activityConfigure field attributes for each activity (activity '02: change').

Make the necessary settings for the layout management in the Customizing of the SAPBusiness Partner under Assign layout groups to relationship categories.

Carry out the BAdI implementation for the user-defined fields in the Customizing of the SAPBusiness Partner in the IMG activity BAdI: Extension of the relationship overview.

1.1.16 CA-BP-UI Dialog SAP-GUI

1.1.16.1 Search Helps (Extended)

Use

From Release 6.40 and 6.20 (SP33) on, the following search helps are provided:

- Search using the locator

- By business partner using the address or address version

______________________________________________________________SAP AG 19

Release Notes______________________________________________________________

- Search by fast entry using the input help

- Partners by address versions

As of 6.40 and 6.20 (SP32) you can also use the search Partner by Relationship by fastentry, using the input help.

1.1.16.2 Role Change for Required Entry Fields (New)

Use

From Release 6.40 SP3 you can change to a different BP role when you create or change abusiness partner in the business partner dialog, even if required entry fields exist.In this case a dialog box appears asking you if you want to save the data you have alreadyentered.

1.2 CA-GTF General Application Functions

1.2.1 BAdIs for DME Engine in Application Basis Layer (New)

Use

As of SAP Application Basis 6.40 (SAP_ABA 640), the Implementation Guide contains threeBAdIs (Business Add-Ins) for use with DME Engine format trees in the Application Basis layer.

You can use these BAdIs to process certain types incoming and outgoing DME files in waysnot technically possible with the DME Engine itself. For a list of the DME format trees thatare supported, see the BAdI documentation itself.

______________________________________________________________SAP AG 20

Release Notes______________________________________________________________


You can implement the BAdIs, if required, in Customizing for Cross-ApplicationComponents by choosing General Application Functions -> DME Engine -> BusinessAdd-Ins.

See also

SAP Library -> SAP ERP Central Component -> Financials -> Financial Accounting-> Accounts Payable (FI-AP) -> FI Accounts Receivable and Accounts Payable ->Payments -> Executing the Payment Program -> Payment Medium Workbench ->Data Medium Exchange Engine

1.2.2 CA-GTF-CSC Country-Specific Objects

1.2.2.1 Tax Jurisdictions (Changed)

Use

As of Release 6.40, when you maintain a business partner master record, the systemautomatically proposes a tax jurisdiction.

This feature only applies in countries where taxes are calculated using tax jurisdictions.


To set up the system, carry out the IMG activities in Customizing for Cross-ApplicationComponents, by choosing SAP Business Partner -> Business Partner -> BasicFunctions -> Tax Jurisdictions.

You can still continue to use the tax jurisdictions as defined in view V_TTXJ_CORE_ABA.However, this view has been removed from the IMG, and we recommend that you migrate tothe new solution.

1.2.3 CA-GTF-IL Relationships Between Objects with GUIDIdentificat

1.2.3.1 Customizing Relationship Types (Changed)

______________________________________________________________SAP AG 21

Release Notes______________________________________________________________

Use

Customizing relationship types has been changed as follows for SP01.

- The indicator GEN_FLG has been added as another field

Client

The client field has been removed. The client is no longer needed in Customizing and wastherefore taken out. The previous Customizing tables have been replaced by the following, newCustomizing tables:

DDIC-Type Previous Object Replaced by New Object

Database Table COMC_IL_RELTYPE COMC_IL_TYPE

Database Table COMC_IL_OBJTYPE COMC_IL_OTYPE

Database Table COMC_IL_TYPE_TXT COMC_IL_TYPE_T

Structure COMT_IL_TYPE

Table Type COMT_IL_TYPE_TAB

Structure COMT_IL_TYPE_T

Table Type COMT_IL_TYPE_T_TAB

Maintenance View COMV_IL_RELTYPE COMV_IL_TYPE

Maintenance View COMV_IL_TYPE_TXT COMV_IL_TYPE_T

Maintenance View COMV_IL_OBJTYPE COMV_IL_OTYPE

The previous Customizing tables and their relevant DDIC objects have, however, not beendeleted and as a precaution still contain the standard SAP data.

If you have programmed on these structures and DDIC objects, you should convert the code tothe new structures, table types or database tables. Please note that not every new table type ornew structure has an old object.

Differentiation Key (KEYTYPE_ID)

The differentiation key has been added as another field. This field contains the ID for the key.This field should not be filled, however, as it currently not used in processes. It therefore hasno further impact.

Indicator 'Generated' (GEN_FLG)

The indicator GEN_FLG has been added as another field. This indicates whether a relationshiptype has been generated manually or via a generation report. This indicator should not be filled.Generation will be realized at a later date and the indicator will be used then. It therefore hasno further impact.


Relationship-type master-data is not affected by the changes.


Data transfer is not affected by the changes.

______________________________________________________________SAP AG 22

Release Notes______________________________________________________________


If you have made no changes to the Customizing of relationship types, then no action isnecessary.

If you have defined your own relationship types or removed SAP relationship types, then youhave to convert the Customizing data of the old tables to the new tables. Use the reportCOM_IL_CUSTOMIZING_TRANSFER to do this, it transfers the data to the new tables. Inthis way the total quantity is combined from all clients.

If you want to transport the data, you can use the maintenance views listed in the table, byexecuting transaction SM30.

1.3 CA-PRO Central Part of Product Master

1.3.1 Archiving Functionality for SAP Products (New)

Use

As of Release 6.40, archiving functionality is available for SAP Products, thus providingarchiving and deletion functionality for all SAP product data (in systems such as CRM, SRM)using archiving object PRODUCT_MD.

Two options are available when working with systems with SAP Basis 6.40:

1. Continue working with the SAP Products-specific archiving tools of the archiving objectPRODUCT_MD (preprocessing, writing to the archive, releasing SAP product data fordeletion, and physically deleting the archived data):

- There are no functional changes or restrictions after upgrading

- No additional measures are required to be able to continue working with transactionSARA and archiving object PRODUCT_MD, which takes you to the archivingfunctionality for SAP product data.

2. Work with Archive Development Kit (ADK) object-independent tools for preprocessing(check and verification functionality) and postprocessing (physical deletion of archivedproducts). If you wish to use the ADK object-independent tools for preprocessing andpostprocessing purposes, meaning that you no longer work on an archiving object-specificbasis, SAP recommends that you switch from the old cross-archiving object tools in CRMto the new ADK object-independent tools for preprocessing and postprocessing.If you choose to work with the new cross-archiving object tools provided by the ADK forpreprocessing and postprocessing, there are a number of changes to take into account:

- Customizing transaction DACONTROL is now called DA_CONTROL (Customizingtable CRG_ARCHOBJ now ARCHDEL_OBJ).Customizing entries may need to be adjusted in table ARCHDEL_OBJ, compare withCRG_ARCHOBJ (see also last point below).

______________________________________________________________SAP AG 23

Release Notes______________________________________________________________

- ADK reports DARGE_VERIFY_PARA and DARGE_DELETE_OBJECTS have beenreplaced by ARCDEL_VERIFY_PARA and ARCDEL_DELETE_PARA.Any preprocessing or postprocessing jobs scheduled using transaction SM36 and theold ADK reports may have to be changed after an upgrade so that the correct reportsare used.

- The new cross-archiving object tools provided by the ADK for preprocessing andpostprocessing are available using transaction SARA.When using transaction SARA with archiving object PRODUCT_MD, the ADK nowgenerates a Check/Delete button if it finds that there are new Customizing entries intable ARCHDEL_OBJ. This function includes the cross-archiving object check anddeletion programs ARCDEL_VERIFY_PARA and ARCDEL_DELETE_PARA.

1.3.2 CA-PRO-SET Set Types and Attributes

1.3.2.1 Multi-value attributes without Product Modeling Engine (PME) (New)

Use

Multiple-value attributes in SAP Product were previously administered via the PME. Theadministration of multiple-value attributes has been decoupled from the PME in this release, sothat applications of SAP Product can use multiple-value attributes without PME. Installing PMEis no longer necessary to define multiple-value attributes in SAP Product.

This change has an affect on the maintenance of set types. When assigning set types tocategories, there are no longer restrictions for set types that have multiple-value attributesassigned to them.

-

To save the meta data for multiple-value attributes directly in the application, the tableCOMC_ATTRIBUTE was extended by the following three fields:

- DB_TABLEThis field contains those database table names generated by the system in which the datafor the multiple-value attributes is stored. The name of the database table does not containthe attribute ID as part of its name component.

- DB_HIST_TABLEThis field contains those database table names generated by the system in which all valuesever taken by the multiple-value attribute, is stored. Ins this respect this database tablecontains the history of the multiple-value attribute. The name of the database table does not

______________________________________________________________SAP AG 24

Release Notes______________________________________________________________

ot contain the attribute ID as part of its name component.

- CLASS_NAMEThis field contains the name of the class generated by the system, in which the methodsfor reading and writing the data for the multiple-value attribute are stored. The name ofthe class contains the attribute ID as part of its name component and follows the namingconvention:

- ZL_<ATTRIBUTE_ID>_DB for the customer system

- CL_<ATTRIBUTE_ID>_DB for the SAP development system


In the system table COMS_SETTYPE_CON the parameter MV_ATTR_DB for the object typeBUS1178 controls whether the use of multiple-value attributes without PME is active orinactive.

The parameter can have the following values:

- Value X = active

- No value = inactive

______________________________________________________________SAP AG 25

Release Notes______________________________________________________________

release notes for sap netweaver 04 cross-application ... recommend that you first execute the report...

Documents