Appendix 5: Tracking Project management in Finance from Manufacturing

An Entry transaction is used for customizing specific functions to the needs of an organization and their processes.

Setting up your system

Manufacturing has been updated for Project management costs to be tracked in Finance.

This appendix details how to set your system up if this functionality is not enabled on your system.

A work order is single project, and for projects only behaves correctly for a single released product line.
Sage recommends that work orders for a project are generated automatically from MRP suggestions.
This minimizes the risk of manual errors as all product/project links are created automatically.
Sage recommends a work order for a project should only cover demand for a single project. If a work order is generated automatically from MRP suggestions, the single work order will cover demand for a single project. Automatic work orders will never cover demand for multiple projects.
If a work order is raised manually for multiple released products, it can be difficult to trace inconsistencies in the postings if they occur if each product on a work order is assigned to a different project.

Default dimensions

Open: Setup > Financials > Accounting interface > Default dimensions

Appropriate identifiers have been added to default dimensions for manufacturing to support initialization of analytical dimensions for projects on manufacturing documents. You must use the Default dimensions function (GESCDE) to update your default dimensions. The identifiers include search allocation rules and calculation formulas.

Identifiers section

Update your default dimensions with the following expressions:

Code

Table

Identifier

MFI

Project

func PIMPL_CSTD_PROGS.PJM_KEY_SPLIT_OPPNUM(GACTX,[M:MFG1]PJT(nolign-1))

MFIAUT

Project

func PIMPL_CSTD_PROGS.PJM_KEY_SPLIT_OPPNUM(GACTX,[F:MFI]PJT)

MFM

Document

evalue("[M:MFG1]CCE"+num$(find(AXE,GDIE)))

MFMAUT

Document

func TRTX3CPT.TRFSEC (“MFI”,AXE)

MFO

Document

evalue("[M:MFG1]CCE"+num$(find(AXE,GDIE)))

MFOAUT

Document

func TRTX3CPT.TRFSEC (“MFI”,AXE)

MKI

Document

func TRTX3CPT.TRFSEC (“MFI”,AXE)

MKIAUT

Document

func TRTX3CPT.TRFSEC (“MFI”,AXE)

MKIB

Document

func TRTX3CPT.TRFSEC (“MFI”,AXE)

MKM

Document

func TRTX3CPT.TRFSEC (“MFM”,AXE)

MKMAUT

Document

func TRTX3CPT.TRFSEC (“MFM”,AXE)

MKMB

Document

func TRTX3CPT.TRFSEC (“MFM”,AXE)

MKO

Document

func TRTX3CPT.TRFSEC (“MFO”,AXE)

MKOAUT

Document

func TRTX3CPT.TRFSEC (“MFO”,AXE)

MKOB

Document

func TRTX3CPT.TRFSEC (“MFO”,AXE)

MKOLAB

Document

func TRTX3CPT.TRFSEC (“MFO”,AXE)

MKOLABAUT

Document

func TRTX3CPT.TRFSEC (“MFO”,AXE)

MKOLABB

Document

func TRTX3CPT.TRFSEC (“MFO”,AXE)

MWIOVEMAT

Document

func TRTX3CPT.TRFSEC (“MFI”,AXE)

 

Source document

func TRTX3CPT.TRFSEC (“MKM”,AXE)

MWIOVESCO

Document

func TRTX3CPT.TRFSEC (“MFI”,AXE)

 

Source document

func TRTX3CPT.TRFSEC (“MKO”,AXE)

MWIOVEWST

Document

func TRTX3CPT.TRFSEC (“MFI”,AXE)

 

Source document

func TRTX3CPT.TRFSEC (“MKO”,AXE)

MWISCI

Document

func TRTX3CPT.TRFSEC (“SCI”,AXE)

MWISCM

Document

func TRTX3CPT.TRFSEC (“SCM”,AXE)

MWISCS

Document

func TRTX3CPT.TRFSEC (“SCS”,AXE)

STKEOF

Document

func TRTX3CPT.TRFSECX ("MTK2,MBI,MTIK,MKI","M,M,M,F",AXE)

STKSOF

Document

func TRTX3CPT.TRFSECX ("MTK3,MBM","M,M",AXE)

General section > Dimensions block

Update your default dimensions for the Project dimension type with a search identifier and the priority order for the released product line. You can select from the entities with Identifier expressions defined (see Identifiers section table above).

Code

Dim. type

Dimension: Project

Identifier

MWIOVEMAT

PRJ

Source document

func TRTX3CPT.TRFSEC (“MKM”,AXE)

 

 

Document

func TRTX3CPT.TRFSEC (“MFI”,AXE)

General parameters

Open: Setup > General parameters > Parameter values

Define the following parameter at the site level (TC chapter, PJM group):

WOPJMMSG

Must all released product lines on a work order be for the same project?

  • Yes
  • No
Sage recommends you set this parameter to Yes.

Set to Yes, if a work order has multiple released products, all product lines must be for the same project as the first released product line or blank (not assigned to a project).

Set to No, a warning will be displayed when a project code is entered that does not match the project code assigned to the first released product line but the addition of the product/project to the work order will not be prevented.

Sage recommends that a work order for a project should be single product only. That is, one work order, for one product, for one project.

Context (Manufacturing integration): Used in the Work order function (GESMFG).

Entry transactions

Open: Setup > Manufacturing > Entry transactions > Work orders

Open: Setup > Manufacturing > Entry transactions > Production plan

Open: Setup > Manufacturing > Entry transactions > Material tracking plan

Open: Setup > Manufacturing > Entry transactions > Time tracking plan

Open: Setup > Manufacturing > Entry transactions > Reintegration plan

Open: Setup > Manufacturing > Entry transactions > Production tracking

  1. The Manufacturing Entry transactions have been updated to include the project analytical dimension type.

    2. Add the project analytical dimension type (for example, PRJ) to the manufacturing entry transactions functions, as follows:

    1. Work orders (GESMFL) (Setup > Manufacturing > Entry transactions > Work orders). Analytical section: Add the project analytical dimension type to the Released product, Operations and Material entry tables.

      2. Work orders Entry transaction (GESMFL): Analytical section, Released product/Operations tables (Material table not shown)

    2. Production plan (GESMIL) (Setup > Manufacturing > Entry transactions > Production plan). Analytical section: Add the project analytical dimension type to the Dimension line entry table.
    3. Material tracking plan (GESMML) (Setup > Manufacturing > Entry transactions > Material tracking plan). Analytical section: Add the project analytical dimension type to the Dimension line entry table.
    4. Time tracking plan (GESMOL) (Setup > Manufacturing > Entry transactions > Time tracking plan). Analytical section: Add the project analytical dimension type to the Dimension line entry table.
    5. Reintegration plan (GESMRE) (Setup > Manufacturing > Entry transactions > Reintegration plan). Analytical section: Add the project analytical dimension type to the Dimension line entry table.
    6. Production tracking (GESMTL) (Setup > Manufacturing > Entry transactions > Production tracking). Analytical section: Add the project analytical dimension type to the Time tracking, Production reporting and Material tracking entry tables (Analytical section).
  2. Create your own single-product managed entry transactions to restrict a work order to a single product line, and therefore a single project code. This is optional.

    3. If you decide to adopt this concept, create one entry transaction for work orders and one for production tracking. You could use the code "PJM", for example.

    1. For the Work orders Entry transaction (GESMFL), leave the Multiple products allowed check box (ITMMULT) clear.
    2. For the Production tracking Entry transaction (GESMTL), set each project analytical dimension type Method field (CCECODn) to Displayed.
    Creation and subsequent use of a single-product managed entry transaction (Work orders/Production tracking) is optional.

    If used in the Work order function (GESMFG) with a manual work order or manual change to a work order, the single-product managed entry transaction will only allow a single released product line to be added to the work order.
    The project analytical dimension fields on the released product, material and operation lines will be displayed but the fields will be greyed out, thereby preventing amendment.

    If used in the Production tracking function (GESMTK) with a work order associated with the single-product managed work order entry transaction, the project analytical dimension fields on the released product, material and operation lines will be displayed but the fields will be greyed out, thereby preventing amendment.

Import/export templates

Open: Setup > Usage > Imports / exports > Import/export templates

The Manufacturing Import/export templates have been updated to include the project and the dimension fields. You must use the Import/export templates function (GESAOE) to update them.

  1. Update your import/export templates with the following Identifiers:

    2. Templ.

    Lvl

    Ind.

    Table

    Key

    Link

    MKI

    2

    LC

    CPTANALIN

    CAL0

    "MKI";0;MFGTRKNUM;ITMTRKLIN;0;""

    MKINOM

    2

    AD

    CPTANALIN

    CAL0

    "MKI";0;MFGTRKNUM;ITMTRKLIN;0;""

    MKM

    2

    AD

    CPTANALIN

    CAL0

    "MKM";0;MFGTRKNUM;MATTRKLIN;0;""

    MKMS

    2

    AD

    CPTANALIN

    CAL0

    "MKM";0;MFGTRKNUM;MATTRKLIN;0;""

    MKO

    1

    LC

    CPTANALIN

    CAL0

    "MKO";0;MFGTRKNUM;OPETRKLIN;0;CPLWST

    Import/export templates (GESAOE): Identifiers section, Template MKI - Import production tracking

  2. Update your import/export templates with the following Fields.

    3. Refer to the legal ledger (Setup > Organizational structure > Ledgers (GESLED)) for your company.
    If the "Project" is on a specific Dimension type n field (DIE), add the DIE(n) and CCE(n) fields as required. For example, to export the PCC dimension type add DIM(4) and CCE(4) if the PRJ dimension type is on the Dimension type 4 field.

      Import/export templates (GESAOE): Fields section, Template MKI - Import production tracking

    1. Add the PJT field (MFGITMTRK table) to the end of the MFGITMTRK fields:

      2. Templ.

      Ind.

      Table

      Field

      Description

      MKI

      MKINOM

      M

      MFGITMTRK

      PJT

      Project

      MKM

      MKMS

      M

      MFGMATTRK

      PJT

      Project

      MKO

      M

      MFGOPETRK

      PJT

      Project
    2. Add the DIE(n) and CCE(n) fields for the CPTANALIN table to the end of the table:

      3. Templ.

      Ind.

      Table

      Field

      Description

      MKI

      MKO

      LC

      CPTANALIN

      DIE(n)

      Dimension type code

      MKI

      MKO

      LC

      CPTANALIN

      CCE(n)

      Analytical dimension

      MKINOM

      MKM

      MKS

      AD

      CPTANALIN

      DIE(n)

      Dimension type code

      MKINOM

      MKM

      MKS

      AD

      CPTANALIN

      CCE(n)

      Analytical dimension

Understanding the process: Work orders

Sage recommends that work orders for a project are generated automatically from MRP suggestions. Work orders for projects behave correctly for a single released product line.
Automatically generated work orders for projects minimizes the risk of manual errors. The work orders are for a single released product line; the product/project links are created automatically.

Create a new work order

  1. Add a released product line.
  2. Project (PJT field code): Add a project code.
    1. Released product line. The Project analytical dimension field (CCEn) is automatically initialized with the default dimension for the project (maintained in Projects > Projects > Project management (GESPJM)).
    2. All components. The Project analytical dimension field (CCEn) is automatically initialized with the default dimension for the project.
    3. All operations. The Project analytical dimension field (CCEn) is automatically initialized with the default dimension for the project.

Change the project code

  1. Project (PJT field code): Change the project code.
    1. Released product line. The Project analytical dimension field (CCEn) is automatically reinitialized with the default dimension for the new project code (maintained in Projects > Projects > Project management (GESPJM)).
  2. A message "Change all lines on the components and operations to the project dimension code?" is displayed.
    1. Select Yes:
      1. All components. The Project analytical dimension field (CCEn) is automatically reinitialized with the default dimension for the new project code.
      2. All operations. The Project analytical dimension field (CCEn) is automatically reinitialized with the default dimension for the new project code.
    2. Select No:
      1. All components. The Project analytical dimension field retains the default dimension for the original project code.
      2. All operations. The Project analytical dimension field retains the default dimension for the original project code.
    3. Select Yes if same value:
      1. All components. The Project analytical dimension field is automatically reinitialized with the default dimension for the new project code if the Project analytical dimension field contains the analytical dimension for the original project code (the Project analytical dimension field on each component, if changed manually, could potentially be different from the original project analytical dimension).
      2. All operations. The Project analytical dimension field is automatically reinitialized with the default dimension for the new project code if the Project analytical dimension field contains the analytical dimension for the original project code (the Project analytical dimension field on each operation, if changed manually, could potentially be different from the original project analytical dimension).

Change the project dimension

  1. Project (CCEn field code): Change the project dimension.
Use your single-product managed "PJM" entry transaction to prevent manual changes to the project dimension fields.
  1. A message "Change all lines on the components and operations to the project dimension code?" is displayed.
    1. Select Yes:
      1. All components. The Project analytical dimension field (CCEn) is automatically changed to the new, manually defined project analytical dimension.
      2. All operations. The Project analytical dimension field (CCEn) is automatically changed to the new, manually defined project analytical dimension.
    2. Select No:
      1. All components. The Project analytical dimension field remains unchanged.
      2. All operations. The Project analytical dimension field remains unchanged.
    3. Select Yes if same value:
      1. All components. The Project analytical dimension field is automatically changed to the new, manually defined project analytical dimension if the project analytical dimension field matches the project analytical dimension field for the released product line.
      2. All operations. The Project analytical dimension field is automatically changed to the new, manually defined project analytical dimension if the project analytical dimension field matches the project analytical dimension field for the released product line.

Using the WOPJMMSG parameter

WOPJMMSG parameter = No

Sage recommends that a work order for a project should be single product only. That is, one work order, for one product, for one project.
  1. Add a second and third released product line to a work order.
  2. Project (PJT field code): Add a different project code to each released product line.
    1. Released product line 1, 2, 3. The Project analytical dimension field (CCEn) is automatically initialized with the default dimension for the assigned project (maintained in Projects > Projects > Project management (GESPJM)).
    2. All components. The Project analytical dimension field (CCEn) is automatically initialized with the default dimension for the project code on the first released product line.
    3. All operations. The Project analytical dimension field (CCEn) is automatically initialized with the default dimension for the project code on the first released product line.

WOPJMMSG parameter = Yes

Reminder: Work ordersSage recommends
ONE work order =
ONE product =
ONE project.

  1. Add a second and third released product line to a work order.
  2. Project (PJT field code): The project code on the second released product line and the third released product line must match the project code on the first released product (or be left blank).
    1. Components of second and third BOM. The Project analytical dimension field (CCEn) is automatically initialized with the default dimension for the project on the first released product line.
    2. All operations. The Project analytical dimension field (CCEn) is automatically initialized with the default dimension for the project code on the first released product line.
  3. Project (PJT field code). Change the project code on the first released product line.

    4. Reminder: Work ordersChanging a project code can cause inconsistencies in the postings.

  4. A message "Change all lines on the components and operations to the project dimension code?" is displayed.
    1. Select Yes:
      1. BOM components. The Project analytical dimension field (CCEn) is automatically reinitialized with the default dimension for the new project code.
      2. All operations. The Project analytical dimension field (CCEn) is automatically reinitialized with the default dimension for the new project code.
    2. Select No:
      1. BOM components. The Project analytical dimension field retains the default dimension for the original project code.
      2. All operations. The Project analytical dimension field retains the default dimension for the original project code.
    3. Select Yes if same value:
      1. BOM components. The Project analytical dimension field is automatically reinitialized with the default dimension for the new project code if the Project analytical dimension field contains the analytical dimension for the original project code (the Project analytical dimension field on each component, if changed manually, could potentially be different from the original project analytical dimension).
      2. All operations. The Project analytical dimension field is automatically reinitialized with the default dimension for the new project code if the Project analytical dimension field contains the analytical dimension for the original project code (the Project analytical dimension field on each operation, if changed manually, could potentially be different from the original project analytical dimension).
  5. Project (PJT field code): Change the project code on the second released product line to match the project code on the first released product line.
    1. Components of second BOM. The Project analytical dimension field (CCEn) remains unchanged (it is set to the original project analytical dimension).
    2. All operations. The Project analytical dimension field (CCEn) remains unchanged (it is set to the default dimension for the project code on the first product line).
  6. Project (PJT field code): Change the project code on the third released product line to match the project code on the first released product line.
    1. Components of second BOM. The Project analytical dimension field (CCEn) remains unchanged (it is set to the original project analytical dimension).
    2. All operations. The Project analytical dimension field (CCEn) remains unchanged (it is set to the default dimension for the project code on the first product line).