SOCO Submit to Grouping functionality?

[Former Member]

Hi SRM people,

Does anyone knows what does the Submit to Grouping button in the Carry Out Sourcing option do. I know that after pressing that button, report BBP_SC_TRANSFER_GROUPED must be executed, but I don't know the consequences.

Thanks in advance,

Sidney Mora

[Former Member · Accepted solution]

Hi Sidney,

the Submit to Grouping Button just flags the REQ to be called later. Within the

Sourcing Cockpit the flagged Reqs then can be called and a collective PO can be

generated. Unfortunatly the flagged Req stays available in the Sourcing Cockpit.

There is no standard available to prevent this. I assume, that is only possible via

Z Transaction and modification of the grouping function.

Thanks,

Claudia

[Former Member]

Hi

<b>Read the Documentation given in the report.</b>

For your reference, here it is.

Short text
Automatic Grouping of Requirements for POs and Bid Invitations

Purpose
This report groups together requirement items to which a valid source of supply has been assigned (for grouping into purchase orders) and whose product category has been enabled for grouping (sourcing option in Customizing).

In cases where assignment is automatic, the system sets the requirement as Transferred to Grouping.

In cases where a source of supply is assigned manually, the purchaser has to choose the function Transfer to Grouping in the sourcing application for the requirements.

You should schedule this report periodically, and make sure that the report is run separately for each document type (purchase order, bid invitation).


Prerequisites
You have assigned each relevant product category to a sourcing option for grouping, for example, Automatic Grouping, Sourcing for Item Without Assigned Source of Supply.

For more information, see the Implementation Guide (IMG) for Supplier Relationship Management: SRM Server -> Sourcing -> Define Sourcing for Product Categories.

Features
Report BBP_SC_TRANSFER_GROUPED provides the following functions:

For automatically grouping requirements into purchase orders:

It selects all requirements that have a unique valid source of supply, and have been set up for grouping. You can use selection criteria to further restrict the requirements that are selected.
It groups requirements by vendor. In other words, it groups together all of the requirements that can be sent to the same vendor.
You can use a Business Add-In (BAdI) to make additional groupings. If the standard system groups together certain requirements, but you want to create them in separate local purchase orders, use the BAdI BBP_GROUP_LOC_PO for this purpose.
Note that there are some limitations to creating purchase orders this way. For example, it is not possible to group together requirements with different vendors in the same purchase order. This report uses the same differentiation criteria as the sourcing application (for example, business partner, company code, product type).
It uses function module BBP_PD_PO_CHECK to check the assignment to a source of supply. The report passes on requirements to function module BBP_PD_SC_TRANS_MULTI_LOC_PO, where they are grouped, and converted into a purchase order.
In a production run (that is, not a test run), the system issues error messages to the Application Monitor. Example: A contract item assigned during sourcing is no longer valid when grouping is about to occur. This error appears in the Application Monitor. The system moves the requirement item to the worklist of the sourcing application.
The Application Monitor assigns errors to one of the following categories:
Shopping Cart: Automatic Grouping
Purchase Order: Automatic Grouping
If necessary, you can copy this report, and change the selection criteria to suit your needs. You can start the report in test mode.
Note: In the sourcing application, you can determine which requirements are planned for the next report run by choosing Find -> For Grouping.

For automatically grouping requirements into bid invitations:

It selects all requirements that have been set up for grouping. A source of supply is not required. You can use selection criteria to further restrict the requirements that are selected.
You can use the BAdI BBP_TRANSFER_GROUP to take bid invitations that have been grouped by the system, and then split them up on the basis of your own customer-specific criteria. You can use the BAdI BBP_SAVE_BID_ON_HOLD to determine whether or not a bid invitation should be published automatically.
The report passes on requirements to function module BBP_PD_SC_TRANSFER_MULTI_RFQ, where they are grouped, and converted into a bid invitation.
In a production run (that is, not a test run), the system issues error messages to the Application Monitor.
If necessary, you can copy this report, and change the selection criteria to suit your needs. You can start the report in test mode.
Note: In the sourcing application, you can determine which requirements are planned for the next report run by choosing Find -> For Grouping.




Output
The report displays the purchase orders or bid invitations resulting from the grouping of the requirements. It also shows incorrect requirements that the system was unable to group into a purchase order or bid invitation.

Regards

- Atul

[Former Member]

Hi Atul,

The problem is that, when the report is executed, a purchase order document is generated in the backend system. But, the sourcing appears again in the SOCO, and it can be use to generate another PO.

Is there a way to avoid this behavior.

Thanks in advance,

Regards

Sidney Mora

[Former Member]

Hi

Which SAP version are you using ? <u>Please refer to this OSS notes.</u>

<b>

918169 BBP_SC_TRANSFER_GROUPED cannot use BADI BBP_GROUP_LOC_PO

883539 BBP_SC_TRANSFER_GROUPED picks up wrong line item

Note 520848 - Update of external requirements with existing purchase order

826487 Additions to upgrade on SAP SRM Server 5.5

913848 Add. Info.: Upgrade to SAP SRM Server 5.5 SR1

802048 Description of PO missing after grouping

983582 SOCO: Proposed vendor is not converted to fixed vendor

1027026 BBP_BID_INV: BBP_TRANSFER_GROUP doesnt split bid invitation

441932 Updating: Mapping for order incorrect

202400 Processing of sales documents with SAP APO

481906 SNP - PP/DS integration (documentation)

890882 Termination in the grouping report for bid invitations

832393 Release Restrictions for SCM 5.0

673398 Source of supply as split criteria for consolidation report

838890 No document-specific error messages from grouping report

</b>

Hope this will help.

Please reward full points, incase it suits your requirements.

Regards

- Atul