IPC logging

376 Views

Hi,

With help from Dom and Andrew and others, we've copied an elegant/complex pricing requirement 900 in R3 to IPC, and by applying same principle, we've also copied a formula condition value 903 from R3 to IPC. Appreciate your time and help Dom, Andrew and all!

We'd like to tacle a couple of lower priority issues related to IPC now, basically three questions as follows:

1. For a given item with three different condition type (e.g., ZPR0, ZPR1 and ZNA1),CRM consistantly calls the IPC requirement 900 seven times (2 times per conditon type, plus one conditiontype got called three times), we recorded this by logging statements inside case 900 (Our basis team decided no local IPC be installed, so I don't have a local IPC to run debug runs but the log statements should be reliable). R3 calls one time per condition type which seems reasonable to me, can any one tell me why CRM calls this many times?

2. we're currently using IPCServ1Err.log (IPCServ1Out.log, IPCDispErr.log and IPCDispOut.log) as the main log file, does any one uses other log mechanisms? also, is there a way to config the ipc so the log file (e.g., the IPCServ1Err.log) will keep appending logging statements until a pre-set size has reached when a copy of the log file is made and renamed with a timestamp and the original log file is refreshed (all contents deleted), logging keeps on with this original log file. That way, the logging history can be kept without the potential danger of a very large log file to slow down the performance.

3. The IPCServ1Err.log shows some error for all pricing runs though the prices seem being calculated correctly, any one knows how to fix the problem?

=========== copied from IPCServ1Err.log===============

Nov 8, 2005 2:24:17 PM com.sap.sxe.socket.server.JavaServer [Main TCP/IP Loop] Error: Repository Error: Malformed Repository Entry: Ping (no export SPC_ERROR_NUMBER)

Nov 8, 2005 2:24:17 PM com.sap.sxe.socket.server.JavaServer [Main TCP/IP Loop] Error: Repository Error: Malformed Repository Entry: GetSupportedSAPClients (no export SPC_ERROR_NUMBER)

Nov 8, 2005 2:24:17 PM ...server.rfc.RFCServer$JCOTraceListener [Main TCP/IP Loop] Error: Please note: JCO Tracelevel 0 messages are mapped to error messages. Typically they do not reflect IPC errors. JCO Error messages are typically no cause for concern

Nov 8, 2005 2:25:21 PM ...M-ZKE1-ZPR0.O 50000572-NORM-ZKE1-ZPR0 [JCO.ServerThread-4] Error:

============= end copy of IPCServ1Err.log ===============

"M-ZKE1-ZPR0.O 50000572-NORM-ZKE1-ZPR0" is spilled out from the userexits checkRequirement().

Thanks,

Yanhui Yu