Show TOC

Change Payment CardLocate this document in the navigation structure

Definition

To change a payment card master record.

Technical Data

Entity Type

Service Operation

Software Component Version

SAP_BS_FOUNDATION 731

Release State

released

Technical Name

PaymentCardSUITEChangeRequestConfirmation_In

Namespace

http://sap.com/xi/SAP_BS_FND/Global2

Application Component

CA-EPT

Web Service Definition (Back End)

BS_PAYTCARDSUITECHGRC

Category

A2X

Direction

inbound

Mode

synchronous

Idempotency

yes

Change/Update Behavior

not applicable

P2P Communication Enabled

true
Business Context and Use

The Change Payment Card inbound operation changes a payment card.

Features

To change a Payment Card, the following data is needed:

Input

All mandatory fields have to be filled.

  • ID (ID of the payment card)

  • blockListCompleteTransmissionIndicator (If this indicator is set, all block items will be deleted, which are not part of the block payload.)

  • CategoryCode (not supported; should therefore not be filled)

  • TypeCode (type of payment card)

  • ValidityStartDate (date from which the payment card is valid)

  • ExpirationDate (date up to which the payment card is valid)

  • IssueDate (date the payment card was issued)

  • HolderName (name of the person or company to whom the payment card was issued)

  • IssuerName (bank that issued the payment card)

  • Block

    • PaymentCardBlockingReasonCode (ndicates whether a payment card is blocked and for what reason)

    • ActionCode (If the ActionCode is empty the default 01 = create is used automatically; only ActionCodes 01 (Create) and 03 (Delete) are supported.)

    • ValidityPeriod

      • StartDate (date as of which the payment card block is valid)

      • EndDate (date up to which the payment card block is valid)

      • Duration (not supported; should therefore not be filled)

Output

Output

For security reasons, the payment card ID which corresponds to the payment card number in the SAP Business Suite back-end system is not displayed. Instead the Payment Card MaskedID of the payment card master record is displayed, which has been created by the current service operation. The security level can be adjusted in Customizing of the SAP Business Suite back-end system underCross Application Components -> Payment Cards -> Basic Settings -> Maintain Security Settings for Payment Cards.If the Customizing is not maintained only the first five and the last two digits of the card number are displayed (for example 99341*********77).   

For security reasons, the payment card ID which corresponds to the payment card number in the SAP Business Suite back-end system is not displayed. Instead the Payment Card MaskedID of the payment card master record is displayed, which has been created by the current service operation. The security level can be adjusted in Customizing of the SAP Business Suite back-end system under Cross Application Components -> Payment Cards -> Basic Settings -> Maintain Security Settings for Payment Cards. If the Customizing is not maintained only the first five and the last two digits of the card number are displayed (for example 99341*********77).   

Error Handling

If errors occur, tThe system issues an error log.

Message Types

  • PaymentCardSUITEChangeConfirmation_sync

  • PaymentCardSUITEChangeRequest_sync

Prerequisites

You have created a payment card master record.

Constraints

ActionCode 02 used to change the block of a payment card is not supported. As an alternative you can delete the block and then create a new block

Notes on SAP Implementation

Configuration

You must run the application component Payment Card (AP-MD-PCA). You have defined at least one payment card type in Customizing under Cross Application Components -> Payment Cards -> Basic Settings -> Maintain Payment Card Type .

Depending on the Customizing settings you have made for the security level, the system:

  • Encrypts payment card numbers when they are saved  

  • Masks payment card numbers in the service confirmation message

You set the security level in Customizing under Cross Application Components -> Payment Cards -> Basic Settings -> Maintain Security Settings for Payment Cards .

In addition, to ensure secure handling of payment card information in the SAP Business Suite, you must deactivate the recording of service calls in the PI monitor (also see SAP note  1032588).

 

Enhancements

There are three Business Add-Ins available to enhance the current operation:

  • Change Payment Card ( PYCD _ESOA_PAYTCARDCHGRC), e nhancement spot PYCD_SPOT_ESOA_PAYT_CARDMethod INBOUND_PROCESSING of this BAdI is processed at the beginning of the operation. Using this method you can run checks and modify the input data. Method OUTBOUND_PROCESSING is processed at the end of the operation. Using this method you can modify the values in the response message before they are sent to the consumer.

  • Mapping for Blocking Reason Code ( PYCD_ESOAMAP_PAYTCARDBLCKREAS), e nhancement spot PYCD_SPOT_ESOA_PAYT_CARD Using Method MAP_EXT2INT, you can implement your own value mapping for the external field PaymentCardBlockingReasonCode to the payment card block (data element CC_LOCK ) in the SAP Buisness Suite back-end system. Using Method MAP_INT2EXT, you can implement your own value mapping for the  payment card block (data element CC_LOCK ) in the SAP Business Suite back-end system to the   external field PaymentCardBlockingReasonCode.

  • Mapping of Payment Card Type (BSBP_ESAMAP_PAYMNTCRDTYPE), e nhancement spot BSBP_ESAMAP_PAYMNTCRDTYPE Met hod: MAP_EXT2INT Using Method MAP_EXT2INT, you can implement your own value mapping for the  external field TypeCode to the payment card type (data element CC_INSTITUTE) in the SAP Buisness Suite back-end system. Using Method MAP_INT2EXT, you can implement your own value mapping for the  payment card type in the SAP Business Suite back-end system to the to the external field TypeCode.