SetLevelError_Line

Set Level Error - Line

Minor Business Rule

Object Name: BLM0103

Parent DLL: CMFGBASE

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
The purpose of this function is to prepare tam specs to write level messages to the F01131 & F01133
ppat files.
This function should be used in conjunction w/ b0100011 which actually does the writing to the above
mentioned files. This function has been modified from traditional BLM functions to allow different
applications to be called from the same action message. This will be used for Product Data Management
Interoperability applications.

1.2Setup Notes and Prerequisites
• The alias for the data dictionary error message is LM0103 - "User &1, Batch &2, Transaction &3, Line
Number &4 contains errors."
• 'b7
1.3Special Logic

2.Technical Specifications

Data Structure

DLM0103 - Set Level Error - Line

Parameter Name Data Item Data Type Req/Opt I/O/Both

szEdiUserId EDUS char OPT 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 OPT 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.

szEdiTransactNumber EDTN char OPT 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.

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.

cIncludeInterconnect EV01 char OPT NONE

An option that specifies the type of processing for an event.

szApplicationName OBNM char OPT 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

szFormName SFMN char OPT NONE

The object name of the search form associated with this data dictionary item.

idGenericLong GENLNG ID OPT NONE

General purpose ID variable.

Related Functions

None

Related Tables

None

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szEdiUserId	EDUS	char	OPT	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	OPT	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.
szEdiTransactNumber	EDTN	char	OPT	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.
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.
cIncludeInterconnect	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
szApplicationName	OBNM	char	OPT	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
szFormName	SFMN	char	OPT	NONE
The object name of the search form associated with this data dictionary item.
idGenericLong	GENLNG	ID	OPT	NONE
General purpose ID variable.