Skip Headers
JD Edwards EnterpriseOne Applications Functionality for Mobile Devices Implementation Guide
Release 9.1

E21453-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

Beta Draft: 2013-08-13

A Business Services for Mobile Applications

This appendix describes each of the business services used by the JD Edwards EnterpriseOne mobile applications, and their related operations. The appendix is organized by mobile application, and includes these sections:

Note:

You can also access additional information about each business service using the Oracle Technical Catalog. For information about the catalog, see Using the Oracle Technical Catalog.

A.1 Mobile Expense Management Business Services

The mobile expense management processes use these business services and operations:

  • ExpenseReportManager published business service (JP09E000).

  • ExpenseReportQueryProcessor (J09E0001), which contains these two methods:

    • getAllExpenseReports

    • getExpenseReportsToApprove

    • getExpenseReports

    • getExpenseReportHeaders

    • getExpenseReportsForEdit (Release 9.1 Update)

  • ExpenseManagementEmployeeProfileQueryProcessor (J09E0002), which contains these methods:

    • getExpenseManagementEmployeeProfile

    • getExpenseManagementEmployeeProfileV2

  • ExpenseReportWorkflowProcessor (J09E0003), which contains these methods:

    • approveExpenseReport

    • rejectExpenseReport

    • submitExpenseReport

  • CreditCardTransactionQueryProcessor (J09E0004), which contains the getCreditCardTransactions method.

  • ExpenseReportProcessor (J09E0005), which contains these methods:

    • processExpenseReports

    • processExpenseReportHeader

    • processExpenseReportDetails

  • ExpenseReportRecordReservation (J09E0006), which contains these methods:

    • reserveExpenseReport

    • releaseExpenseReport

  • getExpenseManagementPolicy (J09E0007).

  • ExpenseReportAttachmentManager (JP09E001) (Release 9.1 Update)

  • ExpenseReportAttachmentsQueryProcessor (J09E0008), which contains the getExpenseReportAttachment method. (Release 9.1 Update)

  • ExpenseReportAttachmentsProcessor (J09E0009), which contains the processExpenseReportAttachment method. (Release 9.1 Update)

  • getExpenseManagementValuesList (J0000030), which is a method contained by the getUserDefined code operation, which is managed by the FoundationEnvironment published business service (J000000).

  • lookupBusinessUnits (J0000040), which is managed by the FoundationEnvironment published business service (J000000).

  • lookupCurrencyCodes (J0000060), which is managed by the FoundationEnvironment published business service (J000000).

  • lookupAddressBook (J0100009), which is managed by the ManageAddressBook published business service.

  • lookupWorkOrders (J4800001, which is managed by the WorkOrderManager published business service (JP480000).

  • lookupJobCost (J5100001), which is managed by the JobCostManager published business service (JP510000).

See Also:

For detailed information about the lookupBusinessUnits, lookupCurencyCodes, getExpenseManagementValuesList, and lookupAddressBook web service operations, see these topics in the JD Edwards EnterpriseOne Applications Business Services Reference Guide:

The ExpenseReportManager published web service (JP09E000) manages the processing of these mobile expense-related web service operations:

Operation/Method Description
getAllExpenseReports (J09E0001) Use this method to retrieve expense reports of a specific approver, and for a specific employee. Additional filtering on specific header values can be applied. This query includes reports processed through workflow for the signed-on approver, not just reports for the approver's subordinate employees. For example, reports that the signed-on user approved as a delegate would be included.
getExpenseReportsToApprove (J09E0001) This method is contained within the ExpenseReportQueryProcessor operation. Use this method to retrieve expense reports that are currently awaiting approval by the signed-on user.
getExpenseReports (J09E0001) This method is contained within the ExpenseReportQueryProcessor operation. This method retrieves expense report headers and detail records based on the selection criteria.
getExpenseReportHeaders (J09E0001) This method is contained within the ExpenseReportQueryProcessor operation. This method retrieves expense report header information based on the selection criteria.
getExpenseReportsForEdit (J09E0001) (Release 9.1 Update) This method is contained within the ExpenseReportQueryProcessor operation. This method allows the user to query expense reports based on specific criteria.
getExpenseManagementEmployeeProfile (J09E0002) This method is contained within the ExpenseManagementEmployeeProfileQuery Processor operation, and is used to retrieve the expense report profile and EnterpriseOne profile information that is associated with the user name or address number that is entered at sign on.
getExpenseManagementEmployeeProfileV2 (J09E0002) (Release 9.1 Update) This method is the same as the getExpenseManagementEmployeeProfile method, with one exception. This method has been modified to include the additional field, whereAttachmentsAllowed, to accommodate attachments in the mobile expense application.

Within the mobile application this method is used to determine if photos are displayed at the report-level, expense-level, or both. It is also used to determine whether photos can be added to a report, an expense, or both.

approveExpenseReport (J09E0003) This method is contained within the ExpenseReportWorkflowProcessor operation. Use this method to approve a specific expense report.
rejectExpenesReport (J09E0003) This method is contained within the ExpenseReportWorkflowProcessor operation. Use this method to reject a specific expense report.
submitExpenseReport (J09E0003) This method is contained within the ExpenseReportWorkflowProcessor operation. Use this method to submit for approval a specified expense report.
getCreditCardTransactions (J09E0004) Use this operation to retrieve credit card transactions for a specified employee.
processExpenseReports (J09E0005) This method is contained within the ExpenseReportProcessor operation.Use this method to insert, update, or delete expense report headers and expense report details.
processExpenseReportHeader (J09E0005) This method is contained within the ExpenseReportProcessor operation. Use this method to insert, update, or delete expense report headers.
processExpenseReportDetail (J09E0005) This method is contained within the ExpenseReportProcessor operation.Use this method to Use this method to insert, update, or delete expense report details.
reserveExpenseReport (J09E0006) This method is contained within the ExpenseReportProcessor operation.Use this method to reserve an expense report so that it can be edited by another process.
releaseExpenseReport (J09E0006) This method is contained within the ExpenseReportProcessor operation.Use this method to release a reservation from an expense report so that it can be edited by another process.
getExpenseManagementPolicy (J09E0007) Use this operation to retrieve the expense management policy information based on the selection criteria.

(Release 9.1 Update) The ExpenseReportAttachmentManager (JP09E001) manages these web service operations:

  • ExpenseReportAttachmentsQueryProcessor (J09E0008), which contains the published method getExpenseReportAttachments (JP09E001-J09E0008).

    Using this service, the mobile user can retrieve expense report attachments (photos) for both report-level and expense-level attachments. The service supports media attachments. The user can control which types of attachments are returned.

  • ExpenseReportAttachmentsProcessor (J09E0009), which contains the published method processExpenseReportAttachments (JP09E001-J09E000).

    Using this service, mobile users can add or delete attachments to an expense report or an expense detail item.

The WorkOrderManager published web service (JP480000) manages the lookupWorkOrders web service operation (J4800001). This operation retrieves work order records from the JD Edwards EnterpriseOne database when the mobile user is searching for valid work order numbers to use when entering expense information.

The JobCostManager published web service (JP510000) manages the lookupJobCost web service operation (J5100001). This operation retrieves job cost information from the JD Edwards EnterpriseOne database when the mobile user is searching for valid cost codes to use when entering expense information.

A.1.1 ExpenseReportQueryProcessor

The ExpenseReportQueryProcessor (J09E0001) is a web service operation that calls one or more of these methods, based on the action of the user:

  • getAllExpenseReports

  • getExpenseReportsToApprove

  • getExpenseReports

  • getExpenseReportHeaders

  • getExpenseReportsForEdit (Release 9.1 Update)

These methods are database queries that enable consumers to retrieve and review expense report information from the JD Edwards EnterpriseOne database.

The getAllExpenseReports method uses search criteria to retrieve expense reports of the signed-on user, expense reports that need to be approved by the signed-on user, and expense reports that were previously approved by the signed-on user, even if the employees associated with those reports are not subordinate employees of the signed-on user. The reports that are returned are based on the search criteria entered by the user.

The getExpenseReportsToApprove method searches for and retrieves all expense reports that are currently awaiting approval by the signed-on user.

The getExpenseReports method is called from the getAllExpenseReports method to retrieve expense report data from the EnterpriseOne database. This method allows the user to query expense reports based on specific criteria. The response will include both header and detail records for an expense report, with the detail records for splits and summery records represented at a single detail level (flattened). Within the mobile application this method is used by the search and by the chart to view, but not to modify existing reports.

The getExpenseReportHeader method is called from the getAllExpenseReports method, to retrieve expense report header information from the EnterpriseOne database.

(Release 9.1 Update) The getExpenseReportsforEdit method allows the user to query expense reports based on specific criteria. The response will include both header and detail records for an expense report, with the detail records for splits and summery records represented at their correct level (full hierarchy). Within the mobile application this method is used when you select My Reports and view your own reports.

Note that all of the methods contained in this operation return detail records, with the exception of the getExpenseReportHeader method.

A.1.1.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes expense report information. This table includes information about the business service properties that are used by all of the methods contains in the ExpenseReportQueryProcessor (J09E0001) web service operation, with the exception of the getExpenseReportHeader method:

Group Key Description Default Value
J09E0001 J09E0001_MAX_ROWS_F20111 Use this business service property to specify the maximum number of header records the operation can return for a query.

The default value is set to 100, however, this might limit the returned data when searching for expense reports. If you find that limiting the number of results returned to 100 does not enable you to find the expense reports you are searching for, it is acceptable to increase this value to a number that fits your business needs.

100
J09E0001 J09E0001_MAX_ROWS_F20112 Use this business service property to specify the maximum number of detail records the operation can return for a query.

This number pertains to the number of details rows that is returned for each identified header record. If you typically review expense reports with more than 100 lines of detail, you might want to increase this value.

100

This table lists the business service property used by the getExpenseReportHeader method:

Group Key Description Default Value
J09E0001 J09E0001_MAX_ROWS_F20111_HEADER_ONLY Use this business service property to specify the maximum number of header records the operation can return for a query.

The default value is set to 500 to ensure that all valid records are returned by the query.

500

A.1.1.2 Implementation Details

The following table includes information that can help determine whether the ExpenseReportQueryProcessor (J09E0001) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • employeeName

  • employeeID

  • reportNumber

  • reportDate

  • reportType

  • expenseReportTypeDescription

  • reportDescription

  • expenseReportTotal

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.1.2 ExpenseManagementEmployeeProfileQueryProcessor

The ExpenseManagementEmployeeProfileQueryProcessor web service operation (J09E0002) is a database query operation that calls the getExpenseManagementEmployeeProfile method, which enables consumers to retrieve expense management employee profile information from the JD Edwards EnterpriseOne database. This information is used when processing expense report information using the mobile application.

A.1.2.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes expense report information. This table includes information about the business service properties that are used by the ExpenseManagementEmployeeProfileQueryProcessor (J09E0002) web service operation:

Group Key Description Default Value
J09E0002 J09E0002_MAX_ROWS_F09E109 Use this business service property to specify the maximum number of F09E109 records the operation can return for a query. For proper functionality this value should be equal to the number of records in the F09E109 table. You can change the value in this property as needed. 100

A.1.2.2 Implementation Details

The following table includes information that can help determine whether the ExpenseManagementEmployeeProfileQueryProcessor web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, one record is returned, based on the selection criteria.

The record that is returned to the consumer includes all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • approverId

  • approverName

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.1.3 ExpenseManagementEmployeeProfileQueryProcessorV2

This method is the same as the getExpenseManagementEmployeeProfile method, with one exception. This method has been modified to include the additional field, whereAttachmentsAllowed, to accommodate attachments in the mobile expense application.

Within the mobile application this method is used to determine if photos are displayed at the report-level, expense-level, or both. It is also used to determine whether photos can be added to a report, an expense, or both.

A.1.4 ExpenseReportWorkflowProcessor

The ExpenseReportWorkflowProcessor (J09E0003) is an inbound transaction web service operation that calls one of these methods, based on the action of the user:

  • approveExpenseReport

  • rejectExpenseReport

  • submitExpenseReport

These methods enable consumers to submit, approve or reject expense report records in the EnterpriseOne database.

This operation calls the appropriate method, based on the action of the user. When calling the approveExpenseReport or rejectExpenseReport method, the operation calls the Process Expense Reports business function (B09E0074) to approve or reject the expense report.

If calling the submitExpenseReport method, the system calls the F20111_SubmitEpxenseReport business function (B09E0111) to submit the expense report.

If the operation is successful, the system either submits the report for approval, or removes the report from the list of reports for the user to approve (if approving or rejecting). If the operation encounters errors, processing stops and the errors are returned to the consumer.

A.1.4.1 Setup Considerations

Before you can use this operation, you can set business properties to specify how the system processes expense report information. This table includes information about the property used by the submitExpenseReport method:

Group Key Description Default Value
J09E0003 J09E0003_EMS_MBF_VERSION Use this business service property to specify the default version to pass to the B09E0111. The consumer of this service may pass a version as well, which overrides this property setting. ZJDE0001

A.1.4.2 Implementation Details

The following table includes information that can help determine whether the ExpenseReportWorkflowProcessor web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, the consumer receives a successful return message, and the report is removed from the list of reports awaiting approval.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for the hasErrors field when processing the approveExpenseReport and rejectExpenseReport methods. If the transaction is successful, the value for this field is false.

When processing the submitExpenseReport method, the system returns a non-zero value for the reportStatus field. If successful, the reportStatus will be the next status in the approval workflow.

If I encounter errors while processing a transaction, do I need to reverse the transaction? This operation uses standard transaction processing. If the system encounters errors during processing, no data in the JD Edwards EnterpriseOne system is updated. No manual updates are required.
Does this operation use record reservation? Yes. All record reservation processing is handled within the business function. The record is only reserved for the minimal amount of time it takes the function to update the approval status in the expense report record.

A.1.5 CreditCardTransactionQueryProcessor

The CreditCardTransactionQueryProcessor (J09E0004) is a web service operation that calls the getCreditCardTransactions method. This is a database query operation that enables the consumer to retrieve and review available credit card transactions from the EnterpriseOne database.

A.1.5.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes credit card transaction information. This table includes information about the business service properties that the CreditCardTransactionQueryProcessor (J09E0004) web service operation uses:

Group Key Description Default Value
J09E0004 J09E0004_MAX_ROWS_F0075 Use this business service property to specify the maximum number of F0075 records the operation can return for a query. These are the credit cards setup for an employee. 100
J09E0004 J09E0004_MAX_ROWS_F09E150 Use this business service property to specify the maximum number of F09E150 records the operation can return for a query. These are the transactions for each of the credit cards. 100

A.1.5.2 Implementation Details

The following table includes information that can help determine whether the CreditCardTransactionQueryProcessor web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero or more records are returned, based on the selection criteria (EmployeeID).

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • CreditCardTransactionNumber

  • EmployeeID

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing.

A.1.6 ExpenseReportProcessor

The ExpenseReportProcessor (J09E0005) is an inbound transaction web service operation that enables consumers to reserve expense reports for processing, process expense report information, and then release the expense report when processing is complete.

This operation contains the following methods:

  • processExpenseReports

  • processExpenseReportHeader

  • processExpenseReportDetails

The process methods contained in this operation enable consumers to insert, update, or delete multiple expense reports with detail records in the F20111 and F20112 tables in the EnterpriseOne database. These operations use the F20111_FetchExpRptHeader MBF (B09E0111) which is used for net change, the F20111_EditExpRptHeader (B09E0111), the F20112_FetchExpDetailLineBF (B09E0112) which is used for net change, and the F20112_EditExpDetaiLine business functions to process the expense report within the EnterpriseOne database.

A.1.6.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes expense report information. This table includes information about the business service properties that the ExpenseReportProcessor (J09E0005) web service operation uses:

Group Key Description Default Value
J09E0003 J09E0005_EMS_MBF_VERSION Use this business service property to specify the default version to pass to the B09E0111 and B09E0112. The consumer of this service may pass a version as well, which overrides this property setting. ZJDE0001

A.1.6.2 Implementation Details

The following table includes information that can help determine whether the ExpenseReportProcessor web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? The different methods contained within this operation have different success criteria.

If the processExpenseReport and processExpenseReportHeader methods complete successfully, the consumer receives a successful return message, and the system returns values for these fields, at a minimum:

  • ReportType

  • ReportNumber

  • EmployeeID

  • OriginalWorkStationID

  • DateCreated

In addition to the fields listed above, the processExpenseReportDetail method also returns values for these fields:

  • GeneralLineNumber

  • DetailLineNumber

  • RecordType

Lastly, if the reserveExpenseReport method completes successfully, the system returns a non-zero value for the ReservationGenericKey field. The releaseExpenseReport method does not return values for any fields. If no message is returned, the operation was succesful.

If I encounter errors while processing a transaction, do I need to reverse the transaction? This operation uses standard transaction processing. If the system encounters errors during processing, no data in the JD Edwards EnterpriseOne system is updated. No manual updates are required.
Does this operation use record reservation? Yes. There is an interface provided for record reservation. You can indicate the record is already reserved by your process, or that you want the service to provide the reservation processing.

A.1.7 ExpenseReportRecordReservation

The ExpenseReportRecordReservation (J09E0006) is an inbound transaction operation that enables consumers to create a record reservation record (F00095) to reserve an expense report, preventing other processes from operating on the report.

The operation uses the ReserveExpenseReport and ReleaseExpenseReport business functions (B09E0095) to process the expense report record reservation. If the operation is successful, the system returns a completion message to the consumer. If the operation encounters errors, processing stops and the errors are returned to the consumer.

A.1.7.1 Implementation Details

The following table includes information that can help determine whether the ExpenseReportRecordReservation (J09E0006) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for the ExpenseManagementPolicyResponseElement field.

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing.

A.1.8 ExpenseManagementPolicyProcessor

The ExpenseManagementPolicyProcessor (J09E0007) is a database query web service operation that contains the getExpenseManagement method. This operation enables consumers to retrieve expense policy information from the EnterpriseOne database, so it can be used to process expense information using the mobile application.

A.1.8.1 Implementation Details

The following table includes information that can help determine whether the ExpenseMangementPolicyProcessor (J09E0007) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for the ExpenseManagementPolicyResponseElement field.

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing.

A.1.9 ExpenseReportAttachmentsQueryProcessor (Release 9.1 Update)

The ExpenseReportAttachmentsQueryProcessor (J09E0008) is a database query operation that is managed by the ExpenseReportAttachmentManager (JP09E001). This operation contains the getExpenseReportAttachments method (JP09E001 - J09E0008), which enable the mobile user to query for and retrieve expense report attachments (photos) for both report-level and expense-level attachments. The service supports media object attachments. Users can specify which types of attachments are returned.

A.1.9.1 Implementation Details

The following table includes information that can help determine whether the ExpenseReportAttachmentsQueryProcessor web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, and the requested data is available in the database, media object attachment records and associated binary data (if requested) are included in the soap response. If the query returned no results, the response is empty.

The records that are returned to the consumer include, at a minimum, non-zero values for these fields:

  • Expense Header Attachment fields:

    • itemName

    • sequenceNumber

    • type

  • Expense Detail Attachment Fields:

    • detailLine

    • itemName

    • sequenceNumber

    • type

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing.

A.1.10 ExpenseReportAttachmentsProcessor (Release 9.1 Update)

The ExpenseReportAttachmentsProcessor (J09E0009) is an inbound processor operation that is managed by the ExpenseReportAttachmentManager (JP09E001). This operation contains the processExpenseReportAttachment method (JP09E001 - J09E0009), which enable the mobile user to add or delete expense report attachments (media objects) at both the report level and expense level.

A.1.10.1 Implementation Details

The following table includes information that can help determine whether the ExpenseReportAttachmentsProcessor web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If no exceptions were returned by the service, the operation completed successfully. For add operations, the service will respond with a sequence number for the new media object record that was added successfully.

The response will always contain the key data that was sent in. Responses will also contain these details.Header

  • Header:

    • action

    • itemName

    • sequenceNumber

    • type

  • Detail:

    • action

    • detailLine

    • itemName

    • sequenceNumber

    • type

    • expenseLineNumber

If I encounter errors while processing a transaction, do I need to reverse the transaction? No. If individual attachments were not added or deleted there is nothing the user needs to do other than attempt the call to add or delete the attachments again. The user can also manually add the attachments using the base EnterpriseOne system.
Does this operation use record reservation? No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing.

A.1.11 lookupWorkOrders

The lookupWorkOrders (J4800001) is a database query web service operation that enables consumers to retrieve and review work order information from the JD Edwards EnterpriseOne database.

A.1.11.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes expense report information. This table includes information about the business service properties that the lookupWorkOrder (J4800001) web service operation uses:

Group Key Description Default Value
J4800001 J4800001_MAX_ROWS Use this business service property to specify the maximum number of F4801 records the operation can return for a query. 100

A.1.11.2 Implementation Details

The following table includes information that can help determine whether the lookupWorkOrder web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero or more records are returned, based on the search criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • OrderNumber

  • OrderStatus

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing.

A.1.12 lookupJobCost

The lookupJobCost (J5100001) is a database query web service operation that enables consumers to retrieve and review job cost information from the JD Edwards EnterpriseOne database.

A.1.12.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes expense report information. This table includes information about the business service properties that the lookupJobCost (J5100001) web service operation uses:

Group Key Description Default Value
J5100001 J5100001_MAX_ROWS Use this business service property to specify the maximum number of F0911 records the operation can return for a query. 100

A.1.12.2 Implementation Details

The following table includes information that can help determine whether the loookupJobCost web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero or more records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • Job

  • CostCode

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. The operation does not reserve records within the JD Edwards EnterpriseOne system during processing.

A.2 Purchase Order Approvals Business Services

The mobile purchase order approval process uses these business services:

  • ProcurementManager (JP430000).

  • PurchaseOrderApprovalQueryProcessor(J4300040).

  • GetPurchaseOrderDetailForApprover(J4300050).

  • PurchaseOrderEmployeeProfileQueryProcessor (J4300060).

  • GetMobilePurchaseOrderCountsProcessor (J4300070).

  • PurchaseOrderApproveRejectProcessor (J4300080).

The ProcurementManager published web service (JP430000) manages the processing of mobile purchase order-related web service operations. This table includes a description of those web service operations:

Operation/Method Description
getPurchaseOrderEmployeeProfile (J4300060) Use this operation to retrieve the procurement profile, as well as additional EnterpriseOne profile information, for the name or address number that is entered during sign on.
getPurchaseOrdersCounts (J4300070) Use this operation to retrieve the purchase order descriptions and counts for each order type that is currently awaiting approval by the signed-on user.
getPurchaseOrdersForApprover (J4300040) Use this operation to retrieve purchase order header records for all orders that are currently awaiting approval by the signed-on user.
getPurchaseOrderDetailForApprover (J4300050) Use this operation to retrieve purchase order detail records for all orders that are currently awaiting approval by the signed-on user.
processPurchaseOrderApproveReject (JP4300080) Use this operation to approve or reject a specific purchase order, and to update any remarks the user enters.

A.2.1 getPurchaseOrderEmployeeProfile

The getPurchaseOrderEmployeeProfile (J4300060) web service operation is a database query operation that enables consumers to retrieve and review employee profile information from the JD Edwards EnterpriseOne database.

A.2.1.1 Implementation Details

The following table includes information that can help determine whether the getPurchaseOrderEmployeeProfile (J4300060) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, one record is returned, based on the selection criteria.

The record that is returned to the consumer includes all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • approverId

  • approverName

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records during processing.

A.2.2 getPurchaseOrderCounts

The getPurchaseOrderCounts (J4300070) web service operation is a database query operation that enables consumers to retrieve and review purchase order categories, along with counts of the number of purchase orders currently awaiting approval by the signed-on user.

A.2.2.1 Implementation Details

The following table includes information that can help determine whether the getPurchaseOrderCounts (J4300070) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the setup, and whether the signed-on user has orders currently awaiting their approval.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • description

  • recordCount

  • version

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database. Also verify that the processing options for the M43081 and P43081 are set up correctly.
Does this operation use record reservation? No. This operation does not reserve records during processing.

A.2.3 getPurchaseOrdersForApprovers

The getPurchaseOrdersForApprovers (J4300040) web service operation is a database query operation that enables consumers to retrieve and review purchase order information from the JD Edwards EnterpriseOne database.

A.2.3.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes purchase order information. This table includes information about the business service properties that the getPurchaseOrdersForApprovers (J4300040) web service operation uses:

Group Key Description Default Value
J4300040 J4300040_MAX_ROWS Use this business service property to specify the maximum number of records the operation can return for a query. 100

A.2.3.2 Implementation Details

The following table includes information that can help determine whether the getPurchaseOrdersForApprover (J4300040) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the setup, and whether the signed-on user has orders currently awaiting their approval.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • documentCompanyKeyOrderNo

  • documentOrderInvoiceNumber

  • documentOrderTypeCode

  • approver

  • entityNameApprover

  • originator

  • entityNameOriginator

  • businessUnitCode

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records during processing.

A.2.4 getPurchaseOrderDetailForApprover

The getPurchaseOrderDetailForApprover (J4300050) web service operation is a database query operation that enables consumers to retrieve and review purchase order detail information from the JD Edwards EnterpriseOne database.

A.2.4.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes purchase order information. This table includes information about the business service properties that the getPurchaseOrderDetailForApprover (J4300050) web service operation uses:

Group Key Description Default Value
J4300050 J4300050_MAX_ROWS Use this business service property to specify the maximum number of detail records the operation can return for a query. 100

A.2.4.2 Implementation Details

The following table includes information that can help determine whether the getPurchaseOrderDetailsForApprover (J4300050) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the setup, and whether the signed-on user has orders currently awaiting their approval.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • companyKeyOrderNo

  • documentOrderInvoiceNumber

  • documentOrderTypeCode

  • documentLineNumber

  • businessUnitCode

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.

Also verify that the business service property that controls the number of records to return for the query is set correctly.

Does this operation use record reservation? No. This operation does not reserve records during processing.

A.2.5 processPurchaseOrderApproveReject

The processPurchaseOrderApproveReject (J4300080) web service operation is an inbound transaction operation that enables consumers to approve or reject purchase order records in the EnterpriseOne database from their mobile device.

The operation uses the business function B4305420 to approve or reject the purchase order. If the operation is successful, the system returns a completion message to the mobile device, which includes these values:

  • numberOfPurchaseOrdersProcessed

  • numberOfDetailRemarksProcessed

  • confirmApproveRejectSuccess

Additionally, the order is removed from the list of orders awaiting approval.

If the operation encounters errors, processing stops and the errors are returned to the consumer.

A.2.5.1 Implementation Details

The following table includes information that can help determine whether the processPurchaseOrderApproveReject (J4300080) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, the consumer receives a successful return message.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • numberOfPurchaseOrdersProcessed

  • confirmApproveRejectSuccess

The values for both of these fields will be equal to 1 when the operation is successful.

If I encounter errors while processing a transaction, do I need to reverse the transaction? This operation uses standard transaction processing. If the system encounters errors during processing, no data in the JD Edwards EnterpriseOne system is updated. No manual updates are required.
Does this operation use record reservation? No. This operation does not reserve records during processing.

A.3 Requisition Self Service Business Services

The mobile requisition self service approval process uses these business services:

  • RequisitionSelfServiceManager published business service (JP43E010).

  • RSSApproverQueryProcessor (J43E0050), which contains the method getRSSForApprover.

  • RSSDetailQueryProcessor (J43E0060), which contains the method getRSSDetailForApprover.

  • processRSSApproveReject (J43E0080).

The RequisitionSelfServiceManager published web service (JP43E010) manages the processing of mobile RSS-related web service operations. This table includes a description of those web service operations, as they relate to mobile requisition self service processing:

Operation/Method Description
getRSSForApprover (J43E0050) This method is contained within the RSSApproverQueryProcessor operation. Use this method to retrieve the approval requests, at either the order or line level, for the signed-on user.
getRSSDetailForApprover (J43E0060) This method is contained within the RSSDetailQueryProcessor operation. Use this method to retrieve requisition detail records.
processRSSApproveReject Use this operation to approve or reject a specific requisition order or line.

A.3.1 RSSApproverQueryProcessor

The RSSApproverQueryProcessor(J43E0050) is a web service operation that calls the getRSSForApprover method. This method is a database query that enables consumers to retrieve and review requisition approval messages from the EnterpriseOne work center. The method uses search criteria that is defined when the user signs into the mobile application to select records from the work center.

If the operation completes successfully, it retrieves data from the Requisition Header or Requisition Detail tables for each record in the work center message, if data exists in the database.

A.3.1.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes requisition information. This table includes information about the business service properties that the RSSApproverQueryProcessor (J43E0050) web service operation uses:

Group Key Description Default Value
J43E0050 J43E0050_V98860D_MAX_ROWS Use this business service property to specify the maximum number of work center message records to return during a query. 100

A.3.1.2 Implementation Details

The following table includes information that can help determine whether the RSSApproverQueryProcessor (J43E0050) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • companyKeyOrderNo

  • documentOrderInvoice

  • orderType

  • transactionOriginator

  • taskAssignmentUniqueID

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database. Specifically, verify that messages exist in the EnterpriseOne work center for the signed-on user's address book number.
Does this operation use record reservation? No. This operation does not reserve records.

A.3.2 RSSDetailQueryProcessor

The RSSDetailQueryProcessor(J43E0060) is a web service operation that calls the getRSSDetailForApprover method. This method is a database query that enables consumers to retrieve one or many requisition detail lines for a given requisition order from the JD Edwards EnterpriseOne database.

A.3.2.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes requisition information. This table includes information about the business service properties that the RSSDetailQueryProcessor (J43E0060) web service operation uses:

Group Key Description Default Value
J43E0060 J43E0060_F43E11_MAX_ROWS Use this business service property to specify the maximum number of detail records the operation can return for a query. 100

A.3.2.2 Implementation Details

The following table includes information that can help determine whether the RSSDetailQueryProcessor (J43E0060) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, one to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • companyKeyOrderNo

  • documentOrderInvoiceNumber

  • orderType

  • orderSuffix

  • lineNumber

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.3.3 processRSSApproveReject

The processRSSApproveReject web service operation (J43E0080) is an inbound transaction operation that enables consumers to approve or reject requisition workflow messages in the EnterpriseOne database.

The operation uses the Update RSS Approval Rejection business function (N43E01470) to approve or reject the requisitions. If the operation is successful, the system returns a completion message to the consumer. If the operation encounters errors, processing stops and the errors are returned to the consumer.

A.3.3.1 Implementation Details

The following table includes information that can help determine whether the RSSDetailQueryProcessor (J43E0060) web service operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, the consumer receives a successful return message.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • errorMessageIDWorkflow

  • confirmSuccessApproveReject will be equal to 1 if the operation is successful.

If I encounter errors while processing a transaction, do I need to reverse the transaction? This operation uses standard transaction processing. If the system encounters errors during processing, no data in the EnterpriseOne database is updated. No manual updates are required.
Does this operation use record reservation? No. This operation does not reserve records.

A.4 Mobile Sales Inquiry Business Services

The mobile sales inquiry processes use these published business services:

  • MobileSalesOrderManager (JP42M000)

  • InventoryManager (JP410000)

The MobileSalesOrderManager published web service (JP42M000) manages the processing of mobile sales order inquiry-related web service operations. This table includes a description of the web service operations:

Operation/Method Description
getMobileSalesOrderHeader (J42M0010) Use this operation to retrieve sales order header records from the EnterpriseOne database. The operation uses the user-defined search criteria to retrieve records.
getMobileSalesOrderDetail (J42M0020) Use this operation to retrieve sales order detail information from the EnterpriseOne database. The operation retrieves the detail records that are associated with the sales order header that the user selects.
getUDCDescription (J0000050) Use this operation to retrieve valid document type values from user-defined code table 00/DT. This operation is called by the getDocumentTypeDescription method, and is managed by the FoundationEnvironment published business service (JP000000).

The InventoryManager published web service (JP410000) manages the processing of mobile pricing and availability inquiry-related web service operations. This table includes a description of the web service operations:

Operation/Method Description
getCalculatedAvailability (J4100007) Use this operation to retrieve item availability records from the EnterpriseOne database. The operation uses the user-defined search criteria to retrieve records.
getItemPrice (J4100040) Use this operation to retrieve item pricing information from the EnterpriseOne database. The operation uses the user-defined search criteria to retrieve records.
getItemBranchSearch (J4100060) Use this operation to retrieve valid branch plant values that can be used in the search criteria when searching for item price and availability records.
getItemSearch (J4100050) Use this operation to retrieve valid item number values that can be used in the search criteria when searching for item price and availability records.

The following operations and methods are called from the FoundationEnvironment published business service, which is documented in the JD Edwards EnterpriseOne Applications Business Services Reference Guide:

Operation/Method Description
getDocumentTypeDescription (J0000030) Use this method to retrieve the document type description from the EnterpriseOne database. This method is contained in the getUserDefinedCode operation (J0000030).
getUserValues (J0000070) Use this method to retrieve user defined code values from the EnterpriseOne database.
getUserProfile (J0000080) Use this method to retrieve user profile information for the signed-on user from the EnterpriseOne database.
getLookupUDC (J0000090) Use this method to look up user defined code values in the EnterpriseOne database.

A.4.1 getMobileSalesOrderHeader

The getMobileSalesOrderHeader (J42M0010) is a database query operation that enables consumers to retrieve and review sales order header records from the JD Edwards EnterpriseOne database. The operation retrieves data from the F4201 and F42019 (depending on whether the order is active or historical) for each sales order header record that meets the specified search criteria, if data exists in the database.

This operation is managed by the MobileSalesOrderManager published business service (JP42M000).

A.4.1.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes sales order information. This table includes information about the business service properties that the getMobileSalesOrderHeader (J42M0010) web service operation uses:

Group Key Description Default Value
J42M0010 J42M0010_MAX_ROWS Use this business service property to specify the maximum number of header records the operation can return for a query. 100

A.4.1.2 Implementation Details

The following table includes information that can help determine whether the getMobileSalesOrderHeader (J42M0010) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • companyKeyOrderNo

  • documentOrderInvoice

  • orderType

  • costCenter

  • addressNumber

  • addressNumberShipTo

  • dateRequestedJulian

  • soldToDesc

  • shipToDesc

  • branchPlantDesc

  • orderTypeDesc

  • DataDisplayDecimals_OTOT

  • DataDisplayDecimals_FAP

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.4.2 getMobileSalesOrderDetail

The getMobileSalesOrderDetail (J42M00020) is a database query operation that enables consumers to retrieve and review sales order detail information from the JD Edwards EnterpriseOne database. This operation retrieves data from the F4211 and F42119 tables (depending on whether the order is active or historical) for each sales detail record if the data exists in the database.

This operation is managed by the MobileSalesOrderManager published business service (JP42M000).

A.4.2.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes sales order information. This table includes information about the business service properties that the getMobileSalesOrderDetail (J42M0020) web service operation uses:

Group Key Description Default Value
J42M0020 J42M0020_MAX_ROWS Use this business service property to specify the maximum number of header records the operation can return for a query. 100

A.4.2.2 Implementation Details

The following table includes information that can help determine whether the getMobileSalesOrderDetail (J42M0020) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • companyKeyOrderNo

  • documentOrderInvoice

  • orderType

  • lineNumber

  • costCenter

  • dateRequestedJulian

  • statusCodeNext

  • statusCodeLast

  • unitsTransactionQty

  • lastStatusDesc

  • nextStatusDesc

  • DataDisplayDecimals_UPRC

  • DataDisplayDecimals_AEXP

  • DataDisplayDecimals_FUP

  • DataDisplayDecimals_FEA

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.4.3 getCalculatedAvailability

getCalculatedAvailability (J4100007) is a web service operation that calculates the availability for a specified item for a single or multiple branch plant. The operation retrieves both summary and detailed availability information from the F41021 table.

This operation is managed by the InventoryManager published business service (JP410000).

A.4.3.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes item availability information. This table includes information about the business service properties that the getCalculatedAvailability (J4100007) web service operation uses:

Group Key Description Default Value
JP410000 J4100007_F41021_MAX_GRID_ROWS_RETURNED Use this business service property to specify the maximum number of header records the operation can return for a query. If the number of records that meet the search criteria is greater than the value in this property, the system does not return and display all values in the mobile device. 100

A.4.3.2 Implementation Details

The following table includes information that can help determine whether the getCalculatedAvailability (J4100007) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • item

  • unitOfMeasure

  • totalQtyAvailable

  • The fields that include availability summary information.

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.4.4 getItemPrice

getItemPrice (J4100040) is a database query operation that enables consumers to retrieve and review the base price records from the JD Edwards EnterpriseOne database. This operation retrieves data from the F4106 table for each base price record, if the data exists in the database.

This operation is managed by the InventoryManager published business service (JP410000).

A.4.4.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes item pricing information. This table includes information about the business service properties that the getItemPrice (J4100040) web service operation uses:

Group Key Description Default Value
JP410000 J4100040_V4106C_MAX_GRID_ROWS_RETURNED Use this business service property to specify the maximum number of header records the operation can return for a query. 100

A.4.4.2 Implementation Details

The following table includes information that can help determine whether the getItemPrice (J4100040) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • priceHierarchy

  • amtPricePerUnit2

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.4.5 getItemBranchSearch

getItemBranchSearch (J4100060) is a database query operation that enables consumers to retrieve branch plant details for a specified branch plant and description from the EnterpriseOne database. The operation retrieves data from the F41021 table, if data exists in the database.

This operation is managed by the InventoryManager published business service (JP410000).

A.4.5.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes item information. This table includes information about the business service properties that the getItemBranchSearch (J4100060) web service operation uses:

Group Key Description Default Value
JP410000 J4100060_F0006_MAX_GRID_ROWS_RETURNED Use this business service property to specify the maximum number of header records the operation can return for a query. 100

A.4.5.2 Implementation Details

The following table includes information that can help determine whether the getItemBranchSearch (J4100060) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • branchPlant

  • branchType

  • branchCompany

  • description

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.4.6 getItemSearch

etItemSearch (J4100050) is a database query operation that enables consumers to retrieve details for a specified item from the EnterpriseOne database.

This operation is managed by the InventoryManager published business service (JP410000).

A.4.6.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system processes item information. This table includes information about the business service properties that the getItemSearch (J4100050) web service operation uses:

Group Key Description Default Value
JP410000 J4100050_F4101_MAX_GRID_ROWS_RETURNED Use this business service property to specify the maximum number of header records the operation can return for a query. 100

A.4.6.2 Implementation Details

The following table includes information that can help determine whether the getItemSearch (J4100050) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • itemID

  • itemCatalog

  • itemProduct

  • itemFreeForm

  • itemDescription1

  • itemDescription2

  • itemSearchText

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.5 Mobile Service Time Entry Business Services

The mobile service time entry process uses these business services and operations:

  • Service Time Card Manager published business service (JP170002).

    This published business service manages the processing of all mobile time entry related web service operations except lookupServiceOrder and lookupAddressBook.

  • getServiceTimeCards (J1700050).

  • getServiceOperationSequence (J1700060).

  • getServiceTimeCardProcessingOptions (J1700070).

  • processServiceTimeCard (J1700080).

  • lookupServiceOrders (J1700001).

    This web service operation is managed by the CustomerServiceManager published web service (JP170000).

  • lookupAddressBook (J0100009).

    This web service operation is managed by the AddressBookManager published web service (JP010000).

This table lists and describes each of the web service operations used to process mobile service time entry information:

Operation/Method Description
getServiceTimeCards (J1700050) Use this operation to retrieve service timecards for the specific user. Additional filtering on specific search values can be applied.
getServiceOperationSequence (J1700060) Use this operation to retrieve operation sequence, which is attached to a specific service order.
getServiceTimeCardProcessingOptions (J1700070) Use this operation to retrieve the service timecard mobile processing options.
processServiceTimeCard (J1700080) Use this operation to add, update, and delete a service timecard.
lookupServiceOrders (J1700001) Use this operation to retrieve service order information.

See Customer Service Manager Web Service.

lookupAddressBook (J0100009) Use this operation to retrieve customer name or address number. This operation is managed by the AddressBookManager (JP010000), and is also used by the Mobile Expense Management process.

See Address Book Manager Web Service.


A.5.1 getServiceTimecards

The getServiceTimeCards web service operation (J1700070) is a database query operation that enables consumers to retrieve and review service timecard information from the JD Edwards EnterpriseOne database.

A.5.1.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system retrieves data from the database. This table includes information about the business service properties that the getServiceTimeCards operation uses:

Group Key Description Default Value
J1700050 J1700050_MAX_ROWS Use this business service property to specify the maximum number of header records the operation can return for a query. 100

A.5.1.2 Implementation Details

The following table includes information that can help determine whether the getServiceTimeCards (J1700050) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • addressNumber

  • workDate

  • hoursWorked

  • processedCode

  • orderNumber

  • operationSequence

  • shiftCode

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.5.2 getServiceOperationSequence

The getServiceOperationSequence web service operation (J1700060) is a database query operation that enables consumers to retrieve and review list of operation sequence attached to a specific order from the JD Edwards EnterpriseOne database.

A.5.2.1 Setup Considerations

Before you use this operation, you can set business service properties to specify how the system retrieves data from the database. This table includes information about the business service properties that the getServiceOperationSequence operation uses:

Group Key Description Default Value
J1700060 J1700060_MAX_ROWS Use this business service property to specify the maximum number of header records the operation can return for a query. 100

A.5.2.2 Implementation Details

The following table includes information that can help determine whether the getServiceOperationSequence (J1700060) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • operationSequence

  • orderNumber

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.5.3 getServiceTimeCardProcessingOptions

The getServiceTimeCardProcessingOptions web service operation (J1700070) is a database query operation that enables consumers to retrieve and review service time entry mobile application processing options from the JD Edwards EnterpriseOne database.

The operation uses the business function (B1703150) to fetch the procession options from the JD Edwards EnterpriseOne database.

A.5.3.1 Implementation Details

The following table includes information that can help determine whether the getServiceOperationSequence (J1700070) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • operationStatusCode

  • shiftCode

  • hideStatusCode

  • daysPast

If I encounter errors while processing a transaction, do I need to reverse the transaction? This is a database query operation that does not perform transactions. If you encounter errors during processing, review your search criteria and business service property settings and try your query again. If the operation does not return any records, verify that records matching your query exist in the JD Edwards EnterpriseOne database.
Does this operation use record reservation? No. This operation does not reserve records.

A.5.4 processServiceTimeCard

The processServiceTimeCard web service operation (J1700080) is an inbound transaction operation that enables consumers to create, update, and delete service timecards in the EnterpriseOne database.

The operation uses the business function B1703160 to call the existing service timecard master business function B3101040 to create, update, and delete timecards. If the operation is successful, the system returns a completion message to the consumer. If the operation encounters errors, processing stops and the errors are returned to the consumer.

A.5.4.1 Implementation Details

The following table includes information that can help determine whether the processServiceTimeCard (J1700080) operation is functioning correctly:

Question Answer
How can I tell if the operation completes successfully? If the operation completes successfully, zero to many records are returned, based on the selection criteria.

The records that are returned to the consumer include all of the fields that are listed in the response interface for this operation. However, some of those fields can contain blank or zero values, depending on the data that exists in the JD Edwards EnterpriseOne system.

At a minimum, the system returns non-zero values for these fields:

  • hasErrors

If successful, the value of the hasErrors field is false.

If I encounter errors while processing a transaction, do I need to reverse the transaction? This operation uses standard transaction processing. If the system encounters errors during processing, no data in the JD Edwards EnterpriseOne system is updated. No manual updates are required.
Does this operation use record reservation? No. This operation does not reserve records.