How to activate classic scenario?

Dear experts,
What are the generic settings required to activate classic scenario?Are there other settings required other than below?
1. If extended classic scenario is not activated in global mode:
a. Replicate product categories from ERP backend to SRM system.
b. Define an ERP backend system as the target system for the product categories.
c. Define backend Objects for the product categories (based on Purchasing group and source system).
Does any additional settings required for classic scenario?
2. If there is global activation of extended classic scenario?
a. In such cases, We need to take care of BAdi 'BBP_EXT_LOC_PO' and 'BBP_Det_Logsys'.
Do we need any other additional settings?
Thanks in advance,
Ranjan

Classic scenario is the default scenario unless you have activated the Extended Classic. If you do not need Extended classic then you do not need to activate the Extended Classic and deal with BADI's BBP_EXTLOCALPO_BADI, BBP_TARGET_OBJECTS,BBP_TARGET_OBJTYPE.
If the need is only to implement Classic Scenario accross the board then the steps are good to start with.
Regards,
Surya

Similar Messages

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

How to activate Classic on 10.4.11

Just got 10.4.7 and installed and upgraded to 10.4.11 OK. Loaded a lot of applications OK. Now I need to run an old application under Classic. Cannot use my 10.4.7 install disk as I'm now on 10.4.11. I have copied a valid 9.2 system file across (one which works with 10.3.9) but Classic will not start. Any help would be much appreciated.

Booting into 9 and using Classic are two different things, though both can be done from the same Mac OS 9 system folder if the Mac supports it.
In the time period 2003 to 2006 new Macs were released that were in a limbo state of being able to use Classic, but not being able to boot into 9.
Classic is the environment that is launched when you are in Mac OS X and double click on a Mac OS 9 only application, or a Mac OS X application whose Get Info box has been checked to launch in the Classic environment, or Apple menu -> System Preferences -> Classic has been told to launch at a specific time, or the Mac OS 9 menu in the upper right is told to launch. It allows Mac OS 9 and Mac OS X applications to run side by side without rebooting. It does have limited driver support for Mac OS 9 compatible printers and scanners. The iBook G4 can do this, and so can any PowerMac G4 and PowerMac G5 with 10.4.11 or earlier.
Booting into Mac OS 9 is what is done when you go to Apple menu -> System Preferences -> Startup Disk and select a Mac OS 9 system folder, and click on restart and get the Mac OS 9 splash screen upon doing that. The iBook G4 was not capable of this, but the iBook G3 was. PowerMac G4s that are MDD with no Firewire 800 can do it, but PowerMac G4s that have Firewire 800 can't do it.
When booting into Mac OS 9, the full library of Mac OS 9 compatible printer and scanner drivers is available to you. Leopard, 10.5, does not limit the booting of 9 on those machines that support it, but only a handful of Macs support both Leopard and booting into 9.
Message was edited by: a brody

Selective activation of classic scenario

Dear Experts,
One of my client has globally activated extended classic scenario. Now, they want to activate classic scenario for one particular product category. How they will achieve that?
Which BAdi they need to take care? Is BBP_Determine_logsys is enough?
thanks and regards,
Ranjan

Hi, we have implemented BBP_EXTLOCALPO_BADI, and when we create PO from SOCO everything works fine.
But when we create PO from vendor Bid, with "Create PO" button the BADI BBP_EXTLOCALPO_BADI doesn´t execute.
Can you help me please?
Thanks in advance.
Best Regards.

Extended Classic Scenario - how does the integration work ?

Hi,
Apologies for asking a basic question, but we are looking at requirements for integrating SRM with R/3 using the extended classic scenario and I need to understand how the integration actually works ? How is the data transferred between the 2 systems ? Does it use BADI's, idocs etc ?
Many thanks,
fiona

Hi Olaf,
I just wanted to give some precision on what you said (in the thread How to "see" PO in EBP ? also)
The Extended classic scenario only refers to the local PO creation replicated in R/3.
In this scenario, in the R/3 PO only the data not managed/sent from the SRM are available for modification (which depends on the SRM version you use)
The "PR transfer from R/3" is called "Plan driven procurement", and in this scenario only RFC is used, the qRFC are only used for BDocs of the CRM Middleware.
Regards.
Vadim

How to choose diffetent PO types in R/3 from a SC in Classic Scenario

Hello everyone,
I am working with SRM 5.0 in a classic scenario and I have a problem. I create a SC, then it is sent to sourcing cockpit where I assign it a vendor to create a PO, but I can't choose what kind of PO I want to create.
In PPOMA_BB, the user has at least 2 different PO's in attribute BSA and attribute DP_PROC_TY. When I create a PO from a Bid invitation I can choose this kind of POs.
Do you know how to choose different POs type from SC??
Thanks,
Ivá

Hi,
For backend products,In standard you can not choose what PO you want. By default the backend document type 'EC' is chosen. In number ranges for SC followon documents the interval number 'PO' would correspond to backend EC document external interval number. This is the standard behaviour though you might have maintained BSA attribute with other values in addition to EC.
For local products you can choose the PO transaction type. After youclick on create purchase order, in the next screen you will get an option choose your transaction type, provided you have maintained these in PPOMA_BBP for BSA attribute.
Hope this clarifies.
Rgds,
RRK

How to know which BAPi is being used for creation of PO in classic scenario

Hello Experts,
We are in SRM 7.0 classic scenario.
How can we know which BAPI is being used in the calssic scenario i.e. How can we know if we are usind BAPI_PO_CREATE or BAPI_PO_CREATE1 for creation of PO?
Any pointers will be highly appreciated.
Thank you in advance,
Thanks & Regards,
RKS

Hi RKS
yesterday BLOG by our SUMMER WANG helps every SRM consultant to debug the PO error
/people/summer.wang/blog/2010/05/11/trouble-shooting-of-srm-po-transfer-error
Good work Summer wang !!
Muthu

Activate extended classic scenario

Hello, when I try to activate extended classic scenario to create contracts in SRM and then transfer them to R/3 I have these options:
Extended local PO
BE Purch Grps Resp.
Back-end check reqd
Back-end errors, show as error msg
Which options may I have to select?
Thanks in advance

Hi,
I think Rosa's requirement is to create a manual and local contract in SRM. Indeed you mentioned an excellent BADi, but my understanding is this badi gets called from the sourcing application. I am not sure whether this gets called from the SRM local contract. This is the help documentation I am pasting here. It would be wonderful if this works. See the highlighted "importing parameters" part of the following pasted one.
Thank you,
DV
Determine Target System of Contract
Use
With method CONTRACT_LOGSYS_DETERMINE, you can control the target system determination for contracts.
In the standard, the Sourcing application and SAP Bidding Engine create contracts locally in SAP Enterprise Buyer . With this method, you can create a contract in the backend system instead.
Requirements
You are using a backend system with Release 4.6B or higher.
You have created the logical system in activity Define Logical System
Parameters
Importing
The BAdI takes this data from requirements in SAP Bidding Engine (bid) or from requirements in the Sourcing application.
IT_HEADER
Header structures
IT_ITEMS
Item structures
IT_PARTNER
Business partner data such as vendor or location
IT_ORG
Organizational data
Changing
In the method you can overwrite the following field:
CV_LOGSYS
Name of the system in which a contract is to be created.
If this field remains empty or contains the name of the local system, then the contract is created locally.
If this field contains the name of a backend system, then the contract is created there.
Notes
When coding the method, use the delivered sample coding as a guide.
See also
BAdI Determine Backend System / Company Code

How is PR created in Extended Classic Scenario

Hai friends
How is PR created in Extended classic Scenario
Please let me know
Regards
Krishna

Hi krishna,
Shopping cart in SRM is equal to PR in R/3.If it is Classic scenario we can customise to create PR in backend for the shopping cart in EBP , but in ECS directly PO will be created against the shopping cart in EBP and it will replicate to R/3 system.
Regards,
Baparao.

In an extended classic scenario, how can we make few purchase orders to sta

Hi All,
In an extended classic scenario, how can we make few purchase orders to stay local (i.e. without copying it to the back end). The decision criteria to stay local is information other than product category, i.e. using pcard and the cart value.
Thanks
Murali

Murali,
As I said usually this integration is done using ALE - IDOCs. You can find the all the configuration do be done here.
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
In this the filtering can be done at two levels.
1. Data Filtering
2. Segment Filtering
Data Filtering:
Data filtering can be done in dustribution model where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Look at BD64 where you can do the config for data filtering.
Regards,
Ravi
Note : Please mark the helpful answers

Documents / Cookbook on how to configure Extended Classic Scenario?

We currently have the Classic scenario and are thinking of changing to exteded classic becuase we want to use the sourcing cockpit in SRM 7.0. Does anyone have any good documentation on how to configured Extended Classic?

Hi Sivakumar,
If you mean how to archive PO in MM side, please refer to the following info:
====
In ECC system, if you want to archive a MM PO, please use transaction
SARA->archive object MM_EKKO.
456129 FAQ: Archiving in purchasing
401318 Archiving: Additional information
====
If you want to delete this ECC PO, please use BAPI_PO_CHANGE and
refer to the following test data:
Parameters:    PURCHASEORDER      = XXXXXXXXX
Parameters:    POITEM
PO_ITEM                        = 00010
DELETE_IND                     = X
Parameters:    POITEMX
PO_ITEM                        = 00010
PO_ITEMX                       = X
DELETE_IND                     = X
You also need to run BAPI_TRANSACTION_COMMIT after BAPI_PO_CHANGE for updating the change.
Regards,
Ivy

How to get SC number for backend PO in classic scenario

Hello,
In classic scenario, how can I retrieve the SC number from PO backend number.
Best Regards,
Lina

Hi,
Please look at BBP_PD transaction. You will get better understanding how GUID are linked.
Table   CRMD_ORDERADM_I
GUID                         DDC1CD43BF9E69F1881A00505631332B
OBJECT_TYPE          BUS2121001
HEADER                    DDC1CD43BF9E2FF1881A00505631332B
Table   CRMD_ORDERADM_H
GUID                         DDC1CD43BF9E2FF1881A00505631332B
OBJECT_ID               0010000077
OBJECT_TYPE          BUS2121
You can also use Function Modules. Please go to SE80 transaction and check Function Group BBP_PD_SC.
Regards,
Masa

How can we know in classic scenario, whether confirmation has been done in

Hi ,
In Self service procurement with classic scenario:
I believe that we can do confirmation in EBP or in R/3.
How can we know in classic scenario after confirmation, whether confirmation has been done in EBP or in R/3.
Also please give an idea is there any configuration difference for confirmation need to do in EBP.
thanks
RESHMA

Hello Reshma,
>
Reshmab wrote:
> How can we know in classic scenario after confirmation, whether confirmation has been done in EBP or in R/3.
> (...)
Using Web GUI (ITS or Portal), if you look at the SC history (or PO history) in table mode, if column where you find SC number as no value for confirmation (confirmation with SRM number range), this means PO was confirmed directly in R/3 with a Goods Receipt.
Using SAP GUI, if confirmation was done in SRM purchasing document exists in CRMD_ORDERADM_H for PROCESS_TYPE = 'CONF',
>
Reshmab wrote:
> Also please give an idea is there any configuration difference for confirmation need to do in EBP.
> (...)
There is no specific customizing to allow SRM confirmation: just give correct role to users in order access to confirmation transactions (authorization object BBP_PD_CNF ). Check with roles EMPLOYEE* or PURCHASER*.
Regards.
Laurent.

SRM & SUS in Classic scenario

Hello SRM Gurus,
I would be great if you could give your overview for below my quires.
I have good idea of SRM with SUS for extended classic scenario. But how would be the communication between SRM and SUS in Classic scenario. Because the PO will be created in backend.
Now my question is in Classic scenario,
What is the use of SUS in classic scenario?
How the PO will be transfer to SUS system? Does the PO data from SRM or ECC?
What is the communication data between SRM and SUS?
Kindly provide me above information and also your thoughts.
Thanks.
Regards,
Magesh.

Hi Mahesh,
If you are using SRM7.0 & ECC EHP4 version with classic scenario then you can user configuration gudie "Plan-Driven Procurement with Supplier Integration: Configuration Guide" (Release SRM4.0).
But following keys points are to be noted for SRM7.0:
1. "PO" and "service entry confirmation" will be handled using XML messages.
2. To send PO's using XML messages to SUS from ECC activate the workflow in SWETYPV transaction by falging "Linkage activated" for object BUS2012(CHANGED & CREATED) for workflow ws3800008.
3. take the help of PI consulatant to enalbed the PI messages to send PO and Serivce confiramtion bewtween SUS and ECC.
ERP     PurchaseOrderERPRequest_out_V1                          PurchaseOrderERPRequest_In_V1                         SRM
SRM     PurchaseOrderERPConfirmation_Out_V1     PurchaseOrderERPConfirmation_In_V1                         ERP
SRM     ServiceAcknowledgementERPCreateRequest_Out     ServiceAcknowledgementERPCreateRequest_In     ERP
ERP     ServiceAcknowledgementERPConfirmation_Out     ServiceAcknowledgementERPConfirmation_In     SRM
ERP               ServiceAcknowledgementERPCancellationNotification_Out                                                                                    ServiceAcknowledgementERPCancellationNotification_In     SRM
With Regards
Manjunath

Info Record Not Appearing for all materials in classic scenario.

HI ALL,
 I am working on Classic Scenario and all the follow-on documents are getting created properly. But the problem is With SOS. Currently i am able to view the info record for only one of my material, I am also referring backend contracts through vendor list. The contracts are visible in SOS.
 Can somebody pls put a light as to why for other materials the info records is not displayed in SOS, is there a report which has to be run to get the info record into SRM from ECC. If not then how does the system bring these contracts and info record from ECC to SRM.
 I am working on SRM 5.0 and ECC 5.0.
THANKS AND REGARDS
Debu

Hi
Please read this as well.
You have created sources of supply. These could be:
-> Contract items in Enterprise Buyer
-> Vendor-specific prices
For this, you have created Product Linkages in the SRM System with vendor-specific prices via the SAP Menu Master Data -> Products -> Process Products.
-> Entries in the vendor list of Enterprise Buyer
In Customizing you have assigned product categories to which the system is to automatically group requirements and you have scheduled report BP_SC_TRANSFER_GROUPED to run periodically.
For more information, see the Supplier Relationship Management Implementation Guide (IMG): SRM Server -> Sourcing -> Define Interactive Sourcing for Product Categories.
Sourcing is completely integrated with the global availability check in SAP APO and executes a vendor search. You can activate third-party order processing in the check instructions by choosing how you want the system to start sourcing and which sourcing method you want to use for it. There are two different options here:
○ If you want the products to be delivered exclusively by external vendors, the system performs sourcing directly at the external vendors without evaluating internal locations. For this, SAP APO requires corresponding purchasing records, delivery plans and contracts that are transferred from SAP ECC.
○ If you only want to have products delivered by external vendors occasionally, that is to say, if you are unable to deliver the product from your own warehouse stock, choose an ATP profile in which both internal and external vendors are evaluated. In this case, the external vendor is treated like an internal location in SAP APO, and is integrated into location determination in the rule-based availability check.
You can also choose the vendor manually. If you have already specified a vendor as the source of supply in SAP CRM, SAP SCM does not carry out any further sourcing. In this case, SAP SCM merely checks the validity of this vendor and confirms the requirement in its full amount if the vendor is valid.
For more information, see SAP Library for SAP SCM at SAP Advanced Planning and Optimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Advanced Availability Check Methods -> Third-Party Order Processing in the Global ATP -> Sourcing in Third-Party Order Processing.
Refer these links for more details ->
Assignment of Existing Sources of Supply
http://help.sap.com/saphelp_srm50/helpdata/en/25/40f23a53cd0e04e10000000a11402f/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/55/4af548688211d4977e0004ac962ee6/frameset.htm
http://help.sap.com/saphelp_crm50/helpdata/en/fa/84944279c0c66ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/63/36f2323326da4da25d9d0a06f550a0/frameset.htm
Processing Contracts
http://help.sap.com/saphelp_srm50/helpdata/en/43/0f234a9e242a8be10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/5a/4cc5376848616ae10000009b38f889/frameset.htm
See alsoSAP Note 519794 EBP: Replication of Materials exclusively for Purchasing
SAP Note 505030 (Restrictions for the integration of external requirements).
Regards
- Atul

How to activate classic scenario?

Similar Messages

Maybe you are looking for