C Product Information Transactions

This appendix contains these topics:

C.1 Objectives

  • To set up EDI product information transactions for your Electronic Commerce system

C.2 About Product Information Transaction Setup

When setting up the Electronic Commerce system, you need to specify how the system should handle your product information transactions.

Complete the following tasks:

  • Receive the price sales catalog (832/PRICAT) - P47081

  • Send the price sales catalog (832/PRICAT) - P47082

Note:

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

C.3 Receive the Price Sales Catalog (832/PRICAT)

Navigation

From Product Information Transactions (G4723), choose Price Sales Catalog

From Price Sales Catalog (G47231), choose Inbound Edit/Update P47081

Run the Inbound Edit/Update program for the price sales catalog to process price and cost changes for items.

C.3.1 What Happens when You Receive the Price Sales Catalog?

After you make revisions to the price sales catalog, run the Inbound Edit/Update program to update the Supplier/Catalog Price file (F41061) with the changes in the price sales catalog.

When you run the Inbound Edit/Update program for the price sales catalog, the system:

  • Reads the price sales catalog information

  • Edits price sales catalog information

  • Updates the Supplier/Catalog Price file (F41061) with pricing information

  • Prints the Price Sales Catalog Audit report (R47081) to recap and to summarize updated records in the Supplier Item Price file

  • Generates the Price Sales Catalog Exception report (R470811) if errors occur

  • Prints the Price Sales Catalog Items Not Found (R470812) report to list items it received in the price sales catalog but did not find in the Item Master file (F4101)

C.3.2 Mapping Guidelines

The following fields in the EDI interface files must contain data before you can use Inbound Edit/Update for price sales catalog effectively:

  • Header Record (F47081):

    • EDI Document Number (FVEDOC)

    • EDI Document Type (FVEDCT)

    • EDI Document Key Company (FVEKCO)

    • EDI Transaction Set (FVEDST)

    • Send/Receive Flag = R (FVEDER)

    • Transaction Set Purpose (FVTPUR)

    • Catalog Name (FVCATN)

  • Detail - Price Information (F47082):

    • EDI Document Number (FYEDOC)

    • EDI Document Type (FYEDCT)

    • EDI Document Key Company (FYEKCO)

    • EDI Transaction Set (FYEDST)

    • Unit of Measure (FYUOM)

    • Send/Receive Flag = R (FYEDER)

    • Short Item Number (FYCITM), Second Item Number (FYLITM), Third Item Number (FYAITM), or Customer Item Number (FYITM)

    • New Unit Price (FYUPRC)

    • Effective From and To Date (FYEFTJ)

    • Address Number (FYAN8)

C.3.3 Application Files Updated

When you run Inbound Edit/Update for price sales catalog, 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:

  • Supplier/Catalog Price File (F41061)

  • Supplier Item Relationship (F43090)

C.3.4 EDI Inbound Interface Files

When you run Inbound Edit/Update for price sales catalog, the system uses the data in the following EDI inbound interface files:

  • Price Sales Catalog Header (F47081)

  • Price Sales Catalog Retail (F47082)

C.3.5 What You Should Know About

Topic Description
Converting vendor item numbers If necessary, you can use the Item Cross-Reference function of JD Edwards World Inventory Management system to convert vendor item numbers to your item numbers. To do this, map the vendor item numbers to the Customer Item Number field of the EDI Price Sales Catalog -Inbound file. Then, specify the item cross-reference type in the processing options.
Reprocessing branch/plant cost and price records After the system updates the records, it marks records in the corresponding price sales catalog files as processed. Any record that has been processed cannot be reprocessed.
Revising catalogs Use Revisions to revise the price sales catalog.
Locating a transaction status Use Status Inquiry to locate the status of transactions in both the inbound and outbound files for price sales catalog records.
Removing processed records Use the Purge/Archive program to remove processed records from the Price Sales Catalog Header and the Price Sales Catalog Detail Price inbound files. Processed records have Y in the EDI - Successfully Processed field of the files (EDSP). You can specify in the processing options of the Purge/Archive program whether to save purged records.

See Also:

C.4 Send the Price Sales Catalog (832/PRICAT)

From Product Information Transactions (G4723), choose Price Sales Catalog From Price Sales Catalog (G47231/14), choose Outbound Extraction P47082

Run the Outbound Extraction program for the price sales catalog to generate price sales catalog transactions from the Sales Base Price file (F4106) to send to vendors or customers as well as extract item information.

You indicate to the system which records it should create price sales catalog transactions for by entering the specific data selection information based upon any field in the Branch/Plant Item Location fields on the DREAM Writer Data Selection screen. This gives the supplier the ability to pick and choose from the Item/Branch Plant information files which items are part of their catalog. The catalog can be run multiple times for different customers or a generic catalog can be generated.

C.4.1 What Happens when You Send the Price Sales Catalog?

When you run Outbound Extraction, the program extracts price information and item notes, print messages, and flash messages based on processing option set up from the JD Edwards World Branch/Plant Item Location file. The system uses this information to write records to the files for outbound EDI price sales catalog information.

The program also generates the following reports:

  • Price Sales Catalog Audit which summarizes records that were created for transmission - R47082

  • Price Sales Catalog Exception which reports errors if they occur - R470821

  • The program extracts and writes to the files Currency Information if a customer is specified. If a customer is not specified, the currency for the company attached to the Branch/Plant is extracted

  • Text is extracted based on processing option flags for item notes, prints messages, and item flash messages

  • Item Cross-references are retrieved for the customer's item number for an extracted item. If a customer's number is not found, the JD Edwards World item number is extracted

C.4.2 Application Files Providing Data

When you run Outbound Extraction for price sales catalog, the program extracts data from the following files:

  • Item Branch (F4102)

  • Item Master (F4101)

  • Base Price (F4106)

C.4.3 EDI Outbound Files Created

When you run Outbound Extraction for price sales catalog, the program creates records in the following EDI outbound files:

  • Price Sales Catalog Header (F47086)

  • Price Sales Catalog Detail (F47087)

  • Item Text (F4716)

C.4.4 What You Should Know About

Topic Description
Customer Number
  • If the customer number field is blank, then the trading partner cannot be.

  • If a customer number is entered and the processing option to extract the customer's item number is set = 1 the cross reference will be used to determine the correct item number to be extracted.

  • If a customer number is not entered, no customer specific process is extracted. Prices will only be by item or item group.
Pricing Hierarchy The Pricing Hierarchy in pricing preferences is used to determine the price extracted if a customer number is entered by using the X4106 price server and the customer preference program P40400.
Processing Options Processing option 16: Price/Sales Catalog Code - Field SCCD

  • Code indicating purpose of EDI Price/Sales Catalog

  • CP Customized Catalog

  • PC Price Catalog

  • PS Price Sheet

  • RC Resale Catalog

  • SC Sales Catalog

A version of sales catalog may also be run for extracting cost based on processing option 2 = blank.