Kontakt

Ansicht
Dokumentation

RJHADU02 - IS-M/AM: Data Transfer of Contracts from Previous System

RJHADU02 - IS-M/AM: Data Transfer of Contracts from Previous System

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program is used to transfer contracts from an external system to the IS-M/AM System.
Contracts are not transferred using batch input, but rather using a function module that checks the contractss and then creates them in the IS-M/AM System. This method is more favourable in terms of performance than the batch input method. A database commit occurs in each case after n documents. The number n can be specified on the selection screen.
Warning: If you want to copy sales agent assignments, a database commit should be performed for each document.

Interfaces
This program should be used to transfer contracts with items and their business partner assignments (agencies, sales agents and beneficiaries).
Interface records should be prepared for data transfer in a sequential file. (Information about file creation).

Errored records
Errored contracts will not be updated, but will be stored in a batch input session (error session). This session can be used to perform postprocessing of contracts that cannot be updated. It can be run in an open form which enables errored data to be processed in online mode. The respective error message will be displayed in the log for each errored record.

Test run
The program can be started in test mode. In this mode, an error log will be generated but no database updates will be run and no error session will be generated. To identify errors early, e.g. incomplete Customizing settings, you can enter a number of documents to be processed in the test mode. This allows you to test the transfer process for a limited number of contracts without having to create a special file.

Restart procedure
The program can be restarted. If data transfer is terminated (e.g. due to a tablespace overflow or a system shutdown), it can be restarted. The program will skip the records that have already been updated and will continue where it left off. In this instance, the 'Restart' button should be activated when the program is executed.

Buffer number range objects
When contracts are transferred, an internal number must be assigned for each contract. You must buffer the number range object ISP_ABNR.

Requirements

When you start the program, please enter the name of the file in which the data to be transferred is to be stored. The restart procedure means that the length of the file name is limited to 22 characters. You maintain the path and the name of the input file using the transactions SF01 to SF06. (Customizing/Basic/File names/...)
The records in the input file have different structures. A record is identified using the 'SATZART' field.

The following record types are possible for ad transfer:

RecType Meaning
01 Header record
02 Item record
03 Agency assignment record
04 Sales agent assignment record
05 Beneficiary assignment record
Record types 01 and 02 must be transferred for each contract in ASCENDING order for creation. A new contract is created for each new header record (record type =01). If one of the required record types is missing, this will be noted in the error log with the reference contract number.

Example of record type sequence for a contract:

01 Header record
02 Item record
02 Item record
03 Agency assignment record
03 Agency assignment record
01 Header record
:,
:, ...etc.

Defined fields

You will find a detailed description of the record types in the following structure documentation:

You can use the data dictionary function Generate table description to generate a description of the structure for various programming languages.






General Material Data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 5985 Date: 20240531 Time: 080249     sap01-206 ( 94 ms )