subsystem reference manual - epicor reference manual ... buyers ship-to items (bcts/bcim/bsti) ......

Scheduled Release Subsystem Reference Manual Prophet 21 FASPAC 5.0

1

The documentation in this publication is provided pursuant to a Sales and Licensing Contract for the Prophet 21 System entered into by and between Prophet 21 and the Purchaser to whom this documentation is provided (“License Agreement”). In addition, the licensed software to which this documentation refers may be supported in accordance with a customer support agreement by and between the same parties (“Support Agreement”). All warranties, conditions of use, transfer restrictions, and other provisions in the License Agreement or Support Agreement which are applicable to Licensed Software, are applicable to this publication. In addition, this publication may include inadvertent technical inaccuracies or typographical errors for which Prophet 21 is not responsible. Changes may be periodically made to this publication; these changes will be incorporated in new editions of the publication. Any questions about the material contained in the publication should be addressed to the Prophet 21 Customer Support Department at http://customer.p21.com.

Nothing in this statement amends or extends the terms of your agreement with Prophet 21 including any warranties that may be included in our products. Warranties for such agreements are set forth in your agreement with Prophet 21.

Improvements and/or changes to the Licensed Software described in this publication may be made by Prophet 21 at any time without notice.

6/22/04 Prophet 21 Faspac

Prophet 21 is a registered trademark of Prophet 21, Inc. All other trademarks and registered trademarks are the property of their respective companies.

http://customer.p21.com/

Table of Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

1 Overview of SRS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Why Use SRS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

How to Use SRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

2 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Define System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Buyer Contract Specifications (SYS/OPT/BCS) . . . . . . . . . . . . . . 2-2

System Code Maintenance (SYCD) . . . . . . . . . . . . . . . . . . . . 2-5

Define the Buyer Contract Database . . . . . . . . . . . . . . . . . . . . . . 2-8

Buyer Customer Cross Reference Maintenance (BCCR/MAI) . . . . . . 2-9

BCCR/MAI, Screen Two . . . . . . . . . . . . . . . . . . . . . . . 2-17

Carrier Codes File Maintenance (BCTS/BGCM/CCFM). . . . . . . . . 2-19

Buyer Group Item Maintenance (BCTS/BGIM/MAI) . . . . . . . . . . 2-22

Buyer Customer Item Maintenance (BCTS/BCIM/MAI) . . . . . . . . 2-28

BCIM, Second Screen . . . . . . . . . . . . . . . . . . . . . . . . 2-40

3 Acquiring Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Importing EDI Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Get EDI Transactions From PC (EDI/REDI). . . . . . . . . . . . . . . . . . 3-3

Translate Data from EDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Inbound EDI Translation Driver (EDI/EDID) . . . . . . . . . . . . . . . 3-5

The EDID Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Files Updated by EDID . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Reports Produced by EDID . . . . . . . . . . . . . . . . . . . . . . 3-8

Viewing EDID Processed Records . . . . . . . . . . . . . . . . . . 3-13

EDID Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Error or Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Sample 830 and 862 Reports . . . . . . . . . . . . . . . . . . . . . . . 3-21

Example of an EDI 830 Planning Transaction . . . . . . . . . . . . 3-21

Example of an EDI 862 Shipping Transaction . . . . . . . . . . . . 3-26

FPD/319-03 iii

EDI Requirements Received for Previous Ship Dates . . . . . . . . . . 3-30

EDI Past Due . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

How EDID Calculates Demand in FASPAC . . . . . . . . . . . . . . . 3-32

Manual Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

Buyer Customer Item Maintenance (BCTS/BCIM/MAI) . . . . . . . . 3-37

Buyers Ship-To Items (BCTS/BCIM/BSTI) . . . . . . . . . . . . . . . 3-43

Time Phased Management Inquiry . . . . . . . . . . . . . . . . . . . . . . 3-44

Inventory Management Exception (TPI/TPIM). . . . . . . . . . . . . . 3-44

Inflow Source Codes . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

Outflow Source Codes . . . . . . . . . . . . . . . . . . . . . . . . 3-50

4 Processing Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Create a Pull List (OP/SHP/SHC/PLFM). . . . . . . . . . . . . . . . . . . . 4-2

Files Updated by PLFM . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Create Quotes from Pull List (OP/SHP/SHC/PLO) . . . . . . . . . . . . . . 4-7

PLO Pull List Orders Error Report . . . . . . . . . . . . . . . . . . . . . 4-9

Order Desk (OD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

5 Miscellaneous Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Change Customer Group (BCTS/BCCR/CGRP) . . . . . . . . . . . . . . . . 5-1

Customer Item History Maint. (BCTS/BCIH/MAI) . . . . . . . . . . . . . . 5-2

Customer Item History Inquiry (BCTS/BCIH/INQ) . . . . . . . . . . . . . . 5-3

Buyer Customer Item (BCTS/BCIM/INQ) . . . . . . . . . . . . . . . . . . . 5-4

Buyer Group Item Maintenance (BCTS/BGIM/MAI), Second Screen . . . . 5-5

Buyer Group Item Copy (BCTS/BGIM/CPY) . . . . . . . . . . . . . . . . . 5-6

Group Item Inquiry (BCTS/BGIM/INQ) . . . . . . . . . . . . . . . . . . . . 5-7

Customer Inquiry (SAL/BCTS/BGIM/CINQ) . . . . . . . . . . . . . . . . . 5-8

Past Due Report (BCTS/BCSR/PDR) . . . . . . . . . . . . . . . . . . . . . 5-9

Demand Summary Report (BCTS/DSR) . . . . . . . . . . . . . . . . . . . 5-10

Pull List Report (OP/SHP/SHC/PL). . . . . . . . . . . . . . . . . . . . . . 5-11

Buyers Ship-To Copy (BCTS/BGIM/BSTC) . . . . . . . . . . . . . . . . . 5-14

iv FPD/319-03

TABLE OF CONTENTS

Introduction

This manual provides the information you need to set up and work with the

FASPAC Scheduled Release Subsystem (SRS) module.

Conventions

Read this section thoroughly. It describes common operating instructions used

throughout this document.

Screen illustrations throughout the manual are samples only—yours will vary

according to your system and how it is set up.

Italic font Indicates another chapter, section, or book. It is also

used for emphasis.

Bold font Indicates keys you are to press.

Courier font Indicates text that appears on the screen or in a

report.

Courier Bold font Indicates text you are to type.

Enter <text> Means to type the text and press the Return key.

For example, “Enter BCS...” means to type BCS and

press Return.

Press <key1+key2> Means to press these keys consecutively, not

simultaneously.

For example, “Press CMD+Q” means to press the

CMD key and release it, and then press D and

release it.

FPD/319-03 v

Note: Additional information about the topic being discussed.

Caution! Alerts you to a situation that could cause damage to your data or

system.

vi FPD/319-03

INTRODUCTION

1Overview of SRS

This chapter provides an overview of the SRS process.

The Scheduled Release Subsystem (SRS) module allows you to define specific

agreements or contracts for one or more of your customers, based on their

requirements for products and shipping. In other words, they become your

trading partners.

A buyer, who represents one or more companies, contacts your company and

would like to schedule shipment dates for certain items to different locations. A

location may be as specific as a line feed for a certain assembly line.

SRS allows you to enter scheduled orders, easily edit requirements, and plan your

purchasing requirements. For example:

• A customer purchases parts from your company for their assembly line.

• The customer assembles product in three plants.

• Each plant has three line feed locations.

• Shipments are sent to two plants on Friday.

• Shipments to the other plant are sent Monday and Wednesday.

• The customer has a buyer that places orders for the product each week.

SRS is also known as the Buyer Contract System (BCTS); these terms are

interchangeable. SRS can be used with or without Electronic Data Interchange

(EDI) transactions.

FPD/319-03 1 - 1

Why Use SRS?

• It provides a requirement schedule

• The customer commitment to purchase

• The planning capability

• Effective purchasing allows better pricing

• To carry less inventory

• A request is only entered once

SRS accommodates industry standard 830 and 862 EDI transactions.

• An 830 is a planning transaction, an estimated quantity of product over a

period of time. It is a prerequisite for an 862.

• An 862 transaction is a firm request for short term, such as 2-3 weeks with

specific dates and quantities to ship orders.

Note: You would not just have 862 transactions but you may have just 830

transactions, since an 830 is a prerequisite for an 862. When 862 transactions are

received, they override any 830 transactions for the same time frame.

How to Use SRS

The following steps correspond to the numbered points on the flowchart on page

1-4. Detailed descriptions and operating instructions are in Chapters 2 through 4.

First you will set up the SRS module and Buyer Contract files by:

1.1. Turning on the SRS module:

• Enabling the Using Buyer Contracts option.

• Creating system codes for shipping schedules.

• Creating carrier codes if you are using 856 (Advance Shipping

Notification) transactions.

2.2. Entering prerequisite information in the Buyer Contract files that will be

used in subsequent SRS processing:

• Creating customer groups, which are user-defined names to

represent one or more customers. They are used for internal order

processing. Then assigning customers to the corresponding group.

1 - 2 FPD/319-03

OVERVIEW OF SRS

• Entering approved items and purchase orders for each group. This

means all items for the group, not for each customer.

• Combining each customer, items, and shipping schedule.

Then you will import your customer’s shipping requirements/transactions by:

3.3. If you are using EDI:

• A PC is required to receive the EDI transactions from the EDI

provider. It must be connected to your FASPAC system.

• Downloading new EDI data to your EDI PC, creating an ASCII

file and purging previously processed EDI files. This involves

using software appropriate for the chosen Value Added Network

(VAN). This process is not a FASPAC function.

• Importing the EDI data by transferring the ASCII file from the

EDI PC to FASPAC.

• Translating the EDI data to FASPAC files. There are two files that

maintain this data, one for the 862 firm transactions and the other

for the 830 planned transactions.

4.4. If you are not using EDI:

• Creating manual releases using the SRS programs.

• These releases are also included in the planned and firm files.

5.5. Using the FASPAC TPIM inquiry program to view the purchasing and

planning information for one or more warehouses. This includes both

manual releases and EDI transactions. If you are a manufacturing

customer, use the MFPP program.

Finally, you will process the shipping requirements by:

6.6. Creating a temporary quote for the entire customer group. You can

automatically commit tags to the quote FIFO if the WCS option is set

to Y.

7.7. Creating individual quotes from the temporary quote for each individual

customer, item, plant, and PO number. The lines on the temporary quote

are automatically deleted as the individual quote is being created.

8.8. In Order Desk, you can refer to the PLO report for the necessary

information to resume the quote and turn it into an order. You can also

enter individual orders to update the Buyer Contract files.

9.9. Running the Shipping Confirmation program to update the shipped fields

in the Buyer Contract files.

10.10. Running the Invoice Calculation program to update the invoiced fields in

the Buyer Contract files.

FPD/319-03 1 - 3

HOW TO USE SRS

1 - 4 FPD/319-03

OVERVIEW OF SRS

SYS/OPT/BCSTurn on th e S RS

mo d ule

ODConvert the quote

to a n order

PLFMCreate tempora ryquot e for e nt ire

buye rgroup

TP IM or MFP PView all

purchasing andp la nn in g data

S RSRequ ire ment

Fi les

Manua l Rel e aseEnt ry

Cre at e manualrele ases if you are

n ot using EDI

Your Customer 's PC Yo ur E DI PC

EDI So ft ware

Ele ctr onicMail Box

REDIRet riev e EDItra ns ac ti ons(A SCII file )

FASP AC EDIData File

EDI DTran sla te ASCIIfi le to FASPAC

EDI file

A ud it File

EDI Errors Rep ort

Buyer ContractFiles

BCCRCreate custo mer

and ship- tolocati on

PLOCreate a quote for

the in d ividua lcust omer/p la nt

location

PL O Repo rt

Bu yer Co ntra ctFiles:

La st Shippedand L ast

In voiced fie ld s

SCINC

Per form typic alFASPAC order

proce ssing

Download E DItr an saction d at a

2

3

4 5

68

Set Up BuyerContract Fi les

Value Added Network

Elec tro ni cMail Box

BGIMCrea te item sf or

cus tome r

BCI MLin k BG IM i temsto plant/s hip-to

locati on

79 & 10

1Set Up SRS

Module

SYCDCreate s ystem

c od es for shippingschedules

BGCM/CCFMFor 856

transa ctions, ente rc arrier code s

2Setup

This chapter provides the procedures you must follow to set up

the Scheduled Release Subsystem (SRS).

This process consists of the following tasks:

• Defining the system parameters:

– Turning on the SRS module in Buyer Contract Specifications

(SYS/OPT/BCS).

– Creating system codes for shipping schedules in System Code

Maintenance (SYCD).

– If you are using 856 (Advance Shipping Notification) transactions,

entering carrier codes in Carrier Codes File Maintenance

(BGCM/CCFM).

• Creating the Buyer Contract database files:

– Entering information for customer groups in Buyers Customers Cross

Reference Maintenance (BCTS/BCCR/MAI).

– Entering item information for the contract in Buyers Group Item

Maintenance (BCTS/BGIM/MAI).

– Entering item information for specific customers, ship-to locations, and

PO numbers in Buyers Customer Item Maintenance

(BCTS/BCIM/MAI).

Reminder: Screen illustrations are samples only—yours will vary according to

your system and how it is set up.

FPD/319-03 2 - 1

Define System Parameters

The first thing you must do is define the system parameters that will allow you to

use the Scheduled Release Subsystem.

Buyer Contract Specifications (SYS/OPT/BCS)

Use this program to turn on the buyer contract system and create notes in quotes

and orders that will print on both pick lists and invoices.

You will be able to update the Buyer Contract files if you create orders in Order

Desk using the F6 and F11 options.

Working with the Screen

The following are instructions for entering data in this screen. Detailed field

explanations follow this section.

Reminder: After you type an entry in a field, press Return.

To turn on SRS:

1.1. From a FASPAC menu, enter BCS.

The cursor starts in the SELECT prompt.

2 - 2 FPD/319-03

SETUP

2.2. Enter the number of the item you want to change.

The cursor moves to the selected field.

3.3. Enter Y or N.

The cursor returns to the SELECT prompt.

4.4. Repeat steps 2 and 3 for other fields you want to change.

5.5. When finished, press CMD or SKIP to exit the program.

Field Explanations

01 Using Buyer Contracts

Y = Turn on the Buyer Contract System. An order that is entered in OD

using the F6-Alternate Customer and F11-Alternate Item function keys

will be included in the Buyer Contract system.

02 Create Release Note Line

Y = Print the Release Number from the EDI transaction only. This does

not apply to manual releases.

03 Create Short Name Note

Y = Print the short name from IM/MAI.

04 Create Alt. Part Note

Y = Print the customer part number from field 10 Cust Alt Item in

BCIM. If there is no customer part number in BCIM, it prints the

customer part number from field 11 Cust Item No in BGIM.

NOTE: The customer cross-reference number from CR/MAI is not used.

05 Create Comment Note Line

Y = Print the comment entered in BCIM. If there is no comment in

BCIM, it prints the comment from BGIM.

06 Create Line Feed Note

Y = Print the Line Feed from the EDI transaction.

The Line Feed is the dock and bin location for the appropriate assembly

line to which the product should be stocked or delivered.

07 Adjust Quantity To Minimum

Y = If a user enters a quantity required that is less than the minimum ship

quantity specified in in BCIM (field 06 Min. Ship Qty), the EDI and

manual posting programs will increase the quantity required to match the

BCIM minimum ship quantity.

FPD/319-03 2 - 3

BUYER CONTRACT SPECIFICATIONS (SYS/OPT/BCS)

Note Lines

There are certain rules about the note lines:

• The system automatically prints the Purchase Order number on the first

note line. This is not an option.

Caution! The PO note line is mandatory as it is used to update the cumulatives.

This must not be deleted manually.

• The first field indicated with Y will be the second note line. The second

field indicated with Y will be the third note line, etc. These note lines are

always in order.

• The last note line is system-generated and used for internal FASPAC

processing only. It does not print but is displayed on the Order

Confirmation screen in Order Desk and Quote Maintenance. The note type

is W *OPCSO.

NOTE: This information is used to create the order header when resuming the

quote. The customer Ship To code is included in this infomation, so it is

important the user does not manually change or delete this note line.

2 - 4 FPD/319-03

SETUP

System Code Maintenance (SYCD)

Use this program to set up codes for shipping schedules. You only need to create

the shipping schedules required by your Trading Partner agreements.

The required record types, which are not displayed on the screen, are WS

(Weekly Ship) and DS (Daily Ship).

If you are using EDI, you must also set up a code for IT (Operator Initials) of

EDI.

Record Types and Codes

The following Table 2-1 lists the valid codes for the record types.

Note: The descriptions for both record types of WS and DS must be entered as

shown. Example: D cannot be Tuesday; it must be Monday.

FPD/319-03 2 - 5

SYSTEM CODE MAINTENANCE (SYCD)

Table 2-1. Record Types and Codes

Record type (RT) Code Description

WS (Weekly Ship) W Weekly shipments

1 Ship the first week of the month

2 Ship the second week of the month

3 Ship the third week of the month

4 Ship the fourth week of the month

5 Ship the fifth week of the month

6 Ship the first and third weeks of the month

7 Ship the second and fourth weeks of the month

DS (Daily Ship) D Monday

E Tuesday

F Wednesday

G Thursday

H Friday

J Saturday

K Sunday

O DAILY, Monday through Friday

(Note: For EDI transactions, this code will splitthe scheduled quantity equally over five days. Formanual releases, it will schedule the entirequantity on the day entered when creating themanual release.)

S ONCE anytime Monday through Friday

(Note: Grey indicates codes only available forEDI transactions; this is not applicable to manualreleases.)

P ½ Monday, ½ Thursday

Q ½ Tuesday, ½ Thursday

R ½ Wednesday, ½ Friday

T ½ Tuesday, ½ Friday

U ½ Monday, ½ Wednesday

V 1/3 Monday, 1/3 Wednesday, 1/3 Friday

IT EDI EDI Transaction

2 - 6 FPD/319-03

SETUP





To set up codes for shipping schedules:

1.1. From a FASPAC menu, enter SYCD.

The cursor starts in the CO field.

2.2. Press Return to accept the default company number, or enter another

company number.

The cursor moves to the RT field.

3.3. Enter WS. The cursor moves to the Code field.

4.4. Enter a Weekly Ship Code from the above table (such as W). The cursor

moves to the Description field.

5.5. Enter the description for the code. The cursor moves to the Amount field.

6.6. Leave the field blank and press Return. The cursor returns to the RT

field.

7.7. Repeat steps 3 to 6 for more Weekly Ship Codes.

8.8. Enter DS. The cursor moves to the Code field.

9.9. Enter a Daily Ship Code from the above table (such as O). The cursor

moves to the Description field.

10.10. Enter a description for the code. The cursor moves to the Amount field.

11.11. Leave the field blank and press Return. The cursor moves to the RT

field.

12.12. Repeat steps 8 to 11 for more Daily Ship Codes.

13.13. Enter IT. The cursor moves to the Code field.

14.14. Enter EDI. The cursor moves to the Description field.

15.15. Enter EDI Transaction. The cursor moves to the Amount field.

16.16. Leave the field blank and press Return. The cursor returns to the RT

field.

17.17. Press CMD+Q to exit the program.

Reminder: The plus (+) sign means to press these keys consecutively, not

simultaneously. Press CMD and release the key, and then press Q and release the

key.

FPD/319-03 2 - 7

SYSTEM CODE MAINTENANCE (SYCD)

Define the Buyer Contract Database

The Buyer Contract (BCTS) database maintains all of the pertinent information

for the scheduled releases. This includes the customer group, purchase order

number, contract date range, approved items, delivery pattern, and cumulative

quantities shipped and invoiced from FASPAC.

Use these programs to initially configure the BCTS database files:

• Buyers Customers Cross Reference Maintenance

(BCTS/BCCR/MAI)—Create customer groups and assign the customers

to them.

• Buyers Group Item Maintenance (BCTS/BGIM/MAI)—Enter the

items that are approved for the customer groups.

• Buyers Customer Item Maintenance (BCTS/BCIM/MAI)— Enter the

allowable ship-to locations for specific POs for the customer, items, and

customer groups.

2 - 8 FPD/319-03

SETUP

Buyer Customer Cross Reference Maintenance(BCCR/MAI)

Use this program to define and maintain customers in customer groups. A group

can consist of one or several customers.

There are three ways to cross-reference customer plants (ship-to or plant

locations).

• FASPAC identification of a plant = “Customer No” and “Ship To No”

fields

• Generic identification of a plant = “Their Cust No.” field

• EDI identification of a plant = “13 EDI Account No.” field

A customer group is used to create a temporary quote in Pull List File

Maintenance (SHP/SHC/PLFM). It is important to understand and give this some

thought before you create the groups.

• You may want to create a group called MISC for several customers, or a

group that would indicate each customer separately.

• The group will dictate the size of the quote created when generating the

temporary quote.

• PLFM can only be run once for a group and date.

• The group name can be up to four characters. The fifth character is used

by the system.

FPD/319-03 2 - 9

BUYER CUSTOMER CROSS REFERENCE MAINTENANCE (BCCR/MAI)




When you run the program and SRS has not been not turned on in Buyer

Contract Specifications (SYS/OPT/BCS), the following message will be

displayed at the bottom of the screen:

SYS/BCS Parameter Not Set

Press SKIP, run BCS, and set field 1 to Y.

Reminder: After you type an entry, press Return.

To create a customer group:

1.1. From a FASPAC menu, enter BCCR/MAI. The cursor starts in the

Customer No. field.

2.2. Enter the customer number. The cursor moves to the Ship To No. field.

3.3. Enter the customer’s ship-to code if applicable or press return.

The cursor moves to the Their Cust No. Field and the address

information is changed accordingly.

4.4. Enter a generic description or identification for the plant. We recommend

entering the name your customer uses for the ship-to location.

The cursor moves to the Cust Group field.

5.5. Enter the customer group ID, up to a maximum of four characters. The

following message is displayed at the bottom of the screen:

Are You Creating A New Customer Cross Reference

For This Customer? (Y/N)

Enter Y.

The remaining fields on the screen display defaults from Customer

Processing Maintenance (CP/MAI), and the cursor moves to the

SELECT prompt.

You can change any of these fields as necessary for the contract.

6.6. Enter the number of the item you want to change. The cursor moves to

the selected field.

7.7. Change the entry. The cursor returns to the SELECT prompt.


2 - 10 FPD/319-03

SETUP

CMD+L

CMD+L

9.9. If applicable, press F1 to display the second screen and enter truck

times/days or specify one PO per order. See page 2-17.

10.10. When finished in the second screen, press F1 to return to the first screen.

11.11. When finished, press SKIP to exit the program.

To delete a customer group:

NOTE: Deleting the customer group will also delete the BCIM record. It does

not delete the BGIM record.

1.1. From a FASPAC menu, enter BCCR/MAI. The cursor starts in the

Customer No. field.

2.2. Enter the customer number. The cursor moves to the Ship To No. field.

3.3. Enter the customer’s ship-to code. The information for this customer is

displayed and the cursor moves to the SELECT prompt.

4.4. Enter DE. The following question is displayed at the bottom of the

screen:

Are You Deleting This Customer Ship To Location

And Any Items And Item History

That May Have Been Setup? (Y/N))

5.5. Enter Y to delete the customer location, items, and item history.

6.6. Repeat steps 2 to 4 for other customers.


Field Explanations

Customer No

The customer number that is maintained in Customer Processing

Maintenance (CP/MAI). This is half of the FASPAC identification of a

plant, dock, or ship-to location.

Ship-to No

The ship-to code that is maintained in Customer Processing Ship To

Maintenance (CP/STM).

Note: You must enter a valid Faspac ship to code or return for no ship to.

SAME is not a valid ship to response.

Their Cust No.

The generic identification of the plant. We suggest the name of the

ship-to location your customer uses.

FPD/319-03 2 - 11


For example, the ship-to code is 001, but the customer refers to this

ship-to location as the Temecula location.

Cust Group

Caution! The system will automatically create a customer record in

CP/MAI when a customer is assigned to a Customer Group. Do not

delete this customer number from CP/MAI. (The customer number is the

group code plus a 9).

The customer group ID can be up to four characters. Remember this will

dictate the size of temporary quote created when PLFM is processed. The

group can indicate all customers, several customers, or each customer

individually.

We suggest you use a shortened, meaningful name that makes sense to

everyone in your company (in our example, HOND for HONDA).

The customer group is part of the key in BCTS, which, together with the

EDI Account Number and EDI Dock Number, identifies the sender of

the incoming EDI document.

The following error message is displayed if their customer number and

customer group was assigned to a different customer number and ship to

number.

Their Customer No. And Group Is Already Assigned

To Faspac Customer XXX And Ship To Number XXX.

Press Return To Reenter Information

01 Name through

09 Country

The customer’s address information.

10 Bus Phone

11 Bus Contact

We suggest using the number and name of the primary customer contact

for the buyer contact.

12 Comment

This field is for information used on this screen only. It is not used in any

other program or report.

13 EDI Account No.

A unique number that identifies a plant and is verified with the incoming

EDI data. It is defined as part of the Trading Partner information and is

contained in the EDI document.

Note: One of our EDI programmers will help you with the correct EDI

account number.

2 - 12 FPD/319-03

SETUP

EDI Dock No.

Within a plant, if there is more than one shipping location for the same

EDI account number, use this field to identify the more specific ship-to

location. It must match the field on the EDI document exactly.

Each combination of an EDI Account Number and Dock Number is a

unique FASPAC Ship-To.

Note: If there are unique EDI account numbers for each ship to, no dock

code is needed.

15 EDI Vendor No.

This number indicates your company as the vendor to your customer on

the 856 document. It is unique for each customer and is specified by your

customer.

This is only applicable if you are using the 856 or ASN (Advance Ship

Notice) transaction to your customer, confirming that a shipment is in

process (that is, the shipment has left your dock and is en route).

16 P/O Modifier

A suffix that is added to a PO number for EDI transactions. The PO

number on an incoming EDI document is validated in BGIM in one of

two ways.

N = Each PO number will be unique.

Y = The PO numbers will always start with a common prefix. The cursor

moves to the Size field to the right

Size

The number of characters in the PO suffix or modifier. It is important to

realize potential problems if the size field is changed. They are discussed

in the following example.

How it works:

For the incoming EDI data, the PO is first validated in its entirety (the

whole PO number).

If no match is found in BGIM and there is a PO suffix, the suffix is

ignored and a match on the “core” portion of the PO is assessed.

If the match is successful, it is considered a valid PO.

Example:

The PO numbers are 59a through 59z.

Enter Y in the P/O Modifier field and 1 in the Size field.

When the system sees 59a, it checks the PO number field in BGIM. If it

is also 59a, the match is successful and the suffix is not used.

FPD/319-03 2 - 13


If the PO number field in BGIM is 59, the system checks the size field

and drops the appropriate characters from the right. Therefore, for PO

59a, there is no match, the Size is 1—the system drops the “a” and the

field now matches the PO number.

Refer to the “P.O. No.” field explanation in Buyers Group Item

Maintenance (BCTS/BGIM/MAI) on page 2-25.

Caution: It is important to realize the potential problems if the Size field

is changed. Continuing with the above example, the Size field is now

changed to 2 because 59a through 59z have been used and now your

customer wants to use 59aa through 59zz. If the PO number of 59w is to

be used after the Size field is changed to 2, the match wound not be

successful— the system would drop two characters and the PO number

would become 5 instead of 59.

17 Adv Ship Days

How many future days will be included in the shipping requirement. The

number of days can be thought of as the lead time.

For EDI transactions, the EDID program uses this field.

For manual releases, BCIM/MAI uses this field when the release is

entered.

Note: This field is only used if field 17 Adv Ship Days in BCIM/MAI is

blank.

There are two parts to calculating the actual ship date:

• The customer due date less the advance ship days

• The daily ship code schedule in BCIM

Example:

(Note that Saturdays and Sundays are included when calculating advance

ship days.)

The customer requires delivery by Monday, November 1.

The advanced ship days = 4.

The first calculated ship date = Thursday, October 28.

If the daily ship schedule is for Friday, the actual ship date would then be

Friday, October 29.

If the daily ship schedule is for Tuesday, the actual ship date would then

be the following Tuesday, November 2 (that is, it would be a late

shipment).

2 - 14 FPD/319-03

SETUP

18 Only Ship From 862

Y = Only allow 862 (firm) transactions to request a shipment.

N = Accept both 862 and 830 (planning) transactions to request a

shipment (see page 1-2 for more information). This is the default.

19 Use Pull Method

A flag that tells the Pull List File Maintenance (OP/SHP/SHC/PLFM)

program what quantities are to be shipped.

W = Whole cartons only and will round up

P = Partial cartons first, then whole cartons

A = Whole cartons first, then all partial cartons

E = Exact quantity ordered will be shipped using whole cartons first. The

inventory will be relieved FIFO.

Note: The Pull Method is applicable for EDI transactions. The rounding

of these occurs during the EDID process. Manual transactions will only

be included if you are committing tags.

How it works:

The tag record (TAG/INQ) controls the carton or container status. If the

“Container Qty” field is 0 or spaces, it will be considered a partial carton.

If there is a quantity in the “Container Qty” field, it is considered a whole

carton.

This information is maintained during receiving or assigning tag

locations in RPO, RNO, or ATL.

The quantities in carton or container are customer specific defined in

BCIM. See page 2-36, fields 7 and 8.

For example:

A customer ordered 76 and BCIM indicates there is 25 in a carton.

In the buy history for status 2 tags, there are five full cartons of 25, one

partial carton of 13, one partial carton of 12, and one partial carton of 2.

The full cartons are the last ones received and the partial carton of 2 was

the first received.

If you enter W (whole cartons only and will round up), the system will

actually ship four cartons, or a quantity of 100.

If you enter P (partial cartons first, then whole cartons), the system will

actually ship partials cartons 13, 12, and 2, and two whole cartons of 25.

The total quantity being shipped is 77. This option is only available if

you are committing tags; if not, it will operate the same as option W.

If you enter A (whole cartons first, then all partial cartons), the system

will ship four whole cartons because it will round up, plus all remaining

partial cartons. Using the above example of status 2 tags, this order

FPD/319-03 2 - 15


would ship a total quantity of 127. This option is only available if you

are committing tags; if not, it will operate the same as option W.

Note: Committing tags is indicated through the WCS option.

If you entered E (exact quantity ordered will be shipped using whole

cartons first), the system will ship three whole cartons plus one piece for

a total of 76. Since the inventory is relieved FIFO, the one piece will

come from the quantity 2 tag.

20 Control Source

Optional. Your customer will provide this code if it is to be printed on

the ASN (856 transaction). It is not used anywhere else in FASPAC. This

is information the receiver may need for matching.

21 Cum Adj

Y = The system automatically makes an adjustment for over/shortage

based on the cumulative on the next shipment (that is, it keeps track of

what has been shipped). The next shipment would then be accurate in

accordance with the EDI requirement. This is the default.

N = The system will only ship the quantity that is scheduled through the

EDI translation process. It will not consider the cumulative to date.

Note: We recommend you initially set this field to null or N until the

cumulative adjustment quantities are correct.

22 Firm Fab

The 830 planning schedule includes a fabricated quantity, which is a

guaranteed quantity of what will be purchased on the contract.

Y = If a planning transaction is received from the EDI process and the

planned quantity plus the cumulative totals equal the fabricate number, it

will automatically become a firm request.

N = A planned order will never be turned into a firm order. This is the

default

For example:

The cumulative to date is 26,000 and the fabricate number is 30,000.

The next three weeks have firm orders of 1,000, so now the cumulative

to date will be 29,000.

The fourth week is a planned order of 1,000. With this planned order it

would total the fabricate quantity, so this flag would turn the 1,000

planned order into a firm order.

The contract will still continue after the fabricate quantity has been met.

2 - 16 FPD/319-03

SETUP

BCCR/MAI, Screen Two

This screen is optional. Use it to enter truck times and days if you will be running

the Pull List (OP/SHP/SHC/PL) program, or if you want to designate one PO per

order.



explanations are on the next page.

Reminder: After you type an entry, press Return.

To enter a truck schedule:

1.1. This screen is displayed when you press F1 in the first MAI screen.

The cursor starts in the SELECT prompt.

2.2. Enter the line number of the truck time day. The cursor moves to the

selected field.

3.3. Enter the time in military format. The cursor returns to the SELECT

prompt.

4.4. Repeat steps 2 and 3 for other days.

5.5. When finished, press F1 or SKIP to return to the first screen. The cursor

starts in the Customer Number field in the first screen.

FPD/319-03 2 - 17


Field Explanations

Truck Time Mon.

Through

Truck Time Sun.

The time, in military format, on the appropriate days when your

customer will arrive at your location to pick up their shipment.

This information is only used for the truck time options for the pull list or

hot sheet using SHC/PL.

09 One PO Per Order

Y = Create only one PO on an order (that is, include all items for one

PO).

N = Several PO numbers will be on the same order. This is the default.

Reminder: The PO number is a note line for all items on orders created

from EDI transactions or manual releases.

Last Received Date Time

830

862

Displays the actual date and time when the EDI order was processed in

EDID.

2 - 18 FPD/319-03

SETUP

Carrier Codes File Maintenance(BCTS/BGCM/CCFM)

This program is only applicable for 856 (Advance Shipping Notification)

transactions. Use it to define a carrier code for the shipping method you will be

using to ship the items to your customers.

This code is used as the default Carrier code in the Buyer Customer Item

Maintenance (BCTS/BCIM/MAI) program and can be changed when you enter

an 856 transaction.





To enter a new code:

1.1. From a FASPAC menu, enter CCFM. The cursor starts in the Cust Group

field.

2.2. Enter the Customer Group code that you will be creating in Buyers

Customers Cross Reference Maintenance (BCCR/MAI). The cursor

moves to the Carrier Code field.

FPD/319-03 2 - 19

CARRIER CODES FILE MAINTENANCE (BCTS/BGCM/CCFM)

3.3. Enter a code that represents the shipping method. The following question

is displayed at the bottom of the screen:

Are You Creating A New Carrier Record For This

Group? (Y/N)

4.4. Enter Y. The cursor moves to the SELECT prompt.

If you enter N, the cursor returns to the Carrier Code field where you can

enter a different code or exit the program.

Now you can enter carrier information, such as the carrier’s address and

appropriate transportation codes. See the Field Explanations.

5.5. Enter the number of the item you want to change. The cursor moves to

the selected field.

6.6. Enter the information. The cursor returns to the SELECT prompt.



To delete a code:

1.1. From a FASPAC menu, enter CCFM. The cursor starts in the Cust. Group

field.

2.2. Enter the Customer Group code. The cursor moves to the Carrier Code

field.

3.3. Enter the Carrier Code. The cursor moves to the SELECT field.


screen:

You Are About To Delete This Carrier Code Are You

Sure? (Y/N) N

5.5. The default is N. Enter Y to delete the code. The cursor returns to the

Cust. Group field.

6.6. Repeat steps 2 to 5 for other codes you want to delete.


Field Explanations

Carrier Code

Your code that will represent a certain carrier. We suggest you keep a

manual list of codes since they are not stored in a file to display or print.

01 Name through 11 Bus Contact

The carrier’s address, phone number, and business contact.

2 - 20 FPD/319-03

SETUP

12 SCAC Code

Optional. The Standard Carrier Alpha Code, supplied by the carrier. You

can also obtain the master list of SCAC codes from the Department of

Transportation.

13 Pool Code

Optional. A code for a carrier pool, for your internal use. This is optional

and will be included on the ASN.

14 Trans. Method

Optional. How items are shipped (such as air or rail).Your customer will

provide this code if it is to be printed on the ASN.

15 Conveyance Cd

Optional. What kind of equipment is to be used when shipping the items

(such as box car or pickup truck). Your customer will provide this code if

it is to be printed on the ASN.

FPD/319-03 2 - 21

CARRIER CODES FILE MAINTENANCE (BCTS/BGCM/CCFM)

Buyer Group Item Maintenance (BCTS/BGIM/MAI)

Use this program to indicate which items are approved on a PO within a date

range for a specific customer group. The customer groups were created in Buyers

Customers Cross Reference Maintenance (BCCR/MAI).

You can associate the same item numerous times with different PO numbers.

You can also duplicate the same item and PO number, but with a different

reference number (such as for a model year).





To associate an item with a customer group:

1.1. From a FASPAC menu, enter BGIM/MAI. The cursor starts in the Cust.

Group field.

2.2. Enter the Customer Group ID. The cursor moves to the Item No. field.

3.3. Enter the FASPAC item number. The cursor moves to the Reference No.

field.

4.4. Enter an optional alphanumeric reference number or leave the field

blank. The cursor moves to the P.O. No. Field.

2 - 22 FPD/319-03

SETUP

CMD+L

CMD+L

5.5. Enter your customer’s PO number. The following question is displayed

at the bottom of the screen:

Is This A New Item Being Setup For This Group?

(Y/N)

6.6. Enter Y. The cursor moves to field 01 U/M.

7.7. The default unit of measure comes from IM/MAI. Check that it matches

what your customer has specified in the contract and change it if

necessary.

8.8. The cursor moves to field 02 Current Price.

9.9. Enter the price your customer will pay for this unit of measure. The

cursor moves to field 03 Previous Price.

10.10. Press Return through fields 03, 04, and 05. The cursor moves to field 06

Buyer.

11.11. Enter the name of the contract buyer for reference purposes, or leave the

field blank. The cursor moves to field 07 Controlling.

12.12. Press Return. The cursor moves to field 08 Start Date.

13.13. Enter the starting date of the contract. The cursor moves to field 09 End

Date.

14.14. Enter the ending date of the contract. The cursor moves to field 11 Cust

Item No.

15.15. Enter your customer’s part number. The cursor moves to field 12

Comment.

16.16. Enter an optional comment. 13 Commodity Code.

17.17. Enter the optional ASN commodity code provided by your customer.

TThe cursor moves to field 14 Fob Code.

18.18. Enter the optional ASN FOB code provided by your customer. The

cursor moves to field 15 User Defined 1.


To Be Purged.

20.20. Enter N. The cursor moves to field 19 P/O Suffix.

21.21. Press Return. The cursor moves to the SELECT prompt.

22.22. If necessary, make corrections to the fields.

23.23. You do not need to go to the second screen. It displays Invoice/PO

information that is system-generated during invoicing.

24.24. Press F5 to save the record and display the Buyer Customer Item

Maintenance (BCTS/BCIM/MAI) program (see page 2-28).

25.25. If you want to save the data and exit the program, press CMD+U.

Caution! CMD+Q will not save the last record entered.

FPD/319-03 2 - 23

BUYER GROUP ITEM MAINTENANCE (BCTS/BGIM/MAI)

CMD+L

To delete a record:

1.1. From a FASPAC menu, enter BGIM/MAI. The cursor starts in the Cust.

Group field.

2.2. Enter the Customer Group ID. The cursor moves to the Item No. field.

3.3. Enter the FASPAC item number. The cursor moves to the Reference No.

field.

4.4. Press CMD+L and then press Return on the record you want to delete.

The record is displayed and the cursor moves to the SELECT prompt.

5.5. At the SELECT prompt, enter DE. The following question is displayed at

the bottom of the screen:

Do You Want To Delete This Item From This Group

And Any History? (Y/N)

6.6. Enter Y to delete the item.

7.7. Repeat steps 2 to 6 for other records you want to delete.

8.8. When finished, press CMD+Q to exit the program.

Field Explanations

Cust. Group

The customer group ID that was created in BCCR/MAI.

After an item has been created, both the customer group and item will be

displayed when you press CMD+L. The full record is displayed, not just

what the field indicates. This is true with all fields except the Item No

field. That will display just the FASPAC items as normal.

Item No.

The FASPAC item number defined in IM/MAI.

Description

The default Item Description comes from IM/MAI.

Short Name

The default Alternate item name comes from IM/MAI.

Reference No.

Reserved for future use, but you can use it for information only. You can

use a reference number to distinguish an item that has been created with

the same PO number.

2 - 24 FPD/319-03

SETUP

CMD+L

CMD+L

P.O. No.

This PO number will be validated by incoming EDI transactions

processed by the EDID program.

Enter only the base PO number if field 16 in BCCR/MAI specifies that a

PO modifier is to be used for this customer group.

If a modifier is not to be used, enter the entire PO number.

Note: Do not change the PO number here because it is the key FASPAC

uses for that record. Use Group Item Copy (BGIM/CPY), described on

page 5-6.

01 U/M

The UOM from IM/MAI is displayed. You can change it, but it must

match the EDI information from EDID.

02 Current Price

The contract price for the customer per field 01 UM.

03 Previous Price

04 Oem I.D.

05 Asn Type

These fields are reserved for future use.

06 Buyer

The name of the contract buyer (such as the name of the group’s buyer).

This is for reference only, and not used anywhere in FASPAC.

07 Controlling

Reserved for future use.

08 Start Date

09 End Date

The date when the purchase order will begin to be effective and when it

is due to terminate.

If an EDI transaction outside the date range is encountered, a

WARNING message is printed on the EDID Pull List Transaction

Summary Report. The transaction data will still be carried forward to

create requirements in FASPAC.

Note: This error will not stop further processing, so PLFM will still

create quotes, which will eventually become orders, regardless of this

date.

FPD/319-03 2 - 25


11 Cust Item No.

The customer’s item number on the incoming EDI transaction.

The system matches this item number against the number in the

incoming EDI transaction. If no match is found, it is assumed the

incoming number is a FASPAC cross-reference number, and an attempt

is made to match it as such. If no match is found, it assumes the item

number is a FASPAC item number and searches for it.

Note: If no match is found, an error message will print on the EDID Pull

List Transaction Summary Report. The transactions for this item will not

be carried forward to create requirements in FASPAC, until the item is

created in this screen.

This Cust Item number will print as a note line if:

• Field 04 Create Alt Part Note in Buyer Contract Specifications

(SYS/OPT/BCS) is set to Y.

• Field 10 Cust Alt Item (BCIM/MAI) is spaces.

The following message is displayed at the bottom of the screen when a

customer item number is entered that is already in use:

ERROR A Different Item Exists on File

12 Comment

Optional user-defined text. This comment will print as a note line if:

• Field 05 Create Comment Note Line in Buyer Contract

Specifications (SYS/OPT/BCS) is set to Y.

• Field 11 Comment in Buyer Customer Item Maintenance

(BCIM/MAI) is spaces.

13 Commodity Code

Optional. Your customer will provide this code if they want it to print on

the ASN (856 transaction).

14 Fob Code

Optional. Your customer will provide this code if they want it to print on

the ASN (856 transaction).

The code must exist in SYCD as Record Type FO.

The FOB code will not automatically be prompted because this program

is for a group of customers, not a specific customer.

15 User Defined 1

16 User Defined 2

17 User Defined 3


2 - 26 FPD/319-03

SETUP

18 To Be Purged

Do you want to be able to manually enter an order in Order Desk and

have it be included in the Buyer Contract system.

The order can be entered in OD using F6 and F11.

Y = F6 and F11 cannot be used in OD.

N = F6 and F11 can be used to create an order in OD, and have it

included in the Buyer Contract system. This is the default.

This does not pertain to a manual release or an EDI transaction. This flag

will not prevent these orders.

19 P/O Suffix


Function Keys

F1-Next Screen

Displays the quantity, date, customer, ship-to, and invoice number of the

most recent invoiced shipment of this item, to any customer ship-to

within this group. It also displays the total quantity of this item invoiced

to all locations within this group, as well as the total value and cost.

These fields are updated by Invoice Calculation (INC).

These fields should not be maintained manually, unless instructed by a

Faspac representative.

See page 5-5 for an example of this screen.

F5-Update Item And Assign Or Change Customer Info.

The data entered is updated and the BCIM/MAI screen is displayed (see

the next page).

FPD/319-03 2 - 27


Buyer Customer Item Maintenance(BCTS/BCIM/MAI)

Use this program to define and maintain the ship-to or plant locations for

approved items on a purchase order for a group of customers. That is, which

customers can buy this part, and to which plant or ship-to location are the items

to be shipped.

You also use this program to create a manual release if orders are not

electronically transmitted using EDI (see page 3-37).

When your customer tells you they will be clearing their cumulative quantities at

year end, you can clear their cumulative quantities in FASPAC by using the F5

function when you first run the program.

The second screen of BCIM displays the most recent shipped and invoiced

information for an item to a particular ship-to or plant location. The cumulative

totals and last shipped information is also displayed.

You can access this program from the menu or by pressing F5 from Buyers

Group Item Maintenance (BGIM/MAI). If you came from BGIM/MAI, pressing

CMD+Q here returns to that program.

2 - 28 FPD/319-03

SETUP



explanations start on page 2-32.


When you access this screen from BGIM/MAI by pressing F5, the appropriate

information in the first five fields will be displayed and the cursor starts in the

Customer No. field.

When you run the program from a menu, the cursor starts in the Cust. Group

field and you have to re-enter the same information in the first five fields that you

entered in BGIM/MAI.

To define a ship-to or plant location:

1.1. These instructions assume you pressed F5 from BGIM/MAI.

2.2. In the Customer No. Field, enter the number of the customer that has

been assigned to this group. The cursor moves to the Ship To No. field.

If you enter a customer number and ship-to combination that has not

been linked to the customer group, the following error message will be

displayed:

Customer Has Not Been Assigned To This Group. Must

First Do This—SKIP

Use BCCR/MAI to create this record. See page 2-9.

3.3. In the Ship To No. field, enter the FASPAC ship-to number you created

for this customer.

The following question is displayed at the bottom of the screen:

Is This A New Item Being Setup For This Customer?

(Y/N)

4.4. Enter Y. The cursor moves to field 01 Start Date.

If you enter N, the cursor returns to the Customer No. field where you

can start over or exit the program.

5.5. Enter the starting date for this contract if it is different from the date you

entered in BGIM/MAI. The cursor moves to field 02 End Date.

6.6. Enter the ending date for this contract if it is different from the date you

entered in BGIM/MAI. The cursor moves to field 03 Weekly Ship.

7.7. Enter the weekly code. Do not leave this field blank. The cursor moves

to field 04 Daily Ship.

FPD/319-03 2 - 29

BUYER CUSTOMER ITEM MAINTENANCE (BCTS/BCIM/MAI)

CMD+L

CMD+L

8.8. Enter the daily code. Do not leave this field blank. The cursor moves to

field 05 ASN Required.

9.9. Press Return. The cursor moves to field 06 Min. Ship Qty.

10.10. Enter the minimum quantity to be shipped, if applicable. The cursor

moves to field 07 Container Qty.

11.11. Enter the number of items that will be in a container. The cursor moves

to field 08 Container Type.

12.12. Enter the type of container. The cursor moves to field 09 Dock Info.

13.13. Press Return. The cursor moves to field 10 Cust. Alt Item.

14.14. Enter the customer’s alternate part number, if applicable. The cursor

moves to field 11 Comment.

15.15. In enter comments you may have for this record. The cursor moves to

field 12 Carrier Code.

16.16. Enter the carrier code you defined in CCFM. The cursor moves to field

13 User Defined 1.

If you enter a code that has not been defined, the following message is

displayed:

Carrier Code Has Not Been Setup Yet - SKIP.

Press SKIP

Create the code in CCFM and then enter it here.


To Be Purged.

18.18. Press Return to accept the default of N. The cursor moves to field 17 Adv

Ship Days.

19.19. Enter the lead time in days, if applicable. The cursor moves to field 18

Cum Qty Req’d.

20.20. Press Return. The cursor moves to the Model Year field.

21.21. Press Return. The cursor moves to field 19 Active P.O.

22.22. Enter Y. The cursor moves to the SELECT prompt.

23.23. Make changes to any fields, if necessary.

24.24. Press F1 to display the second BCIM screen. Go to page 2-40.

To clear cumulative quantities at year end:

Caution! Invoicing must be done before the cums are cleared.

1.1. In the Cust. Group field, press F5.


2 - 30 FPD/319-03

SETUP

This routine will clear ALL YTD Cum’s for a Ship

To Location, Continue? (Y/N):

2.2. Enter Y.

The following pop-up window is displayed and the cursor starts in the

Group Number field.

3.3. Enter the Customer Group ID. The cursor moves to the Ship To Location

field.

4.4. Enter the FASPAC ship-to code. The cursor moves to the Continue field.

5.5. Enter Y. The pop-up window closes and he cursor returns to the Cust.

Group field.

6.6. Press SKIP to exit the program.

To delete a record:

1.1. In the Cust. Group field, enter the Customer Group ID. The cursor moves

to the Item No. field.

2.2. Enter the item number. The cursor moves to the Reference No. field.

3.3. Press CMD+L and then press Return on the record you want to delete.

The information for the record is displayed and the cursor moves to the

SELECT prompt.


screen:

Are You Deleting This Item For This Customer, Ship

To And Any History? (Y/N)

5.5. Enter Y to delete the item.

6.6. Repeat steps 1 to 5 for other records you want to delete.


FPD/319-03 2 - 31


CMD+L

CMD+L

Field Explanations

Cust. Group

The Customer Group ID that was created in BCCR/MAI.

Item No.

The FASPAC item number defined in IM/MAI that was used in

BGIM/MAI.

Description

The default item description comes from IM/MAI.

Short Name

The default alternate item name comes from IM/MAI.

Reference No.

FASPAC is not currently using this field, but the entry must match the

BGIM record.

P.O. No.

The PO number must match the BGIM record.

Customer No.

The customer number from CP/MAI.

Ship-to No.

The STM record representing the plant to which this item is authorized to

be shipped.

Their Cust No.

Displays the customer’s plant/location code from the BCCR record.

Past Due Qty

This is a system-calculated field that is updated by Shipping

Confirmation (SC) or Pull List File Maintenance (OP/SHP/SHC/PLFM).

This field represents an accumulated total.

SC—this is only applicable if an item is called complete and a back order

is not generated.

PLFM—updates immediately if order is edited to a quantity of zero.

Example:

Qty required on EDI document: 1578

Carton Qty: 100

2 - 32 FPD/319-03

SETUP

SC—The quantity shipped to customer is compared to the required

quantity. The difference is then compared to the carton quantity. If the

difference is greater than the carton quantity, this field is updated. If the

difference is less than the carton quantity, this field is not updated.

Order is for 1578; actually shipped 1500; difference of 78, which is less

than 100 (carton quantity). The field will not be updated.

Order is for 1578; actually shipped 1400; difference of 178, which is

greater than 100 (carton quantity). This field is adjusted by 178.

PLFM—If the quantity were edited to zero, the past due would be the

original required amount. If the quantity is edited to a number greater

than zero, this field is not updated. If EDID is run again after this field

has been populated, an * will be displayed next to this field.

If this quantity is edited to zero, the past due field will be updated with

1578.

This field is decreased or set to zero in one of the following ways:

• An order is entered in OD using the F6 and F11 options and using

the sign on ID of EDI. The Past Due Qty field will be decreased

by the ordered amount. This is actually updated when the quote is

confirmed as an order. The Past Due Qty field is never a negative.

For example, it is currently 10 and the new order is 20. The Past

Due Qty field will now be 0.

Only the sign on of EDI will affect the past due quantity. Any

other sign on will affect everything else in the buyer contract

system except the Past Due Qty field.

If the order is called complete in SC, the Past Due Qty field will

be updated.

If the order is canceled in SC, the Past Due Qty field will be

increased with the order amount.

A back order does not affect the past due quantity.

• A manual release or EDID past due will display * to indicate that

the field has been populated.

• The next time PLFM is run for this item, the PO number and plant

combination it will be re-set to zero and the * will be removed.

01 Start Date

02 End Date

The defaults come from BGIM/MAI, but you can change them for this

particular ship-to or plant.

Only dates after the BGIM Start Date and before the BGIM End Date

will be accepted.

If these are the same dates as BGIM/MAI, leave these fields blank. The

defaults come from BGIM, so you will only have to maintain the dates in

one file.

FPD/319-03 2 - 33


If an EDI transaction outside of the date range is encountered, a warning

is printed on the EDID Pull List Transaction Summary report, but the

requirements are still created in FASPAC.

03 Weekly Ship

The shipping frequency used by EDID to create requirements in weekly

buckets for 830 transactions.

W = Weekly shipments

1 = Ship the first week of the month

2 = Ship the second week of the month

3 = Ship the third week of the month

4 = Ship the fourth week of the month

5 = Ship the fifth week of the month

6 = Ship the first and third weeks of the month

7 = Ship the second and fourth weeks of the month

This code must have been defined in SYCD (see page 2-5).

04 Daily Ship

Which day of the week will the shipment take place.

D = Monday

E = Tuesday

F = Wednesday

G = Thursday

H = Friday

J = Saturday

K = Sunday

O = DAILY Monday through Friday

Note: For EDI transactions, the O code will split the scheduled quantity

equally over five days. For manual releases it will schedule all on the day

entered when creating the manual release.

The following codes (S though V) are only available for EDI

transactions; they are not applicable for manual releases:

S = ONCE any time Monday through Friday

P = ½ Monday, ½ Thursday

Q = ½ Tuesday, ½ Thursday

R = ½ Wednesday, ½ Friday

T = ½ Tuesday, ½ Friday

U = ½ Monday, ½ Wednesday

V = Monday, Wednesday, Friday

2 - 34 FPD/319-03

SETUP

This code must have been defined in SYCD (see page 2-5).

If this field is left blank or is invalid, the Manual Release screen for this

Item/PO/Plant will display the following error message:

Daily Ship Of ____ Is Not Supported At This Time.

SKIP

A code may be invalid even though it has been created in SYCD,

because the rest of the system will not understand that code. An invalid

code results in the EDID and Manual Release calculations assuming a

Monday ship date.

05 ASN Required


The Standard Order Translation (EDI/OT) program generates the

Advance Shipping Notice (ASN).

06 Min. Ship Qty

A plant can specify a minimum ship quantity regardless of the required

pull quantity. The value in this field is used when the quantities required

for each ship date are calculated.

However, quantities required are calculated differently depending on

how field 07 Adjust Quantity To Minimum in SYS/OPT/BCS is set.

Note that in the following examples, the minimum ship quantity works

differently for EDI versus manual transactions.

If BCS field 07 is set to N:

FASPAC will not create a requirement unless the quantity required by

the customer is greater than or equal to this value.

For example, if the Min. Ship Qty is set to100:

Customer’s Weekly

Requirements

FASPAC EDI

Results

Week 1 = 95 0

Week 2 = 200 200

Week 3 = 50 0

The 95 required in Week 1 do not appear as a requirement in

FASPAC. If the customer still requires this quantity in Week 2, they

would include this quantity in Week 2’s EDI document.

If BCS field 07 is set to Y:

For EDI transactions, the required quantity will be automatically

increased to match the minimum ship quantity, and future demands will

be reduced.

FPD/319-03 2 - 35


For example, if the Min. Ship Qty is set to 350:

Customer’s Weekly

Requirements

FASPAC EDI

Results

Week 1 = 280 350

Week 2 = 210 350

Week 3 = 210 0

EDI does not ship anything in Week 3 because the combined weekly

requirements (280+210+210) equals 700 and that was already

shipped in the first two weeks (350+350).

For manual releases, the system automatically increases the

requirements for each date to match the minimum ship quantity.

The following message is displayed when a lesser quantity is entered:

Quantity entered is less than BCIM minimum

quantity

It will be increased to BCIM minimum - SKIP

For example, if the Min. Ship Qty is set to 350:

Customer’s Weekly

Requirements

FASPAC Manual

Results

Week 1 = 280 350

Week 2 = 210 350

Week 3 = 210 350

07 Container Qty &

08 Container Type

Note: The Container Qty field must contain a value greater than zero.

A plant can specify a Container Type and Container Quantity for

shipment.

These fields are used in conjunction with the Pull Method specified in

BCCR: W, P, A, E.

Options P and A are applicable only if you are committing tags to quotes

and the appropriate flag is set in Warehouse Control Specifications

(SYS/WCS).

The Container Type field is validated with Tag Container Types defined

in SYCD with a Record Type of TQ (Tag Container).

2 - 36 FPD/319-03

SETUP

How it works:

If the pull method is W (whole cartons only)—The system looks at all

tag records that have an on-hand quantity, a container quantity, and the

type of container and checks these fields (7 and 8) to see if they match. If

it finds a match, it commits the tag.

If the pull method is P (partial cartons first, then whole cartons)—The

system looks for tags with an on-hand quantity, no container quantity,

and the type of container. If the container type matches these fields, it

will commit these tags for a partial carton up to the quantity required.

Then it matches whole cartons as it does for W.

If the pull method is A (whole cartons first, then all partial cartons)—The

system looks for whole cartons as it does for W. Then it looks for all

partial cartons that match the container type.

If the pull method is E (exact quantity ordered will be shipped using

whole cartons first)—The system looks for the exact quantity and will

commit the tags FIFO.

09 Dock Info.


10 Cust. Alt Item

An optional field used by the ASN. If this field is blank, the ASN looks

at the Customer Item Number in BGIM/MAI.

This field will print as a note line if field 04 Create Alt Part Note in

Buyer Contract Specifications (SYS/OPT/BCS) is set to Y.

11 Comment

A user-defined comment up to 50 characters. This comment will print as

a note line on the quote and order if field 05 Create Comment Note Line

in BCS has been set to Y (see page 2-3).

12 Carrier Code

Optional. The Carrier code that you defined in CCFM (see page 2-19).

This code will print on the ASN. It will be the default carrier for this

item, PO number, and plant combination.

This is not the same carrier code defined in SYCD.

13 User Defined 1

14 User Defined 2

15 User Defined 3


16 To Be Purged

Do you want to be able to manually enter an order in Order Desk and

have it be included in the Buyer Contract system.

The order can be entered in OD using F6 and F11.

FPD/319-03 2 - 37


Y = F6 and F11 cannot be used in OD.

N = F6 and F11 can be used to create an order in OD, and have it

included in the Buyer Contract system. This is the default.

This does not pertain to a manual release or an EDI transaction. This flag

will not prevent these orders.

17 Adv Ship Days

How many future days will be included in the shipping requirement. The

number of days can be thought of as the lead time.

For EDI transactions, the EDID program uses this field.

For manual releases, BCIM/MAI uses this field when the release is

entered.

Note: This field overrides field 17 Adv Ship Days in BCCR/MAI.

There are two parts to calculating the actual ship date:

• The customer due date less the advance ship days

• The daily ship code schedule in BCIM

Example:

The customer requires delivery by Monday, November 1.

The advanced ship days = 4.

The first calculated ship date = Thursday, October 28.

If the daily ship schedule is for Friday, the actual ship date would then be

Friday, October 29.

If the daily ship schedule is for Tuesday, the actual ship date would then

be the following Tuesday, November 2 (that is, it would be a late

shipment).

18 Cum Qty

Model Year


19 Active PO

An 862 transaction does not contain a PO number. It will match the

item, customer group, and ship-to information on the incoming EDI

transaction to the BCIM record.

Y = The PO is active. That is, it is the current PO to be used.

N = The PO is inactive.

Note: If there are more than one active PO number, the EDI transaction

will use the first one it finds in the file.

2 - 38 FPD/319-03

SETUP

Created By

The sign on initials and date is entered when the record was created.

This field cannot be accessed or changed. If a field is changed it is

indicated on screen two.

Function Keys

F1-Next Screen

Displays the current cumulative information of shipments and invoices

for this item, to this ship-to location. It also displays the most recent

shipment and invoice information, for this item, to this location.

Do not maintain these fields manually.

F2-Manual Release

A manual release may be created (see page 3-37).

F7-EDI Notes

Create EDI notes that will be included on the Past Due Report

(BCSR/PDR).

FPD/319-03 2 - 39


BCIM, Second Screen

This screen displays the invoice and last shipment information. You can change

the primary warehouse for this item if it is different from the group’s warehouse.

You can also indicate the number of containers or layers on a pallet, and whether

the containers are returnable.

The top portion of this screen contains the same information you entered on the

first screen.

Fields 01 through 07 are updated by Invoice Calculation (INC).

Fields 11 through 15 are updated by Shipping Confirmation (SC).




When this screen is displayed, the cursor starts in the SELECT prompt. Check

that the following fields have these entries:

08 Keep History The default should be Y.

09 Ret. Contain (Y/N) If applicable, enter Y if the container is to be

returned to your warehouse.

10 Primary Warehouse This is the most important to check.

Be sure that this is the warehouse you will be

shipping from. If not, change it.

2 - 40 FPD/319-03

SETUP

16 Shipped Qty Code For 856 transactions, this field should be I.

17 Contain/Pallet Layer If applicable, enter the number of containers per

layer on the pallet.

18 No. of Layers/Pallet If applicable, enter the number of layers on the

pallet.


To change a field:

1. In the SELECT prompt, enter the number of the field. The cursor moves

to selected field.

2. Change the entry. The cursor returns to the SELECT prompt.

3. Repeat steps 1 and 2 for the remaining fields.

4. When finished, press F1 or SKIP to return to the first screen.

The cursor starts in the Customer Number field in the first screen.

5. Press SKIP to exit the program.

Field Explanations

The fields repeated from the first BCIM screen are not described here.

01 Date

The date of the last invoice, for this item, for this plant.

02 Invoice No.

The FASPAC invoice number.

03 Line No.

The line number on the FASPAC invoice.

04 Quantity

The quantity that was shipped on the last invoice/line.

FPD/319-03 2 - 41


05 Total Qty. Inv’ed

The total cumulative quantity invoiced to date, for this item/plant/PO.

Note: In initial setup, this field must be updated manually with the CUM

SHIPPED QTY found on the EDID Pull List Transaction Summary

report.

CAUTION! After setup, do not change this field since it is used to

calculate net requirements, based on quantities required by the Trading

Partner, and quantities already shipped in FASPAC.

06 Value Inv’ed

The total cumulative dollar value, invoiced to date, for this

item/plant/PO.

07 Cost Inv’ed

The total cumulative dollar cost, invoiced to date, for this item/plant/PO.

08 Keep History

Y = History will be kept by BCTS. Item/Plant/PO Monthly

Quantity/Dollars/Cost is stored in BCIH. Invoice Calculation (INC)

updates and saves the history.

N = History will not be kept.

09 Ret. Contain (Y/N)

Y = The Container Type defined for this Item/PO/Plant combination is

returnable to your warehouse. This flag results in a different presentation

of container information on the ASN.

You should decide during the EDI setup whether or not the container is

to be returned.

N = The container type is not returnable. This is the default

10 Primary Warehouse

The main warehouse from which you will be shipping this item.

11 Date

The date of the last shipped confirmed sales order, for this item at this

plant.

12 Order No.

13 Line No.

The FASPAC sales order number and line number for the last shipped

confirmed order.

14 Quantity

The piece quantity of the item on the last shipped order.

2 - 42 FPD/319-03

SETUP

15 Total Qty Shipped

Caution! This field should never be changed without consulting the

Faspac Support Department.

The total cumulative quantity shipped but not invoiced. If this is greater

than the last invoiced confirmation, more than one sales order has been

shipped confirmed without being invoiced.

16 ASN Shipped Qty Code

I = The shipped quantity is included in the document. This is the default.

If you are not using 856, the system does not use this field.

17 Contain/Pallet Layer

18 No. of Layers/Pallet

The number of containers per layer on the pallet, and the number of

layers of cartons that make up a full pallet (this is determined by the

warehouse).

These fields will be used when PLFM calculates shipments. If the values

are zero, the fields are not used when calculating ship quantities.

How it works:

The system will compare the required quantity to the calculations of

these two fields for a full pallet. It will then look to the future to see if we

can ship additional quantity so a full pallet could be shipped.

If the future demand does not add up to a full pallet, it will then attempt

to add up to complete layer. If there is future demand that can be

included on the first shipment to make up a full pallet or complete layer

it will then readjust the future demand accordingly.

If there is not enough future demand in the schedule it will ship what is

required.

For example:

CTN or Box Qty = 1000

Contain/Pallet Layer = 9, so the total quantity per layer is 9000

No. of Layers/Pallet = 3, so the total quantity per pallet is 27000.

Shipping Day 1 2 3

Original Required Quantity 18500 18500 15000

Future adjust 8500 8000 N/A

Adjusted after PLFM

from previous shipment 10000 7000

Pull Qty to ship 27000 18000 7000

FPD/319-03 2 - 43


Shipping Day 1—A full pallet is 27000, so it calculates the first

requirement of 18500 and looks in the future to see if there is the balance

of 8500 to complete a pallet. It will ship 27000, which is a full pallet.

Shipping Day 2—Since we shipped an additional 8500 on the previous

shipment to make up a full pallet, this requirement was reduced by 8500.

The requirement is now 10000. Looking in the future it will again try to

ship a full pallet and if not possible, full layers. Since 10000 goes into the

second layer it will calculate to the future to complete the layer. It will

ship 18000, which is two full layers.

Shipping Day 3—The adjusted requirement is now 7000. It will ship

7000 since there are no more future requirements to make up a layer or

pallet.

19 Commission Base/Rate


Function Keys

F1-Previous Screen

This displays the first BCIM/MAI screen.

F2-Invoice Detail

Displays the details of the recent 10 invoices for this item, ship-to and

purchase order number. Working in conjunction with the invoice file, it

uses the first, or oldest, 1000 invoices in the invoice file, then sorts for

this item, ship-to, and PO combination.

If current invoices do not display, run the DIN program to delete old

invoices.

The starting cumulative quantity is from Field 05 on the BCIM Second

Screen. It then substracts the individual invoice quantities for a running

total.

F7-EDI Notes

Create EDI notes to be included on the Past Due Report (BCSR/PDR).

2 - 44 FPD/319-03

SETUP

3Acquiring Transactions

This chapter explains how to acquire EDI transactions or enter

manual releases.

You can enter a shipping requirement manually in SRS or receive it through EDI.

Once the scheduled release is stored in FASPAC, you can review it, manipulate

it, turn it into a quote, and then process it as an order.

The following topics are discussed in this chapter:

1.1. Importing EDI transactions—downloading your customer’s EDI

transaction data.

2.2. If you are using EDI:

a) Transferring your customer’s EDI transaction to FASPAC using the

Get EDI Transactions From PC (EDI/REDI) program.

b) Translating the EDI transactions to FASPAC files using the Inbound

EDI Translation Driver (EDI/EDID) program.

3.3. If you are not using EDI, creating manual releases using the Buyer

Customer Items Maintenance (BCTS/BCIM/MAI) program.

4.4. Optionally viewing the requirements using the Time Phased

Management Inventory Management Exception (TPI/TPIM).

If you are a manufacturing customer, viewing the requirements using

Inventory Control Production Planning (MFG/MFI/MFPP).

FPD/319-03 3 - 1

Importing EDI Transactions

The following is the basic procedure for importing your customer’s EDI

transaction data:

1.1. Your customer must upload EDI transactions (in an ASCII file) to the

Value Added Network (VAN).

2.2. You then download the EDI transactions from the VAN to your PC

running the EDI software (such as Harbinger, Sterling, or GE Info

Services).

3.3. Run REDI on the EDI PC to translate the EDI transactions to FASPAC

format.

4.4. The transactions are now stored in FASPAC EDI data files.

Whatever is processed on your EDI PC is what will be included in FASPAC

REDI and EDID processing. For example, if you have downloaded both 830 and

862 transactions from your customer, both will be processed in FASPAC.

3 - 2 FPD/319-03

ACQUIRING TRANSACTIONS

Get EDI Transactions From PC

(EDI/REDI)

This program transfers an ASCII formatted file from your EDI PC to FASPAC.

A predefined number of the most recent ASCII EDI files that were transferred

are kept in FASPAC. When you run REDI, it overwrites the oldest file.

Press F8 to accept the default Y and retrieve files. Enter N or press F7 to exit the

program.

FPD/319-03 3 - 3

GET EDI TRANSACTIONS FROM PC (EDI/REDI)

The defaults on this screen will be specific for your system. They are defined by

the Faspac Representative when your system is first set up.

Press F8 to accept the defaults. If the process was successful, the FASPAC menu

is displayed.

If the process was not successful, one or more error messages, such as the

following example, will be displayed.

ERROR ==> Files Not Retrieved ==> Press <ENTER> to Exit

The error messages vary depending on your system.

If you get an error message, contact Faspac Application Support.

3 - 4 FPD/319-03


Translate Data from EDI

After transferring the ASCII EDI data files to FASPAC, you must then translate

them, using the Inbound EDI Translation Driver (EDI/EDID) program, so that

FASPAC can use the information.

Inbound EDI Translation Driver (EDI/EDID)

This program translates the ASCII EDI file retrieved from your EDI PC into a

file that can be interpreted by FASPAC. It is very important that you sign on to

FASPAC with the same date you used when you ran REDI.

Note: The advance ship days are calculated when this program is run. This is

why the ship date on your EDI report may differ from the customer’s EDI

transmission.

This screen displays the types of documents that you can process, and the last

date and time they were processed by EDID. It does not display the individual

transactions. When you select a document type, all transactions of that type will

be processed.

EDID creates two reports:

• All records, with and without errors or warnings, are printed to a file.

• Records with errors or warnings are printed to the Other printer.

FPD/319-03 3 - 5

INBOUND EDI TRANSLATION DRIVER (EDI/EDID)




To translate the ASCII file:

1.1. From a FASPAC menu, enter EDID. The documents that are ready to be

translated are listed. The cursor starts to the left of the first Document ID.

2.2. To select a type of document, type X beside it and press Return. The

cursor moves to the next line.

To move to the next document without selecting the current one, press

Return.

3.3. Repeat this for other documents you want to translate.

4.4. When finished, press F8 to update the file. The following message is

displayed at the bottom of the screen:

Continue With Documents (Y/N)?

5.5. Enter N to reselect the documents or exit the program.

Enter Y to continue. The following message is displayed:

Have all 830/862 Transactions been transferred

from the EDI Computer? (Y/N):

6.6. Enter N to exit the program.

Enter Y to continue. The following message is displayed:

Continue? (Y/N)

7.7. Enter N to exit the program.

Enter Y to continue. You will see a screen similar to the following

example as the records are processed.

3 - 6 FPD/319-03


The EDID Process

The EDID process takes the customer’s EDI transactions that you transferred

from the EDI PC to FASPAC using REDI, and converts them into FASPAC

customer requirements.

The EDI transactions are then matched against the FASPAC files:

1.1. EDID looks in the BCCR file for your customer’s EDI Account Number

and Dock Number (field 13). If it does not find the EDI account number,

the message No Customer Cross-Reference Found is printed on

the report.

2.2. Then it looks in the BGIM file for your customer’s part number. If it

does not find the part number in BGIM, it looks in the CR/MAI file for a

customer, customer group, or alternate cross-reference.

3.3. If it finds the match in CR/MAI, it looks in BGIM again for the PO

number and FASPAC item number for the customer group. If they are

not found, the following message is printed on the error report.

Customer Part Not In Buyer Group

4.4. If they are found in BGIM, EDID next looks in the BCIM file for the

FASPAC customer number and FASPAC ship-to code.

5.5. If the codes are not found in the BCIM file, the following message is

printed on the report.

No P/O Rec Found for Ship-to

If there is a match on all of the above factors (the plant, PO, and item are all

identified in FASPAC), the requirements on the incoming EDI document are

transferred to the appropriate FASPAC file.

Note: 862 transactions will override 830 transactions for the same date range.

Error Messages

There are two types of error messages during EDID processing:

• Warnings—The record is still processed and updated to FASPAC.

• Fatal errors—The records will not be processed and updated to FASPAC.

FPD/319-03 3 - 7

THE EDID PROCESS

Files Updated by EDID

The firm (pf09) or planning (pf09a) requirements files are updated with the latest

requirements for all items that did not contain fatal errors during the EDID

process.

You can view the requirements in the Inventory Management Exception

(TPI/TPIM) program. If you use the Manufacturing module, you can also view

them in Mfg Inventory Control Production Planning (MFG/MFI/MFPP).

Reports Produced by EDID

When you run EDID, two reports are produced:

• The Pull List Transaction Detail Report contains the details of all items

processed by EDID, including any errors or warnings. This report is not

printed, but is stored in a file and can be viewed.

The report file is stored on your system with a name in the format

YYMMDDHHMM. The path to this file varies from system to system.

See Viewing EDID Processed Records on page 3-13.

• The Pull List Transaction Summary Report prints to the Other printer, as

defined for your login ID. This report contains the transaction detail and

error messages. It also contains a summary of all items processed, with

reference to the page number of the detail report described above.

3 - 8 FPD/319-03


Example of a Pull List Transaction Detail Report

Pages 1 to 3

FPD/319-03 3 - 9

THE EDID PROCESS

COMPANY: 10 ACME FASTENERS PAGE 1

RUN ID: EIPL Pull List Transaction Report 06/15/99

RUN BY: WPD 15:12

================================================================================================================================

TRANSACTION SET: 830

GROUP PURPOSE MY RELEASE TYPE START DATE END DATE ISSUE DATE ISSUER CUSTOMER ERROR MESSAGE

CAMI 05 0 20 DL 11/30/98 08/15/99 04/24/99 14080 1

PART # P.O. NUMBER U/M PRODUCTION CTL LINE FEED DROP POINT DOCK CODE PLANT PATTERN

30000004 000218 PC J JCWLD AF

RECORD NET TYPE TIMING SHIP DATE MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY

0 C W 04/26/99

0 D W 05/03/99

0 D W 05/10/99

0 D W 05/17/99

0 D W 05/24/99

0 D W 05/31/99

0 D W 06/07/99

0 D W 06/14/99

0 D W 06/21/99

3000 D W 06/28/99 3000

0 D W 07/05/99

0 D W 07/12/99

0 D W 07/19/99

0 D W 07/26/99

3000 D W 08/02/99 3000

618 D W 08/09/99 618

REQD CUM CUM START CUM END DATE LAST SHIP QTY LAST SHIP DATE CUM SHIPPED CUM SHIP DATE

1500 11/30/98 0 0

OUR CUMS LAST SHIP TOTAL SHIP FABRICATE MATERIAL

0 0 0 1500 4500



RUN BY: WPD 15:12

=================================================================================================================================



CAMI 05 0 20 DL 11/30/98 08/15/99 04/24/99 14080 1


30000032 000218 PC P JPDT3 AF


0 C W 04/26/99

0 D W 05/03/99

0 D W 05/10/99

0 D W 05/17/99

0 D W 05/24/99

0 D W 05/31/99

0 D W 06/07/99

0 D W 06/14/99

4000 D W 06/21/99 800 800 800 800 800

10000 D W 06/28/99 2000 2000 2000 2000 2000

0 D W 07/05/99

0 D W 07/12/99

0 D W 07/19/99

0 D W 07/26/99

12000 D W 08/02/99 2400 2400 2400 2400 2400

14000 D W 08/09/99 2800 2800 2800 2800 2800


0 11/30/98 0 0


0 0 0 0 14000

3 - 10 FPD/319-03




RUN BY: WPD 15:12

=================================================================================================================================



CAMI 05 0 20 DL 11/30/98 08/15/99 04/24/99 14080 1 Customer Part not in Buyer’s Group!

**E**


96068415 000218 PC J JCWLD AF


0 C W 04/26/99

0 D W 05/03/99

0 D W 05/10/99

0 D W 05/17/99

0 D W 05/24/99

0 D W 05/31/99

0 D W 06/07/99

0 D W 06/14/99

0 D W 06/21/99

0 D W 06/28/99

0 D W 07/05/99

0 D W 07/12/99

0 D W 07/19/99

0 D W 07/26/99

800 D W 08/02/99 160 160 160 160 160

800 D W 08/09/99 160 160 160 160 160


800 11/30/98 0 0


0 0 0 800 800

Example of a Pull List Transaction Summary Report

Pages 1 to 3

FPD/319-03 3 - 11

THE EDID PROCESS


RUN ID: EIPL Pull List Transaction Summary 06/15/99

RUN BY: WPD 15:19

=================================================================================================================================

REC CUST CUSTOMER ITEM / ITEM CUST SHIP PAGE

TYPE GROUP FASPAC ITEM DESCRIPTION PLANT TO NBR

830 CAMI 30000004 M6 X 16 HEX SEMS BOLT w/PILOT j-029 14082 JCWLD 1

/12345-67890/REV.2-8/30/95

830 CAMI 30000032 M6X12 TRUSS HEAD TAPPING SCREW j-035 14081 JPDT3 2

/03141-06123/SESP1405c-4/1/93

830 CAMI 96068415 M6X12 TRUSS HEAD TAPPING SCREW j-035 14082 JCWLD 3

/03141-06123/SESP1405c-4/1/93 Customer Part not in Buyer’s Group!

**E**



RUN BY: WPD 15:19

=================================================================================================================================



CAMI 05 0 20 DL 11/30/98 08/15/99 04/24/99 14080 1 Customer Part not in Buyer’s Group!

**E**


96068415 000218 PC J JCWLD AF


0 C W 04/26/99

0 D W 05/03/99

0 D W 05/10/99

0 D W 05/17/99

0 D W 05/24/99

0 D W 05/31/99

0 D W 06/07/99

0 D W 06/14/99

0 D W 06/21/99

0 D W 06/28/99

0 D W 07/05/99

0 D W 07/12/99

0 D W 07/19/99

0 D W 07/26/99

800 D W 08/02/99 160 160 160 160 160

800 D W 08/09/99 160 160 160 160 160


800 11/30/98 0 0


0 0 0 800 800

3 - 12 FPD/319-03



RUN ID: EIPL Pull List Transaction Summary 06/15/99

RUN BY: WPD 15:19

=================================================================================================================================

ERRORS REPORTED COUNT

No Customer Cross Reference Found! 0

Invalid FASPAC Customer Number! 0

No P/O Rec Found for Any Ship To! 0

Customer Part not in Buyer’s Group! 1

FASPAC Part Not Found! 0

Record Exceeds P/O Dates! 0

No P/O Rec Found for Ship To! 0

Multiple P/O Record Found for Part! 0

YTD Cum’s Out of Balance, Pls Check 0

Model Year Out of Range! 0

862 Adjustment Made Please Check 0

No Carton Quantity Please Fix 0

Immediate Quantity Please Check 0

Pull Signals On Transaction 0

Label Information Included 0

Viewing EDID Processed Records

You can use the FASPAC SHOW utility to view the EDID report file after you

determine the path on your system and the name of the file.

To determine the path of the EDI report file:

1.1. From a FASPAC menu, enter ENV. A list of your working environment

paths is displayed.

2.2. Look for the line beginning with EDIPRTDIR= .

The rest of that line shows the file path of this document. For example:

EDIPRTDIR=/u/data/edi/print

3.3. Make a note of the path, including upper/lower case.

4.4. Enter Q to quit the program.

There are two methods for finding the name of the report file: using the FASPAC

DIR utility or looking at the date and time on the report that printed when you ran

EDID.

To use the DIR utility:

1.1. From a FASPAC menu, enter UTIL/FILE/DIR.

2.2. In the Directory Name field, enter the path you noted above. The path

must be the same upper/lower case as it was displayed in ENV. For

example:

/u/data/edi/print

The files in this directory will be displayed.

3.3. Make a note of the EDI file name you want to view, which is in the

format YYMMDDHHMM (such as 9906151519).

4.4. Enter Q to quit.

To use the EDID printed report:

Look in the upper right hand corner (any page) and find the date and time of the

report.

The file name will be in the format YYMMDDHHMM (such as 9906151519).

FPD/319-03 3 - 13

THE EDID PROCESS

To view the file:

1.1. From a FASPAC menu, enter SHOW.

2.2. In the File Name field, enter the complete path name of the file. For

example,

/u/data/edi/print/9906151519

The report file is displayed on your screen. Note the functions at the

bottom of the screen for scrolling through the file.

These reports tend to be very large, so you may want to use the FIND

command.

3.3. Look at the report that was sent to your printer and find the page number

of the item you want to look at.

4.4. Type / and the following prompt is displayed:

Find what?

5.5. Enter PAGE nnnn.

The page number must be an exact match to the printout (there are four places on

the printout for page numbers). For example:

PAGE 10 type three spaces in front of the number 10

PAGE 3 type four spaces in front of the number 3

3 - 14 FPD/319-03


EDID Error Correction

Before going further with the SRS process, all errors printed on the EDID report

must be examined and corrected, if necessary. Fatal errors will not be processed

further. Warning errors will be processed, but they should be examined first.

Usually, the remedy is to edit the BGIM or BCIM files.

Important: After any changes to the BGIM or BCIM files, the EDID process

must be run again to ensure the requirements file is updated with the correct

requirements. You must rerun the EDID program before you receive further EDI

data to FASPAC (REDI) or run the PLFM process to create the Pull List.

One of the most common errors, especially during initial setup, is

YTD Cums Out of Balance, Pls Check

This is corrected by amending the Total Qty Invoiced field on the second

BCIM/MAI screen.

Caution! The Total Qty Invoice field should only be amended during the initial

setup of these files. After regular processing has begun, if this error occurs,

several things must be checked before editing the BCIM record.

Even though this error is printed, it may not require correcting. It is important

that you understand how this error is identified by the EDID process:

• If the CUM REQD field on the incoming EDI document is not zero, the

CUM SHIPPED field on this document is matched against the value in the

Total Qty Invoiced field on the second BCIM screen (the value prints in

the OUR CUMS field on the EDI document).

• If the CUM SHIPPED is greater than the value in the Total Qty Invoiced

field on the second BCIM screen, the system adds the BCIM Total Qty

Shipped to the Total Qty Invoiced, and then tries to match this against the

CUM SHIPPED.

• If the CUM SHIPPED is less than the value in the Total Qty Invoiced field

on the second BCIM screen, the system subtracts the BCIM second screen

Last Shipped Qty from the Total Qty Invoiced, and then tries to match this

to the CUM SHIPPED.

• If no match can be found from any of these values, the warning error is

printed on the EDID report.

FPD/319-03 3 - 15

EDID ERROR CORRECTION

• However, more than one shipment could have been processed through

FASPAC but have not yet been received by your customer. If this is the

case, do not make changes to the BCIM file, since FASPAC will calculate

net requirements considering the quantities already shipped. If BCIM is

amended with the new CUM SHIPPED from the EDID report, a duplicate

demand will be created.

3 - 16 FPD/319-03


Error or Warning Messages

Note: If the error message status is FATAL, the record is not processed. If the

error message status is a WARNING, the record is processed but may have

consequences later in the process.

862 Adjustment Made Please Check

An 862 transaction for today’s date has been received, and the quantity

has been moved to the next shipment date. This data should be reviewed.

Status—WARNING

Correction—None.

This is notifying you that the Trading Partner made a change at the last

minute.

Customer Part not in Buyer Group

The customer’s part number has not been created in BGIM.

Status—FATAL

Correction—Confirm the item is valid. Either create it in BGIM/MAI or

create an alternate or customer cross-reference in CR/MAI.

The reason for the cross-reference would be if there are several plants for

the same item, but one of the plants refers to the item differently.

Faspac Part Not Found

The item in BGIM/MAI is not a valid FASPAC item.

Status—FATAL

Reason—The item was deleted after BCIM was created.

Correction—Recreate the item in IM/MAI.

Immediate Quantity Please Check

A record is received that indicates your customer requires this part

immediately. The transaction type on the incoming document is A

(Immediate). This is changed to C (Firm) in FASPAC and should be

reviewed.

Status—WARNING

Correction—None; review the transaction.

FPD/319-03 3 - 17

ERROR OR WARNING MESSAGES

Invalid Faspac Customer Number

The corresponding customer number entered in BCCR is not a valid

FASPAC customer.

Status—FATAL

Reason—The customer was deleted after BCCR was originally created.

Correction—Recreate the customer in CP/MAI.

Label Information Included

Label information has printed and must be reviewed.

Status—WARNING


Multiple P/O Record Found for Part

Multiple BCIM/MAI records have been created for the same ship-to

locations.

Status—WARNING

Reason—More than one PO number is active in BCIM (see page 2-38).

Correction—Change the Active field to N for the appropriate POs in

BCIM/MAI.

No Carton Quantity Please Fix

The BCIM record for this part/plant combination does not have a

box/container quantity defined. This will cause errors later in the process.

Status—WARNING

Correction—The BCIM field, Container Qty, is blank or zero. It must

be at least 1.

No Customer Cross-Reference Found

The customer number on the EDI transaction was compared to the EDI

Account Number and EDI Dock Number fields in BCCR, and no match

was found.

Status—FATAL

Correction—Confirm and review the EDI Account No and EDI Dock

No fields in BCCR/MAI.

Note: The EDID report will not have a customer number and the EDI

account number will be in the plant field.

3 - 18 FPD/319-03


No P/O Rec Found for Ship-to

The purchase order on the EDI transaction does not match the PO in

BCIM for that ship-to.

Status—FATAL

Reason—Either the PO field in BCIM record is wrong or the PO

modifier field in BCCR is wrong.

Correction—Correct the BCIM or BCCR record.

Past Due Quantity Forwarded

The EDI transaction contains a requirement prior to today’s date.

Status—WARNING


Possible Obsolete Part

The record identifier is ZZ and the quantity required is zero on the EDI

transaction.

Status—FATAL

Reason—The Trading Partner is transmitting an item that is obsolete.

Correction—You cannot correct this and it will not process.

Pull Signals On Transaction

Pull signal data has printed and must be reviewed.

Status—WARNING


Record Exceeds P/O Dates

The date on the EDI transaction is outside the date range in BCIM or

BGIM.

Status—FATAL

Correction—Confirm that the dates are correct in both BCIM/MAI and

BGIM/MAI.

Transaction Discarded Check Type

The transaction on the incoming document is something other than:

C = Firm

D = Plan

Status—FATAL

Correction—None. We only support C and D.

FPD/319-03 3 - 19

ERROR OR WARNING MESSAGES

YTD Cums Out of Balance, Pls Check

The year-to-date amounts on the EDI transaction do not match those in

BCIM/MAI. FASPAC tries to match the EDI accumulative quantity

using one of three methods:

• Compares the “Total Qty. Inv’ed” of BCIM

• Compares the “Total Qty. Inv’ed” less the “Quantity” of Last

Shipped Info

• Compares the “Total Qty. Inv’ed” less the “Total Qty. Shipped” of

Last Shipped Info

Status—WARNING

Reason—The EDI accumulative quantity does not match any of the

above calculations.

Correction—Research the problem and communicate with your Trading

Partner to see why this accumulative differs. If FASPAC is incorrect,

correct the “Total Qty. Inv’ed” field on the second screen of BCIM/MAI.

The “Total Qty. Inv’ed” field is the only one that should be changed. Do

not change the other fields.

Note: It is imperative that you correct errors of this type. Otherwise

FASPAC may not create the correct demand.

3 - 20 FPD/319-03


Sample 830 and 862 Reports

Example of an EDI 830 Planning Transaction

Field and Column Descriptions

TRANSACTION SET

The type of EDI transaction (830).

GROUP

The Customer Group in BCCR.

PURPOSE

An EDI code that describes the purpose of the transaction. FASPAC

treats all purposes as 05 (replace).

MY

The model year.

RELEASE

The customer release number.

FPD/319-03 3 - 21

SAMPLE 830 AND 862 REPORTS



RUN BY: WPD 15:12

=================================================================================================================================



CAMI 05 0 20 DL 11/30/98 08/15/99 04/24/99 14080 1


30000004 000218 PC J JCWLD AF


0 C W 04/26/99

0 D W 05/03/99

0 D W 05/10/99

0 D W 05/17/99

0 D W 05/24/99

0 D W 05/31/99

0 D W 06/07/99

0 D W 06/14/99

0 D W 06/21/99

3000 D W 06/28/99 3000

0 D W 07/05/99

0 D W 07/12/99

0 D W 07/19/99

0 D W 07/26/99

3000 D W 08/02/99 3000

618 D W 08/09/99 618


1500 11/30/98 0 0


0 0 0 1500 4500

TYPE

The type of schedule: delivery (DL) or shipping (SH). FASPAC treats

both as SH.

START DATE

END DATE

The start and end dates of the forecast (that is, they are horizon dates).

The previous data for this item/plant/PO, between these Start and End

dates, is erased before this current EDI data is processed by EDID.

ISSUE DATE

The date the EDI document was issued by your customer.

ISSUER

The issuer number of your customer’s employee who issued the forecast.

CUSTOMER

The FASPAC Customer Number of your customer.

ERROR MESSAGE

FATAL and WARNING messages from the EDID program.

If the following error message is displayed, the first five characters of the

EDI account number will be displayed in the CUSTOMER column.


PART #

Your customer’s EDI part number. This must match the Customer Item

Number field in BGIM/MAI or the cross-reference in the

Cross-Reference file.

P.O. NUMBER

Your customer’s PO number. This must match the BGIM PO Number.

U/M

The customer’s EDI Unit of Measure. The FASPAC BGIM Unit of

Measure field must match this value.

PRODUCTION CTL

The customer’s engineering level number.

LINE FEED

The customer’s plant line feed location.

3 - 22 FPD/319-03


DROP POINT


DOCK CODE

Your customer’s (optional) reference to a ship-to area within a plant.

PLANT

If the program finds the BCCR record, this is the FASPAC ship-to

number. If it does not find the BCCR record, this is the EDI plant ID.

PATTERN

The EDI delivery pattern.

The next section lists, for each item, demand detail required by your

customer.

RECORD NET

The raw EDI quantity coming from your customer’s EDI transaction.

TYPE

The customer’s confidence level of the quantity and timing of the 830

transaction:

C = Firm Requirement.

D = Planned Requirement, subject to change.

FASPAC ignores all other codes.

TIMING

Indicates the interval grouping of the data. An * next to the Timing

column indicates that the 830 planning transaction is overridden by an

862 shipping transaction.

D = Discrete (this code is ignored by FASPAC)

C = Daily

W = Weekly

M = Monthly

SHIP DATE

Monday’s date of the week your customer requires items to be shipped.

MONDAY through SUNDAY

The quantity based on your daily ship code in BCIM.

FPD/319-03 3 - 23


The following fields are customer information:

REQD CUM

Your customer’s requirements, before the requirements shown in the

NET column of the report. This value includes the total requirements

since the start of the contract. This value, minus the Cum Shipped value,

represents the total outstanding requirements at this time, as perceived by

the customer.

CUM START

The date when the cumulative tracking began.

CUM END DATE

The date when the cumulative number was captured.

LAST SHIP QTY

Your customer’s EDI record of the last quantity received.

LAST SHIPPED DATE

Your customer’s EDI record of the last shipped date.

CUM SHIPPED

Your customer’s EDI record of the total quantity received within this

contract. This number must match the BCIM second screen Total

Quantity Invoiced field.

If the two are different, FASPAC then tries to match the Total Quantity

Invoiced against the CUM SHIPPED value, plus the quantity last

shipped by FASPAC.

If there is still a discrepancy, an error message will be displayed: YTD

Cum’s Out Of Balance. The error must be examined, and corrected

if necessary, before you run PLFM.

CUM SHIP DATE

The date for which your customer has calculated the CUM SHIPPED

quantity. This date is not used by FASPAC.

3 - 24 FPD/319-03


The following fields are FASPAC information:

OUR CUMS

Your total invoice quantity from the BCIM second screen, Total

Quantity Invoiced field. This field is updated each time an EDI order is

invoiced, and each time a manual order is entered using F6-Alternate

Customer in OD is invoiced (any SRS orders invoiced).

Note: To calculate net requirements, FASPAC does not create demand

until the REQD CUM plus NET quantities exceed the OUR CUMS

value.

If OUR CUMS is less than the CUM SHIPPED, FASPAC will

compensate by creating an immediate additional demand for the

difference, to bring the values back in line. This is why it is imperative to

ensure in the initial setup that the BCIM second screen Total Quantity

Invoiced field is correct, and that any errors on the EDID report are

thoroughly investigated and corrected.

LAST SHIP

The last ship quantity from FASPAC for any SRS orders ship confirmed,

whether entered through OD or EDI.

TOTAL SHIP

The total quantity shipped from FASPAC for any SRS orders shipped

but not invoiced.

FABRICATE

The cumulative quantity that your customer has approved for fabricating.

MATERIAL

The cumulative quantity that your customer has approved for purchasing

raw material.

FPD/319-03 3 - 25


Example of an EDI 862 Shipping Transaction

Field and Column Descriptions

TRANSACTION SET

The type of EDI transaction (862).

GROUP

The Customer Group in BCCR.

PURPOSE

An EDI code that describes the purpose of the transaction. FASPAC

treats all purposes as 05 (replace).

REFERENCE

Your customer’s release number.

ISSUE DATE

The date the EDI document was issued from your customer.

START DATE

END DATE

The start and end dates of the forecast (that is, they are horizon dates).

The previous data for this item/plant/PO in the requirements files,

between the first release and last release dates, are erased before this

current EDI data is processed by EDID.

3 - 26 FPD/319-03




RUN BY: WPD 14:38

=================================================================================================================================


GROUP PURPOSE REFERENCE ISSUE DATE START DATE END DATE ISSUER CUSTOMER PLANT ERROR MESSAGES

HOND 05 05/10/99 05/10/99 05/25/99 14081 No Customer Cross Reference Found! **E**

Customer Part not in Buyer’s Group! **E**

PART # EXPEDITOR PHONE DOCK LINE FEED DEL. YEAR DROP POINT

30022554 J

RECORD NET 862 ADJUST ORIG QTY REQD NET CUM QTY TYPE SHIP DATE SHIP TIME

240 240 39483 39483 C D 05/10/99 15:00

0 280 0 39483 C D 05/11/99 15:00

0 320 0 39483 C D 05/12/99 15:00

0 320 0 39483 C D 05/13/99 15:00

0 280 0 39483 C D 05/14/99 15:00

1560 360 1560 41043 C D 05/17/99 15:00

0 280 0 41043 C D 05/18/99 15:00

0 320 0 41043 C D 05/19/99 15:00

0 280 0 41043 C D 05/20/99 15:00

0 0 41043 C D 05/21/99 15:00

880 880 41923 C D 05/24/99 15:00

AUTH QTY CUM START CUM END DATE LAST SHIP QTY LAST SHIP DATE YTD CUM QTY

39243 05/29/97 05/10/99 39879 0

ISSUER

The issuer number of your customer’s employee who issued the forecast.

CUSTOMER

The FASPAC Customer Number of your customer.

PLANT

If the program finds the BCCR record, this is the FASPAC ship-to

number. If it does not find the BCCR record, this is the EDI plant ID.

ERROR MESSAGES

FATAL and WARNING messages from the EDID process.

If the following error message is displayed, the first five characters of the

EDI account number will be displayed in the CUSTOMER column.


PART #

Your customer’s reference for the Item Number. This must match the

Customer Item Number field in BGIM/MAI or the cross-reference in the

Cross-Reference file.

EXPEDITOR

PHONE

Your customer’s expeditor code and phone number.

DOCK

Your customer’s (optional) reference to a ship-to area within a plant.

LINE FEED

The customer’s plant line feed location.

DEL. YEAR

Your customer’s delivery year.

DROP POINT


FPD/319-03 3 - 27


The next section lists, for each item, demand detail required by your

customer.

RECORD NET

Displays the quantity required for each ship date.

862 ADJUST

The quantity that was required before today’s date. If there is a value in

this column, the following message is printed.

862 Adjustment Made Please Check

ORIG QTY

The original 862 quantity from the EDI transaction before it has been

processed in FASPAC.

REQD NET

The quantity to be shipped to the customer.

CUM QTY

The cumulative quantity.

TYPE

The first column is the customer’s confidence level of the quantity and

timing of the 862 transaction:

C = Firm Requirement.

D = Planned Requirement, subject to change.

FASPAC ignores all other codes.

The second column is the interval grouping of the data.

D = Discrete (this code is ignored by FASPAC)

C = Daily

W = Weekly

M = Monthly

SHIP DATE

SHIP TIME

The date and time your customer requires items to be shipped.

AUTH QTY

The cumulative quantity required before this scheduled release.

CUM START

The date when the cumulative tracking began.

3 - 28 FPD/319-03


CUM END DATE

The date when the cumulative number was captured.

LAST SHIP QTY

Your customer’s record of the last quantity received.

LAST SHIP DATE

The last shipped quantity from FASPAC for any SRS orders invoiced

either through OD (using F6 and F11) or EDI.

YTD CUM QTY

Your customer’s EDI record of the total quantity received within this

contract. This number must match the BCIM second screen Total

Quantity Invoiced field.

If the two are different, FASPAC then tries to match the Total Quantity

Invoiced against the CUM SHIPPED value, plus the quantity last

shipped by FASPAC.

If there is still a discrepancy, the following error message will be

displayed:

YTD Cum’s Out Of Balance

The error must be examined, and corrected if necessary, before you run

PLFM.

After running EDID and correcting any errors, it should be run again

immediately, to confirm the changes made, and there are no more errors. This

must be done before either receiving further EDI data (REDI), or running PLFM.

After this, PLFM can be run to create a quote for the next ship date.

Note: A demand is not created in FASPAC until the cumulative net requirements

for a date are equal to or greater than the BCIM Minimum Ship Quantity.

FPD/319-03 3 - 29


EDI Requirements Received for Previous ShipDates

EDID will take any requirements for previous ship days and add them to the next

possible shipment date.

Example:

Data Received: Monday, Week 0

Customer EDI Requirements EDID Data Population

Cum Required: 500

Cum Shipped: 600

Monday, Week -2: 100

Monday, Week -1: 100

Monday, Week 0: 100 200



The customer required 500 pieces before the schedule and has received a total of

600 pieces. The total requirements by Week 0 are 800 pieces (500 (cum) + 100

(Wk-2) + 100 (Wk-1) +100 (Wk-0). Therefore, outstanding requirements for the

current week (Wk 0) are 200 (800 required - 600 shipped).

If there are no requirements for the current week or in the future, the previous

requirements will create a new record for the next shipment date.

3 - 30 FPD/319-03


EDI Past Due

If there is a Past Due quantity, the EDI data received will include this amount

because it is still an outstanding requirement for the customer. EDID flags the

BCIM Past Due quantity as having been re-populated (that is, EDID has been

run).

If the next date with shipment requirements is beyond the BCIM Advance Ship

Days, this quantity will not be created as a quote by PLFM, but it will still be

seen as Past Due.

The requirement will be lost from view when quotes are automatically created,

until an EDI document is received with a next ship date within the PLFM range.

However, the requirement can still be identified and ordered manually. The

quantities in this case can be identified by running a Past Due Report

immediately after PLFM. This will identify all Past Due quantities in this

situation.

If there are no requirements for the current week or in the future, the Past Due

requirements will not be added to the requirements files, but will be seen in the

Past Due Report using the above procedure.

FPD/319-03 3 - 31

EDI PAST DUE

How EDID Calculates Demand in FASPAC

Example 1: Pulling Exact Quantity, No Minimum Ship Quantity

This is based on the Cum Adj flag in BCCR being set to Y.

BCCR Use Pull Method: E (E = Exact Quantity Only)

BCIM Minimum Ship Qty: 0

BCIM Container Quantity: 100 (This is ignored if Pull Method = E)

BCIM Daily Ship: F (F = Wednesday)

The REQD CUM of 134 is added to the first requested shipment of 60, and the

total of 194 is compared to OUR CUMS of 216. If it is less, no shipment will be

made.

The second requested shipment of 12 is added to 194 for a total of 206. It is still

less than OUR CUMS of 216, so there is no shipment for the second schedule.

The third requested shipment is for 60, which is added to 206 for a total of 266.

This is compared to OUR CUM of 216. There will be a shipment of 50, the

difference for that week.

3 - 32 FPD/319-03



GROUP PURPOSE MY RELEASE TYPE START DATE END DATE ISSUE DATE ISSUER CUSTOMER ERROR MESSAGEHOND 05 00000000 DL 01/06/99 12/01/00 01/21/99 12345

PART# PO NUMBER U/M PRODUCTION CTL LINE FEED DROP POINT DOCK CODE PLANT002546327 05214123 EA 01

RECORD NET TYPE TIMING SHIP DATE SUNDAY MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY

60 C W 01/06/9912 C W 01/13/9960 D M 03/01/99 5048 D M 04/01/99 4866 D M 05/01/99 6648 D M 06/01/99 480 D M 08/01/99

24 D M 09/01/99 2436 D M 10/01/99 3636 D M 12/01/99 36

REQD CUM CUM START CUM END DATE LAST SHIP QTY LAST SHIP DATE CUM SHIPPED CUM SHIPPED DATE134 24 09/24/98 216 09/24/98

OUR CUMS LAST SHIP TOTAL SHIP FABRICATE MATERIAL216 0 0 0 0

Example 2: Pulling Exact Quantity, Minimum Ship Quantity=50

BCCR Use Pull Method: E (E =Exact Quantity Only)


BCIM Container Quantity: 100 (This is ignored if Pull Method =E)

BCIM Daily Ship: F (F =Wednesday)



made.




This is compared to OUR CUM of 216. There will be a shipment of 50, the

difference for that week.

The next week the requirement is for 48, but that is below the minimum so there

will not be a shipment. The following week’s requirement is 66, which will be

shipped.

FPD/319-03 3 - 33

HOW EDID CALCULATES DEMAND IN FASPAC





60 C W 01/06/9912 C W 01/13/9960 D M 03/01/99 5048 D M 04/01/9966 D M 05/01/99 6648 D M 06/01/990 D M 08/01/99

24 D M 09/01/9936 D M 10/01/9936 D M 12/01/99



Notes about Minimum Ship Quantity

When the required quantity for a date is less than the minimum ship quantity

specified in field 06 Min. Ship Qty in BCIM:

• If field 07 Adjust Quantity To Minimum in SYS/BCS is set to N, the

required quantity will not be included in requirements. This quantity is lost

from view and will never be created as a customer order in FASPAC.

• If BCS field 07 is set to Y, the required quantity will be automatically

increased to match the minimum ship quantity and the future demands will

be reduced.

3 - 34 FPD/319-03


Example 3: Pulling Whole Container Quantity, Minimum Ship Quantity=50

BCCR Use Pull Method: W (W =Whole Cartons Only)


BCIM Container Quantity: 100

BCIM Daily Ship: F (F =Wednesday)



made.




This is compared to OUR CUM of 216. There will be a shipment of 100 because

of the Whole Carton option (see page 2-15).

The next week’s requirement is 48, but that is below the minimum so there will

be no shipment.

The following week’s requirement is 66 and 100 will be shipped because of the

Whole Carton method (see page 2-15).

FPD/319-03 3 - 35

HOW EDID CALCULATES DEMAND IN FASPAC





60 C W 01/06/9912 C W 01/13/9960 D M 03/01/99 10048 D M 04/01/9966 D M 05/01/99 10048 D M 06/01/990 D M 08/01/99

24 D M 09/01/9936 D M 10/01/9936 D M 12/01/99



Notes about Minimum Ship Quantity

When the required quantity for a date is less than the minimum ship quantity

specified in field 06 Min. Ship Qty in BCIM:

• If field 07 Adjust Quantity To Minimum in SYS/BCS is set to N, the

required quantity will not be included in requirements. This quantity is lost

from view and will never be created as a customer order in FASPAC.

• If BCS field 07 is set to Y, the required quantity will be automatically

increased to match the minimum ship quantity and the future demands will

be reduced.

3 - 36 FPD/319-03


Manual Releases

There are two methods for manually entering scheduled requirements instead of

receiving them through 830 or 862 EDI transactions:

• Using the Buyer Customer Item Maintenance (BCTS/BCIM/MAI)

program—you must enter the Customer Group and Item Number

• Using the Buyers Ship-To Items (BCTS/BCIM/BSTI) program—you must

enter the Customer Number and Ship-To Code

Buyer Customer Item Maintenance(BCTS/BCIM/MAI)

Use this program to manually enter scheduled requirements for each date

required by the customer. The actual ship date displayed is determined by the

value in the Daily Ship and Adv Ship Days fields in BCIM screen one.

Caution: Manual releases should not be entered for items with EDI transactions.

EDI transactions will override manual releases if found in the requirements file.

As release requirements are updated by the customer, you can modify the values

entered in this program.

The remaining steps to create orders for firm requests is the same as those for

processing EDI transactions (by running PLFM and PLO, and resuming quotes

in OD).

FPD/319-03 3 - 37


Creating manual releases adds records to the firm or planning requirements files

the same as EDID, but these records are internally flagged as generated by

manual releases.

After PLFM has been run, the records for which a quote has been generated are

flagged that PLFM has been run, and they no longer display on the initial manual

release maintenance/inquiry screens.

Note: There is no place in FASPAC that will indicate this order was originated

by a manual release.





To manually enter scheduled requirements:

1.1. From a FASPAC menu, enter BCIM/MAI. The cursor starts in the Cust.

Group field.

2.2. Enter the Customer Group ID. The cursor starts in the Item No. field.

3.3. Enter the item number. The cursor starts in the Reference No. field.

4.4. Press CMD+L and then press Return on the record you want to

manually release. The information is displayed and the cursor moves to

the SELECT prompt.

5.5. Press F2 to display the Manual Release Maintenance screen.

3 - 38 FPD/319-03


CMD+L

CMD+L

The cursor starts in the Release No field.

6.6. Enter the release number provided by your customer. Do not leave the

field blank. The cursor moves to the Release Date field.

7.7. Press Return to accept the sign on date or enter another date. The cursor

moves to the SELECT prompt.

8.8. Press F5 to add a scheduled requirement. The cursor moves to the Type

field.

9.9. Enter P for a planned scheduled requirement or F for a firm scheduled

requirement. The cursor moves to the Date field.

10.10. Enter the requested due date in MMDDYY format. The cursor moves to

the Net field.

11.11. Enter the requested quantity. The cursor moves to the Release/PO

Number field.

If BCS field 07 is set to Y and you enter a quantity that is less than the

minimum ship quantity, the following message is displayed:

Quantity entered is less than BCIM minimumquantity. It will be increased to BCIM minimum -SKIP

12. Enter a release or PO number, or leave the field blank and press Return.


All Entries OK? (Y/N)

13. Enter Y if you want to add the next entry, or N if you want to change the

entry you just made. In both cases, the following question is displayed:

More Entries? (Y/N) Y

14. Enter Y to add more scheduled releases, or N to finish. The cursor moves

to the SELECT prompt.

15. Press F10 or SKIP to update the record and exit this screen. The first

BCIM screen is redisplayed.

16. Press SKIP and add another release, or press SKIP again to exit.

Field Explanations

For the first screen, see page 2-28 for field descriptions.

The following fields are for the Manual Release Maintenance screen. The header

fields are the same as the first screen and are for information only.

Release Number

Identifies a particular release and is issued by the customer.

FPD/319-03 3 - 39


Release Date

The sign on date, which can be changed.

Type

The type of demand:

F = Firm Requirements

P = Planned Requirements

You can enter up to 99 requirements.

Note: Only the firm requirements will be converted to a quote when

PLFM is run. The Planned requirements need to be manually changed to

Firm when necessary in this program.

Date

The due date (when this quantity is to arrive at the customer’s site).

The system looks in field 17 of BCIM/MAI for the advance ship days. If

that field is blank, it looks in field 17 of BCCR/MAI for the advance ship

days.

The system subtracts the advance ship days from the due date, and then

adjusts the actual ship date to be the next shipping day specified in field

4 of BCIM/MAI

Net

The actual quantity required. This should not include any Past Due

quantities since PLFM and PLO consider the Past Due value when

creating the quotes.

If field 07 Adjust Quantity To Minimum in BCS is set to Y and a

minimum ship quantity was entered in field 06 Min. Ship Qty in BCIM,

the following message is displayed if you enter a quantity that is less

than the minimum ship quantity:

Quantity entered is less than BCIM minimumquantity. It will be increased to BCIM minimum -SKIP

For example, field 06 in BCIM is set to 1000 and you enter 500 in the

Net field. When you press Skip, the quantity in the Net field will be

changed to 1000.

Note: The requirement files are not updated at this point; they are

updated when you press F10 to update the record.

Cum

The running total of the Cum Ship field and the Net column.

3 - 40 FPD/319-03


Ship Date

The ship date is calculated by FASPAC based on the value in the Daily

Ship and Adv Ship Days fields in BCIM/MAI.

If the requirements are entered for a Monday, but the Daily Ship code is

for a Thursday, the date here would be the Thursday following the

Monday’s date.

Note: The date displayed in TPIM is this Ship Date.

Function Keys

F1-Start

Displays the first 10 scheduled requirements.

F3-Next

If there are more than 10 scheduled requirements, this displays the next

10 requirements (that is, it scrolls to the next page). This is not available

if there are not more than 10 requirements.

F4-Show All

Displays the Quote/Order Number and Status columns, and all

requirements entered for this release.

The status codes are:

Not Attch—Indicates that PLFM has not been run.

Purge Rec—Indicates that the release requirement has been deleted.

Ordered—The individual quote has been resumed and converted to an

order in OD.

Held—PLFM or PLO has been processed, but the quote has not been

converted to an order in OD.

Canceled—The quote was canceled in QMA.

Unknown—A system error has occurred, typically when the program

cannot find the data.

Note: If there is no existing release, enter a release number and date and

then press F4 to display all previous release information.

F5-Add Mode

Allows further scheduled requirements to be entered. The existing

requirements are cleared from this screen.

When additions have been completed, all requirements are then

displayed, including those previously entered, sorted by date required. If

requirements are added for a date previously entered, the new

requirements are added to the existing requirements for that date.

FPD/319-03 3 - 41


F8-Chg Release

Moves the cursor to the Release No. field to change the release number

or release date, if required. This is to ensure FASPAC is current with the

release number supplied by the customer.

F10-Update

Updates the information entered in the firm and planning requirements

files. If you enter N to the question OK To Update, the changes are

retained in the manual release file but the requirements files are not

updated.

F12-Purge

Deletes all scheduled release requirements for this release number

through an entered date.

To delete a single scheduled release, enter that line number at the

SELECT prompt and enter Y to the question Delete Entry Number

nn? (Y/N). If you enter N, the cursor moves to the Type field of that

line where you can make changes.

SKIP-Exit

Exit this program and return to the BCIM screen. If changes have been

made but F10-Update has not been pressed, the prompt OK To Update

is displayed.

You can also press CMD-Q to update, exit, and return to the FASPAC

menu

If you enter N to the question OK To Update, the changes are retained

in the manual release file but the requirements files are not updated.

3 - 42 FPD/319-03


Buyers Ship-To Items (BCTS/BCIM/BSTI)

You can use this program to access the Buyer Customer Item Maintenance

(BCTS/BCIM/MAI) program. When a record is retrieved, you can then select a

line number and display the BCIM screen for that record. From there you can use

the F2 function for manual releases.


The following are instructions for entering data in this screen.


To display the BCIM screen for an item:

1.1. From a FASPAC menu, enter BCIM/BSTI. The cursor moves to the

Customer field.

2.2. Enter the customer number. The cursor moves to the Ship To field.

3.3. Enter the ship-to code. All items for this customer and ship-to

combination are displayed and the cursor moves to the SELECT prompt.

4.4. Enter the line number for the item. The BCIM/MAI screen is displayed.

5.5. Go to page 3-37for information about the Buyer Customer Item

Maintenance (BCTS/BCIM/MAI) program.

FPD/319-03 3 - 43

BUYERS SHIP-TO ITEMS (BCTS/BCIM/BSTI)

CMD+L

CMD+L

Time Phased Management Inquiry

You can view all purchasing and planning requirements for a scheduled release

in the following program in the Time Phased Management (TPIM) module.

Note: This is the same program as the Inventory Control Production Planning

(MFG/MFI/MFPP) in the Manufacturing module.

For more information about TPIM, refer to the Time Phased Inventory

Management Reference Manual in Volume 3.

Inventory Management Exception (TPI/TPIM)

There are four screens of questions and options where you can select options for

your inquiry:

• The standard FASPAC inventory report screen

• Inflows to the inquiry

• Outflows from the inquiry

• Miscellaneous criteria (Other Issues)

You can either save all responses to a file that can be run whenever you want or

select options for this time only.

When you first see each screen, there are two functions available before you

select any options:

• F8 will accept the currently displayed screen and the remaining screens. If

you press it, the screens will not be displayed.

• F10 will accept the currently displayed screen only and display the next

screen.

You can use either of these functions if you are satisfied with the selections and

do not want to go through all four screens.

3 - 44 FPD/319-03



The following are instructions for entering data in this screen. They assume you

will be going through all the screens and not using the F8 or F10 functions.


To inquire on requirements for a scheduled release:

1.1. From a FASPAC menu, enter TPIM.

Either the standard FASPAC inventory report screen or a screen with

previous saved files will be displayed.

2.2. If previous saved files are listed, press CMD. The following prompt is

displayed:

Use Previously Collected Information? (Y/N)

3.3. Enter N. The standard FASPAC inventory report screen is displayed.

4.4. Enter Y to continue and answer the questions.

5.5. When you are satisfied with the answers, enter N at the following

prompt:

Any Changes (Y/N)

FPD/319-03 3 - 45

INVENTORY MANAGEMENT EXCEPTION (TPI/TPIM)

6.6. The Inflows screen is displayed.

7.7. Select Inflow options by entering Y in the appropriate fields.

8.8. If you are satisfied with the answers, enter N to the prompt Any

Changes (Y/N). The Outflows screen is displayed.

9.9. Select Outflow options by entering Y in the appropriate fields.

10.10. In the Use 862s and Use 830s fields, you can enter Y in only one field,

not in both. This is because of the way FASPAC works with the 862 and

830 firm and planned releases.

3 - 46 FPD/319-03


The hierarchy is:

862 F

862 P

830 F

830 P

How it works:

If you enter Y in the Use 862s field and P in the Firm, Plan Or Estimate

field, the 862 planned and firm releases will be considered. The Use 830s

field is skipped.

If you enter N in the Use 862s field, Y in the Use 830s field, and F in the

Firm, Plan Or Estimate field, the 862 firm and planned and 830 firm

releases are considered.

If you want to include everything, enter N in the Use 862s field, Y in the

Use 830s field, and P in the Firm, Plan Or Estimate field.

Note: In the Firm, Plan Or Estimate field, E is not currently used.


Changes (Y/N). The Other Issues screen is displayed.

12.12. Enter the Customer, EDI, and Buyer groups, or press Return in those

fields to accept All.

13.13. Enter the date range for the information you want to see.

FPD/319-03 3 - 47


14.14. If you specified a warehouse in the first TPIM screen, the Warehouse

field is skipped.

If you selected ALL warehouses in the first TPIM screen, this

Warehouse field is asking for the warehouse whose minimum and

maximum position will be used to assess “out of control” parts.

15.15. To see the out of control items, enter N in the Ignore Minimum and

Ignore Maximum fields. For each, you can enter a percentage to

temporarily increase or decrease the minimum or maximum stock levels.

16.16. If you selected Manufacturing inflows, you can sort by Ship Date, Due

Date, or Estimated End Date and specify the source of the standard cost.


Changes (Y/N).

18.18. Enter Y at the prompt OK To Continue (Y/N) or N to exit the

program.

19.19. If you want to save your responses in the four screens for use at another

time, enter Y and then enter a file name. If you enter N, the program will

run but the responses will not be saved.

20.20. The program displays the number of records found and the prompt OK

To Continue? (Y/N). If you want to redo your selections, enter N.

If you want to continue with the process, enter Y. A screen similar to the

following will be displayed.

3 - 48 FPD/319-03


21.21. To view details for an item, enter the line number. A screen similar to the

following is displayed.

22.22. Press F3 to display the next page of information.

23.23. Press F7 to print this list to your Other printer, F9 to select another item

to review, or F10 to exit the program.

The inflow and outflow source codes are explained in the following sections.

FPD/319-03 3 - 49


Inflow Source Codes

T-S Code Source Of Supply

P - O Purchase Order

PIO In-transit Order Desk Purchase Order

W - T Warehouse Transfer

R - O Rework Order

K - T Kitting Order

M - A Authorized Manufacturing Job

M - O Ordered Status Manufacturing Job

M - R Reserved Status Manufacturing Job

Outflow Source Codes

T-S Code Source Of Demand

SO Sales Order

SHO Shipped Order

W - T Warehouse Transfer

K - T Kitting Order

3 - P EDI 830 Planning transaction from the SRS System (of “lower”weight than a “firm” 830)

3 - F EDI 830 Firm Planning transaction from the SRS System.

6 - P EDI 862 planned Shipping transaction from the SRS System (of“lower” weight than a “firm” 862)

6 - F EDI 862 Firm Shipping transaction from the SRS System

M - F A Firm Manual Release forecast from the SRS System

M - P A Planned Manual Release from the SRS System (consideredof “lower” weight than a “firm” release)

M - A Authorized Manufacturing Job

M - O Ordered Status Manufacturing Job

M - R Reserved Status Manufacturing Job

P - D Past Due EDI from the SRS System

P - P Past Due is repopulated

3 - 50 FPD/319-03


4Processing Orders

This chapter tells you how to process the orders that you

acquired in the previous chapter.

After you have imported and translated the shipping requirements from your

customer, you are ready to process the orders in FASPAC.

The tasks you will be performing are:

1.1. Creating a temporary quote for the entire customer group in the Create a

Pull List (OP/SHP/SHC/PLFM) program. You can automatically commit

tags to the quote FIFO if the WCS option is yes.

2.2. Using the Create Quotes from Pull List (OP/SHP/SHC/PLO) program to

create individual quotes from the temporary quote for the individual

customer, item, plant, and PO number. The lines on the temporary quote

are automatically deleted as the individual quote is being created.

A report is printed showing the individual quotes that were created in

PLO.

3.3. In Order Desk (OD), you can refer to the PLO report for the necessary

information to resume the quote and turn it into an order.

4.4. Running the Shipping Confirmation (SC) program to update the shipped

fields in the BCIM file.

5.5. Finally, runing the Invoice Calculation (INC) program to update the

invoiced fields in the BCIM file.

FPD/319-03 4 - 1

Create a Pull List (OP/SHP/SHC/PLFM)

Use this program to create a temporary quote for the generic customer that was

created in CP/MAI (the generic customer number is the customer group plus 9).

This is the customer number that will be displayed in FASPAC when viewing the

quote in Customer Quote Maintenance (OP/OPQ/QMA).

You can also edit an existing quote if you have not run PLO for it.

The quote will only include the items that are due on the day this is run. PLFM

uses the firm requirements from EDID or firm manual orders. As an item is

added to the quote, the corresponding Item/Plant/PO record is amended with the

quote number and line number for which PLFM was run.

The main features of the PLFM program are:

• Only firm orders are processed.

• No report is printed.

• Requirements can be viewed in five day increments.

• A requirement can be edited.

4 - 2 FPD/319-03

PROCESSING ORDERS




To create a new pull list (PLFM quote):

1.1. From a FASPAC menu, enter PLFM. The cursor starts in the Whse field.

2.2. Enter the warehouse number. The following question is displayed at the

bottom of the screen:

Are You Creating a New Pull List?

3.3. Enter Y to create a new pull list (PLFM quote) for a specific ship date.

the following prompt is displayed at the bottom of the screen:

Enter Pull List Date:

Note: Only one quote per customer group, per date, can be created. If

you try to create a new pull list after PLO was processed, the following

message will be displayed: Pull List Already Converted

The default pull list date is the next working day (after your sign on

date). You can change it to the date when the quote is to be created. The

date is usually for the current date or next day. If a Saturday or Sunday

date is entered, the following message will be displayed.

Warning. Saturday or Sunday Date Entered, Continue

(Y/N)

4.4. Press Return to accept the default date or enter a different date. The

cursor moves to the Group field.

5.5. Enter the customer group name. The cursor moves to the Continue

prompt at the bottom of the screen.

6.6. At the Continue prompt, enter Y. The Pull List is created and the cursor

moves to the Part Number field.

Entering N exits the program.

If a Pull List has no requirements for the date entered, or a prior pull list

had not been created for that date, one of the following error messages is

displayed:

No Pull List Was Created for this Group and

Day—SKIP

Or,

No Prior Pull List Created to Resume—SKIP:

FPD/319-03 4 - 3

CREATE A PULL LIST (OP/SHP/SHC/PLFM)

When you press SKIP, the program quits and the FASPAC menu is

displayed.

7.7. In the Part Number field, enter the item to be viewed or edited.

This can be either the FASPAC part number and press F1 or the

FASPAC short name and press F2. If the customer part number has been

created in CR/MAI, you can enter ! followed by the customer part

number.

8.8. The field OTHER PARTIAL is displayed. For each container type, the

available quantity and number of tags is displayed.

The information for the release is displayed: the plant, the quantity and

when it is due, the package/carton code, quantity in each package, how

many is needed, and how many should be pulled.

9.9. The following functions are listed at the bottom of the screen:

• F1-Display PO Window—Displays a pop-up window showing the

PO number and reference number information.

• F3-Pull Ctns Shown—Recalculates the pull number based on the

available quantity and updates the record. This is only valid when

you are committing tags to quote.

• F4-More Plants—Displays the next page if there are more than 10

plants.

• F5-Next Part—Select the next item if applicable.

10.10. Press SKIP when finished to exit the program.

To resume working with an existing pull list (PLFM quote):





3.3. Enter N to edit the requirement. The following question is displayed:

Are You Resuming a Previous Pull List?

4.4. Enter Y to edit an existing pull list. The following prompt is displayed:


Note: Maintenance can only be performed before running PLO for the

customer group/date combination.

5.5. Enter the Pull List Date. The cursor moves to the Group field at the top

of the screen.

4 - 4 FPD/319-03

PROCESSING ORDERS

6.6. Enter the customer group name. The cursor moves to the Continue

prompt at the bottom of the screen.

7.7. Enter Y. The Pull List is resumed and the cursor moves to the Part

Number field.

Entering N exits the program.

8.8. You can make the following changes to the pull list:

a) To add items to the pull list by pressing F6 (Add Part). The required

quantity may be added only for the first date displayed on the screen.

b) Quantities for existing quote lines may be modified. The line number

of the correct plant displayed on the screen is entered to display

detail.

c) An increase or decrease in quantity records the new quantity in the

quote. If the quantity is edited to zero the original required quantity

is updated in the BCIM Past Due field.

d) If tags are committed to the quote during PLFM, these may be

un-committed and re-committed if required. For resuming the pull

list, there will be a prompt:

Reset Committed Tags On Pull List? (Y/N)

e) If you enter Y, the process of resuming a pull list un-commits the

tags, and then re-commits them, based on the revised requirements

and the current tag status.

f) The Container Type and Quantity may also be edited in this

program.

To preview five days of requirements:

Note: This is a inquiry only; it will not create a quote.





3.3. Enter N. The following question is displayed:

Are You Resuming a Previous Pull List?

4.4. Enter N.The following prompt is displayed:


5.5. Enter the start date for five days of requirements. The cursor moves to

the Group field.

6.6. Enter the the group name. The cursor moves to the Part Number field.

FPD/319-03 4 - 5

CREATE A PULL LIST (OP/SHP/SHC/PLFM)

7.7. Type / and then press F1 to start the search from the beginning of the

Inventory file.

The following message is displayed at the bottom of the screen:

Nothing to Process! - SKIP

8.8. Press Return. The cursor returns to the Part Number field and displays

the first item for this group for this date.

9.9. Press F5 to display the next part number.

10.10. When finished, press CMD+Q to exit the program.

Files pdated by PLFM

When PLFM is run, the records in the Firm file (pf09) are examined to determine

which items and quantities should be added to the temporary quote. As an item is

added to the quote, the corresponding item/plant/PO record in pf09 is amended

with the quote number and the date for which PLFM was run.

Once a quote is in the pf09 file, no modification can be made through EDI or

manual releases.

4 - 6 FPD/319-03

PROCESSING ORDERS

Create Quotes from Pull List

(OP/SHP/SHC/PLO)

Use this program to convert the temporary quote for the customer group into

individual quotes for the customer, plant, and PO number information according

to BCIM.

• A report is printed to the Other printer as defined for your login ID.

• As a line item is created on the individual quote, it is canceled on the

temporary quote.

• The temporary quote is still on file, but all lines are canceled.

• If tags were committed to the temporary quote, they will now be

committed to the individual quote.




To convert a temporary quote to individual quotes:

1.1. From a FASPAC menu, enter PLO. The cursor starts in the Whse field.

2.2. Enter the warehouse number. The cursor moves to the For all Customer

Groups (Y/N) field.

FPD/319-03 4 - 7

CREATE QUOTES FROM PULL LIST (OP/SHP/SHC/PLO)

3.3. Enter Y to include all customer groups. The cursor moves to the Create

Orders for Date field. Go to step 4.

Or, enter N to specify one or more customer groups. The From Group

and Thru Group fields are displayed.

4. If you entered N in the previous field, enter the range of customer groups

in the From Group and Thru Group fields. The cursor moves to the

Create Orders for Date field.

5. Enter the date when the PLO program is to be run.

Note: This should be the same date as when the PLFM program was run.

The following screen is displayed and the cursor starts in the Continue

prompt.

6. Enter Y to continue the process, or N to exit the program.

7. If you enter Y, the program processes your request and then exits when it

is finished.

4 - 8 FPD/319-03

PROCESSING ORDERS

PLO Pull List Orders Error Report

In the example above, 15649592 is the customer part number; BARON is from

the BCCR Their Cust No. field.

This report lists all orders and any error messages, if applicable.

The following error messages indicate that the records have been changed or

deleted after PLFM (and before PLO).

Customer Not Found

The CP/MAI record has been deleted.

Invalid Read od01 for Cancel

The temporary quote was deleted in QMA.

Invalid ReRead of New Quote

The generic quote was changed in QMA.

Invalid ReWrite od01 for Cancel

The temporary quote was changed in QMA.

Inventory Not Found

The IM/MAI Master record has been deleted.

Inventory Warehouse Not Found

The IM/MAI warehouse record has been deleted.

No Valid pf01 Record Exists

The BCCR record has been deleted.

No Valid pf03 Record Exists

The BGIM record has been deleted.

Ship To Customer Not Found

The CP/STM record has been deleted.

FPD/319-03 4 - 9

CREATE QUOTES FROM PULL LIST (OP/SHP/SHC/PLO)

COMPANY: 10 PAGE 1

RUN ID: PLO PULL LIST ORDERS ERROR REPORTRUN BY: WPD

QUOTE LINE CUSTOMER PO NUMBERITEM QUANTITY AVAILABLE ERROR MESSAGE

==========================================================================================================================================================================23276 001 12430 BARON 01933-02003 03/07/99 12:50:52 EDI

15649592

Order Desk (OD)

In addition to resuming quotes created by PLO, you can use the standard OD

functions to enter regular orders for Buyer Contract items and still update the

cumulative shipped and invoiced fields in BCIM.

There are two other times when you will use OD:

• Your customer sends you an EDI 830 transaction for purchasing planning,

but not an 862 transaction for a firm order. Your customer will notify you

when they want an order shipped.

• Your customer forwards an immediate requirement and the next shipping

schedule would be too late.

To tell FASPAC this order should update the Buyer Contract files, at the

Customer prompt press F6-Alternate Customer to select the correct plant from

BCTS.

If the item number you entered is on more than one PO for that plant, press

F11-Alternate Item and then select the correct Item/Plant/PO. This will ensure

that the correct BCTS files are updated during shipping confirmation and

invoicing.

Note: It is very important that you run Shipping Confirmation (SC) before

running EDID again.

EDID does not look at open orders when calculating requirements. If using EDID

to create demand, even if only to view requirements in TPIM or MFPP, it is

essential these orders are entered and ship confirmed, before running the next

EDID, otherwise demand may be duplicated.

After you have turned the quote into an order using Order Desk, you then process

it as normal using the Shipping Confirmation (SC) and Invoice Calculation (INC)

programs.

Note: We recommend using BCIM instead of OD if you are entering manual

orders without EDI transactions.

4 - 10 FPD/319-03

PROCESSING ORDERS

5Miscellaneous Programs

This chapter includes other programs you can optionally use

while working in the SRS module.

Change Customer Group

(BCTS/BCCR/CGRP)

Use this program to assign a customer and ship to location to a different group.

FPD/319-03 5 - 1

Customer Item History Maint.

(BCTS/BCIH/MAI)

If necessary, use this program to make corrections to an item’s purchase history

by your customer/ship-to location.

5 - 2 FPD/319-03

MISCELLANEOUS PROGRAMS

Customer Item History Inquiry

(BCTS/BCIH/INQ)

This program displays the item history for a customer/ship-to location. You

cannot make any changes in this program.

FPD/319-03 5 - 3

CUSTOMER ITEM HISTORY INQUIRY (BCTS/BCIH/INQ)

Buyer Customer Item (BCTS/BCIM/INQ)

This program displays the item information for a plant/ship-to location. You

cannot make any changes in this program.

5 - 4 FPD/319-03

BUYER CUSTOMER ITEM (BCTS/BCIM/INQ)

Buyer Group Item Maintenance

(BCTS/BGIM/MAI), Second Screen

The second BGIM screen displays the quantity, date, customer, ship-to, and

invoice number of the most recent invoiced shipment of this item, to any

customer ship-to within this group. It also displays the total quantity of this item

invoiced to all locations within this group, as well as the total value and cost.

These fields are updated in invoice calculation (INC).

These fields should not be maintained manually, unless you are instructed to do

so by a Faspac representative.

FPD/319-03 5 - 5

BUYER GROUP ITEM MAINTENANCE (BCTS/BGIM/MAI), SECOND SCREEN

Buyer Group Item Copy

(BCTS/BGIM/CPY)

Use this program to copy a group’s item from your customer’s purchase order to

another purchase order.

Note: Do not change the PO number in BGIM because it is the key FASPAC

uses for that record.

5 - 6 FPD/319-03


Group Item Inquiry (BCTS/BGIM/INQ)

This program displays the item information for a group/PO number.

FPD/319-03 5 - 7

GROUP ITEM INQUIRY (BCTS/BGIM/INQ)

Customer Inquiry

(SAL/BCTS/BGIM/CINQ)

This program displays all ship-to information associated with a group/item. This

is an inquiry only.

5 - 8 FPD/319-03


Past Due Report (BCTS/BCSR/PDR)

This report lists items that are considered past due if:

• In PLFM, you adjust a release quantity to zero

• In SC, you short-ship a number greater than the container quantity

(maintained in the BCIM record) and do not back order.

FPD/319-03 5 - 9

PAST DUE REPORT (BCTS/BCSR/PDR)

Demand Summary Report (BCTS/DSR)

This report lists large increases or decreases in the piece count.

5 - 10 FPD/319-03


Pull List Report (OP/SHP/SHC/PL)

Use this program to print a Pull List, which is very useful if you are committing

tags when creating the quotes in PLFM or PLO. The warehouse personnel will

use this list when pulling the items to be shipped.

You can run this report after PLFM, PLO, or OD.

You can use MSGS/MAI to add a note that will automatically print on the pull

list for the appropriate customer/item/ship to combination. To do this, create an

ISHP message for a note type of PULLL (Pull List).

Note: We do not recommend running this report if you are not committing tags

to quotes—the information is not useful otherwise.

The following are the main features of this program:

• Prints to the Other printer

• Pull List—Includes all items in the firm requirements file for which that a

quote has been generated for or orders generated in OD.

• Hot Sheet—Indicates the items to be pulled that are not committed or if

there is not enough stock.

• Option to include non-EDI orders

• Option to recommit tags to non-EDI orders

FPD/319-03 5 - 11

PULL LIST REPORT (OP/SHP/SHC/PL)

Field Explanations

Whse

Enter the Warehouse number.

Print Pull List, Hot Sheet or Both?

P = Pull list only

H = Hot sheet only

B = Pull list followed by the hot sheet

(O)ne EDI Group or (A)ll Customers or (N)o EDI Customers

O = One EDI customer group. This entry must match the BCCR record

for EDI orders. The associated customer number and ship-to in the

BCCR record must match the order for non-EDI orders.

A = All customer groups on the reports.

N = Reports are only for orders created in OD and will not include any

EDI orders.

Group

This field is displayed if you selected O in the previous field. Enter the

group name.

Include Non-EDI Sales Orders?

N = Orders created in OD are not to be included.

Y = Include orders created in OD with or without using the F6 and F11

option. The date wanted field is equal or prior to the Report Date.

Sort By

A through H as listed on the screen. Your choice will dictate the

headings and information on the report.

The following prompt is displayed:

Print Item or Shortname

I = FASPAC part number

S = Shortname

The first two columns of the report are always the part number and

ship-to. The option will indicate which is first, the part number or

ship-to. Whatever field is listed first in the option will be the first

column.

Examples:

Option A—Ship To/Line Feed/Part Number the ship-to will be the first

column, the part number will be the second column.

Option B—Customer Part Number /Ship To/Line Feed the part number

will be the first column, the ship-to will be the second column.

5 - 12 FPD/319-03


Print For All Parts?

Y = All items will be included.

N = Enter the item or range of items.

From Faspac Part

Thru Faspac Part

These fields are displayed if you entered N in the previous field.

Report Date

Enter the same date when PLFM was created.

The following question is displayed:

Recommit Stock to Non-EDI Orders (Y/N)

Y = You can recommit tags through FIFO in the event additional

receiving has been done.

OK To Continue

Enter Y to run the program, or N to exit.

FPD/319-03 5 - 13

PULL LIST REPORT (OP/SHP/SHC/PL)

Buyers Ship-To Copy

(BCTS/BGIM/BSTC)

Use this program to copy all items from a customer and ship-to combination to

another customer and ship-to combination.

For example, you have a customer with five ship-to locations. After you have set

up the first customer/ship-to record in BCIM, you can copy it to the remaining

four locations using this program.

5 - 14 FPD/319-03
