Exception condition "INVALID_POS"

[Former Member]

Hi,

I am getting the error while monitoring the outbound queue in SMQ1 very rarely as FM-------"BBP_NOTIFY_FOLLOWON_INBOUND" with exception condition "INVALID_POS". Kindly assit me what could be the reason for this error.

regards,

Kannan B

[former_member88970]

We have this problem a few times/week.  Anyone find a solution to it?  Thanks in advance, - Dow

[ivy_li]

Hi,

The root cause of such dump is that some PO has no value in BE_LOG_SYSTEM field which generated a dump in SRM system, and the update in ECC system is stuck in smq1.

To solve this, you have to find out the PO number in the dump file (IT_PURCH_ORDERS).

Then please do as follows:

====

- Please delete all the sysfail entries for FM BBP_NOTIFY_FOLLOWON_INBOUND in t-code SMQ1 on ECC system;

- Retransfer the PO (which you found in the dump file) using the FM BBP_PD_PO_TRANSFER_EXEC;

- Check on header on tcode BBP_PD if the BE_LOG_SYSTEM field is filled for header of this PO.

- Run report BBP_PO_INIT_NOTIFY_FOLLOWON in SRM system insert a new AV entry for the PO in BBP_DOCUMENT_TAB and then run report CLEAN_REQREQ_UP for this PO.

====

After this, the system will be working as usual.

BR,
Ivy

[former_member88970]

Thanks Ivy!  I appreciated the help! 

Is there any way to prevent this from happening, rather than keeping an eye on it all through the day?

- Dow

[ivy_li]

Hi Dow,

Would you please check if note 2224552 is applied in your system or not?
If not, please apply it and monitor if the similar dump happened again.
In fact, it is really difficult for us to find out the root cause, because issue always happened randomly without reproducible steps.

BR,
Ivy

[former_member268977]

I have raised incident and awaiting SAP response.

Thanks for your help!!!

[Former Member]

Hi Turdy/All,

We are facing a similar issue in the PROD system and because of this around 1500 dumps are created due to which none of the users' are able to login to the system.

Could you please let me know if the issue is solved, if yes what is the resolution.

Appreciate your response.

Thanks,

Raghavendra.

[Former Member]

Hi Raghu,

If I am not wrong , this issue is coming in SRM  , whenever an update happen to PO in ECC  and which updates SRM vai RFC all.

Even I raised message to SAP and it went for long time too.. as per my knowledge

When ever you change the PO in SRM , the PO is not get updated with "BE_LOGICAL_SYSTEM" , which is the condition checked by BBP_PO_INIT_NOTIFY_FOLLOWON FM . 

Is your issue solved now?

Thanks

CB

[Former Member]

Hi CB,

Thanks for your response.

Unfortunately it is not solved and on top of it this occurs sporadically, blocking the outbound queue in ECC system which results in the dumps in SRM system.

Please let me know if you were able to figure out a solution for this problem.

BR,

Raghu.

[former_member268977]

Ivy,

We cleared the block queue but we get continuous blocks throughout the day and daily.    The document that has the queue block references a GR document.   What would be the reason for this?  Also how can we trace a transaction ID to the document so that we can found the PO associated with it?

Thanks

Trudy

[ivy_li]

Hi Trudy,

Your issue seems to be more complex.

I suggest you raise one incident to report this so that processor can reproduce and debug the process.

Best regards,

Ivy

[former_member268977]

I applied the following note 1619911.  Issue still exist.  Have any found a resolution to this problem?

Thanks

Trudy

[ivy_li]

Hi Tudy,

This note will solve the dump for this report.

After implementation, you should delete the stuck entries in trx smq1 in ECC side.

Then run this report again to see if dump is generated.

If dump persists, please check if the PO example is successfully transferred to ECC side.

Best regards,

Ivy

[Former Member]

Hi Ivy,

We are facing a similar issue and note# 1619911 is already present in the system and also PO and GR data is transferred to the PO in ECC side.

Could you please suggest any solution for this problem.

best regards,
Raghavendra.

[ivy_li]

Hi Kannan,

For this dump, please apply the following note to solve it:

1619911 - DUMP in Program BBP_PO_INIT_NOTIFY_FOLLOWON

After this, please also delete the lock entries of BBP_NOTIFY_FOLLOWON_INBOUND in trx SMQ1(ECC side).

This will solve the case.

Best regards,

Ivy

[Former Member]

Hello Kannan,

   We are also facing same issue , Can you please tell how you solved this issue?

Regards

CB

[Former Member]

Hello Channu

How did you resolved this issue ?? any idea ?? we are also getting same issue

Kaustubh