Telecom OCS user failed to open an account.

Handling: there was an error in the search keyword: BMPdebug log, and the following records were found through the search results: 2010/kloc-0:18: 48.075 | debug | BME |1264645128075. DASTrigger looks for 0 trigger information, and is exiting dastrigger 2010-0/-2810:18: 48.075 | info | bus |12646451. [verifyProductData] failed. [ProductCode]6520277 appears but 2010-0/-2810:18: 48.076 | info | bus |1264645/kloc-does not exist. [guild line] business execution failed | trade:stackTrace = (), String:message = product does not exist)) 2010-01-2810:18: 48.077 | info | BME. | locale = en _ us, ResultCode = 4057000 12, ResultDesc = error that the product does not exist is reported in the log. Business acceptance failed because the product does not exist. Looking up the error that the product does not exist, we found the following records: [Exception] calling [PrenewsubscriptForCDMA] > [Verifyproductdata] failed [Product code] 6520277 does not exist, that is, the product with the number of 6520277 in the CRM message does not exist. 1, smdb user logs in and inquires that the package table (table 3304) corresponding to product number 6520277 does not exist. 2. Get the user's subscription information and know the specific package content ordered by the user. 3. The product number OCS of the package ordered by the user is inconsistent with the configuration on the CRM side, and the product number corresponding to the modified 3304 table is consistent with the CRM side. 4.CRM will run the failed message again.