Oracle by Example brandingClassify Suppliers as Chile Risky Tax Payers

section 0Before You Begin

This 30-minute tutorial shows you how to classify the suppliers as Chile Risky Tax Payers.

Background

The regulations in Chile indicate that there is now a classification of Retaining Taxpayers and Risky Taxpayers. When a Retainer taxpayer makes a purchase from a Risky Taxpayer, the regulation requires the one who makes the purchase (Customer) to issue a purchase invoice that ensures the associated Tax in the mentioned invoice will be 100% withheld. JD Edwards currently does not have the functionality to generate legal documents like the purchase invoice from the purchasing module. When the Servicio de Impuestos Internos Tax authority declares the list of suppliers as risky taxpayers, JD Edwards needs to tag all the suppliers in the list as risky taxpayers.

What Do You Need?

You also need the following minimum technical requirements to import customer data to the JD Edwards EnterpriseOne system using an orchestration.

  • Orchestrator Studio 7.0.0.0
  • EnterpriseOne 9.2 with tools release 9.2.3.3

section 1Creating an FTP server (Windows 10)

Following are the instructions to setup an FTP server in Windows 10:

1. Installing an FTP server on Windows 10

  1. Open the Control Panel and navigate to the Programs and Features section.
  2. On the left pane, select Turn Windows Features On or Off option to get a list of folders.
  3. Expand the Internet Information Services folder and select FTP server. Expand the FTP server; select FTP extensibility and FTP Service options.
  4. Select the Web Management Tools folder and retain the default settings.
  5. Click OK to start the installation.
  6. Click Close once the installation is complete.

2. Configuring an FTP server on Windows 10

  1. Open the Control Panel and navigate to Administrative Tools.
  2. Select and open Internet Information Services (IIS) Manager.
  3. Navigate to Connections panel, expand the host machine and right click on Sites, select Add FTP Site.
  4. Give a name to the FTP site and enter the Physical Path of the FTP folder that you want to use to send and receive files. Alternatively, you can create a new folder to store your FTP files.
  5. Click Next.
  6. In this screen, change SSL settings to No SSL and retain the other default settings.
  7. If you are configuring a business site, make sure to choose Require SSL option, as it will add an extra layer of security to the transfer.
  8. Click Next and you will get the authentication screen.
  9. Navigate to the authentication section of this screen and select the Basic option.
  10. In the authorization section, select Specified Users from the drop-down menu.
  11. In the following field, enter the User Name of your Windows 10 account to give you access to the FTP server. You can also add multiple users. Ensure that your User Name is added as an administrator to the Windows 10 system.
  12. In the permission section, select both Read and Write boxes.
  13. Click Finish.

In addition to the above steps, you need to perform the following tasks to send and receive files using the FTP server:

  • Create a CSV file that contains Tax ID as one of the columns.
  • Create supplier records in Address Book Master and Supplier Master with the same Tax ID, which is present in the CSV file.

    Note: Turn on CHILE localization while creating supplier record. The data is stored in the Address Book Tag File CHI 01 (F76H101T) table.

  • Upload the CSV file in the physical path of the FTP server.

section 2Creating a Soft Coding Record for an FTP or SFTP Server Connection

Create a soft coding record for a connection to a server that supports FTP or SFTP. This enables a business administrator to create connector service requests for transferring files to an FTP or SFTP server

  1. On the Orchestrator Studio Home page, click the Connections icon icon.
  2. On the Connections page, click New and select FTP from the drop-down list.
  3. On Connection Information, complete these fields:
    • Name: Enter a unique name for the connection.
    • Description: Enter a description to identify the connection. For example, if you are creating more than one soft coding record to connect to different locations, include the location in the description.
    • Type: Select FTP File Transfer.
    • User/Role: Enter the user authorized to run the originating orchestration – the orchestration on the local system uses the FTP connection. The user can be an EnterpriseOne user, role, or *PUBLIC.
    • Environment: Enter the environment where the local orchestrations reside.
  4. In the FTP Connection Details section, complete the following fields:
    • FTP Host: Enter the URL of the FTP server.
    • FTP Port: Enter the port number of the FTP host server.
    • Connection Type: (Orchestrator Studio 7.2.0.0) Choose the connection type. Valid values are Anonymous, Username/Password, and SSH Key.
    • User: Enter the user authorized to access the directory on the FTP server.
    • Password: Enter the password of the user authorized to access the directory on the FTP server.
    • Use Secure FTP (SFTP): Enable this toggle if the server uses secure FTP.
    • FTP File Path: Enter the path to the directory on the FTP server where you want the file transferred.
  5. Click Save icon icon.

section 3Creating FTP Connector Using Service Request

Use an FTP connector to retrieve data from a CSV file on an FTP server. The data is imported as an array, which gives you the option to map the data set in the array to a subsequent orchestration step.

  1. On the Orchestrator Studio Home page, click the Connectors icon icon.
  2. On the Connections page, click New and select FTP from the drop-down list.
  3. Complete the following fields:
    • Name = Chile Connector Request
    • Description = Connector Request for Chile Risky Tax Payer Orchestration
  4. Click the Product Code drop-down list and select 55 for a customer product code.
  5. On the FTP Field, select the connection that was created.
  6. Select the File option.
  7. Click the Type drop-down list and select Receive.
  8. Click the Import CSV as Array check box. The Orchestrator Studio displays additional fields to configure the importing of data from a CSV file.
  9. If the CSV file has a header row, click the CSV Has Headers check box to exclude the header row. This ensures that at runtime, the Orchestrator will not import the column headers as data in the array.
  10. Complete the following fields:
    • Delimiter: Enter the delimiter used in the CSV file to separate values.
    • Source File Name: Enter the name of the CSV file
    • Path Extension: Enter the name of the sub-directory on the third-party FTP server that contains the CSV file. The FTP connection already contains information for the base folder.
    • Data Set Variable Name: Enter a name for the data set or array in which the data from the CSV file will be imported. Later, you can reference this data set variable name to map data in the data set to a subsequent orchestration step.
  11. Enable or disable the Remove File toggle. By default this is enabled and removes the file from the temporary location on the AIS Server after the data is imported.
  12. In the Model CSV File section, select a model CSV file to define the columns in the CSV file that you want to import.

    The model CSV file should be a copy of the CSV file from which the FTP connector will import data, or you can use a different CSV file as long as it has the same column names.

    • Click Browse to select a file and click Ok.

      • If the CSV Has Headers check box is selected, the grid displays the column names from the model CSV file in Member Name and Variable Name columns. Otherwise, the grid displays column 1, column 2, and so on.

    • In the grid, you can change the member names or variable names, and you can use the X button at the end of the rows to remove any columns from the import.

      • The variable names represent the values imported into the array. If you map these values to a subsequent orchestration step, select these variable names for the mappings.

      Caution:

      When importing the CSV data into an array, the order of the columns is considered and not the names of the columns. If the CSV has 10 columns and you have specified only eight in the grid, the array will contain the first eight columns from the CSV. If column headers are present, the third column in the CSV file is mapped to the third row of the table, regardless of the column and member names match.

      Your connector service request should look like this. This is applicable if your CSV file contains Tax ID as first column.

      Description of image_1.png follows
      Connector Service Request
  13. Click Save icon icon.

section 4Create a Form Request in Orchestration

Following are the instructions to create a form service request:

  1. On the Orchestrator Studio Home page, click the Form Requests icon icon.
  2. On the Form Requests page, click New.
  3. Complete the following fields:
    • Name = Chile Form Request
    • Description = Form Request for Chile Risky Tax Payer Orchestration
  4. Click the Product Code drop-down list and select 55 for a customer product code.
  5. In the Add Form option, click First as shown in the following screen:
    Description of image_1.1.png follows
    Form Request Step
  6. In the pop up window, enter the Application, Form, and Version details. Click Save and Load and enable Application Stack from the Form Request Options.

    The required values are as follows:

    • Application: P01012
    • Form: W01012B – Work With Addresses
    • Version: ZJDE0001
  7. In the Work with Address-QBE form, under Available Actions, choose Tax ID and click Add icon icon to add the Tax ID to the Order of Execution. Enter a variable name in the mapped variable field.
  8. Select Find under Buttons and Exits; click Add icon icon to add the action to the Order of Execution.
  9. In the Work with Addresses – Grid, under Available Actions, choose Select Row and click Add icon icon to add the action to the Order of Execution. Enter 1 in the default value to select the first row from the grid.
  10. Select Regional Info under Buttons and Exits, click Add icon icon to add the action to the order of execution.

    Your form request should look like this.

    11. Description of image_2.png follows
    Form Request
  11. To add the next application, click After as shown in the following screen:
    Description of image_2.1.png follows
    Addition of Next Application Step
  12. In the pop up window, enter the Application, Form, and Version details. Click Save and Load.

    The required values are as follows:

    • Application: P76H101
    • Form: W76H101B – A/B Regional Information Revision
    • Version: ZJDE0001
  13. Choose Category Code 01 and click Add icon icon to add the action to the Order of Execution and enter 1 in the default value column of the Order of Execution.
  14. Select OK under Buttons and Exits and click Add icon icon to add the action to the Order of Execution.

    The form request created after adding P76H101 should look like this.

    15. Description of image_3.png follows
    Form Request After Adding P76H101
  15. Click Save icon icon.

section 5Create an Orchestration

  1. On the Orchestrator Studio Home page, click the Orchestrations icon icon.
  2. On the Orchestrations page, click New.
  3. Complete the following fields:
    • Name: Chile Risky Tax Payer Orchestration
    • Description: Orchestration to set Suppliers as Risky Tax Payer
  4. Click the Product Code drop-down list and select 55 for a customer product code.
  5. Click the Add icon icon present in between Start and End as shown in the following screen:
    6. Description of image_4.png follows
    Add Icon Between Start and End
  6. Choose Connector from the options and select the Chile Connector Request.
  7. Click the Add icon icon to add a new step. Choose Form Request from the options and select Chile Form Request.
  8. Click the Chile Form Request and select the Transformations icon icon from the options.
  9. In the Transformations pop-up window, select Data Set Variable Name (risky_task_payer_data) from the Iterate Over drop-down list. Data Set Variable Name is already set in the Connector Service Request.
  10. In the Transformation grid, use the Available Values drop-down list to map the orchestration inputs to the form request (service request) inputs.

    The Input Mapping screen should look like this.

    Description of image_5.png follows
    Input Mapping Screen

    The Orchestration screen should look like this.

    Description of image_6.png follows
    Orchestration Screen
  11. Click Save icon icon.

section 6Test the Orchestration in Orchestration Client

  1. To run the orchestration, select Run Orchestrations in the Orchestrator Studio Home page as highlighted in the following screen.
    2. Description of image_8.png follows
    Orchestrator Studio Home Page
  2. Select the Orchestration you have created in the last section from the list.
  3. Select Refresh Cache.
  4. Click Run to execute the Orchestration.

    The output screen should look like this.

    Description of image_8.png follows
    Output Screen