Decoupled scenario

Hi All,
I know that decoupled scenario means any combination of classic, extended classic and standalone scenario.
My client is using extended classic scenario, but now require to create Import Purchase Orders as classic scenario.
Could you give me steps to create from a shopping cart a purchase order as classic scenario.
Thanks in advance,
Martí

Hi Martin,
Still if you didnt get the answer , then here is the information for you.
you can use the BADI BBP_EXTLOCALPO_BADI for your requirement.
Following are the useful links
http://wiki.sdn.sap.com/wiki/display/SRM/BBP_EXTLOCALPO_BADI
Classic to Extended Classic
Best Regards,
Srini

Similar Messages

Decoupled scenario and HR

Hi ppl,
I have a couple of questions:
a.]Can someone give me a real time eample of why a company will undertake a decoupled scenario?Why have the burden of maintaing records in two systems(back-end and SRM)?
b.]During HR replication:when we replicate users from back end to SRM, how does the replicated user atatch itself to the SU01 user id created in SRM?Do we maintain any attribute in the organization?What if there is no SU01 user id created in SRM?
Please share your views!
Jack

Hello,
a. Decoupled is good if you want to completely separate processes for different materials. That does not mean maintenance of records in two but only in respective system. Also, SRM can be used without material master records, only catalog entries are necessary. Those you must produce anyway. We are using classic scenario just for some materials but I think that decoupled will be better. By my opinion, if you are planning to switch all procurement to SRM decoupled is better start. Anyhow you can define scenario on product category.
b. System is responsible to attach users to positions. You need to maintain infotype 0105 subtype 0001 in HR system to enable this. This is only way.
As for replication without SU01 user in table T77S0 there is switch HRALX/USRAC . If you set this switch to "X" relationships are created without user existence. I do not know you release but note 550055 is a good start. In it you will find links to other relevant notes describing thing in more detail.
HTH
Gordan

Bid decoupled scenario

Hi all,
We are running SRM 7.01 and using the Bid Decoupled Scenario.
We create the RFX in SRM and send it to the Supplier Portal (SUS). We have checked in the SXI_MONITOR and goes out SRM and enters SUS without any error.
Where can I see the RFX in SUS? There isn´t any object type (BUSxxxx) to see it in BBP_PD.
Thanks
Ezequiel

Hi Sam,
you are right, there are errors in the inbond monitor in SUS side.
In /n/sappo/ppo2 transaction there are two errors messages related to the RFX we are transferring:
1-Partner 0000602461 not found
2-Partner 0000000101 not found with partner function type Bidder
Error 1: Partner 0000602461 not found:
This is the Business Partner of the Purchaser in SRM. Do we have to transfer, replicate or create purchasers in SUS?
Error 2: Partner 0000000101 not found with partner function type Bidder
This Business Partner is the contact person for the vendor 3000062 in SUS. We have created it in BP as Bidder but still same error occurs.
Thanks for your help
Ezequiel

Decoupled Scenario Error

Hi Gurus,
I have active a Classic Scenario and I´m trying to create in Standalone scenario the SC for 1 specific Product category.
Already configure the Product Category as local.
Although when I try to create the shopping cart I get an error of the Company Code and close the window.
Please let me know the config. I missing.
Currently using SRM 7.0
Regards.

Hello,
In order to have decoupled scenario active, badi BBP_EXTLOCALPO_BADI should be used to flag PO as local or not.
Regards,
Ricardo

Decoupled scenario small clarification

Hi SRM Gurus,
We are now using the Stand-Alone scenario and now we want to go for Extended Classic scenario for certain Product categories. In this regard I have one doubt which is mentioned below.
Can we go with local product categories for ECS scenario or not?
And also please give me some pointers for this scenario.
Award the points.
Regards,
Ram

check this link
http://help.sap.com/saphelp_srm50/helpdata/en/0a/baf73a93ad9179e10000000a114084/content.htm
you can use local categories for ECS
BR
Dinesh

Can we use the Extended Classic Scenario with MM-SUS

HI, expert :
    In extended classic scenario ,the PO created in SRM system ,and then replicated into the MM system .You can't change it in MM system .
    So, in this situation ,I want to know the MM-SUS can be suitable or not ?The PO can transfer from ECC to SUS ?
   If I use the decoupled scenario ,which one I can select ?MM-SUS or EBP -sus ?
   BR !
Alex!

Hi Alex,
as noted by Bill, in MM-SUS is the extended classic not possible at all.
By default it's also not supported in the SRM-SUS. Please see the note 543544. If you would like to activate this, you need to pay a consulting fee for SAP:
"Please note that the full scenario can be enabled by a consulting solution, compare OSS note 700350."
Regards,
Peter

Use the MM-SUS in Extended Classic Scenario

HI,my experts :
    The standard function doesn't support the MM-SUS in Extended Classic Scenario .Now I may have two questions about it .
1、 I have one ECC system .I need handle the invice in the ECC system .In other word ,the invoice rcreated in the SUS should transfer to the MM system .But in EBP-SUS ,the invoice is transfered to the SRM system .What can I do now ?
2、 If I want to use the decoupled scenario ,some POs are create in EBP ,and others are created in MM .Now ,which sus I should select ? EBP-SUS or MM-SUS?
   Or some detail document about it .
BR!
   Alex!
Edited by: Alex on May 25, 2010 9:17 AM

Khan has explained most of the things.
The external web service I meant is actually OPI catalog which you need to maintain.
The same has to be entered in the attribute CAT of the EBP purchaser.
To maintain the call structure of this catalog
Get the URL from SE80->BSP appln->ros_prescreen->controller->main.do
then give the client no of yr ROS client
the RFC user user ID from EBP to ROS
it's password
sap-sessioncmd=open
sap-language=sy-langu
the operational purchaser role in EBP (sap_EC_BBP_OP_PURCHASER) should be linked with
the same in ROS via role menu->business partner->screen supplier->right click->change details
->sap-client=ROS client no
The administrator & op purchaser should be present in ROS org structure also
& should have same userID & password as EBP
you have to define the vendor root, the root of the purchasing organization and the currency in
table BBP_MARKETP_INFO in the SRM System (Enterprise Buyer client).
BR
Dinesh

How differentiate POs classic scenario and POs extended classic scenario?

Hi Gurus,
Is possible determine that some POs are generated in SRM system and send to R3 (Extended classic scenario) and other POs only to send from SRM to R3 system (classic scenario) in the same system?
How we can differentiate which POs should be sent to R3 (classic scenario) and which not? Is possible use type of document for example? Could you explain me if exists standard process?
The objective is determining the following: Is necessary differentiating POs created in SRM of importation and should be sent to R3 system (classic scenario), and in case of local POs (not importation) is necessary extended classic scenario.
I have understood that there is a scenario that includes the Classic and Extended Classic, I think is called Decoupled scenario.
Thanks for your help!!

Hello,
Yes this is possible.
You can do it automatically based on the product category. You must define the back-end system you wish to use for each product category by making the relevant settings in Customizing for SAP SRM under SRM Server --> Technical Basic Settings --> Define Backend System for Product Category
Check the online documentation here: http://help.sap.com/saphelp_srm701/helpdata/en/f3/6f505050404ce99151722a79a2c089/frameset.htm
You can also use Business Add-In BBP_EXTLOCALPO_BADI to overwrite settings made in Activate Extended Classic Scenario and implement more rues for the scenario determination, e.g. based on the purchasing organization for manually created PO's.
First you set you system to Activate Extended Classic Scenario : SPRO --> SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
Then you set exceptions in the BAdI.
Regards
Franck

SRM scenario XI / PI requirements

Hi all,
i have a question regarding XI requirements in SRM scenarios. What are the requirements for CLASSIC, EXTENDED CLASSIC, STAND ALONE and DECOUPLED scenarios? Are there standard contents for all of them? I understand that in CLASSIC, the connection of ERP and SRM-EBP is via RFC. Can we use XI instead for the integration to be clear?

Hi
Downlaod SAP SRM SERVER and SRM SERVER IC tpz and import them in IR.
one of these would have the mappings and the other would contain service intrefaces. If you want to make any changes, copy this to a custom and make releavnt changes.
Regards
Monika

SRM scenario's difference

hi everyone,
i want to know the difference& functionality of technical scenarios in SRM............
1) can we activate the classic &extn. classic at the same time?is it possible.
2) is it possible to replicate the material from SRM to R/3? but i know from R/3 to SRM.
3) which technical scenario is better for industry requirements?
can anyone pls put an eye to solve these.points will b awarded. send asap.
Warm Regards
rakhi

Hi,
For all your questions I think Claudia answers are correct. Just to add one more point that defining the backend documents whether to happen in SRM or R/3 can be done in Purchasing group and Product category combination in SPRO.
That kind of scenario is called Decoupled Scenario. Normally when we opt for direct material (STOCK) the system behaves as extended classic. For consumables classic will be good option.
Regards,
Munna

SAP SRM Scenarios

Is it possible to revert back to classic scenario , after extended classic scenario has been implemented in the system in SAP SRM ? If so, how to perform that activity ? Thanks.

Hi Harini,
If the extended classic checkbox is checked, then you cannot revert this setting back.
But even though you have this extended scenario activated you can always have classic scenario also running with few SPRO settings to control the same using product categories.
This becomes your decoupled scenario.
Hope this helps/.
Regards
-sam

Various scenario

Dear Experts,
what is the difference between these different scenarios
Pls. explain it so that a beginner can understand it.
The classic scenario
The extended classic scenario
The decoupled scenario
The standalone scenario
Kindly Regards
Marco M

Hi,
In addition to what Muthu has given.
There are Two Scenarios in SAP SRM
1.Technical Scenario
2.Business Scenario.
1)TECHNICAL SCENARIO:
The classic scenario
The extended classic scenario
The decoupled scenario
The standalone scenario
What you have mentioned is Technical Scenario.
2) BUSINESS SCENARIO
1.Self Service Procurement -Classic Scenario
2.Self Service Procurement -Extended Classic scenario
3.Plan Driven Procurement.
4.Service Porcurement
5.Contract Management
6.Master Data Management
7.Sourcing
8.Spend Analytics
For any company to implement SAP SRM they have take one ore more scenarios to be Implement depending onthe business
process
Mandatory : To take one scenario from Each .
Regards
G.Ganesh Kumar.

Help on EWM scenarios

Dear EWM Experts,
I am in need of some quick help.
I am in the process of preparing some EWM scenarios for an internal Demo.
Kindly help me out with 3 simple scenarios which I can build for a demo on EWM Functionalities.
I am new to EWM.
Appreciate your response.
Thanks,
SShetty

Hi Chinna,
This could be defined as easily or as complex as you like, I will go for the easy route:
Standalone/Decoupled Scenario: Local documents only, only direct integration with backend systems is for FICO data. No follow on docs are passed to a backend.
Classic Scenario: ERP backend is the leading system, all follow on docs created in the backend not locally.
Extended Classic Scenario: Local documents created in the SRM-SERVER and a COPY is sent to the ERP backend(s).
In a nutshell, thats about it .... of course there is a lot to each scenario other than this but this describes the basics of the scenarios.
Regards,
Jason

PO status in " error In Process ".

Hi Experts,
We have some POs that are stuck in SRM with status as " Error in Process ".
The PO is got replicated to R/3.
The Workflow Log is Completed.
But in Follow-on Documents the status shows as " Error in Process ".
Can you pl. guide me int his issue.
Thanks & Regards
Sachin

Hi,
We have the same type of problem in creating invoices for our SRM 5.0 decoupled scenario.
The invoice is created and not shows any error and gives a completed message. But if we see follow-on documents it says as "Invoice -
Error in Process"
Do anybody has the same prob. solved.
Kindly suggest from gurus.
Sincerely,
Sridhar.
Message was edited by:
P.T. Sridharbabu

SRM -ECC: CIN_Plan_Driven_Procurement_SupplierEnablement

Has anyone used this add on scenario for Plan driven procurement.
Please let us know how to use this. The scenario is a bit confusing.
Thanks and Regards,
Himadri

Hi
There are 4 points regarding replicaton of produt master. As it is mentioned above ,
1. if you are going to user directl procurement (Extended classic) scenario you need to replicate locations (Plant) & Product master into SRM.
2. In case if you are managing contracts in SRM and replicating to ECC (either srm 7.0 / 5.0 versions) then you need to replicate product master to SRM in order to create GOA / Central contractrs against a prodcut
3. If your implementation is decoupled scenario (Classic + Ext.classic), and you want to create reservations in ECC through SRM then you need to replicate products into SRM
4. Finally, when your implementation scenario is Classic then if you user SRM for stock procuremnent / reservations creations from SRM then you need to replicate product master to SRM.
Hope this will give you more clarity on your query.
Regards,
Krish
Edited by: Krish on Feb 1, 2012 9:27 AM

Decoupled scenario

Similar Messages

Maybe you are looking for