Extended Classic Sceanario or Classic Scenario

dear all,
i'm a bw person and right now trying to figure out why my confirmation extractor in SRM isnt delivery the data i want. I did a search in service market place and found this 1101861.
anyway, my question is, is there a function or table or anyway i can determine if the srm system i'm extracting from is using extended classing or just the classing scenario?
thank you!

Hi
Please confirm what sceanrio in SRM are you planning for ?
I have not tried this. In Extended Classic Scenario, using BADI " BBP_TARGET_OBJTYPE" -> I guess, it's possible, but not sure. Try it out.
Purchase Order (PO) will be created in the R/3 system using the BADI - BBP_TARGET_OBJTYPE. Please read the standard documentation of this BADI, before implementing the same.
Regards
- Atul

Similar Messages

Classical to ALV classical

Hi All,
Please help in converting classical report to classical ALV report as in my classical report between the program four Internal table were used for calculation , now after calculation block i have deleted all the WRITE statement to convert it into classical ALV and after end of the program i have used
PERFORM LAYOUT_INIT USING gs_layout.
PERFORM COMMENT_BUILD USING gt_list_top_of_page[].
PERFORM build_fldcat CHANGING field_cat1.
PERFORM build_layout.
PERFORM set_events CHANGING lt_events.
and FM Reuse_alv_grid_display.
but in FM i can only pass one internal table so what should i do please suggest
Please suggest the right way where to use these perform statements & the FM Reuse_alv_grid_display.
either in place of the deleted write statements or any where else in the program so that the calculation part output is displayed in Grid form.
Thanks.

see this simple example for converting into different formats
report zalv_sample                            .
tables vbak.
data it_vbak like vbak occurs 0 with header line.
selection-screen begin of block b1 with frame.
parameters: alv1 radiobutton group alv,       "REUSE_ALV_LIST_DISPLAY
            alv2 radiobutton group alv,       "REUSE_ALV_POPUP_TO_SELECT
            alv3 radiobutton group alv,       "REUSE_ALV_GRID_DISPLAY
            alv4 radiobutton group alv.       " NORMAL DISPLAY
selection-screen end of block b1.
select * from vbak
         into corresponding fields of table it_vbak
         up to 10 rows.
if alv1 = 'X'.
perform alv_func1.
elseif alv2 = 'X'.
perform alv_func2.
elseif alv3 = 'X'.
perform alv_func3.
elseif alv4 = 'X'.
perform norm.
endif.
*&      Form ALV_FUNC1
form alv_func1 .
call function 'REUSE_ALV_LIST_DISPLAY'
    exporting
      i_structure_name = 'VBAK'
    tables
      t_outtab         = it_vbak
    exceptions
      program_error    = 1
      others           = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
endform.                                                    " ALV_FUNC1
*&      Form ALV_FUNC2
form alv_func2 .
call function 'REUSE_ALV_POPUP_TO_SELECT'
    exporting
      i_title          = 'SALES ORDER INFO'
      i_zebra          = 'X'
      i_tabname        = 1
      i_structure_name = 'vbak'
    tables
      t_outtab         = it_vbak
    exceptions
      program_error    = 1
      others           = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
endform.                                                    " ALV_FUNC2
*&      Form ALV_FUNC3
form alv_func3 .
call function 'REUSE_ALV_GRID_DISPLAY'
    exporting
      i_structure_name = 'vbak'
      i_grid_title     = 'SALES ORDER INFO'
    tables
      t_outtab         = it_vbak
    exceptions
      program_error    = 1
      others           = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
endform.                                                    " ALV_FUNC3
*&      Form NORM
form norm .
format intensified.
skip 1.
write: /'SALES DOC.',
          '    Created on ',
          '    Time',
          '      Created by',
          '       Valid from ',
          '     Sold-to party'.
format intensified off.
skip 2.
loop at it_vbak.
    write: / it_vbak-vbeln,'   ',
             it_vbak-erdat,'   ',
             it_vbak-erzet,'   ',
             it_vbak-ernam,'   ',
             it_vbak-angdt,'       ',
             it_vbak-kunnr.
endloop.
endform.                    " NORM

Classical report to classical ALV report

Hi All,
       Please help in converting classical report to classical ALV report as in my classical report between the program ,after calculation block i have deleted all the WRITE statement to convert it into classical ALV and after end of the program i have used
PERFORM LAYOUT_INIT    USING    gs_layout.
PERFORM COMMENT_BUILD USING    gt_list_top_of_page[].
PERFORM build_fldcat   CHANGING field_cat1.
PERFORM build_layout.
PERFORM set_events     CHANGING lt_events.
and FM Reuse_alv_grid_display.
Please suggest the right way where to use these perform statements & the FM Reuse_alv_grid_display.
either in place of the deleted write statements or any where else in the program so that the calculation part output is displayed in Grid form.
Thanks.

use in place of the write statements only....
Regards,
SAPient

Classic PO in PDP scenario

Hello,
We want to implement the following scenario. The PR's of NB type are created and released in ECC. They are transfered to SRM using SOA services. In SRM we group the created SC's to RFX and define the winner. We want to create backend PO for the winning bid using SOA services, service PurchaseOrderERPRequest_Out_V1.
However, when we create a purchase order from the winning bid a PO in SRM is created and then transfered to ERP through BAPI. We don't like this scenario as we need an ECC system to be the leading system for the PO.
We have a guide where this scenario is present, it seems it must be pure standard. After reading a couple of threads on the forum I got a view that the problem is in account assignment. We have direct PR and direct PO - that's why the system act as extended classic scenario.
Am I right in this statement? If I would add a technical account assignment when I receive SC in SRM and clear it in PO - would it help?
Thanks for help.
Mukailov Sergey.

Hi Sergey,
Please check this thread
PR with material assigned failed to create PO in SAP through Rfx process
This would be of great help.
The reply by Jagdish in the thread above might just resolve your issue.
Check that and let us know in case of any further clarifications.
Regards,
Teja

DIFFERENCE BETWEEN EXTENDED WITH HOLDING AND CLASSIC WITHHOLDING TAX

< MODERATOR: Message locked. Please read the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] before posting next time. >
HI
What is the difference between classic with holding tax and extended with holding tax ...
teja.k

Check this site.......
http://help.sap.com/saphelp_erp2004/helpdata/en/2d/936b3ae886616ae10000000a114084/content.htm

Switching between Classic and exended classic

Hello All,
We are going for an upgrade to SRM Server 5.0 with the Classic scenario. Can we in the near future go for Extended classic Scenario to have all the purchasing processes in SRM. If it is possible how can we go for and what are the efforts, we plan to add direct procurement functionality at this time.
Thank you,
Surya

HI Manyam
For converting from classic scenario to Extended classic scenarios it is easy as we have to apply one tick in the customising that Extended clasic scenarios Active.
And then test the processes on QA client.
Even we can bring in the direct procurement scenario for that follow this steps
Following settings are done in SRM
1 you need to maintain the Document type in spro and in PPOMA_BBP - Doc type - DC_PROC_TY
2 Maintaint the nnumber rannges in customising for the Document type in R3 as well as in SRM .
3 Once the direct procument button is clicked Goods receipent is replace by Plant and
4 The account assignemt tab is removed.
5 Get all locations from backend by running report
BBP_LOCATION_GET_from_system
Settings in R3
Set up the document type and number ranges .
Regards,
Nimish Sheth
Do reward points for helpful answers.

Extending the IDoc to cXML scenario

Hi Experts,
I have a scenario IDoc to cXML for sending ORDERS05 .
We got a requirement to develope a scenario by extending the Order header and line extention segements to include extra fields)of the IDoc used in the above scenario , hence I am doing the following
-Imported the extended IDoc into the Integration repository.
-Mapped the extra fields included to the target message.
-reloaded the IDoc Metada using IDX2.
As i am doing this as part of the other project please suggest on the following
--Explain the sections to be included in the Technical design document for XI configuration.
--configurations that I need to work on.
please do suggest any other things i need to work on to take the right approach.
Thanks in advance.
MK

Hi,
Nothing more u require in XI development when ever u are dealing with the Extended IDOC's.
Normal procedure as Standard IDOC's only.
If u are not able to view the extended IDOC's in the Repository means then u have to think the solution.
This problem is not there for u. so go a head with the normal procedure by importing those IDOC's in IR and do mapping as usual
Regards
Seshagiri

Why is video 30gb cost more than classic 80gb (if classic has better specs)

Why is it that a better ipod for specs and features is cheaper than an older, less memory and less features ipod video ?
Is there something apple isnt saying ?
Or have ipod's finally come down in price from the start ?

They always end up making things cheaper even though the new cheaper product is better.

Reference to SC in classic Scenario

Dear SAP gurus,
We're planning to install SRM 7 EHP 2 with backend ECC 6 EHP 5. We plan to use classic scenario, as we know that now, classic scenario already support Sourcing Cockpit and creation of RFx/Auction referring to SC.
However we want to clarify somethings. As I know, the control for classic scenario can be set to 2 things:
a. If stock available create reservation,
b. If external, create PR if no source found.
So let's say that in classic scenario, I create SC with non-stock item. Once it is approved, does it create PR in backend? Or it is not creating PR in backend, rather it sticks in SRM and go to sourcing.
Then in sourcing, let's say I decide to create RFx, and as result, I create PO from RFx response. As it is in classic, the PO will be created directly in backend. In backend, what will be the value in PR field? Is it going to show the SC number? The PR number? (assuming that once approved, SC will create PR in backend as well) OR the PO will NOT have any reference to the SC at all?
Appreciate if someone can shed some light of system behaviour in this case.
Best regards,
John

Hi
So let's say that in classic scenario, I create SC with non-stock item. Once it is approved, does it create PR in backend? Or it is not creating PR in backend, rather it sticks in SRM and go to sourcing.
Ans: In classic scenario for a non stock item if the source is not there,after the SC is approved it will create PR
in the backend.
In Extended classic sceanario(ECS) if the Sc is not having source once the SC is approved it will go to Sourcing cockpit
(or) you can see in Purchaser worklist
Then in sourcing, let's say I decide to create RFx, and as result, I create PO from RFx response. As it is in classic, the PO will be created directly in backend.
Ans : In ECS if you creating Rfx to PO in the tracking tab you can see the SC.
In backend, what will be the value in PR field? Is it going to show the SC number? The PR number? (assuming that once approved, SC will create PR in backend as well) OR the PO will NOT have any reference to the SC at all?
This is not clear
G.Ganesh Kumar

Direct Procurement in Classic Scenario

Hi Experts,
We are on SRM 7 Ehp1, ECC 6 Ehp4.
Classic Scenario.
1. I have read in the forums , that in Classic Scenario, direct procurement is possible but the system behaves like Extended Classic and creates a Local PO. Just want to confirm this and if yes , does this happen as a standard or do we need to implement any BADI or anything to achieve this.
2. Also , in Classic Scenario, PDP scenario , can we transfer stock items(Direct Materials) PR's into SRM system or are there any limitations.
Thanks
Aditya

Hi Aditya,
You are right. Classic system behaves as extended classic for Direct procurement scenario. Your PO will be created in SRM itself and a copy of this will be sent to ECC. This happens as a standard and no BADIs need to be implemented for this.
Also in your classic system, you can transfer stock PRs into SRM. These will be available as shopping carts in the sourcing cockpit.
Regards,
Nikhil

URGENT: CLASSIC & EXTENDED CLASSIC

hi gurus,
can anyone tell me the difference between classic and extended classic scenarious in SRM? when will we use them for client requirement?
what is the difference between R/3 enterprise structure and SRM organizational plan?
what is meant by SAP SCM?
if i implement the extended classic then willl it possible in classic?how and why
what r the followon documents will support for each scenarious?please be detail.
what is the transactioncode for VENDORMAPPING?
CCM,SUS,SOURCING,SSP,PDP,SERVICEPROCUREMENT are depending on which scenarios i.e classic or extended classic for each business scenarious?
please send solutions immediatly to my id <i>[email protected]</i>
warm regards
rakhi

Let me see if I can satisfy you :
- The major difference between classic and Ex. classic is the system where the leading PO is created. In classic it's r/3 while in ECS it's SRM.
The usage depends on the customer requirement and convinience.
- R/3 ent structure and SRM org are mutually exclusive. But you take ref of r/3 ent structure in SRM org structure at many points.
- SCM is collabration of many SAP components like APO, ICH. It's basically group of SAP solutions to map the tptal functionality of supply chain.
- You can control ECS scenario with BADI depending on yr business objects.
- Follow on documents are same for both PO or contract , GRN/Confirmation, Invoice
- already tolD BBPGETVD for downloading vendors from R/3 and BBPUPVD for synchronisation
- CCM is component for catalog can work in both classic or ECS
SUS is component for suppliers can work in both classic or ECS
sourcing is functionality for purchasers can work in both classic or ECS
SSP is business scenario for self service can work in both classic or ECS
PDP is BS for plan driven procurement can work in both classic or ECS
service procurement is for service and work in same way
these components or business scenarios are mapped as per customer requirements and hence the leading PO location has flexibility.
BR
Dinesh
(Reward if helps)

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.

Why extended Classic is implemented

Hi Everybody,
I was working in SAP SRM for past 3 years and only Support Experience. Yesterday attended an interview and he asked me why your client has implemented Extended Classic why not Classic Scenario?
I know it depends to client-to-client.
Can any one let me know the list of points need to be discussed to support this question. My answer was not impressive.
Sree

Hi Sree,
You are right here it depends on the client whether to configure the system for extended classic and classic scenario.
The extended classic scenario suits customer who wants to
their purchasing department to save time and money by using the streamlined purchasing functionality of SAP SRM
use the full sourcing capabilities offered by SAP SRM, yet who also want to be able to confirm and invoice direct materials
the flexibility of being able to pre-enter confirmations and invoices
Where the classic scenario suits the customer who wants:
wide user group, for example employees not necessarily working in the purchasing department, to be able to enter their requirements quickly and easily. SAP SRM’s functionality and ease of navigation allow this, as it requires only minimal training
their purchasing department to operate solely with the functionality offered by the backend system(s)
For whom a transfer of purchasing activities to SAP SRM is not viable in SAP SRM
You can use both the classic and extended classic capabilities by configuring the product categories
Please let me know if the above answer is helpful.
Best Regards,
Ankit Jain

Classic WT To Extended WT

Dear SAP Experts,
I am working on upgrade project from SAP 4.7 to ECC 6.0.
My client uses the classic withholding tax and they want to go for extended withholding tax.
What would you suggest me to configure EWT from first or should I go for Migration.
What precaution I should take in both the cases.
Thanks & Regards,
Reva Naik.

Hi,
check the link -
http://help.sap.com/additional/cv_india/en/home.htm
In it Navigate as - TDS - Extended WHT-Migration from classic to WEHT
Regards,
Sridevi
Pls .assign points, if useful

Can we activate Classic General Ledger in ECC6.0 during upgrade from 4.6C

Dear SAP Gurus,
Greetings
My Client's technical team had upgraded their system from 4.6C to ECC6.0 and they had activated classic GL instead of New GL. And they had also activated classic withholding tax in place of Extended Withholding tax.
They are facing some error during posting of transactions (like generation of excise invoices, posting of WHT transactions, etc.) I told that it can be a reason of not activating New GL.
Is my understanding correct...?? Can we activate classic GL during upgrade from 4.6C to ECC6.0...??
In case of a new client built (with ECC6.0), can we activate the classic GL instead of the New GL..??
Does the system will work correctly in the long run if they had activated classic GL and classic WHT...??
Please clarify. Thanks in advance for your time and efforts
Regards,
Chaps
P.S. Points will be awarded for answers !!

Hi,
I think that you should read long text of OSS note 999614 carfully and you are
aware of the fact that you will have additional migration efforts in
case you need to migrate to new G/L later on.
In case you are convinced that this is the best way please feel free
to deactivate new G/L as described in note 999614.
Please make sure that you deactivate new G/L in all clients of your
new system in case there were already client copies done.
Yes this is possible and I would not automatically assume that
error during posting of transactions are due to New GL not being activated.
Note 756146 documents the issue and possible repercussions
of using Classic GL.
In the case of a new installation the new G/L accounting
is active by default in ERP. In principle, the use
of the classic GL is also possible for new customers, however,
SAP does not recommend it since this requires an additional
migration expense in later years.
Regards,
Aidan

Extended Classic Sceanario or Classic Scenario

Similar Messages

Maybe you are looking for