Question:
In WE20, find the partner that the idocs are using, and double click on the inbound idoc (DESADV). This will take you to a screen where you can select either:
1. Trigger by background program
OR
2. Trigger immediately
1. will wait until you execute RBDAPP01, and 2. will go in automatically without waiting.
Answer:
In WE20, find the partner that the idocs are using, and double click on the inbound idoc (DESADV). This will take you to a screen where you can select either:
1. Trigger by background program
OR
2. Trigger immediately
1. will wait until you execute RBDAPP01, and 2. will go in automatically without waiting.
Currently the WE20 setting is Trigger Immediately - but it doesn't seem to be having that effect.
The IDocs get 'stuck' in the Pass to Application Status regardless of the processing method chosen in the Partner Profile.
Anyone else got any other ideas?
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru
Answer:
If that is the case then you probably don't have your workflow event linkage set up to process IDOCs automatically. You can turn this on by running program RSEINBEV.
Answer:
If that is the case then you probably don't have your workflow event linkage set up to process IDOCs automatically. You can turn this on by running program RSEINBEV.
Since my QA system and my Production system are exhibiting different behaviour (trigger immediately is working in QA) is there any way to validate whether this program has been run in the past?
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru
Answer:
Hi Rosie,
Check in PFTC_DIS and select standard task 30200090, display it and go into the "triggering events" tab. In here you should see event "PROCESSSTATEREACHED". If the left column has a green light, I believe this means the program has been run.
Answer:
Hi Rosie,
Check in PFTC_DIS and select standard task 30200090, display it and go into the "triggering events" tab. In here you should see event "PROCESSSTATEREACHED". If the left column has a green light, I believe this means the program has been run.
Having looked at this in our system, the workflow appears to be active and the triggering event has and active binding and green light.... so perhaps this is not our problem with this.
Anyone else got any other ideas?
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru
Answer:
Anyone else got any other ideas? (please) - not afraid to beg here......
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru
Answer:
you haven't got the 'test' button ticked have you ?
Answer:
you haven't got the 'test' button ticked have you ?
Where? There's quite a few places where it seems to be ticked..... but this is the same between our QA and our PRD systems.....
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru
Answer:
Hi
Sometimes, if there are any ABAP Program dumps, the Idoc processing gets effected and goes into halt and waits gets struck. Check ST22 transaction, to find if the processing is being halted due to Program dumps.
R
Answer:
There are no short dumps associated with IDocs on the system when this happens. I am really at a loss to understand how it works in QA but not in PRD. Everything appears to be fine, but the IDocs wait for the batch job before processing through applications rather than automatically when received.
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru
Answer:
might not solve your problem but there's some useful reading here.....
http://www.sapgenie.com/sapgenie/docs/advanced_guide_to_edi_configuration.doc
http://www.sapgenie.com/edi/operations.htm
Answer:
Thanks Malcom for the links - but thus far I haven't been able to find anything which solves the problem.
If anyone else has any suggestions I'll gladly hear them
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru
Answer:
Well it seems to be working - and I haven't changed a thing!
I have no idea how it has started to work as it should, I haven't done anything (other than go in and out of the partner profiles etc. checking things).
Somehow or another this seems to have reactivated whatever link was missing and it all appears to be fine.... confused - but satisfied
Thanks to everyone who suggested things to look at.
_________________
Kind Regards
Rosie Brent
Please remember to search the forum and check the FAQ before posting questions, thank you.
Tuly Idiot most of the time, part-time Guru