AS2 to IDOC schenario - need to stop posting IDOC for perticular interval

[Harish]

Hi All,

I have AS2 to IDOC schenario and i need to stop the posting of IDOC messages for one time interval in a month.

Can you please suggest the best way to achive this in PI (7.3 SP06 dual stack).

I think of following possibilities

- As2 Comm channel availability at sender side - But the sender will get error if they want to send message between this time.

- Post the message to some FTP location and pick again (comm channel availability) - have multiple schenario and need only for one interval in a month

- BPM - I would like to avoid BPM and holdinig the msg in PI.

Please suggest if this can achive in ECC with simple change.

Regards,

Harish

[ambrish_mishra · Accepted solution]

Hi Harish,

I have not worked on AS2 adapter but are you sure about this-->>- As2 Comm channel availability at sender side - But the sender will get error if they want to send message between this time.

because for any other standard adapter, for eg file... the files will simply not be picked up. Similarly I think the messages should be parked in a buffer space on sender side till the the adapter starts polling again.

If this is not an option and you want to automate this process, IMO, this can be done through BPM only.

Unless someone wants to follow a manual process, switch the partner profile to collect mode, process the messages after the interval and switch the Partner profile back.

Hope it helps!

Ambrish

[Harish · Accepted solution]

Hi Ambrish,

AS2 adapter do not poll but the sender push the message to AS2 like http post.

I would interested if there is any way in ECC without doing manual work.

Regards,

Harish

[former_member185856 · Accepted solution]

Hi Harish,

              Are you using custom IDoc or standard?

Thanks,

Sunil.

[Harish · Accepted solution]

Hi Sunil,

I am using standard IDOC.

Regards,

Harish

[ambrish_mishra · Accepted solution]

Hi Harish,

I guess the monthly time interval you are looking to block the IDocs for, is monthly outage which is planned.Or is it some different scenario like posting period changeover?

Cheers,

Ambrish

[Former Member · Accepted solution]

Hi Harish,

here's different solutions:

1. Have a dummy step "AS2 to temp. file" + "temp. File to Idoc".

Let these temp. files somewhere in a server, and then define a flow "File to idoc" for which you can manage the monthly Availibility-time planning (PI job).

2. have "AS2 to Std Idoc".

but in ECC config (WE20), choose option "Trigger by background progam". So all your inbound idoc will be in status "64" (wait).

Define a SAP job (monthly) on program RBDAPP01 by given your Idoc message/type.

This program is to process idoc which are in status 64 (or 66 if you have serialization).

To have idoc in status "64" during one month, is in my mind bad, especilly if you have idoc monitoring, and also because one month, that's long,some one can by mistake run RBDAPP01 or use BD87... before your monthly date.

3. have "AS2 to specific Idoc".

Define a specific idoc which will not create your stuff in SAP, but which will store the relevant data in a Ztable.

Develop an Abap program (for which you define a monthjly job) which will pick-up this data from these Ztable, process them (either like idoc or by bapi), do a report, clean processed data in Ztable (or flagged them to 'processed').

4. Ask to your souce system (negociation) to only send data to PI.... monthly!

That is the TECHNICAL approach... after that depends also on your Business needs: log + reprocess (idoc) + etc...

Ha, I forgot one point, if it's really necessary to say it : do NOT use a BPM.... opened during one month to collect data.

regards

Mickael

[Harish · Accepted solution]

Hi Ambrish,

It is for some special period in a month and not related to Outage.

Regards,

Harish

[ambrish_mishra · Accepted solution]

Then I would suggest to make a manual process.. collect IDocs for that period, reprocess them later and switch to automatic later..

BPM or non-BPM, it is going to be un-necassarily complex.

Since you mentioned it is a push from Sender side, why not try and negotiate with Sender party not to send messages during that period. that would be the best way to achieve this.

Cheers

Ambrish

[Harish · Accepted solution]

Hi Ambrish,

Thanks for your reply. I will check the option of collect IDOC via automatic process in ECC. I would like to exclude the option of negotiate with sender (as customer is sending the message) and try to handle this within the landscape.

Regards,

Harish

[former_member184720]

Not sure if it possible in your case but may be lock the RFC user for that duration and later process them from PI?

[former_member192892]

Hi Harish,

I would suggest not to use BPM for this sort of requirements. Instead keep your idoc in collect mode and schedule the job in ECC for posting the Idocs. The schedule can take care of any requirements on stopping.

This way, all systems will be in green and you will have control.

Regards

Varun

[Harish]

Hi Varun,

ECC is using the standard jobs to process the IDOC. Can we do with simple user exit or we need to create custom job for the requirment.

Regards,

Harish

[Former Member]

Hi Harish,

ECC uses standard job when patner profile is made to "process immediately"

We need to change the option to "Collect Idocs", Schedule (SM36) a custom job to process the Idocs except for specific period of month or you can improve performance to process Idocs in batch mode every hour.

Regards,

Pranav