ALE Config Problem

Hi Guru
I have two SAP System ,
1. MOP client (100) and 2. PQR Client (200)
MOP system sending Idoc to PQR. There is no Idoc is flowing from PQR to MOP.
Now my Question is
In PQR system Config Require
In defined Logical System PQR in PQR System
now in Assignment part of Logical system
I need to assign PQR to client 100 or Clent 200 ?
Regards
RJ

200.
Your partner profile in the MOP system will have an outbound LS partner representing your PQR/200 system. This name will match the setting you made in BD54 for your logical system. The message type that you add to the profile will point to a receiver port which has an RFC destination assigned. The RFC destination will point to your PQR/200 system.

Similar Messages

Urgent...problem in manuall ale config

hi all,
when iam doing ale config for a a simple vendor master data transfer i got error.
the first 3 steps r ok. rfc destination and test connection and remote logon is ok.
in step 4 ..i assigned a message type(cremas) to the modelview.when i expand modelview i shows sender lg sys,rec log sys and cremas,no fillers in cremas.
1)but when distribute modelview it shows no message type is assigned to modelview.
2)in partner profiles i generate ports . here also i got error. partnet profile is not generated to the xxxx log sys and cancelled in both xxxx and yyyy log sys..
reply please.
vijay

Hi,
Try creating the ports and partner profiles manually through transactions WE21 and WE20 respectively and then the distribution model (txn BD64). Now try distributing the model view and proceed with the Idoc generation.
~ Bineah.

CRM to PI outbound IDOC scenario : IDOC ALE config

Hi folks,
I have a scenario: CRM-> PI
CRM system posts an IDOC to PI,
I have done all the necessary ALE configs:
1. comm. id on PI
2. RFC Destination on CRM to PI
3. Port on CRM. we21
4.Logical SYsm on CRM
5. Partn Prof on CRM
now, when i try to push out an idoc out of CRM , it fails in CRMs TRFC queu(SM58)
with this error:
Transaction IDX1: Port SAPDX1, client 500, RFC destination contain error
I have no clue why it failed with this error.
1. No idea from where it picked up this port as well.
2. Port i created to PI was an autogenerated Port and not SAPDX1, don't knw how it picks this up.
Would appreciate any help with respect to this.
Thanks,
Hank

Also, for your reference just double check if the following steps are completed properly for outbound processing:
1.Define Logical Systems and Assign Client to Logical System u2013 Transaction SALE
2.Maintain RFC Destinations u2013 Transaction SM59
3.Define Ports u2013 Transaction WE21
4. Maintain Distribution Model u2013 Transaction BD64
5.Generate/Create Partner Profile u2013 Transactions BD82/WE20
6.Distribute Model View u2013 Transaction BD64
    -Select the Model View
     -Go to menu path Edit -> Model View -> Distribute
     -Result log will be displayed on the next screen
Hopefully it should work now.
Puneet

ALE Config for Solman BPs

Is there any documentation out there to help me in setting up ALE between ECC and Solman to create BPs in Solman. I have basic documentation on ALE config in general but am looking for specific docs for Solman BP population.
Thank you,
Alex

Hi Alex,
Solution Manager was based on CRM so I will recomend you to start with Note 550055 - EBP/CRM: New integration for business partner
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index
This will give you the guideline, what I would suggest is to mantain as well the Org Structure in 1 system in this case ECC and then replicate maybe the Support Org Structure along with the BP's to Solution Manager.
Another SAP Note you cam use 615896 - HR-ALX: Distribution models - Templates, Most probably you have the templates in your system if you have current SP's, I do remember I saw some templates for CRM which will work fine for Solution Manager.
Hope this helps
Best regards,
Juan Jose Alvarado
Edited by: Juan Jose Alvarado on Mar 1, 2010 5:27 PM
Edited by: Juan Jose Alvarado on Mar 1, 2010 5:31 PM

Ale config part 2...question

Hi,
While doing the ale config as per blog...
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I managed to distribute the model view..however when i go to BD10 and select the specified material SWAR1...out of matmas...i get an error telling me that no material could be found.............How can i test that i can send an idoc to the XI system....? is there a standard material that i can send to verify this...
Venkat

There are no standard material numbers avaiable in SAP. All u need to do it to create in the TC MM01 and u can refer to the table MARA and the material number field is MATNR.
Coming WRT to the blog when u want to test it either u press F4 to get the list of material avaiable or check in MARA.

Audio Config" problem after upgrading to 7.6

I have only had my ipod one week. It is working beautifully. My problem is that I can no longer charge it or add songs to it because I can not open itunes. The previous version worked beautifully on my computer. After I upgraded to 7.6, it stopped working and I get an Audio Config. problem everytime I try to open it. I have tried uninstalling and reinstalling the program but it does not help. What do I need to do to fix this problem?

I have had my ipod a few weeks - but have nothing but problems letting itunes run the syncing, sometime it works and sometimes it does not. I had to reset my ipod 2 times already just to keep song on here, should have gone with Zune or Sonys (what my wife has) they are not having a single issue...
I would like to add my voice to his - I upgraded to 7.6, it stopped working and I get an Audio Config. problem everytime I try to open it. I have tried uninstalling and reinstalling the program but it does not help. What do I need to do to fix this problem ! ! ! ! ?

Problem in ALE config

Hi all,
Ihave created 2 logical systems gir800 , gir810 in the same server for the clients 800 and 810,when i am trying to configure ALE while running <b>Generate partner Profile</b>, i am getting the Error
<b>Port could not be created
RFC destination GIR800 not specified for system GIR800
Enter the RFC destination and restart the generation    </b>
Please let me know what could be the Problem,
I checked SM59 everything is ok,
Help me with the solution........................
Thanks,
Girish

Hi Girish Kosuri
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
     Click on Sending & Receiving Systems-->Select Logical Systems
     Here Define Logical Systems---> Click on Execute Button
     go for new entries
     -System Name : ERP000
     -Description : Sending System
        -System Name : ERP800
     -Description : Receiving System
     press Enter & Save
     it will ask Request
     if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
     Select Assign Client to Logical Systems-->Execute
     000--> Double click on this
     Give the following Information
     -Client : ERP 000
     -City :
     -Logical System
     -Currency
     -Client role
     Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
     Click on Create Button
     RFC Destination Name should be same as partner's logical system name and case sensitive
     to create the ports automatically while generating the partner profiles
     give the information for required fields
     RFC Destination : ERP800
     Connection type: 3
     Description
     Target Host : ERP000
     System No:000
     lan : EN
     Client : 800
     User : Login User Name
     Password:
     save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
     click on create moduleview
     short text : xxxxxxxxxxxxxx
     Technical Neme : MODEL_ALV
     save this & Press ok
     select your just created modelview Name :'MODEL_ALV'.
     goto add message type
     Model Name : MODEL_ALV
     sender : ERP000
     Receiver : ERP800
     Message type :MATMAS
     save & Press Enter
STEP 4) Goto Tcode BD82
     Give Model View : MODEL_ALV
     Partner system : ERP800
     execute this by press F8 Button
     it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
     select the modelview
     goto >edit>modelview-->distribute
     press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
     Material : mat_001
     Message Type : MATMAS
     Logical System : ERP800
     and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
     Material : 100-300
     Message Type : MATMAS
     and Execute --> 1 request idoc created for message type Matmas
     press enter
     Here Master Idoc set for Messge type MATMAS-->press Enter
     1 Communication Idoc generated for Message Type
     this is your IDOC
Good luck and Reward me for the same
Thanks
Ashok.N

[SOLVED]Xorg.conf, mouse config problem

The Rapoo M765 mouse can not work properly under normal mouse configuration.
The mouse goes beyond controll when config as below:
hacksign@XSign [14:13:13] : ~
>> cat /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
#Section "InputClass"
# Identifier "Mouse2"
# MatchProduct "RAPOO RAPOO 2.4G Remote Mouse"
# MatchIsPointer "yes"
# MatchDevicePath "/dev/input/event*"
# Driver "mouse"
# Option "Protocol" "auto"
# Option "Emulate3Buttons" "no"
# Option "Buttons" "7"
# Option "ButtonMapping" "1 2 3 6 7"
#EndSection
When there is no any configuration, the mouse can work abnormally. Movement and right/left click work fine, but I can not use scroll wheel,and the "go forward"&"go backward" mouse key can not work too.
(I know Option "ZAxisMapping" "4 5" is the configuration of scroll wheel emulation.)
The real problem is 'mouse beyond controll',the cursor goes crazyly on screen ....
I guess it is something wrong of ButtonMapping option. But when I tried to get button number from command xev,when scroll wheel scrolles, I get something below(the scroll wheel movement is identified as a key event~):
//left click
ButtonPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3766452, (135,143), root:(2287,595),
state 0x0, button 1, same_screen YES
ButtonRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3766588, (135,143), root:(2287,595),
state 0x100, button 1, same_screen YES
//right click
ButtonPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3767716, (135,143), root:(2287,595),
state 0x0, button 3, same_screen YES
ButtonRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3767852, (135,143), root:(2287,595),
state 0x400, button 3, same_screen YES
//mouse scroll, identified as keyboard event(?)
KeyRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3769332, (135,143), root:(2287,595),
state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3769332, (135,143), root:(2287,595),
state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
here is some Information(I dont know why the mouse is identified as 'type:KEYBOARD'):
hacksign@XSign [14:55:03] : ~
>> xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ RAPOO RAPOO 2.4G Remote Mouse id=13 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=16 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Heng Yu Technology Poker Pro S id=9 [slave keyboard (3)]
↳ Heng Yu Technology Poker Pro S id=10 [slave keyboard (3)]
↳ Integrated Camera id=11 [slave keyboard (3)]
↳ RAPOO RAPOO 2.4G Remote Mouse id=12 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=17 [slave keyboard (3)]
hacksign@XSign [14:55:06] : ~
>> xinput list-props 13
Device 'RAPOO RAPOO 2.4G Remote Mouse':
Device Enabled (142): 1
Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (270): 0
Device Accel Constant Deceleration (271): 1.000000
Device Accel Adaptive Deceleration (272): 1.000000
Device Accel Velocity Scaling (273): 10.000000
Device Product ID (260): 9390, 8192
Device Node (261): "/dev/input/event8"
Evdev Axis Inversion (274): 0, 0
Evdev Axes Swap (276): 0
Axis Labels (277): "Rel X" (152), "Rel Y" (153), "Rel Horiz Wheel" (267), "Rel Dial" (268), "Rel Vert Wheel" (269)
Button Labels (278): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Up" (148), "Button Wheel Down" (149), "Button Horiz Wheel Left" (150), "Button Horiz Wheel Right" (151), "Button Side" (265), "Button Extra" (266), "Button Unknown" (263), "Button Unknown" (263), "Button Unknown" (263), "Button Unknown" (263)
Evdev Scrolling Distance (279): 1, 1, 1
Evdev Middle Button Emulation (280): 0
Evdev Middle Button Timeout (281): 50
Evdev Third Button Emulation (282): 0
Evdev Third Button Emulation Timeout (283): 1000
Evdev Third Button Emulation Button (284): 3
Evdev Third Button Emulation Threshold (285): 20
Evdev Wheel Emulation (286): 0
Evdev Wheel Emulation Axes (287): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (288): 10
Evdev Wheel Emulation Timeout (289): 200
Evdev Wheel Emulation Button (290): 4
Evdev Drag Lock Buttons (291): 0
hacksign@XSign [14:55:14] : ~
>> grep -i rapoo /var/log/Xorg.0.log
[ 29.102] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event7)
[ 29.102] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
[ 29.102] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
[ 29.102] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
[ 29.102] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event7"
[ 29.102] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
[ 29.102] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
[ 29.102] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
[ 29.102] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 12)
[ 29.103] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event8)
[ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev pointer catchall"
[ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
[ 29.103] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
[ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
[ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event8"
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found 9 mouse buttons
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found scroll wheel(s)
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found relative axes
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found x and y relative axes
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found absolute axes
[ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Forcing absolute x/y axes to exist.
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
[ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as mouse
[ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
[ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Adding scrollwheel support
[ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: YAxisMapping: buttons 4 and 5
[ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 29.103] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 13)
[ 29.104] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: initialized for relative axes.
[ 29.104] (WW) evdev: RAPOO RAPOO 2.4G Remote Mouse: ignoring absolute axes.
[ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) keeping acceleration scheme 1
[ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration profile 0
[ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration factor: 2.000
[ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration threshold: 4
[ 29.104] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/mouse0)
hacksign@XSign [14:59:47] : ~
>> yaourt -Q|grep -i 'input-'
local/xf86-input-evdev-trackpoint 2.9.1-1
extra/xf86-input-keyboard 1.8.0-3 (xorg-drivers xorg)
extra/xf86-input-mouse 1.9.1-1 (xorg-drivers xorg)
extra/xf86-input-synaptics 1.8.1-1 (xorg-drivers xorg)
Last edited by Hacksign (2015-01-14 02:22:51)

Thanks for reply !
change Driver 'mouse' to Driver 'evdev',solved cursor goes beyond controll problem.
but I still can not use scroll button and 'go forward'&'go backward' button.
(BTW:evdev_drv.so is from local/xf86-input-evdev-trackpoint, and local/xf86-input-evdev-trackpoint package is from AUR)
I think, maybe something wrong with my button number mapping, but I still can not get scroll button number with 'xev' command....
below is my configuration:
hacksign@XSign [17:15:19] : /var/log
>> cat /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
Section "InputClass"
Identifier "Mouse2"
MatchProduct "RAPOO RAPOO 2.4G Remote Mouse"
MatchIsPointer "yes"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "Protocol" "auto"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
Option "Buttons" "9"
Option "ButtonMapping" "1 2 3 6 7 8 9 4 5"
EndSection
and here is Xorg.0.log
[ 11357.287] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
[ 11357.287] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
[ 11357.287] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
[ 11357.287] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event7"
[ 11357.287] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
[ 11357.287] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
[ 11357.287] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
[ 11357.287] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:24AE:2000.0003/input/input8/event7"
[ 11357.288] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 12)
[ 11357.288] (**) Option "xkb_rules" "evdev"
[ 11357.288] (**) Option "xkb_model" "pc104"
[ 11357.288] (**) Option "xkb_layout" "us"
[ 11357.288] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event8)
[ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev pointer catchall"
[ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
[ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "Mouse2"
[ 11357.288] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
[ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
[ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event8"
[ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: ButtonMapping '1 2 3 6 7 8 9 4 5'
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found 9 mouse buttons
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found scroll wheel(s)
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found relative axes
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found x and y relative axes
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found absolute axes
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Forcing absolute x/y axes to exist.
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as mouse
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Adding scrollwheel support
[ 11357.288] (**) Option "Emulate3Buttons" "no"
[ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: YAxisMapping: buttons 4 and 5
[ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 11357.288] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:24AE:2000.0004/input/input9/event8"
[ 11357.288] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 13)
[ 11357.288] (**) Option "xkb_rules" "evdev"
[ 11357.288] (**) Option "xkb_model" "pc104"
[ 11357.288] (**) Option "xkb_layout" "us"
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: initialized for relative axes.
[ 11357.288] (WW) evdev: RAPOO RAPOO 2.4G Remote Mouse: ignoring absolute axes.
[ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) keeping acceleration scheme 1
[ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration profile 0
[ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration factor: 2.000
[ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration threshold: 4
[ 11357.289] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/mouse0)
[ 11357.289] (II) No input driver specified, ignoring this device.
[ 11357.289] (II) This device may have been added with another device file.
olive wrote:In the config file you mentioned, all is commented; do you mean that you have problems when you have uncommented it? You should not use the mouse driver (old deprecated driver) but evdev. Try to remove xf86-input-mouse and xf86-input-keyboard (same as before, this is deprecated and handled by evdev) and remove also a "joystick" driver if you have it (I have had problem with it conflicting with the evdev driver).
Last edited by Hacksign (2015-01-13 09:27:06)

FTP Adapter config problem (again :/ )

Hello all.
I know that this topic was discussed few times before but i still cant setup my FTP adapter.
My OS is Win XP. I downloaded free ftp server (XLight FTP Server) and setup my oc4j-ra.xml in following way:
     <connector-factory location="eis/Ftp/FtpAdapter" connector-name="Ftp Adapter">
     <config-property name="host" value="10.172.201.57"/>
     <config-property name="port" value="210"/>
     <config-property name="username" value="szeryf"/>
     <config-property name="password" value="szeryf"/>
     </connector-factory>
where shown ip address is my computer address. I also created user szeryf/szeryf at my local FTP server and tried to connect to that server using some ftp client - with success. Then i created some simple BPEL process to upload file to FTP server. Each time i try i get fault that connection to server failed.
Maybe someone experienced such a thing and could help me with that problem?
Regards,
Chris

Are you sure your ftp server is on port 210? It seems odd.
And is there a reason you are editing oc4j-ra.xml directly? Why not make a partner link and get that working first?

Transport abt ALE Config

Hi,
We have done all IDOC to File scenarios
We have configured the ALE settings on SAP R/3's DEv server.
Can i transport these Config to SAP R/3's QTY Server or Should i create them as it is appear in the SAP R/3's DEV server???
Regards
Suman

Hi Suman..
This was the ALE settings...
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.\
idoc to idoc
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
regards,
Kishore

Visa config. problem

Hi, everyone
I connect my device at COM1, but I cannot find that com port in serial config.
It means I cannot find any connection with my device in system manager.
I only want to use labview to control my device, even not use dll.
Anybody can figure out what problems in my situation ?
# I use vb.net to do the same thing, and it works. So I think my deivce have no problems.
Certified LabVIEW Developer

Hi, RavensFan
Com1 shows in windows device manager, but it not show my device name.
Like this picture.
So visa resource name not show "Com1".
I didn't install MAX, and I will try later and reinstall my visa driver.
thank for your reply.
Certified LabVIEW Developer

Config problem when transport

Hi Experts,
I created a Z output type in NACE in Dev system 200 client. and with this i create a process code to for my inbound IDOC partner profile. Along with this we created IDOC segments and other stuff. Now after transport I am not getting these changes reflected in TST System
How can we confirm about thr TR request number in whic TR the changes saved.
I think the possible problems are:
1. May be saved in any other TR or
2. Because of config changes are done in 200 client instead of 100 client.
I have no idea about config related things.
Can anyone please tell me about the problem and its solution
Regards,
Nik

Hi John,
Thanks for your reply. The thing is,
I dont remember, when i created the Process code for inbound IDOC did it asked for the TR, ya it must ask, but i forget the TR number. Can you please help me how to get which TR it is saved. Also the thing is when i treed creating new Process Code it is not asking me any TR. So the Posibilities i think may be it dont ask for the TR or a TR is not Transported thats y it is not asking me for the new TR.
In menu i am not getting any button which tell me about the TR in which the process code saved.
For NACE issue, i am bit confused regarding the client. Can u please explain me to add an output type in NACE, which client i have to use (100 client ?).For a new output type I used the cleint i usually work on i.e 200. and things are working fine in DEV, But when i transported all my requests to TST server, i am not able to see the output type there in TST system.
DO I NEED TO DO BOTH THINGS PROCESS CODE & NACE IN CONFIG CLIENT ??
Regards,
Nik

ALE Config

Hi,
When i am configuring the ALE in my system, i have created the logical systems, the RFC test is successful. and i have even modelled the distribution but when i try to exute the profile parameters i am getting the msg like:
Log for Partner Profile Generation
Distribution model                        No messages have been defined for the selection conditions in the model
i ignored that msg and continued with the recieving system profile parameters generation , but i got same msg....
when i try to distribute the model i am getting the error like :
Distribution of model view VENDMODEL
Target System LCDCLNT300   RFC Destination for synchronous communication ( message type SYNCH )
                                             Partner Profile LS LIDCLNT300 SYNCH doesnot exist.
                                             Generate Partner Profile
                                             or specify outbound partner profile for message type SYNCH
but i have already try to maintain partner profile for clinet 300 but i got msg.
can i know where would be the problem in my process.
Thanx & Regards,
Srinath

regarding the SYNCH problem.
You have to configure each receiving System in the SendingSystem PartnerProfiles.
Partnertype: LS (Logical System)
Sender = Sendersystem of the Distribution Model
Receiver = Receiver of the distributes Modelview.
Messagetype: SYNCH
IDoctype: SYNCHRON

ALE IDOC Problem...

HI..
I am facing a problem on the inbound side.
If I check the IDoc in WE02, I am getting a status error as
"No status record was passed to ALE by the a"
Customised IDoc is used.
Please advise if you can Thnx

HI,
IAM GIVING A DOCUMENT WHICH HELPS YOU TO UNDERSTAND EASILY AND YOURSELF CAN WORKOUT WITH THIS REAL TIME SCENARIO WHICH TRANSFERS THE DATA BETWEEN TWO SYSTEMS.
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User:      MMUSER200 (This is the logon for dist.)
Client :      200
Password:      MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG100.
Receiver as      LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG200.
Receiver as      LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as      Mechanical Engineering
Material Type as           Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time:   WE07.

LMS 4.1 multiserver config problem

I m facing a problem in multiserver configuration, in making master-slave servers.
Master server config is done, certificates are imported, SSO is also configured and all the pre-requisites given in the multiserver-config doc of lms4.1.
While making slave server from stand-alone, getting errors like "cetrificate expired" and "certificte not installed" in two different ways, putting master-server IP as master address and putting master-server domain name respectively, both snapshots are attached. My Domain name is DNS resolvable.
Anyone can help me out on this...?

You can add your custom prompts into /opt/CSCOpx/objects/cmf/data/TacacsPrompts.ini. No restart of LMS is required for the addition to be recognized.

ALE Config Problem

Similar Messages

Maybe you are looking for