Data exchange process in IDE

[Former Member]

Dear All,

I am part of a project which implements IDE solution for a utility company in the de-regulated market. We plan to use the Data Exchange Process in IDE , I have gone through few documents on the same but stuck on the following points:

1. How to use the event modules for the IDOCs (for inbound process to identify the basic process and to call the data exchange controller ). Is it to be configured as the inbound function module for the particular IDoc type in partner profile ?

2. Where exactly the Data Exchange Format function module is called (to process the IDocs, ie to update the switch document with the message data)? I searched in the code level but in vain.

It would be of great help if somebody can address this.

Thanks in advance,

Abhilash.T

[Former Member · Accepted solution]

Abhishek,

1. How to use the event modules for the IDOCs (for inbound process to identify the basic process and to call the data exchange controller ). Is it to be configured as the inbound function module for the particular IDoc type in partner profile ?

[SS] - Yes, you need to configure the IDoc types in partner profile. It is the same way you do it for any interface development but depending on the type of communication you would need to configure your processing function module in Datex process. In case of inbound interfaces COMEV Function module gets triggered automatically from IDOC/ALE layer and is attached to the inbound process code.

2. Where exactly the Data Exchange Format function module is called (to process the IDocs, ie to update the switch document with the message data)? I searched in the code level but in vain.

[SS]: ABAP Class CL_ISU_DATEX_PROCESS contains all the methods related to the processing of each datex format. A sub class of CL_ISU_DATEX_PROCESS needs to be created with methods PROCESS_INBOUND and SHOW_REFERENCE(if required) needs to be re defined in order to display the switch document activities and status. You would then configure this class in the SPRO for your datex format.

PROCESS_INBOUND method is used for import process i.e., in inbound processing of IDocs. This method is responsible for setting up the data exchange task reference to Switch document, determining datex format used for communication, and calls specific datex function module configured for basic process. The datex function module(COMPR) is identified based on the basic process, IDoc Type and Message Type.If there occurs any error, the status of the Datex Task would be set to u2018Erroru2019. Usually

In case of inbound processing, the COMPR function module is responsible for applying the business validations to the IDoc data and processes data depending on requirements of the interface. For example, updates SAP tables, Triggers workflow events etc. As a generic rule for Inbound interfaces IDoc status is set in the COMPR Function Module, failing to do so would result the Datex Task to be u2018ERRORu2019 and Switch document must be updated in the COMPR Function Module.

Let me know if this works. BTW is your project within the US or elsewhere?

Thanks,

Sai

[Former Member]

Hi Sai,

Thanks a lot for your input. This project is in the european market(belgium).

warm regards,

Abhi

[Former Member]

Thank you

Regards,

gopi

[Former Member]

Hi Sai,

I have few conceptual clarification.

Could you explain the diff between data exchange process and data exchange task (read that execution of data exchange process creates data exchange task) but could you explain this in bit detail. Is scheduling of data exchange task and scheduling of data exchange process the same?

Thanks in advance,

Abhi

Edited by: ABHILASH THANKAPPAN on Dec 5, 2009 8:14 PM

[Former Member]

A data exchange task is the actual execution of a data exchange definition for a point of delivery for a certain due date. The data exchange task logs the import or export of messages (logging of the executed data exchange processes and monitoring of the planned due dates). You can generate or manually create data exchange tasks based on the data exchange definition that was last created. A data exchange task describes the following:

a.Point of delivery

b.Data Exchange Process

c.Third party service provider - The service provider with whom you want to communicate

d.Own service provider- the service provider managed in your own system that sends/receives the data.

e.Status of data exchange task

Describes the status of the actual execution of the data exchange process. The following statuses exist:

1.OK Ended with OK -- Indicates successful processing. IDocs cannot be exported unless the status is OK

2.ERROR Ended with error(s) -- If a task is being re-imported then the status should be ERROR. If the corrected flag is set then the task must either be ERROR or IN_WORK.

3.CANCELLED Process stopped by application -- The status CANCELLED is only allowed for outbound processes where the Data Exchange task is currently PLANNED or OK and the due date has not been reached.

4.PLANNED Scheduled -- When the task is first created the status is set to PLANNED. This includes when a task is created by copying an existing task. You can only delete data exchange tasks that have the status SCHEDULED.

5.IN_WORK In process

6.OBSOLETE No longer relevant

7.UNKNOWN Processing status unknown note: statuses 5,6 and 7 are for internal use only.

The status of generated or manually created tasks is PLANNED. The status of successfully completed tasks is ended with OK.

f.A due date (date and time)

g.A reference time (optional)

Some data exchange processes require a reference period to be able to send/receive the appropriate data.

[Former Member]

Thanks a lot Sai.

Regards,

Abhilash

[Former Member]

Hi, colleages,

i have problem with inbound process for exchange task "Improfile".

My case is follow: via PI i am translate xml-file to the ERP system with IS-U add-on. I had write FM and this module via BAPI read incoming IDOC and save values at the EDM profile. My ALE-Partner customizing for case "The inbound IDoc is processed immediately". All is work fine....

BUT i want to use data exchange procces according to schedule and now all my scheduled tasks have status "PLANNED" without any modification. And of course, Inbound method at the CL_ISU_DATEX* not working((...

Tell me what i must to do for sheduling import task process?

Best regards,

Igor