Error F5 080 While doing MIGO

[vinod_naik2]

Hi Gurus,

We are receiving error as F5 080 "Consolidated companies & and & are different".  The error is coming while doing MIGO transaction.

The error is coming when there is difference in company code entered in "trading partner" for the main vendor and what used in vendor master used in the purchase order line item.

If we match the trading partner entry in vendor master data for these two vendors then we do not get the error.

In OBA7 for document type WE (Goods receipt) inter-company posting tick is not activated. If we activate the same the issue will go off. But we are checking why the issue started coming suddenly. There are no recent developments related to this.

We have checked SAP notes 1588233, 1511270 and also various posts on the forum. But all talks about making changes in OBA7 for the "inter-company postings" tick.

But we were investigating about is there any other setting or program which might have affected and due to which this particular error started popping out.

The transaction we are using is actually not the inter-company transaction. We are having one company code in trading partner for main vendor in PO. For another vendor which we add in the item condition for one of the freight condition type, there is no trading partner company code is added.

If we add same company code in trading partner for both vendor master then the issue doesn't come. But this can not be done each and every time. And business needs to know why the issue started coming suddenly. We had some SAP system upgrades recently, but we are not able to  figure out which particular update has affected this functionality.

It will be great help  for us you can help in knowing what are other settings in addition to OBA7 settings for this particular error.

Warm regards,

Vinod Naik

[kamalkumar_biswas2 · Accepted solution]

Vinod

  This is basically doc level settings and may differ doc to doc type. In your case I think it may work either option (1) tick only inter com postng keep blank in trading postng  or (2) keep both unticked

In option (1) It will trigger from master data not allow manual entry

              (2) will allow manual entry by choosing Extra menu bottom >

[vinod_naik2 · Accepted solution]

Hi Kamal,

Yes the issue can be resolved by the config change. But we are analyzing how cum suddenly the error started. Till now with all exsiting settings and master data the system was working very fine.  So we are trying to find out what exactly happened during upgrade and system started behaving like this.

regards,

Vinod

[kamalkumar_biswas2 · Accepted solution]

What are the areas you got upgrading?  have you FM area upgradation?

[vinod_naik2 · Accepted solution]

Hi Kamal,

The upgrades were related to some patches which basis team did.

Regards,

Vinod

[kamalkumar_biswas2 · Accepted solution]

Then only way to find out the patches basis team done where they may have unknowingly changes some basic prog files. BASIS & ABAP together debugging the process and can identify the issues where changes have occurred. Otherwise how from functional point it will be detected?

or raise a OSS to SAP

[vinod_naik2 · Accepted solution]

Hi All,

I have raised message to SAP for this issue. Reply from them is awaited. Will update the same once I get solution for this issue.

regards,

Vinod

[Former Member · Accepted solution]

Hi Vinod,

Did you receive any feedback from SAP? We are experiencing the same issue after upgrade to ECC 6.0 EHP 7.

Thanks,

Divina Dela Cruz

[vinod_naik2 · Accepted solution]

Hi Divina,

Yes, we have received reply from SAP yesterday. The changes are required to be carried out in OBA7. We added intercompany posting tick for document type WE. This has resolved the issue.

regards,

Vinod Naik

[Former Member]

Hi Vinod ;

You can look the link below ;

Regards.

Özgün.

[Former Member]

Hi Vinod,

I would request you to check the different partners involved in the PO.

We had similar error and when checked we found that the Vendor, Goods Supplier was different to the Invoicing party.

Some times even if there are some additional condition for expenses as expense then the partner would be different.

Check the Vendor Master data for all the Partners whether you have maintained the Trading Partner details in the same.

Thanks,

Vishal

[vinod_naik2]

Hi Vishal,

In vendor master the trading partner details are different for these two vendors. But those were different right from beginning.  The error started coming recetly.

Now it seems we need to raise ticket for SAP.

regards,

Vinod

[Former Member]

Hi Vinod,

Due to the different trading partner the error is stated.

Do check previous document either the trading partner were same or different document type was used which had the correct setup for inter-company company transaction.

Thanks,

Vishal

[former_member190537]

Hi,

Check your document-type with transaction code OBA7

and check field XGSUB(cross-company posting) = X

Mahesh Naik

[Prasoon]

Hi,

   Please check the KBA: 1802488 - Error 'F5 080' is raised when trying to post a goods receipt in MIGO which explains the reason and the solution for the issue.

Regards,

AKPT

[vinod_naik2]

Hi AKPT,

Thanks for the reply. But in this particular case the transaction is not inter-company. Even though its not inter company we are getting this particular error. And the issue started recently. Previously with same settings it was working fine.

We have not changed OBA7 settings for document type WE. If we add inter-company tick then the issue will get resolved but we are worried to activate it as we do not use inter-company scenarios here.

regards,

Vinod Naik

[Prasoon]

Hi,

   Seems the issue came after system upgrade. In this case, I would suggest to raise an OSS ticket to SAP.

Regards,

AKPT