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

[EasyDNNnews:IfExists:Event]
[EasyDNNnews:IfExists:EventRegistration][EasyDNNnews:EventRegistration:RegisterButton][EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:Payment][EasyDNNnews:Price][EasyDNNnews:EndIf:Payment] [EasyDNNnewsLocalizedText:Eventdate]: [EasyDNNnews:EventDate] [EasyDNNnewsLocalizedText:ExportEvent] [EasyDNNnews:IfExists:EventLocation]

[EasyDNNnewsLocalizedText:EventLocation]: [EasyDNNnews:EventLocation]

[EasyDNNnews:EndIf:EventLocation] [EasyDNNnews:IfExists:EventRegistration]
  • [EasyDNNnewsLocalizedText:NumberOfAttendants]: [EasyDNNnews:EventRegistration:NumberOfAttendants]
  • [EasyDNNnewsLocalizedText:MaxNumberOfTickets]: [EasyDNNnews:EventRegistration:MaxNumberOfTickets]
  • [EasyDNNnewsLocalizedText:NotUsedTickets]: [EasyDNNnews:EventRegistration:NotUsedTickets]
  • [EasyDNNnews:IfExists:Payment]
  • [EasyDNNnewsLocalizedText:Price]: [EasyDNNnews:Price]
  • [EasyDNNnews:EndIf:Payment]
[EasyDNNnews:EventRegistration:InfoMessage] [EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:EventSignUp]

[EasyDNNnewsLocalizedText:AreYouGoing]

[EasyDNNnews:SignUpActionBar]
[EasyDNNnews:EndIf:EventSignUp]
[EasyDNNnews:EndIf:Event] [EasyDNNnews:IfMediaType:Image]
[EasyDNNnews:Title] [EasyDNNnews:IfExists:GalleryBackLink] [EasyDNNnewsLocalizedText:ViewInGallery] [EasyDNNnews:EndIf:GalleryBackLink]
[EasyDNNnews:EndIfMediaType] [EasyDNNnews:IfMediaType:EmbedMedia]
[EasyDNNnews:MainMedia] [EasyDNNnews:IfExists:GalleryBackLink] ViewInGallery [EasyDNNnews:EndIf:GalleryBackLink]
[EasyDNNnews:EndIfMediaType]
[EasyDNNnews:Author:Link]
/ [EasyDNNnewsLocalizedText:Categories]: [EasyDNNnews:Categories]

Infor LN & Baan Tip: Separate item codes for incoming & outgoing subassemblies

You may be wondering if it's necessary to have separate item codes for incoming and outgoing subassemblies.

No, it is not necessary to have separate item codes for incoming and outgoing subassemblies, but it is recommended. In theory, you could have only one item code with the description subassembly and use the same item code for the outgoing subassembly and for the incoming subassembly. However, when monitoring inventory movements and financial integration transactions, it will be difficult to understand the process. Also, the costing logic is much clearer when different item codes for the incoming and outgoing subassemblies are used. Because of this, it is advised to use a different item code for the outgoing subassembly and a different item code for the incoming subassembly.

Previous Article Infor LX & BPCS Tip: Changing an item to non-inventory
Next Article Infor LX & BPCS Tip: What items should be M-P-S planned vs. M-R-P planned?
Print
61996 Rate this article:
5.0
[EasyDNNnews:GravityGallery] [EasyDNNnews:IfExists:AuthorProfile]
[EasyDNNnews:Author:Image:Width:85:Height:120:Resize:Crop]

[EasyDNNnews:Author:DisplayName][EasyDNNnews:Author:RSSURL]

[EasyDNNnews:Author:ShortInfo] [EasyDNNnewsLocalizedText:Otherpostsby] [EasyDNNnews:Author:Link]
[EasyDNNnews:Author:Contact] [EasyDNNnews:Author:FullInfo] [EasyDNNnews:Author:Facebook] [EasyDNNnews:Author:Twitter] [EasyDNNnews:Author:LinkedIn] [EasyDNNnews:Author:GooglePlus] [EasyDNNnews:Author:YouTube] [EasyDNNnews:Author:Instagram] [EasyDNNnews:Author:Website]
[EasyDNNnews:EndIf:AuthorProfile] [EasyDNNnews:IfExists:AuthorGroup]
[EasyDNNnews:Author:GroupImage:Width:85:Height:120:Resize:Crop]

[EasyDNNnews:Author:GroupName][EasyDNNnews:Author:GroupRSSURL]

[EasyDNNnews:Author:GroupInfo]
[EasyDNNnews:Author:GroupContact] [EasyDNNnews:Author:GroupFacebook] [EasyDNNnews:Author:GroupTwitter] [EasyDNNnews:Author:GroupLinkedIn] [EasyDNNnews:Author:GroupGooglePlus] [EasyDNNnews:Author:GroupYouTube] [EasyDNNnews:Author:GroupInstagram] [EasyDNNnews:Author:GroupWebsite]
[EasyDNNnews:EndIf:AuthorGroup] [EasyDNNnews:RelatedArticles]

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

This enhancement allows users to update Reason Code Maintenance, INV140D1, for Transaction Effects that they are not authorized to in any other programs. A new system parameter was added to Inventory Parameters, INV820D. The enhancement allows users who do not actually perform transactions in Infor LX to maintain the reason codes for the transactions.

This enhancement provides clients the ability to store the opening/ending on hand balance for each Inventory period at the Item (IIM), Warehouse/Item (IWI) and Lot/Location (ILI) levels. Infor LX clients can back date inventory transactions into the immediate previously closed period, and thus update what was saved as the opening/ending balance throughout the current open period. 

Tracking the opening/ending/period balance for each inventory period can give users insights into the levels of inventory for each item, item/warehouse and item/warehouse/lot/location combination.

FirstLast

Tips: LN | Baan

You can move monthly periods to a different parent period. For example, if you have a monthly calendar, you can create quarter periods and move months to the quarters.

  1. Select Financials > Global Ledger > Setup > Finance Enterprise Group > Maintenance.
  2. Open the finance enterprise group.
  3. Click the Calendar tab.
  4. Open the calendar for which you want to move periods.
  5. Click the Hierarchy tab.
  6. Select the periods to move.
  7. Select Actions > Move.
  8. Select the new parent period under which you want to move the periods.
  9. Click OK.

Categories