schedule jobs in SRM

[Former Member]

Hi

may i know the purpose of scheduled jobs in SRM like BBP_GET STATUS2 and CLEAN REQREQUP. i just want to know why/when we are using these jobs in SRM.

please suggest me with your finest solutions. kindly help.

Regards

sss

[Former Member]

thank you

Regards

sss

[dean_hinson2]

Hello,

BBP_GET_STATUS_2 Update Status Information

Description:

After the documents (purchase requisition, purchase order, reservation) have been created in the backend system for a requirement coverage request, the following references are stored in the requirement coverage request:

The name of the backend system in which the documents exist.

The document numbers

Subsequent activities for the documents can take place in the backend system. For example, a goods receipt for a purchase order. Using the report "Update requirement coverage requests", you can transfer the following information on subsequent activities from the backend system to the Enterprise Buyer System:

For the purchase requisition: the purchase order that was created with reference to the purchase requisition, the goods receipt quantity and the invoiced quantity for the purchase order

For the purchase order: the goods receipt quantity and the invoiced quantity

For the reservation: the quantity withdrawn

The report always updates all requirement coverage requests for which documents have been created.

You should only start the report in the background. We recommend starting the report daily. In this way, you ensure that the information that the user sees in the "Status and Delete" scenario is up-to-date.

Output

The report either issues a message stating that the changes have been made successfully, or issues an error log.

The log can contain the following types of errors:

In the Enterprise Buyer system, there is the information that the requirement coverage request has been transferred to the backend system (status 6), but no reference is transferred to the requirement coverage request.

The system did not find the R/3 document to which the cross-reference is made.

In this case, the report only writes the changes to the Enterprise Buyer system for those requirement coverage requests that do not contain errors.

Communication errors

CLEAN_REQREQ_UP reads table BBP_DOCUMENT_TAB and checks if the relevant follow-on document has been created for an SRM document.

If the follow-on document exists, the object relationships for the SRM document are updated, the status is set, and the relevant entry is deleted from table BBP_DOCUMENT_TAB.

If the follow-on document does not exist, the entry remains in table BBP_DOCUMENT_TAB, where it can be checked again the next time the report is run.

Background:

If follow-on documents (local or backend documents) are created for SRM documents, the checks to see if a follow-on document can be created are run synchronously. However, the actual creation of the follow-on document is carried out asynchronously.

In order to check if a follow-on document has actually been created, an entry is written to system BBP_DOCUMENT_TAB in SRM. This entry contains the object type and object ID of the SRM document and the object type, ID and system of the follow-on document.

You should schedule report CLEAN_REQREQ_UP as a job so that it runs at regular intervals.

Regards, Dean

Edited by: Dean Hinson on Jun 10, 2009 7:17 PM