<HTML><BODY>
<div>Paul,</div>
<div> </div>
<div>I did use <SPAN class=correction id="">BDCs</SPAN> in <SPAN class=correction id="">Workflow</SPAN>. You have to make sure you have a way to correct any errors and continue with the <SPAN class=correction id="">workflow</SPAN>. <br>
</div>
<div>My first approach would be to contact SAP since they have provided a way to extend the table <SPAN class=correction id="">IFLOT</SPAN> as well as user exits to populate them the feature should be extended to the <SPAN class=correction id="">BAPI</SPAN> as well. In one of my previous projects SAP did modify a <SPAN class=correction id="">BADI</SPAN> where the extended structure was not available to any of the methods when we approached them and explained the situation and the <SPAN class=correction id="">business</SPAN> need.</div>
<div> </div>
<div>Or, you can do a <SPAN class=correction id="">BDC</SPAN> for <SPAN class=correction id="">IL01</SPAN> instead of a two step process (Assuming the extended fields are available on the Create screen and processed from a user exit).</div>
<div>Why not <SPAN class=correction id="">cre</SPAN></div>
<div> </div>
<div style="CLEAR: both">Best Regards,<br>
<SPAN class=correction id="">Ramki</SPAN> <SPAN class=correction id="">Maley</SPAN>.</div>
<div> </div>
<br>
-----Original Message-----<br>
From: Paul.Bakker@osr.treasury.qld.gov.au<br>
To: SAP-WUG@mit.edu<br>
Sent: Tue, 7 Nov 2006 8:52 PM<br>
Subject: Using <SPAN class=correction id="">BDC</SPAN> in a <SPAN class=correction id="">FuncLoc</SPAN> <SPAN class=correction id="">workflow</SPAN><br>
<br>
<STYLE>
.AOLPlainTextBody {
margin: 0px;
font-family: Tahoma, Verdana, Arial, Sans-Serif;
font-size: 12px;
color: #000;
background-color: #fff;
}
.AOLPlainTextBody pre {
font-size: 9pt;
}
.AOLInlineAttachment {
margin: 10px;
}
.AOLAttachmentHeader {
font: 11px arial;
border: 1px solid #7DA8D4;
background: #F9F9F9;
}
.AOLAttachmentHeader .Title {
font: 11px arial;
background: #B5DDFA;
padding: 3px 3px 3px 3px;
}
.AOLAttachmentHeader .FieldLabel {
font: 11px arial;
color: #000000;
padding: 1px 10px 1px 9px;
background: #F9F9F9;
}
.AOLAttachmentHeader .FieldValue {
font: 11px arial;
color: #000000;
background: #F9F9F9;
}
.AOLAttachmentHeader a, .AOLImage a {
color: #2864B4;
text-decoration: none;
}
.AOLAttachmentHeader a:hover, .AOLImage a:hover {
color: #2864B4;
text-decoration: underline;
}
body {
background-color: white;
font-family: "Verdana";
font-size: 10pt;
border: 0px;
}
p {
margin: 0px;
padding: 0px;
}
img.managedImg {
width: 0px;
height: 0px;
}
img.placeholder {
width: 275px;
height: 206px;
background: #F4F4F4 center center no-repeat;
border: 1px solid #DADAD6 !important;
}
</STYLE>
<div class=AOLPlainTextBody id=AOLMsgPart_0_2942cbfd-19d2-4c6b-bb68-94213315af07><PRE><TT><SPAN class=correction id="">G'day</SPAN>,
I'm investigating how to create a functional location via a workflow. The
idea is to present the user with a form (roughly based on table <SPAN class=correction id="">IFLOT</SPAN>), and
then pass their input data to the <SPAN class=correction id="">BUS0010</SPAN>.CREATE method.
Fine so far. My problem is that the client has extended table <SPAN class=correction id="">IFLOT</SPAN> with Z*
fields (in a custom include). As far as I can see, there is no way to adapt
the CREATE method (which calls BAPI_FUNCLOC_CREATE) so that it will handle
the new Z* fields.
So what are my options? The only one I can think of, is to call the CREATE
method, and then execute a subsequent step to update the custom fields via
a BDC session on transaction <SPAN class=correction id="">IL02</SPAN>!
This is a <SPAN class=correction id="">yuk</SPAN> solution, because it is brittle, it splits the creation into
two steps, and I would have to introduce BDC error handling into the
workflow.
Do you have a better idea? Has anyone else had to execute <SPAN class=correction id="">BDCs</SPAN> via workflow
to make up for inflexible <SPAN class=correction id="">BAPis</SPAN>? I wonder what 'best practice' is.
<SPAN class=correction id="">thanx</SPAN>
Paul
******************************************************************************************************************************************************
Only an individual or entity who is intended to be a recipient of this e-mail
may access or use the information contained in this e-mail or any of its
attachments. Opinions contained in this e-mail or any of its attachments do not
necessarily reflect the opinions of Queensland Treasury.
The contents of this e-mail and any attachments are confidential and may be
legally privileged and the subject of copyright. If you have received this
e-mail in error, please notify Queensland Treasury immediately and erase all
copies of the e-mail and the attachments. Queensland Treasury uses virus
scanning software. However, it is not liable for viruses present in this e-mail
or in any attachment.
******************************************************************************************************************************************************
_______________________________________________
SAP-WUG mailing list
<A href="mailto:SAP-WUG%40mit.edu">SAP-WUG@mit.edu</A>
<A href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A>
</TT></PRE></div>
<!-- end of AOLMsgPart_0_2942cbfd-19d2-4c6b-bb68-94213315af07 -->
<div class="AOLPromoFooter">
<hr style="margin-top:10px;" />
<a href="http://pr.atwola.com/promoclk/1615326657x4311227241x4298082137/aol?redir=http%3A%2F%2Fwww%2Eaol%2Ecom%2Fnewaol" target="_blank"><b>Check out the new AOL</b></a>. Most comprehensive set of free safety and security tools, free access to millions of high-quality videos from across the web, free AOL Mail and more.<br />
</div>
</BODY></HTML>