Description
This program transfers subscription changes from the legacy system intoIS-M/SD.

Procedure for data transfer:
Subscription changes in the legacy system that do not contain errorsare posted directly to IS-M/SD (with CALL TRANSACTION USING...).
If the input record cannot be transferred due to an error situation,the following two cases are possible:

• It is possible to determine the item for which a change is to be made:
==> The errored record is included in a BDC error session.

• It is not possible to determine the item for which the change is to be
made: ==> The errored record is saved in an error table (JKTMEMORY).
Information on whether data transfer was successful is saved in tableTJY09. Data transfer was successful if all input records weretransferred or all errored records were saved in BDC sessions. Pleasenote that the error sessions must still be processed.
If data transfer is unsuccessful, this can have the following causes:

• System crash during data transfer


• Subscription changes for transfer cannot be saved in a BDC error
session due to an error that occurred beforehand (for example, an errorduring transfer of the live subscriptions).
If data transfer was unsuccessful, you can restart the transfer programas often as required until the transfer has been completed successfully(for this reason, several BDC error sessions can be generated for theerrored records in a legacy data file. These sessions must all have thesame session name.)
The following information on the status of data transfer is stored foreach legacy file in table TJY09:

• Number of records imported from legacy file until this point


• Indicator denoting whether or not the legacy file was imported fully


• Indicator denoting whether or not error processing is completed (if
errored records exist, these are saved in BDC error sessions).

• Name of BDC error sessions in which errored records were saved.

Data updated
The program transfers subscription changes from the legacy system toIS-M/SD.
The following subscription changes are transferred:


• Changes to and deletion of standard items

(Not creation of standard items; see transfer of live subscriptions)

• Changes to and deletion of free items

(Not creation of free items; see transfer of live subscriptions)

• Changes to and deletion of trial items

(Not creation of trial items; see transfer of live subscriptions)

• Creation, change and deletion of suspensions


• Creation, change and deletion of partial suspensions


• Creation, change and deletion of redirections


• Creation, change and deletion of additional copy redirections


• Creation, change and deletion of transfers


• Creation, change and deletion of gift transfers


• Creation, change and deletion of unlimited changes


• Creation, change and deletion of terminations

(Creation, change and deletion of terminations is only transferred if
the termination is not yet completed (similar to dialog function))

• Conversion of a trial item to a standard item (this takes place using

the activity type 'Create')
(Change and deletion are not possible with this function)

• Conversion of a free item to a standard item (this takes place using

the activity type 'Create')

• (Change and deletion are not possible with this function)

In the case of changes to the item period, please note that onlychanges in which the old and new periods overlap can be transferred. Ifthis is not the case, the old status of the item must be deleted andthe new status then created (two records are required for this in thetransfer file: the old status of the item with the activity type 'L'and the new status with the activity type 'H').

Interface definition
The data on an item change is distributed between the followingsegments (for a structural description, see the Data Dictionary):


• RJKIF_S_ITEM ,,- General item data ,,(record type: 02)


• RJKIF_ITEMCC, ,,- Payment card data ,,(record type: 03)


• RJKIF_S_ITEMWBZ ,,- WBZ data ,,(record type: 04)


• RJKIF_ADDRESS ,,- Add.data for alt.S-T pty ,,(record type: 05)

The segments for an item that belong to a change must be present insequence in the dataset, although segments of record types 03, 04 and05 are optional.
For a description of the interface, please see the programdocumentation on the include RJKDFABO.
Unlike the entry requirements for the fields specified in the abovedocumentation, only fields REFBELEG, SATZART, FUNKTION, AKTIVTYP andGUELTIGVON are required fields when transferring changes.
The structure RJKIF_S_HEAD mentioned in this documentation (record type01) is not required (in fact not admissible) when transferring changes.
For a description of the individual fields, please see the onlinedocumentation.
Similarly to the functions in dialog processing, you need only makeentries in the fields that can also be entered in dialog for therelevant functions and activity types.
Transfer of subscription changes transfers the fields from theinterface that have a value other than the 'No data'indicator on the selection screen.
The following values are allowed for the fields FUNKTION and AKTIVTYP:

• FUNKTION:

'01' : Standard item
'02' : Free item
'03' : Trial item
'04' : Suspension
'05' : Partial suspension
'06' : Redirection
'07' : Additional copy redirection
'08' : Transfer
'09' : Gift transfer
'10' : Unlimited change
'11' : Termination
'13' : Conversion of trial item to standard item
'14' : Conversion of free item to standard item

• AKTIVTYP:

'H' : Create
'V' : Change
'L' : Delete

Selection options
The following data is specified for the transfer file:


• Name of transfer file


• Indicator marking a field as irrelevant ('No data' indicator)


• Function determining whether data transfer is to be restarted


• Test run: all activities are only performed as a test; no session is
created

• Name of BDC session


• Blocking date for processing BDC session


• Indicator determining whether or not the BDC session is to be retained
after processing.

Output
The program outputs a log of the data transfer.


• Number of records read


• Number of records processed successfully


• Number of errored records and those that cannot be processed


• Number of successful transactions


• Number of errored transactions


• Number of transactions placed in the batch input session


• Information on each errored record

You can double click on the record number to display the record indialog processing.
Double click on the fields in the error message to access details onthe message.