How to trigger SYSTAT01 IDOC

[buddhika_krishantha]

Hi experts,

I want to send systat01 IDoc, when I receive a IDoc from external system.

Plese let me know the way to do it.

Thankyou.

[Former Member]

Hi Buddhika,

      Please follow the instructions in following links.

      Inbound and Outbound Idoc Configuration Steps - Contributor Corner - SCN Wiki

      http://scn.sap.com/docs/DOC-34785

[buddhika_krishantha]

Hi Prakash,

I did those. I want to know how to configure SYSTAT01 Idoc to send status.

Thank you.

[Former Member]

Hi Buddhika,

              Please check the link it might be useful for your scenario.

              Handling Idoc Acknowledgements - ABAP Development - SCN Wiki

[Former Member]

Hi,

If you want to trigger SYSTAT01 , you may have to write code in the workflow method using MASTER_IDOC_DISTRIBUTE by trapping the success/error event configured in the Process Code.

If you are using middleware, you can give it a thought of using ALEAUD Message. The reason is that there is a standard program ( RBDSTATE T code : BDM8 ) available which will do the job for you. No coding required.

You can schedule this program using standard variant SAP_AUDIT_SEND periodically. Only thing you have to do is to set up the partner profile.

R

[buddhika_krishantha]

Hi Rudra,

My inbound message type is "SHP_IBDLV_CONFIRM_DECENTRAL". Do I need to amend standard BAPI to send SYSTAT01?

[buddhika_krishantha]

Hi Prakash,

I checked that. But it's not for SYSTAT01. Thanks.

[Former Member]

Amending standard BAPI may not help, as you need a place which is triggered after your Shipment is saved in database otherwise it might lead to data inconsistency.

What is the process code you are using? BAPI?

Check the setting in WE42 . Can you see the following Events associated?

If yes, you can trap the event as a "triggering event" and create a workflow task/method and trigger SYSTAT01 via MASTER_IDOC_DISTRIBUTE.

Or you can set up output type on Inbound Delivery/Shipment and write the same code in the processing routine.

I am sorry, but there is no such shortcut solution available. That is why I wonder why you can't use ALEAUD? It would be much easier to set that up as you have standard solution available already. Give it a thought.

R

[buddhika_krishantha]

Hi Rudra,

Thanks for your precious time.

I checked in WE42, It has same screen as your comment.

Could you please let me know how to "trap the event as a "triggering event"".

Thank you.

[Former Member]

Hi,

This is in line with what you do normally in Workflow.

1. First check if the event is triggered when you post your Idoc. Tcode SWELS ( To switch on trace ) and SWEL to display.

2. If the event is triggered, create a Business Object via SWO1 and add a method.(Background One) Or you can create a subtype to existing Business Object IDOCAPPL and then delegate it.

3. Now create a standard task and use the event as "Triggering Event" and use you own method where you should write your code to trigger the STATUS Idoc. Put some proper check(Like Message Type/Basic type etc) as it will be triggered from many places. Or you can use Check Function module for better performance.

Read some document as well on SAP Workflow. There are loads of docs available over the internet.

R

[buddhika_krishantha]

Hi,

Event is not triggering.

[buddhika_krishantha]

This is done.

I copied BAPI_IDOC_INPUT1 and added the coding to send SYSTAT01 Idoc.

Then created new process code using copied BAPI.

Thanks for all for your time.