EBI 9.2: Error Message (12500,43) on Auto-Generated Invoice ID Upon Saving Billing Invoice With Page and Field Configurator Fields Requirement (Doc ID 2905370.1)

Last updated on OCTOBER 28, 2022

Applies to:

Symptoms

It has been detected that after enabling Page and Field Configurator settings to require Fields Accounting Date, Invoice Date, and Bill Source ID be populated at the Standard Billing component (BI_ENTRY), the system correctly throws Error Message (18111,25031) if any of those Fields are left blank upon saving the new transaction.

However, the system also throws Error Message (12500,43) once the required fields have been updated, and a new save is done.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a System Administrator
    2.- Navigate to: Enterprise Components > Page and Field Configuration > Page and Field Configurator
    3.- Add a new value for Component Name BI_ENTRY, under Market Global, and Configuration Type Standard
    4.- On the Page Configuration tab, define Sequence Number 1, and click on the SELECT FIELDS button
    5.- From the Primary Page drop down, select the value '03 - Header - Info 1' and click on SEARCH button
    6.- From the list of Fields displayed, select the below ones:
             a) 'Accounting Date' row (Record BI_HDR, Field ACCOUNTING_DT)
             b) 'Invoice Date' row (Record BI_HDR, Field INVOICE_DT)
             c) 'Source' row (Record BI_HDR, Field BILL_SOURCE_ID)
    7.- Click on the OK button
    8.- For the new 3 rows that have been added into the 'Configure Field Properties' section, select the 'Required Field' check-box
    9.- Save the changes
    10.- Click on the VALIDATE CONFIGURATION button
    11.- Confirm that the system pops up Message (18111,25019) confirming the validation was correct without any errors detected
    12.- Go to the User List tab, and define the below set up:
             a) Level = Header Level
             b) Applies To = All With Excluded Roles/Users
    13.- Go to the 'Map to Portal Registry' tab, select the EMPLOYEE listed row, and click on the APPLY CONFIGURATION button
    14.- Confirm that the system pops up Message (18111,25043) confirming the mapping of the configuration to the Component Events
    15.- Navigate to: Set Up Financials/Supply Chain > Install > Installation Options > Billing - General Options
    16.- At the 'Auto-Numbering Parameters' section, ensure to select the radio-button for Bill Type
    17.- Navigate to: Set Up Financials/Supply Chain > Product Related > Billing > Setup > Invoice Number ID
    18.- Add a new Invoice Number ID as OSS, with the below criteria:
             a) Part 1: Select Static radio-button, and enter a value of OSS in the edit field
             b) Part 2: Select the 'Auto Sequenced' radio-button, add a number in the 'Next Seq' field, such as 23, select the Autofill checkbox, and in Length field enter a value of 8
             c) Part 3: Select the None radio-button
    19.- Save the changes
    20.- Navigate to: Set Up Financials/Supply Chain > Product Related > Billing > Setup > Bill Type
    21.- Open Bill Type MSC under Set ID SHARE, and go to the Bill Type 2 tab
    22.- At the 'Bill Type Level System Control' section, ensure that the field 'Invoice Number ID' has the new value defined OSS
    23.- Save the changes
    24.- Log into the FSCM Online Application as a Billing User
    25.- Navigate to: Billing > Maintain Bills > Standard Billing
    26.- Click on 'Add A New Value' tab
    27.- Define the values for Fields: Business Unit US001, Bill Type Identifier MSC, Customer ID 1000, and leave the Invoice as NEXT
    28.- Click on Add button
    29.- Once the Header - Info 1 page is loaded, save the transaction
    30.- Confirm the system triggers the Error Message (18111,25031) stating that the Accounting Date field is required
    31.- Populate the Accounting Date, Invoice Date, and Bill Source ID fields
    32.- Save the transaction again
    33.- ISSUE: The system throws Error Message (12500,43)

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

ERROR MESSAGE:

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.