Mount Olive Pickle, a leading producer of pickles, peppers, and relishes in the United States, has chosen Crossroads RMC as their solutions vendor for data collection and manufacturing production reporting. In the first phase of the project, the Crossroads team will implement the Inventory Visibility Data Collection software connected to BPCS. The transactions to be implemented include PO Receipts, Transfers, Component Issues, Cycle Counting, and Production Receipts.  

The  Annual Meeting is COMMON’s largest educational event of the year, with four full days of in-depth IBM i, AIX, and Linux-related education that includes all-day pre-conference workshops, open labs, and a wide variety of regular-length sessions. It is the annual meeting of the COMMON membership and the largest gathering of the Power Systems user community. Come see us in Booth 203.

Crossroads RMC is also proud to announce our membership in COMMON for 2016. We look forward to partnering with COMMON and providing valuable content to their user community and sharing in dialogue with users across the country.

In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

You can change your master schedule by specifying the type of master schedule update to perform. You can run a Net Change or Regenerative Schedule.

You also have the ability to clear the lower level requirements out of the Planned and Firm-Planned Order file.

Understanding: What Was Issued to the Shop Order

The shop order inquiry program provides several function keys. By using the function key for the material, the display will present what components have been issued under the issued quantity column. You are also presented with the required quantity. While viewing the quantities you may see that more was issued than what was required. Possibly there was scrap and more material was required to be issued. Perhaps there was an over issue and the balance of the material is slated to be returned to stock.

A red flag should go up if the Shop Order quantity finished is equal to the required quantity for the end item and all the components have not been issued. You may want to investigate why.

Understanding: The quantities required, finished and remaining at the operation and in total for the Shop Order

The shop order may require 1,000 pieces but only 950 are reported as finished in total for the shop order. The quantity required is what is planned on the SO and it may be a higher number than what is finished, factoring in that there can be scrap. If a 1,000 pieces are required to be produced, and there is always is scrap of 10 pieces, then plan for scheduling a quantity of 1,010.

The quantity finished for the end item is what is reported in the inventory application with a production order receipt transaction. At the operation level, if the quantity is reported at the operation, there will be a value in the PCS Complete field on the operation detail screen showing the pieces completed through that operation.

If you want to get a handle on the difference between the required quantity and the finished quantity, you may want to look into reporting quantities at the operation level as well as examining how scrap is controlled and reported.