BADI's in classic scenario after upgrading to SRM 07

Hello,
We are using the classic scenario, just finished upgrading the SRM 4.0 (server 5) to SRM 07.
We are using ECC 6.0.
We used the BADI's:
BBP_CREAT_PO_BACK
BBP_CREAT_RQ_BACK
I have understood that in SRM 7.0 the BADI's that I have to use are:
BBP_CREAT_BE_PO_NEW
BBP_CREAT_BE_RQ_NEW
Do I have to work with the new BADI's or can I stay with the old one?
Thank's
Yaron

Hello,
As far as I know, once you activate new badis, old ones will not be called anymore.
So, if you do not activate them, old badis will still be called.
Just remember that these badis are valid when follow on document is created via RFC in ECC.
If you have activated ESOA (creating POs in ECC via XML), PO badi is not valid anymore.
Regards,
Ricardo

Similar Messages

Very bad signal on iPhone 4 after upgrade to IOS 6

After upgrading my iPhone 4 from IOS 5.1.1 to IOS 6, I started having lot of troubles with signal and signal strength: the phone is continuously switching form 3G to GPRS/Edge, signal strength is always bad, Internet access is almost unusable, and sometimes I can't even make phone calls or send text messages; even when it seems to have good 3G signal, as soon as I try to use it to do anything (even a phone call), 7 times out of 10 the signal drops.
This doesn't seem to depend on the places where I go, and anyway I know for sure I'm now having signal troubles in the exact same places where I had perfectly good signal before the IOS upgrade. I'm in Italy, my carrier is TIM, but again, it worked perfectly fine before the IOS upgrade.
Steps I tried to fix the issue:
Settings -> General -> Cellular -> Cellular Data Network -> Reset Settings
Settings -> General -> Reset -> Reset network settings
Using iTunes: backup, reset (also downloading a fresh copy of the IOS image), restore from backup
Nothing seems to have worked.
I've been searching around, and it looks like many people have had similar problems after the IOS upgrade, although some of them seem also to have resolved it using some or all of the above steps; anyway, they were not enough for my phone.
Is there something else I can try? Is this a known IOS bug? Is Apple working on some fix?

Looks like the reset actually solved the issue. I posted the question soon after having done it, and the signal was still bad, but that was probably due to the place I was in. I've tested it for a whole day, and now signal strength is indeed like it was before upgrading to IOS 6.
I also called Apple support, and they confirmed is a known bug, and a full phone reset solves it.

Classic scenario - goods receipt in SRM

Hi,
I've seen on a business scenario document of SAP that even in the classic scenario it's possible to execute goods receipt by the requester in SRM. My question is: if in classic scenario the purchase order is created on R/3, how can the requester create goods a receipt in SRM for a specific PO? Does SRM get data (items, supplier, etc.) from a R/3 PO in the creation of a goods receipt document?
Regards,
Cristiano Soares

HI SRM GURU
We are implementing SRM 4.0 and follow a classic scenarios.
While creating a shoping cart the approval of Shopping cart is based on various attributes like
Material Group + Cost Center + Value .
Can I change the standard workflow conditions and add new conditions like material Group and cost centers.
So that when I create a Shopping cart and change the cost center in the shopping cart, it goes to the head of the new cost center(for Approval) which is manually entered in the shopping cart.
Can this control be achived through the Org plan attributes.
Regards,
Nimish Sheth

Pictures not appearing in after upgrade to SRM-MDM Catalog 3.0 SP7 Patch4

Hello,
Due to some issues in Advanced search we performed the service pack upgrade from SRM-MDM Catalog 3.0 SP5 (with MDM 7.1.03.72) to SRM-MDM Catalog 3.0 SP7 Patch4 ( MDM 7.1.04.146). With this new SP, the Pictures are not appearing anymore under the Hyperlink section anwhere in Catalog browser( Compare, Context view, Item details). With earlier SP pictures were appearing perfectly.
We have done like this:( refer earlier thread - Re: SRM MDM Catalog 3.0 Image display) thanks Sudhanshu, Jitesh and Mandeep for suggesting that solution!
Using the hyperlink field
type : rendered
MIME type : image type i.e. .jpg
URL : web URL
We had gone for this option because we dont want to store impages in MDM, and this worked perfoectly until new SP upgrade.
Any clues?
Thanks
Pravin

Hi Bala,
Nothing appears under the Hyperlink section in Catalog browser, though a valid link exists in Data Manager under Hyperlink as type-Rendered, MIME type as JPG and a valid URL.
I have searched Service Market place for this fix of this issue and found that SAP has improved the technology ( from Object Cache to Blob Cache) to display pictures/hyperlinks from SRM-MDM Catalog 3.0 SP06 and MDM 7.1SP04 onwards. We were on SRM-MDM Catalog 3.0 SP05 and MDM 7.1 SP03 before Dev upgrade.
Here are the notes for reference of others who get into same issue.
Note 1450593 - Implementation of BlobCache
This note states "MDM7.1 SP04 offers new image caching functionality called Blob Cache. The old functionality of Object Cache is replaced with the Blocb Cache mechanism in Catalog 3.0 SP06 P1"
Note 1505796 - Images not showing in SRM-MDM catalog (error in BlobCache)
This note talks about the issue in MDM API with Blob Cache. The Fix has been provided in SRM-MDM Catalog SP08 Patch 01.
But upgrade is not something that happens on the drop of a hat, we dont want to do another upgrade, I would like to know if there is a workaround.
Thanks
Pravin

Switch on classic GL after upgrade to ECC 6.0

We are in the process of upgrading from 4.6c to ECC 6.0. We intended to use the classic GL for the start and switch to the new GL next year. However we inadvertently failed to switch on the classic settings during install. Is there a way to turn on the classic GL on the fly without starting over and reinstalling?
Any ideas would be appreciated.
Thanks,
Hubby

There is no such thing as to 'failed to switch on the classic settings' . By default when you upgrade the classic GL runs. Only if you want to use the New GL, you need to activate in the Financial Global Settings, the new G/L feature.
When you activate data continue to populate the old tables namely GLT0. This is for you to compare the data in the old with the new, if satisfactory, then de-activate the old GL.

ITunes did not recognized nano but recognize classic (occur after upgrade)

After update to 7.5 iTunes do not recognize the nano. with the classic everything works fine. Need help. Thanks in advance!!!

Simple restart of the iPod solved the problem

POWL fatal exception after upgrading to SRM 7.01

Hello,
We are upgrading SRM 5.0 to SRM 7.0 SRM server 7.01 SP5. We are getting POWL error when we want to create a shopping cart. Error in ST22 is CX_POWL_FATAL_EXCEPTION. We have done the necessary changes regarding the roles en the post installation steps (as far as we can see). Can anybody help on this ? Any other things we are going to encounter ? Please share your experience! By the way I read the threads regarding this error but they seem not to be the solution to our problem.
These are the details of the technical errors in SRM:
Method: GET_LAYOUT of program CL_POWL_PERS_ACCESSOR=========CP
Method: INITIALIZE of program CL_POWL_MODEL=================CP
Method: HANDLEDEFAULT of program /1BCWDY/47B31TM8X1UWQ6FVUXCS==CP
Method: HANDLEDEFAULT of program /1BCWDY/47B31TM8X1UWQ6FVUXCS==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/47B31TM8X1UWQ6FVUXCS==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_IF_VIEW=====CP
Method: DISPLAY_TOPLEVEL_COMPONENT of program CL_WDR_CLIENT_COMPONENT=======CP
Method: INIT of program CL_WDR_CLIENT_APPLICATION=====CP
Thanks!
Kind regards,

Hello Sri Sri,
This problem will happen if you have entry missing for POWL Application ID.
POWL application is maintained in FPB_MAINATAIN_HIER.
Please check if your entries exist there.
http://wiki.sdn.sap.com/wiki/display/WDABAP/POWL
Please let me know if you are still facing the issue.
Best regards,
Rohit

Changing the Global Control of Extended Classic Scenario

Hi,
We are implementing a duplicate scenario, where for a certain product category we will use classic scenario (Only contracts on SRM) and for the others ext. classic scenario (contracts,requisitions and PO's on SRM). I activated the ext classic scenario by flaging it on the customizing. I also read in the documentation that we have to use BBP_EXTLOCALPO_BADI in order to determine which category will be handled in which scenario.
Did anybody had experience on this and provide the important points while implementing such a scenario?
Thank you in advance,
If you need to forward details, [email protected]
Message was edited by:
Gaia K.

Hi,
Well that quite simple
As you have done it just activate ECS scenario and activate the badi to change to classic scenario with you custom rules (product category...).
As soon as you get the ECS scenario configured, evrything will be ok for classic scenario.
Kind regards,
Yann

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

Consignment process in Classic scenario

HI Experts,
can anyone let me know whether we can use consignment process in classic scenario.
we are having SRM 5.0
If it is possible kindly let me know what needs to be done in SRM to set up the same
regards
subbu

Hi Subbhu
Azad is correct.
but you can see this thread but doing enhancement you might achieved .but before comitting to customer you have to do lot of business analysis /business impactsand etc.
See Yorum thread. you must get an idea.
STO classic scenario SRM 4.0
BBP_CREATE_BE_PO_NEW badi helps
you need to change the item category /document type must have consignment
Consignment is items procured on a consignment basis.
Material number is necessary
Account assignments cannot be made for material ordered on consignment.
Goods Receipt is necessary
Invoice receipt not necessary
Consignment stocks are managed separately and are not valuated
br
muthu

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.

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.

Contract Creation in SRM 7.0 classic scenario

Hi All,
We are using SRM 7.0 Classic scenario with ECC 6.0 EHP 4 and CLM 2. We are creating contracts in SAP CLM and pushing into as Global outline agreement.
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
What are the mandatory fields required to transfer the CLM contracts contracts to ECC outline agreement - I know ,Vendor, Purchase org, Pur grp, company code are required - is product catagory is also a mandatory field.
Rgds/Pawan

Hi Pawan,
Please find the answered for your questions:
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
Mitesh: Yes we can very well create in Classic Scenario as well in SRM 7.0.SC can be pushed to SOCO based on the Prod Category configuration in SPRO.From SOCO PO, Contract and RFX can be created for SC.
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
Mitesh: I dont think we can use ECC outline agreement as source of supply in SRM while creating SC.Contract replication in SRM 7.0 with EHP 4 ECC is eSOA based and ONLY Outbound to SRM (inbound to ECC).Contract cannot be replicated from ECC to SRM.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
+Mitesh: Standard intergeration of CLM/ESO to SRM 7.0 is very much there in roadmap for future releases of SRM/ESO.+
+As of now there is a consulting solution available to integerate ECC and ESO/CLM.+
+This logic can be leveraged to integrate ESO/CLM to SMR 7.0 (or lower version) requiring Developement effort from SRM functional,SRM technical,PI, Basis,ESO and java consultants.+
+Such contracts can be forced to be used as Source of Supply or alternatively replicated to ECC Via standard repliation scenario.+
Hope this helps.
Regards,
Mitesh

Extended Classic Scenario

Referring to note 963000, we are about to install SRM 5.0 as AddOn to
Ecc ERP 2005. In SRM we would like to implement the "Exteded Classic
Scenario", meaning the procurement process will take place locally in
EBP and a copy of data is replicated to the beckend system (ECC).
Is the "Exteded Classic Scenario" compatible with the "SRM as add-on"
installation? Note 963000 sais "The following scenarios are released
within SRM AddOn: ... Self service procurement (classic deplyment)":
does that mean that only the "Classic scenario" (meaning only Shopping
cart on EBP, the rest of the purchasing process on backend) is
available?

HEllo,
Only self-service scenario is supported. Means classic, extended classic and standalone.
HTH
Gordan
Message was edited by: Gordan Flego
Message was edited by: Gordan Flego

Extended Classic Scenario, BADI for PO creation in R/3

Hi,
We are using the extended classic scenario. When the PO gets replicated from SRM to R/3, right now the field CATALOGID is not being transmitted to the backend R/3 system.
1) What BADI should I implement (and the method) to transmit the CATALOGID to R/3?
2) After implementing the BADI, do I also have to change the BAPI?
3) Is the BAPI used to transfer data from SRM to R/3, BAPI_PO_CREATE?
Thanks and Regards,
Peter

Hi Peter,
1-You can use BBP_ECS_PO_OUT_BADI for ECS scenario.
Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field can been used for example to store this information. In this BADI all the items are identified and their tracking number field is populated with a catalogue id value.
2-If you use the tracking number field, no use of R/3 BADI is required.
3-BAPI_PO_CREATE1
Please check my answers in this post :
catalogid field not going in R3 backend
Kind regards
Yann
Message was edited by: Yann Bouillut
Message was edited by: Yann Bouillut

BADI's in classic scenario after upgrading to SRM 07

Similar Messages

Maybe you are looking for