SRM Help

[Former Member]

Friends,

As I am preparing for the SRM Certification Test, I need some help.

I have the following questions, can someone pl. help me to clear my doubts ?

1. With EBP 3.0, the classic scenario is replaced with the extended classic scenario.

My question : Is it true ?

2. The Business Connector for exchange of data between EBP and the catalog.

What is Business Connector ? Is Business Connector means XI ?

3. The message types and BAPIs that are defined in the distribution model are later

transferred to the back-end in either synchronous or asynchronous fashion,

according to type.

Since the Model's can ONLY be distributed from EPB to back-end and regened in back-end,

I believe the transfer to the back-end happens in asynchronous fashion. Is that true ?

I may come back with more questions, please help me out. .

If anyone have any SRM Certification questions, please pass on to me @ ramesh.vasudevan@gmail.com

Thank you

Ramesh V

[former_member195032]

Hi Ramesh,

1. Classical and extended classic are just two scenarios ,rather technical scenario's and none is replacing other.

2.You can treat it like that business connector is now XI.

http://help.sap.com/saphelp_nw04/helpdata/en/6a/3f93404f673028e10000000a1550b0/content.htm

3.It happen in synchronos way.

Documents are forwarded to you id.

Regards,Nishant

Message was edited by:

Nishant Rajan

[Former Member]

Thank you Nishant..

You can count on my points

Ramesh V

[Former Member]

Hello Ramesh,

Just to ellaborate the answers further:

1. apart from classic & extended classic - Decoupled & Standalone are two other tech scenario.

In classic -R/3 is leading system i.e. purchasing docs are created in R/3.

Ex. classic- EBP is leading system i.e.purchasing docs are created in EBP.

Decoupled - Product category(Matl grp) can decide the leading sys.

Standalone - SRM works with SAP/NON SAP FI

My observation is that Classic is more popular scenario because industries like to use

shopping & approving capabilities of SRM with robust purchasing facilities of ECC.

2. Business Connector

A middleware application based on the B2B integration server from webMethods.

The SAP Business Connector enables both bi-directional synchronous communication and asynchronous communication between SAP applications and SAP and non-SAP applications.

The SAP Business Connector makes all SAP functions that are available via BAPIs or IDocs accessible to business partners over the Internet as an XML-based service.

The SAP Business Connector uses the Internet as a communication platform and XML or HTML as the data format. It integrates non-SAP products by using an open, non-proprietary technology.

3. no need of ellaboration

BR

Dinesh

<b>Reward if helps</b>