TRADINGCONTRACT01 Message type

[john_pawski]

I am trying to configure ALE for outbound (from SAP) processing for IDOC basic type TRADINGCONTRACT01. I thought TRADINGCONTRACT was the message type. However, when I go to set up my distribution model I get this message when I go to add message type:

Message type TRADINGCONTRACT belongs to BAPI

TradingContract.Create: Use the BAPI in the model

Any ideas? Perhaps my config is off somewhere else.

[Former Member]

use table EDIMSG to find the message type for the corresponding idoc type

[john_pawski]

Thanks for the note. One more question. It does show up with message type TRADINGCONTRACT as I thought. However, when I use that message type in my distribution model I get an error message stating I should add BAPI and not message type. Any idea?

[john_pawski]

Thanks for your note. I did see it is TRADINGCONTRACT as I thought it was when doing my configuration.

However, when I go to set up my distribution model I get this message when I go to add message type:

Message type TRADINGCONTRACT belongs to BAPI

TradingContract.Create: Use the BAPI in the model

I'm not sure why that in EDIMSG table the basic IDOC type TRADINGCONTRACT01 has message tyep TRADINGCONRACT but I get the above message.

Have you seen this behavoir before?

Thanks

[Former Member]

Message type TRADINGCONTRACT is also used in the BAPI for tradingcontract (see details below) and apparently you can't have both. If you want to use the idoc interface, then i suggest that you create a new message type (e.g. ZTRADINGCNTR) and link it to idoc type TRADINGCONTRACT 01. You can do this via transactions WE81 and WE82.

Bapi definition

Method Create

Business object TradingContract / BUS2124

Short description Create from Template Data

New in Release 46C

Function module BAPI_TRADINGCONTRACT_CREATE

ALE message type TRADINGCONTRACT

[john_pawski]

Do I also need to associate a tcode with my new message type? If so, do you know how to do it? I seem to recall I did that before but can't find the appropriate place.

Thanks

[Former Member]

I think the message type ZTRADINGCONTRACT should have an associated process code with it.

For example; ORDERS has process code ME10 for outbound idocs. What ME10 does is - it selects all the details and fills the idoc.

So may be a similar thing needs to be assocaited.

(Look at t code WE41)

- Ven

[john_pawski]

Ven, so even if I created a custom message type it would have an associated tcode? Is this because TRADINGCONTRACT01 has a related tcode. Is there a way I can see which tcodes are associated with TRADINGCONTRACT01? I'm assuming WB21 and perhaps on in purchasing would be associated, please let me know.

Thanks

[Former Member]

By CODE, I mean the process code that extracts the data and passes on to the IDoc structure and it is not a T Code.

WE41 the transaction code where you can see the Process Code Vs the Message type.

Putting this aside,

I am a bit baffled why the TRADINGCONTRACT message type - even though associated with the Idoc type TRADINGCONTRACT01 - is throwing the error when you try to add it at BD64.

Any body - any ideas?