E Scheduling & Planning Transactions

This appendix contains these topics:

E.1 Objectives

  • To set up EDI scheduling and planning transactions for your Electronic Commerce system

E.2 About Scheduling and Planning Transaction Setup

When setting up the Electronic Commerce system, you need to specify how the system should handle your scheduling and planning transactions.

Complete the following tasks:

  • Receive planning schedule forecasts (830/DELFOR) -- P47061

  • Send planning schedule forecasts (830/DELFOR) -- P47062

Note:

This information is set up in UDC 40/ST from Menu G4731/4.

E.3 Receive Planning Schedule Forecasts (830/DELFOR)

Navigation

From Scheduling & Planning Transactions (G4725), choose Planning Schedule Forecast

From Planning Schedule Forecast (G47251), choose Inbound Edit/Update P47061

Run the Inbound Edit/Update program for planning schedule forecasts to receive planning schedule forecast transactions. Planning schedule forecast transactions are processed into the Forecast file (F3460).

E.3.1 What Happens when You Receive Planning Schedule Forecasts?

When you run Inbound Edit/Update for Planning Schedule - Forecast, the program:

  • Writes the transactions to the Forecast file (F3460) for further processing by the JD Edwards World MRP/DRP Requirements Planning system, if no errors are detected when editing the transactions.

E.3.2 Transaction Processing Mode

Each item in the Forecast file has a summary record by item number and branch plant. For all transaction codes except I, the system handles the forecast summary records as described in the following paragraphs.

Each EDI transaction for planning schedule forecasts has a transaction set purpose code, which is a user defined code (system 47/type PU). Each valid code corresponds to an action code of Add (A), Replace (R), Delete (D), or Inquire (I). If a code is not entered, the system uses R as the default and writes a warning on the error report.

The system processes each of these actions as follows:

Action Description
Add Adds detail records.
Replace The system replaces the forecast value in the detail record with the new forecast value.
Delete Deletes detail records.
Inquire The system displays information for the data you have requested. No database changes take place during an inquiry.

E.3.3 Report Processing

When you run Inbound Edit/Update, the system prints information on an error report and an audit report using the following process:

  • The system records each error that it encounters for the forecast records on the error report. The system does not process records that are in error unless the error is a warning. For forecast records that you want to delete, the system checks only the following fields for errors:

    • Transaction Set Purpose

    • Branch Plant

    • Date Requested

    • Item Number

    • Forecast Type

  • The system writes a line to the error report (R470611) for every inbound forecast record that contains an error.

  • The system writes a line to the audit report (R470612) for every forecast record that it processes.

E.3.4 Mapping Guidelines

The following fields in the EDI interface files must contain data before you can use the Inbound Edit/Update for planning schedule forecasts effectively:

  • Header Record (F47061):

    • EDI Document Number (MJEDOC)

    • EDI Document Type (MJEDCT)

    • EDI Document Key Company (MJEKCO)

    • EDI Transaction Set (MJEDST)

    • Send/Receive Flag = R (MJEDER)

    • Address Number (MJAN8)

  • Detail Record (F47062):

    • EDI Document Number (MYEDOC)

    • EDI Document Type (MYEDCT)

    • EDI Document Key Company (MYEKCO)

    • EDI Transaction Set (MYEDST)

    • Send/Receive Flag = R (MYEDER)

    • Address Number (MYAN8) -- This is the address of the supplier in the Item/Branch

    • Short Item Number (MYITM), Second Item Number (MYLITM), Third Item Number (MYAITM), or Customer Item Number (MYCITM)

    • Forecast Quantity (MYFQT)

    • Date Requested (MYDROJ)

    • Forecast Type (MYTYPF)

    • Unit of Measure (MYUOM)

E.3.5 Application Files Updated

When you run Inbound Edit/Update for planning schedule forecasts, the program edits the data it receives from your trading partner and uses the data from the EDI interface files to update the following application files:

  • Forecast (F3460)

  • Item Branch (F4102)

E.3.6 EDI Inbound Interface Files

When you run Inbound Edit/Update for planning schedule forecasts, the program uses the following EDI inbound interface files:

  • EDI Planning Schedule Header (F47061)

  • EDI Planning Schedule Detail (F47062)

E.3.7 What You Should Know About

Topic Description
Reviewing inbound planning schedules Use Status Inquiry to locate information about inbound planning schedules.
Revising inbound planning schedule forecast Use Revisions to revise inbound planning schedule information if the inbound planning schedule forecast differs from that used by other transactions.
Right-justify the Branch Plant field (MCU) in the F47122 Ensure the branch plant field (MCU) in the F47122 is right-justified or you receive error 0294 - Item Branch Plant record does not exist.

E.4 Send Planning Schedule Forecasts (830/DELFOR)

Navigation

From Scheduling & Planning Transactions (G4725), choose Planning Schedule Forecast

From Planning Schedule Forecast (G47251), choose Outbound Extraction P47062

Run the Outbound Extraction program for planning schedule forecasts to generate planning schedule transactions to send to your supplier and to communicate the expected demand for components over a specified period of time.

Use the data selection on any field in the Forecast file to control which records to choose for processing. For example, you can choose a data range or forecast type.

Planning schedule forecast transactions are retrieved from the JD Edwards World Forecast file.

E.4.1 Application Files Providing Data

When you run Outbound Extraction for planning schedule forecasts, the program extracts data from the following application files:

  • Forecast (F3460)

  • Supplier Schedule Quantity (F3430)

E.4.2 EDI Outbound Files Created

When you run Outbound Extraction for planning schedule forecasts, the program creates records in the following EDI outbound interface files:

  • EDI Planning Schedule Header (F47066)

  • EDI Planning Schedule Detail (F47067)

E.4.2.1 The P47062 creates report R47062

Figure E-1 Display Spooled File (Report R47062) screen

Description of Figure E-1 follows
Description of "Figure E-1 Display Spooled File (Report R47062) screen"

Note:

The existing Outbound 830 transaction was previously built by using the Forecast file (F3460). A processing option was added to use the Supplier Release Schedule file (F3430) instead. The same output files are used.