Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Project Status Options

Ever wonder what the implications are of choosing one project status versus another?

Here is the explanation of project status possible values:

Free
You can carry out project engineering. This means that you can:

  • Define the project master schedule (PMS) by using the Project Control module.
  • Maintain the project structure.
  • Maintain the customized product structure by using customized bills of material and routing sheets.
  • Carry out project estimating.

Simulated
You simulate the rough capacity requirements planning and the detailed material and resource requirements planning (RRP) based on the network planning. The capacity requirements for a simulated project are visualized separately. Infor LN (ERP LN) generates planned RRP purchase orders, planned production orders, and PRP warehouse orders for customized items. However, those orders cannot be released. Moreover, the RRP does not allocate standard items to the project.

Active
This status indicates the project's execution stage. You can release planned orders so that the required purchase and production activities can be actually started and completed.

Canceled
The project has been canceled. You cannot release new orders for the project, but you can, however, finish pending logistical activities. You can close a canceled project, but a project can also remain canceled. If the project remains canceled, be aware that the final costs are not posted to Financials, and that WIP can still exist for completed orders. Costs are only posted if you close the project.

Finished
As far as manufacturing is concerned, the project is finished. Also, all purchase and production activities have been completed or closed, and all sales orders have been delivered for the project.

Closed
Financially, the project has been closed. This means that the financial project results have been computed. Financial project transactions can no longer be posted to the project.

To be Closed
If you select the COGS and Revenues restricted to Financial Company of PCS Project check box in the Project Control Parameters (tipcs0100m000) session, financial transactions are posted on the financial companies of the sales office, service department, and/or warehouse instead of on the financial company of the PCS project. If internal invoices are sent from the PCS project to those departments, and the internal invoices are not completed yet, the Close Project (tipcs2250m000) session sets the project status to To be Closed instead of to Closed. You must first complete the internal invoices, and then run the Close Project (tipcs2250m000) session again to set the project status to Closed.

Archived
The project has been archived. This means that all project data has been stored in archive files and is removed from the original files.

Previous Article Infor LX & BPCS Tip: How Items Are Selected for a Cycle Count
Next Article Collaborate IN-PERSON With Infor LN Users
Print
41072 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

  • When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

Read more

This enhancement improved the subfile utilized in MRP320D Master Schedule Detail Inquiry -SCR001 by expanding the subfile with data rather than clearing the subfile as user pages. This change provides full support for the WebTop 4.8 Grid decorator.

This enhancement updated the approach used to populate the subfile to allow a deployed Webtop Grid to function correctly. There is no visible or user-impacted change to the way the program functions.

This enhancement provides improved functionality and full support of a Webtop grid applied to the subfile.

Read more
Last

Tips: LN | Baan

Users can personalize sessions and apply special formatting to the data displayed in sessions. The personalizations and formatting settings that are specified by the users are stored on the LN server. Administrators can maintain these settings.

  • Session personalizations

    Users can personalize sessions in various ways. users can, for example, hide fields, change labels, customize the toolbar, and move fields to another tab. Administrators can maintain the personalizations defined by the users. For example, an administrator can export personalizations to an XML file, import personalizations from an XML file, and copy personalizations to another user, to a DEM role, or to a company number.

  • Report personalizations

    You can use the Report Designer (ttstppersrep) to personalize the layouts and style of reports, without modifying the standard reports or using an external reporting solution. The changes are stored as personalizations.

    You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer (ttstppersrep), or modify them in Infor LN Studio.

    For details, see the Infor LN Report Designer Development Guide
     

  • Conditional formatting

    users can define conditions to apply special formatting to the data displayed in LN sessions. The users can define multiple conditions per session and different types of formatting, such as a specific color for particular fields or rows, and a warning symbol for particular rows. Administrators can maintain the formatting settings specified by the users and can define system-wide formatting settings.

Read more
  • If Finances is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.

You cannot delete a purchase order (line) if:

  • The linked warehouse order is closed but cannot be removed.
  • The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
  • A consignment replenishment order is not yet consumed completely.
  • The invoice is yet to be completely matched and approved.
  • The invoice amount is not yet inserted as turnover history.
  • The sales order or service order that is linked to the purchase order line, and for which an internal invoice must be sent from the purchase office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.
Read more

Categories