1. Mobile Enterprise Applications Implementation Guide
  2. Differences and Limitations: Mobile Order Entry

Differences and Limitations: Mobile Order Entry

Mobile applications are intended to be a simplified version of the applications that are available in the base software. In most cases, these applications provide a subset of the functionality available in the base software.

For the Order Entry mobile tablet application, there is no specific JD Edwards EnterpriseOne base program that performs the same function. This mobile application uses features and functionality from several different base applications to enable sales personnel to create orders for customers while they are away from the office.

Barcode Scanning

This application is designed to accept data entry from a barcode scanner. To use this functionality, you must create barcodes that represent a single field in the JD Edwards EnterpriseOne system. This application does not accept barcodes that include data for multiple fields.

Additionally, you must specify, in the processing options of the M42010 program, which item number field is used for scanning. You can specify the 2nd Item Number, 3rd Item Number, or Short Item Number.

For example, if you want users to be able to scan the item number with their device, and you have selected 2nd Item Number in the processing options, you must create a barcode that represents only the value in the 2nd Item Number field for that item. The barcode cannot include both the item number and quantity, for example.

You can generate barcodes using services such as those offered by Barcodes Inc.

Note: Oracle is not affiliated with Barcodes Inc., and does not require or recommend that you use this service to create your barcodes.

Item Image Display

If you want images from the Item Master to display in the Order Entry mobile application, the item image must be attached to the item master as the first attachment. If the first attachment in the item master is not an image file, the Order Entry mobile application displays a default image next to the item.

Credit Card Processing

This application is designed to integrate with a third-party solution that can process credit card transactions at the point of sale. The third party referred to here is a third-party hardware device and a software plug-in written for the specific hardware device.

The third-party solution that you select must be able to perform all of the processing, including scanning the credit card, transmitting the credit card information to the credit card bank, and receiving purchase authorization from the bank. The third party must provide security to protect the credit card information. The Oracle JD Edwards EnterpriseOne system does not interact with or store the customer's credit card information.

The tablet application interfaces with the third party only to:

  • Provide information (sales order header and order totals) necessary to process the transaction.

  • Receive the authorization information (transaction date, transaction amount, and authorization code) returned from the third party.

    The JD Edwards EnterpriseOne system stores the authorization information in the Prepayments Transaction table (F004201) to support processing the sales order through the sales update and accounts receivable processes.

For additional information, refer to the document "JD Edwards EnterpriseOne Mobile Sales Third Party Plug-In" on the Oracle Learning Library site.

https://apexapps.oracle.com/pls/apex/f?p=44785:24:0::::P24_CONTENT_ID,P24_PREV_PAGE:11488,1