Kontakt

Ansicht
Dokumentation

RJHADU01 - IS-M/AM: Data Transfer of (New) Orders from Previous System

RJHADU01 - IS-M/AM: Data Transfer of (New) Orders from Previous System

Vendor Master (General Section)   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program is used to transfer ad, ad insert and online orders from an external system to the IS-M/AM System. (New orders)
New items can be added to orders that have already been transferred during this process. This is only possible if a new item number is used to do so in the interface records.
If the order item transferred in the interface already exists (was transferred), the system ignores this and does not create a new item.

Orders are NOT transferred using batch input, but rather using a function module that checks the orders 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.

Interfaces
This program is used to transfer ad, ad insert and online orders. The structure of the interface records is different for each item type. This means that it is necessary to create a separate sequential file for data transfer for each item type. (Information about file creation)

Errored records
The system does not update errored orders but places these in a batch input session (error session) instead. This session is only created for the 'ad' and 'online' item types. This session can be used to postprocess orders that cannot be updated. It can be run in an open form which enables errored data to be processed in dialog mode. The system displays the respective error message in the log for each errored record.
Note: Address selection is not possible for orders that were created using the error session. The system always uses the central address for the business partner involved within the program.

Batch input session
If direct input is not to be used to transfer ad items, data transfer can be controlled directly in the batch input session by activating the Transfer by batch input only selection parameter.

  • Batch input transfer must be activated if CPD orders are to be transferred.
    Direct input does not support CPD transfer.
    More detailed information about CPD transfer can be found in the interface structures RJHANZKOPF and RJHANZISZ.

Test run The program can be started in test mode for direct input. The system generates an error log in this mode but does not run any database updates or generate any error sessions. To identify errors early, such as incomplete Customizing settings, you can process a certain number of documents intended for processing in the test mode. This allows you to test the transfer process for a limited number of orders.

Restart procedure
The program can be restarted. If data transfer is terminated (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 continue where it left off. In this instance, the 'Restart' button should be activated when the program is executed.

Migration support tools

The Generate table description ABAP Dictionary function can be used to generate a description of the structure for various programming languages.

  • You will find the migration support tools that describe the process and the test in the IS-M/AM Sales menu under: Environment -> Order data transfer -> Tools.

Requirements

All master data required for IS-M/AM order transfer such as business partner, booking units, ad inserts must have been created previously.
The same applies to elements that can be assigned additionally such as contracts, sales agent contracts etc.

When you start the program, you should 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.
The records in the input file have different structures. A record is identified using the 'SATZART' field.

Buffer number range objects
For reasons of performance, you should buffer the number range objects affected, such as the number range for KONV, during productive data transfer or for the mass testing of data transfer. If you are transferring orders with internal number assignment, you should also buffer the number range object for the orders.

Ad orders

The following record types are possible for ad transfer:

RecType Meaning
01 Header record
02 Item record
03 Booking unit assignment record
04 Date assignment record
06 Advertiser assignment record
07 Ad spec record
08 Business partner assignment record
10 Sales agents for the item
13 Text records for the item
16 Documents for the ad spec
Record types 01, 02, 03, 06 and 07 MUST be transferred for each order in ASCENDING order for creation. The system creates a new order for each 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 order number.
Example : Interface records request for an ad order
||AVM_NR | FRD_AVM_NR | POS_NR | SATZ_ART | SART_REIFO |...data..||Rec
||---------------------------------------------------------------||-----
|| 4711 | EXT123-45 | 000 | 01 | 01 | ... ||hdr
|| 4711 | EXT123-45 | 010 | 02 | 01 | ... ||itm
|| 4711 | EXT123-45 | 010 | 03 | 01 | ... ||Bpz
|| 4711 | EXT123-45 | 010 | 03 | 02 | ... ||Bpz
|| 4711 | EXT123-45 | 010 | 03 | 03 | ... ||Bpz
|| 4711 | EXT123-45 | 010 | 06 | 01 | ... ||Isz
|| 4711 | EXT123-45 | 010 | 07 | 01 | ... ||Mot
|| 4711 | EXT123-45 | 010 | 08 | 01 | ... ||GPZ
|| 4711 | EXT123-45 | 010 | 08 | 02 | ... ||GPZ
|| 4711 | EXT123-45 | 010 | 08 | 03 | ... ||GPZ
|| 4711 | EXT123-45 | 010 | 08 | 04 | ... ||GPZ
|| 4711 | EXT123-45 | 010 | 13 | 01 | ... ||TXT
|| 4711 | EXT123-45 | 010 | 16 | 01 | ... ||DRV
|| 4711 | EXT123-45 | 020 | 02 | 01 | ... ||Pos
|| 4711 | EXT123-45 | 020 | 03 | 01 | ... ||Bpz
|| 4711 | EXT123-45 | 020 | 03 | 02 | ... ||Bpz
... etc.
The system starts a new order with a header record.

Defined fields

You will find a detailed description of the record types in the

following structure documentation:

  • RJHANZISZfor the advertiser assignment record

Ad insert orders

Record types for transferring ad insert orders

RecType Meaning
01 Header record
02 Item record
03 Booking unit assignment record
06 Advertiser assignment record
08 Business partner assignment record
10 Sales agents for the item
13 Text records for the item
17 Sub-item record
Record types 01, 02, 03, and 06 MUST be transferred for each order in ASCENDING order for creation. The system creates a new order for each header record (record type =01).
Only one booking unit can be assigned for each item.
The date and the ad insert number must be unique in the transfer structure for the item. A unique ad insert number means that the ad inserts must be created first in dialog processing or using batch input, so that the number can also be transferred in the order transfer tables.
If one of the required record types is missing, this will be noted in the error log with the reference order number.

Defined fields

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

  • RJHANZISZfor the advertiser assignment record

Online orders

Record types for transferring online orders

RecType Meaning
01 Header record
02 Item record
06 Advertiser assignment record
07 Ad spec record
08 Business partner assignment record
10 Sales agents for the item
13 Text records for the item
16 Ad spec master assignment record
18 Item BU/CC assignment record
19 Target group assignment record
Record types 01, 02, 06, 07, and 18 MUST be transferred for each order in ASCENDING order for creation. The system creates a new order for each 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 order number.

Defined fields

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

  • RJHANZISZfor the advertiser assignment record

  • RJHANZDRVfor the ad spec master assignment record

  • RJHONLIKZfor the item BU/CC assignment record

  • RJHONLTGZfor the target group assignment record

The Generate table description ABAP Dictionary function can be used to generate a description of the structure for various programming languages.






BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 16989 Date: 20240520 Time: 081449     sap01-206 ( 164 ms )