What is external classic scenario?

[Former Member]

Gurus,

What is external classic scenario? Is this the other name for Plan driven procurement OR something else? Please clarify

Thanks,

Sid

[laurent_touillaud · Accepted solution]

Hi Siddarth,

Please see link below :

http://help.sap.com/saphelp_srm30/helpdata/en/0a/baf73a93ad9179e10000000a114084/content.htm

Regards,

Laurent

[Former Member]

Hi Siddarth,

This scenario is an extension of the classic scenario. Whereas in the classic scenario, goods and services are processed in the backend system, in the extended classic scenario, the procurement process takes place locally in SAP Enterprise Buyer and a copy of the data is replicated to the backend system. Communication between Enterprise Buyer and the backend system is via RFC. The purchase order is created locally in Enterprise Buyer.

If the data in the shopping cart is insufficient to generate a complete purchase order, you can supplement the data manually in SAP Enterprise Buyer before it is transferred to the backend system. The purchase order in SAP Enterprise Buyer is the leading purchase order. From SAP Enterprise Buyer Release 4.0 with an SAP backend system Release 4.6, the complete purchase order is replicated to the backend. It is a read-only copy and supplies the reference needed for the creation of goods receipts, service entry sheets, and invoices in the backend system. The plant is the criterion used for splitting shopping cart items into different purchase orders. This is because the purchasing organization is determined in the backend system based on he basis of the plant. Goods receipts (confirmations) and invoices can be pre-entered in Enterprise Buyer.

The following takes place in the Enterprise Buyer system:

Search for scource of supply, pricing, tax determination, commitments are updated in the backend system, account assignment and budget check are performed against the backend system.

Data for the Business Information Warehouse is updated partly from Enterprise Buyer and partly from the backend system: Purchase order data is updated from Enterprise Buyer, goods receipt and invoice data is updated from the backend system.

This scenario suits customers:

• Who want their purchasing department to save time and money by using the streamlined purchasing functionality of SAP Enterprise Buyer

• Who want to use the full sourcing capabilities SAP Enterprise Buyer offers, yet who also want to be able to confirm and invoice direct materials

• Who want the flexibility of being able to pre-enter confirmations and invoices in SAP Enterprise Buyer

The extended classic scenario does not support purchase orders based on limit shopping carts or procurement card functions, as these require the invoice to be local.

Hope this helps you.

Please Reward Points if useful..

Regards,

Sreenivas

[Former Member]

Thanks for your replies...both of them are referring more to extended classic scenario...I want to know about "external classic scenario"...

Thanks

Sid

[laurent_touillaud]

Hi Sid,

If you are talking about business scenarios there are only four as in link :

http://help.sap.com/saphelp_srm30/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/frameset.htm

I never heard of external classic scenario.

Where did you take this term from?

Regards,

Laurent.

[Former Member]

This was taken from the certification material.

Reference : SAP EBP 4.0 Configuration

Page no: 9-7

<i>As of EBP 4.0, you have full access to all sources of supply located in the corresponding back end

(contracts and purchasing information records) within the sourcing cockpit. These can be assigned to

requirements coming from the back end with a resulting purchase order created directly in the back end

(<u>External classic requirement</u>.)</i>