GOA distribution to backend problems

Hi everyone, we are replicating GOA's in SRM 5.5 to contracts in ECC backend. This is working well, we are even able to distribute to multiple contracts in the backend, depending on what we enter in the distribution screen of the GOA. The problem we are encountering is random. Sometimes the contract number in the backend will come back to the GOA properly as the BE-Object id and sometimes it won't. If 1 GOA seems to work, and I copy it and release the copied GOA to the backend, that one will not bring back the follow-on document number as view in bbp_pd. The status indicates distribution incorrect, but that is the only message we can find anywhere in the systems. This is very frustrating considering 1 GOA will work but an exact copy of the one that works, doesn't work.
Helpful answers will be rewarded with points.
Thanks,
Marty

Hi Bejoy,
I had the same issue and it can be solved like this:
The Company Code is not part of the Interface for the Contract Idoc in R/3.
Use R/3 Badi BBP_CTR to derive the company code from the plant used on item
level and fill the segment for the company code on header level of the Idoc.
As there also can be the case, that there are several company codes
possible, you need to define a logic, which company code should be entered
into the Idoc Segment.
Thanks,
Claudia

Similar Messages

GOA distribution to backend- Multiple companies

Hello,
I am distributing a GOA from SRM to ECC. There is one purchasing organization and several company codes in the backend. There is no assignment of company code to Purchasing Organization. In ECC when the IDOC is processed, the pop up to enter the company code appears and the IDOC processing fails. I can clearly see on the IDOC log that the failure is due to the pop up as the error in WE02 refers to the screen number of the pop-up. So I assigned a purchasing organization to a company code in ECC and the problem is resolved temporarily. My question is what is the best way to resolve this issue permanently?
Ideally we would not like to create multiple contracts in ECC and create a global contract in ECC. If this is not possible in ECC, what is the best way to split the GOA into one contact each for each company code ( I am aware of the BAdI for this)? What about issues like the material not extended to the plant etc in the backend?
Any insights will be very helpful.
Regards,
Bejoy Narayana

Hi Bejoy,
I had the same issue and it can be solved like this:
The Company Code is not part of the Interface for the Contract Idoc in R/3.
Use R/3 Badi BBP_CTR to derive the company code from the plant used on item
level and fill the segment for the company code on header level of the Idoc.
As there also can be the case, that there are several company codes
possible, you need to define a logic, which company code should be entered
into the Idoc Segment.
Thanks,
Claudia

GOA Distribution to backend - Multiple Contracts

Hi,
We are trying to create multiple local contracts (one for different company code) in ECC for a given GOA. I reviewed note 646903 and the sample code given for item 2 there. It appears the code there only creates one local contract for a given GOA. How can I create multiple local contracts.
Thanks,
SG

Resolved. Had to put in mapping code in BBP_CTR from location to company.

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

SRM 7.0 Central Contract- Distribution to backend failure

Hello experts,
We are implementing SRM 7.0 Central contracts scenario with PI.
The Contracts get created and Released but the problem is that the Distribution to backend fails. The Status in BBP_PD shows 'Distribution Incorrect' and the RZ20 gives an error 'Backend data cannot be read'.
We checked all the configuration settings (including the PI settings) and everything seems to be in order.
Would appreciate if someone could throw some light on the potential cause of the problem.
Thanks
Raman.

Message must have created . check all SRM outbound transactions .but PI could not catch them.
Note 1284369 - User attributes check in Contract distribution via services - what is your SP level in SRM 700.
The sap stratergy in earlier version
table in ECC BBPD_CTR_IDOCREF with message 019-This will result in setting the GOA status to 'Distribution Incorrect'.
so SAP might have tried the same way in CCTR as well, Once message are created and this message number like IDOC number updated in ECC table for the further refrence .so like wise SRM trying to communicate the same to ECC but it would have failed.
do you remeber when GOA idoc fails this table we will have reference number and reprocessing idoc.
like any reference of your input must register in one ECC table but there may have this table or some other reference table.
/SAPSRM/CL_CH_SOA_MAP_CTR_OUT CLASS DO SOME trick and see what is happening here
Muthu

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

GOA distributed to backend as Scheduling Agreement

Hi,
SRM 5.0 - ECS
We have a requirement to transfer the GOA created in SRM to backend as scheduling agreement.
GOA replication to backend as a contract is working fine, but i could not crack on the SA.
Any tips would be useful.
Regards
Sudhakar

Hi Sudhakar,
like said, you need to program within BADI to differentiate which document is created. By standard the system takes the first doc type and distributes it to the backend depending on the doc type. To make it more clear: the functionality to either create a Contract or a Scheduling Agreement does not work without programming. By customizing, only one document can be created.
Typcially there are specific doc types in Backend for Contracts and Scheduling Agreements by standard. So it makes sense to follow the standard and create different doc types for Contracts and Scheduling Agreements and use these doc types within the BADI to tell which document is supposed to be created.
Cheers,
Claudia

BI PRD sys got shutdown due to some backend problem so will PC runs automu00E1

Hello All,
BI PRD system got shutdown due to some backend problem, so when they restart the system will pc runs automatically?
then if its yes will it affect tommrrow process chain?
Regards,
Ranga

Hi,
By tomorrow morning if your system is Ok then the Jobs will start automatically in system, but you need to monitor the system bcoz after shutdown all jobs are starting, so monitor it, it won't effect any loads.
Thanks
Reddy

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

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

GOA distribution problem with message type COND_A

Hi All,
we are facing problem to transfer the GOA from SRM to R/3.
When we check with RZ20 we can trace error saying Processing of IDCs of types COND_A02 in the system XXXXXX canceled.
Is there any idea regarding this?
Regards,
Nav

Hi Nav,
you need to implement Badi BBP_CTR to map the conditions used in SRM with the ones in R/3. Within the Badi there is an example for mapping. Also there are some threads here explaining the mapping. Have alook at Note 646903 - Global outline agreement: Tips and tricks explaining in detail how to implement these BADI's.
Cheers,
Claudia

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 ?
Meanwhile, try the pointers ->
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

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

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 distribution to backend problems

Similar Messages

Maybe you are looking for