cancel
Showing results for 
Search instead for 
Did you mean: 

background job 'SPOOL_OBJECTS' ?

Former Member
0 Kudos

We have a background job in our SRM 5.0 (Extended Classic Scenario) which runs the program SPOOL_OBJECTS. This job is sometimes run by RFCUSER, and sometimes by user WF-BATCH.

We've been live on SRM since 02/2007. We are trying to document all background jobs, and this one has slipped thru the cracks.

Can anyone shed some light on what this job is or what it does ?

Thanks

Sue

Edited by: Susan Keohan on Feb 5, 2008 11:24 AM

Accepted Solutions (1)

Accepted Solutions (1)

yann_bouillut
Active Contributor
0 Kudos

Hi Susan,

I guess it is the one from the configuration point "Set Control Parameters".

Here are an extract of the configuration help.

"

Set Control Parameters

You only perform this step if you create Materials Management documents in the backend system.

You specify:

Information about the spooler

Information about the update frequency

Documents in the backend system are updated asychronously. You can only further process the requirement coverage request in the Enterprise Buyer system after the update has been made.

The system checks at set intervals whether the backend documents have been created. If so, the system updates the requirement coverage request. Then the requirement coverage request can be further processed. If not, the system checks after the next interval whether the documents have been posted.

Example

You specify:

That the spooler should try to contact the backend system at ten-minute intervals

You enter the lead time in seconds

The system calculates the time until the next attempt as follows:

Time interval = lead time entered * square of the number of previous attempts

The backend user names that the system should use to start the retries

That the spooler should try to contact the backend system a maximum of ten times

Key Description Value

SPOOL_JOB_USER User name MEIER

SPOOL_LEAD_INTERVAL Lead time 600

SPOOL_MAX_RETRY Number of tries 10

For the update interval, you define:

That the system should check at 60 second intervals whether the backend documents have been posted

The backend user name that the system should use to start the retries

Key Description Value

CLEANER_INTERVAL Interval 60

CLEANER_JOB_USER User name SMITH

"

Kind regards,

Yann

Answers (1)

Answers (1)

keohanster
Active Contributor
0 Kudos

Thank you very much Yann. I suspected it was related to config, but wanted to be sure.

Regards,

Sue