oplan_48Record identification codes

Nach oben  Vorige Seite  Nächste Seite

A record

A work plan category can be defined in an A record. The category can map a group of work plans.

S record

An S-record is used for transferring the work plan selectors. The work plan selectors represent the work plans, which are composed of individual working processes. An S record is connected to a category selector if this has been transferred previously. Otherwise, the selector is connected directly to the import selector.

C record

A C-record is used for transferring the working processes. A C record always refers to the previously defined S-record, i.e. the working processes are connected to the previously transferred work plan selector.

Info

A transfer file for a C record must always contain an S record, since all the working processes are connected to the work plan.

T record

A T record is used for transferring lines of a table. The table refers to the previously transferred S record or C record. In ORTIMplan, 2-D tables are connected to work plans or working processes.

Record properties

Table: Name

Table designation.

Table: Code

Table code.

Table: Row

Row name.

Table: Column

Column name.

M record

An M record is used for transferring material data. A material record does not refer to any other data record. Material records are used in ORTIMplan for generating or updating material resources.

F record

An F record is used for transferring resource data. A fresource record does not refer to any other data record. Resource records are used in ORTIMplan for generating or updating free resources.



Resource: Name

Name of the resource.

Resource: Code

Code of the resource.

Resource: Status

Status.

Resource: Userfield

Userfield name.

B record

Customer data is transferred in the B record. Customers are managed in the customer administration of the calculation module.

The B-record is a separate sentence that does not affect any previous sentence. The last imported customer record or customer is saved in the import interface. A B-record can be supplemented by price records (P-record).

Record properties

Customer: Code

Unique, alphanumeric code.

Customer: Name

Any length one-line designation of the customer.

Customer: Description

Any length description.

P record

Prices are handed over in the P set. Prices are stored in the customer data in the customer administration of the calculation module.

Prices or P record can be added after customer records (B-record) or act as independent record.

Record properties

Customer: Code

See above.

Customer: Name

See above.

CustomerDescription

See above.

Price: Product

Product identifikation.

Price: Price

Price in transferred currency.

Price: Currency

Currency.

Price: Year

Year in which the price was set.

Price: from

Date from which the price is valid.

Price: to

Date until which the price is valid.

D-record

A D-record is used for transferring descriptions. A D-record refers to previously defined S, C, T or M-records. Within ORTIMplan, the descriptions are stored in the description fields of the respective objects. Multiple consecutive D-records are linked together.

U-record

A U-record is used for transferring user fields. A U-record can be composed of the name, value and description of a user field. A U-record refers to previously defined S or C-records.

If a user field does not yet exist, the field will be created. The field description is only relevant for this purpose.

The use of U-records instead of user field meanings in the work plan and working process definitions offers greater versatility. All the fields do not always have to be transferred, but only those necessary in the particular context. The number of U-records can be different for each work plan or each working process. When using the user field meanings in the working processes and working process definitions, a fixed number  of fields is defined. The fields must be transferred in each data record.

Record properties

User field: Name

Name of field.

User field: Wert

Field value.

User field: Beschreibung

Any length description.

R-record

An R-record can be used for removing work plans and working processes.

An R-record defines the identification attributes necessary for finding the work plan or the working process. Standard attributes are the name and code. You can also define user fields as an attribute.

Info

When using the R-record for removal purposes, always be sure to use the correct identification. The ERP interface removes - without asking for confirmation - all the work plans and working processes that match the transferred attributes.

Record properties

Delete: Name

Name of the object to be deleted.

Delete: Code

Code of the object to be deleted

Delete: User field

User field name of the object to be deleted.