GOA - Q

Would like to confirm one thing.
When GOA is released then system determines the backend system based on the logical system attached to the purchasing org in the Org structure?
What happens if there is a mismatch between the logical system names of authorized Porg and location, means Porg is given with logical system L1 and restrication for location LOC which is attached to logical system L2.

Hi,
the logical system, company code and the plant are derived from the selection made in the distribution tab. The org model is not an element. The system checks during the release the appropiate assignment. The distribution will fail and you'll get an error in R/3.
Cheers,
Claudia

Similar Messages

Creation of multiple contracts in ERP backend from 1 GOA in SRM

Hello fellow SRM'ers, we are on SRM 5.5 and we have a scenario where we create a GOA in SRM and it get's created as a contract in the ERP backend system. This is working fine. Now our client would like to have multiple contracts created in the backend, one for each company when the GOA is saved. I found OSS note 646903, statement #2 that explains how to code the badi bbp_ctr, but is this all that is required to do this? It seems to me that the code in BBP_CTR will only create 1 contract/idoc. Can anyone tell me how we generate an idoc/contract that we want to create in ERP backend? Or is this how it's done?
Points will be rewarded for usefull answers. I have read most of the posts on this forum and have not found any answers yet.
Thanks,
Marty

Hi,
Please go through the below explanation from SAP documentation which says the no of contracts that would be created in the backend depends on
--If you activate grouping logic for locations in GOA from SPRO under cross aplication settings, items belonging to the same release-authorized purchasing organization, but different locations, can be grouped together into one backend contract. This requires a 1:1:1 relationship between an item, the release-authorized purchasing organization, and the location. This means that for each item, you can only assign one release-authorized purchasing organization, and one location, in order to release the GOA.
If you do not select this indicator to activate the grouping logic for location, a separate backend contract is created for each item belonging to the same release-authorized purchasing organization, but with different locations. Only items referring to the same release-authorized purchasing organization and location can be combined into one backend contract.---
So the bottomline is by default, when we distribute one separate contract is created for each location.
Hope this clarifies.
Regards,
RRK

GOA replication problem- data missing during RFC-Urgent

Hi,
I have an issue with updating GOA from SRM to ECC. Standard GOA do not have any fields to update TAX code and ERS indicator to the back end.
This two fields are added to the structure BBPS_CTR_ITEM through customization.
The GOA is transferred to the backend through the FM META_CTR_TRANSFER which in turn calls the FM B46B_CTR_TRANSFER.
Inside the FM B46B_CTR_TRANSFER the RFC call is made to FM BBPV_CONTRACT_TRANSFER which actually transfers the GOA to the backend. The GOA line item details are passed to this FM through lt_be_items[].
The issue is, i can able to see the TAX code and ERS indicator in the itab lt_be_items in SRM side, but when it goes to the ECC through RFC these two fields become blank,
I checked the structure of the same itab in ECC side the field names and the domains are same.
Thanks in advance,
Aravind.

The issue was due to improper structure mapping between two systems. Now its solved.
Regards,
Aravind.

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
Please refer to few OSS notes.
Note 1033458 - Item level Tolerance values in GOA not transferred to R/3
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

Incase this OSS notes, don't work, then
Please try do this as well. Uncheck the ERS indicator, but then also pass tax codes from from GOA.
Then try out again.
For BADIs and other useful information, refer to these forum linksGOA 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
Incase nothing helps, Please raise a OSS message with SAP as well.
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Multiple contract creation in ECC from a single GOA

Hi Experts,
I am working on a solution regarding to GOA in SRM - Contract in ECC creation and i am wondering about the following scenario:
Create 1 GOA in SRM 5.0 for a central/global purchasing organization and when the appropriate BADI going to transfer it into ECC, it creates contracts for all company codes.
At my current client they use GOA but until now they created 1 GOA for a specific p.org and the BADI transferred (and created) contract in ECC for the specific company code (they donu2019t have kind of central/global purch organization unit in ppoma). In the future they would like to create GOAs which are usable for all companies, but instead of creating (and changing) them manually (N GOA in SRM for N contract in ECC) they want to have an automatism.
Does any of you have any experience on this? That would be really good if you can share with me some high level overview about concept.
Thanks in advance for your help!
Best Regards,
Attila

Hi,
Let me correct if i am right:
- Central Contract -> new concept of SRM 7.0. 1 contract which is visible and usable from ECC and SRM as well. (not available in SRM 5.0 - agree)
- GOA -> it exist in SRM 5.0 for sure! (we are currenlty using it for ECC procurement).
The solution what you are mentioned is good...but as you said only for SRM 70...we are in SRM 5.0 and we need solution for here. Do you have any idea?
Currently i am thinking about a new solution based on "standard" functionalities: if a GOA need to be created for mulitple company, it has to be populated in Header distribution (all company will have the same contract header). It item detail all the required information need to be poupulate in SRM (i.e.: item 1 for p.org1/comp.cod1; item 2 for p.org2/comp.cod2).
When this is done, the BADI need to check the informatoin in SRM GOA and create contract according to that -> in this case 1GOA is created, but the 2 items for totally different p.org/comp.code, the BADI needs to create 2 different contract in ECC (i would like to avoid using reference purchasing organization in ECC!
Thanks in advance!
Best Regards,
Attila

Distributing the GOA to multiple locations in the same backend

Hello Folks,
We are implementing SRM 5.0 (SAPKIBKT10 Support Package level) with Extended Classic Scenario, with only one backend system (R3 V4.6b) integrated with the SRM system.
Queries:
At GOA header - Distribution, Example is shown below....
Backend Purchase Organization 1 - Location A
Backend Purchase Organization 1 - Location B
When we distribute one GOA to the backend with multiple locations for the same Purchase organiation.
In the backend system two idocs are getting generated with the same contract number. While processing the first Idoc the system is creating the contract but while processing the second idoc the system is changing the previously created contract, instead of creating a new contract.
So, in standard does the system creates actually creates two contract numbers for two different locations?
Can somebody throw some light on the logic of the distribution
Regds
Amith
Edited by: Amith Varma on Feb 26, 2008 4:51 AM

Hi Amith,
this is normal behaviour of the system in the case POrgs are set up accross company codes. In the Contract IDoc the Comany Code is derived from the location. When the system finds the same company code, it does not create an additional contract, but just updates the already distributed contract.
Cheers,
Claudia

Master Data coming from 1 backend and GOA distributed to many bakends

Hello,
In our case (using SRM 5.0) one backend system is used to replicate all material master data and GOA will be distributed to multiple backends including the one that is used for master data. As far as i know the logical backend system is determined through materials/material groups while GOA is distributed. In the above case how can we intervene with this logic to be able to distribute the GOA to whatever backend we have, even though if the MD is not coming from them?
Thank you,

Hi,
You can use the BADI BBP_DETERMINE_LOGSYS for this purpose.
The method :CONTRACT_LOGSYS_DETERMINE (Determine Target System of Contract) has been provided for the same purpose.
Sample BADI Implementation at SDN Wiki:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/srm/bbp_determine_logsys-contract_logsys_determine&
Regards
Kathirvel
Edited by: Kathirvel Balakrishnan on Feb 25, 2008 1:00 PM

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.
Please go through the SAP OSS notes below, depending on your System release and support pack details ->
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

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 U (Unknown). Instead I want that account category is blank (my back end contract has to have item category W (material group) and account category "blank", in this way i can create a release order with item category standard and account category "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

Help on GOA screen control at line item for only material

Hello All
scenario:-
1. create a GOA
for a material with has alternative UOM ( CAR - ORDER UNIT ; 1 CAR - 34 ea) . So i created GOA FOR MATERILA LINE ITEM.
FOR CAR .
2. I released GOA and distributed GOA for CAR as Oeder Unit UOM.
3. now my buyer go to GOA and change UOM as EA and price I AND CHANGE THE PRICE IN THE SAME LINE ITEM.
4. No PO released against the COntract in the ECC
5. Unfortunately buyer could change this UOM from CAR to EA. now GOA shows as EA in the line item
6. this info taken to ECC via IDOC but this info never updated in ECC contract.
7. my PO release as CAR forever rather than EA since my ECC contract always shows as CAR
i can lock this item i can create a new line item, no issues.
how buyer knows each time ? if the system allows buyer always try to change rather than entering new item. it is not buyer fault. it is srm fault.
Now ican u suggest some code in ui control badi , if the PO not releases system should not allow to change the UOM in the GOA line item for a material.
PS:- once PO released against contract . srm will not allow to change the UOM . that is fine.
SAP has to correct this problem and release the note.
Muthu

Hi Donald/SCot/ kiran/ jay...
are you having the same problem in SRM 700. front end validation is required here toooooo...
please help me.
I could not accept this functionality ..
why SRM allows to change the UOM by the buyer after release the GOA for the same line item
if srm allows to do edit, SAP SRM and ECC has to update the same UOM in the existing purchasing contract. IDOCs carry all new uom but why not updated in ECC purchasing contract.
decided to write own logic in ui badi to protect this. what to do
Muthu

GOA not picked up as source of supply in R/3 when converting PR to PO

Hi
We are currently using SRM 5.0 extended classic scenario. Here we are using Global outline agreements which will get replicated to backend R/3 system and can be used as source of supply while converting a Purchase requisition to Purchase order. The aim is to use Global outline agreements instead of Info records which will be more flexible.
Once MRP run is done, based on requirement Purchase requisitions are created. Using ME57 we convert the PRs to Purchase orders by assigning source of supply. At this point I would expect the GOA to be picked up,whcih is created against this product. But this is not happening as of now.
Please let me know if there is configuration or prerequisites that need to be done for this.
Also when I am trying to assign the GOA manually in PR, it is throwing the error as 'Item category of contract does not match with Item category in PR', even though both has Item category as 'Standard'.
<< Moderator message - Everyone's problem is important >>
Regards
Edited by: Rob Burbank on Nov 15, 2010 3:15 PM

Hi
GOA is not source of supply Indeed.
whatever you have distributed the GOA as a Purchasing contract is a real source of supply.
if the contract is available in ECC , then it is a valid source of supply for your purchase request.
Can you use the same contract for any other manual / PM /PS purchase request?
Are you assigning same material contract to your purchase request ?
the problem is for only MRP PRs or all PRs.
Muthu

Service GOA -Service line item in R/3 hasn't updated the gross price

Hi all
I am new to SRM system,i had got a query in Service GOA.
Serice GOA created in SRM 5.0 and moved to R/3 4.7
In R/3 ME33K/32K, select the line item and goto
Item-->services,here service masters are maintained.
Here i want to know how the gross price is populated.I am not sure whether will it pick up automatically or it has to be maintained manually in srm,so that it is creating a condition record on moving to R/3
In my case if i maintain 3 services,for one of the services gross price is 0
In the same screen i see conditions link at the bottom,on clicking it takes me to condition record screen which shows condition type PRS.this was maintained for package number and line item,maintained by RFC(automatic)
how this PRS is maintained?
I also see in SPRO the shema is maintained for NB(PR and PO)
Can any one help me out in understanding this functinality.
Thanks in advance
Regards
Ratha

Hi Yann
Thanks for your reply. I am using 4.5b. I am able to create a service PO manually in R/3 with reference to the service PR created by EBP. Also, I think this issue is very close to SAP Note 509059 but it is for EBP Release 3 & 3.5 & I am unable to find the simillar note for EBP2. Please let me know how to proceed further...
Thanks & Regards
Raghu

Extended Classic- GOA to backend-SOS

Hi All,
We are working in extended classic scenario. SRM 5.0 with backend as ECC6.0. We want to distribute GOA as a contract to backend. Also, we want to use backend contract as a source of supply in shopping cart and then in PO. How can it be done? Is that possible to distibute GOA as a local contract in SRM and in backend too? I know in the standard system it can only be distributed to backend but is there any way of doing it? It is quite urgent. Every useful reply will be rewarded with full points.
Regards
Kapil

Hi Kapil,
Just a thought, you can upload the same contract from back end to SRM using a report BBP_CONTRACT_INITIAL_UPLOAD and can be used for procurement in SRM.
Rgds,
Teja

GOA Internal notes and Vendor text not transmitted to R/3

Hi SRM Gurus,
I'm currently working with SRM_SERVER 500(SAPKIBKS09) release, we use ECS (Extended Classic Senario) and we have following problem with global outline agreements (GOA).
In a GOA, the Internal notes and vendor text can be entered on Header and Item level. But the information from a GOA are not transmitted to R/3.
Do you know why !?
Cheers,
Rafi.

Hi,
Pls see if the foll notes help:
609222
646903
BR,
Disha.
Pls reward points for helpful answers.

GOA - Q

Similar Messages

Maybe you are looking for