Field help (ITM2STA)

The product status determines how its availability has evolved. The different statuses are: Active, In development, On shortage, Not renewed, Obsolete and Not usable.

During product creation, the default status is dependent on the creation method defined for the assigned product category:

• If the product category Creation method is set to Direct, the product status will be Active.
• If the product category Creation method is set to With validation, the product status submitted by default will be In development.

Impact of the product status in the sales and purchase modules

Sales

• An Active, product can be entered and selected in all sales documents.
• An In development, On shortage, Not renewed or Obsolete product can be entered (a warning message is displayed) in all sales documents but it will not be submitted for selection.
• A Not usable product cannot be entered (blocking message) or submitted for selection.

Purchases

• An Active product can be entered and selected in all purchase documents.
• An In development, On shortage, Not renewed or Obsolete product can be entered (a non-blocking warning message is displayed) in all purchase documents but it will not be submitted for selection.
  Upon receipt of the product, an order or a delivery can be selected.
  A product with an In development status can be entered on a request for quote.
• A Not usable product can be entered in the following documents (a warning message is displayed) but will not be submitted for selection:
• Purchase orders
• Contracts
• Buyer plan
• Planning workbench - generation of orders or delivery requests only.
• Enterprise planning - generation of orders or delivery requests only.
• Grouping workbench - the orders for products with this status have the suffix "-".
• Purchase invoices.

Upon receipt of the product, an order or a delivery can be selected.

Use the status to change product availability. The titles in the local menu can be set up and managed as follows:

• Active. The product is available in all the processes.
• In development
• On shortage. The product does not appear in search results, but it can be used by directly entering its code. A non-blocking warning message appears. If the product category creation method is With validation, the status cannot be accessed and its value is forced to the In development value.
• Not renewed
• Obsolete
• Not usable. The product does not appear in search results and cannot be used in scripts. It can however be used in purchase invoices, by directly entering its code. In that case, a non-blocking warning message is displayed.

Non blocking and blocking messages according to the context and status:

• Context - Input
• Non-blocking message: In development, On shortage, Not renewed, Obsolete.
• Blocking message: Not usable.


• Issues - BOMs
• Non-blocking message: Not renewed, Obsolete, Not usable.


• Work order (component)
• Non-blocking message: In development, On shortage.
• Blocking message: Not renewed, Obsolete, Not usable (product not returned).


• Work order (parent product)
• Non-blocking message: On shortage.
• Blocking message: In development, Not renewed, Obsolete, Not usable.


• Sales order
• Non-blocking message: In development, On shortage, Not renewed, Obsolete.
• Blocking message: Not usable.


• Purchase order
• Non-blocking message: On hold.
• Blocking message: In development, Not renewed, Obsolete, Not usable.


• Assembly - On shortage
• Compound assembled:
• Non-blocking: In development, Not renewed, Obsolete.
• Component:
• Non-blocking: In development, Not renewed, Obsolete.


• Disassembly - On shortage
• Compound assembled:
• No message: In development, Not renewed, Obsolete.