This document describes possible issues related with F40039 (Document Type Master) and F400391 (Document Type Exclusion Rules).
Application P40040 (Document Type Maintenance) is available in EnterpriseOne beginning with release 8.12.
Document Type Maintenance is a centralized access point which enables you to maintain document type with ease. Through this application a number of UDC values can be added/deleted to control the process of a certain transaction in Inventory, Sales, Procurement, Service Order, Work Order and Shipping per document/order type.
The P40040 program maintains document type information in these UDC tables:
Note:
Where Vertical Feature (UDC 40/VF) and EnterpriseOne System Control (P99410) control the process globally/vertically, the document type master (P40040) enable/disable a certain routine per document type (or, order type).
In case you need to add additional order/document type [Target], refer exiting document type [Source] which you want to take same process. Once you have created a new document type, verify all values between Source Document type and Target Document type in F40039 - Document Type Master through Databrowser utility and verify that all the necessary UDC values are populated properly.
| Category | Active Controls | Column ID in F40039 | Values | Reference |
|---|---|---|---|---|
| Document TypeR | DCT* | UDC 00/DT | Primary Key for F40039 | |
| Inventory | (radio button) Transaction Type (TNTP) | TNTP | 0 - Ignore 1 - Incoming 2 - Outgoing 3 - Both |
A value that specifies if the transaction type is incoming, outgoing, or both. Valid values are: * Select all transactions. 1 Select only incoming transactions. 2 Select only outgoing transactions. 3 Select only transaction types that are both incoming and outgoing. Above value does not affect actual transactions except Stock Valuation through NER N3900130 - SVCCardexTrigger (Stock Valuation Cardex Trigger) when online valuation is on to write F39120W (Period Detail Work File) when TNTP is 1, 2 or 3. <Document 625399.1> - E1: 39: Advanced Stock Valuation Overview |
|
(check box) Include in Integrity Report (IRPT) Per the help behind the check box, this check box appears to only be applicable to inventory integrity reports, Item Ledger/Account Integrity Report (R41543) and Item Balance/Ledger Integrity Report (R41544). Select this option when the system should include transactions with the specified inventory document type in these two integrity reports. |
IRPT | 1 - Checked 0 - Unchecked |
This feature is not currently activated.
|
|
| (check box) Cross Docking Supply | A112 | cGenericChar12 1 - Checked 0 - Unchecked |
cSupplyOrderType to handle Cross Docking Supply 1 - Purchase Order 2 - Work Order In a Sales Order, if an F4211 line is cross-dock related(i.e. pegged) to a PO, then the related cross-dock fields must match EXACTLY, the Purchase order fields for the record to be selected If an F4211 line is cross-dock related(i.e. pegged) to a WO, then the Order number and the Order Type in the related cross-dock fields must match, EXACTLY the WO Order number and Order Type <Document 857942.1> - E1: 46: Work Orders Not Shown On Planned Cross-Docking Workbench |
|
| (check box) Display Lot Trace/Track | ILTT | 1 - Checked 0 - Unchecked |
If you select this option, then inventory transactions with the appropriate document type will be displayed in lot tracing and tracking. If you do not select this option, then the system will process inventory transactions with this document type, but the transactions will not appear in lot tracing and tracking. Add/Update/Delete UDC 40/DC - Trace/Track Document Types, with UDCValue = FC Document TypeR
UDCDescription1 = Description 1 of 00/DT UDCDescription2 = Description 2 of 00/DT <Document 625954.1> - E1: 30: Lot Trace/Track Inclusion Rules Defined |
|
| (check box) Consolidate Lot Trace/Track | LTTC | 1 - Checked 0 - Unchecked |
(No Implementation) If this box is checked, an attempt to consolidate inventory transactions will made. If unchecked, consolidations will be avoided. |
|
| Nature of Transaction | NATN | UDC 40/NT Possible values are, (blank) - None B - Bottom C - Top I - Issue M - WO Completion T - Transfer |
This value is used to tell Lot Trace/Track how to process inventory transactions that have a 'From' side and a 'To' side, as well as 'Bottom' and 'Top' levels. Examples of From/To transactions are: Inventory Transfers, Inventory Reclassifications, and Work Order Issues/Completions. Examples of Bottom/Top transactions are: Sales Orders and Purchase Receipts. An inappropriate value will cause the inventory transaction to be processed incorrectly. Add/update/delete UDC 40/DC -Trace/Track Document Types, with szUDCValue = FC Document TypeR
szUDCDescription1 = Description 1 of 00/DT szUDCDescription2 = F40039.NATN <Document 625954.1> - E1: 30: Lot Trace/Track Inclusion Rules Defined |
|
| Sales | Order Category | OCAT | UDC 40/OC | Use this value to identify blanket order types in the Sales Order Management and Procurement systems. Validate Values are, (blank) Regular Order 1 - Blanket Order (Note: Though code 2 and 3 are available from UDC 40/OC but these values are not valid for this entry because the purpose of this control is to add/delete UDC 40/BT) Add/update/delete UDC 40/BT - Blanket Order Type, with szUDCValue = FC Document TypeR
szUDCDescription1 = Description1 of 00/DT szUDCDescription2 = Description2 of 00/DT <Document 625581.1> - E1: 42: How to Create Sales Orders from Blanket Orders (P4210/P42101/P420111) |
| Interbranch Orders | IBOR | UDC 40/IB | (No Implementation) A value of 1 will identify this order type as an interbranch order type. When you create an interbranch order using the Sales Order Entry (P4210), the system process additional order information, such as cost markup. You would use an Interbranch orders in a situation where the customer places an order with a sales office, but the sales office ships the inventory to the customer from a warehouse facility. The system creates accounting transactions and intercompany invoices for interbranch sales orders during Sales Update and Invoice Print. Note: currently Interbranch order is determined by processing option of P4210 (szPOInterbranchOrderTypes) |
|
| Other Quantity (1/2) | OTQY | UDC 40/OQ | (No Implementation) This field determines if the Quantity on Other Sales Order 1 or 2 field in the Item Location file is to be updated instead of the Soft Commit or Hard Commit fields. Valid Values are, (Blank) None 1 - Update Sales Order Qty 1 or 2 (F4211) 2 - Update Item Location (F41021) cf., Currently F4211.OTQY is used to indicate Quote/Blanket Order with value 1 and 2 <Document 625559.1> - E1: 42: Inventory Commitments In Sales (R42995/P4210/P42101/R42118/P42117/R42520) |
|
| (check box) Relieve On Hand Inventory at Ship Confirm | RELV | 1 - Checked 0 - Unchecked |
This feature is not currently activated. (For future usage) Use this field to indicate whether the quantity committed to this sales order will be relieved from the On Hand Quantity during the Shipment Confirmation process. If this option is disabled, the Shipment Confirmation process will only hard commit the quantity shipped to the appropriate item location. Add/update/delete UDC 40/IU - Inventory Update Type, with szUDCValue = FC Document TypeR
(If RELV = '1' then insert/update or changed to '0' then delete it from UDC 40/IU)szUDCDescription1 = Description1 of 00/DT szUDCDescription2 = Description2 of 00/DT <Document 625559.1> - E1: 42: Inventory Commitments In Sales (R42995/P4210/P42101/R42118/P42117/R42520) |
|
| (check box) Ship And Debit Processing | A105 | 1 - Checked 0 - Unchecked |
A code that indicates whether ship and debit processing is activated or inactivated for a document type. Valid values are: 0 Ship and debit processing is inactive. 1 Ship and debit processing is active. <Document 625583.1> - E1: 42: Ship and Debit |
|
| Product Code | SY | UDC 98/SY Allow Blank |
(No Implementation) since next number can be handled up to Company by Fiscal year | |
| Order Type Next Number | ORNN | (No Implementation) Index for next number table | ||
| Send Status Notification | A110 | Only when the value is 1 send notification to customer via XPI Functions B4003000 & B4003020 (cf., A106 in Procurement setup). Do not set value 1 unless you have interface with 3rd party software | ||
| (hidden push button) Consignment | CSNOT | 0 - Non-Consignment Order 1 - Consignment Billing Order 2 - Consignment Shipping Order |
A value to identify the Consignment Order Type. Whenever selection changes (push button) consignment is to be called as below, (Case CSNOT = 0) Non Consignment Enable Control(FC Relieve On Hand Inventory at Ship Confirm) (Case CSNOT = 1) Consignment Billing Order Disable Control(FC Relieve On Hand Inventory at Ship Confirm) Set RELV = '0' (Case CSNOT = 2) Consignment Shipping Order Disable Control(FC Relieve On Hand Inventory at Ship Confirm) Set RELV = '1' <Document 625644.1> - E1: 42: Consignment Sales |
|
| Procurement | ProcurementOrderCategory | OCAT | UDC 40/OC | (Shared with Order Category in Sales Tab) Use this value to identify blanket order types in the Sales Order Management and Procurement systems. Use this value to identify blanket order types in the Sales Order Management and Procurement systems. Validate Values are, (blank) Regular Order 1 - Blanket Order (Note: Though code 2 and 3 are available from UDC 40/OC but these values are not valid for this entry because the purpose of this control is to add/delete UDC 40/BT) Add/update/delete UDC 40/BT - Blanket Order Type, with szUDCValue = FC Document TypeR
szUDCDescription1 = Description1 of 00/DT szUDCDescription2 = Description2 of 00/DT <Document 625636.1> - E1: 43: Blanket Orders in Purchasing FAQ |
| ProcurmentOtherQuantity | OTQY | UDC 40/OQ | (No Implementation) (Shared with Order Category in Sales tab) This field determines if the Quantity on Other Purchase Order field is updated in the Item Location file instead of the On Purchase Order field. Valid Values are, (Blank) None 1 - Update Sales Order Qty 1 or 2 (F4311) 2 - Update Item Location (F41021) Currently F4311.OTQY is to be set 1 for quote order based on processing option value |
|
| (check box) Commit Procurement Orders | CTPA | 1 - Checked 0 - Unchecked |
A code that specifies whether the system automatically commits the amount on a purchase order for a service or a subcontract. Add/Update UDC 40/CT - Commitment Document Type, with UDCValue = DCT
UDCDescription1 = Description 1 of 00/DT UDCDescription2 = Description 2 of 00/DT <Document 625480.1> - E1: 43: Encumbrance/Commitment Processing |
|
| Publish Externally | A106 | 1 - Checked 0 - Unchecked |
A code that specifies whether the system allows you to publish document types externally. If you do not enter a value, the system does not allow you to publish document types externally. Other valid values are: 0 - You cannot publish document types externally. 1 - You can publish document types externally. Publish Externally via B4302150 - XPI to 3rd party software If you are in upgraded environment, the description must be changed as described at enhancement <Bug 10754837> : SETUP DOC TYPES IN P40040 - SAR: 5231668 |
|
| ProcurementSystemCode | SY | UDC 98/SY Allow Blank |
(No Implementation) | |
| ProcurementNextNumber | ORNN | (No Implementation) | ||
| S/WM | Contract Type | CSKT | UDC 17/CM (Blank) - None 1 - Service Contract 2 - Service Contract Quote 3 - Supplier Contract |
A document type that indicates that this document is a service contract in CSMS. You can also use this document type to define the specific contract type. For example, this could be a regular CSMS service contract or it could be a quote for a CSMS service contract. This value is to be checked through Entitlement Checking (where code value is 1) or Supplier Recovery Entitlement (where code value is 3) Tab name has changed from CSMS to S/WM through enhancement |
| Work Order Definition | Work Order Type | A201 | UDC 48/OT | Hard Coded (Do Not Change)
<Document 1098535.1> - E1: 31: Work Order Type Field A201 in Document Master Table F40039 |
| Service Order Type | CSOT | Note: This column does not appear in P40040. A document type that indicates a work order. You can also use the document type to define the specific work order type, such as a regular work order or a quote for a work order. If Work Order Type (F40039.A201) is IN ("05", "06", "07") then F40039.CSOT = '1' else CSOT = '0' |
||
| Shipping | Carton Creation Status | A204 | UDC 46/RS (Blank) Blank 10 - Created 20 - Changed 30 - Approved |
A user defined code (46/RS) that specifies which status the system uses when creating cartons in the Carton Recommendations table (F4615). <Document 1184633.1> - E1: 49: Standard Pack Carton Recommendations (P4615/P4620/P46091/P460131/P460132/R46151) |
| Carton Change Status | A205 | UDC 46/RS (Blank) Blank 10 - Created 20 - Changed 30 - Approved |
A user defined code (46/RS) that specifies which status the system uses when changing cartons in the Carton Recommendations table (F4615). | |
| (check box) Recommend Standard Packs | A109 | 1 - Checked 0 - Unchecked |
Default Value is 0 <Document 1184633.1> - E1: 49: Standard Pack Carton Recommendations (P4615/P4620/P46091/P460131/P460132/R46151) |
|
| (check box) Enable Shipment Sequencing | DTSQ | 1 - Checked 0 - Unchecked |
Document Type Sequencing flag that indicates that the Document Type will enable manual entry or production sequencing fields PSJOBNO and JOBSQ. This control is to be disabled unless SY49 - Transporation is enabled through P99410 - EnterpriseOne System Control <Internal_Only>B4210390&B4900240 </Internal_Only> |
Document Type Exclusion Rules (P400391) enables you to bypass update of the Item History (F4115) file during inventory transactions. Since this routine is handled by XT4111Z1 - Inventory Master Business Function, any inventory transaction can invoke this functionality.
The document Type Maintenance program has been updated to provide form/row exits to Document type exclusion rules (P400391) which allows user overrides of document types at the branch and ALL branch level. In case you want to exclude all the branch/plant for a certain document type, you may define it as " ALL" .
F400391 - Document Type Exclusion Rules
| Column | Description | Detail |
|---|---|---|
| DCT | Document Type | DCT value which is defined in P40040 (F40039) - Document Type Maintenance |
| MCU | Business Unit | Specific Branch/plant to bypass Or " ALL" branch/plant for specific document type |
| EIHU | Exclude Item History Update | A flag to indicate that a specific Document Type is to be excluded from update to the F4115 Item History Update table when relieving inventory. You can set 'Y' for this column to exclude |
Refer to individual implemenation guides for additional information.
| Implemenation Guide | Detail |
|---|---|
| EnterpriseOne Applications Inventory Management Implementation Guide 2 Setting Up the Inventory Management System
2.8 Setting Up Document Type Information
|
This is main documenation on Document Type Maintenance |
| EnterpriseOne Applications Sales Order Management Implementation Guide 9 Entering Additional Orders
9.6 Entering Quote Orders
|
When the customer confirms the order, you convert the quote order into a sales order. You can also generate a sales proposal based on a quote order. Quote orders can be designated to relieve or not relieve quantity through the Document Type Maintenance program (P40040). |
| JD Edwards EnterpriseOne Applications Configurator Implementation Guide 6 Entering Orders for Configured Items
6.13 Entering Credit Orders for Configured Items
6.13.3 Prerequisites
|
Set up a document type for credit orders in the Document Type Maintenance program (P40040). The document type is usually CO. |
| EnterpriseOne Applications Requisition Self Service Implementation Guide 3 Setting Up Direct Connect and Purchase Order Dispatch
3.5 Setting Up Additional Information for PO Dispatch
|
you must verify that document type that you are using for purchase orders exists, and that the Publish Externally option for that document type is selected. You use the Document Types Maintenance program (P40040) to set up this information. The default document type for purchase orders is OP. You can use this document type, or create your own for purchase orders. |
|
9 Creating Purchase Orders
9.1 Understanding Purchase Order Creation
9.1.1 Using Purchase Order Dispatch
|
Select the Publish Externally option for the purchase order document type using the Procurement tab in the Document Type Maintenance program (P40040). |
| EnterpriseOne Applications Warehouse Management Implementation Guide 2 Setting Up Warehouse Management
2.16 Working with Standard Pack Carton Recommendations
|
The system generates the recommendation when creating shipments, based on the type of order established in the Document Type Master table (F40039) and whether you have activated carton recommendation processing for the document type in the Document Type Maintenance application (P40040). When you activate carton recommendations, you can: Select standard pack recommendations. The system recommends the innermost carton and any additional packaging layers that are set up in standard pack rules. Specify the Carton Creation Status. This is the status for recommendations created by the system. Specify the Carton Change Status. The status for recommendations that have been manually changed or Carton Detail has been created. Once the carton is at this status, the system does not automatically re-calculate packaging recommendations if the sales order quantity is changed for an item. Specify shipment sequencing. The system indicates that the document type enables manual entry of production sequencing fields Job Number (PSJOBNO) and Job Sequence (JOBSQ). |
|
6 Working with Putaway Requests
6.2 Creating Putaway Requests
6.2.2 Prerequisites
|
In the Document Type Maintenance program (P40040), set up document type |
| JD Edwards EnterpriseOne Applications Shop Floor Management Implementation Guide 5 Working with Work Orders and Rate Schedules
5.7 Entering Work Order Headers
|
You need to differentiate each type of work order, such as manufacturing work orders, rework orders, repair orders, engineering change orders, orders for prototypes, and so on, by assigning each of them a unique document type and work order type. You use the Document Type Maintenance program (P40040) to set up these document constants. |
| EnterpriseOne Applications Product Data Management Implementation Guide 3 Setting Up Product Data Management
3.6 Defining Document Type Constants for Work Orders
|
Document types are used in the software to specify particular types of transactions. You define the characteristics of document types in the Document Type Maintenance program (P40040). The document type constants defined in this program affect all software transactions. The order type for each of the document types must be defined so that the system knows how to process the activity for it. For example, the document type for a manufacturing work order can be set to WO for the correct transactions that relate to the processing of a manufacturing work order. To differentiate the various work order document types from each other, you assign a specific order type to each work order document type. For example, a manufacturing work order is associated with order type 02. The order type values for work order processing are stored in the UDC table 48/OT (Order Type) and are hard-coded |
|
3.8 Setting Up Engineering Change Management
3.8.2 Prerequisites
|
Ensure that the document type for ECOs is set up in Document Type Maintenance program (P40040). |
| JD Edwards EnterpriseOne Applications Service Management Implementation Guide 5 Managing Contracts
5.3 Managing Contracts
|
Contract Type Enter a value from UDC 00/DT (Document Type - All Documents) that identifies the type of document. The document types for service contracts are defined in the Document Type Master table (F40039) from the Document Type Maintenance program (P40040). |
|
6 Managing Work Orders
6.4 Setting Up Work Orders
6.4.3 Prerequisites
|
Set up work order document types in the Document Type Maintenance program (P40040) from the Work Order Setup menu (G1742). For each document type, enter 1 in the Work Order field. |
|
6.5 Creating Work Orders Using the Service Management Workbench Program (P90CD020)
6.5.6 Setting Processing Options for Service Management Workbench (P90CD020)
|
Order Type: Enter a value from UDC 00/DT (Document Type - All documents) that identifies the type of document. This code also indicates the origin of the transaction. JD Edwards has reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.) These document types should not be changed: P: Accounts payable. R: Accounts receivable. T: Payroll. I: Inventory. O: Purchase order processing. J: General accounting/joint interest billing. S: Sales order processing. |
|
6.9 Processing Work Orders
6.9.2 Prerequisites
|
Set up work order document types in the Document Type Maintenance program (P40040) from the Work Order Setup menu (G1742). Ensure that the document type on the work order is set to 1 in the Work Order field on the Document Type Maintenance program (P40040). |
| JD Edwards EnterpriseOne Applications Engineer to Order Implementation Guide 3 Setting Up Engineer to Order
3.1 Understanding Engineer to Order Setup
|
JD Edwards EnterpriseOne Engineer to Order enables you to use several different task types as part of the work breakdown structure. Each task type represents a different type of activity that is related to the project that might require different actions on the part of the project manager and responsible project employees. You can use only task types that are set up in the Document Type Maintenance program (P40040). |
| JD Edwards EnterpriseOne Applications Capital Asset Management Implementation Guide 4 Setting Up Capital Asset Management
4.2 Understanding UDCs for CAM
4.2.2 Work Order UDCs
|
Use these codes to differentiate between different types of work order transactions in the general ledger. For example, you can create document types for preventive maintenance work orders, corrective maintenance work orders, and so on. Work order document type is a key work order code. You define this code in the Document Type Maintenance program (P40040) to indicate that the work order is an equipment work order type. |
| EnterpriseOne Applications Real Estate Management Implementation Guide 9 Processing Tenant Work Orders
9.2 Entering Tenant Work Orders
|
Use the Tenant Work Order Entry program (P48201) to enter tenant work orders, compare completion to a projected schedule, and track task completion. You must use the Document Type Maintenance program (P40040) to set up the document type for tenant work orders in UDC (user-defined code) table 00/DT. |
| JD Edwards EnterpriseOne Applications Kanban Management Implementation Guide 4 Processing Kanban Transactions by Item
4.5 Releasing Quantity from a Blanket Order Using Kanban Processing
|
Specify the document type (UDC 00/DT) that you associate with the blanket purchase orders from which you will release quantity using kanban processing. If you create a new document type to represent blanket orders, whether for kanban processing or otherwise, you must set up that document type in the Document Type Maintenance program (P40040). |
| JD Edwards EnterpriseOne Applications Customer Relationship Management for Sales Implementation Guide 6 Managing Sales Opportunities
6.4 Creating Quotes and Sales Orders for Opportunities
6.4.2 Prerequisites
|
You must also set up Document Type Maintenance (P40040) for Sales Quotes. If you do not set this up, the system will not convert opportunities to quotes. To set up document types for Sales Quotes, enter 2 or 3 in the Order Category field on the Sales tab of the Document Type Revisions form. |
| EnterpriseOne Applications Business Interfaces Implementation Guide 12 Work Order - Service
|
In the EnterpriseOne system, work orders are stored in the Work Order Master table (F4801). When you create a work order, you must specify the document type that is associated with the work order. The system uses the value in the Document Type field (DCTO) to determine the order type of the work order. You use the Document Type Maintenance program (P40040) to maintain document type information. Document type records are stored in the Document Type Master table (F40039). When you enter a document type into the system, you can associate that document type with an order type. Order types might include manufacturing orders, equipment orders, and service work orders. To specify that the document type is associated with service work orders, enter 05 in the Order Type field. The getServiceOrder and processServiceOrder operations process only those work orders that have been defined as service work orders. Service work orders must include a document type that is associated with an order type of 05. |
|
77 Purchase Orders
77.3 Purchase Orders Real-Time Events
77.3.1 RTPOOUT
77.3.2 RTPOOUT2 |
The Document Type of the purchase order must be set up to publish externally. Use the P40040 application to inquire on a document type and select the publish externally check box on the Purchasing tab of the Document Type Revisions form. |