Show TOC

 Product Change (Account)

Definition

Business object in Account Management (FS-AM) that depicts the transition of an account from a source product to a target product . The target product can be a new product version of the source product or a completely different product . The system always chooses the valid product version of the target product.

In the Account Management (FS-AM) system, a product change (account) is managed as an orderby Order Management (FS-AM-OM) . When you activate the order, the flagging of the product change (account) is depicted and when you execute it, the product change (account) itself is depicted.

During a product change (account), the history and central data of the account, such as the account number and account holder, remain unchanged. For each attribute group you can define whether the attributes of the source account or those of the target product have priority during product change.

Structure

The structure definition for a product change (account) is divided into attributes , methods, and customer enhancements . Everything described in the Order Management section also applies to a product change (account).

Attributes

  • Attributes of Order Management

  • Target product and product version

  • Transfer procedure

  • Planned product change date

  • Actual product change date

  • Correspondence for product change

  • Future contract changes

  • Immediate product change

  • Reference attributes

    Reference attributes refer to other Account Management (FS-AM) objects, whose documentation is referred to below in the “Integration” section.

Methods

In Account Management (FS-AM) , you can use one of the following channels for processing objects:

  • Dialog

  • Business Application Programming Interface (BAPI)

  • Direct Input (DI)

The product change (account) function uses the Entry Origin or Processing Origin fields to identify the channel used to process it.

Entry OriginProcessing Origin

Short Description

Channel

BAPCOP

Product change (account) - BAPI

BAPI

BDTCOP

Product change (account) - BAPI (EDT)

BAPI

BOCOP

Product change (account) - dialog

Dialog

COPAC

Due product changes (account) – mass processing

Dialog

COPPP

Mass product change (account) – mass processing

Dialog

COPVCA

Optimized mass product version change (account) – mass processing

Dialog

The following overview shows which methods of the product change (account) function can be called via which channel:

Method

Channel

Dialog

BAPI

DI

Create

x

x 1

Change

x

x 2

Enter

x

Display

x

x

Execute

x

Activate

x

x

Deactivate

x

Delete

x

Execute due product changes (account)

x

Edit mass product changes (account)

x

Edit mass product changes (account)optimally

x

1 Only combined with method Activate .

2 Only combined with methods Activate or Deactivate .

The methods can change the order status of the product change (account) .

Dialog

You can call up the following transactions in dialog mode:

Transaction Code

Short Description

Entry OriginProcessing Origin

BCA_OR_COP

Change Account Product

BOCOP

BCA_COP_ACC_BCA_BOCA

Edit Mass Product Change (Account)

COPPP

BCA_AC_COP_PP_ALL

Application Log – Selected Product Changes (Account)

BCA_COP_ACC_BCA_PVCA

Edit Mass Product Change Version Change (Optimized)

COPVCA

BCA_PV_COP_PP_ALL

Application Log – Optimized Product Version Changes

BCA_COP_TEV_BCA_BOCP

Execute Due Product Change (Account)

COPAC

BCA_OR_COP_PP_ALL

Application Log – Due Product Changes (Account)
Business Application Programming Interface

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

Method*

Short Description

ProductChange.ChangeAndActivate

Change and activate product change

ProductChange.ChangeAndDeactivate

Change and deactivate product change

ProductChange.CreateAndActivate

Create and activate product change

ProductChange.GetDetail

Read product change

ProductChange.GetOrdersByAccount

Read order numbers

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

Direct input

Direct input is not implemented for a product change (account). You can make external data transfers (EDT) via the BAPIs that have entry origin or processing origin BDTCOP .

Customer Enhancements

For the overview of the Business Transaction Events (BTEs), use transaction fibf (Business Transaction Events) .

In addition to the order-related BTEs of the product change (account) function, the account BTEs are also important for product changes. Any additional bank-specific or product-specific rules also need to be realized, as well as the standard transfer procedure used.

Integration

You make the settings for a product change (account) in the Customizing for Account Management (FS-AM) under the following nodes or in the following IMG activities:

  • Start of the navigation path Basic Settings Next navigation step Maintain Origin Data End of the navigation path

  • Start of the navigation path Order Management Next navigation step Basic Settings Next navigation step Configure Order Category End of the navigation path

  • Start of the navigation path Order Management Next navigation step Product Change End of the navigation path

When you are processing product changes (account), the corresponding release object and the various authorization objects have a controlling function for the program flow. For more information, see Authorization Administration in Account Management .The system calls up and processes the following Account Management (FS-AM) objects when processing the product change (account).

Objects Checked by the System

  • Account

    The system checks the account and outputs messages accordingly if one or more of the following requirements have not been met:

    • The account exists.

    • The account has contract status Active, Used or Active, Not Yet Used .

    • The account is Not in Release .

    • The planned product change date is after the date of event 0004 (Contract Start Date) .

    • The planned product change date is before the date of event 0005 (Planned Account Closure) .

    • There is no product change (account) for the account with order status 0120 (active).

  • Product

    The system checks the following settings and attributes:

    • Is the product transition from the source product of the account to the target product permitted according to the Customizing for product changes (account)? If this is not the case, the system displays an error message.

    • Is the status of the product version of the target product active on the planned product change date when you activate the product change (account)? If this is not the case, the system displays an error message.

    • Is the status of the product version of the target product active on the actual product change date when you execute the product change (account)? If this is not the case, the system displays an error message.

  • Payment Item

    When you activate and execute a product change (account), the system checks whether there are payment items for the planned product change date and outputs a warning message if this is the case.

Objects Changed by the System

  • Account

    • The system always changes the following data on the account:

      • Date of event 0010 (Planned Product Change) when you activate the product change (account)

      • Date of event 0009 (Actual Product Change) when you execute the product change (account)

      • Date of event 0003 (Last Account Change) when you activate and execute the product change (account)

    • The system never changes the following data on the account:

      • Contract currency

      • Date of event 0004 (Account Contract Start Date)

      • Date of event 0007 (Account Live from)

      • Date ofevent 0006 (Account Can Be Posted to From)

      • Feature locks

      • Posting locks

      • Account identificationdata

      • Contract-managing organizational unit

      • Contract status

      • Account holder

    • The system can change all the other data on the account, in accordance with the Customizing settings made for the product change (account).

  • Standing Order

    The system checks whether there are standing orders for the account for which a product change is being made. The system also checks if the Standing Order feature no longer applies as a result of the product change. If this is the case, the existing standing orders are deleted.

  • Notice on Amount

    Depending on the setting of attribute BCON01 (existing notices on amount) in the transfer procedure used, the system deactivates existing notices on amount.

    If the attribute origin for the above-mentioned attribute group reflects value 0200 (attribute values of the target product) in the corresponding transfer procedure, the system deactivates the

    notices on amount.

Objects Generated by the System

  • Change Document

    The system generates a change document that meets auditing requirements.

  • Correspondence Request

    The system generates a correspondence request.

  • Flag for mass processing

    When you activate a product change (account) for which the Immediate Product Change indicator is not set, the system generates a flag for mass processing.

  • Work Item

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