Skip navigation

Reader.pngIt is required that JD Edwards EnterpriseOne roles managed from the LDAP server be also used for the E1 authentication process. This new KM document provides the steps to set up the E1 role management at LDAP server level and the steps involved when the roles need to be changed for specific users. Doc ID 2465810.1. http://ora.cl/5cP5i

Reader.pngIn a scenario where two adjustments are being used for the same factor numeric value, the R42800 may have a rounding difference for the amounts. This KM document explains the scenario for the adjustments. Doc ID 2465375.1. http://ora.cl/jP2TW

You can automatically debit (withdraw funds from) a customer’s bank account by updating an automatic debit file that you send to the bank that collects payment from the customer using Electronic Funds Transfer (EFT). The automatic debit process records the receipt at the time the file is updated. You run a program to format the file according to the bank’s specifications, and then send it to the bank by copying it to a medium or sending it electronically. The bank collects payment from the customer and then notifies you that the transaction is complete. Automatic debits work well in situations in which you invoice predefined amounts every month. You can also use automatic debits with invoice amounts that vary with each billing period. The steps involved in processing automatic debits are as follows:

  1. Create invoices
  2. Create a batch of automatic debits using Create Automatic Debit Batch (R03B571).
  3. Process automatic debits in final mode:
    • Creates Receipt Header (F03B13) and Receipt Detail (F03B14) records.
    • Updated the Automatic Debits Batch Control (F03B571).
  4. Update Automatic Debit Invoice Select & Build table (F03B575).
  5. Format the batch of Automatic Debits
  6. Update the Automatic Debits Standard Formatted Tape table (F03B57OW).
  7. Copy F03B57OW table to media (and send to the bank).
  8. Purge Automatic Debits

  style="margin-top:auto;margin-bottom:auto"

    • Select the customer invoices to be paid.
    • Build and update worktables that are sent to the bank.
    • Update customer invoices as paid.
    • Format automatic debit information to meet country-specific bank requirements.
    • Copy automatic debit information to a medium to send to the bank, or transfer automatic debit information electronically.
    • Purge automatic debit batches.

  style="margin-top:auto;margin-bottom:auto"

    • Auto Debit Invoice Select and Build (F03B575).
    • Auto Debit Standard Formatted Tape File (F03B57OW).

 

Note: Country-specific functionality for processing automatic debits exists for certain countries. For more information relating to EMEA globalizations, please visit the ‘JD Edwards EnterpriseOne Globalization site, Document 752291.1. This site provides details about country specific localizations, translations, announcements about upcoming plans and other helpful information.

 

More details on how this process works, common issues and troubleshooting tips could be found in:

  • How To Set Up, Process and Frequently Asked Questions Automatic Debits In EnterpriseOne Accounts Receivable (R03B571, R03B575) (Doc ID 655040.1)
  • Frequently Asked Questions on Automatic Debits (R03B571) (Doc ID 644179.1)

In the Orchestrator Studio, you can create a Connector Service Request to Call external REST Service.

 

In this blog, we will be using a free REST API for Currency Conversion from https://free.currencyconverterapi.com

 

Sample Input -

--------------------

v6/Convert API takes input as FromCurreny_ToCurency

 

https://free.currencyconverterapi.com/api/v6/convert?q=USD_INR

 

Sample Output -

-----------------------

{

   "query":{

      "count":1

   },

   "results":{

      "USD_INR":{

         "id":"USD_INR",

         "val":70.544948,

         "to":"INR",

         "fr":"USD"

      }

   }

}

 

 

Using Orchestrator Studio, we will be calling v6/convert REST API and pass parameters at the run-time to get the output.

 

Step# 1 - Create Connector

 

Login into Orchestrator Studio and click on Tools option.

 

1.png

 

Click on Connectors -

 

2.png

 

here we need to fine Connection properties for external REST system and save it -

 

Type - External REST

Endpoint - https://free.currencyconverterapi.com/api/v6/convert

3.png

Note - This API doesn't require authorization. if required Authorization can be defined under the Security tab.

Also, if you are using a proxy server then it can be defined under the Proxy tab.

 

4.png

Step#3-  Creating Connector Service.

 

Click on Service Request and select Connector -

 

 

Here define the connector details and select the connection name which we have defined in previous steps.

Also, define the parameter to the REST API.

Example - https://free.currencyconverterapi.com/api/v6/convert?q=USD_PHP here q is the parameter for this API

5.png

 

You can also quickly test this service using the Test button.

 

6.png

 

Test result Output -

7.png

 

Step 3# Creating Orchestration and map input variable.

 

Now, we will map the created Connector Service to Orchestration and map variables.

 

8.png

 

Click on the drop-down and select the previously defined Connector Service.

 

9.png

 

10.png

 

Notice the Variable ${From_To} is displayed as an input to Connector Service Request -

 

11.png

 

Now, define Orchestration Input and map to the variable from Connector Service Request.

 

12.png

 

Testing -

 

Login into Orchestrator Client and select your Orchestration from the drop-down list.

Orchestration input variable will be displayed under INPUTS.

 

Example - Enter the value as usd_inr for converting currency from USA to India.

 

Reference -

 

check https://free.currencyconverterapi.com/ for the available list of countries and currency.

JD Edwards EnterpriseOne Tools Orchestrator Guide

ThisReader.png new KM document explains how to return an array of values from a groovy custom Service Request in an Orchestration so that the next step in the Orchestration can use those values to iterate over. Doc ID 2464581.1. http://ora.cl/p6Z8h

Reader.pngThis new KM document explains a scenario where an 'Action Invalid' error is received in P4600 and why the functionality is different when Auto Location Selections is OFF. Doc ID 2464499.1. http://ora.cl/ZS5rW

Reader.pngCan you could remove error id 495C ('The selected shipment is on a load') to allow adding lines to shipments that are currently assigned to a load? This KM document explains why the error code cannot be removed and provides a better process to achieve adding the lines. Doc ID 2462708.1. http://ora.cl/H4zm2

Grower and Blend operations that use additives, sprays, or consumables now validate the availability of that inventory and process commitments. Because an inventory commitment is created at the time the operation is created, buyers now have visibility into inventory that is running low and users are assured that the inventory and lot is available at the time they are executing the operation. When the operation is closed, inventory is relieved ensuring that on-hand inventory remains accurate.

 

Review Blend and Grower Inventory (Consumables, Additives, Spray Items) Commitment Processing (Doc ID 2368852.1) for additional information regarding this new functionality.

Reader.pngWhen a line type has an inventory interface of "A", this means that it will require the entry of an account number and will validate that account number against the F0901.  No other validations are done. With this inventory interface, any value can be entered in the Item Number field.  The system will accept any entered value since no editing or valuation is done. Note that the second item number (LITM) and third item number (AITM) fields are populated with the exact value entered.  However, the Short Item Number field (ITM) will always be blank for line types with Inventory Interface of "A".

 

This KM document provides an example to illustrate the scenario. Doc ID 2458894.1. http://ora.cl/5SI18

Reader.pngCan you include returnable packaging containers on a sales order as separate line items with a Base Price (P4106) of zero and an Item Cost (P4105) of greater than zero? Yes! This KM document explains the process. Doc ID 2458763.1. http://ora.cl/Ze4Uq

Reader.pngThis new KM document provides the steps with screen prints to assign a customer to a sales person as seen in application Customers Assigned to OB (P42470). Doc ID 2458199.1. http://ora.cl/Pg8lA

Users often set up a non-stock line type in Line Type Constants (P40205). Line Type is a required value for each Purchase Order detail line. Furthermore, it determines how a line is processed through the Purchasing system via Order Activity Rules.  In P40205 for a Non-Stock line, the GL Class is setup in G/L Offset field or in Item Master (P4101) in G/L Class field.

 

Occasionally, in P4310 (Purchase Order Entry), users enter a line for a non-stock item that has a different GL Class code setup in the item master but the value of GL Class code defaults from Non-Stock Line Type setup in (P40205) instead. This can occur when in Line Type Constant user did not select or check Edit Item Master for Non-Stock Item in line type constant. Once the Edit Item Master for Non-Stock Item is checked then G/L Offset value from P4101 will default into purchase order entry instead of Line Type setup.

 

It should be noted that the info above information was taken from Line Types in Procurement (P40205 / Inventory Interface) [Video] (Doc ID 625509.1). This quick reference guide contains a lot of other information that can be helpful with regard to Line Type setup in procurement module. Of special interest is a link to a recording “Where Does The G/L Class Code Default From” in the middle of the document. The video contains detailed information about GL Class code for sales order detail lines as well as purchase order detail lines.

attention.jpgToday, Oracle JD Edwards announces significant customer-driven product updates to empower companies on their journey to becoming digital enterprises. These enhancements provide companies with transformative solutions to innovate in the digital economy and to run their business their way.

JD Edwards EnterpriseOne Tools Release 9.2.3 provides customers with innovation benefiting our EnterpriseOne Applications Releases 9.1 and 9.2, including Notification framework enhancements, new Orchestration capabilities, Extensibility framework enhancements, User Defined Object simplification, 64-bit enablement and updated platform certifications. Doc ID 2464407.1. http://ora.cl/iv15m

Reader.pngStarting with Tools Release 9.2.2.x and Orchestrator 6.0, you can use a variable to "read" line numbers from a form. This new KM document describes, with screen prints, how you can achieve passing the data from multiple lines in a form to another using two service requests with orchestration. Doc ID 2457216.1. http://ora.cl/jO89A

Reader.pngOracle Ravello is an overlay cloud that enables enterprises to run their VMware and KVM applications with data-center-like (Layer 2) networking ‘as-is’ on public cloud without any modifications. With Ravello, enterprises don’t need to convert their VMs or change networking. This empowers the business to rapidly develop and deploy existing data-center applications on the public cloud without the associated infrastructure and migration cost and overhead for a variety of use-cases such as devtest, staging, UAT etc.

Access the whitepaper "JD Edwards EnterpriseOne on Oracle Ravello Cloud Service" attached to this new KM document to learn more. Doc ID 2456235.1. http://ora.cl/R8KK6

Reader.pngThis new KM document is designed to provide the basics for understanding Advanced Pricing in EnterpriseOne. The intent is to show the setup requirements and to provide an example of a sales order advanced pricing adjustment. A brief troubleshooting section is also included. Doc ID 2452815.1. http://ora.cl/gr8lv

Reader.pngJD Edwards EnterpriseOne has provided sample files for processing Z file entries with Lease for the following tables: F1201Z1 Asset Master, F1501BZ1 Lease Master, F1502BZ1 Recurring Billing, F1507Z1 Unit Master, F1511BZ1 Manual Billing, F1512Z1 Bill Codes, F1514Z1 Area Master, and F15017Z1 Lease Detail. http://ora.cl/rj8kN

Reader.pngThis new KM document provides links to information on workflow delegation and tasks reassignments. It describes how workflow administrators and workflow users can reassign action and information tasks to other users. Doc ID 2439369.1. http://ora.cl/7KX8u

Reader.pngThis KM document contains the xml layout mapping for Hungary B2B E-Invoicing. Doc ID 2450411.1. http://ora.cl/9G0Pd

Reader.pngTECHNICAL NOTE 2016_002 V1.50 and NFe XML Tags for Outbound NFe contains updates to Groups LA, N, NA, YA, Y and validation changes as specified in NFe 4.0 Technical Note 1.50. It also contains corrections for direct Export Tags. This new KM document contains the datasheet with the XML layout. Doc ID 2436823.1. http://ora.cl/9VO3v

Filter Blog

By date: By tag:

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see https://community.oracle.com/docs/DOC-1022508 for instructions.