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 EXECUTIVES

OPERATIONS: Update, Cancel or Remove Outbound Order Lines
When the originating order or order line of an outbound order line is canceled or changed, this affects the outbound order line and may affect the related outbound advice, shipments, or shipment lines.

For most order origins, warehousing order-type parameters determine whether these actions are allowed:

  • Update the outbound order line if the originating order is changed.
  • Cancel the originating order line and the outbound order line.
  • Delete the canceled outbound order line.

If updating is allowed, changes made to the originating order are updated to the outbound order line and the related outbound advice, and, if present, picking lists, are deleted.

If updating is not allowed, a message is displayed, and the input is blocked when you try to change the originating order line.

If canceling is allowed, the outbound order line is deleted or set to Canceled when the originating order line is canceled.

When a canceled outbound order line is deleted, if present, the related outbound advice and picking list are also deleted. Outbound order lines originating from manual order origins cannot be deleted when canceled.

To process an outbound order line that is not deleted but set to Canceled, the outbound order line must be set to Shipped. The status of the outbound order line determines whether all steps of the outbound and shipment procedures must be completed to process the outbound order line.

When a canceled outbound order line is set to Shipped, the shipped quantity is automatically set to 0. You can create a transfer order to return the not-shipped goods to inventory.

If canceling is not allowed, you cannot cancel the originating order line or the outbound order line. A message to that effect is displayed when you try to cancel the originating order line.

To prevent the goods from being shipped when canceling is not allowed, you must complete the outbound and shipment procedures. When confirming the shipment line, you must set the shipped quantities to 0 and create a transfer order to return the not-shipped goods to inventory.

FINANCE: Currency Differences Accounts
Currency differences can make the financial analysis and reconciliation more complex. These types of currency differences can occur:

  • Currency differences
    Currency result caused by fluctuations in the exchange rate, for example, if the rate differs between the invoice date and the payment date.

  • Exchange gain and loss
    Currency result caused by the use of different exchange rate types, for example, the Sales rate type and the Internal rate type, or if using the rate determiner you have changed the exchange rate for a transaction during the order handling procedure.

  • Translation gain and loss
    Currency result caused by the use of different currencies during the order handling procedure, for example, if the order currency or the payment currency differs from the invoice currency.

  • Destination gain and loss
    Currency result caused by different results when the transaction currency is converted to the various home currencies. Destination gain and loss can only occur in an independent currency system.

To support good reconciliation possibilities, currency differences and exchange gain and loss are posted to these accounts:

  • Exchange Gain and Loss
    For differences between related amounts (debit and credit postings) due to different exchange rate types or different currency rates.

  • Currency Translation
    For transactions in which the debit posting and the credit posting are made in different currencies.

  • Currency Differences contra account
    For currency differences on the invoice accrual account due to rate changes between the receipt date and the approval date of the invoice and calculated when you close a financial period.


TECHNOLOGY: Advantages of Data Replication
Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

Previous Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Advantages of Data Replication
Print
783 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

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.

Understanding: How many hours remain in total and at each operation?

Now let’s look at what information is being supplied from the shop floor.

It’s not uncommon for transaction reporting to be captured manually on the shop packet that was issued to the factory floor when the SO was released.

The big question is, is anything done with the data? Is it collected and keyed to a  spreadsheet and not shared, or is the transaction data keyed to SFC600? If it is being keyed, ask how often and by whom? Some companies use alternative methods to capture transaction data that do not require batch keying via a keyboard.

Not a lot of data is required to be keyed to SFC600 in order for the SO Inquiry to be useful. The data that should be reported for the transaction process is as follows:

  • The type of hours being reported – machine, run labor, setup labor
  • If reporting setup and run labor you want an employee clock number
  • The shop order and the operation that is being reported
  • Is the operation complete
  • How many good were produced at this operation
  • How many hours – the numbers of hours are critical. Do the employees estimate how many hours they worked, or do they track actual time started and stopped in order to calculate the actual number of hours.

Based on what is captured and how often will have an impact on the SO inquiry screen. Understanding the batch times as to when the transactions are keyed will provide you with the window as to the SO status at that point in time. Or, are they keyed as they happen in a near real time fashion so that you can have a more current view of the factory floor.

First120121122123125127128129Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

12345678910Last

Theme picker

Categories