<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Apologies for the spam :P<BR>
<BR>
So, OK it decomposes the structures element by element (but only up to 255 chars for each). Hence a container becomes quite full of 'sub' elements belonging to the parent element.<BR>
<BR>
I think I knew this...been a while since I've neeeded to care about it XD<BR>
<BR>
But...I still don't think this is ideal where the parameter will be extended a lot...<BR>
<BR>
I know that I can pass a multi-line table based on SWCONT into an SWCONT-based container (so setting a container into a container as a table), so I'm leaning towards suggesting an unstructured 'table of elements + values' instead of a complex structure...<BR><BR>
Pity BoR can't cope with ABAP_PARMBIND though...<BR>
<BR>
MGT<BR><BR>
<HR id=stopSpelling>
<BR>
From: madgambler@hotmail.com<BR>To: sap-wug@mit.edu<BR>Subject: RE: SWCONT's limitations with long values...<BR>Date: Fri, 21 Nov 2008 15:40:37 +0000<BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
Hi again,<BR> <BR>I forgot to mention that the example they provide where an importing parameter structure is already longer than 255 is BoR Object Method ISUCONTRCT.ChangeFromData where parameter ContractData is based on BAPIISUCONTRACT which is 386 chars long in our system.<BR> <BR>So, it must be able to cope somehow...presumably if I could be bothered to debug it I'd find out how ;)<BR> <BR>MGT<BR><BR><BR>
<HR id=EC_stopSpelling>
<BR>
<BR>From: madgambler@hotmail.com<BR>To: sap-wug@mit.edu<BR>Subject: SWCONT's limitations with long values...<BR>Date: Fri, 21 Nov 2008 15:30:31 +0000<BR><BR><BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
<DIV class=EC_EC_EC_Section1>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Hi,</SPAN></FONT></P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">I'm trying to convince SAP that using a really long structure-based single line importing parameter for a BApI, that might grow and grow, isn't a smart idea because SWCONT is limited to 255 chars. My fear is that we'll hit some sort of limit somewhere which will cause problems, whether that will be in BoR elsewhere like a BAdI.</SPAN></FONT></P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">They've come back and said that swc* macros can cope with longer strings at runtime and no truncation will result. Personally I'm not convinced and can only assume that the SAP code flicks into set/get table mode to cope somehwere, but I can't seem to find where..does anyone here know whether it can do this and how?</SPAN></FONT></P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Regardless of their suggested approach, I want to try and impress upon them that a nested unstructured approach is more suitable to our needs and something more akin to SAP's Master Data Generator table EPRODA (which assigns a type definition to an element) has more of a future in our system. </SPAN></FONT></P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">But they're being a bit stubborn about this and any ammuntion from the WUG about pitfalls when using long parameter definitions like this would be useful.</SPAN></FONT></P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Thanks in advance,</SPAN></FONT></P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=EC_EC_EC_MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Mike GT</SPAN></FONT></P></DIV><BR>
<HR>
BigSnapSearch.com - 24 prizes a day, every day. <A href="http://clk.atdmt.com/UKM/go/117442309/direct/01/">Search now</A><BR>
<HR>
Win £1000 John Lewis shopping sprees with BigSnapSearch.com <A href="http://clk.atdmt.com/UKM/go/117442309/direct/01/">Search now</A><br /><hr />Get the best wallpapers on the Web - FREE. <a href='http://wallpapers.msn.com/?ocid=[B001MSN42A0716B]' target='_new'>Click here!</a></body>
</html>