Ansicht
Dokumentation

Due Day-Controlled Monitoring of Renewal Subscriptions ( RELNISMSD_464_K_REMIND02 )

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Short text

Due Day-Controlled Monitoring of Renewal Subscriptions

Use

As of IS-M Release 4.64, monitoring of renewal subscriptions is controlled by means of the new field Due Day (day on which the payment amount is due).
This means the payment amount for renewal subscriptions that are paid by credit card or automatic debit can be collected on certain days in the month.

You can specify the following for each order by means of the due day (on the billing details screen):

• Due day initial: the due day is the same as the expiration date.

• Due day set: the due day is calculated from the expiration date (the due day is the last due date before the expiration date, according to the billing frequency).

Balancing days

Because not all months are the same length and, for example, Sunday editions may be more expensive, an installment can sometimes be higher or lower than the normal period installment. This fact can be taken into account by means of balancing days in the monitoring procedure. (Maintain Monitoring Procedures).

Example: A daily newspaper (weekday and Sunday edition) is paid in monthly installments, which are due on the first day of each month. The following cases are possible:

• In February (28 days, 4 of which are Sundays) the monthly installment is not used up and a credit balance is left in the liability account.

• In July (31 days, 5 of which are Sundays), the monthly installment only covers 29 days. The subscriber receives the last two issues in July even though these have not been paid for.

Payments in excess and underpayments are not cleared for the individual months until a full year has passed.

Calculating the first installments

When a new subscription begins, the first offer covers the start-up period and the first billing period. This means the first installment is usually greater than a normal period installment. Other offers each cover one billing period.

Example: The subscriber chooses a quarterly newspaper on the 15th. The subscription begins on July 20th. The first offer covers the start-up period from July 20th through August 15th and the first billing period, August 15th - November 15th. The first installment therefore covers the period from July 20th to November 15th.

Remaining amounts on liability account

If suspensions within a period result in amounts in the liability account that are not used up, these are retained until they add up to a full installment. The due date is then postponed by one full billing period; in other words, monitoring is skipped once.

Effects on Existing Data

The following new fields have been added for due day-controlled monitoring of renewal subscriptions:

• JKKD-DUEDAY
  Due day containing initial value as default

• JKREMIND-DUEDATE_BASE
  Due date when offer created, initialized with JKACCOUNT-EXPDATE

• JKAPRENEW-DUEDATE
  Current due date, initialized with JKAPRENEW-EXPDATE

Effects on Data Transfer

These new fields can be supplied with values during data transfer from the legacy system:

• Transfer of 'normal' order data:
  Structure RJKIF_S_ITEM, new field DUEDAY

• Transfer of renewal data:
  Structure RJKIF_S_ITEMREMIND, new field DUEDATE_BASE_PRESYS

Effects on System Administration

Correct initialization of the new fields JKREMIND-DUEDATE_BASE and JKAPRENEW-DUEDATE is performed during the Release upgrade by the XPRA RJKXPRA464_DUEDATE.

Effects on Customizing

You can maintain balancing days when maintaining monitoring procedures (Maintain Monitoring Procedures).

You can use the user exit EXIT_SAPLJKRR01_001 (enhancement JKRENEW0) to calculate the due date according to company-specific logic. The result of this due date determination process is saved with the order.
The user exit EXIT_SAPLJKREMIND_003 in the same enhancement allows you to move the due date temporarily during the monitoring process, thus delaying monitoring or triggering it earlier than planned.

Addresses (Business Address Services)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4714 Date: 20240520 Time: 174002     sap01-206 ( 73 ms )