Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

ALE/IDOCS - Process code for Inbound message code MATMAS

Former Member
0 Likes
4,228

Hi All,

I am creating IDOCS for message type MATMAS, the Outbound process is sucessfull but the Inbound process (T-code BD11) Process code: AFSA

its giving

Status 51: Application Document not posted.

"IDoc: 0000000000576096 Status: Application document not posted

Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT".

Please lemme know how to resovle it.

Thanks and Regards

Shazia

8 REPLIES 8
Read only

jiteshmehta
Active Contributor
0 Likes
1,928

It is neccesary to remove the faulty entry from the 'Logical Message <-> Inbound process codes' Table (TMSG2). to do so please follow these steps:

1. Go to transaction SM30 (Maintain Table Views)

2. Type VEDI_TMSG2 in Table/view field

3. Press the Maintain button

4. When the 'Determine Work Area:entry' dialog box appear, enter AFSA in the 'Inbound process code' field, and press enter.

5. Select the MATMAS line by pressing on the SELECTION BOX at the begining of line.

6. Delete the line by pressing the Delete button (the button with a red minus) or by pressing Shift-F2.

7. Save the modification (CTRL-S) and press F3 to leave the session.

Please refer the note : 318927

Read only

Former Member
0 Likes
1,928

Hi,

I have the same error. Have done all the steps specified in the Note 318927. But the error still persists. Can anyone suggest a solution for this?

Regards,

Suma

Read only

Former Member
0 Likes
1,928

Hi Shazia,

Use process code MATM

Regards

Arun

Read only

Former Member
0 Likes
1,928

hi,

try changing process code for matmas which is MATM. and check whether both sender nad receiver has same message types with same inbound and outbound parameters.

if its correct then check at receiver side the function module is defined or not using T.code BD 51 and while assigning it to process code to receiver side as WE42.

IF HELPFUL REWARD SOME POINTS.

WITH REGARDS,

SURESH ALURI.

Read only

Former Member
0 Likes
1,928

have you specified port in partner profile of sender and reciever.and also the process code 'MATM' in partner profile.

create partner prfile using we20 tcode.

Read only

Former Member
0 Likes
1,928

Hi,

I had already tried by changing the process code to MATM. But the error still persists. Hence I am now trying to check whether both sender and receiver has same message types with same inbound and outbound parameters. I see that the inbound parameter of the receiver system has 'MATMAS' message type assigned to 'MATM' process code. I am not able to see process code in outbound parameters. I see that the outbound parameter for message types does not show process code. Do I need to define this explicitly somewhere?

BD51 tcode shows that the function module is defined correctly. What do you mean by 'while assigning it to process code to receiver side as WE42’? There is no process code as WE42. I think you are referring to the Tcode WE42 where it shows the details of the inbound process codes. I see that there is a entry for 'MATM' in this.

I am stuck up again... Any solution?

Regards,

Suma

Read only

0 Likes
1,928

I recently resolved a similar issue.

Status 51: Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT".

Just creat an entry for this FM in the we57 for message type MATMAS and the problem will be resolved.

<b>Please reward the helpful entries</b>

Regards,

Raman

Read only

Former Member
0 Likes
1,928

Hi Raman,

Creating an entry in We57 will not help since it now gives the error ' The IDoc interface is not complete for message type MATMAS' . I think this is now not possible since we have deleted entries as specified in note 318927 .

Any more pointers ?

Regards,

Suma