Ansicht
Dokumentation

FSBP_TC_VC_TP38 - Make Settings for Total Commitment

RFUMSV00 - Advance Return for Tax on Sales/Purchases CPI1466 during Backup
This documentation is copyright by SAP AG.

Use

In this Customizing activity, you make the settings for the total commitment.

Requirements

Standard settings

Entries for the applications Account Management (AM), Loans Management (CML), Collateral Management (CMS), Bank Current Accounts (BCA), SAP Leasing (CRM-LAM)and Deposits and Loans for BPP Banking (TRBK)are supplied in the standard system.

Activities

To display the total commitment for a business partner in the transaction Maintain Business Partner, activate total commitment (status Active).If you do not want to display total commitment on the business partner interface, you can deactivate it.

If you want to make this setting in your production system (to deactivate total commitment after it has already been activated, for example), you can also use the transaction FSBP_TC_STATUS (Change Status of Total Commitment and Applications). This transaction is only intended for emergencies, and helps you to speed up processing by avoiding the Customizing activity in the short term.

Contract data for the business partner is usually distributed across several systems (SAP systems or non-SAP systems). The SAP applications Account Management (FS-AM) and Loans Management (FS-CML), for example, supply data to the total commitment in real time, and are linked to the total commitment by Remote Function Call (RFC). To connect the participating systems to the total commitment, assign the RFC destinations to the logical systems.

Determining the participating logical systems makes it easier to assign logical systems to applications in the step Make Settings for Application, and to assign identification types to logical systems in the step Assign BP Identification to Logical System.

Only those logical systems you have determined previously are displayed in the input help for the Logical System field, and you can run a plausibility check to ensure that the entry is correct.

The standard system contains the entry logical system "SPACE", RFC destination "NONE" that enables your own system to be called too.

By selecting this checkbox, you can determine that parallel processing is to be used. If you select the parallel processing checkbox, then determine the relevant server group and the maximum number of work processes as well.

In this step you can activate the function to display contract information according to total commitment grouping. For more information about settings, see grouping status of total commitment.

In the customer namespace, define the applications linked to total commitment that make contract data for the business partner available.

The standard system provides entries for the applications Account Management (FS-AM), Loans Management (FS-CML), Collateral Management (FS-CMS), Bank Customer Accounts (BCA), SAP Leasing (CRM-LAM)and Deposits and Loans for BPP Banking (TRBK). You can override the names of the applications supplied by SAP.

In order to use the CML (Loans Management) application, you must create an RFC destination for each system and each client in which the application is run.

Make the settings for the application:

Enter the description of the application.

Determine whether the application is relevant for the total commitment.

Determine the activation status for the application.

If you want to make this setting in your production system, you can also use the transaction FSBP_TC_STATUS (Change Status of Total Commitment and Applications).

Determine the access mode for the application.

If real-time access to an application is required, select the synchronous checkbox.

If you do not set the indicator, the system reads the contract data from buffer tables, providing this function is supported by the respective application.

Note:If you have set synchronous access for your application then you have to name a logical system from which the system is to retrieve data.

If you want the system to read data at program runtime/synchronously, then you also have to create an implementation in the Business Add-In (BAdI) Read Contract Details for an Application. Technically speaking this should be an implementation of the interface IF_EX_FSBP_TC_ITEMSGETMULT with the corresponding method ITEMS_GET_MULTIPLE for the filter value "Z*" or "Y*". The filter value is the same as the technical name of the application that you have defined. You can analyze the implementations supplied by SAP before you create your own.

If you want to access the application using the RFC interface, as you would for the CML application, for example, enter the logical system for the application.

You can determine the sort sequence for the contract data in the application to be displayed on the total commitment interface.

Determine the business partner roles in the application that are permitted for the total commitment.

Bundle the business partner roles for an application that are permitted for total commitment in role sets.

Define the role sets for the application, and assign the business partner roles for the application that are permissible for total commitment to them. If you do not want to display any contract details for a business partner role in the total commitment, select the Do Not Provide Detailed Information checkbox. You can also change the sort sequence for the business partner roles for the applicationthat are displayed in the total commitment.

Define the selection variants that are required for selecting and displaying data in the total commitment. If necessary, change the display currency for the contract data in the total commitment and determine a different exchange rate type for converting the contract data to the display currency. You can determine which list output is used to display the total commitment. Enter a possible layout for displaying the total commitment. The layout depends on the respective list output. You can also deactivate the sorting of total commitment according to total commitment groupings for certain selection variants (Deactivate Total Commitment Grouping).

The selection variant DEFAULT is provided in the standard system.

Assign the applications and the role sets to be evaluated by the system to the selection variant. This assignment enables you to control the selection and display of the relevant contract data in total commitment with regard to the business partner roles that are to be included.

Assign the relationship categories that are to be evaluated in the total commitment to the selection variant. This assignment enables you to include additional business partners that exist in a relationship with the business partner to be displayed when you select and display the relevant contract data.

If you want to execute your own calls for the total commitment, define the necessary call contexts for selecting and displaying data in the total commitment.

Assign a selection variant to the call context.

The call context "DEFAULT" (business partner) is provided in the standard system. The selection variant "DEFAULT" is assigned to this call context in the standard system.

Total commitment normally merges contract and business partner data that comes from different systems (SAP and non-SAP systems). Different business partner numbers can exist in the individual systems. If you would like to have complete overview of all the contract data for the business partner, you may have to read contract data for different business partner numbers.

In this step, assign the corresponding type of BP identification and the identification type to the logical system.

You can identify business partners in an external system using the following settings:

Identification numbers

The business partner is identified in an external system using an additional identification number for the business partner in the local system. The business partner number from the external system is stored as an identification number in the local business partner When you call the total commitment, the business partner number is converted to this identification number. This enables the system to find the business partner in other systems.

Before you do this, you must have made settings for the identification numbers in Customizing for SAP Business Partner for Financial Services under General Settings -> Business Partner -> Basic Settings -> Identification Numbers. You have defined the applications used as identification categories and identification types in the customer namespace. You have also made settings for the identification categories to ensure that each identification number is unique.

If the business partner is identified using an additional identification number, then assign the corresponding identification type for the application as well as the BP identification to the logical system in this Customizing activity.

Business partner numbers (identical numbers)

The numbers for the business partners in the local system and those in the external system have to be identical. Business partners in the external system are identified using the business partner number.

If the business partner is identified using the business partner number, then do not assign an identification number category to the logical system.

Cross-system GUID for the business partner

The business partner in the external system is identified using a cross-system business partner GUID.

If the business partner is identified using a cross-system business partner GUID, then do not assign an identification number category to the logical system.

If you have assigned a logical system to the application in the step Make Settings for Application and if you have not made an entry for this logical system in the step Assign BP Identification to Logical System, then the system assumes that the numbers have to be identical.,,

Below is an overview of the possible applications and business partner IDs:

Application (remote)	Application is local	Application and BP in another system (remote)
CMS, CML, BCA, LAM, AM (TRBK 3.0) (BPID001 as of ABA710 BUT0ID)	No settings are required	Either BP number or ID number from "identification numbers"
AM (TRBK 4.0), TRBK =(Deposits&Loans)	Always via "cross-system GUID for the business partner"	Always via "cross-system GUID for the business partner"

Always via "cross-system GUID for the business partner"

You can check the settings for total commitment for the plausibility of the entries in the Customizing activity Check Settings for Total Commitment.