CO_ITEM job cancellation issue

[surya_kiran1]

Hi Experts,

We have scheduled CO_ITEM Archiving object Write jobs which got cancelled due to SAPSQL_NO_ROLL error. Even if we have provided Period wise in selection criteria also, jobs are getting cancelled with same error.

Please refer the screenshots of created variant and error logs.

Could you please suggest us how to overcome this error.

Thanks & Regrads,

surya kiran.

[surya_kiran1]

Hi Jurgen,

Thank you for your response.

My basis team is not helping to resolving this issue...we raised to them but they didn't solved.

We are also checking some notes.

Please provide me any S-notes to resolve this issue so then will move furthrer to close this.

Thanks & Regards,

surya kiran.

[JL23]

there are no notes for this problem for object CO_ITEM.

[surya_kiran1]

Hi Jurgen,

Ok...then,how we have to resolve this issue.

is their anything need to delete some logs or increase the size of logs ?

any links are their related to this issue please share me...

for SAP support we have raised yesterday till now no reply.....

Thanks & Regards,

surya kiran.

[JL23]

There is nothing further which I could provide from a distance without having the details from the dump and knowing about the total numbers which need to be processed in your CO_ITEM job. But even with this information I am not sure if it would really help me to find a solution, I am not a basis guy and not so deep in programming either.

Be patient and wait for the reply from SAP Support.

[surya_kiran1]

Hi Jurgen,

Many thanks for your interaction for this issue.

Please find the below dump screenshot.

and i will provide you the table level screenshot too.

and we are waiting for the SAP support response.

co-item-cap1.jpg

Thanks & Regards,

surya kiran.

[surya_kiran1]

hi Jurgen,

We got below reply from SAP Support .

1. Your administrator could/ would increase the allocated memory for defined by your job. 2. (Used by the most customers) Would be if you restrict the job by Object Type responding to your customizing in the Transaction as for example only for Cost Centers, for Orders, for Sales documents ... In case you get the same issue with DUMP SAPSQL_NO_ROLL also if you restrict to Object Type (For example for Orders or for Orders or Sales documents) you should add additional restriction parameter 'Group or Set' for Object Selection (See F1-Help for further details).

Thanks & regards,

surya kiran..

[JL23]

there are 2 OSS notes with fixes on other archiving objects which terminated also in a SAPSQL_NO_ROLL

I would discuss this with a basis admin, maybe your roll_area is defined too small. If the basis admin can't help you further then you probably need to contact SAP Support desk.

[surya_kiran1]

Hi Jurgen,

Many thanks for your response.

please find the attached technical settings screenshot for CO_ITEM archiving object

and i think their is no problem with that we given correctly.

Thanks & Regards,

surya kiran.

[JL23]

yes, this setting looks fine

[JL23]

can you show the customizing of this archiving object, maybe you defined a too high number in either

• Maximum Size in MB
• Maximum number of data objects