Fox syntax errors after SEM 600 Patching to SP12

Greetings all you experts out there..
Pre patching to SP12, all our Fox formulas using the following syntax to convert a fiscal period to a fiscal year worked without problem:
PER = 0092008.
YEAR = PER/0001000.
This would return a value for YEAR = 0002008.
Yes, it worked with the 3 leading zero's....!!!
Post patching, system no longer likes this syntax and throws out an syntax error message.
Please understand that I have no difficulty in changing the code - say using SUBSTR - to simply get the 4 digits only relevant to the fiscal year.......BUT...because we have these fox functions all over our solution, we were hoping for a more general fix which then would not require changes (and thus transports to production) etc.....
So, any ideas on how to fix WITHOUT changing the Fox code...???
Thanks and regards,
Rael

Hi Hans,
Sorry, well spotted.....a typing mistake...
Yes, the fiscal period is in format 2008009....and when you apply following Fox statement:
PER = 2008009.
YEAR = PER / 0001000.
the result is
YEAR = 0002008.
and this is where the Fox formula editor is throwing up the syntax error....because it expects a 4 digit number for the year, i.e., no leading zeros.......
Remember, these Fox formulas have beein working correctly for years, and it is only after patching that we are receiving the syntax error....
Regards,
Rael

Similar Messages

Syntax error after convert data : LSMW

Hi,
I am doing a LSMW for MM01. After the convert data step I get the following syntax error:
The following syntax error was found in program
/1CADMC/SAP_LSMW_COMV_00000168
For typr "C", a max length specification of 65535 is allowed.
Can anybody help me in figuring out where I am going wrong.
Thanks,
Nilesh

just execute ur lsmw in this, there is tab button user menu next to execute button , click on that , u come across a pop screen where u have a check box in that just select generate conversion program and display conversion program. and press enter.
afterwards select the radio button generate conversion program , it will shows the program in this do systax check. u will findout the error .
do syntax check by running step generate conversion programe,
and also check source fields step , r u giving correct length or not for each field.
Thanks
null

Syntax Error after creating enhancements for subroutine

Problem:
Creating enhancement sections gives a syntax error when creating enhancement options and implementations for a subroutine and then ceating enhancement options and implementations for the call to that same subroutine.

Syntax Error:
"Different number of parameters in FORM and PERFORM (routine: SET_LAYOUT, number of formal parameters: 2, number of actual parameters: 1)


Here's the following scenario:


A subroutine is defined in a program.
The subroutine is called within the same program.


I then executed these steps:
 1. Defined an enhancement section around the subroutine definition
 2. Defined an enhancement section around the subroutine call.
 3. Implemented the enhancement section around the subroutine definition and add an additional parameter.


 Currently, this gives a syntax error as expected, since the call to the subroutine needs 1 more parameter.


 4. Implemented the enhancement section for the subroutine call. I change the call in the implementation so it passes the new parameter.


A syntax check to this gives an error. The syntax checker is not only checking the new implementation, but also the original subroutine that should have been overwritten.


The enhancement sections use the same enhancement spot, and the enhancement implementations use the same implementation.


I tried various combinations of using different enhancement spots and/or implementations, but all give the same syntax error. I tried separating the subroutine in a different include and retried my testing, but it still gave the same syntax error.


Here's the sample code I first created to try troubleshooting the problem:


<pre>
ENHANCEMENT-SECTION ZEP_Z_MICHAEL_02 SPOTS ZES_Z_MICHAEL .
 PERFORM set_layout
 CHANGING
 wa_layout.
END-ENHANCEMENT-SECTION.
$$-Start: ZEP_Z_MICHAEL_02----
$$
ENHANCEMENT 2 ZEI_TEST_SECTIONS.
 "inactive version
 PERFORM set_layout
 using 'X'
 CHANGING
 wa_layout.
ENDENHANCEMENT.
$$-End: ZEP_Z_MICHAEL_02----
$$
ENHANCEMENT-SECTION ZEP_Z_MICHAEL_01 SPOTS ZES_Z_MICHAEL STATIC .
FORM set_layout
CHANGING p_wa_layout TYPE slis_layout_alv.
p_wa_layout-zebra = 'X'.
wa_layout-no_colhead = 'X'..
p_wa_layout-colwidth_optimize ='X'.
wa_layout-window_titlebar = 'Woot'.
ENDFORM. "set_layout
END-ENHANCEMENT-SECTION.
$$-Start: ZEP_Z_MICHAEL_01----
$$
ENHANCEMENT 1 ZEI_TEST_SECTIONS.
 "inactive version
FORM set_layout
using p_test type boolean
CHANGING p_wa_layout TYPE slis_layout_alv.
p_wa_layout-zebra = 'X'.
wa_layout-no_colhead = 'X'..
p_wa_layout-colwidth_optimize ='X'.
wa_layout-window_titlebar = 'Woot'.
ENDFORM. "set_layout
ENDENHANCEMENT.
$$-End: ZEP_Z_MICHAEL_01----
$$
</pre>


Please let me know if you think I am doing something wrong.


Thanks, 
Mike

Edited by: Michael Herman on Mar 8, 2010 8:11 PM

Yes, Sandra. That is what did and it worked with no syntax errors!
I'm not sure if this is getting off topic or not, but the SAP documentation(taken from the SAP help after pressing F1 on the keyword static in ERP6) seems misleading:
"The STATIC addition is intended for the enhancement of data declarations, while the statement ENHANCEMENT-POINT without the STATIC addition is designed for the enhancement of executable coding."
I would think the enhancement section ZEP_Z_MICHAEL_02 would fall under the category of executable code, while the enhancement section ZEP_Z_MICHAEL_01 would fall under the category of declarative code.
Unfortunately, all the SAP enhancement sections I come accross are dynamic. The SAP help explains the reasoning for this:
"In contrast to the statement ENHANCEMENT-POINT, the addition STATIC of the statement ENHANCEMENT-SECTION can only be used with maximum caution for changes of data declarations, because a replacement and no completion is carried out. Especially application development within SAP should not use the addition STATIC at all with ENHANCEMENT-SECTION as the change will be active in the entire customer system. "
I do not know what the word "completion" means in the previous quote, so I can't determine why it would matter. Regardless, if a developer wanted to change a standard subroutine declaration, they would also have to mod an enhancement section to change it to static. This seems to defeat the purpose of using enhancements, but maybe this scenario is not what enhancements were intended for.

Syntax error after 6.20 SP53

Hello,
we get a syntax error in previously error-free BSP pages after basis support package SP53 6.20.
The line with error is
<yhr_pd_pm:button onClick="return fSubmitNewWindow('<%=<l_mgr_detail>-act_ioper%>', '<%=l_selval%>')"
text="<%=<l_mgr_detail>-act_text%>"
enforce_width="X" />
The error message is
After "")", there must be a space or equivalent character (":", ",", ".").
Adding a dot after the closing bracket
'<%=l_selval%>')."
resolves the error message but will obviously be a JavaScript syntax error. Adding a simple space (as the error message suggests) does not help. But adding a semicolon works:
'<%=l_selval%>');"
It seems like SAP is trying to check code inside of a parameter string to a BSP extension tag.
This is similar to the problem described in note 868333 and in this forum threads
Menu Bar
Syntax error while activating BSP with OTR in htmlb element
BSP error after SP53
but is a new problem.
We already implemented note note 851647 and got rid of the first bunch of problems but than this one came up.
Hope this helps you when you get the same problem.
Best regards,
Christian.

Well, I finally resolved the issue. The problem was actually against another method of the same class. The method had some comments/remarks in the header and therefore found it to be different to the new version. The code was identical thouugh. It's about time some logic was built in to ignore comments and just compare the code. Anwyay, problem solved, I compared the other method and the lock was released. Suddenly, the Method DO_PREPARE_OUTPUT did have code behind it, so I did not actually have to do anything after this.
Regards
Jason

Error after implementing SP11 Patch 5 for 7.5 MS

After implementing SP11 Patch 5 for BPC 7.5 the SPRunConversion function (which worked find under SP07) no longer works. Every time that the function runs an error FX-160 is generated indicating that there is No Entity selected.
I have modified all of the applications, optimized all of the applications, and reprocessed all of the rate related dimension files.
Has anyone else run into this issue with the stored procedure after upgrading to patch 5 on SP11?

Hey Experts,
other templates working fine (personell admin. personell time, organizational management, travelmngt.)!
The templates running in the 3.5 BW....but since the update of our testsystem the e-recruiting templates give back these errors.
We dont wanna initialize the migration of templates and other objects to 7.0 now. Maybe in a few months.
Could it be that several (in my case the e-Recruiting Templates/Queries) 3.5 objects never be running without migration?
Thx for your answers!!!
kind regards,
moriz

Syntax error in purgeDeploymentLibrary while patching for GC provisioning

In trying to apply one off patch 5998260, I get an error when I attempt to Purge the Software Library prior to opatch.
The readme instructs:
6) Purge the Software Library by executing the following command:
% $ORACLE_HOME/bin/purgeDeploymentLibrary <conn string> <username> <password>
Where
<conn string> is of form: "jdbc:oracle:thin:@dbhost:dbport:sid" where dbhost,
dbport and sid to be replaced appropriately with the hostname, database port
and database SID for the Oracle Management Repository.
<username> is Oracle Management Repository username.
In an anttempt to follow this form my exact syntax is:
$ORACLE_HOME/bin/purgeDeploymentLibrary jdbc:oracle:thin:@devdb3:1521:emrep sysman xxxxxx
The system's response to this command is:
purgeDeploymentLibrary: test: argument expected
Obviously it did not like my presentation of the connectstring user and password variables? hmmm....what do I need to tweak to make this statement work
Regards,
Tim

The ORACLE_HOME was already set to the OMS_HOME when I tried the first time. So my first thought was some sort of a syntax error in the parameter list...thanks for the reply and please let me know of any other suggestions.

Syntax error after upgrade to ECC6

Hi,
I have customized infotype and BAPI in SAP 4.6. After upgade to ECC6, my Infotype is working fine, but my BAPI give this error :
The following syntax error was found in the program SAPLZBAPI_HR :
"INCLUDE report "%_HR9000" not found."
If I goto SE38 to recreate %_HR9000, SAP not allow me to continue and appear message "Do not use any special character".
May I know how to resolve this problem ?
Thanks a million.
Regards,
Eric

Hi,
In the ECC6.0 version, it seems that one of the INCLUDE that was generated for that infotype in 4.6 C ending.. with words....HR9000 was not transported or not found for that infotype. Please check all the includes..
In SE38 you can enter the characters like %, so that error is coming
% means LIKE PATTERN ....HR9000 .
Hope you understood.
Regards,
ANJI

Too many syntax errors after upgrade to ECC 6.0

Hello,
We have made a test upgrade from 4.6C to ECC 6.0. OS --> AIX 5.3; DB --> DB2 8.2. After upgrade we have a lot of syntax errors, why? Anybody has the same problem? Do I must to check all my programs?
Thanks.
Martin

Hello, here there is an example in Z program, but I have seen in no Z programs too with includes or userexits in the second example.
Thanks.
Martin.
first example:
Error in the ABAP Application Program
The current ABAP program "GBT10CO0" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "ZGGBR000 " in include "ZGGBR000
" in
line 279:
""SYST-MODNO" must be a character-type data object (data type C, N, D, "
"T or STRING) ."
second example:
Error in the ABAP Application Program
The current ABAP program "SAPLGBL5" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "GBT10FI0 " in include "GBT10FIB
" in
line 1288:
"The FORM "SEND_CMPLX_DATA_015" does not exist."

Strange Data Mapping Errors after SEM 6 Upgrade. Please assist.

Hi All, I encountered these sudden Mapping errors after I tried to do Testing in Post Upgrade Sand Box. Here I am trying to to perform Collected Reported Financial Data under Data Collection Method for a particular Company Code 3040. Kindly help me with some quick responses as this is kind of high priority. The errors and the Diagnosis Notes I am unable to follow as I do not where I shall write those Mapping Rules they are referring to. I do not even know if that need to apply any SAP Notes as such. Once again Highly appreciate your quick response and Many Thanks in Advance.
Regards, BIP
Input conversion for field Period Value LC has invalid format Message no. UCT8210 Diagnosis The mapping rule for target field Period Value LC contains a move with a selected Input Conversion indicator. Therefore, the system performs an input conversion prior to creating the target data. However, an error in the input conversion occurred while moving the source key figure to the target key figure Period Value LC. This means that the format used for the input conversion is incompatible with the target data. System Response The system will not perform the move. Procedure Examine the mapping rule for field Period Value LC. Either select the Conversion Exit indicator or deselect the Input Conversion indicator. Execute the method again. -
3040 is incompatible with input format for field /1FB/COMPANY Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field /1FB/COMPANY from the mapping rule for the target field. 3040 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field /1FB/COMPANY. However, the value 3040 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 3040 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field /1FB/COMPANY. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field /1FB/COMPANY. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field /1FB/COMPANY. If incorrect values were selected, make sure that the mapping rule used by source field /1FB/COMPANY has been defined correctly. If the mapping rule is correct and value (3040) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 3040 for field /1FB/COMPANY and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field /1FB/COMPANY, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field /1FB/COMPANY is unsatisfactory: You can define a source selection for field /1FB/COMPANY in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field /1FB/COMPANY. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule. -
Cannot derive the source selection from target field Version Message no. UCT8252 Diagnosis Field Version has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Version. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Version. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Versionthrough mapping), choose one of the alternatives below: Change the mapping rule for field Version so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Version. -
Cannot derive the source selection from target field Group Currency Message no. UCT8252 Diagnosis Field Group Currency has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Group Currency. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Group Currency. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Group Currency through mapping), choose one of the alternatives below: Change the mapping rule for field Group Currency so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Group Currency
1 is incompatible with input format for field FISCPERIOD Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field FISCPERIOD from the mapping rule for the target field. 1 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field FISCPERIOD. However, the value 1 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 1 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field FISCPERIOD. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field FISCPERIOD. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field FISCPERIOD. If incorrect values were selected, make sure that the mapping rule used by source field FISCPERIOD has been defined correctly. If the mapping rule is correct and value (1) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 1 for field FISCPERIOD and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field FISCPERIOD, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field FISCPERIOD is unsatisfactory: You can define a source selection for field FISCPERIOD in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field FISCPERIOD. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule
Input must be in the format ___,___,__~ Message no. 00088 Diagnosis Your entry does not match the specified input format. System Response The entry in this field was rejected. Procedure The entry must comply with the edit format. The following edit format characters have a special meaning: "_" (underscore) There should be an input character at this point; this should be a number for numeric fields. "." (decimal point) (applies to numeric fields) The decimal point occurs here (setting in the user master record). "," (thousands separator) (applies to numeric fields) This separator occurs (optionally) for more than three figures. Depending on the setting in the user master record, it can be a period or a comma. "V" (applies to numeric fields) The operational sign appears here. If used, it must by at the right margin of the field. The sign is either "-" or " "(space). "~" (tilde) (applies to numeric fields) As of and including this character, leading zeros must also be entered. Otherwise, this character has the same meaning as an underscore. Leading zeros need not be entered on the left of the tilde. They are not output at this position. All other characters have their normal meanings and must be entered in the same position as in the edit format.

Hi Dan,
Could you Kiindly advise me where we need to write the Mapping Rules in Consolidation Monitor? All he time the errors refering to Mapping Rules. The only Tab I seen "Mapping" is in Data Basis But as per my Understanding Iwe do not have much to do there as it is system generated Mapping Tab.
Where we actually go and select/deselct those Input Conversion Indicator/ Conversion exit Indicator.
Highly appreciate your advise.
Thanks and Regards,
BIP

Query syntax error after multiprovider change

Hi everyone,
I removed key figures from a multicube, changed a query on top afterwards and saved it. The key figures are no longer in the key figure list of the query in the Query designer, and are no longer used in any place within the query.
Now, I'm getting a syntax error on query execution, since the compiled query still contains a reference to the old key figures. Regeneration via RSRT or saving under a new name doesn't work, and to delete the generated report I need a developer key.
Any ideas?
Regards,
Tilman

Hi Shashank,
thanks for your response.
I did try the "check query" button, it didn't return an error. When executing the query via rsrt, I get a dump due to "Syntax error in program GP48VM7K0MSF08DRO2382A2PSTI ". The program still contains data type references to the removed infoobjects. When checking the program via SE38, you get just that syntax error.
I'm looking for a way to clean these things up. Even when creating a new query on the aggregation level (I was talking about a multiprovider earlier, which is located underneath), the error pops up. I activated all the objects along the way, with no effect.
Regards,
Tilman

Syntax error after applying NOTE 2028544

Hello Experts,
We implemented Fiori My Timesheet application and it was working fine except while saving the time data from Fiori we were getting short dump saying conversion error (found during debugging) as mentioned in below screenshot.
To overcome this error we implemented SAP NOTE 2028544 in ECC using SNOTE but it was throwing an syntax error in a interface /IWBEP/IF_MGW_MED_ODATA_TYPES. While during version comparision we found out that the NOTE has removed a line from the program (Below screenshot) which is causing the error. Also we are currently in SAPK-20009INIWBEP version of IW_BEP.
Can anyone please let us know what wrong we did and how to overcome this situation since we cannot revert back the changes because it is asking for access key to manually change the code and when we are trying to reset the NOTE implementation using SNOTE then we are getting syntax error in the above program?
Thanks in advance.
Regards,
Rahul
Tags edited by: Michael Appleby (but please start doing this on your own)

Hello Pankaj,
While checking the NOTE 2032088 and the correction instructions, it was mentioned that the prerequisites is to apply NOTE 2028544 (The one in which we are facing error).
But the main problem now is we applied the NOTE 2028544 but it caused a change in a program (mentioned earlier) and we activated it forcefully. Now when we are trying to open My Timesheet application it is giving error. When we try to reset this NOTE implementation then we cannot do because it is saying there is a syntax error in your program.
We are now in deadlock situation where we cannot move forward or backward
Regards,
Rahul

ATRV FoX syntax error

Hi I'm using the formula ATRV to get functional area from cost center. I'm getting a syntax error in IP at the line of the function while using this function. I've used this function in BW- BPS before and used to work properly. Somehow its not working here.. Pls check the code below..
syntax error. at ATRV line is..
"A comma and other arguments were expected instead of ).
The code below is
DATA L_COSTCENTER TYPE 0COSTCENTER.
DATA L_ACCOUNT TYPE 0GL_ACCOUNT.
DATA L_COSTELEMENT TYPE 0COSTELMNT.
DATA L_INFOPROVIDER TYPE 0INFOPROV.
DATA L_FUNCAREA TYPE 0FUNC_AREA.
DATA L_FLAG TYPE ZCH_REVF.
DATA L_FACTOR TYPE F.
L_FUNCAREA = ATRV ( 0FUNC_AREA , L_COSTCENTER ).
FOREACH L_COSTCENTER.
IF L_COSTCENTER <> '#'.
FOREACH L_COSTELEMENT.
IF L_COSTELEMENT <> '#'.
L_ACCOUNT = L_COSTELEMENT.
{ 0AMOUNT,#,#,1000,L_ACCOUNT, ZPCA_T01} ={ 0AMOUNT, L_COSTCENTER,L_COSTELEMENT,1000, #, ZCO_T01}
ENDIF.
ENDFOR.
ENDIF.
ENDFOR.

Thanks, I Included the controlling area and there was no syntax error..however When I execute the code below .. I'm getting a new error saying Cost Center is invalid.. its not reading the statatement or something.. Can you answer how I should the CO AREA and the function..
This is the following error
Planning function Move Cost Center Information ( ZFORMULA1 ) ended with errors
Value 'D700012' from the 0COSTCENTER characteristic is not valid
Value 'D700012' from the 0COSTCENTER characteristic is not valid
Value 'D700012' from the 0COSTCENTER characteristic is not valid
DATA L_FUNCAREA TYPE 0FUNC_AREA.
DATA L_FLAG TYPE ZCH_REVF.
DATA L_FACTOR TYPE F.
L_FACTOR =20.
FOREACH L_COSTCENTER.
IF L_COSTCENTER <> '#'.
L_FUNCAREA = ATRV ( ' 0FUNC_AREA ', L_COSTCENTER,L_CONAREA ).
IF L_FUNCAREA = '1000'.
L_FLAG = 'N'.
ELSEIF L_FUNCAREA <> 1000 .
L_FLAG = 'Y'.
ENDIF.
FOREACH L_COSTELEMENT.
IF L_COSTELEMENT <> '#'.
L_ACCOUNT = L_COSTELEMENT.
{ 0AMOUNT,#,#,1000,#,L_ACCOUNT, ZPCA_T01,L_FLAG} ={ 0AMOUNT, L_COSTCENTER,L_COSTELEMENT,1000, #,#, ZCO_T01,#} * L_FACTOR.
ENDIF.
ENDFOR.
ENDIF.
ENDFOR.

Error after applying support patch SAPK-40009INCPRXRPM

Hi all,
In our PLM system after applying support patch SAPK-40009INCPRXRPM of component CPRXRPM, release-400
we are getting some short dumps like CALL_FUNCTION_NOT_FOUND saying that OLR3_DMS_RFC_LOAD_OBJECT_LINKS function module can't found but this function module doesn't exist in the system.
plz help me in this regard.
Thanks in advance.
Regards,
Raja

Thanks for the prompt response Samrat,
But with SGEN we can only regenerate the programs, but here the problem is the module I mentioned doesn't exist in system.
Regards,
Raja

Error after applying the patch p12748351

Hi experts,
We installed the OIM version 11.1.1.1.5.0, and we implemented a solution almost out of the box.
After the patching to the version 11.1.1.5.1 we faced an issue during the target reconciliation from AD for the new users.
We see that no new event is generated and from the log we face this issue:
<Dec 15, 2011 11:52:16 AM CET> <Error> <oracle.iam.reconciliation.impl> <IAM-5010000> <Generic Information: {0}
oracle.iam.platform.utils.SuperRuntimeException: java.sql.SQLSyntaxErrorException: ORA-00907: missing right parenthesis
ORA-06512: at "PROD_OIM.XL_SP_RECON_ACCOUNT_DATA_MATCH", line 149
ORA-06512: at line 1
at oracle.iam.reconciliation.dao.event.EventMgmtDao.ignoreEventAccountDataMatch(EventMgmtDao.java:527)
at oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.ignoreEvent(ReconOperationsServiceImpl.java:421)
at oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.ignoreEvent(ReconOperationsServiceImpl.java:351)
at Thor.API.Operations.tcReconciliationOperationsIntfEJB.ignoreEventx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy414.ignoreEventx(Unknown Source)
at Thor.API.Operations.tcReconciliationOperationsIntfEJB_troehf_tcReconciliationOperationsIntfRemoteImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at Thor.API.Operations.tcReconciliationOperationsIntfEJB_troehf_tcReconciliationOperationsIntfRemoteImpl.ignoreEventx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)
at $Proxy177.ignoreEventx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
at $Proxy408.ignoreEventx(Unknown Source)
at Thor.API.Operations.tcReconciliationOperationsIntfDelegate.ignoreEvent(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.processUserChange(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.processBatch(Unknown Source)
at com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController.searchResultPageEnum(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.performReconciliation(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.execute(Unknown Source)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.execute(SchedulerBaseTask.java:384)
at oracle.iam.scheduler.vo.TaskSupport.executeJob(TaskSupport.java:145)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.iam.scheduler.impl.quartz.QuartzJob.execute(QuartzJob.java:196)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
Caused By: java.sql.SQLSyntaxErrorException: ORA-00907: missing right parenthesis
ORA-06512: at "PROD_OIM.XL_SP_RECON_ACCOUNT_DATA_MATCH", line 149
ORA-06512: at line 1
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:213)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1075)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3752)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3937)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:9259)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1535)
at weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:99)
at oracle.iam.reconciliation.dao.event.EventMgmtDao.ignoreEventAccountDataMatch(EventMgmtDao.java:519)
at oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.ignoreEvent(ReconOperationsServiceImpl.java:421)
at oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.ignoreEvent(ReconOperationsServiceImpl.java:351)
at Thor.API.Operations.tcReconciliationOperationsIntfEJB.ignoreEventx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy414.ignoreEventx(Unknown Source)
at Thor.API.Operations.tcReconciliationOperationsIntfEJB_troehf_tcReconciliationOperationsIntfRemoteImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at Thor.API.Operations.tcReconciliationOperationsIntfEJB_troehf_tcReconciliationOperationsIntfRemoteImpl.ignoreEventx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)
at $Proxy177.ignoreEventx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
at $Proxy408.ignoreEventx(Unknown Source)
at Thor.API.Operations.tcReconciliationOperationsIntfDelegate.ignoreEvent(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.processUserChange(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.processBatch(Unknown Source)
at com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController.searchResultPageEnum(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.performReconciliation(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.execute(Unknown Source)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.execute(SchedulerBaseTask.java:384)
at oracle.iam.scheduler.vo.TaskSupport.executeJob(TaskSupport.java:145)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.iam.scheduler.impl.quartz.QuartzJob.execute(QuartzJob.java:196)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>
<Dec 15, 2011 11:52:16 AM CET> <Error> <OIMCP.ADCS> <BEA-000000> <====================================================>
<Dec 15, 2011 11:52:16 AM CET> <Error> <OIMCP.ADCS> <BEA-000000> <com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask : processUserChange : oracle.iam.platform.utils.SuperRuntimeException: java.sql.SQLSyntaxErrorException: ORA-00907: missing right parenthesis
ORA-06512: at "PROD_OIM.XL_SP_RECON_ACCOUNT_DATA_MATCH", line 149
ORA-06512: at line 1
>
<Dec 15, 2011 11:52:16 AM CET> <Error> <OIMCP.ADCS> <BEA-000000> <====================================================
>
<Dec 15, 2011 11:52:16 AM CET> <Error> <OIMCP.ADCS> <BEA-000000> <================= Start Stack Trace =======================>
<Dec 15, 2011 11:52:16 AM CET> <Error> <OIMCP.ADCS> <BEA-000000> <com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask : processUserChange>
<Dec 15, 2011 11:52:16 AM CET> <Error> <OIMCP.ADCS> <BEA-000000> <oracle.iam.platform.utils.SuperRuntimeException: java.sql.SQLSyntaxErrorException: ORA-00907: missing right parenthesis
ORA-06512: at "PROD_OIM.XL_SP_RECON_ACCOUNT_DATA_MATCH", line 149
ORA-06512: at line 1
>
<Dec 15, 2011 11:52:16 AM CET> <Error> <OIMCP.ADCS> <BEA-000000> <Description : oracle.iam.platform.utils.SuperRuntimeException: java.sql.SQLSyntaxErrorException: ORA-00907: missing right parenthesis
ORA-06512: at "PROD_OIM.XL_SP_RECON_ACCOUNT_DATA_MATCH", line 149
ORA-06512: at line 1
>
<Dec 15, 2011 11:52:16 AM CET> <Error> <OIMCP.ADCS> <BEA-000000> <Thor.API.Exceptions.tcAPIException: oracle.iam.platform.utils.SuperRuntimeException: java.sql.SQLSyntaxErrorException: ORA-00907: missing right parenthesis
ORA-06512: at "PROD_OIM.XL_SP_RECON_ACCOUNT_DATA_MATCH", line 149
ORA-06512: at line 1
at oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.ignoreEvent(ReconOperationsServiceImpl.java:469)
at oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.ignoreEvent(ReconOperationsServiceImpl.java:351)
at Thor.API.Operations.tcReconciliationOperationsIntfEJB.ignoreEventx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy414.ignoreEventx(Unknown Source)
at Thor.API.Operations.tcReconciliationOperationsIntfEJB_troehf_tcReconciliationOperationsIntfRemoteImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at Thor.API.Operations.tcReconciliationOperationsIntfEJB_troehf_tcReconciliationOperationsIntfRemoteImpl.ignoreEventx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)
at $Proxy177.ignoreEventx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
at $Proxy408.ignoreEventx(Unknown Source)
at Thor.API.Operations.tcReconciliationOperationsIntfDelegate.ignoreEvent(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.processUserChange(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.processBatch(Unknown Source)
at com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController.searchResultPageEnum(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.performReconciliation(Unknown Source)
at com.thortech.xl.schedule.tasks.ActiveDirectoryReconTask.execute(Unknown Source)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.execute(SchedulerBaseTask.java:384)
at oracle.iam.scheduler.vo.TaskSupport.executeJob(TaskSupport.java:145)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.iam.scheduler.impl.quartz.QuartzJob.execute(QuartzJob.java:196)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
Caused by: oracle.iam.platform.utils.SuperRuntimeException: java.sql.SQLSyntaxErrorException: ORA-00907: missing right parenthesis
ORA-06512: at "PROD_OIM.XL_SP_RECON_ACCOUNT_DATA_MATCH", line 149
ORA-06512: at line 1
at oracle.iam.reconciliation.dao.event.EventMgmtDao.ignoreEventAccountDataMatch(EventMgmtDao.java:527)
at oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.ignoreEvent(ReconOperationsServiceImpl.java:421)
... 54 more
Caused by: java.sql.SQLSyntaxErrorException: ORA-00907: missing right parenthesis
ORA-06512: at "PROD_OIM.XL_SP_RECON_ACCOUNT_DATA_MATCH", line 149
ORA-06512: at line 1
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:213)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1075)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3752)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3937)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:9259)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1535)
at weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:99)
at oracle.iam.reconciliation.dao.event.EventMgmtDao.ignoreEventAccountDataMatch(EventMgmtDao.java:519)
... 55 more
>
<Dec 15, 2011 11:52:16 AM CET> <Error> <OIMCP.ADCS> <BEA-000000> <================= End Stack Trace =======================>
Because of this error: "ORA-06512: at "PROD_OIM.XL_SP_RECON_ACCOUNT_DATA_MATCH", line 149" we recompiled the SQL procedures but nothing has changed.
We also re-run the creation of the reconciliation profile, but is not correctly working.
I want to re-bring to your attention that all those users that have been reconciled before the migration are still working fine, the users that have been reconciled after the migration are subject to this error (and no event is created for them).
Did anyone faced an analogous problem?
Have you any idea about how to fix it?
Thank you

The error is due to the fact that, contrary what written in the documentation, the services shouldn't be restarted until the update process is completed

Compilation error after installing Sun patches

hello,
One of our customer installed teh following Sun patches:
119254-73
124867-14
124863-23
124870-03
124872-07
126495-04
126995-04
127000-13
127001-04
127143-03
118683-05
119963-20
120753-08Now when they compile the application they get the following error:
cd /usr/opt/temip/mmtoolkit/examples/
make -f temip_ef_user_library.make
/opt/SUNWspro/bin/CC -c -m64 -xcode=pic32 -g -xO0 -D_POSIX_PTHREAD_SEMANTICS -mt -pto -I/usr/opt/temip/tfc/include -I//usr/opt/temip/mmtoolkit/include -I//usr/opt/temip/acloc/include -I//usr/opt/temip/ocs/include -D_RWCONFIG_m -o temip_ef_user_library.o temip_ef_user_library.cxx
**"/opt/SUNWspro/prod/include/CC/Cstd/rw/traits", line 535: Error: The function "wcsstr" must have a prototype.*
*1 Error(s) detected.
*** Error code 1
The following command caused the error:
`echo "/opt/SUNWspro/bin/CC -c -m64 -xcode=pic32 -g -xO0 -D_POSIX_PTHREAD_SEMANTICS -mt -pto -I/usr/opt/temip/tfc/include -I//usr/opt/temip/mmtoolkit/include -I//usr/opt/temip/acloc/include -I//usr/opt/temip/ocs/include -D_RWCONFIG_m " | sed 's/[ ][ ]*/ /g'` -o temip_ef_user_library.o temip_ef_user_library.cxx
make: Fatal error: Command failed for target `temip_ef_user_library.o'
does anyone has an idea ?
thank you for your help.
regards,
Christine

Notes for future posting:
1. When you have a question about patches, please also provide the one-line patch description. Otherwise, anyone who might be inclined to help first has to look them up. Making volunteers do extra work to help you for free is not the best strategy. 119254-73 Install and Patch Utilities Patch (unlikely to affect compiling programs)
124867-14 Patch for C 5.9 compiler (unlikely to affect C++ compiling)
124863-23 Patch for Sun C++ 5.9 Compiler (Aha!) <-----------
124870-03 Patch for Sun Performance Library (unlikely to affect compiling programs)
124872-07 Patch for dbx 7.6 Debugger (unlikely to affect compiling programs)
126495-04 Patch for debuginfo handling (unlikely to affect compiling programs)
126995-04 Patch for Performance Analyzer Tools (unlikely to affect compiling programs)
127000-13 Patch for Fortran 95 8.3 Compiler (unlikely to affect C++ compiling)
127001-04 Patch for Fortran 95 8.3 Dynamic Libraries (unlikely to affect compiling programs)
127143-03 Patch for Fortran 95 8.3 Support Library (unlikely to affect compiling programs)
118683-05 Patch for profiling libraries and assembler (could possibly affect compiling C++) <----------
119963-20 Shared library patch for C++ (unlikely to affect C++ compiling)
120753-08 Microtasking libraries (libmtsk) patch (unlikely to affect compiling programs)If you had gone through this exercise, you could have eliminated many of these patches from consideration. For example, a Fortran runtime library patch or a dbx patch cannot cause the C++ compiler to generate a compile-time error that it did not generate before.
2. Put all source code and error messages in "code" tags, as you did with the list of patches. The non-alphanumeric characters in source code and messages can be interpreted as formatting directives instead of being displayed. The result is often nonsense or is hard to read.
Notes on the command line:
1. The -xO0 option is not supported, and has unpredictable results. If you do not want optimization because you want to debug the code, use either no -xOn option, or use -xO1. Using no option is generally preferred: compilation is faster, and the generated code is usually better than with -xO1.
2. The -pto (-instances=static) option is generally a really bad idea. Unless you have a specific reason why you need this template compilation mode, you should remove the -pto option from all command lines (to use the default -instances=global mode), delete all your binaries, and rebuild the application.
Neither of these problems causes the error message, however.
What could be wrong
Also on the command line is a macro definition that appears to be -D_RWCONFIG_m
Is that the correct rendering of the option? If not, please show the command line again inside "code" tags.
I'm concerned that you are trying to override a configuration macro for libCstd, the C++ runtime library. Doing so is not supported and has unpredictable results. If -D_RWCONFIG_m is what is really on the command line, it will not cause a problem with the library.
Except for the possible macro definition issue, finding the problem will require looking at the source code. Since the error message refers to one of the compiler's own headers, the most likely possibilities are
1. A bug in the headers that might be fixed in a later patch -- 124863-23 is not the most recent patch.
2. An error in your code that worked only by accident before. I'm thinking of an inappropriate macro definition.
If you strip everything out of the temip_ef_user_library.cxx file after all the #include directives, you should be able to compile the resulting file and see the same error message. If so, please post that small file here (inside "code" tags).

Fox syntax errors after SEM 600 Patching to SP12

Similar Messages

Maybe you are looking for