Tax setting in Extended Classic Scenario

I am using SRM 5.5, ECS, ECC 6.0, VERTEX for Tax in ECC (Tax calculation occurs in the backend) and completed the following config steps
1) Set the default to "Tax Calculation occurs in the backend"
2) Entered the same tax codes as in backend (I0, I1 and U1)
3) Even maintained the “Assign EBP Tax code to FI system"
4) Completed all the tax settings in ECC
If I create a PO directly in ECC, its calculating the taxes. The problem I see is sending the tax code in the PO to ECC, I am getting the following errors if I select I1 or U1 as tax code in the line item of the SC
"Jurisdiction code could not be determined”
"Not possible to calculate tax”
Please give me any ideas to fix this.
Thanks in Advance,
CD

Hi
<b>Configuarion is missing in this case.</b>
Please maintain data in the following tables in SRM side, similar to what is maintained in R/3.. In order to go ahead further.
<b>The main tables are as follows ->
BBP_TAX              Tax Codes for Enterprise Buyer                   
BBP_TAXT             Enterprise Buyer: Tax Code Description
BBP_MAP_TAX_CODE ( Assign Enterprise Buyer Tax Code to FI System )  
BBP_DET_TAX_CODE  (    Tax Code Determination  )</b>
Hope this will help.
Pls reward suitable points.
Regards
- Atul

Similar Messages

  • Extended classic scenario to Classic scenarioc in SRM.??

    someone pls tell me how to change from Extended classic scenario to Classic scenarion while creating in shopping cart...?
    I am using BADI "BBP_EXTLOCALPO_BADI" change to classic scenarion from extending classic..but i got confused about source code..So i request any one can help me for suitable source code..

    Hi
    Do you mean to say that you have set up Extended Classic Scenario but you want to change it to Classic Scenario?... If this is the case, remove the activation in COnfiguration for Extended classic scenario and deactivate BADIs you ve implemented for Extended Classic
    OR
    Do you want to change it to Classic only for the Document user is creating.--> Read the indicator or data from SC and decide whether the document has to be in Classic or Extended classic SCenario.... The BADI will either have Extended classic = X or NOT.... so there is no parameter for classic Scen... Depending on your requirements, implement the ext. classic badi to SET it or NOT set it...
    Regards
    Virender SIngh

  • Configuration steps for Extended Classic Scenario

    Hi All,
    Could you please let me know what are the configuration steps required for extended classic scenario.
    Thanks in advance

    Hi,
    Important Settings that Determine the Extended Classic Scenario
    The following settings are required for the extended classic scenario:
    u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
    u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
    u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
    u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
    u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
    u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
    u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
    u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
    u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
    u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
    This is for your additional information.
    Hope this helps.
    Regards,
    Vikas

  • Error occured while saving PO in Extended Classic Scenario

    Hi All,
    I have set up Extended Classic Scenario.
    While I try to make any changes in PO through manager or purchser I get following error:
    "Cannot get process info from WF archive; function AS_API_READ causes exceptn No Infostruc Found."
    Please suggest.
    Regards,
    Yaniv
    Edited by: yaniVy on Jun 17, 2011 12:33 PM

    Hello!
    This message usually is shown when no workflow can be determined at the time the approval process starts.
    Please check your start conditions at transaction SWB_COND and compare them with the information in your PO (values, status, etc). Then make the appropriate changes in your workflow.
    Best regards,
    Christian Zeuch

  • Freight is not updated in R/3 in the Extended Classic scenario

    Friends,
    Freight is not updated in R/3 in the Extended Classic scenario.
    Once a PO is ordered, if a freight condition in SRM is applied, it does not get updated in R/3.
    We have created a condition for Freight (Value and Percentage)in Create
    Payment Conditions using the following menu path:
    spro
    --> Supplier Relationship Management
    --> SRM Server
    --> Cross-Application Basic Settings
    --> Pricing
    --> Process Payment Conditions
    When creating a Purchase Order in SRM in the "Item Data" tab, there is
    a"Pricing" option. Choose "Pricing" and select "Add Further Conditions"
    from the drop down menu. Here Freight is available. Add Freight and
    the PO record in SRM is updated with the Freight Condition. However,
    upon ordering, the Freight condition does not transfer to the PO
    recordin R/3.
    We've heard this can be achieved by enhancement: only ie by implementing
    set of BADIs..  But does anyone know WHICH BADIs we need?  Or how we could find out?  Thanks.

    Hi
    <b> You can either of these BADIs to handlwe the scenario.</b>
    BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
    BBP_CREATE_PO_BACK   OLD Exit while creating a PO in the backend system     
    BBP_ECS_PO_OUT_BADI  ECS: PO Transfer to Logistics Backend                  
    BBP_EXTLOCALPO_BADI  Control Extended Classic Scenario  
    Hope this will help.
    Please reward suitable points.
    Regards
    - Atul

  • 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

  • Extended Classic Scenario - SHC: Buffer table not up to date

    Hello all,
    I'm working in SRM_SERVER 550, SAPKIBKT11, and having issues using BACKEND PURCHASING ORGANISATIONS and the Extended Classic Scenario.
    According to SAP note 944918 the following indicator should not be required to be set:
    Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario --> extended classic scenario active.
    I did set the Backend Purch. Grps Responsible indicator, and I did create organizational units specifically for the backend purch. grps.
    We need to set the main part of all SHCs to ECS, but when I do set the indicator in customizing to "extended classic scenario = active", I get a dump in my web environment: 'buffer table not up to date'.
    What is causing this failure in my SHC?
    I tried to implement BAdI "BBP_EXTLOCALPO_BADI" (method DETERMINE_EXTPO) like described below here: without the line bbp_extpo_gl-bbpexpo = 'X'., I can continue and create the SHCs. Problem is though: all SHCs will get marked as Classic Scenario. So, to make sure the SHCs will always get marked as ECS, I have added this line in the BAdI. Unfortunately this immediately results in the 'buffer table not up to date' error in the SHC itself, as soon as I try to open the details of the new item.
    Hope you help me out here?? It doesn't seem to be related to the BAdI, but somehow the system doesn't allow me to mark SHC items as ECS.
    Thanks & Regards,
    Berend Oosterhoff
    SRM Consultant Accenture Technology Solutions - The Netherlands.
    BAdI BBP_EXTLOCALPO_BADI:
    method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO.
    data definition----------------------------------------------------*
      DATA:    wa_mattype     TYPE BAPIMATDOA,
               wa_char18      TYPE MATNR,
               attrib_tab     TYPE TABLE OF bbp_attributes,
               wa_attrib_tab  TYPE bbp_attributes,
               wa_value       TYPE om_attrval,
               wa_product_id  TYPE comt_product_id.
        bbp_extpo_gl-bbpexpo = 'X'.
    from here I did the specific selection for the SC, but that's not relevant here.

    Hi Prashant,
    Thanks for your quick reply!
    Note 1085700 is about Short Dumps when creating or changing a contract. I am trying to create a Shopping Cart, without a reference to a contract. BAdI BBP_DOC_CHANGE_BADI is not active in our system.
    Any other thoughts?
    Regards,
    Berend

  • Extended classic scenario - no backend PO created

    I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.
    I get following error messages in application monitor as backend application errors:
    No instance of object type PurchaseOrder has been created. External reference:  
    PO header data still faulty  
    Document number 100000093 not within defined inter val  
    What's going wrong here?
    Hubert

    Hello,
    Check if you have set up the customizing as below:                                                                               
    Extended classic scenario:                                                                               
    a) at SRM side:                                                                               
    - To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.                                           
    - Create a number range for a local PO.                                                                
    - Assign the local PO number range as a internal numer range to the transaction type.                                                                               
    b) at R/3 side:                                                                               
    - Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)                                                                               
    - Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)                                                                               
    - Make sure that the SRM and R/3 number ranges match are exactly the same.
    Kind regards,
    Ricardo

  • Extended Classic Scenario - PO Update issue

    Hello experts.
    We are working with SRM 5 in the extended classic scenario and we have a serious problem in a productive environment for the following case.
    (01) We create a purchase requisition (PR) in R/3 with several items;
    (02) We send PR to the SRM generating a shopping cart;
    (03) The buyer creates a PO for all items from the shopping cart;
    (04) The PO is transmitted to R/3;
    (05) For some cases buyer changes the PO wich is sent back (updated) to R/3;
    So far so good. The problem happens when some item in the request already has GR or Invoice. In those cases when the PO is updated on SRM, its transmission to R/3 does not occur, generating an error log that can be seen in transaction RZ20 of SRM.
    I understand that if any GR or Invoice exists for the item it can no longer be modified, but is it expected that no other item can also be modified from SRM? What is the expected behavior for this case?
    Moreover, even if the GR and Invoice have been canceled, we are still unable to update the PO in R/3 from SRM. Is this a expected behavior? It was our understanding that the PO should be updated if all incoming documents (GR, Invoice, SES ..) were completely canceled.
    We appreciate any help on this matter.
    Thanks and Regards,
    Evandro Miasato

    Hi, Masa,
    Thank you for your advice,
    I set the method U:Print Using Berkeley Protocol, after that
    in  trx. SP01 I have the Error Status on Composite Document -
    Status Incorrect (Reason Unknown).
    Best regards,
    Guzal.

  • PO approval process in ECC for extended classic scenario

    Hi All,
    At this moment we are using SAP ECC for procure to pay process. In the existing system set up, our ECC purchase order goes for approval via SAP enterprise portal(EP). We are planing to implement SRM 7.0 Extended classic scenario, so that user can take the advantage of creating PO in their web portal. We don't want to disturb our existing ECC PO approval process at this point of time.  
    So our requirement is :
    User will create PO in SRM. Same PO will replicated in ECC and the PO will goes for approval in in ECC and the PO output will generate in ECC. Can it me possible in extended classic scenario ?
    Thanks in advance.
    Regards,
    Jennifer
    Edited by: Jennifer Batty on Aug 8, 2011 5:08 PM

    Hi Jennifer,
    Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
    Thanks and regards,
    Ranjan
    Ranjan Sutradhar

  • Number range for extended classic scenario

    Hi,
    we've activated extended classic scenario for some defined categories (material groups), other will use classic scenario as before. It works, we are able to craete POs in both ways. I've tried to use the same number range for backend POs and for local POs. I've set the same number for both ranges but only the one which is used is getting updated. Is it possible to syncronize these ranges so backend POs will all be created in the same range?
    Regards
    Hubert

    Hi Hubert,
    Not the best practice that you are following. it might work for some time  but will fail for most of the time . The maintenance is going to be huge and you could expect problem with these.
    I would suggest not to think on the solution of same number range itself.
    Thanks
    Iftekhar Alam

  • Sourcing of GOA in Extended Classic Scenario

    Hello all,
    We are using the <u>extended classic scenario</u> with both Purchase Contracts and Global Outline agreements.
    Is it possible to use the GOA in the back-end as a source of supply in the sourcing transaction in SRM? What setting do I have to use exactly?
    Kind regards,
    sander

    Hi
    Which SRM and R/3 versions are you using ?
    I guess, the following threads will help.
    <b>Source determination in backend (R/3) for distributed contract i.e. GOA
    Transaction For Creating GOA
    Distribution of GOA in R/3
    FM or BADI s' used to create a GOA
    GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
    Hope this will help.
    Please reward full points, incase it suits your requirements.
    Regards
    - Atul

  • Convert classic in extended classic scenario

    hai,
    i wanted to convert classis scenario into extended classic scenario.what are all the steps that i needed to be follow.does it require any implementation of badi?how the po will be sent to the r3 in display mode?
    could anyone give the solution
    Edited by: chakradhar  nannapaneni on May 11, 2009 12:45 PM

    Hi,
    1.     Activate the extended classic scenario
    When the extended classic scenario is set, SRM generates a local purchase order for each item in the shopping cart. All follow-on documents are created in the backend system as well as locally in the SRM
    2.     Activate IPC pricing
    Since SRM 3.5 IPC (Internet Pricing Configurator) pricing is mandatory for extended classic implementations.
    In the classic scenario you can replace the IPC by the simplified pricing
    IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Cross-Application Basic Settings  Activate Extended Classic Scenario
    IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Business Add-ins for SRM Pricing
    Check whether the BAdIs relevant for the pricing are activated correctly and filled with the correct coding:
    BAdI                                     I            PC Pricing (Extended)          Simplified Pricing (Classic)
    BAdI: BBP_PRICEDATA_READ
    Implementation:. BBP_PRODUCT_PRICE                     Not active         Active
    *BAdI: PRODUCT_UPDATE2
    Implementation. IPC_UPD_PROD_BUFFER2     Active         Not active
    Regards,
    Abraham

  • Sourcing in extended classic scenario

    Hello, all
    We are using the extended classic scenario in SRM 5.0.
    In sourcing cockpit I have the following problem. In spro Supplier Relationship Management/SRM/Server/Sourcing/Define Sourcing for Product Categories I set  Sourcing Always Carried Out. From a shopping cart the purchase order is created automatically as the data complete, but  I'd like to sent shopping cart to the sourcing, where from  a shopping cart create bid invitation or purchase order. How  do it?
    Please help,
    Best regards,
    Guzal

    Hi Guzal,
    As informed by Claudia, Incomplete mainly means no vendor assignment, no price etc.
    If the vendor is assigned at the shopping cart level by means of a contract the shopping cart (details)  is complete. Even in this case the SC should go to Sourcing cockpit in case of "Sourcing Always carried out" is chosen in the sourcing column.
    In the above case the P.O gets directly created from SC only when the options
    " Sourcing never carried out" & " Sourcing carried out for items w/o assigned source of supply" were chosen.
    Hope you will be more clear on this issue. Any clarifications always welcome.
    Rgds,
    Teja

  • PCARDS in extended classic scenario

    Is it possible to use PCARDS in extended classic scenario?

    Madidipa-
    True this is only available as a standard option with stand alone scenario.  However it can be enabled with a a customized process, using customer fields.  In fact this process was highlighted in a SAP Teched presentation a couple of years back.
    In short we created customer defined fields to hold the pcard, linked to the pcard master data tables in EBP, and then when it goes to the R/3 we created an additional account assingment category to make R/3 happy and set it for no invoice.(the pcard data was transferred to R/3 as additional customer fields)  As usual, with enough time and money most things are possible.
    Regards-
    b

Maybe you are looking for