500.000-1000000 IDOCs per day via XI?

We are looking to implement a project that could use XI as an interface to R/3 and BW. Initially the system would receive about 5000 files daily and convert these into 500,000 - 1,000,000 IDOCs for posting into R/3 and BW. Is anyone doing anything around this size and can you provide any advice?
Thanks in advance, Hermann

I have been involved with a scenario that transforms a handful of files from a legacy system into about 350.000 IDocs in R/3. This volume is processed in XI in about 15 minutes, but we learned some lessons before getting this to work:
We started out with a BPM performing a split mapping to go from batch files to single IDocs. This performed horribly in general and for the large volumes invariably crashed the XI server. The problem seemed to be that the workflow engine (which executes the BPM) cannot handle the large number of container elements. The way to avoid this problem is to use a simple, straight-through mapping (i.e. no BPM) and use IDoc bundling to send many IDocs as a single XI message. There is a note describing how this is done.
Based on the numbers you gave, you are looking (on average) at a single file being mapped to a bundle of 1000-2000 IDocs. I don't think this will be a problem for XI. However, we found that while XI handles these loads quite well, the R/3 system receiving the IDocs required significant tuning in order to keep up. (I don't know the details of this, so I can't elaborate.)
Best regards,
Thorsten

Similar Messages

Controlling multiple travel requests per day via schema

Hello,
I am working on Travel Management.
My client wishes that it should not be possible for any employee to raise more than one travel requests per day.
In the schema, the check box- Multiple TRs/Day is not available. I think with the help of this, maybe issue could be resolved.
I am not sure.
Can someone point out what could be missing? What should I do to control this?
Thank you.
Ruth Dhamone

I'm on NW AS 7.03 ABAP Stack 731 Level 13, ECC 606 (EHP 6) with SAP_HR 604 Level 81 and EA_HR 607 (HR-Renewal 1) Level 32 over here. Maybe they really removed it... or it's not available for the deviant Public Sector ;-/. Doesn't really matter though, we don't need it, I was just curious ;-)
Anyway, since this is not your problem (I misunderstood), there are two possibilities I can think of at the moment:
1. The Trip is still in the future, hence the Schema doesn't have to be changed and the system remains in technical Schema PL (which is unlikely in your case if the status really says "Trip Completed"). I.e. your Trip is not in the future, is it?
2. Only one of your expense Schemas qualifies for the trip. In that case the system silently defaults to that one and you don't get the option to choose from a list.
Cheers, Lukas

Please note that i am seeking some assistance with adding the followng resource: A maximum of 4 resources can be added at an additional cost of $500 per day per resource.

Hi, Please note that i am seeking some assistance with adding the following resource to a task in Microsoft Project 2010:
A maximum of 4 resources can be added at an additional cost of $500 per day per resource.

Hi Clemence,
Your post has quite little details, but as far as I understand, you want to add 4 resources on a task, each resource costing 500$ a day. Since it is not mentionned if it is generic resources (skill or role) or named resources, I'll assume that it is generic
resources. Based on this understanding, here is a proposal:
Go to the resource sheet,
Create a work generic resource ("type" field set to "work", "generic" field to "yes"), typing in the resource name field the skill name,
In the max unit field, enter 400% for 4 resources (for just 4 if your Project 2010 is configured to display units in decimals),
Since the rate is an hourly rate, make the calculation : 500$ per day / 8 hours a day = 62,5$ per hour,
Go back to the Gantt Chart, split the window (click "detail" in the view tab of the ribbon),
Select your task and assign the newly created resource with a given % units.
Hope this helps.
Guillaume Rouyre - MBA, MCP, MCTS

JDBC Inbound to separate IDOCS per Row instead of one single IDOC?

Hello everyone,
I'm currently working on the migration of our old B1iSN 8.8 scenarios to B1iSN 9.0.
The scenario is the following: I have a SQL table with data and a separate control table where I store the date of the last run/data retrieval. My JDBC Inbound is triggered every day and the SQL Statement selects all new data between now and the last run. The process flow only consists of one transformation Atom which builds my custom idoc structure.
In B1iSN 8.8 I've got one IDOC per row from the resultset. In the B1 9.0 outbound all rows are now withing one single IDOC. How can I trigger that separate IDOCS are created!?
I've already tried the "Block Size" Setting. When I set it to "1" I get for two datasets two output IDOCS. However all data is in IDOC 1 and the second IDOC is empty. What is wrong here? How can I access the data in the current block? I currently use a "for each" on the normal jdbc resultset rows.
I'm testing it at the moment with flat file output as our target system is not accessible yet, but I suppose this is not the reason?
Thanks in advacne for any help.

Hello André,
please use a two-step approach with two integration scenarios:
DB INBOUND -> VOID OUTBOUND
INTERNAL QUEUE INBOUND -> ECC OUTBOUND
In step one add a condtion including a for-each loop into your integration flow.
Within this for-each please hand over for each IDoc you want to create into a second integration step via "Internal queue":
The second step is triggered x-times via internal queue and does the field mapping into IDoc format.
Best regards
Bastian
P.S.: with this approach, you can keep the block processing setting for DB INBOUND to an higher amount.

Mac Mini Restarting Multiple times per day

I have a Mac Mini from Sept 2010. Recently upgraded to Mountain Lion and now the restarts due to an issue several times per day. The computer is fine when i am using it, but the issue comes up when i return to wake the monitor by hitting a key or moving the mouse. Sleep is disabled, but the monitor is set to turn off after 10 minutes of inactivity. Sometimes it will be fine left for hours on its own and other times when i come back to the computer, I am met with a gray screen stating the computer had to restart.
Below is the log from the last crash:
Jan 26 06:52:06 MacMini kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=895[GoogleSoftwareUp] clearing CS_VALID
Jan 26 07:05:48 MacMini.local com.apple.usbmuxd[27]: _handle_timer heartbeat detected detach for device 0x82-192.168.1.2:0!
Jan 26 07:07:40 MacMini.local LKDCHelper[909]: Starting (uid=501)
Jan 26 07:17:51 MacMini com.apple.launchd.peruser.501[134] (com.apple.KerberosHelper.LKDCHelper[909]): Exited with code: 1
Jan 26 07:50:49 MacMini kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=926[GoogleSoftwareUp] clearing CS_VALID
Jan 26 08:07:40 MacMini.local LKDCHelper[951]: Starting (uid=501)
Jan 26 08:17:51 MacMini com.apple.launchd.peruser.501[134] (com.apple.KerberosHelper.LKDCHelper[951]): Exited with code: 1
Jan 26 08:47:52 MacMini.local com.apple.usbmuxd[27]: _handle_timer heartbeat detected detach for device 0x95-192.168.1.2:0!
Jan 26 08:49:32 MacMini kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=973[GoogleSoftwareUp] clearing CS_VALID
Jan 26 08:59:57 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/30: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/126: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/157: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/164: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/165: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not look up channel/token: com.apple.time/0x165: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Bug: 12C60: libxpc.dylib + 36100 [FAC04D8B-680E-325F-8F0C-DD69859D0E01]: 0x3
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/168: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/172: 0x3: No such process
Jan 26 08:59:59 --- last message repeated 7 times ---
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/176: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/178: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not look up channel/token: com.apple.time/0x178: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Bug: 12C60: libxpc.dylib + 36100 [FAC04D8B-680E-325F-8F0C-DD69859D0E01]: 0x3
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/178: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/180: 0x3: No such process
Jan 26 08:59:59 --- last message repeated 1 time ---
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/185: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/190: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/194: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/195: 0x3: No such process
Jan 26 08:59:59 --- last message repeated 2 times ---
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not look up channel/token: com.apple.time/0x195: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Bug: 12C60: libxpc.dylib + 36100 [FAC04D8B-680E-325F-8F0C-DD69859D0E01]: 0x3
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/195: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/196: 0x3: No such process
Jan 26 08:59:59 --- last message repeated 1 time ---
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not look up channel/token: com.apple.time/0x196: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Bug: 12C60: libxpc.dylib + 36100 [FAC04D8B-680E-325F-8F0C-DD69859D0E01]: 0x3
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/196: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/198: 0x3: No such process
Jan 26 08:59:59 --- last message repeated 10 times ---
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not look up channel/token: com.apple.time/0x198: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Bug: 12C60: libxpc.dylib + 36100 [FAC04D8B-680E-325F-8F0C-DD69859D0E01]: 0x3
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/198: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/200: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not look up channel/token: com.apple.time/0x200: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Bug: 12C60: libxpc.dylib + 36100 [FAC04D8B-680E-325F-8F0C-DD69859D0E01]: 0x3
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/200: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/201: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not look up channel/token: com.apple.time/0x202: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/202: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Bug: 12C60: libxpc.dylib + 36100 [FAC04D8B-680E-325F-8F0C-DD69859D0E01]: 0x3
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/202: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/210: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/215: 0x3: No such process
Jan 26 08:59:59 MacMini.local UserEventAgent[137]: Could not get event name for stream/token: com.apple.time/220: 0x3: No such process
Jan 26 09:07:39 MacMini.local LKDCHelper[999]: Starting (uid=501)
Jan 26 09:08:37 MacMini.local WindowServer[87]: handle_will_sleep_auth_and_shield_windows: no lock state data
Jan 26 09:10:33 MacMini.local CVMServer[101]: Check-in to the service com.apple.cvmsCompAgent_x86_64 failed. This is likely because you have either unloaded the job or the MachService has the ResetAtClose attribute specified in the launchd.plist. If present, this attribute should be removed.
Jan 26 09:11:04 --- last message repeated 1 time ---
Jan 26 09:20:53 localhost bootlog[0]: BOOT_TIME 1359210053 0
Any help would be appreciated, as this happens multiple times a day.

Thanks for the reply, den.thed.
I tried the first suggestion, resetting the SMC, but after this the problem continues.
I think the issue is related to the second, kernel panicking.
As for suggestions 3 and 4, i have my energy settings as you show in your post, with monitor sleep after 15 minutes, computer sleep never and none of the options checked. While the computer does not sleep, this is only an issue when i step away from the computer for a while and come back, not when i am actively using it.
The latest error message is as follows, and seems to indicate a kernel panic (or several).
Interval Since Last Panic Report: 112486 sec
Panics Since Last Report:          7
Anonymous UUID:                    67206185-78EF-3547-FDBF-AFC3D867EDFE
Sat Jan 26 14:22:44 2013
panic(cpu 1 caller 0xffffff8002cb7bd5): Kernel trap at 0xffffff7f83801a58, type 0=divide error, registers:
CR0: 0x000000008001003b, CR2: 0x0000000109d21000, CR3: 0x00000000058bf000, CR4: 0x0000000000000660
RAX: 0x00015025a5a86800, RBX: 0x0000000000000000, RCX: 0x00000000092dd698, RDX: 0x0000000000000000
RSP: 0xffffff800ada3000, RBP: 0xffffff800ada3090, RSI: 0x0000000000000000, RDI: 0xffffff800fcbc004
R8: 0xffffff800ada2f94, R9: 0x00000000092dd698, R10: 0x00000000000061a8, R11: 0x0000000000000002
R12: 0xffffff8067b91da0, R13: 0xffffff800f1c2004, R14: 0x000000000000000a, R15: 0xffffff800fcbc004
RFL: 0x0000000000010246, RIP: 0xffffff7f83801a58, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000109d21000, Error code: 0x0000000000000000, Fault CPU: 0x1
Backtrace (CPU 1), Frame : Return Address
0xffffff800ada2ca0 : 0xffffff8002c1d626
0xffffff800ada2d10 : 0xffffff8002cb7bd5
0xffffff800ada2ee0 : 0xffffff8002cce4ed
0xffffff800ada2f00 : 0xffffff7f83801a58
0xffffff800ada3090 : 0xffffff7f837faefb
0xffffff800ada3140 : 0xffffff7f837dbefc
0xffffff800ada3180 : 0xffffff7f837ddcf1
0xffffff800ada3330 : 0xffffff7f837e0294
0xffffff800ada3380 : 0xffffff7f838c8ba1
0xffffff800ada34c0 : 0xffffff7f838cef2e
0xffffff800ada3510 : 0xffffff7f835d9659
0xffffff800ada3540 : 0xffffff7f834c383b
0xffffff800ada35e0 : 0xffffff7f8348c3f7
0xffffff800ada3610 : 0xffffff7f834bf23d
0xffffff800ada3800 : 0xffffff7f834c03a2
0xffffff800ada38d0 : 0xffffff7f836b415a
0xffffff800ada3900 : 0xffffff7f836b05ce
0xffffff800ada3920 : 0xffffff7f836af158
0xffffff800ada39a0 : 0xffffff7f836ababb
0xffffff800ada39c0 : 0xffffff7f8369f704
0xffffff800ada3a30 : 0xffffff7f836b5851
0xffffff800ada3ae0 : 0xffffff7f836aa61c
0xffffff800ada3c60 : 0xffffff7f834563c7
0xffffff800ada3cd0 : 0xffffff7f8344057b
0xffffff800ada3d40 : 0xffffff7f834431b8
0xffffff800ada3db0 : 0xffffff7f83442db4
0xffffff800ada3e10 : 0xffffff7f83409c04
0xffffff800ada3e50 : 0xffffff7f83408eef
0xffffff800ada3e80 : 0xffffff7f834082cb
0xffffff800ada3ef0 : 0xffffff80030472a8
0xffffff800ada3f30 : 0xffffff8003045daa
0xffffff800ada3f80 : 0xffffff8003045ed9
0xffffff800ada3fb0 : 0xffffff8002cb26b7
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f833fb000->0xffffff7f83432fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f8324c000
         com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f8343e000->0xffffff7f8344ffff
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f833fb000
            dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f8324c000
         com.apple.NVDAResman(8.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f83452 000->0xffffff7f83754fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f8324c000
            dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f8343e000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f833fb000
         com.apple.nvidia.nv50hal(8.0)[9F3D09B5-3158-3D9E-BDA3-E71576AAD3B7]@0xffffff7f8 3762000->0xffffff7f83a84fff
            dependency: com.apple.NVDAResman(8.0.0)[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f834 52000
            dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f8324c000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12C60
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide:     0x0000000002a00000
Kernel text base: 0xffffff8002c00000
System model name: Macmini4,1 (Mac-F2208EC8)
System uptime in nanoseconds: 9708470052980
last loaded kext at 3660329715313: com.apple.filesystems.afpfs          10.0 (addr 0xffffff7f84f16000, size 348160)
last unloaded kext at 1940466153095: com.apple.driver.AppleUSBCDC          4.1.22 (addr 0xffffff7f84ef5000, size 12288)
loaded kexts:
com.Cycling74.driver.Soundflower          1.5.1
com.iospirit.driver.rbiokithelper          1.8.0
com.antecea.driver.AnteceaAudioDrv          1.0.0
com.apple.filesystems.afpfs          10.0
com.apple.nke.asp_tcp          7.0.0
com.apple.filesystems.smbfs          1.8
com.apple.driver.AppleIntelProfile          97
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.driver.AppleBluetoothMultitouch          75.15
com.apple.iokit.IOBluetoothSerialManager          4.0.9f33
com.apple.driver.AGPM          100.12.69
com.apple.driver.ApplePlatformEnabler          2.0.5d4
com.apple.driver.AppleHDA          2.3.1f2
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.0.9f33
com.apple.driver.AppleMikeyDriver          2.3.1f2
com.apple.driver.AudioAUUC          1.60
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.ApplePolicyControl          3.2.11
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.AppleUpstreamUserClient          3.5.10
com.apple.driver.AppleMCCSControl          1.0.33
com.apple.GeForce          8.0.0
com.apple.filesystems.autofs          3.0
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          34
com.apple.iokit.SCSITaskUserClient          3.5.1
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.2.2
com.apple.driver.AppleUSBHub          5.2.5
com.apple.iokit.AppleBCM5701Ethernet          3.2.5b3
com.apple.driver.AppleUSBOHCI          5.2.5
com.apple.driver.AppleFWOHCI          4.9.6
com.apple.driver.AppleSDXC          1.2.2
com.apple.driver.AirPort.Brcm4331          602.15.22
com.apple.driver.AppleAHCIPort          2.4.1
com.apple.driver.AppleUSBEHCI          5.4.0
com.apple.driver.AppleEFINVRAM          1.6.1
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleHPET          1.7
com.apple.driver.AppleACPIButtons          1.6
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.6
com.apple.driver.AppleAPIC          1.6
com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
com.apple.nke.applicationfirewall          4.0.39
com.apple.security.quarantine          2
com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
com.apple.security.SecureRemotePassword          1.0
com.apple.driver.AppleProfileTimestampAction          97
com.apple.driver.AppleProfileThreadInfoAction          97
com.apple.driver.AppleProfileRegisterStateAction          97
com.apple.driver.AppleProfileReadCounterAction          97
com.apple.driver.AppleProfileKEventAction          97
com.apple.driver.AppleProfileCallstackAction          97
com.apple.iokit.AppleProfileFamily          97
com.apple.driver.AppleBluetoothHIDKeyboard          165.5
com.apple.driver.AppleHIDKeyboard          165.5
com.apple.driver.IOBluetoothHIDDriver          4.0.9f33
com.apple.driver.AppleMultitouchDriver          235.28
com.apple.iokit.IOSerialFamily          10.0.6
com.apple.driver.DspFuncLib          2.3.1f2
com.apple.iokit.IOFireWireIP          2.2.5
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.0.9f33
com.apple.iokit.IOSurface          86.0.3
com.apple.iokit.IOBluetoothFamily          4.0.9f33
com.apple.iokit.IOAudioFamily          1.8.9fc10
com.apple.kext.OSvKernDSPLib          1.6
com.apple.driver.AppleGraphicsControl          3.2.11
com.apple.driver.AppleHDAController          2.3.1f2
com.apple.iokit.IOHDAFamily          2.3.1f2
com.apple.driver.AppleSMBusPCI          1.0.10d0
com.apple.driver.AppleSMC          3.1.4d2
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.driver.IOPlatformPluginFamily          5.2.0d16
com.apple.driver.AppleSMBusController          1.0.10d0
com.apple.nvidia.nv50hal          8.0.0
com.apple.NVDAResman          8.0.0
com.apple.iokit.IONDRVSupport          2.3.5
com.apple.iokit.IOGraphicsFamily          2.3.5
com.apple.kext.triggers          1.0
com.apple.iokit.IOUSBHIDDriver          5.2.5
com.apple.driver.AppleUSBMergeNub          5.2.5
com.apple.driver.AppleUSBComposite          5.2.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.1
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.iokit.IOAHCISerialATAPI          2.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.1
com.apple.iokit.IOUSBUserClient          5.2.5
com.apple.iokit.IOEthernetAVBController          1.0.2b1
com.apple.driver.NVSMU          2.2.9
com.apple.iokit.IOFireWireFamily          4.5.5
com.apple.iokit.IO80211Family          500.15
com.apple.iokit.IONetworkingFamily          3.0
com.apple.iokit.IOAHCIFamily          2.2.1
com.apple.iokit.IOUSBFamily          5.4.0
com.apple.driver.AppleEFIRuntime          1.6.1
com.apple.iokit.IOHIDFamily          1.8.0
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          220
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.DiskImages          344
com.apple.iokit.IOStorageFamily          1.8
com.apple.driver.AppleKeyStore          28.21
com.apple.driver.AppleACPIPlatform          1.6
com.apple.iokit.IOPCIFamily          2.7.2
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0
Model: Macmini4,1, BootROM MM41.0042.B03, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.65f2
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334648302D4346382020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334648302D4346382020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.81.22)
Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: TOSHIBA MK5055GSXF, 500.11 GB
Serial ATA Device: OPTIARC DVD RW AD-5680H
USB Device: hub_device, 0x0409 (NEC Corporation), 0x005a, 0x24100000 / 2
USB Device: iPhone, apple_vendor_id, 0x12a0, 0x26200000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x06500000 / 2
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06600000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0x06630000 / 4

OS X freezes few times per day

Hello. I've a problem with my Macbook Pro Retina 15". Few times per day system freeze. After freeze and manual reboot (power button) sometimes system have a problem with boot (i need turn on and off few times). Now i check in logs when i open Diablo 3 and have something like this:
24.07.2014 17:56:59,158 WindowServer[135]: CGXMuxCapture: Starting
24.07.2014 17:56:59,158 WindowServer[135]: CGXMuxCapture: Acquired
24.07.2014 17:56:59,159 WindowServer[135]: Display 0x4280642 captured by conn 0x1cc8f
24.07.2014 17:56:59,202 Diablo III[28354]: *** WARNING: Method convertPointFromBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.
24.07.2014 17:56:59,394 Diablo III[28354]: *** WARNING: Method convertRectToBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.
24.07.2014 17:57:31,000 kernel[0]: NVDA(OpenGL): Channel exception! Exception type = 0x8 DMA Engine Error (FIFO Error 8)
24.07.2014 17:57:31,000 kernel[0]: 4443564e 00000118 88c93bc5 01f794e7 00000001 00000014 d3793533 46d3a4a6
24.07.2014 17:57:31,000 kernel[0]: 4614f297 e71edccf 00088301 000000e1 12f2500a 081d0a4d 1002a0ad 20001801
24.07.2014 17:57:31,000 kernel[0]: 30002800 02803800 0c828040 00500048 00601258 01080d22 808e8010 81042202
24.07.2014 17:57:31,000 kernel[0]: 22188093 1001080d 02808a84 9c820422 0e2268b4 84100108 22028180 80a6b805
24.07.2014 17:57:31,000 kernel[0]: 030a0880 0a00149a 1f138222 41100008 81200218 9b862808 5000480c 60015802
24.07.2014 17:57:31,000 kernel[0]: 78007064 01019000 0a000198 00138a03 13923d0a 24380a3a 0e000000 01000000
24.07.2014 17:57:31,000 kernel[0]: 490000e0 0100000f 49000000 0000000b 47000000 ff000304 ff000000 ff000000
24.07.2014 17:57:31,000 kernel[0]: ff000000 ff000000 ff000000 0a000000 1d13c220 00100008 e480a818 12200bf7
24.07.2014 17:57:31,000 kernel[0]: 03300828 a7a6a038 0dd7b0b6 48028040 00000000 4443564e
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to start of command buffer processing!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,000 kernel[0]: NVDA: Unable to make context resident prior to adding drawable to channel!
24.07.2014 17:57:31,000 kernel[0]: NVDA: Calling glrKillClient for task 0xffffff8044c190c0
24.07.2014 17:57:31,835 WindowServer[135]: CGXMuxCapture: Released
24.07.2014 17:57:31,835 WindowServer[135]: Display 0x4280642 released by conn 0x1cc8f
24.07.2014 17:58:18,000 bootlog[0]: BOOT_TIME 1406217498 0

The logic board is defective and must be replaced under warranty.

Messages per day in XI

HI,
Is there any transaction code where I can get the Statistics of Messages exchanged in XI on daily basis, for a month or more.
We have more than 50,000 messages being exchanged daily. Its hard to find the statistics in SXMB_MONI...So looking for a transaction...
Regards,
Vasu

Hi,
of course you can do it:
open runtime workbench and go to
<b>performance monitor</b>
from there you can see everything:
messages per day, week etc
one interface per day, week etc
aggegated messages etc
Regards,
michal

Indesign CS5 Buggy Crashes Many times per day

I manage to crash CS5 at least 10 times per day. Cut and paste from one layter to another seems to do it alot. Running on a new Core I7 machine. Very disappointed. CS4 rarely crashed. Also I wish Adobe would focus on performace of their programs. CS5 has a few marginal things over 4 but to Adobe performance never seems to matter.
Rob

There are quite a few document elements I've ran into that were valid in CS3 layouts that InDesign CS5 will not copy and paste. I've not ran into any elements created in CS5 that didn't copy and paste expected.
Generally I've found it to be elements that were never meant to be text frames that have been converted to text frames via the text tool click to create frame option. It's mostly when elements that should have been type on path through that tool being created as a frame.
Also, though this forum occasionally has some venting is generally support oriented. This late into CS5 most people aren't really concerned with the relative displeasure of new users. Getting used to it is the best way and someone may come along with the link to the feature request for to vote for what you want to see. I'll sympathize that things aren't going to get better and performance is likely to continue to degrade, that much of the new stuff is designed for next generation hardware and won't perform even on great hardware now, such as live screen drawing and not making me swear with files that used to not make me swear (particularly EPS which although I know is dead is very much alive in the history of a 20+ year old art departments past files).

Debugging customized function module when Idoc is triggered via ALE

Hi,
Whenever we save the billing document, an outbound idoc is triggered via ALE. The logic for the data to be included in the idoc is written in a customized function module.
However we are making some changes and would like to include some more data in the idoc. But we find that when we put a breakpoint in the function module, on saving the billing document, the flow does not stop at the break point. We are 100% sure that the code in the function module gets executed based on the data in the idoc.
How do we get into debug mode and break the flow in the function module so that we can debug in the function module?
Any help would be greatly appreciated.
Thanks in advance,
Mick

Hi Mick, this might be of some help 4 u.
ALE IDOC
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 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view
This is Receiving system Settings
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
Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors
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
1) System Name : ERP000
Description : Sending System
2) 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
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
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)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
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
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
cheers,
Hema.

Start JDBC Receiver channel twice per day

Hello,
I need to get some piece of data from Oracle database twice per day. For example at 12:00am and 12:00pm. Standard JDBC Receiver channel has no needed settings. It has only "poll interval" without exact time.
I can set up "poll interval" to 12 hours, but this can't guarantee that JDBC receiver channel will works only twice per day. For example after XI system restart JDBC adapter loses time counter. It means that JDBC adapter can starts more than 2 times per day.
I have only one idea at this moment.
I can create ABAP program which can be planned as ABAP job at needed time and with needed period.
This program should send some dummy message to Integration Engine. Integration Engine should start some Integration Process which can read data from Oracle database via JDBC channel.
What else opportunities are?
Thanks.
Best regards,
Eugeny

Message deleted
Message was edited by: Shabarish Vijayakumar

Adobe Muse CC Crashing 5x per day

We have a team of 6 designers using Adobe Muse CC on a daily basis to build simple sites as well as complex prototypes.
We work off a corporate server, this is a requirement and cannot operate locally on our own hard drives.
Each of us are reporting multiple Muse crashes per day from various actions such as:
Switching between Design & Preview views.
Simply opening a page to edit it.
Attempting to Export...
Attempting to Place an object...
As well as other random actions.
We are all using v7.2, Build 232, CL 779928
AIR Runtime: 4.0.0.1390
Awaiting response from Adobe staff before supplying detailed information. But this is getting to a point where we are researching alternative tools - I'd rather have Adobe staff provide a chance to correct these issues for us since we have multiple subscriptions and a lengthy investment into the tool.
Thanks

If what you're encountering is the "DBCW/assertTheDataBaseFileIsUnchange- Database file has been modified externally." error, there is no workaround other than working on the files locally.
Code was added in Muse 7.0 that protects against simultaneous access of a Muse file from two separate computers, since that can result in a corrupt and unrepairable .muse file. The code that was added turned out to be incompatible with some file servers, leading to the error mentioned above, or variants thereof.
We spent a considerable amount of time attempting to come up with a way to make the current approach serve it's intended purpose while avoiding this incompatiblity, but ultimately had to give up on the original approach. We're currently in the process of implementing an entirely different approach to preventing simultaneous access to a .muse file on top of some significant architectural changes underway for Muse 8.
Until the release of Muse 8, you're only viable workaround is to copy the .muse file to a local drive prior to working on it in Muse.
All Muse subscribers who can accept the terms of the Non-disclosure Agreement are invited to join the Private Beta Program via the Help menu in Muse. At present the Beta program is dormant, but it will start back up again in a few weeks with the first alpha/beta release of Muse 8. It would be extremely helpful if you could test with a beta of Muse 8 on your specific file server configuration to confirm this bug is fully resolved when working with your configuration.

500,000 views with typekit in the CC

I saw that the typekit in the creative cloud includes 500,000 views. Is there any FAQ that shows how much extra 1,000,000 views would cost? Is it 500,000 views per site with 5 of the includes sites, or 500,000 total views between all 5 sites?
I may be totally confused as to what this means, so I apologize if my question doesnt make sense.
Thanks

this might help:- https://typekit.com/plans

Win7 64bit w/Chrome, Firefox, IE, Maxthon, Opera - Flash Crashes 10+ Per Day

First up, I did the steps on this forum post: http://forums.adobe.com/message/5143120#5143120 -- All drivers and updates are current and up to date. Here is the computer I have via 'msinfo32' under run command:
OS Name
Microsoft Windows 7 Home Premium
Version
6.1.7601 Service Pack 1 Build 7601
Other OS Description
Not Available
OS Manufacturer
Microsoft Corporation
System Name
PRIVATE ON THIS FORUM
System Manufacturer
Dell Inc.
System Model
Inspiron 580
System Type
x64-based PC
Processor
Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz, 3200 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date
Dell Inc. A07, 11/13/2010
SMBIOS Version
2.6
Windows Directory
C:\Windows
System Directory
C:\Windows\system32
Boot Device
\Device\HarddiskVolume2
Locale
United States
Hardware Abstraction Layer
Version = "6.1.7601.17514"
User Name
PRIVATE ON THIS FORUM
Time Zone
Central Daylight Time
Installed Physical Memory (RAM)
8.00 GB
Total Physical Memory
7.80 GB
Available Physical Memory
3.46 GB
Total Virtual Memory
15.6 GB
Available Virtual Memory
10.3 GB
Page File Space
7.80 GB
Page File
C:\pagefile.sys
QUESTION:
I constantly use in-browser flash. And I've tried quite a few browsers, computers, different computers with differnent operating systems. They've all done the same thing. CRASH. Over, and over, and over again. 10 times or more per day. Yes, I play the Facebook games, but I also use it for in-browser radio/video. It is one of the most annoying things I've ever had to endure on a computer. If there was something else I could use, I'd already downloaded it and deleted Adobe Flash. But since there really isn't anything at the moment, I'm stuck having to write this up and hope that there is a fix. There are thousands with this issue online. If I find a fix here, I will gladly share it with every person I know.
But back to the issue. Whether I have one tab open, or twenty. Flash crashes about every 20-30 minutes. Every now and then, it'll hit an hour. I've also turned off Google Chrome's built-in flash and vise versa. I've gone through so many helps and fixes online it's not even funny. If there's any kind of fix that I can do that will stop all these crashes, I would appreciate this very much. I can't list every little detail I've ever done on this forum, but I will tell you if I have already tried anything that is said here. I hope someone says something new and we can get this thing fixed.
--Oh yeah, and this has gone on since my computer was an hour old. Back a couple years ago. Back a couple wipes ago.. I've factory reset 3 times I believe since I got this computer. Don't ask, just how I am. Junk happens and from time to time I like to wipe it all out. Just how I do. I have external drives so everything gets backed up and becomes rather easy to wipe my computer.

I couldn't have written it better myself. I did exactly what is talked about here and feel exactly the same way,
QUESTION:
I constantly use in-browser flash. And I've tried quite a few browsers, computers, different computers with differnent operating systems. They've all done the same thing. CRASH. Over, and over, and over again. 10 times or more per day. Yes, I play the Facebook games, but I also use it for in-browser radio/video. It is one of the most annoying things I've ever had to endure on a computer. If there was something else I could use, I'd already downloaded it and deleted Adobe Flash. But since there really isn't anything at the moment, I'm stuck having to write this up and hope that there is a fix. There are thousands with this issue online. If I find a fix here, I will gladly share it with every person I know.
But back to the issue. Whether I have one tab open, or twenty. Flash crashes about every 20-30 minutes. Every now and then, it'll hit an hour. I've also turned off Google Chrome's built-in flash and vise versa. I've gone through so many helps and fixes online it's not even funny. If there's any kind of fix that I can do that will stop all these crashes, I would appreciate this very much. I can't list every little detail I've ever done on this forum, but I will tell you if I have already tried anything that is said here. I hope someone says something new and we can get this thing fixed.

Number of collect calls per day

is there a limit of collect calls you can recieve per day? my boyfriends has tried to call and he gets a messge sayin the call can not go thru due to a limit?

Hi,
This you can get by running the below query on the ICM DB.
select count (*) as amt,ANI from Route_Call_Detail
where DateTime > '2013-02-28 00:00:00.000'
and DateTime < '2013-02-28 23:59:59.000'
group by ANI
Regards
Sandeep

Edge Transport Server Limitations - messages delivered per day?

I'm currently on the hunt for some kind of baseline / benchmark that will indicate how many messages per day (or per second) an Edge Transport server is capable of handling. I feel like this should be in some whitepaper somewhere for when Edge Transport
is designed, so you know how many to deploy, but I can't find it.
I know system specs will be a factor. We have the current hardware in our box:
2 processors (2.67 GHz)
16 GB RAM
64-bit OS (Windows Server 2008 R2 Enterprise)
If anyone has come across any kind of guideline for email delivery limitations of ET, I'd appreciate being pointed to them.
Thanks

The current Exchange servers are much faster and beefier than they were when I worked with Exchange 4 Beta 2 with a customer many years ago. They tried to swamp their Exchange server (dual 90 MHz Pentium server with 128 MB RAM) using six Unix workstations
running Mailstorm against it. They had to stop when their primary Unix systems handling inbound email were overloaded due to how they set up their test. And the Exchange server never skipped a beat.
Another customer situation that may help is that I have seen 10,000 messages in an Exchange 2010 queue (due the smart host they were using for external delivery was offline for maintenance) drop to zero within 15 minutes. I'd suggest that you run some
sort of test of your own to determine how many messages your edge is capable of delivering, but these may give you an indication of the expected capabilities.

500.000-1000000 IDOCs per day via XI?

Similar Messages

Maybe you are looking for