Product Change (Card)

Business object in Account Management (FS-AM) that maps the exchange of a product (source product) that is based on a

card with a target product. The target product can be a new version of the source product or another product. The system always chooses the valid version of the target product.

In Account Management (FS-AM), a product change is possible for individual cards and as a mass run for multiple cards. You can carry out the product change immediately, on a certain date, or have it event-controlled when a card is exchanged or renewed. You can carry out an event-controlled product change for individual cards or for all cards of a product.

A product change for an individual card can be necessary if the customer or the bank wants to make the following essential changes to the card contract on a certain current or future date, for example:

Changes to the conditions
Adjustment of the scope of functions of the card (such as credit lines)
Changes to features

A product change for multiple cards can be necessary if the bank wants to change all cards of a certain product to a new product version or a new product due to redesigned products, product enhancements, or product changes.

A product change when exchanging or renewing a card can be necessary if a product change is scheduled for a certain date and the card goes missing in a transition phase before this date due to theft or loss.

The product change is managed in the Account Management (FS-AM) system as an order

by Order Management (FS-AM-OM). A product change always takes place in two steps:

Flag the card for a product change: create an order for the card product change and activate the order.
Carry out the product change: execute the order.

The history of the card and the central card data (such as the card holder) remain intact for the product change. For every attribute group, you can define whether the field values of the source card take precedence for the product change or the attributes of the target product.

When a product change is carried out, it can be necessary to also create a new plastic card (reproduction of the source card). For this reason, in Customizing for the card product, you can set during which period before the due date of a card and how long before a possible cancellation date of the card a reproduction is still possible. In Customizing, you can also define which attribute changes in the context of a product change require you to create a new plastic card (attributes requiring reproduction).

A card product change takes places either in the dialog or by means of a

Business Application Programming Interface (BAPI).

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

Entry Origin Processing Origin	Short Description	Channel
BOCOCP	Product Change (Card) - Dialog	Dialog
COCPPP	Mass Product Change (Card) - Mass Processing	Dialog
COCPCA	Due Product Changes (Card) - Mass Processing	Dialog
BAPCOCP	Product Change (Card) - BAPI	BAPI
BDCOCP	Product Change (Card) - BAPI (EDT)	BAPI

Methods

Dialog

You can call up the following transactions in dialog mode:

Transaction Code	Short Description
BCA_OR_COCP	Change Card Product
BCA_COCP_CARD	Edit Mass Product Change (Card)
BCA_CP_COCP_PP_ALL	Application Log of Selected Product Changes (Card)
BCA_COCP_TEV	Execute Due Product Changes (Card)
BCA_OR_COCP_PP_ALL	Application Log of Due Product Changes (Card)
BCA_COCP_VERS_CARD	Edit Mass Product Version Change (Card) - Optimized
BCA_COCP_VERS_PP_ALL	Application Log of Optimized Product Changes (Card)
BCA_OR_COCP_RULE	Edit Rules for Event-Controlled Product Changes (Card)
BCA_OR_COCP_PP_ALL	Application Log of Due Product Changes (Card)

Business Application Programming Interface

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

Method*	Short Description
ProductChangeCard.CreateAndActivate	Create and activate product change (card pool)
ProductChangeCard.ChangeAndActivate	Change and activate product change (card pool)
ProductChange.ChangeAndDeactivate	Change and deactivate product change (card pool)
ProductChange.GetDetail	Read product change (card pool)
ProductChange.GetOrdersByCard	Read order numbers of product change (card pool)

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

When you create or change a card product change in the dialog, the system enters the entry and processing origin fields. Using a BAPI, you yourself have the option of specifying an entry or processing origin.

When you process a card product change, the order status can change (see Order Status of Product Changes).

Direct Input

Direct input is not implemented for card product changes. You can carry out the external data transfer (EDT) by means of BAPI with the entry or processing origin BDCOCP.

Customer Enhancements

For the Business Add-Ins (BAdIs) that are available to you for card product changes, see Customizing for Account Management (FS-AM) under Start of the navigation path Order Management Next navigation step Product Change (Card) Business Add-Ins (BAdIs) End of the navigation path .

Structure

Attributes

Attributes in Order Management
Target product
Transfer procedure
Planned product change date
Actual product change date
Correspondence for product change
Future contract changes
Immediate product change
Reference attributes
The reference attributes refer to other objects in Account Management (FS-AM). See the documentation linked to below in the "Integration" section.

Integration

You make the settings for card change in the Customizing for Account Management (FS-AM) under the following grouping nodes or in the following Customizing activities:

Basic Settings Maintain Origin Data
Order Management Basic Settings Configure Order Category
Order Management Product Change (Card)

When you are processing card product changes, 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 objects in Account Management (FS-AM) when processing card product changes:

Checks

The system checks whether the following conditions are met:

The card exists.
The card status of the card is Active. The card status Locked (with the exception of a dispatch lock) is also possible, if the product change does not trigger a reproduction.
If a reproduction is required, this must be allowed.
The card is not in the release process.
The source and target product are accessory products, or the source and target product are not accessory products. If the source and target product are accessory products, both product must have the same settings with regard to the dependency to an account or a card pool.
The planned product change date is after the date of the event 0004 Card Contract Start Date.
There is no product change for the card with the order status Active.
If at least one of the following is not met, the system displays an error message.
Product
The system checks the following settings:
- The target product must exist in an active and valid version on the execution date of the product change.
- The product transition from the source product of the card to the target product must be allowed in accordance with the Customizing for the product change.
- The status of the product version of the target product must be Active on the planned product change date when you activate the product change.
- The status of the product version of the target product must be Active on the actual product change date when you execute the product change.
- If you have made security settings for card numbers, the source product must have the same security settings as the target product.
If these criteria have not been fulfilled, the system generates an error message.

Objects Generated by the System

Change document
The system generates a change document that meets auditing requirements.
Correspondence request
If desired, the system generates a correspondence request.
Flag for mass processing
When you activate an product change (card), if 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.

Dependent Cards

For more information about a product change for cards belonging to a linked account relationship, see Product Change for Linked Account Relationship.

Archiving

You can specify that product changes (card) are archived after a particular period of time has expired. You define this period of time for each bank posting area, product, and order status in Customizing for Account Management (FS-AM) under Start of the navigation path Order Management Next navigation step Product Change (Card) Archiving Define Residence Time for Product Change (Card). End of the navigation path

You can archive product changes (card) that have the status Entered, Deleted, Deactivated, and Executed. However, no version of the product change may be in the release process.

For more information about archiving, see Data Archiving in Account Management (FS-AM).

Example

Due to changed requirements, a customer would like to have his/her card contract revised or adjusted. Due to the product, the changes require you to change the card to an alternative product or to a new product version.
Due to changed requirements, a customer would like to have his/her card contract revised or adjusted. However, the product change is not to take place until the old card is exchanged or renewed.
As a result of redesigned products, enhancements or product changes (within the bank or triggered by forced events, such as new legal requirements), an automatic conversion of the cards involved to a new product version or a new product becomes necessary.