IDOC status 62

[narayani_krishnamoorthy]

I have created Inbound IDOC with LSMW. When I process the IDOC the status is 62. The IDOC is in background. Now how do I know when the record has been created and how?/

[Former Member]

hi,

if the status is 53 the idoc created application document successfully.

[narayani_krishnamoorthy]

How do i find what is the error ?? Is there any specific way by which i need to create the file

[Former Member]

If you have a status of 62 that means that the IDoc is created and ready to be transferred to the application. Creating an IDoc in itself is not the end of the process. You have to pass it on to the application. Let us say you are creating a sales order using EDI. First you will create the IDoc. It will be in status 62 at this stage. Once you process the IDoc, then it will be passed to the sales order application which will create the actual sales order.

Run the program RBDAPP01 with your IDoc number and it should create whatever it is supposed to create.

Srinivas

[Former Member]

Hi

To directly past the idoc without running RBDAAP01 you may the change the partner profile in WE20 for the message type to Immediate Processing ( Instead of Collect IDOCS).

IDOC status is 62 as the partner profile may have the option of collect IDOCS.

Cheers

[narayani_krishnamoorthy]

When I run the RBDAAP01 program and give the IDOC number it gives me a message "No data selected". What could the problem be??

[Former Member]

By default this program will look for the IDocs created on the current date. Change the from date to an earlier date so as to include your IDOC.

[narayani_krishnamoorthy]

I have not given any date range at all. But when I see in We02 I am able to see the IDOC with the same status

[Former Member]

If you don't give the date range, the default is today's date. So change it to say 20040101 to 20050914 and enter your IDOC number.

[Former Member]

Hi Narayani,

Have you configured the partner profile correctly ? Try creating a copy of your IDOC using Txn. WE19 and Choose option "Standard Inbound" if everything is fine then you will see a green traffic light. Also check if ALE event linkage is activated by running program RSEINBEV.

Cheers,

Sanjeev

[Former Member]

Sanjeev is right, I overlooked that vital detail. If you have the status 62, your IDOC is passed to the application, but it should end in a status 53(Application Document Posted) or a status of 51(Error: Application Document not Posted).

Now when you are displaying the IDOC, on the left hand side panel, you should see "Status Records". When you open that section, is 62 your top-most status record?

Srinivas

[narayani_krishnamoorthy]

I tried and the error is " IDoc 0000000000003017 was saved but cannot or should not be processed". Same status 62. Is a special way of creating a file for IDOC's

[Former Member]

No. LSMW mapping should take care of your IDOC creation. Remember, Idoc is created, it is just not doing the last step of posting it to the application. Something is missing in the data.

What LSMW object are you using? What should it create?

Srinivas

[Former Member]

Hi,

I think the problem is that the function module that process the IDoc, is not updating the status. Is it a standard IDoc ??? standard FM ???

Regards

PabloX.

[Former Member]

Hi

RBDAPP01 will process idocs in status 64 ( Ready to be passed to application ). 62 means some error.

Check OSS 92252. you may get a solution here.

Cheers

[Former Member]

Hi

Try using BD87 to process the IDOC.

Cheers

[narayani_krishnamoorthy]

I am using IDOC as the object. I have an tab delimited file. I have to upload this txt file into CRM and create an Ibase / component.

[narayani_krishnamoorthy]

I tried to key in some more things that may be necessary for the IDOC. So the status now I got was 64 . But when I processed them the status changed to 62. WHy??

[Former Member]

I cannot help you much in that area(CRM). In R/3, I see that this message EA-406(IDoc & was saved but cannot or should not be processed) is raised in the program MSED7F05 right after the line PERFORM idoc_build_and_store. If this is the same in CRM, put a break-point here and see what it is doing. It is saving the IDOC, but for some reason did not think that it the data is relevant for creation.

Do you have any workflow approvals etc associated with this? Can you create one manually in the system? Do you have the sufficient authorization to create?

Srinivas

[Former Member]

I don't think your partner profile is configured to match the control record. Easiest way to identify this is using the steps I mentioned in my previous message. Have you tried WE19 ?

Cheers,

Sanjeev

[narayani_krishnamoorthy]

I solved the problem. The process code should be APLI and not ED00.

[Former Member]

Please close the post.

Thanks,

Srinivas