Jde table list

Jde table list DEFAULT

Data Tables in JDE

AR tables:-

Table
Description
Fld Prefix

F03B01
Customer Master by Co Table
A5

F03B08
Credit/Collection Date Pattern
RD

F03B11
Customer Ledger
RP

F03B112
Invoice Revisions
RW

F03B112P
Invoice Revisions Purge File
RW

F03B11P
Customer Ledger Purge File
RP

F03B11Z1
Invoice Transactions – Batch File
VJ

F03B11Z2
F03B11 Interoperability Table
SY

F03B13
Receipts Header File
RY

F03B13P
Receipts Header Purge File
RY

F03B13Z1
Electronic Receipts Input
RU

F03B13Z2
F03B13 Interoperability Table
SY

F03B14
A/R Check Detail File
RZ

F03B14P
Receipts Detail Purge File
RZ

F03B14Z2
F03B14 Interoperability Table
SZ

F03B15
Credit and Cash Management
RT

F03B16
A/R Statistical History
RV

F03B16S
A/R Statistical Summary
RS

F03B20
A/R Notification History
ZR

F03B21
A/R Notification History Detail
ZS

F03B22
A/R Fee Journal History
RS

F03B23
A/R Fee Journal History Detail
RT

F03B25
A/R Delinquency Policy Table
RF

F03B26
A/R Delinquency Policy Notification
RL

F03B27
A/R Delinquency Policy Detail – Fees
RM

F03B28
Letter Text Table
RJ

F03B29
Credit Insurance Table
IP

F03B30
Activity Type Master
ZI

F03B31
Customer Activity Log
ZG

F03B40
A/R Deduction Management
RB

F03B41
A/R Deduction Activity
RC

F03B41Z1
Inteoperability – Deductions Management
SZ

F03B42
Deductions Activity Master
RD

F03B465
A/R Netting Workfile
RO

F03B50
Receipt Application Algorithm Execution Lists
RE

F03B571
Auto Debit Batch Control
RC

F03B575
Auto Debit Invoice Select and Build
RD

F03B57OW
Auto Debit Standard Formatted Tape File
RE

F03B672
Draft Remittance Work File – One World Only
RD

F03B67OW
Drafts Standard Formatted Tape File
RE

F03B920
Credit Reporting Tape – TRW
ZC

F03B920C
Create Credit Reporting Tape – Creditel
ZD

F03BUI04
Work File for Integrity by Offset Account
W3

F03BUI05
Auto Receipts Batch Workfile
R5

AP Tables

Table
Description
Fld Prefix

F0401
Supplier Master
A6

F0401M
Multiple Vendor Bank Account Status
A6

F0401Z1
Supplier Master – Batch File
VO

F0411
Accounts Payable Ledger
RP

F0411A
WF – “As Of” Accounts Payable Ledger
RP

F0411P
Purge – Accounts Payable Ledger
RP

F0411Z1
Voucher Transactions – Batch File
VL

F0411Z3
F0411 Interoperability Table
SZ

F0413
Accounts Payable – Matching Document
RM

F0413A
WF – “As Of” Accounts Payable Payment Register
RM

F0413P
Purge – Accounts Payable Matching Documents
RM

F0413Z1
F0413 Interoperability Table
SY

F0414
Accounts Payable Matching Document Detail
RN

F0414A
WF – “As Of” Accounts Payable Payment Detail
RN

F0414P
Purge – Accounts Payable Matching Document Detail
RN

F0414Z1
F0414 Interoperability Table
SZ

F0415
A/P Payments – Check Sequencing
KJ

F0417
A/P Payments – Default Print and Update
KB

F0417M
Multiple Vendor Bank Account Types
KB

F04257W2
Payments Window Workfile
KE

F0450
Payee Control File
PC

F04514
WF – 1099 Combined Workfile (Merge of F045141 and F045143)
G1

F045141
WF – 1099 G/L Workfile
G1

F045143
WF – 1099 A/P WorkFile
G1

F04515OW
1099 Magnetic Media Tape File – OneWorld
G1

F0457
A/P Payment Tape File
KM

F04571
A/P Payment Processing – Header File
KH

F04572
A/P Payment Processing – Summary File
KK

F04572OW
A/P Payment Tape File – OneWorld
KN

F04572TO
A/P Tape Work File – OneWorld
KN

F04573
A/P Payment Processing – Detail File
KI

F0474N1
A/P Enterprise Info. – Sweden BGI/BGU
QB

F0474N2
A/P Enterprise Info. – Norway DNB
QD

F0474N3
Supplier Inf. Foreigen Payments Sweden
QC

F0490
A/P ‘As Of’ Date Workfile
GC

F04UI004
Integrity Report Table F04UI004
RP

F04UI006
1099 Workfiles User Index
G1

GL

Table
Description
Fld Prefix

F0901
Account Master
GM

F0901D
Account Master – Alternate Description
LK

F0901T
Account Master Tag File
GM

F0901WO
Account Master Search Word Occurrence
WO

F0901WS
Account – Word Search
WS

F0902
Account Balances
GB

F0902B
Account Balances – 52 Period Accounting
GB

F0902P
Purge – Account Balances
GB

F0902Z1
Account Balances – Batch File
GB

F0902Z2
Account Balances – PC Budget Upload File
GB

F0907
Chart of Accounts Format
GY

F0909
Chart of Accounts – Reference File
AC

F0911
Account Ledger
GL

F0911P
Purge – Account Ledger
GL

F0911R
WF – Acct Ledger File for Reconciliation
GL

F0911R1
Account Reconciliations Header – OneWorld ONLY
GL

F0911T
Account Ledger Tag File
GL

F0911Z1
Journal Entry Transactions – Batch File
VN

F0911Z1T
Journal Entry Transactions – Batch Tag File
VN

F0911Z3
Account Detail – Journal Entry Upload File
SR

F0911Z4
F0911 Interoperability Table
SZ

F0912
Cost Allocations/Flex Budgeting
RJ

F0912A
Index Computation Entry File
RI

F0912B
Variable Allocation File
R#

F0916
Bank Statement Header
GH

F0917
Bank Statement Detail
GD

F0917S
Bank Statement Detail Extension
GD

F09218
Online Consolidations Set-up File
LS

F092181
Online Consolidation Detail File
LR

F09505
WF – Bank File of Cleared Checks.
GN

F095051
Bank File OF Cleared Checks – Flat File OneWorldONLY
GN

F09UI004
Variable Numerator Allocations work file
R#

F09UI005
Tax Offsets User Index
GL

F09UI006
Tax (F0018) Replica
TD

F09UI007
Match Bank Tape to Recon File – ONE WORLD ONLY
GL

F09UI008
Global Business Unit Change
GM

F09UI009
Trial Balance Generic Work File – OneWorld ONLY
GB

F09UI010
WorkFile for R097011
WF

F09UI011
Receipt Prepost Work File
GL

F09UI013
Company by Batch Out of Balance
GL

F09UI014
Annual Close Work Table
GB

F09UI015
Indexed Computations Multi-Tiered Entries
GL

Best Rgds,
Francis Chin
mobile :- +65 9819 8907
email:[email protected]
_____
From: Jayashis via jdedwards-l [mailto:[email protected]]
Sent: Friday, 25 December 2009 5:26 PM
To: Francis Chin
Subject: [jdedwards-l] Data Tables in JDE

Posted by Jayashis (ERP knowledge
with domain expertise in Retail Jewellery Industry)
on Dec 25 at 7:22 AM

Can anybody please provide me a list of data tables used in Accounts
Receivale, Accounts Payable and General Ledger module of JDE E1 8.12. I need
to map those with a legacy application.
Thanks in advance.

Sours: https://www.toolbox.com/tech/enterprise-software/question/data-tables-in-jde-122509/

JD Edwards EnterpriseOne Tools

Table Design Guide

Release 9.1

E21486-01

December 2011

The JD Edwards EnterpriseOne Tools Table Design Guide contains the following topics:

Designing Tables

This section contains the following topics:

Understanding JD Edwards EnterpriseOne Table Design Aid

The Oracle's JD Edwards EnterpriseOne system uses a relational database. Tables are related using common key fields.

Database tables store the data that is used by applications in columns and rows. Each column is a data item, and each row is a record. You can create custom tables for use in JD Edwards EnterpriseOne applications.

You create tables by selecting data items from the data dictionary and assigning key fields as indices. An index enables a database management system to sort and locate records quickly. You must define a table so that the JD Edwards EnterpriseOne software recognizes that the table exists.

Use JD Edwards EnterpriseOne Table Design Aid to generate the table whenever you:

  • Create new tables.

  • Add or delete data items.

  • Add or modify an index.

Understanding Table Creation

When an existing or custom application requires that you create tables for the JD Edwards EnterpriseOne database, use JD Edwards EnterpriseOne Table Design Aid to create the custom tables. You can access JD Edwards EnterpriseOne Table Design Aid from the Oracle's JD Edwards EnterpriseOne Object Management Workbench.

To create tables:

  1. Create a table object.

    Use the recommended naming conventions when creating table objects.

  2. Design the table.

    Add data dictionary items as table columns and create indices. Include audit fields in the table.

  3. Generate the table.

  4. Add data to the table.

Creating Tables

This section discusses how to:

  • Create audit trail information.

  • Name tables.

  • Use index guidelines.

Creating Audit Trail Information

Before you add a new table to the JD Edwards EnterpriseOne system, determine whether an existing table contains the data items required. If an appropriate table does not exist, you must create a new table.

When you add a new table, you should include these audit trail columns:

  • User ID (USER)

  • Program ID (PID)

  • Machine Key (MKEY)

  • Date - Updated (UPMJ)

  • Time - Last Updated (UPMT)

Naming Tables

Use these naming conventions when adding tables:

The name of a table can be a maximum of eight characters and should be formatted as Fxxxxyyy, where:

F = Data table.

xx (second and third digits) = the system code, such as:

  • 00 - Foundation

  • 01 - Address Book

  • 03 - Accounts Receivable

xx (fourth and fifth digits) = the group type, such as:

  • 01 - Master

  • 02 - Balance

  • 1X - Transaction

yyy (sixth through eighth digits) = object version, such as programs that perform similar functions but vary distinctly in specific processing.

LA through LZ = Logical file.

JA through JZ = Table join.

Columns must include a two-character prefix that is used to uniquely identify the table columns. The first character must be alphabetic, while the second character can be alphanumeric. You cannot assign special characters to table columns: for example, $, #, or @. The data item alias follows the two-character column prefix. Typically, the column prefix indicates the type of data included in the table; for example, the prefix of the columns in the Address Book Master (F0101) table begin with AB.

A table description can be no more than 60 characters. Ensure that the table description is the topic of the table. If the table description comes from IBM i, it should be the same name as the file that it represents, such as F0101 (Address Book Master) and F4101 (Item Master).

Using Index Guidelines

If an index includes only one field, use the field name as the index name: for example, Address Number.

If an index includes two fields, list them consecutively: for example, Address Number, Line Number ID.

If an index includes more than two fields, and the first two fields are the same as the first two fields of another index, list the first two fields and follow them by an alpha character: for example, Address Number, Line Number, A. Place a comma and space between each index field and between the last index field and the alpha character. Do not include more than 10 fields in an index.

The total length of the index name cannot exceed 19 characters. If you exceed 19 characters, the compiler displays a warning. This situation affects fetches that use the wrong index ID in business functions.

Working with JD Edwards EnterpriseOne Table Design Aid

This section discusses how to:

  • Use Table Design Aid forms.

  • Select data items.

  • Define indices.

  • Review table information.

Using Table Design Aid Forms

JD Edwards EnterpriseOne Table Design Aid presents these forms within a single window:

  • Columns

    Displays the data items that you select to include in the table.

  • Data Dictionary Browser

    Provides a search method to locate the data items required for the table.

  • Indices

    Provides a method to define unique data items for quick sorting and updating of the table.

  • Object Properties

    Displays data item attributes for a data item that is selected in the Columns form.

Selecting Data Items

Use data items to create table columns. Table columns store information used by applications. Data items must exist in the data dictionary before you can use them in a table. In JD Edwards EnterpriseOne Table Design Aid, you can locate data items using the query by example (QBE) line of the Data Dictionary Browser. To select data items, you can double-click them or drag them to the Columns form. All selected data items appear on the Columns form. Tables can contain data items from multiple system codes.

When you modify or delete data items, you must regenerate the table. Changes that you make to a table can affect business views and forms that reference that table.

Use the Generate Table feature to generate a newly modified table. Generating an existing table clears all data from the table.

Important:

If you delete a table or delete columns from a table, then business views that reference that table, or the deleted table columns, are invalid. The system displays error messages when you generate the application.

Defining Indices

Indices are used to locate specific records and to sort records faster. Table indices are like tabs in a card file. Each index is made up of one or more keys, which are individual data items. Use indices to access data in a simple manner, rather than to read the data sequentially.

Tables can have multiple indices, but every table must have only one primary index. The primary index is the one unique identifier for each record in the table. Additionally, you can use the primary index to build business views. The system does not allow you to save a table without defining a primary index.

When you modify or delete indices, you must regenerate the table. Changes that you make to a table can affect business views and forms that reference that table.

Table InformationDescription
DescriptionThe description of each data item included in the table.
TypeThe field type of each data item included in the table.
LenThe field length of each data item included in the table.
AliasThe alias of each data item included in the table.
Data ItemThe name of each data item included in the table.
Table Column PrefixThe prefix of the table columns.
IndicesInformation regarding all of the indices included in the table.

Reviewing Table Information

You can use JD Edwards EnterpriseOne Table Design Aid to review information regarding a table. You can review the table information online or send it to a printer. This table describes the table information:

Working with Tables

This section discusses how to:

  • Generate tables.

  • Generate indices.

  • Generate header files.

  • Copy tables.

  • Remove tables.

Generating Tables

You must generate tables to create the physical table in the database. Tables are created in the database based on the specifications that you defined. After the table is generated, you can add data to the table. Table generation also creates an .h file, or header file, that is used in business functions and table event rules.

JD Edwards EnterpriseOne Object Management Workbench provides a central location from which you can manage tables.

After you have selected data items for a table and assigned indices, you can configure the table for a specific data source. JD Edwards EnterpriseOne Object Management Workbench employs the Oracle's JD Edwards EnterpriseOne Object Configuration Manager (P986110) application to configure tables. You can configure the table within any existing data source. If you do not indicate a data source, the software automatically configures the table according to the default data source mapping. You can change the path code to generate tables in a different location. Doing so causes the system to perform a drop statement, similar to the remove table, after which the system recreates the table.

After you modify a table, you must regenerate it. If you regenerate an existing table, the table data is lost. To ensure that data is not lost, you must export the data, generate the table, and then copy the data back into the generated table.

Generating Indices

You must regenerate indices each time that you modify existing indices or create additional indices. Doing so modifies the .h file. When you regenerate indices, you do not lose existing data as you do when you regenerate the entire table.

Generating Header FIles

Header files, or .h files, are used in business functions and table event rules. Occasionally, you might run across a table that does not include a header file. You can generate header files without having to generate the entire table.

Header files are located in the Include folder in the path code in which the file was generated (for example, E812\DV812\Include).

Copying Tables

Use the Copy Table feature to copy tables from one data source to another. However, doing so does not copy the table specifications. You can also use Table Conversion to copy tables from one data source to another.

Removing Tables

You cannot physically delete a table using JD Edwards EnterpriseOne Table Design Aid. If you delete a table from JD Edwards EnterpriseOne Table Design Aid, the system deletes only the specifications; it does not delete the physical table.

To completely remove a table from the system, you must use the Remove Table From Database feature.

Viewing the Data in Tables

You can view data in tables using:

  • Oracle's JD Edwards EnterpriseOne Data Browser on the web client.

  • Oracle's JD Edwards EnterpriseOne Universal Table Browser (UTB) on the Microsoft Windows client.

Both tools enable you to verify the existence of data in tables, as well as determine the structure of the table. You can use both tools to view data in all JD Edwards EnterpriseOne supported databases, independent of the type of database that you use.

UTB is an executable application that is part of the JD Edwards EnterpriseOne Microsoft Windows client install. You cannot use JD Edwards EnterpriseOne security to control user permissions for UTB. However, you can apply form security to the Table and Data Source Selection form (W98TAMC). This action secures UTB because the executable cannot function without this form. All column and row security that you set up through the Oracle's JD Edwards EnterpriseOne application applies to UTB.

JD Edwards EnterpriseOne Data Browser is part of the Oracle's JD Edwards EnterpriseOne web client product. You can set up security for the JD Edwards EnterpriseOne Data Browser using JD Edwards EnterpriseOne Security Workbench.

Designing Custom Tables

This section discusses how to:

  • Add table objects.

  • Modify table objects.

  • Select data items for tables.

  • Define indices.

  • Preview tables.

  • Generate tables.

  • Generate indices.

  • Generate header files.

  • Copy tables.

  • Remove tables.

  • View the data in tables.

Forms Used to Create Tables

Form NameFormIDNavigationUsage
Object Management WorkbenchW98220AEnterpriseOne Life Cycle Tools, Application Development (GH902), Object Management, Object Management WorkbenchSelect and view objects in projects and access the JD Edwards EnterpriseOne design tools.
Add EnterpriseOne Object to the ProjectW98220CClick the Objects node of a project and click Add on the Object Management Workbench form.Add new objects to a project.
Add ObjectW9861AFSelect Table and click OK on the Add EnterpriseOne Object to the Project form.Enter the table name, description, product code, product system code, object use, and column prefix.
Table Design AidW9860ALComplete the object information and click OK on the Add Object form.Access Table Design Aid, generate header files, generate tables, generate indexes, remove tables from the database, and copy tables.
Generate TableW9866ESelect the Table Operations tab, and click Generate Table on the Table Design form.Generate tables.
Generate IndexesW9866JSelect the Table Operations tab, and click Generate Indexes on the Table Design form.Generate indices.
Copy TableW9866MSelect the Table Operations tab, and click Copy Table on the Table Design form.Copy tables.
Remove TableW9866DSelect the Table Operations tab, and click Remove Table from Database on the Table Design form.Remove tables.
Universal Table BrowserNAEnterpriseOne Life Cycle Tools, Application Development Tools (GH902), Object ManagementView the data in tables.

Adding Table Objects

Access the Add Object form.

Object Name

Enter a unique name for the new table. Use the recommended naming convention for naming JD Edwards EnterpriseOne objects.

Description

Enter a meaningful description of the table.

Product Code

Select a user-defined code (UDC) (98/SY). Use one of the values from the range of values reserved for clients: 55–59.

Product System Code

Select a UDC (98/SY) that represents the JD Edwards EnterpriseOne system where the data is used. This value is used for reporting and jargon purposes. Example values include:

01: Oracle's JD Edwards EnterpriseOne Address Book

03B: Oracle's JD Edwards EnterpriseOne Accounts Receivable

04: Oracle's JD Edwards EnterpriseOne Accounts Payable

09: Oracle's JD Edwards EnterpriseOne General Accounting

11: Oracle's JD Edwards EnterpriseOne Multicurrency

Object Use

Select a UDC that indicates the use of the object. For example, the object may be used to create a program, a master file, or a transaction journal. A 2, or any other value from the 200 series, represents a table.

Object Type

The system displays an abbreviation that identifies the type of object being created. The object type for a table is TBLE. This field is populated by the system based on the type of object that you selected on the Add Object form.

Column Prefix

Enter a two-character prefix to be used for the table column names.

Modifying Table Objects

Either click OK on the Add Object form or select a table in a project and click Design to access the Table Design form.

  1. Select the Summary tab and revise these fields as appropriate:

    • Description

    • Product Code

    • Product System Code

    • Object Use

  2. Select the Attachments tab and enter information in the text area to document the table.

Selecting Data Items for Tables

Select a table in a project and access JD Edwards EnterpriseOne Table Design Aid.

  1. On the Data Dictionary Browser form, use the query by example (QBE) line to locate the required data dictionary items to include in the table.

  2. Drag each required data dictionary item from the Data Dictionary Browser to the Columns form.

  3. To remove a column from a table, select the column and select Delete from the Edit menu.

Defining Indices

Select a table in a project and access JD Edwards EnterpriseOne Table Design Aid.

  1. Click the indices form so that it is active, and the indices menu is visible.

  2. From the indices menu, select Add New.

    You can also drag indices from the Columns form onto the Indices form.

    The index description is Untitled, and the index is marked with a key icon that displays the letter P to indicate a primary index.

  3. Enter a name for the index, and press Enter.

  4. On the Columns form, drag appropriate columns to the index.

    A unique index is marked with a single key. You can right-click the index and select Unique from the Index menu to toggle the unique status. The Unique Primary Index cannot be changed to a non-unique status.

  5. Right-click the data item and select or clear the Ascending option to indicate the sort order of ascending or descending for an index column.

    An upward-pointing arrow indicates that the index column is sorted in ascending order.

Previewing Tables

Select a table in a project and access JD Edwards EnterpriseOne Table Design Aid.

  1. Click the Columns form so that it is active, and select Print Preview from the File menu.

    A preview of the table appears on the Columns form in place of the column names.

  2. On the Columns form, click Zoom In to enlarge the preview.

  3. Click Print to send the information to the printer.

Generating Tables

Access the Generate Table form.

Table Name

Displays the unique name of the table. This field is populated by the system based on the name that you gave the table when you created it.

Data Source

Enter the name of the data source where the database resides.

Object Owner ID

Enter the owner ID of the database that resides in the defined data source.

Password

Enter the database password that corresponds to the owner ID.

Generating Indices

Access the Generate Indexes form.

Table Name

Displays the unique name of the table. This field is populated by the system based on the name that you gave the table when you created it.

Data Source

Enter the name of the data source where the database resides.

Object Owner ID

Enter the owner ID of the database that resides in the defined data source.

Password

Enter the database password that corresponds to the owner ID.

Generating Header Files

Access the JD Edwards Table Design Aid form.

  1. Select the Design Tools tab, and click Generate Header File.

  2. The system generates a .h, or header, file.

Copying Tables

Access the Copy Table form.

Table Name

Displays the unique name of the table. This field is populated by the system based on the name that you gave the table when you created it.

Source Data Source

Enter the name of the source data source, that is the data source to copy from.

Destination Data Source

Enter the name of the target data source, that is the data source to copy to.

Object Owner ID

Enter the owner ID of the database that resides in the defined data source.

Password

Enter the database password that corresponds to the owner ID.

Removing Tables

Access the Remove Table form.

Table Name

Displays the unique name of the table. This field is populated by the system based on the name that you gave the table when you created it.

Data Source

Enter the name of the data source where the database resides.

Object Owner ID

Enter the owner ID of the database that resides in the defined data source.

Password

Enter the database password that corresponds to the owner ID.

Viewing the Data in Tables

Access the Universal Table Browser form.

Table

Enter the name that identifies a table in JD Edwards EnterpriseOne. For example, F0101 is the name of the Address Book master table. You can use the visual assist to search for a table

Data Source

Enter the name of the data source where the table resides. The default value is obtained from the JD Edwards EnterpriseOne Object Configuration Manager (OCM) settings for the environment in which the user is signed on. Use the visual assist to select from a list of valid JD Edwards EnterpriseOne data sources.

Format Data

Select this option to indicate whether UTB should format the data once it is fetched from the database. JD Edwards EnterpriseOne Data Browser on the web does not provide this option. It always formats data after it is fetched from the database. The options are:

Formatted: UTB formats data according to the specifications of the JD Edwards EnterpriseOne data dictionary item. For example, assume that the data item PROC is a numeric field with a size of 15 and includes four display decimals. For a PROC value of 56.2185, UTB displays a formatted value (using the data dictionary editing) as 56.2185, even though the value is stored in the database as 562185.

Unformatted: UTB displays the data according to the specification of the database and the data item type (such as numeric). For example, assume that the table data item PROC is a numeric field stored in the database. Depending on the type of database, the default for this field might be 32 with a precision of 15. Because JD Edwards EnterpriseOne does not store the decimals in the database, a PROC value of 56.2185 would be stored by the database as 562185.000000000000000 and would appear the same in UTB.

Working with Table Input/Output

This section contains the following topics:

Understanding Table I/O

Use the Table I/O feature in Event Rules Design to create instructions that perform table input and output. The Table I/O feature enables you to access a table through event rules. You can use the Table I/O feature to:

  • Retrieve records.

  • Update or delete records.

  • Add records.

Table I/O event rules enable event rule support for database access.

Available Operations

This table describes the Table I/O features and the operations that you can perform:

OperationDescription
FetchSingleCombines the Select and Fetch options in a basic operation. Indexed columns are used for the Select, and non-indexed columns are used for the Fetch. The operation opens a table for input or output but does not close it. All tables that do not use handles close automatically when the form that uses them is closed.
InsertInserts a new row.
UpdateUpdates an existing row. Only those columns mapped (presently in tables with or without handles) are updated. You can do partial key updates with tables and handles to tables. If you do not specify all the keys, then several records might be updated.
DeleteDeletes one or more rows in a table.
OpenOpens a table or business view.
CloseCloses a table or business view.
SelectSelects one or more rows for a subsequent FetchNext operation.
SelectAllSelects all rows for a subsequent FetchNext operation.
FetchNextFetches rows that you specify. You can fetch multiple records with multiple FetchNext operations or with a FetchNext operation in a loop.

Valid Mapping Operators

The Mapping form displays available objects that you can map to selected table columns. For SELECT statements, the available objects are used to build a WHERE clause. For FETCH statements, the available objects are used to receive data fetched from the database.

Key columns have an asterisk (*) next to them.

This table describes the operators that you can use for mapping specific table I/O operations:

Table I/O OperationMapping Operators
FetchSingleIndex Fields: =, <, <=, >, >=, !=, Like

Non-Index Fields: Copy Target

InsertAll Fields: Copy Source
UpdateIndex Fields: =

Non-Index Fields: Copy Source

DeleteAll Fields: =
OpenNA
CloseNA
SelectAll Fields: =, <, <=, >, >=, !=, Like
SelectAllNA

Understanding Buffered Inserts

You can use buffered inserts to improve the performance of inserting hundreds or thousands of records into a single database table as long as you don't need immediate feedback if an insertion failure occurs. You cannot use buffered inserts with interactive applications but you can use them with:

  • Table conversions

  • Table I/O

  • Batch processes

  • Business functions

Buffered inserts are not available with an Access database, post-insert triggers, or multiple-table views. They are available only with these databases:

  • Oracle (V8 and later)

  • DB2/400

  • SQL Server

The JD Edwards EnterpriseOne database middleware delivers records to the database management system one buffer load at a time.

When you request buffering, the database records are inserted individually and the buffer is automatically flushed when it fills; that is, the JD Edwards EnterpriseOne database middleware delivers the buffer to the database management system. The buffer can also be explicitly flushed. For example, the buffer flushes automatically when you commit a transaction or when you close a table or business view. The business function, table conversion engine, or Table I/O feature can explicitly request that the buffer be flushed as well.

Buffered Insert Error Messaging

Use caution when deciding to use buffered inserts. The system provides no immediate feedback while using buffered inserts if an insertion fails. If an insertion fails, the error appears in the log file. Consequently, buffered inserts are used primarily with batch applications.

Unless you are using the Oracle's JD Edwards EnterpriseOne Table Conversion application, you must request more detailed information from the middleware to get detailed error messages. In the JD Edwards EnterpriseOne Table Conversion application, the table conversion engine automatically performs this task. You can enable tracing to receive more detailed error messages. Otherwise, you get an error message that the insert failed. You should clear the output tables so that you do not receive duplicate error logging.

After you set up buffered inserts, you can use Special Operations to flush the buffers or get error messages.

Understanding Special Operations

In addition to the basic and advanced operations available on the Insert TableIO Operation form, there are two special operations:

  • Flush Insert Buffer

    To maintain data integrity, you should flush the insert buffer before you perform any operations other than an insert. If you fail to do so, the results of recent inserts might not be reflected in other operations, and the operations might not work properly.

    When you use the flush insert buffer option for a specific table, you must flush the buffer before you close the table.

  • Get Error Data

    To retrieve errors for records that the system did not insert properly, use the Get Error Data option. Depending on when the buffers are flushed, or when you begin another insert, you might overwrite the error information for a specific insert. If error information is critical, retrieve the information before the next insert begins.

    If you need to perform special error handling, set the error handling up after each table I/O insert and each Flush Insert Buffer option. Always retrieve the error information before you begin the next table operation.

    Note:

    The return code of each table I/O statement is stored in system variable SV File_IO_Status. If an Insert or Flush Insert Buffer operation failed, the SV File_IO_Status system variable might contain a value of CO ERROR_DETAILS_AVAILABLE. If so, you need to run the Get Error Data table I/O special operation to retrieve the error data. The Get Error Data operation returns the values used in the insert for all the requested columns.

Get Error Data Event Rules Example

This example illustrates how you can use CO ERROR_DETAILS_AVAILABLE:

F0101.Insert //Attempt an insert SL AgingDaysAP1 -> TK Address Number RC Page - -fi fi fi fi fi fi fi > TK Tax ID SL TargetEnvironment -> TK Description - Compressed If SV File_IO_fi Status is equal to CO ERROR_DETAILS_AVAILABLE F0101.Get Error Data //Failed withfi errors so get errors //Map values used in insert to the //specifiedfi fields. SL AgingDaysAP1 <- TK Address Number RC TESTT <- TK Tax ID SLfi ReportName <- TK Description - Compressed End If

Understanding Handles

In JD Edwards EnterpriseOne table I/O operations, the term handle refers to a type of file pointer. This file pointer connects the application or Universal Batch Engine (UBE) with the JD Edwards EnterpriseOne database middleware that communicates with the database manager. Handles point to a database table, and they are references to an address within the database middleware. Handles enable you to perform these operations, which cannot be performed using non-handle table I/O operations:

  • Concurrently open multiple instances of a single table or business view.

  • Open a table or business view in an environment other than the environment to which you are signed in.

    This feature is particularly helpful when you receive an upgrade to JD Edwards EnterpriseOne software or when you need to convert data from another system into JD Edwards EnterpriseOne software.

  • Pass handles into a form, named event rule, or business function so that you do not need to open a table or business view more than once.

    Note:

    You cannot use handles in transaction processing.

If you pass a handle to a form or a named event rule, a HANDLE data item must be included as a member in the data structure for the form or named event rule. In the form interconnect or business function call, you must assign a handle value from the event rules to the HANDLE data structure member. You can use this handle in the form or named event rule in the same way that you use any other table I/O handle.

You must explicitly open and close handles, unlike other table I/O operations in which the system implicitly opens or closes the table for you. You must open a handle before you can use it. All of the table I/O operations, except Open, work the same for handles as they do for tables and business views. When you are finished using a handle, you must explicitly close it. Close the handle in the same way that you close a table or business view, except select the Handle option.

In order to use handles in table I/O event rules, you must:

  • Define the handle in the data dictionary.

  • Create a handle variable in event rules.

  • Open the handle explicitly.

You might be able to find an existing handle for the table I/O. Whether you use an existing handle or create a new handle, you must create a handle variable in Event Rules Design. Create a handle variable in the same way that you create other variables. You can use any scope that is necessary.

After you create a handle variable, you must explicitly open the handle. Then, after performing the required table I/O, you must explicitly close it.

Working with Table I/O

This section lists the prerequisites and discusses how to:

  • Create table I/O event rules.

  • Use buffered inserts in table I/O.

  • Use special operations for buffered inserts.

  • Create handles.

  • Use handles with table I/O.

Prerequisites

Before creating table I/O event rules, ensure that you:

  • Create a batch application.

  • If you want to update the database, ensure that the batch application is defined as an update report.

Creating Table I/O Event Rules

Open a batch application in Oracle's J.D. Edwards EnterpriseOne Report Design Aid (RDA) and access Event Rules Design.

  1. Click the Table I/O button.

  2. On the Insert TableIO Operation form, select an operation from Basic Operations, Advanced Operations, or Special Operations and click Next.

  3. On the Data Source form, select a table, business view, or handle as the data source and click Next.

  4. On the Mapping form, select fields from the Available Objects list to map to columns in the mapping.

    The key field must be mapped. Map as many other fields as required to ensure that the correct data is associated with the correct record.

  5. Click the Operation for each map until you locate the operator that you want.

    The default operator is equal.

  6. Click Finish to save the operation and return to Event Rules Design.

Using Buffered Inserts in Table I/O

Open a batch application in RDA and access Event Rules Design.

  1. Click the Table I/O button.

  2. On the Insert TableIO Operation form, select Open under Advanced Operations and click Next.

  3. On the Data Source form, select the table that you want to use and click Advanced Options.

  4. On the Advanced Options form, select Buffer Inserts and click OK.

Using Special Operations for Buffered Inserts

Open a batch application in RDA and access Event Rules Design.

  1. At the point in which you want to perform either a Flush Insert Buffer or Get Error Data operation, click the Table I/O button.

  2. On the Insert TableIO Operation form, select one of these options under Special Operations:

    • Flush Insert Buffer

    • Get Error Data

Creating Handles

In JD Edwards Solution Explorer access EnterpriseOne Life Cycle Tools, Application Development, Data Dictionary Design, select Work With Data Dictionary Items to access the Work With Data Items form.

Data Item

Enter the name of the data item. This is a 32-character alphabetical field that does not allow spaces or special characters.

Alias

Enter a unique identifier.

Glossary Group

Select a user-defined code (UDC) (H95/DG) that indicates the type of data item. A handle is glossary group D, Primary Data Elements.

Description

Enter a meaningful description of the data item.

Product Code

Select a UDC (98/SY) from the range of values reserved for clients: 55–59.

Product System Code

Select a UDC (98/SY) that represents the JD Edwards EnterpriseOne system where the data is used. This value is used for reporting and jargon purposes. Example values include:

01: Oracle's JD Edwards EnterpriseOne Address Book

03B: Oracle's JD Edwards EnterpriseOne Accounts Receivable

04: Oracle's JD Edwards EnterpriseOne Accounts Payable

09: Oracle's JD Edwards EnterpriseOne General Accounting

11: Oracle's JD Edwards EnterpriseOne Multicurrency

Data Type

Select the style or classification of data. Examples include, string, date, character, and identifier. A handle is an identifier data type.

Size

Enter the field size of the data item.

Class

Select a class that defines the essential attributes and characteristics of the data item. Examples include, name, email, and table handle.

Control Type

Select the type of graphical user control that is associated with the data item. Examples include button, radio button, and user-defined code.

Row Description

Enter the description of the data item as it will appear in a group report.

Column Title

Enter the description of the data item as it will appear in a columnar report.

Using Handles with Table I/O

Open a batch application in RDA and access Event Rules Design.

  1. Create an event rule variable using the appropriate handle data dictionary item.

  2. Click the Table I/O button.

  3. Select Open under Advanced Operations and click Next.

  4. On the Data Source form, select the Handles tab.

  5. Select the handle that you want to open and click Next.

  6. Select a variable that contains the name of the environment in which you want to open the table and click Finish.

    If you want to open the table in the login environment, select the system value SL LoginEnvironment. System values also exist for the source and target environments if you use the Table I/O in Table Conversion feature.

  7. Click the Table I/O button.

  8. Select Close and click Next.

  9. On the Data Source form, select the Handles tab.

  10. Select the handle that you want to close, and click Finish.

Creating Table Event Rules

This section contains the following topics:

This chapter provides an overview of table event rules and discusses how to work with table event rules.

Understanding Table Event Rules

Use table event rules to attach database triggers (or programs) that automatically run whenever an action occurs against the table. An action against a table is called an event. When you create a database trigger in Oracle's JD Edwards EnterpriseOne, you must first determine which event activates the trigger and then use Event Rules Design to create the database trigger.

Table event rules provide embedded logic at the table level. Table event rules have their own location, events, and system functions. When you use table event rules, neither the calling application nor the user is notified of changes or events to the table. No form or report interconnect is available with table event rules.

You can use table event rules for data integrity. For example, when you delete a record in Oracle's JD Edwards EnterpriseOne Address Book, you might want to delete all associated records, such as phone and category codes. You can also use table event rules for currency. The Currency Conversion is On event rule handles currency information in table event rules.

You can attach event rules on a table-by-table basis to these events:

  • After Record is Deleted

  • After Record is Fetched

  • After Record is Inserted

  • After Record is Updated

  • Before Record is Deleted

  • Before Record is Inserted

  • Before Record is Updated

  • Currency Conversion is On

This table describes the functions that you can use in table event rules:

FunctionsDescription
Assignment\ExpressionEnables you to create assignments and complex expressions.
If\WhileEnables you to create IF/WHILE conditional statements.
Business FunctionEnables you to call existing business functions.
System FunctionEnables you to attach existing JD Edwards EnterpriseOne system functions.
VariablesEnables you to create Event Rule variables.
ElseEnables you to insert an ELSE clause, which is only valid within the boundaries of IF and ENDIF.
Table I/OEnables you to create event rules used for database access. Performs table input and output, data validations, and record retrieval.

You do not need to create and associate data structures to table event rule functions. The table itself is the data structure that is passed to the table event rule function.

Working with Table Event Rules

This section provides an overview of table event rule triggers and discusses how to add table event rules to table conversions.

Understanding Table Event Rule Triggers

To create table event rules, you must:

  • Create the table trigger in Event Rules Design.

  • Generate the JD Edwards EnterpriseOne table trigger as C code.

  • Build the table trigger.

    When you build table triggers, the system performs these actions:

    • Converts the event rule to C source code, which creates the files OBNM.c and OBNM.hxx (OBNM = Object Name).

      The source file contains one function per table event rule event.

    • Creates a make file to compile the generated code.

    • Runs the make file to compile the new functions and to add them into JDBTRIG.DLL.

      This consolidated DLL contains table event rule functions.

Adding Table Event Rules to Table Conversions

Access the Object Management Workbench form.

  1. Check out the table to which you want to attach event rules and click Design.

  2. On the Table Design form, select the Design Tools tab and click Start Table Trigger Design Aid.

  3. Select an event from the Events list.

  4. On Event Rules Design, click one of the event rule buttons and complete the event rules.

  5. Click Save to save the event rule specifications and then click Close.

  6. If you are creating a new table in Oracle's JD Edwards EnterpriseOne Table Design Aid, select the Table Operations tab and click Generate Table.

    Important:

    Never perform this step on an existing table because it clears all data.
  7. On the Generate Table form, complete these fields and click OK:

  8. On the Table Design form, select the Design Tools tab and click Build Table Triggers.

  9. To review a log of the build, select Generate Header File, and then open the file that the system created.

    The creation of the table event rules is complete. The newly created or modified table event rule is called from the JD Edwards EnterpriseOne database middleware whenever the corresponding event occurs against the table.


JD Edwards EnterpriseOne Tools Table Design Guide, Release 9.1

E21486-01

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Sours: https://docs.oracle.com/cd/E24705_01/doc.91/e21486/toc.htm
  1. The outdoors trader
  2. Awesome o 3000
  3. Mini starbucks stickers
  4. Ufc line up
  5. Chillicothe mo radar

A Appendix: Tables Used by the JD Edwards EnterpriseOne Console

F0006Business Unit MasterF0008Date Fiscal PatternsF0009General ConstantsF0010Company ConstantsF0012Automatic Accounting Instructions MasterF03012Customer Master by Line of BusinessF03B11Customer LedgerF03B13Receipts HeaderF03B14Receipts DetailF03B16A/R Statistical HistoryF0411Accounts Payable LedgerF0413Accounts Payable - Matching DocumentF0414Accounts Payable Matching Document DetailF0902Account BalancesF0911Account LedgerF09521Cash Type RulesF09522Cash Forecast DataF09E108Policy Edit RulesF1602Cost Analyzer BalancesF1603Cost Analyzer View StructureF3102Production CostF4101Item MasterF4102Item Branch FileF41021Item Location FileF4105Item CostF4201Sales Order Header FileF4211Sales Order Detail FileF42119Sales Order History FileF4301Purchase Order HeaderF43090Supplier/Item RelationshipsF4311Purchase Order Detail FileF43121Purchase Order Receiver FileF4322Purchasing Tolerance RulesF4801Work Order Master FileF80D010Sales Order FactF80D020GL Account Balances FactF80D021Financial Ratios Amount Dimensions TableF80D100PMD - Date DimensionF80D101PMD - UBE TimestampF80D104Address Book ListF80D105Business Unit ListF80D106Product Group ListF80D107Goals DefinitionF80D107AGoals Definition TagF80D108Goals Definition Cross ReferenceF80D110PMD Search By Saved QueryF80D111FMD Search By Saved QueryF80D112SOD RulesF80D113SOD Process MasterF80D114SOD Group MasterF80D120SOD ViolationsF80D130Compliance MasterF80D131Compliance Instance DetailF80D135SOD Alert MasterF80D136SOD Alert DetailF80D150Whistle Blower Recipient ListF80D200Days Sales Outstanding Aggregate TableF80D201Days Payable Outstanding AggregateF80D202Cash to Cash Cycle Time AggregateF80D203Forecasted Cash Flow AggregateF80D210On Time Shipment Customer Request Date Aggregate TableF80D211On Time Shipment Promise Ship Date Aggregate TableF80D212Past Due Aggregate TableF80D213Back Order Aggregate TableF80D214Variance TableF80D215Book to Ship Aggregate TableF80D220Inventory Aggregate TableF80D221General Ledger Aggregate TableF80D230On Time Manufacturing Production CompletionsF80D231Manufacturing Production CostingsF80D240Booked Orders AggregateF80D241Shipped Order RevenueF80D242Projected Revenue AggregateF80D243Backlog AggregateF80D250Supplier On-Time Delivery AggregateF80D251Material Lead Time Exception AggregateF80D252Supplier Pass Quality AggregateF80D253AP Daily Counts and AmountsF80D254AP Discount Information AggregateF80D255AP Open Payables AggregateF80D256AP Voucher Paid Late AggregateF80D272Most Profitable Customers AggregateF80D273Most Profitable Products AggregateF80D274Most Profitable Brands AggregateF80D280AR Daily Counts and Amts AggrF80D281AR Delinquency Info AggregateF80D282AR Discount Information AggregateF80D283AR Open Chargeback AggregateF80D284AR Open Receivables AggregateF80D285AR Total Chargeback AggregateF80D300Dashboard ConstantsF80D301Dashboard Code Metric Cross ReferenceF80D302Metric ID Time Dimension Cross ReferenceF80D303Metric DefinitionF80D304Variant DefinitionF80D305Hierarchy DefinitionF80D306Action DefinitionF80D307Metric Action Cross ReferenceF80D309Metric Series Cross RefF80D310Alert DefinitionF80D310AAlert Definition Tag TableF80D311Alert InstanceF80D311AAlert Instance Tag TableF80D312Alert SubscriptionF80D315Alert Instance StatusF80D320Dashboard ConfigurationF80D321UI Metric Group DefinitionF80D322UI Metric Group DetailF80D323GroupID Email AddressF80D701Unposted Transactions Aggregate
Sours: https://docs.oracle.com/cd/E16582_01/doc.91/e15094/tablesusedbyjdeconsole.htm
Oracle BI Publisher Jumpstart for JD Edwards Reporting and BI

A Tables Used by JD Edwards EnterpriseOne Project Manufacturing

MPS/MRP/DRP Message File (F3411)Contains the action messages that are generated by MPS, MRP, or DRP.

Stores the production number and production number short.

MPS/MRP/DRP Lower Level Requirements File (F3412)Contains the source of gross requirements that are posted to items from parent items.

Stores the production number short.

MPS/MRP/DRP Summary File (F3413)Contains the time series data for forms and reports.Vendor Schedule Quantity File (F3430) Stores blanket order-based schedules.

Stores the production number and production number short.

Vendor Schedule Commitment File (F3435)Stores commitment information for blanket order-based schedules.

Stores the production number and production number short.

Production Number Master File (F34401)Stores production number information including company, production number short, item number, branch/plant (Release 9.1 Update), type, status, dates, and segment values.Production Number Master Tag File (F34401T) (Release 9.1 Update)Stores production number information including company, production number, production number short, branch/plant, order number from sales order detail line, production number long (Future Use field), and audit fields. (Release 9.1 Update)Production Number Structure File (F34402)Stores the production number structure definition including production type, separator option, separator value, segments, and segment sequence.Adhoc Vendor Schedule File (F3450)Stores supplier release schedules without supplier and blanket order information.

Stores the production number and production number short.

Forecast File (F3460)Stores the forecast data that Resource Requirements Planning (RRP) validates. The data is then used as input to MPS/MRP/DRP.

Stores production number and production number short.

Item Transactions Detail File (F41UI001)Stores the production number, production number short, and production number controlled setting. Stores a process flag to determine if inventory consumption form is required to consume on-hand quantity.Item Master (F4101)Stores basic information about each item in inventory, such as item numbers, description, category codes, and units of measure.

Stores production number controlled setting.

F4101 Item Master Unedited Transaction Table (F4101Z1)Stores production number controlled setting.Item File (F4101A)Stores item information in a work file.

Stores production number controlled setting.

Item Branch (F4102)Stores the branch/plant information for an item, such as quantities, category codes, and cost information.

Stores production number controlled setting.

Item Location File (F41021)Stores primary and secondary locations for an item.

Stores the cumulative on-hand quantity of generic and production controlled inventory.

Item Location Tag File (F41021T) Stores on-hand quantity information by production number.Item Ledger File (F4111)Stores transaction history for all items.

Stores the production number and production number short.

Cycle Count Transaction Tag File (F4141T)Stores on-hand quantities by production number for items in the cycle count process.SO Detail Cache File (MBF) (F42UI11)Stores the production number and production number short.Sales Order Detail (F4211) Stores detail information for each sales order line (item number, quantity ordered, price, and so forth).

Stores the production number and production number short.

Sales Order History (F42119)Contains past sales data, which provides the basis for the forecast calculations.

Stores the production number and production number short.

S.O. Detail Ledger File (F42199)Stores order history information.

Stores the production number and production number short.

Purchase Order Detail File (F4311)Stores the detail information for the purchase order. This includes the category codes 01 through 04 fields. The Job Typ field for Project and Government Contract Accounting is stored in this table.

The column GBCFG (Generated by Configurator) has a flag that indicates that the purchase order has a related configured order.

Stores the production number and production number short.

Purchase Order Generator File (F4311Z)Stores purchase order information.

Stores the production number and production number short.

Purchase Order Detail Unedited Transaction Table (F4311Z1)Stores purchase order detail information for Procurement outbound interoperability. This includes user-defined fields. The records for the Purchase Order Clauses table (F4320) are not written to any Z file.

Stores the production number and production number short.

Purchase Order Receiver File (F43121)Stores receipt record and voucher record information with details such as open quantity and open amount. The Job Typ field for Project and Government Contracting is stored in this table.

Stores the production number and production number short.

Receiver workfile (F43121Z)Stores receipt record and voucher record information in a temporary work file.

Stores the production number and production number short.

Receipts Unedited Transaction Table (F43121Z1)Stores purchase order receipt information for Procurement outbound interoperability.

Stores the production number and production number short.

P.O. Detail Ledger File - Flexible Version (F43199)Stores detail information for each purchase order line, such as item number, price, quantity ordered, and purchase amount (PA) ledger type.

Stores the production number and production number short.

EDI Purchase Order Detail - Inbound (F47012)Stores the production number and production number short.EDI Product Activity Data Detail - Inbound (F47122)Stores information for the product activity data inbound transactions.

Stores production number and production number short for inventory issues, adjustments, and transfers.

EDI Purchase Order Change Detail - Inbound (F47132)Stores the production number and production number short.Work Order Master Tag (F4801T)Stores additional information about a work order.

Stores the production number and production number short.

Outbound Work Order Header (F4801Z1)Stores work order information.

Stores the production number and production number short.

Sours: https://docs.huihoo.com/oracle/jd-edwards/enterpriseone/applications/9.1/doc.91/e23888/tables_used.htm

List jde table

Welcome to JDE Tables.com

New JDE 9.20 Demo Virtual Machines

The home of table descriptions for Oracle's Enterprise Resource Planning system, JD Edwards

If there's one thing we thought was missing online - it's reference material for Oracle's superb Enterprise Resource Planning system, JD Edwards - namely table definitions/descriptions! Knowing table structure is critical if you're developing applications or writing reports, and is also useful for general users too in gaining a deeper understanding of the systems they use. In the interests of helping others, we've set about collecting this information and grouping it altogether to provide an easy, simple and free resource to assist you, the community of JD Edwards users, support technicians, consultants and developers, with a better understanding of Oracle's flagship product.

TablePrefixColumnsIndexesDescriptionTypeReportCategory
1F4211SD26819Sales Order Detail FileTransaction Files42: Sales Management
2F0101AB9515Address Book MasterMaster Files01: Address Book
3F9671SD131Software Update Detail TableHistory FilesH96U: UpgradeSystem Tables
4F4101IM2098Item MasterMaster Files41: Inventory ManagementBusiness Data
5F0911GL14124Account LedgerTransaction Files09: General AccountingBusiness Data

TablePrefixColumnsIndexesDescriptionTypeReportCategory
1F0011WIC51F0011W - WF - Batch To DetailFiles09: General Accounting
2F4211SD26817Sales Order Detail FileTransaction Files42: Sales Management
3F4101IM2098Item MasterMaster Files41: Inventory ManagementBusiness Data
4F0101AB9515Address Book MasterMaster Files01: Address Book
5F0911GL14126Account LedgerTransaction Files09: General AccountingBusiness Data

TablePrefixColumnsIndexesDescriptionTypeReportCategory
1F0911GL13425Account LedgerTransaction Files09: General AccountingAS400 Coexistence Tables
2F0101AB9514Address Book MasterMaster Files01: Address BookBusiness Data
3F0411RP14215Accounts Payable LedgerTransaction Files04: Accounts PayableAS400 Coexistence Tables
4F4311PD21810Purchase Order Detail FileTransaction Files43: ProcurementAS400 Coexistence Tables
5F4211SD25415Sales Order Detail FileTransaction Files42: Sales ManagementAS400 Coexistence Tables
JDE Tables.com is mobile/tablet enabled

We have a more mobile/tablet friendly version of this service available too - for those times you're away from your computer. Also, have you tried printing Printer Icon a table/column description page yet? We've styled output specifically for print media - simple, clean, no-ads and in mono.

Finally on Facebook!

We're now on FaceBook. Yes, a bit late on the bandwagon but there none-the-less. Send us your suggestions and comments, praise or criticism - we'd love to hear your views.

SAP

Migrating from/to SAP? Why not visit our sister site www.saptables.net for all your table description requirements!


Sours: http://jderef.com/
JD Edwards EnterpriseOne Table Design

.

Now discussing:

.



1039 1040 1041 1042 1043