Bottler
Member
Hello All,
This is my first JDEList posting so please be gentle.
My problem is as follows:-
I am running the R42520 (Print Pick Slips) UBE with processing options 1 & 2 on the 'Process' tab set to "1". This enables the hard commitment of inventory, and turns on the preference commit processing.
When running the UBE over any given sales order the preference commit logic is overriding the Unit Cost (F4211.UNCS) field on the sales order with a different value to the one that was populated into the unit Cost field when the sales order was originally entered.
I wish to leave the preference commit processing on, but to retain the value of the F4211.UNCS field that was set when the sales order was entered.
The business analyst who referred the problem to me said that he had experimented with the preferences set up and had consulted the JDE Manual, but was unable to 'turn off' the F4211.UNCS override.
I was asked to debug R42520, and found the following:-
When the preference commit processing is 'turned on' R42520 retrieves a unit cost from the UNCS field of the F4105 (Item Cost File). The way that it selects the records from F4105 is as follows:-
WHERE F4105.ITM = F4211.ITM AND F4105.MCU = F4211.MCU
The primary key of F4105 (ITM, MCU, LOCN, LOTN, LEDG) is being used to retrieve records, and the unit cost will ALWAYS come from the UNCS field of the first record that is returned. This often does not match the unit cost that is on the sales order.
The unit cost from F4105 is then written into an interim workfile (F42UI130) which is then used by the 'F42UI130 F4211 SO Detail Line Split' business function to update the F4211.UNCS field on the sales order.
The logic that selects records from the F4105 file is part of an internal function (IB4200780_GetItemCostFromF4105) within the B4200780 (F42UI130 Get/Update Commitment Work File) business function. As far as I can tell (having looked at the source code) this logic will always be executed whenever the preference commit processing is 'turned on' for R42520.
My questions are:-
1) Is there any way that I can guarantee that the unit price from the sales order will not be overridden by the preference commit processing (without having to make any code changes)?
So far the only solution that I have come up with is to create a record in F4105 which has the right unit cost and will always be picked up first. This is not ideal, as there may still end up being a mismatch between the unit cost on the F4105 record and that on the F4211 record.
2) Does anybody know of any decent documentation covering the Preference Commit set-up? Just for future reference. I promised the business analyst that I would give him an overview of the preferences logic, but it could take me a long time to determine what that logic is.
Hopefully this explanation isn't too garbled, and nobody has fallen asleep reading it!
Thanks in advance
Bottler
This is my first JDEList posting so please be gentle.
My problem is as follows:-
I am running the R42520 (Print Pick Slips) UBE with processing options 1 & 2 on the 'Process' tab set to "1". This enables the hard commitment of inventory, and turns on the preference commit processing.
When running the UBE over any given sales order the preference commit logic is overriding the Unit Cost (F4211.UNCS) field on the sales order with a different value to the one that was populated into the unit Cost field when the sales order was originally entered.
I wish to leave the preference commit processing on, but to retain the value of the F4211.UNCS field that was set when the sales order was entered.
The business analyst who referred the problem to me said that he had experimented with the preferences set up and had consulted the JDE Manual, but was unable to 'turn off' the F4211.UNCS override.
I was asked to debug R42520, and found the following:-
When the preference commit processing is 'turned on' R42520 retrieves a unit cost from the UNCS field of the F4105 (Item Cost File). The way that it selects the records from F4105 is as follows:-
WHERE F4105.ITM = F4211.ITM AND F4105.MCU = F4211.MCU
The primary key of F4105 (ITM, MCU, LOCN, LOTN, LEDG) is being used to retrieve records, and the unit cost will ALWAYS come from the UNCS field of the first record that is returned. This often does not match the unit cost that is on the sales order.
The unit cost from F4105 is then written into an interim workfile (F42UI130) which is then used by the 'F42UI130 F4211 SO Detail Line Split' business function to update the F4211.UNCS field on the sales order.
The logic that selects records from the F4105 file is part of an internal function (IB4200780_GetItemCostFromF4105) within the B4200780 (F42UI130 Get/Update Commitment Work File) business function. As far as I can tell (having looked at the source code) this logic will always be executed whenever the preference commit processing is 'turned on' for R42520.
My questions are:-
1) Is there any way that I can guarantee that the unit price from the sales order will not be overridden by the preference commit processing (without having to make any code changes)?
So far the only solution that I have come up with is to create a record in F4105 which has the right unit cost and will always be picked up first. This is not ideal, as there may still end up being a mismatch between the unit cost on the F4105 record and that on the F4211 record.
2) Does anybody know of any decent documentation covering the Preference Commit set-up? Just for future reference. I promised the business analyst that I would give him an overview of the preferences logic, but it could take me a long time to determine what that logic is.
Hopefully this explanation isn't too garbled, and nobody has fallen asleep reading it!
Thanks in advance
Bottler