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

Similar Messages

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

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

I have been a loyal customer for years and have a hot spot because internet options are very limited in our rural area. I have stayed with 10G since the beginning. Most months I don't use the 10G. Verizon has no problem with me paying for Data I don't

I have been a loyal customer for years and have a hot spot because internet options are very limited in our rural area. I have stayed with 10G since the beginning. Most months I don't use the 10G. Verizon has no problem with me paying for Data I don't use. This month my daughter comes home from College and she accidentally uses 24G.....14 over get blind sided with $140.00 in overages. I called Verizon today......stopped in to the store today......My neighbor told me they waved charges for her one time. Lots of charges.....But I'm am getting no help. Not even an offer of a payment plan to help me out. I went back just 6 months and I have over paid for 19G.....Seems like they would like to help out their loyal customers!!!! Does anybody have any suggestions on how to deal with them? We are not wealthy....or I would just pay this and walk away......

There is a big misconception in what customers believe a cell carrier is obligated to do.
You pay a set price to use up to that amount of xx data. It makes no difference if you use it to the paid limit or way under. Its like peace of mind when you don't have to worry about a data counter.
Your daughter used the data, your plan is quite clear of what overage charges are. Why should or would Verizon wireless just forgive the charges because you are a customer? Your daughter used the data, get the money from her. That is the responsible thing to do.
There is no "I have been a loyal customer so please remove the $120, or $250, or $2,000.00 since I did not mean to use it"
Your electric company, or gas company or any other company does not remove valid charges. Why should Verizon wireless?
Just pay the invoice and don't think you are being mistreated because Verizon is a business and not a charity.
Good Luck

BBPSC18 - Request for external staff - Classic Scenario in SRM 5.0 possible

Hello Community,
one of my customers wants to use "Reqest for External Staff". As far as I remember, in SRM 5.0 it is only possible in "Standalone Scenario".
Is this assumption correct? So not possible in Classic Scenario?
How about "Extended Classic"? Probably not possible either, right?
Thanks for any help or input!
Cheers, Julian

Hi Rahul,
thanks for your answer!
Actually I am only looking into the part "Request for External Staff" - "Acceppt Bid" - "Create PO (Classic in ERP)".
I have seen that this part works in SRM 7.01.
But currently we are not planning to upgrade. We are still on 5.0.
I tested the abovementioned process in our DEV-System. I behaves fine, no error messages. But when I want to create the PO out of the "Check Status" (yes, in SRM 5.0 this was possible), the system pretends to create a PO but it never gets created. So I just wonder if I missed some customizing, or if this also only works in Standalone or if there maybe is a smart technical workaround (some custom coding etc...).
Cheers, Julian

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

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

Seeking recommendations for handling large binary documents with security(preferable) for inbound and outbound scenarios from OSB- SOA and SOA- OSB

Hi,
I am currently working on a project with the following requirements
1. Client transfers binary document (between 1-20MB in size) from OSB proxy to SOA composite to Content Management system
2. Client retrieves binary document (between 1-20MB in size) from Content Management system to SOA composite to OSB proxy
In otherwords, a inbound and outbound integration.
What I have tried so far and my results:
Scenario A
1. Enabled MTOM on SOA composite by attaching wsmtom policy
2. Created an OSB business service and consumed the SOA composite application
3. Enabled MTOM on OSB proxy and business service and configured it to pass by reference
Scenario B
1. Enabled MTOM and security on SOA composite by attaching wsmtom policy and SAML policy
2. Created an OSB business service and consumed the SOA composite application
3. Enabled MTOM on OSB proxy and business service and configured it to pass by reference
I have a demo integration setup that writes a binary document to a file using the above steps. My SOA composite has a file adapter that writes the binary data to an external file and it is exposed as a web service with a simple WSDL definition that has an inline XSD schema with an single element of base64binary type. I have added a mediator that maps this base64binary element node to the file adapter's input node.
Result for Scenario A with file size less than 1 MB:
Flawless execution with sub-second response times
Result for Scenario A with file size of 8MB
First attempt: SOA composite faults with database transaction related error, solved by increasing JTA timeout
Second attempt: Flawless execution, but file transfer took over 100 seconds to complete. This is very poor performance and my suspicions are that this cannot be the expected behaviour, but I dont know the internal workings of the SOA composite and why its taking this long.
Result for Scenario B:
The OSB business service does not accept/recognize the SAML policy in the WSDL and suggests to configure OWSM policies manually, but OWSM policy in OSB does not have the wsmtom policy. Regardless of this, any permutation of MTOM + WSS security in this integration scenario either did not work outright or MTOM optimization was not happening ie binary data was materalizing in the message body.
I have only about 3 weeks left to implement a viable solution and the closest ive come to a solution is Scenario A but that +100 second response time for an 8MB file is really worrying.
I would appreciate any level of guidance, recommendations or suggestions as to how I go about tackling this problem.
Thanks
regards,
Johnny

I think this is due to the underlying mechanism of weblogic classloading..
You can contact oracle support @ https://support.oracle.com to report issues. Roughly this is the process .
1- get the Oracle Customer Support Identifier (CSI) for the client you are working for.
2- Create a user profile quoting the CSI. This will send an approval request to oracle support admins at your client.
3- Get the oracle support admins at your client site to approve your request for support access.
4-Once they approve , you can access the support site and raise service requests.

XI content for SRM and CCM scenario - mapping

Hi All,
We are using the standard business content for integrating SRM with CCM to update contract information from SRM to CCM. Both SRM and CCM are on the same system.
The configuration scenario used is MasterDataInclusionInCatalogOnWAS700 which is in the name space SAP CATALOG CONT.MGMT. 2.0_700 , http://sap.com/xi/CCM/CAT.
There are 2 interfaces being referred by this scenario: CatalogUpdateNotification_Out and this CatalogUpdateNotification_In and both the interfaces are pointing to the same meesage type CatalogTransmission but they are in different name spaces.
Once the scenario was configured there was no interface mapping available in the standard business content to map the above 2 interfaces.
SAP SRM SERVER 5.5
CatalogUpdateNotification_Out
CatalogTransmission
http://sap.com/xi/EBP
SAP CATALOG CONT.MGMT. 2.0_700 ,
CatalogUpdateNotification_In
CatalogTransmission
http://sap.com/xi/CCM/CAT
Is this the normal case and we need to develop our own mapping or is the standard content not imported correctly?
The service pack details are as follows:
PI 7.0 SP level 14
XI content
u2022 SAP BASIS 7.00 - SP 14
u2022 SAP CATALOG CONT.MGMT. 2.0_700 - SP 12
u2022 SAP SRM SERVER 5.5 - SP 11
u2022 SAP ABA 7.00 - SP 14
Thanks,
Shravan

ditto, anybody received a response from SAP with regards to this problem?
As suggested above, we could build our own mapping in XI but this would obviously be a modification to SAP standard which we would prefer to avoid.
Regards, Kyle.
OK Received a response from SAP dated Oct. 9, 2008
I assume that you have installed NW 7.00 SP14 (or higher).
Within earlier versions the mapping from XML to ABAP was to lax.
The XML message was processed witout regarding the name of the root
element. This was fixed with SP14.
When you call an interface the XML message must match with the type
defined in the WSDL used for proxy generation.
Either the message or the WSDL used to generate the proxy seems to be
wrong here.
Here is a work around should solve this problem until we make available in a standard note soon.
I will do it internally to our development team but I am sorry that i can not tell now when the note will be ready.
Disable the new check by adding the following entry in transaction sproxset
-Name: ST_USE_LAX_ON
-Value: X
-User: <empty>
-Inactive: <empty>
Edited by: Kyle Freeman on Oct 9, 2008 5:54 PM

Network lagging for printing and classic

I have a weird problem. I just upgraded an iMac tray-load 333Mhz 320mb ram to OS 10.3.9 from OS 9.2.2 and now when I go to print it takes up to 20 mins per page. Also when running a filemaker database from a mac server in Classic the network lag makes the database almost unuseable. I know it's not the printer because it printer (HP Laserjet 2200D) as it works just fine with 3 other iMac computers on the same network. The database also works just fine on the other 3 computers. Listing files on other computers via file-sharing is also sluggish (explains the database slowness). I have tried swapping the network cables and hooking up to a different hub. I thought it might just be the ethernet card going out but internet browsing is plenty fast (tested at DSL reports.com)

Just a thought, Depending on a couple of things, If you Installed from scratch the HP Printer Set-up utility or you are trying to carry it over from 9.2 I find it best to start from scratch that includes going to HP's site and download the latest updates and drivers for your Operating System and Printer. If they download to your desktop be sure you drag them to the Applicatins and Hp Folder before you double click and launch them if they do not go there automaticlly.
Cheers Don

Vendor Return for WM and HUM Scenario.

Hi.
We have a requirement where we need to return the stock back to the vendor.The stocks are HU managed and also the TR and TO has been created.Above all we have mapped the return cycle from SD route.Ie we have created the vendor as customer and assigned to the vendor along with Notification.
Please help me TCode wise the flow of cycles.
Yogesh Walde

Hi
This is resolved(changed the confirmation to inbound delivery) and when iam posting GR with inbound delivery ,getting the below message.
No item category exists (Table T184L HID V )

Difference between Classic Scenario and Extended Classic Scenario

Hi Expers,
I need your help again........:-)
I just want to know what is the differne between classic and Extended Classic Scenario.
Points will be rewarded
Thank you
sam

Hi Sam,
(explaination frm a previous thread)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Please check this too:
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
BR,
Disha.

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 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

Customizing for extended and classic scenarios

Similar Messages

Maybe you are looking for