Data Collection Environments

About data collection server definitions

The TranConnect program provides tools for defining your data collection servers and devices. This procedure is performed one time and only changes when your system requirements change.

Detailed definitions give you the flexibility to control each transaction at a particular level. These definitions are referenced throughout the entire system.

By using the System Parameters (SYS), Data Collection Server (DCS), and the Reader Logical Unit (RLU) forms, you can define your entire environment. These forms define each data collection server and device by name, location, business unit, and time zone.

About defining data collection servers

Defining your data collection server is a required part of the setup process. You must define this server to ensure that the process is performed successfully.

The Data Collection Server (DCS) parameters identify the computer that receives transaction records from the devices (RLU) and transmits them to the host environment. The parameters for the data collection server include PC name, location, business area code, and polling data queue. Each data collection server must be uniquely identified in your environment to ensure proper communications with the client and server environment.

To complete the data collection server fields, you must have the following information.

The device name of the data collection server if one is assigned in Agent Settings for the TranConnect Host Agent.
Whether the data collection server will be assigned its own business area
Whether the polling data queue receives the transaction records from the data collection server
Whether the data collection server is in the same time zone as its host computer
Whether the data collections server uses its own DREAM Writer version

Understanding operating parameters

You must define the following operating parameters in TranConnect. These parameters affect how transaction records are recorded in the data collection system, what the system uses as standard message queues, library names and default values, and communications parameters. The descriptions are listed in the order in which you must complete the setup.

Business Area

Defines transaction groups and associated information according to business needs and acts as a transaction editor. This procedure lets you group your transactions for definition purposes, providing tight controls at the transaction/business-area level. Transaction have a unique identifier (ID) comprised of the transaction ID and the business area.

System parameters

Defines standard message queues, library names, and default values. This procedure involves setting up the system-level default parameters. These defaults are used unless you override them using transaction-level values (using MTD), device-level values (using RLU), or server-level values (using DCS). Before changing system values, ask your Advanced Inventory consultant which options are applicable to your system configuration.

About planning your business area structure

Planning is an important part of defining your environment. Because the business area code plays an important role in the processing, you must decide how you want to group transactions.

Your business operations determine how you use business area codes. You can group transactions based on location or function within a location. For example, you can group inventory transactions based on a BAC and group warehouse transactions on a different BAC, all within the same branch/plant location.

You can assign unique business area codes to identify transactions coming from a particular data collection server or device. The BAC assigned at the DCS level precedes the BAC assigned at the SYS level. The BAC assigned at the RLU level precedes the BAC Assigned at the DCS level. Transactions must use a BAC assigned at either the SYS, DCS, or RLU level.

Before defining your data collection environment, consider how you want transactions processed in your system. Use the following guidelines when planning your business area structure:

Plan your business structure on paper.
Decide the codes you want to assign to your business areas.
Decide how transaction are processed in your environment.
Determine which BAC level you want to control the processing flow: SYS, DCS, or RLU.

After you decide how to group your transactions, define the business area codes using the BAC function. The business area codes that you want to use in the data collection environment must be defined at this level before you can use them elsewhere. As you define business area codes, they are added to the BAC file. Other programs and forms throughout the system refer to this file and, in some cases, control transaction processing according to options associated with the BAC.

Note:If you want to use the default business area code, DCE, you do not need to define business areas.

About reader logical units

Reader Logical Units (RLUs) are devices or secondary files generated by a compatible database program. Transaction records entering the pipeline from a secondary file are identical to those from a device. The system uses RLU definitions primarily for tracking transaction records. The polling program looks up the RLU record when it processes transaction records.

Every device must be uniquely identified in the system. You can manually assign a device ID to each device or you can have the system assign the device ID. For more information, refer to Autogenerate RLU ID Records. If you define the device ID, that ID must be unique.

For information about specific devices, refer to the documentation from the device manufacturer.

Define a data collection server

Defining your data collection server is a required part of the setup process. You must define this server to ensure that the process is performed successfully.

To define a data collection server, complete the following steps.

On the menu selection line, enter DCS and press Enter or select OK.

Expected Result

Result:The Data Collection Server form displays.
For Action, enter one of the following action codes you want to use.
- To add a new record, enter A.
- To change an existing record, enter C.
- To delete an existing record, enter D.
- To find a record, enter F.
- To inquire on a specific record, enter I.
Expected Result

The cursor goes to the next field. Press TAB to move from field to field or click any field you want to change.

You can also press F1 to see a list of existing records.
For Opt, enter 1 and press Enter or select OK.
For Action, if necessary, change the code.
If you are adding a data collection server, in the PC Name field, enter the server name.
Step Information
Note:

If you are changing or reviewing an existing record, you can skip this step.

The PC name in the host environment must be the same name as the one used in the client and server environment. The PC name for the data collection server can be assigned in the Configuration Utility program on the data collection server.

The PC name must be unique within the data collection environment. It can contain one to ten characters from A to Z, 0 to 9, plus an underscore. The field cannot contain any punctuation, special characters, or spaces and must start with an alpha character.

If you are using TCP/IP communications, you must define a data collection server for the SocketPoll Server.
For PC location, enter the location of the data collection server.

Step Information

Note: For SocketPoll Server, use SocketPolling.
For APPC, do one of the following.
- If your network uses APPC, enter the device name for the data collection server. Typically this is the same name you entered in the previous step.
- If your network does not use APPC, enter any letter.
Step Information

Note:For the SocketPoll Server, use the same name as the PC name.
For Business area, enter BAC.

Step Information

Note:The Business area field is the BAC the data collection server assigns to transactions originating from RLUs with default areas of *PC. Any other business area codes assigned to an RLU override this value. To view a selection list of valid BACs, press F1.
For Data-queue ID, enter the name of the polling data queue.

Step Information

Note:The Data-queue ID is the host polling data queue that receives transactions sent by the data collection server. When the transaction pipeline is active, these transactions process immediately. If the pipeline is not active, the transactions accumulate until the pipeline is started using the Start/Stop Transaction (SST) function.
For Send date/time to PC, enter one of the following values.
- Enter Y (yes) to send the date and time data to the collection server.
- Enter N (no) to not send date and time data to the collection server.
Step Information

Note:Y (yes) is the default setting.

Expected Result

Result: When communication initiates, the data collection server gets the date and time from the host. When the polling process is active, a dummy record transmits from the data collection server to the host every 15 seconds. If the host detects a variance of more than five seconds, and the field is a Y (yes), the host transmits the current system date and time back to the data collection server.
For Time zones diff from As/400, enter a number between -12 and +12.

Step Information

Note:You must enter any difference between the local time zone and the host time zone. To calculate the difference between the value from the AS/400 value, subtract the local time from the time at the host. If the data collection server is east of the host, the difference is positive. If the data collection server is west of the host, the difference is negative. The default value is zero, meaning both servers are in the same zone.

Note:If the Daylight Savings Time status is different between the host and data collection server location, you must change the Time zone diff from AS/400 twice each year.
For Hold PC, enter one of the following values.
- Enter Y (yes) to hold all transactions.
- Enter N (no) to not hold transactions unless the transaction is in error. This is the default value.
Expected Result

Result: Held transactions remain in the DCCLF file with a status of *HLD until they are released using the Working with Held Transactions (WHT) option. You must review the transaction processing data before the program database updates.
Verify the Cost Center field is not blank.
(Optional) For Version, enter the version number of the default DREAM Writer processing option.
Press Enter or select OK.

Example

The program updates the system configuration record.

Autogenerate RLU ID Records

You can configure the device with Device Loader to autogenerate RLU ID records. You can use this program to assign the device ID to each device. Each device must have a unique ID in the system. During the configuration process, the Device Loader assigns the device ID and other communication parameters. When the pipeline processes a transaction record from a device that has been named through the Device Loader program, the processor program creates a new RLU record using the same BAC as the data collection server transmitting the transaction record.

To define a reader logical unit, complete the following steps in Oracle JD Edwards World.

Enter RLU and press Enter or select OK.

Expected Result

Result:

The Reader Logical Units (RLU) form displays.

The key field is Device ID. You use the Reader Logical Units form to add new RLU records and change existing RLU records.
Starting from a blank form or an existing record, to add an RLU record, perform the following substeps.
1. Inquire or Find the existing record that resembles what you want.
2. Change the Action to A.
3. Change fields as needed.
For Action, enter the appropriate code for one of the following values.
- Select Add a new record (code A) to add a new RLU device.
- Select Change an existing record (code C) to inquire, find, or change fields.
- Select Delete an existing record (code D) to delete a record.
- Select Find a record (code F) to display a record equal to or greater than the input.
- Select Inquire about a specific record (code I) to display a record equal to the input.
Expected Result

Result: The cursor moves to the key field. If you press F1, a list of existing records displays.
Press TAB to position the cursor beside the desired record in the list.
For Opt, enter 1 and press Enter or select OK.

Expected Result

Result: The selected record displays.
(Optional) For Action, change the code.
If you are adding a new RLU, in the Device ID field, enter the name of the device.
Step Information
Note:

The device ID is the RLU network device identification. The device ID can contain from one to ten characters from A to Z, 0 to 9 plus an underscore. The ID cannot contain any punctuation, special characters, or spaces, and must start with an alpha character.

When assigning device IDs, use IDs that help identify the devices in your data collection environment, such as an abbreviation of the location plus a sequence number. For example, for devices used in your receiving area, you might assign them as REC1, REC2, and so forth.

If you are changing or reviewing an existing record, skip this field.
Optional. For Device type, enter either Reader or RF.
Optional. For Business area, enter the BAC you want for this device.
Step Information
Note:

This field is the business area for this device.

Valid entries are the business area codes entered on the BAC form. This code must exist before you use it.

You can also use *SYS to use the system default BAC (set up on the SYS - System Parameters form) or *PC to default to the Business Area Code (set up on the DCS - Data Collection Server form) for the data collection server.

To display a selection list of valid BACs, press F1 on the field.

If no entry is made, the default business area code is the BAC entered on the DCS form, if any, or the default BAC on the SYS form.
For PC Name, enter the name of the data collection server where the RLU is to be used.

Step Information

Note:You can also enter *ANY in this field.
Optional. For Processing version, enter the DREAM Writer processing options version for the transactions originating from this RLU. This value is used only if the corresponding field in the MTD form is blank.
For Hold Reader, enter one of the following values.
- To hold all transactions, enter Y (yes).
- To not hold all transactions, enter N (no).
Expected Result

Result: When you set the hold status to Y, all transactions require manual release before processing. For information about how this field affects held transactions, see Processing Held Transactions in TranConnect Administrators Guide.
Press Enter, to add the RLU record to the system.
Optional. Place the cursor in the Reader Device ID field, and press F1 to verify your information and locate the new record.
Press Enter again to record your changes.

There was a problem loading this topic

Mobile Enterprise Platform