Ansicht
Dokumentation

RCCLBI02 - Batch Input: Create Classification Data

RCCLBI02 - Batch Input: Create Classification Data

Addresses (Business Address Services)   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Description

This program generates batch input for the following classification functions.

  • Allocation -> Object to classes
  • Allocation -> Class to classes
Note
You cannot use this program to classify batches. To generate batch input for batches, use transaction MSC1 to write your own program.
  • Dataset name
  • Generate session indicator

The dataset name shows the path to the external data that is to be processed via batch input. The file must have the following structure:

  • Session header record (Table BGR00)
  • Allocation data of record type "1" (Table BIKSSK)
  • Assigned value data of record type "2" (Table BIAUSP)

The following restrictions apply:

  • A data file can only process either the allocation of objects to classes or classes to classes.
  • You can only process data for one class type.
  • The objects in table BIKSSK must be sorted.
  • If a batch input session is to be generated, there must be no session header record between two allocation records with the same object number.

If this indicator is not set, the classification data is created immediately using CALL TRANSACTION USING. Otherwise, one or more sessions are created, which can then be processed either online or in batch mode.

Required data

Table BIKSSK must contain the following entries.

Field Value
STYPE 1
TCODE CL20 or CL22
MAFID O (Object) or K (class)
KLART Vlass type suitable for object
OBJEK Object number or class
CLASS Class
STATU Classification status
STDCL Standard class indicator
XLINE For internal use only
OBTAB For CL20: table from TCLAO, if more than one object can be
classified with a class type

Table BIAUSP must contain the following entries.

Field Value
STYPE 2
XLINE Line index = initial
ATNAM Language-independent characteristic name
ATWRT Language-independent characteristic value

The classes, objects, and characteristics must exist in the target system.

Requirements

Before you can start this program, you must extract the data from the source system and write this data to a sequential file. To do this, create a program in the source system that collects the data in the format required and generates the sequential file.

You must define a logical file name for the sequential file in Customizing. This name forms the link to the physical file name. You can enter the logical file name when you start the program, by displaying the help on the logical file name field.

Output

An error log is output.

Example

Example for creating a batch input dataset.

  • Open dataset
OPEN DATASET DS_NAME FOR OUTPUT IN TEXT MODE.
  • Enter session header data in table BGR00
TRANSFER BGR00 TO DATASET DS_NAME.
  • Enter allocation record with record type "1" transaction and the data of the external system (for example, object number 4711;class DEMK1; this class has the characteristic COLOR with the values RED and BLACK)
TRANSFER BIKSSK TO DATASET DS_NAME.
  • Enter value data in BIAUSP with record type "2" and the data of the external system (for example, characteristic COLOR;value RED)
TRANSFER BIAUSP TO DATASET DS_NAME.
  • Enter value data in BIAUSP with record type "2" and the data of the external system (for example, characteristic COLOR;value BLACK)
TRANSFER BIAUSP TO DATASET DS_NAME.
  • Enter allocation record with record type "1" transaction and the data of the external system (for example, object number 4711;class DEMK2; the class has the characteristic HEIGHT with the values 1-20)
TRANSFER BIKSSK TO DATASET DS_NAME.
  • Enter value data in BIAUSP with record type "2" and the data of the external system (for example, characteristic HEIGHT;values 1-20)
TRANSFER BIAUSP TO DATASET DS_NAME.
  • Close dataset.
CLOSE DATASET DS_NAME.

A new session is created for each BGR00 record. The name of the dataset (DS_NAME) is required later during batch input. The sessions are generated from the datasets in the sequential file.






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 6512 Date: 20240601 Time: 212232     sap01-206 ( 69 ms )