difference study infor erp baan 5.0c - erp ln 6.1 fp2baansupport.com/docs/erpln/p3597b us.pdf ·...

Infor ERP LN 6.1

Difference Study Infor ERP Baan 5.0c - ERP LN6.1 FP2

© Copyright 2011 Infor

All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Inforand/or its affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respectiveowners.

Important Notices

The material contained in this publication (including any supplementary information) constitutes and contains confidentialand proprietary information of Infor.By gaining access to the attached, you acknowledge and agree that the material (including any modification, translationor adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the soleproperty of Infor and that you shall not gain right, title or interest in the material (including any modification, translation oradaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solelyin connection with and the furtherance of your license and use of software made available to your company from Inforpursuant to a separate agreement (“Purpose”).In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain suchmaterial in strict confidence and that your use of such material is limited to the Purpose described above.Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Inforcannot warrant that the information contained in this publication is complete, does not contain typographical or othererrors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability,consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors oromissions in this publication (including any supplementary information), whether such errors or omissions result fromnegligence, accident or any other cause.

Trademark Acknowledgements

All other company, product, trade or service names referenced may be registered trademarks or trademarks of theirrespective owners.

Publication Information

P3597B USDocument code

B5061Release

September 2011Publication date

About this document

...............19Chapter 1 Common.............................................................................................................

...............19Changed and new functionality....................................................................................

...............19Alternative manufacturers..................................................................................

...............20Alternative items for sold-to business partners..................................................

...............20Company data....................................................................................................

...............20Configured items without PCS...........................................................................

...............21Date effective item type......................................................................................

...............22Date-effective parameters..................................................................................

...............22Delete item data and structures.........................................................................

...............23Employees.........................................................................................................

...............24Entity - entity relationships.................................................................................

...............25Environmental compliance.................................................................................

...............25EU sales listing declaration................................................................................

...............26Grand total rounding..........................................................................................

...............26Intrastat declaration...........................................................................................

...............27Lot control by serialized items............................................................................

...............28Sales and use tax..............................................................................................

...............29Standard calendar..............................................................................................

...............29Table sharing......................................................................................................

...............30Taxation - general..............................................................................................

...............32Tax provider........................................................................................................

...............33Terminology changes in the Central Calendar Management (CCP) module.....

...............33Time zones.........................................................................................................

...............34Unit Effectivity (UEF)..........................................................................................

...............35Withholding tax and social contributions............................................................

...............36Modules.......................................................................................................................

...............36Central Calendar Management (CCP) module - Differences B50c/ERP61.......

...............38Enterprise Modeling Management (EMM) module - Differences B50c/ERP61..

Table of Contents

...............38Financial Integrations (FIN) module - Differences B50c/ERP61........................

...............39General Data (COM) module - Differences B50c/ERP61..................................

...............39Item Base Data (IBD) module - Differences B50c/ERP61.................................

...............41Tables (MCS) module - Differences B50c/ERP61.............................................

...............43Chapter 2 People.................................................................................................................

...............43Hours Accounting - Differences by ERP LN 6.1 topic..................................................

...............43Centralized hours accounting............................................................................

...............44Hours budgeting.................................................................................................

...............44Hours approval and processing.........................................................................

...............44Related data.......................................................................................................

...............45Enhanced usability.............................................................................................

...............45Usability enhancements for People in ERP LN 6.1.....................................................

...............45Easy access to all employee-related data.........................................................

...............45Single point of access to hours and expenses sessions....................................

...............46Fast data-entry in hours accounting sessions....................................................

...............46User profiles.......................................................................................................

...............46Assignments.......................................................................................................

...............46Improved employee selection............................................................................

...............47Update actual hours for other period table codes..............................................

...............47Registration and approval authorizations...........................................................

...............47Posting to Financials..........................................................................................

...............47Miscellaneous new sessions..............................................................................

...............49Chapter 3 Financials...........................................................................................................

...............49Changed and new functionality....................................................................................

...............49Automatic direct debit procedure.......................................................................

...............49Bank charges.....................................................................................................

...............50Bank master data...............................................................................................

...............50Belgian localizations..........................................................................................

...............52Cash application................................................................................................

...............53Cash flow statements.........................................................................................

...............53Consumption tax................................................................................................

...............54Currency differences..........................................................................................

...............55Daily balances....................................................................................................

...............55Dimension accounting........................................................................................

...............56Employee's expenses........................................................................................

...............56Factoring............................................................................................................

...............57Fixed assets management enhancements........................................................

...............58Freight Management integration........................................................................

...............59German localizations.........................................................................................

...............60GL codes............................................................................................................

...............61Integration mapping scheme..............................................................................

...............62Intercompany settlement....................................................................................

...............63Intercompany settlement....................................................................................

...............64Interim Revenue reconciliation...........................................................................

...............66Japanese bank file layout..................................................................................

...............66Journal books.....................................................................................................

...............67Ledger history....................................................................................................

...............67Localizations......................................................................................................

...............69Lower cost or market value method...................................................................

...............70Monthly billing invoice........................................................................................

...............70Multicompany purchase invoice matching.........................................................

...............71Multiple control accounts...................................................................................

...............72Open entry enquiries on purchase orders..........................................................

...............73Parameter wizard...............................................................................................

...............73Payment slips.....................................................................................................

...............74Pay-to business partner statistics......................................................................

...............74Period handling for integration transactions.......................................................

...............75Procurement card payments..............................................................................

...............76Purchase invoice matching - Enhanced error reporting.....................................

...............77Reconciliation.....................................................................................................

...............77Recurring journal transactions...........................................................................

...............78Remap integration transactions.........................................................................

...............78Reverse entries..................................................................................................

...............79Scandinavian localizations.................................................................................

...............79Trade notes........................................................................................................

...............80VAT books..........................................................................................................

...............81Modules.......................................................................................................................

...............81Accounts Payable (ACP) module - Differences B50c/ERP61............................

...............84Accounts Receivable (ACR) module - Differences B50c/ERP61.......................

...............87Cash Management (CMG) module - Differences B50c/ERP61.........................

...............91Cost Accounting (CAT) module - Differences B50c/ERP61...............................

...............92Fixed Assets Management - Differences B50c/ERP61.....................................

...............94Financial Budget System (FBS) module - Differences B50c/ERP61.................

...............95Financial Statements (FST) module - Differences B50c/ERP61.......................

...............95General Ledger (GLD) module - Differences B50c/ERP61...............................

.............103Chapter 4 Enterprise Planning...........................................................................................

.............103Changed and new functionality....................................................................................

.............103Aggregation and disaggregation........................................................................

.............104Allow multiple sources per requirement.............................................................

.............104Boundaries on supply sources...........................................................................

.............105Capacity and component CTP...........................................................................

.............106Company switching............................................................................................

.............107Cumulative Order Lead Time (COLT)................................................................

.............107Date-effectivity on item type...............................................................................

.............108Distribution planning and multisite planning.......................................................

.............109Fixed delivery moments.....................................................................................

.............109Master planning.................................................................................................

.............110Material-routing relationships.............................................................................

.............110Offsetting logic in master-based planning..........................................................

.............111Order grouping...................................................................................................

.............112Order pegging....................................................................................................

.............112Order planning...................................................................................................

.............113Planned orders...................................................................................................

.............114Resource capacity planning...............................................................................

.............115Signals...............................................................................................................

.............116Sort and select planned purchase orders by buyer...........................................

.............116Sort and select planned purchase orders by supplier........................................

.............117Supply chain strategy.........................................................................................

.............117Switch off the time fence....................................................................................

.............118Terminology changes.........................................................................................

.............118Transfer of orders to the execution level............................................................

.............119Unit effectivity.....................................................................................................

.............119Use-up materials and alternative materials........................................................

.............120Warehouse on the BCM line..............................................................................

.............120Modules.......................................................................................................................

.............120Cyclic Planning (CLP) module – Differences B50c/ERP61...............................

.............120Resource Planning Data (RPD) module – Differences B50c/ERP61................

.............123Chapter 5 Order Management............................................................................................


.............123Alternative items................................................................................................

.............123ATP/CTP in Sales Control..................................................................................

.............124Business partner search....................................................................................

.............125Cancel sales orders...........................................................................................

.............126Commission and rebate currencies...................................................................

.............128Configured items in Sales Control.....................................................................

.............128Delivery notes....................................................................................................

.............129Delivery types....................................................................................................

.............131Effectivity units...................................................................................................

.............131Equate balance of receipts with inventory level.................................................

.............132Invoicing commissions and rebates...................................................................

.............135Link between Purchase Control and Freight Management................................

.............136Link between Sales Control and Freight Management......................................

.............137List groups..........................................................................................................

.............138Lot and serial information on the sales order.....................................................

.............138Over deliveries...................................................................................................

.............139Order entry.........................................................................................................

.............140Order units.........................................................................................................

.............142Print prices and discounts by business partner.................................................

.............142Purchase back orders........................................................................................

.............143Purchase orders for non-direct deliveries..........................................................

.............144Purchase order approval....................................................................................

.............145Purchase order line types..................................................................................

.............146Purchase order origin.........................................................................................

.............147Purchase order receipt information....................................................................

.............148Purchase order status........................................................................................

.............150Purchase requisition enhancements..................................................................

.............150Purchase schedules...........................................................................................

.............151Reconciliation (Purchase Control).....................................................................

.............152Reconciliation (Sales Control)............................................................................

.............153Sales order acknowledgements.........................................................................

.............154Sales order approval..........................................................................................

.............154Sales contracts..................................................................................................

.............155Sales order delivery and invoice information.....................................................

.............156Sales order line types........................................................................................

.............157Sales order status..............................................................................................

.............158Sales price includes upgrade price for unit effective items................................

.............159Sales return orders............................................................................................

.............160Sales schedules.................................................................................................

.............161Self billing...........................................................................................................

.............161Shipping constraints...........................................................................................

.............163Synchronize header - lines................................................................................

.............163Tax......................................................................................................................

.............165Modules.......................................................................................................................

.............165Commission Control System (CMS) module - B50c/ERP61..............................

.............166Item Purchase Data (IPU) module - Differences B50c/ERP61..........................

.............167Item Sales Data (ISA) module - Differences B50c/ERP61................................

.............168Pricing Control (PCG) module - Differences B50c/ERP61................................

.............169Product Catalog (PCT) module - Differences B50c/ERP61...............................

.............170Purchase Statistics (PST) module - Differences B50c/ERP61..........................

.............170Purchase Control (PUR) module - Differences B50c/ERP61............................

.............173Sales Control (SLS) module - Differences B50c/ERP61...................................

.............176Sales Statistics (SST) module - Differences B50c/ERP61................................

.............179Chapter 6 Central Invoicing................................................................................................


.............179Billing request composing criteria......................................................................

.............179Change composed invoices...............................................................................

.............180Print draft invoices in logistic packages.............................................................

.............181Print references to rebate agreements on sales invoices..................................

.............181Print texts and details on invoices......................................................................

.............182Rebates..............................................................................................................

.............182Modules.......................................................................................................................

.............182Sales Invoicing (SLI) module - Differences ERP61/B50c..................................

.............187Chapter 7 Manufacturing....................................................................................................


.............187Add and explode phantoms in a production order.............................................

.............187Alternative material and use-up of old revisions................................................

.............188Cost components...............................................................................................

.............188Costing work centers.........................................................................................

.............189Drawing sizes and drawing locations in EDM....................................................

.............189ECO approval procedure...................................................................................

.............189Engineering Change Orders (ECOs).................................................................

.............190Engineering item groups....................................................................................

.............190Generic Browser Framework (GBF)..................................................................

.............191Generic engineering data: BOM and routing.....................................................

.............192Graphical planning board in SFC (Webtop).......................................................

.............193Hours accounting...............................................................................................

.............193Lead time elements............................................................................................

.............194Lot by unit...........................................................................................................

.............194Lower cost or market value................................................................................

.............194Machine utilization chart....................................................................................

.............195Micro routing......................................................................................................

.............195Operation overlap..............................................................................................

.............195Order pegging in Manufacturing........................................................................

.............196Production order groups....................................................................................

.............196Production warehouse orders............................................................................

.............197Project segment in Engineering Data Management (EDM)...............................

.............198Pull notes...........................................................................................................

.............198Reference designators.......................................................................................

.............199Revenue recognition..........................................................................................

.............199Rough capacity consumption of work centers in PCS.......................................

.............199Sequence of material issue and backflushing....................................................

.............200Shared work centers..........................................................................................

.............200Task type............................................................................................................

.............201Task - work center relationships.........................................................................

.............201WIP warehouses................................................................................................

.............202Modules.......................................................................................................................

.............202BOM Control (BOM) module - Differences B50c/ERP61...................................

.............203Cost Accounting (CPR) module - Differences B50c/ERP61..............................

.............203Production Order Costing (CST) module - Differences B50c/ERP61................

.............204Engineering Data Management (EDM) module - Differences B50c/ERP61......

.............205Hours Accounting (HRA) module - Differences B50c/ERP61............................

.............206Product Configuration (PCF) module - Differences B50c/ERP61......................

.............206Project Control (PCS) module - Differences B50c/ERP61.................................

.............207Routing (ROU) module - Differences B50c/ERP61...........................................

.............209Chapter 8 Warehouse Management...................................................................................


.............209Adjustments and cycle counting........................................................................

.............210Blocking..............................................................................................................

.............210Cross-docking....................................................................................................

.............211Delivery notes....................................................................................................

.............211Direct material supply........................................................................................

.............211Handling units....................................................................................................

.............212Integration with Freight Management................................................................

.............215Integration with Service......................................................................................

.............215Inspections.........................................................................................................

.............216Line supply.........................................................................................................

.............217Loading list.........................................................................................................

.............217Lots (not in inventory)........................................................................................

.............218Multicompany warehouse transfers...................................................................

.............218Order grouping...................................................................................................

.............219Order cancellation..............................................................................................

.............219Receipts.............................................................................................................

.............220Serialized items..................................................................................................

.............222Shipment generation for warehouse issues.......................................................

.............222Unit effectivity.....................................................................................................

.............223Usability improvements for shipment notices.....................................................

.............223Warehouse Management dashboard sessions..................................................

.............224Warehousing order processing..........................................................................

.............224Modules.......................................................................................................................

.............224Inventory Analysis (INA) module - Differences B50c/ERP61.............................

.............225Inventory Handling (INH) module - Differences B50c/ERP61............................

.............227Inventory Planning (INP) module - Differences B50c/ERP61............................

.............228Inventory Reporting (INR) module - Differences B50c/ERP61..........................

.............228Lot Control (LTC) module - Differences B50c/ERP61........................................

.............229Warehouse Master Data (WMD) module - Differences B50c/ERP61................

.............231Chapter 9 Freight Management..........................................................................................

.............231Freight Management - Differences by ERP Baan5.0c topic........................................

.............231ERP Baan5.0c...................................................................................................

.............231ERP LN 6.1........................................................................................................

.............231Freight Management..........................................................................................

.............233Chapter 10 Service..............................................................................................................


.............233Call blocking.......................................................................................................

.............233Call handling......................................................................................................

.............234Contract coverage at item level.........................................................................

.............235Customer call dashboard...................................................................................

.............235Direct call invoicing............................................................................................

.............236Failure analysis..................................................................................................

.............237Functional element.............................................................................................

.............237Global update of contract prices........................................................................

.............238Item-specific contract templates........................................................................

.............238Item pricing using contract item price lists.........................................................

.............238Labor rates and skills.........................................................................................

.............239PCS/Service integration enhancements............................................................

.............240Physical breakdown structure............................................................................

.............241Pricing and discounts.........................................................................................

.............241Reference activities............................................................................................

.............242RMA and depot repair........................................................................................

.............243Serialized items in Service.................................................................................

.............243Serialized items dashboard for Service.............................................................

.............244Service type and coverage type.........................................................................

.............244Subcontract management..................................................................................

.............246Transaction logging............................................................................................

.............247Modules.......................................................................................................................

.............247Configuration Management (CFG) module - Differences B50c/ERP61.............

.............247Call Management (CLM) module - Differences B50c/ERP61............................

.............248Contract Management (CTM) module - Differences B50c/ERP61....................

.............248Master Data Management (MDM) module - Differences B50c/ERP61..............

.............249RMA & Depot Repair (MSC) module - Differences B50c/ERP61......................

.............249Subcontract Management (SBM) module - Differences B50c/ERP61...............

.............249Service Order Control (SOC) module - Differences B50c/ERP61.....................

.............251Chapter 11 Project...............................................................................................................


.............251Activities.............................................................................................................

.............252Combine PRP warehouse orders......................................................................

.............252Contract data......................................................................................................

.............253Copy activities....................................................................................................

.............253Employee data...................................................................................................

.............254Expense tax.......................................................................................................

.............254Hours accounting...............................................................................................

.............254Independent currency system............................................................................

.............255Integration of Project with Service.....................................................................

.............256Integration of Infor ERP Project with Microsoft Project......................................

.............257Internal project...................................................................................................

.............257Invoicing enhancements....................................................................................

.............259PCS item procedure...........................................................................................

.............259Project dashboard..............................................................................................

.............260Project estimation..............................................................................................

.............261Project specific labor rates.................................................................................

.............262Project template.................................................................................................

.............263Project warehouse.............................................................................................

.............263Revenue Recognition (RR) and Cost of Goods Sold (COGS)...........................

.............264Usability improvements......................................................................................

.............265Modules.......................................................................................................................

.............265Project Estimating (EST) module - Differences ERP61/B50c............................

.............265Hours Accounting (HRS) module - Differences B50c/ERP61............................

.............266Project Data Management module - Differences B50c/ERP61.........................

.............267Project Invoicing (PIN) module - Differences B50c/ERP61...............................

.............268Project Production Control (PPC) module - Differences B50c/ERP61..............

.............269Project Scheduling System (PSS) module - Differences B50c/ERP61..............

.............269Project Technical Calculation (PTC) module - Differences B50c/ERP61...........

.............271Chapter 12 Quality Management........................................................................................


.............271Handling units....................................................................................................

.............272Modules.......................................................................................................................

.............272Product Testing and Control (PTC) module - Differences B50c/ERP61............

.............273Chapter 13 Object Data Management................................................................................


.............273Application data locks........................................................................................

.............273Archive files........................................................................................................

.............274Delete files in withdraw document revision mode..............................................

.............274Dynamic host.....................................................................................................

.............275Folder life cycle..................................................................................................

.............275Link query condition to previous run..................................................................

.............276Mail option for folder..........................................................................................

.............276Parallel development.........................................................................................

.............277Query filter..........................................................................................................

.............277Related objects..................................................................................................

.............277Related vault areas............................................................................................

.............278Relative change order........................................................................................

.............278Reviewers mechanism.......................................................................................

.............279Revise change...................................................................................................

.............280Rules and attributes...........................................................................................

.............280Selection of vault areas......................................................................................

.............281Timeframe for reviewers....................................................................................

.............281Modules.......................................................................................................................

.............281Change Management (CHM) module - Differences B50c/ERP61.....................

.............282Common (COM) module -Differences B50c/ERP61..........................................

.............282Document Management (DM)module - Differences B50c/ERP61.....................

.............283Folder Management (FMG) module - Differences B50c/ERP61........................

.............283Queries and Reports (QRY) module - Differences B50c/ERP61.......................

.............284ODM Configuration (SYS) module - Differences B50c/ERP61..........................

Index

SummaryThis manual describes the differences between ERP Baan5.0c and ERP LN 6.1 on a high level.

How to read this guideEvery chapter lists the changed and new functionality of an ERP LN package, and briefly explains thenew terms and concepts. The "Modules" section provides a list of the changes to each module as wellas information on new, replaced, and removed modules.

The chapter titles reflect the ERP LN 6.1 names of the various packages. For example, for informationabout the changes to BAAN Warehousing, refer to Chapter 4, "Warehouse Management".

This manual was created by extracting the text from the Differences ERP Baan5.0c and ERP LN 6.1online Help. These topics only describe what has changed and refer to the ERP LN 6.1 online Help toexplain the current ERP LN functionality. Wherever you read “refer to”, you are referred to the ERP LN6.1 online Help topics.

Comments?We continually review and improve our documentation. Any remarks/requests for information concerningthis document or topic are appreciated. Please e-mail your comments to [email protected] .

In your e-mail, refer to the document number and title. More specific information will enable us to processfeedback efficiently.

Customer SupportIf you have questions regarding the Infor products described, go to Infor’s Customer Support portal atwww.infor365.com .

▪ To access Infor365, go to www.infor365.com and log in. If you do not have an Infor365 account,click Register now, complete the registration form, and a login will be sent to you within 24hours.

▪ To access Infor knowledgebases, documentation, downloads, communities, and incidents,click the appropriate link in the top menu of the home page.

▪ To find your local support phone number, click Contact Infor in the top right corner of thehome page, enter a product name, and click Search.

Infor ERP LN 6.1 | Difference Study Infor ERP Baan 5.0c - ERP LN 6.1 FP2 | 17

About this document

mailto:[email protected]

http://www.infor365.com/

http://www.infor365.com/

18 | Infor ERP LN 6.1 | Difference Study Infor ERP Baan 5.0c - ERP LN 6.1 FP2

About this document

Changed and new functionality

Alternative manufacturers

Differences between ERP Baan5.0c and ERP LN 6.1.

ERP Baan5.0cIn ERP Baan5.0c, manufacturers were only used as item grouping data. You could select onemanufacturer for an item.

ERP LN 6.1In ERP LN 6.1, you can specify a number of manufacturers for an item, and ensure that you only receiveitems from approved manufacturers.

Companies that build their products from various components often buy the components from othermanufacturers and sell them as part of their own product and under their own name. The componentscan be obtained from various manufacturers on the condition that the components have similar or thesame specifications and quality.

Examples of such components are the engines and tires in the car industry, or integrated circuit boardsand so on in the electronic equipment industry.

When you receive the ordered items, you must check that they were produced by an approvedmanufacturer.

ERP LN allows you to specify a number of manufacturers for an item, and to ensure that you only receiveitems from approved manufacturers. For details, refer to To buy items from alternative manufacturers.

The technical coordinatorApproving the manufacturers for items is the responsibility of the item's technical coordinator. Thetechnical coordinator is responsible for maintaining the technical item specifications and the requirementsfor the manufacturer of the item. This employee is also responsible for maintaining the informationconcerning hazardous material and the risk classification in Warehouse Management.


1Chapter 1Common

Alternative items for sold-to business partners


New in Infor ERP LN 6.1In ERP LN 6.1, you can indicate that a sold-to business partner accepts alternative items. If an ordereditem is not available, ERP LN allows you to select alternative items for a sales order.

In the Sold-to Business Partners (tccom4110s000) session, the following fields were added:

▪ Allow Alternative List GroupsIf this check box is selected, during sales-order line entry for the sold-to business partner youcan select list items from the list group that is linked to the business partner as well as fromother list groups.

▪ Allow Shipment of Multiple Alternative ItemsIf this check box is selected, the sold-to business partner accepts the ordered item as well asalternative items in one shipment.For example, if insufficient quantity of the ordered item is available, the shipment can containthe available quantity of the ordered item and additional quantities of alternative items thatare required to reach the ordered quantity.

Company data


ERP Baan5.0cIn ERP Baan5.0c, the Company Data (tccom0100s000) session contained two types of data:

▪ The company data such as the company's address and the company language.

▪ The selection of packages, modules, and concepts used.

As a result, the session title did not properly indicate what the session contained.

ERP LN 6.1In ERP LN 6.1, the company data is divided between two sessions:

▪ General Company Data (tccom0102s000)This new session contains the company data such as the company's address, the companylanguage, and the company's tax number and fiscal identification number.

▪ Implemented Software Components (tccom0100s000)This session only contains the selection of packages, modules, and concepts used.

Configured items without PCS



Common

ERP Baan5.0cIn ERP Baan5.0c, configured products in the Product Configuration module of Manufacturing are handledas customized items to which a PCS project must be linked. The PCS project provides the item with adetailed cost roll-up, and the advantage of pegging. However, in high-volume environments, a detailedcost roll-up is often not required. In addition, the extra time required to calculate the project costs, andto delete the project structure afterwards, is unwanted.

ERP LN 6.1In ERP LN 6.1, you can configure an item in the Product Configuration (PCF) module of Manufacturingwithout using a PCS project. You can define generic items with the order policy Anonymous in theItems - Ordering (tcibd2500m000) session, so that standard items are generated rather than customizeditems. As a result, no time is required anymore to calculate project costs you do not require, and youdo not need to delete project structures afterwards.

Because the project code is no longer the distinguishing feature for a standard configured item, you cannow sort the items on product variant to easily find the product variant you want. In the Items - General(tcibd0501m000) session, on the view menu, point to Sort by and click Product Variant, Project, Item.

In the Delete Item Data (tcibd0206m000) session, you can use the Type of Deletion check box, andthe Delete items based on BOM Structure field to delete the standard configured items and theiraccompanying structures.

For more information about configured items without PCS in Manufacturing, refer to Configured itemswithout PCS

Date effective item type


ERP Baan5.0cIn ERP Baan5.0c, you could not change the item type. If you wanted to purchase an item of theManufactured item type, you had to define another item with the same specifications and of thePurchased item type.

ERP LN 6.1In ERP LN 6.1, you can enter an effective date and an expiry date for the item sourcing types Purchasedand Manufactured. As a result, these attributes apply during the specified period of time.

The item type that you specify in the Item - General (tcibd0101s000) session and the Item - GeneralDefaults (tcibd0102s000) session is the default item type.

In the new Date-Effective Item Data (tcibd0110s000) session, you can enter the item type for specificperiods of time. The item type is specific for the current logistic company.


Common

Change control of date-effective item dataIf you use Data Management, you can use the Change Management module for the change control ofthe item type. baan enters the item type and its effective date and expiry data when you approve achange order in the Change Management module. In this way, you can change the item type and otherbaan data at the same time. You must select the CHM Control check box in the Item - General(tcibd0101s000) session to indicate that you want to use change order control for the item.

To support change control of the date-effective item type, in the Item - General (tcibd0101s000) session,the following fields and check boxes were added:

▪ CHM Control▪ Change Order▪ Effective Date▪ Multiple COs▪ Effectivity Dates by CO

Date-effective parameters


ERP Baan5.0cIn ERP Baan5.0c, if you change the parameter in a Parameters session, the new values take effectimmediately when you save the data. The previous parameter values are lost.

If you want to restore the previous values, you must refer to your notes.

ERP LN 6.1In ERP LN 6.1, all Parameters sessions are date-effective.

Compared to ERP Baan5.0c, the following changes were made:

▪ ERP LN keeps a history of the parameter settings, so that you can display the previousparameter values.

▪ If you change the parameter values, you can enter the date and time at which the new valuesmust take effect.

Delete item data and structures


New in Infor ERP LN 6.1In ERP LN 6.1, you can delete standard configured items and their accompanying structures.


Common

The following check boxes were added to the Delete Item Data (tcibd0206m000) session:

▪ Delete items based on BOM StructureIf this check box is selected, not only items defined in the selection range are deleted but alsotheir BOM structures. You must use the Type of Deletion field to determine whether thestructure of standard items or configured standard items must be deleted.

▪ Type of DeletionIf the Delete items based on BOM Structure check box is selected, you must use this fieldto determine whether the BOM structure is deleted for standard items or only for configuredstandard items.This field can have the following values

▪ Standard Items/StructureThe BOM structure of standard items is deleted.

▪ Configured Standard Items/StructureThe BOM structure of configured standard items is deleted. That is, the structure of itemsconfigured on the basis of a generic item with order policyAnonymous. These configureditems are not linked to a PCS project.

Employees


ERP Baan5.0cIn ERP Baan5.0c, you defined all the employees' details in the Employees (tccom0101s000) session.

ERP LN 6.1In ERP LN 6.1, the new People package is used to register the employees' hours and expenses. Tosupport People, the Employees - General (tccom0101m000) session only contains the general employeedata.

From the Employees - General (tccom0101m000) session, you can start the following sessions to definethe more specific employee data:

▪ Employees - People (bpmdm0101m000).▪ Employees - Project (tppdm8101m000).▪ Employees - Service (tsmdm1140m000).▪ Skills by Employee (tcppl0120m000).▪ Employees by Team (tcppl0150m000).▪ Roles by Employee (tcppl0170m000).

After you define the employees, you can also start the listed sessions from the Employees Dashboard(bpmdm0101m100) session in People.


Common

Entity - entity relationships


ERP Baan5.0cIn ERP Baan5.0c, you could define a goods transfer relationship between the following entities:

▪ From a warehouse to a warehouse in the same logistic company

▪ From a work center to a work center in the same logistic company

▪ From a warehouse to a sales office in the same logistic company

▪ From a work center to a sales office in the same logistic company.

ERP LN 6.1The number of entity types between which you can define a goods transfer relationship was extended.

In ERP LN 6.1, you can define a goods transfer relationship between the following entities:

▪ From a warehouse to a warehouse in the same logistic company.

▪ From a work center to a work center in the same logistic company.

▪ From a warehouse to a sales office in the same logistic company.

▪ From a work center to a sales office in the same logistic company.

▪ From a purchase office to a sales office in the same logistic company.

▪ From a shipping office to a purchase office in the same logistic company.

▪ From a shipping office to a sales office in the same logistic company.

▪ From a shipping office to a warehouse in the same logistic company.

▪ From a shipping office to a shipping office in the same or a different logistic company.

▪ From a warehouse in one logistic company to a warehouse in another logistic company. Thismakes it possible to carry out intercompany warehouse orders.

In ERP LN 6.1, you can define a default relationship both for bilateral invoicing and for triangular invoicing.In the Goods Transfer (tcemm2150m000) session, select the Default check box.

Default currencyIn ERP Baan5.0c, in the Goods Transfer (tcemm2150m000) session, you can indirectly select the defaultcurrency for the invoices in the Take Default Currency from field, which can have the following values:

▪ From Enterprise Unit▪ To Enterprise Unit

In ERP LN 6.1, this field was replaced with theCurrency field in which you can select the default currencyfrom the currencies defined in the Currencies (tcmcs0102m000) session.


Common

Environmental compliance


Worldwide, various regulations exist to limit the use of hazardous chemical substances in electronicequipment preventing environmental pollution. Examples are the European directive RoHS (Restrictionof Hazardous Materials), and the Japanese regulation JPSSI.

Companies, in most cases producers of electronic equipment, are legally required to:

▪ Set up and control compliancy rules.

▪ Verify whether purchased, engineered, manufactured, and serviced material is compliant.

▪ Verify whether their work processes are compliant.

New in Infor ERP LN 6.1In ERP LN 6.1, you can link an external application to ERP LN that helps you to limit hazardous material.The following fields in ERP LN display whether a specific material or material is compliant to the rulesaccording to the external application that is linked to ERP LN:

▪ The Environmental Compliance field in the Items - General (tcibd0501m000) details session.▪ The Environmental Compliance Declared field in the Buy-from Business Partners

(tccom4520m000) session.

EU sales listing declaration


ERP Baan5.0cIn ERP Baan5.0c, you can generate the sales listing declaration as a printed report or as an ASCII file.ERP LN does not support automatic transfer to the collection office.

New in Infor ERP LN 6.1In ERP LN 6.1, in The Netherlands you can generate the sales listing declaration as an XML file andset up automatic transmission of the file.

The following changes were made:

▪ You can use the new Sales Listing Declaration Layout (tccom7101m000) session to defineor adapt the layout of the sales listing XML file or comma-separated (CSV) file.

▪ You can use the new Sales Listing Declaration Periods by Tax Period (tccom7103m000)session to define the periods for which you must submit the sales listing and to map the periodsto the tax periods defined for the financial company.

▪ In the Process Sales Listing (tccom7270m000) session, you can no longer generate a partialsales listing for ranges of invoice types, invoice numbers, invoice dates, and tax numbers. Ifyou generate the sales listing, ERP LN automatically retrieves all the relevant data from theperiods for which you generate the sales listing.


Common

▪ In the Process Sales Listing (tccom7270m000) session, if you generate the sales listing forthe preceding period, Infor ERP automatically marks the entries in that period as corrections.If you set up automatic transfer of the sales listing, ERP LN automatically starts the transferif you click Continue in the Process Sales Listing (tccom7270m000) session.

Grand total rounding


ERP Baan5.0cIn ERP Baan5.0c, calculated amounts are rounded according to the rounding factor defined for thecurrency in the Currencies (tcmcs0102m000) session.

For tax amounts, the resulting amount is then rounded according to the rounding method selected forthe tax code in the Tax Codes by Country (tcmcs0136s000) session.

ERP LN 6.1In some countries, the total amounts on legal documents that you send to your customers must berounded in a specific way. In ERP LN 6.1, grand total rounding supports this requirement.


▪ In the Implemented Software Components (tccom0100s000) session, you can select theGrand Total Rounding check box.

▪ In the Currencies (tcmcs0102m000) session, for each currency you can specify an additionalrounding factor for total amounts in the Grand Total Rounding Factor field.

If you use grand total rounding, ERP LN rounds the total amounts according to the grand total roundingfactor on such documents as quotations, contracts, and sales invoices.

Intrastat declaration


ERP Baan5.0cIn ERP Baan5.0c, the Intrastat implementation was rarely used because country-specific data was notprovided, or because the data could not be sent to the authorities in the required format. Localizedadd-on software was required to generate the Intrastat report correctly.

ERP LN 6.1ERP LN 6.1 offers a flexible Intrastat solution which you can set up to retrieve specific data and meetthe specific Intrastat declaration requirements of most European countries.

ERP LN does not generate the Intrastat declarations. The EU Intrastat declarations can be generatedand supplied to the Intrastat authorities by means of an external Intrastat application.


Common

For example, you can use the following Intrastat applications:

▪ IDEP▪ IDES (used in Germany)▪ IRIS (used in The Netherlands)▪ Excel (used in the UK)

Most Intrastat applications validate the data and give you an opportunity to correct the data. Infor ERPhelps you to set up the Intrastat declaration data in such a way that manual corrections afterwards areusually not required.

Use the various EU Intrastat sessions of the new Taxation module to do the following:

▪ Select various options for the collection of the the EU Intrastat transactions data from thevarious ERP LN packages

▪ Extend the data with the information required by the authorities in your country

▪ Perform manual corrections on the collected declaration data

▪ Export the collected data to a file that you can process with IDEP and other external packagesto generate the EU Intrastat declaration.

Lot control by serialized items


A serialized items is a physical occurrence of a standard item that is given a unique lifetime serial number.This enables tracking of the individual item throughout its lifetime, for example, through the design,production, testing, installation, and maintenance phases. A serialized item can consist of other serializedcomponents.

Examples of serialized items are cars (Vehicle Identification Number), airplanes (tail numbers), PCs,and other electronic equipment (serial numbers).

ERP Baan5.0cLot control is used to record and trace groups of items. In ERP Baan5.0c, you can use Lot by Unit inthe item data to identify a separate item as a lot. In this way, you can record and trace the item.

New in Infor ERP LN 6.1In ERP LN 6.1, the concept of serialized items is introduced.

Serialization is used in the following ERP LN packages:

▪ In Warehouse Management, to track and trace items in inventory, for inbound goodsmovements, and/or outbound goods movements.

▪ In Manufacturing, to identify manufactured items, and the components that are used in themanufactured items.

▪ In Service, to identify items and components for service and maintenance purposes.


Common

ERP LN uses a mask to generate serial numbers. A mask is a template that specifies the structure ofan identification code. The mask defines the total length of the identification code and the way the codeis divided into mask segments.

Use the new Masks (tcibd4102m000) session and its related sessions to define the masks.

In the COM Parameters (tccom0000s000) session, the following fields were added to select defaultmasks:

▪ Serialized Mask Code▪ Lot Mask Code

For more information, refer to Overview of serialized items.

Sales and use tax


This topic describes the localization functionality for sales and use tax that was added to the ERP LN6.1 standard software.

ERP LN 6.1

▪ Direct Pay permit registrationERP LN 6.1 can process purchase orders to which a direct pay permit applies. In the TaxExemptions for Purchasing (tcmcs1560m000) and the RegisterWarehouse for Tax Exemptions(tcmcs1561m000) sessions, you can select the new Direct Pay Indicator check box. Thisresults in direct pay processing changes in various packages and modules.

▪ Include tax amounts in order balance (optional)In ERP Baan5.0c, the order balance amount always includes the tax amount. Consequently,the tax amount must be recalculated every time an order line is modified in order to updatethe balance correctly. If the tax provider is activated, this requires an API call for everyre-calculation of tax, which can cause an unacceptable increase in response time.In ERP LN 6.1, you can select or clear the new Include Tax in Order Balance check box inthe COM Parameters (tccom0000s000) session to indicate whether you want to include taxamounts in the order balance amount. This parameter has an effect on various sessions inOrder Management.

▪ Print tax amounts on external documents (optional)In ERP Baan5.0c, the tax amounts are always printed on external documents. In ERP LN 6.1,you can set some parameters to indicate whether you want to print tax amounts on externaldocuments.

▪ Print tax amounts by tax authorityIf you wish, ERP LN 6.1 can print a breakdown of the tax amounts by tax authority on externaldocuments. If you use a tax provider, the tax amounts for each tax authority are reported bystate/province, country, and local jurisdictions. The tax authority summary reports displayseparate city tax amounts and district tax amounts.


Common

▪ Tax exemption certificatesIn ERP Baan5.0c, tax exemption processing is supported only on sales orders for non-taxprovider users. In ERP LN 6.1, tax exemption certificate processing is also performed forpurchase orders, and for sales orders if you use a tax provider.You can define tax-exemption certificates in the following sessions:▪ Tax Exemptions for Sales (tcmcs1142m000).

▪ Tax Exemptions for Purchasing (tcmcs1560m000).

▪ Register Warehouse for Tax Exemptions (tcmcs1561m000)..

Standard calendar

This topic describes how the standard calendar works.

Company calendar in ERP Baan5.0cIn ERP Baan5.0c, you could share a calendar from another company, by using Company of Std CalTemplate parameter in the CCP Parameters (tcccp0100s000) session.

Standard calendar in ERP LN 6.1In ERP LN 6.1, you can define a standard calendar in the new Standard Calendar (tcccp0140m000)session.

baan uses the standard calendar as a week template for each calendar. For each day of the week youcan define combinations of availability types and working hours types.

Table sharing


ERP Baan5.0cIn ERP Baan5.0c, the companies in a multicompany structure cannot share the following tables:

▪ Items - General (tcibd001)▪ Items - General Defaults (tcibd002)▪ Departments (tcmcs065)▪ Warehouses (tcmcs003)

To share the Employees table, the various Business Partners tables, and the item data tables, thecompanies must also share the referenced Departments table and Warehouses table.

If companies share the Departments table and/or theWarehouses table, the departments and warehousesof all the companies are visible in all the companies. However, for many actions the users cannot selecta department or warehouse in a company other than the current company. Therefore, in ERP Baan5.0c,companies cannot share entities that refer to departments or warehouses because they cannot sharethe Departments table and the Warehouses table.


Common

ERP LN 6.1In ERP LN 6.1, logistic companies of a multicompany structure can centrally store data referring todepartments and warehouses, such as:

▪ Central employee data▪ Central business partner data▪ Central item ordering data

The following changes enable companies (both logistic and financial) to share the Departments (tcmcs065)table and the Warehouses (tcmcs003) table:

▪ ERP LN checks whether the enterprise unit that is linked to a department or warehouse belongsto the current logistic company. If so, the department or warehouse can be used.

▪ A browse filter ensures that users who browse through the departments or warehouses, seeonly the departments or warehouses of the current logistic company. Users can select awarehouse from a different logistic company only on warehouse orders.

▪ For the handling of orders, quotations, and contracts that are linked to purchase offices, salesoffices, or service departments, ERP LN displays the department’s enterprise unit and printsthe enterprise unit on the report. In this way, you can see to which financial company ERP LNposts the order.

The following changes make it easier to share the general item data tables:

▪ The date-effective item types are stored separately in the table Date-Effective item Data(tcibd010) table. In this way, logistic companies can share the general item data tables andcontrol the item type, which can be Purchased or Manufactured, per logistic company. Fordetails, refer to Date-effective item data.

▪ The item warehouse was moved from the Items - General (tcibd001) table and the Items -General Defaults (tcibd002) table to the Item Ordering Data (tcibd200) table and the ItemOrdering Data (Defaults) (tcibd201) table. In this way, the item data can be shared and thewarehouse remains company-specific.

To set up the required table sharing in a mullticompany structure, you can use the new Table Sharingwizard. For details, refer to Table sharing

Taxation - general


ERP Baan5.0cIn ERP Baan5.0c, sessions for the setup and execution of tax registration and declaration were spreadover various modules of Common and Financials. In the menu tree, tax-related sessions were not easyto locate.


Common

ERP LN 6.1In ERP LN 6.1, the following changes were made to the setup of tax registration and tax declarations:

▪ Taxation menuIn the menu tree, all sessions for the setup and execution of tax registration and declarationwere collected into a new Taxation submenu.This submenu contains tax-related sessions from the following modules:▪ Common- Taxation (tctax)▪ Common- Tables (tcmcs)▪ Common- General Data (tccom)▪ Financials- General Ledger- Tax (tfgld)The Taxation (tctax) module is a newmodule in ERP LN 6.1. Most of the new taxation sessionsbelong to the Taxation module.

▪ Ledger accounts for tax amounts on advance payments and receiptsIn some countries, the following accounting rules apply:

▪ Tax on advance payments and receipts must be posted to the same account used for thetax posting when the invoice is created.

▪ When you assign advance payments or receipts to invoices, the contra posting for the taxamount must be posted to a separate account.

You can select the ledger accounts for tax amounts on advance payments and receipts in thefollowing new fields of the Posting Data for Singular Tax Codes (tfgld0171s000) and the PostingData for Multiple Tax Codes (tfgld0170s000) sessions:

▪ Purchase Tax on Assignment of Advance Payments▪ Sales Tax on Assignment of Advance Receipts

▪ Ledger accounts for tax amounts on credit notesIn ERP Baan5.0c, sales tax and purchase tax amounts on credit notes was always posted tothe sales tax account and the purchase tax account. In ERP LN 6.1, you can post the taxamounts on credit notes to separate accounts.In the Invoicing Methods (tcmcs0155s000) session, the Positive and Negative Order Linescheck box was added. To create separate sales invoices for credit notes, you can clear thischeck box. If you want to post the tax amounts on credit notes to ledger accounts other thanthe sales tax account, you must clear this check box.In the integration mapping scheme, the Credit Note indicator was added as amapping element.You can use the Credit Note indicator to map sales revenue on credit notes to a specificaccount.You can select the ledger accounts for tax amounts on credit notes in the following new fieldsof the Posting Data for Singular Tax Codes (tfgld0171s000) and the Posting Data for MultipleTax Codes (tfgld0170s000) sessions:▪ Purchase Tax on Credit Notes▪ Sales Tax on Credit Notes

▪ Stamp taxStamp tax is a type of tax that is imposed on trade notes. Stamp tax consists of a fixed amountinstead of a percentage. Depending on the country of your company, if you issue trade notesyou can be obliged to pay stamp tax on the trade note.


Common

You can select the ledger accounts for stamp tax amounts in the new Accrued Stamp Taxfield of the Posting Data for Singular Tax Codes (tfgld0171s000) and the Posting Data forMultiple Tax Codes (tfgld0170s000) sessions.For details, refer to Set up stamp tax.

▪ Tax articles printed on tax reportsFor some tax codes, you must print the section of the law related to the taxation on the taxreport or the tax declaration. To support his functionality, the tax articles are defined as reasoncodes.In the Tax Codes by Country (tcmcs0136s000) session, you can link the reason code of thetax article to a tax code by country combination.

▪ Tax calculation dateIn ERP LN 6.1, Iin the new Tax Calculation Date field of the Tax Codes by Country(tcmcs0136s000) session , you can define whether the tax rates and currency rates of theorder date or of the invoice date must be used for the tax calculations on sales invoices andpurchase invoices.

▪ Tax codesBefore Infor ERP can link a tax code to transactions, you must select the Approved checkbox in the Tax Codes by Country (tcmcs0136s000) session. If you have set up and tested atax code, you can approve the tax code. ERP LN performs a consistency check on the taxcode details.

▪ Transfer tax declarations automaticallyIn some countries the tax authorities require that you submit the tax declaration as an XMLfile. ERP LN supports the automatic transmission of the declaration XML file to a collectionoffice in The Netherlands. For details, refer to Automatic transfer of tax declarations.In The Netherlands, you can also generate and automatically transfer the sales listing as anXML file. For details, refer to Automatic transfer of the sales listing.

▪ Withholding income tax and social contributionsNew in Infor ERP LN 6.1Withholding tax is ERP LN 6.1 supports the calculation and declaration of withholding incometax and social contributions. For details, refer to Withholding tax and social contributions.You can select the ledger accounts for expensed withholding tax amounts in the new SocialContribution (Company Expense) field of the Posting Data for Singular Tax Codes(tfgld0171s000) and the Posting Data for Multiple Tax Codes (tfgld0170s000) sessions.

Note

If you do not want to use the ERP LN tax functionality, you must perform the steps described in Todeactivate the tax functionality.

Tax provider



Common

ERP LN 6.1

▪ API Parameters (tcapi1136s000)In ERP LN 6.1, the application programming interface (API) can only be used for tax providers.It is no longer required to select the type of application for which the API type is used. Therefore,the API Parameters (tcapi1136s000) session was removed. The tax provider-related fields ofthe API Parameters (tcapi1136s000) session were moved to the Tax Provider Parameters(tccom6150s000) session.

▪ Tax provider interface enhancementsThe tax provider interface was upgraded to support:

▪ Tax exemption information on sales transactions.

▪ Tax exemption information on purchase transactions.▪ Vertex’s Q Series

Terminology changes in the Central Calendar Management (CCP) module

TerminologyThe following table shows some changes in terminology:

DefinitionERP LN 6.1ERP Baan5.0c

A part of a day, for example, Monday morningor Wednesday afternoon. For each working

Working hours typeTime interval type

hours type, you can define a default start timeand end time.

Recurring exceptions for a calendar, used tomodel daily, weekly, monthly, or yearly recurringavailable or non-available time.

Calendar RecurrenceCalendar Pattern

Working hour types linked to a calendar recur-rence to make the calendar more specific.

Calendar RecurrenceWorking Hours

Calendar Pattern Time In-tervals

Time zones

This topic describes several changes related to time zones.

Time zones linked to addressesIn ERP Baan5.0c, the system retrieves a resource's time zone as follows:

▪ A calendar code is linked to the resource.

▪ A time zone is linked to a resource's calendar in the Calendar Codes (tcccp0510m000) session.


Common

As a result, in ERP Baan5.0c, resources in different time zones cannot share a calendar.

In ERP LN 6.1, the ERP LN retrieves a resource's time zone as follows:

▪ A department with an address is defined for the resource in the Departments (tcmcs0565m000)session.

▪ A time zone is linked to the address.

▪ If the address' time zone has not been defined, ERP LN uses the time zone of the state/provinceor the country.

Time zone of a financial companyIn ERP LN 6.1, a financial company has a time zone. As a result, ERP LN stores the transactions in thecorrect period, based on the time zone of the financial company.

If you define currency rates and tax codes in a logistic company, ERP LN converts that information tothe financial company's local time.

Maintain periods in other time zonesIn ERP Baan5.0c, you could view and maintain calendars only within your own time zone.

In ERP LN 6.1, you can define periods for other time zones.

For example, if your financial company has a time zone that differs from your logistic company, you canstill define the periods for that financial company.

Unit Effectivity (UEF)


Unit effectivity is a method to control the validity of variations on an end item. You can use unit effectivityfor pegging purposes, or to model exceptions from a standard end item so that you can make variationswithout having to define separate item codes. As a result, you do not need to maintain separate BOMsfor every combination of variations. End items can be, for example, airplanes or touring cars.

The deviations consist of relatively small variations of the end item. For example, fitting red seats insteadof blue ones, or a special type of radar or air-conditioning, in an otherwise standard type of airplane.

You can use unit effectivity to apply changes if:

▪ Few changes are made.

▪ The changes apply to relatively small subsets of the end item.

▪ The changes result from customer requests, engineering, or production.


Common

Use of unit effectivityYou can use unit effectivity in the following three ways:

▪ To configure effectivity unitsUse effectivity units to define exceptions for an item’s series, or series’ subset. You can usethis approach in low-volume production of complex products, for example, in aerospace anddefence industries. Series are defined for a specific end item, for example, for an airplane.Exceptions are then defined, for example, for numbers 50-100 of an item’s series. For anexample of this approach, refer to To configure effectivity units.

▪ As a lean configurator in Sales ControlUse effectivity units to configure items on individual sales order lines. You can use this approachin high-volume industries, such as electronics industries. Unit effectivity is then used as ‘leanconfigurator’. For an example of this approach, refer to Unit effectivity as a lean configuratorin Sales Control.

▪ For peggingIf an effectivity unit is specified for the item on a sales quotation line, a sales order line, or asales contract line, Enterprise Planning provides Manufacturing, Purchasing (in OrderManagement), and Warehouse Management with that effectivity unit. In this way, you cantrace the specific unit effective item through the production process.

Withholding tax and social contributions


New in Infor ERP LN 6.1In many countries, in specific situations, companies are legally required to retain payable income taxand/or social contribution from the payments of purchase invoices, and pay the amount directly to thetax collector’s office. Depending on local rules, the payment is due either when the invoice is paid, orperiodically. Companies must periodically submit a report to declare the amount of withheld and paidtax and social contribution.

As a result, various kinds of tax can apply to an invoice. Separate tax codes are required to calculatethe amounts of withholding income tax and social contributions, and to register the tax amounts of theinvoice in the tax analysis. To link multiple tax codes to a transaction, you can use group tax codes.

A group tax code is a tax code that represents multiple individual tax codes. If more than one tax codeapplies to a transaction, you can link a group tax code to the transaction.

For example, a group tax code can contain tax codes for:

▪ Value added tax▪ Withholding income tax▪ Withholding social contribution


Common

Modules

Central Calendar Management (CCP) module - Differences B50c/ERP61

This topic summarizes the differences between the Central Calendar Management module in ERPBaan5.0c and in ERP LN 6.1 and describes the differences that are not already discussed in otherdifferences topics.

New and changed functionality

▪ Parent calendarsIn ERP Baan5.0c, you could derive a calendar from multiple parent calendars. For eachavailability type, you could specify a parent.In ERP LN 6.1, a calendar has at most one parent calendar. You define a parent calendar inthe Parent Calendar field in the Calendars (tcccp0110m000) session.

▪ Monthly and yearly patternsIn ERP Baan5.0c, you could define weekly recurrent patterns. You could not define monthlyor yearly patterns.In ERP LN 6.1, you can define weekly, monthly, and yearly patterns. For example, you candefine a recurrent national holiday.

▪ Blank availability typeIn ERP Baan5.0c, you could define a blank availability type. This availability type was usedfor ERP Baan5.0c packages in which you could not specify which availability type to use.In ERP LN 6.1, you cannot use blank availability types anymore.

▪ Unavailable daysIn ERP Baan5.0c, you could specify exceptions only on day level. In other words, to definean exception for a day for one availability type, you had to also enter the calendar line datafor the unchanged availability types for that day.In ERP LN 6.1, you are no longer required to define a special availability type that indicatesthat a resource is not available. You can use the new Calendar Non-Available Days(tcccp0119m000) session. You can still specify the availability or nonavailability of an availabilitytype per calendar line in the Calendar Working Hours (tcccp0120m000) session.

▪ Unavailable availability typesIn ERP Baan5.0c, calendar lines were either available, or unavailable.In ERP LN 6.1, calendars inherit details from the parent calendar on availability type level. Todetermine whether an availability type is available or not available for a resource, you canselect or clear the Available check box in the following places:▪ On the availability type (the default setting).▪ On the standard calendar.▪ On the calendar time intervals.▪ On the calendar pattern time intervals.


Common

▪ Fields removed from Availability Types (tcccp0101m000) sessionIn ERP LN 6.1, the following fields were removed from the Availability Types (tcccp0101m000)session:▪ Plan Time Unit▪ No. of Hrs/Day▪ Day PercentageThese fields were intended for functionality that was not fully implemented or functionalityprovided by external scheduling packages that carry out planning based on exact time.

▪ Calendar navigationIn ERP LN 6.1, you canmuch easier navigate from period to period by using the new navigationicons in the Calendar Working Hours (tcccp0120m000) session and related sessions.With these icons you can perform the following actions:

▪ You can set the Period field to a day, week, month, or year.▪ Jump to the next or previous period.▪ Jump to the current date.▪ Jump to a specific date.

▪ Actual calendar removedIn ERP LN 6.1, the following sessions are no longer necessary and have been removed:▪ Update Actual Calendar (tcccp0230m000)▪ Display Actual Calendar (tcccp0530m000)In ERP LN 6.1, the capacity data for a specific combination of calendar and availability typeis displayed in the CalendarWorking Hours (tcccp0120m000) session, underCapacity Details.

▪ Update First Day of the Week (tcccp0224m000) session removedIn ERP Baan5.0c, you used the Update First Day of the Week (tcccp0224m000) session toupdate the calendar data after you change the First Day of the Week field in the Companies(ttaad1100m000) session.In ERP LN 6.1, this session was removed, because ERP LN 6.1 updates calendar dataautomatically after you change the first day of the week for your company.

▪ Update efficiency factor and capacity percentageThe terms efficiency factor and capacity percentage are defined as follows:

▪ efficiency factorA variable that baan uses to take into account differences in the daily availability of aresource when, for example, working overtime, hiring extra man craft, or working in differentshifts. Efficiency factors impact on lead-time calculation in baan Enterprise Planning.

▪ capacity percentageThe maximum utilization percentage of a resource indicating the capability to produceoutput per time period.

In ERP LN 6.1, the new Update Efficiency Factor and Capacity (tcccp0225m000) session isavailable. You can use this session to define a new value for the efficiency factor and thecapacity percentage, and update the calendar working hours accordingly for the involvedcalendar in the Calendar Working Hours (tcccp0120m000) session.


Common

▪ Calendar calculations after an actual calendar's end dateIn ERP Baan5.0c, the base-capacity definition of 24 hours per day and 7 days a week wasused to plan dates beyond the actual calendar.In ERP LN 6.1, if the actual calendar is expired, ERP LN looks for a date in a higher levelcalendar by following the calendar’s derivation path up to the standard calendar.

Enterprise Modeling Management (EMM) module - Differences B50c/ERP61

This topic summarizes the differences between the Enterprise Modeling Management module in ERPBaan5.0c and in ERP LN 6.1 and describes the differences that are not already discussed in otherDifferences topics.


▪ Entity - entity relationshipsThe number of entity types between which you can define a goods transfer relationship wasextended. In addition, you can define a default relationship both for bilateral invoicing and fortriangular invoicing. For details, refer to Entity - entity relationships (p. 24)

▪ Parameter wizardIn ERP LN 6.1, you can use the new parameter wizard to set up the specific localizedfunctionality required for your company. For more information, refer to Parameter wizard (p. 73).

▪ Euro currencyIn the Euro Currency field of the Companies (tcemm1170m000) session, you can select thecurrency code you use for euros. ERP LN uses the Euro currency in several processes in theCash Management module.

Financial Integrations (FIN) module - Differences B50c/ERP61

This topic summarizes the differences between the Financial integrations modules in ERP Baan5.0cand in ERP LN 6.1 and describes the differences that are not already discussed in other Differencestopics.

ERP LN 6.1To support the new integration mapping scheme and financial reconciliation in ERP LN 6.1, the followingchanges were made to the Financial integrations module:

▪ Because all reconciliation functionality is provided in the General Ledger module, the sessionsfor the reconciliation of WIP, projects (TP), service order data, and inventory were removed.

▪ To support the new integration mapping scheme and reconciliation functionality, The followingnew sessions and their related subsessions and Print sessions were added:

▪ Initialize Mapping Scheme Data (tcfin0210m000)

▪ Integration Document Type by Transaction Origin/Financial Transaction (tcfin0110m000)▪ Reconciliation Groups (tcfin0120m000)


Common

▪ Reconciliation Elements (tcfin0130m000)For details, refer to Integration mapping scheme (p. 61) in Financials.

General Data (COM) module - Differences B50c/ERP61

This topic summarizes the differences between the General Data modules in ERP Baan5.0c and in ERPLN 6.1 and describes the differences that are not already discussed in other Differences topics.

ERP LN 6.1To support new functionality in various ERP LN packages, the following sessions were added or changed:

▪ City codesIn ERP Baan5.0c, cities are only identified by their city names, for example, in the followingsessions:▪ Addresses (tccom4130s000)▪ Distance Table by City (tccom4537m000)In ERP LN 6.1, cities are identified by a city code. ERP LN uses the city codes in the Distancesbetween Cities (tccom137) table.Use the new Cities by Country (tccom4539m000) session to specify the cities in each country,and optionally in the state or province. ERP LN uses this information in the Distance Table byCity (tccom4537m000) session.

Item Base Data (IBD) module - Differences B50c/ERP61

This topic summarizes the differences between the Item Base Data modules in ERP Baan5.0c and inERP LN 6.1 and describes the differences that are not already discussed in other Differences topics.

ERP LN 6.1


▪ Alternative manufacturersIn ERP Baan5.0c, manufacturers were only used as item grouping data. You could select onemanufacturer for an item.In ERP Baan5.0c, you can specify a number of manufacturers for an item, and ensure thatyou only receive items from approved manufacturers.In ERP LN 6.1, you can specify a number of manufacturers for an item, and ensure that youonly receive items from approved manufacturers. For details, refer to Alternative manufacturers(p. 19) .

▪ Configured items without PCSIn ERP Baan5.0c, configured products were handled as customized items to which a PCSproject must be linked.


Common

In ERP LN 6.1, you can configure an item in the Product Configuration (PCF) module ofManufacturing without using a PCS project. You can define generic items with the order policyAnonymous. For details, refer to How to define a product model.

▪ Copy item dataIf you use the Copy Item Data (tcibd0205m000) session to copy an item to another item, errormessages appear when errors occur while you copy the item’s sub-entities. In ERP Baan5.0c,the copy process cannot continue and you must you solve the problem in the original item.You must then restart the copy process.In ERP LN 6.1, if an error occurs, the copy process continues. The error messages appear ina separate window. After the copy process completes, you can solve the problems.

▪ Date-Effective Item typeIn ERP Baan5.0c, you could not change the item type. If you wanted to purchase an item oftheManufactured item type, you had to define another item with the same specifications andof the Purchased item type.In ERP LN 6.1, you can enter an effective date and an expiry date for the item sourcing typesPurchased andManufactured. As a result, these attributes apply during the specified periodof time.For details, refer to Date effective item type (p. 21) .

▪ Delete item data and structuresIn ERP LN 6.1, you can delete standard configured items and their accompanying structures.For details, refer to Delete item data and structures (p. 22) .

▪ Item costing dataIn ERP LN 6.1, the item costing data were moved from the Item Base Data module in Commonto the Cost Price Calculation module in Manufacturing.The related session codes were changed as follows:

▪ Item Costing Data (tcibd0107s000) changed to Item Costing Data (ticpr0107m000)

▪ Item Costing Data (Defaults) (tcibd0108s000) changed to Item Costing Data (Defaults)(ticpr0108m000)

▪ Item Ordering DataThe following changes were made to the Item - Ordering (tcibd2100s000) and Item - OrderingDefaults (tcibd2101s000) sessions. In these sessions, you can:

▪ Enter the item warehouse or default warehouse.

▪ If the item order system is Planned, you can select or clear theCritical in Planning checkbox. If this check box is selected, this plan item is critical in the master planning. Thismeans that in the master-planning process in Enterprise Planning, the item is treated asa critical component.

▪ Lot control by serialized itemsIn ERP LN 6.1, you can perform lot control by using serialized items. A serialized item is aphysical occurrence of a standard item that is given a unique lifetime serial number. Thisenables tracking of the individual item throughout its lifetime, for example, through the design,production, testing, installation, and maintenance phases. A serialized item can consist ofother serialized components.


Common

For details, refer to Lot control by serialized items (p. 27)

▪ MasksERP LN uses a mask to generate serial numbers. A mask is a template that specifies thestructure of an identification code. The mask defines the total length of the identification codeand the way the code is divided into mask segments.Use the new Masks (tcibd4102m000) session and its related sessions to define the masks.

▪ Mass change of item assignmentsuse.session.to define or change assignments for a large number of items at once. For example,you can reassign a range of items from buyer Clarke to buyer Frydman, or you can assign allthe items that are not assigned to a buyer to buyer Frydman.For ranges of item groups and items you can change the following assignments:▪ The buyer.▪ The planner.▪ The shop floor panner.▪ The routing group.

▪ Share the item data tablesIn ERP Baan5.0c, companies cannot share the Items - General (tcibd001) table and theGeneral Items - General Defaults (tcibd002) table because these tables contained the itemwarehouse, which is company-specific data.To make it possible that companies share the Items - General (tcibd001) table and the GeneralItems - General Defaults (tcibd002) tables, in ERP LN 6.1, the warehouse was moved fromthe item data to the item ordering data.For more deatils, refer to Table sharing (p. 29) .

Tables (MCS) module - Differences B50c/ERP61

This topic summarizes the differences between the Tables modules in ERP Baan5.0c and in ERP LN6.1 and describes the differences that are not already discussed in other Differences topics.

ERP LN 6.1To support new functionality in various ERP LN packages, the following sessions were added or changed:

▪ Freight service levelsIn the new Freight Service Levels (tcmcs0175m000) session, you can define freight servicelevels which are used in the new Freight Management package. A freight service level is anentity that expresses the duration of transportation, such as: delivery within twelve hours.For more details, refer to Freight Management integration (p. 58) .

▪ Sales types and purchase typesSales types and purchase types are a sales order or purchase order property that allows youto identify the kind of sale or pruchase made and the kind of receivable or payable. Thisproperty is used to post the amounts to the correct control accounts.


Common

To support multiple control accounts in Accounts Payable and Accounts Receivable, you candefine sales types and purchase types and exceptions fro each type in the following newsessions:▪ Purchase Types (tcmcs2101m000)▪ Sales Types (tcmcs2102m000)▪ Purchase Type Exceptions (tcmcs2103m000)▪ Sales Type Exceptions (tcmcs2104m000)For details, refer to Multiple control accounts (p. 71) .

▪ Time zonesIn ERP LN 6.1, a new Time Zone field was added to the following sessions:▪ Countries (tcmcs0110s000)▪ States/Provinces (tcmcs1143m000)In these fields you can enter the default time zone for all resources with an address in thiscountry or state or province. If you do not enter a default time zone for the country or in theStates/Provinces (tcmcs1143m000) session, you must enter the time zone for every address.For details, refer to To use time zones.

▪ ZIP codes and postal codes maskIn ERP LN 6.1, , you can define the number of positions and the type of characters of the ZIPcodes or postal codes in the country. In the new ZIP/Postal Code Mask field of the Countries(tcmcs0110s000) session, you can enter the ZIP code mask. For example, for postal codessuch as 6715 GV, you must enter the following mask: 9999 ZZ. For postal codes such as671F 20, the mask can be: 999Z 99 or 99XX 99.For details, refer to ZIP code/postal code mask


Common

Hours Accounting - Differences by ERP LN 6.1 topic

This topic explains how hours accounting functionality present in ERP Baan5.0c is implemented in thenew People package in ERP LN 6.1.

People was created to replace the hours-accounting functionality in the various packages with onecentral hours-accounting package.

People helps avoid duplication, redundancies of functionality, and over-registering, or over-budgeting,of hours. To achieve user-friendliness, ERP LN 6.1 enables easy maintenance of hours, and facilitatesthe following actions:

▪ Use of assignments (p. 46) input as a starting point for hours accounting.▪ Easy access to all employee-related data (p. 45)▪ Fast data-entry in hours accounting sessions (p. 46)

▪ Automatic registration of hours through:▪ Backflushing▪ Direct Time Recording

▪ Automatic overtime calculation

▪ Global registration of hours for employees or their teams

Centralized hours accounting

In ERP Baan5.0c, hours accounting is performed in the hours accounting sessions of the variouspackages:

▪ In Manufacturing, in the Hours Accounting (HRA) module.▪ In Project, in the Hours Accounting (HRS) module.▪ In Service, in the Service Order Control (SOC) module.

In ERP LN 6.1, all hours accounting is performed in the Time Management (TMM) module of People.

Most employee-related data are now stored in the Master Data Management (MDM) module of People.

An employee’s budgeted hours will now be registered centrally. You can now globally update employeehours, and globally approve/undo registered hours.


2Chapter 2People

Hours budgeting

You can enter budgets by employee, by team, and by department. This enables you to compare thebudgeted hours with the actual hours entered by employees.

After processing, you can:

▪ View the actual hours alongside the budgeted hours in the Budget by Employee(bptmm3100m000) session.

▪ Update employees' budgets by using the new Update Budget by Employee with Actual Hours(bptmm3201m000) session.

Hours approval and processing

The registered hours in People are related to the respective packages for control, progress, and trackingof tasks and activities. After the hours are registered, (optionally) approved, and processed, the detailsare sent to the respective packages.

Note

In the People Parameters (bpmdm0100m000) session, on the Process Labor Costs/Expenses tab,you can set processing options for hours registered for any of the following:

▪ General Task▪ Project▪ Manufacturing▪ Field Service▪ Depot Repair

Related data

With the creation of the employee data in People, all other related attributes and functionality that waspreviously (that is, prior to ERP LN 6.1) moved to a separate module in Common Data, is now availablefrom within the People package.

Supporting details, together with employee information, that are also maintained in the Master DataManagement module, including the following:

▪ Teams▪ Roles▪ Skills

▪ Labor types(Previously hourly labor types in Manufacturing, hourly-wage types in Project.)

▪ Labor rates(Previously wage rates in Project.)

▪ Working time schedules(Previously working time tables in Manufacturing.)


People

Note

In addition to the employee's labor rate, you can also create and maintain customer-specific and/orproject-specific labor rates, using the new Labor Rates by Business Partner and Project (tcppl0192m000)session.

Enhanced usability

ERP LN 6.1 People includes various usability enhancements.

For more information, refer to Usability enhancements for People in ERP LN 6.1 (p. 45)

Usability enhancements for People in ERP LN 6.1

This topic describes the usability enhancements in ERP LN 6.1 People.

Easy access to all employee-related data

The Employees Dashboard (bpmdm0101m100) session provides employee administrators with easyaccess to all employee-related data from a single window.

Single point of access to hours and expenses sessions

In the ERP LN 6.1 menu, the new Hours and Expenses (bptmm1800m000) menu entry provides a singlepoint of access to the following sessions:

▪ General Hours (bptmm1111m200)▪ Project Hours (bptmm1111m000)▪ PCS Project Hours (bptmm1170m000)▪ Production Order Hours (bptmm1120m000)▪ Assembly Hours (bptmm1160m000)▪ Service Order Hours (bptmm1130m000)▪ Work Order Hours (bptmm1140m000)▪ General Expenses (bptmm1111m300)▪ Project Expenses (bptmm1111m100)

Similarly, the new Hours and Expenses History (bptmm2800m000) menu entry provides a single pointof access to the corresponding history sessions.

To switch easily between any of the hours and expenses sessions, you can use the shortcuts or newlydesigned toolbar buttons.

New toolbar buttons in Project Hours (bptmm1111m000) session


People

Note

You can set a default startup session in the new User Profiles (bpmdm0102m000) session.

Fast data-entry in hours accounting sessions

A number of sessions have been redesigned to enable users to enter all data without having to accessa details session. This fast data-entry is made possible in the following sessions:

▪ PCS Project Hours (bptmm1170m000)▪ Production Order Hours (bptmm1120m000)▪ Assembly Hours (bptmm1160m000)▪ Service Order Hours (bptmm1130m000)▪ Work Order Hours (bptmm1140m000)

All history sessions have been redesigned in the same manner.

Note

In addition to the general session redesign, sessions' views have been redesigned as well.

User profiles

The User Profiles (bpmdm0102m000) session enables users to specify general startup defaults, as wellas various session-specific settings.

Assignments

The Assignments (bpmdm0130m000) session contains preset tasks used for hours accounting with astart date, end date (optional), and a calculated default of hours. These tasks can be assigned by asupervisor or planning manager, or by the actual employee. The assigned employee must accept oredit the hours after the employee retrieves the assignments in the hours-accounting session.

You can set the assignments' recurrence pattern toDaily,Weekly,Monthly, or Yearly, and then specifyfurther recurrence data in the Recurrence (bpmdm0131m000) session.

The specific menu in the Assignments (bpmdm0130m000) session enables you to access the followingsessions:

▪ Use Assignments (bptmm1204m000)▪ Copy Assignments (bpmdm0235m000)▪ Delete Hours and Expenses (bptmm1206m000)

Improved employee selection

In sessions in which you can enter a range of employees, you can speed up data entry by clicking Spec.Employees, which will select all (active) employees in the Specific Employees (bpmdm1140m000)session. In this session, you can: create a list of employees you want to use in a process. The employeesindicated will be stored by your logon code.


People

On the specific menu of the Specific Employees (bpmdm1140m000) session, you can click ImportEmployees to start the Import Specific Employees (bpmdm1240m000) session, which enables you toeasily add employees from one or more teams to the list of specific employees.

Update actual hours for other period table codes

Whereas previously actual hours were updated only for the default period-table code, the new UpdateBudget by Employee with Actual Hours (bptmm3201m000) session enables you to update actual hoursalso for any other period table codes that you use for budgeting purposes.

Registration and approval authorizations

If, in the People Parameters (bpmdm0100m000) session, the Use Registration Authorization checkbox and/or Use Approval Authorization check box are selected, you can specify and maintain usersthat are authorized to register and/or approve other employees’ hours/expenses. To this purpose, twosessions are added:

▪ Registration Authorizations (bpmdm0110m000)▪ Approval Authorizations (bpmdm0111m000)

Note

The Approval Authorizations (bpmdm0111m000) session can only be used for Project hours/expenses.

Posting to Financials

In the General Tasks (bpmdm0150m000) and the General Expense Codes (bpmdm0155m000) sessions,a check box enables users to indicate whether or not costs must be posted to Financials.

Miscellaneous new sessions

▪ Budget by Team (bptmm3120m000)

▪ Capacity Flows between Departments (bptmm2525m000)▪ Delete Hours and Expenses (bptmm1206m000)

▪ Print Hours and Expenses (Completeness Check) (bptmm1410m000)

▪ Labor Rates by Business Partner and Project (tcppl0192m000)

▪ Copy Labor Rates to Business Partner and Project (tcppl0292m000)▪ Rate Simulator (tcppl0292m100)▪ Set Labor Rate Code Final (tcppl0292m200)


People


People


Automatic direct debit procedure


ERP Baan5.0cIn ERP Baan5.0c, the direct debit procedure requires frequent user interaction, whereas payments areprocessed automatically. In a business situation, processing a large volume of direct debits becomesvery time consuming.

ERP LN 6.1In ERP LN 6.1, direct debits can be processed automatically, without user interaction, in the same wayas payments are processed automatically. The transactions that cannot be processed correctly aremoved to a separate batch. After the direct debit run has finished, you can solve the problems and thenprocess this batch.

You can supply default values for the automatic direct debit process in the following sessions:

▪ Automatic Process Defaults (tfcmg1190m000).

▪ Automatic Process Defaults by Bank/Payment-Receipt Method (tfcmg1191m000).

Bank charges


New in Infor ERP LN 6.1Bank charges are the costs a bank charges to process the transactions. The bank charges can dependon the type of transfer, for example, whether the transfer is between different banks or between branchesof the same bank. In addition, the bank charges can vary for different ranges of transaction amounts.

In ERP LN 6.1, you can define the bank charges of individual bank branches and you can indicatewhether you or your pay-to business partner pays the bank charges.


3Chapter 3Financials

To view the tax amounts on the bank charges by bank branch, you can define the bank branch as abusiness partner. In the Tax Analysis (tfgld1520m000) session, you can print the tax analysis by pay-tobusiness partner report.

Bank master data


ERP Baan5.0cIn ERP Baan5.0c, bank data could be defined in Baan Common and in Baan Finance, among othersin the following sessions:

▪ Banks by Pay-by Business Partner (tccom4115s000).

▪ Banks by Pay-to Business Partner (tccom4125s000).▪ Banks by Factoring Company (tcmcs0126m000).▪ Maintain Bank Relations (tfcmg0110m000).

▪ One-Time Business Partner Addresses (tfacr1102s000).▪ One-Time Supplier Addresses (tfacp1102m000)

ERP LN 6.1In ERP LN 6.1, the bank master data is defined centrally, which is more efficient and avoids duplicationand redundancy of the data.

The bank are defined in the new Bank Branches (tfcmg0511m000) session in the Cash Managementmodule. In other sessions in which you must select a bank, for example, for a business partner or for afactoring company, baan zooms to this session.

In ERP Baan5.0c, the type of bank account number check you selected in the COM Parameters(tccom0000s000) session applied to the whole company. In ERP LN 6.1, you can specify the type ofbank account number check separately for each country in the Countries (tcmcs0110s000) session.

As the SWIFT code is one of the bank identifier codes used for international payments, in ERP LN 6.1the term SWIFT Code is replaced with the more generic term International Bank ID.

Belgian localizations


This topic describes the Belgian localization functionality that was added to the ERP LN 6.1 standardsoftware.

Belgian financial requirements in ERP LN 6.1

▪ Bank files for foreign payments and domestic paymentsThe Belgian Bankers’ Association has developed specific banking standards for the electronicinterchange of payment orders/credit advices between financial institutions and customers.


Financials

ERP LN 6.1 supports the special Belgian bank file formats for domestic payments in euro(EUR), and for foreign payments in any currency.The following new and changed sessions support the Belgian bank files:

▪ You can define the Belgian Financial Institutions in the new Financial Institutions (Belgium)(tfcmg0109m000) session.

▪ You can then select the related Financial Institution for each bank in the Bank Relations(tfcmg0510m000) session.

▪ In the Payment/Receipt Method (tfcmg0140s000) session, you can select the variousBelgian reports in the Payment Report and the Additional Report fields of thePayment/Receipt Method (tfcmg0140s000) session.

▪ Balance of Payments reportingCompanies in Belgium and Luxembourg are obliged to declare their financial transactions(payments) with foreign countries. The banks usually declare the payments, but the companymust declare the open entries. The declaration is made on a provided form. The statementcontains a list with information about the total amounts of debt and assets because of foreignsales and purchases.In ERP LN 6.1, the EU-reporting functionality has been adjusted to meet the Belgium Balanceof Payment reporting requirement.The Belgium Balance of Payment report was previously called the BLWI declaration.The following new and changed sessions support the Balance of Payment reporting :

▪ In Common Data:▪ Country Groups (tcmcs1180m000)

▪ In the Countries (tcmcs0110s000) session, the new Belgian BoP field.

▪ In the Currencies (tcmcs0102m000) session, the new Belgian BoP Currency field.In Financials:

▪ Print Belgian Balance of Payments (tfcmg3407m000).

▪ Process Belgian Balance of Payments (tfcmg3207m000)

▪ Belgian Balance of Payments Invoice Data (tfcmg3507m000).▪ Print NBB Invoice Data (tfcmg3406m000).

▪ Print Belgian Balance of Payments (tfcmg3407m000)..

For more information, refer to To set up the Belgian Balance of Payments report data.

▪ Intracom reportingEvery tax payer that applies tax exemption to intra EU (European Union) deliveries must reportthe buyer of such transactions to the tax authorities with the Intracom declaration. The conditionsfor EU reporting are described in the Belgian law.In ERP LN 6.1, the following new and changed sessions support the Intracom reporting:

▪ In the Business Partners (tccom4100s000) session, the I-Code field.▪ In the Sales Listing (tccom7170s000) session, the new I-Code field and the Address

Code field.▪ The various Intracom report types were added to the Print Sales Listing (tccom7470m000)

session.


Financials

▪ VAT reportThe VAT reporting in Belgium requires an alternative means of presenting the tax amounts.In ERP LN 6.1, you can generate the VAT reports according to the Belgian requirements. Theuse of tax country groups facilitates the setup of the relations by tax position. The tax countrygroups can be used for tax reporting and for the tax journal.In ERP LN 6.1, the following new and changed sessions support the Belgian VAT reporting:▪ Country Groups (tcmcs1180m000).

▪ In the Countries (tcmcs0110s000) session, the new Tax field.▪ Relations by Tax Position (tfgld0121s000).

▪ Print Tax Report by Tax Position (tfgld1421m000).

▪ Print Tax Report by Tax Position / Country Group (tfgld1423m000).

▪ Print Journal Report - Belgium (tfgld1442m000).

▪ In the Print Tax Analysis (tfgld1420m000) session, the Tax Journal report was added.

▪ In the Print Yearly Tax Report (Business Partners) (tfgld1432m000) session, the reportsrequired for Belgian VAT reporting were added.

▪ Tax journalIn ERP LN 6.1, the Trial balance (fiscal period) and the Trial balance (reporting period) reportswhich are required for Belgian VAT reporting were added in the following sessions:▪ Print Trial Balance (tfgld3402m000).

▪ Print Extended Trial Balance (tfgld3411m000).

▪ Accon interfaceIn ERP LN 6.1, you can create ASCII files that can be processed by the Accon application.Accon is a third party application that you can use to report the annual balances to the NationalBank of Belgium. You can use the new Create Accon Interface File (tfgld5210m000) sessionto generate an Accon report file.

Cash application


ERP Baan5.0cThe cash that you receive from a pay-by business partner through a bank statement can cover multipleopen sales invoices. The customer sends you a remittance advice note with details of the invoices paidand the amounts paid towards each invoice. In previous Infor ERP, you must post the received amountto an Unallocated Payments ledger account and then apply the received cash amount to the salesinvoices line by line.

Cash application is a high volume process. You want to enter data at high speed and with few errors.

However, in ERP Baan5.0c, each time you enter data, ERP LN verifies the data, which slows down theprocess. In addition, you must repeatedly look at the computer screen to ensure the validity of data,whereas it is more convenient to make the necessary corrections afterwards.


Financials

ERP LN 6.1In ERP LN 6.1, the process of applying the cash to the open sales invoices was improved and speededup considerably. The new Remittance Advice (tfcmg2150m000) session was added to handle multilineremittance-advice data entry. You can manually enter the data, and the assignments are confirmedthrough bank transactions.

ERP LN does not perform consistency checks at data entry, but validates the data when you finishentering the data. In addition, you can set up cash application parameters to handle short paymentsand over payments easily and immediately.

The business-partner-payment document number was added to the customer receipt data. This allowsyou to retrieve and apply receipts by customer-payment document number and to use the customerpayment document number for inquiries on open entries.

Note

The cash application solution is limited to manual entry of the remittance advice. Infor ERP does notsupport the processing of remittance advice received through EDI or other media.

Cash flow statements


New in Infor ERP LN 6.1The cash flow statement is an indication of the kind of cash transaction. Transactions to which you linka reason code of the Cash Flow type are included in the cash flow statement, sorted by cash flowreason.

The cash flow reason is an indication of the kind of cash transaction. Transactions to which you link areason code of the Cash Flow type are included in the cash flow statement, sorted by cash flow reason.

In Japan, according to the Securities and Exchange law, companies are obliged to submit a consolidatedcash flow statement periodically.

In ERP LN 6.1, you can use a cash flow reason to mark transactions that contribute to the cash flow.

In the new Cash Flow History (tfgld2519m000) session, you can view the transactions that contributeto the cash flow and from this session, you can start printing the report.

For details, refer to Cash flow statement.

Consumption tax


New in Infor ERP LN 6.1In Japan, value added tax is called 'consumption tax'. For consumption tax, the tax amounts are roundeddown. In addition, it is important that the tax amount on return sales orders equals the tax amount onthe sales invoice line.


Financials

Consumption tax is closely related to the customer approval rules and regulations which were implementedin Order Management.

For details, refer to:

▪ Consumption tax▪ Customer approval.

Currency differences


ERP Baan5.0cIn ERPBaan5.0c, calculated currency differences were not completely correct because advance paymentsand receipts and unallocated payments and receipts were not considered, however, cash accounts andinvoice accounts were considered.

You could only calculate currency differences in the Calculate Currency Differences (tfgld5201m000)session. The currency differences were posted to the ledger accounts you specified in the CompanyParameters (tfgld0103s000) session or in the Currency Difference Ledger Accounts by Currency(tfgld0119s000) session. As a result, no details can be traced to individual transactions for reconciliationpurposes.

Exchange gain and loss could only be calculated in an independent multicurrency system.

ERP LN 6.1In ERP LN 6.1, the way to calculate, handle, and post currency differences was improved.

The following improvements were made:

▪ Currency difference contra accountsCurrency differences are posted to the currency difference contra account that you mustassign to each ledger account for which you select Required, Calculate Currency Diff.

▪

in the Currency Analysis field of the Chart of Accounts (tfgld0108s000) session. You canmap the currency difference contra accounts separately in the integration mapping scheme.As a result, the reconciliation data for currency differences is more accurate.

▪ Exchange gain and loss for integration transactionsERP LN calculates exchange gain and loss for integration transactions if different ratetypes are used for the debit side and the credit side of the transaction. The differenceamounts are posted to theDestination Gain /Loss for Integration Transactions accountthat you select for the financial company in the Company Parameters (tfgld0103s000)session.

For details, refer to Currency differences interim accounts

▪ Advance payments and receipts and unallocated payments and receipts are included in thecurrency differences calculations.

▪ The transaction occurrence and the transaction amount are always available on the ledgeraccount, so that the calculate currency differences process can be performed.


Financials

▪ In the General Ledger, you can print an interim table of the calculate currency differencesprocess.

▪ In Accounts Payable and Accounts Receivable, you can write off payment differences andcurrency differences for specific invoices.

Daily balances


New in Infor ERP LN 6.1In ERP LN 6.1, to maintain daily balance information for a ledger account, you can select the DailyBalance check box in the Chart of Accounts (tfgld0108s000) session. You can only select this checkbox for ledger accounts of level 0 (zero).

You can display the distribution by period of the ledger history in the following sessions:

▪ Distribution by Date for Ledger Account (tfgld3533m000)

▪ Distribution by Date for Dimension/Ledger Account (tfgld3535m000)

If you also select the new Balance by Business Partner check box, you can display the distribution ofthe ledger history by period and by business partner in the following sessions:

▪ Distribution by Date for Ledger Account by Business Partner (tfgld3534m000)

▪ Distribution by Date for Dimension/Ledger Account by Business Partner (tfgld3536m000)

You can use the Daily Balances (tfgld2531m000) session for analysis of the daily balances.

The session shows:

▪ The effect of each transaction on the ledger account balance

▪ The opening balance of the ledger account on the first date of the date range

▪ The closing balance of the ledger account on the last date of the date range

▪ The total sums for the credit side and debit side for the given date range

To analyze the transactions of a single document date, enter the same date in the Document DateFrom and the Document Date To fields.

Dimension accounting


ERP Baan5.0cIn ERP Baan5.0c, the dimensions of the control accounts and tax accounts to which invoice-relatedtransactions such as currency results, early payment discounts, payment differences, and unallocatedpayments are posted are fixed. You select these dimensions in the Ledger Accounts by Business PartnerGroup (tfacr0111m000) session and the Ledger Accounts by Business Partner Group (tfacp0111m000)session.


Financials

In addition, in ERP Baan5.0c you cannot define dimensions for the Interim Closing account.

ERP LN 6.1

Dimension accounting provides good insight in the financial situation of various parts of an organization,and reduces the need to set up multiple financial companies, which reduces the implementation time,the number of intercompany transactions, and the period closing cycles and year closing cycles.

In ERP LN 6.1, dimension accounting has been extended and the dimension accounting setup for controlaccounts is more flexible. The following enhancements were made:

▪ For the dimension types linked to the control accounts, ERP LN posts the open entries to thedimensions specified on the invoice header. You can specify the default dimensions for salesinvoices and purchase invoices on several levels.To determine the dimensions, ERP LN searches these levels from the most specific, theinvoice, to the least specific, the financial business partner group. For details, refer to Dimensionaccounting.

▪ In ERP LN 6.1, the Interim Closing account is known as the Retained Earnings account. Inthe Company Parameters (tfgld0103s000) session you can use the Dimension Accountingon Retained Earnings check box to specify the dimensions for the Retained Earnings accounton company level. If you clear this check box, Infor ERP derives the dimensions for retainedearnings from the dimension history.

▪ To support dimension accounting also for tax amounts, tax amounts are posted to thedimensions that you link to the control accounts. The dimensions that you can still enter in thePosting Data for Multiple Tax Codes (tfgld0170s000) and Posting Data for Tax Codes(tfgld0171s000) sessions are only used if mandatory dimension types are linked to the taxaccounts and the corresponding dimensions are not defined for the control account.

Employee's expenses


New in Infor ERP LN 6.1In ERP LN 6.1, you can assign expenses to advance payments, for example, to settle an employee'sstatement of expenses with a received advance.

For details, refer to To assign employees' expenses to advance payments.

Factoring


Factoring is a form of accounts receivable financing that consists of the sale of a company's accountsreceivable to a third party (the factor), in order to obtain funding. The sale is made at a discount fromthe account's value. Customers remit to the factor either directly or indirectly through the seller. Factoring


Financials

can be with or without recourse. For factoring with recourse, the risk of customer non-payment remainswith the company.

ERP Baan5.0cIn ERP Baan5.0c, you can indicate that a supplier uses a factoring company to collect payments fortheir invoices. Payments are then made to the factor's bank instead of the supplier's bank.

ERP LN 6.1In ERP LN 6.1, the factoring functionality was redesigned and extended. You can set up factoring bothfor accounts payable and accounts receivable. Factoring with recourse and without recourse are bothsupported.

For details, refer to Factoring.

To support the new factoring functionality, new sessions were added to and sessions were changed inthe following modules:

▪ Accounts Receivable for factoring of your sales invoices. For details, refer to To set up factoringof accounts receivables.

▪ Cash Management.

▪ Accounts Payable for payments of purchase invoices that are factored by your suppliers. Fordetails, refer to To set up factoring of accounts payables.

Fixed assets management enhancements


New in Infor ERP LN 6.1In ERP LN 6.1, the following features and requirements are implemented:

▪ Transaction types for various FAM transactionsIn the FAM Parameter (tffam0100s000) session, you can select the transaction types fordifferent fixed assets transactions such as disposal, depreciation, and investment. For exampleyou can use this feature to exclude specific fixed assets transactions from the journal book.

▪ Suspended DepreciationTo suspend depreciation for specific periods. In some countries, you can suspend depreciationfor periods during which the asset is not used for any reason. You can perform the depreciationin later periods.You can use the new Mass Suspend Depreciation (tffam1207m000) session to suspend thedepreciation of a range of asset books for a range of years and periods. For details, refer toSuspending depreciation.

▪ Accelerated DepreciationTo depreciate an asset by an extra amount in a specific year. In some countries, accelerateddepreciation is allowed to a maximum of 100 percent of the yearly standard depreciation


Financials

amount, until the asset value becomes zero. Accelerated depreciation reduces the depreciationtime. Accelerated depreciation transactions must be posted to specific ledger accounts.Accelerated depreciation follows the same rules as the standard depreciation. If the standarddepreciation is suspended, the accelerated depreciation is also suspended. If the actual useof the asset changes, you can reduce or suspend the accelerated depreciation accordingly.You can use the new Mass Accelerated Depreciation (tffam1208m000) session to depreciatea range of asset books by an additional amount. You can do this only once a year. For details,refer to Accelerated depreciation.

▪ Asset Book (tffam1110s000)In connection with the new suspended depreciation and accelerated depreciation functionality,the following fields were added to the Asset Book (tffam1110s000) session:

▪ Count of Suspended PeriodsThe number of periods for which the asset was not depreciated because you suspendedthe depreciation in the Mass Suspend Depreciation (tffam1207m000) session. This fieldis not affected by suspended depreciation that you perform using the Suspended Periods(tffam7120m000) session.

▪ Accelerated DepreciationIf you perform accelerated depreciation on the asset, Infor ERP selects this check box.

▪ Remain. Depr. Life (YY/MM)The total remaining depreciation life, expressed as the sum of the remaining asset life andthe number of periods for which you suspended the depreciation.

Freight Management integration


Freight Management is a new package in ERP LN 6.1

The purpose of Freight Management is to plan and/or to subcontract the transportation of inbound andoutbound goods, which helps you select the most cost-effective way to get goods in and out of the siteat the correct times.

New in Infor ERP LN 6.1In ERP LN 6.1, the handling of freight invoices raised in Freight Management was added to Financialsand Central Invoicing.

Depending on the agreements you make with the carriers and the involved business partners, one orseveral of the following actions take place:

▪ Business partners are invoiced for the estimated freight costs through Central Invoicing.

▪ For internal business partners, alternatively the freight costs can be dealt with throughintercompany settlement transactions.

▪ The carrier's invoices for the actual freight costs are entered and matched with the shipmentor load in Accounts Payable.


Financials

▪ For the difference between the estimated freight costs and the actual freight costs, an additioninvoice or a credit note can be generated in Central Invoicing.

The Freight Management integration includes the following changes:

▪ Sold-to Business Partners (tccom4110s000) and Buy-from Business Partners(tccom4120s000)You can use the Invoice BP for Freight check box to indicate whether you charge the businesspartner for the freight costs of the sold goods or purchased.

▪ Invoice-to Business Partners (tccom4112s000)You can indicate whether the freight costs on the invoice must be based on the client's ratesor the actual costs.

▪ ACP Parameters (tfacp0100s000)In the Internal Freight Invoices group box, you can enter the transaction type and series,the batch reference, and the integration document type used to map freight invoices forgenerated internal freight invoices.

▪ Purchase Invoices (tfacp1110s000)The Invoice Type field indicates whether the invoice is related to purchase orders or othercosts. If the invoice covers purchased transport rather than purchased goods, select InvoiceRelated to Freight Orders.For invoices related to freight orders, you can specify the load, the shipment, and the freightorder cluster.

▪ Mapping Scheme (tfgld4573m000)You can use the following integration document types to map the freight-related integrationtransactions:

▪ Freight Order / Freight Costs Invoiced (10070042)

▪ Freight Order / Revenues Analysis (10070082)▪ Freight Shipment / Freight Costs (10071041)

▪ Freight Shipment / Price Variance (10071065)

▪ Freight Shipment / Subcontracting (10071089)

▪ Freight Order Cluster / Freight Costs (10072041)

▪ Freight Order Cluster / Price Variance (10072065)

▪ Freight Order Cluster / Subcontracting (10072089)

German localizations


This topic describes the German localization functionality that was added to the ERP LN 6.1 standardsoftware.


Financials

German financial requirements in ERP LN 6.1

▪ Z4 report for foreign paymentsIn Germany, foreign payments must be reported to the German National Central Bank withthe so-called Z4 report. In ERP LN 6.1, you can print the Z4 data to a file.The following new sessions support the Z4 report for foreign payments:▪ Payment Analysis (tfcmg3140m000).▪ Payment Analysis by Item (tfcmg3545m000).

▪ Payment Analysis by Item Group (tfcmg3544m000).

▪ Pay-by Business Partner Payment Analysis (tfcmg3450m000).In the Pay-by Business Partner Payment Analysis (tfcmg3450m000) session, you can generatethe Z4 report data.

▪ DTAUS disk clearing for direct debitsBusinesses in Germany use two direct debit methods:

▪ Mandate (German: Einzugsermächtigungsverfahren).▪ Preauthorized (German: Abbuchungsverfahren).In ERP LN 6.1 the German direct debit methods are available in the Payment/Receipt Method(tfcmg0140s000) session. If you enter Create German Bank Order (Debit) for Diskette(tfcmg4261s000) in the Sess for Payt/Recpt field, you can select a German direct debitmethod in the Payment Method Procedure field.

▪ Advance payment categoriesBusinesses in Germany are legally required to make a distinction between advance paymentsthat you make for intangible assets, tangible fixed assets, inventories, and other assets. InERP LN 6.1, you can select separate ledger accounts for the financial business partner groupin the Accounts by Financial BP Group (tfacp0110m100) session for each advance paymentcategory. In addition, you can select or view the advance payment category, such as banktransactions, payment advice, and standing orders, in the sessions to which this applies.

GL codes


A GL code represents a ledger account and the corresponding dimensions. GL codes are used torepresent ledger accounts to users who are not familiar with the structure of the chart of accounts. Tospecific logistic transactions, you can link a GL code. Such integration transactions are mapped directlyto the ledger account and dimensions of the GL code, they are not included in the mapping process.

ERP Baan5.0cIn ERP Baan5.0c, for some types of logistic transactions such as purchase orders, if you did not wantto map the transaction according to the integration mapping scheme, you could enter the ledger accountand the dimensions to which the transaction must be posted on the order lines.


Financials

ERP LN 6.1In ERP LN 6.1, you can define GL codes, to directly map integration transactions. In this way, if youcreate an order, you can select a GL code of which the description corresponds with the nature of theorder. No knowledge of the ledger account and/or dimension codes an numbers is required.

in the Integration Transactions (tfgld4582m000) session, you can see whether an integration transactionwas mapped through a GL code.

Integration mapping scheme


This topic describes the redesigned integration mapping scheme of ERP LN 6.1.

ERP Baan5.0cIn ERP Baan5.0c, the transaction origin/financial transaction combinations and the correspondingintegration elements are hard coded in the software. As a result, if new transaction origins, financialtransaction types, and integration elements are introduced in the logistic packages, Financials must beupgraded before you can set up the financial mapping of the new integration transactions.

In ERP Baan5.0c, mapping and posting the integration transactions is done in one step. If the mappingis incorrect, the posting is automatically also incorrect. You must then manually create correctivetransactions on the integration ledger accounts.

ERP LN 6.1In ERP LN 6.1, the integration transactions (tror/fitr combinations) existing in ERP Baan5.0c arerepresented by a whole new set of integration document types, and many new integration transactionswere added.

As a result, if you migrate from ERP Baan5.0c to ERP LN 6.1, you must set up a new integration mappingscheme.

The new integration mapping scheme has the following main components:

▪ integration document typeRepresents a type of Operations Management transaction for the purpose of mapping andposting the integration transactions to Financials and for financial reconciliation.

▪ mapping elementA property of a logistic transaction that you can use to define the ledger account and dimensionsfor an integration transaction. You can post the transactions with specific values of the mappingelements to specific ledger accounts. A mapping element consists of the combination of abusiness object and a business object attribute. For example, the Item group/Item mappingelement represents the Item group business object attribute of the Item business object.

The redesigned integration mapping scheme provides a solid basis for the reconciliation of logistictransactions and financial transactions, and for financial reporting.


Financials

Integration mapping scheme enhancementsThe integration mapping scheme offers the following enhancements:

▪ Decoupling of Financials from the logistic environment. The new mapping scheme setup isindependent of the number and types of logistic transaction origins and integration elements.If logistic transaction origins and integration elements are added or changed, the Financialsprograms do not need to be changed.

▪ Improved calculation, handling, and posting of currency differences.

▪ Easier integration of logistic third party applications and customized ERP LN functionality withFinancials.

▪ The mapping to dimensions is similar to the mapping to ledger accounts.

▪ Asmuch as possible, ERP LN prevents that youmakemistakes in themapping scheme setup.At every setup step, you can only select the integration document types, ledger accounts,integration elements, and so on, that are valid for the selections you made during previoussteps of the setup process.

▪ Before you use amapping scheme, ERP LN checks whether the mapping scheme is completeand consistent.

▪ ERP LN performs version control on the mapping schemes. You can maintain a number ofintegration mapping scheme versions with their effective dates and expiry dates.

▪ Logging, mapping, and posting of the integration transactions consists of three separate steps.Before you post the integration transactions to Financials, you can remap the integrationtransactions if this is required. If the mapping is correct and error free, you can post thetransactions.

▪ If required, you can reverse the mapping of integration transactions, make the necessaryadjustments, and rempa and repost the transaction. For details, refer to To remap integrationtransactions.

▪ You can set up compression of the integration transactions in the mapping scheme detailsseparately for the credit side and the debit side of each mapped integration transaction.

Intercompany settlement


In ERP Baan5.0c, goods transfer between logistic companies require sales orders and purchase orders.The sales orders and purchase orders result in an accounts receivable open entry in the selling logisticcompany and an accounts payable open entry in the buying logistic company. To clear these entries, apayment must be generated in the buying logistic company, and you must manually apply the paymentsto the sales invoices of the selling logistic company. These time consuming and labor intensivetransactions only represent technical transactions between the logistic companies. No funds are actuallytransferred.

New in Infor ERP LN 6.1In ERP LN 6.1, you can use intercompany settlement transactions transactions to transfer goods betweenlogistic companies without creating an invoice. Intercompany settlement transactions are a specific type


Financials

of intercompany transactions that apply to purchase and sales transactions between logistic companiesin a multilogistic/single-financial company structure.

Intercompany settlement transactions generate less than half the number of postings (10) of a regularinvoicing procedure (24). Therefore, if no invoices are required, you can use intercompany settlementtransactions to considerably reduce the number of postings in your ledger accounts.

Intercompany settlement transactions in a single financial company structure are automatically postedfinancial transactions in one financial company to intercompany accounts. Instead of generating openentries for sales transactions and purchase transactions between the logistic companies, the amountsare posted to intercompany billing accounts and clearing accounts. Such intercompany accounts mustbe of the Balance Sheet type, not of the Intercompany type.

The sales and purchase transactions can concern:

▪ WIP transfer.▪ Inventory transfer.

To create intercompany settlement transactions for purchase/sales transactions between logisticcompanies of a multicompany structure, you must define the logistic companies as affiliated companybusiness partners.

An affiliated company is a separate logistic company that acts as a business partner to your logisticcompany. You must define the sold-to role and the buy-from role for an affiliated companybusiness-partner.

Intercompany settlement


Intercompany settlement transactions are the automatic postings in one financial company to intercompanybilling and clearing accounts instead of invoices generated for sales/purchase transactions between theentities of two logistic companies.

ERP Baan5.0cIn ERP Baan5.0c, goods transfer between logistic companies required sales orders and purchase orders,which resulted in open entries that must be cleared by generating a payment in the buying logisticcompany. In a multilogistic/single finance company structure, these transactions only representedtechnical transactions between the logistic companies without any actual transfer of funds.

New in Infor ERP LN 6.1In ERP LN 6.1, in a multilogistic/single finance company structure the intercompany invoicing processcan be simplified by generating intercompany settlement transactions. Intercompany settlementtransactions only apply to purchase and sales transactions between logistic companies in amultilogistic/single-financial company structure. The sales and purchase transactions can concern WIPtransfers and inventory transfers.


Financials

Intercompany settlement transactions generate less than half the number of postings (10) of a regularinvoicing procedure (24). Therefore, if no invoices are required, you can use intercompany settlementtransactions to considerably reduce the number of postings in your ledger accounts.

Interim Revenue reconciliation


ERP Baan5.0cIn ERP Baan5.0c, reconciliation of interim revenue is not possible. Interim revenue is posted to thefollowing accounts:

▪ Debit: The account defined for Sales/Revenues Analysis in the integration mapping scheme.This must be an integration account.

▪ Credit: the Sales account defined for the tax code by country. This cannot be an integrationaccount.

ERP LN logs a reconciliation transactions for every integration transaction. As a result, ERP LN logs areconciliation transaction for the debit entry but not for the corresponding credit entry. As a result,reconciliation of sales order interim revenue is not possible.

ERP LN 6.1In ERP LN 6.1, to enable reconciliation of sales order interim revenue, the mapping and posting of theAccounts Receivable open entries was changed. This affects the following transactions entered orgenerated in Central Invoicing:

▪ Sales invoices▪ Manual sales invoices▪ Interest invoices

Posting of interim revenueThe following changes were made:

▪ When the invoice is created and stored in the Non-finalized Transactions (gld102) table, thecredit side is posted to the accounts and dimensions defined in the integration mapping schemefor the Sales/Revenues Analysis debit posting. For reconciliation purposes, reconciliation datais logged when the open entry is created.

▪ To retain the current possibility to use different accounts for different tax codes, the tax codeand tax country are available as mapping elements for the ledger and dimension mapping.

▪ Accounts Receivable open entries created through Central Invoicing are posted to the followingaccounts:

▪ Debit: The Accounts Receivable control account. The dimensions are determined throughthe integration mapping scheme.

▪ Credit: The accounts and dimensions to which you mapped the debit side of the SalesOrder/Revenue Analysis integration document type in the integration mapping scheme.


Financials

▪ If the sales invoice has lines with different tax codes, multiple lines for interim revenue arecreated. For a sales invoice, ERP LN calculates and registers tax amounts based on the netinvoice amount aggregated by tax code. Because of this, the Interim Revenue accounts towhich sales orders, service orders and so on are mapped must be identical for a specific taxcode. ERP LN checks this consistency when you check a mapping scheme. If you want touse other interim revenue accounts for sales orders and service orders, you must definedifferent tax codes for sales and service.

▪ For an Accounts Receivable open entry, Sales Invoicing logs the details in the ReconciliationData (tfgld495) table. This data is logged as follows:▪ Reconciliation group = Interim Revenue 5▪ Business Object = Sales Invoice

▪ Business Object ID = sales invoice number (11 positions)▪ Kind of Entry = Sales Invoice.

▪ For the new Interim Revenue 5 reconciliation group, the business objects of the debittransactions, such as the sales order or the service order, are linked through a reference linkto the business objects of the credit transactions, which consist of the sales invoices.

Reconciliation of manual sales invoices and interest invoicesTo enable reconciliation for manual sales invoices and interest invoices entered in Central Invoicing, inaddition, the following changes were made:

▪ The revenue postings for manual sales order lines and interest invoice lines are posted throughthe integration mapping scheme. The following new integration document types were created:▪ Interest Invoice / Revenues Analysis▪ Manual Sales Invoice / Revenues Analysis

▪ The sales ledger account defined for the tax code was removed from the Posting Data forMultiple Tax Codes (tfgld0170s000) and the Posting Data for Singular Tax Codes(tfgld0171s000) sessions. ERP uses the integration mapping scheme to determine the salesledger account.

▪ The existing reconciliation groups for Interim Turnover that are used for posting sales invoicesare combined into one new reconciliation group Interim Revenue 5.

▪ The following ledger accounts are no longer used:

▪ The default manual sales account for manual sales invoice lines, defined in the SLIParameters (cisli1500m000) session. The account is only used for fixed assets disposal,and it must have an integration with the Fixed Assets module for fixed asset disposal. Forfixed assets disposal, ERP generates the integration transactions described in InterimRevenue for Asset Disposal.

▪ The Interest Invoice account defined in the Ledger Accounts by Business Partner Group(tfacr0111m000) session. Instead, the interim revenue on interest invoices is posted asdefined for Interest Invoice / Revenues Analysis in the integration mapping scheme.

▪ In the Manual Sales Invoice Data - Lines (cisli2525m000) session, you can optionally enter aGL code for the posting of the invoice line.


Financials

To facilitate tax auditing, you can use the new Print Tax Transactions for Interim Revenue on SalesInvoices (tfgld1433m000) session to print a report of the revenues and the tax lines in the FinalizedTransactions (tfgld106) table.

Japanese bank file layout


New in Infor ERP LN 6.1In ERP LN 6.1, you can generate bank payment files with the specific Japanese ZENGINKYO formatfor the automatic payment process.


▪ Payment/Receipt Method (tfcmg0140s000)In the Payment Report field, you can enter 54 for the ZENGINKO Japanese bank file layout.

▪ Bank Relation (tfcmg0110s000)The Blocked Account field was replaced with the Account Type field. For Japanese bankrelations, you can select Other.

▪ Bank Branches (tfcmg0511m000)In addition to the Bank Branch Name, you can also enter the Bank Name.

Note

The specific Japanese bank file layout is required to support businesses in Japan.

Journal books


Italian law requires companies to submit a journal book report which contains all financial transactionsin date sequence. The journal book is used for internal and external audits, during lawsuits, and so on.Both a detailed report and a summary report are required. The report pages and the transaction linesmust be numbered sequentially.

New in Infor ERP LN 6.1In ERP LN 6.1, you can generate and print journal books and journal book summaries.

To support the journal book functionality, the following new sessions were added to the General Ledgermodule in Financials:

▪ Journal Book Sections (tfgld0150s000)▪ Print Journal Book Sections (tfgld0450m000)▪ Print Journal Book (tfgld5410m000)▪ Journal Books (tfgld5510m000)▪ Journal Book Transactions (tfgld5511m000)▪ Journal Book Summaries (tfgld5512m000)


Financials

▪ Archive / Delete Journal Books (tfgld5212m000)

Ledger history


New in Infor ERP LN 6.1In ERP LN 6.1, the reporting possibilities on the ledger history were extended. The following improvementswere made:

▪ Daily balances and balances by business partnerTo record the ledger balance information for a specific period and for specific business partners,in the Chart of Accounts (tfgld0108s000) session, you can select the following check boxes:

▪ Daily BalanceIf this check box is selected, ERP maintains daily balance information for the ledgeraccount. You can only select this check box for ledger accounts of level 0 (zero).If you select this check box, you can display the distribution by period of the ledger historyin the following sessions:▪ Daily Balances (tfgld2531m000)

▪ Distribution by Date for Ledger Account (tfgld3533m000)

▪ Distribution by Date for Dimension/Ledger Account (tfgld3535m000)

▪ Balance by Business PartnerIf this check box is selected, for every transaction posted to the ledger account, ERPrecords the business partner. If you select this check box, you can display the distributionby business partner of the ledger history in the Ledger History by Business Partner(tfgld3530m000) session.

▪ Ledger history dashboardThe new Ledger History (tfgld3501m000) session is a completely redesigned version of theprevious Ledger History (tfgld3501s000) session. The new session displays various views onthe ledger history and provides easy access to the related ledger history sessions.

For details, also refer to Ledger history.

Localizations


In ERP LN 6.1, you can use the new parameter wizard to set up the specific localized functionalityrequired for your company. For more information, refer to The Parameter Wizard.

The following localizations are part of the standard software in ERP LN 6.1:

▪ BelgiumThe following requirements specific for Belgium are part of the ERP LN 6.1 standard software:

▪ Bank files for foreign and domestic payments.▪ Balance of Payments reporting.


Financials

▪ Intracom reporting.▪ VAT report.▪ Tax journal.▪ Accon interface.For more information, refer to Belgian localizations (p. 50) .

▪ European UnionThe following functionality was added for business partners and bank account in countries ofthe European Union:

▪ VAT number checkIn ERP LN 6.1, baan can check whether VAT numbers for business partners in EU countriesare entered correctly. For EU countries, you can select the VAT number check for thecountry in the VAT Number Check field of the Countries (tcmcs0110s000) Countries(tcmcs0110s000) session.

▪ Bank account number checkIn ERP Baan5.0c, the type of bank account number check you selected in the COMParameters (tccom0000s000) session applied to the whole company. In ERP LN 6.1, youcan specify the type of bank account number check separately for each country in theCountries (tcmcs0110s000) session.

▪ Sales listing enhancementsIn ERP LN 6.1, in The Netherlands you can generate the sales listing declaration as anXML file and set up automatic transmission of the file. For details, refer to EU sales listingdeclaration (p. 25) .

▪ Intrastat declaration enhancementsERP LN 6.1 offers a flexible Intrastat solution which you can set up to retrieve specificdata and meet the specific Intrastat declaration requirements of most European countries.Infor ERP does not generate the Intrastat declarations. The EU Intrastat declarations canbe generated and supplied to the Intrastat authorities by means of an external Intrastatapplication. For details, refer to Intrastat declaration (p. 26) .

.

▪ FranceIn ERP LN 6.1, the following functionality was added:

▪ DAS 2 reportingDAS 2 is the Déclaration Annuelle des Salaries (Annual declaration of the wages/fees).A report of all payments made to third parties during a fiscal year, which must be submittedannually to the French government. The DAS 2 report must include all normal payments,assignments, and settlements through sales invoices. For details, refer to DAS 2 reporting.

▪ French payment filesIn ERP LN 6.1, the following French payment files are available:ChecksTrade notesBank transfersIn the Payment/Receipt Method (tfcmg0140s000) session, select the appropriate reportgroup.


Financials

▪ GermanyThe following requirements specific for Germany are part of the ERP LN 6.1 standard software:▪ Z4 report for foreign payments.▪ DTAUS disk clearing for direct debits.▪ Advance payment categories.For more information, refer to German localizations (p. 59) .

▪ The NetherlandsERP LN 6.1 suports the electronic transmission of the VAT declaration, the Intrastat declaration,and the sales listing declaration to the tax authorities.For details, refer to:▪ Automatic transfer of tax declarations▪ Intrastat declaration (p. 26)▪ EU sales listing declaration (p. 25)

▪ North America (USA)The sales and use tax functionality was extended with the following functionality:▪ Direct Pay permit registration.

▪ Tax calculation date is order date or invoice date.

▪ Optionally include tax amounts in order balance.

▪ Optionally print tax amounts on external documents.▪ Print tax amounts by tax authority.▪ Tax provider API enhancements.

▪ PortugalTo meet legal requirements in Portugal, you can specify separate ledger accounts for the VATamounts on credit notes and on advance payments in the following sessions:

▪ Posting Data for Singular Tax Codes (tfgld0171s000)

▪ Posting Data for Multiple Tax Codes (tfgld0170s000)

▪ The Scandinavian countriesThe following requirement specific for the Scandinavian countries are part of the ERP LN 6.1standard software:

▪ Bank files for foreign payments and domestic payments. (Norway, Sweden, Finland,Denmark)

▪ Bank reference numbers. (Norway, Finland)▪ Allow payments of negative amounts. (Sweden)▪ Journal report. (Finland)

▪ Interest invoices for partly paid and non-paid invoicesFor more information, refer to Scandinavian localizations (p. 79) .

Lower cost or market value method


For the inventory valuation in the balance sheet, in some countries the inventory value based on any ofthe inventory valuation methods must be compared with the current market price. If the market price is


Financials

lower that the valuation according to one of the internal valuation methods, the whole inventory of anitem must be valuated for the balance sheet with the market price. This method of valuating items ininventory is called the Lower Cost or Market Value method.

The Lower Cost or Market Value method is legally required in several countries, for example, theEuropean countries, the US, and Japan.

New in Infor ERP LN 6.1In ERP LN 6.1, in Warehouse Management, the Perform Inventory Valuation (whina1210m000) sessionand its resulting reports were changed so that you can optionally apply the lower cost or market valuemethod.

Monthly billing invoice


New in Infor ERP LN 6.1In some countries, for example, in Japan, it is common practice for organizations to send their customersa monthly statement of the open invoices. Such a statement is called a monthly billing invoice.

You can set up Infor ERP to generate monthly billing invoices for your customers and to use self-billingfor receipts from suppliers from whom you receive a monthly billing invoice.

The implementation of the monthly billing invoice affects the following packages:

▪ In Financials, the following modules:▪ Accounts Payable▪ Accounts Receivable▪ Cash Management

▪ Central Invoicing

For details, refer to Monthly billing invoices.

Note

In previous versions of ERP LN, the monthly statement of invoices was available as a localization forJapan.

Multicompany purchase invoice matching


ERP Baan5.0cIn ERP Baan5.0c, purchase invoice matching was only possible in the financial company of the purchaseoffice that created the purchase order.


Financials

New in Infor ERP LN 6.1In a multicompany structure in ERP LN 6.1, purchase invoice matching is possible in any financialcompany of the structure, provided that the companies share the correct tables for this purpose.

FeaturesMulticompany purchase invoice matching is needed to support:

▪ The use of a shared service center for Accounts PayableCentral handling of purchase invoice entry, invoice matching and payment for multiple financialcompanies.

▪ VAT registration in multiple EU countriesIf a company’s activities that are subject to value added tax (VAT) in an EU country other thanthe member country in which the company is registered exceed a specified threshold, thecompany is legally obliged to be VAT registered in that other EU country.In a multicompany structure, a dedicated financial company is created for each foreign VATregistration. Usually, the purchase offices in which the purchase orders are entered are notlinked to such financial companies.If the purchase invoice matching can be performed in the ‘VAT registration companies’, thecosts of the purchase order are automatically charged to the company of the purchase office.If this matching scenario is used, it is no longer necessary to create an internal invoice betweenthe two financial companies.

Posting principlesThe posting principles that apply to this method of purchase invoice matching are as follows:

▪ The costs directly related to the purchase order and/or inventory are posted in the financialcompany of the purchase office. Some examples are the price variance, the FTP result, andadditional costs posted at matching.

▪ The results from the open entry are posted in the financial company in which the purchaseinvoice is registered and matched. Some examples are the currency result, the paymentdiscount, the late payment surcharge, the payment difference.

Multiple control accounts


ERP Baan5.0cIn ERP Baan5.0c, you can define only one control account for the financial business partner groups inthe Accounts Payable and the Accounts Receivable modules.

ERP LN 6.1Business practices in Japan, Spain, Italy, and other countries require that different types of receivablesand payables be posted to different control accounts. To achieve this, in ERP LN 6.1, you can set up


Financials

multiple control accounts for a business partner group. You can use the new Sales Type and PurchaseType properties to post sales invoices and purchase invoices to specific control accounts.

For each business partner group, you can define the control account to be used for each sales type andpurchase type.

Examples of various types of sales and purchases are:

▪ Trade▪ Non-trade▪ Cost (purchases only)▪ Fixed asset

Sales types and purchase typesSales types and purchase types are a sales order or purchase order property that allows you to identifythe kind of sale or pruchase made and the kind of receivable or payable. This property is used to postthe amounts to the correct control accounts.

To support multiple control accounts in Accounts Payable and Accounts Receivable, you can definesales types and purchase types in the following new sessions in Common:

▪ Purchase Types (tcmcs2101m000)▪ Sales Types (tcmcs2102m000)

Sales type and purchase type exceptions link sales types or purchase types (and in this way, a controlaccount) to transactions that involve specific details for a business partner and order origin. You candefine sales type and purchase type exceptions in the following sessions:

▪ Purchase Type Exceptions (tcmcs2103m000)▪ Sales Type Exceptions (tcmcs2104m000)

Open entry enquiries on purchase orders


ERP Baan5.0cIn ERP Baan5.0c, to perform open entry enquiries you must enter the invoice number. You cannotdisplay the open entries related to a specific purchase order.

ERP LN 6.1In ERP LN 6.1, you can view the purchase invoices that are related to a specific order.

From the specific menu in the Accounts Payable Management Dashboard (tfacp2560m000) session,you can start the new Invoice Information on Purchase Orders (tfacp2540m000) session.

The Invoice Information on Purchase Orders (tfacp2540m000) session displays the purchase orders.


Financials

You can select an order and on the specific menu click one of the following commands:

▪ Purchase-Invoice DetailsStarts the Purchase-Invoice Details (tfacp2100s000) session, which displays the details ofthe selected invoice.

▪ Invoices by OrderStarts the Invoices by Order (tfacp2550m100) session, which displays the invoices that arerelated to the selected purchase order. If you select an invoice, on the specific menu you canclick Purchase-Invoice Details to start the Purchase-Invoice Details (tfacp2100s000) session.

Note

If no invoices are linked to the purchase order, the commands on the specific menu are not available.

Parameter wizard


ERP Baan5.0cIn ERP Baan5.0c, for specific functionality you must define parameter values and select options inseveral sessions in multiple modules and/or ERP LN packages.

New in Infor ERP LN 6.1In ERP LN 6.1, you can use the new parameter wizard to set up the specific localized functionalityrequired for your company. For more information, refer to The Parameter Wizard.

Payment slips


Payment slips are optically readable documents attached to an invoice, which can be sent to the bankto make the payments for the invoice. The supplier's bank account number, the invoice amount, and aninvoice reference number are preprinted on the payment slip. If a payment slip is attached to an invoice,the payment slip is created and printed together with the invoice.

New in Infor ERP LN 6.1ERP LN 6.1 supports the use of payment slips that meet the requirements of Swiss banks.

To support the use of payment slips, the following changes were made:

▪ General LedgerIn the newAdditional Currency Features (tfgld0129m000) session, you can define the currenciesfor which ERP LN must print a payment slip for sales invoices with this invoice currency.

▪ Cash ManagementIn the Report Group Payments/Receipts and the Additional Report fields of thePayment/Receipt Method (tfcmg0140s000) session, you can enter number 44, 'DTA Report',


Financials

to generate a payment file that can be sent to the bank and which contains the informationrequired to process payment slips. DTA = Daten Traeger Austausch, or Data carrier exchange.

▪ Central InvoicingIf you select the Payment Slip check box for the invoice currency in the Additional CurrencyFeatures (tfgld0129m000) session, ERP LN prints a payment slip for the invoice.

Pay-to business partner statistics


ERP Baan5.0cIn ERP Baan5.0c, you can use the Pay-by Business Partner Statistics (tfcmg3500s000) session to viewthe payment performance of your customers. However, no information is available about your paymentsto your suppliers.

ERP LN 6.1In ERP LN 6.1, you can generate and view your own payment performance to your suppliers in the sameway.

Use the following sessions:

▪ Update Pay-to Business Partner Statistics (tfcmg3202m000)

▪ Pay-to Business Partner Statistics (tfcmg3502m000)

You can start these sessions from the menu tree and from the Business Partner Balances(tfacp2582m000) session, which you can start from the Accounts Payable Management Dashboard(tfacp2560m000) session.

Period handling for integration transactions


ERP Baan5.0cIn ERP Baan5.0c, if you cleared the Posting to Next Open Period Allowed check box in the IntegrationParameters (tfgld4150s000) session, ERP LN generated an error message for integration transactionsfor a period that was Closed. To post the transaction, you could set the period to Open, or manuallychange the period on the transaction.

If you selected the Posting to Next Open Period Allowed check box, all integration transactions for aperiod that was Closed were posted to the next open period. This could result in problems during thereconciliation.

ERP LN 6.1In ERP LN 6.1, posting integration transactions to the next open period is better controlled. For integrationtransactions for a Closed integration period, you can manually enter a request for exception in the


Financials

Requested Exceptions for Integration Transactions (tfgld4585m000) session. If the request is approved,you can post the integration transaction to the next open period or to the closed period, provided theGLD period for general ledger transactions is Open.

For each integration document type, you can select the action ERP LN performs if a period is Closed.

You can select the following closed period handling options:

▪ Exception handling▪ Post to next open period▪ Post to current period

In the Closed Period Handling field of the Integration Parameters (tfgld4150s000) session, you canselect the default option. In the new Period Handling by Integration Document Type (tfgld4579m000)session, you can select the closed period handling option for individual integration document types.

If you select Exception handling, ERP LN automatically creates an exception request if the period isClosed. However, the request must still be manually approved and youmust ensure that theGLD periodstatus is Open at the time when you post the integration transaction.

Because for reconciliation only the fiscal period is considered, the exception requests only apply to fiscalperiods. If the reporting period or the tax period is closed, the integration transaction is automaticallyposted to the next open reporting period or the tax period.

Period type selectionIn ERP LN 6.1, you can select the period type ERP LN checks to detect whether the period is Open.

You can select the following period types:

▪ INT for integration transactions.▪ ACP for accounts payable transactions.▪ ACR for accounts receivable transactions.▪ GLD for general ledger transactions.

For example, if you select ACP then you cannot post an integration transaction if the ACP period isClosed even if the INT period is still Open.

In the Requested Exceptions for Integration Transactions (tfgld4585m000) session, you must enter thefiscal year and period, the reporting year and period, and/or the tax year and period to which theintegration transaction must be posted. Only the fields that correspond to a Closed period are enabled.

Procurement card payments


ERP Baan5.0cIn ERP Baan5.0c, procurement card payments were not supported. Procurements must bemade throughpurchase orders, using printed documents or a semi-automated process. This process is complex andtime consuming.


Financials

ERP LN 6.1In ERP LN 6.1, purchases can be paid through procurement cards. New procurement card processingfunctionality was added to the Accounts Payable module.

Purchased goods that you pay through a procurement card are received immediately if they are purchasedfrom the store, or later if you order them through E-Procurement. For each purchase, you can enter apurchase requisition or you can import a purchase requisition file from E-Procurement or anotherapplication.

The procurement card company sends procurement card statements periodically. The procurementcard statement contains the product code, the credit card number, and other details, which are alsoregistered for the purchase requisition. The procurement card statement must be matched against thepurchase requisitions and then approved for payment. If you did not enter a purchase requisition earlier,you can still enter the purchase requisitions or you canmanually approve the procurement card statement.

A ledger posting is made when you enter the purchase requisition and when the procurement cardstatement is invoiced. All the purchase requisitions for which no procurement card statements arereceived for payment can be accrued to a special ledger account. This enables you to control the entireprocurement cycle, from a purchase requisition to payment and reconciliation with the general ledger.

Note

ERP LN does not support procurement card payments for sales.

Purchase invoice matching - Enhanced error reporting


ERP Baan5.0cIn ERP Baan5.0c, the error log of the Match/Approve Purchase Invoices by Range (tfacp2280m000)session contains both errors and confirmations for matched and approved invoices. Each time whenyou start the session, ERP LN deletes the complete error log.

ERP LN 6.1In ERP LN 6.1, the following changes were made to the error log that you can display and maintain inthe Error Log (tfacp2580m000) session:

▪ The error log only contains error messages. ERP LN prints the confirmation messages of theMatch/Approve Purchase Invoices by Range (tfacp2280m000) session, for example, aboutsuccessfully matched invoices, on a process report.

▪ The error log contains all the error messages that result from matching and approval. Thisincludes the messages resulting from other match and approve sessions which in ERPBaan5.0c were not included in the error log, such as the Purchase Invoices (tfacp1110s000)session.

▪ The error log contains all errors that are not yet resolved. If you run the Match/ApprovePurchase Invoices by Range (tfacp2280m000) session, for the transactions within the specifiedrange ERP LN adds new error messages and deletes resolved errors from the error log.


Financials

▪ The error messages include the batch number of the purchase invoice, to facilitate the locationof the invoice for which an error was logged.

▪ A new sort option allows you to sort the errors by error description.

▪ You can use the new Delete Error Log (tfacp2280m001) session to manually delete messagesfrom the error log.

Reconciliation


ERP Baan5.0cIn ERP Baan5.0c, reconciliation possibilities were limited.

Differences between the amounts of the logistic transactions and the financial postings could have thefollowing causes:

▪ The rounding of amounts and quantities

▪ The use of various currency rate types and currency rates for related transactions

▪ The expression of the transaction amounts in various currencies within one transaction.

To perform reconciliation, you needed to generate various reports of the financial integration transactionsand compare themwith reports generated in the logistic packages. In the logistic packages, transactionscould be deleted before a reconciliation had taken place, which made a reliable reconciliation awkward.

ERP LN 6.1ERP LN 6.1, provides a complete and consistent reconciliation functionality. Instead of generating variousreports of the integration transactions, you can use the reconciliation reports generated in the newOperations Management - Financial Reconciliation (tfgld4595m000) session.

You can use the new reconciliation functionality to analyze and report whether:

▪ Financial transactions are handled on time.▪ Reports are complete.

▪ The amounts posted to ledger accounts correctly reflect the logistic transactions.

In addition, in ERP LN 6.1 currency differences are posted to separate interim accounts so that thereconciliation data is more accurate.

Recurring journal transactions



Financials

ERP Baan5.0cIn ERP Baan5.0c, you can set up the following kinds of recurring journal transactions:

▪ Recurring/Reversing Journal transactions, in the General Ledger module. Based on existing,finalized journal transactions, ERP LN can generate recurring journal transactions accordingto a schedule.

▪ Recurring sales invoices, in the Recurring Sales Invoices (tfacr1514m000) session.

▪ Recurring purchase invoice, in the Recurring Purchase Invoices (tfacp1113s000) session.

ERP LN 6.1In ERP LN 6.1, you can use the Recurring Journals (tfgld0140m000) session to create both recurringjournal transactions and recurring invoices. The recurring transactions are not based on an existingfinalized transaction. In addition, you can set up recurring reversal transactions that reverse the relatedrecurring transactions.

For details, refer to Recurring journals.

Remap integration transactions


ERP Baan5.0cIn ERP Baan5.0c, if integration transactions were mapped and posted to an incorrect ledger accountdue to errors in the integration mapping scheme, you could not correct the errors.

ERP LN 6.1In ERP LN 6.1, you can use the new Remap Posted Integration Transactions (tfgld4282m100) sessionto remap Posted transactions that were mapped incorrectly. For example, you can remap transactionsthat were mapped and posted to an incorrect ledger account or dimensions.

If you remap a transaction, ERP LN performs the following actions:

▪ Generate a reversal transaction for the posted transaction.▪ Create a new integration transaction.

▪ Map the new transaction according to the currently active version of the mapping scheme orto the specified GL code.

Reverse entries


ERP Baan5.0cIn ERP Baan5.0c, you could not reverse finalized financial postings, for example, to correct a mistake.Corrections had to be made manually and this could be very time consuming.


Financials

ERP LN 6.1In ERP LN 6.1, you can use the Reverse Entry (tfgld1295m000) session to create reversal documentsfor finalized transactions.

On ledger accounts that can be matched, you can only reverse the transactions that are not yet matched.

You can only reverse single transactions, and you can reverse a transaction only once. You cannotreverse a batch of transactions. If you have corrected the transaction document or linked the transactiondocument to another document, you cannot reverse the transaction.

Scandinavian localizations


This topic describes the localization functionality for Scandinavian countries that was added to the ERPLN 6.1 standard software.

Scandinavian countries financial requirements in ERP LN 6.1

▪ Bank files for foreign payments and domestic paymentsIn Scandinavian countries, electronic bank files for payments must include some extrainformation such as the customer code or service number, an identifier of the company'sdivision, and the company's fiscal identification number.The additional information results in specific format requirements for bank files in Scandinaviancountries. ERP LN 6.1 supports 16 new bank formats for the Scandinavian countries. Formore information, refer to the Payment Report field of the Payment/Receipt Method(tfcmg0140s000) session and to To set up Scandinavian bank files.

▪ Bank referenceERP LN 6.1 supports the use of bank reference numbers, which is a common banking practicefor domestic transactions in Norway and Finland. For more information, refer to Bank referencenumbers.

▪ Allow payments of negative amountsIf the total amount of the credit notes exceeds the total amount of the invoices for a businesspartner, this can result in a payment with a negative amount. If the bank can handle paymentsof negative amounts, you can select the Allow Negative amount for Payment check box inthe Payment/Receipt Method (tfcmg0140s000) session for the payment methods used withthe bank.

▪ Finnish journal reportAccording to the Finnish Law, financial transactions must be registered and reported inchronological order to the journal and in transaction type sequence to the general ledger. Thereports required by the authorities concern only the fiscal periods, not the reporting periods.In ERP LN 6.1, you can use the new Print Journal Report - Finland (tfgld1446m000) sessionto generate the required reports.

Trade notes



Financials

Trade note is a generic term for payment instruments such as bank drafts, checks, promissory notes,and bills of exchange. Trade notes can be used instead of cash payments if credit is extended to thecustomer. A trade note can replace the invoice. Because trade notes are negotiable, they can also beused as a credit instrument, for example, for discounting and endorsing. Trade notes can exist on paperand on magnetic supports, according to local business practices and banking standards.

ERP Baan5.0cIn ERP Baan5.0c, trade notes are treated as anticipated documents. Proper trade note processing wasonly available in a number of localizations.

ERP LN 6.1In ERP LN 6.1, the trade notes functionality was redesigned and significantly extended.

For example, received trade notes can be:

▪ Discounted to a bank to obtain early cash.▪ Used as collateral to obtain a loan.▪ Endorsed to pay your supplier.

To support the extended trade notes functionality, a number of new Trade Notes sessions were addedto the Cash Management module.

For details, refer to Trade notes.

Stamp taxIf you use trade notes, in some countries you must pay stamp tax on trade notes. In the Tax Codes byCountry (tcmcs0136s000) session, the new Stamp Tax option was added to the Kind of Tax field. Fordetails, refer to Set up stamp tax.

VAT books


New in Infor ERP LN 6.1Italian law requires companies to prepare and submit a VAT book and a VAT liquidation report.

The VAT book is a legal report of all value added tax (VAT) transactions of a company, in date sequence.The transactions can be grouped by tax articles, which typically group transactions that have the sametax percentage.

In addition to the VAT book, instead of the VAT declaration, companies must yearly submit a VATliquidation report which shows the net VAT amount payable to the tax authorities for the report period.

The liquidated VAT amount is the result of the VAT on purchases minus the VAT on sales. If the resultis a negative amount, the amount must be paid to the tax authorities. If the result is a positive amount,the amount is carried over as a credit amount to the next VAT book period.


Financials

In ERP LN 6.1, you can prepare and submit a VAT book and a VAT liquidation report.

To support the VAT book functionality, the following new sessions were added to the General Ledgermodule in Financials:

▪ VAT Books (tfgld0160m000)▪ Print VAT Book (tfgld1435m000)▪ VAT Book (tfgld1536m000)▪ VAT Book Details (tfgld1535m000)▪ VAT Liquidation (tfgld1534m000)

▪ Archive / Delete VAT Book Details (tfgld1235m000)

Modules

Accounts Payable (ACP) module - Differences B50c/ERP61

This topic summarizes the differences between the Accounts Payable module in ERP Baan5.0c and inERP LN 6.1 and describes differences that are not already discussed in other Differences topics.


▪ Additional investments on fixed assetsIn ERP Baan5.0c, to register a purchase invoice, you could not specify a quantity of zero onthe purchase invoice line in the Purchase Invoice Transactions (tfacp1120s000). In ERP LN6.1, if you register the first purchase invoice, you can specify a quantity of one and forsubsequent invoice lines related to the same asset, you can specify a quantity of zero.For example, you acquire an asset such as a truck, which you pay in monthly installments.Every month, you register a purchase invoice for the installment. In ERP Baan5.0c, for everyinvoice line, you must enter a quantity of at least one, so after ten months, ERP LN hasregistered that you acquired ten trucks. In ERP LN 6.1, you can enter a quantity of one for thefirst purchase invoice and for subsequent invoices, you can specify a quantity of zero.

▪ Aging analysis reportIn ERP Baan5.0c, the business partner aging analysis report always included the cost invoices,independent of the selected options.In ERP LN 6.1, you can use the Include Cost Invoices check box in the Print Invoice-fromBusiness Partner Aging Analysis (tfacp2420m000) session to include the cost invoices or toignore them.

▪ CommissionsCommissions are created as open entries in the Accounts Payable module. In ERP Baan5.0cthe open entries are created through the scripts of the corresponding Order Managementsessions, and you specify the transaction type and document series of the commissiontransactions in the Commissions/Rebates Parameters (tdcms0100s000) session.


Financials

In ERP LN 6.1 the open entries are created by the scripts of the Accounts Payable moduleand you specify the transaction type and document series of the commission transactions inthe ACP Parameters (tfacp0100s000) session.

▪ Assigned credit notes reportIn ERP Baan5.0c, if you link credit notes to invoices, it is not clear for the pay-to businesspartner which credit notes you used to reduce the payment amounts. This can lead to confusionand misunderstandings.In ERP LN 6.1, you can to create a report of the invoices, the credit notes linked to the invoices,and their amounts, for a selection of invoice-from business partners. You can send this reportto your suppliers for information. Use the new Assigned Credit Notes Letter (tfacp4160m000)to define the layout and the addressee for the credit notes report.In the Invoice-from Business Partners (tccom4122s000) session, select the credit notes reportdefinition for the business parnter in the new Document Method field.

▪ Bank reference numbersThe use of bank reference numbers is a common banking practice for domestic transactionsin Norway and Finland. The bank reference number is a unique number that is used to identifythe invoice for which the payment is made. The bank reference number is communicated tothe customer on the invoice document and is always referred on the payment document.For details, refer to:▪ Bank reference numbers▪ Bank reference numbers on purchase invoices

▪ Expensed purchase taxExpensed purchase tax means that the tax amounts of purchase invoices with this tax codeare considered as costs. The purchase tax amounts are posted to the same ledger accountsand dimensions to which the purchase receipt transaction is posted.In ERP Baan5.0c, the expensed purchase tax functionality is only available if you select theDestination Sales Tax Applicable check box in the COM Parameters (tccom0000s000)session.In ERP LN 6.1, you can set up expense purchase tax codes independently of the selection ofthe Destination Sales Tax Applicable check box.Only in North America, specific rules apply to the posting of tax on purchase invoices. To postexpensed purchase tax according to the rules for North America, select the North AmericanPurchase Expensed Tax check box in the ACP Parameters (tfacp0100s000) session. Youcan then select a tax variance account and dimensions.

▪ FactoringIn ERP Baan5.0c, you can indicate that a supplier uses a factoring company to collect paymentsfor their invoices. Payments are then made to the factor's bank instead of the supplier's bank.In ERP LN 6.1, the factoring functionality was redesigned and extended. Factoring with recourseand without recourse are both supported.For details, refer to Factoring.


Financials

▪ Freight Management integrationIn ERP LN 6.1, the handling of freight invoices raised in Freight Management was added toFinancials and Central Invoicing.For details, refer to Freight Invoicing.

▪ Multicompany purchase invoice matchingIn ERP Baan5.0c, purchase invoice matching was only possible in the financial company ofthe purchase office that created the purchase order.In ERP LN 6.1, purchase invoice matching is possible in any financial company of the structure,provided that the companies share the correct tables for this purpose.In the Purchase Invoice Matching field of the ACP Parameters (tfacp0100s000) session,you can select the required matching type. You can click Purchase Offices to start thePurchase Offices byMatching Company (tfacp0101m000) session which displays the purchaseoffices linked to a financial company, or the financial companies linked to a purchase office.For details, refer to Multicompany purchase invoice matching.

▪ Monthly billing invoiceNew in Infor ERP LN 6.1In some countries, for example, in Japan, it is common practice for organizations to send theircustomers a monthly statement of the open invoices. Such a statement is called a monthlybilling invoice.You can set up Infor ERP to generate monthly billing invoices for your customers and to useself-billing for receipts from suppliers from whom you receive a monthly billing invoice.For details, refer to Monthly billing invoices.

▪ Open entries, usability improvementsIn ERP LN 6.1, the new Accounts Payable Management Dashboard (tfacp2560m000) sessionprovides fast access to the purchase invoices and to various types of related information suchas the business partner balances and the aging analysis. You can view the purchase invoicesthat are related to a specific order.

▪ Payment slipsERP LN 6.1 supports the use of payment slips that meet the requirements of Swiss banks.For details, refer to Payment slips.

▪ Price differences authorizationIn ERP Baan5.0c, if you want to specify price differences for invoice matching, you could notenter a percentage of zero or higher than 100, or amounts higher or lower than the actualinvoice amount.In ERP LN 6.1, in the Automatic Matching Tolerances by Invoice-from BP (tfacp0107m000)session, you can select the new Full Authorization check boxes to accept extremely high orlow differences in percentage and amount. If you select these check boxes, you cannot entertolerance amounts or percentages and ERP LN always matches the invoices.For example, you can use this functionality to automatically match invoices with many lines ifsmall differences on each line result in an invoice difference that you do not want to investigatefurther.


Financials

▪ Procurement card paymentsIn ERP Baan5.0c, procurement card payments were not supported. Procurements must bemade through purchase orders, using printed documents or a semi-automated process.In ERP LN 6.1, purchases can be paid through procurement cards. New procurement cardprocessing functionality was added to the Accounts Payable module.For details, refer to Procurement card payments.

▪ Purchase invoice matching - Enhanced error reportingIn ERP Baan5.0c, the error log of the Match/Approve Purchase Invoices by Range(tfacp2280m000) session contains both errors and confirmations for matched and approvedinvoices. Each time when you start the session, ERP LN deletes the complete error log.In ERP LN 6.1, the error reporting on matching manual purchase invoices was enhanced. Fordetails, refer to Purchase invoice matching - Enhanced error reporting (p. 76) .

▪ Recurring journal transactionsIn ERP Baan5.0c, you can set up recurring purchase invoice, in the Recurring PurchaseInvoices (tfacp1113s000) session.In addition, in ERP LN 6.1, you can use the Recurring Journals (tfgld0140m000) session tocreate both recurring journal transactions and recurring invoices. The recurring transactionsare not based on an existing finalized transaction. In addition, you can set up recurring reversaltransactions that reverse the related recurring transactions.For details, refer to Recurring journals.

▪ Self-billed invoicesIn ERP Baan5.0c, you cannot benefit from early payment discounts for self-billed invoices,due to time needed to complete the quantity approvals in Warehouse Management. If youcreate a self-billed invoice without waiting for approval, the invoice is created with a zeroamount and the invoice is matched and approved, which blocks the logistic approval process.In ERP LN 6.1, you can create an invoice without waiting for the approvals. In addition, youcan create a debit memo for any rejected quantity after the self-billed invoice is raised. Therejected quantity is calculated as the total rejected quantity minus the already debited rejectedquantity.In the Pay After field of the Buy-from Business Partners (tccom4120s000) session, you canselect whether you want to create self-billed invoices after receipt or after approval.

▪ Trade notesIn ERP Baan5.0c, trade notes are treated as anticipated documents. Proper trade noteprocessing was only available in a number of localizations. In ERP LN 6.1, the trade notesfunctionality was redesigned and significantly extended.For details, refer to Trade notes.

Accounts Receivable (ACR) module - Differences B50c/ERP61

This topic summarizes the differences between the Accounts Receivable module in ERP Baan5.0c andin ERP LN 6.1 and describes differences that are not already discussed in other Differences topics.


Financials


▪ Assigned credit notes reportIn ERP Baan5.0c, if you link credit notes to invoices, it is not clear for the pay-to businesspartner which credit notes you used to reduce the payment amounts. This can lead to confusionand misunderstandings.In ERP LN 6.1, you can to create a report of the invoices, the credit notes linked to the invoices,and their amounts, for a selection of invoice-from business partners. You can send this reportto your suppliers for information. Use the new Assigned Credit Notes Letter (tfacp4160m000)to define the layout and the addressee for the credit notes report.In the Invoice-from Business Partners (tccom4122s000) session, select the credit notes reportdefinition for the business parnter in the new Document Method field.

▪ Bank reference numbersThe use of bank reference numbers is a common banking practice for domestic transactionsin Norway and Finland. The bank reference number is a unique number that is used to identifythe invoice for which the payment is made. The bank reference number is communicated tothe customer on the invoice document and is always referred on the payment document.For details, refer to:▪ Bank reference numbers▪ Bank reference numbers on purchase invoices

▪ FactoringIn ERP Baan5.0c, you can indicate that a supplier uses a factoring company to collect paymentsfor their invoices. Payments are then made to the factor's bank instead of the supplier's bank.In ERP LN 6.1, the factoring functionality was redesigned and extended. Factoring with recourseand without recourse are both supported.For details, refer to Factoring.

▪ Interest InvoicesIn the Interest Invoice Parameters (tfacr5101s000) session, the following check boxes wereadded:

▪ Interest on Interest InvoiceIf this check box is selected, baan generates interest invoices for interest invoices in thesame way as for other types of invoices.

▪ Interest on Adv. / Unalloc. / Credit NotesIf this check box is selected, baan takes into account advance payments, unallocatedpayments, and credit notes for the generation of interest invoices.

▪ Interim Revenue reconciliationIn ERP Baan5.0c, reconciliation of interim revenue is not possible. In ERP LN 6.1, to enablereconciliation of sales order interim revenue, the mapping and posting of the AccountsReceivable open entries was changed. For details, refer to Interim Revenue reconciliation(p. 64) .

▪ Monthly billing invoiceNew in Infor ERP LN 6.1


Financials

In some countries, for example, in Japan, it is common practice for organizations to send theircustomers a monthly statement of the open invoices. Such a statement is called a monthlybilling invoice.You can set up Infor ERP to generate monthly billing invoices for your customers and to useself-billing for receipts from suppliers from whom you receive a monthly billing invoice.For details, refer to Monthly billing invoices.

▪ Open entries, usability improvementsIn ERP LN 6.1, the new Accounts Receivable Management Dashboard session provides fastaccess to the sales invoices and to various types of related information such as the businesspartner's credit profile and aging analysis.

▪ Print open entries linked to checksIn ERP LN 6.1, you can use the new Print Documents by BP Payment Number (tfacr2400m000)session to print the open entries that were paid through a check or a range of checks. Thechecks are recognized by means of the business partner payment number which links thepayment to a receipt document and a remittance advice document.


▪ Rebates integrationRebates are created as open entries with negative amounts in the Accounts Receivablemodule. However, in ERP Baan5.0c, open entries are created through the scripts of thecorresponding Order Management sessions, and in ERP LN 6.1, the open entries are createdby the scripts of the Accounts Receivable module.Order Management passes on invoice requests for rebates to Central Invoicing.After processing in Central Invoicing, the rebates are sent to the customers in the form of salesinvoices or credit notes, and posted to Financials as open entries in the Accounts Receivablemodule. In this way, Order Management uses the standard invoicing functionality offeredthrough Central Invoicing, and no longer creates open entries directly in Financials.

▪ Recurring journal transactionsIn ERP Baan5.0c, you can set up recurring sales invoices, in the Recurring Sales Invoices(tfacr1514m000) session.In addition, in ERP LN 6.1, you can use the Recurring Journals (tfgld0140m000) session tocreate both recurring journal transactions and recurring invoices. The recurring transactionsare not based on an existing finalized transaction. In addition, you can set up recurring reversaltransactions that reverse the related recurring transactions.For details, refer to Recurring journals.

▪ Tax code for interest invoicesIf you select the Common Tax Code check box, for interest invoices baan uses the tax codeyou specify in the Interest Invoice Parameters (tfacr5101s000) session.If you clear the Common Tax Code check box, for interest invoices baan uses the tax codeof the invoice.


Financials

Independent of the selection of this check box, baan uses the default tax country of the businesspartner of the invoice.


Cash Management (CMG) module - Differences B50c/ERP61

This topic summarizes the differences between the Cash Management modules in ERP Baan5.0c andin ERP LN 6.1 and lists the differences that are not already discussed in other topics.


▪ Automatic direct debit procedureIn ERP Baan5.0c, the direct debit procedure requires frequent user interaction, whereas aspayments are processed automatically. In a business situation, processing a large volume ofdirect debits becomes very time consuming.In ERP LN 6.1, direct debits can be processed automatically, without user interaction, in thesameway as payments are processed automatically. The transactions that cannot be processedcorrectly are moved to a separate batch. After the direct debit run has finished, you can solvethe problems and then process this batch.For details, refer to Automatic direct debits process.

▪ Bank chargesIn ERP LN 6.1, you can define the bank charges of individual bank branches and you canindicate whether you or your pay-to business partner pays the bank charges.For details, refer to Bank charges.

▪ Bank master dataIn ERP Baan5.0c, bank data could be defined in Baan Common and in several sessions inBaan Finance.In ERP LN 6.1, the bank master data is defined centrally in the new Bank Branches(tfcmg0511m000) session in the Cash Management module.As the SWIFT code is one of the bank identifier codes used for international payments, inERP LN 6.1 the term SWIFT Code is replaced with the more generic term International BankID.

▪ Bank reference numbersThe use of bank reference numbers is a common banking practice for domestic transactionsin Norway and Finland. The bank reference number is a unique number that is used to identifythe invoice for which the payment is made. The bank reference number is communicated tothe customer on the invoice document and is always referred on the payment document.For details, refer to:▪ Bank reference numbers


Financials

▪ Bank reference numbers on purchase invoices

▪ Multiline entry of bank transactionsERP LN 6.1 supports multiline bank-transaction entry in the new Bank Transactions(tfcmg2500m000) session. To use this, you must create a transaction type of the Cash typefor the bank transactions and link the Bank Transactions (tfcmg2500m000) session to thetransaction type.

▪ Cash applicationIn ERP LN 6.1, the process of applying the cash to the open sales invoices was improved andspeeded up considerably. The new Remittance Advice (tfcmg2150m000) session was addedto handle multiline remittance-advice data entry. You can manually enter the data, and theassignments are confirmed through bank transactions.For details, refer to The cash application procedure.

▪ DiscountsIn ERP Baan5.0c, if you enter payments that were made later than the expiry date of thediscount period, ERP LN automatically enters zero in the discount field. This is correct, however,it is possible that on a late payment you still want to grant the discount to the customer. Tofind the original discount amount for the invoice, you must then search through the invoices.In ERP LN 6.1 Infor ERP displays the original discount amount of the invoice.

▪ Electronic bank statementsIn ERP Baan5.0c, the possibilities to use electronic bank statements (EBS) are limited. Forexample, ERP Baan5.0c can match the payments of electronic bank statements to the openentries only if there is a one-to-one relationship. If one payment line clears more than oneopen entry, you must balance the open entries manually.To improve the usability of electronic bank statements, the following enhancements wereimplemented in ERP LN 6.1:

▪ If you use electronic bank statements for several banks, the bank file is automaticallystored in the correct folder for this bank.

▪ In ERP Baan5.0c, you can assign the same series code to more than one transaction typeand transaction category. In other words, the series is not unique. In ERP LN 6.1, a seriescan be used only once. This is necessary because not all customers write the completesales invoice number, which consists of the transaction type and the series, in theDescription field. Through the unique definition, an automatic reconciliation can still becarried out, for example, even if the transaction type is missing.

▪ Infor ERP supports the German MT940 format prescribed by the bank.

▪ ERP LN can post payment differences for several invoices automatically.

▪ If several open entries are paid with one payment, the system can balance several openentries with one payment.

▪ Match electronic bank statementsIn the Match Electronic Bank Statements (tfcmg5212m000) session, the CreateUnallocated Receipt check box was added. If this check box is selected and the statementamount differs from the document amount, baan creates a new unallocated receipt for thestatement amount.


Financials

If this check box is cleared and the statement amount differs from the document amount,baan tries to match the statement with a document of which the amount is equal to thestatement amount.

▪ Electronic bank remittanceTo support Italian bank requirements, the following details were added to the Payment/ReceiptMethod (tfcmg0140s000) session:

▪ The Print Remittance Letter (Italy) check box.If this check box is selected, for payments with this payment method, baan generates aremittance letter during the automatic payment procedure.The remittance letter contains details about the invoices and the individual payments. Theremittance letter is printed with the Print Remittance Letters (tfcmg1270m000) session.The layout of the remittance letter answers the Italian requirements.

▪ The following new payment reports:

▪ 20: Remittance file Ricevuta Bancaria Elettronica (RI.BA)

▪ 21: Remittance file Rapporti Interbancaria Diretti (RID)

▪ 22: Bank Remittance file Ricevuta Bancaria Elettronica (RI.BA)

▪ 23: Bank Remittance file Rapporti Interbancaria Diretti (RID)If you select one of these reports, baan clears the Foreign Countries Allowed and theForeign Currencies Allowed check boxes and sets the Currency field to the company'seuro currency.

▪ Ledger account balances by accounting departmentTo support the reporting of ledger balances by accounting department, a Department fieldwas added to all Trade Notes sessions. For details, refer to To use an accounting office.

▪ Employee's expensesIn ERP LN 6.1, you can assign expenses to advance payments, for example, to settle anemployee's statement of expenses with a received advance.For details, refer to To assign employees' expenses to advance payments.

▪ Japanese bank file layoutIn ERP LN 6.1, you can generate bank payment files with the specific Japanese ZENGINKYOformat for the automatic payment process. For details, refer to Japanese bank file layout(p. 66) .

▪ Payment adviceThe following enhancements were made:

▪ Multiple unallocated payments and advance paymentsIn ERP Baan5.0c, a payment advice or a direct debit advice can contain only oneunallocated payment and only one advance payment. If you create a second unallocatedpayment or advance payment, ERP LN displays the error message "Record already exists."In ERP LN 6.1, you can include multiple unallocated payments and multiple advancepayments in a payment advice or direct debit advice. The composing criteria must beunique.


Financials

▪ Negative amountsIn ERP Baan5.0c, invoices and credit notes from Accounts Payable can be selected forpayment. Because many banks cannot handle the payment of a negative amount, thetotal amount of the invoices must exceed the total amount of the credit notes for a businesspartner. Else, the payment process halts during the audit step of the payment and ERPLN generates an exception error.In ERP LN 6.1 you can define special payment methods for which payments of negativeamounts are allowed. For example, Swedish banks offer the service to also accept negativepayments. The bank keeps the negative payment in storage for a period of time and clearsthe amount with positive payments from the same customer to the same business partner.After the agreed retention period has expired, the bank transfers any remaining amountto their customer.To allow negative amounts for payments, in the Payment/Receipt Method (tfcmg0140s000)session, you can select the Allow Negative Amount for Payment check box.

▪ Process invoices wihout a payment method or receipt methodIn ERP Baan5.0c, invoices to which no payment method or receipt method is linked cannotbe processed when you compose a payment advice or a direct debit advice. The invoiceswithout a payment method are moved to an error batch.In ERP LN 6.1, a payment advice or a direct debit advice can include invoices to whichno payment method is linked. In the Select Invoices for Payment (tfcmg1220m000) andthe Select Invoices for Direct Debit (tfcmg4220m000) sessions, you can select the IncludeInvoices Without Payment/Receipt Method check box.

▪ Selection on Terms of PaymentIn ERP Baan5.0c you cannot select invoices for payment advice based on the terms ofpayment that apply to the invoice.In ERP LN 6.1, the terms of payment were added to the selection criteria for paymentadvice. In the Select Invoices for Payment (tfcmg1220m000) session, you can enter arange of terms of payment.

▪ Pay-to business partner statisticsIn ERP Baan5.0c, no information is available about your payments to your suppliers.In ERP LN 6.1, you can generate and view your own payment performance to your suppliersin the same way as for pay-by business partner statistics. For details, refer to Pay-to businesspartner statistics (p. 74) .


▪ Standing order - copy the posting dataIn ERP Baan5.0c, if you manually create a payment schedule for a standing order, you mustenter the posting data separately for each payment schedule line.In ERP LN 6.1, if you copy a payment schedule, you can copy the posting data. If you copya standing order with an existing payment schedule to create a new standing order, ERP LNdisplays a question whether you also want to copy the posting data.


Financials


Cost Accounting (CAT) module - Differences B50c/ERP61

This topic describes the differences between the Cost Accounting module in ERP Baan5.0c and in ERPLN 6.1.

In ERP LN 6.1, the Cost Accounting module and the Financial Budget System modules were combinedin the new Controlling module.

▪ Allocation keysIn Cost Allocation, you can maintain allocation relations between dimensions, carry outallocation procedures according to the relations, and integrate the resulting amounts intobudgets or actual analyses. In ERP Baan5.0c, you must manually maintain cost allocationstructures that concern the same set of destination dimensions and as a result, occur multipletimes.ERP LN 6.1, allocation keys are introduced. An allocation key is a scheme to create allocationrelations automatically if the source of the allocation relations is known. A new allocation ruleset is used to collect rules of different types for the automatic generation of allocation relations.An allocation net can be created by using allocation keys, default allocation relations, orconsumption rules.Default allocation relations serve as a template for allocation relations with repeatingoccurrences regarding source and destination dimensions. Consumption rules are used togenerate outgoing allocation relations from a retrograde source following user provided roles.

▪ Cumulated cost allocationIn ERP LN 6.1, you can use cumulated cost allocation sheets to compare the amounts of aperiod with the accumulated amounts up to that period. You can use values that are aggregatedbased on a user-definable hierarchy. Before you make such a comparison, you must firstgenerate the hierarchical results. You can print the report based on the structures.

▪ Hierarchical resultsIn ERP Baan5.0c, you could not generate and evaluate hierarchical results for ledger accountsand dimensions based on hierarchical structures. This meant that must always use an OLAPtool or an external report application to view the results.ERP LN 6.1 includes a number of new sessions which provide quick access to the aggregatedreports of costs and deviations for a selected hierarchy. You can drill down to the sources onledger account and dimension level. The hierarchical results are generated and displayed inthe Cost Accounting module, based on the structures maintained in the Financial BudgetSystem module.

▪ Integration with PeopleIn ERP Baan5.0c, the only employee attribute that was defined in a separate session wasskills. In ERP LN 6.1 you define the employees’ personal data, skills, and labor rates in sessions


Financials

of the new People package. You can also use People to define roles and teams and assignthem to the employees. Roles grant authorization to employees to perform specific tasks andprocesses. Teams are used, for example, to distribute team hours, and to assign roles to theteam’s employees.In the Cost Accounting module, the dimensions and reference units have relations to workcenters, departments, and tasks in People through the defined integration relations.

▪ Reverse integrations to the General Ledger (GLD)In ERP Baan5.0c, you cannot revert and then reprocess the integration of iteration results tothe general ledger. If you detect mistakes after the integration to General Ledger, this can bea problem.For example, the following errors can occur:▪ Missing allocation relations▪ Incorrect allocated quantity▪ Missing cost categoryYou cannot reset the Integrated to GLD status in the Allocation Relations (tfcat400) table,and you must manually reverse the postings to the general ledger.In ERP LN 6.1, you can reverse previously created transactions in the general ledger andrepeat the integration process. Use the new Reverse Posted Cost Allocation Results(tfcat4214m000) session to reverse the integration of iteration results for a specific transactiontype.

Fixed Assets Management - Differences B50c/ERP61

This topic summarizes the differences between the Fixed Assets Management modules in ERP Baan5.0cand in ERP LN 6.1 and lists the differences that are not already discussed in other topics.


▪ Accelerated depreciationIn ERP LN 6.1, you can depreciate an asset by an extra amount in a specific year. In somecountries, accelerated depreciation is allowed to a maximum of 100 percent of the yearlystandard depreciation amount, until the asset value becomes zero. Accelerated depreciationreduces the depreciation time. Accelerated depreciation transactions must be posted to specificledger accounts.

▪ Asset Books - mark as RequiredIn the Asset Books (tffam1510m000) session, you can select the Required check box toindicate that the book is required according to the Default Books (tffam0510m000) session.You can mark asset books as Required to avoid that you select required books for deletion.

▪ Asset recapitalizationIn ERP LN 6.1, you can change some asset-related details before you recapitalize the asset.After the recapitalization, ERP LN bases subsequent transactions such as depreciation,transfer, and so on, on the new values.

▪ Declining balance percentageIn ERP Baan5.0c, you can only enter the depreciation percentage as an integer value.


Financials

In ERP LN 6.1, you can enter the depreciation percentage as a value with up to 5 decimalplaces, to provide the required precision in the fiscal and economical depreciation costs andbook values.

▪ Insured assets by locationNew in Infor ERP LN 6.1In ERP LN 6.1, you can print a report of the insured assets of each location. In the Print InsuredFixed Assets (tffam1461m000) session, you can select the Print by Location check box.In addition, if you clear the Include also assets partly in location range check box, assetsthat are only partly encompassed by the specified location range are not included on the report.

▪ Integration mapping schemeIn ERP Baan5.0c, not all fixed assets management mapping elements were available forledger account mapping and dimension mapping.In ERP LN 6.1, you can select all of the fixed assets management mapping elements for ledgeraccount mapping and dimension mapping. For example, you can use the Reason mappingelement to map an asset revaluation transaction to a specific revaluation ledger account.

▪ Intercompany transfersIn ERP LN 6.1, you can transfer fixed assets between financial companies. In both companies,the balance sheet is adjusted.Intercompany asset transfers provide for situations in which the use of a fixed asset is notrestricted to operations controlled by a single legal entity, or the asset is transferred from oneentity to another, and the balance sheet of the companies involved must reflect shared andtransferred assets.

▪ Invoice detailsIn ERP Baan5.0c, for assets transactions for which an invoice exists, you can display theinvoice number. However, to view the invoice details you must manually find and view theinvoice in the Accounts Payable module.In ERP LN 6.1, you can zoom to the invoice details from the Capitalization/Transfer - Details(tffam8510s000) session.

▪ Map asset books for transferNew in Infor ERP LN 6.1If you transfer assets from one company to another, you can map the asset books of thesource company to the target company. Use the new Mapping Books for Transfer(tffam0520m000) session to link the source and destination books for all valid companiesbefore transferring. This session is used to transfer assets from one company to another.The asset books in the destination company are created using the values in the sourcecompany's asset books. You do not have to link the books when you select the destinationcompany, even if the books are not required. If the destination book is a posting book, thesource book must also be a posting book.

▪ Salvage value as a percentageIn ERP Baan5.0c, you can only enter the salvage amount.In ERP LN 6.1, you can also enter the salvage value as a percentage.


Financials

▪ Suspended depreciationIn ERP LN 6.1, you can suspend depreciation for specific periods. In some countries, you cansuspend depreciation for periods during which the asset is not used for any reason. You canperform the depreciation in later periods.

▪ Tag number must be uniqueIn ERP Baan5.0c, you can enter any number as the tag number for an asset, even if thenumber is already in use as tag number for another asset.In ERP LN 6.1, if you enter a new tag number in the Asset (tffam1100s000) session, InforERP checks whether the tag number is unique. If the number is already in use, ERP LNdisplays a warning.For example, if you use the tag number for your inventory number, it is important to ensurethat the tag number is unique. In a multicompany structure, Infor ERP also checks whetherthe tag number is unique across the companies.

Financial Budget System (FBS) module - Differences B50c/ERP61

This topic describes the differences between the Financial Budget System module in ERP Baan5.0cand in ERP LN 6.1.

In ERP LN 6.1, the Cost Accounting module and the Financial Budget System modules were combinedin the new Controlling module.

In ERP LN 6.1, the flexible budget functionality was enhanced.

The most important changes are:

▪ Copy a range of reference unitsThe same reference units are often used for several dimensions. In ERP Baan5.0c, you cannotcopy a range of reference units from one dimension to a range of other dimensions. To usea number of reference units for a range of dimensions, you must define the reference unitsfor the first dimension and then use Duplicate Group to copy the reference units to the otherdimensions separately.In ERP LN 6.1, you can use the new Copy Reference Units per Dimension (tffbs0230m000)session to copy a range of reference units of a specific dimension type and dimension to arange of other dimensions of the same dimension type. ERP LN adds the reference units ofthe source dimension to the destination dimensions. If the destination dimensions alreadyhave reference units linked to them, the copied reference units are added to these.

▪ Import performance figures from logistic packagesPerformance figures from the ERP LN 6.1 logistic package can be imported in the CostAccounting module to be used in the allocation of actual costs. The calculated rates andsurcharges can be integrated with the logistic package, and calculated variances can be postedto dimensions in the General Ledger module.

▪ Performance driven budgetYou can create a performance driven budget. Based on a single dimension budget and theactual costs, ERP LN 6.1 calculates the allowed costs, which results in a variance analysis.


Financials

In the flexible budget, rates and surcharges can be determined, which can be integrated withthe ERP LN 6.1 logistic package.

▪ Reverse integrations to the General Ledger (GLD)In ERP Baan5.0c, you cannot revert and then reprocess the integration of iteration results tothe general ledger. If you detect mistakes after the integration to General Ledger, this can bea problem.For example, the following errors can occur:▪ Missing allocation relations▪ Incorrect allocated quantity▪ Missing cost categoryYou cannot reset the Integrated to GLD status in the Allocation Relations (tfcat400) table,and you must manually reverse the postings to the general ledger.In ERP LN 6.1, you can reverse previously created transactions in the general ledger andrepeat the integration process. Use the new Reverse Posted Cost Allocation Results(tfcat4214m000) session to reverse the integration of iteration results for a specific transactiontype.

▪ Sequence numbers for single dimension budgetIn the Ledger Account Structure by Dimension (tffbs0120m000) session, you can create aledger account structure by dimension with sequence numbers to have a specific sequenceof the ledger accounts used for budgeting. However, in ERP Baan5.0c, if you create a singledimension budget for a specific combination of dimension and reference unit, all the ledgeraccounts in the ledger account structure are copied without the sequence number. ERP LN6.1 sorts the ledger accounts by ledger account code.ERP LN 6.1 retains the sequence defined in the ledger account structure when you create asingle dimension budget.

Financial Statements (FST) module - Differences B50c/ERP61

This topic describes the main difference between the Financial Statements module in ERP Baan5.0cand in ERP LN 6.1.

In ERP Baan5.0c, in the Process Financial Statement Values (tffst1205m000) session, you could onlyprocess a single financial statement and a single budget at a time.

In ERP LN 6.1, you can enter ranges of financial statements and budgets for processing.

General Ledger (GLD) module - Differences B50c/ERP61

This topic summarizes the differences between the General Ledger module in ERP Baan5.0c and inERP LN 6.1 and describes the differences that are not already discussed in other Differences topics.


Financials


▪ Additional investments on fixed assetsIn ERP Baan5.0c, to register a purchase invoice, you could not specify a quantity of zero onthe purchase invoice line. In ERP LN 6.1, if you register the first purchase invoice, you canspecify a quantity of one and for subsequent invoice lines related to the same asset, you canspecify a quantity of zero.For example, you acquire an asset such as a truck, which you pay in monthly installments.Every month, you register a purchase invoice for the installment. In ERP Baan5.0c, for everyinvoice line, you must enter a quantity of at least one, so after ten months, ERP LN hasregistered that you acquired ten trucks. In ERP LN 6.1, you can enter a quantity of one for thefirst purchase invoice and for subsequent invoices, you can specify a quantity of zero.

▪ Bank chargesIn ERP LN 6.1, you can define the bank charges of individual bank branches and you canindicate whether you or your pay-to business partner pays the bank charges. To view the taxamounts on the bank charges by bank branch, you can define the bank branch as a businesspartner. In the Tax Analysis (tfgld1520m000) session, you can print the tax analysis by pay-tobusiness partner report.For details, refer to Bank charges.

▪ Delete reconciliation data during postingIn the Integration Parameters (tfgld4150s000) session, you can select the Delete LoggedElements during Posting check box. If this check box is selected,, baan deletes the loggedintegration elements from the Logged Elements (tfgld 481) table when the integrationtransactions are posted. A large amount of logged data that is no longer needed can have anegative impact on the performance of the processes that handle integration transactions andreconciliation transactions. To save space and avoid a possible low performance, you canselect this check box.

▪ Cash flow statementsIn Japan, according to the Securities and Exchange law, companies are obliged to submit aconsolidated cash flow statement periodically. In ERP LN 6.1, you can use a cash flow reasonto mark transactions that contribute to the cash flow. In the new Cash Flow History(tfgld2519m000) session, you can view the transactions that contribute to the cash flow andfrom this session, you can start printing the report.For details, refer to Cash flow statement.

▪ Currency differencesThe following improvements were made:

▪ Exchange gain and loss on integration transactions is posted to a separate ledger account.

▪ Currency differences are posted to Currency Difference contra accounts which you assignto the ledger accounts in the Chart of Accounts (tfgld0108s000) session. As a result, thereconciliation data for currency differences is more accurate.

▪ The transaction occurrence and the transaction amount are always available on the ledgeraccount, so that the calculate currency differences process can be performed.


Financials

▪ In the General Ledger, you can print an interim table of the calculate currency differencesprocess.

▪ Advance payments and receipts and unallocated payments and receipts are consideredfor the currency differences calculations.

▪ in Accounts Payable and Accounts Receivable, you can write off payment differences andcurrency differences for specific invoices.

For details, refer to Currency differences interim accounts

▪ Dimension accountingIn ERP LN 6.1, dimension accounting has been extended and the dimension accounting setupfor control accounts is more flexible. The following enhancements were made:

▪ For the dimension types linked to the control accounts, ERP LN posts the open entries tothe dimensions specified on the invoice header. You can specify the default dimensionsfor sales invoices and purchase invoices on several levels. To determine the dimensions,Infor ERP searches these levels from the most specific, the invoice, to the least specific,the financial business partner group.

▪ In ERP LN 6.1, the Interim Closing account is known as the Retained Earnings account.In the Company Parameters (tfgld0103s000) session you can use the DimensionAccounting on Retained Earnings check box to specify the dimensions for the RetainedEarnings account on company level. If you clear this check box, Infor ERP derives thedimensions for retained earnings from the dimension history.

▪ IFRS segment reportingThis topic is part of the effort to implement the International Financial Reporting Standards(IFRS) requirements. To support dimension accounting also for tax amounts, tax amountsare posted to the dimensions that you link to the control accounts. The dimensions thatyou can still enter in the Posting Data for Multiple Tax Codes (tfgld0170s000) and PostingData for Tax Codes (tfgld0171s000) sessions are only used if mandatory dimension typesare linked to the tax accounts and the corresponding dimensions are not defined for thecontrol account.

For details, refer to Dimension accounting.

▪ DimensionsIn ERP LN 6.1, you can you can import the codes of various entities and properties definedin the Tables module of Common to create the dimensions. In the Dimensions (tfgld0510m000)session, on the specific menu, click Import Dimensions.For example, for the Total Items dimension type, you can import the item groups, which resultsin the addition of as many dimensions as item groups, and with the item group codes.

▪ Finalize batches for specific transaction typesIn ERP Baan5.0c, in the Global Selection of Batches for Finalization (tfgld1210m000) session,you can select a ranges of batches to be finalized. However, you cannot finalize the transactionsof specific transaction types.In ERP LN 6.1, you can select a range of transaction types for which you want to finalize thebatches, for example, purchase invoices, journal, or bank transactions. To finalize the batchesfor a single transaction type, select the same transaction type in the From and To fields.


Financials

Note: If you specify a transaction type or a range of transaction types and the a batch containsone or more transactions of which the transaction types are outside the range, ERP LN cannotfinalize the batch.

▪ Integration mapping schemeIn ERP LN 6.1, the integration transactions (tror/fitr combinations) existing in ERP Baan5.0care represented by a whole new set of integration document types, and many new integrationtransactions were added. As a result, if you migrate from ERP Baan5.0c to ERP LN 6.1, youmust set up a new integration mapping scheme.For details, refer to Financial integrations.

▪ Intercompany settlementIntercompany settlement transactions are the automatic postings in one financial company tointercompany billing and clearing accounts instead of invoices generated for sales/purchasetransactions between the entities of two logistic companies. Intercompany settlementtransactions only apply to purchase and sales transactions between logistic companies in amultilogistic/single-financial company structure.In ERP Baan5.0c, goods transfer between logistic companies required sales orders andpurchase orders, which resulted in open entries that must be cleared by generating a paymentin the buying logistic company.In ERP LN 6.1, in a multilogistic/single finance company structure the intercompany invoicingprocess can be simplified by generating intercompany settlement transactions. The sales andpurchase transactions can concern WIP transfers and inventory transfers.For details, refer to Intercompany settlement.

▪ Journal booksItalian law requires companies to submit a journal book report which contains all financialtransactions in date sequence. The journal book is used for internal and external audits, duringlawsuits, and so on. Both a detailed report and a summary report are required. The reportpages and the transaction lines must be numbered sequentially. In ERP LN 6.1, you cangenerate and print journal books and journal book summaries.For details, refer to Journal book - overview.

▪ Journal reportsTo support financial reporting according to Japanese requirements, the following new sessionsand reports were added:

▪ Print Journal Report for Document Date (tfgld1412m000)

▪ Print Journal Report for Document Period (tfgld1413m000)

▪ In the Print Finalized Transactions - Ledger Account (tfgld1406m000) session, the FinalizedTransactions (Japan) report, which shows the ledger account balance before and afterthe posting of every transaction.

▪ Journal voucher entryTo provide fast and easy way to enter journal vouchers, in ERP LN 6.1, the Journal Vouchers(Multiple Lines) (tfgld1115m000) session was completely redesigned. Most of the fields alsopresent in the Journal Vouchers (tfgld1103s000) session were added to the Journal Vouchers(Multiple Lines) (tfgld1115m000) session. On the specific menu, you can click a vast rangeof commands to start journal voucher-related sessions.


Financials

▪ Journal vouchers for reference currenciesIn a multicompany structure with multiple financial companies, it can be required to createjournal vouchers with a transaction amount of zero and amounts in the reporting currenciesonly. For example, you can use this functionality to manually eliminate currency differencesin the general ledger or to revaluate the reporting currency amounts in a different way thanby writing off currency differences.In ERP LN 6.1, you can use the new the Journal Vouchers for Reporting Currencies(tfgld1125s000) session to create journal vouchers with amounts in the reporting currenciesonly.

▪ Ledger account detailsIn the Chart of Accounts (tfgld0108s000) session, the following check boxes were added:

▪ Daily BalanceTo maintain daily balance information for a ledger account, you can select this check box.You can only select this check box for ledger accounts of level 0 (zero).

▪ Balance by Business PartnerTo maintain daily balance information by business partner on the ledger account, you canselect this check box. You can only select this check box for ledger accounts of level 0(zero).You can use various sessions to display the distribution of the ledger history by periodand/or by business partner

▪ Include in Journal BookThis field is only relevant for integration accounts. Usually, integration transactions mustbe included in the journal book book. However, for non-statutory integration transactions,you can clear the check box. If you clear the check box, you must define a schedule forautomatic transactions for the ledger account, to balance the journal book entry.

▪ Ledger historyThe new Ledger History (tfgld3501m000) session is a completely redesigned version of theprevious Ledger History (tfgld3501s000) session. The new session displays various views onthe ledger history and provides easy access to the related ledger history sessions.For details, refer to Ledger history.

▪ Lower cost or market value methodFor the inventory valuation in the balance sheet, in some countries the inventory value basedon any of the inventory valuation methods must be compared with the currenct market price.If the currenct market price is lower that the valuation according to one of the internal valuationmethods, the whole inventory of an item must be valuated for the balance sheet with thecurrenct market price. This method of valuating items in inventory is called the Lower Cost orMarket Value method. The Lower Cost or Market Value method is legally required in severalcountries, for example, the European countries, the US, and Japan.In ERP LN 6.1, inWarehouseManagement, the Perform Inventory Valuation (whina1210m000)session and its resulting reports were changed so that you can optionally apply the lower costor market value method.


Financials

▪ Period handling for integration transactionsIn ERP Baan5.0c, ERP LN generated an error message if you created integration transactionsfor a period that was Closed.In ERP LN 6.1, posting integration transactions to the next open period is better controlled.For details, refer to Period handling for integration transactions.

▪ ReconciliationERP LN 6.1, provides a complete and consistent reconciliation functionality. Instead ofgenerating various reports of the integration transactions, you can use the reconciliation reportsgenerated in the new Operations Management - Financial Reconciliation (tfgld4595m000)session. In addition, in ERP LN 6.1 currency differences are posted to separate accounts sothat the reconciliation data is more accurate.For details, refer to Reconciliation overview.

▪ Reconciliation of PCS Work in Process (WIP)You can use the new Print Reconciliation Data PCSWork In Process (tfgld4495m300) sessionto print various reports that you can use for financial analysis of the work in process (WIP)values of PCS projects.

▪ Recurring journal instructionsIn the Recurring Journal Instructions (tfgld0143s000) session, the Create Instructionscommand was added to the specific menu. This command starts the Create Instructions(tfgld0143s100) session, which you can use to generate instructions for a range of months orfiscal periods.In ERP Baan5.0c, you cannot change a single detail of a recurring transaction instruction. Forexample, if you only want to change the amount, you must delete the old instruction and setup a new instruction for the remaining periods.In ERP LN 6.1, you can change an existing recurring transaction instruction. If you changetransaction details in the Recurring Transaction Instructions (tfgld1107m000) session, the newdetails apply to the remaining periods.

▪ Reports for periods in multiple yearsIn ERP Baan5.0c, reports of finalized transactions are restricted to the periods of a singlefiscal year.In ERP LN 6.1, such reports can cover multiple fiscal years. You can enter a range of financialperiods in a number of fiscal years in the following sessions:

▪ Print Finalized Transactions - Ledger Account (tfgld1406m000)

▪ Print Finalized Transactions - Dimension/Ledger (tfgld1407m000)

▪ Transaction type seriesTo support the VAT book functionality, the following fields were added to the Transaction TypeSeries (tfgld0114m000) session:

▪ Tax YearThe tax year of the document number. For transaction types linked to a VAT book, thisfield is mandatory. VAT book transactions can only be processed if the tax year of thedocument number equals the transaction entry date of the batch.


Financials

▪ Last Batch DateThe transaction entry date of the most recent batch. For transaction types linked to a VATbook, Infor ERP stores the last batch date.

For details, refer to VAT book - overview.

▪ VAT booksThe VAT book is a legal report of all value added tax (VAT) transactions of a company, in datesequence. The transactions can be grouped by tax articles, which typically group transactionsthat have the same tax percentage. In ERP LN 6.1, you can prepare and submit a VAT bookand a VAT liquidation report, which shows the net VAT amount payable to the tax authoritiesfor the report period.For details, refer to VAT book - overview


Financials


Financials


Aggregation and disaggregation

Centralized multisite planningTo prepare for aggregation and disaggregation of planning data to and from family items, you mustdefine the aggregation relationships in the Aggregation Relationships (cprpd3110m000) session.

In ERP Baan5.0c, the scenario codes of the companies involved in a multisite environment, and betweenwhich you want to aggregate or disaggregate planning data, must be identical. Because the centralmultisite scenario cannot be the actual scenario, setting up a separate logistic company was mandatoryfor this central scenario.

In ERP LN 6.1, however, you can use the Scenario and the Sub Scenario field to set up an aggregationstructure in a multisite environment.

You can also use these fields to aggregate data from one scenario to another scenario in a single-siteenvironment.

For more information, refer to The use of centralized multisite planning.

Disaggregation Rule: Pro rateIn ERP LN 6.1, a new option for the Rule field in the Disaggregate Channel, Plans & Orders(cprmp2260m000) session is available: the Pro Rate rule.

baan disaggregates the planning quantities in a proportional way, based on the current values in theitem master plan. If sub-item 1 has the most in the current situation, the sub-item will have the mostafter disaggregation.

The Pro Rate disaggregation rule enables you to split planning data of a family plan item based on theoriginal quantities of the underlying (individual) plan items.

For more information, refer to Disaggregation rules


4Chapter 4Enterprise Planning

The generation of aggregation relationshipsIn ERP LN 6.1, the Generate Aggregation Relationships (cprpd3211m000) session is available to assistyou to define aggregation relationships. This session is particularly useful if you have a family item withan extensive range of subitems.

Allow multiple sources per requirement

Changed in Infor ERP LN 6.1In ERP LN 6.1, in the Generate Order Planning (cprrp1210m000) session, the Allow Multiple Sourcesper Requirement check box is added.

The same option is available in the Generate Order Planning (Item) (cprrp1220m000) session.

▪ If you select the Allow Multiple Sources per Req. check box in the Generate Order Planning(cprrp1210m000) session or the Generate Order Planning (Item) (cprrp1220m000) session,baan uses the percentages to divide a single requirement over the various sources.

▪ If you clear the Allow Multiple Sources per Req. check box, baan tries to approximate thepercentages as closely as possible, but assigns each requirement to one source. In otherwords, baan does not split planned orders.

Boundaries on supply sources

Sourcing strategies in ERP Baan5.0cIn ERP Baan5.0c, you can define sourcing strategies in the Sourcing Strategy cprpd7110m000) session.

A sourcing strategy defines the distribution of the planned supply of a plan item over the followingsources:

▪ Production▪ Purchase▪ Distribution

Boundaries on supply sources in ERP LN 6.1In ERP LN 6.1, you can also define boundaries for each supply source in the Sourcing Strategy(cprpd7110m000) session.

To define boundaries, you enter a minimum volume and a maximum volume for any of the supplysources, Production, Purchase, and Distribution.

You can use the boundaries in two ways:

▪ As a limit for a particular time period, for example, several days, months, or weeks

▪ As a limit for the entire effectivity period of the sourcing strategy


Enterprise Planning

Capacity and component CTP

Graphical CTP browserIn ERP LN 6.1, in the ATP Handling (tdsls4899m000) session, you can start the Capable to PromiseOverview (cprrp4899m000) session to browse the CTP information in a tree-structured browser.

CTP checks without master planIn ERP Baan5.0c, the extended capable-to-promise functionality was only available for items for whichyou maintained an item master plan.

In ERP LN 6.1, Capacity CTP checks and component CTP checks are now also available for itemswithout master plan. (However, you still need a resource master plan to enable capacity CTP checking).

CTP checks for clustered itemsCapacity CTP checks and component CTP checks are also available for clustered items, with somerestrictions, as described in the Component CTP and capacity CTP for clusters online manual topic.

CTP reservationsA component CTP reservation is defined as follows:

▪ The item quantity reserved to be used as critical components for the (as yet unplanned)production of other items.

In ERP Baan5.0c, if component CTP and/or capacity CTP were used to make more of an item availableto promise, the Cumulative ATP field in the Item Master Plan (cprmp2101m000) session was reset tozero.

Now, in ERP LN 6.1, if component CTP reservations and/or capacity CTP reservations are made for aplan item, the Cumulative ATP field remains negative, and the expected additionally produced quantityof the item is stored in the CTP Reservation Receipts field. (See also Cumulative ATP field Help).

The component CTP reservation is made when the ATP data in an item master plan is updated and thefollowing is true:

▪ The cumulative ATP for plan item A drops below zero.

▪ The plan item settings for item A are set to enable component CTP checks.

▪ The bill of critical material for item A contains item B.

▪ Item B is defined as CTP critical in the plan item settings.

In this case, a component CTP reservation is recorded for item B, and the ATP of item B is reducedaccordingly. Item A's cumulative ATP is reset to zero.

Note

To guarantee that ERP LN can carry out an ATP check correctly, you must fill theWarehouse field inthe Bill of Critical Materials (cprpd3120m000) session. ERP LN explodes the ATP of a main item to plan


Enterprise Planning

items that have the same cluster as the warehouse you specified on the bill of critical materials of themain item.

A new CTP Reservation Receipts field is included in the Item Master Plan (cprmp2101m000) session.

New session: CTP Reservations (cprrp0111m000). Use this session to list the component CTPreservations that ERP LN made for a particular manufactured plan item.

CTP based on BOM and routing, in stead of on the BCMIn ERP Baan5.0c, the cumulative ATP was always based upon the bill of critical materials and the billof critical capacities.

ERP LN 6.1 takes into account the BOM and the routing to perform CTP checks in the following situations:

▪ The ordered item is not critical in master-based planning.▪ The ordered item is not a generic item.

▪ ERP LN carries out the check inside the order horizon.

CTP for generic itemsIn ERP LN 6.1, if you request the CTP of a generic item during sales order entry, ERP LN configuresthe item (in memory, without permanently storing the configuration) to check CTP on components andresources, based on customized BOM and customized routing.

ATP checking for all components in the BCMIn ERP Baan5.0c, ATP checking was available only for items for which the Critical in Master Planningcheck box in the Item Production Data (tiipd0501m000) session was selected.

In ERP LN 6.1, ATP checking is available for all materials in the bill of critical materials, including thematerials that you added manually.

Company switching

Changed functionalityIn ERP LN 6.1, you can easily switch to another company in the following sessions:

▪ Item Master Plan (cprmp2101m000)▪ Item Order Plan (cprrp0520m000)▪ Resource Order Plan (cprrp0530m000)

To switch to another company, on the specific menu, click Change Company.


Enterprise Planning

Cumulative Order Lead Time (COLT)

Items - Planning (cprpd1100m000)In ERP LN 6.1, the Items - Planning (cprpd1100m000) session includes the following new fields todisplay the item's cumulative order lead time:

▪ Cumulative Order Lead TimeThe cumulative order lead time (COLT) is the total value of the item purchase lead time andthe cumulative production lead time of all components.

▪ Non-Critical COLTThe noncritical cumulative order lead time is the total value of the item purchase lead timeand the cumulative production lead time of all noncritical components.

Enterprise Planning uses the cumulative order lead time and the noncritical cumulative order lead timeto determine the minimum value of the order horizon and the planning horizon.

Check Horizons (cprpd1200m000)In ERP LN 6.1, this new session recalculates the following fields in the Items - Planning (cprpd1100m000)session:

▪ Cumulative Order Lead Time▪ Non-Critical COLT

Based on the updated value of the COLT, this session also checks the values of the following fields inthe Items - Planning (cprpd1100m000) session:

▪ Order Horizon▪ Planning Horizon

Optionally, this session automatically corrects the values of the order horizon and the planning horizon.

Date-effectivity on item type

Default supply source in ERP Baan5.0cIn the Plan Item Data (cprpd1500m000) session in ERP Baan5.0c, you can set the Default SupplySource field to Production, Purchase, or Distribution.

If Enterprise Planning cannot find a sourcing strategy, Enterprise Planning uses the default supplysource.

Date-effective item types in ERP LN 6.1In the Items - Planning (cprpd1100m000) session in ERP LN 6.1, you can set theDefault Supply Sourcefield to Production/Purchase or Distribution.

If no valid sourcing strategy is present, baan checks the value of the Default Supply Source field inthe Items - Planning (cprpd1100m000) session.


Enterprise Planning

This default supply source is independent of the value that you specified in the Item Type field in theItems - General (tcibd0501m000) session.

The Default Supply Source field can have the following values:

▪ DistributionIf the default supply source is Distribution, Enterprise Planning generates only planneddistribution orders.

▪ Production/PurchaseIf the default supply source is Production/Purchase, Enterprise Planning searches theDate-Effective Item Data (tcibd0510m000) session, and uses the item type specified for theorder finish date.If the default supply source is Production/Purchase and no valid date effectivity lines arepresent for the order finish date, baan falls back on item type that you defined in the Items -General (tcibd0501m000) session.

You can use date-effective item data to change an item's item type frommanufactured item to purchaseditem, and vice versa, on exactly defined dates.

Distribution planning and multisite planning

Warehouse orders for multisite distribution ordersIn ERP Baan5.0c, if a planned distribution order 's supplying site differs from the receiving site, EnterprisePlanning always transfers the planned distribution order to a purchase order.

In ERP LN 6.1, you can transfer a planned distribution order that has different supplying and receivingsites to a purchase order or to a multisite warehousing order.

To set this process up, set the Type of Order to be Generated by Enterprise Planning field in theEntity - Entity Relationships (tcemm2110m000) session to one of the following values:

▪ Purchase Order▪ Warehouse Transfer▪ Not Applicable

For more information, refer to To transfer multicompany distribution orders.

Copy multilevel supplying structure from cluster to clusterIn ERP LN 6.1, the Copy Multilevel Supplying Structure (cprpd7200m000) session provides an easyway to copy all of a plan item's supplying relationships to the corresponding plan item in another cluster.


Enterprise Planning

Fixed delivery moments

New concepts

▪ Fixed delivery momentA specific date and time that you define as a firm and unchangeable time point on which goodsmust be delivered to you. If you defined fixed delivery moments for a plan item, ERP LN setsthe unconstrained planned finish date back to the nearest fixed delivery moment.You can define incidental fixed delivery moments, or define a pattern of recurrring fixed deliverymoments.

Delivery moments ERP Baan5.0cIn ERP Baan5.0c, the planned delivery dates and the planned finish dates of planned orders weredetermined solely by the date the items were required. To influence the finish dates, you had to entera fixed delivery date for a planned order.

Fixed delivery moments in ERP LN 6.1In ERP LN 6.1, you can specify that an item must be delivered on a fixed moment, for example, alwayson Friday afternoons. For more information, refer to Fixed deliveries in Enterprise Planning.

Master planning

This topic describes miscellaneous differences in the sessions for master-based planning.

Item master planIn ERP LN 6.1, in the Item Master Plan (cprmp2101m000) session, you can easily switch to anotherlogistic company.

To change to another company, on the specific menu, click Change Company.

Move Master Plan to Planned Orders

▪ Name changeIn ERP LN 6.1, the Move Master Plan to Planned Orders session is renamed Convert MasterPlan to Planned Orders (cprmp2240m000) session.

▪ New check box: Move in Multi-siteIn ERP LN 6.1, the Convert Master Plan to Planned Orders (cprmp2240m000) session has aMove in Multi-site check box.If you select this check box, baan also moves master plans to planned orders in each plansite that falls in the specified range of sites.

▪ The following conditions apply:

▪ This option is available only if the specified scenario is a central multisite scenario.


Enterprise Planning

▪ baan only takes into account the plan sites that are linked to the central multisitescenario involved.

▪ In each plan site involved, baan only takes into account the master plans that exist inthe plan site's local scenario.

▪ New check box: Update Master PlansIn ERP LN 6.1, the Convert Master Plan to Planned Orders (cprmp2240m000) session hasan Update Master Plans check box.If this check box is selected, baan automatically updates the itemmaster plan and the resourcemaster plan after baan moved the purchase plan and/or the production plan to planned orders.

Sales schedulesThe master-based planning takes the demand from sales schedules into account.

For more information, refer to Sales schedules in Enterprise Planning

Material-routing relationships

For a manufactured item, you can define multiple routings. Every routing consists of a different seriesof operations.

In ERP LN 6.1, you can define material-routing relationships in the new BOM Line - Material-RoutingRelationships (tibom0140m000) session to determine for every routing on which operation a specificmaterial must be present on the shop floor.

The order-planning process takes the material-routing relationships into account.

Offsetting logic in master-based planning

IntroductionBecause the production process obviously takes time, the planning of a critical material requirementmust fall sometime before the planned supply of the end item. Assuming that the supply of the end itemis evenly distributed over the plan period, the material requirement is shifted back in the past with thelead-time offset recorded in the BCM of the end item.

As a result, the master-planning engine often splits a material requirement over multiple plan periods.

This procedure is applicable in both ERP Baan5.0c and ERP LN 6.1.

Details of the procedure in ERP Baan5.0cIn ERP Baan5.0c, the master-planning engine simply distributes the material requirements over relevantplan periods.


Enterprise Planning

ExampleTake for example, the following situation:

▪ You manufacture carts and for each cart, you require two axles, which you defined as criticalcomponents.

▪ You defined weeks as plan periods. Each week has five working days.

▪ The lead-time offset for the axles is 1.5 weeks.

▪ In week 47, you have a demand for five carts.

The master-planning engine plans as follows:

▪ The total material requirement for axles is 10 axles (5 × 2).

▪ The planning engine distributes this requirement as follows:

▪ Week 45: Production is started to manufacture five axles

▪ Week 46: Production is started to manufacture another five axles

A consequence of this procedure is, that the quantity of axles planned in week 5 does not match a wholenumber of carts.

Details of the procedure in ERP LN 6.1In ERP LN 6.1, master-planning engine rounds the quantity of a critical material requirement plannedin a plan period and makes sure that the material quantity ordered in one plan period matches a wholenumber of parent items.

ExampleSuppose the situation is identical to the previous example.

The master-planning engine plans as follows:

▪ Like in the previous example, the planning engine distributes this requirement as follows:

▪ Week 45: Production is started to manufacture five axles

▪ Week 46: Production is started to manufacture another five axles

▪ In an additional step, the master-planning engine rounds the material quantity in accordancewith the unit set that you defined for the parent item in the Items - General (tcibd0501m000)session. The quantity of "5 axles" corresponds with "2.5 carts". "2.5 carts" is rounded up to "3carts". For 3 carts, you require 6 axles.

Order grouping

This topic describes the purpose of order grouping.

New in ERP LN 6.1An order group in Enterprise Planning is a collection of planned production orders. You can use ordergroups as work packages to reduce the handling effort. You can create an order group by selecting


Enterprise Planning

planned production orders on the basis of certain selection criteria. You can manually add or removeplanned production orders to or from an order group.

You can transfer all planned production orders within an order group with a single command.

You can use order groups in Enterprise Planning to create order groups for production orders in theShop Floor Control module.

Order pegging

New functionalityPegging relations contain information about which planned order supplies which order. Pegging relationsinvolve both component-main item relationships and supplying relationships between sites.

The following new sessions are introduced:

▪ The Generate Pegging Relations (cprrp0240m000) session is a tool to generate pegginginformation.

▪ The Browse Order Pegging (cprrp0740m000) session enables you to use a graphical browserto browse through the pegging relations.

Order planning

This topic describes the differences between the order-based planning procedure in ERP Baan5.0c andERP LN 6.1.

These differences apply mainly to the functionality of the following sessions:

▪ Generate Order Planning (cprrp1210m000)

▪ Generate Order Planning (Item) (cprrp1220m000)

Date range for Generate Order PlanningIn the Generate Order Planning (cprrp1210m000) session, you can no longer specify a date range. Theorder generation is always carried out from the scenario start date to the scenario end date.

Item selection for order planningIn the Generate Order Planning (cprrp1210m000) session, the functionality of the Use Bottom-Up ItemSelection and Use Top-Down Item Selection check boxes was enhanced.

In ERP LN 6.1, these options also take into account:

▪ Project items▪ Generic items▪ Supplying relationships

For more information, refer to RRP run, item selection.


Enterprise Planning

Forecast consumptionThe effect of the values of the Backward Forecast Consumption and the Forward ForecastConsumption fields has been adapted. If an item does not have an item master plan, the demandforecast for the day in which the planned or actual delivery dates of a customer order fall is alwaysconsumed, regardless of the value entered in these fields.

For more information, refer to Forecast Consumption.

Freight Management integrationIn ERP LN 6.1, you can generate freight orders for planned distribution orders during the generation ofplanned orders.

ERP LN does not generate freight orders for planned purchase orders or for planned production orders.

For more information, refer to Integration of Freight Management with Enterprise Planning.

Week-bucket planningIn ERP LN 6.1, week-bucket planning is no longer supported.

Purchase schedules and sales schedulesThe order-based planning can also generate or refresh purchase schedules.

The planning process also generates supply for sales orders that come from sales schedules.

For more information, refer to the following online manual topics:

▪ Purchase schedules and Enterprise Planning▪ Sales schedules in Enterprise Planning

Planned orders

This topic describes the differences between ERP Baan5.0c and ERP LN 6.1, related to planned orders.

Most of these differences apply to the functionality of the Planned Orders (cprrp1100m000) session.

To change suppliersIn ERP LN 6.1, if you change the buy-from business partner (supplier) or the ship-from business partnerin the Planned Orders (cprrp1100m000) session, baan asks if you want to change the buy-from businesspartner in the Item - Purchase (tdipu0101m000) session as well, provided the plan item is a project itemand no item-business partner data is present.

The same functionality existed in Infor Baan IV.


Enterprise Planning

Repair planned ordersYou can use the new Repair Planned Orders (cprrp3200m000) session to repair corrupted data. Datacorruption can occur with multisite (multi-company) transactions performed on multiple servers. Formore information, refer to the Repair Planned Orders (cprrp3200m000) session Help.

Copy planned orders to other scenariosIn ERP LN 6.1, the new Copy Planned Orders to Scenarios (cprrp1240m000) session helps you to setup a new scenario to study various planning strategies.

You can start that session directly from the following sessions:

▪ Planned Orders (cprrp1100m000)▪ Item Order Plan (cprrp0520m000)▪ Resource Order Plan (cprrp0530m000)

Resource capacity planning

This topic describes the differences between ERP Baan5.0c and ERP LN 6.1, related to the use ofresources.

New conceptsIn this topic, the following new terms are used:

▪ resource order planA period based overview of the capacity utilization of a specific resource and of the ordersthat require resource capacity.The resource order plan can contain the following order types/entities:

▪ Critical capacity requirements from Enterprise Planning

▪ Planned production orders from Enterprise Planning

▪ Production orders from the Shop Floor Control module of Manufacturing

▪ Project activities from the Project Control module of Manufacturing

▪ Service order activities fromt the Service Order Control (SOC) module or the Work OrderControl (WCS) module of Service

Resource order plan

In ERP Baan5.0c, only the Capacity Use by Planned Order (cprrp2100m000) session was available toanalyze the utilization of production capacity.

In ERP LN 6.1, the new session Resource Order Plan (cprrp0530m000) provides a flexible overview ofthe use of the available production capacity of a resource.


Enterprise Planning

Plan chartYou can use the new Resource Order Plan Chart (cprrp0731m000) session to display data from yourresource order plan in a graphical format.

Capacity use by planned orderIn ERP LN 6.1, the Capacity Use by Planned Order (cprrp2100m000) session has several new fields,including:

▪ Cycle TimeIn Infor ERP, the time between completion of two separate units of production. For example,the cycle time of motors assembled at a rate of 120 per hour is 30 seconds.The cycle time is also equal to the time that a product stays in one position on a assemblyline, or the time that an operation is carried out on an item in a work station, excluding setuptime.

▪ Queue TimeThe amount of time that an order remains at a work center before setup or work is performedon the order.

▪ Wait TimeThe time that an order remains at a work center after an operation is completed until the orderis moved to the next operation.

▪ Move TimeThe time that a semifinished good is in transit from one operation to the next operation. Afterthe last operation, the move time is the time to transfer the finished good to the warehouse.

Signals

Process signals automaticallyIn ERP LN 6.1, you can set up Enterprise Planning to process the following types of order signalsautomatically:

▪ Cancel OrderIndicates that a planned order is no longer required.

▪ Reschedule InIndicates that a planned order must be moved to an earlier date.

▪ Reschedule OutIndicates that a planned order must be moved to a later date.

To indicate that a type of signal must be processed automatically, select signal type, and select theAuto Process check box in the Signal Types - by Planner (cprao1110m000) session.

To process signals, use the Process - Signals (cprao1220m000) session.


Enterprise Planning

Minimum-cost-price filterIn ERP LN 6.1, you can filter order signals based on the cost price of plan items. If you define a minimumcost price for a certain signal type, Enterprise Planning does not generate the corresponding signal foritems that cost less than the minimum cost price.

You can define a signal type's minimum cost price in the Signal Types - by Planner (cprao1110m000)session.

Sort and select planned purchase orders by buyer

DefinitionThe term buyer is defined as:

▪ The employee of your company who is the contact to the concerned buy-from business partner.

For all purchased items, you can define who is the designated buyer for that item.

New functionalityIn the Planned Orders (cprrp1100m000) session, baan displays the buyer that is responsible for theordered item. baan searches for the relevant buyer in the following sessions:

▪ Item - Purchase (tdipu0101m000)

▪ Business Partners (tccom4500m000), for the business partner linked to the planned purchaseorder.

▪ User Profiles (tdpur0143m000)

In the following sessions, you can select the planned orders for a range of buyers:

▪ Print Planned Orders (cprrp1410m000)▪ Confirm Planned Orders (cprrp1200m000)▪ Transfer Planned Orders (cppat1210m000)

In the Print Planned Orders (cprrp1410m000) session, you can sort the report by buyer.

Sort and select planned purchase orders by supplier

DefinitionThe term supplier denotes either the buy-from business partner or the ship-from business partner, orboth:

▪ Buy-from business partnerThe business partner from whom you order goods or services. This usually represents asupplier's sales department.

▪ Ship-from business partnerThe business partner that ships the ordered goods to your organization. This usually representsa supplier's distribution center or warehouse.


Enterprise Planning

For all purchased items, you can define the buy-from business partner and the ship-from businesspartner.

New functionalityIf you transfer planned purchase orders in the Transfer Planned Orders (cppat1210m000) session, youcan enter a range of suppliers (buy-from business partners) to select the planned purchase orders thatmust be transferred to the execution level.

The Planned Orders (cprrp1100m000) session also displays the supplier designated to supply theplanned purchase order and enables you to sort the planned orders by buy-from business partner(supplier).

From within the Planned Orders (cprrp1100m000) session, you can also print the planned (purchase)orders sorted by supplier.

Supply chain strategy

Supply chain strategy in ERP Baan5.0cIn ERP Baan5.0c, you can define supply chain strategies. For each supply chain strategy, you can defineone or more sourcing strategies and supply strategies. You can use the Supply Chain Strategies byScenario (cprpd7501m000) session to determine which supply chain strategy is valid for which scenario.

In ERP Baan5.0c, you can define beforehand on which date a supply chain scenario is replaced byanother supply chain scenario.

Scenario-related strategies in ERP LN 6.1In ERP LN 6.1, the concept of supply chain strategies was abandoned. In the Sourcing Strategy(cprpd7110m000) session and in the Supply Strategy (cprpd7120m000) session, you can link a scenariodirectly to sourcing strategies and supply strategies. However, you cannot define beforehand on whichdate a scenario is replaced by another scenario.

Switch off the time fence

Time fence in ERP Baan5.0cIn ERP Baan5.0c, if you do not want to use a time fence, you can set the Time Fence field in the PlanItem Data (cprpd1500m000) session to 0 (zero). However, in that situation Enterprise Planning cannotgenerate planned orders that start in the past.

Switching off the time fence in ERP LN 6.1In ERP LN 6.1, the Items - Planning (cprpd1100m000) session has a new option: the Use Time Fencecheck box. If you clear that check box, Enterprise Planning can generate planned orders that startanytime, including in the past.


Enterprise Planning

For example, assume you have a sales demand for yesterday and you clear the Use Time Fence checkbox. In that case, Enterprise Planning plans the finish date of the planned order for yesterday, becauseEnterprise Planning can plan in the past in that situation.

Terminology changes

Changed in Infor ERP LN 6.1

CodeERP LN 6.1ERP Baan5.0c

cprmp1202m000 (session)Generate Master PlanningSimulate Master Plan

cprrp1210m000 (session)Generate Order PlanningSimulate Orders

cprao3200m000 (session)Optimize Order ParametersOptimize Lot Sizing

Transfer of orders to the execution level

This topic describes various differences related to the transfer of planned orders to actual purchaseorders, production orders, and warehousing orders.

All of these differences are related to the Transfer Planned Orders (cppat1210m000) session.

Respect planned materials in planned production ordersIf you use the Transfer Planned Orders (cppat1210m000) session to transfer planned production ordersto the Shop Floor Control (SFC) module in Infor ERPManufacturing, baan respects thematerial selectionsand quantities as planned by Infor ERP Enterprise Planning.

Transfer purchase planIn ERP Baan5.0c, you can transfer a production plan to production orders, but you cannot transfer apurchase plan to purchase orders.

In ERP LN 6.1, you can not only transfer a production plan to production orders, but you can also transfera purchase plan to purchase orders.

To transfer a purchase plan, select the Purchase Plan field in the Transfer Planned Orders(cppat1210m000) session. If this check box is selected, baan converts the purchase plan of the specifiedplan item range to planned purchase orders, and transfers these purchase orders to the the PurchaseControl (PUR) module of Order Management.

The order quantity of the planned purchase orders that baan creates depends on the values you definedin the Minimum Order Quantity field and the Maximum Order Quantity field in the Items - Ordering(tcibd2500m000) session, and the planned requirement date of the purchase order is equal to the startdate of the plan period in which the purchase plan is defined.


Enterprise Planning

Transfer items with order policy to orderIn the Transfer Planned Orders (cppat1210m000) session, you can now also transfer planned ordersfor items with empty project segments of which the order policy is To Order.

To this end, you must select the Transfer Items with order policy To Order check box.

For more information, refer to To plan to-order items anonymously

Related differencesFor related difference topics, refer to:

▪ Order grouping (p. 111)

▪ Sort and select planned purchase orders by supplier (p. 116)

▪ Sort and select planned purchase orders by buyer (p. 116)

Unit effectivity

New conceptsThe term effectivity unit is defined as:

▪ A reference number on a sales order line or a sales quotation line that is used to modeldeviations for a unit effective item, or to peg purchase orders or production orders to a specificsales order line.

New functionalityIn ERP LN, you can use unit effectivity to adapt the standard business procedure for items, and modelexceptions that originate from specific customer requirements. The unit effectivity concept supportssituations in which customers have specific wishes in regard to the features of the products they order.For each specific wish, you can define an exception, and link the exception to the business aspect thatis impacted by the exception. In this way, you can model small deviations from the standard productconfiguration. ERP LN takes into account the exceptions that you define in the process of order planning.

Use-up materials and alternative materials

New conceptsIn ERP LN 6.1, the following concepts are introduced:

▪ Use-up materialA material that has been replaced by another item in all BOMs. After the use-up material'slast allowed order date elapses, any remaining stock is used up and then the replacementmaterial is used.

▪ Alternative materialA substitute for a BOM material that the system can select in case the standard material isout of stock. An alternative material is supposed to meet the same specifications, but only inthe context of a BOM for a specific main item.


Enterprise Planning

New functionalityYou can define use-up materials and alternative materials in the bill of material (BOM) of an item. If yougenerate planned orders, baan checks the projected inventory of the materials. If the projected inventoryis insufficient, baan tries to use any of the alternative materials.

baan also checks whether the planned order must use any use-up material in stead of the standardmaterial.

Warehouse on the BCM line

Warehouse for critical material in ERP Baan5.0cIn ERP Baan5.0c, you cannot specify a warehouse in the Bills of Critical Materials (tibom2520m000)session. For the master-based planning, Enterprise Planning uses the warehouse from the ItemOrderingData (tcibd2500m000) session.

If the warehouse in the item ordering data differs from the warehouse in the BOM, the master-basedplanning allocates the material demand to the wrong warehouse. This problem is particularly serious ifthe warehouses belong to separate clusters.

BCM in ERP LN 6.1In ERP LN 6.1, you can specify the warehouse from which ERP LN issues the critical component.

To align the master-based planning with the order-based planning, you must specify the same warehousein the bill of material and the bill of critical material.

Modules

Cyclic Planning (CLP) module – Differences B50c/ERP61

In ERP LN 6.1, the cyclic planning planning method is no longer supported.

Resource Planning Data (RPD) module – Differences B50c/ERP61

This topic describes miscellaneous differences between the Resource Planning Data (RPD) module inERP Baan5.0c and ERP LN 6.1.

New session: Copy Plan Items to Clusters (cprpd1210m000)With this new session, you can copy plan items to clusters.

You can use the session in the following ways:

▪ Copy one plan item to a range of clusters.

▪ Copy one plan item to one clustered item, if you enter the same cluster in the From Clusterfield and the To Cluster field.


Enterprise Planning

▪ Copy a range of plan items to one cluster.

Critical Item in Master PlanningIn ERP Baan5.0c, the Item Production Data (tiipd0501m000) session includes the Critical Item inMaster Planning check box.

In ERP LN 6.1, that check box is called the Critical in Planning check box. That check box was movedto the Items - Ordering (tcibd2500m000) session.

New option in Initialize, Roll, and Update Scenario (cprpd4200m000) sessionIn ERP LN 6.1, the Initialize, Roll, and Update Scenario (cprpd4200m000) session includes an InitializeOnly for Items Without Existing Plan check box. This check box is implemented for performancereasons.

If you selected the Generate Item/Channel Master Plan check box, you can select the Initialize Onlyfor Items Without Existing Plan check box, if baan must only initialize the scenario that you selectedfor plan items that do not have an item master plan or a channel master plan yet.


Enterprise Planning


Enterprise Planning


Alternative items

This topic explains how the procedure for selling alternative items has changed in ERP LN 6.1 comparedto ERP Baan5.0c.

Alternative items in ERP Baan5.0cIn ERP Baan5.0c, whenever an inventory shortage occurs for an item, the order taker can offer thesold-to business partner an alternative item. You cannot offer a mix of the original item and the alternativeitem.

Alternative items in ERP LN 6.1In ERP LN 6.1, if an item is replaced by another item, you can first consume the available inventory ofthe original item and then fill the remaining shortage with an alternative. You can offer the sold-to businesspartner a mix of the original item and the alternative item. As a result, you can prevent an item frombecoming obsolete.

For more information, refer to To ship alternative items.

ATP/CTP in Sales Control

This topic explains how the available-to-promise (ATP) and capable-to-promise (CTP) functionality haschanged in ERP LN 6.1 compared to ERP Baan5.0c.

ATP/CTP in ERP Baan5.0c

▪ ATP/CTP for configurable itemsIn the ATP Handling (tdsls4899m000) session, you cannot accept a delivery schedule for ToOrder items and generic items that are not customized yet.

▪ ATP check for sales order line BOM componentsIn ERP Baan5.0c, you cannot execute an ATP check for sales order lines that have theInventory Handling field set to By Component in the Sales Order Lines (tdsls4101m000)


5Chapter 5Order Management

session. Although the sales order line has insufficient ATP, it can be saved. As a result,negative values can appear in the Item Master Plan (cprmp2101m000) session for thecomponents.

ATP/CTP in ERP LN 6.1

ATP/CTP for configurable itemsNew in Infor ERP LN 6.1

The Create Order Lines check box is introduced in the ATP Handling (tdsls4899m000) session, whichdetermines how a delivery schedule is processed on sales order level.

For To Order items and generic items that are not customized yet, this check box is unavailable andselected. The reason for this is that a proposed (ATP) delivery schedule can only be accepted for theseitems if multiple order lines are created. As a result, sales order lines are generated with different datesand/or warehouses.

For customized items, a delivery schedule can be set up. As a result, after a product/project structureis generated for the lines in the Generate (Project) Structure for Sales Orders (tdsls4244m000) session,sales order delivery lines can be created that represent the delivery schedule.

ATP check for sales order line BOM componentsChanged in Infor ERP LN 6.1

To prevent negative values to appear in the Item Master Plan (cprmp2101m000) session for thecomponents, the following has changed in ERP LN 6.1:

▪ If the CTP Check for Sales (for EP and OPS) check box is selected in the EP Parameters(cprpd0100m000) session, and the sales order line is set to By Component, the ATP ischecked for all components when the available-to-promise is checked for the sales order line.If one of the components has insufficient ATP, you cannot save the sales order line.

▪ If a back order has planned components linked in the Sales Order Line - BOM Components(tdsls4532m000) session, and the back order is confirmed in the Maintain and Confirm BackOrders (tdsls4125m000) session, the back order's planned delivery date is the latest planneddelivery date that is calculated for one of the components based on the ATP values in thecomponents' master plan.

▪ If an inventory shortage occurs for a planned item, you can select the Calculate DeliveryDate from MPS option from the inventory shortage menu. As a result, Infor ERP retrieves theearliest planned delivery date for all components from the master plan. The latest deliverydate that is retrieved for these components is inserted as the earliest planned delivery dateon the sales order line.

Business partner search

This topic explains how you can use default selection criteria when searching for business partners inERP LN 6.1.


Order Management

Business partner search ERP LN 6.1New in Infor ERP LN 6.1

To enhance the selection of business partners based on name and address, you can define the defaultfields that you want to use for searching in the Sales Parameters (tdsls0100s000) session.

The check boxes you select on the BP Search Criteria tab of the Sales Parameters (tdsls0100s000)session are the default check boxes used during the search. However, during the actual search, youcan select less or more check boxes. The key is that you do not select more check boxes in theparameters than you usually use, so the load is minimalized.

The search mechanism, defined in the parameters, has an impact on all sessions in which you can enterthe business partner.

For example, if you select the Name check box in the Sales Parameters (tdsls0100s000) session, theName check box is automatically selected when you use the Search by Address Criteria (tdsls0270m000)session to search for a business partner.

Cancel sales orders

This topic explains how the procedure for canceling sales orders and sales order lines has changed inERP LN 6.1 compared to ERP Baan5.0c.

To cancel a sales order, sales order line, or sales order line detail in ERP Baan5.0cIn ERP Baan5.0c, you can click:

▪ Cancel Order to cancel a sales order directly in the Sales Orders (tdsls4100s000) session.▪ Cancel Line to cancel a sales order line directly in the Sales Order Lines (tdsls4101s000)

session.

▪ Cancel Line to cancel a sales order line detail directly in the Sales Order Line Details(tdsls4101s200) session.

To cancel a sales order, sales order line, or sales order line detail in ERP LN 6.1Changed in Infor ERP LN 6.1

In ERP LN 6.1, you can only cancel a sales order, sales order line, or delivery line in the Cancel SalesOrders (tdsls4201s300).

You can start the canceling process from the following sessions:

▪ Sales Orders (tdsls4100m000) or Sales Order - Lines (tdsls4100m900), to cancel a salesorder.

▪ Sales Order Lines (tdsls4101m000), Sales Order - Lines (tdsls4100m900), or Maintain andConfirm Back Orders (tdsls4125m000) session, to cancel a sales order line.

▪ Sales Order Delivery Lines (tdsls4101m100), or Sales Order Line - Deliveries (tdsls4101m900),to cancel a sales order delivery line.


Order Management

Commission and rebate currencies


ERP Baan5.0cIn the Commission Control System module of ERP Baan5.0c, you cannot control the calculation ofcommissions and rebates in detail. As a result, if different currencies are used, several problems arisewhen calculating and invoicing commissions and rebates. For example, it occurs that ERP Baan5.0cwrongly converts the commissions/rebates from one currency to another.

ERP LN 6.1In ERP LN 6.1, a user can control the calculation of commissions and rebates in a detailed way.

A user can define for a relation when the calculation must be performed, in which currency, and againstwhich rate. The calculation process then calculates and displays the commission/rebate amounts notonly in the home currency, but also in the order currency and the invoice currency based on the definedrate/rate factor and exchange rate type. As a result, a user can now easily retrieve which rates are usedfor calculating and invoicing commissions and rebates.

New in Infor ERP LN 6.1A number of fields are added to various sessions in the Commission Control System module of ERPLN 6.1.

Relations (tdcms0110s000) sessionThe following fields are added, or extended:

▪ Currency for Invoicing▪ Calculation Method. This field is moved from the Commissions/Rebates Parameters.▪ Rate used for Calculating/Invoicing▪ Exchange Rate Type▪ Exchange Rate Type Used

Agreement parameters

▪ The Currency field is added to the Commission Agreement Parameters (tdcms0135s000)session.

▪ The Currency field is added to the Rebate Agreement Parameters (tdcms1135s000) session.

Note

The currency as entered in the agreement parameters, is defaulted to the Currency field of theCommission Agreements (tdcms0130m000) and Rebate Agreements (tdcms1130m000) sessions.


Order Management

Commissions Calculated by Order (tdcms0550m000)/ Commissions Calculated by Relation(tdcms1550m000) sessionsThe following fields are added:

▪ Transaction Type▪ Sales Invoice▪ Amount in Sales Order Currency▪ Sales Order Currency▪ Amount in Invoice Currency▪ Invoice Currency

Rebates Calculated byOrder (tdcms2550m000)/ Rebates Calculated by Relation (tdcms3550m000)sessionsThe following fields are added:

▪ Transaction Type▪ Sales Invoice▪ Amount in Sales Order Currency▪ Sales Order Currency▪ Amount in Invoice Currency▪ Invoice Currency

Commissions Calculated by Order (tdcms0150s000)/ Commissions Calculated by Relation(tdcms1150s000)/ Commissions Paid to Employees by Relation (tdcms1151m000)/ CommissionsPaid to Employees by Order (tdcms0151m000)/ Commissions Calculated by Cumulative Sales(tdcms1500m000)/ Close Commissions Reserved for Employees (tdcms2102m000)The following fields are added:

▪ Amount in Sales Order Currency▪ Sales Order Currency▪ Amount in Invoice Currency▪ Invoice Currency

Rebates Calculated by Cumulative Sales (tdcms1505m000)/ Rebates Calculated by Order(tdcms2150s000)/ Rebates Calculated by Relation (tdcms3150s000)/The following fields are added:

▪ Amount in Sales Order Currency▪ Sales Order Currency▪ Amount in Invoice Currency▪ Invoice Currency


Order Management

Configured items in Sales Control

This topic explains how the configuration of items has changed in ERP LN 6.1 compared to ERPBaan5.0c.

Configured items in ERP Baan5.0cIn ERP Baan5.0c, configured items in PCF always are customized items. This means that an item ispart of a PCS project. The advantages of PCS are, amongst others, that it provides an item with adetailed cost roll-up. It also provides the possibility of pegging by means of the project code.

Configured items in ERP LN 6.1New in Infor ERP LN 6.1

In high volume environments, the detailed cost roll-up provided by PCS is often not necessary.Furthermore, using PCS costs extra time to calculate the project costs and to delete the project structureafterwards. As a result, in ERP LN 6.1, the configuration of a generic item not always results into acustomized item. Configured items can now be customized items as well as standard items. If youconfigure items without PCS projects, standard items are generated instead of customized items. Fordetails, refer to How to define a product model.

Pegging functionality is secured by the unique item codes of the configured items that can be relatedback to the sales order.

Delivery notes

A delivery note is a transport document that provides information on a consignment contained in onetruck (or other vehicle) and refers to an order or a set of orders for one consignee at a delivery address.If the truck load contains shipments for various business partners, the load includes more than onedelivery note. The information on a delivery note includes the delivery date and address, the customer'sname, the contents of the consignment, and so on. In Italy, a delivery note is a legally required document,where it used to be called BAM (Bolla Accompagnamento Merci). Currently it is called DDT (Documentodi Trasporto). In Portugal and Spain delivery notes are also used, but there they do not have the samelegal status as in Italy.

ERP Baan5.0cIn ERP Baan5.0c, delivery notes were not included in the shipping documents that you can print forgoods leaving the warehouse.

New in Infor ERP LN 6.1In ERP LN 6.1, the delivery notes funcionality is implemented in Warehouse Management. For moreinformation, refer to Delivery notes.

Due to implementation of the delivery notes functionality, the motive of transport and delivery code fieldsare added to the following sessions in Order Management:

▪ Sales Order - Lines (tdsls4100m900)


Order Management

▪ Sales Order Lines (tdsls4101m000)▪ Sales Order Delivery Lines (tdsls4101m100)▪ Sales Schedules (tdsls3111m000)

After the shipment lines are confirmed in Warehouse Management, the new Delivery Note, GrossWeight, andWeight Unit fields are defaulted from Warehouse Management in the Sales Order ActualDelivery Lines (tdsls4106m000) and the Schedule Shipment Details/Corrections (tdsls3140m000)session.

In case of a purchase return order, the newDelivery Note field can also be filled in the Purchase Receipts(tdpur4106m000) session.

Delivery types

This topic explains how the settings for the different types of delivery has changed in ERP LN 6.1compared to ERP Baan5.0c.

Delivery types in ERP Baan5.0cIn ERP Baan5.0c, the following types of deliveries exist:

▪ Direct deliveries. For these type of deliveries, the Direct Delivery check box is selected onthe sales order line.

▪ Non-direct deliveries.

Delivery types in ERP LN 6.1Changed in Infor ERP LN 6.1

In ERP LN 6.1, you can select a delivery type in the new Delivery Type field of the Sales Order Lines(tdsls4101m000)/ Delivery Lines (tdsls4101m100) session.

The following delivery types are available:

▪ SalesThe sales order (delivery) line must be delivered by the Sales Control module. As a result,you must maintain the deliveries in the Maintain Deliveries Sales Order Lines (tdsls4101m200)session.

▪ Work CenterThe sales order (delivery) line must be released to Warehouse Management, but instead ofa warehouse, a work center is communicated to Warehouse Management. Delivery takesplaces from work center to business partner. This applies to generic items that are assembledby means of the Assembly Planning module.

▪ InvoicingThe sales order (delivery) line must be invoiced only, no physical delivery takes place. Forexample, this is applicable in case of consignment invoicing, and retrobilling.


Order Management

▪ Not ApplicableNo delivery type is applicable, because the order line is of the Order Line type. Lines of thistype are split up in several sequences (delivery lines) and only display totaled quantities andamounts.

▪ Direct DeliveryThe sales order (delivery) line is a direct delivery.This value can be selected as follows in the Delivery Type field of the Sales Order Lines(tdsls4101m000) session or the Delivery Lines (tdsls4101m100) session:

▪ Automatically, if the ordered quantity is equal to or greater than the quantity defined in theDirect Delivery from Quantity field in the Item - Sales (tdisa0101s000) session.

▪ Manually, by selecting Direct Delivery.▪ By selecting Generate Direct Delivery from the shortage menu that appears when an

inventory shortage exists for the item.For more information, refer to Direct delivery.

▪ Cross-dockingThe sales order (delivery) line must be cross-docked.This value can be selected as follows in the Delivery Type field of the Sales Order Lines(tdsls4101m000) session or the Delivery Lines (tdsls4101m100) session:▪ Manually, by selecting Cross-docking.▪ By selecting Generate Purchase Order Advice from the shortage menu that appears

when an inventory shortage exists for the item.

▪ After you run the Generate Purchase Order Advice for Sales Order (tdsls4240m000)session with the Type of Line set to All Lines for sales order (delivery) lines with theDelivery Type field set toWarehouse.

For more information, refer to Purchase orders for non-direct deliveries (p. 143) .

▪ WarehouseThe sales order (delivery) line is delivered by Warehouse Management.

For direct deliveries or cross-docking orders, you must generate a purchase order advice in the GeneratePurchase Order Advice for Sales Order (tdsls4240m000) session, which was called a planned purchaseorder in ERP Baan5.0c.

Note

▪ For a direct delivery, a one-to-one relationship exists between the sales order line and thepurchase order line. As a result, updates to a number of fields on the sales order line reflectin the linked purchase order line. For a cross-docking order, however, several purchase orderline details can be linked to one sales order line, or several sales order delivery lines can belinked to one purchase order line. As a result, if you make changes to the sales order line, thelink with the purchase order line (detail)(s) can be broken. See also: Relation betweencross-docking and splitting deliveries.

▪ A sales order line is linked to Purchase Control if one of the following fields is filled in theLinked Order Line Data (tdsls4102s200) session:▪ Planned Purchase Advice Number▪ Purchase Order


Order Management

After deliveries are executed for a delivery type, delivery information is reported back to Sales Control.

You can view delivery information centrally in the following sessions:

▪ Sales Order Lines Monitor (tdsls4510m000)

▪ Sales Order Actual Delivery Lines (tdsls4106m000)

Effectivity units

An effectivity unit is a reference number on a sales order line or a sales quotation line that is used tomodel deviations for a unit effective item, or to peg purchase orders or production orders to a specificsales order line.

New in Infor ERP LN 6.1In ERP LN 6.1, you can define effectivity units in the new Unit Effectivity (UEF) module of CommonData, after which you can enter these units in sales quotations, sales orders, and sales contracts.

Effectivity units are used as follows:

▪ For pegging purposes. For more information, refer to Overview of unit effectivity.

▪ To control exceptions for an end item according to the series approach. For more information,refer to Unit effectivity procedure 1 – series approach.

▪ To control exceptions for an end item according to the sales order approach. For moreinformation, refer to Unit effectivity procedure 2: Sales approach.

If you use unit effectivity to configure an item:

▪ The new Configuration Date (UEF) field in the Sales Parameters (tdsls0100s000) sessiondetermines the date on which an effectivity unit must be configured for a sales order/quotation.

▪ For every requirement that you select for an effectivity unit in the Requirements(tcuef0106m000) session, you can define an upgrade price. In case special components oraccessories are used, it is common practice that a sold-to business partner must pay anadditional (upgrade) price for these components or accessories. The requirement's upgradeprice is added to the effectivity unit's sales price.

As a result, in each session in which sales order/quotation lines prices are used or displayed, upgradeprices are added to, or included in the sales price for unit effective items.

For more information about how to configure an effectivity unit, refer to:

▪ To configure effectivity units

▪ Unit effectivity as a lean configurator in Sales Control

Equate balance of receipts with inventory level

New in Infor ERP LN 6.1In the Purchase Order Parameters (tdpur0100m400) session, you can use the Method of CalculatingAverage Purchase Price field to determine how the average purchase price is calculated.


Order Management

You can select the following:

▪ Current InventoryThe average purchase price is calculated based on the average price of the current inventory.

▪ Purchases (Cum)The average purchase price is calculated based on the average price of the cumulatedpurchases up to the time of the new receipt.

If you select Purchases (Cum), and the value of the cumulative receipts is high, the influence of theorder price on the average purchase price is very small. If this influence becomes too small, you mustdecrease the value of the cumulative receipts by equating the value with the inventory on hand.

In ERP LN 6.1, you can use the new Equate Balance of Receipts with Inventory Level (tdipu0201m000)session to decrease the value of the cumulative receipts. You must run this session periodically to ensurethat realistic average purchase prices for the items are calculated.

Invoicing commissions and rebates

This topic explains how the commissions and rebates invoicing procedure has changed in ERP LN 6.1compared to ERP Baan5.0c.

Invoicing in ERP Baan5.0cIn ERP Baan5.0c, if a link with Financials exists for commissions and rebates, invoices are createddirectly in the Commission Control System (CMS) module. When processing the commissions andrebates in the Process Commission/Rebate (tdcms2201m000) session, they are posted to the GeneralLedger (GLD) module of Financials.

Invoicing in ERP LN 6.1In ERP LN 6.1, if a link with Financials exists for commissions and rebates:

▪ Commissions are released to the Accounts Payable (ACP) module of Financials. As a result,ERP LN 6.1 creates an open entry in the Accounts Payable module.

▪ Rebates are released to Central Invoicing. After processing in Central Invoicing, the rebatesare sent to the customers in the form of sales invoices or credit notes, and posted to Financialsas open entries in the Accounts Receivable module.

Note

This functionality has changed to support:

▪ The use of the standard invoicing functionality offered through Central Invoicing. For moreinformation, refer to Invoicing.

▪ The generation of invoices that combine both rebate requests and other invoice requests fora specific sold-to business partner.

▪ A lean integration between commissions and the Accounts Payable module of Financials.


Order Management

Changed in Infor ERP LN 6.1Because of the new invoicing functionality, a number of changes are made to the Commission ControlSystem module of ERP LN 6.1.

Unreserved commissions and rebates

Print Approved Commissions/Rebates (tdcms2402m000)In ERP Baan5.0c, this session was called the Print Commission/Rebate Invoices (tdcms2402m000)session.

The following fields are removed from this session, because the invoicing functionality is moved toFinancials:

▪ Final Invoices▪ Invoice Date

This session prints the approved unreserved commissions or rebates for commissions and rebates thatapply to the same relation or order.

Because the invoicing functionality is removed from this session, its purpose is now to change the statusof the commission/rebate from Approved to Ready. The Ready status is necessary to release thecommission/rebate to invoicing in the Release Commissions/Rebates to Invoicing (tdcms2201m000)session. If the Link with Finance check box is cleared in the Commissions/Rebates Parameters(tdcms0100s000) session, the status changes to Closed.

Reserved commissions and rebates (with a link to Finance)

Reservation and Approval of Reserved Commissions/Rebates (tdcms2202m000)In ERP Baan5.0c, this session was called the Global Approval of Reserved Commissions/Rebates(tdcms2202m000) session.

The following field is added to this session:

▪ Approve Reserved Commissions/Rebates

You can use this session to do the following:

▪ Set the status to Reserved for the commissions and rebates that:

▪ Are approved in the Global Approval of Commissions/Rebates (tdcms0250m000) session.

▪ Have the Reserve check box selected in the Global Approval of Commissions/Rebates(tdcms0250m000) session.

▪ Set the status to Reservation Approved for the commissions and rebates with the Reservedstatus.

Print Reserved Commissions/Rebates (tdcms2403m000)In ERPBaan5.0c, this session was called the Invoice Reserved Commissions/Rebates (tdcms2403m000)session.


Order Management

The following fields are removed from this session:

▪ Final Invoices▪ Invoice Date

This session prints the approved reserved commissions or rebates for commissions and rebates thatapply to the same relation or order.

Because the invoicing functionality is removed from this session, the purpose of this functionality is nowto change the status of the commission/rebate from Reservation Approved to Ready, if the Link withFinance check box is selected in the Commissions/Rebates Parameters (tdcms0100s000) session.The Ready status is required to release the commission/rebate to invoicing in the ReleaseCommissions/Rebates to Invoicing (tdcms2201m000) session. If the Link with Finance check box iscleared in the Commissions/Rebates Parameters (tdcms0100s000) session, the purpose of thisfunctionality is to change the status of the commission/rebate from Approved to Closed.

Reserved and unreserved commissions and rebates

Commissions/Rebates Parameters (tdcms0100s000)The following fields are removed from the Commissions/Rebates Parameters (tdcms0100s000) session:

▪ Tax Code for Commission Invoice▪ Tax Code for Rebate Invoice▪ Commission Calculation Method▪ Rebate Calculation Method

These fields are transferred to the Relations (tdcms0110s000) session, because they must bemaintainable by relation.

Relations (tdcms0110s000)The following fields are added to the Relations (tdcms0110s000) session:

▪ Purchase Type. For more information, refer to To set up control accounts.▪ Sales Type. For more information, refer to To set up control accounts.▪ Tax Code. This field is moved from the Maintain Commission Parameters (tdcms0100m000)

andMaintain Rebate Parameters (tdcms1100m000) sessions, to the Relations (tdcms0110s000)session in ERP LN 6.1, because the tax codes must be maintainable by country.

▪ Currency for Invoicing▪ Calculation Method. This field is moved from the Commissions/Rebates Parameters

(tdcms0100s000) session.▪ Rate used for Calculating/Invoicing▪ Exchange Rate Type▪ Exchange Rate Type Used

For more information, refer to Commission and rebate currencies (p. 126) .


Order Management

Release Commissions/Rebates to Invoicing (tdcms2201m000)In ERP Baan5.0c, this session was called the Process Commission/Rebate (tdcms2201m000) session.

The following fields are added to this session:

▪ Commissions to Accounts Payable▪ Rebates to Central Invoicing

In this session, both the reserved and unreserved commissions and rebates with the Ready status canbe released to invoicing.

For more information, refer to online help of the Release Commissions/Rebates to Invoicing(tdcms2201m000) session.

Print List of Reserved Commissions/Rebates (tdcms2404m000)In ERP LN 6.1, you can use this session to do the following:

▪ Print a list of the reserved commissions or rebates. If you select this option from the MenuBrowser, ERP LN 6.1 starts the Print List of Reserved Commissions/Rebates (tdcms2404m000)session.

▪ Print relations by invoice. ERP LN 6.1 starts the Relations by Invoice (tdcms2404m000) sessionif you click the printing button in the Relations by Invoice (tdcms2502m000) session.

The Also print Rebates released to SLI, but not yet Invoiced check box is added to this session.

Relations by Invoice (tdcms2502m000)Although this session already existed in ERP Baan5.0c, it was never used.

In ERP LN 6.1, the following field is added to this session:

▪ Released to SLI(Rebate)

For more information, refer to the online help of the Relations by Invoice (tdcms2502m000) session.

Note

After a rebate is released to Central Invoicing and the invoice status is Confirmed orOn Hold in CentralInvoicing, you can still update the rebate invoice data in the Rebates Calculated by Order(tdcms2150s000), or the Rebates Calculated by Relation (tdcms3150s000) sessions. For moreinformation, refer to To change sales data after release to Central Invoicing.

Link between Purchase Control and Freight Management

This topic explains how the Purchase Control module is linked to the new Freight Management packagein ERP LN 6.1.


Order Management

Freight Management in ERP LN 6.1The purpose of the Freight Management package is to plan and/or to subcontract the transportation ofinbound and outbound goods, which helps you select the most cost-effective way to get goods in andout of the site at the correct times.

For infomation on the setup and use of the Freight Management package, refer to Freight Management.

Link with Freight ManagementIf Purchase Control is responsible for the transportation of goods and must consequently collect goodsfrom a supplier, you can generate a freight order from the purchase order. If the transportation of goodsis not the supplier's responsibility, but the responsibility of Purchase Control, the supplier must know onwhat date the goods must be ready. As a result, you must consider the planned load date in the purchaseorder as the shipment date: when to pick up the goods from the supplier.

The following links exist:

▪ Between Freight Order Control and Purchase ControlDuring the planning and execution of a freight order, its status often changes. If PurchaseControl is responsible for creating the freight order, the progress of the shipment and loadscan be exchanged and information can be shared between Freight Order Control and PurchaseControl. For more information, refer to Integration Freight Order Control and Purchase Control.

▪ Between freight invoicing and purchase invoicingThe freight rate that you must pay to the carrier, is called freight costs. You can invoice yourbusiness partner for the freight costs, based on:▪ Freight Costs.▪ Freight Costs (Update Allowed).▪ Client Rates.For more information, refer to Integration Freight Invoicing and Purchase Invoicing

Link between Sales Control and Freight Management

This topic explains how the Sales Control module is linked to the new Freight Management package inERP LN 6.1.

Freight Management in ERP LN 6.1The purpose of the Freight Management package is to plan and/or to subcontract the transportation ofinbound and outbound goods, which helps you select the most cost-effective way to get goods in andout of the site at the correct times.

For infomation on the setup and use of the Freight Management package, refer to Freight Management.

Link between Sales Control and Freight ManagementIn ERP LN 6.1 Sales Control, you can generate a freight order from the sales order. The purpose of theintegration between Sales Control and Freight Management is to identify and choose the appropriatemeans of transportation during order entry.


Order Management

The following links exist:

▪ Between Freight Order Control and Sales ControlIn Freight Order Control, two types of planning exist:

▪ Rough planning, which is used for long-term capacity planning.

▪ Load building, which is the actual execution time plan of the shipments and loads. To shipthe goods, Freight Order Control must know the shipments to be moved over a period oftime. If Sales Control is responsible for creating the freight order, the progress of theshipment and loads can be exchanged and information can be shared between FreightOrder Control and Sales Control.

For more information, refer to Integration Freight Order Control and Sales Control and Togenerate freight orders for direct delivery sales orders.

▪ Between freight rating and Sales ControlDuring sales order entry or sales quotation entry, you can zoom to Freight Management toselect the most suitable carrier. Based on several factors, such as the invoicing method, item,freight class, service level, transport type, and transport means group, the freight invoiceamount is then retrieved from Pricing Control. baan prints the calculated invoice amount onthe order acknowledgement. For more information, refer to Integration Freight Rating andSales Control.

▪ Between freight invoicing and sales invoicingThe freight rate that you must pay to the carrier, is called freight costs. You can invoice yourbusiness partner for the freight costs, based on:▪ Freight Costs.▪ Freight Costs (update allowed).▪ Client Rates.For more information, refer to Integration Freight Invoicing and Sales Invoicing

List groups

This topic explains how the procedure for buying list items from list groups has changed in ERP LN 6.1compared to ERP Baan5.0c.

List groups in ERP Baan5.0cIn ERP Baan5.0c, you can only link one list group to a sold-to business partner from which the sold-tobusiness partner can order list items.

List groups in ERP LN 6.1In ERP LN 6.1, sold-to business partners can indicate whether they want to buy only from the list groupthat is linked to them, or also from other list groups. If a business partner wants to choose from multiplelist groups, a user can now choose from the available list groups when entering a sales order or salesquotation.

For more information, refer to To buy items from list groups.


Order Management

Lot and serial information on the sales order


Lot items in ERP Baan5.0cLot control is used to record and trace groups of items. In ERP Baan5.0c, you define lot conditions forlot items on the sales order line.

Lot and serialized items in ERP LN 6.1New in Infor ERP LN 6.1

In ERP LN 6.1, the concept of serialized items is introduced. A serialized item is a physical occurrenceof a standard item that is given a unique lifetime serial number. This enables tracking of the individualitem throughout its lifetime, for example, through the design, production, testing, installation, andmaintenance phases. A serialized item can consist of other serialized components.

Examples of serialized items are cars (Vehicle Identification Number), airplanes (tail numbers), PCs,and other electronic equipment (serial numbers).

As a result, in ERP LN 6.1, lot and serial information is available on the sales order.

Lot and serial information that is communicated by the sales order is not only useful for direct deliveriesand multi-site environments, but also for normal issues and shipments in single-site environments.

For more information, refer to Lot control by serialized items (p. 27) .

Over deliveries

This topic explains how the functionality for over deliveries has changed in ERP LN 6.1 compared toERP Baan5.0c.

Over deliveries in ERP Baan5.0cIn ERP Baan5.0c, if more goods are delivered than ordered, you cannot record and track these overdeliveries. As a result, over deliveries are not possible.

Over deliveries in ERP LN 6.1New in Infor ERP LN 6.1

Before an over delivery can take place for an item and business partner combination in ERP LN 6.1,you must define a number of settings in the Item Sales Data (ISA) module of Order Management.

Define the following fields in the Item - Sales Business Partner (tdisa0110s000) session:

▪ Select the Allow Over Deliveries check box. This check box enables the WarehouseManagement package to ship an over delivery for the item and business-partner combination.

▪ Define whether the tolerance for the over delivery is expressed either as a percentage or aquantity in the Tolerance Type field.


Order Management

PercentageThe tolerance is represented as a percentage of the order quantity.

▪▪ Quantity

The tolerance is a fixed quantity.

▪ In the Action field, define the way in which ERP LN must handle the outbound order line if ashipment does not meet the quantity tolerances.You have the following options:

▪ WarnIf the maximum tolerance is exceeded, ERP LN gives a warning message to WarehouseManagement.

▪ BlockIf the maximum tolerance is exceeded, ERP LN blocks the shipment in WarehouseManagement.

▪ NoERP LN does not take any action.

▪ Define the percentage or quantity that the shipped quantity may be more than the orderedquantity in theMaximum Tolerance field. For more information, refer to the online help of theMaximum Tolerance field.

Order entry

This topic explains how the procedure for entering sales orders and sales order lines and purchaseorders and purchase order lines has changed in ERP LN 6.1 compared to ERP Baan5.0c.

Order entry in ERP Baan5.0cIn ERP Baan5.0c, you can enter sales orders, sales order lines, and sales order line details in thefollowing sessions:

▪ Sales Orders (tdsls4500m000)▪ Sales Order - Lines (tdsls4501m000)▪ Sales Order Line Details (tdsls4501m200)

You can enter purchase orders, purchase order lines, and purchase order line details in the followingsessions:

▪ Purchase Orders (tdpur4500m000)▪ Purchase Order - Lines (tdpur4501m000)▪ Purchase Order Line Details (tdpur4501m200)

Order entry in ERP LN 6.1New in Infor ERP LN 6.1

In ERP LN 6.1, header-lines sessions are introduced. Header-lines sessions consist of a header and anumber of tabs or satellites that refer to sessions with their own session codes.


Order Management

Header-lines sessions in Sales ControlIn Sales Control, header-lines sessions enable you to quicly enter and process sales orders, sales orderlines, and delivery lines, which are called sales order line details in ERP Baan5.0c. The followingheader-lines sessions are available:

▪ The Sales Order - Lines (tdsls4100m900) session, in which you can enter a sales order headerand sales order lines on one screen.

▪ The Sales Order Line - Deliveries (tdsls4101m900) session, in which you can view the salesorder line in read-only mode and in which you can enter the delivery lines that are linked to aspecific sales order line.

Header-lines session in Purchase ControlIn Purchase Control, the new header-lines session enables you to quicly enter and process purchaseorders and purchase order lines. The following header-lines session is available:

▪ The Purchase Order - Lines (tdpur4100m900) session, in which you can enter a purchaseorder header and purchase order lines on one screen.

You can enter and maintain purchase order line details in the Purchase Order Line Details(tdpur4101m200) session.

Note

In weptop, on the View menu, you can click:

▪ Customize Form, to customize the layout of the purchase order and sales order sessions.As a result, you can indicate which fields you want to hide and unhide. You can select fieldsfrom the Sales Orders (tdsls4100m000) session that must be displayed in the Sales Order -Lines (tdsls4100m900) session and fields from the Purchase Orders (tdpur4100m000) thatmust be displayed in the Purchase Order - Lines (tdpur4100m900) session.

▪ Customize Toolbar, to hide and unhide icons on your toolbar.▪ Customize Menu, to hide and unhide options from the specific menu.

Order units

This topic explains how the use and definition of units has changed in ERP LN 6.1 compared to ERPBaan5.0c.

Order unit in ERP Baan5.0cIn ERP Baan5.0c:

▪ All quantities on the purchase order line, contract line, and requisition line are stored in thepurchase unit.

▪ All quantities on the sales order line, contract line, and quotation line are stored in the salesunit.


Order Management

InWarehouseManagement, all quantities are stored in the inventory unit. When quantities are exchangedbetween Order Management andWarehouse Management, ERP Baan5.0c must convert the quantities.

Inventory unit and (back) order unit ERP LN 6.1Changed in Infor ERP LN 6.1

To avoid incorrect roundings and incorrect postings to Financials and Central Invoicing as a result ofconverted quantities, the following changes are made in ERP LN 6.1:

▪ You must define an inventory unit for a purchased item.

▪ If a quantity is stored in more than one unit, ERP LN 6.1 also converts the quantity to the otherunit as the unit in which the quantity is expressed. For example, if a quantity is expressed inthe (back) order unit, the quantity is also converted to the inventory unit, and vice versa. Asa general rule, you can assume that the order/schedule/contract/quotation quantity expressedin the (back) order unit appears first in a session, followed by the quantity in the inventory unit.Most of the time, you can only view the quantity in inventory unit in the details session, ifapplicable. The overview session only displays the quantity in the (back) order unit.

▪ On reports that contain quantities, you can choose to print the quantities in the (back) orderunit, or the inventory unit.

▪ The back order unit is introduced to enable you to express back order quantities in other unitsthan the order unit or the inventory unit.You can enter the back order quantity in the following sessions:

▪ Maintain and Confirm Back Orders (tdsls4125m000)

▪ Potential Purchase Back Orders (tdpur4101m700)

Note

The back order unit only appears in the Maintain and Confirm Back Orders (tdsls4125m000) sessionand the Potential Purchase Back Orders (tdpur4101m700) session. In all other sessions, the back orderquantity is expressed in the order unit, which is the sales unit, or the purchase unit.

Example Sales▪ Sales unit = pallet.▪ Inventory unit = pieces.

▪ Conversion factor = 1000 (1000 pieces on one pallet).▪ Another unit = box.

▪ Conversion factor between box and pallet = 4 (four boxes on one pallet).

▪ Conversion factor between box and pieces = 250 (250 pieces in one box).

If the order quantity is 20, 20 pallets are sold. If Warehouse Management does not deliver 20 pallets,but two boxes, the delivered quantity on the sales order line is displayed as 0.5 pallet (sales unit) and500 pieces (inventory unit).


Order Management

Example Purchase

▪ The purchase unit for the an item is pallet (a pallet contains 450 kilos)▪ The inventory unit for the item is kilo.▪ One kilo of the item costs €1.

▪ The order quantity is one pallet of the item.

▪ The supplier delivers one pallet of the item, which contains 500 kilos instead of 450 kilos.▪ A receipt of 500 kilos is registered.

▪ The receipt results in a purchase receipt transaction of €500 in Financials.

▪ The received quantity on the purchase order line is displayed as 1.11 pallet (purchase unit)and 500 kilos (inventory unit).

▪ Financials receives an invoice for €500.

Because the receipt is not only stored in the purchase unit pallet, but also in the inventory unit kilogram,automatic matching does not fail. A receipt of 1.11 pallet = 500 kilograms = €500

Print prices and discounts by business partner

ERP Baan5.0cIn ERP Baan5.0c, the setup of pricing is flexible. A user can decide on which level prices and discountsare defined by means of a set of matrix attributes in a matrix. However, it is not possible to print pricesand discounts for a specific business partner.

ERP LN 6.1In ERP LN 6.1, the following new sessions are available to print prices and discounts:

▪ Print Discounts via Discount Matrices (tdpcg0421m100)

▪ Print Prices via Price Matrices (tdpcg0431m100)

In these sessions, you can select the attributes, for example, a business partner, for which you want toprint prices and discounts.

You can start the Print Discounts via Discount Matrices (tdpcg0421m100) session from the Price Matrices(tdpcg0130m000) session. You can start the Print Prices via Price Matrices (tdpcg0431m100) from theDiscount Matrices (tdpcg0130m100) session.

Purchase back orders

This topic explains how the handling of purchase back orders has changed in ERP LN 6.1 comparedto ERP Baan5.0c.

Purchase back orders in ERP Baan5.0cIf back orders are allowed in ERP Baan5.0c, which you can define in the Purchase-Order Parameters(tdpur0100s400) session, you can register a particular quantity as back ordered when you maintainreceipts in the Purchase Order Receipts (tdpur4101s300) session. By default, ERP Baan5.0c displays


Order Management

a back order quantity equal to the order quantity less the quantity delivered. If required, you can overwritethis quantity.

In the Purchase Order Receipts (tdpur4101s300) session, you must also confirm the back orders if backorders are not confirmed automatically.

Purchase back orders in ERP LN 6.1In ERP LN 6.1 Purchase Control, potential back orders are introduced. A potential back order is a backorder that must be manually confirmed and that can be modified by the user.

As a result, separate sessions are developed for:

▪ Maintaining back orders.▪ Displaying confirmed back orders.

These are the following sessions:

▪ Potential Purchase Back Orders (tdpur4101m700), in which you can manually maintain backorders. This session replaces the former Purchase Order Receipts (tdpur4101s300) session.

▪ Confirmed Purchase Back Orders (tdpur4101m800), in which you can view confirmed backorders, both manually and automatically confirmed,

After a back order is processed, the back order no longer appears in the Confirmed Purchase BackOrders (tdpur4101m800) session, but the back order information moves into the regular PurchaseOrder/Schedule History (tdpur5505m000) session.

Note

Back order lines that are the result of rejection during inspection cannot be confirmed automatically andalways result into a potential back order. The reason for this is that a user must have the time to decidehow to handle the rejected inventory that is stored in the reject location of the warehouse, which canalso be accepted again.

For more information on:

▪ The automatic generation and confirmation of back orders, refer to Back orders - automaticconfirmation.

▪ The generation and manual confirmation of potential back orders, refer to Back orders - manualconfirmation.

Purchase orders for non-direct deliveries

This topic explains how the generation of purchase orders for non-direct deliveries, which is calledcross-docking in ERP LN 6.1, has changed compared to ERP Baan5.0c.

Cross-docking is the process by which inbound goods are immediately taken from the receipt locationto the staging location for issue. For example, this is used to fulfill an existing sales order for which noinventory is available.


Order Management

Non-direct deliveries in ERP Baan5.0cIn ERP Baan5.0c, you can generate planned purchase orders for non-direct delivery sales orders in theGenerate Purchase Order Advice for Sales Order (tdsls4240m000) session.

Cross-docking in ERP LN 6.1Changed in Infor ERP LN 6.1

In ERP LN 6.1, the following types of cross-docking exist:

▪ Static cross-dockingA cross-docking order is created in Sales Control and, by means of a purchase order advice,a purchase order is generated that is linked to the sales order. The order is called static,because you cannot maintain the cross-docking order or order lines inWarehouseManagement.

▪ Dynamic cross-dockingWith dynamic cross-docking you can:

▪ Create cross-docking orders and order lines in Warehouse Management.

▪ Change or cancel the cross-docking order and order lines at various points during thecross-docking process in Warehouse Management.

▪ Enable Infor ERP to automatically create cross-docking orders and/or cross-docking orderlines in Warehouse Management.

New in Infor ERP LN 6.1

Splitting deliveries is in fact splitting order lines. If purchase order lines or sales order lines are generated,you can split up the order lines into several delivery lines. As a result, multiple deliveries take place onone order line. If a cross-docking order exists and a split delivery is required, you can further split up adelivery line into several deliveries in the new Split Line (tdpur4000s000) session.

For detailed information on static cross-docking and the relation between cross-docking and splittingdeliveries, refer to Relation between cross-docking and splitting deliveries.

For more information on dynamic cross-docking, refer to Dynamic cross-docking.

Purchase order approval

This topic explains how you can approve purchase orders in ERP LN 6.1.

Purchase order approval in ERP Baan5.0cIn ERP Baan5.0c, you need not approve purchase orders in the purchase order procedure.

Purchase order approval in ERP LN 6.1New in Infor ERP LN 6.1

In ERP LN 6.1, purchase order approval is a mandatory step in the purchase order procedure.


Order Management

You can approve purchase orders:

▪ Based on approval rules for a range of purchase orders in the Approve Purchase Orders(tdpur4210m100) session.

▪ Manually, for a range of purchase orders in the Approve Purchase Orders (tdpur4210m100)session.

▪ Manually , for a specific purchase order. To approve a specific purchase order, click Approveon the specific menu of the Purchase Orders (tdpur4100m000) session, or the Purchase Order- Lines (tdpur4100m900) session.

For more information, refer to Purchase order approval.

Purchase order line types

This topic explains how purchase order line types have changed in ERP LN 6.1 compared to ERPBaan5.0c.

Order line types in ERP Baan5.0cIn ERP Baan5.0c, the following order line types are available:

▪ TotalThe purchase order line is split up in several sequences. The totaled quantities and amountsare visible in this line.

▪ DetailThis purchase order line is a normal line with a sequence number of zero. The line is createdmanually or is generated automatically.

▪ The purchase order line is a split order line with a sequence number greater than zero. As aresult, also a Total line exists.

▪ Back orderThe purchase order line is partially delivered and a back order is confirmed. As a result, a lineof type Back Order is generated with a sequence number greater than zero, which is linkedto the purchase order line of the type Detail.

Order line types in ERP LN 6.1Changed in Infor ERP LN 6.1

In ERP LN 6.1, a purchase order line can be of the following Order Line Type:

▪ Total: The purchase order line is split up in several sequences (receipt lines). The totaledquantities and amounts are visible in this line.

▪ Order Line: This purchase order line is a normal line. The line is created manually or isgenerated automatically.

A purchase order line detail can be of the following Order Line Type:

▪ Detail: This line is a split order line. The line is created manually or is generated automatically.Fields are taken by default from the Total line.


Order Management

▪ Back Order: This line is a back order line. It is created through back order confirmation. Fieldsare defaulted from the original line with the back order quantity.

When anOrder Line is generated in the Purchase Order - Lines (tdpur4100m900) session, the purchaseorder line's sequence number is one. When the relevant order line is split, or a back order is generatedfor the order line, the order line changes to a Total line with a sequence number of zero. The linkeddetail lines of line type Detail or Back Order have a sequence number greater than zero. As a result,in ERP LN 6.1, a purchase order line can no longer have a back order line linked. The purchase orderline is always converted into a purchase order line of the type Total and a detail line of the type BackOrder.

To have the correct information on the various order lines, the Detail lines and the Back Order linesare synchronized with the Total and vice versa, when they are updated. For more information, refer toSynchronization between purchase order line and purchase order line detail.


▪ Sequence numbering, refer to Sequence numbers in Purchase Control (PUR).

▪ The changed procedure for entering purchase orders and purchase order lines, refer toOrderentry (p. 139) .

Purchase order origin

This topic explains how the purchase order origins have changed in ERP LN 6.1 compared to ERPBaan5.0c.

Purchase order origins in ERP Baan5.0cIn ERP Baan5.0c Purchase Control, you can view the origin of the purchase order in the Purchase OrderHeaders (tdpur4100s000) session.

Purchase order origins in ERP LN 6.1In ERP LN 6.1 Purchase Control, you can view the origin of the purchase order in the Purchase OrderOrigin field of the Purchase Orders (tdpur4100m000) and Purchase Order - Lines (tdpur4100m900)session.


The following purchase order origins have changed in ERP LN 6.1:

▪ EPThe order results from the execution of the Transfer Planned Orders (cppat1210m000) sessionin Enterprise Planning.This origin replaces the following ERP Baan5.0c origins:▪ SCP▪ PCS

▪ ContractsThe order results from the execution of the Generate Purchase Orders (tdpur3204m000)session. For more information, refer to To set up a delivery contract.


Order Management

▪ ManualThe purchase order is entered manually in the Purchase Order - Lines (tdpur4100m900)session.


The following purchase order origins are new in ERP LN 6.1:

▪ ASCThe order results from the execution of the Generate WIP Transfer (tiasc7200m000) sessionin Manufacturing.

▪ ComminglingThe order results from the execution of the Commingle Purchase Orders (tdpur4210m000)session. For more information, refer to Purchase orders for commingling.

▪ MaintenanceThe order results from the execution of the Work Order Planning/Releasing (tswcs3200m000)session in Service. For more information, refer to Integration between Purchase Control andDepot Repair.

Purchase order receipt information

This topic explains how the storage of purchase order receipt information has changed in ERP LN 6.1compared to ERP Baan5.0c.

Receipt information in ERP Baan5.0cIn ERP Baan5.0c, you can view receipt information onmany places in Purchase Control (PUR). However,no separate sessions exist in which you can view information on actual receipts.

Receipt information in ERP LN 6.1New in Infor ERP LN 6.1

To centrally store information on actual receipts, the following sessions are new in ERP LN 6.1:

▪ Purchase Receipts (tdpur4106m000), which stores the receipts that are recorded for a purchaseorder line.

▪ Purchase Actual Receipt History (tdpur4556m000), which stores the purchase order actualreceipt history, based on which reconciliation takes place for purchase orders.

▪ Print Purchase Actual Receipts (tdpur4406m000).

Note

▪ You can also view receipt information in the changed Purchase Orders - Receipt Overview(tdpur4531m000) session.

▪ The Purchase Order - Receipts (tdpur4501m300) session is expired.


Order Management

Correct purchase receiptsFor non-inventory items, you can enter multiple purchase receipts for one order line in the PurchaseReceipts (tdpur4106m000) session. You must confirm the purchase receipt after it is saved. Afterconfirmation, you can no longer correct the receipt in the Purchase Receipts (tdpur4106m000) session.However, in the new Correct Purchase Receipt (tdpur4106s100) session, you can still correct specificreceipt data.

▪ Confirm receiptsTo confirm a purchase receipt, click Confirm Receipt on the specific menu of the PurchaseReceipts (tdpur4106m000) session. As a result, the Confirmed check box is selected.

▪ Correct receiptsTo correct a confirmed receipt, click Correct Purchase Receipt on the specific menu of thePurchase Receipts (tdpur4106m000) session. As a result, the Correct Purchase Receipt(tdpur4106s100) session is started in which you can correct the confirmed receipts fornon-inventory items.You can change the following fields in this session:▪ Received Quantity▪ Packing Slip Quantity▪ Final Receipt

Receipts for direct delivery ordersIf you use advance shipment notices, receipts for items that are purchased for a direct delivery salesorder, are inserted in the Purchase Receipts (tdpur4106m000) session as soon as you click ReceiveDirect Delivery Lines in the Shipment Notices (whinh3100m000) session. If you do not use advanceshipment notices, you must manually enter the receipts for direct delivery sales orders in the PurchaseReceipts (tdpur4106m000) session.

You must use the new Update Sales Order with Delivery Information (tdpur4222m000) session tocommunicate the item, quantity, lot and serial information back to Sales Control for final receipts. Foreach purchase order receipt line that is registered in the Purchase Receipts (tdpur4106m000) session,a sales order delivery line is created in the Sales Order Line - Deliveries (tdsls4101m900) session andthe Sales Order Actual Delivery Lines (tdsls4106m000) session.

For more information, refer to Direct delivery.

Purchase order status

This topic explains how you can move a purchase order to the next status in ERP LN 6.1.

Purchase order line status in ERP Baan5.0cIn ERP Baan5.0c, you can only view the status of a purchase order line.


Order Management

Purchase order (line) status in ERP LN 6.1In ERP LN 6.1, you cannot only view the status of a purchase order line, but also of a purchase orderheader. The purchase order header status enables you to view what actions must be performed to movethe order to the next status.

You can view the purchase order line activity status in the following sessions:

▪ Purchase Order Line Status (tdpur4534m000)▪ Purchase Order Lines Monitor (tdpur4501m500)


In the Status field of the Purchase Order - Lines (tdpur4100m900) session, or the Purchase Orders(tdpur4100m000) session, you can view the status of the purchase order. Because statuses can differfor each order line, the header status shows the lowest line status.

Now that you know the purchase order status, you know what actions you must perform to move theorder to the next status. You can make a selection with which orders you want to proceed. If you clickView on the specific menu of the Purchase Order - Lines (tdpur4100m900) session, or the PurchaseOrders (tdpur4100m000) session, you can select the purchase orders that await a particular action.

You can make a selection based on the following statuses:

▪ Open OrdersDisplays all orders for which no receipts are booked yet.

▪ Orders for PrintingDisplays all orders that are waiting to be printed in the Print Purchase Orders (tdpur4401m000)session.

▪ Orders for Release to WarehousingDisplays all orders that are waiting to be released to Warehouse Management in the ReleasePurchase Orders to Warehousing (tdpur4246m000) session.

▪ Orders for Manual ActivitiesDisplays all orders that are waiting for a manual activity, which you can execute in the PurchaseOrders - by Manual Activities (tdpur4501m150) session.

▪ Orders for ProcessingDisplays the orders that are waiting to be closed in the Process Purchase Orders(tdpur4223m000) session.

Note

▪ To view the purchase orders with the Created status that are waiting for commingling, filteron the For Commingling check box in the Purchase Order - Lines (tdpur4100m900) session,or the Purchase Orders (tdpur4100m000) session and commingle the purchase orders in theCommingle PurchaseOrders (tdpur4210m000) session. For more information, refer to Purchaseorders for commingling.

▪ To track a purchase order through the order's life cycle, the objects, such as orders, invoicesand so on that are linked to the purchase order line, are added to the Purchase Order LinesMonitor (tdpur4501m500) session. You can click Open Object to open the linked object. Asa result, if you await a particular action from another package before you can continue theorder procedure, you can also view the linked order and its status.


Order Management

▪ You can convert Created purchase orders to Approved purchase orders in the ApprovePurchase Orders (tdpur4210m100) session, or in the Purchase Order - Lines (tdpur4100m900)session and Purchase Orders (tdpur4100m000) sessions.

Purchase requisition enhancements

This topic explains how the purchase requisition functionality has changed in ERP LN 6.1 compared toERP Baan5.0c.

Purchase requisitions in ERP Baan5.0cIn ERP Baan5.0c, any requestor in a company can raise a purchase requisition and forward it to approversin the list for approval. No hierarchy exists among the approvers.

If changes are made to the requisition during the approval process, you cannot track these changes.

Purchase requisitions in ERP LN 6.1Changed in Infor ERP LN 6.1

In ERP LN 6.1, a hierarchy in the approval structure is built, so the first approver knows to whom therequisition must next be forwarded. As a result, a clear approval path among the approvers exists withinan organization. For more information, refer to Approval process.

A revision number is introduced that tracks the changes made to the requisition. Each time a change ismade to the requisition, the revision number is incremented. This helps organizations analyze and auditrevisions that often lead to delays, and carry out improvements to avoid such delays. For more information,refer to the Revision field in the Purchase Requisition (tdpur2101s000) session.

Purchase schedules

This topic explains the new purchase schedule functionality in ERP LN 6.1.

A purchase schedule is a timetable of planned supply of materials. Purchase schedules support long-termpurchasing with frequent deliveries and are usually backed by a purchase contract. All requirements forthe same item, buy-from business partner, ship-from business partner, purchase office, and warehouseare stored in one schedule.

▪ New in Infor ERP LN 6.1In ERP LN 6.1, the purchase schedule procedure is introduced. Because this procedure iscompletely new, refer to the following online manual topics:▪ Purchase schedules, basic data▪ Planned delivery moments▪ Push schedules▪ Receipts on push schedule lines▪ Pull forecast schedules

▪ Constraints for generating non-referenced purchase schedule lines▪ Pull call-off schedules


Order Management

▪ To create and update sequence shipping schedule lines▪ Segment sets▪ Purchase schedule release types▪ Purchase releases▪ Clustering purchase schedule lines▪ To approve and reject scheduled items▪ Authorizations▪ Resetting authorizations▪ Purchase schedule cumulatives▪ Resetting purchase schedule cumulatives

Note

If you want to use a simplified purchase schedule functionality, you can define scheduled deliveriesbased on a purchase contract. This functionality applies if you do not send schedules to your buy-frombusiness partners, but you do want to set up a list of time-phased receipts based on a purchase contract.For more information, refer to To set up a delivery contract.

Reconciliation (Purchase Control)

This topic explains how the redesigned reconciliation functionality of ERP LN 6.1 Financials, affectsERP LN 6.1 Purchase Control.

Reconciliation in ERP Baan5.0cIn ERP Baan5.0c, the reconciliation functionality, which is part of Financials, is very limited. For details,refer to Reconciliation (p. 77) .

Reconciliation in ERP LN 6.1In ERP LN 6.1, the reconciliation functionality is revised completely. Because reconciliation takes placein Financials, it is not explained in this topic. Only the fields and sessions in Purchase Control that areaffected by reconciliation, are discussed. For more information on financial reconciliation, refer toReconciliation overview.

History dataIn ERP LN 6.1, reconciliation can be performed on purchase orders, purchase schedules, and purchasecontracts.

Reconciliation is always based on the history data and never on actual data. As a result, define thefollowing parameters:

▪ Set the LogOrder History Data field toAll in the PurchaseOrder Parameters (tdpur0100m400)session.

▪ In the Purchase Contract Parameters (tdpur0100m300) session:

▪ Set the Log Contract Line Transactions field to All Transactions.


Order Management

▪ Select the Log Turnover on Contract check box.▪ Select the Log financial transactions check box.

ERP LN 6.1 performs reconciliation based on:

▪ Purchase order actual receipt history in the new Purchase Actual Receipt History(tdpur4556m000) session.

▪ Purchase schedule line history in the Purchase Schedule Line History (tdpur3561m000)session.

▪ Purchase contract line history in the Purchase Contract Line - History (tdpur3551m000) session.

Deleting history dataBecause ERP LN 6.1 uses the history data for reconciliation purposes, you can only delete history dataif the data is no longer required for reconciliation.

You can delete purchase order/schedule history data and purchase contract history data in the followingsessions:

▪ Archive/Delete Purchase Order/Schedule History (tdpur5201m000)

▪ Delete Purchase Contract History (tdpur3202m000)

Reconciliation (Sales Control)

This topic explains how the redesigned reconciliation functionality of ERP LN 6.1 Financials, affectsERP LN 6.1 Sales Control.

Reconciliation in ERP Baan5.0cIn ERP Baan5.0c, the reconciliation functionality, which is part of Financials, is very limited. For details,refer to Reconciliation (p. 77) .

Reconciliation in ERP LN 6.1In ERP LN 6.1, the reconciliation functionality is revised completely. Because reconciliation takes placein Financials, it is not explained in this topic. Only the fields and sessions in Sales Control that areaffected by reconciliation, are discussed. For more information on financial reconciliation, refer toReconciliation overview.

History dataIn ERP LN 6.1, reconciliation can be performed on sales orders and sales schedules.

Reconciliation is always based on the history data and never on actual data. As a result, you must setthe Log Sales Order History field to All in the Sales Order Parameters (tdsls0100s400) session.

ERP LN 6.1 performs reconciliation based on:

▪ Sales order line history in the Sales Order Line History (tdsls4551m000) session.


Order Management

▪ Sales schedule line history in the Sales Schedule Line History (tdsls3561m000) session.

Deleting history dataBecause ERP LN 6.1 uses the history data for reconciliation purposes, you can only delete history dataif the data is no longer required for reconciliation.

You can delete sales order/schedule history data in the Archive/Delete Sales Order/Schedule History(tdsls5201m000) session.

Sales order acknowledgements

This topic explains how the order acknowledgement's printing functionality is refined in ERP LN 6.1compared to ERP Baan5.0c.

Sales order acknowledgements in ERP Baan5.0cAfter a sales order is entered in ERP Baan5.0c, you can print an order acknowledgement in the PrintOrder Acknowledgements/RMAs (tdsls4401m000), after which you can send it to your customer.

Sales order acknowledgements in ERP LN 6.1In ERP LN 6.1, you can still use the Print Sales Order Acknowledgements/RMAs (tdsls4401m000)session to print order acknowledgements.


However, the following functionality is added to this session:

▪ With the Promotions check box you can indicate whether you want to print promotions onthe order acknowledgement, if promotions apply to the order.

▪ With the Print UEF Requirements check box you can indicate whether you want to printrequirements on the order acknowledgement, if a unit effective item applies to the order.

▪ You can control the printing of order acknowledgements based on the order amount and/orthe delivery date. These conditions only apply for order types that do not have the Print SalesOrder Acknowledgements/RMAs (tdsls4401m000) linked as a mandatory activity to the ordertype in the Sales Order Type - Activities (tdsls0560m000) session.

Conditions for printingIf you want to control the printing of order acknowledgements based on the order amount and/or thedelivery date, perform the following in the Print Sales Order Acknowledgements/RMAs (tdsls4401m000)session:

▪ Set the Order Line Types to Print field to All Lines.▪ Enter an amount in the Order Amount From field, which indicates from what order amount

the order acknowledgement must be printed. ERP LN 6.1 only prints those order lines withan amount greater than or equal to the entered amount.


Order Management

▪ Enter a date and time in the Delivery Date From field, which indicates from what deliverydate the order acknowledgement must be printed. ERP LN 6.1 only prints those order lineswhose delivery date falls after the entered date.

Note

▪ Use the Print Sales Orders to be Acknowledged (tdsls4401m100) session to print an overviewof sales orders that you must still acknowledge.

▪ Use the Preview Acknowledgments/RMAs (tdsls4401m200) session to have a preview ofsales order lines as if they were acknowledged.

Sales order approval

This topic explains how you can approve sales orders in ERP LN 6.1.

Sales order approval in ERP Baan5.0cIn ERP Baan5.0c, you need not approve sales orders in the sales order procedure.

Sales order approval in ERP LN 6.1New in Infor ERP LN 6.1

In ERP LN 6.1, sales order approval is a mandatory step in the sales order procedure.

To approve a sales order, perform the following:

▪ Select a sales order and click Approve on the specific menu of the Sales Order - Lines(tdsls4100m900) session, or the Sales Orders (tdsls4100m000) session.

▪ Run the Approve Sales Orders (tdsls4211m000) session, in which you can approve a rangeof sales orders.

Note

▪ When a sales order is approved, flexible sales order processing can start. For more information,refer to Flexible sales order processing.

▪ If you defined a sales order as a rush order, the order cannot be rushed before the orderreceives the Approved status. After the rush order is released to Warehouse Management,the order has priority over normal sales orders. For more information, refer to Rush orders.

Sales contracts

This topic explains how the sales contract procedure has changed in ERP LN 6.1 compared to ERPBaan5.0c.

Sales contracts in ERP Baan5.0cIn ERP Baan5.0c, sales contracts can be linked to sales orders.


Order Management

Sales contracts in ERP LN 6.1Changed in Infor ERP LN 6.1

Because of the new sales schedule functionality in ERP LN 6.1, sales contracts cannot only be linkedto sales orders, but also to sales schedules. For more information, refer to Sales contracts.


In ERP LN 6.1, you can define scheduled deliveries based on a sales contract. This functionality canbe useful if you do not receive schedules from your sold-to business partners, but you do want to setup a list of time-phased deliveries based on a sales contract. As a result, this is a kind of simplified salesschedule functionality.

You can define scheduled requirements for a sales contracts by means of :

▪ Delivery schemesIf you want to use delivery schemes, you must define sales contract delivery lines that containdelivery dates and quantities. You can automatically generate sales orders from a deliveryscheme. For more information, refer to To define contract deliveries by means of deliveryschemes.

▪ Sales schedulesIf you want to use sales schedules, you must generate a sales schedule on contract line level,after which the sales schedule process is automatically started. For more information, referto To define contract deliveries by means of sales schedules.

Tip

The easiest way to set up and process scheduled requirements for a sales contract is to define a deliveryscheme.

Sales order delivery and invoice information

This topic explains how the storage of sales order delivery and invoice information has changed in ERPLN 6.1 compared to ERP Baan5.0c.

Delivery and invoice information in ERP Baan5.0cIn ERP Baan5.0c, you can view delivery and invoice information on many places in Sales Control.However, no separate sessions exist in which you can view information on actual deliveries and invoices.

Delivery and invoice information in ERP LN 6.1New in Infor ERP LN 6.1

To centrally view information on actual deliveries, the following sessions are new in ERP LN 6.1:

▪ Sales Order Actual Delivery Lines (tdsls4106m000), which stores the actual delivery informationfor sales orders.

▪ Sales Order Actual Delivery Line COGS (tdsls4109m000), which stores the actual cost ofgoods sold (COGS) information for sales orders.


Order Management

▪ Print Sales Order Actual Delivery Lines (tdsls4406m100).

After a sales order is released to Central Invoicing, sales invoice information is reported back to SalesControl. You can view this data in the following sessions:

▪ Sales Order Actual Delivery Lines (tdsls4106m000)▪ Sales Order Invoice Lines (tdsls4106m100)

If you use direct delivery orders, for each purchase order receipt line, a sales order delivery line is createdin the Sales Order Line - Deliveries (tdsls4101m900) session and the Sales Order Actual Delivery Lines(tdsls4106m000) session when you communicate the deliveries to Sales Control with the new UpdateSales Order with Delivery Information (tdpur4222m000) session. For more information, refer to Directdelivery.

Note

▪ You can also view delivery and invoice information in the changed Sales Order Lines Monitor(tdsls4510m000) session.

▪ If you use direct delivery orders, for each purchase order receipt line, a sales order deliveryline is created in the Sales Order Line - Deliveries (tdsls4101m900) session and the SalesOrder Actual Delivery Lines (tdsls4106m000) session when you communicate the deliveriesto Sales Control with the new Update Sales Order with Delivery Information (tdpur4222m000)session. For more information, refer to Direct delivery

Sales order line types

This topic explains how sales order line types have changed in ERP LN 6.1 compared to ERP Baan5.0c.

Order line types in ERP Baan5.0cIn ERP Baan5.0c, the following order line types are available:

▪ TotalThe sales order line is split up in several sequences. The totaled quantities and amounts arevisible in this line.

▪ DetailThis sales order line is a normal line with a sequence number of zero. The line is createdmanually or is generated automatically.

▪ The sales order line is a split order line with a sequence number greater than zero. As a result,also a Total line exists.

▪ Back orderThe sales order line is partially delivered and a back order is confirmed. As a result, a line oftype Back Order is generated with a sequence number greater than zero, which is linked tothe sales order line of the type Detail.

Order line types in ERP LN 6.1Changed in Infor ERP LN 6.1


Order Management

In ERP LN 6.1, a sales order line can be of the following Line Type:

▪ Order Line: The sales order line is split up in several sequences (delivery lines). The totaledquantities and amounts are visible in this line. This line type is also referred to as a Total Line.

▪ Order/Delivery Line: This sales order line is a normal line. The line is created manually or isgenerated automatically.

A delivery line, which is called a sales order line detail in ERP Baan5.0c, can be of the following LineType:

▪ Order/Delivery Line: The delivery line is a split order line.▪ Back Order: The delivery line is a back order line.

When an Order/Delivery Line is generated in the Sales Order - Lines (tdsls4100m900) session, thesales order line's sequence number is zero. When the relevant order line is split, or a back order isgenerated for the order line, the order line changes to an Order Line line with a sequence number ofzero. The linked delivery lines of line typeOrder/Delivery Line orBack Order have a sequence numbergreater than zero. As a result, in ERP LN 6.1, a sales order line can no longer have a back order linelinked. The sales order line is always converted into a sales order line of the type Order Line and adelivery line of the type Back Order.

To have the correct information on the various order lines, the Order/Delivery Line lines and the BackOrder lines are synchronized with the Order Line and vice versa, when they are updated. For moreinformation, refer to Synchronization between sales order line and delivery lines.


▪ Sequence numbering, refer to Sequence numbers in Sales Control (SLS).

▪ The changed procedure for entering sales orders and sales order lines, refer to Order entry(p. 139) .

Sales order status

This topic explains how you can move a sales order to the next status in ERP LN 6.1.

Sales order line status in ERP Baan5.0cIn ERP Baan5.0c, you can only view the activity status of a sales order line.

Sales order (line) status in ERP LN 6.1In ERP LN 6.1, you cannot only view the activity status of a sales order line, but also view the status ofa sales order header. Because activity statuses can differ for each order line, ERP LN displays a headerstatus that corresponds to the lowest line activity status.

You can view the sales order line activity status in the following sessions:

▪ Sales Order Line Status (tdsls4534s000)▪ Sales Order Lines Monitor (tdsls4510m000)



Order Management

In the Status field of the Sales Order - Lines (tdsls4100m900) session, or the Sales Orders(tdsls4100m000) session, you can view the status of the sales order.

The following mandatory statuses are available:

▪ Free: The order is created in the Sales Order - Lines (tdsls4100m900) session and waits forapproval.

▪ Approved: The order is approved in the Sales Orders (tdsls4100m000) session, the SalesOrder - Lines (tdsls4100m900) session, or the Approve Sales Orders (tdsls4211m000) session.

▪ In Process: The order can be at various stages of the delivery procedure.▪ Closed: The order is processed in the Process Delivered Sales Orders (tdsls4223m000)

session.

The following optional statuses are available:

▪ Modified: The order is modified after approval because order lines are added or adapted. Asa result, the sales order must be approved again.

▪ Canceled: The order is canceled and is no longer available for further execution. You cancancel (a range of) sales orders in the Cancel Sales Orders (tdsls4201s300) session.

▪ Blocked: The order is blocked and is (temporarily) not available for further execution.

Note

To know what action you must perform to move the order line to the next activity status and the orderto the next status, view the Ready for field in the Sales Order Lines Monitor (tdsls4510m000) session,which is called the Sales Order Lines Overview (tdsls4510m000) session in ERP Baan5.0c. This fieldinforms you about the next activity to be executed in the order procedure.

To track a sales order through the order's life cycle, the objects, such as orders, invoices and so on thatare linked to the sales order line, are added to the Sales Order Lines Monitor (tdsls4510m000) session.You can click Open Object to open the linked object. As a result, if you await a particular action fromanother package before you can continue the order procedure, you can also view the linked order andits status.

Sales price includes upgrade price for unit effective items

ERP Baan5.0cIn case special components or accessories are used, it is common practice that a sold-to businesspartner must pay an additional (upgrade) price for these components or accessories. ERP Baan5.0cdoes not support the use of upgrade prices.

ERP LN 6.1In ERP LN 6.1, you can define an upgrade price for every requirement in the Requirements(tcuef0106m000) session. If you use unit effectivity to configure an item, for every requirement that youselect for a effectivity unit, the requirement's upgrade price is added to the effectivity unit's sales price.


Order Management

As a result, in each session in which sales order/quotation lines prices are used or displayed, upgradeprices are added to, or included in the sales price for unit effective items.

For more information about how to configure an effectivity unit, refer to:

▪ To configure effectivity units

▪ Unit effectivity as a lean configurator in Sales Control

Sales return orders

This topic explains how the return order functionality is extended in ERP LN 6.1 compared to ERPBaan5.0c.

Return orders in ERP Baan5.0cIn ERP Baan5.0c, you cannot use directly delivery for sales return orders. If you ordered items from aspecific buy-from business partner for a specific customer, and the customer sends one or more itemsback, you will receive the items first in the warehouse registered in ERP LN.

Return orders in ERP LN 6.1

Changed in Infor ERP LN 6.1In ERP LN 6.1, sales return orders can be directly delivered from your customer (sold-to businesspartner) to your buy-from business partner. In that case, no goods are received in your own warehouse.

For a sales return order with direct delivery, a normal order type with negative quantities can be usedas well as a return order type. In the Sales Order Types (tdsls0594m000) details session, you can usethe Return Order field to define a sales order as a return order.


Serialized items and return ordersIn ERP LN 6.1, serialized items are introduced. A serialized item is a physical occurrence of a standarditem that is given a unique lifetime serial number. This enables you to track the individual item throughoutits lifetime, for example, through the design, production, testing, distribution, and maintenance phases.A serialized item can consist of other serialized components.

In ERP LN 6.1, you can return serialized items on a sales order. Serialized items that are returned ona sales order can be unlinked in Service and the sales return order can be updated with the deliveryinformation for the serialized items.

As a result, the following changes are introduced to enable the return order handling for serialized items:

▪ A cluster is automatically linked to the return order when the delivery information is updatedon the order by means of the Warehouse Receipts (whinh3512m000) session, or the UpdateSales Order with Delivery Information (tdpur4222m000) session.


Order Management

However, a cluster is not linked automatically if:

▪ The serialized items on the sales return order line are linked to different clusters in Service.

▪ The item is an anonymous item, or the items are serialized in Service only.If required, you can unlink a cluster from the sales return order line, link an item to a cluster,or link a cluster to the sales return order line in the Sales Order Lines (tdsls4101m000) session.

▪ The following options are added to the specific menu of the Sales Order Lines (tdsls4101m000)session:▪ Link Cluster to Sales Order Line...▪ Unlink Cluster from Sales Order Line▪ Unlink item from Cluster▪ Link Item to Cluster▪ Delete Physical Breakdown

For more information, refer to Lot control by serialized items (p. 27)

Customer approval and return ordersIn ERP LN 6.1, the customer approval functionality is introduced. Customer approval refers to the deliveryof goods: the sold-to business partner must approve the goods that are delivered on a sales order beforethe goods can be invoiced. The ownership of the goods does not change from supplier to sold-to businesspartner until the goods are approved by the sold-to business partner.

If customer approval is implemented, you can automatically generate a sales return order for the rejectedquantity. For more information, refer to Customer approval.

Sales schedules

This topic explains the new sales schedule functionality in ERP LN 6.1.

A sales schedule is a timetable of planned supply of materials. Sales schedules support long-term saleswith frequent deliveries. All requirements for the same item, sold-to business partner, ship-to businesspartner, and delivery parameter are stored in the same sales schedule.

▪ New in Infor ERP LN 6.1In ERP LN 6.1, the sales schedule procedure is introduced. Because this procedure iscompletely new, refer to the following online manual topics:▪ Sales schedule process▪ EDI and sales schedules▪ Sales releases▪ Sales schedules▪ Sales schedule revisions

▪ Zero required quantity for sales schedule lines▪ Referenced sales schedules▪ Sales schedule type▪ Sales schedule line requirement type▪ To approve sales schedules▪ Sales schedule adjustment


Order Management

▪ Sales schedules and Enterprise Planning▪ Sales schedules and Warehouse Management▪ Sales schedules and Central Invoicing▪ To terminate sales schedules▪ To process/delete sales schedules▪ To reconcile sales schedules▪ Sales schedule authorizations▪ Sales schedule cumulatives

Note

If you want to use a simplified sales schedule functionality, you can define scheduled deliveries basedon a sales contract. This functionality applies if you do not receive schedules from your sold-to businesspartners, but you do want to set up a list of time-phased deliveries based on a sales contract. For moreinformation, refer to Scheduled requirements for a sales contract.

Self billing

This topic explains how the self billing functionality has changed in ERP LN 6.1 compared to ERPBaan5.0c.

Self billing in ERP Baan5.0cSelf billing is a method to pay the suppliers without waiting for their invoices. In ERP Baan5.0c self billingis only possible after approval of the goods received.

Self billing in ERP LN 6.1Changed in Infor ERP LN 6.1

In ERP LN 6.1, self billing is not only possible after approval of the goods received, but also after receiptof the goods. If the goods are rejected in a later stage, you can send the supplier a debit note for therejected quantities.

For more information, refer to Self billing.

Shipping constraints

This topic explains how the naming of the shipping constrainst has changed in ERP LN 6.1 comparedto ERP Baan5.0c.

Shipping constraints in ERP Baan5.0cIn ERP Baan5.0c, you can select the following shipping constraints:

▪ Order Complete▪ Ship Complete▪ Release Complete


Order Management

▪ Ship & Cancel▪ None

Shipping constraints in ERP LN 6.1Changed in Infor ERP LN 6.1

In ERP LN 6.1, the following shipping constraints are available:

▪ Ship Line CompleteEach order line must be delivered as a whole. baan assigns a unique set number to eachorder line. Lack of inventory results in the postponement of shipment of the order line. This isthe Ship Comlete constraint in ERP Baan5.0c.

▪ Ship Set CompleteAll the order lines with the following common delivery criteria must be shipped in a singleshipment:▪ Delivery date.▪ Carrier.▪ Warehouse.▪ Ship-to business partner.▪ Ship-to address.This is the Release Complete constraint in ERP Baan5.0c.

▪ Ship Order CompleteThe total order must be shipped in a single shipment. As a result, baan does not allow partialdeliveries. Lack of inventory results in the postponement of shipment of the order. This is theOrder Comlete constraint in ERP Baan5.0c.

▪ Ship Line & CancelThe available inventory is shipped. If sufficient inventory exists, this results in a completeshipment. Lack of inventory does not result in a back order but in cancellation of the order forthe remaining quantity. baan enters a predefined cancel reason to the order line. This cancelreason is defined in the Pre-Defined Cancellation Reason for Ship/Cancels field of theSales Order Parameters (tdsls0100s400) session. This is the Ship & Cancel constraint inERP Baan5.0c.

▪ NoneThere is no shipping constraint. The same naming is used in ERP Baan5.0c.

You can enter a shipping constraint in the following sessions:

▪ Sales Quotations (tdsls1100s000). If you set a shipping constraint in this session, Baan ERPautomatically enters this constraint on the sales quotation lines.

▪ Sales Quotation Lines (tdsls1101s000).

▪ Sales Orders (tdsls4100m000). If you set a shipping constraint in this session, Baan ERPautomatically enters this constraint on the sales order (delivery) lines.

▪ Sales Order Lines (tdsls4101m000).▪ Delivery Lines (tdsls4101m100).

When a sales order (delivery) line with a shipping constraint is saved, baan automatically enters a setnumber for the sales order (delivery) line in the Sales Order Lines - Shipping Constraints Related Sets


Order Management

(tdsls4507m000) session. When you release sales order lines to Warehouse Management, order lineswith the same set number are released simultaneously.

Synchronize header - lines

ERP Baan5.0cIf you make changes in ERP Baan5.0c, in the header of a sales order, sales quotation, contract, purchaseorder, or request-for-quotation, these changes are not synchronized with the information on the line(s).

ERP LN 6.1New in Infor ERP LN 6.1

If you change a header in ERP LN 6.1, a session appears in which you can choose to synchronize thelines.

The following sessions can appear:

▪ In Sales Control, the Sales Order - Lines - Synchronization (tdsls0280m000) session.

▪ In Purchase Control, the Purchase Order - Lines - Synchronization (tdpur0280m000) session.

Tax

Tax in ERP Baan5.0cIn ERP Baan5.0c, the set up and defaulting of tax data is not always sufficient or handled correctly.

Tax in ERP LN 6.1In ERP LN 6.1, the tax model has changed completely. Most sessions for the setup and execution oftax registration and declaration are stored in the Tax Handling module of the Common Data package.For details, refer to Overview of tax handling.

As a result of this improved tax model, the tax defaulting logic has changed completely. In the TaxParameters (tctax0100m000) session, you can specify how ERP LN determines the tax code, the taxcountry, and the business partner's tax country of taxable transactions.

If, for example, a sales order is created and all logistic data is entered, such as the warehouse, theship-to address, the invoice-to address, tax related data is defaulted to the order. If the logistic datachanges, the tax data is defaulted again.


Due to this improved tax model, tax is now modeled at line level in Order Management. As a result, thefollowing has changed:

▪ Tax data is removed from various header sessions and added to various lines sessions in thePurchase Control and Sales Control modules.


Order Management

▪ Terms of delivery and point of title passage are added to various lines sessions in the PurchaseControl and Sales Control modules.

Removed and added tax data

RemovedThe Country and Tax fields are removed from the following header sessions in ERP LN 6.1:

▪ (Request for) quotations▪ Contracts▪ Schedules▪ Orders

AddedThe following fields are new in ERP LN 6.1:

▪ Tax ID▪ BP Tax Country▪ BP Tax ID▪ Exempt

These fields are added to the following lines sessions:

▪ Sales Quotation Lines (tdsls1101s000)▪ Sales Contract Lines (tdsls3101s000)▪ Sales Schedule - Lines (tdsls3107m000)▪ Sales Order Lines (tdsls4101m000)▪ Sales Order Delivery Lines (tdsls4101m100)▪ Sales Installment Orders (tdsls4110m000)▪ Buy-from BP - Quotation (tdpur1106s000)▪ Purchase Contract Lines (tdpur3101m000)▪ Purchase Schedule - Lines (tdpur3111m000)▪ Purchase Release - Lines (tdpur3121m000)

▪ Purchase Release Line - Details (tdpur3522m000)▪ Purchase Order Lines (tdpur4101m000)▪ Purchase Order Line Details (tdpur4101m200)

Terms of delivery and point of title passageNew in Infor ERP LN 6.1

Because the terms of delivery and the new point of title passage field are strongly related to the taxsituation, these fields are not only available on the header, but also on the lines in ERP LN 6.1. On theorder header, the terms of delivery and point of title passage serve as a default for the lines.

For example, if for one order several shipments must be executed on different moments in time, theterms of delivery and point of title passage might differ per shipment and therefore per line. If one line


Order Management

is delivered later than the others, it must be possible to use a different carrier with a different term ofdelivery and point of title passage. To enable this, the terms of delivery and the point of title passagemust be available on order line and order line detail level.

The Terms of Delivery and Point of Title Passage fields are added to the following sessions:

▪ Sales Order - Lines - Synchronization (tdsls0280m000)▪ Sales Quotation Lines (tdsls1101s000)▪ Sales Contract Lines (tdsls3101s000)▪ Sales Order Lines (tdsls4101m000)▪ Sales Order Delivery Lines (tdsls4101m100)

▪ Purchase Order - Lines - Synchronization (tdpur0280m000)▪ Purchase Contract Lines (tdpur3101m000)▪ Purchase Order Lines (tdpur4101m000)▪ Purchase Order Line Details (tdpur4101m200)

Note

You can not use blank tax codes in ERP LN 6.1.

Modules

Commission Control System (CMS) module - B50c/ERP61

This topic describes the most important differences between the Commission Control System (CMS)module in ERP Baan5.0c and in ERP LN 6.1.

Changed functionalityIn ERP Baan5.0c, if a link with Financials exists for commissions and rebates, invoices are createddirectly in the Commission Control System (CMS) module and are posted to the General Ledger(GLD) module of Financials.

In ERP LN 6.1, if a link with Financials exists for commissions and rebates, Commission Control Systempasses on invoice requests for rebates to Central Invoicing and for commissions to the Accounts Payable(ACP) module of Financials.

As a result of the modified invoicing functionality, the following changes are made in ERP LN 6.1:

▪ Commission and rebate currenciesIf different currencies are used, you can control the calculation of commissions and rebatesin a detailed way. As a result, commissions and rebates can be correctly converted from onecurrency to another. For more information, refer toCommission and rebate currencies (p. 126).


Order Management

▪ Release commissions/rebates to invoicingCommissions are released to the Accounts Payable module of Financials and rebates arereleased to Central Invoicing. For more information on the changed invoicing procedure, referto Invoicing commissions and rebates (p. 132) .

▪ Draft invoicesIf you want to print a draft invoice for commissions and rebates in ERP Baan5.0c, you mustclear the Final Invoices check box in the Print Commission/Rebate Invoices (tdcms2402m000)session.In ERP LN 6.1:

▪ You can no longer print a draft invoice for commissions. The commisions are paid throughsystem-generated purchase invoices. For details, refer to Sales Order / Commission.

▪ A separate session is developed to print draft invoices for rebates. For more information,refer to the Print Draft Invoices for Rebates (tdcms2401m000) session.

Item Purchase Data (IPU) module - Differences B50c/ERP61

This topic describes the most important differences between the Item Purchase Data module in ERPBaan5.0c and in ERP LN 6.1.

New functionality

▪ Alternative manufacturer itemsYou can define various manufacturers for a combination of item and supplier. As a result, youcan specify from which manufacturer a purchased item originates. For more information, referto To set up alternative manufacturer items.

▪ Business partner selection based on unit effectivityIn ERP LN 6.1, you can define effectivity units in the new Unit Effectivity (UEF) module ofCommon Data. As a result of this new functionality, the Standard Configuration andExceptions present check boxes are introduced in the Item - Purchase Business Partner(tdipu0110m000) session. The standard configuration determines whether or not an item -purchase business partner combination is valid, but exceptions for a specific effectivity unitor requirement can overrule the standard configuration. For more information, refer to Businesspartner selection based on unit effectivity.

▪ Buyer dashboardA dashboard offers a quick way to access multiple sessions that are used to perform particulartasks of a user. The new Buyer Dashboard (tdipu0103m000) session is developed to providea buyer with a quick overview of item data and easy access to item- and purchase-relateddata.

▪ Nett prices per buy-from business partnerIn ERP LN 6.1, you can view and calculate price and discount information for a combinationof item and buy-from business partner in the new Nett Prices per Buy-from Business Partner(tdipu0110m100) session.


Order Management

Changed functionality

▪ PatternsTo support the new purchase schedule functionality, you must create patterns in the ItemPurchase Data module. Although patterns already existed in ERP Baan5.0c, the patternfunctionality has changed completely.In ERP LN 6.1, you can define patterns in the new Patterns (tdipu0120m000) session. Theyare used to calculate:▪ Schedule issue dates (issue pattern).

▪ Planned delivery moments (delivery pattern). For more information, refer to Planneddelivery moments.

▪ Segment setsSegment sets must also be defined to support the new purchase schedule functionality. Likepatterns, segment sets also existed in ERP Baan5.0c, but are used differently in ERP LN 6.1.To define segment sets, take the following steps in ERP LN 6.1:a. Create segments in the Schedule Segments (tdipu0115m000) session.b. Create a segment set in the Schedule Segment Sets (tdipu0113m000) session.c. Add the segments to the segment set in the Segment Set - Segments (tdipu0114m000)

session.For more information, refer to Segment sets.

For further information on the new purchase schedule funtionality, refer to Purchase schedules (p. 150).

Item Sales Data (ISA) module - Differences B50c/ERP61

This topic describes themost important differences between the Item Sales Datamodule in ERPBaan5.0cand in ERP LN 6.1.

New functionality

▪ Over deliveriesIn ERP LN 6.1, you can define whether over deliveries are allowed for an item and businesspartner combination and define additional conditions for over deliveries in the Item - SalesBusiness Partner (tdisa0110s000) session . For more information, refer to Over deliveries(p. 138) .

▪ RetrobillingIf you completely processed and reported a sales order to history and if price changes aremade to a sales contract or to an item after the renegotiation date, you can use the retrobillingfunctionality in ERP LN 6.1. Retrobilling enables you to re-invoice previously shipped itemsusing a price based on a new contract negotiation. As a result of this new functionality, theRetro-Billing group box is added to the Item - Sales Business Partner (tdisa0110s000) session.For more information, refer to Retrobilling.


Order Management

Removed functionalityAs a result of the new sales schedule functionality, in the Item Sales Data module, you can no longerdefine:

▪ Patterns▪ Segments and segment sets

You can only define patterns and segments in the Item Purchase Data module.

For more information, refer to:

▪ Item Purchase Data (IPU) module - Differences B50c/ERP61 (p. 166)▪ Sales schedules (p. 160)

Pricing Control (PCG) module - Differences B50c/ERP61

This topic describes the differences between the Pricing Control in ERP Baan5.0c and in ERP LN 6.1.

New functionality

▪ Freight rate matrixBecause of the introduction of the new Freight Management package, a user must be able tomaintain and retrieve freight rates in Pricing Control. As a result, the new freight rate matrixis introduced in ERP LN 6.1. For more information, refer to To set up a freight rate matrix.

▪ Global update of purchase prices and sales prices on item levelIn ERP LN 6.1, the following sessions are introduced to globally update base prices in thepurchase item data and the sales item data:

▪ Global Update of Prices in Item Purchase Data (tdpcg0232m000)

▪ Global Update of Prices in Item Sales Data (tdpcg0233m000)

▪ Print prices and discounts by business partnerIn ERP LN 6.1, you can print prices and discounts by matrix. For more information, refer toPrint prices and discounts by business partner (p. 142) .

▪ Promotion matrixIn ERP LN 6.1, promotions are used to offer extra discounts and/or free gifts on sales ordersor sales order lines. Before promotions can be linked to sales orders and sales order lines,you must first set up promotions in the Pricing Control module. For more information, refer toTo set up a promotion matrix.

▪ Recalculate prices and discountsIn ERP LN 6.1, the Recalculate Price and Discount (tdpcg0240s000) session is introduced torecalculate prices and discounts for quotations and quotation lines, and for orders and orderlines.

▪ Sales price includes upgrade price for unit effective itemsIn ERP LN 6.1, in case special components or accessories are used, you can define anadditional (upgrade) price for these components or accessories. For more information, referto Sales price includes upgrade price for unit effective items (p. 158) .


Order Management


▪ Copy existing price books and item base data to price booksWhen you enter an item in the Item Base Data (IBD) of ERP Baan5.0c Common Data, asecond entry is automatically created in the default price book of Pricing Control. In ERP LN6.1, this link is removed.However, in ERP LN 6.1, you can:

▪ Copy a selection of another price book to a new or existing price book. For moreinformation, refer to the Copy Price Book (tdpcg0231m100) session.

▪ Copy a selection of items from IBD to a price book. For more information, refer to theImport Prices from Item Data to Price Book (tdpcg0231m200) session.

▪ Copy supplier quotation (RFQ) to a price bookIn ERP Baan5.0c, you can only copy a supplier quotation to a purchase order or to a contract.Because quotations are usually the input for price book maintenance, in ERP LN 6.1, you canalso copy the quotation to the supplier price book. For more information, refer to the onlinehelp of the Convert Quotations to Contracts/Orders/Price Books (tdpur1202m000) session.

▪ Default purchase price bookThe default purchase price book is replaced by a supplier price book in ERP LN 6.1. With asupplier price book you can avoid the concept of setting up matrix definitions, linking them toprice books, giving them a search priority, and so on. It enables you to quickly retrieve andmaintain prices for a buy-from business partner/ ship-from business partner/ item combination.For more information, refer to To set up a supplier price book.

▪ Flexible break typeIn Infor ERP, you can define prices and discounts with different break types. Because supplier'squotations often have different break types for each item, you must be able to easily shiftbetween minimum and maximum break types. As a result, in ERP LN 6.1, you can define aflexible break field type at price book level in the Price Books (tdpcg0131m000) session andat discount schedule level in the Discount Schedules (tdpcg0121m000) session, rather thanat parameter level in ERP Baan5.0c.

▪ Pricing information retrievalBecause of the new and changed entities in which you can define pricing information, theretrieval of pricing information has changed in ERP LN 6.1. For more information, refer to Anoutline of the pricing information retrieval processes.

Product Catalog (PCT) module - Differences B50c/ERP61

This topic describes the differences between the Product Catalog module in ERP Baan5.0c and in ERPLN 6.1.

Product catalogs in ERP Baan5.0cIn ERP Baan5.0c, product catalogs are defined in the Product Catalog module of the Common Datapackage.

You can order items from a catalog by means of the Intuitive Order Processing (IOP) module of theElectronic Commerce package.


Order Management

Product catalogs in ERP LN 6.1In ERP LN 6.1, the following has changed:

▪ The product catalog data is moved to the Product Catalog module of the Order Managementpackage. With regard to the creation of product catalogs, no major changes are made. Formore information, refer to Product catalogs.

▪ The Intuitive Order Processing (IOP) module no longer exists. This module's functionality istaken over by E-Sales. However, you can still order catalog items in ERP LN 6.1. In the SalesOrder - Lines (tdsls4100m900) session, you can directly add catalog items to the sales order.For more information, refer to To use templates and catalogs in sales orders.

Purchase Statistics (PST) module - Differences B50c/ERP61

This topic describes the most important differences between the Purchase Statistics (PST) module inERP Baan5.0c and the Satistics (STA) module in ERP LN 6.1.

Statistics in ERP Baan5.0cIn ERP Baan5.0c, statistics for purchase are stored in the Purchase Statistics (PST) module andstatistics for sales in the Sales Statistics (SST) module.

Statistics in ERP LN 6.1In ERP LN 6.1, purchase and sales statistics are stored centrally in the new Statistics (STA) module.The Purchase Statistics (PST) and Sales Statistics (SST) module are removed in ERP LN 6.1.

With the exception of statistical information for schedules, which is new in ERP LN 6.1, the Satistics(STA) module contains the same functionality as the modules in ERP Baan5.0c.

For more information, refer to Statistics.

Purchase Control (PUR) module - Differences B50c/ERP61

This topic describes the most important differences between the Purchase Control module in ERPBaan5.0c and in ERP LN 6.1.

New functionality

▪ ComminglingCommingling is introduced in ERP LN 6.1. Commingling is the grouping of a number ofpurchase orders that originate from different sources into a single purchase order. Comminglingreduces the number of purchase orders and enables you to obtain the best available pricesand discounts. For more information, refer to Purchase orders for commingling and Tocommingle purchase orders.

▪ Effectivity unitsIn ERP LN 6.1, you can define effectivity units in the new Unit Effectivity (UEF) module ofCommon Data, after which you can enter these units in purchase requisitions, requests forquotations, purchase orders, and purchase contracts.


Order Management

Effectivity units are used as follows:

▪ For pegging purposes. For more information, refer to Overview of unit effectivity.

▪ To control exceptions for an end item according to the series approach. For moreinformation, refer to Unit effectivity procedure 1 – series approach.

▪ To control exceptions for an end item according to the sales order approach. For moreinformation, refer to Unit effectivity procedure 2: Sales approach.

▪ Equate balance of receipts with inventory levelIn ERP LN 6.1, you can decrease the value of the cumulative receipts regularly to ensure thatrealistic average purchase prices are calculated for items. For more information, refer to Equatebalance of receipts with inventory level (p. 131) .

▪ Link with Freight ManagementIn ERP LN 6.1, you can plan and/or subcontract the transportation of (purchased) goods withthe new Freight Management package. For more information, refer to Link between PurchaseControl and Freight Management (p. 135) .

▪ Link with Object Data ManagementERP Object Data Management supports the functionality of connecting documents in anyformat to Infor ERP objects. An object is, for example, a quotation, purchase contract, purchaseorder, and so on. The general rule in ERP LN 6.1 is that you must click the Show attachmentsbutton to link a document of any format, or to view the linked document(s). You can accessthe document that is attached to the object by means of a document link.

▪ Purchase order approvalIn ERP LN 6.1, you must approve purchase orders. For more information, refer to Purchaseorder approval (p. 144) .

▪ Purchase order statusIn ERP LN 6.1, a status is added to the purchase order header and objects that are linked toa purchase order line are now visible in the Purchase Order Lines Monitor (tdpur4501m500)session. For more information, refer to Purchase order status (p. 148) .

▪ Purchase schedulesIn ERP LN 6.1, the purchase schedule procedure is introduced. For more information, referto Purchase schedules (p. 150) .

▪ Synchronize header - linesIn ERP LN 6.1, if you make changes to a header, the linked lines can be synchronized withthe header. For more information, refer to Synchronize header - lines (p. 163) .


▪ Order unitIn ERP Baan5.0c Order Management, all quantities on an order, schedule, contract, orquotation, are stored in the order unit. In Warehouse Management all quantities are stored inthe inventory unit. To avoid rounding problems, a number of unit changes are made in ERPLN 6.1. For more information, refer to Order units (p. 140) .

▪ Purchase back ordersIn ERP LN 6.1, the back order procedure has changed. For more information, refer to Purchaseback orders (p. 142) .


Order Management

▪ Purchase contractsBecause of the new purchase schedule functionality, the purchase contract functionality isextended in ERP LN 6.1. You can no longer link purchase contracts only to purchase orders,but also to purchase schedules.The following contract sessions are new in ERP LN 6.1:

▪ Purchase Contract Line Logistic Data (tdpur3102m000)

▪ Purchase Contract Price Revisions (tdpur3103m000)▪ Delivery Contract (tdpur3104m000)For more information, refer to Purchase contracts.

▪ Purchase order entryIn ERP LN 6.1, the procedure for entering purchase orders and purchase order lines haschanged. For more information, refer to Order entry (p. 139) .

▪ Purchase order line typesIn ERP LN 6.1, order line types have changed and are extended. For more information, referto Purchase order line types (p. 145) .

▪ Purchase order originIn ERP LN 6.1, the origins from which purchase orders are generated, have changed and areextended. For more information, refer to Purchase order origin (p. 146) .

▪ Purchase order type activitiesIn ERP LN 6.1, the processing of purchase orders can be automated. For each activity thatis linked to an order type, you can indicate its execution mode. As a result, for each order typeyou can define the activities that you want to automate and the activities that need yourinterference. For more information, refer to Flexible purchase order processing.

▪ Purchase orders for non-direct deliveriesThe generation of purchase orders for non-direct deliveries, a functionality that is calledcross-docking in ERP LN 6.1, has changed. For more information, refer to Purchase ordersfor non-direct deliveries (p. 143) .

▪ Purchase requisition enhancementsIn ERP LN 6.1, the following enhancements are introduced for purchase requisitions:▪ A hierarchy in the approval structure.▪ A revision number for tracking changes.For more information, refer to Purchase requisition enhancements (p. 150) .

▪ Receipt informationIn ERP LN 6.1, the storage of receipt information has changed. For more information, referto Purchase order receipt information (p. 147) .

▪ ReconciliationThe redesigned reconciliation functionality in Infor ERP Financials also affects a number ofsettings and processes in Purchase Control. For more information, refer to Reconciliation(Purchase Control) (p. 151) .

▪ Self billingIn ERP LN 6.1, the self billing functionality is extended. This functionality can apply not onlyafter approval of the goods received, but also after receipt of the goods. For more information,refer to Self billing (p. 161) .


Order Management

▪ TaxIn ERP LN 6.1, the tax model has changed completely. As a result, tax fields have changedand are extended in Purchase Control. For more information, refer to Tax (p. 163) .

Sales Control (SLS) module - Differences B50c/ERP61

This topic describes the most important differences between the Sales Control module in ERP Baan5.0cand in ERP LN 6.1.

New functionality

▪ Automatic stock shortage optionIf the inventory to fill a sales order line is insufficient, you can define how ERP LN 6.1 handlesthe inventory shortage with the new Use Automatic Stock Shortage Option check box inthe User Profiles (tdsls0139m000) session. For more information, refer to the Use AutomaticStock Shortage Option check box.

▪ Business partner searchIn the parameters of ERP LN 6.1, you can define the selection criteria that are used to searchfor business partners. For more information, refer to Business partner search (p. 124)

▪ Customer approvalIn ERP LN 6.1, you can indicate whether customer approval must be implemented. Customerapproval refers to the delivery of goods: the sold-to business partner must approve the goodsthat are delivered on a sales order before the goods can be invoiced. The ownership of thegoods does not change from supplier to sold-to business partner until the goods are approvedby the sold-to business partner. For more information, refer to Customer approval.

▪ Delivery notesIn ERP LN 6.1 Warehouse Management, the delivery notes functionality is introduced, whichalso affects Sales Control. For more information, refer to Delivery notes (p. 128) .

▪ Draft invoicesIn ERP LN 6.1, a new session is developed in which you can print draft invoices for salesorders, sales schedules, and installment orders. For more information, refer to the Print SalesDraft Invoices (tdsls4447m000) session.

▪ Effectivity unitsIn ERP LN 6.1, you can define effectivity units in the new Unit Effectivity (UEF) module ofCommon Data, after which you can enter these units in sales quotations, sales orders, andsales contracts. For more information, refer to Effectivity units (p. 131) .

▪ Link with Data ManagementObject Data Management supports the functionality of connecting documents in any formatto Infor ERP objects. An object is, for example, a sales quotation, sales contract, sales order,and so on. The general rule in ERP LN 6.1 is that you must click the Show attachmentsbutton to link a document of any format, or to view the linked document(s). You can accessthe document that is attached to the object by means of a document link.


Order Management

▪ Link with Freight ManagementIn ERP LN 6.1, you can plan and/or subcontract the transportation of (sold) goods with thenew Freight Management package. For more information, refer to Link between Sales Controland Freight Management (p. 136) .

▪ Over deliveriesIn ERP LN 6.1, you can define whether over deliveries are allowed for an item and businesspartner combination and define additional conditions for over deliveries. For more information,refer to Over deliveries (p. 138) .

▪ PromotionsIn ERP LN 6.1, promotions are used to offer extra discounts and/or free gifts on sales ordersor sales order lines. Before promotions can be linked to sales orders and sales order lines,you must first set up promotions in the Pricing Control module. For more information, refer toTo set up a promotion matrix.

▪ RetrobillingIf you completely processed and reported a sales order to history and if price changes aremade to a sales contract or to an item after the renegotiation date, in ERP LN 6.1, you canuse the retrobilling functionality. Retrobilling enables you to re-invoice previously shippeditems using a price based on a new contract negotiation. For more information, refer toRetrobilling.

▪ Rush ordersEach company deals with rush requests from customers. To meet these requests, rush orderscan be entered in ERP LN 6.1. For more information, refer to Rush orders.

▪ Sales order approvalIn ERP LN 6.1, you must approve sales orders. For more information, refer to Sales orderapproval (p. 154) .

▪ Sales order entry based on templates and catalogsERP LN 6.1 enables you to:

▪ Define and use catalogs for the shopping list type of order entry. For details, refer toProduct Catalog (PCT) module - Differences B50c/ERP61 (p. 169) .

▪ Define and use order templates for recurring sales orders.For details, refer to:▪ Sales order templates

▪ To use templates and catalogs in sales orders

▪ Sales order statusIn ERP LN 6.1, a status is added to the sales order header and objects that are linked to asales order line are now visible in the Sales Order Lines Monitor (tdsls4510m000) session.For more information, refer to Sales order status (p. 157) .

▪ Sales schedulesIn ERP LN 6.1, the sales schedule procedure is introduced. For more information, refer toSales schedules (p. 160) .

▪ Standard sales conditionsIn ERP LN 6.1, you can link standard terms of delivery and standard terms of payment to asales order type in the Sales Order Types (tdsls0194s000) session. These standard termsare defaulted to the sales order if the specific sales order type is used.


Order Management

▪ Synchronize header - linesIn ERP LN 6.1, if you make changes to a header, the linked lines can be synchronized withthe header. For more information, refer to Synchronize header - lines (p. 163) .


▪ Alternative itemsIn ERP LN 6.1, the procedure for selling alternative items when the standard item cannot bedelivered is extended. For more information, refer to Alternative items (p. 123) .

▪ ATP/CTP in Sales ControlIn ERP LN 6.1, the ATP/CTP functionality has changed and is extended. For more information,refer to ATP/CTP in Sales Control (p. 123)

▪ Buy items from list groupsIn ERP LN 6.1, the procedure for buying list items from list groups is extended. For moreinformation, refer to List groups (p. 137)

▪ Cancel sales order/ sales order line/ sales order line detailIn ERP LN 6.1, the procedure for canceling sales orders and lines has changed. For moreinformation, refer to Cancel sales orders (p. 125)

▪ Change sales data after release to Central InvoicingAfter a sales order or installment order is released to Central Invoicing, and the invoice statusis Confirmed orOn Hold, you can still update the sales invoice data in ERP LN 6.1. For moreinformation, refer to To change sales data after release to Central Invoicing.

▪ Configure generic itemsIn ERP LN 6.1, the procedure for configuring items has changed. For more information, referto Configured items in Sales Control (p. 128) .

▪ Credit checkingIn ERP LN 6.1, the credit checking functionality is extended with an additional phase in theorder process during which the credit limit must be checked. For more information, refer toCredit ratings.

▪ Delivery and invoice informationIn ERP LN 6.1, the storage of actual delivery and invoice information has changed. For moreinformation, refer to Sales order delivery and invoice information (p. 155)

▪ Direct and non-direct delivery settingsIn ERP LN 6.1, the settings for direct deliveries and non-direct deliveries have changed. Formore information, refer to Delivery types (p. 129)

▪ InstallmentsIn ERP LN 6.1, invoicing by installments has changed. For more information, refer toInstallments.

▪ Lot and serial information on the sales orderIn ERP LN 6.1, you cannot only define conditions for lot items, but also for serialized items.For more information, refer to Lot and serial information on the sales order (p. 138) .

▪ Order acknowledgementsIn ERP LN 6.1, the printing of sales order acknowledgements is refined. For more information,refer to Sales order acknowledgements (p. 153) .


Order Management

▪ Order unitIn ERP Baan5.0c Order Management, all quantities on an order, contract, or quotation, arestored in the order unit. In Warehouse Management all quantities are stored in the inventoryunit. To avoid rounding problems, a number of unit changes are made in ERP LN 6.1. Formore information, refer to Order units (p. 140) .

▪ Purchase orders for non-direct deliveriesThe generation of purchase orders for non-direct deliveries, a functionality that is calledcross-docking in ERP LN 6.1, has changed. For more information, refer to Purchase ordersfor non-direct deliveries (p. 143) .

▪ ReconciliationThe redesigned reconciliation functionality in Infor ERP Financials also affects a number ofsettings and processes in Sales Control. For more information, refer to Reconciliation (SalesControl) (p. 152) .

▪ Return ordersIn ERP LN 6.1, the return order functionality is extended. For more information, refer to Salesreturn orders (p. 159) .

▪ Sales order line typesIn ERP LN 6.1, order line types have changed and are extended. For more information, referto Sales order line types (p. 156) .

▪ Sales order type activitiesIn ERP LN 6.1, the processing of sales orders can be automated. For each activity that islinked to an order type, you can indicate its execution mode. As a result, for each order typeyou can define the activities that you want to automate and the activities that need yourinterference. For more information, refer to Flexible sales order processing.

▪ Sales contractsBecause of the new sales schedule functionality, the sales contract functionality is extendedin ERP LN 6.1. For more information, refer to Sales contracts (p. 154) .

▪ Sales order entryIn ERP LN 6.1, the procedure for entering sales orders and sales order (delivery) lines haschanged. For more information, refer to Order entry (p. 139) .

▪ Shipping constraintsIn ERP LN 6.1, the naming of the shipping constraints has changed. For more information,refer to Shipping constraints (p. 161) .

▪ TaxIn ERP LN 6.1, the tax model has changed completely. As a result, tax fields have changedand are extended in Sales Control. For more information, refer to Tax (p. 163) .

Sales Statistics (SST) module - Differences B50c/ERP61

This topic describes the most important differences between the Sales Statistics (SST)module in ERPBaan5.0c and the Satistics (STA) module in ERP LN 6.1.


Order Management

Statistics in ERP Baan5.0cIn ERP Baan5.0c, statistics for purchase are stored in the Purchase Statistics (PST) module andstatistics for sales in the Sales Statistics (SST) module.

Statistics in ERP LN 6.1In ERP LN 6.1, purchase and sales statistics are stored centrally in the new Statistics (STA) module.The Purchase Statistics (PST) and Sales Statistics (SST) module are removed in ERP LN 6.1.

With the exception of statistical information for schedules, which is new in ERP LN 6.1, the Satistics(STA) module contains the same functionality as the modules in ERP Baan5.0c.

For more information, refer to Statistics.


Order Management


Order Management


Billing request composing criteria


Invoices for business partners with different tax numbers must not be collected on one invoice.

Invoices for VAT book transactions and other transactions cannot be composed on an invoice. Fordetails, refer to To use the VAT book.

New in Infor ERP LN 6.1In ERP LN 6.1, the following details were added to the fixed composing criteria:

▪ The business partner's tax countryIn the Invoicing Methods (tcmcs0155s000) session, you must clear the Collect Sold-toBusiness Partners check box.baan cannot create one invoice for business partners with different tax numbers. If the possibilityexists that multiple sold-to business parnters with different tax numbers are linked to the orders,you must clear this check box because you cannot use the business partner's tax number asa composing criterion.

▪ VAT book transaction typeInvoices for VAT book transactions and other transactions cannot be composed on an invoice.For details, refer to To use the VAT book.

Change composed invoices


ERP Baan5.0cIn ERP Baan5.0c, once you had confirmed the order data in Central Invoicing, the invoice amountscould not be changed.


6Chapter 6Central Invoicing

ERP LN 6.1In ERP LN 6.1, if changes to the invoice amounts are required, you can undo the composition of acomposed invoice in Central Invoicing.

To change a composed invoice, in the Compose/Print/Post Invoices (cisli2200m000), select theDecompose check box. ERP LN changes the order line status to On Hold. In the related OperationsManagement package, you can change the invoice-related details of the order lines, such as the price,and the discount percentage or discount amount.

You cannot change other data such as the invoice-to business partner or the terms of payment. If yousave the data, ERP LN automatically transfers the new data to Central Invoicing and sets the order linestatus to Confirmed.

For details, refer to To correct the invoices.

In connection with the new functionality, the following changes were made:

▪ The invoice numbersBecause composing of the invoices can be reversed, the actual invoice numbers cannot beassigned when you compose the invoices. The actual invoice number is assigned when youprint the original invoice. Until that moment, the composed invoices are identified by a generatedinvoice sequence number. In the SLI Parameters (cisli1500m000) session, you can view thehighest sequence number used.

▪ The invoice statusThe invoice status handling was slightly changed. For details, refer to Invoice status.

Note

You cannot change internal invoices once they are released to Central Invoicing.

Print draft invoices in logistic packages


ERP Baan5.0cIn ERP Baan5.0c, you could print a draft invoice in Central Invoicing, which you could only use to checkwhether the invoice was printed correctly. If corrections were required, you could cancel the order linesin Central Invoicing. After correcting the order data in the logistic package, you had to release thecorrected orders again to Central Invoicing.

ERP LN 6.1In ERP LN 6.1, prior to releasing the order data to Central Invoicing you can print a draft invoice in thelogistic packages, for example, in Order Management. You can use the draft invoice to check the invoiceand to make corrections to the invoiced amounts. The default template and billing request additions thatyou define in the SLI Parameters (cisli1500m000) session are used for the draft invoice.

For details about printing draft invoices, refer to the documentation of the logistic packages.


Central Invoicing

Print references to rebate agreements on sales invoices


In some countries, if you have a rebate agreement or a bonus agreement with your business partner,you must print a reference to the agreement on the sales invoices.

ERP Baan5.0cTo answer this legal requirement, in ERP Baan5.0c, you must create an additional text and add it to thebilling request addition in the Billing Request Addition (cisli1120s000) session.

ERP LN 6.1In ERP LN 6.1, you can add a reference text to a billing request addition. ERP LN prints the referencetext at the bottom of the sales invoice.

Usually, the text of the reference to a rebate agreement can be generic, for example, "Deductions applybased on rebate and bonus agreements."

Note

You must manually check whether a rebate agreement or bonus agreement with the business partnerexists.

You can only print references to rebate agreements on sales invoices, not on service invoices.

Print texts and details on invoices


ERP Baan5.0cIn ERP Baan5.0c, the possibilities to print extra information on invoices was limited to header and footertext, additional order texts, and detail order line texts.

ERP LN 6.1In ERP LN 6.1, in addition you can print the following texts and information on invoices:

▪ Lot and serial textIf serialized items or lot items occur on the invoice, you can print the serial numbers and/orthe lot numbers on the invoice. For details, refer to To print reference texts on invoices.

▪ Text related to a tax codeIf special tax rates apply, in some cases a reference to the applicable tax law chapter mustbe printed on the invoice. For details, refer to To print tax articles on invoices.

▪ The business partner's bank address and account numberIn some countries, the bank address and the business partner's bank account number mustbe printed on the invoice. For details, refer to To print business partner bank details on invoices


Central Invoicing

▪ Delivery notesIf the goods were accompanied by a delivery note, the delivery note number must be printedon the invoice.

▪ A reference textA text printed at the bottom of the sales invoice. For example, you can use this text forreferences to rebate agreements that apply to the invoice. For details, refer to To print referencetexts on invoices.

Rebates


ERP Baan5.0cRebates are created as open entries with negative amounts in the Accounts Receivable module. However,in ERP Baan5.0c, open entries are created through the scripts of the corresponding Order Managementsessions.

ERP LN 6.1In ERP LN 6.1, the open entries are created by the scripts of the Accounts Receivable module. OrderManagement passes on invoice requests for rebates to Central Invoicing.

After processing in Central Invoicing, the rebates are sent to the customers in the form of sales invoicesor credit notes, and posted to Financials as open entries in the Accounts Receivable module. In thisway, Order Management uses the standard invoicing functionality offered through Central Invoicing,and no longer creates open entries directly in Financials.

Modules

Sales Invoicing (SLI) module - Differences ERP61/B50c

This topic summarizes the differences between the Sales Invoicing module in ERP Baan5.0c and inERP LN 6.1 and lists the differences that are not already discussed in other topics.


▪ Billing request composing criteriaInvoices for business partners with different tax numbers must not be collected on one invoice.Invoices for VAT book transactions and other transactions cannot be composed on an invoice.The VAT book is a legal report of all value added tax (VAT) transactions of a company, in datesequence. The transactions can be grouped by tax articles, which typically group transactionsthat have the same tax percentage.For details, refer to Billing request composing criteria (p. 179) .


Central Invoicing

▪ Change composed invoicesIn ERP LN 6.1, if changes to the invoice amounts are required, you can undo the compositionof a composed invoice in Central Invoicing.For details, refer to Change composed invoices (p. 179) .

▪ Freight Management integrationThe Freight Management integration with Financials results in a number of new integrationtransactions as well as a few new sessions in Central Invoicing to handle freight invoices.For details, refer to Freight Invoicing.

▪ Grand total roundingIn some countries, the total amounts on legal documents that you send to your customersmust be rounded in a specific way. In ERP LN 6.1, grand total rounding supports thisrequirement.Grand total rounding is to round the grand total amounts on legal documents that you sendto your customers, such as sales quotations, service contracts, and sales invoices. For example,if the currency rounding factor is 0.01 and grand totals must be rounded on 0.05, you can usegrand total rounding and define a grand total rounding factor of 0.05.For details, refer to Grand total rounding (p. 26) .

▪ Bank reference numbersThe use of bank reference numbers is a common banking practice for domestic transactionsin Norway and Finland. The bank reference number is a unique number that is used to identifythe invoice for which the payment is made. The bank reference number is communicated tothe customer on the invoice document and is always referred on the payment document. Usethe new Bank Reference Positions by Country (cisli1130m000) session, to define how thebank reference number is composed on the sales invoices. For details, refer to Bank referencenumbers.

▪ Print references to rebate or bonus agreements on sales invoicesIn some countries, if you have a rebate agreement or a bonus agreement with your businesspartner, you must print a reference to the agreement on the sales invoices.For details, refer to Print references to rebate agreements on sales invoices (p. 181) .

▪ Print texts on invoicesIn ERP Baan5.0c, the possibilities to print extra information on invoices was limited to headerand footer text, additional order texts, and detail order line texts.In ERP LN 6.1, in addition you can print the following texts and information on invoices:▪ Lot and serial text▪ Text related to a tax code

▪ The business partner's bank address and account number▪ Delivery notes▪ A reference textFor details, refer to Print texts and details on invoices (p. 181) .


Central Invoicing

Other differences

▪ SLI Parameters (cisli1500m000)In ERP LN 6.1, the parameters are date-effective. The session was extended with fields andcheck boxes for the new functionality in ERP LN 6.1.You can enter the transaction types and series used to generate document numbers for thefollowing new types of invoices:▪ Rebates▪ Purchase Orders▪ Service Calls▪ Maintenance Orders▪ Intercompany Orders▪ Freight Orders▪ Credit Notes (Finance)▪ Debit Notes (Finance).

▪ Filter to show only non-confirmed linesIn ERP Baan5.0c, in the Global Confirmation of Order data (cisli2219m000) session, you mustselect a range of sales invoices or warehouse order invoices that are not yet confirmed.However, the browse session displays all the invoicing data, whether or not they have beenconfirmed.In ERP LN 6.1, you can only select invoices for confirmation that have not yet been confirmed.

▪ Global Confirmation of Order data (cisli2219m000)If you browse to the Sales and Warehouse Invoice Data (cisli2540m000) session, only theinvoices with the On Hold status are displayed for selection.

▪ Reprint invoices by projectIn ERP Baan5.0c, in the Reprint Invoices (cisli2405m000) session, you cannot print or reprintthe invoices by project.In ERP LN 6.1, you can print the invoices for a specific range of projects. To print the invoicesfor a range of projects, in the Reprint Invoices (cisli2405m000) session, select Select byProject. You can enter the range of projects.

▪ VAT amounts on Invoice - Source Relation reportIn ERP Baan5.0c, all the amounts on the Invoice - Source Relation (cisli240611000) reportinclude the VAT amount. However, none of the other Central Invoicing sessions and reportsinclude VAT amounts. Moreover, there is no indication that the amounts include the VATamounts. Therefore, it is confusing to use this report, for example, for auditing purposes.In ERP LN 6.1, the Invoice - Source Relation (cisli240611000) report includes the followingamounts:▪ The amounts exclusive the VAT amount.▪ The VAT amount.▪ The total amount including the VAT amount.


Central Invoicing

▪ Exception report for confirming invoicesIn ERP Baan5.0c, if you confirm invoices in the Global Confirmation of Order data(cisli2219m000) session, ERP LN does not report the reason why some invoices were notconfirmed. Such a report is only generated if you confirm invoices in the Sales andWarehouseInvoice Data - Lines (cisli2545m000) session.In ERP LN 6.1, ERP LN generates an exception report for the invoices that could not beconfirmed.

▪ Enhanced report Print Invoice Lines By Status (cisli241012000)The following enhancements were made to the Print Invoice Lines By Status (cisli241012000)report:

▪ Add selection criteriaIn ERP Baan5.0c, the Print Invoice Lines By Status (cisli241012000) report prints all thebusiness partners in the selected range. It is not possible to report on the invoices thatare handled by a specific sales representative or sales office.In ERP LN 6.1, the following additional selection criteria are available in the Print InvoiceLines by Status (cisli2410m000) session:▪ Sold-to Business Partner▪ Department▪ Sales Representative

▪ Add invoice number and sequence numberIn ERP Baan5.0c, the Print Invoice Lines By Status (cisli241012000) report does not showthe invoice number, or the sequence numbers of the shipment lines.In ERP LN 6.1, the following information is also printed on the Print Invoice Lines By Status(cisli241012000) report:▪ The invoice number▪ The sequence number of the invoice lineIf items are back ordered and multiple shipment lines are invoiced separately, the reportshows a number of lines for one sales order line. The invoice line sequence numberindicates to which invoice line the invoiced shipment line belongs.


Central Invoicing


Central Invoicing


Add and explode phantoms in a production order

This topic describes how to use a phantom as a material in a production order.

New in Infor ERP LN 6.1In ERP LN 6.1, you can manually add phantoms to an existing production order, in the same way asyou can add extra material to an existing production order. If no inventory of the phantom item is available,the phantom’s material is exploded and included in the production order’s estimated material.

If you want add and explode a phantom for a production order, click Add/Explode Phantom in thespecific/TextRef> menu of the Material to Issue for Production Orders (ticst1501m000) session or theEstimated Materials (ticst0101m000) session.

Alternative material and use-up of old revisions

Especially in electronics business, using alternative material on the shop floor is common practise. Dueto the frequent replacement of new versions of components on one hand, and a variety of similar,exchangeable components on the other hand, an estimated material on the shop floor may be replacedby another component. Using alternative material results in reduced stock levels.

New in Infor ERP LN 6.1In Infor ERP LN 6.1 FP2, the following functionality is implemented:

▪ Use-upIf a component must be phased out, the planning engine consumes the old versions in stockbut old versions are not ordered anymore.

▪ Alternative materialIf a specific material must be issued but no stock can be found, an exchangeable componentis selected. You can use alternative material during planning, allocation in SFC, and outbound.


7Chapter 7Manufacturing

Cost components

This topic explains the changed cost component concept in ERP LN 6.1.

Cost components in ERP Baan5.0cIn ERP Baan5.0c, you can collect costs on three, aggregated cost components.

Aggrated cost components and detailed cost components in ERP LN 6.1In ERP LN 6.1, you can choose whether to collect costs on aggregated cost components defined in theItems - Costing (ticpr0107m000) session, or to break down costs into detailed cost components. To usedetailed cost components, you must enter a chart code in the Cost Component Chart field in the Items- Costing (ticpr0107m000) session. Subsequently, you must define in the Chart Details (ticpr0110m000)session the detailed cost components that you want to use to break up the costs. For more information,refer to Cost components.

If you actualize an item's cost price by using the Calculate Cost and Valuation Prices (ticpr2210m000)session or the Actualize Standard Cost and Valuation Prices (ticpr2220m000) session, an effective costcomponent structure is generated. You can view the structure in the Effective Cost Component Structure(ticpr3506m000) session.

Note

In Assembly Control, you must actualize the costing data in the Actualize Assembly Line Costing Data(ticpr0215m000) session. You can view the effective cost component structure in the Effective CostComponent Structure by Assembly Line and Item (ticpr3161m000) session.

Costing work centers

This topic describes the costing work center concept

Changing work centers during production planning in ERP Baan5.0cIn some situations, it can be necessary to use an unallocated work center or an unallocated machinein order to meet a due date. In ERP Baan5.0c, it is difficult to change work centers during productionplanning when the estimated costs are already frozen. It is mostly time consuming because of recalculationof the estimated costs.

Costing work centers in ERP LN 6.1In ERP LN 6.1, a flexible work centers concept is introduced that involves the decoupling of planningwork centers and costing work centers. Costing work centers serve as an extra level on top of theplanning work centers, which makes costing and planning more independent.

The planning work centers (logistical work centers) are used for production planning. The costing workcenters are used for production order costing purposes such as calculation of the end item unit costs,WIP transfers, production results, and posting financial transactions. A production planning work center


Manufacturing

can be changed when the costs are already frozen as long as the new work center has the sameenterprise unit as the costing work center for that operation.

This solution offers the following advantages:

▪ More flexibility to update the planning manually.

▪ Better possibilities to ad hoc subcontract an operation.

▪ The possibility of creating one costing work center for every enterprise unit.

For more information, refer to Costing work centers.

Drawing sizes and drawing locations in EDM

This topic is about drawing sizes and locations in EDM.

Drawing sizes and locations in ERP Baan5.0cDrawing sizes are the paper sizes of engineering drawings. Drawing locations are places where theengineering drawings are stored. In ERP Baan5.0c, drawing sizes en drawing locations are part of EDM.

Drawing sizes and locations in ERP LN 6.1In ERP LN 6.1, drawing sizes and drawing locations are not stored in EDM anymore, but in the DocumentManagement (DOC) module in Infor ERP Object Data Management.

ECO approval procedure

This topic describes the difference between the ECO approval procedure in ERP Baan5.0c and theapproval procedure in ERP LN 6.1.

ECO approval procedure in ERP Baan5.0cIn ERP Baan5.0c, the approval of ECO changes is part of the change procedure in EDM.

EDM approval procedure in ERP LN 6.1In ERP LN 6.1, the approval procedure is not part of EDM, but is managed by change orders in the DataManagement package, in the Change Management (CHM) module.

Engineering Change Orders (ECOs)

This topic is about Engineering Change Orders (ECOs) and Mass BOM Changes (MBCs). ECO is aERP Baan5.0c term, which does not exist in ERP LN 6.1. In ERP LN 6.1, the concept of MBC is used.

Engineering Change Orders (ECOs) in ERP Baan5.0cIn ERP Baan5.0c, the steps to approve changes (by change orders) for engineering items or BOMs,and their related standard or customized items/BOMs, is part of an ECO procedure.


Manufacturing

Mass BOM Changes (MBCs) in ERP LN 6.1In ERP LN 6.1, the concept of ECOs is replaced by the concept of Mass BOM Changes (MBCs). Thenew functionality of MBCs is more systematic than that of ECOs. The MBC contains all informationabout changes that must be performed and about the E-items that will be affected by these changes.The E-items can be defined for each action that is defined in the MBC Action (tiedm3120m000) session.This is an improvement compared to ERP Baan5.0c, in which the affected E-items could only be definedfor the ECO, and not for each action that was defined in the ECO lines.

For more information refer to To change EBOMs - Automatic procedure.

Engineering item groups

This topic is about engineering item groups.

Engineering item groups in ERP Baan5.0cIn ERP Baan5.0c, engineering item groups are sets of engineering items grouped on the basis of commonfeatures.

Engineering item groups in ERP LN 6.1Engineering item groups do not exist in ERP LN 6.1.

Generic Browser Framework (GBF)

You can use the Generic Browser Framework (GBF) in Manufacturing to display graphical representationsBOMs, E-BOMs, engineering item revisions, items, pegging relations, or family trees (in the ProductClassification (GRT) module. You can also maintain data in the GBF. If you use a GBF, you avoidtraversing through multiple sessions to carry out a process.


In ERP LN 6.1, you can start a GBF from the following sessions:

▪ To display an BOM:Bill of Material (tibom1110m000)The GBF displays a tree structure that consists of (E-)BOM lines, including the quantities,units, and the effective and expiry dates of the (E-)BOM lines. Note that you can view referencedesignators in the GBF (if applicable). Double-click the BOM line's component for which youdefined reference designators. For every reference designator, a line is displayed in the tree.

▪ To display an E-BOM:Engineering BOM (tiedm1110m000)The comments made on the BOM apply also to the engineering BOM.

▪ To display engineering item revisions:Engineering Item (tiedm0110m000)


Manufacturing

▪ To display pegging relations▪ Production Planning (tisfc0110m000)▪ Production Order (tisfc0101m100)▪ Production Orders (tisfc0501m000)

▪ To display a family tree of items:Structure Levels (tigrt0199m000)

Generic engineering data: BOM and routing

This topic describes the differences in the generic BOM and generic routing in ERP LN 6.1 comparedto ERP Baan5.0c.

Generic BOM and routing in ERP Baan5.0cThe generic BOM and the generic routing are part of the Product Configuration (PCF) module in ERPBaan5.0c. The functionality of the generic BOM and routing largely resembles the BOM and routing ofstandard or customizid items.

Generic BOM and routing in ERP LN 6.1In ERP LN 6.1, the generic BOM and the generic routing are still part of Product Configuration (PCF).However, compared to ERP Baan5.0c, there are some additions in the generic BOM and generic routingto keep them in line with the BOM and routing for standard and customized items in ERP LN 6.1.

Furthermore, in ERP LN 6.1, the generic BOM and the generic routing can be viewed and maintainedin the Generic Item - Structure (tipcf3100m100) session, which is a so-called header-lines session. Fromthis session, you can also start the Generic BOMs (tipcf3110m000) details session, the Generic Routing(tipcf3120m000) details session, and some other sessions related to PCF.

Generic BOM differencesDue to changes in the BOM for customized and standard items, the following fields are added in thegeneric BOM in ERP LN 6.1:

▪ Lot SelectionYou can use the Lot Selection field in the Bill of Material (tibom1110m000) details sessionto determine whether you want to issue the material on the BOM line from a specific lot, thesame lot, or from any lot.

▪ Use Phantom InventoryIf a phantom item is available in inventory, and the quantity is sufficient, this inventory is usedas a component in the production order. If no phantom inventory is available, or if the quantityis insufficient, the inventory is not used. Infor ERP treats the component as a normal phantomitem, so the phantom is exploded for the total quantity. For more information, refer to Phantoms.

Generic routing differencesDue to changes in the routing for customized and standard items, the following fields are added orchanged in the generic routing in ERP LN 6.1:


Manufacturing

▪ Fields that express lead time elements, for example, queue time, wait time, and move time.These lead time elements are only available on work center level in ERP Baan5.0c. In ERPLN 6.1, these lead time elements are also available on the operation level. . For moreinformation, refer to Lead time elements (p. 193) .

▪ Fields that express scrap and yield.▪ Scrap Quantity▪ Yield Type▪ Yield Percentage

▪ Fields in relation to Kanban and containers:▪ Container▪ Container Method▪ Container Quantity▪ Number of Kanbans▪ Dscr on KanbanFor more information, refer to Pull notes (p. 198) .

Graphical planning board in SFC (Webtop)

In ERP LN 6.1, the Webtop provides a new graphical planning board in SFC.

ERP Baan5.0cIn ERP Baan5.0c, you can use the following sessions to start a planning board with a simple userinterface for shop floor planning:

▪ Production Planning by Planning Board (tisfc1120m000)

▪ Work Center Planning by Planning Board (tisfc1130m000)

▪ Machine Planning by Planning Board (tisfc1140m000)

ERP LN 6.1In ERP LN 6.1, a more advanced graphical planning board (SFC Gantt chart) is implemented in theERP LN, in theWebTop.

You must select the data that you want to display in the graphical planning board in the Select Data forPlanning Board (tisfc1125m000) session. After that, you can start the SFC Gantt Chart (tisfc1126m000).

Some features of the new graphical planning board are:

▪ Possibility to choose between a Gantt view and a schedule view.▪ Sorting options.

▪ Starting SFC planning sessions from the planning board.

▪ Using colors to indicate information such as operation status and lateness.

Note

In the Infor ERPWorktop, the graphical planning board is not implemented. The old situation still applies.


Manufacturing

Hours accounting

This topic is about hours accounting.

Hours accounting in ERP Baan5.0cIn ERP Baan5.0c, hours accounting in Manufacturing is performed in the Hours Accounting (HRA)module.

Hours accounting in ERP LN 6.1In ERP LN 6.1, all hours accounting is performed in the Time Management (TMM) module of People.

Lead time elements

This topic describes the production order lead-time elements in ERP Baan5.0c and ERP LN 6.1. Leadtime elements are important for planning purposes.

Production order lead-time elements in ERP Baan5.0cIn ERP Baan5.0c, you can define setup time and cycle time on the task level, or on a routing operation.

On the work center level, you can define the queue time and the transfer delay, which is the sum ofmove time and wait time. The lead time elements on work center level are the defaults for the productionorder.

Production order lead-time elements in ERP LN 6.1In ERP LN 6.1, several lead time elements can be defined on the routing-operation level:

▪ queue time▪ average setup time▪ cycle time▪ wait time▪ move time

Note that transfer delay does not exist anymore as a lead time element in ERP LN 6.1. Instead, you candefine move time and wait time in ERP LN 6.1.

You can also define queue time, wait time, and move time on the work center level in the Work Centers(tirou0101m000) session. These times then appear as defaults on routing operations that are linked tothe work center. However, you can always change the times on the routing operations. The times of thelead time elements on the operations are the defaults for the production order.

Note that you cannot define queue time and cycle time on the task anymore. Instead, you must definequeue time and cycle time for the task - work center relationship in the Task Relationships(tirou0104m000) session. For more information, refer to Task - work center relationships (p. 201) .


Manufacturing

Lot by unit

This topic is about the use of lot by unit or serialization to track and trace items.

Lot by unit in ERP Baan5.0cLot control is used to record and trace groups of items. In ERP Baan5.0c, you can use Lot by Unit inthe item data to identify a single item as a lot. In this way, you can record and trace the item.

Serialization in ERP LN 6.1In ERP LN 6.1, the concept of serialized items is introduced. Serialization is used in the following BaanERP packages:

▪ In Manufacturing, to identify manufactured items, and the components that are used in themanufactured items.

▪ In Warehouse Management, to track and trace items in inventory, for inbound goodsmovements, and/or outbound goods movements.

▪ In Service, to identify items and components for service and maintenance purposes.

In Manufacturing, you can find the sessions related to serialization in the Manufacturing Control (MFC)module.

For more information, refer to Overview of serialized items.

Lower cost or market value

New regulations resulted in adjustments in ERP LN 6.1 functionality.

New in Infor ERP LN 6.1The International Financial Reporting Standards (IFRS) require in some cases reporting of the inventorymarket value instead of an inventory value determined by the original purchase prices. Themarket valuecan provide you with a better insight into the real value of the inventory. Reporting inventory value basedon market prices instead of (higher) purchase prices is also referred to as lower cost or market value(LCMV). You can apply LCMV in ERP LN 6.1.

In addition to reporting the inventory value based on market prices, you can also choose to revaluatethe inventory value to the market value in ERP LN 6.1.

Machine utilization chart

This topic is about the improved utilization chart in ERP LN 6.1.

Utilization chart in ERP Baan5.0cIn ERP Baan5.0c, only a utilization chart on (critical) work center level is available.


Manufacturing

Machine utilization chart in ERP LN 6.1In ERP LN 6.1, a machine utilization chart is available, which provides a utilization overview for allmachines, depicting all required hours against available capacity.

You can start the machine utilization chart using the Machine Utilization Chart (tisfc1511m000) session.

Micro routing

This topic is about a new concept in ERP LN 6.1, the micro routing.

Micro routing in ERP LN 6.1In ERP LN 6.1, the new concept of micro routing is introduced. A micro routing facilitates work on theshop floor by providing stepwise, extra information related to a routing operation.

Operation overlap

This topic is about overlap of operations.

Operation overlap in ERP Baan5.0cIn ERP Baan5.0c, you can define a quantity to indicate operation overlap.

Transfer batch quantity/percentage in ERP LN 6.1In ERP LN 6.1, you can choose whether you want to indicate the operation overlap with a quantity, orwith a percentage. The Transfer BatchMethod field in the Routing Parameters (tirou0100m000) sessiondetermines whether you must type a quantity or a percentage in the Routing Operations (tirou1102m000)session.

Order pegging in Manufacturing

You can use order pegging in Manufacturing to trace orders that are related to a specific productionorder.

New in Infor ERP LN 6.1In ERP LN 6.1, you can use order pegging in the following sessions:

▪ Production Planning (tisfc0110m000)▪ Production Order (tisfc0101m100)▪ Production Orders (tisfc0501m000)

To start order pegging, select a production order, and choose order pegging from the specific menu.


Manufacturing

You can choose between two types of order pegging:

▪ Pegging - UpstreamClick Pegging - Upstream to start the GBF browser in which you can view the productionorder's supply orders, that is, the preceding production orders and/or purchase orders.

▪ Pegging - DownstreamClick Pegging - Downstream to view the production order's demand orders, that is, thesuccessive production orders and/or sales orders.

You can only start pegging if the following is true:

▪ The production order date is between the scenario's start date and end date.

▪ The production order is part of the actual scenario.

▪ One of the following sessions is run:

▪ The Generate Order Planning (cprrp1210m000) session, while the Update PeggingRelations check box is selected.

▪ The Generate Pegging Relations (cprrp0240m000) session.

Production order groups

This topic is about production order groups.

Production order groups in ERP Baan5.0cIn ERP Baan5.0c, production order groups do not exist.

Production order groups in ERP LN 6.1In ERP LN 6.1, order groups are introduced. In Manufacturing, production order groups are used tocarry out actions on all the production orders in the group at the same time. For more information aboutorder groups in Manufacturing, refer to Order grouping.

Order groups are also used in Enterprise Planning. For more information, refer toOrder grouping (p. 111).

Production warehouse orders

In addition to the Material to Issue for Production Orders (ticst1501m000) session, a new session isadded in ERP LN 6.1 to issue material.

Material issue in ERP Baan5.0cIn ERP Baan5.0c, you must use the Material to Issue for Production Orders (ticst1501m000) sessionto issue, cancel, and/or return material from the warehouse to the shop floor and vice versa.


Manufacturing

Material issue in ERP LN 6.1In ERP LN 6.1, a new session is introduced, the ProductionWarehouse Orders (timfc0101m000) session,in which you can issue, return, or cancel items in a more detailed way. This is especially important incase of serialized items, lot controlled items, or unit effective items.

In the Production Warehouse Orders (timfc0101m000) session, so-called production warehouse ordersreflect every material or end item transaction that has resulted in a warehouse order. The ProductionWarehouse Orders (timfc0101m000) session enables you to:

▪ Make a difference between canceling a quantity that is still in the warehouse, and returning aredundant quantity from the shop floor to the warehouse.

▪ Return a specific lot code or serial number to the warehouse. This is useful if multiple lots orserial numbers are in the warehouse for a specific material or production order.

▪ Specify different planned issue dates or receipt dates for a material or a production order. Forexample, a Subsequent Delivery quantity for a specific material can have a planned datethat differs from the planned date of the To Issue quantity of the material. The planned inventorytransactions reflect the different dates. Consequently, the MRP planning will result in a moreaccurate material planning.

▪ Restart automatic processing, if you use automatic processing of warehouse orders (theDirectProcess Outbound check box is selected), and previous automatic processing was notsuccessful, for example, due to a shortage.

▪ Select a different warehouse procedure when using return orders.

Note

The Material to Issue for Production Orders (ticst1501m000) session is still available for material issue.

Project segment in Engineering Data Management (EDM)

ERP Baan5.0cIn ERP Baan5.0c, you cannot engineer a customized item. You cannot enter a project in the projectsegment of the Engineering Item field of the Engineering Item (tiedm0110m000) session.

ERP LN 6.1In ERP LN 6.1, the project segment for an engineering item is made available so that you can usecustomized engineering items in EDM. You can relate a customized engineering item to customizeditems with the same PCS project.

If you define an engineering BOM (EBOM) for a customized engineering item, the components can onlybe standard items, or items with the same project as the customized engineering item.

Note

▪ Standard engineering items can relate to both standard items and customized items.


Manufacturing

▪ The project that you define in the Engineering Project field in the Engineering Item(tiedm0110m000) session refers to the engineering project that manages and controlsengineering activities.

Pull notes

This topic explains the new labels funtionality in ERP LN 6.1.

Pull notes in ERP Baan5.0cIn ERP Baan5.0c, pull notes are used to cover and initiate the movement of goods towards, on, or fromthe shopfloor.

Labels in ERP LN 6.1In ERP LN 6.1, the pull notes are replaced by the concept of labels. Two types of labels can bedistinguished:

▪ Kanban labelsTrigger the supply of intermediate products between work centers.

▪ Production order labelsIdentify completed production order quantities. The labels are an aid to move the productionorder to the warehouse, and contain information such as the number of the production order,the kind of item in the production order, the warehouse to which the items must be transferred,and so on.

For details, refer to Labels in Manufacturing.

Reference designators

This topic is about reference designators.

Reference designators in ERP Baan5.0cIn ERP Baan5.0c, you can define for a BOM line on which location the BOM line item must be mountedor attached.

The link between materials and reference designators exists only in the BOM module. As a result, if aproduction order is generated, reference designators cannot be viewed andmaintained for the productionorder's estimated materials in SFC. You can only print on order documents the reference designatorinformation that was defined in the BOM .

In ERP Baan5.0c, you cannot use reference designators in Engineering Data Management (EDM)module.


Manufacturing

Reference designators in ERP LN 6.1In ERP LN 6.1, reference designators are defined by item, after which they can be linked to items on aBOM line as well as to items in the EDM module. If production orders are generated, you can view andmaintain the reference designators in the estimated materials.

For more information, refer to Overview of reference designators.

Revenue recognition

New regulations resulted in adjustments in ERP LN 6.1 functionality.

New in Infor ERP LN 6.1International accounting rules, for example, IFRS (International Financial Reporting Standards) requiremore transparancy in business financials. Public companiesmust be able to recognize costs and revenuesnot only at the end of a project but also on different moments during the project. With revenue recognitionin Project Control (PCS), you can determine the interim revenue and interim cost of goods sold (COGS)for an unfinished project, even before shipping any end item.

Rough capacity consumption of work centers in PCS

This topic describes how to prevent double consumption of work center capacity in PCS.

Double consumption of capacity in ERP Baan5.0cIf you use PCS network planning in ERP Baan5.0c, and an network activity involves production, workcenter capacity can be consumed double:

▪ By the rough capacity that is defined for the PCS activities.

▪ By the capacity that is required for SFC production orders related to the activities.

Prevent double consumption of capacity in ERP LN 6.1Double consumption of work center capacity is not always desirable. In ERP LN 6.1, you can use theUse Rough PCS Capacity Reguirement check box in the Work Centers (tirou0101m000) session toprevent double consumption.

Sequence of material issue and backflushing

This topic describes how the sequence of material issue and backflushing has been changed.

Sequence of material issue and backflushing in ERP Baan5.0cIn ERP Baan5.0c, if you are handling more than one production order, material is first issued orbackflushed for the production order with the lowest production order number. The production orderstart date is not taken into account when issueing or backflushing material.


Manufacturing

Sequence of material issue and backflushing in ERP LN 6.1In ERP LN 6.1, backflushing or issuing material for production orders can also be determined by theproduction order start date.

A production order with a high production order number can have a production start date that is earlierthan a production order with a low production order number. In that case you might want to issue orbackflush material for the production order with the earliest start date first. Therefore, you can choosebetween two sequences in which material must be issued or backflushed for production orders:

▪ Based on Start Dates▪ Based on Order Numbers

Use the Issue Sequence field in the Initiate Inventory Issue (tisfc0207m000) session to determine thesequence in which material is issued.

Use the Backflush Sequence field in the Backflush Materials and Hours (tisfc0220m000) session todetermine the sequence in which material is backflushed.

Shared work centers

This topic is about a new concept in ERP LN 6.1, shared work centers.

Work centers in ERP Baan5.0cIn ERP Baan5.0c, you can only plan work for work centers in the current logistic company.

Shared work centers in ERP LN 6.1In ERP LN 6.1, the new concept of shared work centers is introduced. A shared work center is a workcenter on a central location that has a relationship with work centers in different logistic companies. Youcan use this relationship for capacity planning. You can plan work in a specific logistic company that isactually carried out in a different company. The secondary work center and the primary work center areshared work center types.

For more information, refer to Shared work centers.

Task type

This topic is about task types.

Task types in ERP Baan5.0cIn ERP Baan5.0c, you can define the following task types:

▪ Production▪ Indirect task▪ Absence▪ Repair


Manufacturing

Task types in ERP LN 6.1In ERP LN 6.1, task types do not exist in Manufacturing anymore. If a machine is defined for an operation,ERP LN considers the task on the operation as a machine task. As a result, machine hours are takeninto account to calculate operation hours. If no machine is present, the task is a non-machine task, andonly man hours are used to calculate operation hours.

Note

In People, you can still define general tasks that have task type Absence Task or Indirect Task.

Task - work center relationships

This topic describes where to define lead time elements and other data related to a task.

Task relationships in ERP Baan5.0cIn ERP Baan5.0c, you can define data such as setup time, cycle time, man occupation and machineoccupation on the task level.

Task relationships in ERP LN 6.1In ERP LN 6.1, you cannot define lead time elements such as cycle time and cycle time on the tasklevel anymore. You must define the lead time elements either directly on the routing operation, or for atask - work center relationship in the Task Relationships (tirou0104m000) details session. You can alsodefine data such as man occupation and machine occupation in the Task Relationships (tirou0104m000)details session. If you enter a task on an operation for which you defined a task - work center relationship,the defined data appears as defaults on the routing operation.

To define task relationships the following must be true:

▪ TheWork Center Selection Method field or the Machine Selection Method field in theTasks (tirou0103m000) details session is Specific.

▪ The Type of Operation Rates field in the Cost Price Calculation Parameters (ticpr0100m000)session is Task Relationship Rate.

WIP warehouses

The name WIP warehouse in ERP Baan5.0c changed to shop floor warehouse in ERP LN 6.1.

WIP warehouses in ERP Baan5.0cIf you use WIP warehouses in ERP Baan5.0c, the materials are first allocated on the warehouse that isdefined in the estimated materials. When the production order is released, the allocated materials aremoved to the WIP warehouse.

Shop floor warehouses in ERP LN 6.1In ERP LN 6.1, WIP warehouse is renamed to shop floor warehouse.


Manufacturing

If you define a shop floor warehouse on your work center, material for production orders can be allocateddirectly to the shop floor warehouse during production order generation or during production orderrelease, dependent on the Move Allocation to Shop Floor Warehouse field in the Shop Floor ControlParameters (tisfc0100s000) session.

For details, refer to Using shop floor warehouses.

Modules

BOM Control (BOM) module - Differences B50c/ERP61

This topic describes the most important differences between the Bill of Material module in ERP Baan5.0cand in ERP LN 6.1.

Removed functionality

▪ Pull notesIn ERP Baan5.0c, you can define the number of notes on the BOM line. In ERP LN 6.1, thepull notes concept is removed, and replaced by the labels concept. For more information, referto Pull notes (p. 198) .


▪ WIP warehousesWIP warehouse is renamed to shop floor warehouse in ERP LN 6.1. A new parameter relatedto shop floor warehouse is present in the Shop Floor Control Parameters (tisfc0100s000)session. For more information, refer toWIP warehouses (p. 201) .

▪ Reference designatorsIn ERP LN 6.1, the reference designator concept has changed. For more information, referto Reference designators (p. 198) .

New functionality

▪ Unit effectivityYou can link exceptions to BOM lines so that you can model a deviation of the BOM for a uniteffective item. For more information, refer to Exceptions in unit effectivity and Overview of uniteffectivity.

▪ Generic Browser Framework (GBF)In ERP LN 6.1, you can use the Generic Browser Framework (GBF) to display graphicalrepresentations of BOMs. For more information, refer to Generic Browser Framework (GBF)(p. 190) .

▪ Alternative materialIn ERP LN 6.1, you can define up to nine alternative materials for any material in a BOM. If ashortage of a standard material is expected to delay a production order, baan can automatically


Manufacturing

select one of the alternative materials. For more information, refer to Alternative material anduse-up of old revisions (p. 187) and Alternative materials in BOMs.

Cost Accounting (CPR) module - Differences B50c/ERP61

This topic describes the most important differences between the Cost Price Calculation module in ERPBaan5.0c and in ERP LN 6.1.


▪ Cost componentsIn ERP LN 6.1, you can choose whether to collect costs on aggregated cost componentsdefined in the Items - Costing (ticpr0107m000) session, or to break down costs into detailedcost components. For more information, refer to Cost components (p. 188) .

New functionality

▪ Lower cost or market valueIn ERP LN 6.1, you can choose to use market prices to valuate inventory for standard items.For more information, refer to Lower cost or market value.

Production Order Costing (CST) module - Differences B50c/ERP61

This topic describes the most important differences between the Production Order Costing module inERP Baan5.0c and in ERP LN 6.1.


▪ Financial transactions by production order or work centerIn ERP LN 6.1, financial transactions cannot only be recorded by production order, but alsoby work center. For more information, refer to Financial transactions by production order orwork center.

New functionality

▪ Actual costingIn actual costing, actual valuation methods calculate the valuation price of end items ininventory. For more information, refer to Actual costing for receipt postings.

▪ Costing work centersThe introduction of costing work centers makes costing and planning more independent. Formore information, refer to Costing work centers (p. 188)

▪ Adding and exploding phantomsIn ERP LN 6.1, you can manually add phantoms to an existing production order, in the sameway as you can add extra material to an existing production order. For more information, referto, Add and explode phantoms in a production order (p. 187) .


Manufacturing

▪ Production warehouse orders to issue materialIn ERP LN 6.1, a new session is introduced, the Production Warehouse Orders(timfc0101m000) session, in which you can issue, return, or cancel items in a more detailedway. This is especially important in case of serialized items, lot controlled items, or unit effectiveitems. For more information, refer to Production warehouse orders (p. 196) .

Engineering Data Management (EDM) module - Differences B50c/ERP61

This topic describes the most important differences between the Engineering Data Management modulein ERP Baan5.0c and in ERP LN 6.1.

Removed functionality

▪ Engineering item groupsEngineering item groups do no exist anymore in ERP LN 6.1. For more information, refer toEngineering item groups (p. 190)


▪ ECOsIn ERP LN 6.1, ECOs are replaced by MBCs. For more information, refer to EngineeringChange Orders (ECOs).

▪ ECO approval procedureIn ERP LN 6.1, ECO approval procedures are not part of EDM, but they are managed bychange orders in the Data Management package. For more information, refer to ECO approvalprocedure.

▪ Drawing sizes and locationsIn ERP LN 6.1, drawing sizes and drawing locations are stored in the Document Managementmodule in Object Data Management. Drawing sizes and drawing locations in EDM

▪ Multilevel finalizingIn ERPBaan5.0c, ERP LN generated E-BOM copy data onmultiple levels and ERP LN finalizedE-BOM copy data only on the single level.In ERP LN 6.1, you can also finalize E-BOM copy data on multiple levels. To finalize multilevel,select the Finalize Multilevel check box in the Finalize Engineering Data (tiedm3240m000)session.

▪ Generate E-BOM copy data with an automatic insertion of E-item – item relationshipsIn ERP Baan5.0c, if you generated E-BOM copy data, you had to define E-item-itemrelationships for each E-item one by one.In ERP LN 6.1, in the Generate EBOM Copy Data (Multilevel) (tiedm1230m000) session, youcan also create the E-item - item relationships automatically.


Manufacturing

New functionality

▪ Unit effectivityUnit effectivity is a method to control the validity of variations on an end item. You can useunit effectivity for pegging purposes, or to model exceptions from a standard end item so thatyou can make variations without having to define separate item codes. As a result, you do notneed to maintain separate BOMs for every combination of variations. End items can be, forexample, airplanes or touring cars.You can link exceptions to an E-BOM line so that you can model a deviation of the E-BOMfor a unit effective item. For more information, refer to Exceptions in unit effectivity, Uniteffectivity in EDM, and Overview of unit effectivity.

▪ To copy a P-BOM to an E-BOMIn ERP Baan5.0c, if you want to use the Engineering Data Management EDM module toredesign an existing manufactured item, you must first define an E-BOM for the itemmanually.In ERP LN 6.1, a new session makes it much easier to create an E-BOM from an existingP-BOM. This session is the Copy PBOM to EBOM (tiedm0205m000) session.

▪ To copy an E-BOMIn ERP LN 6.1, the new Copy Engineering BOM (tiedm1210m000) session provides aconvenient method to copy engineering BOMs.

▪ Print comparison reportsIn ERP LN 6.1, the new Print Engineering BOMComparison Report (tiedm1414m000) sessionenables you to print a report that compares any two E-BOMs.

▪ Generic Browser Framework (GBF)In ERP LN 6.1, you can use the Generic Browser Framework (GBF) to display graphicalrepresentations of E-BOMs and engineering item revisions. For E-BOMs, start the GBF fromthe Engineering BOM (tiedm1110m000) session, for engineering item revisions from theEngineering Item (tiedm0110m000) session. For more information, refer to Generic BrowserFramework (GBF) (p. 190) .

▪ Use-up of old revisionsIn ERP LN 6.1, if a component must be phased out, the planning engine consumes the oldversions in stock but old versions are not ordered anymore. For more information, refer to,Alternative material and use-up of old revisions (p. 187) .

Hours Accounting (HRA) module - Differences B50c/ERP61

This topic describes in which packages and modules hours accounting for manufacturing takes placein ERP Baan5.0c and in ERP LN 6.1.

Hours accounting for manufacturing in ERP Baan5.0cIn ERP Baan5.0c, hours accounting for manufacturing takes place in the Hours Accounting (HRA)module in Manufacturing.


Manufacturing

Hours accounting for manufacturing in ERP LN 6.1In ERP LN 6.1, the HRAmodule does not exist anymore in Manufacturing. All hours accounting activitiesin ERP LN 6.1 are centralized in People.

Working hours in ERP Baan5.0c HRA are called working hours types in ERP LN 6.1. This functionalityhas moved to the Central Calendar Management (CCP) module in Common Data. Also period tablesare moved from HRA to the Calendars and Periods module. For more information, refer to CentralCalendar Management (CCP) module - Differences B50c/ERP61 (p. 36) .

Product Configuration (PCF) module - Differences B50c/ERP61

This topic describes the most important differences between the Product Configuration module in ERPBaan5.0c and in ERP LN 6.1.


▪ Generic BOM/routingIn ERP LN 6.1, the generic BOM and routing have some extra functionality to keep them inline with the production BOM and routing. For more information, refer to Generic engineeringdata: BOM and routing (p. 191) .

▪ Usability improvementsIn ERP LN 6.1, the new Generic Item - Structure (tipcf3100m100) session provides fast accessto information related to generic items, such as the generic routing, generic BOM, productfeatures, and constraints. For more information, refer to To use a header-lines session.

Project Control (PCS) module - Differences B50c/ERP61

This topic describes the most important difference between the Project Control module in ERP Baan5.0cand in ERP LN 6.1.


▪ Rough capacity consumptionIn ERP LN 6.1, you can use the Use Rough PCS Capacity Reguirement check box in theWork Centers (tirou0101m000) session to prevent double consumption. For more information,refer to Rough capacity consumption of work centers in PCS (p. 199) .

New functionality

▪ Revenue recognitionIn ERP LN 6.1, you can use revenue recognition to determine the interim revenue and interimcost of goods sold (COGS) for an unfinished project, even before shipping any end item. Formore information, refer to Revenue recognition (p. 199) .

▪ Lower cost or market valueIn ERP LN 6.1, you can choose to use market prices to valuate inventory for customized items.For more information, refer to Lower cost or market value.


Manufacturing

Routing (ROU) module - Differences B50c/ERP61

This topic describes the most important differences between the Routing module in ERP Baan5.0c andin ERP LN 6.1.


▪ Lead time elementsThe lead time elements, defined in Routing, have changed compared to ERP Baan5.0c. Formore information, refer to Lead time elements (p. 193) .

▪ Operation overlapIn ERP LN 6.1, you can choose whether you want to indicate the operation overlap with aquantity, or with a percentage. For more information, refer to Operation overlap (p. 195) .

▪ Task typeIn ERP LN 6.1, you cannot define task types anymore. For more information, refer to Tasktype (p. 200) .

▪ CalendarsThe calendar functionality is moved to the Calendars and Periods (CCP) module in CommonData. For more information, refer toCentral Calendar Management (CCP) module - DifferencesB50c/ERP61 (p. 36) .

▪ Usability improvementsIn ERP LN 6.1, the new Work Centers Dashboard (timfc1501m000) session provides fastaccess to information related to work centers, such as utilization and input/output control.Furthermore, from the new Items Dashboard (timfc1500m000) session, you can easily accessthe BOM and routing for a specific item. For more information, refer to To use a dashboardsession.

New functionality

▪ Task relationshipsIn ERP LN 6.1, you cannot define lead time elements such as cycle time and cycle time onthe task level anymore. For more information, refer to Task - work center relationships (p. 201).

▪ Micro routingThe new concept of micro routing enables you to add an extra level of information to routingoperations. For more information, refer to Micro routing (p. 195) .

▪ Shared work centersThe new concept of shared work centers enables you to plan work in other logistic companies.For more information, refer to Shared work centers (p. 200) .

▪ Unit effectivityYou can link exceptions to a routing or a routing operation so that you can model a deviationof the routing (operation) for a unit effective item. For more information, refer to Exceptions inunit effectivity and Overview of unit effectivity.


Manufacturing


Manufacturing


Adjustments and cycle counting


ERP Baan5.0cIn ERP Baan5.0c, the cycle count functionality and inventory adjustment functionality are combined inthe same sessions.

ERP LN 6.1In ERP LN 6.1, these functionalities are separated.

Other main changes to the cycle count functionality are:

▪ Enhanced printing of cycle count orders▪ Easy entering of cycle count results▪ Easy entry of adjustments

▪ Usability of cycle countingTo enhance the usability of the cycle counting sessions, the following selection criteria fieldsare added:

Print Cycle Counting Orders (whinh5400m000) and Print Cycle Counting Check Report(whinh5401m000)▪ Warehouse▪ Employee▪ Order Date

Process Cycle Counting Orders (whinh5201m000)▪ Warehouse▪ Employee▪ Order Date


8Chapter 8Warehouse Management

▪ Count Number

WarehouseTheWarehouse field is added to the following sessions:▪ Recount Cycle Counting Orders (whinh5203m000)▪ Delete Cycle Counting Orders (whinh5210m000)

▪ Remove Processed Cycle Counting Orders (whinh5251m000

Blocking


ERP Baan5.0cIn ERP Baan5.0c, you can block an entire stockpoint.

ERP LN 6.1In ERP LN 6.1, you can also block a part of a stockpoint. Another change is that Quality Managementcan block a stockpoint as well.

Quality ManagementIf you create a storage inspection in Quality Management, ERP LN 6.1 automatically blocks the stockpointor quantity to be inspected. As a result, a record is created in the Warehouse - Location - Item - BlockedInventory (whwmd6130m000) session if the following applies:

▪ The Created by QM check box is selected

▪ The Reason for Blocking is the Reason for Storage Inspection as specified in the MasterData Parameters (whwmd0100s000) session.

You cannot manually unblock the stockpoint by deleting the record. ERP LN 6.1 unblocks the stockpointif the storage inspection is closed.

Cross-docking


ERP Baan5.0cIn ERP Baan5.0cWarehousing, cross-docking did not exist.

ERP LN 6.1In ERP LN 6.1, dynamic cross-docking is introduced.

Cross-docking is the process in which inbound goods are immediately taken from the receiving locationto a staging location for issue, without intermediate storage.


Warehouse Management

In addition to static cross-docking – where a sales order and a purchase order are linked – ERP LN 6.1now provides users with dynamic cross-docking functionality. This type of cross-docking does not requirea pre-established link between a purchase order and a sales order. Instead, it enables users to performthe following actions in Warehouse Management:

▪ Create cross-dock orders and cross-dock order lines.

▪ Change or cancel the cross-dock orders and cross-dock order lines at several moments duringthe cross-docking process.

▪ Let ERP LN 6.1 automatically create cross-dock orders and/or cross-dock order lines.

Note

In ERP LN 6.1, cross-docking can also be used for direct material supply (DMS).

Delivery notes

ERP Baan5.0cIn ERP Baan5.0c, delivery notes were not included in the shipping documents that you can print forgoods leaving the warehouse.

ERP LN 6.1In ERP LN 6.1, delivery notes are implemented in Warehouse Management and Freight Management,and you can model scenarios in which the use of delivery notes is enabled or suppressed.

Direct material supply


ERP Baan5.0cIn ERP Baan5.0c, direct material supply (DMS) did not exist.

ERP LN 6.1In ERP LN 6.1, direct material supply is introduced.

Direct material supply (DMS) is a supply method in which (pending) receipts and available inventory onhand are used to meet high-priority demand within a user-specific cluster of warehouses. This supplymethod can be run either automatically, interactively, or manually, using the Direct Material SupplyDistribution (whinh6130m000) session.

Handling units




ERP Baan5.0cIn ERP Baan5.0c, handling unit functionality was unavailable.

ERP LN 6.1In ERP LN 6.1, you can use a handling unit to pack items and to process inventory transactions for thepacked items.

A handling unit is a uniquely identifiable physical unit that consists of packaging and contents. Thecontents of a handling unit are the items that you receive, store, issue, or transfer into or from yourwarehouse.

Inventory transactions and handling unitsYou can use both handling units and warehousing orders as a basis for processing inventory transactions.If you use handling units to process goods in the warehouse, the inventory levels and warehousingorders on which the handling units are based are updated in the background. For more information,refer to Handling units.

Handling unit structuresA handling unit has a structure of packing materials and items. A handling-unit structure can vary froma simple box that contains a particular number of items, to a more complex structure such as a palletwith a number of boxes, which in turn can contain smaller boxes that contain a number of items. Ahandling unit structure can consist of various handling units related in a parent-child fashion.

You can manually create a handling unit structure for a given number of items, or you can define apackage definition in which you set up a template that determines the handling unit structure for particulartypes of items. For further information, see Package definitions and Handling unit structures.

Serialized items and handling unitsYou can register serial numbers for serialized items that are included in handling units. For moreinformation, refer to Handling Unit Lots and Serials (whwmd5136m000).

Handling unit setupTo make the handling unit functionality work in the preferred way, you must define some master dataand set some parameters. You can specify how handling units are used for particular items, warehouses,and/or business partners. For more information, refer to To set up handling units.

Integration with Freight Management




ERP Baan5.0cIn ERP Baan5.0c, the receipt and the issue of goods are based on warehousing orders. If no ASNs areused, you cannot receive goods triggered by the arrival of a specific truck at the dock.

The concept of shipments and loads is only used to issue goods, not to receive goods. Because shipmentsare composed from warehousing orders or warehousing order lines, you cannot automatically combinewarehousing orders or warehousing order lines with different destinations. However, you can manuallyadjust the shipments. You cannot pick the warehousing order lines that must go into a specific truck thatleaves at a particular time.

ERP LN 6.1ERP LN 6.1, Warehouse Management is integrated with Freight Management to enable loads andshipments created by Freight Management to be processed.

Freight ManagementFreight Management creates freight orders from inbound or outbound warehousing-order lines and orderlines of other origins, such as purchase orders or sales orders. If a freight order is created for a salesorder or an order of another origin, there is no need to create a freight order for the warehousing orderrelated to the originating order.

The freight orders are used to create load plans or freight order clusters.

The load plans are created by means of various consolidation algorithms and grouping criteria such asroutes, transport costs, carriers, and so on. A load plan is, essentially, a transport plan and includesloads and shipments. A load plan provides you with information such as:

▪ Details about the goods to be transported

▪ Loading and unloading addresses, dates, and times

▪ The carrier that is to carry out transportation▪ Transport costs

A freight order cluster is a group of freight order lines with matching properties, such as shipping offices,planning groups, overlapping time windows, transport means groups, and so on, that is subcontractedto a carrier. The carrier will plan and carry out the transportation of the goods listed on the freight orderlines according to the subcontracting order.

Freight Management is not used for sales schedules that are related to the Closed Loop ASN functionality.For these sales schedules, a shipping sequence is already defined inWarehouseManagement. Therefore,these sales schedules cannot be planned in a different sequence.

Load plans processed by Warehouse ManagementFreight Management sends load plans, which are based on freight orders created from warehousingorders, to the Planned Loads/Shipments (whinh4180m000) session in Warehouse Management forfurther processing.



You can use the loads and shipments of the load plans to receive or ship goods from the warehouse.If you ship or receive a load or a shipment, the related inbound or outbound warehousing order linesare updated in the background.

You can also ignore the loads or shipments from the load plan and create loads and shipments inWarehouseManagement to replace them. In addition, if you do not create freight orders for warehousingorder lines, you can create loads and shipments in Warehouse Management without using FreightManagement.

Warehousing orders and freight ordersFor warehousing orders, freight orders can be generated automatically from Warehouse Managementor createdmanually or automatically in Freight Management. Freight orders can also be directly generatedfor purchase orders and sales orders before a warehousing order is generated for these purchase ordersand sales orders.

If a warehousing order is generated, changed, or deleted, and a freight order is already available forthis warehousing order, the freight order is updated with the changes or deleted. For more information,refer to Freight order statuses. If the freight order cannot be deleted, the warehousing order cannot bedeleted either.

Receipt based on planned loads and shipmentsIn the Planned Loads/Shipments (whinh4180m000) session, you can use a load number and/or ashipment number register a receipt. When a load or shipment is received and the receipt is confirmed,the inbound order lines that are linked to the shipment or load are automatically linked to the receiptbased on the planned loads and shipments recorded in the Planned Loads/Shipments (whinh4180m000)session.

Shipment based on planned loads and shipmentsIn the Planned Loads/Shipments (whinh4180m000) session, you can generate and release outboundadvice, and generate picking lists for a range of planned loads or planned shipments.

To ship the goods listed on outbound order lines for which freight order lines are present, by default,Warehouse Management uses the loads and shipments of the load plan based on the freight order linescreated by Freight Management. You can also overrule the load plan and haveWarehouseManagementcreate loads and shipments, or manually create loads and shipments in the Planned Loads/Shipments(whinh4180m000) or Compose Load (whinh4134m000) session. For more information, refer toOverruleLoad Plan and Planned Loads/Shipments (whinh4180m000)

You can specify that the load plans created by Freight Management are leading. If a load plan is leadingand you change the loads and shipments of the load plan in the Planned Loads/Shipments(whinh4180m000) session, the changes are confirmed or rejected by Freight Management. If the changesare rejected, Freight Management provides Warehouse Management with an alternative load plan. Ifthe load plan is not leading, you can change the planned loads or planned shipments without confirmationof Freight Management.



Integration with Service


ERP LN 6.1Service uses the warehousing functionality to handle the following types of items:

▪ Repairable items▪ Consumable items▪ Loan items

To support warehouse transactions involved in depot repair, the following warehouse types and orderorigins have been introduced in Warehouse Management:

Order origins

▪ Maintenance Sales and Maintenance Sales (Manual)Maintenance sales orders are used to handle the customer’s request for repair of a customerowned item, the customer's request for a loan item, and the return of both the customer owneditem and the loan item.

▪ Maintenance Work Order and Maintenance Work (Manual)Maintenance work orders are used to handle the actual repair of customer owned items in amaintenance shop and the physical movement of the customer owned item between theService Customer-Owned Warehouse and the work center.

Warehouse types

▪ Service Customer OwnedA type of warehouse that you use exclusively to store items that are owned by the customersand that have been sent to the depot to be repaired or serviced. Receipt and issue of itemsdoes not affect the value of the warehouse inventory because the items are owned by thecustomers. Therefore, receipt and issue of items does not result in financial transactions.

▪ Service RejectA type of warehouse that you use to store items which are rejected after inspection. The itemsin a Service Reject warehouse can be:▪ Repaired on a work order▪ Scrapped by means of a warehouse procedure▪ Returned to the owner

The Service Reject warehouse and the Service Customer Owned warehouse are available formaintenance sales orders and maintenance work orders, and, in some cases, the Service Rejectwarehouse can be used for orders of origin Sales and Sales (Manual).

Inspections




ERP Baan5.0cIn ERP Baan5.0c, during inspections you can approve or reject goods. For rejected goods, an adjustmentorder is generated automatically and as a result, the rejected goods are removed from inventory. Totake rejected goods back into inventory, an adjustment order must be created.

ERP LN 6.1In ERP LN 6.1, you can approve, destroy, or reject goods after inbound or outbound inspection. Inaddition, various options are available for handling goods that are rejected during inspection.

TheApprovals (whinh3522m000) session is replaced with theWarehouse Inspections (whinh3122m000)session. You can use the Warehouse Inspections (whinh3122m000) session to approve, reject, ordestroy goods. The destroyed quantity is part of the approved quantity and removed from inventory.

The destroyed quantity is part of the approved quantity because the supplier must be paid for thedestroyed goods. The supplier must be paid for the destroyed goods, because usually the goods weredestroyed for testing purposes or by some accident, for which the supplier is not liable.

To handle rejected inventory, you can move rejected goods to a reject location. In the Rejected Inventory(whwmd2570m000) session, you can accept, return, or destroy rejected goods. For destroyed or returnedrejected goods, a back order is generated.

An adjustment order is generated for any rejected quantity if no reject location is present.

The Rejected Inventory (whwmd2570m000) session and locations of type Reject are new in ERP LN6.1. These, and various other new features are described in Rejected inventory settings

Line supply

This topic explains the new line supply functionality in ERP LN 6.1.

ERP Baan5.0cIn ERP Baan5.0c, the following supply systems are available:

▪ Kanban▪ Time-phased order point▪ Order controlled/Single

ERP LN 6.1In ERP LN 6.1, two new line supply systems are added to feed the assembly line:

▪ Order controlled/Batch▪ Order controlled/SILS



Loading list

ERP LN 6.1In ERP LN 6.1, loading lists are available in Warehouse Management. A loading list is a report thatshows the loading sequence of the shipments of a load.. The loading sequence of a loading list is basedon the planned load dates and the delivery addresses, and you can specify whether the loading sequencemust be ascending or descending.

In addition, a loading list provides information about the shipments of a load such as items, quantities,route details, packing instructions, and so on. This session enables you to specify the types of additionalinformation that the report must include.

The report also includes an empty column titled Loaded Quantity, in which warehouse personnel canenter quantities of goods actually loaded, for example, if discrepancies occur between planned andactually loaded quantities.

Optionally, you can enter free text, for example, additional loading instructions, on the report.

You can generate loading lists in the Generate Loading List (whinh4445m000) session. You can accessthe Generate Loading List (whinh4445m000) session from the following sessions:

▪ Shipments (whinh4130m000)▪ Loads (whinh4140m000)▪ Planned Loads/Shipments (whinh4180m000)▪ Shipments (whinh4630m000)

In addition, the loading sequence number for shipments is displayed in the following sessions:

▪ Shipments (whinh4130m000)▪ Planned Loads/Shipments (whinh4180m000)▪ Shipments (whinh4630m000)

Lots (not in inventory)

This topic explains the new lots (not in inventory) functionality in ERP LN 6.1.

ERP Baan5.0cIn ERP Baan5.0c lot handling in Warehouse Management requires one receipt line, inbound advice line,outbound advice line, shipment line, and so on, for each lot. The advantage is that the exact location ofthe lot can be found in inventory at stockpoint.

ERP LN 6.1ERP LN 6.1 introduces lot handling for which lot numbers are not stored in inventory, which is called lot(not in inventory). Both lot in inventory and lot (not in inventory) is available in ERP LN 6.1.

For the following transactions, you can register which lots were involved in the receipt transaction. Youregister this information in distribution tables for lots and serial numbers.

▪ Lot Entry During Receipt



▪ Lot Entry During Transfer▪ Register Lot Issue During As Built

The transaction for which lot registration is available is determined by parameter settings.

The following sessions are changed as a result of the introduction of lot (not in inventory):

▪ Item - Warehousing (whwmd4100s000)

▪ Handling Unit Lots and Serials (whwmd5136m000)

▪ Inbound Order Line Lots and Serials (whinh2116m000)▪ ASN Line Lots and Serials (whinh3105m000)

▪ Receipt Line Lots and Serials (whinh3123m000)

▪ Outbound Advice Lots and Serials (whinh4126m000)

▪ Shipment Line Lots and Serials (whinh4133m000)

Multicompany warehouse transfers


ERP Baan5.0cIn ERP Baan5.0c, transfers between two logistic companies were supported by the sales-purchaserelation.

ERP LN 6.1In ERP LN 6.1, functionality is available that supports multi-company warehouse transfers. Multicompanywarehouse transfers enable you to use warehouse transfers to ship goods between warehouses thatbelong to different logistic companies.

The benefits of multicompany warehouse transfers are:

▪ More transparency about the inter-logistical company transfers to the user.▪ Fewer transactions.

Note

▪ You cannot use customized items in multicompany warehousing orders, because the projectdata is not shared in the overall multisite solution. For the same reason, you cannot usecustomized items for project warehouses.

▪ You can only use multicompany warehousing orders in a single-server environment.

Order grouping

This topic explains the new order grouping funtionality in ERP LN 6.1.

Order grouping is a flexible and dynamic new capability that facilitates more efficient order processingfor users interacting with ERP LN 6.1. For example, if several separate orders must undergo the same



operations and/or must be managed by the same person, it can be useful to group and process theorders simultaneously.

User interaction with Warehouse Management includes confirming, transferring, printing, releasing, andprocessing outbound advice, all based on order groups. The order groups are generated in Manufacturingwhere all orders that meet particular criteria are automatically linked to the newly-generated order group.InWarehouse Management, the order group is displayed only, but can be used to group orders for whichthe previously mentioned transactions can be performed.

The functions affected by this change, are:

▪ Process Outbound Advice▪ Generate Outbound Advice▪ Release Outbound Advice▪ Generate Picking List

Note

You can use order groups in the following sessions:

▪ Warehousing Orders (whinh2100m000)▪ Outbound Order Lines (whinh2120m000)▪ Warehousing Orders History (whinh2550m000)

Order cancellation

This topic explains the new order cancellation funtionality in ERP LN 6.1.

You can cancel all current or future orders or schedules for a specific business partner in the Salesmodule and in Service. You can choose to delete orders, for example, when contracts are broken, orcredit limits are exceeded. You can also terminate the material supply to a specific work center in Service.

When these orders or schedules are cancelled, cancellation for the related warehousing orders musttriggered by the originating package. In ERP LN 6.1, you can cancel the outbound order lines that arerelated to the cancelled orders or schedules, when triggered by the originating package.

To make order cancellation work in the preferred way, for each warehousing order type, you must selectthe relevant value in theRemove Canceled Outbound Order Lines Till field of theWarehousing OrderType (whinh0110m000)

Receipts

ERP Baan5.0cIn ERP Baan5.0c, handling receipts in Warehouse Management required the use of various sessions,and limitations in the available search options for order lines were encountered.

Infor® ERP LNIn ERP LN 6.1, the usability of the Warehouse Receipts (whinh3512m000) session is vastly improved.



You can perform the entire receipt procedure in this session and the sessions that you can access viathe specific menu.

TheWarehouse Receipts (whinh3512m000) session is now subdivided into a header and a lines section.Both the header section and the lines section are provided with tabs that group the available informationand the tasks to be performed.

You can customize this session by showing or hiding header section tabs and/or line section tabs, andshowing or hiding toolbar commands. The information and the functionality of the tabs are also availableas a regular ERP LN 6.1 sessions.

Header sectionThe tabs on the header section enable you to:

▪ Enter receipt headers▪ Enter receipt texts

▪ Look up inbound orders, order lines, or ASNs that you want to link to or unlink from the receipt.To look up records, the following search facilities are available:

▪ Receipt filter, which provides extensive search functionality.

▪ Receive (Easy Entry), a more compact search facility.▪ Link records to a receipt▪ Unlink records from a receipt

Lines sectionThe tabs on the lines section show:

▪ The receipt lines of the receipt header

▪ The messages generated for the current receipt

▪ Inbound advice lines associated with the receipt▪ Inspection lines associated with the receipt

If you double-click a line in a tab, a session opens showing more detailed information of the line. Forexample, if you double-click a line in the Inspections tab, the Warehouse Inspections (whinh3122m000)session opens showing more detailed information of the associated inspection and inspection line.

The information in the lines section tabs is editable, unless the status of the lines displayed does notallow editing.

Serialized items


ERP Baan5.0cIn ERP Baan5.0c, you can assign lot numbers to units in order to classify and track items. In ERP LN6.1, the lot-by-unit functionality is replaced with serialized items.For further information on the use ofserialized items, see Serialized items in Warehouse Management.



ERP LN 6.1A serialized item is a physical occurrence of a standard item that is given a unique lifetime serial number.This enables tracking of the individual item throughout its lifetime, for example, through the design,production, testing, installation, and maintenance phases.

A serialized item can consist of other serialized components. Examples of serialized items are cars(Vehicle Identification Number), airplanes (tail numbers), PCs, and other electronic equipment (serialnumbers).

In Warehouse Management, you can use serial numbers to track serialized items through receipts,transfers, storage, or issues, the latter of which is mandatory. This package also enables you to trackserialized items back to their source. The source of a serialized item is, for example, the purchase orderor the production order that caused the receipt of the serialized item, or the sales order or the work orderthat caused the issue of the serialized item.

In theWarehousingMaster Data (WMD)module of ERP LN 6.1, various settings are available to enabletracking of serialized items.

Low volume scenarioThis scenario is used for expensive items produced and handled in relatively small quantities that requireintensive tracking throughout the warehouse flow.

Each serialized item is individually stored in inventory, and processed individually trough warehousing.For each warehousing transaction, an individual receipt line, outbound advice line, shipment line, orinspection line is created and, either manually or automatically, a serial number is allocated. Whilewarehouse transactions are carried out, inventory records of the serialized items are updated. For moreinformation, refer to To register serial numbers in the low volume scenario.

High volume scenarioThe high volume scenario is used for relatively less expensive items produced and handled in largequantities that require less intensive tracking. In this scenario, serialized items are not individually storedin inventory.

For each item-by-warehouse you can specify whether serial numbers must be registered for receipts,transfers, and/or issues. This helps you obtain an overview of the whereabouts of particular serializeditems through warehousing but also enables you to skip scrutinizing serials where you do not need it.For more information, refer to To register serial numbers in the high volume scenario

Tracking originating orders for serialized itemsWarehouse Management also provides the option to track the orders that initiated the receipt, transfer,or issue of serialized items, such as production orders, purchase orders, or sales orders. This option isavailable for both the low volume scenario and the high volume scenario. For further information onserial tracking options, see Serial Tracking.

To delete redundant lot and serial tracking data, you can use the following:

▪ The Delete Serial Tracking (whltc5210m000) session.



▪ TheDelete Serial Tracking field in the Delete Serials byWarehouse (whltc5200m000) session.

SetupTo use serialized items in the preferred way, some data setup is required. For more information, referto To set up serialized items.

In the Warehousing Order Type (whinh0110m000) session, in the Generate Serials Automaticallyfield, you can specify whether lot and/or serial codes must be automatically created during receipts forparticular warehousing order types.

Shipment generation for warehouse issues

ERP Baan5.0cIn ERP Baan5.0c, you could not generate shipments for:

▪ Goods received from suppliers that are passed on to work centers without entering thewarehouse, the cross-docking scenario.

▪ For goods issued from a warehouse to a work center.

As a result, you could not register lot codes or serial numbers for items passed on to work centers viacross-docking or print delivery notes.

ERP LN 6.1In ERP LN 6.1, the user is enabled to generate shipments for various types of issues to facilitate lot andserial registration and the creation of delivery notes. For more information, refer to Create Shipment.

Unit effectivity


ERP Baan5.0cIn ERP Baan5.0c, unit effectivity did not exist.

ERP LN 6.1In ERP LN 6.1, unit effectivity is introduced. Effectivity units are not defined in Warehouse Management,but effectivity unit codes added to unit effective items appear throughout Warehouse Management, forexample on inbound and outbound order lines, shipments, receipts, outbound advice, and so on.

Unit effectivity is a method to control the validity of variations on an end item. You can use unit effectivityfor pegging purposes, or to model exceptions from a standard end item so that you can make variationswithout having to define separate item codes. As a result, you do not need to maintain separate BOMsfor every combination of variations. End items can be, for example, airplanes or touring cars.



The deviations consist of relatively small variations of the end item. For example, fitting red seats insteadof blue ones, or a special type of radar or air-conditioning, in an otherwise standard type of airplane.For more information, refer to Overview of unit effectivity

Usability improvements for shipment notices

ERP Baan5.0cIn ERP Baan5.0c, handling shipment notices in Warehouse Management required the use of varioussessions.

ERP LN 6.1In ERP LN 6.1, the Shipment Notices (whinh3600m000) session is created to improve shipment noticehandling and processing. The Shipment Notices (whinh3600m000) session is subdivided into a headersection and a lines section and includes the following information:

▪ Header sectionShipment notice details

▪ Lines sectionLines

▪ Routings▪ Packaging

The lines section provides access to the following sessions:

▪ Shipment Notice - Lines (whinh3101m000)▪ Inbound ASN Routings (whinh3115m000)

▪ Shipment Notice - Header Packaging (whinh3103m000)

In the lines section, if you double-click a line in any of the tabs, detailed information is displayed. Forexample, in the Lines section, if you double-click a line in the Lines tab, the Shipment Notice - Lines(whinh3101m000) session starts showing detailed information on the shipment notice line.

Warehouse Management dashboard sessions

ERP LN 6.1For ERP LN 6.1, warehousing dashboard sessions are introduced in Warehouse Management. Adashboard session provides a quick overview of the information and the tasks of a particular functionalarea and provides easy access to more detailed information. This will help users perform their tasksmore efficiently. The following dashboard sessions are available:

▪ Warehouse Manager Dashboard (whinh2300m000)▪ Warehouses Dashboard (whwmd2300m000)▪ Inventory Dashboard (whwmd4300m000)▪ Shipment Notice (whinh3600m000)▪ Shipments (whinh4630m000)



Warehousing order processing


ERP Baan5.0cIn ERP Baan5.0c, warehousing procedures are defined and allocated to warehousing order types. Asa result, a warehousing order of a particular warehousing order type is processed according to thewarehousing procedure that is allocated to the warehousing order type.

Once the warehousing procedure is defined and allocated to a warehousing order type, you cannotchange the warehousing procedure for orders of this particular warehousing order type.

For most activities in a warehousing procedure, you cannot specify whether they are applicable for theprocedure, or control whether they are performed automatically or by user intervention.

ERP LN 6.1In ERP LN 6.1, warehouse processing for warehousing orders has become more flexible. You canchange the warehousing procedure for individual warehousing orders and warehousing order lines,even after the procedure has started. After a warehousing procedure has started, you can change theactivities that are still to be carried out. For more information, refer to How to modify warehousingprocedures

For most activities of a warehousing procedure, you can specify whether they must be included in theprocedure, or whether theymust be carried out automatically or by user intervention. For more information,refer to Default values for order line activities

Modules

Inventory Analysis (INA) module - Differences B50c/ERP61

This topic describes the most important differences between the Inventory Analysis modules in ERPBaan5.0c and in ERP LN 6.1.

New functionality

▪ Additional inventory valuation methodIn ERP LN 6.1, a new inventory valuation method has been added: Moving. Average UnitCost (MAUC). The MAUC is the average value for each unit of the current inventory. For eachnew receipt the MAUC is updated. For more information, refer to Moving Average Unit Cost(MAUC).

▪ Lower cost or market valueIn ERP LN 6.1, you can choose whether or not to revaluate the inventory value to the lowercost or market value (LCMV). This valuation method compares the inventory value based onone of the inventory valuation methods with the inventory's market value. If the market value



is lower, the entire inventory of a specific item is valued in the balance sheet using the marketvalue.. For more information, refer to Inventory valuation.

▪ Item/Warehouse valuation groupsIn addition to inventory valuation by warehouse, inventory valuation can now also be performedby:▪ Item type▪ Item valuation group▪ Warehouse valuation group


▪ Cost Component Solution (CCS)In ERP LN 6.1, the cost component solution is made available for assembly environmentsthat use the Assembly Control (ASC) module in Manufacturing. For more information, referto Assembly order costing.

▪ Negative inventoryIn ERP LN 6.1, the negative inventory functionality is divided in a part that deals with thelogistical negative inventory transactions and a part that deals with the financial negativeinventory transactions.As a result, the following sessions are added:

▪ Negative Inventory Consumptions (whina1520m000)

▪ Negative Inventory Consumption Cost Details (whina1521m000)

▪ Print Negative Inventory Consumptions (whina1420m000)

▪ New fieldTo enable employees to distinguish their own workload from their coworkers’ workloads, thePlanner field was added to the selection criteria in the Perform Slow-Moving Analysis(whina6220m000) session.

Inventory Handling (INH) module - Differences B50c/ERP61

This topic summarizes the differences between the Inventory Handling modules of B50c/ERP61 andERP LN 6.1.

New functionality

▪ Cross-dockingIn ERP LN 6.1, functionality that supports cross-docking has been introduced. For moreinformation, refer to Cross-docking (p. 210) .

▪ Delivery notesIn ERP LN 6.1, delivery notes are added to the shipping documents that you can print forgoods leaving the warehouse. For more information, refer to Delivery notes (p. 211)

▪ Direct material supplyIn ERP LN 6.1, the direct material supply functionality has been introduced. For moreinformation, refer to Direct material supply (p. 211) .



▪ Freeze/Confirm shipment lineIn ERP LN 6.1, you can print the shipment documents before the shipment is confirmed.Therefore, the shipment documents can be printed at the moment the goods are picked andready for shipment. To enable shipment document printing before the shipment is confirmed,you must allocate the Frozen status to the shipment.For more information, refer to▪ The shipment procedure▪ Shipments and loads▪ Shipment and load statusesFreight Management performs transportation planning for both inbound and outbound goodsthat require transportation. For more information, refer to Integration with Freight Management(p. 212) .

▪ Integration with Freight ManagementERP LN 6.1, Warehouse Management is integrated with Freight Management to enable loadsand shipments created by Freight Management to be processed.Freight Management performs transportation planning for both inbound and outbound goodsthat require transportation. For more information, refer to Integration with Freight Management(p. 212) .

▪ Loading listFor ERP LN 6.1, loading lists are introduced in Warehouse Management. A loading list is areport that shows the loading sequence of the shipments of a load. For more information, referto Loading list (p. 217)

▪ Order cancellationIn ERP LN 6.1, outbound order lines can be cancelled if triggered by the package that createdthe originating order. For more information, refer to Order cancellation (p. 219) .

▪ OverdeliveryIn ERP LN 6.1, functionality is introduced that enables you to ship more goods than thecustomer ordered. You can also keep track of the customer’s actually ordered quantity andthe overdelivered quantity. The overdelivered quantity is calculated as follows:Advised quantity - (Ordered quantity + Rejected quantity + Quantityexpected not shipped + Quantity not shipped).

The allowed overdelivery depends on the tolerances specified in the Warehousing Orders(whinh2100m000) session.


▪ Adjustments and cycle countingIn ERP Baan5.0c, the cycle count functionality and inventory adjustment functionalities arecombined in the same sessions. In ERP LN 6.1, the cycle counting and adjustmentfunctionalities are separated. For more information, refer to Adjustments and cycle counting(p. 209) .



▪ InspectionsIn ERP LN 6.1, you can approve, destroy, or reject goods after inspection. In addition, variousoptions are available for handling goods that are rejected during inspection. For moreinformation, refer to Inspections (p. 215) .

▪ Order groupingOrder grouping is a flexible and dynamic new capability that facilitates more efficient orderprocessing for users interacting with ERP LN 6.1. For more information, refer toOrder grouping(p. 218) .

▪ Order processingWarehousing order processing has become more flexible in ERP LN 6.1. You can include orexclude activities activities from a warehousing procedure, or determine whether the activitiesmust be carried out automatically or by user intervention. In addition, you can changewarehousing procedures for individual warehousing orders and order lines. For moreinformation, refer toWarehousing order processing (p. 224) .

▪ ReceiptsMajor enhancements have been introduced for the receipt functionality. For more information,refer to Receipts (p. 219) .

▪ Shipment generation for warehouse issuesIn ERP LN 6.1, the user is enabled to generate shipments for various types of issues to facilitatelot and serial registration and the creation of delivery notes. For more information, refer toShipment generation for warehouse issues (p. 222)

▪ Usability improvements for shipment noticesMajor enhancements have been introduced for the shipment notice functionality. For moreinformation, refer to Usability improvements for shipment notices (p. 223)

Inventory Planning (INP) module - Differences B50c/ERP61

This topic describes the most important differences between the Inventory Planning module in ERPBaan5.0c and in ERP LN 6.1.


▪ Inventory commitment and lead timesIn ERP LN 6.1, the calculation of the commitment date is changed, some lead times are added,and the calendars are taken into account. For more information, refer to Inventory commitmentdate calculation.

▪ Rebuild planned inventory transactionsIn ERP Baan5.0c, you only could rebuild planned inventory transactions for all items.In ERP LN 6.1, you can indicate a range of item groups or items for which the planned inventorytransactions must be rebuilt. In addition to this, you can simulate rebuilding planned inventorytransactions. For more information, refer to Rebuild Planned Inventory Transactions(whinp1200m000).

▪ New fieldThe Committed in Process field was added to the Inventory Commitments (whinp2100s000)session.



Inventory Reporting (INR) module - Differences B50c/ERP61

This topic describes the most important differences between the Inventory Reporting module in ERPBaan5.0c and in ERP LN 6.1.


▪ Sessions mergedIn ERP Baan5.0c, two sessions are available to view the lot inventory data.:▪ Lot by Warehouse (whltc1505m000)▪ Inventory by Warehouse, Item, and Lot (whinr1540m000)In ERP LN 6.1, these sessions are merged into the Warehouse - Item - Lots Inventory(whltc1505m000) session.

▪ In ERP Baan5.0c, four sessions are available to view the stockpoint inventory data.

▪ Inventory byWarehouse, Location, Item, and Lot (whinr1541m000)/(whinr1541s000)▪ Inventory by Item, Warehouse, Location, and Lot (whinr1542m000)▪ Inventory by Warehouse, Item, Lot, and Location (whinr1543m000)▪ Inventory by Item, Lot, Inventory Date, and Warehouse (whinr1545m000)In ERP LN 6.1, these sessions are merged into the Stock Point Inventory (whinr1540m000)session.

Lot Control (LTC) module - Differences B50c/ERP61

This topic describes the most important differences between the Lot Control modules in ERP Baan5.0cand in ERP LN 6.1.

New functionality

▪ Serial trackingThe new functionality to track and trace serialized items is combined with the functionality totrack and trace lots. This combined functionality also enables users to track the serializeditems and lot-controlled items for multi-level bills of material (BOMs). You can track serializeditems for which, in the Item - Warehousing (whwmd4100s000) session, the Serial Trackingcheck box is selected. You can use the following sessions to track serialized items on variouslevels:▪ Serial Tracking - Overview (whltc5515m000)

▪ Item - Serials and Warehouses (whltc5100m000)▪ Item - Serials - Issues (whltc5510m000)▪ Item - Serials - Receipts (whltc5511m000)▪ Order - Serials (whltc5512m000)

▪ Lot (not in inventory)ERP LN 6.1 introduces lot handling for which lot numbers are not stored in inventory, whichis called lot (not in inventory). Both lot in inventory and lot (not in inventory) is available in ERPLN 6.1. For more information, refer to Lots (not in inventory) (p. 217) .



▪ Lot code based on originThe lot code based on the origin is added to improve the transparency of linkage betweenorder origin and lot codes. To improve transparency you can include original order numbersin lot numbers at the moment of lot creation.


▪ Lot and serial parametersIn ERP LN 6.1, you can specify that lot and serial tracking must be done at item level insteadof at company parameter level, as in ERP Baan5.0c.

▪ Lot allocationIn ERP Baan5.0c, the allocated lot inventory (both the soft allocated and the location allocatedlot inventory) is displayed in one field. which may result in misinterpretation of the allocatedlot quantity and errors in the allocation of lots.In ERP LN 6.1, the allocated lot inventory is divided in allocated lot inventory and locationallocated lot inventory.

Warehouse Master Data (WMD) module - Differences B50c/ERP61

This topic summarizes the differences between theWarehouse Master Data (WMD) modules ofB50c/ERP61 and ERP LN 6.1.

New functionality

▪ Handling unitsA handling unit is a uniquely identifiable physical unit that consists of packaging and contents.The contents of a handling unit are the items that you receive, store, issue, or transfer into orfrom your warehouse. For more information, refer to Pay-to business partner statistics (p. 74).

▪ Serialized itemsIn ERP Baan5.0c, you can assign lot numbers to units in order to classify and track items. InERP LN 6.1, the lot-by-unit functionality is replaced with serialized items. For more information,refer to Bank charges (p. 49) .

▪ Rejected goods handlingIn ERP Baan5.0c, for rejected goods, an adjustment order is generated automatically and asa result, the rejected goods are removed from inventory. To take rejected goods back intoinventory, an adjustment order must be created. In ERP LN 6.1, various options are availableto handle rejected goods. For more information, refer to Inspections (p. 215) .

▪ Multi-company warehouse transfersIn ERP Baan5.0c, transfers between two logistic companies were supported by thesales-purchase relation. In ERP LN 6.1, functionality is available that supports multi-companywarehouse transfers. Multi-company warehouse transfers enable you to use warehousetransfers to ship goods between warehouses that belong to different logistic companies. Formore information, refer to Multicompany warehouse transfers (p. 218) .




▪ BlockingIn ERP Baan5.0c, you can block an entire stockpoint. In ERP LN 6.1, you can also block apart of a stockpoint. Another change is that Quality Management can block a stockpoint aswell. For more information, refer to Blocking (p. 210)

▪ Integration with ServiceTo support warehouse transactions involved with depot repair handling, various order originsand warehouse types have been introduced. For more information, refer to Integration withService (p. 215)

▪ Line supplyFor ERP LN 6.1, various new supply systems are introduced in Warehouse Management. Formore information, refer to Line supply (p. 216)



Freight Management - Differences by ERP Baan5.0c topic

ERP Baan5.0c

In ERP Baan5.0c, transport planning functionality was unavailable.

ERP LN 6.1

In ERP LN 6.1, the Freight Management package is introduced. The purpose of Freight Managementis to plan and/or to subcontract the transportation of inbound and outbound goods, which helps youselect the most cost-effective way to get goods in and out of the site at the correct times.

Freight Management

Freight Management creates freight orders from inbound or outbound warehousing order lines and orderlines of other origins, such as purchase orders or sales orders. If a freight order is created for a salesorder or an order of another origin, there is no need to create a freight order for the warehousing orderrelated to the originating order.

The freight orders are used to create load plans or freight order clusters.

The load plans are created by means of various consolidation algorithms and grouping criteria such asroutes, transport costs, carriers, and so on. A load plan is, essentially, a transport plan and includesloads and shipments. A load plan provides you with information such as:

▪ Details about the goods to be transported

▪ Loading and unloading addresses, dates, and times

▪ The carrier that is to carry out transportation▪ Transport costs

A freight order cluster is a group of freight order lines with matching properties, such as shipping offices,planning groups, transport means groups, overlapping time windows, and so on, that is subcontractedto a carrier. The carrier will plan and carry out the transportation of the goods listed on the freight orderlines according to the subcontracting order.


9Chapter 9Freight Management


Freight Management


Call blocking

This topic describes the call blocking functionality in ERP LN 6.1.

Call blocking in ERP Baan5.0cThe call blocking functionality did not exist in ERP Baan5.0c.

Call blocking in ERP LN 6.1In ERP LN 6.1, call blocking is introduced to the Call Management (CLM)module. You can block a callif the customer is blocked for one or more of the following financial reasons:

▪ The customer’s credit limit is exceeded.▪ The customer’s credit review is overdue.▪ The customer’s invoice is overdue.▪ The customer is doubtful.

A call can be blocked if the call's status is one of the following:

▪ Registered▪ Assigned▪ In process

You must define the call blocking parameters in the Call Parameters (tsclm0100m000) session. Beforeyou set these parameters, be sure to select the Invoice after Call check box on the General tab.

Call handling

This topic describes the improved call handling functionality in ERP LN 6.1.

Call handling in ERP Baan5.0cIn ERP Baan5.0c, call handling enables you to manipulate and process calls in the following ways:


10Chapter 10Service

▪ Enter and log a call.▪ Assign calls to a service center.▪ Assign calls to a support engineer.▪ Reassign a call.▪ Process a call.▪ Accept a solved call.▪ Delete a call.▪ View calls.▪ Transfer calls to service orders.

Call handling in ERP LN 6.1In ERP LN 6.1, the call-handling functionality is improved by the introduction of the following sessions:

▪ Call List (tsclm1509m000)▪ Calls to be Assigned (tsclm1513m000)

▪ Support Department Call Queue (tsclm1515m000)▪ Support Engineer Call Queue (tsclm1517m000)

Contract coverage at item level

This topic describes the contract coverage at item level functionality in ERP LN 6.1.

Contract coverage at item level in ERP Baan5.0cIn ERP Baan5.0c, service contracts could only be defined for one or more clusters that represented oneor a group of maintainable products.

Contract coverage at item level in ERP LN 6.1In ERP LN 6.1, on special contract configuration lines, you can now specify the items or serialized items,with or without a cluster, for which contract template are defined. However, if required, general coverageis also available for the remaining items of the installed base for which no specific information has beenprovided in the service contract.

In addition to cluster, item, serialized item, and anonymous items, with no cluster information, can alsobe covered under a service contract. With the introduction of defining terms at item level, the conceptof splitting/not splitting terms by cluster has become obsolete. You can only define coverage terms forspecific configuration lines.

To define a contract to cover specific items or serialized items, you can use the following sessions tocreate the contract configuration lines:

▪ Contract Configuration Lines (tsctm1110m300): Use this session manually to create theappropriate configuration lines.

▪ Generate Contract Configuration Lines (tsctm2210m000): Use this session to generate theappropriate configuration lines.


Service

In the Service Contracts (tsctm3100m000) session, on the Specific menu, click Configuration Lines.Next, in the Contract Configuration Lines (tsctm1110m300) session, on the Specific menu, clickGenerate Configuration Lines to start theGenerate Contract Configuration Lines (tsctm2210m000)session.

Customer call dashboard

This topic describes the customer call dashboard functionality in ERP LN 6.1.

Customer call dashboard in ERP Baan5.0cIn ERP Baan5.0c, customer call dashboard functionality did not exists.

Customer call dashboard in ERP LN 6.1In ERP LN 6.1, Customer Call Dashboard (tsclm1509m100) session is used to view, maintain, andcreate call-related data. This dashboard is a useful tool for a support engineer and helps them in gettingan overview of the calling customer. All service-related details are provided through easy lookups. Inaddition, the support engineer can quickly view the financial liability of the customer, the customer levelresponse time, and priority definition.

A number of views are available to show orders specific to the customer such as service orders,maintenance sales orders, work orders, and other registered calls. These views enable you to quicklyscan the various agreements with the customer, such as service contracts, service job quotations, andservice contract quotations. These views also render visibility into the installed base by providing acustomer-specific list of clusters and serialized item structure. In addition, these views also provide aninsight into the sales orders under process for this customer, to keep better track of the possible newinstallations.

Direct call invoicing

This topic describes the direct call invoicing functionality in ERP LN 6.1.

Direct call invoicing in ERP Baan5.0cIn ERP Baan5.0c, the direct call invoicing functionality did not exist.

Direct call invoicing in ERP LN 6.1In ERP LN 6.1, you can use direct call invoicing to invoice a call that is solved directly, without the needto first create a service order. To implement direct call invoicing, open the Call Parameters(tsclm0100m000) session and specify the corresponding settings.

You must set the following parameters in the Invoicing area on theGeneral tab of theCall ManagementParameters (tsclm0100m000) session:

▪ Invoice after Call: Select this check box to enable direct call invoicing.


Service

▪ Time Interval: Select the Invoicing Intervals (tsclm0170m000) session to define a time interval.The main characteristics of the time interval are the lower and upper limits. You use theselimits to determine whether the time spent on a call is invoiced. If the time spent is less thanthe lower limit, no invoice is created. Otherwise, the actual amount of time spent is invoicedwith the upper limit as maximum.

▪ Cost Component: Open theCosts Components (tcmcs0148m000) session, select or definethe appropriate cost component.

▪ Coverage Type: The value in this field indicates to what extent work is covered under warranty,and what part of the activities you can charge. Open the Coverage Types (tsmdm0135m000)session to select the appropriate coverage type.

▪ Path for Labor Rate: Specify up to three levels for the search path used to retrieve the laborrate. Select from the following:▪ Cluster▪ Support engineer▪ Activity Taken▪ Serialized item group▪ Support Department

Failure analysis

Failure analysis in ERP Baan5.0cIn ERP Baan5.0c, failure analysis functionality did not exist.

Failure analysis in ERP LN 6.1In ERP LN 6.1, failure analysis functionality explains about gathering up-to-date data related to confirmedfailures, providing failure reports at right points, the results of a selected analysis, and providing primaryor preliminary causes of failures in various instances. An assumption is made here that the report wouldbe as good as the data captured, so if the data gathered were inaccurate the report on failure analysisalso would be inaccurate.

You can use Service Resolution - Failure Analysis (tsclm3170m000) session to register failure on amaterial line on any of the following order:

▪ Service order – material lines

▪ Maintenance sales order – Part delivery/receipt lines▪ Work order – material resource lines

You can use Service Resolution History - Failure Analysis (tsclm4100m000) session to view total failurehistory in an Organization.

You can use Consolidated Failure Analysis (tsclm4110m000) session to view the failure data of bothactive and history failure analysis data.


Service

Functional element

This topic describes the functional element functionality in ERP LN 6.1.

Functional element in ERP Baan5.0cIn ERP Baan5.0c, functional Element structure functionality did not exist.

Functional element in ERP LN 6.1In ERP LN 6.1, functional items are a group of exchangeable items with identical functions and can beused in item breakdown, physical breakdown and reference activity. A functional element enables youto define, for example, more generalized activities for a non-physical, generic item, rather than for aspecific item. This eliminates the need for multiple, identical reference activities for items that share thesame properties and usage characteristics. As a result, there can be a reference activity, which describesthe removal of a fan instead of the removal of item Fan-54576787. When the reference activity is linkedto a work order, the actual item that is placed in the physical breakdown can be specified.

You can use functional elements to list several exchangeable items for a specific position in the itembreakdown.

Note

Functional elements are defined and maintained in the Functional Elements (tscfg0140m000) session.

Global update of contract prices

This topic describes the global update of contract prices functionality in ERP LN 6.1.

Global update of contract prices in ERP Baan5.0cIn ERP Baan5.0c, functionality for global update of contract prices did not exist.

Global update of contract prices in ERP LN 6.1In ERP LN 6.1, prices of service contracts that are opened for renewal can be updated according touser-definable settings that affect the following amounts:

▪ The sales amounts of the configuration lines related to a contract . For each pricing method,you can define a separate percentage by which the amounts must be updated. For the ItemPricing pricing method, you can also retrieve the latest (changed) prices from the item pricelist.

▪ The coverage amounts of the related coverage terms and cost terms. You can update theamounts by a particular percentage, or retrieve the latest (changed) prices.

To update a service contract’s sales and coverage amounts, in theContract Changes (tsctm3120m000)session, select the appropriate renewal line, with status Open, and on the Specificmenu, click UpdateContract Prices to start the Global Update Contract Prices (tsctm3220m000) session.


Service

On the Sales tab, specify percentages for the various pricing methods. For the Item Pricing pricingmethod, you can also select the Update from Contract Price List update method.

To view the resulting contract prices without actually applying the prices, be sure to select the PrintChanges check box, and leave the Final Prices check box cleared.

On the Coverage tab, you can either specify a percentage for each term type, or, for a number of termtypes, indicate that the latest prices must be retrieved from master data.

Item-specific contract templates

This topic describes the item-specific contract templates functionality in ERP LN 6.1.

Item-specific contract templates in ERP Baan5.0cIn ERP Baan5.0c, contract templates were applicable for specific types of contracts rather than beingapplicable to specific items.

Item-specific contract templates in ERP LN 6.1In ERP LN 6.1, you can define specific terms for an item as a contract template. If a contract quotationor service contract covers these types of items, you can copy terms from the corresponding template.Each item in the contract configuration line can have a unique template.

Item pricing using contract item price lists

This topic describes item pricing by means of the contract item price lists functionality in ERP LN 6.1.

Item pricing using contract item price lists in ERP Baan5.0cIn ERP Baan5.0c, item pricing using contract item price lists functionality did not exist.

Item pricing using contract item price lists in ERP LN 6.1In ERP LN 6.1, to specify recommended prices for items, you can link contract templates to items formore realistic pricing, based on experience. If, on a contract configuration line, the user enters an itemin combination with a contract template which specifies the Item Pricing pricing method, ERP LN retrievesthe recommended sales price from the contract price list defined for that item.

Use the Contract Item Price Lists (tsctm0115m000) session to define one or more recommended salesprices for an item.

Labor rates and skills

Labor rates and skills in ERP Baan5.0cIn ERP Baan5.0c, you can define labor rates, skills and hourly labor types using the following sessionin Master Data Management:


Service

▪ Labor Rates (tsmdm0110m000)▪ Skills (tsmdm1130m000)▪ Hourly labor Types (tsmdm0125m000)

Labor rates and skills in ERP LN 6.1In ERP LN 6.1, labor rates, skills and hourly labor types session are moved to Infor ERP People package.

▪ Skills (tcppl0110m000)▪ Labor Rate Codes (tcppl0190m000)

PCS/Service integration enhancements

This topic describes PCS/Service integration, and its role in Service.

PCS/Service integration in ERP Baan5.0cIn ERP Baan5.0c, PCS/Service integration did not exist.

PCS/Service integration in ERP LN 6.1In ERP LN 6.1, this functionality is used to make handling of customized (or PCS) items more effectiveand flexible. Following are the new enhancements:

▪ Copy PBOM directly into Service serials and PBD

▪ You can use the Create Physical Breakdown Structure (tscfg2210m000) session, to createthe physical breakdown from a Bill of Material. If you create a physical breakdown from aBill of Material, this results in a direct copy of effective items present in the Bill of Material(tibom1110m000) session of Manufacturing to Service. If item service data is not present,ERP LN uses item service defaults maintained for item type and item group to create itemsin ERP LN Service.

▪ Usage of customized items on the service order material

▪ A new field Reference Item Details is added in Service Order Estimated Material Costs(tssoc2120m000) session. The reference item is referred to generate a customized item,by creating a new PCS project for the sold to business partner mentioned on the serviceorder header. You can also link the reference item, as a project part, to an existing PCSproject for the Sold-to BP mentioned on the service order header. The reference item canbelong to PCS project of any business partner.

▪ A new session Generate (Project) Structure for Service Orders (tssoc2275m000) isintroduced in Service Order Estimated Material Costs (tssoc2120m000) session. Inany of the material lines in a service order - if the reference item is filled with the main itemleft blank, it’s not possible to plan or release the order. It is first required to generate projectstructure for items present on all those material lines, which are to be customized orproduced.

▪ Physical Breakdown change report


Service

▪ It is used to present the difference between the configuration structure on a selected datewith respect to the structure on a selected past date. This gives a track of all the changesthat occurred on the Physical Breakdown. Following fields are introduced in Print PhysicalBreakdowns (tscfg2410m000) session.▪ Off Date▪ Compare Date▪ Physical Breakdown Log check box

Physical breakdown structure

This topic is about object relation and physical breakdown structure functionality. Object relation is aERP Baan5.0c term and physical breakdown structure is a ERP LN 6.1 term.

Object relation in ERP Baan5.0cIn ERP Baan5.0c, useObject Relations (tscfg2510m000) session to display the object relations. Theserelated objects form the configuration structure.

Physical breakdown structure in ERP LN 6.1In ERP LN 6.1, the concept of physical breakdown is introduced. Physical breakdown is used to displaythe relation between serialized item. Physical breakdown relates the serialized item with each other(through parent-child relations). You can explode the physical breakdown to display a (multi-level)breakdown structure showing the complete structure of the serialized items within a configuration.

To manage product configurations (breakdown structures) during service and maintenance activities,you can set up a physical breakdown.

In the Service Order Control module, you can handle the service-order activities, to update activephysical breakdowns.

Select the Configuration Status Usage check box in the Configuration Management Parameters(tscfg0100m000) session. You can maintain the physical breakdowns in the Physical Breakdowns(tscfg2110m000) session.

You can create a physical breakdown using any of the following options:

▪ as-built structure▪ item breakdown▪ Sales order line▪ bill of material (BOM)▪ ASCII file▪ project-breakdown structure

Set the top-serialized item to Active to activate the physical breakdown. All the events and changes tothe physical breakdown of an item are automatically logged. Physical breakdown log is used so thatevery change in physical breakdown structure is traceable and formally controlled. The initial physicalbreakdown is stored in the physical breakdown log as well as all modifications identified with the action


Service

taken that have been executed on it. Select the Create Physical Breakdown Log check box inConfiguration Management Parameters (tscfg0100m000) session to create a physical breakdown log.

Pricing and discounts

Pricing and discounts in ERP Baan5.0cIn ERP Baan5.0c, pricing and discounts functionality did not exist.

Pricing and discounts in ERP LN 6.1In ERP LN 6.1, price and discount fetch is based on the pricing parameters and service parametersdefined. For example, Price fetch can be either the first valid one or the lowest price. The discount canbe defined at a number of levels. Parameter can be set to define whether to get the first discount or thebest discount or to accumulate the discount or not apply at all. Default price books can be mentionedto be applicable per package.

Use General Service Parameters (tsmdm0100m000) session to:

▪ Determine whether discounts are fetched from the price book

▪ Select Discount Policy procedure that has to be used for applying the discount percentageor amount on the Service Order Actual Material Cost Lines andMaintenance Sales OrderCoverage lines.

In Service Order Actual Material Costs (tssoc2121m000) session and Coverage Lines (tsmsc1120m000)session aMultilevel Discounts check box is provided to indicate whether there are more than one levelof discounts in Pricing.

Reference activities

This topic describes the reference activities functionality in ERP LN 6.1.

Reference activities in ERP LN 6.1In ERP LN 6.1, reference activities are centralized in the Master Data Management module. A singlerepository for reference activities for depot repair, call management, project, and field service is nowavailable. The new Reference Activities (tsacm1101m000) session is now also available.

The repository of activities is based on a service organization’s experience. These activities are serviceactivities that you can carry out within a given finite time: long enough to act as buckets of planning. Anyactivity can be specific to field service, depot repair, or both. Reference activities are tagged with coveragetypes to provide visibility into the type of coverage that might apply.

A reference activity can also contain details about recommended methods to run, such as duration, orsuggested frequency of execution. This can also suggest whether the activity is recommended forsubcontracting.


Service

You can define the resource requirement lines that might be incurred while carrying out this activity.Subsequently, you can have an overview of the costs that might be incurred while you carry out thisactivity.

RMA and depot repair

This topic describes RMA and depot repair, and their role in Service.

RMA and depot repair in ERP Baan5.0cRMA and Depot Repair did not exist in ERP Baan5.0c.

RMA and depot repair in ERP LN 6.1In ERP LN 6.1, depot repair functionality enables service organizations to track and carry out serviceand maintenance activities in their shops and depots. In ERP LN 6.1, the RMA and Depot repairfunctionality supports the following business flows:

▪ Part maintenance: This procedure handles part repair in a depot.▪ Part loan: This procedure handles temporary loans of items to customers. Temporary loans

of items help prevent delays in the customer’s business process if the original item is damaged.The customer can then use the loaner, or replacement item, until the defective item is repairedat the service provider’s depot.

▪ Part receipt: This procedure handles the receipt of an item into the service provider’s company,which is useful if an item must be sent back to the company, for example, for scrapping.

▪ Part delivery: This procedure handles the delivery of an item to the customer, which is usefulfor service providers, for example, if the providers must sell spares.

To accomplish these procedures, RMA and Depot Repair use the following two modules:

▪ Maintenance Sales Control (MSC): Handles RMA.▪ Work Control System (WCS):Handles the implementation of repair work orders in the depot.

Maintenance Sales Control (MSC):

To register a maintenance sales order, you can either enter the order directly or transfer the orders froma call. Each maintenance sales order can handle a number of part lines.

The following sessions are available as part of the Maintenance Sales Control module:

▪ Maintenance Sales Control Parameters (tsmsc0100m000)▪ Maintenance Sales Orders (tsmsc1100m000)▪ Part Lines (tsmsc1110m000)▪ Coverage Lines (tsmsc1120m000)

Work Order Control (WCS):

In theWork Control System (WCS) module, work order preparation, planning, and execution inmaintenance shop or repair shop is handled. You can use the work control system module for internalmaintenance and for maintenance on business partner-owned parts. For maintenance on business


Service

partner-owned parts, the work control system is fully integrated with the maintenance sales control(MSC) module.

The following sessions are available as part of the Work Order Control module:

▪ Work Order Parameters (tswcs0100m000)▪ Work Orders (tswcs2100m000)▪ Work Order - Lines (tswcs2100m100)▪ Work Order Activities (tswcs2110m000)▪ Cancel Work Orders (tswcs2260m000)▪ Work Order Measurements (tswcs2120m000)

▪ Work Order Material Resources (tswcs4110m000)▪ Work Order Other Resources (tswcs4130m000)

Serialized items in Service

This topic is about object and serialized item functionality. Object is a ERP Baan5.0c term and serializeditem is a ERP LN 6.1 term.

Objects in ERP Baan5.0cIn ERP Baan5.0c, use Objects (tscfg2500m000) session to display the objects in a configurations.

Serialized items in ERP LN 6.1In ERP LN 6.1, serialized item is an item that is uniquely identified by the item code (manufacturer partnumber) in combination with the serial number.

A unique serial number is assigned to every manufactured or purchased item to track the item duringits lifecycle. The serialized item identification consists of two parts namely item code and serial number.In this entity type specific data of serialized items can be defined.

To define a serialized item and its relationships, perform the following steps:

▪ Define the item in the Serialized Items (tscfg2100m000) session. See the Help of the PhysicalBreakdowns (tscfg2110m000) session.

▪ Use the Cluster - Lines (tsbsc1110m000) session to assign the serialized item to a cluster.Clusters are defined in the Clusters (tsbsc1100m000) session.

▪ Define the serialized item's relationships in the Physical Breakdowns (tscfg2110m000)session.

Serialized items dashboard for Service

This topic describes the serialized items dashboard, and its role in Service.

Serialized items dashboard in ERP Baan5.0cIn ERP Baan5.0c, the serialized items dashboard did not exist.


Service

Serialized items dashboard in ERP LN 6.1In ERP LN 6.1, this functionality is used to have a complete visibility into serialized items used acrossERP LN Service module. Visibility into a product life cycle of any serialized item enables you to understandthe behavior and plan for the actions/maintenance.

A Serialized Item Dashboard (tscfg2100m100) session is an overview session that can give a user aquick insight in the status of a certain serialized item. The user does not have to go into the menu's toopen related User Interfaces to see whether data is available. In the dashboard, all sessions related tothe serialized item are visible (buttons) and check boxes indicate if data is available.

Service type and coverage type

This topic describes the service type and coverage type functionality in ERP LN 6.1.

Service type and coverage type in ERP Baan5.0cIn ERP Baan5.0c, the Service Type field in Service Types (tsmdm0130m000) session is used tocontrol service order procedures and to define cost coverage in contracts and warranties.

Service type and coverage type in ERP LN 6.1In ERP LN 6.1, the service type field is now used for service order execution control. At the same time,the coverage type field is introduced in Service Types (tsmdm0130m000) session, to deal with costcoverage control in Service.

In ERP LN 6.1, a new session Coverage Types (tsmdm0135m000) is introduced to define coveragetypes. Coverage types are used as a differentiator for coverage under various agreements, such aswarranties, contracts, or quotations. A coverage type is also used as a differentiator while definingreference activities.

You can use a coverage type to indicate conditions under which coverage can be afforded to thecustomer, under an agreement. By changing the coverage type in cases not applicable when damageoccurs to equipment because of a fault at the customer site, then, simply by changing the coveragetype, you can deny agreement coverage.

Subcontract management

This topic describes subcontract management, and its role in Service.

Subcontract management in ERP Baan5.0cIn ERP Baan5.0c, subcontract management did not exist.

Subcontract management in ERP LN 6.1In ERP LN 6.1, subcontract management enables users to define subcontracting agreements relatedto the service provider’s business partners.


Service

Subcontract agreements can be defined in the following ways:

▪ Manually▪ Generated from a service contract

Subcontract Management consists of following process:

▪ Create Subcontract▪ Maintain Subcontract▪ Archive Subcontract agreement

Create subcontractThis process is used to create subcontract agreement (both header and lines). Subcontract agreementscan be manually created or they can be generated from service contracts. As subcontract agreementinformation is divided into header and lines, subcontract agreement header must be created first withthe details of subcontractor and service level information and then subcontract agreement lines can beappended with the details of the items. You must mention the following in subcontract agreement header:

▪ Buy-from BP with whom the service organization wants to make an agreement.

▪ Any high level agreements made with the subcontractor.▪ The responsible ship-from and pay-to BP.

▪ The cluster on which the service needs to be provided.▪ Sold-to BP and currency details.

Once the header information is created, item details can be added as the lines. In item details section,you can mention the response times expected for each particular item from the subcontractor andfinancial details like total invoice amount and amount paid.

In case, the subcontract agreements are generated from service contract, the item details maintainedin the contract are taken and based on the subcontractor information maintained at the item level or atthe serialized item level, subcontract agreements will be generated. The subcontract agreement and itslines changes to status Free when created / generated.

Use Subcontract Agreement (tssbm1100m000) session to list and maintain subcontract agreements foryour subcontractors.

Maintain subcontractOnce the subcontract agreement is created, you might need to manually change or maintain certainfields like the service contract under which the subcontract agreement is covered or the sold-to BP towhom the subcontract agreement is meant. This process allows you to make such changes on thesubcontract agreement. Apart from this, you can perform various operations on subcontract agreementslike printing, activating, canceling and expiring under specified conditions.

If the subcontract agreement status is Free, then you are allowed to add new lines / delete lines / makeany modifications in the existing lines. If the subcontract agreement status is “Printed”, you can makechanges on the subcontract agreement and lines, you cannot add new lines to the existing subcontractagreement. If new lines need to be added, then the subcontract agreement status must be changed to“Free” and addition of new lines must be handled. When subcontract agreement status is reverted to


Service

“Free”, all its underlying lines, which are in “Printed” status, will change to “Free”. In all the other statuseslike “Active”, “Expired” or “Cancelled”, you are not allowed to make any changes in the subcontractagreement details.

Archive subcontract agreementThis process allows deleting the subcontract agreement and moving it to history. This is possible onlywith subcontract agreement header but not with lines. The lines will be deleted and moved to historyonly when header is deleted. The deleted subcontract agreement can be viewed in history. Subcontractagreements can be deleted when they are in free / ordered / expired / cancelled statuses but they willbe moved to history only when they are in expired / cancelled statuses. This process allows deletion ofsubcontract agreements that are in expired / cancelled status.

Use Subcontract Agreement - History (tssbm8100m000) session to list the subcontract agreements thathave been moved to history.

Transaction logging

This topic describes the improved transaction logging functionality in ERP LN 6.1.

Transaction logging in ERP Baan5.0cIn ERP Baan5.0c, use Call Transaction Log (tsclm8580m000) session to display the call transactionsthat are logged.

You can view details of:

▪ All transactions▪ Transactions due only to status changes▪ Transactions due only to waiting▪ Transfer-related transactions

Transaction logging in ERP LN 6.1In ERP LN 6.1, transaction logging is improved by the introduction of registration of modified fields andcomment text.

Registration of modified fieldsEvery time a field in a call is modified, the previous value and the new value is registered in the transactionlog. To view a call’s transaction log, in the Call (tsclm1100m000) session, click Transaction Log on theSpecific menu, or click Transaction Log to start the Call Transaction Log (tsclm8580m000) session.

Comment textTo add comments to the call, users can now manually log transactions. In this way, any employee canadd information to the call, without the need to change the status of the call. You enter comment text inthe Comment field on the Comment tab of the Call (tsclm1100m000) session.


Service

Modules

Configuration Management (CFG) module - Differences B50c/ERP61

This topic describes the most important differences between the Configuration Management module inERP Baan5.0c and in ERP LN 6.1.


▪ Physical breakdown structureIn ERP LN 6.1, the concept of physical breakdown is introduced. Physical breakdown is usedto display the relation between serialized item. For more information, refer to Physicalbreakdown structure (p. 240) .

▪ Functional elementIn ERP LN 6.1, functional items are a group of exchangeable items with identical functionsand can be used in item breakdown, physical breakdown and reference activity. For moreinformation, refer to Functional element (p. 237) .

▪ Serialized ItemIn ERP LN 6.1, serialized item is an item that is uniquely identified by the item code(manufacturer part number) in combination with the serial number. For more information, referto Serialized items in Service (p. 243) .

▪ Serialized items dashboard for ServiceIn ERP LN 6.1, this functionality is used to have a complete visibility into serialized items usedacross ERP LN Service module. For more information, refer to Serialized items dashboardfor Service (p. 243)

Call Management (CLM) module - Differences B50c/ERP61

This topic describes the most important differences between the Call Management module in ERPBaan5.0c and in ERP LN 6.1.


▪ Customer call dashboardIn ERP LN 6.1,Customer Call Dashboard (tsclm1509m100) session is used to view, maintain,and create call-related data. For more information, refer to Customer call dashboard (p. 235).

▪ Direct call invoicingIn ERP LN 6.1, you can use direct call invoicing to invoice a call that is solved directly, withoutthe need to first create a service order. For more information, refer to Direct call invoicing(p. 235) .

▪ Call blockingIn ERP LN 6.1, call blocking is introduced to the Call Management (CLM) module. For moreinformation, refer to Call blocking (p. 233) .


Service

▪ Call handlingIn ERP LN 6.1, the call-handling functionality is improved by the introduction of the newsessions. For more information, refer to Call handling (p. 233) .

▪ Transaction loggingIn ERP LN 6.1, transaction logging is improved by the introduction of registration of modifiedfields and comment text. For more information, refer to Transaction logging (p. 246) .

Contract Management (CTM) module - Differences B50c/ERP61

This topic describes the most important differences between the Contract Management module in ERPBaan5.0c and in ERP LN 6.1.


▪ Item-specific contract templatesIn ERP LN 6.1, you can define specific terms for an item as a contract template. For moreinformation, refer to Item-specific contract templates (p. 238) .

▪ Contract coverage at item levelIn ERP LN 6.1, on special contract configuration lines, you can now specify the items orserialized items, with or without a cluster, for which contract template are defined. For moreinformation, refer to Contract coverage at item level (p. 234) .

▪ Item pricing using contract item price listsIn ERP LN 6.1, to specify recommended prices for items, you can link contract templates toitems for more realistic pricing, based on experience. For more information, refer to Item pricingusing contract item price lists (p. 238) .

▪ Global update of contract pricesIn ERP LN 6.1, prices of service contracts that are opened for renewal can be updatedaccording to user-definable settings. For more information, refer to Global update of contractprices (p. 237) .

Master Data Management (MDM) module - Differences B50c/ERP61

This topic describes the most important differences between the Master Data Management module inERP Baan5.0c and in ERP LN 6.1.


▪ Labor rates and skillsIn ERP LN 6.1, labor rates, skills and hourly labor types session are moved to Infor ERPPeople package. For more information, refer to Labor rates and skills (p. 238) .

▪ Service Type and Coverage TypeIn ERP LN 6.1, the service type field is now used for service order execution control. At thesame time, the coverage type field is introduced in Service Types (tsmdm0130m000) session,to deal with cost coverage control in Service. For more information, refer to Service type andcoverage type (p. 244) .


Service

▪ Reference activitiesIn ERP LN 6.1, reference activities are centralized in the Master Data Management module.For more information, refer to Reference activities (p. 241) .

RMA & Depot Repair (MSC) module - Differences B50c/ERP61

This topic describes the most important differences between the RMA & Depot Repair module in ERPBaan5.0c and ERP LN 6.1.


▪ RMA & Depot RepairIn ERP LN 6.1, depot repair functionality enables service organizations to track and carry outservice and maintenance activities in their shops and depots. For more information, refer toRMA and depot repair (p. 242) .

Subcontract Management (SBM) module - Differences B50c/ERP61

This topic describes the most important differences between the Subcontract Management module inERP Baan5.0c and ERP LN 6.1.


▪ Subcontract ManagementIn ERP LN 6.1, subcontract management enables users to define subcontracting agreementsrelated to the service provider’s business partners. For more information, refer to Subcontractmanagement (p. 244) .

Service Order Control (SOC) module - Differences B50c/ERP61

This topic describes the most important differences between the Service Order Control module in ERPBaan5.0c and in ERP LN 6.1.


▪ Failure AnalysisIn ERP LN 6.1, failure analysis functionality explains about gathering up-to-date data relatedto confirmed failures, providing failure reports at right points, the results of a selected analysis,and providing primary or preliminary causes of failures in various instances. For moreinformation, refer to Failure analysis (p. 236) .

▪ PCS/Service integration enhancementsIn ERP LN 6.1, this functionality is used to make handling of customized (or PCS) items moreeffective and flexible. For more information, refer to PCS/Service integration enhancements(p. 239) .


Service

▪ Pricing and DiscountsIn ERP LN 6.1, price and discount fetch is based on the pricing parameters and serviceparameters defined. For more information, refer to Pricing and discounts (p. 241) .


Service


Activities

This topic describes the extended activity functionality in ERP LN 6.1.

Work authorization structureIn ERP LN 6.1, the work authorization structure concept is introduced. Work authorization structure isa formal authorization procedure to begin work on a specific activity. The process helps ensure that theauthorized work is performed at the right time and in the proper sequence.

Work authorization status can have the following values:

▪ Free: Work is not authorized for execution.

▪ Released: Work is sanctioned for execution. This status is permitted only for activities undera leading plan and for elements that are part of the leading structure. The parent activity/elementand the activity type cannot be changed.

▪ On Hold: Work is under execution and needs to be suspended due to some constraints. Theparent activity/element and the activity type cannot be changed.

▪ Finished: Work is executed. The parent activity/element and the activity type cannot bechanged.

▪ Closed: Work is completed and all related financial transactions are closed. The parentactivity/element and the activity type cannot be changed.

HoldbackIn ERP LN 6.1, you can use holdback for an activity if the Use Holdback check box is selected in theActivities (tpptc2100s000) session. The holdback amount per project appears in the Holdback(tppin4540m000) session in the Project Invoicing module. The holdback percentage is defined in theProject (tppdm6100s000) session in the Project Definition module.


11Chapter 11Project

SurchargesIn ERP LN 6.1, surcharge on budget, cost, and revenue can be calculated and posted to an activitydefined for a project.

Activity relationshipIn Infor ERP LN 6.1 FP2, you can maintain relationships between activities, between budget lines andbetween an activity and a budget line. The relationships can be transferred to Microsoft Project forschedule development. This functionality enables the user to reuse the activities and their sequencingfor new projects.

You must sequence the activities accurately to provide realistic schedules. An activity relationshipindicates that a particular activity (successor) cannot start or end until another activity (predecessor)starts or ends. You cannot link the same predecessor task twice to the same successor task, and youcannot link the same predecessor task to the same successor task.

A new Activity Relationships (tppss2510m000) session is introduced for this purpose in the ProjectPlanning module.

Combine PRP warehouse orders

This topic describes the combining PRP warehouse orders functionality, which is new in ERP LN 6.1

Combine PRP warehouse orders ERP Baan5.0cIn ERP Baan5.0c, combining PRP warehouse orders functionality did not exist.

Combine PRP warehouse orders ERP LN 6.1In ERP LN 6.1, you can combine PRP warehouse orders (advise orders) in the PSS module in InforERP Project.

Planned PRP warehouse orders generated using the Generate Planned PRP orders (tppss6200m000)session or manually entered using the Planned PRP Warehouse Orders (tppss6515m000) session arefirst confirmed using the Approve Planned PRP Warehouse Orders (tppss6225m000) session. Theseconfirmed PRP warehouse orders are then transferred to Infor ERP Warehousing as actual orders.

Note

You can combine the orders only if the Combine Orders group box in the Transfer Planned PRPWarehouse Orders (tppss6235m00) session is selected.

Contract data

This topic explains the new contract data functionality in ERP LN 6.1.

Contract data in ERP Baan5.0cIn ERP Baan5.0c, the contract data did not exist.


Project

Contract data in ERP LN 6.1In ERP LN 6.1, you can modify contract data in the Advance Payment Requests (tppin4110s000) sessionand the Installments (tppin4151s000) session before the invoicing data is transferred to Infor ERPCentral Invoicing. You can modify the following contract data:

▪ Late Payment Surcharge▪ Payment Method▪ Tax▪ Terms of Payment▪ Tax [Y/N]

Note

This data is defaulted from the Business Partner by Project (tppdm6101s000) session.

Copy activities

This topic explains the new copy activities functionality in ERP LN 6.1.

Copy activities in ERP Baan5.0cIn ERP Baan5.0c, the copy activities functionality did not exist.

Copy activities in ERP LN 6.1In ERP LN 6.1, you can copy activities across plan, from a source structure to a target structure. If thetarget is the same plan you must define the source and the target. If the target is a different plan youdefine the source, select the Copy Across Plan check box in the Copy Activities (tppss2201m000)session and define the target.

You can also copy activities across projects. If the target is a different project, you must select the CopyAcross Project check box in the Copy Activities (tppss2201m000) session and define the target project.

For more information, refer to the Copy Activities (tppss2201m000) session.

Employee data

This topic describes in which packages and modules of ERP LN employee data is defined in ERPBaan5.0c and in ERP LN 6.1.

Employee data in ERP Baan5.0cIn ERP Baan5.0c, employee-related data is set up in Infor ERP Project.

Employee data in ERP LN 6.1In ERP LN 6.1, all employee-related data is now stored in the Master Data Management (MDM) modulein Infor ERP People.


Project

Expense tax

This topic describes the new expense tax functionality in ERP LN 6.1.

Expense tax in ERP Baan5.0cIn ERP Baan5.0c, the expense tax functionality did not exist.

Expense tax in ERP LN 6.1In ERP LN 6.1, the expense tax functionality is introduced. Expense tax is the extra cost on direct deliveryspecified on the project invoice. The purpose of expense tax is to include tax for cost control. The taxamount is part of the project cost and is posted as cost to the project when the invoices are matched.Expense tax is applicable for material, equipment, and subcontracting. For direct delivery, the transactionsare posted separately.

When delivery is made through a project warehouse, the expense tax is included in the valuation priceor fixed price transfer.

To calculate the expense tax of a project, you must select the Expensed Purchase Tax check box inthe Tax Codes by Country (tcmcs0136s000) session.

Hours accounting

This topic describes in which packages and modules hours accounting for Infor ERP Project takesplace in ERP Baan5.0c and in ERP LN 6.1.

Hours accounting for Infor ERP Project in ERP Baan5.0cIn ERP Baan5.0c, hours accounting for Project takes place in the Hours Accounting (HRS) module.

Hours accounting for Infor ERP Project in ERP LN 6.1In ERP LN 6.1, the Hours Accounting (HRS) module does not exist anymore. All hours accountingactivities in ERP LN 6.1 are centralized in Infor ERP People. When the hours are registered in InforERP People, the costs of these hours are automatically transferred to the Project Progress module.

Use the Project Hours (bptmm1111m000) session to register hours spent on a project activity. Usethe Use Assignments (bptmm1204m000) session to copy assignments to hours accounting sessions.You can use assignments to facilitate efficient data entry in the hours accounting sessions.

You can update the tasks of the employees or the assignments using the Update Assignments in HoursAccounting (tpptc2211m000) session in the Project Budget module. The budget lines of Infor ERPProject are sent to Infor ERP People as assignments.

For more information, refer to Assignments (bpmdm0130m000) session.

Independent currency system

This topic explains the independent currency functionality supported by Infor ERP Projects.


Project

Independent currency system in ERP Baan5.0cIn ERP Baan5.0c, Infor ERP Projects does not support the independent currency functionality.

Independent currency system in ERP LN 6.1In ERP LN 6.1, Infor ERP Projects supports the independent currency functionality. Use the RotateCurrency option in the Specific menu to view the amounts in budget lines, cost and revenue lines inany of the currencies.

Note

For more information, refer to Independent multicurrency system

Integration of Project with Service

This topic explains the new functionality of integration of ERP Project with ERP Service in ERP LN 6.1

Integration of Project with Service in ERP Baan5.0cIn ERP Baan5.0c, the integration of ERP Project with ERP Service did not exist.

Integration of Project with Service in ERP LN 6.1In ERP LN 6.1, ERP Project is integrated with ERP Service to handle service requirements of acompleted project and of projects in progress.

Handling service requirements of completed projects involves providing service to a part or the entireproject, as per the contract. This is made possible by transferring the project structure and the materialsconsumed in the project to ERP Service.You can copy the activity structure or the element structureand the material cost lines of the actual consumedmaterial items, to Service so that these items becomepart of the physical breakdown structure. This enables identifying the items that need service andmaintenance.

The project structure can be transferred as the 'as maintained' structure to ERP Service.

You can only copy:

▪ Actual consumed material items stored in Project cost history.

▪ Actual consumed material items for which Service item data is defined.

You cannot copy:

▪ Consumables like oil used for a project.

▪ Actual consumed material items for which Service item data is not defined.

The copying process is handled in ERP Service in the Copy Project Breakdown Structure(tscfg2210m200) session.

To handle service requirements of projects in progress, you can generate service orders for the project,in Infor ERP Project. The cost incurred for the service performed, is transferred from Infor ERP Serviceto Infor ERP Project. To generate service orders, the reference activity from Service is linked to the


Project

activity or element labor budget lines in Projects. When the service order is set to Costed in Infor ERPService, the cost is transferred to Infor ERP Project and is aggregated as labor cost.

The cost is approved, confirmed and transferred to Infor ERP Central Invoicing as service cost. FromCentral Invoicing, the service cost is posted to Infor ERP Financials as service cost.

Integration of Infor ERP Project with Microsoft Project

This topic explains the new functionality of integration of Infor ERP Projectwith Microsoft Project (MSP)in .

Integration of Project with MSP inIn , the integration of Project with MSP did not exist.

Integration of Project with MSP inIn , Infor ERP Project is integrated with Microsoft Project 2002 Standard, Professional and Serverversions to leverage the functionality of scheduling. Schedule development consists of activity definition,activity sequencing and activity duration estimating. Activity definition can be created either in Infor ERPProject or in Microsoft Project and sent to the other system for the next process steps.

It is possible to maintain relationships between activities, between budget lines and between an activityand a budget line and update the activity relationships defined in Project from Microsoft Project andvice-versa. The status of the ownership for the project’s activity and budget line relationships can be setto either MS Project or . The ownership of activity relationships depends on the ownership of activitystructure/budget lines. Following scenarios are possible:

▪ Activity Structure and Budget Line owned by and Activity Relationship owned by :The completeactivity structure and the budget lines, including the activity relationships are maintained inand MS Project is used for resource planning. This option is useful when the activity structureand the budget lines including the relationships are part of the template project. The option isused to create projects from templates.

▪ Activity Structure and Budget Line owned by ERP LN and Activity Relationship ownedby MSP: The complete activity structure, and the budget lines are maintained in and theactivity/budget lines relationship (task dependencies) is maintained in MS Project client sideto use the graphical functionality provided in MS Project. MS Projects checks the circularrelationship (circular relationship is not checked in ). While establishing the connection, thedefault activity relationships, if present, in the , are transferred as default dependencies andMS Project owns the task dependencies. This option is useful to create template projects.

▪ Activity Structure and Budget Line owned by MSP and Activity Relationship owned byMSP: The complete activity structure, the budget lines and task dependencies are maintainedin the MS Project client side in order to use the planning functionality provided by MS Project.While establishing the connection, the ownership is set to MSP and a connection is made toan empty Project plan with no activities. The top summary task in MS Project becomes thetop activity in and the connection node. The structure under the top summary task in MSProject is transferred as the activity structure in . All the budget lines are transferred to . After


Project

the activity structure and the activity budget lines are created, the activity/budget line relationshipis created in from MS Project.

Microsoft project 2002 allows the user to define/save multiple baselines. This functionality is used toprevent overwriting of data in . The user can select the baseline with which the planned date is to beupdated in .

TheMSP-TP integration certifies the working of existing ERP LN 6.1 Project – Microsoft Project integrationsolution with Microsoft Project 2003 on Windows XP environment.

Internal project

This topic explains the new internal project functionality in ERP LN 6.1.

Internal project in ERP Baan5.0cIn ERP Baan5.0c, the internal project functionality did not exist.

Internal project in ERP LN 6.1In ERP LN 6.1, an internal project is defined, planned and executed for internal use only. The internalproject does not have a sold-to-business partner or a sales order and no invoicing takes place for thisproject.

ExampleA training program for the employees is a normal internal project.

For details, refer to the online Help of Project (tppdm6100s000) session.

Invoicing enhancements

This topic describes the new invoicing enhancements in ERP LN 6.1

Unit rate invoicing and progress invoicing in ERP Baan5.0cIn ERP Baan5.0c, you can base the unit rate invoice on the sales price of an element . The amount tobe invoiced equals the sales price of the element multiplied by the physical progress of the element.

In ERP Baan5.0c, the progress invoicing procedure resembles the installment invoicing procedure.The progress invoicing procedure consists of invoicing partial contract amounts at predefined intervals,for example, every four weeks. In this procedure, the installment amount depends on the element'sprogress and the element's sales rates.

Unit rate invoicing and progress invoicing in ERP LN 6.1In ERP LN 6.1, you can base the unit rate invoice on the sales price of an element or an activity. Theamount to be invoiced equals the sales price of the element or the activity multiplied by the physicalprogress of the element or the activity.


Project

For the progress invoicing procedure, the installment amount can be based on the element's or theactivity's progress and the element's or the activity's sales rates.

BillableIn ERP LN 6.1, a new Billable check box is introduced in the Cost Plus Transactions to Be Invoicedsessions to enable you to block certain transactions from being billed/invoiced to the customer.

This check box is enabled for all projects with the Contract Type field in the Project (tppdm6100s000)session set to Cost Plus and all Project Extensions with the Invoice Calculation Method field in theExtension (tpptc0110s000) session set to Actual Costs. By default, this check box is selected.

All cost plus transactions to be invoiced, are maintained in the Project Invoicing (PIN) module. Thetransactions must be set toNon-Billable to effectively block the transactions from being billed or invoiced.

If the Billable check box in the Cost Plus transactions to be invoiced sessions is selected, ERP LN6.1 enables you to approve the transactions for invoicing. If this check box is cleared, ERP does notallow you to approve the transaction for invoicing.

CeilingIn ERP LN 6.1, a new check box Ceiling is introduced in the Business Partner by Project(tppdm6101s000) session and the Extension (tpptc0110s000) session to alert you with respect to themaximum project amount that can be invoiced.

If the Ceiling check box is selected, the amount entered in the Contract Amount field is consideredthe ceiling amount. The total invoiced amount that appears next to the ceiling amount in the BusinessPartner by Project (tppdm6101s000) session and the Extension (tpptc0110s000) session.

For the Unit Rate invoicing method, the amount is updated while you transfer transactions from the PINmodule to Central Invoicing. For the Cost Plus invoicing method, the amount is updated when thetransactions are approved for invoicing.

Note

This check box appears only for projects with invoicing type set to Cost Plus or Unit Rate and the checkbox is available only if the Bus. Partner Cost Plus/Unit Rate check box is selected.

Billing request for extensionIn ERP LN 6.1, you can process a billing request for an extension.

Multiple line selection for approval processIn ERP LN 6.1, you can select multiple cost plus transactions for approval in theCost Plus Transactionsto Be Invoiced sessions by means of the Approve/Unapproved option on the Specific menu. All costplus transactions to be invoiced are maintained in the Project Invoicing (PIN) module.

You can select multiple holdback records for approval in the Holdback (tppin4540m000) session bymeans of the Approve/Unapproved option on the Specific menu. The holdback amount per projectappears in the Holdback (tppin4540m000) session in the Project Invoicing module.


Project

Tax handlingIn ERP LN 6.1, to enable better tax handling, tax details such as tax country, tax ID, tax code, businesspartner tax country, and business partner tax ID are added to the Installments (tppin4151s000) sessionand the Advance Payment Requests (tppin4110s000) session. By default, all the values are displayedfrom the Business Partner by Project (tppdm6101s000) session. You can, however, modify the taxcountry, Tax Code and Business Partner Tax Country fields.

Split advance amountsIn ERP LN 6.1, you can click Split Amount in the Advance Payment Requests (tppin4110s000) sessionto start the Advance - Installment Settlement Mapping (tppin0512m000) session and view the mappingof the installment numbers and the split advance amounts.

PCS item procedure

This topic explains the improved method of handling a PCS item in ERP LN 6.1.

Handling a PCS item in ERP LN 6.1In ERP LN 6.1, following enhancements are made to the PCS item procedure:

▪ Possibility to view the progress of a PCS item from Project (by milestone or across milestones).▪ Option to insert a generic item. A product variant defined in the Product Configurationmodule

in Manufacturing can be inserted on a material budget line. The product variant can becustomized into a PCS item. A PCS item and a generic item can be configured and generateddirectly in Project on a budget line.

For more information, refer to Element Budget (Labor) (tpptc1111s000)/ Activity Budget (Labor)(tpptc2111s000).

Project dashboard

This topic explains the new dashboard functionality in ERP LN 6.1

Dashboard in ERP Baan5.0cIn ERP Baan5.0c, the dashboard functionality does not exist.

Dashboard in ERP LN 6.1In ERP LN 6.1, the new dashboard functionality is aimed at improving the ease of use of the ERPapplication. The dashboard is based on one primary object (for example, an item, business partner,order, project and so on). Relevant details of this object are presented on the dashboard, as also thepossibility to open the sessions in which the relevant information for this/these tasks is stored. Additionally,a user with a certain role and task, can use one session as a starting point from where the user caneasily perform the task.


Project

The dashboard consists of a grid, relevant details of the objects in the grid, and command buttons usedto go to related sessions. The checkboxes in front of the command buttons indicate if there is relevantinformation available when you click the button.

Project Dashboard

For Project, it is a new session Projects Dashboard (tppdm6500m100)wherein the project functionalityis placed together, introducing a quicker and easier way to access multiple sessions. In project drivencompanies, irrespective of the role, all the users access projects for executing their tasks. Typically,different users perform tasks in different phases of the project. The dashboard session has been createdto provide all the users and most importantly the project managers, a complete overview of the differentphases of the project in one single interface.

Based on the user authorizations one, can add / modify / delete / view data in different phases of theproject. The dashboard gives the user with a certain task, a quick overview of the status of project objectswithout having to open all the related sessions.

For more information, refer to Projects Dashboard (tppdm6500m100)

Project estimation

This topic explains the new functionality of Project Estimating module of Infor ERP Project in ERPLN 6.1.

Project estimation in ERP Baan5.0cIn ERP Baan5.0c, project estimating did not exist.

Project estimation in ERP LN 6.1In ERP LN 6.1, the main topics that are addressed in the Project Estimating (EST) module are asfollows:

▪ Cost price estimation▪ Sales price calculation▪ Schedule estimation▪ Estimate analysis▪ Preparing a bid▪ To create an estimate▪ Copying a project▪ To launch an estimate to a budget

Two types of estimate structures are possible; element structure and activity structure.

The user can create an estimate project. For each estimate version, a complete estimate can be simulatedand if the estimate is accepted, a bid can be created from the estimate version. Estimating is oftencontinued after submitting the bid, for example, if the customer asks for changes or more details.

If the customer accepts the bid, the actual project can start. Two scenarios are possible:

▪ Copy estimate project to a new project


Project

▪ Launch the estimate to budget

Copy estimate project to a new project: The estimate project is blocked and the newly copied project(with a recognizable series and number) starts under a contract with the customer. With the LaunchEstimate to Budget (tpest2200m000) session the estimate is defined as the budget for the project. Theestimate project has the status Blocked and can only be used for history data. The status is just adisplay status and not one you can choose.

Launch estimate to budget: After the bid is approved and the contract is signed, you launch the estimatelines to actually start working on the project budget. The estimate becomes the project and is used forall phases of the project life cycle, from Estimating to Invoicing. Costs that are made during the estimatephase can be charged on the project. The current integration betweenProject and the external schedulingpackageMicrosoft Project is used to set the estimate structural elements in time. They can be scheduledand the new dates update estimate lines cost and sales release dates. For cost, the new structuralelement start date releases the costs for an estimate line, and for sales, the finish date sets the expectedsales date.

The Estimating (EST) module relies heavily on the integration with the MS Office suite, especially MSExcel for calculation, and MS Word for bidding text. You can use the Object Data Management (ODM)package to link the documents.

For more information, refer to Integration of Projects with Order Data Management

Note

The integration with microsoft excel is mainly used to update field values such asQuantity, Surcharges,Cost Price, Sales Price and so on, for a range of records; create new estimate lines; draw charts/graphsof the data imported.

The Print Bids (tpest3400m000) session report displays the Rounded Sales Amount as per theGrandTotal Rounding Factor field defined in the Currencies (tcmcs0102m000) session when the GrandTotal Rounding check box is checked in the Implemented Software Components (tccom0100s000)session.

Project specific labor rates

This topic describes in which packages and modules of ERP project labor rates are defined in ERPBaan5.0c and ERP LN 6.1.

Project specific labor rates in ERP Baan5.0cIn ERP Baan5.0c, standard wage rates and project wage rates are defined in Project.

Project specific labor rates in ERP LN 6.1In ERP LN 6.1, the wage rates are termed as labor rates and are not defined in Project. Labor rates aredefined in the new People package.


Project

Project template

This topic explains the new project template functionality introduced in ERP LN 6.1.

Project template in ERP Baan5.0cIn ERP Baan5.0c, the project template functionality did not exist.

Project template in ERP LN 6.1In ERP LN 6.1, you can create a project template. A project template enables you to predefine a set ofproject types for a company. If you select a predefined template during the project definition, a largenumber of fields are filled according to the template definition.

The creation of new projects becomes faster and easier with templates. Companies can reduce costson administration of the project setup with the new template functionality. Templates provide a user-friendlyway to define a project.

ExampleFor example, the required project information to build a new assembly hall can be defined in a template.This template can be used for any assembly hall expansions since most of the required information willbe similar.

You can use the template functionality in the following ways:

Using Create Project from Template (tppdm6200m000) sessionYou can use the Create Project from Template (tppdm6200m000) session to create a project froman existing template.

For details, refer to the online Help of Create Project from Template (tppdm6200m000) session.

Using Project (tppdm6100s000) sessionThe template functionality has been built into the Project (tppdm6100s000) session. You can define aproject as a template. Templates can be created manually or from existing projects in the Projects(tppdm6100s000) session. When a project is created from a template, some or all the data can becopied to the target project. For more information, refer to Copy Projects (tppdm7840m000) session.

Note

TheCopy Projects (tppdm7840m000) session opens asCreate Project from Template session whenyou use theCreate Project fromTemplate option in the specific menu of theProjects (tppdm6500m000)session and opens as Save as Template session when you use the Save as Template option.

For details, refer to the online Help of Copy Projects (tppdm7840m000) session and Project(tppdm6100s000) session.


Project

Project warehouse

This topic describes the extended project warehouse functionality in ERP LN 6.1.

Adjustment order and cycle counting in ERP Baan5.0cIn ERP Baan5.0c, the project warehouse does not support the adjustment order and cycle countingfunctionality.

Adjustment order and cycle counting in ERP LN 6.1In ERP LN 6.1, the project warehouse can use the adjustment order and cycle counting functionality asin a standard warehouse.

In case of an adjustment, you can see the result of the adjustment in the Order Line Balance (Material)(tppss6500m000) session. If a cycle count in Project warehouse determines that less inventory isavailable, a line appears in theOrder Line Balance (Material) (tppss6500m000) session with transactionorigin adjustment/cycle count. This line displays the change in data.

Revenue Recognition (RR) and Cost of Goods Sold (COGS)

This topic explains the extended Revenue Recognition and Cost of Goods Sold functionality in ERP LN6.1.

Revenue Recognition and Cost of Goods Sold in ERP Baan5.0cIn ERP Baan5.0c, revenue recognition and cost of goods sold can be determined at the project level.

Methods to Recognize Revenue:

▪ Based on Actuals▪ Based on Progress

Methods to Determine COGS:

▪ Actual Costs

Revenue Recognition and Cost of Goods Sold in ERP LN 6.1In ERP LN 6.1, the revenue recognition and cost of goods sold functionality has been significantlyextended.

The purpose of recognizing revenue is to calculate revenue and to register the revenue in the projectfinancial data. For long term contracts extending over accounting periods, recognition of revenue ispermitted before the contract is complete. This information is later sent to Baan Finance. For a givencontract, the revenue recognition is the process that leads to the calculation (and subsequent postingto the General Ledger) of the total revenue that the contractor estimates he has ‘earned’, based on theprogress of the contract. This amount is independent of the amounts that have been billed/invoiced tothe customer and does not represent any kind of cash flow.


Project

Cost of Goods Sold (COGS) is the expense a company incurs in order to manufacture, create, or sella product. It includes the purchase price of the raw material as well as the expenses of turning it into aproduct. For a given contract, the cost of goods sold is the amount of money spent in the process ofbuilding a deliverable (for which revenue can be recognized) or the money spent on non-recurringactivities (such as engineering design) that have been completed. The Cost of Goods Sold transactionsare posted to the General Ledger.

Revenue Recognition and Cost of Goods Sold can be determined at the project, extension, elementand activity level depending on the method you select. The usage of element and activity depends onwhether the project is controlled by element or controlled by activity.

Revenue Recognition Limit: You can set a limit on the revenue to be recognized. A maximumpercentage is defined on the project and extension level. The default value is set to 100%. But the valuecan be overwritten. The percentage times the contract amount gives the maximum revenue that can berecognized (until the completion of the project). The revenue recognition limit is valid for all RR methodsexcept the Completed Project method.

For more information, refer to Revenue Recognition (RR) and Cost of Goods Sold (COGS)

Methods to Recognize Revenue:

▪ Completed Project Method▪ Percentage of Completion Method▪ Milestone Method▪ Reimbursement Contract Method▪ Earned Revenue Factor Method▪ Actual Revenue Method

Methods to Determine COGS:

▪ Completed Project Method▪ Profit Percentage method▪ Reimbursement Contract Method

Usability improvements

This topic explains the new usability improvements in ERP LN 6.1.

Usability enhancements in ERP LN 6.1Usability enhancements are essential for the following reasons:

▪ More effective and efficient working▪ Less errors, higher quality▪ Less training required▪ Less support required▪ More user friendly application

Following are the ease-of-use improvements:


Project

▪ Browse filters: These help to display only the valid records, effectively preventing the userfrom selecting a wrong record. Browse filters minimize scrolling, as fewer records are displayed.Data is filtered for this specific purpose.

▪ Dynamic forms: These enable you to configure a screen based on the setting defined elsewhere in the application.The user can filter out irrelevant fields, the fields can be hidden andthe view changed.

▪ Object action model: This enhancement is aimed at presenting alternative ways to perform atask, present more relevant information, offer direct links to information. This results in restrictingthe menu, more specific options to sessions, the movable application toolbar thereby offeringmore user friendly options to the user.

▪ Dynamic menu: The dynamic menu shows objects related to a project. If the user wants toview another project, the user can change the active project in the dynamic menu. From onedynamic menu, the user can open another dynamic menu. You can access the related sessionsfrom the Specific menu of the dynamic menu. The objective of a dynamic menu is to groupactions relevant to the business processes you need, instead of listing all options. For moreinformation, refer to To use a dynamic menu.

▪ Map: A map displays the project in a structure of elements, activities or extensions. You candouble click on the structure node to view the details. A map can be accessed from the menubrowser or from a session. For more information, refer to To use a map.

Modules

Project Estimating (EST) module - Differences ERP61/B50c

This topic describes in brief the new Project Estimating (EST) module in ERP LN 6.1.

In ERP LN 6.1, the user can create an estimate project. For each estimate version, a complete estimatecan be simulated and if the estimate is accepted, a bid can be created from the estimate version.Estimating is often continued after submitting the bid, for example, if the customer asks for changes ormore details. For more information, refer to Project estimation (p. 260)

Hours Accounting (HRS) module - Differences B50c/ERP61

This topic explains how hours accounting in the various packages of ERP Baan5.0c is implemented inInfor ERP People in ERP LN 6.1.

In ERP Baan5.0c, hours accounting for Infor ERP Project takes place in the Hours Accounting (HRS)module.

In ERP LN 6.1, the Hours Accounting (HRS) module does not exist anymore. All hours accountingactivities in ERP LN 6.1 are centralized in Infor ERP People. When the hours are registered in InforERP People, the costs of these hours are automatically transferred to the Project Progress module.

Infor ERP People works with assignment which are defined in the Assignments (bpmdm0130m000)session. You can update assignments using the Update Assignments in Hours Accounting


Project

(tpptc2211m000) session in the Project Budget module. The budget lines of Project are sent to InforERP People. The buget lines are regarded as assignments.

For more information, refer to Hours accounting (p. 254)

Project Data Management module - Differences B50c/ERP61

This topic describes the most important differences between the Project Data Management module inERP Baan5.0c and in ERP LN 6.1.


▪ Project warehouseIn ERP LN 6.1, project warehouses have been introduced. Warehouses have to be set up inInfor ERP Common in the Warehouses (tcmcs0103s000) session, the warehouse type mustbe set to Project. When a particular project is defined, the warehouse can be linked to theproject. For more information, refer to Project warehouse (p. 263) .

▪ Internal projectIn ERP LN 6.1, an internal project is defined, planned and executed for internal use only. Theinternal project does not have a sold-to-business partner or a sales order and no invoicingtakes place for this project. For more information, refer to Internal project (p. 257) .

▪ Project templateIn ERP LN 6.1 the introduction of templates helps speed up the creation of new projects. Theproject template is used in Project by linking it to a user in the User Profiles (tppdm0101s000)session. The template checkbox has been added to the Project (tppdm6100s000), Projects(tppdm6500m000), and Projects Dashboard (tppdm6500m100) session. For more information,refer to Project template (p. 262) .

▪ Usability improvementsIn ERP LN 6.1, the usability enhancements made result in more effective and efficient working,less errors, higher quality, less training requirement and more user friendly application. Formore information, refer to Usability improvements (p. 264) .

▪ Project dashboardIn ERP LN 6.1, the Projects Dashboard (tppdm6500m100) session has been introduced toimprove the ease of use of the ERP application. It is a new session wherein the projectfunctionality is placed together, introducing a quicker and easier way to access multiplesessions. For more information, refer to Project dashboard (p. 259) .

▪ Surcharges on activitiesIn ERP LN 6.1, surcharge on budget, cost and revenue can be calculated and posted to anelement, activity, or a cost component, defined for a project.

▪ Extensions in BudgetIn ERP LN 6.1, the Extensions in Budget check box gets checked in the Project(tppdm6100s000) session if the Use Extension In Budget option in the specific menu of theProject Extensions (tpptc0510m000) session is selected. The cost control settings in theProject - Cost Control Levels (tppdm6102m000) session also change. All the check boxes forthe extension related cost control levels get checked in the session. You can select this optionfor projects with status higher than Free and lesser than Closed.


Project

▪ Number group and seriesIn ERP LN 6.1, the Template Number Group and Series can be selected for the templates inthe User Profiles (tppdm0101s000) session.

▪ View customer/supplier amountsIn ERP LN 6.1, four new fields Paid to Supp., Overdue to Supplier, Received fromCustomer;CustomerOverdue have been added to the Projects Dashboard (tppdm6500m100)session to enable the user to view the amount received/paid, amount overdue from thecustomers or to suppliers at project level. The information is retrieved from the ERP LNFinancials.

▪ Tax handlingIn ERP LN 6.1, to enable better tax handling, a new field BP Tax Country has been addedto the Business Partner by Project (tppdm6101s000) session. The Tax ID and the BusinessPartner Tax ID information is also displayed. The Calculate Tax check box has been removedfrom the Business Partner by Project (tppdm6101s000) session.

Project Invoicing (PIN) module - Differences B50c/ERP61

This topic describes the most important differences between the Project Invoicing (PIN) module inERP Baan5.0c and in ERP LN 6.1.


▪ HoldbackIn ERP LN 6.1, you can use holdback for an activity if theUse Holdback check box is selectedin the Activities (tpptc2100s000) session. The holdback amount per project is displayed in theHoldback (tppin4540m000) session in theProject Invoicingmodule. The Holdback percentageis defined in the Project (tppdm6100s000) session in the Project Definition module.

▪ Unit rate invoicing and progress invoicing for activityIn ERP LN 6.1, you can base the unit rate invoice on the sales price of an activity. For theprogress invoicing procedure, the installment amount can be based on the activity's progressand the activity's sales rates.

▪ Cost plus invoicing enhancementsIn ERP LN 6.1, a new check boxBillable, has been introduced in theCost Plus transactionsto be invoiced sessions to enable you to block certain transactions from being billed/invoicedto the customer. In ERP LN 6.1, a new check boxCeiling has been introduced in the BusinessPartner by Project (tppdm6101s000) session and the Extension (tpptc0110s000) session toalert you with respect to the maximum project amount that can be invoiced.

▪ Independent currency systemIn ERP LN 6.1, the contract with a business partner can be in a currency and exchange ratetype that is different from that of the project. The invoices to a project business partner are inthe contract currency. For more information, refer to Independent currency system (p. 254) .

▪ Split advance amountIn ERP LN 6.1, you can use the Split Amount button in the Advance Payment Requests(tppin4110s000) session to access the Advance - Installment Settlement Mapping


Project

(tppin0512m000) session and view the mapping of the installment numbers and the splitadvance amounts.

▪ Tax handlingIn ERP LN 6.1, to enable better tax handling, tax details such as Tax Country, Tax ID, TaxCode, Business Partner Tax Country and Business Partner Tax ID have been added to theInstallments (tppin4151s000) session and the Advance Payment Requests (tppin4110s000)session. By default, all the values are displayed from the Business Partner by Project(tppdm6101s000) session. You can however modify the tax country, tax code and the BusinessPartner tax country fields.

▪ Billing requestIn ERP LN 6.1, you can process a billing request for an extension.

▪ Multiple line selection for approval processIn ERP LN 6.1, you can select multiple cost plus tansactions for approval in the Cost Plustransactions to be invoiced sessions and you can select multiple holdback records forapproval in the Holdback (tppin4540m000) session.

▪ Invoicing procedureIn ERP LN 6.1, the invoicing functionality of the various ERP packages has been removedand is now centralized in the Sales Invoicingmodule of Infor ERPCentral Invoicing package.

▪ Contract dataIn ERP LN 6.1, you can modify contract data in the Advance Payment Requests(tppin4110s000) session and the Installments (tppin4151s000) session before the invoicingdata is transferred to Infor ERP Central Invoicing. For more information, refer to Contractdata (p. 252)

Project Production Control (PPC) module - Differences B50c/ERP61

This topic describes the most important differences between the Project Production Control modulein ERP Baan5.0c and in ERP LN 6.1.


▪ RR and COGSIn ERP LN 6.1, the revenue recognition and cost of goods sold functionality has beensignificantly extended. Revenue Recognition and Cost of Goods Sold can be determined atthe project, extension, element and activity level depending on the method you select. Theusage of element and activity depends on whether the project is controlled by element orcontrolled by activity. For more information, refer to Revenue Recognition (RR) and Cost ofGoods Sold (COGS) (p. 263) .

▪ Expense taxIn ERP LN 6.1, the expense tax functionality has been introduced. Expense tax is the extracost on direct delivery specified on the project invoice. The purpose of expense tax is to includetax for cost control. For more information, refer to Expense tax (p. 254)


Project

Project Scheduling System (PSS) module - Differences B50c/ERP61

This topic describes the most important differences between the Project Scheduling System modulein ERP Baan5.0c and in ERP LN 6.1.


▪ Activity enhancementsIn ERP LN 6.1, the activity functionality has been extended considerably. For more information,refer to Activities (p. 251) .

▪ Integration with ServiceIn ERP LN 6.1, Infor ERP Project is integrated with Infor ERP Service to handle servicerequirements of a completed project and of projects in progress, Infor ERP Project is integratedwith Infor ERP Service. For more information, refer to Integration of Project with Service(p. 255) .

▪ Copy activitiesIn ERP LN 6.1, you can copy activities across plan, from a source structure to a target structure.For more information, refer to Copy activities (p. 253)

Project Technical Calculation (PTC) module - Differences B50c/ERP61

This topic describes the most important difference between the Project Technical Calculationmodulein ERP Baan5.0c and in ERP LN 6.1.


▪ PCS item procedureIn ERP LN 6.1, the procedure to handle customized manufactured items (PCS items) withinProject, has been further enhanced. For more information, refer to PCS item procedure (p. 259).


Project


Project


Handling units

This topic describes the handling units functionality in ERP LN 6.1.

Handling units in ERP Baan5.0cHandling units functionality did not exist in ERP Baan5.0c.

Handling units in ERP LN 6.1In ERP LN 6.1, handling unit functionality is introduced. A handling unit is a uniquely identified physicalunit that consists of packaging and contents. A handling unit can contain items registered in Infor ERPWarehouse Management and can also contain other handling units. A handling unit is a single entityused to process goods in the warehouse.

The handling unit functionality enables the user to receive, store, and issue goods in an automatedmanner. To implement handling units functionality in Quality Management, the items inWarehouseManagement System are labeled with handling unit. Whenever an inspection order is generated for aparticular item, the handling unit labeled with that item must be stored in quality management system.When the inspection order is processed and the results are updated in warehouse management systemfor that item, the handling unit must be sent back to the Warehouse Management System to update thecorrect packing structure.

To implement this functionality in Quality Management, a Handling unit field is added in the followingtwo sessions:

▪ Standard Orders - by Origin (qmptc1120m000)

▪ Storage Inspection - Inventory (qmptc2130m000)


12Chapter 12Quality Management

Modules

Product Testing and Control (PTC) module - Differences B50c/ERP61

This topic describes the most important difference between the Product Testing and Control (PTC)module in ERP Baan5.0c and ERP LN 6.1.

New and Changed functionality

Handling Units

▪ In ERP LN 6.1, a handling unit is a uniquely identified physical unit that consists of packagingand contents. A handling unit can contain items registered in Warehouse Management andcan also contain other handling units. For more information, refer to Handling units (p. 271) .


Quality Management


Application data locks

This topic describes application data locks and their role in Object Data Management.

Application data locks in ERP Baan5.0cApplication data locks did not exist in ERP Baan5.0c.

Application data locks in ERP LN 6.1In ERP LN 6.1, application data locks functionality is used to clear the application data that has beenlocked by the system for any life cycle problem or network problems. You can use the locking mechanismto help the life cycle mechanism for the ODM Objects to run more smoothly by removing the data locksfor the respective users.

During the life cycle of an object, the concurrent changes made to the object status are stored in thedata locks table. If two or more users try to change an objects status, the data locking mechanism takesover and stops one of the users from carrying out the process.

There can be a situation in which the system can fail during the life cycle mechanism. In this type ofscenario, all the data of the object and their corresponding statuses that is stored in the data locks tablecan become redundant. This type of data must be removed from the system so that the life cycleoperations on the objects can be carried out smoothly. Use the Remove Application Data Locks(dmcom0223m000) session to remove redundant and problematic data.

Archive files

This topic describes the files archiving functionality in ERP LN 6.1.

Archive files in ERP Baan5.0cThe files archiving functionality did not exist in ERP Baan5.0c.


13Chapter 13Object Data Management

Archive files in ERP LN 6.1The files archiving functionality is introduced in ERP LN 6.1 to archive the vaulted files from one vaultarea to another vault areas based on specified range of dates.

An authorized user can archive all the files in a vault area or the files created in a specified time range.

Delete files in withdraw document revision mode

This topic describes the delete files functionality when the document revision is withdrawn in ERP LN6.1.

Delete files in withdraw document revision mode in ERP Baan5.0cIn ERP Baan5.0c, the delete files option in withdraw document revision mode did not exist.

Delete files in withdraw document revision mode in ERP LN 6.1In ERP LN 6.1, the files are attached to the document revision and this document revision is subjectedto life cycle.

Attached files are stored in the work area and moved to the defined vault area when the linked documentrevision is submitted or released.

After the document revision is released, the document can be withdrawn. Because the withdrawndocument revision can no longer be used, the user can keep the related files either in the vault or workarea or delete the files. Deleting the unwanted files automatically enables users to take the leverage onthe storage of the system.

If the document has more than one revision, and if those revisions have versions of the file differentfrom the original file version in either the work area or the vault area, the user can remove these files.If other revisions of the document are linked to the same version of the file, you cannot delete this typeof file.

Dynamic host

This topic describes the dynamic host functionality in ERP LN 6.1.

Dynamic host in ERP Baan5.0cIn ERP Baan5.0c, when you create a new area, you must specify the host, the area type, such as workor vault and the full local path to the area. You can also use the browser to specify the path directory orselect the required directory.

Dynamic host in ERP LN 6.1In ERP LN 6.1, you are not required to specify the computer name and IP address while you specifythe area.


Object Data Management

In case of users whose IP address or host name continues to change every time, the host details aredynamically retrieved at runtime.

Note

If you select the Dynamic Host check box in the Areas (dmdoc5120m000) session, ERP LN 6.1automatically picks the IP address of the host at runtime.

Folder life cycle

This topic describes the folder life cycle functionality in ERP LN 6.1.

Folder life cycle in ERP Baan5.0cIn ERP Baan5.0c, you can create a folder as an independent entity. When a folder is created, it visibleand accessible across the system. As a result, the authorization to amend the folder is determinedaccording to the folder's status and the rights assigned by the user who created the folder.

Folder life cycle in ERP LN 6.1The folder life cycle functionality is extended in ERP LN 6.1.

If you create a new folder, the folder receives the Design/Created status and you can change thecontents of the folder. If the folder is in Design/Created status, you can use the content profile to placethe ERP objects defined in ODM in the folder. After the initial design stage, you must lock the folder andthe folder status changes to Locked. After the folder is locked, you can no longer modify the folder'scontents and properties. To change the properties or content of a folder, you must unlock the folder andthe folder's status changes to Design/Created.

The life cycle of folder can be illustrated as follows:

▪ Design/Created --> Lock --> Unlock --> Approve --> Revise --> Design/Created.

For more information, refer to Folders (dmfmg0522m000) session.

Link query condition to previous run

This topic describes the link query condition to previous run functionality in ERP LN 6.1.

Link query condition to previous run in ERP Baan5.0cThe link query condition to previous run functionality did not exist in ERP Baan5.0c.

Link query condition to previous run in ERP LN 6.1In ERP LN 6.1, if the user wants to view the query condition for a query from the previous runs session,the results reflect the state of the conditions existing during that time.

ERP LN 6.1 assumes that the same query ran on previous occasions with different conditions. As aresult, the user can view the query condition based on the previous execution’s result sets.



Mail option for folder

This topic describes the e-mail option for folder in ERP LN 6.1.

Mail option for folder in ERP Baan5.0cIn ERP Baan5.0c, the e-mail option for folder did not exist.

Mail option for folder in ERP LN 6.1The e-mail option for folder is introduced in ERP LN 6.1. Using this functionality, you can send thecontents of the folder by e-mail. The e-mail functionality of the folder is used for the following:

▪ Folders can contain various objects, such as changes and document revisions. For personalfolder, the owner or creator of the folder can only mail the contents of the folder and the mailconsists the shortcut to this folder. The user at the receiver end can click the shortcut to viewdirectly the folders session with relevant data.

▪ In case of a shared folder, any user can mail the contents of the folder.

Parallel development

This topic describes the parallel development functionality in ERP LN 6.1.

Parallel development in ERP Baan5.0cIn ERP Baan5.0c, the parallel development functionality allows the user to revise the released documentrevision more than once.

Parallel development in ERP LN 6.1In ERP LN 6.1, the parallel development functionality has been extended. Parallel development allowsmultiple users to propose multiple changes on the same date.

Parallel development operates in the following way:

▪ More than one revision with status In-Design can exist in parallel.

▪ When a new revision is created, by revising released revision, all the other users who createdthe new revision are notified about the additional revision by e-mail.

▪ If two new revisions exist, such as released and submitted are derived from the same releaseddocument revision then the user is asked to merge the changes manually with the alreadyreleased document revision.

▪ The user also be asked to perform the submit operation or can directly submit the revisionwithout merging the changes.

▪ Only one released document revision can exist at any one time. If any approved documentrevision is released, and if any released document revision already exists, the releaseddocument revision expires.



Query filter

This topic describes the query filter functionality in ERP LN 6.1.

Query filter in ERP Baan5.0cThe query filter functionality did not exist in ERP Baan5.0c.

Query filter in ERP LN 6.1In ERP LN 6.1, an option is provided to select a query as part of the query filter mechanism. On theSpecific menu, click Filter -> Query Filter to start the Query (dmqry0501m000) session. The filter optionhas two sub-options: Query Filter and Undo Query Filter.

Note

In all the important ODM sessions, the Specific menu includes the Query Filter and Undo Query Filtercommands, which enable you to filter data according to the selected query and the previous run of thequery.

Related objects

This topic describes related objects functionality and the role of related objects in Object DataManagement.

Related objects in ERP Baan5.0cRelated objects functionality did not exist in ERP Baan5.0c, .

Related objects in ERP LN 6.1In ERP LN 6.1, you can use the Related Objects (dmsys1113m000) session to view the documentrevision of the related objects, along with the document revisions of the main object.

Related objects are objects related to the main object in a functional flow.

ExampleA BOM is a main object and an item is a related object.

Related vault areas

This topic describes the related vault areas functionality in ERP LN 6.1.

Related vault areas in ERP Baan5.0cIn ERP Baan5.0c, the related vault areas functionality did not exist.



Related vault areas in ERP LN 6.1In ERP LN 6.1, multiple vault areas which are known as primary vault areas can be linked to a library.Secondary/related vault areas can be linked to all primary vault areas.

Relative change order

This topic describes the relative change order functionality in ERP LN 6.1.

Relative change order in ERP Baan5.0cIn ERP Baan5.0c, the relative change order functionality did not exist.

Relative change order in ERP LN 6.1In ERP LN 6.1, when a change is approved and if that change proposal has a relative change order,the triggering of relative change orders is based on the main change order date.

The user can specify the number of days in the duration field. The triggering of relative change orderdepends on the duration period.

Note

The RCO depends on the base change order date in addition to the duration specified by the user. Thisdate is used to make an ERP entity effective or expired. The ERP entity must be logically dependenton the ERP entity linked to the base change order. Whenever a change is made in the base changeorder date, the RCO date is also updated.

Reviewers mechanism

This topic describes the reviewers mechanism functionality in ERP LN 6.1.

Reviewers mechanism in ERP Baan5.0cThe reviewers mechanism functionality did not exist in ERP Baan5.0c.

Reviewers mechanism in ERP LN 6.1In ERP LN 6.1, the reviewers are defined for a committee. Reviewers provide the recommendations onthe proposal of a change for change management. Similarly, the reviewers provide the recommendationsabout the document approval for document management. The reviewer can also use either Approve orReject options to provide the recommendations.

You can add or select the required reviewers of the defined committee for each change or for eachdocument, accordingly. When the change or document is submitted for review, the reviewers are eligibleto provide the recommendations.



The reviewers mechanism is of two types:

▪ Fixed Reviewer mechanism: The review process is carried out in a sequential and timelymanner

▪ Normal Reviewermechanism: The review process is not carried out according to a sequence.

Features of fixed reviewer mechanism in ERP LN 6.1The features of fixed reviewer mechanism are:

▪ In fixed reviewer mechanism, the reviewers provide recommendations in a predefinedsequence. The recommendations are sent to the person next in sequence.

▪ An e-mail option is provided to send the recommendations.

▪ The chairperson can approve or reject the change without any recommendations from thereviewers.

Features of normal reviewer mechanism in ERP LN 6.1The features of normal reviewer mechanism are:

▪ The request to review a proposal is sent by e-mail to the chairperson and reviewers of acommittee

▪ The chairperson can approve or reject the proposal of a change only after all the reviewersprovide their respective recommendations

▪ E-mail message reminder

▪ Parallel review: A reviewer provides recommendations to all other reviewers simultaneouslyand no specific sequence is followed.

Note

The enhancement for reviewersmechanism is applicable for both the ChangeManagement andDocumentManagement modules.

Revise change

This topic describes the revise change functionality in ERP LN 6.1.

Revise change in ERP Baan5.0cIn ERP Baan5.0c, the revise change functionality did not exist.

Revise change in ERP LN 6.1In ERP LN 6.1, the revise action revises the approved changes by rejecting the approved proposal. Italso creates a new proposal with copying links as an option.

Revise action allows you to update the change order date by re stamping on the linked entity that islinked to a change proposal.



Rules and attributes

This topic describes rules and attributes, and their role in Object Data Management.

Rules and attributes in ERP Baan5.0cIn ERP Baan5.0c, rules and attributes did not exist.

Rules and attributes in ERP LN 6.1In ERP LN 6.1, rules and attributes are used to define rules for the instances of an object. The ruletriggers the events for the set of entities that are retrieved from the rule. Each of the events that aretriggered can in turn trigger other dependent events.

The attributes have the following features:

▪ Attributes are used in rules to pick up the specific affected objects.

▪ Attributes provide the flexibility to assign additional properties to objects.

▪ ERP LN 6.1 generates the attribute ID automatically. For this to happen, the user must definea mask for the attribute.

The following sessions are available as part of the Rules and Attributes Business Object:

▪ Attributes (dmcom2100m000)▪ Link Attribute Setup (dmcom2110m000)

▪ Link Attributes and Properties (dmcom2120m000)▪ Rules (dmcom2170m000)

Selection of vault areas

This topic describes the vault area selection functionality in ERP LN 6.1.

Selecting vault areas in ERP Baan5.0cThe vault areas selection functionality did not exist in ERP Baan5.0c.

Selecting vault areas in ERP LN 6.1In ERP LN 6.1, to assign vault areas to document libraries, you must define one or more vault areas foreach library in the Library Contents session. These vault areas are the primary vault areas. The usercan select the option of primary vault area when the document is submitted for review or released incase of a light document.

Multiple secondary/related vault areas can be associated with each of these primary vault areas. Filesattached to documents in the library will be moved to this primary vault area when the document revisionis submitted or released in case of quick approval mechanism.



Timeframe for reviewers

This topic describes the time frame for reviewers functionality in ERP LN 6.1.

Time frame for reviewers in ERP Baan5.0cIn ERP Baan5.0c, the time frame for reviewers functionality did not exist.

Time frame for reviewers in ERP LN 6.1In ERP LN 6.1, the time frame must be set in terms of date and time.

If the user views the reviewers from the Document Revisions (dmdoc1520m000) session or changessession, the related document or change specific reviewers session starts and the Time Frame field isadded in this session. After the chairperson gives the final recommendations, reviewers can no longergive recommendations. After the change or document revision is approved, the time frame cannot beset and this field must be disabled.

The basic features include the following:

▪ The committee chairperson must be able to set a time frame for reviewers.

▪ The due date of the first reviewer becomes the start date for the next reviewer.

▪ The time frame must be applicable for fixed reviewers mechanism only. The chairperson ofthe committee must have the privilege to change the time frame for any reviewers at any pointuntil the reviewer gives the recommendations.

Note

The time frame for reviewers functionality is applicable for both the ChangeManagement and DocumentManagement module.

Modules

Change Management (CHM) module - Differences B50c/ERP61

This topic describes the most important difference between the Change Management (CHM) modulein ERP Baan5.0c and in ERP LN 6.1.


Revise Change

▪ In ERP LN 6.1, the revise action revises the approved changes by rejecting the approvedproposal. For more information, refer to Revise change (p. 279) .

Relative Change Order

▪ In ERP LN 6.1, when a change is approved and if that change proposal has a relative changeorder, the triggering of relative change orders is based on the main change order date. Formore information, refer to Relative change order (p. 278) .



Reviewers Mechanism

▪ In ERP LN 6.1, the reviewers are defined for a committee. Reviewers provide therecommendations on the proposal of a change for changemanagement. For more information,refer to Reviewers mechanism (p. 278) .


▪ In ERP LN 6.1, the time frame must be set in terms of date and time. For more information,refer to Timeframe for reviewers (p. 281) .

Common (COM) module -Differences B50c/ERP61

This topic describes the most important differences between the common module in ERP Baan5.0c andERP LN 6.1.


Rules and Attributes

▪ In ERP LN 6.1, rules and attributes are used to define rules for the instances of an Object.For more information, refer to Rules and attributes (p. 280) .

Application Data Locks

▪ In ERP LN 6.1, application data locks functionality is used to clear the application data thathas been locked by the system for any life cycle problem or network problems. For moreinformation, refer to Application data locks (p. 273) .

Document Management (DM)module - Differences B50c/ERP61

This topic describes the most important difference between the Document Management (DM) modulein ERP Baan5.0c and in ERP LN 6.1.


Reviewers Mechanism

▪ In ERP LN 6.1, the reviewers are defined for a committee. Reviewers provide therecommendations on the proposal of a change for changemanagement. For more information,refer to Reviewers mechanism (p. 278) .


▪ In ERP LN 6.1, the time frame must be set in terms of date and time. For more information,refer to Timeframe for reviewers Timeframe for reviewers (p. 281) .

Selection of Vault Areas

▪ In ERP LN 6.1, to assign vault areas to document libraries, you must define one or more vaultareas for each library in the Library Contents session. For more information, refer to Selectionof vault areas (p. 280) .



Related Vault Areas

▪ In ERP LN 6.1, the secondary/related vault areas can be linked to all primary vault areas. Formore information, refer to Related vault areas (p. 277) .

Parallel Development

▪ In ERP LN 6.1, the parallel development allows multiple users to propose multiple changeson the same date. For more information, refer to Parallel development (p. 276) .

Archive Files

▪ The files archiving functionality is introduced in ERP LN 6.1 to archive the vaulted files fromone vault area to another vault area based on specified range of dates. For more information,refer to Archive files (p. 273) .

Dynamic Host

▪ In ERP LN 6.1, you are not required to specify the computer name and IP address while youspecify the area. For more information, refer to Dynamic host (p. 274) .

Delete files in withdraw document revision mode

▪ In ERP LN 6.1, the files are attached to the document revision and this document revision issubjected to life cycle. For more information, refer toDelete files in withdraw document revisionmode (p. 274) .

Folder Management (FMG) module - Differences B50c/ERP61

This topic describes the most important difference between the Folder Management (FMG) module inERP Baan5.0c and in ERP LN 6.1.


Folder life cycle

▪ In ERP LN 6.1, the folder life cycle functionality has been extended form ERP Baan5.0c. Formore information, refer to Folder life cycle (p. 275) .

Mail option for Folder

▪ In ERP LN 6.1, the e-mail option for folder has been introduced. Using this functionality, youcan send the contents of the folder by e-mail. For more information, refer to Mail option forfolder (p. 276) .

Queries and Reports (QRY) module - Differences B50c/ERP61

This topic describes the most important difference between the Queries and Reports (QRY) module inERP Baan5.0c and in ERP LN 6.1.




Link query condition to Previous Run

▪ In ERP LN 6.1, if the user wants to view the query condition for a query from the previous runssession, the results reflect the state of the conditions existing during that time. For moreinformation, refer to Link query condition to previous run (p. 275) .

Query Filter

▪ In ERP LN 6.1, an option is provided to select a query as part of the Query Filter mechanism.For more information, refer to Query filter (p. 277) .

System defined parameters in Query Conditions

▪ In ERP LN 6.1, the user is allowed to specify conditions based on system variables like DATE$,TIME$, and LOGNAME$ . For more information, refer to Query Conditions (dmqry0502m000).

ODM Configuration (SYS) module - Differences B50c/ERP61

This topic describes the most important differences between the configuration module in ERP Baan5.0cand ERP LN 6.1.


Related Objects

▪ In ERP LN 6.1, a related object is related to the main object in a functional flow and definedin Infor ERP ODM along with the main object. For more information, refer to Related objects(p. 277) .



,,, 247, 249

AbsenceDifferences B50c/ERP61, 200

Activity enhancementsDifferences B50c/ERP61, 251

Add and explode phantoms in a productionorder

Differences B50c/ERP61, 187Adjustments and cycle counting

differences B50c/ERP61, 209Aggregated cost components

Differences B50c/ERP61, 188Aggregation

differences B50c/ERP61, 103Allow multiple sources per requirement

Differences B50c/ERP61, 104Alternative items

Differences B50c/ERP61, 123Alternative material and use-up of oldrevisions

differences B50c/ERP61, 119Alternative material

Differences B50c/ERP61, 187Application data locks, DifferencesB50c/ERP61

Differences B50c/ERP61, Application datalocks, 273

Archive files, Differences B50c/ERP61, 273Available to promise (ATP)

Differences B50c/ERP61, 123B50c/ERP61

bank charges, 49daily balances, 55Dimension accounting, 55GL codes, 57, 60handling units, 211Journal books, 66

open entry enquiries, 72Payment slips, 73pay-to business partner statistics, 74period handling for integration transactions,74purchase invoice matching, 76remap integration transactions, 78

Back ordersDifferences B50c/ERP61, 142

Bill of Material (BOM) moduleDifferences B50c/ERP61, 202

Blockingdifferences B50c/ERP61, 210

Boundaries on supply sourcesDifferences B50c/ERP61, 104

Business partner searchDifferences B50c/ERP61, 124

Call blockingDifferences B50c/ERP61, 233

Call handlingDifferences B50c/ERP61, 233

Call Management (CLM) moduleDifferences B50c/ERP61, 247

Cancel sales ordersDifferences B50c/ERP61, 125

Capable to promise (CTP)Differences B50c/ERP61, 123

Capacity and component CTPdifferences B50c/ERP61, 105

Change Management (CHM) module ,Differences B50c/ERP61

Differences B50c/ERP61, ChangeManagement (CHM) module, 281

COLTDifferences B50c/ERP61, 107

Combine PRP warehouse ordersDifferences B50c/ERP61, 252

Commission and rebate currencies

Index

Differences B50c/ERP61, 126Commission Control System (CMS) module

Differences B50c/ERP61, 165Common (COM) module, DifferencesB50c/ERP61

Differences B50c/ERP61, Common (COM)module, 282

Company numberdifferences B50c/ERP61, 106

Configuration (SYS) module, DifferencesB50c/ERP61

Differences B50c/ERP61, Configuration (SYS)module, 284

Configuration Management (CFG) moduleDifferences B50c/ERP61, 247

Configured itemsDifferences B50c/ERP61, 128

Contract coverage at item levelDifferences B50c/ERP61, 234

Contract dataDifferences B50c/ERP61, 252

Contract Management (CTM) moduleDifferences B50c/ERP61, 248

Copy activitiesDifferences B50c/ERP61, 253

Cost Accounting (CPR) moduleDifferences B50c/ERP61, 203

Cost componentsDifferences B50c/ERP61, 188

Costing work centerDifferences B50c/ERP61, 188

Cross-dockingdifferences B50c/ERP61, 210

Cumulative Order Lead TimeDifferences B50c/ERP61, 107

Customer call dashboard,Differences B50c/ERP61, 235

Cycle timeDifferences B50c/ERP61, 193

Cyclic Planning (CLP)differences B50c/ERP61, 120

Delete files in withdrawal document revisionmode , Differences B50c/ERP61, 274Delivery notes

differences B50c/ERP61, 211Differences B50c/ERP61, 128

Delivery typesDifferences B50c/ERP61, 129

Detailed cost componentsDifferences B50c/ERP61, 188

Differences B50c/ERP61, Archive files, 273Differences B50c/ERP61, Delete files inwithdrawal document revision mode, 274Differences B50c/ERP61, Dynamic host, 274Differences B50c/ERP61, Folder life cycle, 275Differences B50c/ERP61, Handling units, 271DifferencesB50c/ERP61, Link query conditionto previous run, 275Differences B50c/ERP61, Mail option forfolder, 276Differences B50c/ERP61, Paralleldevelopment, 276Differences B50c/ERP61, Query filter, 277Differences B50c/ERP61, Related vault areas,277Differences B50c/ERP61, Relative changeorder, 278Differences B50c/ERP61, Reviewersmechanism, 278Differences B50c/ERP61, Revise change, 279Differences B50c/ERP61, Selection of vaultareas, 280Differences B50c/ERP61,

Serialized items in Service, 243Differences B50c/ERP61, Timeframe forreviewers, 281Differences B50c/ERP61

Absence, 200Accounts Payable (ACP), 81Accounts Receivable (ACR), 84Activity enhancements, 251Add and explode phantoms in a productionorder, 187adjustments and cycle counting, 209Aggregated cost components, 188aggregation, 103Allow multiple sources per requirement, 104Alternative items, 123Alternative items for sold-to businesspartners, 20Alternative manufacturers, 19Alternative material, 187alternative material and use-up of oldrevisions, 119Automatic direct debit procedure, 49Available to promise (ATP), 123

Back orders, 142Bank master data, 50Belgian localizations, 50Billing request composing criteria, 179Bill of Material (BOM) module, 202blocking, 210Boundaries on supply sources, 104Business partner search, 124Call blocking, 233Call handling, 233Call Management (CLM) module, 247Cancel sales orders, 125Capable to promise (CTP), 123capacity and component CTP, 105Cash application, 52cash flow statements, 53Cash Management (CMG), 87Central Calendar Management (CCP), 36Combine PRP warehouse orders, 252Commission and rebate currencies, 126Commission Control System (CMS) module,165Company data, 20company number, 106Configuration Management (CFG) module,247Configured items, 128consumption tax, 53Contract coverage at item level, 234Contract data, 252Contract Management (CTM) module, 248Copy activities, 253Cost Accounting (CAT), 91Cost Accounting (CPR) module, 203Cost components, 188Costing work center, 188cross-docking, 210Cumulative Order Lead Time (COLT), 107Currency differences, 54Customer call dashboard, 235Cycle time, 193Cyclic Planning (CLP), 120Date effective item type, 21Date-effective parameters, 22Date-effectivity on item type, 107delivery notes, 211Delivery notes, 128Delivery types, 129

Detailed cost components, 188Direct call invoicing, 235direct material supply, 211disaggregation, 103distribution planning, 108Draft invoices in logistic packages, 180drawing locations, 189drawing sizes, 189ECO approval procedure, 189EDM approval procedure in ODM, 189Effectivity units, 131Employee data, 253employee expenses, 56Employees, 23Engineering Change Orders (ECOs), 189Engineering Data Management (EDM)module, 204Enterprise Modeling Management (EMM), 38Entity - entity relationships, 24environmental compliance, 25Equate balance of receipts with inventorylevel, 131Expense tax, 254Factoring, 56, 61Failure analysis, 236Financial Budget System (FBS), 94Financial Integrations (FIN), 38Financial Statements (FST), 95Fixed Assets Management, 92fixed delivery moments, 109Freight Management, 135, 136Freight Management integration, 58Freight Management- overview, 231Functional element, 237GBF, 190General Data (COM), 39General Ledger (GLD), 95Generic BOM, 191Generic Browser Framework (GBF), 190Generic routing, 191German localizations, 59Global update of contract prices, 237Grand total rounding, 26Graphical planning board in SFC (Webtop),192Horizon checking, 107Hours accounting, 193, 254Hours Accounting (HRA) module, 205

Indirect task, 200inspections, 215Integration of Infor ERP Project with MicrosoftProject, 256Integration of Project with Service, 255integration with Freight Management, 212integration with Service, 215Intercompany settlement, 62Interim Revenue reconciliation, 64Internal project, 257Inventory Analysis (INA) module, 224Inventory Handling (INH) module, 225Inventory Planning (INP) module, 227Inventory Reporting (INR) module, 228Invoicing commissions and rebates, 132Invoicing enhancements, 257Item Base Data (IBD), 39Item pricing using contract item price lists, 238Item Purchase Data (IPU) module, 166Item Sales Data (ISA) module, 167Item-specific contract templates, 238Japanese bank file layout, 66Labels, 198Labor rates and skills, 238Lead time elements, 193ledger history, 67line supply, 216List groups, 137loading list, 217Localizations, 67Lot by unit, 194Lot control, 27Lot Control (LTC) module, 228lots (not in inventory), 217Lots and serials, 138Lower cost or market value, 194Lower cost or market value method, 69Machine utilization chart, 194Mass BOM Changes (MBCs), 189Master Data Management (MDM) module,248Master planning, 109, 110Material-Routing Relationships, 110Micro routing, 195monthly billing invoice, 70Move time, 193Multicompany purchase invoice matching, 70multicompany warehouse transfers, 218

Multiple control accounts, 71multisite planning, 108Non-direct deliveries, 143Offsetting logic in master-based planning, 110Operation overlap, 195order cancellation, 219order grouping, 111, 218Order groups, SFC, 196order pegging, 112Order pegging in Manufacturing, 195order planning, 112order processing, 224Order units, 140Over deliveries, 138Overlap, 195Parameter wizard, 73PCS/Service integration, 239PCS item procedure, 259People- enhancements, 45People- overview, 43Physical breakdown structure, 240planned orders, 113, 114Pricing and Discounts, 241Pricing Control (PCG) module, 168Print prices and discounts by matrix, 142Procurement card payments, 75Product Catalog (PCT) module, 169Product Configuration (PCF) module, 206Production Order Costing (CST) module, 203Production order groups, 196Production task, 200Production warehouse orders, 196Project Control (PCS) module, 206Project currency, 254Project dashboard, 259Project Data Management module, 266Project estimation, 260Project Hours Accounting (HRS), 265Project Invoicing (PIN) module, 267Project labor rates, 261Project Production Control module, 268Project Scheduling System (PSS) module,269project segment in Engineering DataManagement (EDM), 197Project Technical Calculation (PTC) module,269Project template, 262

Project warehouse, 263Pull notes, 198Purchase Control (PUR) module, 170Purchase order approval, 144Purchase order entry, 139Purchase order line types, 145Purchase order origin, 146Purchase order receipt information, 147Purchase order status, 148purchase planning per buyer, 116purchase planning per supplier, 116Purchase requisition enhancements, 150Purchase schedules, 150Purchase Statistics (PST) module, 170Queue time, 193Rebates, 182receipts, 219Reconciliation, 77, 151, 152recurring journal transactions, 77Reference activities, 241Reference designators, 198Reference rebate agreement, 181Repair task, 200Revenue recognition, 199Revenue Recognition (RR) and Cost ofGoods Sold (COGS), 263Reverse entries, 78RMA & Depot Repair (MSC) module, 249RMA and depot repair, 242Rough capacity consumption of work centersin PCS, 199Routing, micro, 195Routing (ROU) module, 207Sales and use tax, 28Sales contracts, 154Sales Control (SLS) module, 173Sales Invoicing, 182Sales order acknowledgements, 153Sales order approval, 154Sales order delivery information, 155Sales order entry, 139Sales order invoice information, 155Sales order line types, 156Sales order status, 157Sales price includes upgrade price for uniteffective items, 158Sales return orders, 159Sales schedules, 160

Sales Statistics (SST) module, 176Scandinavian localizations, 79Self billing, 161Sequence of material issue and backflushing,199serialized items, 220Serialized items, 27, 194Serialized items dashboard, 243Service Order Control (SOC) module, 249Service type and coverage type, 244Setup time, 193SFC order groups, 196Shared work centers, 200shipment generation for warehouse issues,222Shipping constraints, 161Shop floor warehouses, 201signals, 115standard calendar, 29Subcontract management, 244Subcontract Management (SBM)module, 249Supply chain strategy, 117Supply sources, 104Synchronize header - lines, 163Tables (MCS), 41Table sharing, 29Task type, 200Task - work center relationships, 201Tax, 163Tax provider, 32Terminology, 118terminology changes in CCP, 33Text on invoices, 179, 181time zone, 33Trade notes, 79Transaction logging, 246transfer of orders, 118unit effectivity, 119, 222Unit Effectivity (UEF), 34Usability improvements, 264usability improvements for shipment notices,223Use time fence option, 117Use-up of old revisions, 187VAT books, 80Wait time, 193Warehouse Management dashboardsessions, 223

WarehouseMaster Data (WMD) module, 229Warehouse on the BCM line, 120WIP warehouses, 201Withholding tax and social contributions, 35Work center, shared, 200

differences B50c/ERP61engineering item groups, 190

Differences ERP61/B50cProject Estimating (EST), 265

Differences Infor ERP LN 6.1 FP2Configured items without PCS, 20Delete item data and structures, 22EU sales listing declaration, 25Intercompany settlement, 63Intrastat declaration, 26tax, 30

Direct call invoicingDifferences B50c/ERP61, 235

Direct material supplydifferences B50c/ERP61, 211

Disaggregationdifferences B50c/ERP61, 103

Distribution planningdifferences B50c/ERP61, 108

Document Management (DM) module ,Differences B50c/ERP61

Differences B50c/ERP61, DocumentManagement (DM) module, 282

Drawing locationsdifferences B50c/ERP61, 189

Drawing sizesdifferences B50c/ERP61, 189

Dynamic host , Differences B50c/ERP61, 274ECO approval procedure

differences B50c/ERP61, 189EDM approval procedure in ODM

differences B50c/ERP61, 189Effectivity units

Differences B50c/ERP61, 131Employee data

Differences B50c/ERP61, 253Engineering Change Orders (ECOs)

differences B50c/ERP61, 189Engineering Data Management (EDM)module

Differences B50c/ERP61, 204Engineering item groups

Differences B50c/ERP61, 190Equate balance of receiptswith inventory level

Differences B50c/ERP61, 131Expense tax

Differences B50c/ERP61, 254Failure analysis

Differences B50c/ERP61, 236Fixed delivery moments

differences B50c/ERP61, 109Folder life cycle, Differences B50c/ERP61, 275Folder Management (FMG) module ,Differences B50c/ERP61

Differences B50c/ERP61, FolderManagement (FMG) module, 283

Freight ManagementDifferences B50c/ERP61, 135, 136

Freight Management- overview B50c/ERP61differences, 231

Functional elementDifferences B50c/ERP61, 237

GBFDifferences B50c/ERP61, 190

Generic BOMDifferences B50c/ERP61, 191

Generic Browser Framework (GBF)Differences B50c/ERP61, 190

Generic routingDifferences B50c/ERP61, 191

Global update of contract pricesDifferences B50c/ERP61, 237

Graphical planning board in SFC (Webtop)Differences B50c/ERP61, 192

Handling units, Differences B50c/ERP61, 271Horizon checking

Differences B50c/ERP61, 107Hours Accounting (HRA) module

Differences B50c/ERP61, 205Hours accounting

Differences B50c/ERP61, 193, 254Indirect task

Differences B50c/ERP61, 200Inspections

differences B50c/ERP61, 215Integration of Infor ERP Project with MicrosoftProject

Differences B50c/ERP61, 256Integration of Project with Service

Differences B50c/ERP61, 255Integration with Freight Management

differences B50c/ERP61, 212

Integration with Servicedifferences B50c/ERP61, 215

Internal projectDifferences B50c/ERP61, 257

Inventory Analysis (INA) moduleDifferences B50c/ERP61, 224

Inventory Handling (INH) moduleDifferences B50c/ERP61, 225

Inventory Planning (INP) moduleDifferences B50c/ERP61, 227

Inventory Reporting (INR) moduleDifferences B50c/ERP61, 228

Invoicing commissions and rebatesDifferences B50c/ERP61, 132

Invoicing enhancementsDifferences B50c/ERP61, 257

Item pricing using contract item price listsDifferences B50c/ERP61, 238

Item Purchase Data (IPU) moduleDifferences B50c/ERP61, 166

Item Sales Data (ISA) moduleDifferences B50c/ERP61, 167

Item-specific contract templatesDifferences B50c/ERP61, 238

Item typeDifferences B50c/ERP61, 107

LabelsB50c/ERP61, 198

Labor rates and skillsDifferences B50c/ERP61, 238

Lead time elementsDifferences B50c/ERP61, 193

Line supplydifferences B50c/ERP61, 216

Link query condition to previous run,Differences B50c/ERP61, 275List groups

Differences B50c/ERP61, 137Loading list

differences B50c/ERP61, 217Lot by unit

Differences B50c/ERP61, 194Lot Control (LTC) module

Differences B50c/ERP61, 228Lots (not in inventory)

differences B50c/ERP61, 217Lots and serials

Differences B50c/ERP61, 138

Lower cost or market valueDifferences B50c/ERP61, 194

Machine utilization chartDifferences B50c/ERP61, 194

Mail option for folder , DifferencesB50c/ERP61, 276Mass BOM Changes (MBCs)

differences B50c/ERP61, 189Master Data Management (MDM) module

Differences B50c/ERP61, 248Master planning

Differences B50c/ERP61, 109, 110Material-Routing Relationships

Differences B50c/ERP61, 110Micro routing

Differences B50c/ERP61, 195Move time

Differences B50c/ERP61, 193Multicompany warehouse transfers

differences B50c/ERP61, 218Multisite planning

differences B50c/ERP61, 108Non-direct deliveries

Differences B50c/ERP61, 143Offsetting logic in master-based planning

Differences B50c/ERP61, 110Operation overlap

Differences B50c/ERP61, 195Order cancellation

differences B50c/ERP61, 219Order grouping

differences B50c/ERP61, 111, 218Order groups, SFC

Differences B50c/ERP61, 196Order pegging

differences B50c/ERP61, 112Order pegging in Manufacturing

Differences B50c/ERP61, 195Order planning

differences B50c/ERP61, 112Order processing

differences B50c/ERP61, 224Order units

Differences B50c/ERP61, 140Over deliveries

Differences B50c/ERP61, 138Overlap


Parallel development, DifferencesB50c/ERP61, 276PCS/Service integration

Differences B50c/ERP61, 239PCS item procedure

Differences B50c/ERP61, 259Physical breakdown structure

Differences B50c/ERP61, 240Planned orders

differences B50c/ERP61, 113, 114Pricing and Discounts

Differences B50c/ERP61, 241Pricing Control (PCG) module

Differences B50c/ERP61, 168Print prices and discounts by matrix

Differences B50c/ERP61, 142Product Catalog (PCT) module

Differences B50c/ERP61, 169Product Configuration (PCF) module

Differences B50c/ERP61, 206Production Order Costing (CST) module

Differences B50c/ERP61, 203Production order groups

Differences B50c/ERP61, 196Production task

Differences B50c/ERP61, 200Production warehouse orders

Differences B50c/ERP61, 196Product Testing and Control (PTC) module ,Differences B50c/ERP61

Differences B50c/ERP61, Product Testingand Control (PTC) module, 272

Project Control (PCS) moduleDifferences B50c/ERP61, 206

Project currencyDifferences B50c/ERP61, 254

Project dashboardDifferences B50c/ERP61, 259

Project Data Management moduleDifferences B50c/ERP61, 266

Project Estimating (EST)Differences ERP61/B50c, 265

Project estimationDifferences B50c/ERP61, 260

Project Hours Accounting (HRS)Differences B50c/ERP61, 265

Project Invoicing (PIN) moduleDifferences B50c/ERP61, 267

Project labor ratesDifferences B50c/ERP61, 261

Project Production Control moduleDifferences B50c/ERP61, 268

Project Scheduling System (PSS) moduleDifferences B50c/ERP61, 269

project segment in Engineering DataManagement (EDM)

Differences B50c/ERP61, 197Project Technical Calculation (PTC) module

Differences B50c/ERP61, 269Project template

Differences B50c/ERP61, 262Project warehouse

Differences B50c/ERP61, 263Pull notes

Differences B50c/ERP61, 198Purchase Control (PUR) module

Differences B50c/ERP61, 170Purchase order approval

Differences B50c/ERP61, 144Purchase order entry

Differences B50c/ERP61, 139Purchase order line types

Differences B50c/ERP61, 145Purchase order origin

Differences B50c/ERP61, 146Purchase order receipt information

Differences B50c/ERP61, 147Purchase order status

Differences B50c/ERP61, 148Purchase planning per buyer

differences B50c/ERP61, 116Purchase planning per supplier

differences B50c/ERP61, 116Purchase requisition enhancements

Differences B50c/ERP61, 150Purchase schedules

Differences B50c/ERP61, 150Purchase Statistics (PST) module

Differences B50c/ERP61, 170Queries and Reports (QRY) module,Differences B50c/ERP61

Differences B50c/ERP61, Queries andReports (QRY) module, 283

Query filter, Differences B50c/ERP61, 277Queue time


Receiptsdifferences B50c/ERP61, 219

ReconciliationDifferences B50c/ERP61, 151, 152

Reference activitiesDifferences B50c/ERP61, 241

Reference designatorsDifferences B50c/ERP61, 198

Related objects, Differences B50c/ERP61Differences B50c/ERP61, Related objects,277

Related vault areas , Differences B50c/ERP61,277Relative change order, DifferencesB50c/ERP61, 278Repair task

Differences B50c/ERP61, 200Resource Planning Data (RPD) module, 120Revenue Recognition (RR) and Cost of GoodsSold (COGS)

Differences B50c/ERP61, 263Revenue recognition

Differences B50c/ERP61, 199Reviewers mechanism, DifferencesB50c/ERP61, 278Revise change, Differences B50c/ERP61, 279RMA & Depot Repair (MSC) module

Differences B50c/ERP61, 249RMA and depot repair,

Differences B50c/ERP61, 242Rough capacity consumption of work centersin PCS

Differences B50c/ERP61, 199Routing, micro

Differences B50c/ERP61, 195Routing (ROU) module

Differences B50c/ERP61, 207Rules and attributes, Differences B50c/ERP61

Differences B50c/ERP61, Rules andattributes, 280

Sales contractsDifferences B50c/ERP61, 154

Sales Control (SLS) moduleDifferences B50c/ERP61, 173

Sales order acknowledgementsDifferences B50c/ERP61, 153

Sales order approvalDifferences B50c/ERP61, 154

Sales order delivery informationDifferences B50c/ERP61, 155

Sales order entryDifferences B50c/ERP61, 139

Sales order invoice informationDifferences B50c/ERP61, 155

Sales order line typesDifferences B50c/ERP61, 156

Sales order statusDifferences B50c/ERP61, 157

Sales price includes upgrade price for uniteffective items

Differences B50c/ERP61, 158Sales return orders

Differences B50c/ERP61, 159Sales schedules

Differences B50c/ERP61, 160Sales Statistics (SST) module

Differences B50c/ERP61, 176Selection of vault areas, DifferencesB50c/ERP61, 280Self billing

Differences B50c/ERP61, 161Sequence of material issue and backflushing

Differences B50c/ERP61, 199Serialized items dashboard

Differences B50c/ERP61, 243Serialized items

differences B50c/ERP61, 220Differences B50c/ERP61, 194

Serialized items in ServiceDifferences B50c/ERP61, 243

Service Order Control (SOC) moduleDifferences B50c/ERP61, 249

Service type and coverage typeDifferences B50c/ERP61, 244

Setup timeDifferences B50c/ERP61, 193

SFC order groupsDifferences B50c/ERP61, 196

Shared work centersDifferences B50c/ERP61, 200

Shipment generation for warehouse issuesdifferences B50c/ERP61, 222

Shipping constraintsDifferences B50c/ERP61, 161

Shop floor warehousesDifferences B50c/ERP61, 201

Signalsdifferences B50c/ERP61, 115

Standard calendardifferences B50c/ERP61, 29

Subcontract Management (SBM) moduleDifferences B50c/ERP61, 249

Subcontract managementDifferences B50c/ERP61, 244

Supply chain strategyDifferences B50c/ERP61, 117

Supply sourcesDifferences B50c/ERP61, 104

Synchronize header - linesDifferences B50c/ERP61, 163

Task typeDifferences B50c/ERP61, 200

Task - work center relationshipsDifferences B50c/ERP61, 201

TaxDifferences B50c/ERP61, 163

Terminology changes in CCPdifferences B50c/ERP61, 33

TerminologyDifferences B50c/ERP61, 118

Timeframe for reviewers, DifferencesB50c/ERP61, 281Time zone

differences B50c/ERP61, 33Transaction logging

Differences B50c/ERP61, 246Transfer of orders

differences B50c/ERP61, 118Unit effectivity

differences B50c/ERP61, 119, 222Usability improvements

Differences B50c/ERP61, 264Usability improvements for shipment notices

differences B50c/ERP61, 223Use time fence option

Differences B50c/ERP61, 117Use-up of old revisions

Differences B50c/ERP61, 187Wait time

Differences B50c/ERP61, 193WarehouseManagement dashboard sessions

Differences B50c/ERP61, 223Warehouse Master Data (WMD) module

differences B50c/ERP61, 229

Warehouse on the BCM lineDifferences B50c/ERP61, 120

WIP warehousesDifferences B50c/ERP61, 201

Work center, sharedDifferences B50c/ERP61, 200