on 11-20-2008 3:50 PM
Hi,
MBGMCR03 is also not working. Any other idoc to trigger to o/b idoc for both MIGO & MB1B.
Thanks & Regards,
Balaji
See if WMMBID02 suits your requirement.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
yes.
This idoc WMMBID02, i'm using for inbound. The same i tried for outbound also.
In WE20, in outbound parameters, for LS partner, for Message type WMMBXY, i've maintained the receiver port & basic type as WMMBID02.
In BD64, i've created a model view for this message type & distributed the same.
Then i've tried both MIGO & MB1B, this idoc not triggered at all.
Any other settings other than this...
rgds,
balu
hi,
This idoc WMMBID02, i'm using for inbound. The same i tried for outbound also.
In WE20, in outbound parameters, for LS partner, for Message type WMMBXY, i've maintained the receiver port & basic type as WMMBID02.
In BD64, i've created a model view for this message type & distributed the same.
Then i've tried both MIGO & MB1B, this idoc not triggered at all.
Any other settings other than this...
Thanks & Regards,
Balaji
hi,
This idoc WMMBID02, i'm using for inbound. The same i tried for outbound also.
In WE20, in outbound parameters, for LS partner, for Message type WMMBXY, i've maintained the receiver port & basic type as WMMBID02.
In BD64, i've created a model view for this message type & distributed the same.
Then i've tried both MIGO & MB1B, this idoc not triggered at all.
Any other settings other than this...
Thanks & Regards,
Balaji
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.