Confirmation error Do not specify a funds reservation when referencing a purchase order

[former_member184111]

Hi Forum,

we are on SRM713 in ECS scenario. When creating confirmation for A SC that uses Account Assignment Category as Asset it shows the below error

Do not specify a funds reservation when referencing a purchase order

But when posting a GR in ECC directly for a PO created using same asset number no error is shown.

What is the reason for this error in SRM Confimation?

Thanks,

Anubhav

[Former Member · Accepted solution]

Hello,

we have the same problem in our systems, so we have opened an OSS message. The solution from SAP was to modify the structure BBPS_BAPI2017_GM_ITEM_CREATE as follow:

Add the following fields after the field BUDGET_PERIOD(see also the image below):

Component	Typing Method	Component Type	Data Type	Length	Decimal Pl	Short Description
EARMARKED_NUMBER	Types	KBLNR	CHAR	10	0	Document Number for Earmarked Funds
EARMARKED_ITEM	Types	KBLPOS	NUMC	3	0	Earmarked Funds: Document Item
STK_SEGMENT	Types	SGT_SCAT	CHAR	16	0	Stock Segment
MOVE_SEGMENT	Types	SGT_UMSCAT	CHAR	16	0	Receiving/Issuing Stock Segment

After the changes on the structure BBPS_BAPI2017_GM_ITEM_CREATE it was possible for us to confirm SCs with Account Assignment Category as Asset in SRM. Maybe it's the same solution for you. At the moment there isn't a note available for this issue, the SAP will discuss the issue and maybe create a note later.

I hope I could help and you understand my english ;D.

Best Regards,
Tom Deinert

[former_member184111 · Accepted solution]

Hello Tom,

Many thanks for sharing the solution, will confirm with SAP as it requires modification and confirm.

Your English is perfect

Regards,

Anubhav

[Former Member · Accepted solution]

Hi Anubhav,

We still have no answer from SAP regarding the OSS message we created for the same issue. I noticed that you marked the thread as answered. So should we consider the solution described in the post from Tom Deinert? Is there any OSS note available?

@Tom,Thanks a lot for sharing the solution

Best regards

Hazem Daoud

[former_member184111 · Accepted solution]

Hi Hazem,

Yes, sap confirmed the same solution though data type SGT_SCAT and SGT_UMSCAT were not in our system so we created Z.

It is working now.

Thanks,

Anubhav

[Former Member · Accepted solution]

Hi,

The solution described above was released in the OSS note: 2302638.

Best regards

Hazem Daoud

[laurent_burtaire]

Hello Anubhav,

check in T100 table what is the message class.

If you do not find it, check this KBA:

1482249 - How to determine where an SRM error message is coming from

Regards.

Laurent.

[former_member184111]

Hi Laurent,

It is a back end message Class RE No.203.

Error RE203

It comes from B46A_GOODSMVT_CREATE_CHECK

Thanks,

Anubhav

[laurent_burtaire]

Hello,

did you do a where-used for this message?

In ECC6 EhP7 release, it is called in FMRE_COBL_CHECK function module (linked to Fund Management).

Regards.

Laurent.

[former_member184111]

Hi Laurent,

Yes found that in the said FM FMRE_COBL_CHECK Line 67

when FM called from SRM

KBLPOS = SPACE

and hence system goes on checking other things

When doing GR in ECC

KBLPOS = '000'

system skips other check because of next line

CHECK NOT kblnr IS INITIAL OR

         NOT kblpos IS INITIAL.

Not sure why it behaves differently.

Thanks,

Anubhav

[laurent_burtaire]

Hello,

cannot help you: debug, look for OSS notes, raise an OSS message...

Regards.

Laurent.

[Former Member]

Hi Anubhav,

We are facing exactly the same issue after the last upgrade. Have you been able to solve the issue? It seems to be more a bug in SAP standard.

Thanks in advance for your feedback.

Hazem Daoud

[former_member184111]

Hi Hazem,

Yes it looks like a bug in standard.

We have raised an OSS will update the thread of response from SAP.

Thanks,

Anubhav

[Former Member]

Hi Anubhav,

In fact after making a comparison between two systems (one upgraded and the other not) i noticed the following:

The logic to get kblpos is changed in the FM MB_CREATE_GOODS_MOVEMENT. The field was previously taken from the strcuture DM07M and its intital value was 000 so it was fine when doing the check in the FM FMRE_COBL_CHECK.

After the upgrade,the kblpos is now removed from DM07M and moved to MSEG and the logic in the FM MB_CREATE_GOODS_MOVEMENT was adapted accordingly. What i noticed is that the default field value is empty so i think if SAP tick initial value in the field defintion in the table MSEG,the problem would be solved.

What do you think?

Thanks and best regards,

Hazem Daoud

[former_member184111]

Hi Hazem,

Yes we also found that in debug. When the FM is called from SRM KBLPOS = Space where as when posting GR directly in ECC KBLPOS = '000'. In the upgraded system the field value in MSEG is already '000'. Check the snap shot attached.

If you see the comments in FM at Line 79 it talks about a switch  FMRE_INV_CONSUMPTION. If this switch is activated the validation will not be done and this switch does not exists in previous version but what other things this switch will affect we are not sure.

Waiting for response from SAP. Do let me know if you find any more information.

Thanks,

Anubhav

[Former Member]

Hi Anubhav,

I checked the line 79 in the FM FMRE_COBL_CHECK as you said and that's correct that they talk about this switch FMRE_INV_CONSUMPTION but i think this is not related to that since this FM was not changed since one year for us.

As explained i noticed that the logic to get this KBLPOS in the FM MB_CREATE_GOODS_MOVEMENT wa recently changed and when i debugged in upgraded and non upgraded system and in both cases creating GR from SRM, the MSEG-KBLPOS was empty in the upgraded system however DM07M-KBLPOS was 000 in the non upgraded system. You can search for the coding in the FM MB_CREATE_GOODS_MOVEMENT where the note 2135143 is mentioned (it should be in line 1524 after enhancment MB_CREATE_GOODS_MOVEMENT_27)

Best regards

Hazem Daoud

[former_member184111]

Hi Hazem,

In our system we can post GR directly for same PO with out any issue, problem comes when doing it from SRM only. When doing GR in ECC KBLPOS = '000' in our system as in the snap shot in previous reply MSEG-KBLPOS has initial value '000'.

Thanks,

Anubhav