IN_FL_SHADW_AET

(SQL Table)

# PeopleSoft Field Name PeopleSoft Field Type Database Column Type Description

1 PROCESS_INSTANCE Number(10,0) DECIMAL(10) NOT NULL Process Instance

2 SELECT_UNFULFILLED Character(1) VARCHAR2(1) NOT NULL Indicates requests fed to the Fulfillment Engine should include data in an unfulfilled state.

3 SELECT_RELEASABLE Character(1) VARCHAR2(1) NOT NULL Indicates requests fed to the Fulfillment Engine should include data in a releasable state.

4 SELECT_CONFIRMED Character(1) VARCHAR2(1) NOT NULL Indicates requests fed to the Fulfillment Engine should include data in a confirmed state.

5 SELECT_RELEASED Character(1) VARCHAR2(1) NOT NULL Indicates requests fed to the Fulfillment Engine should include data in an Released state.

6 COMMIT_LEVEL Character(2) VARCHAR2(2) NOT NULL Identifies the level for the Commit Count. When Commit Count is not zero, Commit Level must be less than or equal to Processing Level.
10=Request
20=Order
30=Line
40=Item

7 COMMIT_COUNT Number(10,0) DECIMAL(10) NOT NULL Count based on Commit Level used to determine the size of a unit of work to commit to the database. A value of zero indicates include all updates in the same unit of work and do one commit at the end of each Processing Group. This count can be used to help tune at a site that is running into issues with large runs causing blocking and deadlocks on the base tables updated by the process.

8 PROCESSING_LEVEL Character(2) VARCHAR2(2) NOT NULL Identifies the level for the Processing Count. When Processing Count is not zero, Processing Level must be greater than or equal to Commit Level.
10=Request
20=Order
30=Line

9 PROCESSING_COUNT Number(10,0) DECIMAL(10) NOT NULL Count based on Processing Level used to determine the Processing Group. A value of zero indicates include all data into one Processing Group. This count can be used to help tune at a site that is running into issues with large runs causing blocking and deadlocks on the base tables updated by the Process. When processing, if Commit Count is greater than the specified Processing Count and the Processing Level is the same as the Commit Level, the Processing Count should be set to the Commit Count.

10 PASS_THROUGH_LEVEL Character(2) VARCHAR2(2) NOT NULL Provides the ability to pass good transactions through the system while holding up transactions that need additional review. When processing, the Pass-through Level must be less than or equal to Processing Level and Commit Level. If the process recieves a Pass-through Level greater than the specified Commit Level or Processing Level, the Commit Group and/or Processing Group will be expanded to include all data at the Pass-through Level.
10=Request
20=Order
30=Line

11 COMPLETE_FLG Character(1) VARCHAR2(1) NOT NULL Complete Flag
0=Process Location
1=Pick Line Complete
2=Pick Batch Complete
3=Pick Line as Planned
4=Pick Batch as Planned
5=Process Location - Incomplete
6=Complete Pick - Zero Quantity
7=Complete Pick - Leave Alone
8=Complete Pick - Dft Ship Loc
A=Use Defaults
B=No Action

#	PeopleSoft Field Name	PeopleSoft Field Type	Database Column Type	Description
1	PROCESS_INSTANCE	Number(10,0)	DECIMAL(10) NOT NULL	Process Instance
2	SELECT_UNFULFILLED	Character(1)	VARCHAR2(1) NOT NULL	Indicates requests fed to the Fulfillment Engine should include data in an unfulfilled state.
3	SELECT_RELEASABLE	Character(1)	VARCHAR2(1) NOT NULL	Indicates requests fed to the Fulfillment Engine should include data in a releasable state.
4	SELECT_CONFIRMED	Character(1)	VARCHAR2(1) NOT NULL	Indicates requests fed to the Fulfillment Engine should include data in a confirmed state.
5	SELECT_RELEASED	Character(1)	VARCHAR2(1) NOT NULL	Indicates requests fed to the Fulfillment Engine should include data in an Released state.
6	COMMIT_LEVEL	Character(2)	VARCHAR2(2) NOT NULL	Identifies the level for the Commit Count. When Commit Count is not zero, Commit Level must be less than or equal to Processing Level. 10=Request 20=Order 30=Line 40=Item
7	COMMIT_COUNT	Number(10,0)	DECIMAL(10) NOT NULL	Count based on Commit Level used to determine the size of a unit of work to commit to the database. A value of zero indicates include all updates in the same unit of work and do one commit at the end of each Processing Group. This count can be used to help tune at a site that is running into issues with large runs causing blocking and deadlocks on the base tables updated by the process.
8	PROCESSING_LEVEL	Character(2)	VARCHAR2(2) NOT NULL	Identifies the level for the Processing Count. When Processing Count is not zero, Processing Level must be greater than or equal to Commit Level. 10=Request 20=Order 30=Line
9	PROCESSING_COUNT	Number(10,0)	DECIMAL(10) NOT NULL	Count based on Processing Level used to determine the Processing Group. A value of zero indicates include all data into one Processing Group. This count can be used to help tune at a site that is running into issues with large runs causing blocking and deadlocks on the base tables updated by the Process. When processing, if Commit Count is greater than the specified Processing Count and the Processing Level is the same as the Commit Level, the Processing Count should be set to the Commit Count.
10	PASS_THROUGH_LEVEL	Character(2)	VARCHAR2(2) NOT NULL	Provides the ability to pass good transactions through the system while holding up transactions that need additional review. When processing, the Pass-through Level must be less than or equal to Processing Level and Commit Level. If the process recieves a Pass-through Level greater than the specified Commit Level or Processing Level, the Commit Group and/or Processing Group will be expanded to include all data at the Pass-through Level. 10=Request 20=Order 30=Line
11	COMPLETE_FLG	Character(1)	VARCHAR2(1) NOT NULL	Complete Flag 0=Process Location 1=Pick Line Complete 2=Pick Batch Complete 3=Pick Line as Planned 4=Pick Batch as Planned 5=Process Location - Incomplete 6=Complete Pick - Zero Quantity 7=Complete Pick - Leave Alone 8=Complete Pick - Dft Ship Loc A=Use Defaults B=No Action