InteroperabilityLaunchVendorUBE

Interoperability, Launch Vendor-Specific UBE

Minor Business Rule

Object Name: B0000178

Parent DLL: COPBASE

Location: Client/Server

Language: C

Purpose

This function is designed to launch the Interoperability Vendor-Specific UBE
specified in the Input Parameter's UBE Name and Version. It will also pass 6
additional parameters to the Vendor-Specific UBE, namely EDI User ID(EDUS), EDI
Batch Number(EDBT), Transaction Number (EDTN), Export Mode Flat File(FFEM), Export
Mode Database(EDEM) and Export Mode API(EAEM). After the Vendor-Specific UBE
returns, it will copy the UBE Error Code parameter from the Vendor-Specific UBE's
report interconnect data structure to the Output Error Code parameter.

Data Structure

D0000178 - Interoperability, Launch Vendor-Specific UBE

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szVendorSpecificUBEName	OBNM	char	NONE	NONE
The name that identifies a system object. J.D. Edwards ERP architecture is object-based. Discrete software objects are the building blocks for all applications, and developers can reuse the objects in multiple applications. The Object Librarian tracks each object. Examples of system objects include: o Batch Applications (such as reports) o Interactive Applications o Business Views o Business Functions o Business Functions Data Structures o Event Rules o Media Object Data Structures
szVersionToCall	VERS	char	NONE	NONE
A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version.
szEdiUserId	EDUS	char	NONE	NONE
The source of the transaction. This can be a user ID, a workstation, the address of an external system, a node on a network, and so on. This field helps identify both the transaction and its point of origin.
szEdiBatchNumber	EDBT	char	NONE	NONE
The number that the transmitter assigns to the batch. During batch processing, the system assigns a new batch number to the PeopleSoft transactions for each control (user) batch number it finds.
szEdiTransactionNumber	EDTN	char	NONE	NONE
The number that an Electronic Data Interchange (EDI) transmitter assigns to a transaction. In a non-EDI environment, you can assign any number that is meaningful to you to identify a transaction within a batch. It can be the same as a J.D. Edwards document number.
cExportModeFlatFile	FFEM	char	NONE	NONE
A code that determines whether the transaction record should be exported to a flat file. Valid codes are: 1 Export transaction record to a flat file. 0 Do not export transaction record to a flat file.
cExportModeDatabase	EDEM	char	NONE	NONE
A code that determines whether the transaction record should be exported to an external database. Valid codes are: 1 Export transaction record to an external database. 0 Do not export transaction record to an external database.
cExportModeAPI	EAEM	char	NONE	NONE
A code that determines whether the system exports the transaction record to an external API. Valid codes are: 1 Export transaction record to an external API 0 Do not export transaction record to an external API
cUBEErrorCode	ERRC	char	NONE	NONE
This error code indicates if any errors occurred during the creation of the Trip Document Detail (F4914) records by the Delivery Document Set Server program (XT4914).
cErrorCode	ERRC	char	NONE	NONE
This error code indicates if any errors occurred during the creation of the Trip Document Detail (F4914) records by the Delivery Document Set Server program (XT4914).
mnEdiLineNumber	EDLN	MATH_NUMERIC	OPT	NONE
This is the line number you assign when originating an EDI transaction. This number can represent an order line number (applicable for any order type), an invoice pay item, a journal entry line number, and so on.

Related Functions

None

Related Tables

None