In EnterpriseOne, F4102 - Item Branch File and F41021 - Item Location File can be created on the Fly. This document is to explain when it gets created and what are the conditions for this. The document provides answers to frequently asked questions on this functionality.
Question 1: What are the inventory transactions which affect creation of F4102/F41021?
Answer 1:
Trans
Application
F/T
F4102
F41021
Conditions
1
P4112 - Inventory Issues
F
Y
Y
cLocationInCache='1'
2
P4114 - Inventory Adjustment
T
Y
Y
8
P4242 - Transfer Order
T
Y
Y
16
P49660 - Load Disposition
T
Y
Y
3
P4113 - Inventory Transfer
F/T
Y
Y
12
P4116 - Inventory Reclassifiction
F/T
Y
Y
cFromTo='F'
4
P4312 - Purchase Order Receipt
T
Y
4
P4314 - Voucher Match
T
Y
4
P43253 - Routing Disposition
T
Y
4
P43250 - Receipt Routing Movement and Disposition
T
Y
5
P4205 - Shipment Confirmation
F
N/A
N/A
13
R42800 - Sales Update
F
N/A
N/A
19
P4205 - Shipment Confirmation
F
N/A
N/A
*Serial
19
R42800 - Sales Update
F
N/A
N/A
*Serial
6
R41413 - Cycle Count Update
T
Y
7
R41610 - Tag Count Update
T
Y
9
P31113 - Work Order Inventory Issues
T
N/A
N/A
*Completion
10
P31114 - Work Order Completions
T
N/A
N/A
*Completion
11
P31113 - Work Order Inventory Issues
T
N/A
Y
*Issue
14
P4205 - Shipment Confirmation
F
N/A
N/A
14
P42800 - Sales Update
F
N/A
N/A
15
P4312 - Purchase Order Receipt
T
N/A
Y
*In Routing
15
P4314 - Voucher Match
T
N/A
Y
*In Routing
15
P43253 - Routing Disposition
T
N/A
Y
*In Routing
15
P43250 - Receipt Routing Movement and Disposition
T
N/A
Y
*In Routing
17
P49660 - Transportation Compartment - Based Load
T
N/A
N/A
20
DFM - Completion
F
N/A
Y
21
DFM - Issue
F
N/A
Y
Note:
1st Column "Trans" is "nTransaction" in XT4111Z1 - F4111EditLine
3rd Column "F/T" is to indicate the direction of transaction F - From and T - To
4th Column and 5th Column are cAllowItemBranchAdd and cAllowItemLocationAdd respectively
Some Transactions are not related with this category thus set as "N/A" - Not Available
DFM - Demand Flow Manufacturing
Condition cLocationInCache for P4112 is implemented through Bug 10901470 : BLEND WT ISSUES-LOCATION ERROR - SAR: 7813661. In general, P4112 is from side transaction to it is not allowed to create item location on the fly.
Note: Per Bug 11043796/SAR 8963654: When the item branch record is created on the fly, the item details will be copied from Item Master and not from the From branch of Inventory Transfer. So the category codes populated in Item Master will default to the new branch record. This functionality is same as we add a new item branch record through Item Branch (P41026) application.
Here also all the item details will be defaulted to Item Branch from Item Master. In the SAR scenario, to default the PRP6, PRP7, PRP8, PRP9, PRP0, SRP6, SRP7, SRP8 and SRP9 category codes, user needs to set these values in the Item Master category code. So the category codes will be defaulted to the newly created item branch.
The Enh <Bug 12516444> - PREVENT CREATE LOC ON THE FLY - SAR: 7449484 is rejected
Question 2: What are the exclusive conditions in creating Item Branch Records (F4102)?
Answer 2:
When Branch/Plant is warehouse Branch. It does not allow the user create a branch on the fly. Since this would only create the F4102 records without creating all the necessary warehouse setup to make use of this newly added branch/plant. This information is coming from F41001.WCTL - Control Code - Warehouse Management is '1' to determine whether B/P is meant for Warehouse management or not
If a certain item is Non-stock item (e.g., F4101.STKT - Stocking Type = 'N' - Non-Stock Item) then do not allow F4102 gets created. In this case, a certain application will issue error '4080 - Branch / Plant and Item Inconsistent'
Bulk Transfer
Addition takes places in P31113/P31114
Question 3: Will system issues any warning message before Item Branch Record gets created to have the user to decide to proceed it or not?
Answer 3: Yes, if Bug 10980836/SAR 8721700 is in place, warning "121D - Item Branch Record Not Found - WARNING". This warning message will be issued even when Lot Number is not blank.
Question 4: What are other conditions to create Item Branch Records on the Fly?
Answer 4:
It has to meet above metrics
Stock Item
Not warehouse Branch/Plant
Not Bulk Transfer
Error Code '0294 - Error: Item Branch Record Does Not Exist' is not issued. Except P31113/P31114, applications listed above will check whether there is existing data from F4102 and the direction are transaction is not 'T' then Item Branch record is not be created on the fly.
Question 5: Does system issue a warning message before it creates an Item Location record (F41021)?
Answer 5: Yes it issues warning '0678 -Warning: Item Location Record Not Found'
Question 6: What are other conditions which may not allow the users to create Item Location records (F41021)?
Answer 6:
Application ID has to meet above metrics
Error '3138 - Error: Invalid Location' is not to be issued in validating Location
Stock Item
Not warehouse Branch/Plant
Not Bulk Transfer
Note: when a record is inserted/updated into F41021, Cardex F4111 is to be inserted
Question 7: The Item Location (F41021) was set Primary location for a specific location when to-side-transaction holds specific location (and lot) during inventory transaction. Is there way to set blank location and lot as primary location into F41021 (Item Location)?
Answer 7:
To set blank location and lot as primary location,
Add Blank Location and Lot using P41024
(Row Exit) Change Primary using same application
cf., Follow the workaround steps in <Document 2146010.1> - E1: 41: Cannot Add Primary Location - Workaround, in case missing location is concern.
Note:
Depends on calling BSFN(e.g., XT4114Z1 - F4114EditLine (F4114 Edit Line)) of XT4111Z1 - F4111EditLine input parameter of FTRN - cFromSideOfTransfer = '1' or cFromTo='F' can be specified to hard code whether to allow creation of Item Branch or Item Location File on the fly
Do not change any code which is given as example, as it may cause discripancy among F4101/F4102/F41021/F4111 and so on
Oracle is not responsible any mismatching data which are caused by modification of standard code