import bulk tasks from daylite to billings pro

Hz_imp_batch_summary_v2pub.create_import_batch(NULL,'&batchname','&batchdescription', Use the create batch procedure from the Create Import Batch API to guarantee that a unique batch ID is assigned.Ĭall the following script to create a batch ID: Set serveroutput on Batch IDsĮach import batch must have a batch ID. Note: When the request set is running, you also cannot run the Import Batch to TCA Registry program to transfer any batch from the interface tables into the TCA Registry. The request set uses direct inserts into the interface tables, which requires table-level locks. However, if a D&B import batch is being loaded into the interface tables, using the D&B Import Adapter request set, the tables are locked and all other batches must wait until the D&B batch is completed. The interface tables can store as many batches from different sources as needed, and any number of batches can be actively populating the interface tables at the same time. The data in one batch must be from the same data source. See: File Loads Overview, Oracle Customers Online User Guide.Ī set of data to be loaded into the TCA Registry at one time is called a batch. See: D&B Import Adapter and Batch Loading.įile Load: Use Oracle Customers Online (OCO) or Oracle Customer Data Librarian (CDL) to load data from a comma-separated value (CSV) file, or file delimited by another allowed character, into the interface tables. See: Bulk Import Interface Tables, Oracle Trading Community Architecture Reference Guide.ĭ&B Load: Use the standard D&B bulk file that you receive from D&B and run the D&B Import Adapter request set to automatically map and load the D&B information into the interface tables. SQL/ETL Load: Create scripts or use tools to extract the source information, transform the values to meet the data requirements of the interface tables, and populate the interface tables with large volumes of information. You should have a strong knowledge of the data and data structure to be imported. Using Oracle Trading Community Architecture Loading Data into the Interface Tables Run the TCA Import Error report to view errors, and reload the corrected data. Optionally run the Import Batch De-Duplication report to view results of batch de-duplication. Run the Import Batch to TCA Registry program to import a batch into the TCA Registry. See: Loading Data into the Interface Tables. See: Setting Up Bulk Import, Oracle Trading Community Architecture Administration Guide. Your administrator can set up for Bulk Import. See: Party Merge Overview or De-Duplication Overview, Oracle Customer Data Librarian User Guide. As a result, if duplicates are created, use Party Merge or Oracle Customer Data Librarian to resolve them. In particular, if the process does not find an existing account site or account contact point, it creates a new account site or contact point, as well as the associated party site or contact point, even if the party level versions already exist. Note: Customer Interface runs independently and does not regard party information already loaded in the TCA Registry. To import both party and account information, use Customer Interface. The import is only for information on the party level.

TCA provides validations and optional de-duplication to ensure the quality of the imported information. Use Oracle Trading Community Architecture (TCA) Bulk Import to load data from legacy or other external systems in bulk into the TCA Registry. This chapter covers the following topics: This chapter describes using Bulk Import to load data from legacy or other external systems into the TCA Registry.

Import bulk tasks from daylite to billings pro