Product Change (Card) 

Definition

Account Management (FS-AM) business object that represents the exchange of the product a card is based on (source product) with a target product. The target product can be a new version of the source product or a completely different product. The system always chooses the valid version of the target product.

In Account Management (FS-AM), a product change can be carried out for individual cards and as a mass run for a large number of cards. You can carry out the product change immediately, on a particular date, or event-controlled when a card is exchanged or renewed. An event-controlled product change can be carried out for individual cards or all cards of a product.

A product change for an individual card can be necessary if the customer or bank requires substantial changes to card contracts at a particular time in the present or future, such as changes to the conditions or the scope of functions of the card (such as available limit), or changes to features.

A product change for a large number of cards can be necessary if the bank wants to convert all cards of a particular product to a new product version or product, due to new product structures, enhancements or changes.

A product change for exchange or renewal of a card can be necessary if a product change is planned for a certain date and the card is lost or stolen during a transition phase before this date.

In Account Management (FS-AM), a product change is managed as an order by order management (FS-AM-OM). A product change always has two steps:

...

       1.      To flag the card for a product change, create and activate an order for card product change.

       2.      To carry out the actual product change, execute the order.

During a product change, the history and the central data of the card (such as card holder) are retained. For each attribute group, you can define whether the field values of the source card or the attributes of the target product have priority in a product change.

If a product change is carried out, it could be necessary to create a new plastic card (reproduction of the source card). In the Customizing settings for the card product, you can set the period before expiry of a card in which a reproduction is still possible, and how long before any cancellation date of the card. You can also set which attribute changes in the context of a product change require creation of a new plastic card (attributes requiring reproduction).

Use

The card product change is done either manually in dialog mode or automatically using a Business Application Programming Interface (BAPI).

The card product change function can use 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 change (card) – mass processing	Dialog
BAPCOCP	Product change (card) - BAPI	BAPI
BDCOCP	Product change (card) – BAPI (EDT)	BAPI

When you create or change a card product change in dialog mode, the system enters the Entry Origin and Processing Origin fields. You can use a BAPI to specify an entry or processing origin.

The order status can change during processing of a card product change (see the Order Status of Product Change section).

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 – selected product changes (card pool)
BCA_COCP_TEV	Execute due product changes (card)
BCA_OR_COCP_PP_ALL	Application log – due product changes (card)
BCA_COCP_VERS_CARD	Edit mass product version change (card) - optimized
BCA_COCP_VERS_PP_ALL	Application log – optimized product version change (card)
BCA_OR_COCP_RULE	Edit rules for event-controlled product change (card)
BCA_OR_COCP_PP_ALL	Application log – 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 methods as a test run.

Direct Input

Direct input is not implemented for card product change. You can make external data transfers (EDT) using the BAPIs that have the entry origin or processing origin BDCOCP.

Customer Enhancements

You can find the Business Add-Ins (BAdIs) available for a card product change in the Customizing for Account Management (FS-AM) by choosing Order Management ® Product Change (Card) ® Business Add-Ins (BAdIs).

Structure

Attributes

·        Attributes of 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

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

Integration

You make the settings for card product change in the Customizing for Account Management (FS-AM) under the following structure nodes and in the following IMG activities:

·        Basic Settings ® Maintain Origin Data

·        Order Management ® Basic Settings ® Configure Order Category

·        Order Management ® Product Change (Card)

In addition:

When processing card product changes, the corresponding release object and the various authorization objects have a controlling function for the program flow. The system calls up and processes the following objects from Account Management (FS-AM) when processing the card product change:

Checks

The system checks whether the following conditions are met:

·        The card exists.

·        The card has the status Active. Card status Locked (except for dispatch lock) is also possible, if the product change does not cause a reproduction.

·        If a reproduction is necessary, this must be permitted.

·        The card is not in the release process.

·        Source and target products are accessory products, or source and target products are not accessory products. If the source and target products are accessory products, both products must have the same settings with regard to dependency on an account or card pool.

·        The planned product change date is after the date of the event 0004 Card Contract Start Date.

·        No product change with the order status Active exists for the card.

If one of these requirements has not been met, the system displays an error message.

·        Product

The system checks the following settings and attributes:

¡        Does the target product exist in an active and valid version on the execution date of the product change?

¡        Is the product transition from the card source product to the target product permitted according to the Customizing settings for product change?

¡        Is the product version of the target product status Active on the planned product change date when activating the product change?

¡        Is the product version of the target product status Active on the actual product change date when executing the product change?

If this is not the case, the system displays an error message.

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 if required.

·        Flag for mass processing

When activating a product change (card) 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.

Dependent Cards

For information about product changes for cards that belong to an account/card relationship, see Product Change: Account/Card 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 the Customizing for Account Management (FS-AM) by choosing Order Management ® Product Change (Card) ® Archiving ® Define Residence Time for Product Change (Card).

Product changes (card) with status Created, Deleted, Deactivated and Executed can be archived. However, there cannot be a version of the product change in the release process.

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

Example

·        A customer wants to change his or her card contract. Depending on the product, the changes result in the card changing to an alternative product or product version.

·        A customer wants to change his or her card contract. However, the product change needs to be done when the old card is exchanged or renewed.

·        Due to new product structures, enhancements or changes (within the bank or caused by compulsory events such as new legal regulations), it is necessary to automatically convert the cards affected to a new product version or product.