topic Unable to create Functional Location in SAP using BAPI_FUNCLOC_CREATE in Application Development and Automation Discussions

Unable to create Functional Location in SAP using BAPI_FUNCLOC_CREATE

Former Member — Wed, 21 Oct 2009 18:01:38 GMT

Hi,

We are able to manually create Functional Location using BAPI_FUNCLOC_CREATE through the SAP front end.(BAPI_TRANSACTION_COMMIT has to be issued after this)

However, if we try to create the same from Business Objects Data Services, the Data Services Job runs through fine, without error. However the functional location does not get created. It says the functional location does not exist when we verify through the T Code IL03

Has anybody come across this issue before ? It would be of great help if you can share your experience

Thanks

Zebah

Re: Unable to create Functional Location in SAP using BAPI_FUNCLOC_CREATE

Former Member — Thu, 22 Oct 2009 16:14:18 GMT

Hi Zebah,

If you don't get any errors and are sure the call got executed, I'd say it sounds like the commit is missing. So are you sure that your data service job includes the individual commits (and if executed as RFC's that they are in the same context as the original call)?

Cheers, harald

Re: Unable to create Functional Location in SAP using BAPI_FUNCLOC_CREATE

Former Member — Fri, 23 Oct 2009 14:05:57 GMT

Hi Harald,

Thanks for trying to help me. We are issuing a commit. Please see the function module:

FUNCTION zfm_bapi_funcloc_create.

*"----

""Local Interface:

*" IMPORTING

*" VALUE(EXTERNAL_NUMBER) LIKE BAPI_ITOB_PARMS-FUNCLOC

*" VALUE(LABELING_SYSTEM) LIKE BAPI_ITOB_PARMS-LABEL_SYST OPTIONAL

*" VALUE(DATA_GENERAL) LIKE BAPI_ITOB STRUCTURE BAPI_ITOB

*" VALUE(DATA_SPECIFIC) LIKE BAPI_ITOB_FL_ONLY STRUCTURE

*" BAPI_ITOB_FL_ONLY

*" EXPORTING

*" VALUE(FUNCTLOCATION) LIKE BAPI_ITOB_PARMS-FUNCLOC_INT

*" VALUE(DATA_GENERAL_EXP) LIKE BAPI_ITOB STRUCTURE BAPI_ITOB

*" VALUE(DATA_SPECIFIC_EXP) LIKE BAPI_ITOB_FL_ONLY STRUCTURE

*" BAPI_ITOB_FL_ONLY

*" VALUE(RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2

*"----

CALL FUNCTION 'BAPI_FUNCLOC_CREATE'

EXPORTING

external_number = external_number

labeling_system = labeling_system

data_general = data_general

data_specific = data_specific

IMPORTING

functlocation = functlocation

data_general_exp = data_general_exp

data_specific_exp = data_specific_exp

return = return.

IF return-type NE 'E' OR return-type NE 'A'.

COMMIT WORK AND WAIT.

ENDIF.

ENDFUNCTION.

I also believe that I am calling this BAPI from Business Objects DataServices in the same session. I am just assigning the right values to the BAPI columns. If we execute the BAPI from SAP front end, it commits fine. However when I call from Data Services, it comes out with no error, but we find that the commit has not happened.

Does this throw any more light ?

Thanks

Zebah

Re: Unable to create Functional Location in SAP using BAPI_FUNCLOC_CREATE

Former Member — Tue, 27 Oct 2009 18:46:59 GMT

Hi Harald,

I thought that these additional information might help:

In the SAP front end, the following message pops up after running my job from business objects dataservices:

SAP office express info

Express document "Update was terminated" received from author " User name "

In the TCode sm13

we find that the module name (function) ITOB_BUF_FL_SAVE_UPD_TASK

has failed.

Further, in Tcode st22 we have this error : DBIF_RSQL_INVALID_RSQL

Note: the external job in business objects dataservices completes successfully with no error

Any thoughts on way forward is very much appreciated

Thanks

Zebah

Re: Unable to create Functional Location in SAP using BAPI_FUNCLOC_CREATE

Former Member — Wed, 28 Oct 2009 03:24:28 GMT

Hi Zebah,

Sorry for the late response, but based on your response to my comment it was clear that it wasn't the COMMIT and there was some other issue. Unfortunately I don't have any good idea what might be causing this problem. I searched OSS and a couple of notes turn up for BAPI_FUNCLOC_CREATE, but none of them seem relevant to your short dump.

Please check the statement where the dump occurs. Based on the exception it sounds like some SQL statement is causing problems, but the exception seems odd. The most common cause for the DBIF_RSQL_INVALID_RSQL exception is a SELECT statement with an IN select-option with too many conditions. Doesn't sound like this should happen in the update process...

For analysis of the DBIF_RSQL_INVALID_RSQL exception SAP recommends though checking the system log and the trace file of the work process (ST11) where the error occurred. With that information you should have more details as to what might be causing the short dump (possibly also gives you some relevant keywords to feed into OSS).

Best wishes, harald