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
47337 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

The Customer Tax Exemption Maintenance program, SYS160, allows you to specify customer declarations used by the Customer Order Entry (ORD) and Billing (BIL) applications to apply a tax rate code to specific order lines of an invoice.

With this program, Infor LX can invoice customers without value-added tax (VAT) if one of the following conditions occurs:

  • The cumulated...

Don’t laugh! I know, I know…many of our customers say that after 7-10 years they are finally settling in after the implementation! We have seen many a customer stretch out the lifespan of their ERP system to 20+ years. That sounds great for the company’s bank account, but is it good for the business?

An outdated ERP system hurts your business in many ways, not just with slow performance. The best-of-breed functionality is now 2 decades old, and obsolete technology can't leverage newer technology. Lack of integration leads to siloed data that hurts communication and your internal teams feel the pain, and your customers are noticing. Poor visibility into your operations makes it nearly impossible to achieve industry-based regulatory compliance and meet financial auditing requirements. Not to mention the sheer size of Big Data that is being collected today vs. 2 decades ago or the fact that your vendor is no longer supporting your ERP version.

Let’s scrap it all and start over!...

FirstLast

Tips: LN | Baan

Categories