6 Business Services for Pre-Built Integrations

This chapter includes these topics:

6.1 Overview of Business Services for Pre-Built Integrations

The business services that are documented in this guide have been built to enable you to create your own integration processes that meet your business requirements.

In addition to these business services, there are several other business services that have been built to support specific integrations between JD Edwards EnterpriseOne and other third-party systems. Though these business services were created as part of a specific solution, you can use them just as you would any other business service to meet the needs of your organization.

In most instances, those business services are documented in the solution-specific documentation that was created for the specific integration solution. This chapter lists all of the business services that are documented outside of this reference guide, provides you with a description of each service, and includes a reference to the detailed documentation for that service.

6.2 Agile Product Lifecycle Management Integration with JD Edwards EnterpriseOne

Agile Product Lifecycle Management (PLM) enables companies to manage individual product life cycles and to complete product portfolios and programs tied to product conception, design, launch, maturity, and phase-out. Primary users of Agile PLM are involved directly or indirectly in the product design. These users manage content in Agile PLM that often directly affects processes managed in other enterprise systems, such as JD Edwards EnterpriseOne, Manufacturing Execution Systems (MES), Customer Relationship Management (CRM), and so forth.

The integration of Agile PLM and JD Edwards EnterpriseOne is designed to synchronize product content information between Agile Product Collaboration and JD Edwards EnterpriseOne.

The Agile PLM integration uses these business services:

Business Service Description
EngineeringChangeOrderManager (JP300000) The EngineeringChangeOrderManager Published Business Service (PBSSV) manages the processing of the following:

  • EngineeringChangeOrdersProcessor (J3000010)

  • EngineeringChangeOrderPartsListProcessor (J3000020)

  • InventoryItemsProcessor (J4100020)

  • InventoryItemBranchProcessor (J4100030)
EngineeringChangeOrdersProcessor (J3000010) The EngineeringChangeOrderManager calls the EngineeringChangeOrdersProcessor from the provider when a user creates an ECO. For the Design to Release PIP, the external system is Agile PLM. The user creates an ECO in Agile PLM and releases the same to JD Edwards EnterpriseOne. This processor calls the create ECO (B3004100) business function to add a header record in F4801. This action generates an ECO number, which the system uses to create a BOM in JD Edwards EnterpriseOne.
EngineeringChangeOrderPartsListProcessor (J3000020) The EngineeringChangeOrdersProcessor calls the EngineeringChangeOrderPartsListProcessor web service. This processor calls the create ECO (B3004100) business function to add a parts list and related items in JD Edwards EnterpriseOne.
InventoryItemsProcessor (J4100020) The EngineeringChangeOrdersProcessor calls the InventoryItemsProcessor web service. This processor calls the F4101 ItemMasterAddition (B4101062) business function to add items in JD Edwards EnterpriseOne.
InventoryItemBranchProcessor (J4100030) The EngineeringChangeOrdersProcessor calls the InventoryItemsProcessor web service is called. This processor calls the F4102 ItemBranchAddition (B4101072) business function to add item branch records in JD Edwards EnterpriseOne.
IntegrationTimeStampManager (JP300010) The IntegrationTimeStampManager PBSSV manages the processing of the ProcessIntegrationTimeStamp (J3000030) business service.
ProcessIntegrationTimeStamp (J3000030) The IntegrationTimeStampManager PBSSV calls the ProcessIntegrationTimeStamp web service. This processor adds and modifies the Integration Time Stamp table (F0095) with the last successful runtime.

For additional information about these business services, see Oracle Design to Release Integration pack for Agile Product Lifecycle Management and JD Edwards EnterpriseOne Implementation Guide, "Configuring the Oracle Design to Release Integration Pack for Agile PLM and JD Edwards EnterpriseOne."

6.3 Mobile Applications

EnterpriseOne offers several mobile applications that enable users to inquire on and process business data on a mobile device while away from the office. EnterpriseOne mobile applications include:

  • Mobile Expense Management

  • Mobile Purchase Order Approval

  • Mobile Requisitions Self Service Approval

  • Mobile Sales Inquiries

  • Mobile Service Time Entry

These mobile applications use business services to pass data between the users' mobile devices and the EnterpriseOne database.


See Also:

For additional information about any of the business services listed in this section, see the Business Services for Mobile Applications in the JD Edwards EnterpriseOne Applications Functionality for Mobile Devices Implementation Guide.

All of the mobile applications documented in the JD Edwards EnterpriseOne Applications Functionality for Mobile Devices Implementation Guide use the AuthenticationManager (JPH90I01) to validate the mobile user's JD Edwards EnterpriseOne sign in credentials.

This table lists the business services used by the Expense Management mobile application:

Business Service Description
ExpenseReportManager (JP09E000) This published business service manages the processing of these business service operations:

  • ExpenseReportQueryProcessor (J09E0001)

  • ExpenseManagementEmployeeProfileQueryProcessor (J09E0002)

  • ExpenseReportWorkflowProcessor (J09E0003)

  • CreditCardTransactionProcessor (J09E0004)

  • ExpenseReportProcessor (J09E0005)

  • ExpenseReportRecordReservation (J09E0006)

  • 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).
ExpenseReportQueryProcessor (J09E0001) This operation manages the retrieval of expense report data for expense report entry, review, and approval processing on a mobile device. This operation contains these methods:

  • getAllExpenseReports

  • getExpenseReportsToApprove

  • getExpenseReports

  • getExpenseReportHeaders
ExpenseManagementEmployeeProfileQueryProcessor (J09E0002) This operation contains the getExpenseManagementEmployeeProfile method, which 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 in the mobile device at sign on.
ExpenseReportWorkflowProcessor (J09E0003) This operation is used to approve, reject, and submit expense reports from a mobile device, and contains these methods:

  • approveExpenseReport

  • rejectExpenesReport

  • submitExpenseReport
CreditCardTransactionProcessor (J09E0004) This operation contains the getCreditCardTransactions method, which is used to retrieve credit card transaction data from the EnterpriseOne database so that it can be added to an expense report that is created using a mobile device.
ExpenseReportProcessor (J09E0005) This operation is used to process expense report data that was entered on a mobile device in the EnterpriseOne database. This operation contains these methods:

  • processExpenseReports

  • processExpenseReportHeader

  • processExpenseReportDetail
ExpenseReportRecordReservation (J09E0006) This operation is used to reserve and release records in the EnterpriseOne database when a mobile user is updating the record. This operation contains these methods:

  • reserveExpenseReport

  • releaseExpenseReport
getExpenseManagementValuesList (J0000030) This operation is managed by the Foundation Environment published business service. This operation contains the getUserDefinedCode method, which retrieves UDC values from the EnterpriseOne database. These values are used to process expense report data on the mobile device.
lookupBusinessUnits (J0000040) This operation is managed by the FoundationEnvironment published business service. This operation retrieves business unit values from the EnterpriseOne database when a user searches for expense reports by business unit using a mobile device.
lookupCurrencyCodes (J0000060) This operation is managed by the FoundationEnvironment published business service. This operation retrieves currency code values from the EnterpriseOne database when a user searches for valid currency codes when entering or editing expense report data on a mobile device.
lookupAddress Book (J0100009) This operation is managed by the ManageAddressBook published business service. This operation is used to retrieve valid values from the EnterpriseOne database when a user searches for an expense report, or a manager, when working with expense reports on a mobile device.
lookupWorkOrders (J4800001) This operation is managed by the WorkOrderManager published business service. This operation retrieves work order numbers from the EnterpriseOne database when a user searches for a valid work order using their mobile device during expense report entry.
lookupJobCost (J5100001) This operation is managed by the JobCostManager published business service. This operation retrieves valid job cost data from the EnterpriseOne database when a user searches for a valid job cost using their mobile device during expense report entry.

This table lists the business services used by the Purchase Order Approval mobile application:

Business Service Description
ProcurementManager (JP430000) This published business service manages the processing of these mobile purchase order operations:

  • PurchaseOrderApprovalQueryProcessor (J4300040)

  • GetPurchaseOrderDetailForApprover (J4300050)

  • PurchaseOrderEmployeeProfileQueryProcessor (J4300060)

  • GetMobilePurchaseOrderCountsProcessor (J4300070)

  • PurchaseOrderApproveRejectProcessor (J4300080).
PurchaseOrderApprovalQueryProcessor (J4300040) This operation contains the getPurchaseOrdersForApprover method, which is used to retrieve purchase order header records for all orders that are currently awaiting approval by the signed on user.
GetPurchaseOrderDetailForApprover (J4300050). This operation contains the getPurchaseOrderDetailForApprover method, which is used to retrieve purchase order detail records for all orders that are currently awaiting approval by the signed on user.
PurchaseOrderEmployeeProfileQueryProcessor (J4300060). This operation contains the getPurchaseOrderEmployeeProfile method, and is used to retrieve the procurement profile, as well as additional EnterpriseOne profile information for the name or address number that is entered in the mobile device during sign on.
GetMobilePurchaseOrderCountsProcessor (J4300070). This operation contains the getPurchaseOrderCounts method, which is used to retrieve the purchase order descriptions and counts for each order type that is currently awaiting approval by the signed on user.
PurchaseOrderApproveRejectProcessor (J4300080). This operation contains the processPurchaseOrderApproveReject method, which is used to approve or reject a specific purchase order, and to update any remarks the user enters.

This table lists the business services used by the Requisition Self Service Approval mobile application:

Business Service Description
RequisitionSelfServiceManager published business service (JP43E010). This published business service manages the processing of all mobile RSS approval business service operations, which include:

  • RSSApproverQueryProcessor (J43E0050)

  • RSSDetailQueryProcessor (J43E0060)

  • processRSSApproveReject (J43E0080)
RSSApproverQueryProcessor (J43E0050) This operation contains the getRSSForApprover method, which is used to retrieve the approval requests, at either the order or line level, for the signed-on user.
RSSDetailQueryProcessor (J43E0060) This operation contains the getRSSDetailForApprover method, which is used to retrieve requisition detail records that are awaiting approval by the signed on user.
processRSSApproveReject (J43E0080) This operation contains the processRSSApproveReject method, which is used to approve a requisition order or line.

This table lists the business services used by the Sales Inquiries mobile application:

Business Service Description
MobileSalesOrderManager (JP42M000) This published business service manages the processing of these mobile sales business services:

  • getMobileSalesOrderHeader (J42M0010)

  • getMobileSalesOrderDetail (J42M0020)
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.
getUDCDescsription (J0000050) Use this operation is managed by the FoundationEnvironment published business service, and is used to retrieve valid document type values from user-defined code table 00/DT. This operation is called by the getDocumentTypeDescription method.
InventoryManager (JP410000) This published business service manages these operations, which are used by the mobile RSS Approval application:

  • getItemPrice (J4100040)

  • getItemSearch (J4100050)

  • getItemBranchSearch (J4100060)

  • getCalculatedAvailability (J4100007)
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.
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.
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.
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.

This table lists the business services used by the Mobile Service Time Entry application:

Operation/Method Description
Service Time Card Manager published business service (JP170002) This published business service manages the processing of the web service operations listed below in this table.
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.

6.4 Direct Connect for Requisition Self Service

The Direct Connect feature in the JD Edwards Requisition Self Service system enables users to select goods and services from approved vendor websites using the JD Edwards EnterpriseOne Shopping Cart program, and add them to a purchase requisition. This requisition is then processed through the JD Edwards EnterpriseOne system using standard processing.

The Direct Connect solution uses these business services:

Business Service Description
Direct Connect Authentication Processor (J43E0010) The Direct Connect Authentication Processor business service (J43E0010) is a transaction service that invokes the HTTP service to connect to the vendor's website and authenticates the user credentials.
Shopping Cart Processor (J43E0020) After JD Edwards EnterpriseOne users access a vendor's website and select the products or services that they want to purchase, they complete the steps on the vendor's website to check out. When a user initiates the checkout process, the Shopping Cart Processor business service (J43E0020) is invoked. The Shopping Cart Processor is an inbound transaction business service that transfers the user's checkout data from the vendor's website to the JD Edwards EnterpriseOne database.
InteroperabilityManager (JPH90I00) This published business service is called during XAPI execution, which is used during Direct Connect and Purchase Order Dispatch processing, to route the XAPI XML response to the enterprise server for business function execution.

For additional information about these business services, see "Setting Up Direct Connect and Purchase Order Dispatch."

6.5 Order Promising Integration Using Web Service Callout (Release 9.1 Update)

The Web Services Callout integration uses the GOP JAXRPC Processor (JC34A010) or the GOP JAXWS Processor (JC34A020) business services to consume the Global Order Promising Web service. When the system transmits sales order, purchase order, manual inventory, work order, work order parts list, and routing events from EnterpriseOne to Order Promising, the Order Promising business service converts the events into the XML format required by the Order Promising Server.

The Global Order Promising integration uses these business services:

Business Service Description
GOP JAXRPC Processor (JC34A010) The GOP JAXRPC Processor business service (JC34A010) runs on the Oracle WebLogic Server (WLS) platform and reads the data stored in specific JD Edwards EnterpriseOne tables.

The E1 Enterprise server collects the data required for determining promised delivery date from the JD Edwards EnterpriseOne tables and then calls the JC34A010 business service. The JC34A010 business service makes the necessary calls to the GOP Web methods and returns the promised dates received from GOP to the E1 Enterprise server.
GOP JAXWS Processor (J34A020) The GOP JAXWS Processor business service (JC34A020) runs on the Oracle WebLogic Server (WLS) platform or the Web Application Server (WAS) platform, and reads the data stored in specific JD Edwards EnterpriseOne tables.

The E1 Enterprise server collects the data required for determining promised delivery date from the JD Edwards EnterpriseOne tables, and then calls the JC34A020 business service. The JC34A020 business service makes the necessary calls to the GOP Web methods and returns the promised dates received from GOP to the E1 Enterprise server.

6.6 Purchase Order Dispatch for Requisition Self Service

Many organizations and vendors require purchase orders before they will complete a purchasing transaction. The Purchase Order (PO) Dispatch solution enables users to send purchase orders electronically from the JD Edwards EnterpriseOne system to the vendor.

The PO Dispatch solution uses this business service:

Business Service Description
PO Dispatch Processor (J43E0030) The PO Dispatch Processor business service (J43E0030) transforms the data that is generated by the Purchase Order Print program (R43500) into cXML 1.2.016 OrderRequest schema format. The PO Dispatch Processor business service then posts that cXML message so that it can be received by the vendor's website. The PO Dispatch Processor business service then receives the response from the vendor in cXML 1.2.016 OrderResponse schema format.

For additional information about these business services, see JD Edwards EnterpriseOne Applications Requisition Self Service Implementation Guide, "Setting Up Direct Connect and Purchase Order Dispatch."

6.7 Rate Shopping Integration Using Web Service Callout (Release 9.1 Update)

The Web Services Callout integration uses the Rate Shopping Processor (J49T0010) and the Rate Shopping WLS Processor (J49T0015), or the Rate Shopping JAXWS Processor (JC49T020) business services to consume the Rate Inquiry Web service of the Oracle Transportation Management system. When accessing rate shopping from the Sale Order programs, P4210 or P42101, the applicable business service converts the requested date, quantity, weight, and volume information into the XML format required by the Oracle Transportation Management rate inquiry Web service.

Business Service Description
Rate Shopping Processor (J49T0010) The Rate Shopping Processor business service (J49T0010) runs on the Oracle Application Server (OAS) platform or the Websphere Application Server (WAS) platform and receives the data that is passed from the Rate Shopping application (P49T10) through the call to the J49T0010 method getRateShopping. The data is transformed into an XML message. The Rate Shopping Processor business service consumes the Oracle Transportation Management Rate Inquiry Query (RIQ) Web service with the XML message and in turn receives the RIQ Response from the Oracle Transportation Management Web service. The Rate Shopping Processor business service converts the response and returns the data to the Rate Shopping application.
Rate Shopping WLS Processor (J49T0015) The Rate Shopping WLS Processor business service (J49T0015) runs on the Web Logic Server platform and receives the data that is passed from the Rate Shopping application (P49T10) through the call to the J49T0015 method getRateShoppingWLS. The data is loaded into the proxy classes generated from the Oracle Transportation Management WLS wsdl to build an XML message. The Rate Shopping WLS Processor business service consumes the Oracle Transportation Management Rate Inquiry Query (RIQ) Web service with the XML message and in turn receives the RIQ response from the Oracle Transportation Management Web service. The Rate Shopping WLS Processor business service converts the response received through the Oracle Transportation Management Web services proxy generated classes, and returns the data to the Rate Shopping application.
Rate Shopping JAXWS Processor (JC49T020) The Rate Shopping JAXWS Processor business service (JC49T020) runs on the Weblogic Server platform or the Websphere Application Server (WAS) and receives the data that is passed from the Rate Shopping application (P49T10) through the call to the JC49T020 method getRateShoppingJAXWS. The data is loaded into the proxy classes generated from the Oracle Transportation Management WLS wsdl to build an XML message. The Rate Shopping JAXWS Processor business service consumes the Oracle Transportation Management Rate Inquiry Query (RIQ) Web service with the XML message and in turn receives the RIQ response from the Oracle Transportation Web service. The Rate Shopping JAXWS Processor business service converts the response received through the Oracle Transportation Management Web services proxy generated classes and returns the data to the Rate Shopping application.

For additional information about these business services, see JD Edwards EnterpriseOne Applications Integration with Oracle Transportation Management Implementation Guide, "Rate Inquiry Process Using Web Services Callout."

6.8 EU VAT ID Validation with VIES Using Web Service (Release 9.1 Update)

You use the VAT Information Exchange System (VIES) Web service to enable quick and easy validation of VAT identification numbers throughout the European Union community. JD Edwards EnterpriseOne is set up to communicate with the VIES Web service, enabling you to validate VAT identification numbers for customers or suppliers directly in the JD Edwards EnterpriseOne system.

The aim of this business service is to enable you to run the Web service proxy on a weblogic server without having to run the migration tool.

This functionality runs on three supported applications servers:

  • Weblogic Server (WLS)

  • Websphere Application Server (WAS)

  • Oracle Application Server (OAS)

The type of business service (BSSV) build that you are using or that you want to use with this service determines which business service object you must configure:

Business Service Description
VIES VAT ID Validation (WLS)-EU – 01 (J740105) The VIESAppServerOASorWLS business service (J740105) allows running the JAXRPC web service proxy on a weblogic server instead of OAS without having to run the migration tool.
VIES VAT ID Validation JAXWS – EU-01 (J740120) This business service allows running a JAXWS based proxy for both WLS and WAS.
VIES VAT ID Validation – EU- 01 (J740102) This business service allows running the Web service proxy on OAS/WAS.

The EU VAT ID validation solution uses these business services:

Server Build Type Business Service
Weblogic Server (WLS) JAX-RPC with JDeveloper 11g J740105
Weblogic Server (WLS)

Note: For JD Edwards EnterpriseOne release Tools 9.1.2 or later.

 JAX-WS with JDeveloper 11g J740120
Websphere Application Server (WAS) JAX-RPC with JDeveloper 10g & RAD J740102
Websphere Application Server (WAS)

Note: For JD Edwards EnterpriseOne release Tools 9.1.2 or later.

 JAX-WS with JDeveloper 11g J740120
Oracle Application Server (OAS)

Note: Releases prior to JD Edwards EnterpriseOne Tools 9.1 use this option.

 JAX-RPC with JDeveloper 10g J740102

For additional information about this business service, see JD Edwards EnterpriseOne Applications Tax Processing Implementation Guide

6.9 Brazil NF-e Transmission Web Services (Release 9.1 Update)

The Web Services Callout integration uses the NF-e Lot Processing Processor (J76B0021) business services to orchestrate calls to the BSSV consumer proxies which in turn call the Web service of the Brazil fiscal authority.

It uses internal functions to read the input XML and convert it into the Simple Object Access Protocol (SOAP) message format required by the Web service and invokes the corresponding web service consumer proxy.

Business Service Description
NfeRecepcao (JC76B001) The NfeRecepcao service is called by the J76B0021 service to dispatch the NFe lot to the NfeRecepcaoLote2 web service provided by SEFAZ (Brazilian fiscal authority) and receive the receipt number or error code sent by SEFAZ.
NfeRetRecepcao (JC76B002) The NfeRetRecepcao service returns a status message from SEFAZ.
NfeCancelamento (JC76B003) The NfeCancelamento service is called by the J76B0021 service to dispatch the cancelled NFe numbers to the SEFAZ (Brazilian fiscal authority).
NfeInutilizacao (JC76B005) The NfeInutilizacao service is called by the J76B0021 service to dispatch the unused or destroyed NFe numbers to the SEFAZ (Brazilian fiscal authority).


See Also:

"Using the NFe Transmission Process" in the JD Edwards EnterpriseOne Applications Localizations for Brazil Implementation Guide.

"Business Services for Brazil" in the JD Edwards EnterpriseOne Applications Localizations for Brazil Implementation Guide.