JDE Connector API Reference

The JDE Connector provides integration to JD Edwards EnterpriseOne Synchronize data and automate business processes between JD Edwards and third party billing, marketing automation, CRM, HR, and social applications.

Additional Info

Requires Mule Enterprise License

Yes

Requires Entitlement

Yes

Mule Version

3.6.0 or higher

Configs

Configuration

<jde:config>

Connection Management

JDE connector configuration that uses JDE authentication for establishing connection with JDE Enterprise Server.

Attributes

Name	Java Type	Description	Required
name	String	The name of this configuration. With this name can be later referenced.	x
user	String	JDE User used to initialize the JDE Session	x
password	String	Password used to authenticate the JDE user	x
environment	String	This value must be used for specifying the JDE Environment	x
role	String	This value must be used for specifying the JDE User Role	x

Name

Java Type

Description

Default Value

Required

name

String

The name of this configuration. With this name can be later referenced.

user

String

JDE User used to initialize the JDE Session

password

String

Password used to authenticate the JDE user

environment

String

This value must be used for specifying the JDE Environment

role

String

This value must be used for specifying the JDE User Role

Processors

Call BSFN

<jde:call-object>

DataSense enabled

Invoke a JDE Business Function on JDE Enterprise server.
The BSFN parameters mapping has 4 commons parameters:

_BSFNThrowExceptionWithErrorsYN (Input) - String - Values: Y, The flow will throw exception JDEBfsnError when BSFN found an error.
_BSFNReturnCode (Output) - Integer - Values: 0: Processed Correctly, 1: There is warnings, 2: There is errors.
_BSFNNumberOfErrors (Output) - Integer - Number of errors.
_BSFNDetailErrors (Output) - List - Detail of the error. It return ArrayList of CallObjectErrorItem.

XML Sample

<jde:call-object config-ref="JDE__Configuration" entityType="AddressBookMasterMBF" doc:name="JDE">
        <jde:entity-data>
                <jde:entity-datum key="mnAddressBookNumber">#[1L]</jde:entity-datum>
                <jde:entity-datum key="_BSFNThrowExceptionWithErrorsYN">N</jde:entity-datum>
                <jde:entity-datum key="cActionCode">I</jde:entity-datum>
        </jde:entity-data>
</jde:call-object>

Attributes

Name	Java Type	Description	Default Value	Required
config-ref	String	Specify which config to use		x
entityType	String	The BSFN function name. Example: AddressBookMasterMBF		x
entityData	Map<String,Object>	The BSFN function parameters/values and common parameters/values.	#[payload]

Name

Java Type

Description

Default Value

Required

config-ref

String

Specify which config to use

entityType

String

The BSFN function name. Example: AddressBookMasterMBF

entityData

Map<String,Object>

The BSFN function parameters/values and common parameters/values.

#[payload]

Returns

Return Java Type	Description
Map<String,Object>	a map containing the BSFN parameters with its values of the invoked operation. The MAP will have the parameter names as the key and the following object as value: -

Return Java Type

Description

Map<String,Object>

a map containing the BSFN parameters with its values of the invoked operation. The MAP will have the parameter names as the key and the following object as value: -

Submit Batch Process

<jde:submit-batch-process>

DataSense enabled

Submit UBE/VERSION to JDE Enterprise Server.
The Submit Batch Process parameters mapping has 3 commons parameters:

_Job_ID: (Output) - Long - JDE Job ID.
_Job Queue: (Input) - String - Enter the Job Queue or empty if you prefer default job queue for the UBE selected.
_Selection: (Input) - Where SQL Sentence using table from the master UBE View. Example: F0010.CO = '00000'
[Report Interconnect and its values]

XML Sample

<jde:submit-batch-process config-ref="JDE__Configuration" entityType="R0008P_XJDE0001" doc:name="JDE">
        <jde:entity-data>
                <jde:entity-datum key="_Job_Queue">QBATCH</jde:entity-datum>
                <jde:entity-datum key="_Selection">F0010.CO = '00000'</jde:entity-datum>
                <jde:entity-datum key="cFiscalDatePattern">F</jde:entity-datum>
        </jde:entity-data>
</jde:submit-batch-process>

Attributes

Name	Java Type	Description	Default Value	Required
config-ref	String	Specify which config to use		x
entityType	String	UBE-VERSION name.		x
entityData	Map<String,Object>	The UBE function parameters and values.	#[payload]

Name

Java Type

Description

Default Value

Required

config-ref

String

Specify which config to use

entityType

String

UBE-VERSION name.

entityData

Map<String,Object>

The UBE function parameters and values.

#[payload]

Returns

Return Java Type	Description
Map<String,Object>	a map containing the UBE parameters with its values of the invoked operation. The MAP will have the following values: - '_Job_ID': Long - JDE Job ID generated by JDE

Return Java Type

Description

Map<String,Object>

a map containing the UBE parameters with its values of the invoked operation. The MAP will have the following values: - '_Job_ID': Long - JDE Job ID generated by JDE

Get Batch Process Information

<jde:get-batch-process-information>

DataSense enabled

Get UBE status from JDE server
The Get Batch Process Information has 2 parameters:

"Job_ID" (Long) - Input - (JOBID for the ube that it ran or is running on the EnterpriseServer)
"Job_Status" (String) - Output - Status of the job. The possible values of job status are: "S" In Queue , "W" Waiting, "P" Processing , "D" Done, "E" Error, "H" Hold

XML Sample

<jde:get-batch-process-information config-ref="JDE__Configuration" entityType="Get Job Status" doc:name="JDE">
        <jde:entity-data>
                <jde:entity-datum key="Job_ID">#[1L]</jde:entity-datum>
        </jde:entity-data>
</jde:get-batch-process-information>

Attributes

Name	Java Type	Description	Default Value	Required
config-ref	String	Specify which config to use		x
entityType	String	"Get Job Status"		x
entityData	Map<String,Object>	"Job_ID" (Long) - Input - (JOBID for the ube that it ran or is running on the EnterpriseServer) "Job_Status" (String) - Output - Status of the job.	#[payload]

Name

Java Type

Description

Default Value

Required

config-ref

String

Specify which config to use

entityType

String

"Get Job Status"

entityData

Map<String,Object>

"Job_ID" (Long) - Input - (JOBID for the ube that it ran or is running on the EnterpriseServer) "Job_Status" (String) - Output - Status of the job.

#[payload]

Returns

Return Java Type	Description
Map<String,Object>	a map containing the UBE Batch Information parameters with its values of the invoked operation. The MAP will have the following values: - 'Job_ID': (same as input

Return Java Type

Description

Map<String,Object>

a map containing the UBE Batch Information parameters with its values of the invoked operation. The MAP will have the following values: - 'Job_ID': (same as input

Poll Events

<jde:poll-events>

DataSense enabled

Get Outbound Events that it come from an application that uses a Master Business Function to generate transactions.
JDE outbound transactions requires that you set a Processing Option specifying a transaction type.
Additionally, some entry programs enable you to specify a version of the Master Business Function Processing Options program that, in turn, enables you to specify a version of the Interoperability Processing Options program.
The Poll Events has 5 parameters:

Transaction Code(String) - Input - Transaction Code informed in MBF
Max Qty Transactions to Read(Integer) - Input - Transactions to read for each poll - Max values is 100
Last Batch Number (EDBT)(String) - Input - Used to read from that last edbt
Quantity Transactions Unprocessed(Integer) - Output - Pending transaction unproccessed
Event Transactions(String) - Output - XML with the transaction.

XML Sample

<jde:poll-events config-ref="JDE__Configuration" entityType="Capture Event Transactions" doc:name="JDE">
        <jde:entity-data>
                <jde:entity-datum key="Transaction Code">JDECM</jde:entity-datum>
                <jde:entity-datum key="Last Batch Number (EDBT)">#[&amp;quot;&amp;quot;]</jde:entity-datum>
                <jde:entity-datum key="Max Qty Transactions to Read">10</jde:entity-datum>
        </jde:entity-data>
</jde:poll-events>

Attributes

Name	Java Type	Description	Default Value	Required
config-ref	String	Specify which config to use		x
entityType	String	"Capture Event Transactions"		x
entityData	Map<String,Object>	Interoperability Parameters and values	#[payload]

Name

Java Type

Description

Default Value

Required

config-ref

String

Specify which config to use

entityType

String

"Capture Event Transactions"

entityData

Map<String,Object>

Interoperability Parameters and values

#[payload]

Returns

Return Java Type	Description
Map<String,Object>	a map containing the results of the invoked operation. It will contain the same input parameters: Transaction Code,Max Qty Transactions to Read,Last Batch Number

Return Java Type

Description

Map<String,Object>

a map containing the results of the invoked operation. It will contain the same input parameters: Transaction Code,Max Qty Transactions to Read,Last Batch Number

EDI Outbounds

<jde:edi-outbounds>

DataSense enabled

Get EDI Outbounds events from JDE EDI Application The Poll Events has 5 parameters:

EDI Code(Input) - String - EDI code
EDI Document Type(Input) - String - EDI Document Type that it will be captured.
EDI Last EDI Document(Input/Output) - Integer - Last EDI number processed.
EDI UBE QUEUE(Input) - String - Queue where the EDI UBE-VERSION will run.
EDI UBE-VERSION to update Transaction(Input) - String - Standard UBE to update transactions as processed.
Max Qty Transactions to Read(Input) - Integer - Transactions to read for each poll - Max values is 100
Quantity EDI Transactions Unprocessed(Output) - Integer - Transactions pending.
EDI Transactions(Ouptut) - String: XML with the transactions

XML Sample

<jde:edi-outbounds config-ref="JDE__Configuration" entityType="Capture EDI Transactions" doc:name="JDE">
        <jde:entity-data>
                <jde:entity-datum key="EDI Last EDI Document">#[0L]</jde:entity-datum>
                <jde:entity-datum key="EDI UBE QUEUE">QBATCH</jde:entity-datum>
                <jde:entity-datum key="Max Qty Transactions to Read">10</jde:entity-datum>
                <jde:entity-datum key="EDI Document Type">SO</jde:entity-datum>
                <jde:entity-datum key="EDI UBE-VERSION to Update Transaction">R47027-XJDE0001</jde:entity-datum>
                <jde:entity-datum key="EDI Code">855</jde:entity-datum>
        </jde:entity-data>
</jde:edi-outbounds>

Attributes

Name	Java Type	Description	Default Value	Required
config-ref	String	Specify which config to use		x
entityType	String	Get EDI Transactions and Update EDI Transaction		x
entityData	Map<String,Object>	the EDI Parameters and values	#[payload]

Name

Java Type

Description

Default Value

Required

config-ref

String

Specify which config to use

entityType

String

Get EDI Transactions and Update EDI Transaction

entityData

Map<String,Object>

the EDI Parameters and values

#[payload]

Returns

Return Java Type	Description
Map<String,Object>	a map containing the results of the invoked operation. It will contain the same input parameters: EDI Code,EDI Document Type,EDI Last EDI Document,EDI UBE QUEUE,EDI

Return Java Type

Description

Map<String,Object>

a map containing the results of the invoked operation. It will contain the same input parameters: EDI Code,EDI Document Type,EDI Last EDI Document,EDI UBE QUEUE,EDI

BSFN Transaction

<jde:bsfn-transaction>

DataSense enabled

Transaction Processing For BSFN.
Used to wrap one or more BSFN in a transaction.

XML Sample

<jde:bsfn-transaction config-ref="JDE__Configuration" entityType="Begin Transaction" doc:name="JDE">
</jde:bsfn-transaction>
<jde:bsfn-transaction config-ref="JDE__Configuration" entityType="Commit Transaction" doc:name="JDE">
</jde:bsfn-transaction>
<jde:bsfn-transaction config-ref="JDE__Configuration" entityType="Rollback Transaction" doc:name="JDE">
</jde:bsfn-transaction>

Attributes

Name	Java Type	Description	Default Value	Required
config-ref	String	Specify which config to use		x
entityType	String	"Begin Transaction" / "Commit Transaction" / "Rollback Transaction"		x
entityData	Map<String,Object>	N/A	#[payload]

Name

Java Type

Description

Default Value

Required

config-ref

String

Specify which config to use

entityType

String

"Begin Transaction" / "Commit Transaction" / "Rollback Transaction"

entityData

Map<String,Object>

N/A

#[payload]

Returns

Return Java Type	Description
Map<String,Object>	an empty map

Return Java Type

Description

Map<String,Object>

an empty map

Log Out

<jde:log-out>

Logs the current user out of the JDE server.

XML Sample

<jde:log-out config-ref="JDE__Configuration"  doc:name="JDE">
</jde:log-out>

Attributes

Name	Java Type	Description	Default Value	Required
config-ref	String	Specify which config to use		x

Name

Java Type

Description

Default Value

Required

config-ref

String

Specify which config to use