Contract Accounts Receivable and Payable (FI-CA)

Contract Accounts Receivable and PayablePurposeContract Accounts Receivable and Payable (FI-CA) is a subledger accounting for processing large document volumes and realizes the typical accounts receivable functions.It is an integral component of the mySAP Financials solution and can be integrated with this and other solutions for additional tasks.

FeaturesContract Accounts Receivable and Payable covers the following components:1. Basic Functions1. Business Transactions1. Integration1. Closing Operations1. Information System1. Job Control1. European Monetary Union and Contract Accounts Receivable and Payable1. Archiving1. Contract Accounts Receivable and Payable: InterfacesFor Contract Accounts Receivable and Payable you can use the area menu FSCCAX.

Basic FunctionsPurposeYou use this component to enter your basic settings for master data and to post and process documents. You can also use it to create and process master data, and to post and process documents manually.Implementation ConsiderationsYou must implement all the components listed below.FeaturesThis component consists of the following detailed components:SAP Business PartnerBusiness Data ToolsetContract AccountsPostings and DocumentsTax Postings Open Item ManagementAccount Balance Display Print WorkbenchCorrespondenceCustomer Contacts

SAP Business Partner (SAP BP)PurposeThe component SAP Business Partner enables you to create and manage business partners centrally. This is of prime interest if a business partner plays different roles for a company, such as sold-to party and ship-to party.SAP Business Partner is designed to utilize technical benefits such as data integrity and freedom from data redundancy, and to place greater emphasis on aspects relating to customer maintenance and acquisition of new customers. FeaturesYou can create a business partner in different business partner roles, and during the course of the business relationship the business partner can assume other business partner roles. No new data has to be created each time, meaning that redundant data creation and retention is avoided, and there can be no inconsistencies. By using SAP Business Partner, it is possible to merge the partner data already held by a company in more than one system in such a way that the potential for new contracts within the same customer contact can be identified. When you enter data, the central data related to SAP Business Partner, and the application-specific data are integrated seamlessly on the processing screen. Seamless integration of customer-specific data is possible without modification, ensuring full future maintenance, because defined interfaces exist for this purpose.

SAP Business Partner (SAP BP)PurposeThe component SAP Business Partner enables you to create and manage business partners centrally. This is of prime interest if a business partner plays different roles for a company, such as sold-to party and ship-to party.SAP Business Partner is designed to utilize technical benefits such as data integrity and freedom from data redundancy, and to place greater emphasis on aspects relating to customer maintenance and acquisition of new customers. FeaturesYou can create a business partner in different business partner roles, and during the course of the business relationship the business partner can assume other business partner roles. No new data has to be created each time, meaning that redundant data creation and retention is avoided, and there can be no inconsistencies. By using SAP Business Partner, it is possible to merge the partner data already held by a company in more than one system in such a way that the potential for new contracts within the same customer contact can be identified. When you enter data, the central data related to SAP Business Partner, and the application-specific data are integrated seamlessly on the processing screen. Seamless integration of customer-specific data is possible without modification, ensuring full future maintenance, because defined interfaces exist for this purpose.

General InformationIn the following sections you find general information, which helps you in your work with the interface of the Business Partner dialog and gives you basic information about the processing of business partners: Locator Interface Elements in Business Partner Settings Business Partner Category Creating Business Partners Displaying/Changing Business Partners

LocatorDefinitionThe locator allows you to search for business partners.

StructureIt consists of a tab with the tab pages Worklist and Search and can be displayed in various different ways, according to the setting made when you logged on to the system.You can choose one of the following settings: NarrowThe locator is found in the left-hand screen area, and is thus available in parallel to the business partner dialog in the work area. Full screenThe locator is displayed on the entire screen. When you select a business partner you reach the business partner dialog, which is also displayed on the entire screen. HiddenThe business partner dialog is started without the locator and is displayed on the entire screen.You can use pushbuttons on the left-hand edge of the screen to make the locator narrower and wider, and can choose various intermediate stages between the narrow and full screen locator. You can also switch directly to the full screen locator. You can switch the locator on and off in order to enlarge the work area on your screen. To do this you choose the button Show/Hide Locator. Tab Page FindYou can search for business partners and business partner categories (person, organization, group) by means of the tab page Find.You can limit the search using various search criteria like number or search term. The hits are listed in the hit list beneath the search area. The hit list allows you to make a multiple selection.Via the pushbutton Add to My Objects, you can transfer the selected business partners to the list of your personal objects on the tab page Worklist.From the hit list you can go directly to the processing of the business partners, using the pushbutton Choose.Tab Page WorklistThe tab page Worklist contains a list with selected objects. You can display the following objects: the business partners that were processed lastThe history can be used for all transactions: When you leave the business partner dialog, the last ten search requests are saved. selected business partners that you have added to the list of your personal objectsYou can add or remove one or more business partners from the hit lists of your personal objects. You can branch directly to the display or change mode from the respective hit list.

Interface Elements in Business Partner

UseYou use Business Partner interface elements to search for, display or process business partners.

StructureTabsThere are two tabs for processing business partners in the business partner dialog.The tab for the General Data can contain the following tab pages: Address Address Overview Identification Control Payment Transactions Status

The contents of the tab pages depend on the settings in the Customizing and the role of the business partner that you are processing.The pushbutton Relationships brings you to the processing of the business partner relationships.

Additional Elements of the Business Partner Dialog Business partner dialog (general)You can always use fast entry to call up a business partner via the application toolbar. You can also create a new business via pushbuttons. You can switch by means of pushbuttons from one business partner to the other business partners that have you have just processed.If you do not use the full screen locator, the last-maintained business partner is selected when you restart the business partner dialog after having left it. In addition, the last-maintained role and tab page are displayed.In the area above the tab, you can always see the following during processing: the business partner number the business partner category (as an icon) the business partner roleRoles that are maintained or newly created for a business partner are correspondingly indicated in the change mode.In addition, the mode in which you are working is displayed in the title bar.

You can switch between display and change mode by means of a pushbutton.For more information on creating and processing business partners, see Creating Business Partners Displaying/Changing Business Partners

Navigation in Business PartnerYou can switch to other roles without exiting the processing of the given business partner. General data and relationships for a business partner are displayed and processed in separate tabs, but are saved together. You can navigate by means of a pushbutton to the dialog for the relationships.For more information on business partner relationships, see Business Partner Relationships

Change historyYou can display a change history for the following objects: Partner FieldYou can also display a history according to periods.

SettingsUnder Settings you can make general settings for displaying the interface, and you can also get an overview of your authorizations.

SettingsDefinitionWith the pushbutton Settings or via the menu entry Extras -> Settings you make the settings that help you in your work with the Business Partner interface.

StructureThe dialog box Settings consists of the tab pages General and Authorization Overview.On the tab page General you determine the settings that you already want to have each time you log on to the system. The system saves these settings under your user name, so that the same settings are already there each time you log on to the system.You can choose the following options for the initial screen of the business partner dialog and of the business partner relationship processing: Display Change Setting last selectedYou can set an indicator in order to receive a security check when you create a business partner in a different role be able to sort the relevant list when you mark a column heading You can select the following display options for the locator: Narrow Full screen HiddenOn the tab page Authorization Overview you can display your authorizations for the various activities during the processing of business partners: for each business partner category for each business partner role for each business partner relationship category

Business Partner Category

DefinitionThe business partner category denotes whether a business partner is a natural person (private individual), organization (legal person/entity or part of a legal entity, such as a department), or a group.

UseWhen you create a business partner, you have to select a business partner category. Depending on the business partner category, a certain set of fields has to be filled with data. For example, if you are creating a business partner as an organization, you can enter the legal form and industry, whereas in the case of a person you can enter first names, name affixes, gender and so on.

StructureThe standard business partner categories are: Natural person (private individual) Organization (e.g. company, department in a company, club, association) Group (e.g. married couple, shared living arrangement)It is not possible to create any other business partner categories. You cannot alter the business partner category at a later stage.

Creating Business Partners

PrerequisitesThe initial screen for maintaining a business partner depends on the Settings you have chosen for the initial screen leading into the business partner dialog. For more information, see Settings.

ProcedureYou are in the Business Partner dialog.1. Select a business partner category in the application toolbar. 2. Specify the role in which you wish to create the business partner. With the BP role "contact person" the business partner category "person" is default. 3. Select a grouping. Each grouping is assigned to a number range.

If a grouping has been defined as a standard grouping in Customizing, this grouping is chosen automatically. If you want to assign the business partner to a grouping that is different to the standard grouping, then you should select the grouping you require.If you select a grouping with internal number assignment, you do not need to enter a business partner number. This is created automatically by the system.If you select a grouping with external number assignment, you need to enter a business partner number. 4. Enter the required data for the business partner in the tab pages. Fill the appropriate required entry fields. 5. Choose Save.ResultYou have created a business partner in the role you selected.

Displaying/Changing Business Partners

PrerequisitesThe initial screen for maintaining a business partner depends on the Settings you have chosen for the initial screen leading into the business partner dialog. For more information, see Settings.The business partner whose data you want to display or change must already exist in the system.

ProcedureYou are in the display or change mode of the Business Partner dialog.1. Select a business partner via. the button Open in the application toolbar the tab page Search of the locator the tab page Worklist of the locator2. Select the relevant tab page on which you want to display or change data.Make the necessary changes.3. Save your changes.

ResultYou have displayed or changed the data of a business partner.

Business Partner Role (BP Role)

DefinitionThe basis for the definition of a BP role is a business transaction. The attributes of the BP role depend on the particular transaction involved.

ExampleTransactionBP Role

OrderSold-to party

Delivery of goodsShip-to party

UseThe standard BP roles are: Contact person Prospect Business partner, general Employee Organizational unit Internet userIn addition there are component-specific BP roles such as: IS-U: Contract partner, installer IS-IS-CD: Contract partner BCA: Account maintenance officer, account holder, authorized drawer, bank statement recipient CRM: Sold-to party, ship-to party B2B: Bidder, portal providerIt is possible to create a business partner in one or more BP roles. Central data such as name, addresses and bank details only has to be created once.

StructureAll the supplied business partner roles are displayed for selection in the Business Partner dialog.If you want only certain business partner roles to be displayed in the selection list, you can hide the other business partner roles. In the same way, you can replace the standard title of BP roles with user-defined descriptions, and establish at which point the relevant BP role should appear in the selection list.Make these settings in the SAP Reference IMG under Cross-Application Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Business Partner Roles -> Properties of Business Partner Roles.With the help of field groupings in the Customizing you can hide or display fields for this role.An extension of the BP roles to include customer-specific attributes is possible. In theory it is possible to define other BP roles but this should only be considered if a customer has developed own applications. For more information, see the Business Data Toolset.

BP Role Business Partner, General

DefinitionThe BP role business partner, general is not specified in any direction. Data entered in this BP role is for information purposes only.

UseYou use the BP role business partner, general to store data on a business partner who does not (yet) play any specific role for the company. For example, at a meeting you are given a persons business card. You might want to store this data without pursuing a specific business interest. In this case you can use the BP role business partner, general .

StructureYou can store the name and address as well as data on bank details and relationships. If a business relationship does materialize with a business partner created in this BP role, you can also create this business partner additionally in other, specific BP roles such as sold-to party . Conversely, it is not possible to take a business partner who has already been created in a specific role and add the role of business partner, general . This is because a business partner created in another role automatically receives the role of business partner, general .

BP Role Contact Person

DefinitionA business partner in the BP role of contact person acts as intermediary to an organization with which business contact is maintained.

StructureWith the BP role contact person you can enter data on name, address and relationships but not on bank details and payment cards.

IntegrationTo map a "is contact person for" relationship, you must have created one business partner as an organization, person, or group, and another business partner as a person.

BP Role Prospect

DefinitionA prospect is a potential customer.

UseThe BP role prospect is a suitable option for a possible future business partner with whom just a first loose contact has been made. In this way this business partner can be provided with information on a product, for instance.

StructureFor the BP role prospect you can define the name and address and control data.

BP Role Employee

DefinitionThe BP role Employee is the term for someone who works in your own company.

UseIf a company has business relations with one of its own employees, you can enter data on this business partner in the BP role Employee.

StructureIn addition to the corresponding master data, you can also define the user number and personnel number of the employee for the BP role of Employee.

IntegrationIf you use the SAP HR component, the system creates the relationship to the HR object Central person and checks entries.

BP Role Organizational Unit

DefinitionThe BP role Organizational unit maps units of internal structures in your own company.

UseFor example, if two organizational units in your company with different company codes have business relations with one another, you can enter these units in the BP role Organizational unit.

StructureYou must create the business partners in the role of Organizational unit in Organizational Management. This means that you have to maintain data on the name and address in Organizational Management as well. The corresponding fields are not ready for input in Business Partner.If the role of Organizational unit exists in Organizational Management, you can enter changes to other master data, such as bank details, in Business Partner.

BP Role Internet User

DefinitionWith the BP role Internet user you can define user-specific attributes of a business partner of the category person.

UseIn the BP role Internet user, you store the data for a business partner. Using this data the business partner can log on to your system via the Internet. For this purpose he has chosen a name that differs from his user name. You therefore also have the possibility to identify this business partner via his Internet user.

StructureYou can store user data, like Internet user, user name, password, block and user group, in the dialog of the SAP Business Partner on the tab page Internet user.In addition you can maintain user roles and fixed values, for example logon language and date format, for an Internet user.

BP Role Grouping

DefinitionMerging of several BP roles to simplify data maintenance.

UseTo simplify data maintenance you can merge individual BP roles into a BP role grouping. In this way it is possible to create a business partner in a BP role grouping and thus in the BP roles belonging to this grouping. Example: From the point of view of SAP BP, the customer in the classical area of FI has the BP roles invoice recipient, payer, dunning recipient and correspondence recipient. If you want to manage and maintain a customer (debtor) with the help of SAP BP, the best option is to select a BP role grouping that incorporates the above-mentioned BP roles.

StructureYou can define the screen structure and screen sequence for each BP role grouping individually.

Address Data

DefinitionThe entry and administration of address data of a business partner.

UseYou can create one or more addresses for each business partner. When you enter a gender-specific form of address (e.g. Mr., Mrs.) or change the form of address, the assignment of the gender is automatically adapted on the tab page Identification. If you enter only one address per business partner, this is used for all activities. If you create multiple addresses, you can define when they should be used (for example, use of a certain address as the delivery address).Based on the address usage that you have established, the automatic address determination recognizes which address is used for which business activity.You can create several international address versions for an address. This allows you to format address, communication data and also name fields (e.g. first and last name, academic title, etc.) for all business partners in different fonts, each with its own character set.In order to be able to use the international address versions, you have to activate them in the Customizing.The SAP regional structure checks whether the address data (postal code, city and street) is correct. For more information see Checks against the SAP regional structure.Furthermore, the Business Address Services (BAS) make interfaces available for connecting postal checks of external providers. For more information, see Postal check and Duplicate check and error-tolerant search.

Structure If you only require one address for each business partner, you can enter the address data in the tab page Address on the maintenance screen Standard Address. This address will be used for all activities. If you require several addresses for a business partner, you enter the standard address in the tab page Address and enter other addresses in the tab page Address Overview. You assign the address usage in the tab page Address Overview on the maintenance screen Address Usages.

IntegrationIn Customizing you define the activities and address types, and establish whether several addresses may be assigned to an address type. In addition, you can assign activities to certain address types. (See IMG: SAP Customizing IMG -> Cross-Application Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Address Determination).Make the settings for the dependency of the fields Title and Gender in the SAP Customizing IMG under SAP Web Application Server -> Basis-Services -> Address Management -> Maintain Title Texts.Activate the international address versions that you require in the SAP Customizing IMG -> SAP Web Application Server -> Basis-Services -> Address Management -> Activate International Address Versions.

Creating Other Addresses

PrerequisitesYou are in the Business Partner maintenance dialog in the Create or Change mode.

Procedure1. Choose the Address Overview tab page. The Address Overview maintenance screen appears. 2. Choose Create. The maintenance screen for entering address data appears. 3. Enter the address data and choose Continue. 4. Enter additional addresses if necessary and save your data.

ResultYou have created one or more addresses. Via the pushbutton Change history you can display the change information for an address.Assigning Address UsagePrerequisitesYou have created several addresses.

Procedure1. Choose the Address overview tab page in the Business Partner maintenance dialog. The Address usages maintenance screen appears. 2. Select an address type (for example, delivery address) and then choose Create. 3. Select the corresponding address in the dialog box and then choose Continue. You have assigned an address to an address usage. The selected address is identified as standard usage.If you have assigned several addresses to an address type, the indicator Standard appears next to the first address entered. If you wish to define a different address as the standard usage for the address type, select the desired address and choose Standard. 4. Save your data.

ResultYou have assigned one or more addresses to an address usage.

ExampleIn addition to the standard address you require addresses for certain activities. For example, with a business partner you want to send letters to a different address to the one used for deliveries. In Customizing you have to define the address types Correspondence address and Delivery address.You assign the address to which letters should be sent to the address type Correspondence address, and the address to which deliveries should be sent to the address type Delivery address. Assigning Address Usage

PrerequisitesYou have created several addresses.

Procedure1. Choose the Address overview tab page in the Business Partner maintenance dialog. The Address usages maintenance screen appears. 2. Select an address type (for example, delivery address) and then choose Create. 3. Select the corresponding address in the dialog box and then choose Continue. You have assigned an address to an address usage. The selected address is identified as standard usage.If you have assigned several addresses to an address type, the indicator Standard appears next to the first address entered. If you wish to define a different address as the standard usage for the address type, select the desired address and choose Standard. 4. Save your data.

ResultYou have assigned one or more addresses to an address usage.

ExampleIn addition to the standard address you require addresses for certain activities. For example, with a business partner you want to send letters to a different address to the one used for deliveries. In Customizing you have to define the address types Correspondence address and Delivery address.You assign the address to which letters should be sent to the address type Correspondence address, and the address to which deliveries should be sent to the address type Delivery address.

Converting Communication Data

UseIf you have created a business partner with only address-independent communication data and then define an address for this business partner, you have the possibility to convert the address-independent communication data into address-dependent communication data.In the same way you can convert address-dependent communication data into address-independent communication data. This is the case, for example, if several addresses are defined for a business partner, and the mobile phone number of the business partner should be applicable to both addresses.

PrerequisitesIf you want to convert address-independent communication data into address-dependent communication data you must have created at least one address and have made one or more entries in the address-independent communication data of the required business partner.In order to convert address-dependent communication data into address-independent communication data, you must have made one or more entries in the address-dependent communication data.

You can preset a country key so that you do not have to enter the country key for each entry that you make for the address-independent communication data. To do this, choose System User Profile Own Data in the menu, and enter the parameter LND on the tab page Parameters and also a valid country key as a value.

Converting Address-Independent Communication DataYou are in the General Data of the business partner on the tab page Address and want to convert address-independent communication data into address-dependent communication data.1. Choose Independent Dependent. A dialog box appears.2. Select the required entry or entries and the address to which you want to assign the communication data by holding down the control key on you keyboard. 3. Choose Continue.The entries you have selected are converted into address-dependent communication data.

Converting Address-Dependent Communication DataYou are in the General Data of the business partner on the tab page Address and want to convert address-dependent communication data into address-independent communication data.1. Choose Dependent Independent. A dialog box appears.2. Select the required entry or entries in the communication data by holding down the control key on you keyboard. 3. Choose Continue.The entries you have selected are converted into address-independent communication data.

Bank DetailsUseYou can enter any number of bank details for each business partner.

IntegrationBank master data can imported to the database from an external data medium with the aid of read programs. (See IMG: Financial Accounting Bank Accounting Bank Accounts Transfer Data to Bank Directory).You can transfer international bank account numbers (IBAN) into the SAP System with the help of BAPIs.

PrerequisitesThe corresponding fields have been assigned to the BP role.

FeaturesWith the help of bank data you can uniquely identify the bank and the account in the system. If the bank referred to does not yet exist in the system, create this with the bank details.Futhermore you have the possibility to define international bank account numbers (IBAN) at the bank details. This is an internationally valid ID number for bank details, which consists of a combination of the country key of the bank (ISO code), a two-character check digit and a country-specific account number. The maximum length of the IBAN is 34 alphanumeric characters and varies from country to country . You can generate an IBAN for bank details and transfer it to your bank data derive bank details from an IBAN that you know of, and enter the relevant bank details IDYou can recognize that an international bank account number has been defined by the change in color of the icon in the column IBAN.Via the pushbutton Change history you can display the change information for bank details.

Payment CardsDefinitionThe entry and administration of payment cards of a business partner.

UseYou can enter any number of payment cards for a business partner. A payment card can be assigned to one or more persons.You assign the payment cards to the business partner in the dialog of the SAP Business Partner on the tab page Payment Transactions.

StructureEnter a payment card ID via which the payment card details for a business partner can be uniquely identified.State the payment card type and enter the relevant card number.You can identify the payment card that a business partner mainly uses as the standard payment card.Via the pushbutton Change history you can display the change information for payment card details.Make the settings for payment card type, payment card category and payment card blocks in the SAP Reference IMG under Cross-Application Components Payment Cards.

Identification Numbers

DefinitionKey figure for identifying a business partner.

UseYou can enter as many identification numbers as you like for each business partner during maintenance, in order to determine a business partner as precisely as possible. Select the corresponding identification number type using the F4 help, and assign the identification number.In addition, you can use the search help to determine a business partner by means of identification number or identification number type.Via the pushbutton Change history you can display the change information for an identification number.

IntegrationDuring the customizing you are free to choose which identification number type you set, for example: Dun & Bradstreet number, ID card, passport, drivers license, etc. (See IMG: SAP Business Partner -> Business Partner -> Basic Settings -> Identification Numbers -> Identification Number Types).

Status Management

DefinitionThis allows you to display and manage the various statuses of a business partner. Changes to the status are stored in change documents.

UseYou carry out the status management in the dialog of the SAP Business Partner on the tab page Status. You have the possibility to define and assign the user status freely.To do this you define a status profile in the Customizing to which you can assign several user statuses. According to the settings you have made in the Customizing, the user statuses of the status profile assigned to the object type are offered to you for selection. For more information on the status profile, see the documentation of the Implementation Guide for the SAP Business Partner under Basic Settings Status Management.

See also: Assigning User Status

Assigning User StatusPrerequisitesYou have defined at least one status profile in the Customizing, to which several user statuses have been assigned.

ProcedureYou are in the general data of the SAP Business Partner on the tab page Status.Before you can define user statuses for a business partner, you must assign a status profile to the business partner. The procedure depends on whether you have already assigned a status profile to a business partner.

Assign a status profile and user status1. If you have not yet assigned a status profile to the business partner, you choose Assign status profile. You reach the dialog box Status profile selection. Assign a status profile to the business partner in order to be able to define a required user status for the business partner.

You can assign only one status profile to a business partner. It is not possible to cancel this assignment at a later date.2. After the assignment of a status profile, you reach a dialog box in which the defined user statuses are displayed for selection. Select the required user status and transfer it.You have assigned a status to a business partner.

User statuses to which no status number has been assigned in the Customizing can be set at any time and can also be cancelled. On the other hand, user statuses that have status numbers cannot be deleted, but can be replaced only by other user statuses of the same numbering scheme.For more information on the status profile, see the documentation of the Implementation Guide for the SAP Business Partner under Basic Settings Status Profile.

Assign or change user status1. If you have already assigned a status profile to a business partner and want to change the user status, choose Insert status. You reach a dialog box in which the defined user statuses are displayed for selection. 2. Select the required user status and copy it.You have assigned a status to a business partner.

Assignment of Industries

DefinitionCategorization of business partners according to industries.

UseDuring business partner maintenance, you can assign a business partner to various industries, after making the corresponding settings for these industries in the Customizing. The assignment of business partners to industries provides you with an additional means of identifying business partners if you, depending on your application, want to create mailing lists, for example, or to carry out statistical surveys according to industries.

IntegrationYou can make the industry assignment of business partners for several industry systems at the same time. In turn, you can assign as many industries as you like to an industry system.You can select the industry system with which you mainly work as the standard industry system. This is then automatically displayed in the Business Partner dialog. For additional information on industry systems and industries, see the SAP Customizing IMG under Cross-Application Components ->SAP Business Partner -> Business Partner -> Organizations -> Maintain Industry Systems and Industries.

See also:Assigning an Industry

Assigning an Industry

UseYou assign business partners to one or more industries, in order to categorize these business partners.

PrerequisitesYou have defined at least one industry system in the Customizing, to which you have assigned several industries.

Procedure1. Choose the tab page Identification in the processing screen Change organization. If you have defined an industry system as the standard industry system in the Customizing, this will be displayed automatically in the Business Partner dialog.If you have defined several industry systems, you can display them with the pushbutton All industry systems. 2. Select the required industry using the F4 help and assign it to the business partner. When you call up the input help, the hierarchical presentation of the industry system that is defined in the Customizing is displayed.If you have not selected an industry system, the description of the industry and the relevant industry system is completed automatically by the system when you select the industry.3. If the selected industry is the standard industry of the business partner, you should set the corresponding indicator. You should always identify one industry as the standard industry in the standard industry system.4. Save your entries.

ResultYou have assigned a business partner of the category organization to one or more industries.Via the pushbutton Change history you can display the change information for an industry within an industry system.

Business Partner Relationships

DefinitionA business partner relationship maps the business-relevant connection between two business partners. The Business Partner Relationship Category describes the characteristics of the business partner relationship.

UseIn order to create a relationship between two business partners you have to assign a business partner relationship category to the business partner relationship. If the relationship category has been assigned, then the two business partners are said to have this relationship. You can assign attributes to a relationship, meaning that redundant data retention is avoided.

StructureYou can limit a relationship in time by entering the start date and end date of the relationship. This means that it is possible to get an overview of the periods in which certain business partners were contact persons for a company, for example.

ExampleIf a business partner is both the purchasing manager of company A and also the MRP controller of company B, the attributes that this business partner has as purchasing manager and as MRP controller (such as department, function, power of attorney) can be defined in the relevant relationships. If you were unable to assign any attributes to a relationship, you would have to create the business partner twice so that you could uniquely assign the corresponding data to the business partner.

Business Partner Relationship Category

DefinitionThe business partner relationship category determines the business-relevant characteristics of a relationship between business partners.

UseWith the help of relationship categories you can define temporary contact persons and contact persons for a company, as well as certain data on members of a shared living arrangement or marriage. The latter might be necessary for liability reasons. Relationship is the term used if a relationship category contains information on concrete business partners.The business partner relationship categories that can be selected depend on the business partner category and on the BP role. A distinction is made between one-way (unidirectional) and two-way (bi-directional) relationship categories. In the case of a one-way relationship category, a relationship exists from a business partner (1) to a business partner (2), but not the other way round.E.g.: The enterprise Miller & Co (BP 1) has the employee Mr. Smith (BP 2); Mr. Smith however does not have the employee Miller & Co. In the case of a two-way relationship category, a relationship exists from a business partner (1) to a business partner (2), and the other way round.E.g.: Mr. and Mrs. Meyer are married. Thus Mrs. Meyer is married to Mr. Meyer and Mr. Meyer is married to Mrs. Meyer.The standard relationship categories are: is contact person for is married to is temporary contact person for belongs to a shared living arrangement is identical to has the employee has the employee responsible is shareholder of is replaced by

StructureIn the dialog, all the supplied business partner relationship categories are displayed for selection in the relationship overview. If you want only certain business partner relationship categories to be displayed in the selection list, you can hide the other business partner relationship categories. In the same way, you can replace the standard title and the standard description of business partner relationship categories with user-defined descriptions, and establish at which point the relevant business partner relationship category should appear in the selection list. In this way you also determine the order of the relationship category-specific tab pages in the BP maintenance.Make these settings in the SAP Reference IMG under Cross-Application Components -> SAP Business Partner -> Business Partner Relationships -> Basic Settings -> Properties of Business Partner Relationship Categories.With the help of field groupings in the Customizing you can hide or display fields.An extension of the relationship categories to include attributes is possible. You can also create your own relationship categories.

Creating Relationships (Integrated Maintenance)

PrerequisitesThe business partner for whom you want to create a relationship must already exist in the system. The initial screen for Business Partner relationship maintenance depends on the Settings you have chosen. For more information, see Settings.

Procedure1. You are in the General Data of a business partner. Choose the pushbutton Relationships in order to create a business partner relationship. You reach the Overview for the business partner relationships.or1. You are in the Overview for the relationships.2. Choose the relationship category, and enter the number of the business partner for which you want to create a relationship.

You can establish a time limit for some relationship categories, for example is shareholder of, is married to, belongs to shared living arrangement. 3. Choose Create.

If you want to create additional relationships, for the selected relationship category, then enter the corresponding business partner number and choose Create. for a different relationship category, then select the required relationship category, enter the corresponding business partner number and choose Create.4. Maintain the detailed data, if necessary. The relationship is included in the overview.5. Save your entries.

ResultYou have created one or more relationships.

Creating Relationships (Integrated Maintenance)

PrerequisitesThe business partner for whom you want to create a relationship must already exist in the system. The initial screen for Business Partner relationship maintenance depends on the Settings you have chosen. For more information, see Settings.

Procedure1. You are in the General Data of a business partner. Choose the pushbutton Relationships in order to create a business partner relationship. You reach the Overview for the business partner relationships.or1. You are in the Overview for the relationships.2. Choose the relationship category, and enter the number of the business partner for which you want to create a relationship.

You can establish a time limit for some relationship categories, for example is shareholder of, is married to, belongs to shared living arrangement. 3. Choose Create.

If you want to create additional relationships, for the selected relationship category, then enter the corresponding business partner number and choose Create. for a different relationship category, then select the required relationship category, enter the corresponding business partner number and choose Create.4. Maintain the detailed data, if necessary. The relationship is included in the overview.5. Save your entries.

ResultYou have created one or more relationships.

Changing Relationships (Integrated Maintenance)

PrerequisitesThe business partner relationship that you want to change must already exist in the system.The initial screen for Business Partner relationship maintenance depends on the Settings you have chosen.For more information, see Settings.

Procedure1. You are in the General Data of a business partner.Choose the pushbutton Relationships in order to change a business partner relationship.You reach the Overview for the business partner relationships.or1. You are in the Overview for the relationships.Enter the business partner number of the business partner whose relationships you want to process, and copy your entry.2. Select the relationship you want to process, and choose the pushbutton Change relationship to process detailed data concerning the relationship or its validityThe dialog box for maintaining detailed data appears. Enter the changes that you wish to make. Delete relationship, in order to delete the relationship3. Save your entries.

ResultYou have changed one or more relationships.

Changing Relationships (Independent Maintenance)

PrerequisitesBefore you can change relationships, you must have already created business partners and relationships.

Procedure1. Choose Relationship Change. 2. In the initial screen, you can make a pre-selection of the relationship/s that you want to change, by specifying a search strategy, relationship category, business partner 1 or 2, validity key data and sorting sequence. 3. Choose Execute.

If you do not enter any details, you get an overview of relationships (maximum of 5000 relationships), from which you can choose the desired relationship by drilling down the hierarchy. 4. Position the mouse pointer on the node that you want to process, and choose: To change the validity: Edit Change validity To delete the relationship: Edit Delete To create a relationship that is identical to a relationship that already exists: Edit Copy.

If you want to edit several relationships at the same time, position the mouse pointer on the corresponding relationship and choose Select. This allows you to make the desired change to all the relationships selected, in one activity.

When you are in relationship maintenance, it is also possible to create a new relationship. The data from the node that you have selected is taken as default.

ResultYou have changed one or several relationships.

Central Relationship Data

UseUsing control tables, you specify whether attributes can be maintained for the relationship category. To date, attributes can be maintained with the contact partner relationship and shareholder relationship. Contact person relationshipFrame on screen:Description

Contact person: General dataYou can specify a VIP indicator for the business partnerYou can also enter data on the department, function, and power of attorney of the business partner, plus free text as a comment.

Address dataIn addition to telephone and fax numbers, and email address, you can also specify address details such as company department and name of function. If a company address is maintained, you can assign this by choosing Assign company address.

PushbuttonsDescription

Address overviewYou can view the address data of the contact person in the address overview.

Address print previewShows you the address of the contact person in the print preview.

Calling hours/visiting hoursYou can enter the times at which a contact person can be visited or called. You can also define additional consulting hours, and enter which calling/visiting hours are not permitted.You can also select which calendar you have based these times on, and define any exceptions to the rule.

Shareholder relationshipFrame on screen:Description

Shareholding dataYou can specify the shareholding percentage as well as the actual amount, together with the currency. With the Control indicator you can state whether it is a controlling interest on the basis of a controlling agreement or key shareholding. A controlling interest is not strictly limited to one business partner. For example, if two business partners each hold an interest of 50%, both can have a controlling interest.

If you have specified an own relationship category (see Extensibility), you can define an attribute maintenance for this relationship category.

Displaying Business Partner Relationships

UseYou can display business partner relationships in one of the following ways: as a list as a hierarchy as a networkAccording to the form of display, you can gather various information from the relationships.

PrerequisitesYou have maintained one or more relationships to a business partner.

FeaturesList:In the Overview of the list display, you can see all the relationships of a business partner to all relationship categories. Select the required relationship category to display the relationships of a relationship category. From the list, you can access the detailed data of the relationship, via the pushbutton Change relationship, and maintain this data.It is also possible to display business partner relationships in the form of a list in SAP GUI for HTML.

Hierarchy:In the hierarchical display, you can see all the relationships of a business partner to each selected relationship category on a selected Key Date (1:n view). You can select the display level of the view by means of the list box Depth.From the hierarchical display, you can access the detailed data of the relationship, via the pushbutton Change relationship, and maintain this data. The relationship is maintained, starting with the lower-level business partner.It is also possible to display business partner relationships in the form of a hierarchy in SAP GUI for HTML.

Because of the hierarchical display format (1:n), it is not possible to map additional relationships to a business partner that is already displayed. For this reason, additional incoming and outgoing relationships to business partners that are already displayed are shown in the form of an icon. To maintain these relationships, select the corresponding business partner and right-click on it, then select Display relationships. Choose Incoming or Outgoing relationships. A detail screen appears. Select the business partner for the required relationship in order to be able to maintain the detailed data.

Network:In the network display, all the relationships of a business partner for a selected relationship category on a selected Key Date (1:n view) are displayed graphically. The business partners are represented as nodes, and the business partner relationships are represented as lines between the nodes. The graphical display format allows you to view all the incoming and outgoing business partner relationships as well as the relationships for additional business partners simultaneously. You can select the display level by means of the list box Depth, and you can use buttons to enlarge or reduce the representation. You can choose to display the relationships either vertically or horizontally.You can maintain both business partners and relationships from the network display. In addition, you can create relationships of the selected relationship category between any two business partners displayed in the network, by means of the pushbutton Insert dependency.It is not possible to display business partner relationships in the form of a network in SAP GUI for HTML.

Summary:Method of displayMaintenanceDisplay level (Depth) Display in SAP GUI for HTML

ListA list of all the relationships of a BP to all relationship categories.Maintenance of relationships possibleSelection not possiblePossible

Hierarchy Hierarchical display of all relationships of a BP to a relationship category (1:n display).Additional relationships to existing business partners are identified by means of a icon.Maintenance of relationships possibleSelection possiblePossible

NetworkGraphical display of all relationships of a BP to a relationship category (n:m display).The business partners are represented as nodes, and the business partner relationships are represented as lines between the nodes.Maintenance of business partners and relationships possible Selection possible Possibility to enlarge and reduce Choice of vertical or horizontal formatNot possible

Extensibility

UseSAP Business Partner is designed to enable you to make extensions, as the screen structure and the screen sequences are defined in control tables. Program logic can be integrated by way of firmly defined interfaces.

Features1. SAP Business Partner a. Extension by way of attributes: SAP Business Partner can be extended to include attributes. If you wish to make customer-specific evaluations or enter additional information on a business partner, you can add fields to existing BP roles in an existing screen or in a separate screen.b. Extension to include BP roles: An extension of BP roles is also permitted. Extensions should only be made by developers with ABAP/4 experience and only if specific customer applications have been programmed. Adding new BP roles only makes sense if a customer-specific development is being conducted. The business partner data required for this application can comprise data supplied by SAP as well as customer-specific data. If no BP role-specific data is required, you should first check whether the required function cannot also be mapped using the BP role Business partner (general), or whether it is not enough to transfer existing business partner roles. For more information about the renaming of business partner roles, see Business Partner Role For detailed information on the extension to include new BP roles see Business Data Toolset. c. Extension to include a check on SAP fieldsCustomers can conduct specific checks for SAP fields. For example, customers can assign the check rule that a last name must contain at least three letters and one vowel.2. Relationships:a. Extension by way of attributes: Relationships can be extended by way of attributes. b. Extension by way of relationship categories: You can create new relationship categories. Examples of relationships: Is a member of (club)Is an employee of (business partner company)Is the son/daughter ofIs the managing director ofIs guarantor forIs guardian ofYou define your own relationship categories in the same way as you define your own BP roles.

Before you create your own relationship categories, you should check carefully whether this relationship category is necessary from a business point of view, and whether it would not also suffice to rename existing business partner relationship categories. For more information about the renaming of business partner relationship categories, see Business Partner Relationship Categories.

Business Data Toolset

Developers ManualIntroductionIntroduction to the BDT - What is the BDT?Function OverviewRoadmap for ImplementationAppendix Terminology DefinitionsIntroductionThis manual describes the functions in the Business Data Toolset (BDT) as of January 1999. Development for Release 4.6A in the standard R/3 system has already begun at this point. The following IBU releases have the same development status: IBU Banking Release 4.01B IBU Insurance Release 2.1A IBU Telecommunications Release 1.2 IBU Utilities Release 1.2This manual is divided into five main sections. After this introduction, the chapter Introduction to the BDT - What is the BDT? provides a brief overview of the BDTs origins, current features and enhancements planned for the future. The chapter Function Overview describes current functionality in detail. In writing this manual, the authors have assumed thorough knowledge of dialog programming and the related tools. The chapter Roadmap for Implementation is devoted to practical problem-solving. It lists any necessary steps and then makes reference to sections that provide more detailed descriptions. Explanations of special terms and abbreviations as well as an overview of naming conventions ( Terminology Definitions) comprise the last section of the manual.Depending on your interests, different sections will be more or less relevant for you: For a brief overview of the functions in the BDT, see section 2 Introduction to the BDT - What is the BDT? Developers and consultants who plan to use the BDT for implementation but are unfamiliar with it need to read the entire manual. Developers and consultants with BDT experience may only need to consult the Roadmap for Implementation to solve actual problems. Introduction to the BDT - What is the BDT? The BDT (Business Data Toolset) is a central control tool for maintaining master data and simple transaction data. In addition to dialog maintenance, it also supports maintenance with direct input and/or function modules. The BDT also provides generic services for consistently recurring requirements such as occur in change document lists, field groupings and the deletion program. It takes control over these objects as well as generic parts and calls the applications using predefined interfaces (control tables and events). The applications themselves introduce application-specific enhancements, such as writing and reading application tables. Note: The BDT is used at SAP for maintaining several application objects (see Current Status, user). Development partners and customers can also extend these application objects via the BDT interfaces. However, objects belonging to the development partners and customers may not be mapped using the BDT, as the required control has not yet been released.

HistoryThe Business Data Toolset originated in the Central Business Partner project. The following demands on the technical aspect of data entry played an important role in the development of the BDT: ExtensibilityAlthough the Business Partner project group had realized the central attributes of a business partner, (such as name components, addresses and bank details) there were other specific attributes in many of the remaining applications. Development partners and customers needed a facility for incorporating their own attributes into maintenance. In master data for accounts receivable and accounts payable, you had to make modifications to do this.Because it is impossible to collect and implement all these different attributes in one project group, maintenance for downstream enhancements had to be extensible without the need for modifications. ConfigurabilityBecause mid-size customers in particular tend to suppress most of the standard SAP data fields, dialog maintenance becomes tedious when you still have to go through screen after screen on which only one or two fields are relevant. Switching screens often slows down data entry considerably.As a result, it was decided to make screens configurable in order for customers to both tailor entry screens to their individual needs and keep the number of screens to a minimum. DivisibilityIf you were to count up all the attributes in the SAP system that are relevant for a business partner, you would have several hundred fields. Since it is impossible to include all these attributes in each type of maintenance, the maintenance itself must be divisible into parts wherein only those attributes are visible which are relevant in the current business context. These parts are called roles in Business Partner.The necessary technology was first developed in a common program with application data for Business Partner. However, it soon became apparent that the second part of this project - i.e., the business partner relationships - were placing the same technical demands on data maintenance. The requirements listed above were also applicable to other business objects. As SAP restructured with a new industry orientation, extensibility assumed a greater importance for development. Many of the IBUs wanted to extend or enhance application objects from the standard system. As a consequence, the Business Partner project group decided to separate the technical part from the application data and then make this technology available to other application objects. This technical part, which was called BP control or master data control for a long time, is now known as the Business Data Toolset, or BDT.

Current Status

UsersThe first user of the BDT is SAP Business Partner (see Introduction to the BDT - What is the BDT?). Business Partners purpose is to integrate all partner solutions that currently exist in the SAP system. In the first step, the following new applications build on this development: Contract Accounts Receivable and Payable IBU Banking IBU Insurance IBU Utilities IBU TelecommunicationsThe integration of the Treasury business partner is currently in process and should be complete by R/3 Release 5.0.In the meantime, other application objects have already taken advantage of the BDT. The following application objects are currently being realized or developed in conjunction with the BDT: Central Business Partner Partner maintenance Relationship maintenance Contract Accounts Receivable and Payable Contract account IBU Banking Bank account Standing order Financial product Financial conditions Risk object Variable transactions IBU Insurance Insurance: Claims Insurance: Loss event Commissions Remuneration agreements Real Estate Real estate contract Tenant information Cost efficiency analysis

AdvantagesSimilar technical demands are often placed on the development of application objects. By using the BDT, an application object can provide functions without having to realize them itself. The essential advantages of using the BDT are: ExtensibilityYou can extend various dialog parts without the need for modifications using downstream applications either within SAP or through development partners or customers. This applies to Screen layout Screen sequence Program logic Menu Search help Field grouping Authorization checksExtensibility is also possible in other areas, such as data maintenance without dialog or change document lists.Extensions, or enhancements, can be created over multiple levels. As a rule, application development in R/3 has a maximum of five levels: Application basis Standard applications Industry applications Development partners Customers ConfigurabilityScreen layout and sequence can be configured by application developers and/or customers. While developers use BDT control tables to modify screens, customers can take advantage of a configuration tool developed using Visual Basic for changing standard SAP screen layout and sequence with the drag&drop method. DivisibilityThe maintenance of large objects can be broken down into smaller parts. You use control tables to define which attributes can be maintained in an object part. The term object part can be replaced by a more suitable term for any given application object. The BDT supports two types of divisibility: Each object instance can take on multiple parts (example: roles with a business partner) Each object instance can take on just one part (example: account type with a bank account) DelinkingEach application always develop within its own function group. The individual applications are thereby delinked. Use of Other InterfacesInterface and program logic are separate in the BDT. The program logic for the applications is contained fully in function modules that are called by the BDT at predefined times. As a result of both of these factors taken together, the R/3 interface of the BDT can be replaced by a different interface. Faster DevelopmentBecause the BDT takes control of dialog processes, the applications limit themselves to realizing business functions. The BDT also provides services in which the applications can be included. These factors reduce considerably the time needed to develop applications. UniformityIn all application objects that use the BDT, online navigation takes place using the BDT and is therefore identical. Using the generic object services also contributes to a certain uniformity.

FunctionalityThe following provides you with an overview of functions that have already been realized. Dialog Maintenance Existing tables can be extended by downstream applications using the APPEND structure technique from Basis. These new table fields as well as completely new tables can be integrated seamlessly into a dialog by SAP applications, development partners or customers. Screen layout and sequence can be extended and configured using control tables (without the need for modification). Customers can adapt standard SAP screens to their needs with drag&drop within customizing. Using the Visual Configuration Tool (VCT), customers can change screen layout - or also group several screens together screen sequence screen titles frame titles Program logic can be extended by SAP applications, development partners or customers using event function modules In this way, each application can read its tables check its fields carry out additional checks for fields in other applications save its tables The screen title is composed by the BDT in accordance with SAP ergonomic guidelines. Its elements are the title of the application object (e.g. Business Partner) the activity (e.g. Change the title of the current screen (e.g. Address).In this example, the BDT created the screen title Change Business Partner: Address.You can change the title created by the BDT with event DTITL. The menu is defined by the application that owns the application object. The central functions, such as Cancel, Exit, Save and Back, provided by the BDT are part of the menu. You can use control tables to define when a menu option is to be active depending on the: maintenance mode (save or transfer mode) activity (create, change, display) views on the current screenExample: The menu option Delete bank details is only to be active in the Create or Change activity and when the view of bank details is on the current screen. Field groupings can be made using criteria of your choosing. The BDT supports the application when creating a maintenance transaction for one criterion and links settings for various criteria to the runtime using predefined rules. Using a control table, applications can add any number of other elementary search help functions to fields related to search help. Starting in Release 4.6A, this service will be provided by Basis in the form of APPEND search help functions. You can include notes easily on a screen and, like any other dialog part, place them wherever you like. Authorization checks can be carried out between the initial screen and the first data screen as well as prior to saving. The BDT provides some of the recurring authorization checks that can be used by application objects. Authorization for field groupsExample: Only user A may maintain names and addresses of business partners, while all users can maintain any remaining fields. Authorization for field values of any fieldExample: Authorizations for a business partner are to be granted using the Last name fieldUser A may only maintain those business partners whose last names begin with A-KUser B may only maintain those business partners whose last names begin with L-ZEvery application can also carry out any other authorization checks. Change documents are written by each application when saving data itself; the BDT provides evaluations. The following evaluation types are available: Field changes (display changes to a field of an instance) Account changes (display changes to all fields of an instance) Display changes to multiple/all instances Transfer mode: The maintenance dialog is called from the maintenance of another object. The data is saved together with the calling object.Example: Maintaining a contract requires you specify both parties to the contract - two business partners. You should be able to create and/or change both business partners from contract maintenance. The contract data and the business partner involved are to be saved together. In order to do this, business partner maintenance must be called from the contract in transfer mode. When you exit business partner maintenance, the data entered is flagged but not yet saved in the database. Once the contract has been saved, the flagged business partner data is written to the database. External interfaces can be realized for application objects that were developed with the BDT. In this case, the external maintenance transaction only takes over the structuring of the interface and forwards the field contents entered on to the BDT. BDT function modules are called to carry out program logic such as reading, checking and saving data. They trigger the events that call the event functions modules in the applications. Maintenance Without Dialog Direct Input (DI)Using the DI tools developed in EIS, data is read from a file and transferred to the BDT. The BDT then forwards that data on to the applications within events DINP1 (header data) and DINP2 (data). Finally, the same events are processed in this type of maintenance transaction as in a dialog. Most of the program logic developed by the applications can be reused. Maintenance Using Function ModulesIn contrast to DI, the data in this case is transferred in the interface of a function module instead of being read from a file. Once the data has been transferred to the BDT, the process is the same as that for DI.Future Enhancements

For Release 4.6Various enhancements to the BDT are planned for Release 4.6. These will be partially replicated at a later time in the development systems of those IBUs that use the BDT but do not develop in Release 4.6. Any questions you might have should be directed to the Business Partner development group. The most important developments in Release 4.6 are: Time DependencyThere are numerous ways of creating time dependency, including planned change documents and extending a table key by one or more date fields. It is left up to applications that use the BDT to decide whether and what kind of time dependency they want to use.The BDT supports the use of planned change documents with two service function modules, which are called by the applications at certain times. Calculating Data Status in the Past or FutureA BDT function module uses the database status which contains the current data as a basis for calculating the status at any date in the past or future. As a part of this procedure, the BDT reads the planned (future changes) or actual (changes in the past) change documents. Calculating Data Status for Time IntervalsBased on the database status, the BDT function module determines the various data statuses in the past or future and then displays the date intervals with the data status valid for each.The application writes the planned change documents during the event that saves the data (DSAVE).If you choose the option of extending the table key by one or more date fields, most of the work is left to the applications. The BDT only provides a function module that uses pre-existing date intervals as well as the current change date and the action to be carried out to determine the new date intervals. Deletion ProgramThis program deletes test data prior to production startup. Data should only be archived in production operation (see below). The BDT takes control in the deletion program and uses two events to provide the applications the option to check the deletability of objects delete deletable objects from the view of all applications ArchivingThe ADK (Archive Development Kit) is used for archiving. As in the deletion program, the applications can use events to intervene in the archiving process. Where-Used ListAn employee may sometimes need an overview of all the transactions a company had or is having with a business partner. Ideally, you would be able to include all or only selected areas of a company in this kind of list. Because this service has also been requested for other application objects, the BDT has developed an infrastructure for it. Its various uses are displayed in a user-defined tree structure. Each application can add its own nodes to the tree.The application decides which form of data retention is required on an individual basis for each node. Reading Data at RuntimeThe application stores the name of the function module in the BDT with which data can be imported. The advantage of this method is that redundant data need not be retained. Saving Data in Redundant Usage TablesFor each application object there is a usage table in which the applications can update their usage at the same time as the operative tables. At runtime, the where-used list extracts the data from this table. This type of data retention generally has a better runtime and should be used for usage from external systems.There are also two options for display: Configurable TreeThe BDT can display the usages within one of the configurable trees belonging to an application. Customers can create partial views of this display to see only the usages that they specify. One partial view can be stored as standard for each user group. You can navigate to the maintenance and/or display transaction of an application. You can also use a separately written program to read the data using a BDT function module and output it in its own display. EvaluationsThe ABAP List Viewer (ALV) can be used to create flexible evaluations of the application data. The BDT takes over control based on the extensibility requested at this point. The applications have the option of integrating their own data into the evaluation within just a few events.

After Release 4.6 Default ValuesYou will be able to maintain an unlimited number of default variants so that they can be used as a reference when creating a new instance. You will be able to include default values from other sources using a separate event. By using a field grouping, you will be able to decide whether a default value can be overwritten by a user at a later time. Screen Configuration by Developers with Drag&DropLike customers (see section 4.6.1), developers will also be able to configure their screens with VCT and drag&drop. Generating Application ProgramsLarge parts of the function modules to be created by the applications will be developed according to the specifications of the BDT. The important thing is to complete the actions defined for an event within that event. The application code will be generated according to the specifications of the developer responsible. This code can be supplemented and/or replaced by the developers own programs, thereby accelerating overall development.

Problem Messages/Development RequestsProblem messages or development requests regarding the BDT should be assigned to the CA-BP (SAP business partner) subject area. When finding notes, use key words BDT and CBP.

Task Menu BUPTYou get to the menu with the transaction code of the same name. This menu fulfills several purposes at once: The centrally defined application calls for Business Partner can be found in the Application submenu. There is also a branching point into the menu for BP-BP relationships, which represent a separate application object. All calls relevant for an application will be included in their respective menu so that there is no need to call from the BUPT menu. Cross-application settings (see Basic Settings) are located in the General control submenu. You can also store differentiation types in addition to defining application objects at this point. The BP control submenu contains the object-specific settings (see Dialog) for the Business Partner application object. You have to create a separate task menu for each additional object which contains the calls of the settings specific to this object. The Customizing submenu contains the settings a customer can make in Business Partner. You will also find the same points in the IMG under Cross-Application Settings SAPl Business Partner. Documentation for the individual points, which you need to set up your system with the IMG is located here as well.

Function Overview The BDTs functions are described in detail in this section. Menu paths refer to the described Task Menu BUPT. Task menus belonging to other application objects will generally look very similar.

Basic SettingsThis section outlines the activities required before you can start any dialog programming.

Differentiation TypesMenu path: General control Differentiation typesDescription: Application data is generally dependent on the primary key of the application object. For a business partner, the primary key is the partner number. However, there can also be other attributes that must be differentiated according to other criteria. If data for an instance is only ever entered as a way of describing it as a criterion, then it would be called a differentiation type. Differentiation types are usually entered on the initial screen. The existence of an instance is also updated in dependence on the differentiation type specified.Configure the input screens so that the value of the differentiation type is visible in the header data if the underlying data is dependent on it divergent views of differentiation types are not grouped together on any one screenExamples: Differentiation types are usually organizational units like company codes or sales areas. In addition, there can also be differentiation types that do not constitute an organizational unit. For an FI customer, the company code has to be entered on the initial screen. A large part of the data is dependent on the company code. These fields are grouped on separate screens. Because the header data in these screens also contains the value of the company code, it is obvious to the user which data can be given different characteristics on an individual company code basis. When you save, the existence of the customer in the company code entered is updated. If you create the customer in an additional company code, you must re-enter the company code on the initial screen as well as any data dependent on the company code in the data screens.Note: The definition of one differentiation type is valid for all application objects. You decide which differentiation types are relevant for each application object (see Assigning Application Objects -> Differentiation Types).Use: The relevant differentiation types are assigned to each application object (see Assigning Application Objects -> Differentiation Types). A differentiation type is stored for each view (see Defining Application Objects). When configuring the input screens, bear in mind that you should be able to use them later to check that only views of one differentiation type are grouped on one screen. Activities: Check to see whether differentiation types are relevant for an application object. If this is the case and the differentiation type you need does not exist, contact the Business Partner development group, which is responsible for the central assignment of differentiation types and their associated elements within SAP. To create differentiation types for individual customer purposes, follow the steps below: Define Differentiation TypesEach characteristic used to differentiate data must be entered at this point. Define Differentiation Type ElementsDifferentiation types are made up of one or more elements. While a company code is made up of only one element - the company code itself -, a sales area is comprised of three elements: sales organization, distribution channel and division. Each differentiation element is normally represented by an input field on the interface. Assign Differentiation Type Differentiation Type ElementAllocate the differentiation types elements to it. You still have to make an assignment even if a differentiation type has only one element.Note: The application responsible for the differentiation type determines the elements to be assigned. If an application requires a differentiation type with additional elements, do not extend the existing differentiation type - create a new one instead.

Application objectsDescription: Each master data/transaction data object that uses BDT must be known. The maintenance of application objects is subdivided into the following points: Defining application objects Assigning application objects differentiation types Settings transactions, task menuMenu path: General control Application objects

Defining application objectsIn this step, you register the new application object with the BDT and decide whether you want to use divisibility tab strips for navigation to be visible screen selection to appear on the initial screen to use the central authorization checks provided by the BDTExamples: Currently, there are about 15 application objects from IBU Banking, IBU Insurance, Contract Accounts Receivable and Payable and Real Estate Management. Some examples include: BUPA Business partner BUPR Business partner relationships BKKA Bank account FICA Contract accountNaming convention: The BDT has been released solely for the development of SAP application objects. It should not be used to develop customer application objects. To register a new application object, contact the Business Partner development group. The group keeps a central register that prevents different application objects being given the same name, which could cause problems.

Assigning application objects differentiation typesAt this point, you define whether the differentiation types already maintained are relevant for an application object. If you need a differentiation type that does not exist, you have to create it (see Differentiation Types).

Setting TransactionsThe settings described in the section Dialog are maintained separately depending on the application object. If, for instance, you define a screen for application object BUPA (business partner), it will only exist within that application object.By using setting transactions, you can easily create transactions with which the BDT control tables for your application object can be maintained. Later you also create the task menu for your application object (see Task Menu) from these transactions as well.The following table provides an overview of current setting activities as well as which activity is needed by an application object (required) can be used by an application object (optional)ActivityDescriptionRequiredOptionalRequirement

0001ApplicationsX

0002Field groupsX

0003ViewsX

0004SectionsX

0005ScreensX

0006Screen sequencesX

0007EventsX

0008GUI standard functionsX

0009GUI additional functionsX

0010MatchcodesX

0011Assign screen field DB fieldX

0012Field grouping criteriaX

0013Object partsXDivisibility

0014Object part groupingsXDivisibility

0015Application transactionsX

0016TablesX

0017External applicationsXExternal interface

0100Field grouping per activity typeXService needed

0101field grouping per object partXDivisibility

0102Authorization typesXService needed

0103Field groups for authorizationXService needed

0104Screen configurationX

0105Field grouping per external applicationXExternal interface

0200Change document listsXChange document

Activities: Maintain a setting transaction for each setting activity. For each activity, carry out the following steps: Create a report transaction and enter the report BUSVIEWS as the start parameters.Procedure: Go into the ABAP Workbench menu and choose Development Other tools Transactions. Enter the transaction code and choose Create. Now select the Report transaction option and on the screen that follows enter BUSVIEWS in the program field next to the transaction text. Enter the setting activity with your application object and assign the transaction code you created in the first step.When the transaction is started, the maintenance view that is part of the control function or the view cluster for your application object is called automatically.

Task MenuCreate a separate task menu for your application object. This should contain the control transactions. When creating your menu, use the BP control sub-menu in task menu BUPT as a reference.Note: You can maintain area menus by going into the ABAP Workbench from Development Other tools Area menus.

ApplicationsEach application that is active in the maintenance of an application object has to register itself at this point. They always develop within their own function group. There they create subscreens as well as their own function modules for BDT events.This encapsulates the application and prepares it for delinking. Avoid grouping heterogeneous components in a single application. Any later delinking of these components that becomes necessary would only be possible with your own expenditure of time and effort - in other words, you would have to split the application and thus also the function group.Menu path: Control ApplicationsNaming convention: Name ranges Y* and Z* are reserved for customer applications, while development partners can use name range X*. SAP applications register their application with the application responsible for the application object.The application ID plays an important role in the naming conventions for other BDT objects.DialogUsing the BDT ensures that the dialog created by an SAP application is extensible for other applications both inside and outside SAP. The procedure is changeable. To do this, you would use fully maintained interfaces. Modifications to development objects in other applications are not necessary.

ActivitiesFor each application object, you can define any number of activities in which an object is to be processed. Each application developer can show or hide fields on an individual activity basis. The activity-dependent part of the screen title (see Screen Title) is stored within the activity based on language.Each activity has to refer one of the activity types predefined by the BDT. The following activity types exist for the dialog: Create Change DisplayMenu path: Control ActivitiesNaming convention: The following activities - called main activities below - have to be defined for each application object: 01 Create Activity type 01 02 Change Activity type 02 03 Display Activity type 03Examples: For a standing order in IBU Banking (BCA) there is the Delete activity in addition to the three main activities. However, only a deletion flag is set - the associated activity type is actually Change.Environment: Direct Input also recognizes activity type Modify in addition to the three others listed above. At runtime, the application determines whether a record already exists with the transferred key. If this is the case, the Change activity is set. Otherwise, the activity would be Create.Procedure : Carry out the following steps for each activity: Define the activities for your application object and assign to each an activity type. Once the screen layout and screen sequence have been created, hide those field groups that are unnecessary for an activity.Screen LayoutScreen layout is defined in control tables. Applications from downstream development stages can extend and reconfigure existing screens. The BDT supports the following entities in screen layout Field group View Section Screen

Field groupsFields whose readiness for input was defined collectively are collected in a single field group. You create settings for each field group with in the Field Grouping. A field group may only contain fields from one application. Customers should neither change nor extend the definition of standard SAP field groups, as this would amount to a program modification. As an alternative, customers can define their own field groups to which they also assign their own views. Menu path: Control Screen layout Field groupsProcedure: To define your own field group, proceed as follows: Define field groupThe name of a field group is language-dependent and appears when a field grouping is maintained. If fixed logical dependencies exist, a program can be used to change field groupings set up by customers. If Required entry is set for a field group, the BDT checks automatically whether the fields have entries before the data is saved. If this is not the case, an error message is displayed. A different kind of required field check is necessary for some field groups. For these field groups, the automatic check can be turned off and an individual check used instead. One example of this is bank details for a business partner. The individual check will only trigger an error message if no bank details were entered. A specific check for required fields does not take place on the field level. Assign Fields to the Field GroupEnter the name of the screen fields that are to be assigned to the field group. Besides input fields, you also need to specify the field names o