Ask Denovo's own Carin Wagner spoke at the SoCal User Group the first week of March. Her presentation was shared on LinkedIn, an issue she has dealt with for over 24 years that she solved with a Logic Extension. As this was very well-received, we asked her to do a recording of that Logic Extension. First, the business case which prompted this post, in her words:
In 2001, I was a Business Analyst at a consumer electronics company running JDEdwards OneWorld Xe. The inventory manager asked if the Reason Code in the inventory adjustment screen (P4114) could be required without customization. The short answer I gave was, "Sure, I just need to remove the BLANK option from the UDC table 42/RC!" Once I did that, all sales folks got red errors on all their screens. I didn't realize this UDC was shared between inventory AND sales AND purchasing tables. I had to put the BLANK value back, and I had to break the news that I couldn't make the Reason Code required in Inventory Adjustments without modification. I became a consultant in late 2002, and I was asked this SAME question for years - clients have all really wanted Reason Code to be a required field, preferably without modifying P4114.
Fast forward 24 years. I was going to present the same-ole Logic Extension OBE (Oracle By Example) I've seen a number of times when I wondered if I could finally solve my P4114 issue. The video attached here is the answer to my VERY long pursuit of a non-development solution to make Reason Code on P4114 required.
Click here to watch the video!
In 2001, I was a Business Analyst at a consumer electronics company running JDEdwards OneWorld Xe. The inventory manager asked if the Reason Code in the inventory adjustment screen (P4114) could be required without customization. The short answer I gave was, "Sure, I just need to remove the BLANK option from the UDC table 42/RC!" Once I did that, all sales folks got red errors on all their screens. I didn't realize this UDC was shared between inventory AND sales AND purchasing tables. I had to put the BLANK value back, and I had to break the news that I couldn't make the Reason Code required in Inventory Adjustments without modification. I became a consultant in late 2002, and I was asked this SAME question for years - clients have all really wanted Reason Code to be a required field, preferably without modifying P4114.
Fast forward 24 years. I was going to present the same-ole Logic Extension OBE (Oracle By Example) I've seen a number of times when I wondered if I could finally solve my P4114 issue. The video attached here is the answer to my VERY long pursuit of a non-development solution to make Reason Code on P4114 required.
Click here to watch the video!
If this use case is making you think of more applications of Logic Extensions, let us know! We can help if you get stuck!
If you need a question answered in the series or just want to subscribe for alerts on future articles, simply fill out the form below! Denovo is here for YOU!