Application Engine inbound Process

Hi all,
am new from peoplesoft.
anyone knows how to write application Engine inbound process.
please let me know.
Thanks in advance.
Regards
RS

Hey Inbound threw Application engine is a simple process
take a new file layout from application designer
drag & drop your record into file lay out definition page
go to Preview panel & select segment (your record) name , browse the flat file
go to properties -- use -- File Layout Format check exel format ok
drag your file layout into AE actions ,automatically it generates code. now Run or else use this code
Define a file,array,string,record
Assign values to the above using functions GetFile , CreateArrayRept , text file for string,GetRecord .
Check the file status open using IsOpen ,read the first value of flat file using ReadLine
Push the text into array ,next step split
assign to the record field values Local File &myfile;
Local array of string &myarray;
Local string &text;
Local Record &rec;
&myfile = GetFile("C:\Documents and Settings\Administrator\Desktop\office.txt", "r", %FilePath_Absolute);
&myarray = CreateArrayRept("", 0);
&rec = CreateRecord(Record.IN1_TBL);
If &myfile.IsOpen Then
While &myfile.ReadLine(&text);
&myarray.Push(&text);
&myarray = Split(&text, ",");
&rec.IN1_NAME.Value = &myarray [1];
&rec.IN1_LOCATION.Value = &myarray [2];
&rec.Insert();
End-While;
End-If;
&myfile.Close();

Similar Messages

  • Application Engine Server process dies on Windows

    Hi experts,
    We developed an AE in which employee data will be calculated and inserted to HR core table via CI. We started multiple instance of the AE by people code, most of them will success but others run into error and reported "Process XXX is marked 'Initiated' or 'Processing' but no longer running.". On further research we found the windows process (PSAESRV) died and a folder named PSAESRV.PID was generated in process scheduler log directory. The following can be found in "process_state.txt" in the directory:
    Exception: (0xC0000005) EXCEPTION_ACCESS_VIOLATION - Memory access violation
    (The memory at 0x00133000 could not be read)
    Exception location:
    Fault address=0x2500b836 0001:0000a836 C:\PT850\BIN\SERVER\WINX86\pscmnutils.dll
    Other information:
    Tools: 8.50
    Server:Windows XP SP3.
    Database:Oracle 10.2.0.1.0.
    Could any one figure out what's the problem?
    Edited by: user9546195 on 2010-12-7 下午10:32

    Yes it's running on Windows XP professional. We run the test both in Linux Server and Windows XP.  So far no error has been found in Linux Server.  We began performance test and found the error on Windows XP on April,2010. Then we refine the code and test again these days, and the error happens again with the same error message.
    *Not sure whether the Peopletools is up-to-date or not, the version of modules can be found in the "process_state.txt" file of the dead process. Attached below is the file.
    Thanks!
    Crash report file opened as 'C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT\LOGS\PSAESRV.6604\process_state.txt'
    ==================================================================================
    Process state report - Start
    Local Time: Wed Dec 08 13:40:55 2010
    UTC Time: Wed Dec 08 05:40:55 2010
    Timezone: China Standard Time
    ==================================================================================
    ==================================================================================
    Process information
    Process ID: 6604
    ==================================================================================
    System information:
    Architecture: x86
    OS Name: Windows
    OS Version: XP Professional (Kernel 5.1, Build 2600, Service Pack 3)
    OS Parameters: %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16
    Physical memory: 3327MB total, 243MB available
    Paging space: 6319MB total, 868MB available
    ==================================================================================
    Process diagnostics - Start
    ==================================================================================
    Stack Trace
    Stack trace for process ID: 6604
    Thread 3400 (Exception thread):
    Address Frame Function Arguments Module!Symbol Name
    0x2500b836 0x0012f8b4 0x16219ada 0x03c24ca8 0x01940e58 0x2500d746 EXP pscmnutils!CWriteFrame::Copy+0xf6
    0x2500cab7 0x0012f8fc 0x197eeda0 0x0572d250 0x0572d250 0x0012f94c EXP pscmnutils!CWriteFrame::FlushSecondaryAttachList+0x87
    0x28102666 0x0012f91c 0x0012f970 0000000000 0x0012f958 0x2810d7ce EXP psnetapi!CNetSendMsg::~CNetSendMsg+0x76
    0x28102723 0x0012f92c 0x00000001 0x197eede4 0x01940e58 0000000000 EXP psnetapi!CNetSendMsg::~CNetSendMsg+0x133
    0x2810d7ce 0x0012f958 0x273a8f13 0x01940e58 0x01970a70 0x01214448 EXP psnetapi!CNetReqRepSvc::~CNetReqRepSvc+0xfe
    0x004014a5 0x0012fb7c 0x01940e58 0x273a8fdf 0x0193f8a8 0x0121b250 *** PSAESRV!<symbol>
    0x00401c38 0x0012fbb0 0x01940e58 0x01214448 0x0193d750 0x0121b250 *** PSAESRV!<symbol>
    0x6046776e 0x0012fc58 0x0121b250 0x0012fcd8 0x03452198 0x00000001 EXP LIBTUX!tmsvcdsp+0xc4e
    0x604847fb 0x0012fca8 0x0121b250 0x0012fcd8 0000000000 0x0121db68 EXP LIBTUX!tmrcvrq+0x73b
    0x6048a1a9 0x0012fcfc 0000000000 0x7c93003d 0000000000 0x0012fd20 EXP LIBTUX!tmrunserver+0xe19
    0x7c930021 0x0012fd04 0000000000 0x0012fd20 0000000000 0x0012fd28 EXP ntdll!RtlFreeHeap+0x114
    <Invalid stack frame detected: Frame address 0000000000 should be higher than 0x0012fd04>
    0x7c93003d 0000000000 0000000000 0000000000 0000000000 0000000000 EXP ntdll!RtlFreeHeap+0x130
    Thread 17664:
    Address Frame Function Arguments Module!Symbol Name
    0x7c92e4f4 0x01ccff44 0x00000002 0x01ccff6c 0000000000 0x000493e0 EXP ntdll!KiFastSystemCallRet+0x0
    0x77dc8601 0x01ccffb4 0000000000 0x7c93428f 0000000000 0000000000 EXP ADVAPI32!WmiFreeBuffer+0x24e
    0x7c80b713 0x01ccffec 0x77dc845a 0000000000 0000000000 0x00000032 EXP kernel32!GetModuleFileNameA+0x1b4
    Thread 31556:
    Address Frame Function Arguments Module!Symbol Name
    0x7c92e4f4 0x03c23ac4 0xffffffff 0000000000 0x03c23ae8 0x29712bab EXP ntdll!KiFastSystemCallRet+0x0
    0x7c802455 0x03c23ad4 0xffffffff 0x4cff1a68 0x0121cab0 0x03c24204 EXP kernel32!Sleep+0xf
    0x29712bab 0x03c23ae8 0xffffffff 0000000000 0x18b31bb3 0x00000057 EXP pspal!PSPAL_GetThread+0x11b
    0x297011cc 0x03c24204 0x2971a970 0x2971a5a8 0x00000241 0x2971a9ac EXP pspal!<symbol>
    0x29705515 0x03c24240 0x03c24844 0000000000 0x781778f1 0x00000057 EXP pspal!PSPAL_GetExceptionHandler+0xc25
    0x29705c32 0x03c24258 0x03c24844 0x18b31c1b 0000000000 0x7c885780 EXP pspal!PSPAL_GetExceptionHandler+0x1342
    0x29706502 0x03c245ac 0x03c24844 0000000000 0000000000 0000000000 EXP pspal!PSPAL_GetExceptionHandler+0x1c12
    0x7c864031 0x03c2481c 0x03c24844 0x7c839b21 0x03c2484c 0000000000 EXP kernel32!UnhandledExceptionFilter+0x1c7
    0x7c83ab38 0x03c2ffec 0x7813286e 0x0341cba0 0000000000 0x00000008 EXP kernel32!ValidateLocale+0x1328
    ==================================================================================
    Loaded Modules
    Base Version Name
    0x00400000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\PSAESRV.exe
    0x7C920000 5.01.2600.5512 C:\WINDOWS\system32\ntdll.dll
    0x7C800000 5.01.2600.5512 C:\WINDOWS\system32\kernel32.dll
    0x60420000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBTUX.dll
    0x78130000 8.00.50727.4053 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_e6967989\MSVCR80.dll
    0x77BE0000 7.00.8638.5512 C:\WINDOWS\system32\msvcrt.dll
    0x60D90000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBENGINE.dll
    0x71A40000 5.01.2600.5512 C:\WINDOWS\system32\WSOCK32.dll
    0x71A20000 5.01.2600.5512 C:\WINDOWS\system32\WS2_32.dll
    0x77DA0000 5.01.2600.5512 C:\WINDOWS\system32\ADVAPI32.dll
    0x77E50000 5.01.2600.6015 C:\WINDOWS\system32\RPCRT4.dll
    0x77FC0000 5.01.2600.5834 C:\WINDOWS\system32\Secur32.dll
    0x71A10000 5.01.2600.5512 C:\WINDOWS\system32\WS2HELP.dll
    0x77D10000 5.01.2600.5512 C:\WINDOWS\system32\USER32.dll
    0x77EF0000 5.01.2600.5512 C:\WINDOWS\system32\GDI32.dll
    0x60D30000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBFML.dll
    0x60D10000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBFML32.dll
    0x60C90000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBGICONV.dll
    0x60EE0000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBBUFT.dll
    0x10000000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBUTRACE.dll
    0x76990000 5.01.2600.5512 C:\WINDOWS\system32\ole32.dll
    0x29700000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pspal.dll
    0x29600000 1.10.0000.0000 C:\PT850\BIN\SERVER\WINX86\TRIO.dll
    0x7D590000 6.00.2900.6018 C:\WINDOWS\system32\SHELL32.dll
    0x77F40000 6.00.2900.5912 C:\WINDOWS\system32\SHLWAPI.dll
    0x76BC0000 5.01.2600.5512 C:\WINDOWS\system32\PSAPI.DLL
    0x03000000 6.09.0003.0113 C:\PT850\BIN\SERVER\WINX86\dbghelp.dll
    0x77BD0000 5.01.2600.5512 C:\WINDOWS\system32\VERSION.dll
    0x7C420000 8.00.50727.4053 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_e6967989\MSVCP80.dll
    0x00430000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psaesrvutils.dll
    0x25000000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pscmnutils.dll
    0x76B10000 5.01.2600.5512 C:\WINDOWS\system32\WINMM.dll
    0x30E00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pspetssl.dll
    0x00470000 C:\PT850\BIN\SERVER\WINX86\PSLIBEAY32.dll
    0x00550000 1.02.0002.0000 C:\PT850\BIN\SERVER\WINX86\zlib1.dll
    0x28100000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psnetapi.dll
    0x29800000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\PSJNI.dll
    0x27E00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psmt.dll
    0x25200000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pscompat.dll
    0x24A00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psbtunicode.dll
    0x24F00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pscmn.dll
    0x005E0000 7.18.0001.0000 C:\PT850\BIN\SERVER\WINX86\libpscurl.dll
    0x00630000 C:\PT850\BIN\SERVER\WINX86\PSSSLEAY32.dll
    0x12000000 C:\PT850\BIN\SERVER\WINX86\xerces-depdom_2_6.dll
    0x00680000 2.05.0000.0000 C:\PT850\BIN\SERVER\WINX86\xerces-c_2_6.dll
    0x2B700000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psperfagent.dll
    0x692E0000 5.00.2195.4952 C:\PT850\BIN\SERVER\WINX86\pdh.dll
    0x76320000 6.00.2900.5512 C:\WINDOWS\system32\comdlg32.dll
    0x5D170000 5.82.2900.5512 C:\WINDOWS\system32\COMCTL32.dll
    0x770F0000 5.01.2600.5512 C:\WINDOWS\system32\OLEAUT32.dll
    0x60530000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBTMIB.dll
    0x606C0000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBQM.dll
    0x606B0000 C:\FUSION\TUXEDO10GR3_VS2005\BIN\LIBQS.dll
    0x24600000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psappeng.dll
    0x24D00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psbufapi.dll
    0x2DC00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pssys.dll
    0x27700000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psmath.dll
    0x27A00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psmgr.dll
    0x2CD00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pssam.dll
    0x27D00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psmsf.dll
    0x2AF00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pspceval.dll
    0x00940000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psdbgutils.dll
    0x2B000000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pspcm.dll
    0x25C00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psfinmth.dll
    0x2C500000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pspubsub.dll
    0x27200000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pskeystore.dll
    0x30600000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psxmldoc.dll
    0x009C0000 1.09.0000.0000 C:\PT850\BIN\SERVER\WINX86\Xalan-C_1_9.dll
    0x00C20000 C:\PT850\BIN\SERVER\WINX86\XalanMessages_1_9.dll
    0x26800000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psintbrkr.dll
    0x26C00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psiobase.dll
    0x26D00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psiocls.dll
    0x3E410000 7.00.6000.17080 C:\WINDOWS\system32\WININET.dll
    0x00C70000 6.00.5441.0000 C:\WINDOWS\system32\Normaliz.dll
    0x3EAB0000 7.00.6000.17080 C:\WINDOWS\system32\iertutil.dll
    0x00C80000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\PSAPIAdapter.DLL
    0x25E00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psflr.dll
    0x29100000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psoptshared.dll
    0x2D200000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psqastransfer.dll
    0x27500000 C:\PT850\BIN\SERVER\WINX86\psls.dll
    0x2C300000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pspsm.dll
    0x2CC00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psrenutil.dll
    0x2A900000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pspageutil.dll
    0x29F00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psstflsrvutils.dll
    0x29D00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psbamparser.dll
    0x30F00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pswrkrt.dll
    0x782E0000 8.00.50727.4053 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_b77cec8e\MFC80U.DLL
    0x24500000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psapmsg.dll
    0x29B00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psstatecore.dll
    0x2A100000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psbamutil.dll
    0x29900000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psstateutil.dll
    0x29200000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psoptutil.dll
    0x2AA00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pspams.dll
    0x00DD0000 11.00.0001.0000 C:\PT850\BIN\SERVER\WINX86\cplex110.dll
    0x2D100000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psqasutil.dll
    0x2D400000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psserver.dll
    0x011B0000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pstcagent.dll
    0x2EA00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pstcproxy.dll
    0x76300000 5.01.2600.5512 C:\WINDOWS\system32\IMM32.DLL
    0x62C20000 5.01.2600.5512 C:\WINDOWS\system32\LPK.DLL
    0x73FA0000 1.420.2600.5969 C:\WINDOWS\system32\USP10.dll
    0x77180000 6.00.2900.6028 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\comctl32.dll
    0x5DBA0000 5.01.2600.5512 C:\WINDOWS\system32\rdpsnd.dll
    0x762D0000 5.01.2600.5512 C:\WINDOWS\system32\WINSTA.dll
    0x5FDD0000 5.01.2600.5694 C:\WINDOWS\system32\NETAPI32.dll
    0x2D300000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\pssecurity.dll
    0x5D360000 8.00.50727.4053 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_0ccc058c\MFC80CHS.DLL
    0x60130000 10.03.0000.0000 C:\fusion\tuxedo10gR3_VS2005\bin\registry.dll
    0x25700000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\PSORA.dll
    0x01FF0000 10.02.0000.0000 D:\ORACLE\BIN\OCI.dll
    0x7C340000 7.10.3052.0004 C:\WINDOWS\system32\MSVCR71.dll
    0x61C20000 10.02.0000.0000 D:\oracle\bin\OraClient10.Dll
    0x60870000 10.02.0000.0000 D:\oracle\bin\oracore10.dll
    0x60A80000 10.02.0000.0000 D:\oracle\bin\oranls10.dll
    0x63690000 10.02.0000.0000 D:\oracle\bin\oraunls10.dll
    0x01F30000 10.02.0000.0000 D:\oracle\bin\orauts.dll
    0x636B0000 10.02.0000.0000 D:\oracle\bin\oravsn10.dll
    0x60FA0000 10.02.0000.0000 D:\oracle\bin\oracommon10.dll
    0x02050000 10.02.0000.0000 D:\oracle\bin\orageneric10.dll
    0x63430000 10.02.0000.0000 D:\oracle\bin\orasnls10.dll
    0x025B0000 10.02.0000.0000 D:\oracle\bin\oraxml10.dll
    0x01F40000 7.00.2600.5512 C:\WINDOWS\system32\MSVCIRT.dll
    0x60960000 10.02.0000.0000 D:\oracle\bin\oran10.dll
    0x62740000 10.02.0000.0000 D:\oracle\bin\oranl10.dll
    0x62790000 10.02.0000.0000 D:\oracle\bin\oranldap10.dll
    0x627F0000 10.02.0000.0000 D:\oracle\bin\orannzsbb10.dll
    0x62530000 10.02.0000.0000 D:\oracle\bin\oraldapclnt10.dll
    0x62670000 10.02.0000.0000 D:\oracle\bin\orancrypt10.dll
    0x62920000 10.02.0000.0000 D:\oracle\bin\oranro10.dll
    0x626B0000 10.02.0000.0000 D:\oracle\bin\oranhost10.dll
    0x62660000 10.02.0000.0000 D:\oracle\bin\orancds10.dll
    0x629C0000 10.02.0000.0000 D:\oracle\bin\orantns10.dll
    0x02710000 10.02.0000.0000 D:\oracle\bin\orapls10.dll
    0x02A70000 10.02.0000.0000 D:\oracle\bin\oraslax10.dll
    0x63080000 10.02.0000.0000 D:\oracle\bin\oraplp10.dll
    0x61ED0000 10.02.0000.0000 D:\oracle\bin\orahasgen10.dll
    0x62AB0000 10.02.0000.0000 D:\oracle\bin\oraocr10.dll
    0x62B20000 10.02.0000.0000 D:\oracle\bin\oraocrb10.dll
    0x62980000 10.02.0000.0000 D:\oracle\bin\orantcp10.dll
    0x02A80000 10.02.0000.0000 D:\oracle\bin\orasql10.dll
    0x719C0000 5.01.2600.5512 C:\WINDOWS\system32\mswsock.dll
    0x02DD0000 5.01.2600.5512 C:\WINDOWS\system32\hnetcfg.dll
    0x71A00000 5.01.2600.5512 C:\WINDOWS\System32\wshtcpip.dll
    0x71F00000 5.01.2600.5512 C:\WINDOWS\system32\security.dll
    0x77C40000 5.01.2600.5876 C:\WINDOWS\system32\msv1_0.dll
    0x76760000 5.01.2600.5512 C:\WINDOWS\system32\cryptdll.dll
    0x76D30000 5.01.2600.5512 C:\WINDOWS\system32\iphlpapi.dll
    0x2BE00000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psppr.dll
    0x02F80000 C:\PT850\BIN\SERVER\WINX86\PSUSER.DLL
    0x76FA0000 2001.12.0000.4414 C:\WINDOWS\system32\CLBCATQ.DLL
    0x77020000 2001.12.0000.4414 C:\WINDOWS\system32\COMRes.dll
    0x28700000 8.50.0000.0000 C:\PT850\BIN\SERVER\WINX86\psoftapi.dll
    0x55300000 4.00.0001.0002 C:\PT850\BIN\SERVER\WINX86\pdflib.dll
    Process diagnostics - End
    ==================================================================================
    ==================================================================================
    Internal process state - Start
    ==================================================================================
    Abort message:
    Unrecoverable exception received
    ==================================================================================
    Exception context:
    Exception record:
    Exception: (0xC0000005) EXCEPTION_ACCESS_VIOLATION - Memory access violation
    (The memory at 0x00133000 could not be read)
    Exception is continuable
    Machine context:
    eip:2500b836
    eflags:00210283
    system: [ ID:1 VIP:0 VIF:0 AC:0 VM:0 RF:1 NT:0 IOPL:0 IF:1 TF:0 ]
    status: [ OF:0 SF:1 ZF:0 AF:0 PF:0 CF:1 ]
    control: [ DF:0 ]
    cs:001b ds:0023 es:0023 fs:003b gs:0000 ss:0023
    eax:00002386 ebx:16219a00 ecx:00133000 edx:3eb0003a
    esi:0572d250 edi:0012e8e4 ebp:0012f8b4 esp:0012f8a8
    fpcw:027f [ X:0 RC:0(nearest) PC:2(double) PM:1 UM:1 OM:1 ZM:1 DM:1 IM:1 ]
    fpsw:0120 [ B:0 C3:0 TOP:0 C2:0 C1:0 C0:1 ES:0 SF:0 PE:1 UE:0 OE:0 ZE:0 DE:0 IE:0 ]
    fptw:ffff
    fip:001b:2b70cc0d
    fdp:0023:0012e9f0
    st0:000078141fe4fffffffc (empty) 0
    st1:0000781420637c8097d0 (empty) 0
    st2:00270000000700000000 (empty) nan
    st3:2e58781c19f800000000 (empty) nan
    st4:00000000000000d7fa01 (empty) 0
    st5:000000d7f90460e65d5b (empty) 0
    st6:400ec547000000000000 (empty) 50503
    st7:00000000000000000000 (empty) 0
    mm0:78141fe4fffffffc
    :fffffffc 78141fe4
    :fffc ffff 1fe4 7814
    :fc ff ff ff e4 1f 14 78
    mm1:781420637c8097d0
    :7c8097d0 78142063
    :97d0 7c80 2063 7814
    :d0 97 80 7c 63 20 14 78
    mm2:0000000700000000
    :00000000 00000007
    :0000 0000 0007 0000
    :00 00 00 00 07 00 00 00
    mm3:781c19f800000000
    :00000000 781c19f8
    :0000 0000 19f8 781c
    :00 00 00 00 f8 19 1c 78
    mm4:0000000000d7fa01
    :00d7fa01 00000000
    :fa01 00d7 0000 0000
    :01 fa d7 00 00 00 00 00
    mm5:00d7f90460e65d5b
    :60e65d5b 00d7f904
    :5d5b 60e6 f904 00d7
    :5b 5d e6 60 04 f9 d7 00
    mm6:c547000000000000
    :00000000 c5470000
    :0000 0000 0000 c547
    :00 00 00 00 00 00 47 c5
    mm7:0000000000000000
    :00000000 00000000
    :0000 0000 0000 0000
    :00 00 00 00 00 00 00 00
    mxcsr:00001f80 [ FZ:0 RC:0 PM:1 UM:1 OM:1 ZM:1 DM:1 IM:1 DAZ:0 PE:0 UE:0 OE:0 ZE:0 DE:0 IE:0 ]
    xmm0:00000000000000000000000000000000
    :00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    :0000 0000 0000 0000 0000 0000 0000 0000
    :00000000 00000000 00000000 00000000
    :0000000000000000 0000000000000000
    : 0.000000e+00 0.000000e+00 0.000000e+00 0.000000e+00
    : 0.000000000000000e+00 0.000000000000000e+00
    xmm1:00660020007300730065006300630061
    :61 00 63 00 63 00 65 00 73 00 73 00 20 00 66 00
    :0061 0063 0063 0065 0073 0073 0020 0066
    :00630061 00650063 00730073 00660020
    :0065006300630061 0066002000730073
    : 9.091850e-39 9.275524e-39 1.056124e-38 9.367265e-39
    : 9.345982464254671e-307 9.790542281716366e-307
    xmm2:0020007200650073007500200072006f
    :6f 00 72 00 20 00 75 00 73 00 65 00 72 00 20 00
    :006f 0072 0020 0075 0073 0065 0072 0020
    :0072006f 00750020 00650073 00200072
    :007500200072006f 0020007200650073
    : 1.046940e-38 1.074480e-38 9.275546e-39 2.938896e-39
    : 1.869105501982261e-306 4.450631538595433e-308
    xmm3:0067006e0061006800630020006f0074
    :74 00 6f 00 20 00 63 00 68 00 61 00 6e 00 67 00
    :0074 006f 0020 0063 0068 0061 006e 0067
    :006f0074 00630020 00610068 0067006e
    :00630020006f0074 0067006e00610068
    : 1.019390e-38 9.091759e-39 8.908189e-39 9.459210e-39
    : 8.455497966197594e-307 1.023608670170218e-306
    xmm4:00610070002000650068007400200065
    :65 00 20 00 74 00 68 00 65 00 20 00 70 00 61 00
    :0065 0020 0074 0068 0065 0020 0070 0061
    :00200065 00680074 00200065 00610070
    :0068007400200065 0061007000200065
    : 2.938877e-39 9.551054e-39 2.938877e-39 8.908200e-39
    : 1.068114220898795e-306 7.566011645531745e-307
    xmm5:0020002e00640072006f007700730073
    :73 00 73 00 77 00 6f 00 72 00 64 00 2e 00 20 00
    :0073 0073 0077 006f 0072 0064 002e 0020
    :00730073 006f0077 00640072 0020002e
    :006f007700730073 0020002e00640072
    : 1.056124e-38 1.019391e-38 9.183709e-39 2.938800e-39
    : 1.379626599065753e-306 4.450342947103102e-308
    xmm6:00610063002000720065007300550020
    :20 00 55 00 73 00 65 00 72 00 20 00 63 00 61 00
    :0020 0055 0073 0065 0072 0020 0063 0061
    :00550020 00650073 00200072 00610063
    :0065007300550020 0061006300200072
    : 7.806062e-39 9.275546e-39 2.938896e-39 8.908182e-39
    : 9.346091108988483e-307 7.565923370506860e-307
    xmm7:006100200079006c006e006f0020006e
    :6e 00 20 00 6f 00 6e 00 6c 00 79 00 20 00 61 00
    :006e 0020 006f 006e 006c 0079 0020 0061
    :0020006e 006e006f 0079006c 00610020
    :006e006f0020006e 006100200079006c
    : 2.938890e-39 1.010206e-38 1.111225e-38 8.908088e-39
    : 1.335119688726395e-306 7.565468423830832e-307
    ==================================================================================
    Exception location:
    Fault address=0x2500b836 0001:0000a836 C:\PT850\BIN\SERVER\WINX86\pscmnutils.dll
    ==================================================================================
    Process information
    Process name: PSAESRV
    Command line: PSAESRV -C dom=PSNT_58039 -g 101 -i 3 -u XIAOWEI2-CN -U "C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT\LOGS\TUXLOG" -m 0 -R 15612 -o .\LOGS\stdout -e .\LOGS\stderr -- -CD HC91PT -S PSAESRV
    Process ID: 6604
    Parent process ID: 2680
    Process owner: NT AUTHORITY\SYSTEM
    Desktop: \Sessions\0\Windows\WindowStations\WinSta0\Desktops\Default
    ==================================================================================
    Thread information
    Current thread ID: 3400
    ==================================================================================
    Virtual Memory
    Virtual memory: 2047MB total, 1508MB available
    ==================================================================================
    Environment Variables
    ALLUSERSPROFILE=C:\Documents and Settings\All Users
    APPDATA=C:\Documents and Settings\Administrator\Application Data
    APPDIR=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT
    APP_PW=PS
    BDMCONFIG=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\HC91PT\PSBDMCFG
    CLIENTNAME=Console
    COMMONPROGRAMFILES=C:\Program Files\Common Files
    COMPUTERNAME=XIAOWEI2-CN
    COMSPEC=C:\WINDOWS\system32\cmd.exe
    DEFLOGDIR=C:\Documents and Settings\All Users\Application Data\McAfee\DesktopProtection
    FIELDTBLS=tpadm
    FLDTBLDIR=C:\fusion\tuxedo10gR3_VS2005\udataobj
    FP_NO_HOST_CHECK=NO
    HOMEDRIVE=C:
    HOMEPATH=\Documents and Settings\Administrator
    JAVA_OPTS="-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Xms32m -Xmx64m"
    JAVA_PLUGIN_WEBCONTROL_ENABLE=1
    LD_LIBRARY_PATH=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT;C:\fusion\tuxedo10gR3_VS2005\lib;\lib;\user\lib;
    LOGONSERVER=\\XIAOWEI2-CN
    NLSPATH=C:\fusion\tuxedo10gR3_VS2005\locale\C
    NUMBER_OF_PROCESSORS=2
    ORACLE_HOME=D:\oracle
    ORACLE_SID=HC91PT
    OS=Windows_NT
    PATH=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT;C:\fusion\tuxedo10gR3_VS2005\bin;\bin;C:\PT850\bin\server\winx86;C:\PT850\jre\bin\client;D:\ORACLE\BIN;C:\WINDOWS;C:\WINDOWS\SYSTEM32;C:\PT850\verity\winx86\_nti40\bin
    PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
    PERL5LIB=D:\oracle\perl\5.8.3\lib\MSWin32-x86;D:\oracle\perl\5.8.3\lib;D:\oracle\perl\5.8.3\lib\MSWin32-x86;D:\oracle\perl\site\5.8.3;D:\oracle\perl\site\5.8.3\lib;D:\oracle\sysman\admin\scripts;
    PMID=XIAOWEI2-CN
    PROCESSOR_ARCHITECTURE=x86
    PROCESSOR_IDENTIFIER=x86 Family 6 Model 23 Stepping 10, GenuineIntel
    PROCESSOR_LEVEL=6
    PROCESSOR_REVISION=170a
    PROGRAMFILES=C:\Program Files
    PROMPT=$P$G
    PSAPPSERVSTARTUP=N
    PS_CFG_HOME=C:\Documents and Settings\Administrator\psft\pt\8.50
    PS_HOME=C:\PT850
    PS_MACH=XIAOWEI2-CN
    PS_SERVDIR=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT
    PS_SERVER_CFG=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT\psprcs.cfg
    SESSIONNAME=Console
    SYSTEMDRIVE=C:
    SYSTEMROOT=C:\WINDOWS
    TEMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
    TMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
    TUXCONFIG=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT\PSTUXCFG
    TUXDIR=C:\fusion\tuxedo10gR3_VS2005
    UBBCONFIG=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT\psprcsrv.ubb
    USERDOMAIN=XIAOWEI2-CN
    USERNAME=Admin
    USERPROFILE=C:\Documents and Settings\Administrator
    VIEWDIR=C:\fusion\tuxedo10gR3_VS2005\udataobj
    VIEWFILES=mib_views.VV,tmib_views.VV
    VSEDEFLOGDIR=C:\Documents and Settings\All Users\Application Data\McAfee\DesktopProtection
    WINDIR=C:\WINDOWS
    NTSYMBOL_PATH=C:\PT850\bin\server\winx86
    TUXOFFSET=0
    ULOGPFX=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT\LOGS\TUXLOG
    PS_NLS_LANG=SIMPLIFIED CHINESE_CHINA.ZHS16GBK
    NLS_LANG=SIMPLIFIED CHINESE_CHINA.UTF8
    PS_COBOLTYPE=U
    PSPRCSLOGDIR=C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT\log_output\AE_HR_CPI_POST_1820
    ==================================================================================
    Execution Options
    Global flags: 0x00000000
    ==================================================================================
    Application state
    PeopleTools process state
    Writing PeopleTools state to C:\Documents and Settings\Administrator\psft\pt\8.50\appserv\prcs\HC91PT\LOGS\PSAESRV.6604\peopletools_state.txt
    ERROR: Timed out waiting for internal process state
    Internal process state - End
    ==================================================================================
    Process state report - End
    ==================================================================================

  • Parallel process in Application engine

    could any one explain me what is parallel process in Application engine where temp table is use?
    give me with example?

    Parallel processing is used when considerable amounts of data must be updated or processed within a limited amount of time, or batch window. In most cases, parallel processing is more efficient in environments containing partitioned data.
    To use parallel processing, partition the data between multiple concurrent runs of a program, each with its own dedicated version of a temporary table (for example, PS_MYAPPLTMP). If you have a payroll batch process, you could divide the employee data by last name. For example, employees with last names beginning with A through M get inserted into PS_MYAPPLTMP1; employees with last names beginning with N-Z get inserted into PS_MYAPPLTMP2.
    To use two instances of the temporary table, you would define your program (say, MYAPPL) to access to one of two dedicated temporary tables. One execution would use A-M and the other N-Z.
    The Application Engine program invokes logic to pick one of the available instances. After each program instance gets matched with an available temporary table instance, the %Table meta-SQL construct uses the corresponding temporary table instance. Run control parameters passed to each instance of the MYAPPL program enable it to identify which input rows belong to it, and each program instance inserts the rows from the source table into its assigned temporary table instance using %Table. The following diagram illustrates this process:
    Multiple program instances running against multiple temporary table instances
    There is no simple switch or check box that enables you to turn parallel processing on and off. To implement parallel processing, you must complete the following set of tasks. With each task, you must consider details regarding your specific implementation.
    Define and save temporary table records in PeopleSoft Application Designer.
    You don't need to run the SQL Build process at this point.
    In PeopleSoft Application Engine, assign temporary tables to Application Engine programs, and set the instance counts dedicated for each program.
    Employ the %Table meta-SQL construct so that PeopleSoft Application Engine can resolve table references to the assigned temporary table instance dynamically at runtime.
    Set the number of total and online temporary table instances on the PeopleTools Options page.
    Build temporary table records in PeopleSoft Application Designer by running the SQL Build process.

  • Sending Inbound application log error in inbound processing through email

    Hello all,
    My client wants application log for failed idoc through E-mail.(The application log found in we05 for failed idocs).
    Please guide me how to get/fetch the error log in inbound processing.
    Thank you.
    Edited by: Sanjay_lnt on Feb 9, 2010 5:32 AM

    Hi,
    Query EDIDS table with the relevant selection criteria like date.
    Here field STATXT will give you the message text. REPLACE the place holders(&) with STAPA1, STAPA2, STAPA3 and STAPA4 to build the complete message.
    Make sure that you read the message for the latest counter(Check Max counter in field COUNTER). Because same IDOC can have multiple messages.
    Once you get the message, you can use normal mail sending code for sendingout the mails.
    Thanks,
    Vinod.
    Edited by: Vinod Vemuru on Feb 9, 2010 11:21 AM

  • What happnes when we run any Application Engine Process

    Hi All,
    I have been trying to find the exact flow after we run application engine program either from PIA or from command line and got few resources also which explain what happnes behind the scene but due to mix explanations I am still not clear about it.
    Could any one please explain in steps the flow behind the scene after we run a application engine?
    To be more specific, Like when we run it, the process name along with other parameters(runcontrol, sessionid, process intance) must be written into some table and then Process monitor displays that process and updates its status frequenlty.....
    I hope you got my points..
    Thanks in advance!!

    Please query the records PS_PMN_PRCSLIST and PS_AERUNCONTROL to find the data about an app engine status

  • Inbound processing is not happening for XMG integration

    Currently our project deals with B2B and XMG integration
    We are able to send outbound messages to B2B from XMG successfully.
    For Inbound messages
    1. B2B is picking up payload
    2. Identifying Agreement
    3. Decrypting and verifies digital signature
    but could not deliver the message to ECX_INQUEUE
    Log
    ====
    2008.02.06 at 07:04:32:292: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:getIdentificationExpression Enter
    2008.02.06 at 07:04:32:293: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:getIdentificationExpression idexp = /*[local-name()='envelope']/*[local-name()='itemSyncResponse']
    2008.02.06 at 07:04:32:293: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:getIdentificationExpression Exit
    2008.02.06 at 07:04:32:307: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:processIncomingDocument Exit
    2008.02.06 at 07:04:32:308: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
    2008.02.06 at 07:04:32:308: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
    2008.02.06 at 07:04:32:308: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
    2008.02.06 at 07:04:32:309: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
    2008.02.06 at 07:04:32:309: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
    2008.02.06 at 07:04:32:309: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
    2008.02.06 at 07:04:32:312: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2008.02.06 at 07:04:32:312: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
    2008.02.06 at 07:04:32:316: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
    2008.02.06 at 07:04:32:316: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2008.02.06 at 07:04:32:317: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
    2008.02.06 at 07:04:32:319: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
    2008.02.06 at 07:04:32:322: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2008.02.06 at 07:04:32:322: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
    2008.02.06 at 07:04:32:327: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
    2008.02.06 at 07:04:32:333: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name Oracle Development
    2008.02.06 at 07:04:32:333: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value AS2 Identifier0060974050142
    2008.02.06 at 07:04:32:334: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2008.02.06 at 07:04:32:334: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryTradingPartnerIdentificationType
    2008.02.06 at 07:04:32:336: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryTradingPartnerIdentificationType
    2008.02.06 at 07:04:32:337: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2008.02.06 at 07:04:32:364: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: createBusinessMessageReceiverInter
    2008.02.06 at 07:04:32:367: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: createBusinessMessageReceiverInter
    2008.02.06 at 07:04:32:367: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
    2008.02.06 at 07:04:32:373: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2008.02.06 at 07:04:32:374: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
    2008.02.06 at 07:04:32:377: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
    2008.02.06 at 07:04:32:381: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = <[email protected]_te>
    2008.02.06 at 07:04:32:382: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
    ** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
    2008.02.06 at 07:04:32:383: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2008.02.06 at 07:04:32:383: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: updateWireMessage
    2008.02.06 at 07:04:32:387: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: updateWireMessage
    2008.02.06 at 07:04:32:387: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:continueRequest Collaboration Control not required ..continuing Request processing
    2008.02.06 at 07:04:32:388: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
    2008.02.06 at 07:04:32:388: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
    2008.02.06 at 07:04:32:388: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW2008.02.06 at 07:04:32:389: Thread-10: B2B - (DEBUG) : Wed Feb 06 07:04:32 PST 2008 Converting B2B message to ECX message..
    2008.02.06 at 07:04:32:389: Thread-10: B2B - (DEBUG) : Wed Feb 06 07:04:32 PST 2008 Inbound - B2BtoECX - Enter
    2008.02.06 at 07:04:32:389: Thread-10: B2B - (DEBUG) : Wed Feb 06 07:04:32 PST 2008 B2B Message -2008.02.06 at 07:04:32:389: Thread-10: B2B - (DEBUG) : COLLABORATION_NAME : null2008.02.06 at 07:04:32:390: Thread-10: B2B - (DEBUG) : ACTION_NAME : M4U_SRC_ITEM_SYNC_RESP
    2008.02.06 at 07:04:32:390: Thread-10: B2B - (DEBUG) : DOCUMENT_TYPE : M4U_SRC_ITEM_SYNC_RESP
    2008.02.06 at 07:04:32:390: Thread-10: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : 1.0
    2008.02.06 at 07:04:32:390: Thread-10: B2B - (DEBUG) : SOURCE_NAME : 1Sync-AS2
    2008.02.06 at 07:04:32:391: Thread-10: B2B - (DEBUG) : DESTINATION_NAME : Oracle Development
    2008.02.06 at 07:04:32:392: Thread-10: B2B - (DEBUG) : PAYLOAD : <Payload Goes Here>
    2008.02.06 at 07:04:32:393: Thread-10: B2B - (DEBUG) : Wed Feb 06 07:04:32 PST 2008 ECX Message -
    2008.02.06 at 07:04:32:393: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null2008.02.06 at 07:04:32:393: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
    2008.02.06 at 07:04:32:617: Thread-10: B2B - (ERROR) Error -: AIP-50903: Message "8C57CE13117EF46D5340000013A02150-1" retry count is zero
    at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:325)
    at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:275)
    at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:589)
    at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:428)
    at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:357)
    at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1693)
    at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2007)
    at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1939)
    at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1897)
    at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
    at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
    at java.lang.Thread.run(Thread.java:595)
    2008.02.06 at 07:04:32:618: Thread-10: B2B - (ERROR) Error -: AIP-50903: Message "8C57CE13117EF46D5340000013A02150-1" retry count is zero
    at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:325)
    at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:275)
    at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:589)
    at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:428)
    at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:357)
    at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1693)
    at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2007)
    at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1939)
    at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1897)
    at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
    at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
    at java.lang.Thread.run(Thread.java:595)
    2008.02.06 at 07:04:32:621: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
    2008.02.06 at 07:04:32:621: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
    2008.02.06 at 07:04:32:626: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
    2008.02.06 at 07:04:32:627: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
    2008.02.06 at 07:04:32:627: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:notifyApp retry value <= 0, so sending exception to IP_IN_QUEUE
    2008.02.06 at 07:04:32:627: Thread-10: B2B - (DEBUG) Engine:notifyApp Enter
    2008.02.06 at 07:04:32:630: Thread-10: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
    <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <correlationId>null</correlationId>
    <b2bMessageId>8C57CE13117EF46D5340000013A02150-1</b2bMessageId>
    <errorCode>AIP-50903</errorCode>
    <errorText>Message "8C57CE13117EF46D5340000013A02150-1" retry count is zero</errorText>
    <errorDescription>
    <![CDATA[Machine Info: (ap6003idmz.us.oracle.com)^M
    Message "8C57CE13117EF46D5340000013A02150-1" retry count is zero  ]]>
    </errorDescription>
    <errorSeverity>2</errorSeverity>
    </Exception>
    Following doc - protocol parameters are set for failed message
    =================================================
    Identification Expression (XPath) for XML Document : /*[local-name()='envelope']/*[local-name()='itemSyncResponse']
    Document Routing ID : b2buser1
    Inbound Process Type : M4U_SRC
    Inbound Process Subtype : ITEM_SYNC_RESPONSE
    Outbound Process Type : M4U_SRC
    Outbound Process Subtype : ITEM_SYNC_RESPONSE
    Inbound Party Code : Internal
    DTD/XSD Namespace Conversion :NONE
    Please advise us.
    Thanks
    Praveen

    Hello,
    Plese make sure that the ECX queues are present and are appropriately refferred from the Delivery Channel in B2B UI. I will request one of my team memeber to work with you if the issue still persists.
    Rgds,Ramesh

  • Error while Smart Sync inbound processing

    Hi all,
    I´m running MI 2.5 SP14 Patch 03.
    My application works fine, but after synchronization I get the following message:
    Exception while proccessing method SMARTSYNC : java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException : Error while Smart Sync inbound processing: java.lang.NullPointerException
    The data are booked correctly, but the exception is thrown on the client. What´s wrong?
    Thanks & regards,
    Barbara

    Hi jo,
    the whole trace file follows:
    I ***** LOG / TRACE SWITCHED ON 
    I ***** Mobile Engine version: MI 25 SP 13 Patch 05 Build 200510140658 
    I ***** Current timezone: Europe/Berlin 
    I Trace severity: Info (70) 
    I Synchronize with backend called, Thread=Thread-33 
    I Thread=Thread-33 took lock for synchronization. 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956071B2A13B82E100000086F78463 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429 
    I Skip performing Sync Event (0) com.sap.ip.me.core.StatusUpdater for conversation id MI544553545f55534552 / 43A083B699AE3B82E100000086F78463 (User: TEST_USER, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    I SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429 
    I AppLog severity: Warning (60) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713CB2A13B82E100000086F78463 
    I Saved Smart Sync outbound message for conversation id 4395713CB2A13B82E100000086F78463:  
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802475AA13B82E100000086F78463 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B96D8D3B82E100000086F78463 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.core.StatusUpdater on ConversationId MI46414c5445524d4549455242 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId MI2853484152454429 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.core.RegistryInboundProcessingLog$RegistryInboundProcessingLogSyncEventListener on ConversationId MI2853484152454429 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956070B2A13B82E100000086F78463 
    I Saved Smart Sync outbound message for conversation id 43956070B2A13B82E100000086F78463:  
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713DB2A13B82E100000086F78463 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.core.StatusUpdater for conversation id MI505545545a4b41554c / 43803A5EFBBB3102E100000086F78463 (User: PUETZKAUL, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802465AA13B82E100000086F78463 
    I Saved Smart Sync outbound message for conversation id 439802465AA13B82E100000086F78463:  
    I Saved Smart Sync outbound message for conversation id 439802465AA13B82E100000086F78463:  
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B86D8D3B82E100000086F78463 
    I Saved Smart Sync outbound message for conversation id 439C13B86D8D3B82E100000086F78463:  
    I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Outbound file size for user (SHARED) is 4311 
    I GzipDataCompression: Gzip data compression is switched on 
    I Inbound file size for user (SHARED) is 3114 
    I -
    InboundContainer created: Type:R,Id:43A0856B99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:1 
    I -
    InboundContainer created: Type:R,Id:43A0856B99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:1 
    I -
    InboundContainer created: Type:R,Id:43A0856D99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:3 
    I -
    InboundContainer created: Type:R,Id:43A0856D99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:3 
    I AlertInboundProcessor: Result 1 = 
    I AlertInboundProcessor: Result 2 = 
    I AlertInboundProcessor: Result 3 = 
    I -
    InboundContainer created: Type:R,Id:43A0857099AE3B82E100000086F78463,SId:-1,Items:0,MaxI:1 
    I -
    InboundContainer created: Type:R,Id:43A0857099AE3B82E100000086F78463,SId:-1,Items:0,MaxI:1 
    I -
    InboundContainer created: Type:R,Id:43A0857299AE3B82E100000086F78463,SId:-1,Items:0,MaxI:0 
    I Set last container id 0108331b71512ab15b57 for conversation id 43956070B2A13B82E100000086F78463 
    I Set last container id 0108331b72e737e90913 for conversation id 439C13B86D8D3B82E100000086F78463 
    I Set last container id 0108331b721c2005bfc3 for conversation id 439802465AA13B82E100000086F78463 
    I Set last container id 0108331b70094c518120 for conversation id 4395713CB2A13B82E100000086F78463 
    I Outbound file size for user FALTERMEIERB is 7536 
    I GzipDataCompression: Gzip data compression is switched on 
    I Inbound file size for user FALTERMEIERB is 9432 
    I -
    InboundContainer created: Type:R,Id:43A0857F99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:15 
    I -
    InboundContainer created: Type:R,Id:43A0857F99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:15 
    I -
    InboundContainer created: Type:R,Id:43A0859199AE3B82E100000086F78463,SId:-1,Items:0,MaxI:2 
    W Request ID must have a length of 32 but it has a length of 20 Content: 0108331b71512ab15b57. Padding request id up with empty spaces. 
    I Processed Smart Sync inbound message for conversation id 43956070B2A13B82E100000086F78463 
    I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    successKeine Download-Daten aus R/3 im Downloader gefunden 
    I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    I Reset last container id for conversation id 43956070B2A13B82E100000086F78463 
    I -
    InboundContainer created: Type:R,Id:43A0858699AE3B82E100000086F78463,SId:-1,Items:0,MaxI:2 
    W Request ID must have a length of 32 but it has a length of 20 Content: 0108331b70094c518120. Padding request id up with empty spaces. 
    I Processed Smart Sync inbound message for conversation id 4395713CB2A13B82E100000086F78463 
    I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    successKeine Download-Daten aus R/3 im Downloader gefunden 
    I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    I Reset last container id for conversation id 4395713CB2A13B82E100000086F78463 
    I -
    InboundContainer created: Type:R,Id:43A0858B99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:5 
    E Error while Smart Sync inbound processing: java.lang.NullPointerException 
    java.lang.NullPointerException 
    at com.sap.ip.me.smartsync.syncIn.processors.InternalTopRowProcessor.assignStateIdWithWriter(InternalTopRowProcessor.java:413) 
    at com.sap.ip.me.smartsync.syncIn.processors.ProcessorTopSuccessReplace.startWithContainer(ProcessorTopSuccessReplace.java:81) 
    at com.sap.ip.me.smartsync.syncIn.processors.RowProcessorManager$RowProcessorDispatcher.start(RowProcessorManager.java:497) 
    at com.sap.ip.me.smartsync.syncIn.SaxSyncInProcessor$3.startTop(SaxSyncInProcessor.java:515) 
    at com.sap.ip.me.smartsync.syncIn.SaxSyncInProcessor$3.getNextHandler(SaxSyncInProcessor.java:437) 
    at com.sap.ip.me.xmlParser.MIXMLEventHandlerManager.startElement(MIXMLEventHandlerManager.java:80) 
    at com.sap.ip.me.xmlParser.MIXMLParser$ElementParser.parse(MIXMLParser.java:527) 
    at com.sap.ip.me.xmlParser.MIXMLParser.parse(MIXMLParser.java:164) 
    at com.sap.ip.me.smartsync.syncIn.SaxSyncInProcessor.processSyncInMessage(SaxSyncInProcessor.java:87) 
    at com.sap.ip.me.smartsync.syncIn.SyncInRuntimeImpl.processSyncInMessage(SyncInRuntimeImpl.java:250) 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:344) 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214) 
    at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160) 
    at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709) 
    at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285) 
    at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79) 
    at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447) 
    at java.lang.Thread.run(Thread.java:534) 
    I Processed Smart Sync inbound message for conversation id 439802465AA13B82E100000086F78463 
    I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    439802C55AA13B82E100000086F7846343A0858999AE3B82E100000086F78463successAlle Updates für einen TOP-Block erfolgreich (seqNo= 31, TOP Cntr=0000000001)000100012720053J 05 12 
    I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    E java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException 
    java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException 
    at com.sap.ip.me.smartsync.syncIn.SyncInRuntimeImpl.processSyncInMessage(SyncInRuntimeImpl.java:284) 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:344) 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214) 
    at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160) 
    at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709) 
    at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285) 
    at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79) 
    at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447) 
    at java.lang.Thread.run(Thread.java:534) 
    E Error while Smart Sync inbound processing: Error while Smart Sync inbound processing: java.lang.NullPointerException. Reset Smart Sync data on device to ensure consitency with middleware. 
    java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:351) 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214) 
    at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160) 
    at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709) 
    at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285) 
    at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79) 
    at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447) 
    at java.lang.Thread.run(Thread.java:534) 
    E Error while Smart Sync inbound processing: Error while Smart Sync inbound processing: java.lang.NullPointerException. Reset Smart Sync data on device to ensure consitency with middleware. 
    java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:351) 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214) 
    at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160) 
    at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709) 
    at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285) 
    at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79) 
    at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447) 
    at java.lang.Thread.run(Thread.java:534) 
    W Exception while proccessing method SMARTSYNC 
    java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:368) 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214) 
    at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160) 
    at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709) 
    at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285) 
    at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79) 
    at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447) 
    at java.lang.Thread.run(Thread.java:534) 
    E Exception while processing inbound container 43A0858B99AE3B82E100000086F78463 
    java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:368) 
    at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214) 
    at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160) 
    at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709) 
    at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142) 
    at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402) 
    at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285) 
    at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79) 
    at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447) 
    at java.lang.Thread.run(Thread.java:534) 
    I -
    InboundContainer created: Type:R,Id:43A0858F99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:3 
    I Processed Smart Sync inbound message for conversation id 439802465AA13B82E100000086F78463 
    I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    43A0858D99AE3B82E100000086F78463000100012720053J 05 123J 05 12S 
    I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    I Reset last container id for conversation id 439802465AA13B82E100000086F78463 
    I -
    InboundContainer created: Type:R,Id:43A0858499AE3B82E100000086F78463,SId:-1,Items:0,MaxI:4 
    I Processed Smart Sync inbound message for conversation id 439C13B86D8D3B82E100000086F78463 
    I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    43A0858299AE3B82E100000086F784630001000095200500100010000952005001000000000000100601FLACHSTAHL 80 X 3 MM,DIN 10173J 05 0588.0000.000MFaltermeier 
    I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt' 
    I Reset last container id for conversation id 439C13B86D8D3B82E100000086F78463 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956071B2A13B82E100000086F78463 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429 
    I Skip performing Sync Event (10) com.sap.ip.me.core.StatusUpdater for conversation id MI544553545f55534552 / 43A083B699AE3B82E100000086F78463 (User: TEST_USER, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    I SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713CB2A13B82E100000086F78463 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802475AA13B82E100000086F78463 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B96D8D3B82E100000086F78463 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.core.StatusUpdater on ConversationId MI46414c5445524d4549455242 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId MI2853484152454429 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.core.RegistryInboundProcessingLog$RegistryInboundProcessingLogSyncEventListener on ConversationId MI2853484152454429 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956070B2A13B82E100000086F78463 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713DB2A13B82E100000086F78463 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.core.StatusUpdater for conversation id MI505545545a4b41554c / 43803A5EFBBB3102E100000086F78463 (User: PUETZKAUL, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802465AA13B82E100000086F78463 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B86D8D3B82E100000086F78463 
    I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956071B2A13B82E100000086F78463 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429 
    I Skip performing Sync Event (2) com.sap.ip.me.core.StatusUpdater for conversation id MI544553545f55534552 / 43A083B699AE3B82E100000086F78463 (User: TEST_USER, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) 
    I SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713CB2A13B82E100000086F78463 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802475AA13B82E100000086F78463 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B96D8D3B82E100000086F78463 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 
    I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) 

  • Inbound process of ALE------- get point.s

    Hi all,
    In WE05 i m able to see my idoc with status 03. Now wht i need to configure further for the correspoinding inbound process, to see my data on the receiver system.
    Regards,
    [email protected]

    Hi
    See this and do accordingly
    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.
    Outbound:
    Step 1.  Application document is created when transaction is saved.
             2.  Message control is invoked.
             3.  Messages are processed by system.
             4.  Messages are Edited (if desired).
             5.  Output (ALE /  EDI) is checked
             6.  Validate against Message control record from Partner Profile
             7.  Application Document is saved.
             8.  Entry NAST table is created for every selected output program
                  along with Medium & Timing.
             9.  Check for Process Immediately .
                     If (yes)
                       Determine Processing Program from TNAPR Table.
                     ELSE
                       Execute RSNASTED Program.
           10.  Read Partner Profile to determine Process Code.
           11.  Process Code points to the Function Module & Invoked.
           12.  IDoc is generated. 
           13.  Check for ALE Request.
                        if (Yes)
                            Perform Filters, Conversions, Version Changes etc.
                        Else.
                            IDoc is stored in DATABASE.
    INBOUND:
    Step 1.  EDI Subsystem creates an IDoc file from EDI Messages
            2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
             3.  Data in Control Record is validate against the Partner                       Profile.
            4. IDoc is generated in Database and syntax check is                      carried out.
            5. IDoc file is deleted once file read.
            6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow. 
                       7.  Check for Process Immediately.
                   If NO
                     Execute RBDAPP01 Program
                   Else
                      Read Process Code from Partner Profile        
                           Process Code Points to  Function Module
                     Application Document Posted.     
    further help:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Help needed creating export file from a file layout with Application Engine

    The following is what I would like to do:
    - Read a record from a PS view
    - Manipulate the data as needed
    - Write the fields out to a file as defined by a File Layout
    - Repeat until no more records are found
    I have created the PeopleSoft Application Engine action listed below. It receives an error "BCUNIT is not a property of class File".
    Local Record &rec1;
    Local File &myFile;
    Local SQL &sQL1;
    /* Create instance of Record */
    &rec1 = CreateRecord(Record.W9M_MBSCRSE_VW);
    /* Instantiate the Output File */
    &myFile = GetFile("c:\temp\help_me.txt";, "A", %FilePath_Absolute);
    If &myFile.IsOpen Then
    If &myFile.SetFileLayout(FileLayout.TACOURIN) Then
    /* Create SQL object to populate rowset */
    &sQL1 = CreateSQL("%Selectall(:1) Where INSTITUTION = :2", &rec1, W9M_MBSCRSE_AET.INSTITUTION);
    /* Cycle through the records */
    While &sQL1.Fetch(&rec1)
    /* I know this section is not coded correctly but I'm not sure how to fix it */
    &myFile.BCUNIT = "1";
    &myFile.BCTCD = &rec.W9M_MBS_TERM_CODE;
    &myFile.BCTYR = &rec.W9M_MBS_TERM_YEAR;
    &myFile.BCDPTN = &rec.ACAD_GROUP;
    &myFile.BCCOUR = substring(&rec.CATALOG_NBR,2,5);
    &myFile.BCSEC = &rec.CLASS_SECTION;
    &myFile.WriteRecord();
    End-While;
    Else
    /* Process FileLayout Error here */
    End-If;
    Else
    /* Process File Open Error here */
    End-If;
    &myFile.Close();
    There are probably a lot of things wrong with this approach and if you could provide some guidance and/or  corrections to the above logic I would greatly appreciate it.
    Another approach?
    After doing a bunch of reading on Application Engine maybe my approach is incorrect. Perhaps I should be doing something like the following:
    - Read a record from a PS view
    - Populate a temporary table manipulating data as it is inserted (Temp table is named according to the file layout fields?)
    - Fetch the records from the temp table and write the record to the file layout.
    - Repeat until no more records are found
    Is this approach better and designed correctly? If not, could you recommend how it should be done? Would the population and reading of the Temp table be done in separate actions or within the same action? Do you know of an Application Engine program that can be used as an example with "like" processing?
    As you can probably tell I haven't used Application Engine before and my goal is to start out on the right path. Thank you for any direction and input that you can provide.
    Steve

    I did and my initial logic was based upon them. I don't see where it shows how to manipulate the data before writing it to the file layout fields. Maybe you can send me a link to that section?
    I was hoping that I would be able to reference the file layout fields directly to allow for manipulating the field values. Re-reading the file layout section and the application engine PeopleBooks I believe I need to create a temporary record which matches the file layout fields; i.e., the second alternative that I listed. Then, make my updates to the temp record fields as I load them. Then, load them to the file layout as a row.
    I'm not sure how this would break down in Application Engine; would the insert into the temp table and the writerecord be different steps/actions, etc.

  • Steps in Inbound Processing in ALE IDOC

    Hi all,
    Could anyone explain the steps to be followed in inbound processing in ALE Idoc.
    I know we have to create a FM n then call that in a program. But still the detail steps are not clear.
    An example will be really helpful.
    Thanx

    Hi
    Outbound:
    Step 1.  Application document is created when transaction is saved.
             2.  Message control is invoked.
             3.  Messages are processed by system.
             4.  Messages are Edited (if desired).
             5.  Output (ALE /  EDI) is checked
             6.  Validate against Message control record from Partner Profile
             7.  Application Document is saved.
             8.  Entry NAST table is created for every selected output program
                  along with Medium & Timing.
             9.  Check for Process Immediately .
                     If (yes)
                       Determine Processing Program from TNAPR Table.
                     ELSE
                       Execute RSNASTED Program.
           10.  Read Partner Profile to determine Process Code.
           11.  Process Code points to the Function Module & Invoked.
           12.  IDoc is generated. 
           13.  Check for ALE Request.
                        if (Yes)
                            Perform Filters, Conversions, Version Changes etc.
                        Else.
                            IDoc is stored in DATABASE.
    INBOUND:
    Step 1.  EDI Subsystem creates an IDoc file from EDI Messages
            2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
             3.  Data in Control Record is validate against the Partner                       Profile.
            4. IDoc is generated in Database and syntax check is                      carried out.
            5. IDoc file is deleted once file read.
            6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow. 
                       7.  Check for Process Immediately.
                   If NO
                     Execute RBDAPP01 Program
                   Else
                      Read Process Code from Partner Profile        
                           Process Code Points to  Function Module
                     Application Document Posted.     
    further help:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    Check these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Reward points for useful Answers
    Regards
    Anji

  • BPM: Permanent error in BPE inbound processing

    Hi guys...
    i am having a problem in my scenario which is involving BPM.
    The problem is when i execute the interface it is showing green flag aginst PE in sxmb_moni and in smq2 one queue is showing with sysfail and BPM: Permanent error in BPE inbound processing  error.
    yes..i searched on SDN and found resources like Note number 1126656
    i checked al the steps which were earlier mentioned posts like:
    SWWL:  there are no entries existing
    SMQ2: cleared the queues ,regenerated but still no luck.
    My undertsanding is no work is being generated at all .
    I checked BPM with F7 : its correct no errors
    BPM has return code of 0 in sxi_cache
    In ID BPM is latest and refreshed.
    Is there any way i can overcome this problem.
    Your inputs will be of real help.
    Thanks in advance.
    Regards,
    Kiran.

    My undertsanding is no work is being generated at all .
    If you are getting the error for Source ---> BPM  flow then there is a possibility that the ID objects (RD, Interface determination) are to be blamed.
    1) Recreate these particular ID objects/ make some dummy changes
    2) Activate and ensure that Cache is refreshed
    3) Delete the entry in the queue (or delete the queue)....do this only if the XI system is not of Quality, production
    4) some times the BPM cannot be triggered from sending a test message from RWB .... so make a testing from the source application .... this particular case has heppened to me and hence suggesting to you.
    Regards,
    Abhishek.

  • Error In inbound Processing IDoc

    Dear All,
    I am facing error while inbound processing of IDoc
    In status record of IDoc following errors are occuring
    Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
    The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
    Status 51: Application Document not posted
    Log details :
    Error : Material Number should be filled.
    When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
    Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
    Thanks

    Hi Praveen,
    I checked the data in IDoc for this segment.
    It is ok as required in basic message type.
    e.g. the error says that mandetory segment E1MAKTM is missing.
    when i check basic type
    MSGFN : Function
    internal data type : CHAR
    Internal length : 000003 characters
    Position in segment : 001, Offset : 0063. external length : 000003
    SPRAS : Language Key
    internal data type : LANG
    Internal length : 000001 characters
    Position in segment : 002, Offset : 0066. external length : 000001
    MAKTX : Material Description (Short Text)
    internal data type : CHAR
    Internal length : 000040 characters
    Position in segment : 003, Offset : 0067. external length : 000040
    SPRAS_ISO : Language according to ISO 639
    internal data type : CHAR
    Internal length : 000002 characters
    Position in segment : 004, Offset : 0107. external length : 000002
    is information.
    and data in segment of IDoc is
    MSGFN     005
    SPRAS     E
    MAKTX     MANATA2000 TEST ALE
    SPRAS_ISO     EN
    which i think is ok.
    I have no clue why this syntax error is coming.
    Thanks
    Niketan

  • NM7.1: Inbound processing was stopped because of server error (id=10)

    Dear Experts,
    We have migrated the 2.5 application to 7.1. Now when I am creating few transactions from mobile client say create or modify & trying to synchronize its giving me an error as stated below... I have copied the error code text from trace file of client.
    Pls let me know if anyone has any clue so as what might be the reason behind it..!!
    <r id="1268990872922" t="14:57:52" d="2010-03-19" s="D" c="000" u="" g="" m="HTTPSyncCommandIn#Error(errorId=10, messageText=Error during Uploading messages Id mismatch)">
    <f n="SourceName" v=" [/CFS/Sync/Synchronizer/HttpSyncCommand]"/>
    <f n="LocationName" v=" (com.sap.tc.mobile.cfs.sync.synchronizer.http.Command:execute)"/>
    <f n="ThreadName" v="Thread-41"/>
    </r>
    <r id="1268990872923" t="14:57:52" d="2010-03-19" s="E" c="000" u="" g="" m="An error encountered on server: &quot;Error during Uploading messages Id mismatch&quot;; error code 10">
    <f n="SourceName" v=" [/CFS/Sync]"/>
    <f n="LocationName" v=" (com.sap.tc.mobile.cfs.sync.api.SyncManager:postMessage)"/>
    <f n="ThreadName" v="Thread-41"/>
    </r>
    <r id="1268990872924" t="14:57:52" d="2010-03-19" s="E" c="000" u="" g="" m="Inbound processing was stopped because of server error (id=10): Error during Uploading messages Id mismatch ">
    <f n="SourceName" v=" [/CFS/Sync/Synchronizer]"/>
    <f n="LocationName" v=" (com.sap.tc.mobile.cfs.sync.synchronizer.http.HttpSynchronizer:readResponse)"/>
    <f n="ThreadName" v="Thread-41"/>
    </r>
    <r id="1268990872937" t="14:57:52" d="2010-03-19" s="D" c="000" u="" g="" m="commit called on PersistenceSink with connection 27830759">
    <f n="LocationName" v=" (com.sap.tc.mobile.cfs.pers.jdbc.core.JDBCPersistenceSink:commit)"/>
    <f n="ThreadName" v="Thread-41"/>
    </r>
    Regards,
    Saptak

    Hi Amit,
    Thanks for your inputs.. Do you have any idea behind this error, why does the client & doe messages go out of sync. And what can be done as a precautionary measure to avoid it..
    Do you want me to try "Recover the device", or to reinitialise it ??
    Because if I reinitialise the device then the user will not be able to sync again with same device & i will have to un-install & re-install the client & sync again...and this will create problems in production system.
    I also tried to recover the device; it doesnt work this way.
    Pls guide me...
    Thanks in advance,
    Regards,
    Saptak

  • SUPPORT APPLICATION ENGINEERING POSITION based in Atlanta

    Averna at a glance:
    Averna delivers industry-leading test solutions and services for communications and electronics device makers worldwide, accelerating product development, quality and innovation.
    Be global@work: Serve international customers and collaborate with colleagues in Canada, the U.S., Mexico, Japan and Hungary.
    Drive innovation@work: Participate in the development of market-leading high-tech products in the telecom, transportation, electronics and multimedia sectors.
    Develop your talent@work: Contribute to thrilling projects that will stretch your skills and talent to the maximum.
    Enjoy success@work: Be part of a fast-growing company with award-winning products and team.
    Share your passion@work: Meet passionate people, enjoy our modern environment and dynamic atmosphere.
    The challenge of the Support Application Engineering position:
    The Support Application Engineering position is responsible for customer technical support and some development activities. The chosen candidate will:
    Develop a deep and broad understanding of Averna tools and products;
    Use the in-house tools to track customer requests;
    Take ownership of problems and see them through to successful resolution;
    Be called to travel about 30% to 50 % of the time.
    Duties and responsibilities:
    Provide primarily first and second tier remote customer support, troubleshooting and solutions for existing customers;
    Diagnose, De-Bug and fix less complicated bugs using but not limited to LabVIEW, TestStand, C, C++,  and/or VHDL;
    Work with senior developers to identify and resolve complicated technical software problems, and some hardware problems;
    Become an Expert User for the Jupiter and Mercury Platform;
    Involved in developing new features and tools;
    Document frequent issues into scripted processes; create FAQ;
    Document required bug fixes, end-user feature improvements, and operations feature improvements;
    Troubleshoot problems and solve the incidents through a methodical and process based approach;
    Reproduce errors reported by clients and escalate to R&D by providing a narrowed down list of possible causes;
    Analyze recurring problems and suggest improvements to Peers in the R&D and Services teams
    Provide thorough root cause analysis to Customers;
    Document troubleshooting flowcharts based on real life scenarios;
    Commit and contribute to a high level customer satisfaction by providing best in class Support and Service;
    Occasional week night or weekend work is required to support customer from different time zones and with urgent requests (approx. 15% of the time).
    Qualifications:
    Bachelor degree in computer science, electrical engineering or computer engineering;
    2-5 years experience solving deployment and support issues is an asset;
    Experience with RF is required; DOCSIS experience is a strong asset;
    Good general computer knowledge (e.g. Windows, TCP/IP networking, FTP) with a strong aptitude for problem solving;
    Experience in software engineering for test platforms or real-time software engineering;
    Able to read engineering design documentation (mechanical, electrical or software);
    Knowledge of broadband and telecommunication industries is an asset;
    Practical experience with LabVIEW, TestStand, TCL programming is an asset;
    Practical experience with MS SQL and MySQL is an asset.
    Comportments/ Behavior
    Ability to quickly learn systems and trouble shoot with the customer live and remotely;
    Pro-activity, autonomy, self motivated individual;
    Likes to interact directly with customers to achieve customer satisfaction with a "can do" attitude, ability to easily establish good relationships with customers;
    Diplomacy, open-mindedness, and patience, great listening;
    Good verbal skills for telephonic work and ability to develop well written documentation;
    Excellent oral and written English communication skills. Chinese Mandarin skills are an asset.
    Please send your resume to [email protected] and mention the title of the position: Support Application Engineering position
    We thank you for your interest towards Averna. Please note that only those candidates being considered for the position will be contacted.

    update : this position is based only in Atlanta

  • Inbound Process code

    Hi Folks,
        When creating the Inbound Process for customized scenario where the IDOC type is CUstom and Inbound FM is also custom. The Custom Process code details in WE42 should be like
    Function Module           - Custom FM
    Maximum number of repeats - 0
    Then what should be the IDOC packet , IDOC and Application Object be filled like...should it be blank or you need to pass some details. Please help.
    Regards,
    Tim

    if dont have any application object you can leave them blank.
    It still works.
    Or you can give general seetings.
    Idoc Packet :
    Object Type : IDOCPACKET
    Endevent : MASSINPUTFINISHED
    IDOC:
    Objecttype: IDOC
    Startevent : PROCESSSTATEREACHED
    Endevent : PROCESSSTATEREACHED
    Most of it depends how you want to process the documnet , btu above detaisl should be enough for posting your document.
    Regards,
    Mano Sri

Maybe you are looking for