Hi Arjman,
to your questions:
1) The majority of the follow-on doucments are asynchronously created in SRM. The report CLEAN_REQREQ_UP checks whether this asynchronously triggered follow-on documents are indeed created (technically the report reads the table BBP_DOCUMENT_TAB, and checks whether the follow-on documents are there). An example: in the classic scenario the report checks whether the follow-on doucument purchase requisition is created in the backend system.
2) The report BBP_GET_STATUS_2 checks for changes in the follow-on documents, and if needed it updates the originating document. Example: In the classic scenario there was a Purchase Requisition created from the SC. In case you delete a line item form this Purchase Requisition, the BBP_GET_STATUS_2 will update the history of the SC line item.
3) In case the of classic scenario it's possible to delete PO line items which are created from Shopping Carts. When you delete a line item in the backend PO, the BBP_GET_STATUS_2 will update the SC in the SRM system: in the history you will see, that the follow-on document was deleted, and the item should land in the SOC.
4) Once the SC is approved, no change more is allowed on it (you won't get the change mode in the transaction 'Check status').
However you still will be able to delete the SC line item by pushing the trash icon, and you also can delete the follow-on documents of this SC. This is the current standard behavior.
You can only prevent changes on the SC when you archive the SC, or the follow-on documents have also other follow-on douments. Example: SC -> PO in the backend -> CF -> INV. In this case the SC line item cannot be deleted.
5) This case shouldn't happen without manual interaciton. Normally for this cases the system creates an entry in the alert monitor. Ther the administrator can delete the SC line item, or delete it. Now in your case I suppose you don't have thie alert entry. You can recreate this with the report BBP_ALERT_SB_NOTTRANSFERED as described in the note 441768. Than the administrator can delete the SC line item.
6) In the 'BBP_DOCUMENT_TAB ' shouldn't be older entries, this is only a table for temporary check. Each entry, which is older than one day, has some trouble. This entries sould - and the corresponding SRM documents should be checked one by one.
7) I don't understand the question.
Regards,
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.