Show TOC

Object documentationMaster Contract Termination

 

A business object in Master Contract Management (FS-MCM) that depicts the termination of a master contract between the master contract holder and the contract-managing organizational unit (bank, for example). The system terminates only master contracts and the relationships to participating accounts. It does not close the accounts.

You can set an indicator so that the system deactivates the entire hierarchy that is beneath the selected master contract. This means that it terminates all master contracts and deactivates all the relationships to accounts.

Master contract termination is managed in Master Contract Management (FS-MCM) as an order by Order Management (FS-AM-OM). When you activate an order it represents the notice given for and termination of a master contract. The master contract termination sets the contract status Terminated in the master contract.

Note Note

Note that the master contract termination does not automatically settle the master contract. You need to settle a master contract manually before you terminate it. If you are using Combined Settlement, you can use the report Edit Combined Settlement Dates (/FSBPR/UI_R_SCHED_DISPLAY, transaction /FSBPR/DUE_DATES) to plan a manual date for the settlement.

End of the note.

Structure

The structure definition for master contract termination comprises attributes, methods and customer enhancements.

Attributes

  • Attributes of Order Management

  • Termination Reason

  • Termination Date

  • Correspondence for activation

  • Planned closure date

  • Correspondence for execution

  • Actual closure date

  • Reference attributes

    Reference attributes point to other objects whose documentation is referred to below.

Methods

In Master Contract Management (FS-MCM), you can use one of the following channels for processing objects:

  • Dialog

  • Business Application Programming Interface (BAPI)

  • Direct Input (DI)

The application uses the Entry Origin or Processing Origin fields to identify the channel used to process it.

Entry Origin

Processing Origin

Short Description

Channel

BOTAP

Order for master contract termination (dialog)

Dialog

BAPTAP

Order for master contract termination (BAPI)

BAPI

BDTTAP

Order for master contract termination (EDT)

BAPI

The following overview shows which methods of master contract termination can be called up via which channel:

Method

Dialog

BAPI

DI

Create and enter

X

–

–

Create and activate

X

X

–

Change and enter

X

–

–

Change and deactivate

X

–

–

Change and delete

X

–

–

Change and activate

X

X

–

Display

X

–

–

Read

–

X

–

Read the current master contract termination of a master contract

–

X

–

The methods can change the order status of the master contract terminations. For more information, see Order Status of Master Contract Termination.

Dialog

You can call up the following transaction in dialog processing: BCA_OR_TAP Terminate Master Contract.

Business Application Programming Interface

You can call up the following methods using the BAPI Explorer:

Method

Short Description

AccountPoolTermAM.CreateAndActivate

Create and activate master contract termination

AccountPoolTermAM.ChangeAndActivate

Change and activate master contract termination

AccountPoolTermAM.GetDetail

Read master contract termination

AccountPoolTermAM.GetActiveByAccountPool

Read the order number of the current master contract termination of a master contract

Note Note

You can also execute all the methods in a test run.

End of the note.
Direct Input

Direct input is not implemented for master contract termination. You can make external data transfers (EDT) using the BAPIs that have the entry origin and processing origin BDTTAP.

Customer Enhancements

The following Business Add-Ins (BAdIs) are available for master contract termination:

BAdI Definition

Interface

FS_MCM_IN_TR_BCFC_CANCEL

Deactivating Master Contract Termination

IF_MCM_IN_TR_BCFC_CANCEL

FS_MCM_IN_TR_BCFC_CHANGE

Change Master Contract Termination

IF_MCM_IN_TR_BCFC_CHANGE

FS_MCM_IN_TR_BCFC_CHK_CANCEL

Deactivate Master Contract Termination - Simulation

IF_MCM_IN_TR_BCFC_CHK_CANCEL

FS_MCM_IN_TR_BCFC_CHK_CHANGE

Change Master Contract Termination - Simulation

IF_MCM_IN_TR_BCFC_CHK_CHANGE

FS_MCM_IN_TR_BCFC_CHK_CREATE

Create Master Contract Termination - Simulation

IF_MCM_IN_TR_BCFC_CHK_CREATE

FS_MCM_IN_TR_BCFC_CREATE

Create Master Contract Termination

IF_MCM_IN_TR_BCFC_CREATE

FS_MCM_IN_TR_BCFC_FIND

Find Master Contract Termination

IF_MCM_IN_TR_BCFC_FIND

FS_MCM_IN_TR_BCFC_READ

Read master contract termination

IF_MCM_IN_TR_BCFC_READ

Note Note

All the interfaces named contain the following methods:

  • TRANSFEREXTENSIONIN

  • TRANSFEREXTENSIONOUT

  • TRANSFERCHECK

End of the note.

Integration

When the system processes master contract terminations, the related release object and different authorization objects control the program flow. The system calls up and processes the following objects from Master Contract Management (FS-MCM) during processing.

Objects Checked by the System

Master Contract

The system checks the master contract. If one of the following conditions has not been met, the system issues messages accordingly.

  • The master contract exists.

  • The contract status of the master contract is Active, Not Yet Used or Active, Used.

  • The master contract in not In Release.

  • The master contract has the master contract termination feature and the traffic light is green.

    For more information, see the Editing Features section.

  • The date of receipt of notice is compatible with the master contract event data, such as event 0004 Master Contract Start Date.

Objects Changed by the System

  • Master Contract

    The system changes the following data on the master contract:

    • Date of event 0005 Planned Master Contract Terminations when the master contract termination is activated

    • Date of event 0011 Actual Master Contract Termination when the master contract termination is executed

    • Contract status (Terminated))

    • Contract relationship (all participant accounts are removed)

  • PLM Document

    When terminating a master contract, the system checks whether PLM documents exist for the master contract being terminated and deactivates them.

    If the entry origin or processing origin is BDTTAP, the system does not check the PLM document.

Objects Generated by the System

  • Change document

    The system generates a change document that meets auditing requirements.

  • Work item

    The system generates a work item for the release process, if required on the basis of the Customizing settings.