Difference in PO creation in Classic v/s Extended Classic

[Former Member]

Hi all,

Can anyone tell me in details what is the difference in PO creation in Classic v/s extended classic scenario technically e.g. BAPI,FM etc?

What are the main settings which determine whether PO needs to be created in SRM(local PO) or backend ECC system?

[Former Member · Accepted solution]

Hi

Classic --> PO is created by a RFC call on SC Approval. Once SC is approved, SRM System makes a RFC call using driver function modules , this call uses ECC BAPIs - BAPI_PO_CREATE1 for creation of a PO in ECC

Extended Classic -- Once SRM PO is approved, System makes a call to backend for creation of a ECC PO using the above concept , if you change the PO in SRM, the change is updated in ECC using BAPI_PO_CHANGE.

Determination of Classic and Extended Classic Scenario primarily depends on the settings you make in IMG (Define backend system for product category). At the same time you can use BBP_EXTLOCALPO_BADI to have additional parameters in determining Classic or Extended classic scenario for your processes

Regards

Virender Singh

[Former Member · Accepted solution]

Thanks for the info.

However in case of ECS,when SC is approved,how is the PO automatically created?

[Former Member · Accepted solution]

Hi Ram

In that case too same BAPI_PO_CREATE1 is called in ECC by RFC from SRM. The only difference here is some indicator flows into ECC which makes that PO in ECC as display only. You can find that indicator by debugging the data at the interface.

Regards

Virender Singh

[Former Member · Accepted solution]

I am clear on PO replication in R/3.I need to know how is PO created automatically from SC in case of Extended classic scenario?Is ita background process??Is so,technically how is it done?

[Former Member · Accepted solution]

Hi Ram,

Did you get the answer for your question. can you please let me know what program/Bapi is used to create PO in SRM ECS after shopping cart approval?

Regards

Deepu

[Former Member · Accepted solution]

Are you talking about IMG > SAP SRM > SRM Server > Sourcing > Define Sourcing for Product Categories?

• performance assistance help text below?****

1. Sourcing is never carried out

This is the default setting at delivery.

SAP Enterprise Buyer does not transfer any items to the purchaser's sourcing application.

2. Sourcing is always carried out

SAP Enterprise Buyer transfers each item to the purchaser's sourcing application.

3. Sourcing is carried out for items without a source of supply

SAP Enterprise Buyer transfers all requirements that have multiple sources of supply, of which none are assigned, to the purchaser's sourcing application. Once you have selected a source of supply in the shopping cart, the item does not go to the sourcing application and a PO is created.

4. Sourcing via automatic bid invitation for items without a source of supply

SAP Enterprise Buyer creates a bid invitation for all requirements that do not have a source of supply.

5. Automatic requirement grouping; sourcing for items without assigned source of supply

If a source of supply is assigned to a requirement, the report Automatic Grouping of Requirements for POs and Bid Invitations automatically attempts to create a PO from several requirements. If it is unable to do this, the requirement is displayed so that you can assign it manually in the sourcing application. Once you have assigned a source of supply, you can submit the requirement to the report.

6. Automatic requirement grouping; sourcing is never carried out

If a source of supply is assigned to a requirement, the report Automatic Grouping of Requirements for POs and Bid Invitations automatically attempts to create a PO from several requirements. If it unable to do this, the system creates an incomplete PO for the requirement.

7. Automatic grouping and creation of a bid invitation in the case of items without assigned source of supply

If a source of supply is not assigned, the report Automatic Grouping of Requirements for POs and Bid Invitations automatically attempts to create a bid invitation from several requirement items. If is unable to do so, this is recorded in the error log of the report.

[Former Member]

Hi,

In case of SRM classic scenario, is there a  way to call some BAPI and update existing POs in SAP R/3 from SAP SRM Shopping Carts?

Please advise.

Regards,

Ankur

[Yateesh_h]

Hi Ankur,

Once a back-end document is created for a shopping cart (SC), there is not much freedom to change the SC (you can delete line items, etc..).

One of the possible solutions would be to create 'Change Shopping Carts' (not a standard feature). These SCs after approval will create PRs in the back-end system. The PR can then be adopted to the PO in ME22N. This will ensure traceability for changing POs through Shopping Carts.

Hope this helps

Cheers,

Yateesh

[Former Member]

Hi Ram,

Once the SC is created in EBP it has to go through sourcing cockpit (for source of supply) and approvals (if required ) and the PO can be created automatically or through the Purchaser .

In ex. classic the BADI :BBP_EXTLOCALPO_BADI is also used according to your business requirement for PO creation.

IS