Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for Oracle E-Business Suite
  3. PowerExchange for Oracle E-Business Suite Configuration
  4. Oracle E-Business Suite Sources and Targets
  5. Application Source Qualifier Transformation
  6. Oracle E-Business Suite Mappings
  7. Oracle E-Business Suite Sessions
  8. Datatype Reference
  9. Error Messages
  10. Glossary

PowerExchange for Oracle E-Business Suite User Guide for PowerCenter

PowerExchange for Oracle E-Business Suite User Guide for PowerCenter

Using a Stored Procedure to Generate a Batch Identifier

Using a Stored Procedure to Generate a Batch Identifier

When Oracle E-Business Suite provides stored procedures for the open interface, use the stored procedure to generate a batch identifier. When Oracle E-Business Suite does not provide a stored procedure, you can create a stored procedure in Oracle and import it as a Stored Procedure transformation.
The following figure shows an example of a mapping that uses a stored procedure to generate a batch identifier:
The mapping contains the following objects:
  • Create_Batch_param. Flat file source that contains stored procedure parameters that need to pass to the stored procedure.
  • hz_imp_batch_summary. Stored Procedure transformation associated with an Oracle stored procedure. It takes the input from SQ_Create_Batch_param and generates the batch identifier.
  • hz_imp_batch_summary_Activate. Stored procedure transformation that activates the batch identifier and returns the status of the batch identifier. The stored procedure output is passed to the flat file target, BasicFlatFileTarget.
  • IMP_BATCH_TCA_REG_PARAM and HZ_IMP_CLASSIFICS_INT_SOURCE. Source definitions that contain data to write to the target.
  • Param_Joiner. Joiner transformation that joins the data from the source qualifier, SQ_IMP_BATCH_TCA_REG_PARAM, and the Stored Procedure transformation, hz_imp_batch_summary. The Joiner transformation has manually created ports, “master” and “detail,” and uses the following join condition:
    master port_name = detail port_name
  • Joiner_Data. Joiner transformation that joins the data from the source qualifier, SQ_HZ_IMP_CLASSIFIED, and the Stored Procedure transformation, hz_imp_batch_summary. The Joiner transformation has manually created ports, “master” and “detail,” and uses the following join condition:
    master port_name = detail port_name
  • BasicFlatFileTarget. Flat file target that stores output from the stored procedure.
  • Import_Batch_to_TCA_Register. Oracle E-Business Suite open interface that you want to write data to.
The manually created ports, “master” and “detail,” allow you to join sources that do not have matching columns.

0 COMMENTS

We’d like to hear from you!