baan ivc functions and features of baan ivc2 sch0baansupport.com/docs/baan/p3040bus.pdf · between...

BAAN IVcFunctions and Features of BAAN IVc2SCH0

Functional Release Information P3040B US

Functions and Features of BAAN IVc2 SCH0


Document information

Document

Document code : P3040B USDocument group : Product InformationDocument title : Functions and Features of BAAN IVc2 SCH0Edition : BMonth modified : June 1998

Check the BaanDoc database to see if this document is still a valid edition.

© Copyright 1998 Baan Development B.V. All rights reservedThe information in this document is subject to change without notice. No part of this document maybe reproduced, stored or transmitted in any form or by any means, electronic or mechanical, for anypurpose, without the express written permission of Baan Development B.V.Baan Development B.V. assumes no liability for any damages incurred, directly or indirectly, fromany errors, omissions or discrepancies between the software and the information contained in thisdocument.

Functions and Features of BAAN IVc2 SCH0i

Table of contents

1. Introduction 11.1 Highlights 11.2 General 2

2. Common 32.1 Supplier Information 32.2 Customer Information 32.3 Electronic Data Interchange (EDI) 4

3. Distribution 53.1 General 53.2 Warehousing 53.3 Purchase Requisitions 53.4 Supply Chain Purchasing (PSC) 73.4.1 SCH Purchase Contracts 73.4.2 SCH Purchase Schedules 73.4.3 SCH Delivery Schedules (DCI) 93.4.4 SCH Fabrication and Raw Material Authorization Management (FAB and

RAW) 93.4.5 Advance Shipping Notices (ASN) 93.4.6 SCH Receiving 103.5 Supply Chain Sales (SSC) 103.5.1 SCH Sales Contracts 103.5.2 SCH Sales Schedules 103.5.3 SCH Fabrication and Raw Material Authorization Management (FAB and

RAW) 123.5.4 SCH Shipping Schedules (DCI) and SCH Production Sequence Schedules 133.5.5 SCH Shipping 133.5.6 Advance Shipping Notices (ASN) 15

4. Manufacturing 164.1 General 164.1.1 Planned Inventory Transactions Based on Schedules 164.2 Master Production Scheduling (MPS) 164.2.1 SCH Schedules as Demand 164.3 Material Requirements Planning (MRP) 164.3.1 Planned Inventory Movements Based on Planned Schedules 16

5. Finance 185.1 Evaluated Receipts Settlement 185.2 Automatic Self-Billed Reconciliation 185.3 SCH Finance/Distribution Cross References 18

Functions and Features of BAAN IVc2 SCH0ii

Functions and Features of BAAN IVc2 SCH0iii

About this document

This document presents the enhanced Supply Chain functionality realized by the newrelease BAAN IVc2 SCH0.

The new release satisfies the supply chain requirements of both the European and theNorth American market place. The enhancements which serve the requirements ofonly one of the two regions are indicated.

Functions and Features of BAAN IVc2 SCH0iv

ｴﾗ !ーｽﾀｲﾙが定義されていません。


This document presents the enhanced Supply Chain functionality realized by the newrelease BAAN IVc2 SCH0.

The new release satisfies the supply chain requirements of both the European and theNorth American market place. The enhancements which serve the requirements ofonly one of the two regions are indicated.

At the heart of the Supply Chain functionality lies the support of supply chainschedules for both suppliers and customers. The release provides for rapidcommunication via EDI (Electronic Data Interchange) ensuring that accordancebetween purchase and sales schedules can be maintained and any shipping orproduction irregularities noticed.

1.1 HighlightsMany manufacturing companies are finding that there is a need to reduce inventoriesand to speed up communication between trading partners. As a result, supply chainsare tightening up and more demand is being placed on Enterprise Resource Planning(ERP) systems to provide a framework for total supply chain management.

In order to support these requirements, the concept of sales and purchasing scheduleshas been introduced for planning and controlling shipments and deliveries. SupplyChain (SCH) schedules allow the use of ”lean stock” policies and inventory controlbased on the concepts of Just-In-Time deliveries.

For a supply chain partnership the application maintains customer commitment withnew functions. The handling of inbound customer schedules has been enhanced in thearea of cumulative figure (CUM) management, including adjusting, resetting andmanual or automatic reconciliation of these figures.

The system is able to receive and process cumulative SCH schedules, as well asdiscrete SCH schedules.

The schedules are integrated completely with Material Requirements Planning (MRP)and Master Production Scheduling (MPS). The supplier is able to consistently handlecoexisting SCH Sales, Shipping and Sequence Schedules. With the help of newcontrol features the MRP module can generate SCH Purchase Schedules that follow aspecified day pattern, leave a minimum interval between requirement dates, andremain unchanged in a given ‘Frozen Period’ time horizon.

SCH receiving can be streamlined by utilizing the advanced shipment notifications(ASNs). SCH shipping has been enhanced in regard to delivery lead time, packaging,loading and special charges.

Paper flow and handling effort due to financial transactions can be greatly reducedwith self-billing functions on the sales side and the support of Evaluated ReceiptsSettlement on the purchase side.

1. Introduction



The Electronic Data Interchange (EDI) functionality supports the following EDItransmission standards ANSI X.12, EDIFACT, Odette and VDA.

A new module, Purchase Requisitions (PRQ), handles the formal requests for theraising of non-production and non-SCH purchase orders.

1.2 GeneralBecause BAAN IVc2 SCH0 is an extension of the BAAN IVc2 product, all of thestandard features provided in BAAN IVc2 are also present. These include the use ofthe Graphical User Interface for Windows 95 or Windows NT environments or the useof the standard ASCII interface for users of terminals and terminal emulators.Moreover it can be installed on Unix and Windows NT operating systems. Theextension includes the Tax Provider Functionality for the North American market.



2.1 Supplier InformationFor each supplier additional site specific information can now be defined. Thisincludes information relating to:

n Allow Retro-Billing,n Self-Billing Indicator,n Site Code and Description,n Use Schedule References,n Using CUM’s (Automotive industry specific),n Specific item information to support export requirements is available at the

supplier level by item including:n Harmonized Tariff Code,n Country of Origin,n Valuation and Currency,n Product Identification.

2.2 Customer InformationFor each customer additional site specific information can now be defined. Thisincludes information relating to:

n Allow Retro-Billingn Self-Billing Indicatorn Site Code and Descriptionn Use Schedule Referencesn Using CUM’s (Automotive industry specific)

2. Common



2.3 Electronic Data Interchange (EDI)In order to support the rapid communications requirements of supply chain drivenmanufacturing companies, BAAN IVc2 SCH supports a series of EDI messages foruse between trading partners:

Message Type Direction

Sales / Purchase Schedule In / Out

Shipping / Delivery Schedule In / Out

ANSI X.12 866 (Sequenced Shipping Schedule) In

Advanced Shipping Note In / Out

VDA 4913/36 (ELP informs supplier about despatch to customer) In

VDA 4927/01 (Container accounts) In / Out

VDA 4927/03 (Containers in transit) In

Invoice In / Out

Payment Advice In / Out

Self-Billed Invoices In

VDA 4913/36, 4927/01 and 4927/03 possess no corresponding messages in ANSIX.12.

BAAN IVc2 SCH0 supports the following EDI message standards: ANSI X.12 (NorthAmerica), EDIFACT, Odette (Europe), VDA (mainly Germany). An exception is theprocessing of an inbound Sequenced Shipping Schedule which so far is only supportedfor the standard ANSI X.12.

Within the EDI module standard conversion setups are developed for each of themessage types. An EDI subsystem (translator) is needed to transform the BAANgenerated flat files into external EDI messages.

With a focus on VDA, ODETTE and EDIFACT standards, a well-defined messagestandard (BEMIS) has been laid down for the BAAN generated flat files. BEMIS flatfiles can be processed by EDI subsystems, or passed on directly to the BAAN SCHsystem of a trading partner.

Baan provides detailed directions on how to configure the EDI module and how to setup an EDI subsystem so that for every message type its interface with BAAN matchesthe BEMIS format.

Additional conversion setups can be user defined for specific trading partnerrequirements.

The EDI communications with trading partners are maintained in the EDI module viaEDI relations, which allows the user to communicate different message types todifferent addresses of the same trading partner.



3.1 GeneralThe Distribution base tables of BAAN standard are supplemented by SCH relevantbase tables. Briefly the following can be maintained in these additional tables:

n Supplier Part Numbers,n Receiving Pattern,n Customer Part Numbers,n Customer Part Number Revision Levels,n Time Zones by Company,n Planner Groups,n Transportation Modes,n Carrier Alpha Codes,n Equipment Codes,n Excess Transportation Reason Codes,n Rail Codes,n Traffic Classification Codes,n ANSI Pack Codes,n Freight Terms,n Internal Docks,n Use Codes.

3.2 WarehousingThe Supply Chain extension can be used with or without Inventory Location Control(ILC). As in BAAN standard negative inventory balances are allowed if ILC is turnedoff.

Lot Control (LTC) is fully supported if ILC is tuned on.

The Supply Chain extension does not allow to use a different unit on a SCH SalesContract than is used for inventory.

3.3 Purchase RequisitionsPurchase requisitions (PRQs) are formal requests for raising non-production purchaseorders. The PRQ Module provides the means to control expenditure before it iscommitted by giving the functionality to raise and selectively authorize purchaserequisitions.

The system can be implemented by the user to ensure that varying levels of controlwill be applied, according to the monetary value, budgets and company purchasingpolicy.

3. Distribution



Purchase requisitions may be entered as and when they are required. Authorizedrequisitions will be converted into purchase orders, either automatically within a user-defined range, or manually by requisition number.



If converted automatically, a new batch of purchase orders will be generated; withinthis batch requisition lines may be consolidated if required. If a single requisition isconverted, the user may opt to add these lines to an existing purchase order.

Items, such as stationery, may be purchased for use by a number of departments. Asingle purchase order may be generated from a number of different requisitions. Anysplit of the costs over different departmental codes may be input at requisition linelevel and will be recognized by the system when generating financial transactions.

3.4 Supply Chain Purchasing (PSC)

3.4.1 SCH Purchase Contracts

A SCH Purchase Contract can be assigned three different statuses: live, on hold andcancelled. Among other the contract contains the item code, the supplier part number,purchase price and delivery address. The contract specifies whether the goods are tobe delivered by the supplier or to be picked up by the customer.

In the SCH Purchase Contract one also defines out of how many daily, weekly andmonthly buckets an associated SCH Purchase Schedule consists. The buckets aredistributed over three different types of requirement periods: released, planned andforecast.

Moreover, the SCH Purchase Contract holds FAB and RAW periods which are usedfor the calculation of fabrication and raw material (FAB and RAW) authorizations.

At contract level the user also controls how often SCH Purchase Schedules shall begenerated from Material Requirements Planning (MRP) and whether SCH DeliverySchedules shall be created, too. For the generation of SCH Purchase Schedules fromMRP a frozen period, a receiving pattern, and a minimum order interval can bespecified.

In addition one can specify a packaging structure of up to four levels including flagsthat determine whether the packaging containers may sometimes be partially filled.

3.4.2 SCH Purchase Schedules

SCH Purchase Schedules provide a means to send advance notice of purchaserequirements to suppliers.

SCH Purchase Schedules can either be created manually or automatically generatedfrom within the planning system by MRP and, due to the enhancements, by MPS. Thefrozen period, receiving pattern and minimum order interval features however are onlysupported by MRP, not by MPS.

In addition to the requirement types released, planned and forecast, a SCH PurchaseSchedule can begin with a requirement line of type immediate.

By comparing old and new schedules BAAN IV SCH calculates the Back Orderquantity (part of immediate demand due to delivery delay) or the Over Deliveryquantity. These data are usually transmitted to the supplier in an ODETTE and VDAenvironment.



Standard reports and displays are available to review SCH Purchase Schedules. Thedisplays and reports also include customer cumulative (CUM) figures and informationabout the last receipt.

SCH Purchase Schedules including the supplementary information available in thereports can be transformed into EDI messages.

CUM Management

On the purchase side BAAN SCH’s cumulative figure (CUM) management provides:

n AdjustmentBAAN SCH enables customers to adjust their receipt CUM figures. This might benecessary to eliminate inconsistency caused for example by shipping irregularitiesor loss of material.Adjustments will not affect inventory and accounts receivable.

n ResetThe trading partners occasionally redefine the reference point with respect to whichtheir CUMs count delivered and received goods. Normally, the customer dictateswhen such a reset of CUMs to zero shall occur.

The annual reset can be done jointly for a range of suppliers and item numbers byspecifying a date as reference point. Alternatively, the reference point for reset canbe chosen individually per contract by selecting a particular receipt.

Supplier Schedule Frozen Period

Suppliers need some certainty about customer demand in order to plan theirproduction and their own purchasing. As a result the purchase schedules, to be sent tothe supplier, should have a ‘Frozen Period’ time horizon, in which they do notnormally change.

The MRP has been enhanced to incorporate ‘Frozen period’ functionality. This allowsthe SCH Purchase Schedules for a SCH Purchase Contract to be frozen for adetermined period. The Frozen Period may be declared in calendar or working days onthe contract. When the precluding of SCH Purchase Schedule adjustments during thefrozen period leads to insufficient stock within that period, the application generatesexception messages. The planner could then override the freezing function bymanually adjusting the SCH Purchase Schedule.

Receiving Patterns

BAAN SCH allows the customer to specify a receiving pattern (e.g. every secondThursday of the month) per SCH Purchase Contract in order to define when deliveriesshall occur. When the system generates SCH Purchase Schedules from the MaterialRequirements Plan (MRP) the specified day patterns will automatically be followed.The receiving pattern is also used to recommend delivery dates when manuallyentering schedule requirements.



Minimum Order Interval

In addition to a frozen period and a receiving pattern the planner can specify percontract a minimum number of calendar or working days that shall lie between tworequirement dates. A SCH Purchase Schedule generated by MRP then automaticallyforesees that minimum interval between two requirement dates.

3.4.3 SCH Delivery Schedules (DCI)

In addition to a SCH Purchase Schedule BAAN IV SCH is able to produce andtransmit a SCH Delivery Schedule for short term requirements. This schedule can alsobe generated from the MRP or can be set up manually to support last minuterequirements.

The standard reports of SCH Delivery Schedules also include the cumulative receiptfigures and information about the last receipt.

SCH Delivery Schedules including the supplementary information available in thereports can be transformed into EDI messages.

3.4.4 SCH Fabrication and Raw Material Authorization Management (FAB andRAW)

Each SCH Contract addresses the supplier’s need for commitments by his customersthat enable him to meet the customers’ just-in-time requirements. Customerscommunicate these commitments to their suppliers by means of FAB & RAWAuthorizations. The FAB Authorization gives the supplier authority to manufacture aquantity of finished components which the customer agrees to purchase. Similarly, theRAW Authorization gives the supplier authority to purchase a quantity of rawmaterials which the customer is committed to purchase unless consumed bymanufacture.

BAAN SCH calculates the cumulative and per period authorization figures based onthe SCH Purchase Schedule and the period information stored on the SCH PurchaseContract. The customer can transmit authorization data to the supplier as part of theSCH Purchase Schedule.

3.4.5 Advance Shipping Notices (ASN)

Suppliers often send shipment information ahead of the shipment in the form ofelectronic Advance Shipping Notices (ASN).

Received ASNs can be processed by an automated validation check. The invalidASNs are then stored separately from valid ones. The receipt of a valid ASN can benotified to the supplier with an EDI message. Invalid ASNs can be sent back to thesupplier. If the ASN passes the preliminary validation another electronic message issent to the supplier to confirm its receipt.

Valid ASNs are held until the actual goods are received.

In addition, an ASN can be manually entered into the system, either before thereceiving process or during the receiving process. This allows the customer tomanually create an ASN when the supplier is unable to electronically send ASNs.



3.4.6 SCH Receiving

With SCH Receiving the user can receive against SCH Purchase, respectivelyDelivery Schedules. If a Delivery Schedule is available in addition to a PurchaseSchedule the system automatically chooses to receive against the Delivery Schedule.SCH Receiving is fully integrated with standard receiving functionality so that itlaunches inbound processing directly to move the received goods to inventory.

The receiving process can be streamlined by utilizing advanced shipping notes (ASNs).Receiving personnel can trigger the receiving process by solely entering the ASN orload number along with the contract number. BAAN SCH then will automaticallyselect all expected receipts to which the ASN or load number refers. An additionalfeature enables all selected lines to be accepted by means of a single mouse-clickselection or keystroke combination. If a discrepancy is found, a discrepancy report iscreated and the appropriate EDI messages may be generated and sent back to thesupplier.

3.5 Supply Chain Sales (SSC)Supply Chain Sales has also been significantly enhanced.

3.5.1 SCH Sales Contracts

A SCH Sales Contract can be assigned three different statuses: live, on hold andcancelled. Among other things the contract contains the item code, the customer partnumber, purchase price and delivery address. The contract specifies whether the goodsare to be delivered by the supplier or to be picked up by the customer. A revisionnumber serves to manage changes in customer parts.

Moreover, the SCH Sales Contract holds FAB and RAW periods for which thecustomer authorizes the fabrication of goods and purchase of raw material.

At contract level the user also controls the integration of SCH Sales, Shipping andSequence Schedules with Master Production Scheduling (MPS).

In addition, the SCH Sales Contract includes an improved packaging definition thatallows to define multi-level packaging and mixed loads.

3.5.2 SCH Sales Schedules

SCH Sales Schedules are used to identify both short and long term customer demand.

SCH Sales Schedules are created as part of the inbound EDI message processing fromthe customer or can be entered manually. This also applies for the data usuallyincluded in the schedule header, in particular customer cumulative figures andinformation about the shipment last received by the customer.

Each SCH Sales Schedule can be filled with daily, weekly and monthly buckets of upto four different requirement types: immediate, released, planned and forecast.

The system stores Back Order and Over Delivery information which can betransmitted as part of the inbound EDI message or entered manually.

Standard reports and displays are available to review SCH Sales Schedules.



CUM Management

On the sales side BAAN SCH’s cumulative figure (CUM) management provides:

n AdjustmentBAAN SCH enables suppliers to adjust the shipment CUM figures. This might benecessary to eliminate inconsistency caused, for example, by shipping irregularitiesor loss of material.

Adjustments will not affect inventory and accounts receivable.

n ResetThe supplier is able to reset his shipment CUM. The annual reset can be donejointly for a range of customers, contracts and items by specifying a date asreference point. Alternatively, the reference point for reset can be chosenindividually per contract by selecting a particular shipment.

n Manual ReconciliationThe manual reconciliation process has been streamlined. All data relevant forreconciliation is now recorded directly in the schedule header. The user nowcontrols the necessary adjustments himself with the help of the new adjustmentfunctionality.

n Automatic ReconciliationThe enhancements provide an automated process of identifying discrepanciesbetween a Customer's receipt CUM and the shipment CUM. The reconciliationprocess has been attached to the importing of the EDI Sales Schedule transactions.Based on the shipping log and the receipt CUM data provided by the customer,shipment CUM figures are compared to the customer's receipt CUM. If adiscrepancy is found, the shipping log entry is marked "In Dispute." Areconciliation report has been added to identify the disputed shipments for laterfollow up and correction.

KANBAN SCH Sales Schedules

Especially in the North American market, a number of OEMs (Original EquipmentManufacturers) report their requirements as discrete portions in KANBAN typeschedules. OEMs using this technique vary somewhat in approach, but the underlyingmethod is to issue a KANBAN document for each requirement stating the precisequantity required and when it is needed. Generally this pull-document is numberedand the number is used by the OEM to reference the payment.

BAAN SCH enables the user to receive a KANBAN schedule and track schedulesbased on the number (Customer Authorization Number), such as KANBAN, RAN, orDON numbers, with which the customer enumerates the discrete requirements. Likeany other schedule the KANBAN schedule can be brought into the application throughEDI transactions or entered manually. The Customer Authorization Numbers areassociated with the discrete requirements and can be traced through the life of theschedule, from planning, to shipping, to invoicing. SCH Sales Schedule requirementscan be displayed by Customer Authorization Number.



Netting Logic

It is essential that the supplier knows how far ahead of or behind the customer’srequirements schedule he is. The netting functionality for determining the supplierposition on the requirement schedule supports discrete and cumulative SCH SalesSchedules. Upon receiving such a schedule through EDI, the enhanced system willcalculate the net requirement based on the cumulative requirements, the customerreceipt CUM, and the shipment CUM. Per parameter setting, shipment CUM figurescan be based on:

n At the End of Previous Day,n At Last Shipment.

With ‘At the End of Previous Day’, the shipment CUM from the last shipment of theprevious day is used to determine the net requirement. Using ‘At Last Shipment’, themost current shipment CUM value is used. These shipment CUM values are nettedagainst the Customer's CUM requirement to calculate the true requirement owed to theCustomer.

The netted schedule is stored and used for planning and shipping purposes whereas theoriginal schedule is held for inquiry purposes.

Customer Part Number Revisions

Customers may make a change to a part without changing the part number. Thismostly occurs when form, fit, or function does not change. BAAN SCH allows thesupplier to manage such changes by associating the customer part number with arevision number in the SCH Sales Contract. Effectivity and expiration dates can beused to ensure that the supplier changes his shipments at a precise time.

The current customer revision number is shown on inquires and reports so that thecorrect revision is used when communicating to the customer. The revision will berecorded against each shipment line to allow the ASN generation process to pick upthe correct revision level. The revision number will be reported on the shipment log tofacilitate the historical reporting of the shipped revisions.

Moreover the customer may decide to change the period of validity of a revision level.In order to accommodate such changes the supplier can alter the revision level ofplanned and confirmed shipments. However, the supplier also has the option to set asystem parameter per customer part so as to prevent such changes at the level ofplanned shipments.

3.5.3 SCH Fabrication and Raw Material Authorization Management (FAB andRAW)

BAAN SCH maintains fabrication and raw material (FAB and RAW) authorizationfigures referring to specified periods. The application enables the supplier to receiveauthorization data as part of the customer purchase schedule.

For each received schedule, the application automatically maintains the highestcumulative and per period (discrete) commitments (high watermark figures). Theauthorization information is stored and can be viewed in display sessions.



3.5.4 SCH Shipping Schedules (DCI) and SCH Production SequenceSchedules

Short term and immediate requirements of the customer are best expressed by SCHShipping and Production Sequence Schedules. The SCH Production SequenceSchedule functionality allows the supplier to receive and realize a shipping sequencethat accords with the production planning schedule of the customer.

SCH Shipping and Production Sequence Schedules are created as part of the inboundEDI message processing from the customer or can be entered manually. This alsoapplies for the data usually included in the schedule header, in particular customercumulative receipt figures and information about the shipment last received by thecustomer.

3.5.5 SCH Shipping

Shipping Process

BAAN SCH automatically generates planned deliveries including standard packaging.The process allows the creation of deliveries either by customer order number or bydelivery address. This is especially important for most European customers. Thesystem also provides the ability to automatically collect deliveries that were created bycontract for one delivery address using an enhanced Master Bill of Lading (MBOL)functionality. Other new features of the shipment functionality are the support ofmixed loads and an enhanced packaging functionality (see1317900.1315304.186591964).

The deliveries created by the system automatically will be linked to a reservation listthat enables both, system and user, to monitor the availability of parts. The systemautomatically will update this list whenever new deliveries are generated.

Quantities and packaging of planned deliveries can be manually adjusted. Between thestatuses ”planned” and ”confirmed” the deliveries now take on the status ”inpreparation”, during which the deliveries are not overwritten with automaticallygenerated planned deliveries. The deliveries in the status ”in preparation” can bemanually maintained, too. This functionality is intended for shipping staff at the shopfloor level, whereas manual adjustments to deliveries with status ”planned” should bemade by planners. The confirmation of deliveries and the connected transactions areperformed by an automated process. Deliveries that are not assigned a sufficientquantity of items in the reservation list will be declined.

Shipping Planning Board

The Shipping Planning Board facilitates the movement of items between advice notes/ loads (of the same customer, delivery address and delivery date) to balance outweights and resolve other loading issues.

Shipping Documents

The application provides functionality for creating labels and documents beforedeliveries have been confirmed.



Container Management

Depending on parameter settings the system automatically relieves returnablepackaging, non-returnable packaging, or both, when confirming deliveries.

Additionally the system is able to automatically track packaging accounts perpackaging type and business partner for returnable packaging items.

The user can adjust package accounts manually and reconcile them with the packageaccounts of the trading partners. For users that work with the VDA standard thesystem will also provide an automatic reconciliation based on the packaging accountstatement sent via VDA 4927.

Packaging

The user can define both, a default and an alternative packaging set when setting upthe contract. Each of them may consist of an unlimited number of packaging items.After having created shipments with the standard packaging by using standardsessions, the user can choose to substitute the packaging with alternative packaging.

The application will then "re-pack" the items with the alternative packagingconfiguration. During this process the application leaves the total number of includeditems unchanged. Afterwards the user can manually adjust the proposed packaging,e.g. in order to fill containers up to capacity. The packaging data will be added to theASN.

Loading

Shipments or advice notes are created via the session Automatically Create PlannedDeliveries. This function creates an advice note for all items that need to be deliveredto a specific Customer, Delivery Address at a particular date/time. This function willcreate multiple advice notes when the shipment exceeds the capacity of the normalmode of transportation. For optimum flexibility this weight limit may be specified perDelivery Address.

The created shipments or advice notes can be changed with the existing maintenancesessions.

An increasing number of OEMs use sequenced data transactions and require theirsuppliers to ship products in certain sequences. New Sequenced Shipping Reportfunctionality facilitates the loading of items in sequence onto a shipping conveyance(truck, rail car, etc.). Based on the Sequenced Shipping Schedule (ANSI X.12 866,DELJIT), the report suggests what to load on the conveyance and in what order to loadthe items. The new functionality supports the loading options, back to front, front toback, and side load.

Master Bill of Lading

A load may be comprised of shipments to more than one customer and/or location inorder to use the capacity of a conveyance to its fullest. This may especially be done ifthe supplier employs contracted transport, in which case a single documentsummarizing the load needs to be given to the transport company.



To this end the application enables the user to generate a Master Bill of Lading whichcombines the advice notes (Bills of Lading) making up the load.

Special Charges

With BAAN SCH the user can raise special charges to the Customer at the time ofshipping. Special Charges are charges related to set-up, tooling, packaging, andexceptional delivery. This enhancement permits one or more such charges to be addedto an individual shipment as cost items. The system will include them as lines on theASN and on the invoice.

Special charges are linked to a cost item on the item master. The default cost itemnumbers are specified as part of the Supply Chain Parameters.

Delivery Lead Time

If schedule dates are delivery dates, the calculation of shipping dates takes intoaccount the delivery lead time and transport restrictions on week-ends.

External Logistic Provider Handling

Suppliers often outsource the distribution of goods to External Logistics Providers(ELPs). In such a case customers inform the supplier of their long term requirementsand transmit their short term requirements to the External Logistics Provider.

BAAN SCH bases the planning of shipments on the ELP’s stock and on the SCHSales Schedules sent by the customers. When delivering the products to the finalcustomer, the ELP sends a dispatch note copy to the supplier, which is used forupdating the shipment CUMs as well as for invoicing or processing self-billedinvoices. The application supports the EDI messages that are exchanged with thecustomers and the ELP as part of the external logistics process.

3.5.6 Advance Shipping Notices (ASN)

Shipment information can be sent to the customer in the form of electronic AdvanceShipping Notices (ASN).

In order to manage the transport process, it is often necessary to send an ASN to boththe customer and to the transport or Logistics Company. The user can trigger thetransmission of these notices from within the SCH shipping process. Only the ASNdirected to the customer is integrated into the shipping log.



4.1 General

4.1.1 Planned Inventory Transactions Based on Schedules

SCH Purchase and Sales Schedules give rise to planned inventory transactions. Theseplanned inventory transactions are displayed online by standard display sessions. (Forexample, entries due to SCH Purchase Schedules that have been proposed by MRP orMPS, and then confirmed by the planner, can be viewed there.) Corresponding reportscan be generated by standard print sessions.

4.2 Master Production Scheduling (MPS)

4.2.1 SCH Schedules as Demand

The ‘Customer Orders’ figure in a Master Production Schedule is updated to reflectthe SCH Sales Schedule. For the short term period it is possible to replace this demandfrom the SCH Sales Schedule by either all or part of the SCH Shipping or SCHSequencing Schedule figures depending on parameters set on the SCH Sales Contract.

The offset between delivery and shipping date is accounted for in the generation of aMaster Production Schedule.

4.3 Material Requirements Planning (MRP)

4.3.1 Planned Inventory Movements Based on Planned Schedules

A MRP run generates planned SCH Purchase Schedules which can be manuallymaintained afterwards. Entries due to planned Purchase Schedules are now displayedby standard planned-inventory-movements display sessions.

4. Manufacturing



5.1 Evaluated Receipts SettlementIn a Just in Time environment OEMs and components suppliers need to reduce theirpaper flow and speed up the handling of the high volume of supply chain transactions.The application accomplishes this task with Evaluated Receipts Settlement (ERS). Inthis process the customer eliminates invoices from the supplier by electronicallycreating self-billed purchase invoices based on receipts for payment to suppliers. Thistotally replaces both financial and legal documentation previously generated by thesupplier.

5.2 Automatic Self-Billed ReconciliationToday many customers send self-billed invoices to their suppliers indicating thereceipt or usage of goods. If trading partners agree on using self-billing, the systemrecords for the supplier which self-billed invoices he should expect to receive from thecustomer. BAAN SCH provides the supplier with an automated reconciliation processto handle self-billed invoices which typically are delivered through EDI (e.g.according to German VDA 4908). As part of this process the system tries to matchreceived with expected self-billed invoices. Received and expected self-billed invoicesthat remain unmatched can be corrected manually.

5.3 SCH Finance/Distribution Cross ReferencesFour new cross reference look-ups assist the user in following up the informationprocess across the finance/distribution interface:

n Customer Authorization Number (KANBAN) to Sales Invoice Number,n Advice Note Number to Sales Invoice Number,n Sales Invoice Number to Customer Authorization Number (KANBAN),n Sales Invoice Number to Advice Note Number.

5. Finance