Working With Blend Management Interoperability

This chapter provides an overview of interoperability for JD Edwards EnterpriseOne Blend Management and discusses how to:

• Create and modify inbound operations.

• Revise inbound operations.

• Purge transactions.

Understanding Blend Management Interoperability

Some activities for JD Edwards EnterpriseOne Blend Management may be performed by external systems. Interoperability provides a method for bringing these externally generated data into the system.

Using electronic data interchange (EDI), the external system creates a flat file in the format specified for operations tables in JD Edwards EnterpriseOne Blend Management. The data in this flat file is validated and converted into JD Edwards EnterpriseOne table records. From the data in these tables, you create operations in the JD Edwards EnterpriseOne Blend Management system using an inbound batch engine. You can also manually edit the data in the unedited transaction tables (Z files).

See Also

Processing EDI Documents

Creating and Modifying Inbound Operations

This section provides an overview of inbound operations and discusses how to:

• Run the Inbound Flat File Conversion program.

• Create and modify inbound transactions.

Understanding Inbound Operations

When you import operation data from external systems, you create “after-the- fact” operations with a status of Active or Actual. The inbound data specifies the From and To vessels and the actual quantity or dip measurements. You can only import single-vessel in-place operations, or operations with one-to-one movements. The system does not expect all quantities from the external system, but the inbound data should provide the minimum quantities for calculating operations. For receipt operations the system always expects the actual move quantity. For all other operations any one of the quantities (Actual Move, From After, or To After) is essential so that the system can calculate the appropriate actual quantity as required by the instruction method of the configured operation. The system sets the quantity flag to 1 to indicate that the user entered the quantity. This enables the user to enter a quantity of 0.

Interoperability enables you to import the following basic operation values:

• EUR.

  Lot quantities and the Fixed/Balance flag set appropriately. The system updates the From After and To After EUR values for the operation.

• Composition records in the bill of lading transaction.

• Default owner.

• Blend ID and alternative Blend ID.

  The system updates the override flag for the Blend ID.

• Quality assurance operations.

  The system validates the tests and updates them with test values. It updates the test results for the After lot.

  You also can update tests and import new tests for existing operations.

• Sample information.

  You can import the sample information that is associated with a test. The system stores third-party sample numbers as alternate sample numbers. The system does not consolidate imported samples.

• Equipment.

  The inbound engine can assign multiple pieces of equipment.

• Consumables.

  The system provides default consumables based on the equipment and also assigns consumables from the data tables.

• Resources.

  The inbound engine can process multiple resources.

• Cost.

  The system assigns costs only to receipt operations

• Style.

  The system assigns style only to receipt operations

• Instructed attributes.

  You can add instructed attributes for From or To After lots with override flags.

• VBT.

  You can add new or update existing virtual barrel tank (VBT) operations.

The system does not process other operational data into the JD Edwards EnterpriseOne inbound transaction tables. The following table describes operation data that is calculated by the inbound operation engine or uses default values from the configured operation:

Note. You cannot import media attachments using electronic data interchange.

Z Files

When you prepare to import external operations data into the JD Edwards EnterpriseOne Blend Management system, you first convert the flat file into a JD Edwards EnterpriseOne table for unedited inbound data (Z file) using the Inbound Flat File Conversion program (R47002C). Running this process populates the following tables:

• Operations Transaction File (F31B65Z1)

• Operations Composition Transaction File (F31B31Z1)

• Operations Style Transaction File (F31B34Z1)

• Operations Cost Transaction File (F31B3CZ1)

• Operations Equipment Transaction File (F31B52Z1)

• Operations Consumables Transaction file (F31B53Z1)

• Work Order Transaction File (F31B93Z1)

• Operations Resource Transaction File (F31B97Z1)

• Operations Quality Test Transaction File (F31BQAZ1)

• Sample Transactions (F31BSPZ1)

• Operation EUR Transaction File (F31B17Z1)

• VBT Barrel Transaction File (F31B18Z1)

• Instructed Attributes Transaction File (F31B19Z1)

Note. When you import multiple dependent operations in a work order, ensure that the operation reference numbers are in the appropriate sequence. The system uses the operation reference numbers to sequence operations in the Operation Transaction table during processing.

To process Z files into JD Edwards EnterpriseOne Blend Management, the system uses specific transaction process types for every type of record that you import. You configure a version of the Inbound Flat File Conversion program (R47002C) for each type of record by entering the corresponding transaction process type in the processing options. The following table lists the transaction process types and the corresponding information sets:

Note. Interoperability does not support spirit operations. The Z files do not include temperature fields.

Prerequisites

To run inbound flat files conversions, use the Flat File Cross-Reference program (P47002) to associate the transaction process types with the appropriate flat files.

Running the Inbound Flat File Conversion Program

Select any of the versions of the Flat File Conversion program from the Blend Interoperability (G31B07) menu.

For each data set, such as composition, style, cost, equipment, consumables, resources, quality information, EUR, instructed attributes, VBT information, operations, and work orders, JD Edwards EnterpriseOne Blend Management provides a different version of the Inbound Flat File Conversion program. This table lists the available menu options:

For items that are used in the blend process, for example additive and consumables, you use the Item Master Unedited Transactions Processor program (R4101Z1I) to import item records into the JD Edwards EnterpriseOne system. If you set up operational cumulative thresholds for additives, the program includes this data in the import as well.

Creating and Modifying Inbound Transactions

Select Blend Interoperability (G31B07), Process Inbound Work Order for Blend.

When you run the Inbound Work Order for Blend program (R31B65AZ1I), the system validates the records and creates operations. Based on the operation information in the Z file, the system creates a work order and attaches the operation details from the flat file to the work order.

If the process of creating operations from the transaction records is successful, the system flags the records transaction table (Z file) as processed. If errors occur in this process, the program flags the appropriate record in the Z files and sends an error message to the message center. You can use the appropriate transaction revision program to change the information.

Inbound VBT Operations

When you import operations from external systems, you add or update VBTs based on the transaction action code on the record. Action code 2 means that you are adding or creating a new VBT operation . Action code 4 means that you are updating an existing record.

To add and update VBTs on inbound operations, the system also uses data from the following fields in the F31B65Z1 table:

• From VBT Type and From Capacity Type.

• To VBT Type and To Capacity Type.

The system stores the following VBT information in the VBT Barrel Transaction File (F31B18Z1):

• Barrel ID

• From/To flag

• Volume status

• Quantity received

• Rack number and location

When you add or update VBT information, the system creates operations only if the VBT in the previous operation already had barrels. This validation does not preclude the creation of new VBTs. The system also verifies whether all of the barrels from the Before lot that are included in the After lot either full or empty.

The system calculates dips for all barrels that are not empty.

If you have set the barrel tracking method in the winery constants to C (collection), the system considers the quantity received as the number of barrels. Otherwise, the default value for the number of barrels is 1.

Inbound Samples

If you perform a QA operation with sampling on the blend lot in a VBT, the VBT Barrel Transaction File stores information about which barrels are sampled and in what sequence. For all other operations, these fields are disabled.

Run the Process Inbound Samples for Blend program (R31BSPZ1) to update barrels with the same sample number in the VBT Detail table (F31B101) with sample information, such as the value from Sampled check box, the sample sequence and the barrel location.

Revising Inbound Transactions

This section provides an overview of revising inbound transactions and discusses how to set processing options for Revise Work Order Transaction (P31B97Z1).

Understanding Revising Inbound Transactions

In addition to using the Inbound Flat File Conversion program, you can enter inbound transactions directly into the unedited transaction files using one of the transaction revision programs. You can also use the following programs to revise transactions that contain errors:

• Revise Operations Transaction (P31B65Z1)

• Revise Operations Composition Transaction (P31B31Z1)

• Revise Operations Style Transaction (P31B34Z1)

• Revise Operations Cost Transaction (P31B3CZ1)

• Revise Operations Equipment Transaction (P31B52Z1)

• Revise Operations Consumable Transaction (P31B53Z1)

• Revise Work Order Transaction (P31B93Z1)

• Revise Operations Resource Transaction (P31B97Z1)

• Revise Operations Quality Test Transaction (P31BQAZ1)

• Sample Transaction Revision (P31BSPLZ1)

• Revise Operations EUR Transaction (P31B17Z1)

• VBT Barrel Transaction (P31B18Z1)

• Instructed Attributes (P31B9Z1)

• F4101Z1 Item Master Revisions (P4101Z1)

  Use this program to revise items that you use for blend management and to cumulative and operational threshold information for additive items.

Forms Used to Revise Inbound Operations

Setting Processing Options for Revise Work Order Transaction (P31B93Z1)

These processing options control default settings for the Revise Work Order Transaction program

Display

These processing options control how transactions are displayed on the Work with Work Order Transaction form.

Purging Transactions

This section provides and overview of purging transactions and discusses how to purge transactions.

Understanding Purging Transactions

When records in the unedited transaction tables are no longer needed (for example, because the blend operation has been created successfully), you can purge them from the unedited transaction tables. JD Edwards EnterpriseOne Blend Management provides the following purge programs:

Purging Transactions

Select Blend Interoperability (G31B07), Purge Work Order Records.

You can use the Purge Work Order Records program (R31B93Z1) to purge work orders along with corresponding operations and other attributes, such as EUR, composition, style, equipment, instructed attributes, VBT information, consumables, resources, costs, quality tests, and samples. To delete a particular work order and its associated records, you must select the work order reference number in the data selection. If you do not select a work order reference number, all records are purged.