Successor/Predecessor scenario

[Former Member]

Good day all,

I'm trying to implement a successor step, i think it's all well configured, but the successor step stays on queue and don't get executed.

Outboun in first step

<outbound>

- <Channel id="OUT_DB">

<type>Database</type>

<format>jdbc</format>

<successor>DYN.TesteFile</successor>

<succtype>payload</succtype>

</Channel>

</outbound>

Inbound in the successor step

- <inbound>

- <Channel id="INB_IQ_INTQ_ASYN_BIU">

<type>Internal Queue</type>

<mode>Asynchronous</mode>

<trigger>Queue</trigger>

<obj>DYN.TesteFile</obj>

<ident>vBIU Name</ident>

<idpar>n.a.</idpar>

<idns />

</Channel>

<Retrieval method="" />

<Formatting format="dynamic" />

</inbound>

I don't know what i'm doing wrong.

Any guidence to in this regard will be greatly appreciated.

Kind regards,

Tiago Santos

[Trinidad]

Hi Tiago,

In order to test your successor step and find out where can be the problem I recommend you to:

1. First of all have a look to the information provided by the Queue Monitor. There are different buttons in the right side column that can maybe give you a hint about the problem. If you cannot find out any relevant information from there please delete all messages with the Clear button.

2. You should also check whether some IPO steps got deactivated because of the problem. You can have a look at it from Control Center -> Monitoring -> IPO-Step Status to see if there is any IPO that is deactivated by your scenario failing. You can reactivate them also from there.

3. Retry the step after cleaning the Queue Monitor and checking all IPO-steps are active.

4. If you cannot make it work and the message stills go to the queue you should then:

a. Create a simple processor step with only the final atom in the processing flow and don't do any coding inside the final atom xsl.

b. Try again to see if the processing gets blocked int the Queue with this very simple flow.

5. If the processing stills go to the queue monitor with the very simple step please check if there is a rectest.xml file inside the simple vBIU step folder. You can use this rectest as Inbound message for your step in order to debug it. Just try then to debug it and see if you can find out the problem.

Let me know any extra info.

Regards,

Trinidad.

[Former Member]

Hi Trinidad,

Thanks for you response.

> In order to test your successor step and find out where can be the problem I recommend you to:
> 1. First of all have a look to the information provided by the Queue Monitor. There are different buttons in the right side column that can maybe give you a hint about the problem. If you cannot find out any relevant information from there please delete all messages with the Clear button.

The buttons don't work at all, i click on all of them but gives me no message or window, clear button works ok.

> 2. You should also check whether some IPO steps got deactivated because of the problem. You can have a look at it from Control Center -> Monitoring -> IPO-Step Status to see if there is any IPO that is deactivated by your scenario failing. You can reactivate them also from there.

No IPO steps got deactivated.

> 3. Retry the step after cleaning the Queue Monitor and checking all IPO-steps are active.

All IPO steps are active and step stays in the queue

> 4. If you cannot make it work and the message stills go to the queue you should then:
>                a. Create a simple processor step with only the final atom in the processing flow and don't do any coding inside the final atom xsl. 
>                b. Try again to see if the processing gets blocked int the Queue with this very simple flow.

I tried to call de precedessor step using a timer insted of the successor/predecessor mode ant it get executed, with error because it has nothing defined in the atoms but still get executed

> 5. If the processing stills go to the queue monitor with the very simple step please check if there is a rectest.xml file inside the simple vBIU step folder. You can use this rectest as Inbound message for your step in order to debug it. Just try then to debug it and see if you can find out the problem.

The inbound message should come from the predecessor step, i need this step to execute with or without error to find out what should i look for in the inbound message.

I'm still stuck in this problem.

Regards,

Tiago Santos.

[Trinidad]

Hi Tiago,

I'm able to reproduce the problem you are having.

I can reproduce it when the Inbound Channel is Void/Timer but it works fine when the Inbound channel is B1 for example.

Please create a message for SAP support and attach your package as a sample.

Please let us know if they propose you a workaround or a fix.

Best Regards,

Trinidad.