Completion workflow in extended classic scenario

Hi gurus,
We use extended classic scenario with SRM Server 5.5.
In ppoma, each purch org and purch groups has the local and the backend. Vendors are replicated to backend purch org and then also to the local purch org.
I have seen that in classic scenario purchasers should be assigned to the local purch org. however, completion workflow only determine the agent (purchaser) if it is in the backend purch org.
The problem is that then this purchasers cannot manage any business partner.
How can I solve it?
I have seen other clients that the completion workflow determine the agents in the local purch org...
Many thanks!!!
Regards
Patrícia

Hi,
In the Extended classic scenario, local purchasing organisation and purchasing groups are required to create shopping carts and purchase orders. in this scenario, when
the vendors are replicated from the SAP back-end using BBPGETVD,BBPUPDVD program or vendor-synchronization programs, the vendor update in SRM is only for the R/3 purchasing organizations. because the local purchasing organisations are required in SRM for the Extended Classic or standalone scenario, these replicated vendors needs to be extended to the local purchasing organisations.
organizations can use Tx. BBP_UPDATE_PORG for extending the vendors to the local purchasing organiztion.
see OSS Note 390546 for more info.
Regards
vasanth

Similar Messages

  • No GR on Confirmation Approval in Extended Classic Scenario

    Hi all gurus out there,
    We are trying to implement confirmation approval workflow in our SRM system. Our SRM version is SRM 3.0 or EBP 4.0 and we are operating in extended classic scenario.
    We implement the approval workflow WS10400002 (1-step approval) and WS10400010 (no approval). WS10400002 is used in situation when an administrator does the confirmation and will go to the requestor for approval. Here, when the requestor approves the confirmation, the status is updated correctly to 'Approved' but no goods receipt is triggered by the system. We looked at the workflow and found that there is no task/activity to do the post goods receipt in the backend system.
    Can someone please confirm whether these are the correct workflows that I should be using and that it is not a bug? I just want to make sure it is not as a result of a standard limitation before going back to SAP.
    Cheers!
    Siow Fong

    Hi Guys,
    I checked with SAP on this and found out that the standard codes would have created the goods receipt. This creation is no longer coded in the workflow itself (like the old workflow used to be). The reason why it was not working for us was a piece of code being added that prevented the creation of the goods receipt.
    Regards
    Siow Fong

  • 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

  • 'BAPI_POEC_CREATE' function doesn't work with extended classic scenario

    Hi everybody.
    Antecedents:
    We are working in an extended classic scenario.
    When we create a Purchase Order via ITS in SRM, the system works ok, the PO is replicated in the ERP system.
    But when we execute “BAPI_POEC_CREATE” function module in order to create a PO in SRM, no message are available in the application monitor, but the PO is not replicated in the ERP system.
    Both exampled were created with exactly same data (partners, items, categories, accounts, …)
    Moreover when we modify the second PO created via ITS, the systems doesn’t show any error message, we can order our PO again without error, but the PO isn’t replicate in the ERP system.
    1. We executed “BAPI_POEC_GETDETAIL” function module, and there is only a difference between POs, E_PO_STATUS table.
    PO created by transaction has 8 entries:
           I1009 X
           I1015 X
           I1021
           I1038
           I1039 X
           I1043
           I1080 X
           I1180
    And PO created by BAPI has 5 entries:
           I1015 X
           I1021
           I1038
           I1043
           I1180
    2. We run “BBP_PD” transaction, and there is only a difference.
    PO created by transaction mode shows:
    - Message: W BBP_PD 830 Default values have been taken from Vendor PRUEBA10/purchasing organization Área Global Compras (org. compras)
    And PO created by BAPI
    - Message: No Messages
    Could anyone help me with the problem?
    Thanks in advance.
    Raúl.

    Hi Raúl,
    this is exact, BAPI_POEC_CREATE is designed to create local PO.
    If you want to replicate it to R/3, then you have to change it to an ECS PO.
    In BADI BBP_DOC_CHANGE_BADI, called at the real beginning of BBP_PD_PO_CREATE, you will have to change some data to enable the ECS scenario:
    - change header subtype to EP
    - change header log system to SRM (keep FI LS as is)
    - determine a backend purch group & org
    - complete BE fields (be_object_id, be_object_type, don't change be_log_system because it will be determined during the transfer, be_pur_org and be_pur_group will also be determined during the transfer)
    - ... and maybe other R/3 relevant fields
    Compare both PO one by one, and adapt the gaps.
    Rgds
    Christophe
    PS: please reward points for helpfull answers

  • Extended Classic Scenario PPOMA_Purchasing Org and Group

    Hi gurus,
    We are working with SRM 5.5 and we are having problems with the assignments for the Purchasing organization and Purchasing groups in the PPOMA.
    In the documentation it says we should have one box for the R3 Purchasing Organization (flagged and referred to the backend POrg) and one for the Local Purchasing Organization (flagged but NOT referred to the backend POrg). The same for the Purchasing Groups, the one under R3 POrg will be flagged and referred to the PGroup in R3 and the one under the Local POrg will have the flag but it will not be referred to the backend PGroup.
    Afterwards, in the attributes for the Local POrg and Local PGroup, with the attributes PURCH_ORGX and PURCH_GRPX the local and the R3 POrg and PGroup will be assigned each other.
    The purchasers will be located in the Local PGroup. The R3 POrg and PGroup will never have users assigned.
    The problem is that all the workflow is only working if the "Local" POrg and Group have the backend purchasing organization and purch group assigned in the Function Tab. This means that the 2 boxes for R3 are no longer necessary. In the documentation it says that this version of SRM needs both boxes for the POrgs and the 2 boxes for the PGroups. We have flagged the Extended Classic Scenario.
    Any help on this? It's because of the version?
    Many thanks and regards,
    I will give Points!

    Hi Ana
    PURCH_GRP     Purchasing group     Number of an organizational unit that is indicated as local purchasing group in the organizational plan.
    This attribute is simulated. You define an organizational unit as company on the Function tab.
    PURCH_GRPX     R/3 purchasing group     Number of an organizational unit that is indicated as the R/3 purchasing group in the organizational plan. The value contains the ID and the associated backend system of a backend purchasing group.
    This attribute is simulated. You define the ID and the associated system on the Function tab.
    PURCH_ORG      Purchasing organization     Number of an organizational unit that is indicated as local purchasing organization in the organizational plan.
    This attribute is simulated. You define an organizational unit as purchasing organization on the Function tab.
    PURCH_ORGX     R/3 purchasing organization     Number of an organizational unit that is indicated as the R/3 purchasing organization in the organizational plan.
    This attribute is simulated. You define the ID and the associated system on the Function tab.
    can you elaborate more?
    in ECS also we can map the backend purchase organisation/ purchase group for purchasing activity.
    there might be a resposibilty tab for the backend purchase group might be mapped the responsible purchaser list (dept).plz check it up
    regards
    Muthu
    regards
    Muthu

  • 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.

  • Extended classic scenario local PO

    Hi All ,
    Need some inputs on the extended classic scenario local PO.
    There is couple of functionality which we need to do for the PO. I mean when the PO gets created automatically after shopping cart completely approved
    We can change the same PO from the process purchase order also.
    But if I want to map couple of the fields, when PO is getting created automatically how can do that one. And I donu2019t want map these fields when the PO is from the getting changed process purchase order also.
    I am using the BADI, BBP_DOC_CHANGE_BADI (PO_CHANGE Method) to map these fields.
    The thing is here , this BADI will call even for the automatic PO creation and also for changing the PO .
    Currently when I noticed PO gets created automatically by the user id u201CWF_BATCH u201C , So I am using the same the logic like .
    If sy-uname = WF_BATCH
    Do the mapping part
    Endif,
    But I donu2019t think so; this logic will work all the times.
    Please can anyone give me some pointer for the same, it will be really helpful for me .
    Seeking your help on this
    Thank you,

    Hi Latha,
    This is a bit tricky one. Yes you are vry correct, the logic is not that fool proof, as the PO can be subjected to so many changes back & forth; even approvals can be done after a change is completed etc.
    The other alternative is to go ahead the document version. You can use the function module BBP_PD_PO_GETDETAIL and the table E_VERSION will contain all the versions of the PO. This should differentiate the change & initial PO verions.
    Hope you can build your logic based on this; this is a better logic on par with the existing one.
    Regards
    Kathirvel

  • 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

  • PO status Held in extended classic scenario

    Hello SRM gurus,
             I am very new to SRM with MM background. I have a question which i think you guys might have come across earlier.
    We are using version 5.5 extended classic scenario, replicated all the vendors and materials from R/3 to SRM, did all the basic configuration needed, we are able to see those vendors and materials in SRM also. here is the issue. we are trying to add an item to the shopping cart which in turn creates a PO in SRM so that it automatically replicates in R/3. But the PO status in SRM is Held and we found out that vendor is not assigned to the PO which is very clear why the PO has been held. So what could be reason the vendor is not getting assigned to the PO though we have the inforecord and source list(checked the fix indicator also)for the same material and vendor in R/3 ?
    I'm sure many of u would have come across this issue. please help me out.

    Hi Satya
          Thanks for your quick response.
    1) We are using Workflow without approval process
    2) I checked BBP_NUM_SUSPO in SRM server. There is nothing in there. Is this the correct number range for PO? I checked OMH6 in R/3. please tell me how to sync it.
       When we try to post it after editing the PO with vendor number, we are getting Waiting for approval error though we have activated Without workflow approval process. let me know why is it showing that error?
    We have another strange issue which is, We have assigned a material say M01 to a pur.group P01,Pur.org POrg1 and vendor V01 and have info record and source list, but we don't see this Pur.grp when we create the shopping cart and it defaults to some other pur.grp say AP01 which we deleted long back. can you tell me where it is picking up the deleted ones?
    thanks
    Pradheep.

  • PO Change in Extended Classic Scenario

    Hi SRM Experts,
    Our client is using ECC 5 and SRM 3 (BBPCRM 4.0) and using classing scenario successfully.
    Now we have started using extended classic scenario for limited suppliers.
    Now the client requirement is to change the PO after approval.As you know that in ECC the PO can be displayed only.
    And the PO already directly submitted to the supplier.
    Is it possible to change the PO after submitting to supplier ?
    They are looking for some changes in text/shipping address etc.
    Appreciate all your suggestions.
    Thanks and Regards,
    Pradeep

    Thanks Masa for your quick reply.
    Could you please tell me that,we are using work flow for SC approval and when the Shopping Cart created the WF also starts and finally the SC get final approval the PO will push to supplier directly and the same will be replicated in ECC (display only).
    So after activating the version control will it still allow the user to change the SC/PO after completing the approval ?
    If so do we need to make any changes in our WF ?
    Thanks and Regards,
    Pradeep

  • 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

  • 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

  • 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

  • Difference between Classic Scenario and Extended Classic Scenario

    Hi Expers,
    I need your help again........:-)
    I just want to know what is the differne between classic and Extended Classic Scenario.
    Points will be rewarded
    Thank you
    sam

    Hi Sam,
    (explaination frm a previous thread)
    Difference between scenarios
    WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
    With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
    If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
    Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
    In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
    Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
    Please check this too:
    http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
    BR,
    Disha.

  • Extended classic scenario clarification

    Hello
    I have a question in case of a extended classic scenario.
    Shopping cart is created by a employee and approved by a manager. But still no vendor exists in the shopping cart after approval. Now how the PO is created in SRM.
    Note sourcing is activated, strategic and operational purchasers exits. How the process is implemented. Will the purchasers get informed via work items? Will they get shopping cart work items or incomplete PO work items.
    Could any of you please give clarity on this.
    Thanks in advance.

    Hi
    Once the shopping cart is created, based on sourcing config and also based on Purchase group responsibility the respective shopping cart flows in to the 'sourcing cockpit'(SOCO). Buyers/Purchasers will see all the open shopping carts and in SOCO there are multiple options available for purchasers to do. Such as creation of PO by just adding the vendor and right price/  creation of Bid or Auction or contract/   group the similiar requirements into one requirement create PO etc.
    If the follow on document is chosen to be a PO or Contract then the shopping cart will go out of the SOCO once the PO/contract created. If at all the SC is considered for Bid/Auction process then the SC remains in SOCO till the Bid/Acution process is completed. Hope this helps
    You can also look at SAP application help for SRM sourcing
    http://help.sap.com/saphelp_srm702/helpdata/EN/d8/33ec56f17f4404806072749f7e764f/frameset.htm
    Rgds/Kiran

Maybe you are looking for

  • Safari, Mail, Dashboard quit unexpectedly

    Everytime I try to open Safari, Mail or my Dashboard I get the message "The application (Mail or Safari or Dashboard) quit unexpectedly. I've tried dragging the Library/Preference folder to the desktop and it doesn't work, I've tried dragging differe

  • JDBC Adapter in async. scenario

    Hi everybody. I have the following scenario: R/3  --->  XI ---> Legacy In this scenario, there is at the moment a synchronous call from XI -> Legacy using the JDBC receiver adapter. In this call there are various SELECTs and UPDATEs, so I have to use

  • Augmented reality on mobile devices (android and ios)

    Him, is there already some sort of extension for AIR 3 capable of identify visual tags for augmented reality applications on android and on iOS?

  • Parameter error on call pl sql

    Hi all, I use Flash MX for client side and ColdFusion MX 6 (Hot Fix apply) for biz logic and ORACLE 9i database on HP-UX11i. Flash MX parameter and CF connect using Flash remoting gateway, there is no error between these. in CF, the parameter come fr

  • Confusion in Select query having a inner join on single table

    Hi, I was going through coding and came a accross a select query which has a inner join on a single table. I am getting confused while analysing this . Please someone can help me analysing this query. select         m~MATERIAL         s~NUMERATOR s~D