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
20248 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Read more

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

The functionality to block a warehouse for inbound or outbound transactions has been enhanced. A check for blocks is performed not only during receipt and shipment confirmation, but at multiple stages in the process. In addition, you can specify these blocking options for the inbound and outbound processes:

• No

• Yes

• Interactive

For example, if Blocked for Inbound is set to Yes, no inbound actions are allowed in the warehouse. Consequently, users cannot confirm receipts, generate and put away inbound advice or storage lists, and perform inbound inspections. 

If Interactive is set, during a non-automatic warehouse inbound procedure, warnings are displayed which offer the user a choice to either cancel the action or continue. Batch or automatic inbound processes continue, but the corresponding reports and logs make note of the blocking. However, in all scenarios, receipt confirmation is not allowed.

The same rules are applicable for the warehouse outbound procedure steps. The restriction for receipt confirmation also applies to shipment confirmation.

For warehouse transfer orders, not only the ship-from warehouse is checked for outbound process blocks, but also the ship-to warehouse. This prevents situations in which goods get stuck in transit due to inbound procedure blocks that apply to the destination warehouse. Now, the transfer process is already blocked during outbound.

Read more
First6061626365676869Last

Theme picker

Categories