Previous Topic

Book Contents

Book Index

Next Topic

Field Definitions

About the field definitions it is communicated to the data base, where a value stands in the input record and in into which field of the interface data base it is to be placed. I.e. a field definition must be provided for each value per type of clause, which you want to take over from the input data.

Some fields cannot be filled from the input record, e.g. client or carrier system. They must be assigned over a direct value.

For a service value the following fields must be filled:

  • client
  • carrier system
  • service output (data).  The period is found by the transfer program if it is seized in master data.  
  • one of the LNID's
  • service type
  • quantity or value
  • account characteristic (may not be blank)

If one of these fields is not defined, you receive an appropriate reference with the generation of the transfer program. Are the carrier system, the service type or the period missing, these sentences will be take over, but you recognize this in the data base at the account characteristics S3 - to S5 (s. also with account characteristics).

A field definition consists of the following data:

Record type:

You register the record format numbers, which you put on under the function ' type of clause '.  For each type of clause which you defined, all fields which can be taken over must be described.

Service value number:

From an input record, several service values can be taken over.  In addition the service values must be numbered consecutively.

Field name

The target field from the interface data base, to which the value is to be transferred.  Valid field names and their formats find you in the chapter ' value definitions '.

Field, start/end column

You indicate here the position and/or column name of the value which can be taken over in the input record.  At least, two of the three fields must be filled, the third is determined by the system.

Field type

Indicates the field type of the value from the input record and/or column, which can be taken over.  The following types can be processed by the transfer program (in parentheses those stands for COBOL format instruction, which is generated from it):

Format

Description

X

alphanumeric (PIC X)

N

numeric field (PIC 9)

C

binaric number (PIC COMP).

C3

fix comma number (PIC COMP-3). Only for this type you have to enter the right comma positions.

DD

decimal definition. In this case you can define every Cobol format. You have to enter in the field 'direct- value' the picture instruction for Cobol..

L

literal. In this case, no value from the input set will be taken over, in  'field' must not entered any statements. A value has to be entered in  'direct- value'.

ZZ

free numeric format e.g. for printing. The entering field can have blanks before and after and signs. Decimal commas and points are allowed, too.

Not allowed are separate points and commas for thousand mark note

With the using, these data type will be proofed and converted for the insert in the data base.

Right comma positions

Number of right-of-comma positions for fields with type ' C3 '.  The number of right-of-comma positions must be smaller than the number of places altogether.

Direct value

Here you can register the value for the type ' L ', which is to be placed into the field under ' field name ' (with or without inverted comma).  For the type of ' dd ', you enter here the Picture instruction for this field in COBOL.  It is placed directly as you enter it into the generated transfer program, i.e. also the respective length specification must be indicated here correctly.  Most frequent applications are numeric data in the floating POINT format.  In addition to this, you enter then in the field ' direct value ' to Comp-2.  In this case, no PIC must be indicated in addition (special case in the COBOL).  All other formats with PIC (e.g. PIC Z99).

The following rules apply to the field types:

  • If the target field is a character string, then also the field from the input record must be a character string.  A number packed in the account data cannot be transferred to an alphanumeric field.
  • If the target field is a number and as type if ZZ is not defined, then the original field must likewise be a number or a purely numeric character string (does not prepare, thus without point, comma, sign or blank).
  • Data conversions are not possible.  If they are needed, a userexit has to be written.

See Also

Interface

Carrier

Carrier Type

Record Type

Record Type Conditions