topic Re: ALEs/IDOCs typical problem in Application Development and Automation Discussions

ALEs/IDOCs typical problem

Former Member — Tue, 20 Dec 2005 05:24:20 GMT

Hello Friends,

The business scenario is like that when we create purchase orders in one server it should create sales order in the another server automatically.

In the outbound it is moving without any error, and in the inbound side it is getting 51-status code after I am trying to post the idoc with respective process code.In the error it is shows the message like “The material number for item 000010 could not be identified”....

All inputs is highly appreciated and I promise to return and reward the answers which helps me indeed here

Thanks in advance

Ramu.

Re: ALEs/IDOCs typical problem

Former Member — Tue, 20 Dec 2005 05:29:12 GMT

what is the message type you are using..

check for item

is there any material(e1edp19 will have material)

i think that is mandatory field .if you give message type i will tell you ...

vijay

Re: ALEs/IDOCs typical problem

Former Member — Tue, 20 Dec 2005 05:31:50 GMT

Hi,

Welcome to SDN!!!!!!!!!!!

Can you check the Material no for Item 000010.

What I meant is check the senario whether the Material no should have 00002130 or only 2130.

If this is the case you need to use FM before passing the data ...

FM 'CONVERSION_EXIT_ALPHA_INPUT' this is used to place the zeros in front.

FM 'CONVERSION_EXIT_ALPHA_OUTPUT' this is used to delete zeros.

I hope this helps you...

Thanks.

If this helps you reward with points.

Re: ALEs/IDOCs typical problem

Former Member — Tue, 20 Dec 2005 05:32:00 GMT

Hi please check the server in which you are creating the sales order that whether this material exists. Go to mm03 transaction and pass this material number in inbound side. If the material is not available, either you need to create a material with the same number in this system, or while creating the IDOC you need to change the material to a mapping material number in the inbound system.

Re: ALEs/IDOCs typical problem

Former Member — Tue, 20 Dec 2005 07:42:58 GMT

Hi deepak,

Thanks for ur reply ...my material number is 1111-1111. i treied with function module 'CONVERSION_EXIT_ALPHA_INPUT" but im getting same material number ....plz tell me the steps how to do conversion routines for material or item in the inbound side. its really help ful 2 me.

Thanks in Advance.

Ramu.

Re: ALEs/IDOCs typical problem

Former Member — Tue, 20 Dec 2005 07:47:29 GMT

Hi Kavitha,

Thanks for ur ans ...material is there in both the servers .Plz tell me how to do the mapping (while creating the IDOC you need to change the material to a mapping material number in the inbound system)

Thanks in Advance,

Ramu achanta.

Re: ALEs/IDOCs typical problem

Former Member — Tue, 20 Dec 2005 07:53:50 GMT

Hi Vijay ,

Thanks for ur reply,message type is zorders05

material is there in e1edp19 001 ...field name is idtnr

im waiting for ur response.

Thanks in advance,

Ramu.

mumbai

Re: ALEs/IDOCs typical problem

Former Member — Tue, 20 Dec 2005 08:44:44 GMT

Hi Ramu,

In order to do these conversion using sap standard tools, you have to use the rebate agreements on target system (VD51).

Here you relationship for each customer, the material number in the target system (SD) with the material number from the source system (MM). This is the classical schema and I'm not sure if it fits with your needs.

Hope it helps you,

David R.

Re: ALEs/IDOCs typical problem

Former Member — Wed, 21 Dec 2005 09:17:40 GMT

Hi David,

Thanks a lot for ur gr8 ans, i solved my issue

with ur help by maintaining material info record for coustomer.actually Functional guy is not available here

so 2day i did the settings in VD51.

Please be in touch . If possible plz give ur mail id.

Thanks&Regards.

Ramu.

Re: ALEs/IDOCs typical problem

Former Member — Mon, 02 Jan 2006 08:56:51 GMT

Nice to hear it helped you.

Sorry for late answer, but I was in Xmas holiday

Due to my spam policy I can't give you my email in a public forum, but I have add this question as a watch point in SDN to follow you.

Drop any questions here.

regards,

David R.