Show TOC

 Process Flow for Change Payment Data

Purpose

You can integrate the Internet Application Component Change Payment Data at a suitable point on your company's homepage. You must add a key to the URL used to access the application, referencing the relevant Customizing settings. Like all the other IACs from subscription sales and subscription service, the application can be offered in a number of variants at the same time (you can design it in different ways using the theme concept; for further information, please see the general ITS documentation).

Process Flow

You can design the following two methods for the customer to log on to the Internet Application Component:

  • Explicit logon on a logon screen or

  • Implicit logon on the change form

Choose the procedure you prefer depending on your requirements; an indicator in the Customizing settings for identifying and checking business partners must either be selected or left blank depending on your choice.

  • Explicit logon on a logon screen

    1. On a logon screen (template SAPMJKWWW04_0100.HTML), the customer is asked to log on to the system with certain data. You can define which data this is in the Customizing settings and in the design of the HTML template for logon.

    2. Once the customer has logged on correctly, the change form appears (template SAPMJKWWW04_0200.HTML). Depending on how you design the form, data on the customer's address and on existing orders can be displayed here. Besides choosing the orders to be changed, the customer specifies the new payment data and the start date of the change on this form.

    3. The data entered is checked when the customer saves it; the system checks both the payment data itself and checks to determine whether the change overlaps with other planned changes to the customer's orders. If the data is accepted, the changes are updated in the system and the confirmation screen appears (template SAPMJKWWW04_0300.HTML). The most important data is displayed here again.

  • Implicit logon on the change form

    1. If logon takes place implicitly on the change form, the change form (template SAPMJKWWW04_0200.HTML) is displayed immediately when the customer calls up the IAC (e.g. by clicking a hyperlink on your homepage). In contrast to the process flow described above, logon fields have now been added to this form. The customer enters their new payment data and some logon data.

    2. When they save the data, the system identifies and checks the customer. If the checks are successful, the system reads the customer's order data. The system checks whether the changes are possible for all active orders; if this is the case, the confirmation screen (template SAPMJKWWW04_0300.HTML) is displayed as in the first process flow. If an error occurs while the data is being checked (e.g. the change overlaps with a planned change), the application behaves as in the first process flow. The orders can now be displayed for the customer; the logon fields are hidden dynamically. Fields or entire areas can be shown or hidden in the HTML templates depending on the content of certain fields.

Result

The customer's payment data has been changed from the desired date, i.e. an unlimited change was created for this date in the order. If new payment data, such as a new bank connection, was entered, this is also recorded in the customer's master record. Alternatively, the data is stored initially in the temporary table, where it can be postedited.