External requirements and Classical scenario

Hi experts
Is there some restriction concerning the use of external requirements in Classical scenario?
Is there some some sap note about it?
Thanks
Nilson

Hi Nilson,
Pls refer Note 505030 - Restrictions for the integration of external requirements.
Regards,
Prashant
Do reward points for helpful answers

Similar Messages

Central Contract, MDM Catalog, and classic scenario

Dear SAP experts,
We are in SRM 7.01 with backend ECC 6.05 deploying classic scenario. We are using Central Contract Management in which we negotiate contract in SRM and later distribute it to ECC. We also plan to use SRM-MDM Catalog.
We notice that if we are using classic scenaro, the contract that is used as reference is the contract number in ECC (the one distributed from SRM). So at first we assume that if we want to push the contract data to MDM, we should have pushed the ECC Contract number. However we find out that actually SAP block the ECC Contract coming as distribution from SRM to go to MDM.
Our second option is to use distribution of contract from SRM to catalog. It does using SRM contract number. We create SC and then we pull the catalog item from the catalog (which contain SRM contract number) and then we order. However we end up with 'error in process' in which the system try to create a PR instead in the ECC (meaning that the contract number cannot be read).
We're puzzled with this. How can we use the combination of central contract, MDM catalog and classic scenario? Can we use the combination?
Best regards,
John

Maria
If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
Then local contract data should pick as SOS from the vendor list.
If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
Let me know if the above works or not.
PS : Reward points if helpful.
Regards
Jagadish

Partial quantity of Material in Extended and Classic Scenarios

Does it possible to pass partial quantity of Material into Extended and Classic Scenario ;for instance we have 100 qty for a material & out of them 60 qty goes to Extended PO and 40 qty goes to Classic in backend system .
If yes so how & what criteria would be ?

Hi Lalit,
Until now we did not use both classic and extended classic for one organization.
Are you using that or you just have a doubt??
Regards,
Satish

Local contract and classic scenario

Hi all
A question regarding contracts - and interpretation...
On help.sap.com the following is stated:
<i>SAP Enterprise Buyer, as the central purchasing system, saves the contract data and uses it for local purchase orders and purchase orders of the extended classic scenario.</i>
I interpret this as, if one is using the classic scenario it's not possible to operate with local contracts in the SRM system. Can anyone confirm this?
And if so - any workarounds?
Our dilemma is that we have an extended classic scenario. Some materials are stock materials, and for these materials we are using a BAdi to switch off the extended classic scenario. No contract data is now added to the shopping cart, which I think is due to the classic scenario.
Thanks for your help in advance
;o)
Maria

Maria
If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
Then local contract data should pick as SOS from the vendor list.
If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
Let me know if the above works or not.
PS : Reward points if helpful.
Regards
Jagadish

Limit SC and Classic scenario

Hi Guru's,
Just want to clarify if it's possible to create limit SC and directly createa BE limit PO without using Ext. Classic Scenario?
Thanks in advance,
Thomas

Hi Michael,
We are currently using a SRM 4.0 and we do NOT use ECS.
My problem is that we normaly only give access to BBPSC02 to our users and I do not see the limit position here.
Another thig is that when I create a limit position,the PO is not created because the sloc is missing.
We use the new BAPI_CREATE1 to create the POin BE.
/Thomas

Customizing for extended and classic scenarios

Hi,
I know what is the difference between classic and extended classic scenarios.
But i want to know what is the difference in the customizing.
I understand that there is a badi that decides on the product categories and also there is a customizing for assigning product categories to back end systems.
I want to know what is the significance of this customizing?
Regards
abaper sap

Hi Abaper
in spro
activate extended classic scenario determines the technical scenario as ECS.
and your PO created in SRM system so it is a leading system in SRM.
your PO messages are created in SRM and sent it suppliers from here not from ECC.
all PO transaction type must be defined in SRM system.
you can go EBP_SUS scenario if customer interested.
like many..
Here in ECS , you can use local contracts....
br
muthu

External Requirements and local Product Categories

Hi all,
please could you assist:
We are running SRM 7 with several ECC backends in ECS.
We would like to transfer ext. requirement from one backend to SRM (via BBP_EXTREQ_TRANSFER).
No problems so far.
Prerequisites:
Product categories should only be maintained local in SRM (no r3MATCLASS).
Idea for Solution:
Use of BADI PRODUCT_CUSTOMER2 and BBP_DOC_CHANGE_BADI to use the internal product category for replicated materials and for the Inbound external requirements
Questions:
If we now transfer an external requirement from ECC to SRM (including a product), how does SRM behave (STANDARD)?
Is it mandatory to obtain the replicated product in SRM including the backend product category?
That would mean, we have to replicate the product categories from ECC as well and could not map the incoming requirements to "our" SRM interlanl product categories?
Any experience concerning standard SRM checks for external requirements?
Thanks and best regards
Andreas

Problem solved
We have just mantained local product categories.
Replicated products (from ERP) are automatically switched to these local categories

External requirement handling in SRM using classic scenario

Hi Experts,
We have a requirement in Classic scenario:
PRs for MRO / indirect materials generated in PM / PS of ERP will be transferred to SRM using WF interface for approval process.
Upon final approval in SRM, Follow-on document PO should be created in the back end.
The SC in SRM should have the status u201CApprovedu201D & u2018Follow-on Documentu2019 created.
My question is SRM standard will create a PO as follow-on doc after the SC is approved in SRM. How to control this creation of PO in SRM & only approval message should be transferred to back end ERP.
Pls provide any suggestions or inputs on technical settings / adjustments to be carried out.
Note that we cannot use PDP scenario as SRM will be used only for SC approval process.
Tks.

Thanks Muthu for the reply.
The doc flow in the link above shows that after SC is approved, it will be available in sourcing cockpit for further processing (i.e. RFX, PO etc) in SRM. Our requirement should not be allowed to create PO in SRM and it should be allowed only in back end ECC.
SRM is used to centralize the approval process where multiple back end systems are connected. (How ever, in future follow-on docs are also created in SRM).
Current Target steps:
1. Create PR from PM/PS in ECC (PR status will be "In release").
2. Transfer PR to SRM and SC will be created (SC status will be "In approval").
3. SC will be Approved / or Rejected in SRM. (PR status will be updated to Approved / or Rejected in ECC).
4. If approved, follow-on doc PO (manual or automatic) will be created in ECC. (SC status will be updated to EX: "PO cretaed")
When the SC is in the process of approval, user in ECC may add new items or make changes to PR from PM/PS. After these changes, the current approval WF for SC in SRM should be cancelled and new SC is created and so on...
Sophisticated message synchronization is required between ECC & SRM.
Is it possible to acheave the above solution (create PO only in back end system) using the steps mentioned in doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" with some modifications.
Forgot to mention the following system details:
ERP - ECC with EhP4
SRM - SRM 7.0
Thanks,

External requirement from non SAP system created in SRM 7.0 Extended Classi

Hello SRM Gurus:
Has anyone created an external requirement using XI ExternalRequirement_Create_In (http://sap.com/xi/EBP). We are getting a E001 "No company code could be determined for backend for product##". I traced the error to FM 'BAPI_SCEC_CREATE' in class "CL_BBPX_EXTERNAL_REQUIREMENT". What I found is that it check the attributes for BUK and updates a table with the backend EEC system. Then it checks if any of the entries match our external non SAP system in our external requirement and since it is a non SAP system none do. Then it sets a return error code.
I configured our non SAP system in the SLD and in SPRO under "Define System Landscape" as a non SAP system.
We are running external classic scenario. We just want to created a shopping cart from an external non SAP system. Source the shopping cart in SRM and create the PO in SRM/ECC. We are not using a product master but creating "describe requirement" in our external system. Our product categories are replicated from ECC and the same codes used in our external non SAP planning system.
If I change the external planning system to the ECC backend system, the external requirement is created in SRM but when I source it and convert it to a PO, it returns a backend error that the external requirement number does not exist in ECC. Therefore it appears all of our data from our external system is correct with the exception of how to deternine the backend company code
According to SAP this should be possible using XI.
Has anyone been successful doing this or can you please advise any OSS notes or documentation explaining how to do this. Please advise if you need additikonal info.
Thanks in advance.
Bert

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

Central Contract Management in case of Classic Scenario

Hi,
At our current implementation, requirement is to implement both Service procurement(with hierarchy) and Central Conract Management. I was exploring the possibility of utilizing Central Contract Management with Classic scenario.
Will the Central Contracts created in this fashion be available in Sourcing Cockpit for the buyer to select against Purchase Requisitions? Will the Central Contract be visible at all in SRM in this case ?
Please respond only with reference to Classic scenario.
Thanks,
Abhilash

Yes the Central Contract will be available in the Sourcing Cockpit, both local and classic scenario's. Yes the Central Contracts will be available for the creation of Purchase Requisitions in R/3 and to assign SOS in R/3.
Do know that for SRM 7.0 PI is required for setting up Central Contracts. This is promised to change with the release of EHP1 for SRM (due june 2010).
Kind regards,
Tim

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

SRM 7 PPS Classic Scenario with Plan Driven Procurement?

Hello experts, I want to know if the combination of SRM 7 PPS Classic Scenario with Plan Driven Procurement is possible? or if there any limitation to consider? Our client needs to create purchase requisition in ERP -> send this purchase requisitions to SRM (as shopping carts) create bids - > quotations - > create contract from accepted quotations and then from the contract we need to create purchase order but this one must be created in ERP (classic scenario) Someone has experimented the same situation? Best regards and thanks for your Help.
Liam

Hi Lima ,
Classic scenario wont support PPS .
        - Stand alone and classic scenario not supported
        - Shopping cart renamed to Purchase Requisition
        - Shopping cart generate (pre)commitment in funds management
        - Contract can create Funds Reservation (Earmarked Funds) in Funds Management as a Guarantee
        - Goods Receipt and Invoice created in ERP
        - Mixed PO: PO with lines that works like contract lines, a PO can be created from these lines
        - PO created from contracts or mixed-PO is named call-off PO. Only is a new name, is a "normal" SRM      PO
        - Goods receipt possible in SRM only in "easy" cases
Thanks & Regards
Pradeep Kumar Dondeti

Why Extended Classic Scenario

Hello
I understand the difference between Extended Classic and Classic Scenario with the follow on document creation. But, I need to understand the business benifits of implementing Extended Classic Scenario as opposed to Classic Scenario in SRM. In what business scenario do one suggest Extended Classic.
Appreciate every answer
Thanks
Vijay

Hi Vijay,
The most important thing to consider when choosing the implementation scenario is to consider which system will support the different steps of the procurement process.
In case of the classic scenario, after creation of the request (shopping cart) in SRM, the remaining process steps will be handled / supported in the back-end system (ECC). Goods receipt can be executed in both systems. This would be a good choice if the organization has already an operational back-end system and the users from the purchasing department are already familiar (and happy) with all the MM functionality. SRM will only function as a support tool for administrating the purchasing needs of the end-users in the organization.
In case of the extended-classic implementation scenario the complete purchasing process will be supported in the SRM system (most organizations prefer to use the back-end system for invoice verification). Thus requesters, purchasers, goods recipients etc. all will use the SRM system to support their respective activities. This would be the preferred scenario in case both MM (ECC) and SRM are new to the organisation and will be implemented together.
SRM offers the different users a nicer user interface as opposed to the R/3 screens. Also the (strategic) sourcing capabilities of SRM can only be used when implementing the extended classic scenario. Same for the Suplier Enablement business scenariou2019s. Most are only supported when extended classic is active.
So depending on the intentions of the organization a choice can be made. SRM only as a tool for administrating the decentralized request from the end users in the organization: Classic scenario will suffice. SRM as a tool to support the complete purchasing process, from sourcing till evaluation - Extended classic will be the correct choice.
Regards,
Skander

SRM with PPS = Extended Classic Scenario

Does SRM Procurement for Public Sector (PPS) require Extended Classic Scenario? If so, could some one refer me to an official documentation that states such? Thanks.

http://wiki.sdn.sap.com/wiki/display/SRM/PPS-ProcurementforPublicSector-+enhancements
PPS is only possible by ECS only.
Muthu

SRM PPS using classic scenario

Hi SRM Experts,
I am exploring the possibility of implementing PPS in SRM 7 using the classic scenario.
Please let me know if it is possible and how can it be achieved.
Earlier threads mention that PPS is only available using extended classic.
Thanks.
Regards,
Amish

Hi Amish ,
PSS scenario is not supported for classic scenario ,
changes in procurement process of SRM 7.0
        - Stand alone and classic scenario not supported
        - Shopping cart renamed to Purchase Requisition
        - Shopping cart generate (pre)commitment in funds management
        - Contract can create Funds Reservation (Earmarked Funds) in Funds Management as a Guarantee
        - Goods Receipt and Invoice created in ERP
        - Mixed PO: PO with lines that works like contract lines, a PO can be created from these lines
        - PO created from contracts or mixed-PO is named call-off PO. Only is a new name, is a "normal" SRM      PO
        - Goods receipt possible in SRM only in "easy" cases
Thanks& Regards
Pradeep Kumar Dondeti

External requirements and Classical scenario

Similar Messages

Maybe you are looking for