EBIThree.com > JDE @ EBIThree.com > E1 Database Integration Tips 1

E1 Database Integration Tips 1

CLARIFY EBI SQL ACCESS

Cleo Clarify 3 SQL ACCESS icon

When setting up variables in a SQL Action, the input and output variables for numeric JDE fields can be defined as VARCHAR or NUMERIC. Cleo Clarify JDEdwards SQL Action for F0101 Address Book

CLARIFY EBI RULESETS

Cleo Clarify 3 Ruleset icon

Ruleset Item 1:

Due to Oracle’s NCHAR type of data fields, EXTOL imports the fields with double the length. Meaning, if F47046.PNID is type: NCHAR and a length of 15. EXTOL imports the field with a length of 30.

If a JDE schema is refreshed and a new field is introduced then follow the steps below.

  • Locate where JDE record is being written
  • In the rules following the record creation, add the new alpha field to the target.
For example, this would be applicable to F47046 if a new alpha field is introduced in the Outbound Invoice Header file.

Ruleset Item 2:

As the inbound EDI maps are currently built, all fields are written out after the records are created. If a field is mapped to, before the record is created, then users will get an error in the Auditor log.

Ruleset Item 3:

When working with SQL Actions and passing a character input variable users need to know the field length(s). JDE users can use DataBrowser to determine the field length.

Once the field length is determined users can do the following
  • Move that number of blank spaces into a string variable.
  • Determine length of actual input value and then substring the value into the newly created string variable. See below for examples.
Cleo Clarify JDEdwards Ruleset define length for Database
By: on