Prototype / Extend a TextInput()
Hi --
I would like to add some functionality to a TextInput but I
am not yet
familiar with working with objects in AS 3. I do understand
object oriented
programming and I am familiar with prototyping in Javascript
but I'm not
sure of the exact syntax in Flash.
Ideally what I am looking to do is add a property INPUTMASK
which would
hold a string value and add code to the "on change" event of
the control.
Then I want to store this all as a package and create a new
control that I
can store and drop onto the stage to reuse.
If someone could explain to me how to get this started that
would be great.
If I create this control the way I hope I will be more than
happy to share
it with anyone who is interested in it.
Thanks
Rich
I use the airport utility. It finds the express and says that it has extended the network. However, later when I check the wireless options of the express, it is setup as a Create a Network.
"Create a wireless network" is the correct setting to extend the network when the AirPort is connected to the main router using a wired Ethernet connection.
"Extend a wireless network" would be the correct setting only if the AirPort Express is connected to the main router using wireless only, not Ethernet.
Similar Messages
-
I've been really trying to move away from .NET into the flex
world. With .NET there is a AJAX control for placing a text
watermark on a textbox. This simply gives a sample for the
textinput. Example would be a login form with a username textinput
that says "User Name", but when the user clicks on the box, that
text disappears.
I know how do create this effect with events, but is there
already a control that does this, or do I need to extend the
textinput control to add this functionality?
Any thoughts? Don't want to reinvent the wheel because I
don't know all the lingo.There is no control that has built in support for this, but
you can do it in MXML without extending the control:
<mx:TextInput id="ti1" text="User Name"
focusIn="ti1.text=''"/>
hth,
matt horn
flex docs -
Well I'm just starting with Flex2 and AS3. I have some Flash
Experience as I created this
Flash
app entirely in AS2. All I did was put the different components
on the stage, and then initialized them in Actionscript. So now
it's time to re-write it, add a whole bunch of new features, and
generally just make it cooler.
But I'm not understanding a few things here. I'd prefer to
layout the basic structure of my app in a mxml file, but then wire
everything together using class files written in ActionScript.
How do you use anything in the mx.controls package inside of
a ActionScript file? How do you access elements from the mxml file
in an AS3 class file?
Can you create mx.controls in an AS3 file?
I'm currently using FlashDevelop 2.0.2 which has limited AS3
support while I'm waiting for a staggeringly slow FlexBuilder
download to get to me. So maybe it's lacking in some things, but
i'm using the Flex SDK to compile, so I'm sure the errors will
exist in both places.
Any insight? Or something I can read?One more question - how do I access components that may have
been placed on the stage within my AS3 code? I realize I can
probably pass them in at a later time, but I was wondering if I
could directly access them from the stage?
My current code gives what appears to be a
NullPointerException (yeah I'm a Java programmer). Any hints? or is
it even possible?
Let's say my main.mxml looks like this...
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
xmlns:ff="flex.*"
paddingTop="0" paddingLeft="0" paddingRight="0"
paddingBottom="0"
width="500" height="500"
horizontalScrollPolicy="off" verticalScrollPolicy="off"
applicationComplete="onCreationComplete(event);"
layout="absolute"
horizontalAlign="left"
verticalAlign="top"
>
<mx:DataGrid id="datagrid" name="datagrid" x="99"
y="129">
<mx:columns>
<mx:DataGridColumn headerText="Column 1"
dataField="col1"/>
<mx:DataGridColumn headerText="Column 2"
dataField="col2"/>
<mx:DataGridColumn headerText="Column 3"
dataField="col3"/>
</mx:columns>
</mx:DataGrid>
<mx:Script>
<![CDATA[
import mx.events.FlexEvent;
import mx.containers.Canvas;
import mx.core.Application;
import com.garmin.mb.player.PlayerCanvas;
* the canvas where everything is drawn.
private var mainCanvas:Canvas;
private function onCreationComplete(event:FlexEvent):void {
var main:PlayerCanvas = new PlayerCanvas();
addChild(main);
]]>
</mx:Script>
</mx:Application>
And my PlayerCanvas looks like this...
package com.mb.player {
import flash.events.MouseEvent;
import mx.containers.Canvas;
import mx.controls.Alert;
import mx.controls.DataGrid;
import mx.controls.HSlider;
import mx.controls.TextInput;
public class PlayerCanvas extends Canvas {
* TextInput for nothing of any value;
private var input:TextInput;
* Slider that controls the position of the user on the track
private var slider:HSlider;
* the data table
private var datagrid:DataGrid;
public function PlayerCanvas():void {
this.buildTextInput();
this.buildSlider();
this.datagrid =
(DataGrid)(parent.getChildByName("datagrid"));
this.datagrid.x = 20;
} -
I have written an application using Visual Cafe. I tried to called out the application thru my server but i got this error below. Anyone has any idea whats wrong?
java.lang.NullPointerException
at java.lang.ClassLoader.resolveClass0(Native Method)
at java.lang.ClassLoader.resolveClass(ClassLoader.java:573)
at org.apache.tomcat.loader.AdaptiveClassLoader.loadClass(AdaptiveClassLoader.java, Compiled Code)
at org.apache.tomcat.loader.AdaptiveServletLoader.loadClass(AdaptiveServletLoader.java:174)
at org.apache.tomcat.core.ServletWrapper.loadServlet(ServletWrapper.java:265)
at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:289)
at org.apache.tomcat.core.Handler.service(Handler.java, Compiled Code)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java, Compiled Code)
at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java, Compiled Code)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java, Compiled Code)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java, Compiled Code)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
Desperate.......Below is the source code generated by Visual Cafe.I am using ver 4.
A basic extension of the java.awt.Frame class
import java.awt.*;
import com.symantec.itools.javax.swing.actions.JActionButton;
import symantec.itools.awt.util.ToolBarPanel;
import symantec.itools.awt.ImageHTMLLink;
import symantec.itools.awt.util.ToolBarSpacer;
import javax.swing.JToolBar;
import com.symantec.itools.javax.swing.JToolBarSeparator;
import symantec.itools.awt.ImageButton;
import symantec.itools.awt.BorderPanel;
import symantec.itools.awt.KeyPressManagerPanel;
import com.symantec.itools.javax.swing.JButtonGroupPanel;
import symantec.itools.awt.StatusBar;
import javax.swing.*;
public class Prototype extends Frame
public Prototype()
// This code is automatically generated by Visual Cafe when you add
// components to the visual environment. It instantiates and initializes
// the components. To modify the code, only use code syntax that matches
// what Visual Cafe can generate, or Visual Cafe may be unable to back
// parse your Java file into its visual environment.
//{{INIT_CONTROLS
setLayout(null);
setBackground(new java.awt.Color(215,215,215));
setSize(600,449);
setVisible(false);
add(canvas1);
canvas1.setBackground(java.awt.Color.white);
canvas1.setBounds(96,0,408,449);
try {
toolBarPanel1.setIPadSides(10);
catch(java.beans.PropertyVetoException e) { }
try {
toolBarPanel1.setIPadTop(10);
catch(java.beans.PropertyVetoException e) { }
try {
toolBarPanel1.setOrientation(symantec.itools.awt.util.ToolBarPanel.VERTICAL);
catch(java.beans.PropertyVetoException e) { }
add(toolBarPanel1);
toolBarPanel1.setBounds(504,0,96,449);
try {
imageHTMLLink1.setLinkURL(symantec.itools.net.RelativeURL.getURL("www.google.com"));
catch (java.net.MalformedURLException error) { }
catch(java.beans.PropertyVetoException e) { }
try {
imageHTMLLink1.setImageURL(new java.net.URL("file:///D:/FYP/google2.GIF"));
catch (java.net.MalformedURLException error) { }
catch(java.beans.PropertyVetoException e) { }
toolBarPanel1.add(imageHTMLLink1);
try {
toolBarSpacer1.setSpace(20);
catch(java.beans.PropertyVetoException e) { }
toolBarPanel1.add(toolBarSpacer1);
try {
imageHTMLLink2.setImageURL(new java.net.URL("file:///D:/FYP/yahoo3.JPG"));
catch (java.net.MalformedURLException error) { }
catch(java.beans.PropertyVetoException e) { }
toolBarPanel1.add(imageHTMLLink2);
try {
toolBarPanel3.setIPadBottom(10);
catch(java.beans.PropertyVetoException e) { }
try {
toolBarPanel3.setIPadSides(10);
catch(java.beans.PropertyVetoException e) { }
try {
toolBarPanel3.setIPadTop(10);
catch(java.beans.PropertyVetoException e) { }
try {
toolBarPanel3.setOrientation(symantec.itools.awt.util.ToolBarPanel.VERTICAL);
catch(java.beans.PropertyVetoException e) { }
add(toolBarPanel3);
toolBarPanel3.setBounds(0,192,96,48);
button1.setLabel("Y");
toolBarPanel3.add(button1);
button1.setBackground(java.awt.Color.lightGray);
button1.setFont(new Font("Dialog", Font.PLAIN, 15));
button3.setLabel("N");
toolBarPanel3.add(button3);
button3.setBackground(java.awt.Color.lightGray);
button3.setFont(new Font("Dialog", Font.PLAIN, 15));
try {
toolBarPanel4.setIPadSides(10);
catch(java.beans.PropertyVetoException e) { }
try {
toolBarPanel4.setIPadTop(10);
catch(java.beans.PropertyVetoException e) { }
try {
toolBarPanel4.setOrientation(symantec.itools.awt.util.ToolBarPanel.VERTICAL);
catch(java.beans.PropertyVetoException e) { }
add(toolBarPanel4);
toolBarPanel4.setBounds(0,0,96,192);
try {
imageButton1.setImageURL(new java.net.URL("file:///D:/FYP/questions.JPG"));
catch (java.net.MalformedURLException error) { }
catch(java.beans.PropertyVetoException e) { }
toolBarPanel4.add(imageButton1);
try {
toolBarSpacer2.setSpace(20);
catch(java.beans.PropertyVetoException e) { }
toolBarPanel4.add(toolBarSpacer2);
try {
imageButton2.setImageURL(new java.net.URL("file:///D:/FYP/pen.JPG"));
catch (java.net.MalformedURLException error) { }
catch(java.beans.PropertyVetoException e) { }
toolBarPanel4.add(imageButton2);
try {
toolBarPanel5.setOrientation(symantec.itools.awt.util.ToolBarPanel.VERTICAL);
catch(java.beans.PropertyVetoException e) { }
add(toolBarPanel5);
toolBarPanel5.setBounds(0,240,96,209);
setTitle("A Simple Frame");
//{{INIT_MENUS
menu1.setLabel("Main");
menu1.add(menuItem1);
menuItem1.setLabel("MenuItem");
menuBar1.add(menu1);
menu2.setLabel("Tools");
menu3.setLabel("Applications");
menu3.add(menuItem2);
menuItem2.setLabel("Powerpoint");
menu3.add(menuItem3);
menuItem3.setLabel("Words");
menu2.add(menu3);
menuBar1.add(menu2);
menu4.setLabel("Help");
menuBar1.add(menu4);
//$$ menuBar1.move(0,423);
setMenuBar(menuBar1);
//{{REGISTER_LISTENERS
SymWindow aSymWindow = new SymWindow();
this.addWindowListener(aSymWindow);
public Prototype(String title)
this();
setTitle(title);
* Shows or hides the component depending on the boolean flag b.
* @param b if true, show the component; otherwise, hide the component.
* @see java.awt.Component#isVisible
public void setVisible(boolean b)
if(b)
setLocation(50, 50);
super.setVisible(b);
static public void main(String args[])
(new Prototype()).setVisible(true);
public void addNotify()
// Record the size of the window prior to calling parents addNotify.
Dimension d = getSize();
super.addNotify();
if (fComponentsAdjusted)
return;
// Adjust components according to the insets
Insets insets = getInsets();
setSize(insets.left + insets.right + d.width, insets.top + insets.bottom + d.height);
Component components[] = getComponents();
for (int i = 0; i < components.length; i++)
Point p = components.getLocation();
p.translate(insets.left, insets.top);
components[i].setLocation(p);
fComponentsAdjusted = true;
// Used for addNotify check.
boolean fComponentsAdjusted = false;
//{{DECLARE_CONTROLS
java.awt.Canvas canvas1 = new java.awt.Canvas();
symantec.itools.awt.util.ToolBarPanel toolBarPanel1 = new symantec.itools.awt.util.ToolBarPanel();
symantec.itools.awt.ImageHTMLLink imageHTMLLink1 = new symantec.itools.awt.ImageHTMLLink();
symantec.itools.awt.util.ToolBarSpacer toolBarSpacer1 = new symantec.itools.awt.util.ToolBarSpacer();
symantec.itools.awt.ImageHTMLLink imageHTMLLink2 = new symantec.itools.awt.ImageHTMLLink();
symantec.itools.awt.util.ToolBarPanel toolBarPanel3 = new symantec.itools.awt.util.ToolBarPanel();
java.awt.Button button1 = new java.awt.Button();
java.awt.Button button3 = new java.awt.Button();
symantec.itools.awt.util.ToolBarPanel toolBarPanel4 = new symantec.itools.awt.util.ToolBarPanel();
symantec.itools.awt.ImageButton imageButton1 = new symantec.itools.awt.ImageButton();
symantec.itools.awt.util.ToolBarSpacer toolBarSpacer2 = new symantec.itools.awt.util.ToolBarSpacer();
symantec.itools.awt.ImageButton imageButton2 = new symantec.itools.awt.ImageButton();
symantec.itools.awt.util.ToolBarPanel toolBarPanel5 = new symantec.itools.awt.util.ToolBarPanel();
//{{DECLARE_MENUS
java.awt.MenuBar menuBar1 = new java.awt.MenuBar();
java.awt.Menu menu1 = new java.awt.Menu();
java.awt.MenuItem menuItem1 = new java.awt.MenuItem();
java.awt.Menu menu2 = new java.awt.Menu();
java.awt.Menu menu3 = new java.awt.Menu();
java.awt.MenuItem menuItem2 = new java.awt.MenuItem();
java.awt.MenuItem menuItem3 = new java.awt.MenuItem();
java.awt.Menu menu4 = new java.awt.Menu();
class SymWindow extends java.awt.event.WindowAdapter
public void windowClosing(java.awt.event.WindowEvent event)
Object object = event.getSource();
if (object == Prototype.this)
Prototype_WindowClosing(event);
void Prototype_WindowClosing(java.awt.event.WindowEvent event)
setVisible(false); // hide the Frame -
hi,
i am extending the TextInput control, i have managed to catch
the text typing events...
my question is:
how can i catch the text deletion (delete and backspace
keys) events ??
thanks,
jaimonListen for the "keyDown" event, and the examine the
event.charCode for a value of 8 or 127 respectively.
If you want to prevent the backspace/delete, it's not so easy
- you cannot prevent propagation of the keyDown event. Here's what
I do (not pretty, but it works):
var caretOffset:uint = textField.selectionEndIndex;
textField.setSelection(caretOffset, caretOffset);
textField.replaceSelectedText(' ');
if (event.charCode == 127)
textField.setSelection(caretOffset, caretOffset);
This works by putting a space in the position that's about to
be deleted or backspaced over, so the end effect after the deletion
is unchanged. Because backspace also moves us back, we move the
cursor to after the inserted space.
Tim -
Hi --
I am just beginning to migrate from ActionScript 2 to
Actionscript 3. I
would like to create a simple custom control with the
TextInput as the base
component and just a few custom properties of my own to help
me understand
how AS 3 works. I have started with this code:
package {
import fl.controls.TextInput;
public class MyTextInput extends TextInput {
public function MyTextInput() {
I have my document class set to MyTextInput and I have my
publish settings
set to AS 3 and I have "Export to SWC" checked.
When I try to publish my component I get two errors:
1017: The definition of the base class TextInput was not
found
5000: The class "MyTextInput" must subclass
"flash.display.MovieClip" since
it is linked to a library symbol of that type.
I am confused by the 5000 error as I have no items in the
library.
Any help would be appreciated.
Thanks
RichHi --
I am transitioning from AS 2 to AS 3 -- my job is as an
Actionscript 2
programmer.
I figured out that by adding "$(AppConfig)/Component
Source/ActionScript
3.0/User Interface" to my class path I was able to get rid of
the first
error.
By creating a component in the library and having the base
class as the
default (MovieClip) I was able to get rid of the second
error. It confused
me because I assumed the base class should be what I was
extending -- in
this case the TextInput. However, by having that in my AS
file and having
the base class a MovieClip it works as expected.
Rich
"kglad" <[email protected]> wrote in message
news:g6v3b9$ols$[email protected]..
> you need a textinput component in your library, at a
minimum. but trying
> to create a component is not a good place to start
learning anything about
> actionscript. -
Would like a TextInput that extends FlowElement
I am writing a courseware application in Flex and find the Text Layout Framework very helpful, except that I have many cases where input fields must be within the flow, such as the following:
First there might be a question _________________ and ______________,
___________, then there might be another question __________________.
The input field does not need to be a RichTextEditor, it just needs to be able to move in the flow of the text so that format is maintained if a user increases the size of the text.
I have seen statements in this forum that that the TLF was not designed to be extensible, making this a difficult task. The only other solution that I can see is to put the text into RichText objects and the input fields into TextInput objects, and write a Format Controller that positions these on lines taking into account the ending position of each, and performing line breaks as needed. Does anyone have a better idea? The problem seems a little strange given the ease of doing this in HTML.
GaryThanks to Robin on the excellent find on Platus' solution.
Gary, i was wondering if an underline would be better than an underscore. Can you please share your thoughts on the better way to preserve the underline beneath the words that are typed? It should meet both these conditions:
When the blanks are typed on, the underline should be preserved beneath the typed characters.
When some typed content is deleted, the blanks should be preserved with underline.
My plan before reading this post was to create two separate sets of TLFs - one for the passage with blanks and another set of TLFs superimposed on top, positioned to align with the input blank spaces - similar to Platus' implementation. But now, i would try to directly enter content.
Another query is, how to display underlined blank spaces, without using underscores?
This is a <flow:span textDecoration="underline">red</flow:span> apple.
Would display: This is a red apple.
This is a <flow:span textDecoration="underline"> </flow:span> apple.
Would display: This is a apple.
Shiyaz -
What's changed in the 1.2 prototype.
The 1.2 prototype has surprisingly little documentation. I started this thread to try to remedy that, in part. I'm going to start off by listing what's I've noticed changed in 1.2, gotchas to watch out for, etc, and I hope you all will follow up below w/ all the rest of the changed things which I haven't discovered yet.
1) THE COMMAND-LINE scripts/javac TOOL NEEDS THE '-gj' OPTION.
The previous release didn't. This is a big user-noticible change if you were using the older 1.0-ea prototype in makefiles and such. Note that the 'javac --help' information lists '-gj' as the default; it is wrong. '-nogj' is the default. I hope this doesn't reflect on the status of GJ in java 1.5?
2) THE COLLECTIONS API HAS CHANGED.
This is made more interesting by the fact that this release doesn't come with any javadoc and (as far as I know) javap still crashes when given GJ .class files. The only way to tell that the interface
has changed out from under you is the javac error message which you will sometimes get when you try to extend a Collection class
with a now-incorrectly-typed method. (Other times, javac will just crash.)
The changes I have seen have altered the signature of addAll, putAll, and similar methods from:
class Collection<V> {
boolean addAll(Collection<V> c);
}to
class Collection<V> {
<T extends V> boolean addAll(Collection<T> c);
}Note that this gives you much more flexibility and restores covariance in some ways; but it also breaks all your Collection subclasses which override methods with the now-obsolete signatures.
Are there any other similar method changes to watch out for? Post below; if the 'offical' javadoc for this 1.2 prototype release isn't forthcoming 'soon' I'll probably hand-edit the 1.0 prototype javadoc to be correct for the new release and post it on the web for everyone to use pro tem. (But it would be nice if the Sun folk did this themselves, so I wouldn't have to bother, hint, hint!)
3) NO MORE JAVADOC. Mentioned above; hope you've got a copy of the 1.0 javadoc lying around still.
4) BUGS FIXED. As pnkfelix noted in another post here, some type-system loopholes have been fixed in this release. Also, the bugs which prevented casts from Set to Collection and from Set to Set<T> appear to have been fixed. The bad-line-numbers-on-non-Unix-platforms bug is reputedly gone. Further, it seems that this release compiles non-GJ code better. I'll probably post more on these issues as I get a little more experience w/ this new release. Does anyone else have 'favorite' 1.0-prototype bugs which were fixed in this release?
5) ONLY WORKS ON JDK1.4. The last release didn't work on 1.3 either, as far as I can tell. But, regardless, this is the only documented change in this release (according to the CHANGES file in the distribution).
OK. This feels incomplete. Post below and let's hear what else you've noticed has changed.
[[[ObObscurePersonalNote: Felix, FLEX now has a GJ port. 'magic-4-0' These prototype compilers are far too buggy for me to release it on the rest of the group, but I've been playing with it on my own personal branch.]]]1) THE COMMAND-LINE scripts/javac TOOL NEEDS THE '-gj'
OPTION.Thanks for noting this. It may have saved me a lot of time. With only this change, my "Frink" project
( http://futureboy.homeip.net/frinkdocs/ , 194 classes with a mix of generic and non-generic code, 25000 lines) recompiled with the new compiler with zero changes. Of course, in the course of building this project, I worked around some bugs in the old compiler.
* I think that inner classes still don't work as expected. I don't know if this is a bug, but it's a shortcoming. For example, the following code still doesn't compile:
public class Outer<T>
private T outerMember;
public Outer()
outerMember = null;
private class Inner<T>
private T innerMember;
public Inner()
innerMember = outerMember;
}The compilation error is:
Outer.java:16: incompatible types
found : T
required: T
innerMember = outerMember;
^
1 error
This isn't a particularly wonderful sample, but often you do want inner classes to be able to access data from the enclosing class (say, the inner class is an enumerator that enumerates over the contents of the outer class.) But you can't. Dang.
If nothing else, a better error message should be produced. To me, "T" sure looks like "T".
* The "README" file indicates that the compiled code only works with a 1.3 or later runtime. I've tested with 1.2 and (thankfully) found no cases where it doesn't work (but there may be some.) That would be a showstopper, as many people who use Frink haven't even installed 1.3 yet, and I've worked hard to make it compatible with 1.2, 1.3, and 1.4.
Does anyone know why the documents say that the compiled code only works with a 1.3 environment? Let's hope it's a mistake. I thought one of the goals of the generic compiler was to create bytecode that could run in any JVM. And compiling with the new compiler shouldn't introduce dependencies on classes that the programmer doesn't reference...
I do compile with the -target 1.1 flag for maximum backward compatibility.
3) NO MORE JAVADOC. Mentioned above; hope you've got
a copy of the 1.0 javadoc lying around still.Gafter's recent comments in this forum indicated that they've not even begun making a version of the javadoc tool that works on generic code. I sorta wished that something magical might have happened since then, but I guess not.
The bad-line-numbers-on-non-Unix-platforms bug is
reputedly gone.But Java is write-once-run-anywhere! That's impossible! :) Gafter posted a (one-line) patch for the original compiler to this forum just a week ago. Wish I had it a year ago. That's why I wish that releases would be made more often--it was fixed long ago.
5) ONLY WORKS ON JDK1.4. The last release didn't work
on 1.3 either, as far as I can tell. I tried compiling with 1.3 and the new generic compiler, and got this message:
Exception in thread "main" java.lang.NoClassDefFoundError
at com.sun.tools.javac.v8.Main.bugMessage(Main.java:490)
at com.sun.tools.javac.v8.Main.compile(Main.java:477)
at com.sun.tools.javac.Main.compile(Main.java:36)
at com.sun.tools.javac.Main.main(Main.java:27)
The old compiler did usually work with 1.3 (I've used it for about 10 months with 1.3,) except for 4 classes out of 194, which tickled part of the compiler which used the CharSequence class (which wasn't available until 1.4). Luckily, these 4 classes of mine didn't contain generic code and could be compiled with the normal compiler.
* The new batch file for Windows contains UNIX-style linefeeds. I think that's sorta bad form. -
What class should I extend for this custom control?
The code below is my attempt at a mxml control to replace a custom context-menu that my app needs on certain textInput controls. Characters not on the keyboard are inserted into the text, replacing any selection, if applicable. Flex AIR apps (which I need for local access to SQLite) don't let me do custom contextmenus when the control is not top-level.
The custom component is encapsulated now in a Panel but I would like to have the composite control be nothing more than a textInput and a PopUpMenuButton right next to it. Is that possible—not to have a container? If so, what class should I extend, if creating this as an ActionScript component?
Thanks for the advice.
<?xml version="1.0" encoding="utf-8"?>
<mx:Panel xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" width="228" height="64" creationComplete="onInit();" >
<mx:TextInput id="mytextinput" height="20"></mx:TextInput>
<mx:PopUpMenuButton id="mybutton" itemClick="onCharSelected(event);" x="159" y="-2" label="æ" width="41" />
<mx:Script>
<![CDATA[
import mx.utils.StringUtil;
import mx.events.MenuEvent;
import mx.events.ItemClickEvent;
import mx.controls.TextArea;
import mx.controls.Alert;
import flash.events.*;
import flash.display.Sprite;
import mx.collections.ArrayCollection;
// use a point to track the selection-start and selection-end position for the text field
private var pt:Point=new Point;
private var chars:ArrayCollection = new ArrayCollection(
[ {label:"ð", data : "ð"},
{label:"æ", data:"æ"},
{label:"þ", data:"þ"} ]);
// track the selection positions as the mouse is moved or text is entered
private function onMouseEvent(e:MouseEvent): void{
pt.x=this.mytextinput.selectionBeginIndex;
pt.y=this.mytextinput.selectionEndIndex;
private function trackSelectionIndices(e: Event):void {
pt.x=this.mytextinput.selectionBeginIndex;
pt.y=this.mytextinput.selectionEndIndex;
private function onInit():void {
this.mytextinput.addEventListener(Event.CHANGE, trackSelectionIndices);
this.mytextinput.addEventListener(MouseEvent.MOUSE_DOWN, onMouseEvent);
this.mytextinput.addEventListener(MouseEvent.MOUSE_UP, onMouseEvent);
this.mybutton.dataProvider = chars;
private function onCharSelected(e:MenuEvent):void {
doInsert( e.item.data.toString(), this.mytextinput);
// insert the character chosen from the popup into the text field, replacing any selection, and then reset the insertion point
private function doInsert(s:String, trgt:Object):void {
var v:String = TextInput(trgt).text;
var pre:String =v.substr(0,TextInput(trgt).selectionBeginIndex);
var post:String=v.substr(TextInput(trgt).selectionEndIndex, v.length-TextInput(trgt).selectionEndIndex);
var result:String = pre + s + post;
TextInput(trgt).text=result;
TextInput(trgt).setSelection(TextInput(trgt).selectionBeginIndex+s.length,TextInput(trgt) .selectionBeginIndex+s.length);
]]>
</mx:Script>
</mx:Panel>Wiping perspiration from my brow as I abandon the difficult approach.
Here is the simpler approach where HBox encapsulates the TextInput and PopUpMenuButton. I am trying to figure out how to let the TextInput keep its selection highlight when it loses focus to the PopupMenuButton: setSelection does not cause the repaint.
package Search
import flash.events.*;
import flash.geom.Point;
import mx.collections.ArrayCollection;
import mx.containers.HBox;
import mx.controls.PopUpMenuButton;
import mx.controls.TextInput;
import mx.events.MenuEvent;
public class UnicodeCharPopupMenu extends HBox
public function UnicodeCharPopupMenu() {
super();
Init();
private var mytextinput:TextInput = new TextInput;
private var mybutton:PopUpMenuButton = new PopUpMenuButton;
private function Init():void {
mytextinput.width=100;
mytextinput.height=22;
mybutton.width=44;
this.width=200;
this.height=20;
visible=true;
mybutton.addEventListener(FocusEvent.FOCUS_IN, onMenuGotFocus;
mytextinput.addEventListener(Event.CHANGE, trackSelectionIndices);
mytextinput.addEventListener(MouseEvent.MOUSE_DOWN, onMouseEvent);
mytextinput.addEventListener(MouseEvent.MOUSE_UP, onMouseEvent);
mybutton.addEventListener( MenuEvent.ITEM_CLICK, onCharSelected);
//mybutton.addEventListener(MenuEvent.MENU_HIDE, onMenuHide);
//mybutton.addEventListener(MenuEvent.MENU_SHOW, onMenuShow);
mybutton.dataProvider = chars;
addChild(mytextinput);
addChild(mybutton);
// use a point to track the selection-start and selection-end position for the text field
private var pt:Point=new Point;
private var chars:ArrayCollection = new ArrayCollection(
[ {label:"ð", data : "ð"},
{label:"æ", data:"æ"},
{label:"þ", data:"þ"} ]);
//button got focus, repaint selection highlight
private function onMenuGotFocus(e:FocusEvent): void {
mytextinput.setSelection(pt.x, pt.y);
// nothing selected, menu closed
private function onMenuHide(e:MenuEvent): void {
if (e.item.data==null) {
mytextinput.setFocus();
private function onCharSelected(e:MenuEvent):void {
doInsert( e.item.data.toString(), mytextinput);
public function getText():String {
return mytextinput.text;
// track the selection positions as the mouse is moved or text is entered
private function onMouseEvent(e:MouseEvent): void{
pt.x=mytextinput.selectionBeginIndex;
pt.y=mytextinput.selectionEndIndex;
private function trackSelectionIndices(e: Event):void {
pt.x=mytextinput.selectionBeginIndex;
pt.y=mytextinput.selectionEndIndex;
private function doInsert(s:String, trgt:Object):void {
var v:String = TextInput(trgt).text;
var pre:String =v.substr(0,pt.x);
var post:String=v.substr(pt.y, v.length-pt.y);
var result:String = pre + s + post;
TextInput(trgt).text=result;
TextInput(trgt).setFocus();
TextInput(trgt).setSelection(pt.x+s.length,pt.x+s.length);
pt.x = pt.x + s.length;
pt.y = pt.x; -
How do I get Flash to recognize my TextInput from class?
Hi -
I'm trying to write a class for a standard input form. I've
got a movieclip in the library and have linked it to this class.
(class included below.)
This movieclip contains several text inputs which I have
declared in my class file. I can get their ._x and ._y values, but
I can't assign to the .text value of the TextInput. Nor can I read
this value when I set it in the parameters tab in flash. It just
comes up as undefined.
It's as though flash does not recognize the instance that was
placed on the stage in the authoring environement as a TextInput. I
can trace out the instance, but Flash does not treat it as a
TextInput because I can not assign a string to the .text property.
If I instantiate the TextInput in my class file and then
position it on the stage - I can assign to it. But this is not as
practical because I can not lay things out visually in Flash. How
do I get Flash to recognize my TextInput instance on the stage from
a class file?
Thanks in advance!
import mx.controls.TextInput;
import mini.slide.*;
class mini.slide.InfoCollect extends Slide{
var first:TextInput;
var testInput:TextInput;
var last:TextInput;
var email:TextInput;
var address:TextInput;
var city:TextInput;
var zip:TextInput;
var phone:TextInput;
function InfoCollect(){
trace("InfoCollect created");
this.first = new TextInput();
this.first.text = "testing";
trace("this.first = " + this.first.text);
}Since you are putting the assignment and trace statements in
the Constructor function, it is possible that the textInput boxes
have not all yet loaded. So, when you are trying to assign values
to them, they are not present on the stage.
Put your code in an onLoad function. That way you can insure
that all components have loaded before you assign values to them.
The onLoad function will be called when the "onLoad" event is
triggered after all of your movieclip has loaded.
function onLoad() {
---your code here---
} -
Flex Data Services does not see remote methods in extended ColdFusion component.
I have created a remote service base component as a AModelService.cfc file. I extend that file to make my ModelService.cfc. When I configure the ColdFusion data service and point to ModelService.cfc and click next, I don't see any remote methods (there are none explicitly defined in the component) in the Service Operations window.
If I go back and point to AModelServide.cfc, the parent component, and hit next, I see all the remote methods that are defined in the parent component. So, either I am doing something wrong, or Data Services does not look at methods up the cfc prototype chain, which from an OOP standpoint means that instead of say creating one restful base class and being nice and DRY you can't. I.e. not OOP for data services. Is this a bug, or what?
Anybody get data services to work with extended service components?
MarkThanks for the reply. Yes, I did compile all the Java and it
works OK with a simple Java program. It just will not work in a
Flex application.
The java classes are:
RRA:
package blah.myPackage;
import java.util.List;
import java.util.Collection;
import flex.data.DataSyncException;
import flex.data.assemblers.AbstractAssembler;
class RRA extends AbstractAssembler
public Collection fill( List fillParameters )
RRS service = new RRS();
return service.getSome();
RRS:
package blah.myPackage;
import java.util.ArrayList;
import java.util.List;
import java.sql.*;
import flex.EORS.*;
class RRS
public List getSome()
ArrayList list = new ArrayList();
String str = "bob";
RR rr = new RR(str);
list.add(rr);
return list;
RR:
package blah.myPackage;
class RR
private String name;
public RR() { }
public RR(String name)
this.name = name;
public String getName()
return this.name;
public void setName(String name)
this.name = name;
I started with something that retrieved data from a database
but watered it down just to try and get some kind of communication
between Flex and Java. -
IPTComm 2010 Call for Papers: Deadline Extended
CALL FOR PAPERS: DEADLINE EXTENDED
4th ACM Conference on Principles, Systems and Applications of IP Telecommunications
IPTComm 2010
http://www.iptcomm.org
August 2-3, 2010
Leibniz Supercomputing Center
Munich, Germany
IMPORTANT DATES
================
Paper registration: Midnight, March 5, 2010.
Paper submission: Midnight March 19th, 2010 (Firm deadline).
Notification of acceptance: May 21st, 2010.
Final camera-ready submission: June 30th, 2010.
Conference dates: August 2-3, 2010.
The paper submission deadline has been extended to March 19, 2010.
However, authors are required to register with EDAS and submit
their paper abstract by the original deadline of Midnight March 5,
2010.
The IP communications domain has matured beyond providing VoIP only
services. Universities, enterprises, businesses and individual
consumers routinely use VoIP. The focus of IP communications is now on
the operations, management, administration and provisioning aspects of
large-scale, reliable and secure communication systems. To this extent,
the research and standardization work now includes log file analysis,
session tracing across proxy meshes and overload control. As IP
communications grapples with these issues, newer technologies in the
form of cloud-based IP communication systems; peer-to-peer VoIP
networks; use of IP communications in virtual worlds; social
networks and IP communications are starting to assert a strong
presence in the IP communications domain.
The aim of the IPTComm conference is to serve as a platform for
researchers from academia, research labs, industry and government to
share their ideas, views, results and experiences in the field of
IP-based telecommunication. IPTComm will include presentations of
theoretical and experimental achievements, innovative systems,
prototyping efforts, case studies, and advancements in technology.
We invite authors to submit papers in the following and related areas:
New services and service models
* Over-the-top services.
* Social networking and IP communications.
* IP telecommunications in virtual worlds.
* Compositional services and model checking.
* Cloud-based IP communications infrastructure.
* Rapid application development frameworks.
* APIs and enablers for IP communication services.
* Browser-based IP communication services.
* Context-aware communication services.
* IMS and NGN services.
Management and Resilience
* Advantages and disadvantages of IP communications as a P2P
application.
* Advances in P2P overlays for IP communications systems.
* Management of IP communications systems and networks.
* Overload management schemes for IP communications.
* Log files and log file analysis for IP communication systems.
* Scalability of large-scale IP communication systems.
* Traffic and QoS measurement of VoIP traffic.
* Self-tuning and self-monitoring IP communications systems.
* Service discovery.
* Energy consumption and energy management in IP communication
systems.
* Incentives in P2P IP communication systems.
* Resilience in P2P IP communication system.
Security
* Identity management for IP communications systems.
* Anonymity and privacy in IP communications.
* Forensics and diagnostics in IP communication systems.
* Techniques to detect, mitigate and prevent SPIT, phreaking
and vishing.
* Denial of service detection and prevention.
Mobile IP Communications
* Mobile IP communication services.
* Mobility in cloud-based IP communications infrastructure.
* Mobile P2P IP communication systems.
Miscellaneous
* The role of IP communications in the power grid.
* Open source development in IP communications.
* Research issues in vertical IP communication markets (e.g.,
privacy in the medical field, location in logistical
field, etc.)
* Regulatory issues in IP communications.
AUTHOR INFORMATION
==================
Papers submission is handled by EDAS (http://edas.info/N8459).
IPTComm solicits full papers up to 12 pages in length, in two-column
ACM conference format
(see http://www.acm.org/sigs/publications/proceedings-templates). All
submissions must describe original research, not published nor
currently under review for another conference or journal. The program
committee will referee all papers, and accepted papers will be
published in the conference proceedings. Papers will also be published in
the ACM Digital Library.
In 2010, IPTComm will be accepting short papers of at least 5 pages and
no more than 6 pages. The aim of the short paper category is to help
maintain a published record of work carried out as well as facilitate
future affiliations and foster collaborative work. Short papers are
subject to the same rigorous review process as full papers and follow
the same submission process, schedule and expectation of presentation as
the full papers.
IMPORTANT DATES
================
Paper registration: Midnight, March 5, 2010.
Paper submission: Midnight March 19th, 2010 (Firm deadline).
Notification of acceptance: May 21st, 2010.
Final camera-ready submission: June 30th, 2010.
Conference dates: August 2-3, 2010.
Conference Location: Leibniz Supercomputing Center, Munich, Germany.
CONFERENCE CO-CHAIRS
====================
Georg Carle (Technical University of Munich)
Helmut Reiser (Leibniz Supercomputing Center)
TPC CO-CHAIRS
=============
Gonzalo Camarillo (Ericsson Research)
Vijay K. Gurbani (Bell Laboratories/Alcatel-Lucent)
DEMONSTRATION AND INDUSTRY TALKS CO-CHAIRS
==========================================
Carol Davids (Illinois Institute of Technology)
Saverio Niccolini (NEC Laboratories Europe)
PUBLICITY CHAIR
===============
Gregory Bond (AT&T Research)
Steering Committee
==================
Gregory Bond (AT&T Research)
Saverio Niccolini (NEC Laboratories Europe)
Henning Schulzrinne (Columbia University)
Dorgham Sisalem (Tekelec)
Radu State (University of Luxembourg)
TPC MEMBERS
===========
John Buford Avaya Labs Research
Eric Chen NTT Corporation
Eric Cheung AT&T Labs - Research
Tasos Dagiuklas Technological Educational Institute of Mesolonghi
Carol Davids Illinois Institute of Technology
Ali Fessi Technical University of Munich
Rosario Garroppo University of Pisa
Aniruddha Gokhale Vanderbilt University
Swapna Gokhale University of Connecticut
Carmen Guerrero University Carlos III of Madrid
Christian Hoene University of Tubingen
Alan Jeffrey Bell Laboratories, Alcatel-Lucent
Cullen Jennings Cisco
Salvatore Loreto Ericsson
Jouni Maenpaa Ericsson
Enrico Marocco Telecom Italia
Joerg Ott Helsinki University of Technology
Victor Pascual Avila Acme Packets
Joachim Posegga University of Passau
Anand Prasad NEC Corporation
Yacine Rebahi Fraunhofer Institut Fokus, Berlin
Ivica Rimac Bell Laboratories, Alcatel-Lucent
Ronaldo Salles Military Institute of Engineering (Brazil)
Stefano Salsano University of Rome "Tor Vergata"
Jan Seedorf NEC Europe Ltd.
Jose Solar Technical University of Denmark
Ivan Vidal University Carlos III of Madrid
Xiaotao Wu Avaya Labs Research
Pamela Zave AT&T LaboratoriesReminder: Our call for papers is closing on Monday 27th July. Be sure to send your abstracts to [[email protected]]
We also have a Twitter account and will be posting updates via that. Se sure to follow: aus_ora_spatial
Ross. -
TextInput in List, is it a Bug?
Hi all,
I need to have a TextInput inside a List component because I want the user to be able to change the name of the list item while viewing it. The problem is that the spacebar doesn't get captured. In other words a TextInput in a list works fine untill you want a space in what ever you are typing.
Can anyone offer a suggestion on how to fix this or get around it?
Thanks
Here's the code I'm using.
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/halo">
<s:List id="list" >
<s:itemRenderer>
<fx:Component>
<s:ItemRenderer>
<s:states>
<s:State name="normal" />
<s:State name="hovered" />
<s:State name="selected" />
</s:states>
<s:TextInput id="nameLabel" text="{data.lastName}, {data.firstName}"/>
</s:ItemRenderer>
</fx:Component>
</s:itemRenderer>
<s:dataProvider>
<s:ArrayList>
<fx:Object firstName="Ann" lastName="Green" />
<fx:Object firstName="Tom" lastName="Smith" />
<fx:Object firstName="John" lastName="Black" />
<fx:Object firstName="Jane" lastName="White" />
<fx:Object firstName="Bill" lastName="Jones" />
</s:ArrayList>
</s:dataProvider>
</s:List>
</s:WindowedApplication>Update,
If I create my own list that extends the SDK's list and if I override the findKey function so it looks like this:
override protected function findKey(eventCode:int) : Boolean
var tmpCode:int = eventCode;
return tmpCode >= 32 &&
tmpCode <= 126 &&
findString(String.fromCharCode(tmpCode));
instead of this:
override protected function findKey(eventCode:int) : Boolean
var tmpCode:int = eventCode;
return tmpCode >= 33 &&
tmpCode <= 126 &&
findString(String.fromCharCode(tmpCode));
Then using the space bar in the text input in the list works. -
How Do I Change TextInput Font?
Hi,
I am using Adobe Flash CS5 and Action Script 3, but I am struggling to do something really simple (which means I am looking in the wrong place probably), I have 5 TextInput fields, I have added to the stage via the 'Components' option, but after discovering how to change the colour of the fields, I now want to change the font which appears when you type directly into the fields when the Flash movie is playing, however I can't seems to find this function.
I found a tutorial which mentioned going to the properties panel and then clicking 'Character, then 'Embed Font', but this maybe in CS4?
Any help would be great!Thanks for your very quick reply kglad, I have followed the steps you outlined, my components instance name is 'ti', the font class is 'Harper', do I place this code within the timeline under actions or in the class I generated through the library, called Harper.as?
It is just I keep getting an error of 'access to undefined property ti' and also 'TextFormat is not compile-time-constant'.
Here is my class instance of Harper.as:
package {
import flash.text.Font;
public class Harper extends Font {
public function Harper() {
var tfor:TextFormat = new TextFormat();
var f:Font = new Harper(); // F is your font class name - see below
tfor.font = f.fontName;
tfor.color = 0xFF0000;
tfor.size = 18;
ti.setStyle("embedFonts",true)
ti.setStyle("textFormat", tfor);
// constructor code
Many Thanks -
How to extend an existing IDOC!
tell me the steps to extend the existing IDOC !
Thanks1>we31(create new segments with fields u want to populate)
2>we30(create an extension idoc type).in we30 u will get to radio buttons.1>basic type 2>extension.click on the extension and then copy the basic type.Now will get all the segmnts .Now add the new segments under the parent segement which needs to be extended.
3>attach the extended idoc type to basic type and message type to tcode WE82.
4>Now u have to search for an exit where u have to write ur code in order to populate the fields which u have extended.Basically u will write in the Function module.Make sure u r writing in the correct exit.Evry messagetype will have a function module.
5>create a project in cmod and activate the function exit.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type. Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
First, letâs determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application. It may be necessary to enhance an ALE function module even in situations where an IDOC extension has not been performed if the IDOC data being passed to and from the application requires modifications. The following approach applies to both situations.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
Error handling is a very important consideration when making enhancements to inbound ALE/EDI objects. In ALE and EDI inbound processing, workflow is used for handling errors at different levels such as technical and application. If workflow has been configured for the interface, the error messages and workflow items flow to the inbox of the named recipient(s).
It is also critical to enhance the workflow that handles notifications of the inbound ALE/EDI process. In most scenarios this is not a very difficult task because SAP lets you influence the workflow parameters and messages in function exits (customer functions). You typically do this using flags and message codes to trigger certain workflow actions. If you conform to the status codes and flags stipulated for workflow processing, the enhancement could be error-free and seamless. In the case of an inbound IDOC with an extension, you should populate the EDIDC fields IDOCTYP (new IDOC type) and CIMTYP (extension type) accordingly.
IDOC REDUCTIONS
When distributing or communicating master data to other systems, the volumes of data transmitted over communication lines may be large, resulting in performance problems and/or excessive usage of resources such as disk space and bandwidth. Careful scrutiny of the master data Basic IDOC type may reveal that many of the segments are redundant or are simply not being used. If this is true, then the basic IDOC type is a candidate for a technique known as IDOC reduction. The R/3 System provides the ability to eliminate unused segments and irrelevant segment fields from the Basic IDOC type. This procedure is relatively simple and easy to implement. IDOC reduction is available for only a few message types such as DEBMAS, CREMAS, GLMAST, MATMAS, and certain POS messages.
When performing an IDOC reduction, a new message type is created based on an existing message type. The IDOC segments associated with that message type are proposed for editing. Mandatory segments of the IDOC type canât be excluded. By default optional segments are excluded, but you can choose to include an optional segment and only certain fields in the optional segment. If you have extended the Basic IDOC type and created a new IDOC type associated with a corresponding message type and you are creating a new message type (view) based on it for purposes of IDOC reduction, then the enhanced IDOC type is presented for editing along with the additional segments.
Letâs use the Vendor Master IDOC type CREMAS01 as an example to demonstrate IDOC reduction. Message type CREMAS is used for communicating Vendor Master data to other R/3 or external systems. If you browse the IDOC type CREMAS01 youâll see that it has 10 segments, with E1LFA1M being a mandatory segment (see Figure 6). To reduce this IDOC type:
Use transaction BD53 or from SALE go to Distribution scenarios -> Master data distribution -> Reduce IDOC type for master data.
Enter ZCREMS for View (message type).
Click on Create.
You will see a pop-up box. Enter CREMAS in the Derived From field. Enter.
Enter a description. Enter.
You will see a list display with segment E1LFA1M in green and a * symbol. The symbols used in IDOC reduction are: * for mandatory, 1 for selected, - for deselected, x for core selected, and the Î.â for core not selected. The corresponding elements are highlighted in green, white, red, violet, and gray, respectively.
Expand all trees. You will see nine other segments in red.
Place your cursor on the E1LFB1M segment for company code data and click on Select. It turns white with a 1 symbol.
Double-clicking on it will display a list of fields. You can select fields that you require (see Figure 7).
Note that if a child segment is selected, its parent is also selected automatically in order to maintain the hierarchical integrity.
After youâve selected the segments required and its fields, save.
From the main screen, click on Activate.
Activating the new message type ZCREMS will turn on the message type change pointer generation on a particular client. While creating a reduced IDOC type message is a client-independent activity, activation is client-dependent. An entry is created in table TBDA2 for a specific message type in a specific client and is activated. To delete this message type, you need to deactivate it from all clients on that instance. These message types are transportable.
Now that weâve created a new message type for a reduced IDOC type, letâs build the rest of the ALE configuration to work the interface with the following steps:
Define a logical system to represent the other R/3 or external system.
Configure the Customer Distribution Model to send message ZCREMS to this logical system.
Define a port, if needed, for this system.
Define a partner profile based on the logical system and maintain its outbound parameters. Make sure to use ZCREMS as the message type and CREMAS01 as the IDOC type.
Use transaction BD14 or execute program RBDSECRE or from BALE go to Master Data -> Vendors -> Send. Then, to specify a vendor or range of vendors and enter message type, go to ZCREMS and its target logical system.
Execute.
You can also capture changes to Vendor Master data and create IDOCs by executing transaction BD21 or program RBDMIDOC. Use transaction WE02 or WE05 to view the IDOCs created as a result of the preceding test. Notice the segments populated and the basic segments that are absent due to the reduction. You will find that the fields deselected from the segments have a value of /. This is equivalent to a null value. Eliminating segments may result in saving resources, while eliminating fields may not, unless the data is compressed. Also, if you look at the master data ALE function modules for these few message types, youâll see that a function module IDOC_REDUCTION_FIELD_REDUCE is called for every segment being populated. This in itself may be an overhead. It is important to weigh the pros and cons before implementing IDOC reduction. Of course, in certain cases, it may be a necessity for adjustment of data.
Enhancing ALE/EDI and IDOC extensions and conducting IDOC reductions is fairly simple. However, before proceeding with these tasks, you must carefully research the many options available in ALE and develop the best design for your business scenario.
IMPLEMENTING BAPI WITH ALE: A SAMPLE SCENARIO
Business application programming interfaces (BAPIs) provide an interface to Business Objects in the R/3 System. Business Objects are based on object-oriented technologies and represent an application objects, such as an address or a sales order. This next section prototypes an ALE interface that incorporates BAPI methods. When weâve finished, you should have a good idea of how easy it is to incorporate BAPIs with ALE and of how beneficial leveraging the 1000+ BAPIs available in the R/3 System can be when you want to interface with R/3 application objects.
Letâs start with a brief overview of SAP Business Objects and BAPIs.
SAP Business Objects. An SAP Business Object envelopes R/3 data and business processes while making the details of data structure and access methods transparent to a user interfacing with it. It consists of four layers: kernel, integrity layer, interface layer, and access layer. The kernel represents the R/3 data and its attributes. The integrity layer represents the business logic of the object and contains the business rules that govern the values of the kernel. The interface layer describes the interface mechanisms to external applications. BAPIs belong to the interface layer. The access layer represents communication methods, such as COM/DCOM, RFC, and CORBA.
SAP Business Objects and their details are stored in the Business Object Repository in the R/3 System.
BAPIs. BAPIs are "methods" of SAP Business Objects and represent their interface layer. BAPIs are essentially function modules in the R/3 System that are capable of invoking remote function calls (RFCs) for the purpose of communicating data through the function moduleâs import/export parameters and internal tables. BAPIs do not invoke screen dialogs. Like blackbox technology, BAPIs do not require the programmer or user to know the coding and implementation details of the interface to the Business Object. The user simply invokes the BAPI with its appropriate parameters and values in order to accomplish a task such as getting a list of materials from an external system or sending a list of contact person details to another system.
BAPIs can be executed synchronously or asynchronously while using the ALE communication layer for exchanging data. Typically, with asynchronous BAPI communications, an ALE IDOC is used to distribute the data. As we will learn in the following prototype, the ALE distribution model has to be configured in order to use the appropriate BAPI methods for the RFC destination that provides a gateway to the external system (R/3 or other). For this type of communication, an ALE IDOC interface must exist. If a particular BAPI (SAP-delivered or user-written) does not have an ALE IDOC interface, the interface can be generated using certain R/3 tools and procedures.
BAPIs are fast becoming the communication standard for exchanging data between business systems (including R/3). SAP Business Objects conform to Open Application Group (OAG) standards, and BAPIs support the COM/DCOM and CORBA guidelines. ALE and BAPIs is the strategic direction for all SAP interface technologies and will replace SAPâs traditional techniques in the future.
A BAPI/ALE PROTOTYPE ÷ CONTACT PERSON DETAILS
In the previous section, we learned how to enhance ALE functionality using the example of Customer Contact Person details. We extended the IDOC and enhanced a customer function with a few lines of ABAP code to achieve the additional functionality of distributing contact person details. While this was an exercise to learn IDOC extensions and customer-function enhancements, we can prototype a BAPI/ALE interface in this section that accomplishes the same purpose ÷ the distribution of contact person details. In release 4.5 of the R/3 System, message type ADR3MAS and IDOC type ADR3MAS01 have been provided to distribute contact person details with the aid of a BAPI method. The steps weâll walk through in a moment will illustrate the ease with which we can integrate BAPIs with ALE to get an interface up and running for many standard business scenarios or specialized cases that were not supported by ALE prior to the advent of BAPIs.
The ADR3MAS is considered to be a master data message type because it complements business master data, such as customer and vendor master. It is now supported by change document functionality, implying that change pointer mechanisms can be used to capture and then distribute changes occurring to contact person data using ALE IDOCs. The function module that accesses the R/3 data is a BAPI. In the R/3 System, contact person address is a business object. If we search the Business Object Repository (via transaction SWO1) with the keyword "address," for example, we will find business object BUS4003 under Cross-Application Components -> General Application Functions -> Address Management -> BUS4003: Address of a person in a company. This is the business object that pertains to our scenario, and a drill down on it reveals the details of the object, including its methods (see Figure 8). The method that would be of interest to us is "AddressContPart.SaveReplica." For your information, the corresponding BAPI function module is BAPI_ADDRCONTPART_ SAVEREPLICA in the function group SZAM.
Having gathered this information, Letâs build the outbound interface:
Create a logical system (via transaction SALE) to represent the receiver system.
Configure the distribution model. From transaction SALE, use option Maintain Distribution Model to create a model view for this scenario. Specify the sender system (the base logical system for the client you are working in, such as the logical system that has been assigned to that client) and the receiver system (the logical system). After positioning the cursor on the receiver system, click on Method and enter AddressContPart in the Object Name field on the panel that pops up. Also enter SaveReplica in the Method field on the pop-up panel. Enter and save the Distribution Model (see Figure 9).
From transaction WE20, create a partner profile based on the logical system for the interface. Use message type ADR3MAS and IDOC type ADR3MAS01, with an appropriate port.
Activate the change pointer for message type ADR3MAS. From SALE go to Set up Data Distribution -> Master Data Distribution -> Activate Change Pointers. Ensure that change pointer generation is active at the general level as well.
Now that weâve completed the configuration, letâs test the interface. The purpose of this test is only to create outbound IDOCs. Appropriate settings, such as port definitions and RFC destinations, can be made as required for purposes of communicating the IDOCs to the external system (or other R/3 system).
From the Customer Master or Vendor Master screens, create or make changes to contact person address. This should result in the creation of change pointers. (Check table BDCPS for change pointer entries with message type ADR3MAS.) After this, from transaction BALE go to Periodic Processing -> Process Change Pointers, enter ADR3MAS as the message type, and execute the transaction. This should result in a message indicating the number of master IDOCs created. Use transaction WE05 to display the IDOCs.
THE ALE AUDIT
In this section letâs take a look at the prototyping of the ALE Audit. ALE Audit is a powerful mechanism for verifying the success of ALE transactions/messages sent to another system. As you will see, implementing ALE Audit is not only easy but also very beneficial, because it facilitates the monitoring and tracking of transactions across systems while providing an entry point into error handling.
Program RBDSTATE is used for audit confirmation of ALE transactions between two R/3 systems; in other words, it indicates the success or failure of the ALE transaction on the target system. The program reports the status of the transaction on the target system back to the sending system. This process also serves as an interface itself from the target system to the sender system, facilitated by message type ALEAUD. In the following section, weâll look at the various steps needed to set up ALEAUD and execute program RBDSTATE.
SETTING UP ALEAUD and EXECUTING PROGRAM RDBSTATE
Letâs consider two different R/3 systems with base logical systems BK1CLNT010 (sender system) and BK2CLNT020 (target system). Assume that you are distributing characteristics master (message type CHRMAS) from BK1CLNT010 to BK2CLNT020. When you send CHRMAS02 IDOCs from BK1CLNT010, their status is 03 (data passed to port OK) if they were successfully externalized from the sender system. If the IDOCs were received and processed successfully on the target system, the status of those IDOCs on the target system is 53 (application data posted). Remember that you have to create a partner profile for BK1CLNT010 on the target system in order to receive the CHRMAS messages. The inbound parameters of BK1CLNT010 partner on the target system have CHRMAS as the message type and CHRM as the process code.
You now need to configure BK2CLNT020 to send ALEAUD messages to BK1CLNT010, the sender system. And you also need to configure BK1CLNT010 to receive those messages in order to update the status of CHRMAS IDOCs sent to the target system:
On the target system BK2CLNT020, configure the distribution of message flow of type ALEAUD to logical system BK1CLNT010.
Create filter object using object type MESTYP with a value of the message type for which you need audit confirmation. This message type must flow from the sender, BK1CLNT010 to BK2CLNT020. In this example, the value of the filter object type MESTYP is CHRMAS, message type for characteristics master. Save the distribution model. Use transaction BD64 to do this.
On target system BK2CLNT020, create an RFC destination with name BK1CLNT010. Choose the relevant connection type and enter the logon parameters and password for the R/3 system on which BK1CLNT010 resides. Use transaction SM59 to do this.
On target system BK2CLNT020, generate partner profile and port definition using transaction SALE, go to Communications -> Generate partner profile. Specify the customer model as described. Check the partner profile to ensure outbound parameter entries for message types ALEAUD and SYNCH.
On sender system BK1CLNT010, create a logical system for BK2CLNT020. Create a partner profile for logical system BK2CLNT020 with inbound parameters for message type ALEAUD, with process code AUD1.
Distribution of customer model on BK2CLNT020 to BK1CLNT010 is not necessary.
TESTING THE ALE CONFIRMATION PROCESS
Now you are ready to test the ALE audit confirmation process:
From the sender system, BK1CLNT010, send a couple of CHRMAS02 (characteristics master) IDOCs down to the target system, BK2CLNT020. Make sure that the status of the IDOCs is 03 (data passed to port).
Check the target system for receipt of these IDOCs. Make sure that they are in a status of 53 (application data posted).
Execute program RBDSTATE with appropriate parameters. Specify BK1CLNT010 for Confirm to System, CHRMAS for Message type, and date, if necessary.
Upon successful execution, informational messages will be issued indicating the IDOC number and status of the ALEAUD IDOC. (Note that a single ALEAUD audit IDOC can contain audit messages for multiple application IDOCs. This capability reduces the traffic of IDOCs between the two systems and keeps the overhead of audit confirmations at a minimum.)
Check the sender system for the receipt of the ALEAUD message. The status of the CHRMAS IDOCs that you sent to the target system must be changed to 41 (application document created in target system).
This completes the test of ALE audit confirmations (see Figure 10 and Figure 11 for IDOC display of target and sender system).
Audit confirmations can play a significant role in the reporting and monitoring of production systems. You can schedule program RBDSTATE periodically on target systems to report back to sender systems. Keep in mind that you need to maintain a sufficient time lag between the sending of application IDOCs to the target system and the execution of this audit program because the application documents need to be posted on the target system. This program can also be accessed from BALE using Periodic work -> Audit confirmation.
Maybe you are looking for
-
I launch and relaunch and the same message appears over and over. Should I uninstall and then re-install Lightroom? Would this fix the problem?
-
Library Folder Organization - State of Workflow Labels
One of the problems I face when using Adobe Lightroom (2.5 and prior) is that there is no way to label the state of processing of a particular folder in my library. That is for example I cannot label a folder in my library whether I have processed it
-
Help please....phone icon missing from screen suddenly
Hi,suddenly I looked at my home screen and it seemed different. I noticed that the phone option is missing from the bottom of the home screen. It is usually down with the icons "mail" "safari" and "ipod". Where did it go and how can I get it back????
-
Hey there....yesterday my laptop started giving alerts stating my computer was at risk of hackers and malice spyware. Long story short, after frenzy mode, I contacted Webroot and after quite a few tries, they were able to get into my computer and do
-
In the select query how to search for a particular part of data. (in ABAP code) Table : ABC Field name : Category Field content : Enterprise. Query : Select * from ABC where substr(category,1,3) ='Ent'. [The query should check the complete