Address Invalid Error message upon exiting from ALKY exiting on P4210
Purpose of Document
The audience for this note is someone with developer level knowledge.
Symptoms
Upon exiting Form Control "ALKY- Address Number", system issuing Error message "Address Number - Invalid" as below:
Error ID: 0037 Description: Address Number - Invalid Source File:\\DeploymentServer\E1Release\PathCode\Source\n0100061.c Source Line: 1762 Event: Control Exited/Changed-Inline(or Asynch)
But this error message does not reflect actual root cause of issue, that is, there is valid address book number from F0101 - Address Book Master. So this document is to explain possible cause of error which may be issued during runtime or newly implemented environment.
Solution
This type of error comes:
Either information from table F0009 - General Constants is not valid
Or Environment Cache information is to be reset
So to fix this issue, verify that Address Book Constant information is valid as below:
F0009.GCSYNM - Symbol to Identify A/B Short Number is Blank
F0009.GCSYMA - Symbol to Identify Alternate Key is '*'
F0009.GCSYMT - Symbol to Identify A/B Tax ID is '/'
Note: The error message does not reflect actual issue.
To determine whether the issue is caused by corrupted data of F0009 - General Constants, change value "4242", "/4242" or "*4242".
If one or two above tests do not issue error, then verify whether all the symbols are correct
If error persists then:
Go to Address Book Constant (Fast Path: 1K)
Click OK
Log off/on
For this example, the error has come under below scenario:
The flow of NER N0100061 - ScrubAddressNumberNER (Scrub Address Number)
F0009.Fetch Single VA evt_ProductCode = TK Product Code /* Assign Blank */ VA evt_Symbol_ABAltern_SYMA <- TK Symbol to Identify A/B Alternate Key VA evt_Symbol_ABTaxI_SYMT <- TK Symbol Used to define A/B Tax ID VA evt_Symbol_ABShor_SYMN <- TK Symbol Used to define A/B Short Number If SV File_IO_Status is equal to CO SUCCESS // Scrub Validate Alternate Address Key VA evt_syma = rtrim([VA evt_Symbol_ABAltern_SYMA],'0') VA evt_symt = rtrim([VA evt_Symbol_ABTaxI_SYMT],'0') VA evt_symn = rtrim([VA evt_Symbol_ABShor_SYMN],'0') // Get the first character passed in. VA evt_LeadingCharAltAddress = substr([BF szAlternateAddressKey],0,1) // If the input selection is 1 or 5 then ALKY is being used for input an // We need to find the F0101 record based on what was passed in and what // current default format is in the A/B constants. We will then pass bac // default format for display in the ALKY parameter If BF cInputSelection is equal to "1,5" If VA evt_LeadingCharAltAddress is equal to VA evt_syma Or VA evt_LeadingCharAltAddress is equal to VA evt_symn Or VA evt_LeadingCharAltAddress is equal to VA evt_symt If VA evt_LeadingCharAltAddress is equal to VA evt_syma VA evt_StrippedAltAddKey = ltrim([BF szAlternateAddressKey],[VA // Fetch From F0101 By ALKY F0101.Fetch Single VA evt_AddressNumber <- TK Address Number VA evt_StrippedAltAddKey = TK Long Address Number VA evt_TaxId <- TK Tax ID VA evt_NameAlpha <- TK Name - Alpha If SV File_IO_Status is equal to CO SUCCESS // Return Successful End If End If End If End If
If system fails to validate information on evt_syma, evt_symt and evt_symn, system won't search table F0101.
IMPORTANT: Scrubbing Address Number can be done either through system function or NER N0100061 - ScrubAddressNumberNER (Scrub Address Number) so it is important to analyze jasdebug.log (namely rtdebug which traces runtime routine/specification) if the issue is specific to HTML client.
System Function: This is java code which is running in JAS when input value is scrubbed through DD item.
NER: This is Client Only NER so it has to be serialized and stored in F989999 (so jasdebug.log willc contain the cause of error). This routine gets called when scrubbing routine is written through event rule
In HTML client, the component which triggers error message/label can be traced by clicking small yellow-colored triangle. In FAT client, click right mouse button to go to 'Error Detail' which repeat same message.
Example in HTML client:
Address Number - Invalid Go to error.. CAUSE: The address number entered is not found in the Address Book Master file (F0101). RESOLUTION: Enter a valid address number.
ER Details: Form P4210_W4210A Control Id 800 Control Title Long Address Number Event Control Exited/Changed-Inline Line No 87 Error ID 0037
Example error is triggered in Windows client through system function:
Error ID: 0037 Description: Address Number - Invalid Source File:\build\toolsRlease\Rels\client\Jdeuser\jdecgrt\Rt_sysfun.cpp Source Line: 730 Data Item: ALKY - Long Address Number
To discuss information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the JDE1 Distribution Community.
To look at upcoming or archived Advisor Webcasts please see Advisor Webcast Details (Doc ID 548764.1) if your topic is not currently scheduled please suggest it.
