GOA 'IN DISTRIBUTION'

Hi experts
After I have done all configurations for GOA distribution with GOAs succesfully tranfered to R/3 as Scheduling agreemnt my GOA still in status 'IN DISTRIBUTION' besides I heve creted schedule lines for the contracts in R/3 and nothing updated in SRM GOA.
Some help will be welcome.
Thanks
Nilson

Hi Nilson,
If the document number is there in bbp_document_tab then clean_reqreq_up has not updated the status for this GOA. You can possibly try to run the report again by directly giving the document number (you will find the key in the table).
The IDOC BLAORD needs to be checked in backend not BLAREL.
Regards
Saravanan.
Please award if useful

Similar Messages

GOA item distribution

Dear all,
I am trying to use a BADI and check GOA item distribution data. In particular I need to get plant code.
In BBP_PD I can see that plant GUID is in table BBP_PDDEP but I can not find a connection between item GUID and this table. Can somebody advise how can I access this table?
kind regards,
Robert

I feel that you can read all GOA details using FM <BBP_PROCDOC_GETDETAIL>.
Just populate I_OBJECT_TYPE = BUS2000113
and I_Read_flags as per need.
There is no point in exploring links when you have SAP given FM.
You can also see where used details for above FM to use it in proper way.
Regards,Nishant

Newby question: GOA backend distribution

Hi,
I was wondering if someone can help me understand the GOA to backend OA distribution process.
After reading the config guide for SRM4.0, I cannot understand how the IDOC BLAR02 is triggered?
I know that if I follow the config guide, as soon as I release the GOA, the IDOC will be automagically generated, but how? Is there a function to that gets triggered before the IDOC gets sent? Where can I find this?
Thanks in advance.
Michael.

The GOA is transferred to backend through a BAPI. The BAPI then creates the IDOCs BLAORD and CONDA which are then processed to created a contract/scheduling agreement in backend.
Re: SRM GOA [BLAREL ]
Please debug IDOC_INPUT_BLAORD
GOA BLAORD Error

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

Incorrect distribution -Error while distributing GOA to R3 Backend system

Hi,
We have installed SRM server 5.5 and implementing contract Management
scenario with backend system R/3 4.6B.
In this scenario we are creating a Global Outline Agreement in SRM
system and distributing it to the back-end ERP system.
In SRM5.0 GOA (Trans.type GCTR) that are distributed at Header level
are failing to distribute to R/3 system v4.6b
We are getting this error message in SRM transaction SLG1: -
The error ocurred by processing event RELEASED_NEWLY with GUID
DCA7101B320134F1949F000347DE470F and object_id= 5600000054 " RECEPIENT
NOT FOUND"
The purchasing org , the plant has been mapped .Also vendor & material is maintained for the company & Plant .
The condition types are mapped in SRM
Pls suggest.
Regards,
Avinash

Hi Avinash,
In reference to your query about GOA, the distribution error might be beacause of the issues in BADI implementation.
By using the BADI you can define which document to be created in the backend.
BBP_CTR_BE_CREATE BADI can be used in SRM and BBP_CTR BADI can be used in back end R/3 for this purpose.
Check for the transaction types (GCTR) and the number ranges for the transaction types.
The GOA will either create a contract or a Scheduling agreement in R/3 back end after distribution.
Also refer the below SDN thread in this regard :
Re: Scheduling Agreement from GOA
Any further clarifications are welcome.
Award points for suitable answers.
Rgds,
Teja

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

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

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

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

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.
Please go through the links below for more details ->
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

GOA Distribution error

Hi,
There is a user who has created a Global Outline Agreement in SRM and has distributed the contract in SRM, however, the GOA is not transferred to the backend. When i check the GOA in SRM, it shows the status as "Distribution Incorrect".
What could the reason be?
P.S. : I checked out the PPOMA and the user who has created the GOA is not assigned to the plant (in Extended Attributes) for which the contract has been created.

Hi Amit
In R/3, ME33 Txn, check today's contracts. May be contract is not created with the same number in R/3. You can also check in EKKO-table (normally, logical system is also stored in the table).
best regards
Ramki

GOA 'IN DISTRIBUTION'

Similar Messages

Maybe you are looking for