R3483 Case Study on MRP Messages for ST/OT/WO - How to Maintain Integrity
Purpose of Document
The purpose of this document is to explain how JD Edwards EnterpriseOne maintains integrity among Sales, Procurement and Manufacturing in creating OT message through P3411 (MRP/MPS Detail Message Revisions).
Issue
In generating MRP message for ST/OT (Sales Transfer Order) through P3411 (MRP/MPS Detail Message Revisions), which sets F4801.RORN (RelatedPoSoNumber) = '00000000'
Expected Behavior
The ST number should be populated in the work order Related Order number field, F4801.RORN, because this is the only way to trace the relationship between a sales order (ST) or work order (WO).
Business Scenario
There is regular demand for an item:
Manufactured (Stocking Type = M)
ST to supply in branch/plant M10
OT for demand in branch/plant M30
Create an item (e.g., MPS-DM3).
Create 2 item branch records (e.g., M10 for Supply and M30 for Demand).
M10 belongs to company 00001 and set Address Number 6058 through P41001 (Branch/Plant Constants).
M30 belongs to company 00200 and set Address Number 6074.
(Optional) Create bill of material (BOM) against the above parent item (for this example, omit this).
(Optional) Create routing (P3003) against the above parent item (for this example, omit this).
(Optional) To increase on-hand quantity (F41021.PQOH), adjust quantity through Adjustments (P4114) on From Branch/Plant (M10).
Create Branch Relationship through P3403T (Suppy Branch = M10, Demand Branch = M30 (if needed) Transfer Lead Time).
Create demand. For this example, add forecast for future Request Date (P3460) against Demand Branch M30.
(Optional) Check supply/demand through P4021 for both Supply Branch and Demand Branch.
Run R3483 to create MRP message (check processing option again).
Verify MRP messages created through Detail Messages (P3411).
Action
Item Number
Msg Typ
Message
Hold Code
Message Processed
Required Quantity
UM
Order Number
Or Ty
W.O. Status
Demand Branch
Supply Branch
Before (by R3483)
MPS-DM3
O
Order
A
7
EA
OT
10
M30
M10
After (by P3411)
MPS-DM3
P
Firm Order
A
Y
7
EA
2215
OT
M30
M10
In P3411, use the row exit to display Generate Message(s).
Verify purchase order (and related sales order).
Verify work order based on related order (F4801.RORN with lpad (F4211.DOCO, 0, 8).
E1: 34: P3403T Branch Plant Relationships for Multi Plant MRP R3483 Document 627257.1
E1: 42: Transfer Orders (ST/OT) (P4210/P4310/P4205/P4312) Document 625593.1
Excerpt: "A Transfer Order is an internal sales order used to transfer inventory from one warehouse (branch) to another. The Transfer Order (P4210) program creates both a sales order in the "From Branch" (shipping branch) and a purchase order in the "To Branch" (receiving branch). The default document types created are ST (sales order) and OT (purchase order), and are often referred to as an ST/OT order. When a sales transfer order (ST) order is created, the purchase transfer order (OT) is also created, regardless of whether the "Generate Purchase Order" flag is activated or not in the Line Type Constants (P40205).
Differences between Sales Transfer and Inventory Transfer
Functionality
Sales Transfers (P4210/P4310)
Inventory Transfers (P4113)
Includes revenue and cost accounting entries
Both
Cost Only
Transfers items between companies with different currencies
Yes
No
Transfer within the same warehouse/branch plant
No
Yes
Transfer from one warehouse to another
Yes
Yes
Ability to include a line for freight cost when transfer involves shipment from one warehouse to another
Yes
No
Printed document available for the receiving warehouse
Yes, Receiver Print (R43510)
No
Further detail on sales transfer, refer to E1: 42: Transfer Orders (ST/OT) (P4210/P4310/P4205/P4312) Document 625593.1
Simplified Flow based on MBF (Master Business Function)
P3411 - MRP/MPS Detail Message Revisions
P4210|ZJDE0007 - Sales Transfer
Purpose
1. ProcessMessagesEditLine
2. F4211FSEditLine
3. F4211FSBeginDoc
3. F4311EditLine
4. F4311FSBeginDoc
5. F4301GetNextNumber
3. F4801BeginDocument
3. F4801EditLine
4. X4801MfgEditLineModule
2. F4211EditDoc
3. F4201GetOrderNoFromNextNumber
2. F4211FSEndDoc
3. F4311ZUpdateRelatedOrderInfo
3. F4801EditLine
3. F4801EndDocument
4. F4801GetNextWorkOrderNumber
4. X4801MfgEndDocModule
INSERT F4801/F4801T
INSERT F4211
3. F4801ClearWorkFile
INSERT F4201
3. F4311EndDoc
INSERT F4311/F4311T/F4301
4. UpdateSOHeaderWithRelatedPOInf
UPDATE F4201
3. F4311ClearWorkFiles
1. F4211FSBeginDoc
2. F4201GetOrderNoFromNextNumber
1. F4211FSEditLine
2. F4311EditLine
3. F4311FSBeginDoc
4. F4301GetNextNumber
2. F4801BeginDocument
2. F4801EditLine
3. X4801MfgEditLineModule
1. F4211EditDoc
1. F4211FSEndDoc
2. F4311ZUpdateRelatedOrderInfo
2. F4801EditLine
2. F4801EndDocument
3. F4801GetNextWorkOrderNumber
3. X4801MfgEndDocModule
INSERT F4801/F4801T
INSERT F4211
2. F4801ClearWorkFile
INSERT F4201
2. F4211SOEInternalFunctions
2. F4311EndDoc
INSERT F4311/F4311T/F4301
3. UpdateSOHeaderWithRelatedPOInf
UPDATE F4201
2. ENTER: F4311ClearWorkFiles
2. ENTER: F4801ClearWorkFile
B4200310 - F4211 Begin Document
B4200030 (F0002 Get F4201 Next Number)
B3401360 - Process Messages Edit Line)
B4200310/B4200311 - F4211 Edit Line)
B4200310 - F4211 Begin Document
XT4311Z1/XT4311Z2 - F4311 Edit Line
XT4311Z1 (F4311 Begin Document
B4300050 (F0002 Get Purchase Order Next Number)
X4801 (F4801 Begin Document)
X4801 (F4801 Edit Line)
B4800210 (X4801 Manufacturing Editing Module)
B4200312 (F4211 Edit Doc)
B4200030 (F0002 Get F4201 Next Number)
B4200310 (F4211 End Document)
B4201250 (F4311Z Update Related Order Info
X4801 (F4801 Edit Line)
X4801 (F4801 End Document)
B4800150 (F4801 Get Next Work Order Number)
B4800210 (X4801 Manufacturing End Doc Module)
X4801 (F4801 Clear Work File)
B4200311 - F4211SOEInternalFunctions
XT4311Z1 (F4311 End Document)
B4206080 (Update SO Header with Related PO Inf)
XT4311Z1 (F4311 Delete Work Files)
X4801 - F4801 Clear Work File
For this process, at least 4 different master business functions are to be called,
Sales Order: B4200310/B4200311/B4200312
Purchase Order: XT4311Z1/XT4311Z2
Work Order: X4801/B4800210
(MRP) Messages: B3401360
Refer to Document 1265902.1- E1: BSFN: Master Business Function in EnterpriseOne.
Begin Doc is to be called by Edit Line if it has not been called earlier than Edit Line, which validates/defaults header information and store it into cache.
Data for Key values from F4211, F4311 and F4801
Table
Column
Description
From
Others
F4211
KCOO*
Order Co
00001
F0006.CO on MCU = From B/P (M10)
DOCO*
Order Number
1698
(refer below note)
DCTO*
Order Type
ST
Based on Default Order Type defined for the version specified in processing option of P3411
MCU
Business Unit
M10
From Branch (= Supply Branch)
RKCO
Co Key (Related Order)
00200
= F4311.KCOO
RORN
Related PO/SO No
lpad(F4311.DOCO, '0', 8) e.g., 00002215
RCTO
Rel Ord Type
OT
F4311.DCTO, Determines by Default Order Type based on processing option of P4210 defined for P4310
AN8
Sold To
6074
F41001.AN8 on MCU = To B/P (M30)
SHAN
Ship To
6074
Same with AN8
DRQJ
Request Date
22/02/2013
For this example, request date from Demand Forecast
TRDJ
Order Date
19/02/2013
LNTY
Line Type
'W' to trigger Work Order
Value defined associated version of P4210 for Sales Transfer Refer to Line Type Constant
VEND
Primary Supplier
6058
(F41001.AN8 on MCU = M10)
F4311
KCOO*
Order Company
00200
F0006.CO on MCU = To B/P (M30)
DOCO*
Order Number
2215
DCTO*
Order Type
OT
MCU
Business Unit
M30
To Branch (= Demand Branch)
RKCO
Co Key (Related Order)
00001
RORN
Related PO/SO No
00001698
RCTO
Rel Ord Type
ST
AN8
Address Number
6058
F41001.AN8 on MCU = Supply Branch (=M10)
SHAN
Ship To Number
6074
F41001.AN8 on MCU = Demand Branch (=M30)
DRQJ
Request Date
22/02/2013
F4801
DOCO*
Order Number
4909457
DCTO
Order Type
WO
Processing Option of P48013. The version of P48013 can be defined in both P3411 and P4211
RORN
Related PO/SO No
00001698
Sales Order Number
RCTO
Rel Ord Type
ST
Sales Order Type
CO
Co
00001
MCU
Business Unit
M10
Supply Branch = Manufacturing Branch
MMCU
Branch
M10
Mother Branch is same with Supply Branch
DRQJ
Request Date
20/02/2013
VR01
Reference
Same with F4801.RORN
Difference between Sales Transfer creation between P4210 and P3411
Transaction Processing (rollback take place when P4210 fails to commit a certain record whereas P3411 shall not not rollback any data). Refer to Document 1320968.1 - E1: DB: Listing of Applications with Transaction Processing by EnterpriseOne Release
Order Numbering: In getting a new sales order number, mnNextNumberingIndexNo is determined by F40203.ORNN (OrderTypeNextNumber) from Order Activity Rules. It is important to set same value of F40203.ORNN for any line types otherwise order number shall not be in synchronize. For example, if you set F40203.ORNN = 2 for 'S' line type and F40203.ORNN = 6 for 'W' line type, F4211.DOCO may have totally different numbering. Same rule applies to Purchase Order Number
Work Order Number: mnNextNumberingIndexNo is hard coded with '1' and ECO Order Number '6' so regardless routine which creates work order header same next number can be fetched
Related Order Information from Sales Order file contains Purchase Order. As a result, F4801.RORN is only entry which enables you to check the source of transaction (i.e., Sales Order)
Changes
The latest ESU has been applied for Sales Order application.
Cause
Dependency among B4200310/B4200311 (Sales Order Master Business Function), X4801/B4800210 (X4801 Work Order Entry Master Business Function) and B3401360 (Process Messages MBF).
Solution
It is important to apply all related ESUs based on master business function when having this type of transaction.
It is important to capture callobject kernel log (namely, JDEDEBUG log) in hitting any integrity issue for this routine.
If possible, trace both P4210 and P3411 routines.
Master business function for Sales Order, Purchase Order and Work Order make use of cache heavily, so through callobject kernel log it should be possible to narrow down the exact routine which has the problem.
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the E1 Manufacturing Community.
To look at upcoming or archived Advisor Webcasts please see Advisor Webcast Details Document 1450327.1 if your topic is not currently scheduled please suggest it.
<Internal_Only>Along the way (or upon request), we may add additional information on this routine.</Internal_Only>