GOA + Local Contract distribution to R/3 in Extended Classic Scenario

Dear SRM Gurus,
System Information: SRM Server 5.5   EBP5.5
Technical Scenario: Extended Classic Scenario.
Q1) We have created a Global Outline Agreement in EBP. We want this to be distributed to R/3.
But when we click on distribute, it does not get distriduted to R/3 ???  Is there any IDOC to be maintained----wich one ??
Please guide me as to how can we go ahead with this.
Best Regards,
ANIL RAJPAL.

Hi Anil,
The IDOC to be maintained is: BLAREL
For detail information you can visit the links.
http://help.sap.com/saphelp_srm50/helpdata/en/00/f5c93f4d903b1ce10000000a114084/content.htm
https://websmp104.sap-ag.de/~sapidb/011000358700002529571998/blarel02_d.htm
Also you can have look at notes:
643823
953269
671764
641919
Pls let me what all configuration you have done for GOA functionality so that I can suggest you something specific.
Best Regards,
Amit
Do reward the points if ans is helpful!!!

Similar Messages

  • 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

  • GOA as SOS (Source Of Supply) in extended classic scenario

    Hi,
    I understand that when I create a SC in EBP, GOA can't be a SOS in "Extended Classic Scenario (SRM 5.0)". If I want to make GOA as SOS, how do I do it ?
    I have searched the forums and found that the below BADIs can be used.
    BBP_CTR_BE_CREATE
    BBP_CTR_INIT_UP
    BBP_CTR_MAIL_BADI
    BBP_CTR_MASS_BADI
    Now I am looking for someone who has done this scenario and please explain how did you do it ?
    With regards,
    Pranav

    Hi,
    I had a former project where I modified SRM standard source so that I can use GOA as source of supply in extended classic scenario. In Standard, as you know, SAP doesn't allow to use GOA as SOS in extended classic. In extended classic, we have to use local SRM contract as SOS. In my case, it was SRM 3.0.
    Cheers.

  • Extended Classic Scenario-Replication of Local PO to R/3 fails

    Hi,
    In the Extended Classic Scenario (SRM4.0/ECC5.0),we are creating Purchase Order from the Sourcing Cockpit. Local PO is getting created , but is not getting replicated to Backend R/3.
    After debugging through BBP_PD_PO_TRANSFER_EXEC , noticed that all the PO data is available when BBP_PO_INBOUND is called .But the PO number is missing when the BAPI_PO_CREATE1 is called. Because of this , system is searching for internal number assignment and since only external number is assigned for the document type , it is giving error.
    Can anyone suggest if we are missing anything.
    Regards
    garugu

    Hello,
    this is strange, because in ECS the local PO gets an ID, and this ID is used during the transfer to R/3.
    Debug BBP_PD_PO_TRANSFER_EXEC once again to see where this ID is cleared.
    To you have activated the BADI BBP_ECS_PO_OUT_BADI to transfer data to R/3 ?
    Be carefull, some BADI need to populate all export parameters/tables (E_*) otherwise the inbound data is considered as erased.
    Where is the ID disappearing ? in SRM just before calling R/3, or in R/3 ? In that case look at user-exit or BADI is R/3.
    Rgds
    Christophe

  • Cost distribution in Extended classic scenario

    Hi All,
    We are in SRM 4.0 using extended classic scenario.
    When we create a purchase order with cost distribution, it gets copied to backend system. But the partial invoice field in backend PO is always having the value "Distribution in sequence".
    In configuration for account assignment category, it has been defaulted to "Distribute proportionately".
    When we checked with SAP they told that for SRM POs it will always be distribute in sequence. It has to be distributed while posting MIRO. This value is hardcoded in SRM PO transfer program. It is very strange and moreover this is a essential functionality which needs to be in SRM.
    Any one using extended classic scenario, could you please tell me how you are handling multiple account assignments?
    Please help me.
    Thanks,
    Arun

    Friends,
    If you are using cost distributions in extended classic scenario, then could you please check and let me know the value that you are getting in the "Partial Invoice" field in Account assignment tab of backend PO.
    Please help.
    Thanks,
    Arun

  • Extended classic scenario local PO Output status

    Hello all ,
    Need some inputs on extended classic scenario local PO Output.
    My requirement is , when ever the put get process successfully in SRM , I need to send a mail to requester saying that u201C for this particular output got processed successfully u201C
    I have business requirement, we need to run this report every 30 min, This report has to pull out the all the PO number from the current time to past 30 min, for the output got processed successfully.
    To meet this requirement, I am using the output log entry table PPFTTRIGG where we can see the all the PO with the status and time stamp also.
    But some how, this table maintaining incorrect time stamp.
    Ex: If I create PO, process the PO output, and if I see the time stamp for this PO, its showing as 10 min before the current time.
    Did anybody come across this issue? Or can anybody suggest me any alternative approach for this.
    I mean is there any function module/ table available, which will give PO Output status also.
    Can you please give me any pointers for this?
    Seeking your help on this.
    Wish you a advance happy new year.
    Thank you.

    Hi Latha,
    Did you have a look at the standard report RSPPFPROCESS. For PO's please pass the below selection screen values along with the appropiate date & time details:
    Application = BBP_PD
    Action Profile = BBP_PD_PO
    Then regarding the time difference, please make sure that the application server time is sync with the actual time of the time-zone. This could also be a reason.
    Then what you can do is to clone the RSPPFPROCESS program and add the email notification logic on that.
    Please have a look at the BADI BBP_PROCESS_PO, this can be of some help for your requirement.
    Hope this solves your problem.
    Regards
    Kathirvel

  • 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

  • Contract preference over PIR in SOS in Classic Scenario

    Dear all,
    We are in Classic Scenario, SRM 4.0 (SRM Server 5.0) SP9 with R/3 4.6C backend
    When a Material has a contract and a PIR in the backend, if the material is added from catalog in the Shopping Cart, both Purchase Info Record and backend Contract are found as Source of Supply and then apparently no priority exist then no automatic Source of Supply is defined (user must select one to have one assigned).
    At the opposite doing the same in ME51N in backend selects contract automaticaly (when Sourcing determination is flagged).
    What we want is that if a Contract and a PIR are found for the material in the SC then the contract is taken automatically as preferred Source of Supply like in ME51N.
    Any idea?  Is that  a bug? Or what can we change? BADI?
    Thanks a lot
    RD

    It is possible to disregard inforecords for sourcing purposes in R/3. If you do so EBP will automatically disregard inforecords as well. This approach consistently removes info-records as sources of supply in both, R/3 and EBP. here's how:
    1. run cmod transaction in R/3 and create your project
    2. Assign enhancement LMEQR001 to your project
    3. In component EXIT_SAPLMEQR_001 there is include
    ZXM06U52 and you need to enter some code in this include. Here is an example how to remove ALL inforecords:
    INCLUDE ZXM06U52 *
    loop at t_sources.
    if not t_sources-infnr is initial.
    delete t_sources index sy-tabix.
    endif.
    endloop.
    Note:  BBP_SOS_BADI can only be used for customizing the searches of local sources of supply: local contracts, vendor lists and or vendor interlinkages

  • Local Purchasing Organization in extended classic scenario SRM 4.0

    Hi all,
    I have tried to make settings for updating vendor master records. I used the following path in IMG.
    SAP Implementation Guide > SRM Server > Technical Basic Settings > Settings for Vendor Synchronisation > Define Settings for Each Backend System
    There i wanted to make the entries for: Order, LogSystem, Flag in NoBEPchOrg and Local Purchasing Org. For the Local Purchasing Org. field i could not select any entries.
    My question now is how can I check if there is any local purchasing organization maintained. In the EBP Organizational Structure I have set the flag for the purchasing organization and have entered in the "corresponds to" the number of my purchasing organization from the backend and i have selected the SRM-System in the next field.
    Best regards,
    Bernd

    In the organization structure, under function tab leave the corresponds to field blank

  • SRM 7 Contract Distribution not possible in PPS

    Hi all,
    We're on SRM 7 / ECC6 EHP3, and activated PPS. I have been told that for PPS the  distribution is not supported completely, and hence the functionality is disabled, NOTE 1354971.
    My problem is, since we have activated the PPS functionality in all the landscapes we have at present. I can not switch PPS off or refer to another system without the PPS. By reverting the note 1354971, i have only managed to get an assign distribution button active at item level. I would have assumed, the contract/GOA should be able to be distributed at header level. Consider a contract with 1000 items.
    Can please someone tell me what is the process for distributing a contract completely. Not just selective items.
    Moreover, this does not work, when i have outline items/sub items in the contract.
    Regards
    Ali

    Dear Ali,
    Interfaces(XML) which are used to transfered the central contract are not extended to all the fields related to PPS functionality. Eg. Guaranteed Minimum.
    These fields will not be transfered to backend and other process like release value updation to the backend contract has limitation as PPS funcalities can be used only in extended classic scenario.
    So we have a limitation and also this functionality will not be supported  in PPS.
    As it was a bug , we have corrected this through the note 1354971.
    Nevertheless,  you can enable this funcationality and use with the limitation.
    You will have to handle this through custom meta data handle where you need to create dynamic class and method and maitain in the customizing table /SAPSRM/V_MDA_HC. You can enable the Assign distribution button and link in the dynamic class.
    You can check the configuration in the standard meta table /SAPSRM/V_MDA_HD for reference.
    I hope this helps,
    Kind Regards,
    Lisa

  • GOA versus Contract on SRM

    Hi All,
    We are on SRM 5.0 Server 5.5 and 2 back-ends systems: 4.6c and 4.7
    According to our scenario we have following situation basing on categories
    1) GOA created on SRM and replication after approval to back-ends: no Shopping cart will be created in SRM for these categories.
    2) GOA created on SRM and approval + Shopping Cart created with reference to GOA always on SRM. GOA should also be replicated to back-end.
    According to the above scenario we have some questions:
    a) Is it possible to use the Global outline agreement as a source for making on SRM shopping cart? Looking to SAP documentation seems that the GOA cannot be used as source document for Purchase order creation...
    b) If GOA is not suitable which contract should we use: local contract? Is it possible to replicated local contract to the back-end? Can you advice some BAdI to do it?
    Thanks in advance
    #Bill J.

    Hi Bill,
    In extended Classic Scenario you can create GOA and replicate them in the back end but you cannot use them as source a source.
    Otherwise you can use local contract as a source but you can not replicate them in the back-end system.
    Check Badi
    BBP_CTR_BE_CREATE
    BBP_CTR_INIT_UP
    BBP_CTR_MAIL_BADI
    BBP_CTR_MASS_BADI
    Hope it helps
    Best regards
    Guido

  • Local contract and classic scenario

    Hi all
    A question regarding contracts - and interpretation...
    On help.sap.com the following is stated:
    <i>SAP Enterprise Buyer, as the central purchasing system, saves the contract data and uses it for local purchase orders and purchase orders of the extended classic scenario.</i>
    I interpret this as, if one is using the classic scenario it's not possible to operate with local contracts in the SRM system. Can anyone confirm this?
    And if so - any workarounds?
    Our dilemma is that we have an extended classic scenario. Some materials are stock materials, and for these materials we are using a BAdi to switch off the extended classic scenario. No contract data is now added to the shopping cart, which I think is due to the classic scenario.
    Thanks for your help in advance
    ;o)
    Maria

    Maria
    If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
    Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
    Then local contract data should pick as SOS from the vendor list.
    If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
    Let me know if the above works or not.
    PS : Reward points if helpful.
    Regards
    Jagadish

  • SRM 7 Contract Distribution not possible in PPS - is it true ?

    Hi SRM Gurus,
    I gather that the SRM 7.0 Central Contract are not distributed to ECC 6.04 in PPS environment. 
    ( Ours is SRM 7.0 ECC 6.0 Enhp 4 with PI 7.11 on PPS - ECS.)
    Correct me if i am wrong.
    If so, is there any other way to distribute Central Contract to ECC .  Even it its partial distribution. 
    Thogh, I hv config for CCTR following the SNote 1268821. To start the problem, the Distribution button on the header of the contract is disabled.  CCTR tran type configured both in SRM and ECC.
    Kindly share your thoughts.

    Hello,
    You can try reverting the note 1354971, to get an assign distribution button active at item level.
    Interfaces(XML) which are used to transfered the central contract are not extended to all the fields related to PPS functionality. Eg. Guaranteed Minimum.
    These fields will not be transfered to backend and other process like release value updation to the backend contract has limitation as PPS funcalities can be used only in extended classic scenario.
    So we have a limitation and also this functionality will not be supported in PPS.
    Nevertheless, you can enable this funcationality and use with the limitation.
    You will have to handle this through custom meta data handle where you need to create dynamic class and method and maitain in the customizing table /SAPSRM/V_MDA_HC. You can enable the Assign distribution button and link in the dynamic class.
    You can check the configuration in the standard meta table /SAPSRM/V_MDA_HD for reference.
    Courtesy : Lisa Norris!
    Re: SRM 7 Contract Distribution not possible in PPS

  • Local Contract management (PCTR)

    Hi Friend,
    Business scenario: Extended Classic Scenario (ECS)
    We planning to implement local contract management (PCTR) in SRM7.0 and also contract should available to requester to create SC and after Purchase order gets created.
    Could you please tell us the configuration and technical details.
    Appreciate your valuable inputs.
    Thank You!
    Shrini

    Hi,
    Just to remind; as you are impelementing Local Contract Management;  contracts you will create, will not be updated in ECC. 
    You can create contract using puchaser log in. Assign role u2018operational purchaseru2019 to the purchaser.
    You will see contract (material) in Source of Supply of SC.
    Regards,
    yaniVy
    reward if helps

  • Local Contracts in SRM

    Hi,
    I have the following question:
    I'm trying to do a call off against a Local (Purchase) Contract but can't seem to get this to happen in the Classic scenario?  I've tried to assign the contract line item via the Sourcing Cockpit but it still doesn't reflect the call off against the contract. I've been able to do this in the Extended Classic Scenario. Is this a limitation in the Classic scenario?
    Currently on SRM 5.0, Classic scenario.
    Any info appreciated.

    Hi
    local contract is  applicable to only srm in extrended classic scenario.
    but you can bring r/3 contracts in to srm by reports and the r/3 contracts will be available toy you and you can lock the backend contract at item level.
    regards
    muthu

Maybe you are looking for