Inbound idoc error handling

[Former Member]

Hi,

I have to execute the below scrnario.

I want to have inbound idoc error handling task to be triggered for particular country.

If I activate the triggering event on task TS00008068, does it get triggered for all inbound idocs?

How can I make this task to work only for a particular country?

Based on which criteria I can identify the interfaces for that particular country?

KR,

Vithalprasad

[Former Member]

Hi,

I have to execute the below scrnario.

I want to have inbound idoc error handling task to be triggered for particular country.

If I activate the triggering event on task TS00008068, does it get triggered for all inbound idocs?

How can I make this task to work only for a particular country?

Based on which criteria I can identify the interfaces for that particular country?

KR,

Vithalprasad

[Former Member]

Vittal,

If I activate the triggering event on task TS00008068, does it get triggered for all inbound idocs?

--Yes

How can I make this task to work only for a particular country?

-- There is no country specific criteria that you can use. TS00008068 is a standard task. Its a workflow task and not depended on any criteria.

Based on which criteria I can identify the interfaces for that particular country?

-- One way to control the flow is by using work center. Create object ids and assign appropriate users. Come back to partner profiles (specific country you're looking for) and give the Agent name in Post Processing: Permitted Agent area. If you give it in default area for partner# then every inbound idoc will be routed to that object id. However if you want specific routing, you can do it within the inbound parameters. This is a generic task.

There are many standard tasks available for each individual message types. You might want to look at them. It is easier to control and route according to your desired needs this way rather than working out with a generic standard task for all inbound IDOC errors.

[Former Member]

Hi Gautam,

Thanks for your reply. It is indeed very helpful reply. (Point rewarded ).

If we want to create custom tasks for custome messages types ( Z message types ) How can we trigger that task when idoc for that message type goes in error??

Kr,

Vittal

[Former Member]

Vittal,

1. If your requirement is for a SAP Standard Basic Message type and a Z extension: Then you simply have to find out the 'Standard Task' associated with basic type. You shouldn't worry about extensions. The standard task will be triggered at input error.

2. If your requirement is for a Z basic type i.e. you have created a customer IDOC for a custom processing: There are many dependencies on how you can achieve this. Firstly, you need to know how you're are processing this Z_IDOC. Are you using a standard FM or custom workflow or custom FM? There should be some triggering event within the processing of this Z_IDOC which will raise a certain flag when the error you want to capture happens (or when there is a generic error). You can configure this event in binding objects to trigger a workflow task. If you take a look at any standard tasks, you'll get an idea how the triggering event happens.

Once the workflow task (you can use custom task or use a standard task i.e. by triggering a standard event within the IDOC processing program) is triggered, you can either send it to SAP inbox, e-mail, trigger another processing etc. This is altogether another story.

So bottomline: For custom IDOC processing, you need to trigger an event when error happens. This can be a custom event or a standard event. This event should be linked to a task (custom/standard - check in SWETYPV). Bind all of these in PFTC. Once the task is triggered, you can do whatever you want to do with it.

[Former Member]

hi Gautam,

Thanks for the reply.Point rewarded.