- SAP Community
- Groups
- Industry Groups
- SAP for Public Sector
- Discussions
- ABAP DUMP While doing GI Through Zmovement type in...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2015 4:52 AM
Hi ,
We have migrated from FM FBS to BCS from 12.01.2015.
And we are using 101 profile with GR and IR update.
We received blow ABAP Dump while doing the GI through MIGO Transaction.
Can you please help on this.
Dump detatils
Category ABAP Programming Error
Runtime Errors MESSAGE_TYPE_X
ABAP Program CL_BUAVC_ENTRY================CP
Application Component PSM-FM-BCS-AC
Date and Time 13.01.2015 09:10:00
Operating system..... "AIX 1 6, AIX 1 7" |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 33518336 |
| Heap.... 0 |
| Page.... 196608 |
| MM Used. 21989120 |
| MM Free. 3145840 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|User and Transaction |
| Client.............. 256 |
| User................ "MM_BUX00_ZZ" |
| Language key........ "R" |
| Transaction......... "MIGO_GI " |
| Transaction ID...... "54AEDD9E3EE60710E10080000A15C616" |
| |
| EPP Whole Context ID.... "54B35F7088300910E10080000A15C616" |
| EPP Connection ID....... 00000000000000000000000000000000 |
| EPP Caller Counter...... 0 |
| |
| Program............. "CL_BUAVC_ENTRY================CP" |
| Screen.............. "SAPLMIGO 0001" |
| Screen Line......... 18 |
| Debugger Active..... "none" |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated |
| Termination occurred in the ABAP program "CL_BUAVC_ENTRY================CP" - |
| in "POST". |
| The main program was "SAPLMIGO ". |
| |
| In the source code you have the termination point in line 82 |
| of the (Include) program "CL_BUAVC_ENTRY================CM00J". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
| 52|*--- method has provided some errors!): |
| 53| |
| 54|* Note 1499464: |
| 55|* IF cl_abap_aab_utilities=>is_active( id = 'BUAVC_GROUP' |
| 56|* mode_assert_dump = 'X' ) = 'X'. |
| 57| MOVE 'X' TO l_flg_dump. |
| 58|* ENDIF. |
| 59| |
| 60|*--- Check if the entry buffer of the AVC ledger contains data records |
| 61|*--- from previous COLLECT events: |
| 62| IF ( l_f_avc_ledger-ref_ledger->entry_buffer_lines_count( ) > 0 ). |
| 63|*--- Sorry, must dump: |
| 64| ASSERT ID buavc_group |
| 65| FIELDS c_avc_text 'POSTING_NOT_ALLOWED' |
| 66| CONDITION l_flg_dump <> 'X'. |
| 67| IF l_flg_dump = 'X'. |
| 68| MESSAGE x002(buavc) WITH c_avc_text space |
| 69| 'POSTING_NOT_ALLOWED' space. |
| 70| ENDIF. |
| 71| ENDIF. |
| 72| ENDIF. |
| 73|*---------------------------------------------------------------------- |
| 74|* Note 1666556: |
| 75| IF me->g_commit_before_post EQ 'X'. |
| 76|*--- An unauthorized COMMIT WORK occurred before calling this POST |
| 77|*--- method. This COMMIT WORK has refreshed the AVC entry buffer and |
| 78|*--- would thus create a database inconsistency! |
| 79| MOVE 'X' TO l_flg_dump. |
| 80| IF l_flg_dump = 'X'. |
| 81|*--- Sorry, must dump (see note 1666556): |
|>>>>>| MESSAGE x002(buavc) WITH c_avc_text space |
| 83| 'INVALID_COMMIT' space. |
| 84| ENDIF. |
| 85| ENDIF. |
| 86|*---------------------------------------------------------------------- |
| 87| |
| 88| |
| 89|*--- Call the POST method of the corresponding ledger instance: |
| 90| CALL METHOD l_f_avc_ledger-ref_ledger->post |
| 91| EXPORTING |
| 92| i_ref_appl_log = me->g_ref_appl_log |
| 93| i_doc_ref = i_doc_ref. |
| 94| |
| 95| ENDLOOP. |
| 96|
Thanks Advance.
SAM
- SAP Managed Tags:
- Public Sector
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2015 5:46 AM
Hi Sam,
Please check if there is any commit statement written in badi or enhancement before calling this method for posting which is leading to update termination.
Regards,
Prakash.
- SAP Managed Tags:
- Public Sector
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2015 5:46 AM
Hi Sam,
Please check if there is any commit statement written in badi or enhancement before calling this method for posting which is leading to update termination.
Regards,
Prakash.
- SAP Managed Tags:
- Public Sector
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2015 5:57 AM
Hi Prakash,
Thanks for your reply.
it is becasue of the BADI there are comittment statment wirttens in year 2013, we commented this and now it is working.
Thanks in Advance
SAM
- SAP Managed Tags:
- Public Sector
