In this article, I’m going to share how to fix the ABAP runtime error occurred in the SAP-PRA Oil and Gas module that happened in the escheat process, after SAP Unicode Conversion.
What is Escheat Process?
All States in United States require payers including corporations, financial institutions, and brokerage firms etc., to report when personal property has been abandoned or unclaimed after a period of time specified by State Law. Basically, unclaimed or abandoned property is money and other types of property for which the owner has not made a claim, or cannot be identified or found, after a specified period of time known as the dormancy period. Once the dormancy period has expired, unclaimed property must be remitted (escheated) to the State.
https://www.sec.gov/fast-answers/answersescheathtm.html
Unclaimed payments that are made to owners of venture property in the SAP-PRA Oil & Gas module is not an exception to the escheat process. These unclaimed funds need to be reported and paid to the respective State governments based on the address of Owner.
After implementation of Unicode in SAP, escheat process in SAP-PRA encountered a runtime error. Following are the symptom of the issue and the resolution.
Component: IS-OIL-PRA-REV-JE
Category: ABAP Programming Error
Runtime Errors: BCD_BADDATA
ABAP Program: SAPLOIUH_RDBQ832
Application Component: IS-OIL-PRA-REV-JE
Symptom or Error: Error in the ABAP Application Program. The current ABAP program "SAPLOIUH_RDBQ832" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Symptom:
Transaction: O3UH_ES (Program: ROIUH_ESCHEATPROC)
When we execute the above transaction code, it creates a background job ‘SAP_ESCHEATPROC’ in SM37. This job fails in less than a minute with run time error.
The process fails when Function Module ‘OIUH_SUBMIT_SYNCSORT_CALL’ is called. This Function Module generates a subroutine module pool program that cannot handle Unicode process and it fails with runtime error.
The error details are shown in below screen shots.
Other Terms:
General Keywords: Add-on, IS-Oil, Industry Solution, Oil and Gas Upstream, PRA, Production Revenue Accounting.
Problem Specific Keywords: Escheat summary report, Unicode, Non-Unicode, ROIUH_REPORT_VIEWER, RDBQ830, RDBQ8301, ESREPT, ESREPTT.
Solution:
Apply the following script to remove redundant SORT JILs from the escheat tables, which cause bad data due to Unicode issues.
Z_AG_UPDATE_ESCHEAT_JIL.txt
This script resolves the runtime error complained above.
After running the script, program ‘ROIUH_ESCHEATPROC’ which was giving an error, ran successfully as shown in below screen shot.
With successful execution of the above job, the journal entries will be posted as per the configuration, to reflect the transfer of escheated funds.
What is Escheat Process?
All States in United States require payers including corporations, financial institutions, and brokerage firms etc., to report when personal property has been abandoned or unclaimed after a period of time specified by State Law. Basically, unclaimed or abandoned property is money and other types of property for which the owner has not made a claim, or cannot be identified or found, after a specified period of time known as the dormancy period. Once the dormancy period has expired, unclaimed property must be remitted (escheated) to the State.
https://www.sec.gov/fast-answers/answersescheathtm.html
Unclaimed payments that are made to owners of venture property in the SAP-PRA Oil & Gas module is not an exception to the escheat process. These unclaimed funds need to be reported and paid to the respective State governments based on the address of Owner.
After implementation of Unicode in SAP, escheat process in SAP-PRA encountered a runtime error. Following are the symptom of the issue and the resolution.
Component: IS-OIL-PRA-REV-JE
Category: ABAP Programming Error
Runtime Errors: BCD_BADDATA
ABAP Program: SAPLOIUH_RDBQ832
Application Component: IS-OIL-PRA-REV-JE
Symptom or Error: Error in the ABAP Application Program. The current ABAP program "SAPLOIUH_RDBQ832" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Symptom:
Transaction: O3UH_ES (Program: ROIUH_ESCHEATPROC)
When we execute the above transaction code, it creates a background job ‘SAP_ESCHEATPROC’ in SM37. This job fails in less than a minute with run time error.
The process fails when Function Module ‘OIUH_SUBMIT_SYNCSORT_CALL’ is called. This Function Module generates a subroutine module pool program that cannot handle Unicode process and it fails with runtime error.
The error details are shown in below screen shots.
Other Terms:
General Keywords: Add-on, IS-Oil, Industry Solution, Oil and Gas Upstream, PRA, Production Revenue Accounting.
Problem Specific Keywords: Escheat summary report, Unicode, Non-Unicode, ROIUH_REPORT_VIEWER, RDBQ830, RDBQ8301, ESREPT, ESREPTT.
Solution:
Apply the following script to remove redundant SORT JILs from the escheat tables, which cause bad data due to Unicode issues.
Z_AG_UPDATE_ESCHEAT_JIL.txt
This script resolves the runtime error complained above.
After running the script, program ‘ROIUH_ESCHEATPROC’ which was giving an error, ran successfully as shown in below screen shot.
With successful execution of the above job, the journal entries will be posted as per the configuration, to reflect the transfer of escheated funds.
- SAP Managed Tags:
1 Comment
