The name of the version of the report that you want to processįor example: XJDE0001. The system name of the report that you want to processįor example: APS Outbound Processor (R34A400) and APS Inbound Processor (R34A410) for flat files, and the APS SCBM 2.0 Outbound Processor (R34A700) and APS Master Inbound Processor (R34A820) for XML files Table 3-3 RunUBE Command related KM Options Option
If you want to create a password file, set the password related options as shown in Table 3-2. Specify the JDE_DIRECTORY in which the RunUBE command is executed. If this interface launches the RunUBE command, specify the KM options as follows: Set the standard KM options (INSERT, COMMIT, FLOW_CONTROL). In the Flow tab select the IKM JDE Enterprise One Control Append (UBE). The capability to load the Z-Tables, as well as the call of the RunUBE command is provided by the IKM JDE Enterprise One Control Append (UBE).Ĭreate an integration interface with Z-tables as target datastores.Ĭreate joins, filters, and mappings as usual. The RunUBE call should be activated in the IKM only after loading all the required Z-table for populating JDE. Oracle Data Integrator can automatically call the RunUBE command to write to JDE. These interfaces should be sequenced in a package. This interface also uses the IKM JDE Enterprise One Control Append (UBE) with the JDE_RUNUBE option set to Yes. This is typically done in the interface loading the last required Z-table.
These interfaces can use the IKM JDE Enterprise One Control Append (UBE) with the JDE_RUNUBE option set to No.ĭuring the second phase the RunUBE command is launched to integrate the data from these Z-tables into JDE Enterprise One. The integration of data into JDE Enterprise One is performed in two phases:ĭuring the first phase data is integrated into a set of Z-tables using several interfaces, without calling the RunUBE command. JDE_CONTROL_TABLES: Specify the Control Tables schemaĪfter performing a reverse-engineering using the RKM JDE Enterprise One, you can use JDE Z-tables as a target of an interface to load data from any system to the JDE application with the IKM JDE Enterprise One Control Append (UBE). JDE_OBJECT_LIBRARIAN: Specify the Oracle Schema or Microsoft SQL Server Database storing the JDE Object librarian JDE_DATA_DICTIONARY: Specify the Oracle Schema or Microsoft SQL Server Database storing the JDE data dictionary JDE_CENTRAL_OBJECTS: Specify the Oracle Schema or Microsoft SQL Server Database storing the JDE Central objects In this chapter, refers to the technology containing the JDE data. In the Reverse tab of the Model, select the RKM JDE Enterprise One. This section details only the fields specific to JDE tables: To perform a Customized Reverse-Engineering of JDE tables with the JDE RKMs, use the usual procedure, as described in " Reverse-engineering a Model" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator. These RKMs retrieve metadata from JDE objects such as tables and interface tables. TORG 13 – Transfer Item Note (inventory between two business units within the same company).The JDE RKMs are able to reverse-engineer JDE tables.Appling the calculated currency rate to primary documents package for all kinds of sales.Auto calculation of average currency rate for shipment based aliened advances.
Auto payments for suppliers based requests for paymentsĪdvances from Customers in foreign currency.The primary document creation and sending for client-bank.The Bank statement uploading according to legislation of the Russian Federation.Calculation of unrealized and realized currency gain and losses based RAS rules for AP and AR in foreign currency.Recalculation act for Suppliers or Customers.from Service module for sold services and spare partsĪP an AR reconciliation based on RAS rules.from for finance transactions into the Accounts Receivable module.Correction VAT invoice for returns and customer claims.The primary document package for sales contents following documents: