functional area is stripped from a 16 character field to a 4

[Former Member]

Friends,

Can anyone give me a hand with our R/3 and SRM system? Here our issue:

When a reservation is created in R/3 as a result of a shopping cart in

SRM, the functional area is stripped from a 16 character field to a 4

character field during the BAPI call. As a result, the transaction

fails vailidation. The functional area needs to be extended to 16

characters during this BAPI call. How can we do this?

Here's what we are working with:

ECC version info:

ECC 6.0

SAP_BASIS 700 - 0009 - SAPKB70009

SP9 level

SRM version info:

SRM 5.00

SRM_SERVER 550 - 0006 - SAPKIBKT06

SAP_BASIS 700 - 0009 - SAPKB70009

SP9 Level

Thank you.

Nick Wells

[Former Member · Accepted solution]

Disha,

I opened an OSS message a while back and they responded by saying this in regard to the BADI change. What do you think?

Hi Nick,

1. FKBER_SHORT is in reservation header in FM

B470_RESERVATION_CREATE

BAPI_RESERVATION_CREATE

Unfortunately the generic interfaces can not be changed in the

current Release anymore.

In all other documents like PR, PO FUNC_AREA_LONG is taken into

account.

I am sorry to tell you that this technical restriction is given in

the current Release. The development effort would be substantial

we can not easily change system behaviour in standard at the moment.

Please create a development request as of note 429166 instead.

2. A workaround using Badi BBP_CREATE_RES_BACK would not work,

because finally Backend FM BAPI_RESERVATION_CREATE is called which

also just foresees FKBER_SHORT in header level (see top 1.).

The only way I see it do add accounting data in the follow-on

documents PR, PO.

Please evaluate this in the SRM team and let me know how you would

like to proceed resp. how we can support you further. Thanks!

[Former Member · Accepted solution]

Hi,

As mentioned in the OSS reply,as finally the FM B470_RESERVATION_CREATE is used even though you may implement the BADI ,it will be of no use since the field FUNC_AREA_LONG is not used at all in the FM.So the best option would be to manually go and change the data in the follo on document in R/3.

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

Disha,

Thanks for your help. Yes, I agree that must be the solution.

[Former Member]

Disha,

Could you please be more specific with your original response? We are not too good with the BAPIs and need more detail in order to understand your solution. Thank you so much

Nick

[Former Member]

All,

We are still working on the specifics of the solution on this. Part of the solution has been to implement SAP note 981231. We are looking a Disha's solution to see if this is the best way to do things. I'll let you know when we finish.

Nick

[former_member195032]

Hello Nick,

There is another SAP note on the same issue and I feel that it will address your issue as problem is very similar.

Note 1011875 - Functional area not determined on accounting objects change

regards,nishant

please reward if this helps

[Former Member]

nishant,

we have already implemented that note, but thank you for the posting

[Former Member]

Disha,

Thank you so much for your reply. I'll take a closer look at the solution you suggested and let you know how it goes. Thanks so much.

Nick

[Former Member]

Hi,

You can use the BADI "BBP_CREATE_BE_RS_NEW" to change the data for the field functional area while transferring the SC from SRM to R/3.

You can use the incoming 16 char Functional area from the SC structure "IS_SC_DOCUMENT-ACCOUNT-FUNC_AREA" adn pass it to the 16 char field " FUNC_AREA_LONG " of the exporting parametre structure "CS_RS1_DOCUMENT-IS_RS_HEADER".

If you see in the export structure "CS_RS1_DOCUMENT-IS_RS_HEADER" ,you have another field for "Functional area" whcih is 4 char long i.e. "FUNC_AREA".

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

Hi,

Go to se18 and create an implementation for the BADI "BBP_CREATE_BE_RS_NEW".

Double click on method,"FILL_RS_INTERFACE1".There in the import paramter structure "IS_SC_DOCUMENT",in the component structure "ACCOUNT",there is a 16 char field for the functional area i.e. "FUNC_AREA".In this field you will get the 16 char value which gets truncated when creating reservation in the backend.

So you need to pass this 16 char value to the field "func_area_long" in the exporting parameter structure CS_RS1_DOCUMENT.

BR,

Disha.

Pls reward points for useful answers.