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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Day: LX Inventory Pallet Status Flow

Four fields in the Item/Warehouse record (IIW file) affect the disposition of the

pallet status.

 

1.  Goods Receiving Code: You define these codes in Goods Receiving Maintenance (WHM130). The codes control whether or not the stock passes through inspection, what percentage, or quantity of a delivery to inspect, and the number of quarantine days, if any.

 

2.  Inspection Zone/Inspection Location: Either the Inspection Zone or the Inspection Location must be entered on the Item/Warehouse Master Maintenance screen WHM150D2-01.

 

3.  Default Inventory Status: If the status is 0 (Received) or 1 (Inspection), the item moves from the receiving location to the inspection location in inspection status. If the pallet status is not 0 or 1 (that is, 4 (Available) or 9 (Rejected)), the pallet moves to the inspection location with the default status, but the pallet will not proceed from the Inspection location to the Putaway location. You must manually move the stock.

 

4.  Pallet Status Codes: 0 (Received), 1 (Inspection), 4 (Available), and 9 (Rejected) are the only pallet status codes reserved by the system to update and advance inventory/pallet status. To do this Warehouse Management uses the following rules:

 

·    Rejected inventory goes from receiving to a Reject (type 9) Location with a Location Type A (Rejected) in the Location Extension file (ILE) record. All inventory received into a reject location is set to a pallet/inventory status of Reject (9).

·    Inventory received by Goods Receiving (WHM510) into a Receiving Location takes on the Default Inventory Status that is in the Item Warehouse file (IIW) record.

·    If the Default Inventory Status is 0 (Received), the system places the pallet status at 0 (Received) in the Receiving Location, I (Inspection) in the Inspection Location, and 4 (Available) if moved from Inspection to any palletized location other than rejection. If moved to rejection the Default Inventory Status changes to 9 (Rejected).

Previous Article Baan/LN Tip of the Week: Inventory Valuation
Next Article Baan/LN Tip of the Day: Transfers - LN
Print
47516 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

How can I use an alternate item on a shop order?

The best way is to have the approved alternate item appear on the Bill of Material just after the standard item with a zero required quantity. Now the alternate item will appear on the Shop Order. So, if the standard item is not available, the alternate item can be issued to the shop order.

When the shop order is closed out, one item will have an unfavorable variance while the other shows a favorable variance. This is an easy way to provide alternate items provided engineering approves and they are part of the Bill of Material.

FirstLast

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.

  • 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.

Categories