Requests import in background process

[Former Member]

Hi all,

I am trying to import a lot of requests with the

TMS_MGR_IMPORT_TR_PROPOSAL function. The problem is that when i call that function in background process, the system doesn't imports any request. When I call the function in a common dialog process everything is fine but the report i've made is intended to import 3000 requests at a time. Does anyone has any solution? thanks a lot for your help.

[Former Member]

Hi Santiago,

Just a few ideas as to why it may not be working:

Does the user who executes the background job have authority to import requests?

Is it accessing a file on the server? In this case the background job may be running on another server (if you have multiple application servers running in your instance).

Is it trying to access a file on your PC? In this case it will not work in background, it will need to access a file from the server.

Are you issuing a COMMIT WORK (maybe implicit when called online)?

Cheers,

Brad

[Former Member]

Hi Brad,

I've been checking the things that you told me and these are the results:

The user has permission to import requests.

I don't access to any file in the server or my PC.

I've tried to put the "commit work" sentence after the function call and to debug the function, but the background process doesn't gets started.

Its really strange. Thanks for your help

Santiago

[Former Member]

Hi Santiago,

It does indeed seem strange.

Have you tried running it in background with just a few records (rather than 3000)?

Maybe there is some update problem getting triggered with so much data (database extent, or locking error, or something else).

Try it with just 10 and see what happens.

Brad

[Former Member]

Are you sending spaces to the optional parameters IV_ONLINE, IV_MONITOR, and IV_VERBOSE?

IV_MONITOR has a default value of 'X'.

Regards,

Srinivas

[Former Member]

Hi Brad and Srinivas,

Right now im testing the my report with less than 10 requests. When the report goes to productive it will have the requests i've told you.

I am not changing the optional parameters that you say.

Do you know where can i get some documentation about the TMS_MGR_IMPORT_TR_PROPOSAL function?

Tanks for your help.

Santiago

[Former Member]

Let us know how your testing goes.

You might want to look at the parameters that Srivinas was mentioning. By changing these settings (I haven't looked at the code), it might affect the behaviour of the function when processing online vs. background.

As for doco. for TMS_MGR_IMPORT_TR_PROPOSAL, its an unreleased function module so its unlikely that anything would be publically available.

Cheers,

Brad

[Former Member]

Hi Santiago,

I just checked the code. I don't think it has anything to do with update problems (number of records etc.). I think it gets confused when you schedule as a background job (and ends up doing nothing). Have a look at the parameter IT_TARGET. It has the following fields:

STARTMODE

STARTDATE

STARTTIME

I think that if you will in STARTDATE and STARTTIME with sy-datum and SY-UZEIT it should try and run the update job immediately (this will probably run as a seperate job from the one you schedule). I don't think that STARTMODE is used, but it may require a value (try without one first).

Let us know how you go.

Cheers,

Brad

[Former Member]

I've made it!!!!!

The standard funcion doesn't have any problem. The problem was that I first called a "Z" function and executed it in background processing. Inside that function i called the standard function I mentioned before. The problem was that for background processing mode, the function has to be RFC enabled and my "Z" wasn't.

Anyway, thanks a lot for your help. It's really good to know that there's people out there that tries to help.

Regards

Santiago