Services in extended classic scenarios

Friends,
We have implemented services in extended classic scenario. When we create a shopping cart with two service lines and same product category here is what happens:
The SRM PO has two lines items but in the backend the PO is replicated with one Po line item and the two service lines from the shopping cart. This causes a inconsistency with the SRM PO line item number and R/3 PO line item number.
Please advise. Any help is greatly appreciated

Hi Donna,
Is is standard functionnality as the backend PO has item type "D" for service in the first line.
Then for sub item, only limits or services (Id or description) are allowed.
The first line is dedicated to product category.
All sublines belonging to this product category are implemented in the sub item in the service tab.
I have opened an OSS message too but for other services bugs.
Please post SAP answers to update SDN community
Kind regards,
Yann

Similar Messages

Error while creating Manual Service PO in Extended Classic Scenario

Hi Experts,
Extended Classic scenario (SRM 7.0 with ECC 6.0) While Creating Manual Service PO in SRM i am getting the below mentioned error messages. Can any one suggest what could be the problem.
Error Msgs:
1. Backend Error:In case of account assignment, please enter acc. assignment data for item
2. Backend Error:Purchase order still contains faulty items
Regards,
Mohan

Hi,
Yes i given all CC and GL information properly in Purchase Order Document for Service.. Still finding the error for Service PO alone.
Pl do the needful
Regards,
Mohan

Service procurement using Extended classic scenario

Hi All,
Can Extended classic scenarion supports service procurement.
I mean SC with services and PO with services in SRM without hierarchies
If not any work arounds
Abdul Raheem

Hi Abdul ,
Service procurement using Extended classic scenario is not possible
PO wont able to create in SRM .
Thanks & Regards
Pradeep Kumar Dondeti

Service Procurement in Extended Classic Scenario

Hi,
We are planning to use SRM 7 EHP 1 with backend ECC 6 EHP 4. We are leaning toward the extended classic scenario. However we are a bit confused reading some documentation that saying Service Procurement classic can only be used in classic scenario.
What does this mean? To put this in more simple, can we have this scenario in extended classic deployment:
PDP:
1. We create PR with 2 items, each item have 3 sub-line services,
2. We push this PR to SRM
3. We create PO in SRM and it is copied to ECC.
4. PO will have 2 items, with each item have 3 sub-line services.
Self Service Procurement:
1. We create SC with 2 items, each items have 3 sub-line services,
2. We create PO in SRM and it is copied to ECC
3. PO will have 2 items, with each item have 3 sub-line services.
Really appreciate if someone can clarify this point.
Best regards,
Josh

Dear Josh,
For your scenarios below:
Self Service Procurement:
1. We create SC with 2 items, each items have 3 sub-line services,
2. We create PO in SRM and it is copied to ECC
3. PO will have 2 items, with each item have 3 sub-line services.
The shopping cart and PO in local SRM system does not support service hierarchy (Service subline) in the system.
PDP:
1. We create PR with 2 items, each item have 3 sub-line services,
2. We push this PR to SRM
3. We create PO in SRM and it is copied to ECC.
4. PO will have 2 items, with each item have 3 sub-line services.
Here also, the system will not create po in the local srm system. The local PO cannot support service hierarchy. The system by default create the purchase order in the backend system directly.
Thanks and regards,
Ranjan

Classic Scenanio and Extended Classic Scenario

Hi all,
I would implement on the same system 2 different scenario:
1. Classic Scenario for self service procurement
2. Extended Classic Scenario for the following business scenario:
a. PR from ECC is transfered into Sourcing Cockpit with Plan Driven Scenario
b. buyer convert the SC created in Sourcing Cockpit into a GOA or a PO that are transfered to ECC.
Can coexist this different scenario?
Can I address this different scenario only with organizational differences?
Thanks
Bye
Marco

Hi Marco,
I see 2 quick ways to realise your requirement.
The first is to create an attribute in t77omattr for a position and maintain that attribute in the organisational model. This attribute could just be filled with an X for example.
Then you have to implement BADI BBP_EXTLOCALPO_BADI and retrieve the attribute you created with FM BBP_READ_ATTRIBUTES (use sy-uname to retrieve the attribute for the current user).
The 2nd is to create a Z-table with the user-ids that you want to use the local (or ECS) scenario. Then again in BADI BBP_EXTLOCALPO_BADI you have to write the logic to retrieve and compare this.
Keep in mind that these are user-based distinctions and not based on scenario.

Classic / Extended Classic Scenario for Shopping Cart

Dear Friends,
We are working on two different business scenarios with same Product type, Product and Product Category where we would like to control Extended Classic Scenario.
1. Self Service procurement to be executed in Classic Scenario as the follow-on document (Purchase Requisition) should be created in backed ECC system.
2. Plan Driven Procurement cycle where External requirement is transferred from backend ECC to SRM keeping Extended Classic scenario active so that system creates Shopping cart in SRM.
So which condition should I use to control the Classic / Extended Classic Scenario in BADI BBP_EXTLOCALPO_BADI method DETERMINE_EXTPO.
Regards,
Sandeep Parab

Thanks Pierre,
My Sourcing requirement is working as desired with following code in BADI BBP_SRC_DETERMINE (method DETERMINE_SOURCING).
method IF_EX_BBP_SRC_DETERMINE~DETERMINE_SOURCING.
DATA: w_header TYPE BBP_PDS_SC_HEADER_D.
CALL FUNCTION 'BBP_PD_SC_GETDETAIL'
EXPORTING
    I_GUID = HEADER_BBP_GUID
IMPORTING
    E_HEADER = w_header .
IF sy-subrc = 0.
IF w_header-subtype = 'ER'.
    SOURCING = 'X'.
ELSE.
    SOURCING = ' '.
ENDIF.
ENDIF.
endmethod.
However Im not able to control the Classic and Extended Classic Scenario even after introducing field EXT_DEMID in structure BBPS_EXTPO_BADI in badi BBP_EXTLOCALPO_BADI and method DETERMINE_EXTPO.
method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
IF ITEM_DATA-EXT_DEMID = ' '.
BBP_EXTPO_GL = ' '.   for classic
ELSE.
BBP_EXTPO_GL = 'X'.   for extended classic
ENDIF.
endmethod.
No idea y this is not working to my knowledge it should work
What do you think ? this this code and badi actiation im not able to perform SSP in classic mode and sourcing with extended classic mode.
Regards,
Sandeep Parab.

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

Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
Please provide some help in solving this issue.

Hello,
This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC). And accepting the SES in ML81N will generate GR posting.
For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
So basically, for service items you create confirmation and for materials you create ASN.
Regards,
Prasanna

Limit items on extended classic scenario.

Hi everybody.
We are working in SRM 4.0 with extended classic scenario.
We are testing limit items (not service items), but I can not understand the limit item functionality.
In SC, we can assign contracts form limit items. But when we create PO from the SC, there is not any relationship between PO and contract. Moreover when I create a PO (limit item) from null, I can not assign any contract (field is not available).
In the other hand, in SC (limit item), I can select Follow-Up Actions as Confirmation and Invoice or Invoice. If I select Confirmation and Invoice, when I create a PO, ECC return me a message error, because in ECC, good receives are not allowed for PO with limit item category.
So, I have some questions:
1. Can I use limit items in PO with contract reference?
2. If yes, how can I do it? If not, what is the tab contracts functionality in SC with limit items?
3. What is the functionality to allow confirmations in SC with limit items?
4. Is there any documentation about limit item functionality?
Thanks and regards.
Raúl Moncada.

Hello,
As far as I know, this is a technical limitation. A work around would affect other functionalities.
Note 1358679 corrected such issue.
Regards,
Ricardo

Does SRM 7 Extended Classic Scenario support PCards?

Does SRM 7 Extended Classic Scenario support PCards as standard? I know SRM 4 does not but wanted to know if that has changed.

Paul,
URL https://websmp208.sap-ag.de/support ( service.sap.com) ...on header
Go to 'Release& Upgrade Info' ..then sub item 'Release notes'....look for SAP Solutions on left scroll...then select SRM...
Open pdf file ' Release Notes SAP SRM 2007, SP00 - SP04 '...and look for pg # 40...
Let me know if you did not get it..
Thanks,
Rahul Mandale

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.

Classic Scenario to Extended Classic Scenario

Hi friends,
   We have a requirement to migrate an existing SRM 5.0 solution from Classic to Extended Classic scenario.
   Is there any best practices document available from SAP in this regard? Also what are the things that need to be taken care of in particular? It would be great if some one can share his/her practical experience.
   Thanks in advance!
Best regards,
Pradip

Hello
If it is Plan driven procurement involved, better to go for 'Classic' scenario. Extended classic scenario is best suited for self service procurement of indirect material.(of course both scenario are best for indirect material!)
Now Switching over to Classic ti Extended classic:
1) Technical settings-->Define product categories for backend
    Here source sys is ERP backend and the Target sys is SRM client
2) Nu. ranges for Local P.Os
3) In Cross application basic settings, Activate extended Classing Scenario and Backend pur.grp responsible
4) In Define Objects in Backend system(Pur.req, Resrv, P.O)
    Ensure no entries are there. Since this step is not required for Extended classic
5) BAdi need to be activated.
Before all these, ensure there is no pending documents/transactions exists. All need to be closed. No open purchase documents!
The best guide for ref. is by Shah Khan.
Regards

GR based IV check box suppressed - Extended Classic Scenario

Hello Folks,
How are you doing today ?
We are working in SRM 5.0 Extended Classic scenario.
When created the Local PO in SRM with GR Based IV Check box active, the
follow-on back-end Purchase order is generated without this flag. In
other terms, system is creating the follow-on ECC PO without GR Based
IV check box active. As a result, we are unable to run the ERS cycle.
Back-end system in above scenario is ECC 6.0. And vendor settings are
maintained with GR based IV flag on in both ECC and SRM.
Kindly advice.
Thank you for your assistance !

Hi Ravi and Yann,
Thank you for your inputs. OSS note-956083 can not be applied in my case due to the hight system version (patch level 550).
I have already raised this issue to SAP, but in the lack of proper infrastrucure SAP can not access the system. (BASIS guys are still struggling with it)
Well...let me give you recap-
We have not activated nor implemented any BAdi so far (Vanila SRM 5.0 EC scenario) PO creation for goods is working fine and as desired. But when it come across with PO with limit item or services, system throws an error as -
"PO 5100000263: Service-based invoice verif. requires GR "NO" or G R-based invoice verif."
Would deeply appreciate if you guys can share insight on this issue.
Thank you for your assistance!

Extended Classic Scenarios Basic Queries

Dear SRM Experts,
I am working in the demo of extended classic scenario in SRM 7.0. I have some basic questions on it, Kindly reply for my doubts :
1. Do SRM-SUS Scenario applicable for all three procurements
     a. Self-Service Procurement
     b. Plan Driven Procurement
     c. Service Procurement.
or applicatbility only for Service Procurement .
2. Is it necessary to implement MM-SUS (Classic Scenario) first before implement of SRM-SUS? (Setting UP IDocs etc)
while i will only use XML Communication in XI(will select the Service_Procurement_Supplier_Enablement configuration scenario)
3. Is the configuration for Distribution Model and Partner Profiles necessary between SRM and SUS Communication in extended classic scenario?
Thanks.
Regards
Pawan

Hi Pawan,
Pl go through the following links for better understanding
difference between MM-SUS and SRM-SUS
SRM 7.0 SUS with ECS
Supplier Self Service (SRM-SUS)
Regards,
Nikhil

POR transferred into MM(Backend) system in Extended Classic Scenario

I am working on standard EBP-SUS Extended Classic Scenario. We have SRM Server 7.0 SP9
As we are successfully send PO from EBP to SUS.
Issue : On working to Purchase Order Response,i am getting POR sent by SUS to EBP but we are not getting it replicated to MM.
Our Concerns about is it need extra configuration required or need to have apply some note to getting replicated POR in MM from EBP or have to configure some XI Scenario to replicate POR from SRM EBP to MM.
As we know that Extended Classic Scenario supports till Purchase Order Response still we are not getting Purchase Order Response in MM.
Please tell us, Provided Solution will be really appreaciated.
Thanks.
Regards,
Pawan Keshwani

hi,
Pls see the foll notes:
Note 576349 - Terms of payment in the ECS
Note 541934 - Modification note: Copying base date from T052
Note 953999 - ECS: Terms of Payment values not in PO header
<b>Note 940453 - Backend payment term data not updated in the extended PO
Note 945018 - Incoterms data not transferred to the back end</b>
BR,
Disha.
Pls reward points for useful answers.

Services in extended classic scenarios

Similar Messages

Maybe you are looking for