topic Re: Buffer table not up to date in Application Development and Automation Discussions

Buffer table not up to date

UmaArjunan — Thu, 17 Apr 2008 09:13:01 GMT

Hi experts

New fields are added to the datasource .0srm_td_cf (confirmtion data source) in BI SRM (rsa2,rsa3 transaction)

i.e. There are two fields added to the extract structure of the datasource using append structure

The values are to be populated for the new field.

I enhanced RSA5_SAPI_BADI to populate the data in the extractor.

When i check the extractor checker using rsa3 transaction code, it shows a message,

‘Buffer table not up to date ‘after clicking the extraction at the bottom.

I dont know where to fix the problem like, the problem is with the BADI code or with the resulting table where the values are displayed

Additional info:

When i click the long message for the error

it shows:

Message No : bbp_pd001

Diagnosis.

In FORM LTXT_READ_DATA (function group SAPLBBP_PDLTX) an inconsistent status was discovered.

Procedure

Start the transaction again. If the error occurs again, create an OSS message.

To analyze the error, you can set a break point in the function module 'BBP_PD_ABORT' and look at the call-up heirarchy in debuggging mode.

PLEASE suggest me to resolve this issue asap

Thanks in advance

Re: Buffer table not up to date

Former Member — Thu, 17 Apr 2008 09:21:48 GMT

Hi,

Try to reset you table buffer by executing the following transaction

/$tab

/$sync

Regards

Re: Buffer table not up to date

UmaArjunan — Thu, 17 Apr 2008 09:36:30 GMT

I executed the t_code.

even after that while extracting the data finally . It displays Buffer table not upto date

If any other methods are ther, please provide that......

Thanks

Re: Buffer table not up to date

UmaArjunan — Thu, 17 Apr 2008 10:05:05 GMT

solution please

Re: Buffer table not up to date

UmaArjunan — Thu, 17 Apr 2008 13:15:53 GMT

reopening the issue

Re: Buffer table not up to date

Sm1tje — Thu, 17 Apr 2008 13:22:54 GMT

Did you do what the error message suggested?

Set a break point and have a look at the call hierarchy?

If you did, other suggestion tells you to create an OSS message, which could point to a serious error.

Re: Buffer table not up to date

UmaArjunan — Thu, 17 Apr 2008 13:31:32 GMT

you are correct.I tried debugging also.

since all r std FM and pgms i cant do anything.

Already i enhanced two extractors, same thing adding fields and values are populated. it works fine.

But only for this extractor values are not displayed. it tries to retrieve. but at last it gives dump after clicking the message

"Buffer table not up to date'.

So if anything has left out to check i can do it.

so plz suggest. before creating OSS message

Re: Buffer table not up to date

Sm1tje — Thu, 17 Apr 2008 14:14:18 GMT

Ask one of your Basis administrators to have a look??

Re: Buffer table not up to date

UmaArjunan — Fri, 18 Apr 2008 03:47:47 GMT

Please read this read , and let me know if there is any solution further.

Thanks

Re: Buffer table not up to date

UmaArjunan — Sat, 26 Sep 2009 18:25:49 GMT

Solved by OSS

Re: Buffer table not up to date

Clemenss — Sun, 27 Sep 2009 12:09:10 GMT

Hi Uma,

before closing the thread: Did you find an OSS Note or did you create a Message? What was the solution?

TNX.

Clemens

Re: Buffer table not up to date

UmaArjunan — Mon, 28 Sep 2009 04:57:34 GMT

Hi Clemens,

We created a message and sent that to SAP.

It is specific to our problem.. But it cant be used commonly for all the "Buffer table up to date" problem..

SAP idenitfied the DataSource extraction with 0SRM_TD_CF crashes with message B

The response given by SAP is as follows :

Error is being caused by inconsistent status of the Return Delivery

1341 ; GUID: 47C53CEA56B503E4E10080009148BC5F

(Parent GUID, CRM_ORDERADM_H - 47C53CDC56B503E4E10080009148BC5F)

Problem is in the Long Text ID 'ZCD', which does not exist anymore and

document is trying to reference it.

Other Text IDs (ITXT and RRTN) are present but not ZCD.

It looks like customizing has been changed after creating the involved

document and this is causing the error.

SPRO->SRM->SRM Server->Cross-Application Basic Settings->

Text Schema->Define Text Schema

Thanks,

Uma