Net Change Flag (F4102.MRPC)

Purpose of Document

This document is to explain F4102.IBMRPC - NetChangeFlag (Flag - Net Change) and possible error which may be related with EnterpriseOne business function B4000930 - UpdateF4102MRPNetChg (F4102 Update MRP Net Change) which can be called across systems.

Question 1. Do EnterpriseOne applications try to update this column though the Manufacturing Module not implemented?

Answer 1. Yes. Regardless activation of Manufacturing this flag will get updated.

Question 2. Is there way to update F4102.MRPC using standard application?

Answer 2. Yes, You may set ' ' (a space) through Net Change Review (P3402); however this column may not be appeared in Item Branch/Plant (P41026). To set it a blank, highlight the row(s) you want to update and (row exit, click) 'Upd Net Change'.

Question 3. Why this flag F4102.MRPC is important?

Answer 3. When running R3482 - 'MRP/MPS Requirements Planning' or R3483 - 'Master Planning Schedule - Multiple Plant' there will be at least two versions one is 'Net Change' and the other is 'Gross Regeneration' depends on processing option item #1. Generation Mode from 'Parameters' tab. Currently 1 is Net Change Mode and 2 is Gross Regeneration Mode.

If you select 'Net Change' Mode Supply/Demand will be computed only for the item Branch Plant records where F4102.IBMRPC='1'.

At the end of process of R3482/R3483, this flag will be set ' ' so if there is any transaction is related with Supply and Demand this flag is to be set '1'.
The main consideration is that it may take long time in processing R3482/R3483. So exclude item branch if there is no change from last running to as-if now.

Question 4. What kind of transaction involves updating the MRPC column?

Answer 4. Any transaction which affect supply/demand has this implementation.
<Internal_Only>Refer to E1: 34: P4021 - Supply & Demand Technical FAQ Document 952806.1. This is an internal document.</Internal_Only>

Question 5. How do you track down issues when the process of UpdateF4102MRPNetChg causes Record Locking, Deadlock, blocking (with timeout error or web client exception)?

Answer 5. Look for the latest ESU which is related with this transaction. If issue is coming from the application belong to Manufacturing make it sure that Transaction Processing is off. Refer to E1: 30: FAQ - Transaction Processing in Manufacturing Module Document 989586.1.

In case the issue can be simulated at will; capture the jdedebug log (or callobject kernel log), which shows whether there is any possible code may cause blocking (that is, in a single transaction there can be two different routines to update F4102 so second request may try to get locking information - deadlock).

Question 6. Which Business Functions update F4102.IBMRPC?

Answer 6. Currently the F4102.MRPC flag can be updated via:

• B4000930 - UpdateF4102MRPNetChg (F4102 Update MRP Net Change)
• B3100170 - SetNetChangeFlag (F4102 Update Net Change Flag): Purchase Order and Manufacturing product family
• B3400600 - MPS_SetNetChangeFlag (MPS, Set Net Change Flag): Limited to MPS (R3484 (MPS Set Net Change Flag) is the only application which is calling this function directly)
• Direct update from a certain routine: For example, XT4111Z1 - F4111EndDocument (F4111 End Document) has own code through Bug 11033723 P4114 SLOW PROCESSING - which used to call B4000930 for performance gain

Question 7. Which Master business functions have routines to update F4102.MRPC?

Answer 7. Listed Master Business Function below is to simplify actual routine which updates F4102.MRPC and this is to give application usage

• Application ID Description (where master business function calls B3100170 - SetNetChangeFlag )
• B3401200 - F3460EditLineAndUpdate (F3460 Edit Line And Update)
• B3401360 - ProcessMessagesEditLine (Process Messages Edit Line) when message type code is 'O - Order', 'B - Order & Expedite', 'D - Defer' or 'E - Expedite'
• B4800210 - X4801MfgEndDocModule (X4801 Manufacturing End Doc Module) called by B31P0080 and X4801
• N90CD018 - CRMCreatePurchaseOrder (CRM Create Purchase Order)
• XT4311Z1 - F4311EndDoc (F4311 End Document)
• Application ID Description (where master business function calls B4000930 - UpdateF4102MRPNetChg)
• B3101260 - F3111EditDoc (F3111 Parts List Edit Doc), called by N3001780
• B3102270 - F3111WOIssuesEndDocument (F3111 WO Issues End Document)
• B4205160 - ProcessSOMBFCommitment_Commit (Process Sales Order MBF Commitment - Commit), called by B4200311
• N3002040 - F3002EndDocument (F3002 End Document)
• N3003700 - F3002UpdateIndividualSubstitute (F3002 Update Individual Substitute)
• N3401430 - F3460ForecastMBF (F3460ForecastMBF)
• N4200790 - ShipConfirmEndDoc (Shipment Confirmation End Document)
• N4200860 - BackorderReleaseEndDoc (Backorder Release End Doc)
• XT4312Z1 - F4312EndDoc (F43121 End Document)
• XT4111Z1 is called by below master business functions depends on input parameter cUpdateMRPNetChange is '1' and list of objects which assigns cUpdateMRPNetChange = '1' are
• B3100770 - B3100770CompletionsEndDoc (F4801 End Document)
• XT4113Z1 - F3113FSEndDoc (F4113 FS End Doc)
• XT4114Z1 - F4114EndDocument (F4114 End Document)
• XT4116Z1 - F4116FSEndDoc (F4116 FS End Doc)
• Application ID Description (where master business function calls B3400600)
• R3484: MPS Set Net Change Flag
• Application ID Description (Which update F4102.MRPC in the routine): List of object written here can JDE APIs to update F4102.MRPC directly

Question 8. Is there an object list?

Answer 8. The below objects can be called to update MRP Net Change Flag (F4102.MRPC)

Objects List:

Question 9. How to overcome possible deadlock when two different MBF tries to update F4102.MRPC within a Transaction?

Answer 9. Multiple applications can call multiple master business functions (MBFs) as listed above, which in return have transaction failed. For example,

• ShipConfirmEndDoc (N4200790 - Shipment Confirmation End Document) can call F4311EndDoc (XT4311Z1 - F4311 End Document) and F4312EndDoc (XT4312Z1 - F4312 End Document) for ST/OT (Transfer Order) transaction
• Purchase Order Receipt for ETO order (where Work Order Number is populated) can call F4312EndDoc and F3111EndDoc (B3101260 - F3111 Parts List End Doc) where both MBF tries to update F4102.MRPC

In case you face any deadlock (Transaction Failure) for routines explained above, do apply Bug 11007632 - ETO DEADLOCK BY PO RECEIPT, included in 9.0, which sets update of F4102.mrpc for B4000930 - UpdateF4102MRPNetChg (F4102 Updata MRP Net Change) and <Bug 13490757>: DATABASE RECORD LOCK UPDATING NET CHANGE FLAG MRPC ON PURCHASE ORDER AND PARTSLIST for B3100170 - SetNetChangeFlag (Set Net Change Flag) at outside Transaction Processing boundaries through below code:

idJDBReturn = JDB_InitUser((HENV) lpBhvrCom->hEnv, &hUser, (JCHAR *)NULL, JDEDB_COMMIT_AUTO);