Migration of Service Kit

The auxiliary program 'Service Kit. Convert to Service' (SAS916) creates service definitions in 'Service. Open' (MOS300) from a selected range of service kits in 'Service Kit. Open' (SOS450). Service kit lines from 'Service Kit. Open Lines' (SOS451) create operation hours and material lines connected to the service definition in 'Product. Connect Materials/Operations' (PDS002). Depending on the service expense category of the service kit line, either material lines or run time hours are created in (PDS002).

Before you start

Before running the auxiliary function (SAS916), you must run the auxiliary program for migrating service expenses 'Service Expense. Convert to MAI' (SAS914). Service kit lines can consist of service expenses and if these have not been migrated before migrating service kits, the service kit line will be dropped.

You must also manually create a service definition in (MOS300) with an operation in (PDS002). The service definition will act as a template when creating service kits in (MOS300). The predefined data from the template service definition will be defaulted to service definition created from the service kit.

Overview

The auxiliary program (SAS916) is split into the sections, Selection and Service Information. The Selection section defines and limits the data that should be migrated from (SOS450). Data specified in the Service Information section writes information to the migrated data in (MOS300) and (PDS002).

In the Selection section, the fields for service kit are mandatory. These fields define the range of service kits that will be migrated from (SAS450). Facility is mandatory and should be the facility that the template service definition is created in.

In the Service Information section, the fields for product structure type and service are mandatory. These fields define the template service definition that is used for creating new records in (MOS300).

Migration of service kit header

When migrating service kits from (SOS450) the service definition records in (MOS300) are created through the standard process meaning that related tables are created in the same way as when manually creating a new service definition. Values are populated based on the predefined values from the service definition template specified in (SAS916) with exception of the values in the below migration table.

The template service definition must have a predefined operation in (PDS002). The operation connected to the template service definition is used for creating a new operation in (PDS002), assigned with the next available operation number.

The following values from (SOS450) and (SAS916) update (MOS300):

(SOS450) & (SAS916)

(MOS300)

Comments

(SAS916/E)

STRT

Product structure type

(MOS300/E )

STRT

Product structure type

 

(SOS408/E)

KTIT

Service kit

(MOS300/E )

SUFI

Service

 

(SOS408/E)

KTDS

Name

(MOS300/E )

TX40

Description

 

(SOS408/E)

RESP

Responsible

(MOS300/E )

RESP

Responsible

 

(SOS408/E)

ACRF

Accounting control object

(MOS300/F)

ACRF

Accounting control object

 

(SOS408/E)

TAXC

Tax code

(MOS300/F)

TAXC & TXCS

Tax code & Tax code sub

 

Migration of service kit lines with service expense category 0 and 2

Service kit lines of service expense category 0 and 2 in (SOS451) create run time on the operation in (PDS002). If a service kit has more than one service kit line with service expense category 0 or 2, then the quantities from all lines are accumulated to the run time hours of the operation in (PDS002).

These values from (SOS451) update (PDS002).

(SOS451)

(PDS002)

Comments

(SOS451/E)

CNQT

Quantity in kit structure

(PDS002/E)

PITI

Run time - operation

Limitation: Assumed that the unit of measure is always hours.

Migration of service kit lines with service expense category 3-6 and 8

Service kit lines with service expense category 3,4,5,6, and 8 create material lines connected to the operation in (PDS002). Before migrating service kit lines that should create material lines, the item number that should create a material line in (PDS002) must exist in (MMS001). If the service kit line item ID does not exist in (MMS001), the record is dropped.

The material lines are created in (PDS002) according to the normal material line creation process with values populated from the item in (MMS001). Each material line is automatically assigned a unique sequence number through the migration program.

These values from (SOS451) update (PDS002).

(SOS451)

(PDS002)

Comments

(SOS451/E)

IDEN

Item ID

(PDS002/E)

MTNO

Component number

 

(SOS451/E)

CNQT

Quantity in kit structure

(PDS002/E)

CNQT

Quantity

 

Functional limitations

All fields not mentioned in the migration table are considered limitations. Additionally:

Related topics