Please Wait a Moment
X

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

Crossroads Connections

Infor ERP Tips & News from the Experts

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

Kathy Barthelt

Infor LN & Baan Tips & Tricks for OPERATIONS: Blocking or Unblocking Warehouses

You can block a warehouse for inbound procedures, outbound procedures, or both. For example, you can block inbound and outbound procedures for a warehouse if the warehouse must be closed temporarily for inspection.

You can impose these types of blockings:

  • Full block: Full block on warehousing procedures.

  • Interactive block: Override blocking allowed except blocks on confirm shipment or confirm receipt.

If you impose a full block on inbound procedures, the receipt and inbound inspection procedures are not allowed for the warehouse.

If you impose a full block on outbound procedures, the outbound, outbound inspection, and shipment procedures are not allowed for the warehouse.

An interactive block on inbound procedures blocks the confirm receipt step. For the other inbound steps (for goods already received), a warning is displayed and you are prompted to cancel the procedure or to continue.

These are the other inbound steps:

  • Generate and release inbound advice
  • Print and confirm storage lists
  • Put away stock

If you perform the outbound steps of a warehouse transfer and an interactive inbound block is imposed on the receiving warehouse, you are warned that the receiving warehouse is blocked.

An interactive block on outbound procedures blocks the confirm shipment step. For the remaining outbound and shipment steps, a warning is displayed and the user is prompted to cancel the procedure or to continue. Assembly, internal inventory movements and inventory adjustments are also allowed.

Previous Article Infor LN & Baan Tips & Tricks for FINANCE: Interest Invoices
Next Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Archiving Concept
Print
18208 Rate this article:
5.0

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories