<div>Rick,</div>
<div> why dont you try with SAP_WAPI* Fm's.Hope this may help you.Most of the time the former FM's(SWW*) wont work as expected.</div>
<div> </div>
<div> </div>
<div>Regards,</div>
<div>Priyank<br><br></div>
<div class="gmail_quote">On Mon, Oct 4, 2010 at 8:33 PM, Sample, Rick <span dir="ltr"><<a href="mailto:Rick.Sample@graybar.com">Rick.Sample@graybar.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi folks,<br><br>I have an old FM calling SWW_WI_CONTAINER_READ with an old obsolete parm that is now getting short dumps.<br>
<br>CALL FUNCTION 'SWW_WI_CONTAINER_READ'<br> EXPORTING<br> wi_id = l_activewi_id<br> read_for_update = 'X'<br> TABLES<br> wi_container = container<br> EXCEPTIONS<br>
container_does_not_exist = 1<br> OTHERS = 2.<br><br>SWW_WI_CONTAINER_READ used to have this export parameter called:<br>"read_for_update" (no longer used and obviously not for a long time but never caused issues)<br>
The FM compiles without warning, but does show as error in SLIN. When it was written, was not an issue.<br><br>Now, we are in ECC6 for few years, and did a service pack upgrade over the weekend. (Gathering details on exactly what moved up)<br>
<br>Is there some option that could have been turned on stronger checks on something like the FM interfaces?<br><br>Thanks,<br>Rick<br><br><br><br><br>_______________________________________________<br>SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br></blockquote></div><br><br clear="all">
<br>-- <br>Adios,<br>PRIYANK DEV PATIL<br><br>