> >

Use thisform to set up journals to record actual production consumption. You can assign a name from one the four journal types available. For example, to record the production items reported as finished, you can set up a journal called Report as finished. To record route consumption you might set up a journal called Route card.

Note Note

To prevent more than one person from using a journal at one time, assign unique journal names.

Navigating the form

The following tables provide descriptions for the controls in this form.

Tabs

Tab

Description

Overview tab

View a list of existing journals that contain information about the journal type and the voucher series. To create and set up new journal names, click .

General tab

View details about the selected journal, including voucher information, posting details, and whether the journal is blocked or set to private use by a designated user group.

Fields

Field

Description

Name for the journal.

Description of the journal.

Production journal type.

Group

By setting the width of this extended data type you can control how wide the identifying key to various categorizing tables in the application should be.

Example of Extended Data Types extending SysGroup

System name

Label

Help text

CustGroupId

FreightZoneId

ItemGroupId

PaymCode

RouteOprId

The standard width is set to 10 characters.

  • You can set the width to a lower number if you primarily want to use numbers or short codes for these different identifiers.

  • You can set the width to a higher number if you primarily want to use longer codes for these different identifiers.

IntelliMorph automatically arranges the forms and reports according to the new box length.

Different lengths

If you prefer different lengths of the various identifying keys, this could be done in the Microsoft Dynamics AX Application Object Tree (AOT) like this:

  1. Open the Microsoft Dynamics AX Application Object Tree (AOT) as a developer.

  2. Select the Extended Data Type that needs a different length.

  3. Open the property sheet and set Extendsto blank by removing "SysGroup".

  4. Set StringSizeto the required length.

Unlike other extensions between Extended Data Types, it is possible to break the inheritance from SysGroup to its descendants.

Name for the journal.

Production journal type.

Description of the journal.

Group

By setting the width of this extended data type you can control how wide the identifying key to various categorizing tables in the application should be.

Example of Extended Data Types extending SysGroup

System name

Label

Help text

CustGroupId

FreightZoneId

ItemGroupId

PaymCode

RouteOprId

The standard width is set to 10 characters.

  • You can set the width to a lower number if you primarily want to use numbers or short codes for these different identifiers.

  • You can set the width to a higher number if you primarily want to use longer codes for these different identifiers.

IntelliMorph automatically arranges the forms and reports according to the new box length.

Different lengths

If you prefer different lengths of the various identifying keys, this could be done in the Microsoft Dynamics AX Application Object Tree (AOT) like this:

  • Open the Microsoft Dynamics AX Application Object Tree (AOT) as a developer.

  • Select the Extended Data Type that needs a different length.

  • Open the property sheet and set Extendsto blank by removing "SysGroup".

  • Set StringSizeto the required length.

Unlike other extensions between Extended Data Types, it is possible to break the inheritance from SysGroup to its descendants.

The time when a new voucher number automatically be picked.

The time when a new voucher be allocated.

Specify summation level.

Delete journal lines when posting is completed.

User group that the journal is private to.

Buttons

Button

Description

Create a new production journal name. The wizard helps you set up the journal with the categories that reflect your voucher and posting forms. Journals can be created to show weekly or monthly intervals.