E1: 41: Certain Users Receive Error 084M & 2067 When Trying to Add Item Branch Record from Item Master - CASE STUDY

(Doc ID 2380322.1)

Last updated on MARCH 29, 2018

Applies to:

JD Edwards EnterpriseOne Inventory Foundation - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

This document is a case study only and same shall not encompass possible cause and resolution. This document can be useful only when the issue is user specific and issue is caused by corrupted data or database cache.

P41026 issues errors,

Error    Branch/Plant M30 Invalid Warning
          A form level error has occurred.
          CAUSE: Branch/Plant M30 is not set up in the Constants file.
          RESOLUTION: Set up Branch/Plant in the Constants file.
          ER Details:
             Form P41026_W41026A
             Control Id 162
             Control Title GetItemMasterInfo
             Event Button clicked
             Line No 36
         BSFN Details:
             Source File b4101390.c
             Source Line 273
             Error ID 084M
Error    Item Number Invalid Warning
          A form level error has occurred.
          CAUSE. . . . . The Item Number entered does not exist in the Basic Item Master
          (P4101).
          RESOLUTION . . Enter a valid Item number or add the Item to the Basic Item
          Master (P4101).
          ER Details:
              Form P41026_W41026A
              Control Id 162
              Control Title GetItemMasterInfo
              Event Button clicked
              Line No 36
              BSFN Details:
              Source File n4101060.c
              Source Line 33650
              Error ID 0267
              BSFN DSTR Item 11

when adding Item Branch for existing item number using P41026. This issue is a user specific and the copied user based on problematic user ID does not have issue.

This screen shows the item is valid because it does not issue error so the error in below figure is not reflecting actual issue. 

Above print screen shows that the Branch and Item both appear to be correct.

 

Note:

  • When you receive more than two errors, try to fix the first error.
  • When a certain issue is user specific, possible cause come from the settings from user profile (P0092), security settings (P00950), user override (P98950), and default branch and routing (P400951).
  • In case you do not find any clue from the screen, capture additional log after verifying the source of error (in your clicking yellow triangle),
    • JASDEBUG.log when issue is coming from specification including event rule without having a specific business function
    • JDEDEBUG.log majority of error is handled by business function because validation is done through business functions.
  • So for this case study, jdedebug.log is essential to know the root cause of it.

 

 

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms