140 - Job transaction

To Host

The 144 transaction type has been developed because some host systems cannot differentiate between ''ordinary'' job transactions (those generated at the registration terminal), and ''changed'' job transactions that have been modified in the Change transactions screen in ProMark. If it is necessary to differentiate between ordinary job transactions made via the terminal and job transactions that have been changed via Change transactions in ProMark, then it is important that you check the box Send as 144 job trans in the System set-up screen (System>System set-up).

The ordinary job transactions will be transferred as 140 transactions, whilst those that have been modified in the Change transactions screen will be transferred as 144 transactions. This will ensure that the data is sent to the host system in the correct format.

FieldDescriptionData TypeMandatoryComment
1Employee numberText

2DepartmentText

From the operation

3Job transaction typeInteger

In addition to the fields that are always filled out, the following fields will also be filled out depending on the type of job transaction sent.

3: Resource time on operation
Field 3 (with the value 3), field 24, field 25 and field 26.
This value is used if Job time corr. Type = 8, on the System>System set-up screen.

4: Select Resource on operation
Field 3 (with the value 4)

5: Report Amount
Field 3 (with the value 5), Field 8, field 18, field 19, field 20, field 21 and field 22.

6: Error Reasons
Field 3 (with the value 6), field 8, field 19 and field 23.

7: Change Condition
Field 3 (with the value 7), field 20, field 21, field 25, field 26 and field 29.

8: Time Used
Field 3 (with the value 8), field 24, field 25 and field 26.

9: Job-in
Field 3 (with the value 9).

10: Job-out
Field 3 (with the value 10).

11: Job Finished
Field 3 (with the value 11).

8/13/16: Job time correction
Field 3 (with the value 8/13/16), field 13, field 14, field 15, field 24, field 25 and field 26. This transaction is only sent when a job has been corrected.
On the screen System>System set-up you can select Job time corr. Type to be 8, 13 or 16.

17: Number correction
Field 3 (with the value 17), field 8, field 18, field 19, field 20, field 21, field 22 and field 23. This transaction is only sent when a job has been corrected.

18: Resource start on operation
Field 3 (with the value 18)

19: Resource stop on operation
Field 3 (with the value 19)

20: Idle time job
Field 3 (with the value 20), field 24, field 25, field 26, field 31 and field 32.

21: Material consumption on operation
Field 3 (with the value 21) , field 23, field 29, field 32 and field 33.

22: Return materials from operation
Field 3 (with the value 22) , field 29, field 32 and field 33.

23: Resource time correction
Field 3 (with the value 23) , field 24, field 25 and field 26.
This value is used if Job time corr. Type = 13 or 16, on the System>System set-up screen.

24: Operation Reporting
The reported data is in field 38

31: Condition change on planned resource
Field 3 (with value 31), field 25, field 29, field 31 and field 68.

32: Planned resource finished
Field 3 (with value 33), field 25, field 29, field 31 and field 68

35: Planned material finished
Field 3 (with value 35), field 20 and field 69

36: Time on planned resource
Field 3 (with value 36), field 24, field 62 and field 68.

50: Weight
Field 3 (with value 50) and field 55.

51: Weight correction
Field 3 (with value 51) and field 55.

4Order idText

5Project idText

6Lot idText

7Order numberText

8Article idText

9Operation idText

10Operation sequence numberText

11Operation bar codeText

12Workcentre idText

13Terminal numberText

14Corr. reg. dateDate

15Corr. reg. timeTime

16Job pay codeText

17Operation conditionText

Shows the operation condition. See field 62.

18Added number approvedDecimal number

19Added number scrappedDecimal number

20Total number approvedDecimal number

21Total number scrappedDecimal number

22Number previously scrappedDecimal number

23Scrapped reasonText

24Added operation timeTime duration

25Total operation timeTime duration

26Operation time accountText

27Pay numbersDecimal number

Not used

28Bonus groupText

Not used

29Condition change reasonText

30Transaction deletedLogical

31Resource idText

32Material idText

33Amount of materialDecimal number

34Employee's Home DepartmentText

35Employee's Current DepartmentText

36Employee's Home GroupText

37Employee's Current GroupText

38Report dataText

39Standard set-up timeTime duration

40Standard runtimeTime duration

41Time factorTime duration

42Runtime unitDecimal number

43Planned numberDecimal number

44Order typeText

45Time-1Time duration

See Note 1

46Time-2Time duration

See Note 1

47Time-3Time duration

See Note 1

48Time-4Time duration

See Note 1

49Time-5Time duration

See Note 1

50Time-6Time duration

See Note 1

51Time-7Time duration

See Note 1

52Time-8Time duration

See Note 1

53Time-9Time duration

See Note 1

54Time-10Time duration

See Note 1

55WeightDecimal number

Weight collected from an external unit or entered directly on screen

56Info-1Text

Info field from the employee master

57Info-2Text

Info field from the employee master

58Info-3Text

Info field from the employee master

59Info-4Text

Info field from the employee master

60Info-5Text

Info field from the employee master

61Original Transaction IdentifierText

A unique identifier if the transaction is deleted. To get the optimal use of the field select ''Send all add/del job trans. to host'' in the System Set-up

62Latest operation conditionText

Corresponds to field 17 , except when making corrections. Then this field shows the latest (final) operation condition where field 17 shows the operation condition for the correction.

63From registration dateDate

In connection with job-out and operation time (related to a condition change) transactions, this and the next field will contain the (corrected) registration date/time of the previous job-in or operation time transaction. In other cases, the content will be the same as in the fields 14 and 15. In host transactions representing changed or deleted registrations, the content is currently not useable.

64From registration timeTime

See field 63

65Item typeInteger

66Reason from latest change conditionText

67Batch IDText

68ID of attached ResourceText

69ID af planned ItemText

70Reference to basis operationText

71Plant IDText

72Internal Host FieldText

73Order ID of joining operationText

74Operation ID of joining operationText

75Profile dateDate

Payroll date. Only in connection with job-in, job-out, job time and amount.

76Actual transaction dateDate

The actual date and time when the registration were made

77Actual transaction timeTime

The actual date and time when the registration were made

78Order responsibleText

79Operation responsibleText

80Operation info referenceText

Always the latest content in the operation's ''Info reference'' field. Explicit line breaks are represented by | characters.

81Time overrun reason typeText

If an employee during a job-out or ''direct employee time on operation'' terminal dialog is prompted to select a reason for the operation's standard set-up or production time being exceeded, then the reason's group ID will be reported in this field.

82Time overrun reason IDText

The job reason ID related to the reason group ID in field #81 is reported here.

Notes

IdText
1This is a differentiated reporting back to the ERP system. It is set up in ProMark in the panel "Job Time Distribution" under the registration profile. It is used to distribute the job time on different accounts according to the "value" of the job time. For example, the job time has a different price when a non-educated or new person is performing the job, than if the senior worker is performing the job. (For more information, please refer to the Danish document SAP_PP_IPO_kravspecifikation_DK_ver4.doc).