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: Using Country of Origin for Purchase Orders

For purchase orders, information about the COO allows you to track the related import duties, tariffs, and compliance with sourcing requirements. You can maintain the COO of an item when creating an order or the release level of a purchase order.

When you create a purchase order line in the Purchase Order Lines (tdpur4101m000) session, the COO related details are defaulted based on the item-purchase data defined in the Items - Purchase (tdipu0101m000) session. To view this data, you can use the Country of Origin option from the References menu in the Purchase Order Lines (tdpur4101m000) session.

After the order line is released to Warehousing, an inbound line is created in the Inbound Order Lines (whinh2110m000) session with the COO information. A receipt line is created in the Warehouse Receipt Lines (whinh3512m100) session when the inbound order line is received. To view the actual COO for the item specified on the receipt line, you can use the Country of Origin option from the References menu in this session.

You can view the country of origin (COO) data for the inventory received in a warehouse in the Item - Country of Origin Inventory (tcitu6600m000) session based on the data specified in the header section such as, warehouse, item, and so on.

In the Inventory Tracking Receipt (tcitu2610m000) session, you can view the information related to the purchase order, inventory quantity, and actual COO of the item. You can use the Intrastat Transactions (tccom7171m000) session to view the COO that is reported for an order line and is used for the Intrastat declaration.

Previous Article Infor LN & Baan Tips & Tricks for FINANCE: Remap Posted Integration Transactions (tfgld4282m100)
Next Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Impact of Configuration Changes on Audit Trails
Print
47126 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Get ahead of the curve with a seamless, comprehensive integration strategy that surpasses other competitive solutions. In part two of this webinar, join our discussion of best practice integration tricks and solutions from a fellow customer’s office of finance. Understand what makes their integration approach effective and review best practices in integrating your IBM i solution to other office of finance solutions (F9/EPM/Birst/GRC).

Hosted by Peg Tuttle from the IBM i podcast, “The Incredible i Show”. 

  • How version upgrades have tightened internal control loopholes.
  • Structural IBM i advancements designed to safeguard your organization.
  • IBM i ecosystem solutions that strengthen both data and access vulnerabilities.

Don't miss this fourth fireside chat, Eight Ways to Modernize your IBM i product – Topic #3 of 8: Best practices in integration for the office of finance (Part 2). Register today!

Register today!

Did you know that you can set up one-time vendors in LX? One Time Vendor (1,A): Specify Y to indicate that this vendor is a one-time vendor. Otherwise, could you specify N. The system removes a one-time vendor's information from the Vendor Master file after all transactions are reconciled. If this vendor already exists as a one-time vendor, you can specify N to change the vendor to a regular vendor.

FirstLast

Tips: LN | Baan

Categories