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

Infor LN & Baan Tip: Considerations for Release to Warehousing for a Cost Item

When there are two Cost Items, one with Release to Warehousing applied and the other with Release to Warehousing not applied, upon approval of the Sales Order, the Cost Item that is released to Warehousing will go straight to Staged status, pending Shipment confirmation, while the Cost Item that is not released to Warehousing will be up for Sales Deliveries.

Apart from this main difference in functionality between having and not having this option to release to Warehousing checked, there are other impacts to consider. Below is some information gathered from various KBs related to the impact of having release to Warehousing applied (or not). KBs used as reference are listed as “– REF: KB XYZ”. Editing the checkbox “Release to Warehousing” itself If there is a Sales Order (in status Free is enough) for a Cost Item, the check box is not editable. As soon as all the Sales Orders for which the Item is involved are Closed (or Canceled or Deleted) the check box becomes editable again. – REF: KB 1439313 & KB 1613780 Simultaneous/separate release to Warehousing with Physical Items In a scenario where a Cost Item (that is released to Warehousing) and a physical Item are released to Warehousing separately, then the shipment confirmation of each of these Items will occur separately. If they are released simultaneously, the shipment of the Cost Item will not be processed unless and until the physical Item is ready to be shipped. – REF: KB 1449001 Note: Ensure a Warehouse is added to Order Lines to ensure Release to Warehousing Activity is applicable. – REF: KB 2229767 Invoicing

To invoice them separately or together, factors to consider are:

  • Composing Criteria, a list of fields that need to match to have a single invoice created – REF: KB 717977
  • Invoicing Methods (tcmcs0555m000) in the General tab, select Combine, for example, Shipments, to combine different Shipments of the same Sales Order into one Invoice. This Invoicing Method is also defined in
  • Invoice-to role of a Business Partner (tccom4112s000) in the Invoicing tab. – REF: KB 812637
  • For a Return Order where a Cost Item and a Physical Item were originally invoiced together, to invoice them together again, consider using Original Document type = Invoice and link the original Invoice to the Return Order. – REF: KB 2072847 

Note: Consider solution in KB 2108605 if Composing Criteria is met, yet still Credit Notes are not combined for a Return Sales Order copied from original Sales Order for one Physical Item and one Cost Item without release to Warehousing. 

ASN ASN cannot be generated for Purchase Order Lines with Cost Item if not released to Warehousing. – REF: KB 1548301 & KB 2111341 Intercompany Trade Intercompany Trade can be applied for a Cost Item that is released to Warehousing, as Intercompany Trade needs a Warehouse and a Department. – REF: KB 2112430 Customs Value Cost Items that are released to Warehousing that are handled via normal Sales Order Lines are considered as delivered goods and will get the customs value assigned like other Items being subject to warehouse handling. Cost Items handled on Shipment Lines as "Additional Cost" are not considered as delivered goods but as pure costs. The customs value of these shipment lines gets defaulted with a zero amount and cannot be modified. The same applies to additional costs on sales order lines. – REF: KB 1600847 Freight  Cost Items cannot be used for Freight handling. – REF: KB 1830170 Additional Cost

  • For automatically generated Additional Costs in Sales Orders, Cost Items that are released to Warehousing are not released to Warehousing. This is because automatic Additional Costs are always generated with 0 quantity, therefore only the amount is filled for these Lines, which leads to the Delivery Type being set to Sales and not Warehouse. As a result, delivery must take place in Sales module. – REF: KB 1995781
  • For Additional Cost Lines added to Shipment for Cost Items, refer to KB 2236856.

Intrastat Record When using Cost Items without release to Warehousing, there is no shipping data within Invoicing. Therefore, the corresponding Intrastat record cannot be found during the printing of the Invoice. To get the Invoice data filled on the Intrastat record, Cost Items with release to warehousing should be used. Otherwise, session Update Intrastat Transactions with Invoicing Data (tccom7271m100) should be ran to update the Invoicing data in Intrastat. – REF: KB 2005482

Previous Article Infor LX & BPCS Tip: What is the purpose of document sequencing? How does it work?
Next Article Effective September 30, 2023, IBM® will end support of the IBM i operating system 7.3
Print
15331 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

Enterprise General Ledger (EGL) provides audit attributes to track journal entry changes and approvals.

To implement this enhancement, you can request and apply MR 81026.

This enhancement provides audit attributes for the last maintained user, date, time, and approval user, and date, and time on the Financial Journal Entry and Financial Journal Entry Lines. This audit function provides visibility to who and when the journal was last maintained and to who and when the journal was approved.

The programs or areas impacted include:

  • Financial Event
  • Financial Journal Entry
  • Financial Journal Entry Line
  • Financial Journal Entry Detail Line
  • Post Multiple Events

Did you know CLD provides you with the following benefits?

â–ª You can journalize and post-transaction data from any third-party application or Infor LX subsystem to the Configurable Ledger (CLD).

â–ª You can generate multiple journal entries across different charts of accounts, ledgers, and books within the CLD from one transaction line.

â–ª You can automatically post transaction amounts across different books using an appropriate exchange rate between the batch transaction currency and target book currency.

â–ª You can use validation reports to identify validation errors within the files that contain batch transaction data and then you can make any necessary corrections before resubmission.

â–ª You can use standard CEA grouping and summarization options for journals created during Batch Transaction Processing.

â–ª You can interface GLD journal entries into CEA for the BPCD version of Infor LX. This allows data to be interfaced into CEA without changing the way data is processed through Infor LX subsystems.

First2223242527293031Last

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