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 McKinsey Quarterly - Next Frontiers for Lean
Next Article Barcodes and the Small Business Manufacturer
Print
39060 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Here are 5 ways you can motivate your employees to give their best every day:

1. Train Your Employees

2. Give Your Employees the Right Tools

3. Automate Processes

4. Give Your Employees Real-Time Feedback

5. Provide Incentives to Do More

Optimize Your Manufacturing Today!

Previously, Material Requirements Planning (MRP) preferred practices meant that the component’s due date was the same as the parent’s shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The user is now able change how the due date is determined for multi-level shop orders. If the Due Date of Children parameter is set to 1=Yes, the due date of the child components is the same as the release date of the parent. If the parameter is set to 0=No, the due date is the day before the release date of the parent.

Optimize Your Manufacturing Today!

First7576777880828384Last

Theme picker

Tips: LN | Baan

Table Timestamp Definitions (ttadv4136m000)

Use this session to define timestamps for Infor LN tables. A timestamp is an additional column that stores the date and time of the last change for each record.

Timestamps are utilized by features like the extraction logic of CPM Enterprise Analytics. They enable CPM to perform incremental data extractions. For example, CPM can use the timestamps to extract records that were changed during the last week in a weekly extraction process.

To Create Timestamps...

Operations: To absorb the cost of cost items into specific projects, you'll need to handle them as customized items. However, cost items cannot directly be defined as customized items. Customized items must be physical, either manufactured or purchased.

That said, it's still possible to absorb cost items into a project, although indirectly. Here's how:

  1. Set Up Ledger Account: First, create a new ledger account in session tfgld0508m000 and set the type to "PCS" (project) in the operations management integrations. This account will be used for matching and approving purchase orders for cost items.

  2. Create and Activate Projects: Ensure that the necessary projects are created and set to active status.

  3. Purchasing Cost Items...

12345678910Last

Theme picker

Categories