Distribution in GOA.

Hi Experts,
I need to set the default value in distribute fields for GOA ( purchase organization and plant). Is there a BADI to make this?
I was looking in the badi BBP_CTR_INIT_UP  parameter MODIFY_DIST_DATA, but this parameter is avaible only to create a initial contracts from ERP. I need to set the default ( fixed value ) in purchase organization and plant for GOA`s.
Thanks,

Hi Kathirvel,
I dont know if this Badi BBP_CTR_BE_CREATE is the solution for my problem. I set the Break point..but doest work.
In the BBP_CTR_BE_CREATE there is the parameter CONTRACT_INTERFACE_FILL with IT_DIST, but this is a import parameter, I need the change parameter in the verification contract moment.
I need a Badi to set in the GOA  the fields purchase organization and plant as default ( fixed value ). 
Do you have any idea?
Regards,
GUstavo

Similar Messages

  • Difference between Header and Item level distribution of GOA

    Hi,
    Can anyone tell me the difference between distribution of GOA at header level and item level?
    can we create multiple operational contracts in ECC when we distribute one GOA?
    Thanks
    Sindhu

    Hi
    Which ECC Version are you using ?
    The transaction for creating a GOA in SAP Frontend is BBP_CTR_MAINCC. The Transaction BBP_CTR_MAINCC cannot be called in the Easy Access. Go with /N then call the transaction.
    <b>Please go through the links below for more details -></b>
    Note 646903 - GOA - Tips and Tricks
    http://help.sap.com/saphelp_srm50/helpdata/en/58/2a8442a07b0e53e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/43/05c0c685da6e72e10000000a422035/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/00/f5c93f4d903b1ce10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/fe/14b042fa34b211e10000000a155106/frameset.htm
    Hope this will definitely help.
    Regards
    - Atul

  • Determine distribution of GOA as a Contract or a Schedule Agreement

    Hello,
    We are using SRM 5.5 Server and R/3 4.7 as a backend system. Uptill now we have distributed our GOA by maintaining the same transaction type on SRM and the backend for contracts. However now we have a requirement to be able to distribute GOA as a scheduling agreement for certain product categories. When we choose Scheduling Agreement on item distribution screen, GOA is again distributed as a Contract.
    How can we maintaine settings or use a BADI to be able to distribute the GOA as a Schedule Agreement type that R/3 uses instead of the contract type we maintained?
    Thank you,

    Hi Gaia,
    you can manipulate the transaction type via BADI BBP_CTR_BE_CREATE
    in SRM. Use a Case logic for field iv_logical_system to switch the transaction type
    before IDoc transfer to the Backend System. Just ensure that the transactio type
    with valid number range is available in the Backend System.
    Cheers,
    Claudia

  • Distribution of GOA to the backend system

    Dear Experts,
    I am working in Extended classic scenario (SRM 5.0). We are planing to configure GOA.
    Can any one give me the steps required to configure GOA and distribute the contracts to the back end system.
    When I create the GOA as of now GOA is getting created but not distributed.
    Regards,
    B.N.Karthikeyan

    Hi,
    Here are the main configuration steps needed:
    1: Make sure you have done the following in customizing:                 
       When you go to define transaction type  and you                       
       choose the entry with BUS2000113, then you click Transaction type     
       go to DETAIL screen of GCTR and choose Global Outline                 
       agreement as a specification.                                                                               
    2: You can follow these steps.                                           
       1. Go to the transaction WEDI                                         
       2. Goto IDoc menu and select Partner Profile (or F6)                  
       3. In Partner Profile, Goto PartnerType LS                            
       4. Click on the client eg. ABCCLNT300                                 
       5. In "Inbound parmtrs" make an entry for BLAORD.Enter the client as  
       Partner number. BLAO as Process Code.                                                                               
    3: In the R3 backend system,                                             
       maintain BLAORD as inbound message type, and maintain                 
       BLAREL as outbound message type                                                                               
    4: One of the requirements for setting up GOA is:                        
       Mapping of the appropriate products,product categories, condition     
       types, document IDs, transaction types and text iDs in the BAdis:     
       *IN EBP  > BBP_CTR_BE_CREATE                                          
    IN the backend system: BBP_CTR                                      
    Any GOA contract in EBP has to be mapped in R/3 with the corresponding   
    entry for conditions i.e 01CT to synchronise the two systems.            
    If the conditions are not mapped, the idocs will not be created.         
    Hence, please map the conditions and check for the distribution.         
    It is also an option to try:                                           
    Please run the function module 'BBP_PD_CTR_TRANSFER', this FM posts the
    IDOC in R/3 and add an entry in BBP_DOCUMENT_TAB,                      
    afterwards call report 'CLEAN_REQREQ_UP' which updates the status.                                                                               
    Kindly ensure all customizing and settings are correct in both SRM and 
    R/3 backend in order for the GOA to pass from systems without issues.  
    I hope this helps,
    Kind Regards,
    Lisa

  • Distribution of GOA into the Backend systems

    Hi All,
    I am having aproblem on the above.
    I created a GOA and tried to distribute to the Back end as Contract & Sch Agreement for two items.
    While the Contract is getting distributed to the BE systems properly,the SC.Ag would either get distributed as a Contract or not at all.
    Distibution Model is OK & in Idoc Monitor (WE02) the status for 53 type is showing error saying "the Object linkag to the GOA does not exist"
    Can any body pl suggest step by step process to check & fix the same?
    Thanks & Regards,
    Nagarajan

    Hi
    Which SRM version are you using ?
    <u>Meanwhile, try the pointers -></u>
    Note 888801 List of invoices with status 'Error in transmission'
    Note 901840 - list 'Error in transmission' shows 'approved', 'Transferred'
    Re: Lock status is not getting updates in GOA
    account assignment problem on GoA
    Re: Item Data in GOA
    Do let me know.
    Regards
    - Atul

  • Distribution of GOA contract on multiple backend

    Hi gurus,
    can someone explain me how to setting organization structure to distribute 1 goa contract to multiple back end?
    More in detail, how have I to model the structure of user that has to create GOA contract?
    Have I to use local purchasing org,...?
    Thank you in advance.
    Best regards.

    Hi Marco,
    the setting in the Org Model depends on you design of purchasing organizations and purchasing groups. The Attribute CT_PROC_TY needs to be maintained in the Organizational Plan on the highest Level of your Purchasing Organisation structure with the Value of the document type uses for global outline agreements. In can be one or more doc types, which you then need to maintain for this attribute in the org structure. If no attribute exists, the system checks the transaction type settings for follow on documents maintained for the doc type.
    In case you follow the standard docs / guides, there is only one doc type GCTR used and this value needs to be maintained for the attribute CT_PROC_TY. It depends with doc type you used during config in R/3 & SRM.
    Cheers,
    Claudia

  • Distribution of GOA in srm

    Hi
    When we try to distribute contracts with services from SRM to R/3 system . we are getting the error as
    "Error in number allocation for service items (NRO : BBP_SRV)".
    How to resolve this issue.
    Regards
    Ashish

    Hi Robert,
    As far as I understand, this error is thrown during the execution of NUMBER_GET_NEXT. Message class is BBP_BE_CTR and message number 006.
    As I see, when the NUMBER_GET_NEXT is called the object is always passed as BBP_SRV and it couldn't find an entry and hence the error.
    In the form routine e1edc20_map, the form routines packno_get and subpackno_get are called. In this case, NUMBER_GET_NEXT is called inside these form routines.
            if sv_packno is initial AND
               sv_subpackno is initial.
    * the service packet was not created before. do it now (whether create
    * or change mode)
              PERFORM packno_get
                USING
                  iv_langu
                  is_header
                CHANGING
                  sv_packno
                  ct_return
                  cv_error_flag.
              PERFORM subpackno_get
                USING
                  iv_langu
                  is_header
                CHANGING
                  sv_subpackno
                  ct_return
                  cv_error_flag.
    You can possibly check this part with the data you have to see why it happens. It would be easier if you can debug through this.
    In addition to checking if you need to add that entry, you can also check if this part of code is behaving as you expect it to.
    Regards
    Saravanan.
    Please award if useful
    Edited by: Saravanan Sadasivan on Mar 12, 2008 11:27 AM

  • GOA distribution to R3 - Tax Code for ERS vendors

    Hi all,
    Having an issue with GOA distribution to R3 for evaluated receipt settlement vendors. For ERS vendors, tax code is a required field. There is not a tax code field in the GOA and this is not being passed in any iDoc segment I can find. My current tax configuration is calculate tax in backend, i have maintained tax codes I0.U1, I1 with U1 set as default. As shopping carts are transferred from R3 they are assigned U1 as expected and PO's generated in the BE from these external requirements are getting the U1 as expected. The problem is with contracts and scheduling agreements. Everything is fine unless the vendor has the ERS indicator set. Tax code becomes a required field.
    Has anyone else experienced this? I've' researched SDN and everything talks about shopping carts and PO's, which is working for us.  I cant find any info on the contract distribution. I've investigated the BADI's associated with tax calculation in SRM but I'm not sure these meet the requirement for ERS vendors.
    Am I missing configuration? Is one of the tax badi's the way to go? Any information is appreciated.
    SRM SERVER 550
    R3 46c
    Classic - Plan-Driven Procurement
    Thanks,
    Justin

    Hi
    <b><u>Please refer to few OSS notes.</u></b>
    <u>Note 1033458 - Item level Tolerance values in GOA not transferred to R/3</u>
    <u>1012486 Important Information on upgrading ERP-Systems in HA-Setups
    1014820 Indicators reset in Active versions when line item added
    1029026 Prob in conf. create-Diff in ERS flag for SRM and R/3 vendor
    849567 Output Control for ERS Invoice in Program BBPERS
    703876 Release note SRM Server 5.0 SP00
    762984 SRM40-SUS: Implementation of customer enhancement fields
    1010791 Flag Confirmation based Invoice Verification set erroneous
    1018855 Vendor flag POR expected is not replicated from backend
    Note 967107 - New logic for grouping backend contracts out of a GOA
    909516 SRM40/CTR:New line itm distribution flag cannot be unchecked
    1025863 Wrong Currency code during GOA replication to R/3
    1009872 Contracts : GOA Distribution value divided by 100 
    908058 CheckMan errors - Attachment Original transfer for Contracts
    940632 Distribution incorrect-When invalid Purchasing Org entered
    942008 SRM Distribution of GOA to R/3 System: Scales missing
    945029 Distribution of Target Quantity to QW8 failed
    880097 Attachment Original transfer for Contracts
    989367 Performance improvement for new GOA distribution logic
    916562 CM/CND: Dump in distribution of GOA with deleted line items
    922172 Contract attachment distribution enhancements
    925014 More than one attachment not getting distributed to backend
    923627 Attachement transfer to backend with possible file formats
    923227 Attachments transfer not working in Background 
    937221 CTR: Impossible to modify distribution in Initial Upload GOA
    967107 New logic for grouping backend contracts out of a GOA
    </u>
    <i>Incase this OSS notes, don't work, then</i>
    <u>Please try do this as well. Uncheck the ERS indicator, but then also pass tax codes from from GOA.
    Then try out again.</u>
    <u>For BADIs and other useful information, refer to these forum links</u><b>GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
    Distribution of GOA in R/3
    Source determination in backend (R/3) for distributed contract i.e. GOA
    FM or BADI s' used to create a GOA
    Transaction For Creating GOA
    <b>Incase nothing helps, Please raise a OSS message with SAP as well.</b>
    Hope this will help.
    Please reward suitable points, incase it suits your requirements.
    Regards
    - Atul

  • GOA distribution to several contracts in r/3 not working

    Hi,
    I have a problem with GOA distribution to backend. I would like to obtain the situation when I have 2 items in GOA, in Distribution I have also two inputs (both for the same purchasing organization, but locations are different) and the GOA is distributed to R/3 to 2 different contracts - one for the first location and first item and the second contract for second item and location. I'm not able to get that working right.
    Typically, does the SRM generate 2 different numbers for to r/3 contracts that were distributed from GOA?
    I have GOA number 5600000150 and no matter how many items and locations (in Distribution) I indicate, there is always only one contract in r/3 is being created. When I indicate for instance 2 purchasing organizations in Distribution, there's only one contract in r/3 created for that first one.
    Please help if you know what can be wrong.

    Hi
    Definitely, seems to be a bug in the system.
    <b>Please go through the SAP OSS notes below, depending on your System release and support pack details -></b>
    Note 648393 SRM: Distribution of global outline agreement conditions
    1063593 Invalid price during contract generation in Backend
    859049 SRM 5.0: Restrictions for uploading and downloading
    1043517 Contract Upload: Purchasing Org. is getting lost
    956190 GOA created in SRM3.0 cannot be released in higher relaeses
    1042111 GOA status set to Distribution Incorrect wrongly
    743221 Deleted price during contract generation in Backend system
    656181 Release synchronization of releases on services
    896187 Line Item Internal Note not transferred to R/3 contracts
    942008 SRM Distribution of GOA to R/3 System: Scales missing
    852469 Error in contract distribution with service items
    954183 Contract price cut when GOA is distributed to backend system
    979111 Erratic distribution on adding new item or distribution
    781344 Deleted conditions on GOA in EBP do not update backend
    1030307 Portal Information not maintained in customizing
    1033458 Item level Tolerance values in GOA not transferred to R/3
    1037623 Incorrect Error message for maintaining distribution entries
    1028659 Missing contract number during the synchronization of releas
    1025863 Wrong Currency code during GOA replication to R/3
    897759 Allow transfer of global outline agreement
    909516 SRM40/CTR:New line itm distribution flag cannot be unchecked
    Note 847398 Incorrect determination of the EKGRP back end
    P.S.: In SRM 6.0, hierarchies on GOA is not present. Better to get more details from SAP by creating a Customer OSS message as well.
    Hope this will help.
    Regards
    - Atul

  • 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

  • Create IDOC Type ORDERS in BackEnd System

    Hello together,
    we use " extended classic scenario" in our  SRM 4.0 and replicate PO's in the ECC 6.0 ERP Backend System. We would like create during the replicat a Message Type (IDOC) ORDERS in Backen System. I háve customized (NACE / MN05) but it is not poosible to generate a IDOC. I have read it is necessary to activate a USER-EXIT for BBP PO's.
    My question:
    Which USER-EXIT and how must i create this!
    Thanks for Answer!
    Regards,
    didisap
    Edited by: Dietmar Blome on Feb 8, 2011 11:59 AM
    Edited by: Dietmar Blome on Feb 8, 2011 12:01 PM

    Hi,
    Pls refer to following links for sample code ->
    Re: Status distribution incorrect in GOA
    Re: Distribution of GOA in R/3
    Re: GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
    Re: Source determination in backend (R/3) for distributed contract i.e. GOA
    FM or BADI s' used to create a GOA
    BR,
    Disha.
    Do reward full points for useful answers and close the thread if your query is answered.

  • Create Contract in Backend System

    Hi Experts,
    I need to implement the method CONTRACT_LOGSYS_DETERMINE (on the BADI BBP_DETERMINE_LOGSYS) setting the logical system to create Contracts in the Backend system.
    But, I want to found this value (CV_LOGSYS) dinamically, without need to put the local system on the code (CV_LOGSYS = AABBCCC111).
    Can anyone help me with this???
    Thank you!
    Best Regards,
    Luciana

    Hi,
    Pls refer to following links for sample code ->
    Re: Status distribution incorrect in GOA
    Re: Distribution of GOA in R/3
    Re: GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
    Re: Source determination in backend (R/3) for distributed contract i.e. GOA
    FM or BADI s' used to create a GOA
    BR,
    Disha.
    Do reward full points for useful answers and close the thread if your query is answered.

  • GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution

    Hi everyboby,
    I'm trying to distribute a GOA, or better I have distributed a GOA to ECC, but I have a problem 2 problems:
    1.) account category on the idoc BLAORD (inbound in ECC) is always <b>U</b> (Unknown). Instead I want that account category is blank (my back end contract has to have <i>item category</i> <b>W</b> (material group) and <i>account category</i> "blank", in this way i can create a release order with item category</i> standard and <i>account category</i> "blank", for direct material). How can I assign Account Category to GOA? It must be possible,I think me, do it with standard customizing, without any BAdI!!!
    2.) I want to distribute GOA to several plant on the same backend system, but obviously the contract number is the same and therefore on ECC back end only one contract is created. Is it possible to do this distribution without custom implementation like BAdIs?
    Thanks in advance.
    Bye!!!

    Hi Marco,
    1. the account assignment is U only for text items. In case material record driven line items are transferred, the account category is blank, like you expect.
    2. A GOA can only be distributed for each Backend System, and within one document is create for each combination of POrg and CompCode. This only works when you have POrgs arranged within Company Codes and not accross Company Codes. If the later is the case, only one document is created.
    More than one document is only possible via development by programming method MODIFY_DATA_CTR of BAdI BBP_CTR in R/3.
    Thanks,
    Claudia

  • SRM GoA with status as "Distribution Incorrect" althogh contract is created in ERP

    Dear SRMers,
    We are using the classic scenario with SRM 7.0.2.
    I am facing a problem with Global out line agreements in SRM where the status of the GoA is showing as: "Distribution incorrect".
    We have verified that the respective IDOC of type BLAORD is generated and posted in the backend R/3 system and the respective Contract is also created in the R/3 system(ME33K).
    Can you advise me why this wrong status and can we correct this status to: "Distributed"
    or Is it a standard product error?
    Looking for your valuable advise.
    Thanks in advance.
    -Loknath

    Hi Loknath,
    Try to check transaction RZ20. It should show the real errors behind the "distribution incorrect status".
    I hope this helps,
    Marta

  • Error in GOA distribution

    Hi experts I have the follow error in GOA distribution when I try to create Scheduling agreement in R/3:
    'No batch input data for screen SAPMM06E 0514'
    I could see that the problem is caused because there is no Company code information coming from SRM and it necessary in R/3 contract creation.
    I could see too that some friends solved the problem inserting the company code in badi BBP_CTR, I would like to know what is the metod user for it?
    How can see if the problem is really copany code missing?
    Thanks
    Nilson

    I think this is probably due to the material not maintained in that Plant/Porg. But it shows a different error message.
    Regards, IA

Maybe you are looking for