Sharing attachment documents (e.g. for P.O.) in extended classic scenario

Dear SAP SRM gurus
in the SAP SRM extended classic scenarios (rel. 7.0) attachments of Purchase Order can be viewed also in the backend SAP ECC 6.0  as per SAP Notes n. 1582690 and 1057932 . But I am not sure if attachments are phiysically transmitted from SAP SRM to ECC or only document url is passed even though, as per SAP note n.1357551 it seems that only url is passed.
My customer wants to know if there is the possibility of not replicating them.
Any suggestions will be appreciated.
Many thanks in advance
Best regards
Gianluigi Brenna
Edited by: GIANLUIGI BRENNA on Jul 29, 2011 2:56 PM
Edited by: GIANLUIGI BRENNA on Jul 29, 2011 3:08 PM

Hello,
In extended classic scenario the attachments arent transferred to ECC as the source document is in SRM. The document in ECC is only a copy and it cant be modified also.
If we have to transfer attachments, then probably implicit enhancements to standard logic might be needed.
Regards,
Prasanna

Similar Messages

  • P-card  process available for SRM 5.0 extended classic scenario

    Hello,
    I didn't find the information, so I'm posting this message.
    Is  the p-card functionality available for the extended classic scenario in SRM 5.0 ?

    Hi,
    Use of Procurement Cards are supported in Extended calssic scenario from SRM 2007 ..onwards
    HTH
    Rajesh

  • Question on Purchasing documents in extended classic scenario

    Hi friends
    How to create local purchasing documents i.e po,confirmations,invoice, in extended classic scenario
    Please let me know the path
    regards
    venkat reddy

    Hi Venkat,
    The user interface and the process is same for local documents. However the result of document posting (either backend or local) depends on the setting in SPRO --> SRM --> Technical basic Settings --> Define backend system for product category.
    Here you can define the target system as the system of document posting. If the terget system specified here is your SRM system, then it will create local documents in SRM.
    Regards,
    Prashant
    Do reward points for helpful answers

  • Attachment transfer of PO from SRM to Back end for extended classic scenario

    Hi Experts,
         We are using the SRM 7.0 with EHP 701 and ECC 6 , we have a SRM requirement where we need to transfer the attachment of a PO to back end ECC. I tried to implement the note 1594966 , but it doesn't work . we are using Extended classic scenario. Please suggest some SAP notes or the procedure to be followed to achieve this.
    Thanks ,
    Aishwarya.M

    As far as I am aware this functionality of transferring attachment is not supported in Ext classic scneario  
    http://scn.sap.com/thread/1873708
    Also  I suggest you should debug and see if its sending attachment from SRM if yes then
    could be something missing at ECC side , To debug use this
    http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=340264144
     You may also check in SXI_monitor and see if attachment is being recieved and sent from SRM and ECC respectively
    Are you configuring this for the 1 st time or its an error which u encountered?
    You must raise a NOte to SAP for the same till a solution is found .
    This one is another which you can check ..
    http://wiki.scn.sap.com/wiki/display/SRM/Transfering+shopping+cart+attachments+to+the+backend+system

  • PO output for Extended classic Scenario from the R/3 backend

    Hi,
    1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
    Regards,
    DV

    Hi Anil,
    We are working on extended classic scenario with SRM 5.0 & ECC6.0.
    Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ". 
    Please send the related document to [email protected]
    Thanks in advance
    Ashutosh

  • 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 I’m 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.

  • PO attachment transfer to ECC - Extended classic scenario

    Hi all,
    We are on SRM 5.0 ECS.As standard,can the SRM PO attachments be transferred to  ECC PO?Is this possible in  ECS?If so,what are the steps?

    HI Alexander,
    The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
    attachment transfer logic was only implemented in the Classic Scenario.
    One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
    At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
    I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
    BADI does (BBP_CREATE_BE_PO_NEW).
    We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
    1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
    1413792 Attachment deleted after changing purchase order
    I hope this information help you to understand this issue,
    Kind Regards,
    Rafael Rhoden

  • Multiple PO document types/transaction types in Extended Classic scenario

    Hi All,
    We are on SRM_SERVER 550, Extended Classic Scenario.
    We have a requirement where we need to create multiple PO document types (based on certain criteria).
    I have noticed that in standard, there are only 2 transaction types provided for SRM PO - ECPO and ECDP.
    We need more document types and these should be triggerred automatically after SC is approved.
    I understand that we need to maintain all the PO transaction types in SRM, number ranges in SRM then maintain the same transaction types as PO document types in R/3 and same number ranges in R/3.
    I also understand that the change for document type needs to be done in BBP_DOC_CHANGE_BADI.
    I have 2 specific questions:
    1. We need to maintain attribute BSA for the users. Here we need to mention the document type and source system. What should be the source system mained in attribute BSA for ECS? Should it be the SRM system or R/3 system?
    2. In BBP_DOC_CHANGE_BADI to change the PO document type/transaction type in ECS scenario, which field should be changed? Should it be ET_ITEM- BE_DOC_TYPE?
    Regards,
    Srivatsan

    Srivatsan,
    To create new transaction type:
    Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Define Transaction Types
    To create new number range:
    Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Number Ranges --> SRM Server Number Ranges --> Define Number Range for Local Purchase Orders
    You can define to create automatic PO when a SC was created in: Supplier Relationship Management --> SRM Server --> Sourcing --> Define Sourcing for Product Categories
    Rgs,
    Pedro Marques

  • 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

  • How to findout for which product category extended classic is activated?

    Dear experts,
    How to find out for which product category extended classic is activated? I am working in a test system. In spro settings, Cross aplication basic settings -> activate extended classic is unticked.
    I see, the system allows me to create a Extended classic PO against a product category 001.
    The product category has same ECC backend  system as target and source system.
    Is there any BADI implementation?
    regards,
    Ranjan

    Hi
    ECS - flag activated - means Extended classic scenario.
    target determine badi - helps to create a PO in desired place.
    source system and tatget system logical entry sjhown means
    PRODUCT CATEGORY - created in Backend system and follow on docuemnts also created in ECC system - so it could be Classic .
    as jay said determine log system badi used for DECOUPLE scenario ( Classic as well as ECS) .
    some times unless we study the system in depth, hart to findout what is exact techniacl scenario.
    or you can find out what type of POs are in BBP_PD for all PO means ECS.
    This SRM tools can be used for many purposes.
    some customers uses for Supplier registration only,
    some one is using for only Bid invitation and Bid and selecting the vendor only
    some one use for all non stock procurment only.
    some one use for only free text - ....
    taste vary in all business.
    you must give more details like what are the Business docuement s are created in SRM
    Muthu

  • 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

  • ASN for extended classic scenario

    Hello all,
    we have SRM with extended classic scenario (EBP-MM),
    is it possible to use ASN (shipping notification) functionality in our system ?
    Kind regards,
    Arthur

    Hi
    ASN can be created by the vendor in SUS system for that XI mapping is required. ASn can be created in SUS by any vendor users. I guess it's not possible with ECS.
    Please check the SAP Consulting Note 1026638 GR Output Integration with MM-SUS Scenario for R/3 <= 47
    You need to have functional background for this:
    To create an ASN against PO or SA release:
    1. you need to compulsarily put how much qty you are sending against the reqd. qty(shown by PO / SA )
    2. dispatch vehicle no. (optional)
    3. road challan no. (optional)
    4. one more optional entry ( sorry I forgot)
    Useful related pointers ->
    Re: how does the GR get into SUS---MM-SUS Sceanario
    ASN in Extended Classic Scenario with SUS
    SUS ASN & Invoice
    The specified item was not found.
    Do let me know.
    Regards
    - Atul

  • 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

  • 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

Maybe you are looking for