130 - Create/Update/Delete order and operation

From Host

This ProMark transaction type receives order and operation information from host (ERP system) to ProMark

FieldDescriptionData TypeMandatoryComment
1Order idText(25)X

2Order numberText(25)

3Order descriptionText(80)

4Item idText(25)

5Item descriptionText(80)

6Project idText(25)

7Lot idText(25)

8Order start dateDate

9Order start timeTime

10Order end dateDate

11Order end timeTime

12Order planned numbersDecimal number

13Operation idText(25)X

14Operation bar codeText(25)(X)

If not supplied then Operation id is used.

15Operation sequence numberText(25)(X)

If not supplied then Operation id is used.

16Operation descriptionText(80)

17Registration profile idText

18Work centre idTextX

19Operation start dateDate

20Operation start timeTime

21Operation end dateDate

22Operation end timeTime

23DepartmentText

24Bonus groupText

25Job pay codeText

26Standard setup timeTime duration

27Standard run timeTime duration

28Standard run time unitDecimal number

29Operation number plannedDecimal number

30Max. manningInteger

0 = no limit

31Standard manningInteger

0 = no standard manning

32Relative time factorTime duration

33Operation start priorityInteger

0 = Highest

34Required qualificationsText

A list of qualications

35Generic infoText(250)

36BlockedLogical

37Resource IdText

38Info referenceText(1000)

39Job TypeText

This field id used to set a specific job type. The Job types are 0 for express orders, 1 (default) is normal orders, that is typical production orders (PO) and 2 is indirect production orders (IPO).

40Order typeText

This field is used to set the job type (header to order) when communicating with SAP using IDocs.

41DeleteLogical

Sets a delete ''flag'' that authorities ProMark to delete the order/operation.
The value 1 in this field means that the order/operation is to be deleted.

42Alternative work centersText

List of work centers that can be chosen from a ''change work center'' dialog. Elements in the list must be separated by blanks.

43Plant IDText(25)

The Plant ID can be used to assign a registration profile to the operation.

44Reference to basis operationText

Internal field used in the integration to the Aspect/4 system

45Operation condition codeText

Pseudo condition ID

46Planned setup start dateDate

If field 26 "Standard setup time'' is not filled out, these fields are used to calculate the standard setup time.

47Planned setup start timeTime

If field 26 "Standard setup time'' is not filled out, these fields are used to calculate the standard setup time.

48Planned setup end dateDate

If field 26 "Standard setup time'' is not filled out, these fields are used to calculate the standard setup time.

49Planned setup end timeTime

If field 26 "Standard setup time'' is not filled out, these fields are used to calculate the standard setup time.

50Planned run start dateDate

If field 27 "Standard run time'' is not filled out, these fields are used to calculate the standard run time.

51Planned run start timeTime

If field 27 "Standard run time'' is not filled out, these fields are used to calculate the standard run time.

52Planned run end dateDate

If field 27 "Standard run time'' is not filled out, these fields are used to calculate the standard run time.

53Planned run end timeTime

If field 27 "Standard run time'' is not filled out, these fields are used to calculate the standard run time.

54Operation initial stateInteger

0: No changes, use registration profile setup if new operation. 1: Pre-released (if possible)
2: Planned or released.

55Internal Host FieldText

56Order responsibleText

Input a ProMark user id as responsible or if the responsible is not known by ProMark enter an ID followed by a colon and a Name. Then a responsible can still be identified by that ID or selected by the name. Ex: 4711:John Doe

57Operation responsibleText

Input a ProMark user id as responsible or if the responsible is not known by ProMark enter an ID followed by a colon and a Name. Then a responsible can still be identified by that ID or selected by the name. Ex: 4711:John Doe

58Earliest order start dateDate

59Earliest order start timeTime

60Earliest order end dateDate

61Earliest order end timeTime

62Latest order start dateDate

63Latest order start timeTime

64Latest order end dateDate

65Latest order end timeTime

66Earliest operation start dateDate

67Earliest operation start timeTime

68Earliest operation end dateDate

69Earliest operation end timeTime

70Latest operation start dateDate

71Latest operation start timeTime

72Latest operation end dateDate

73Latest operation end timeTime

74Lock run time to lead timeLogical

If this field is given a "true" value, then Operation start date/time and Operation end date/time (fields 19-22) must be filled-in; otherwise the transaction is rejected with an error message. The following other fields are then defaulted as follows:

26: Standard setup time = 0.
27 Standard runtime: The difference between the operation start date/time(19/20) and the operation end date/time (21/22).
28: Standard runtime unit = 1.
29: Planned numbers = 1.
32: Relative time factor: Same as standard run time (27).

75Reference 1Text(40)

Customer reference fields on order.

76Reference 2Text(40)

Customer reference fields on order.

77Reference 3Text(40)

Customer reference fields on order.

78Use operation in ProPlanningLogical

If true the operation is made available to ProPlanning