Error on IDOC status

[Former Member]

Hello,

I made some changes in user exit of a process order. This will update the STO attached to the process order, and will create an IDOC afterwards. However, my IDOC always come in status 64, although if i check the STO, it is updated correctly. I tried using BAPI_TRANSACTION_COMMIT to dispatch the IDOC, but a dump is encountered everytime i put in a commit work.

Is there any way that i can dispatch the IDOC so its status will be 53 instead of 64?

Thanks!

Louisse

[Former Member]

Hello,

I made some changes in user exit of a process order. This will update the STO attached to the process order, and will create an IDOC afterwards. However, my IDOC always come in status 64, although if i check the STO, it is updated correctly. I tried using BAPI_TRANSACTION_COMMIT to dispatch the IDOC, but a dump is encountered everytime i put in a commit work.

Is there any way that i can dispatch the IDOC so its status will be 53 instead of 64?

Thanks!

Louisse

[Former Member]

Hi,

You should not use commit statement in betwwen the transaction ,with your User exit code.

The reason for having status 64 is:

1. The partner profile is not defined properly

Check the partners are avilable EDP13 table or not

2. Receiver is down or not ready to receive IDOCs.

Execute bd87 and reprocess the Idocs.

Reward if find useful

[Former Member]

Hi,

Please check your Partner profile and verify your 'output mode' is set as 'Transfer idoc immediately' instead of 'collect idocs'.

RGds,

Vasanth.

[Former Member]

hi,

You can reprocess the IDOC with tcode BD87 .

Regards,

Sharath

[Former Member]

Hi Louisse,

As the IDOC status 64 comes with processing mode 3 and output mode 2.

What I did is

Checked here.

IDOC_INBOUND_WRITE_TO_DB->EDI_DOCUMENT_STATUS_SET .

and idoc_start_inbound1->IDOC_INBOUND_PROCESS_DATA_GET .

But was in vain as it was to be retriggered.

It means the IDOC is ALE and has to be put into Application layer.

I too have faced similar situation few days back.

have a look at the following

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

You can go to BD87 and select option "Process it" if its in yellow state.

Check if sending back ALE Audit Log IDOC will solve your purpose.

Look at this blog.

/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc

or

64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.

Although the partner profile is defined and the IDoc has been received, the IDoc cannot be transferred to the application.

You trigger transmission of the IDoc using report RBDAPP01. To do this, plan a regular job in background processing for this report.

Check the processing mode for the IDoc in the partner profile:

Processing mode 1: The system transmits the IDoc immediately after receipt in the application.

Output mode 3: The system collects received IDocs.

IDocs are not intended to be transmitted directly to the application.

Status 64 in the IDoc can normally only occur in conjunction with processing mode 3 and output mode 2.

look at oss note 555229.

or

This status is not an error status. you can correct it by running RBDAPP01 program.

if the problem is occuring frequently. Schedule this in background jobs to execute recursively.

or check this link.

https://www.sdn.sap.com/irj/sdn/forums

Cheers

Mohinder Singh Chauhan

[Former Member]

Hi,

In the partner profile WE20 transaction, the triggering mode option is set as Collect IDOC's. In that case you need to create a background job with the step RBDAPP01 program.

If you set the triggering option as Trigger immediately, then as soon as the IDOC is created it will be processed then you get 53 status automatically once the idoc is processed successfully.

Thanks,

Mahesh.

[Former Member]

Hello Everyone,

Thanks to all that replied. I have already checked in partner profile that the partner is already set to "TRansfer Immediately". But still, my IDOC is in status 64. Here's a part pf my code:

CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'

IMPORTING

pe_idoc_number = v_idocnumber

TABLES

t_data_records = i_segm

CHANGING

pc_control_record = i_doc

EXCEPTIONS

idoc_not_saved = 1

OTHERS = 2.

IF sy-subrc <> 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

ENDIF.

x_doc = i_doc.

REFRESH i_doc.

APPEND x_doc TO i_doc.

CALL FUNCTION 'BAPI_IDOC_INPUT1'

EXPORTING

input_method = 'N'

mass_processing = space

TABLES

idoc_contrl = i_doc

idoc_data = i_segm

idoc_status = idoc_status

return_variables = i_retvar

serialization_info = i_serial

EXCEPTIONS

wrong_function_called = 1

OTHERS = 2.

After the call to BAPI_IDOC_INPUT1, i tried using several FM's to kick in the processing of IDOCs, but to no avail. I am getting a dump. Can you please enlighten me more?

Thanks,

Louisse