Idocs remain in status 64

[Former Member]

I am experiencing a problem when attempting to process inbound EDI documents. IDocs imported remain in status 64 and are not transferred to the application even though immediate processing was selected in the partner profile(WE20). Ideally I would like to avoid processing inbound idocs in background processing. Can anyone offer a solution? Thank you

[christian_wohlfahrt · Accepted solution]

Hi Brendyl!

Do you use (accidently) a second profile (which is not marked 'immediate'? Check in IDOC control record, partner tab, which partner profile is used.

Regards,

Christian

[Former Member · Accepted solution]

G'day Christian!

I've have the same problem. Then I changed the settings to "immediate". Now the idoc is processed, but the status remains in status 64.

Message "No status record was passed to ALE by the application".

I use a Z-function module. Do you have any info about what is needed in order to feed ALE with status information.

When checking a successful (53) idoc I can't see that the internal tables for statusmessage is filled if there is a successful call...

Exporting paramterer Call_transaction_done = 'X'.

Any suggestions is welcomed..

Best reg

Henrik

[christian_wohlfahrt · Accepted solution]

Hi Henrik!

You have to set the status 53 in the end of your (successfull) booking.

I had a look at FM 'BAPI_IDOC_INPUT1' to get an exsample and found following in where-used-list:

  call function 'BAPI_IDOC_INPUT1'
       exporting
            input_method          = input_method
            mass_processing       = mass_processing
       importing
            workflow_result       = workflow_result
            application_variable  = application_variable
            in_update_task        = in_update_task
            call_transaction_done = call_transaction_done
       tables
            idoc_contrl           = idoc_contrl
            idoc_data             = idoc_data
            idoc_status           = idoc_status
            return_variables      = return_variables
            serialization_info    = serialization_info
       exceptions
            wrong_function_called = 1.

  if sy-subrc = 0.
    loop at idoc_status  where status = '53'.
      object_key = idoc_status-docnum.
      call function 'SWE_EVENT_CREATE'
           exporting
                objtype         = 'IDOCARTMAS'
                objkey          = object_key
                event           = 'INPUTFINISHED'
           tables
                event_container = event_container
           exceptions
                others          = 01.
    endloop.
  endif.

Status 53 is surely part of table idoc_status, because it's not set in FM 'BAPI_IDOC_INPUT1' it will come from the called function module.

E.g. in IDOC_INPUT_CONDA2 you can find the filling of the status table.

Regards,

Christian

[Former Member · Accepted solution]

Greetings all,

We have finally fixed this on our end and it turned out to be none of the above. After checking and double checking all the partner profiles, programs, function modules, etc. it turned out that our problem was that the user WF-Batch which processes our inbound documents was locked out and the password needed to be reset. There were also some authorization issues there that needed to be corrected. I hope this helps!