on 12-25-2018 3:28 AM
Dear ABAP Experts,
I am working in New GL SAP implementation project.
In this project. My Client Upgrading system ECC6.0. After Upgrade we are implementing the New GL activation.
After New GL Activation SAP Replaces GLT0. I use SAP Note 2221298 with function module FINS_ACDOCA_BW_EXTRACT_DATA. While testing function module I am enable to get the result in table E_T_FINS_ACDOA_BW
Request your expert guideline on same
Hello Guru
Thanks for reply.
We resolve the problem through ACDOCA table. For some countries we upgrade the system from ECC TO S4/HANA.
Changes done in program through ABAP team
Regards
Yogesh K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Don't confuse between New G/L and S/4 HANA. Table ACDOCA which is mentioned in your question corresponds to S/4 HANA implementation and has nothing to do with New G/L.
Regards,
Eli
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Expert
I am getting Runtime error while testing the FM
FINS_ACDOCA_BW_EXTRACT_DATA.
Access using a 'NULL' object reference is not possible
|What happened? |
| Error in the ABAP application program. |
| |
| The current ABAP program "SAPLFIS_ACDOCA_BIW" had to be terminated because it |
| found a |
| statement that could not be executed. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What can I do? |
| Note which actions and entries caused the error to occur. |
| |
| Consult your SAP administrator. |
| |
| Using transaction ST22 for ABAP dump analysis, you can view, manage, |
| and retain termination messages for longer periods. |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Error analysis |
| An exception has occurred which is explained in more detail below. The |
| exception is assigned to class 'CX_SY_REF_IS_INITIAL' and was not caught in |
| procedure |
| "FINS_ACDOCA_BW_EXTRACT_DATA" "(FUNCTION)", nor was it propagated by a RAISING |
| clause. |
| Since the caller of the procedure could not have anticipated this |
| exception, the current program was terminated. |
| The reason for the exception is: |
| You are trying to access a component with a 'NULL' object reference |
| (points to 'nothing'). |
| An object reference must point to an object (an instance of a class) |
| before it can be used to access a component. The reference has either |
| never been set, or it was set to 'NULL' with a CLEAR statement. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error |
| The exception must either be prevented, caught in procedure |
| "FINS_ACDOCA_BW_EXTRACT_DATA" "(FUNCTION)", or |
| the possibility of it occurring must be declared in the RAISING clause |
| in the procedure. |
| To prevent the exception, note the following: |
| |
| If the error occurs in one of your own ABAP programs or an SAP program |
| that you have modified, try to correct the error yourself. |
| If the error occurs in a non-modfied SAP program, you might be able to |
| find a solution in the SAP Notes system. If you have access to the SAP |
| Notes system, check there first using the following keywords: |
| |
| "OBJECTS_OBJREF_NOT_ASSIGNED_NO" CX_SY_REF_IS_INITIAL |
| "SAPLFIS_ACDOCA_BIW" bzw. LFIS_ACDOCA_BIWU01 |
| "FINS_ACDOCA_BW_EXTRACT_DATA" |
| If you cannot solve the problem yourself, please send the following |
| information to SAP: |
| |
| 1. This description of the problem (short dump) |
| To do this, choose System -> List -> Save -> Local File (unconverted) |
| on the screen you are in now. |
| |
| 2. A suitable system log |
| To do this, call the system log in transaction SM21. Restrict the time |
| interval to ten minutes before the short dump and five minutes after |
| it. In the display, choose System -> List -> Save -> Local File |
| (unconverted). |
| |
| 3. If these are programs of your own, or modified SAP programs: Source |
| code of these programs |
| To do this, choose More Utilities -> Upload/Download -> Download in |
| the Editor. |
| |
| 4. Details regarding the conditions under which the error occurred or |
| which actions and input caused the error. |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|System environment |
| SAP Release..... 750 |
| SAP Basis level 0011 |
| |
| Application server... app05q14 |
| Network address...... 10.214.2.178 |
| Operating system... Linux |
| Release.............. 4.4.73-5-default |
| Hardware type....... x86_64 |
| Character length..... 16 Bits |
| Pointer length........ 64 Bits |
| Work process number... 18 |
| Shortdump setting. full |
| |
| Database server... ksbsap13 |
| Database type..... HDB |
| Database name..... Q14 |
| Database user ID SAPABAP1 |
| |
| Terminal.......... decxksb0040 |
| |
| Character set C |
| |
| SAP kernel....... 749 |
| Created on....... Jun 19 2018 01:31:11 |
| Created at....... Linux GNU SLES-11 x86_64 cc4.8.5 use-pr180618 |
| Database version SQLDBC 2.03.123.1537559908 |
| Patch level....... 517 |
| Patch text....... |
| |
| Database............. HANA 1.0, HANA 2.0 |
| SAP database version. 749 |
| Operating system... Linux |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 22533352 |
| Heap.... 0 |
| Page.... 745472 |
| MM used. 4132208 |
| MM free. 2863608 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|User and Transaction |
| Client................. 099 |
| User.................. KADAYOG |
| Language key.......... E |
| Transaction......... ST22 |
| Transaction ID...... 66E6A1DA58070120E005C21D5BEB5512 |
| |
| EPP whole context ID...... 00215A9B05941ED982822FA290D827D8 |
| EPP connection ID........ 00000000000000000000000000000000 |
| EPP call counter......... 0 |
| |
| Program.............. SAPLFIS_ACDOCA_BIW |
| Screen.............. SAPMSSY0 1000 |
| Screen line.......... 6 |
| Active debugger..... "none" |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated |
| The termination occurred in ABAP program or include "SAPLFIS_ACDOCA_BIW", in |
| "FINS_ACDOCA_BW_EXTRACT_DATA". The |
| main program was "RS_TESTFRAME_CALL". |
| |
| In the source code, the termination point is in line 188 of program or |
| include "LFIS_ACDOCA_BIWU01". |
| The termination is due to exception "CX_SY_REF_IS_INITIAL" occurring in |
| procedure "FINS_ACDOCA_BW_EXTRACT_DATA" "(FUNCTION)". |
| This exception was not handled locally or declared in the RAISING |
| clause in the procedure's signature however. |
| The procedure is in program "SAPLFIS_ACDOCA_BIW". The source code begins in |
| line 1 of |
| (include) program "LFIS_ACDOCA_BIWU01". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
| 158| |
| 159| TRY. |
| 160| so_acdoc_sel->open_cursor( |
| 161| EXPORTING |
| 162| it_projection = lt_projection |
| 163| it_filter = lt_filter |
| 164| iv_aggregate = 'X' |
| 165| iv_compatibility_mode = ' ' |
| 166| iv_include_std_ledgers = i_include_std_ledgers ). |
| 167| CATCH cx_fins_acdoc_select INTO lo_cx. |
| 168| log_write_full 'E' |
| 169| lo_cx->t100key-msgid |
| 170| lo_cx->t100key-msgno |
| 171| lo_cx->t100key-attr1 |
| 172| lo_cx->t100key-attr2 |
| 173| lo_cx->t100key-attr3 |
| 174| lo_cx->t100key-attr4. |
| 175| RAISE error_passed_to_mess_handler. |
| 176| ENDTRY. |
| 177| |
| 178| CREATE DATA sr_t_extstructure TYPE TABLE OF fins_acdoca_bw. |
| 179| |
| 180|************************************************************************ |
| 181|* Data transfer: FETCH data from ACDOCA |
| 182|************************************************************************ |
| 183| ELSE. |
| 184| |
| 185| ASSIGN sr_t_extstructure->* TO <t_extstructure>. |
| 186| |
| 187| ld_package_size = ss_interface-maxsize. |
|>>>>>| so_acdoc_sel->fetch( |
| 189| EXPORTING |
| 190| iv_package_size = ld_package_size |
| 191| IMPORTING |
| 192| et_data = <t_extstructure> ). |
| 193| |
| 194| e_t_fins_acdoca_bw[] = <t_extstructure>. |
| 195| |
| 196| IF e_t_fins_acdoca_bw[] IS INITIAL. |
| 197| RAISE no_more_data. |
| 198| ENDIF. |
| 199| |
| 200|* Write data to LOG table FAGL_BW_LOG_TOTL if activated |
| 201| CALL FUNCTION 'G_BIW_LOG_DATA' |
| 202| EXPORTING |
| 203| i_datasource = ss_interface-isource |
| 204| i_requnr = ss_interface-requnr |
| 205| i_log_table = 'FAGL_BW_LOG_TOTL' |
| 206| TABLES |
| 207| t_istructure = e_t_fins_acdoca_bw[].
Request your help
Regards
Yog K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.