Full Load Infopackage Error

[Former Member]

Friends/Experts,

I am fighting a lot with the below issue more then 3 Weeks , Kindly please help me out.

Data Source : 0CO_OM_CCA_9

While i try for data selection 001.2015 to 006.2015 ----> Full Load Info-package successful.

When i try for data selection 007.2015 ---------> Full Load Info package Throws an error.

I replicated the Data Source in BW and Activated all, then too i got the same error.

Please Refer the Screen shot:

Until 35,400 Data fetched after that same issue.

[Former Member]

Did you get answer to your issue ?

I am also facing same issue in one of my custom extractor, please share the resolution if you found any .

[john_hawk]

Hi Rgi,

The error is clearly telling you that there is a piece of data in Fiscal year/Period that the extractor does not like.

Use ST22 in the source system to see the stack dump, it may give you a clue.

Consider selecting 007.2015 and by single Cost Center or other selection criteria to identify the "bad" data.

Consult with the ECC functional analyst to determine if there is known bad data in this period.

There are multiple SAP Notes for 0CO_OM_CCA_9.

SAP Note 2161776 - BW-BCT: DataSource 0CO_OM_CCA_9 extracts forbidden characters in text field of data record caught my eye.

https://launchpad.support.sap.com/#/solutions/r/?type=note&route=notes&p=%7B%22note%22%3A%222161776%...

If the text field contains forbidden characters, the the extract will fail.

Please don't forget to record your final solution and to mark the question as answered.

Good luck,

John Hawk

[Former Member]

Thanks for Your Response John,

I could not open the link which you provide.

I have no clue to take first step to resolve the issue.

If you help me by step process its really appreciated.

[Former Member]

in your monitor:

menu environment --> Job Overview --> in the source system

you get the job selection screen, hit the execute button. Select the job and click on Job Log.

check the error messages.

M.

[Former Member]

Tibollo,

Job log Screen shot,

[Former Member]

there is a sql error in the source system. check ST22 in the source system for this error message.

M.

[Former Member]

Tibollo,

I have no Clue at all.

[Former Member]

use transaction ST22 in your source system. find the error message. open it. check the additional info.

M.

[Former Member]

sorry screenshot missed in my previous message,

[Former Member]

this is a memory issue. needs to be handled by your basis team. forward them the error message and ask for their help.

you can also check your coding in the user exit. the issue could be linked to a selection without enough limitations... for this you can ask help of somebody who knows abap.

M.

[Former Member]

R u sure its a Memeory Issue.

And then didnt write any routines for this.

[Former Member]

yes, according to my experience it's a memory issue. check with basis team to be sure.

on which system do you have these issues: DEV, QA, PROD?

M;

[Former Member]

Sure Will ask about this to Basis any way.

Working on PRD

[Former Member]

I forwarded to basis team,

Once i got any information let you know.

[john_hawk]

Concur.

However, bad code can create memory issues.

Have an ABAPer check your User exits

John Hawk

[john_hawk]

Hi Rgi,

The screen shot from your job log clearly indicates that is searching for document numbers it cannot find.

Could these documents have been archived?

In other situations, searching for archived data without special instructions in code have led to job failure. Your system may be trying to load ALL archived data from BSEG into memory. This could cause a memory overload.

Please don't forget to record your final solution and to mark the question as answered.

Good luck,

John Hawk

[john_hawk]

Hi Rgi,

You need get with your Basis Support group and have them get you and "S-id" and show you how search for SAP Notes.

Search all notes with "0CO_OM_CCA_9" and have them review the ones which would apply.

Good luck,

John Hawk

[Former Member]

Hi John,

Still my issue is not resolved,

And i dont have access for luanchpad for support.

I could not find proper document.

Guys need your help for sure.