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
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Ledger Default Account

If you do not wish to define a detailed mapping to various ledger accounts for specific integration transactions, you can map the corresponding integration document type to a default account. All the transactions of the integration document type for which an account cannot be determined based on the mapping scheme details, are posted to the default account.

 

The mapping of an integration document type to a default account is direct, without the need for element groups and mapping elements. No distinction is made on any of the transaction details.

 

Default accounts can be used in two ways:

  • Instead of a detailed mapping to various ledger accounts. All the transactions are posted to the same account. For example, all warehouse receipts are posted to the Inventory ledger account, without any distinction.
  • In addition to a detailed mapping. If a transaction cannot be mapped based on the detailed mapping scheme, it is posted to the default account.
Previous Article 2017 Top Ten Trends in Modern Demand-Driven Manufacturing
Next Article BPCS/LX Tip of the Week: Handwritten Inventory Tickets
Print
33986 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

This is a simple way to go from the customer order to making the order and shipping the order. It involves a few simple steps:

  1. Receive and enter the customer order
  2. Automatic credit review
  3. Automatic release of the shop order tied to the customer order
  4. Issue material, report labor to the production order receipt
  5. Pick the order, ship the order, invoice the customer


With lean, you can skip processing the demand through MRP. You can go directly from the customer order to the shop order creation.

Define Inventory transactions for issuing components to the shop and receiving finished items. See the Inventory help text for examples of transactions.

  • Transaction type I - Single Issue to Shop Order. Use this transaction type to issue one component at a time. Use this for high-value items that are marked as Must Single Issue on the Item Master file.
  • Transaction type M - Multiple Issue to Shop Order. Use this transaction type to issue all the components as listed in the Shop Order, in one transaction. Note that this transaction type does not issue Must Single Issue items.
  • Transaction type S - Receipt from shop. Use this transaction type to receive the finished item into stock and update the shop order accordingly. 

The Shop Order Lot/Location Allocation program is an alternative to using the above Inventory transactions. Use this when the item is finished, and you want to review exactly what was used to make it. You can review the components as allocated, make any changes, and finally accept the finished order.

First132133134135137139140141Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

1345678910Last

Theme picker

Categories