Classic to Extended

Hi
Please let m know what are the challenges to move from classic to Extended classic scenario.
Thanks,
Rajan

Hello Rajan,
the processes are different as the POs are created in SRM. It's not just activating the ECS!
You need to define document types and number ranges for local POs, the PO output (and maybe the output documents - PO smartforms) and PO approval workflows if necessary. Also the purchasers are working in SRM instead of ERP and need incorporated into the organizational management and to be trained.
Best regards,
Karsten

Similar Messages

Switch from classic to Extended Classic Scenario- Impact

Hello,
We are proposing to switch from Classic to Extended Classic Scenario.
We are on SRM_SERVER 550,Sp7 and SAP 4.7 backend.
We want to know if this is technically feasible to switch and have less/no impact on existing transactional data and master data.
Main concerns are: Existing open Shopping carts and PO's.
We are also modifying the WF by including buyer completion WF.
Will the carts created in classic scenario and 'awaiting approval' work similarly in ECS?
Can we copy old carts (created in classic scenario) into new ones in ECS?
Are there any other issues like the ones above which people have come across?
Is there any standard SAP material/Consulting note available
which gives some guidelines for switching scenarios?
Regards,
Srivatsan

Hello,
You can switch from the classic to the extended classic scenario by making the global settings in the IMG.
But it would be better if you can decide if only a particular set of categories need ECS.
If you wish to have both the scenarios,the deciding factor is the product category.
You can also activate a BADI for the control of ECS despite the above Global settings.
Reward if answer is helpful,
Thanks & Regards,
Nagarajan

Migration from Withholding Tax ( Classic ) to Extended Withholding Tax

Dear All,
I am doing the Migration from Withholding Tax ( Classic ) to Extended Withholding Tax, I am getting the following error.
I made all the customization and done the necessary process flow steps.
Now I am doing the last transaction i.e. Migration Programme ( J1INMIG )
I am getting the following error. i.e.
Health Check not carried out or health check has reported errors....
Message no. 8I775
Diagnosis
Before migration of data is carried out, it is advisable to carry out the integrity of customizing in both SAP ECC and CIN.
It appears that either the health check is not carried out, in which case it can be run using transaction j1inhc, or the health check has reported errors.
Procedure
Run health check program if not already run.
Resolve the errors reported in customizing and re run the health check.
In case you do not wish to use health check tool, manually update the field 'STATUS'as 'X' for the company code.
So I checked in Health Check ( J1INHC ). Here All are showing the Green Status.
EXCEPT THE FOLLOWING IS IN YELLOW STATUS .
34            Invoice with Payment Type tax code created in classic cannot be executed after switching to EWT.
               These documents have to be processed before switching to EWT.
               SERIAL NO.     COMPANY   DOCUMENT NO.   POSTING DATE   FISCAL YEAR
               1              ITS       1900000022     09.12.2009     2009
               2              ITS       1900000027     09.12.2009     2009
               3              ITS       1900000023     09.12.2009     2009
               4              ITS       1900000021     09.12.2009     2009
               5              ITS       1900000020     09.12.2009     2009
               6              ITS       1900000019     09.12.2009     2009
               7              ITS       1900000018     09.12.2009     2009
               8              ITS       1900000016     09.12.2009     2009
               9              ITS       1900000024     09.12.2009     2009
               10             ITS       1900000025     09.12.2009     2009
               11             ITS       1900000015     08.12.2009     2009
I noticed that because the above documents are having the openitems and down payments. And If I clear the these documents it is becoming Green Status.
It means now my Health Check is correct, Because all are showing the Green status.
Now If I run the Migration Programme ( ( J1INMIG )
IT IS NOT EXECUTING. IT IS GIVING THE MESSAGE THAT NO DOCUMENTS FOUND.
Kindly advise I don't understand the above Migration programme execution and the error details.
Regards
Kumar

Hi All,
Nobody has not answered my issue.
Otherwise anybody can explain in detail about " MIGRATION PROGRAMME " ( J1INMIG ).
I want details about this last T.Code only i.e. J1INMIG and remaining all the necessary steps I completed.
An early reply will be highly appriciated.
Regards,
K. S. Sai Kumar

Conversion of classic to extended classic

hi,
i wanted to convert from classic to extended classic scenario.so what can i do to that?already activated simplified pricing.now how can i activate the ipc pricing?do i need to implement any BADI for po pricing conditions and for organization structure maintenance.kindly help me to solve my issue?
thanks,
chakri

Hello,
Check the following URL. It provides some information about pricing and IPC:
http://help.sap.com/saphelp_srm40/helpdata/en/72/f40f3c98ddaa4ce10000000a11402f/frameset.htm
Additionally, 637562 can be helpful.
Kind regards,
Ricardo

Classic scenario & Extended classic scenario

Hi Experts ,
I am new to SRM , Is it possible to combine both classic scenario & Extended classic scenario . if it possible , then how to achieve this .
Regards
Vel.

Hi Vel
I suggest that instead of checking the possibility of implementing any combined scenario's like how you have asked ( Classic+Extended classic scenario).
You need to map the Business requirement and how the Business teams wanted to handle the PO ,GR etc and accordingly you have to plan for implementation scenario. You can' customise the standard SRM delivered options for these scenario . I t is advisable to either go for Classic or Extended classic.   But combination of Classic & stand alone scenario is possible.
for your ready reference i have given below capabilities of all scenarios, which you may already know..
Key implementation scenarios
u2022     Classic
o     Implement EBP and one or more ERP system . All shopping carts refer to MM process in your ERP backend, your   ERP is the leading system. GR (Confirmations and invoices can be entered in Enterprise Buyer or ERP back end system
u2022     Extended classic
o     Purchase order is created locally within EBP system , if the data in the shopping cart is insufficient to generate a complete purchase order. The data is supplemented manually within the enterprise buyer system EB is the leading system , GR,IV can be done in both EBP and ERP system.
u2022     Decoupled
o     Combination of classic and standalone scenario ,some items are locally handled, some items are transferred to the ERP back end system
o     We are able to send PO from both the system.
u2022     Standalone
o     Your SC items create local procurement only, this means all the follow on doc like GR,IV will be done at EB system only.
o     Only commitment & invoice posting will be done at ERP backend
You can get the final Business requirement and plan.
Regards
Narahari

Classic and Extended Withholding tax

Hi,
Can anybody explain me what is the differance between classic and extended withholding tax.
Rds,
javed

Hi
Text from SAP documentation
SAP provides you with two procedures for processing withholding tax:
"Standard" and extended withholding tax.
"Standard" withholding tax is the procedure that has always been supported by the system. It offers you the following features:
Withholding tax for accounts payable
Withholding tax calculation during payment
Withholding tax code per vendor line item
Extended withholding tax provides the following additional features:
Multiple withholding taxes per customer or vendor line item
Withholding tax calculation for partial payments
Thank You,

Classic and extended Classic.....

Hi Guru's
Can we have classic and extended classic together..If yes what settings need to be done and how based on what system will diffrentiate the follow on documents creation.
Thanks in Adv.
IS

Yes, this can be achieved. By default you have to activate Extended Classic Scenario in the system. But using the BADI BBP_EXTLOCALPO_BADI, you can switch to Classic Scenario based on your requirement.
For more details please check documentation here in your SRM system
SAP Implementation Guide ->
Supplier Relationship Management ->
SRM Server ->
   Business Add-Ins (BAdIs) ->
    Control Extended Classic Scenario ->
     Activate Extended Classic Scenario
Regards
Kathirvel

BADI for Classic and Extended Classic Scenario

Hi,
   Please   provide list of Reports and BADI's for
       Classic and Extended Classic Scenario.
Thanks,
Srini

Hi,
In SRM there will be a number of BADI's are Available, We can utilize them according to the requirements
As per the request few important BAID are provided below..
Workflows
1). BBP_CHNG_AGNT_ALLOW:          Allow / Allow Change/Add Approver
This BADI is implemented not to allow users to change the approvers in the workflow.
2). BBP_WFL_SECUR_BADI:          Overwrites the authorization level of the approver
This BADI controls the restart of the workflow
Purchasing Related
1). BBP_PGRP_FIND:               Shopping Cart: Determine Responsible Purchasing Group(s)
This determines the responsible purchasing group for the shopping carts.
Shopping Cart Related
1). BBP_SC_MODIFY_UI:          BADI to Change Shopping Cart Layout
2). BBP_GROUP_LOC_PO:          Exit Grouping of Items for Local Purchase Orders
This splits local PO if more than one contract in a PO.
3). BBP_TARGET_OBJECTS:          Exit while determining target objects in backend
4). BBP_WF_LIST:               Change Worklists and Search Results Lists
This is used to restrict the search results for the user.
5). BBP_CTR_BE_CREATE:          Exit when Creating a Contract in the Backend System
6). BBP_CREATE_PO_BACK:          Exit while creating a purchase order in the backend system
This BADI is used to add the shopping carts attachments to the PO and also to make adjustments in payment terms, currency etcu2026
7). BBP_DOC_CHECK_BADI:     General BAdI in Cross-Check for Message Returns
8). BBP_DOC_CHANGE_BADI:     BAdI for Changing EBP Purchasing Documents
9). BBP_ECS_PO_OUT_BADI:     ECS: PO Transfer to Logistics Backend
Thanks
prasad .s

Classic to Extended Classic

Hi All,
We are Currently in Classic scenario and Using a local PORG and Local PGRP and maintaining users at Backend PORG Level, Now we want to Switch it to Extended Classic Scenario.We are only Using Business Scenarion SSP. My QUESTION is How to Switch the Existing ORG Structure to Extended Classic , Here I want add some thing that we have already made the Check box Activate Extended Classic in IMG settings But we are unable to replicate the PO to Backend and We maintained Number ranges also. Do we need to maintain any Local PORG and PGRP or Any special setting required to User attributes.
Please guide me in this.
regards,
Anil

Hi ,
Please check the following settings to change the scenario from Classic to Extended.
1. in SPRO - SRM Server - Cross application basic settings - Activate extended classic scenario
-- deactivate the check box.
2.In Extended classic scenario need to maintain IPC settings.. which is not required in classic
3. Give the number range for Local PO's and maintain the same number range in the backend system also.
4. You need to maintain the source and target system as back end system in Back end system for the product categery.
SRM-> SRM server->Technical basic settings->Define backend system for product categeries-->
Here you should maintain source system and target system as R/3 and EBP systems respectively for extended classic scenario.
Thanks,
Koushik.

Migration from Classic to Extended Classic

Hi all,
I would be grateful if you could let me know what is technically involved in migrating from classic to extended classic. We are using SRM 4.
I would also like to know how long this would take and any cost information and an impact on any current master data and new data that would need to be set up.
Many thanks.
Jeff.

Hi,
Pls see the foll thread:
Switching between Classic and exended classic
Related threads:
Classic / Extended Classic Scenario for Shopping Cart
Switch from Extended to Classic ?
Change from ECS to Classic Scenario
BR,
Disha.
Pls reward points for useful answers.

Upgrade Issue: With-holding TAX Conversion From Classic to Extended.

Dear Friends,
I am working for an Upgrade Project. (From 4.5 to ECC 6.0)
Please help me with steps for convesion of With-holding tax from Classic to Extended.
Your help will be appriciated and Rewarded.
Thank you,
DARSHAN PATEL

Hi,
Converting from classic to Extended withholding tax is possible but be sure once do.
Spro-Sap reference img-Financial accounting-withholding tax-withholding tax change over- MAP TAX CODES AND HEALTH CHECK AND MIGRATION PROGRAMS.
YOU HAVE TO UPDATE YOUR TAX CODES LIKE CENTRAL INVOICE PROPORTIONATELY...
IF IT HELPFUL ASSIGN POINTS, ANY PROBLEM REVERT BACK ME.
REGARDS,
SANKAR

Switching scenario from classic to extended classic

Hello Folks,
Hope everyone is well.
I would like to switch our scenario from classic to extended classic. I have set the flag in table V_BBP_EXTPO_GL - Extended classic scenario active.
Now when I try to create a Shopping Cart I get the followng errors.
No organizational data exists on item level -
Vendor 0000401968 not intended for purch. org
I have looked at all my config and cannot see anything obvious.
Any help would be greatly appreciated.
Thanks
Dave

Hello Dave and Vadim,
<b>Attention</b>, prior to the new possibility to use backend purch groups for Extended Classic Scenario, this erroneous solution was commonly implemented.
<b>DO NOT</b> define a local purchasing organization & group. In that case, you will have to:
- complete all the supplier purchasing views for this local Purch org
- define new org IDs and responsibilities
- can not use same purchaser user ID for both org IDs !!
To avoid this, you simply have to implement the BADI to determine the Purch Group. In this BADI, you can copy/paste the standard code of Purch Group determination (find the function module), and just get rid of the logical system in this determination. So backend purch group become eligible.
Kind regards
Christophe

Defination of Classic and Extended Withholding Tax

Hi Gurus,
Can anyone please explain the defination and exact use of Classic and Extended Withholding Tax difference.
Thanks in advance.
Regards,
Dev Mahendra

hello,
"Standard" withholding tax is the procedure that has always been supported by the system. It offers you the following features:
    Withholding tax for accounts payable
    Withholding tax calculation during payment
    Withholding tax code per vendor line item
Extended withholding tax provides the following additional features:
   Multiple withholding taxes per customer or vendor line item
   Withholding tax calculation for partial payments
Regards,
Sankar

Classic and Extended classic scenario

Hi All,
Can we have classic scenario for Service procurement (MM-SRV) and Extended classic for direct material procurement in the same SRM system.
This is because Extended classic doesnot support service procurment where as Classic scenario supports
Does any body implemented like this. If so pls let me know Pros and cons
Abdul Raheem

Hi Laurent,
Thanks for reply.
Do we have any limitations if we go by this model like Service procurement by Classic and Direct procurement by Extended Classic.
If any thing breif on PRos and Cons of going by this model.
Abdul raheem

Withholding Tax Change over from Classic to Extended

Client is using Classic Withholding Tax. They are able to see the tax codes while posting the vendor invoices through F-43 & FB60. But they are not able to see the tax codes on the invoices processed through MIRO. They want the tax codes to be displayed on the invoices processed through MIRO. Can anybody please help me in finding the solution for this issue??

Hi Nagesh Ram ,
MIRO transaction only supports the Extended withholding tax. If you still want to deduct the tax with classic withholding tax in miro. You block the BAPI of Extended withholding tax and activate the amount split in the T.code: OBY6 .
You also contact your Developer to do this.
Thanks
D.K.Lakshmi Narayana

Classic to Extended

Similar Messages

Maybe you are looking for