Skip to Content
0

Mirror transaction not generated even though partner is authorised in TBI6

Sep 07, 2017 at 10:12 AM

209

avatar image
Former Member

Hi All,

while trying to book FTR_CREATE for company code A and partner B123, the mirror deal in company code B and partner A123 is supposed to be generated.

But FTR_CREATE gives a WARNING message(error msg. no T0739) saying that the partner (B123) is not authorized for selected transaction type - 60I and gets saved without a mirror deal.

(note that this partner in error is always the mirror partner, if I try to book a deal in company code B and partner A123, it says A123 is not authorized and vice versa)

But TBI6 has been set and authorized for this partner and company code combination.

All mirror settings and configuration including number ranges are fine.

Strangely, we are able to book the deal for both the company codes and partners in FTR_CREATE separately (but no mirror deal generated)

And also, 55I generates a mirror deal for this partner. Issue seems to be only with 60I.

Don't know what I am missing and Unable to find what the issue is? Can anyone please help here.

Thanks,

Hari Dharen

10 |10000 characters needed characters left characters exceeded
Former Member

Any help? :(

Would highly appreciate your time and inputs!

0
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Jain varghese Sep 10, 2017 at 04:48 AM
0

Hi,

Not sure much about your issue but will be helpful to analyze if you share screenshot of the error.

Anyways, Could you please check the configuration of Table VTBMDMAP also check whether user authorization in below path and RFTB_MIRROR_CUSTOMIZING_CHECK for configuation.


mirror.png (10.3 kB)
Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Sep 11, 2017 at 09:40 AM
0

Thanks Jain Varghese. Highly appreciate your time and inputs.

Checked the user data, the values are maintained correctly.

RFTB_MIRROR_CUSTOMIZING_CHECK also does not give any error (except for

MIRROR: Recursive entry in company code).

Strangely, this mirror does work for some company codes but not for the newly created ones. It also works for 55I but not for 60I

I cross checked mirror settings and other configurations, there doesn't seem to be any difference.

There is a warning message T0739 when trying to post 60I deals with few company code and partner.

T0739 as you know is the error message which we get when TBI6 is missing authorization and usually comes as a stop error. But in our case, this comes as a warning with no mirror deal generated.

Also this works separately, when trying to book for the company code and partner without any mirror deal. So if TBI6 was really the issue, it wouldn't have allowed to book separately.

So am I missing something or a config especially for 60I for mirror deals (apart from those 5 mirror transaction steps)

Share
10 |10000 characters needed characters left characters exceeded
Jain varghese Sep 11, 2017 at 10:55 AM
0

Hi,

I wish i can throw more light but without seeing you configuration its difficult and you had valid point in error is coming due to authorization it should behave uni formally in across product.

Regards,

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member
Sep 12, 2017 at 12:04 AM
0

HI Hari,

Check if no. ranges are maintained in all the relevant company codes.

Regards,

Nikhil

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Nikhil,

Thanks. Yes, that's done too.

Hari Dharen

0
avatar image
Former Member Oct 17, 2017 at 08:10 AM
0

Issue resolved. Closing the thread. Updating the findings for the benefit of the community.

The issue was with mirroring which also had 60A setup. So the system, is trying to find if a partner is authorized for the product type available in mirroring transactions (this is irrespective of what we are trying to post in FTR_CREATE). Hence the solution is to remove the unneeded product types or provide authorization for all the product types mentioned in the mirror transactions. By doing this, our problem was resolved.

Share
10 |10000 characters needed characters left characters exceeded