Error in reconciliation with invoice subject to wtax on payment

When doing reconcilation to BP ,an error appears "Withholding Tax needs to be processed for at least one of the selected transactions. This can only be done by restricting reconciliation to transactions with the same withholding tax code."
This error appears when we try to reconcile Invoice that is subject to withholding tax on payment. Payment was partial only and the balance is adjusted as CM or JE. When doing the internal recon, the above error appears.
Please let us know how to resolve the problem.
Thanks,
Janice

Hi Jesper,
I read the note and as per my understanding it was the systme behavior of SAP if we reconcile BP with JE or other documents with withholding tax this error will appear. The note does not give any workaround resolution on how to resolve that issue.
Did you guys have any idea on how to resolve or to closed the invoice transactions inc. withholding tax that was partially paid and the remaining balance was done in JE or CM?
Thanks,
Janice

Similar Messages

Error: custom reconciliation (with child data)

I have "HR System" Resource Object (Allow Multiple, Allow All).
Reconciliation Fields:
-HR Tab No [String]
-HR FirstName [String]
-HR LastName [String]
-HR Department [String]
-HR Position [String]
-HR Location [String]
-HR Manager [String]
-Role [Multi-Valued]
---Role [String]
Code:
Hashtable ht = new Hashtable();
Hashtable htc = new Hashtable();
ht.put("HR Tab No" , "1368");
ht.put("HR FirstName" , "ReconUser2");
ht.put("HR LastName" , "ReconUser2");
ht.put("HR Department" , "test");
ht.put("HR Position" , "test");
ht.put("HR Location" , "test");
ht.put("HR Manager" , "test");
long result = l_tcRecon.createReconciliationEvent("HR System", ht, false);
System.out.println("recon key: " + result);
htc.put("Role" , "Role1");
htc.put("Role" , "Role2");
long resultc = l_tcRecon.addMultiAttributeData(result, "Role", htc);
System.out.println("child recon key: " + resultc);
l_tcRecon.providingAllMultiAttributeData(result, "Role", true);
l_tcRecon.finishReconciliationEvent(result);
ReconOperationsService l_objReconService = oimClient.getService(ReconOperationsService.class);
l_objReconService.processReconciliationEvent(result);
Error:
+<Sep 3, 2012 6:39:21 PM GMT+04:00> <Warning> <JNDI> <BEA-050006> <An attempt was made to look up versioned object "ejb.stateless.ClientLoginSessionService#oracle.iam.platformservice.api.ClientLoginSessionServiceRemote" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly and thus being retired prematurely.>+
+<Sep 3, 2012 6:39:23 PM GMT+04:00> <Error> <oracle.iam.reconciliation.dao> <IAM-5010001> <Calling stored procedure - XL_SP_RECONEVALUATEACCOUNT+
intUserKey_in = 1
intEventKey_in = 720563
strRequiredAttributesList_in =
strMappedTableName_in = UD_HRSYS
strTargetTableName_in = RA_HRSYSTEM220
strEntityTableName_in = USR
strAccountMatchingRule_in = ((UD_HRSYS.UD_HRSYS_PERSONID=RA_HRSYSTEM220.RECON_HRTABNO2B020A42))
strEntityMatchingRule_in =
strChildTargetTableName_in =
strChildReqAttributesList_in = >
+<Sep 3, 2012 6:39:23 PM GMT+04:00> <Error> <oracle.iam.reconciliation.impl> <IAM-5010000> <Generic Information: {0}+
oracle.iam.platform.utils.SuperRuntimeException: oracle.iam.platform.utils.SuperRuntimeException: Error occured in XL_SP_RECONEVALUATEACCOUNT while processing Event No 720563 Error occurred in XL_SP_RECONUSERMATCH while processing Event No 720563 One or more input parameter passed as null
at oracle.iam.reconciliation.impl.ActionEngine.processEvent(ActionEngine.java:239)
at oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.processReconciliationEvent(ReconOperationsServiceImpl.java:982)
at oracle.iam.reconciliation.api.ReconOperationsServiceEJB.processReconciliationEventx(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 $Proxy350.processReconciliationEventx(Unknown Source)
at oracle.iam.reconciliation.api.ReconOperationsService_emc07d_ReconOperationsServiceRemoteImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at oracle.iam.reconciliation.api.ReconOperationsService_emc07d_ReconOperationsServiceRemoteImpl.processReconciliationEventx(Unknown Source)
at oracle.iam.reconciliation.api.ReconOperationsService_emc07d_ReconOperationsServiceRemoteImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: oracle.iam.platform.utils.SuperRuntimeException: Error occured in XL_SP_RECONEVALUATEACCOUNT while processing Event No 720563 Error occurred in XL_SP_RECONUSERMATCH while processing Event No 720563 One or more input parameter passed as null
at oracle.iam.reconciliation.dao.ReconActionDao.executeAccountMatch(ReconActionDao.java:482)
at oracle.iam.reconciliation.dao.ReconActionDao.executeAccountMatch(ReconActionDao.java:404)
at oracle.iam.reconciliation.impl.AccountHandler.process(AccountHandler.java:203)
at oracle.iam.reconciliation.impl.ActionEngine.processEvent(ActionEngine.java:197)
at oracle.iam.reconciliation.impl.ReconOperationsServiceImpl.processReconciliationEvent(ReconOperationsServiceImpl.java:982)
at oracle.iam.reconciliation.api.ReconOperationsServiceEJB.processReconciliationEventx(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 $Proxy350.processReconciliationEventx(Unknown Source)
at oracle.iam.reconciliation.api.ReconOperationsService_emc07d_ReconOperationsServiceRemoteImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at oracle.iam.reconciliation.api.ReconOperationsService_emc07d_ReconOperationsServiceRemoteImpl.processReconciliationEventx(Unknown Source)
at oracle.iam.reconciliation.api.ReconOperationsService_emc07d_ReconOperationsServiceRemoteImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Please, help!

A_Sergey wrote:
Thanks, but how can I set this parameter?Really do not know. I've just traced your problem down to the PL/SQL procedure, that generates the error message.
I suppose you have no means to set the name explicitly. Rather something is wrong with your configuration.
Regards,
Vladimir

IMAP Email Portlet Error accessing email with blank subject field

I have sucessfully deployed imap portlet and added it to a page. I am able to read and compose emails. However while testing the portlet I ran into few problems:
1. Cannot read an email from inbox if the subject field of email is blank. Only way to read this email is to first select an email that has a subject and then navigate through "next" or "previous" button to read this email.
2. Some of the emails does not show the attachments. Some of them dooes show it. I am unable to figure why is it doing so.
3. It takes too long to load and sometimes ends up in "portlet time out".
Has anyone else also ran into such problems. Is there a solution to these problems.
Thanks
Abhishek Periwal

Thanks for early reply.
I analayzed my emails and figured out that email that are forwarded to me with some attachments have problems. These emails do not include the actual attachments , they only include the text part written by the sender. It will be great if this bug gets fixed.
Secondly I increased the time out and it helped. Thanks for your suggestion.
Thanks
Abhishek

TDS TAX AMOUNT IS NOT MACHING WITH INVOICE WTAX AMOUNTu2019

Dear All,
I am Facing Following Problem in TDS
While creating an A/P Invoice after putting row level information when user click on u2018ADDu2019 button u201CWithholding Tax Tableu201D opens for deduction of TDS amount. When user selects u201CWithholding Tax Codeu201D in u201CWithholding Tax Tableu201D to deduct TDS amount for an invoice system shows WTax amount as per rate of deduction. But when user click on u2018OKu2019 to u201CWithholding Tax Tableu201D window, WTax Amount will comes as zero on A/P Invoice window.
Then when again user will go to u201CWithholding Tax Tableu201D and manually put the value of WTax Amount system reflects it on A/P Invoice window.
In case when we set approval procedure to A/P Invoice, this invoice goes for an approval. After coming back as approved invoice when originator of invoice going to u2018ADDu2019 the same document system shows an error as u2018TDS TAX AMOUNT IS NOT MACHING WITH INVOICE WTAX AMOUNTu2019
please reply me ASAP
Thanks & Regards,
Swapnil

hi
try this
We need to follow the following steps
u2022     Open the BP master for which TDS needs to be deducted go to the accounting tab followed by tax option and then click on the checkbox subject to withholding tax
u2022     Click on the option WTAX codes Allowed and select the TDS Category
u2022     On the previous window click the check box pertaining the checkbox u201CTDS OVERLOOKu201D
Regards,
Manish

Payment reconciliation with A/R Invoice + close Invoice

Hi Again,
I am doing a Payment directly from A/R Invoice; but the A/R Invoice is still Open and there is no reconciliation between the Payment and the A/R Invoice.
Any code sample you can give me to close A/R Invoice with reconciliation of the Payment, and if half paid I assume the A/R Invoice is still open and the A/R Invoice is reconciliated with the payment?
See my code below which is missing the reconciliation.
Thank you
Rune
oPayments = (SAPbobsCOM.Payments)oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oIncomingPayments);
                    oPayments.CardCode = vmp_CardCode_string;
                    oPayments.DocDate = DateTime.Now;
                    oPayments.JournalRemarks = "Incoming - Payment Bank Transfer";
                    oPayments.TaxDate = DateTime.Now;
                    SAPbobsCOM.Recordset oRecordset_BankAccount = null;
                    oRecordset_BankAccount = ((SAPbobsCOM.Recordset)(oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)));
                    oRecordset_BankAccount.DoQuery("SELECT * FROM [dbo].[@PAY_TYPE] WHERE [U_PayMethod] = '01'");
                    oRecordset_BankAccount.MoveFirst();
                    if (oRecordset_BankAccount.EoF == true) // No Records
                    else
                        vmp_BankAccount_string = Convert.ToString(oRecordset_BankAccount.Fields.Item("U_BankAccount").Value);
                    oPayments.TransferAccount = vmp_BankAccount_string;// "_SYS00000000343"; //"1010140-001";
                    oPayments.TransferDate = DateTime.Now;
                    oPayments.TransferReference = vmp_CardCode_string;
                    oPayments.TransferSum = vmp_Amount_double;
                    vc_Message_Result_Int32 = oPayments.Add();

Hi,
I assume I have to add following code to my payment to close the invoice; see below.
But I get following error:
Invalid total [(----) 131-44]
Thank you,
Rune
oPayments = (SAPbobsCOM.Payments)oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oIncomingPayments);
oPayments.Invoices.AppliedFC = 0;
oPayments.Invoices.DocEntry = vmp_DocEntry_Int32;
oPayments.Invoices.DocLine = 0;
oPayments.Invoices.InvoiceType = SAPbobsCOM.BoRcptInvTypes.it_Invoice;//13;
oPayments.Invoices.SumApplied = vmp_Amount_double;
oPayments.Invoices.Add();
oPayments.CardCode = vmp_CardCode_string;
oPayments.DocDate = DateTime.Now;
oPayments.JournalRemarks = "Incoming - Payment Cash";
oPayments.TaxDate = DateTime.Now;
oPayments.CashAccount = vm_CachAccountNumber_string;    //"_SYS00000000342"
oPayments.CashSum = vmp_Amount_double;
vc_Message_Result_Int32 = oPayments.Add();
if (vc_Message_Result_Int32 != 0)          // Check the result

Automatic bank reconciliation with Electronic bank statement

Deal All,
As mentioned in the subject of this mail, this is to request for your inputs to advice the configuration steps with process for Configuration of Electronic Bank Statment in R3 to eneble the user for automatic bank reconciliation with clearing customer/vendor open items.Please send confi doc.
Request you to provide documentation if possible along with your valuble advices.
cvs

Hi
I implemented the EBS in my company 4 month ago and here are some advises on the problems i experienced in the setup process. As for the setup process it is straightforward just read the manual at help.sap.com.
We used the MT940 format for importing bank statements from our bank.
The first thing i would advice you to do is make a list of all the possible transactions that are to be handled by the EBS application.
Then make estimation of how many payments that are recieved in constant structured way which the EBS can handle. (invoice number in the text)
The people in our accounting department complained alot about the output format in the EBS not being userfreindly compared to the advises they recieved in e-mail form from the bank so if not the bulk of your payments can be processed automatically it might not be worth the trouble to implement it. (i still think they uses the the email to postprocess the transactions that was not automatically cleraed)
Make sure you havent got any other applications handling some of the transactions that are contained in the bank statement because this wont work. eg. we had a program automatically placing fx trades on customer and bank account which meant that when we recieved the fx trade on the statement it was already placed and therefore had to be placed on a interims account for later reversal.
We get alot of bankcharges on our payments and we set up the EBS to place them automatically on a bankcharge account if the difference between the recieved amount on the invoice was less that 30 dollars.(we just assume that a difference is a bank charge) This means that a customer if he wants to always can pay x dollars under the invoice amount because it will be automatically processed and therefore go unnoticed.
Establish a contact in your bank who knows how their MT940 format has been structured.
Then contact your bank and get them to provide some test statements of old bank statements.
Make sure that you are not the first customer for using the MT940 format or else you will end up being ginny pig for the banks possible mistakes.
As i learned the way banks interpret the MT940 format guidelines can varry quite alot eg. the ocmt field our bank interpreted as the original payed amount in its original currency. SAP inprets this field as the recieved amount in its original currency and therefore it always try to clear the OCMT amount if availleble which meant it always tried to clear the original amount even though there had been taken som bankcharges underways.
I also found out that our bank didnt really bother to specify the type of transaction (interest, fx contract, bank charges, check and so on) which meant we only had two external transaction codes availleble s103 for incomming payments and ntrf for outgoing payments. This gave alot of trouble as i had to identify the type of transaction through seach algorithms.
Our bank also had trouble creating the MT940 file because it has a limited number of characters availleble which meant in the initial file that it only gave the first x characters of each line and then left out the rest. This meant that the text was broken into alot of pieces and you hardly ever had a complete invoice number to clear on. We had the bank altering their format so they now leave out text at the end of the transaction instead.
In the implementation process we experienced that the EBS application created a payment advice each time the amount of the payment didnt match the invoice in the system. We implemented a note from service.sap which disabled this and just assigned the difference to a bankcharge account.
I dont know if you can use these advices but just felt i would try to warn you about the potential problems that i experienced in the process. .
If you have concrete questions to the EBS setup feel free to contact me and i will see if i can help you.

Error : Reverse an AR invoice having downpayment linked to it.

Hi,
I am facing a problem in reversing a AR Invoice having a downpayment through AR credit Memo. System displays a message as - Copying an invoice which includes a down payment is not currently supported [Message 3703-18]
I am opening the AR invoice and doing the option of Copy to AR credit Memo.
I am using SAP Business One 2005B with patch level 39.
Kindly guide me in this matter.
Thanks and Regards,
Kawish

Dear,
To my understanding,original payment was linked to the Down payment and when you tried to cancel the second incoming payment which was linked with the invoice and original payment,the system blocked it and error message poped up.It is current behavior.
1) payment for the down payment invoice cannot be cancelled if it was withrawn to AR invoice. It can be done after the AR invoice will be credited. However, we have another limitation:
2) the invoice cannot be credited if it closed/reconciled.
And one more:
3) cancelling of the manual reconciliation does not open the invoice.
Wish the information above is helpful for you.
Regards
Apple

Error in Reconciliation

When I reconcile my Ldap resource to IDM, getting an error. the reconciliation status shows:
Error iterating accounts for resource ESAALDAP:
com.waveset.exception.OperationTimedOut: The wait for a response exceeded the configured timeout while listing accounts on resource '<Resource-Name>'.
Can anyone help how I can increase the wait time?..
Thanks
Bino

Hi Jesper,
I read the note and as per my understanding it was the systme behavior of SAP if we reconcile BP with JE or other documents with withholding tax this error will appear. The note does not give any workaround resolution on how to resolve that issue.
Did you guys have any idea on how to resolve or to closed the invoice transactions inc. withholding tax that was partially paid and the remaining balance was done in JE or CM?
Thanks,
Janice

Error while raising a invoice using VF01

Hi,
I am getting an error while raising a invoice using VF01.
Error as follows
RV_MESSAGE_UPDATE
Update was terminated
System ID....   TIP
Client.......   300
User.....   user1
Transaction..   VF01
Update key...   E66E6454075548D8922BAC091E81F0CB
Generated....   18.07.2007, 18:57:38
Completed....   18.07.2007, 18:57:38
Error info...   TD 443: WRITE_FORM
Pls help
Points will be rewarded.
Thanks

Hi,
This is an ABAP short dump. If you go through the error log, there will be a section where in you can see > What caused the problem.
Try to analyze this log and you can find a solution. Probably, you can also check whether there is any OSS note with this error message.
Thanks
Murali.

Purchase Order Reprot with Invoice verification details

Hi Friends,
I need a SAP standard report, in which I can get the PO details for a perticular period of release date along with Invoice verification details, i.e. how much value has been passed and how much is pending.
Can you please suggest any SAP standard report for the Subject.
Kraheja.

Hi
Check ME2n report with selection parameter as GUTSCHRIFT or ME80fn with purchase order history.
Thanks

Error while creating Excise Invoice

Hi All,
Can any one help me on CIN?
I am getting one error while creating "Excise Invoice [T.code J1ILN]" i.e. "System failure during locking GL account Cocode by 13113910"
Regards
Chowdary

Dear Raghavendra
Please make a try with the following but I am not sure whether it will solve your problem.
Go to FS00, give the G/L account which has the problem and select "Control Data" tab. Here punch as asterisk in the field "Tax category" and save.
Now try to create the excise invoice.
Thanks
G. Lakshmipathi

Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

Hello Everyone.
I've run into something quite strange and am hoping you can help me.
I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
When I run the report, al of the columns show up as expected.
However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
If I put back the "*", I then encounter this error again.
I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
I've seen this same error mentioned in connection with forms but never with a report.
So, is there some limit to the number of columns one can have in a "classic" or interactive report?
Any idea why I would be getting this error?
Here is the DDL for my table pvtab:
CREATE TABLE "PVTAB"
 ( "MICRO" VARCHAR2(4),
 "PRIM" VARCHAR2(4),
 "UNIT" NUMBER,
 "SEC_REF_1" NUMBER,
 "SECN_1" VARCHAR2(88),
 "SEC_REF_2" NUMBER,
 "SECN_2" VARCHAR2(88),
 "SEC_REF_3" NUMBER,
 "SECN_3" VARCHAR2(88),
 "SEC_REF_4" NUMBER,
 "SECN_4" VARCHAR2(88),
 "SEC_REF_5" NUMBER,
 "SECN_5" VARCHAR2(88),
 "SEC_REF_6" NUMBER,
 "SECN_6" VARCHAR2(88),
 "SEC_REF_7" NUMBER,
 "SECN_7" VARCHAR2(88),
 "SEC_REF_8" NUMBER,
 "SECN_8" VARCHAR2(88),
 "SEC_REF_9" NUMBER,
 "SECN_9" VARCHAR2(88),
 "SEC_REF_10" NUMBER,
 "SECN_10" VARCHAR2(88),
 "SEC_REF_11" NUMBER,
 "SECN_11" VARCHAR2(88),
 "SEC_REF_12" NUMBER,
 "SECN_12" VARCHAR2(88),
 "SEC_REF_13" NUMBER,
 "SECN_13" VARCHAR2(88),
 "SEC_REF_14" NUMBER,
 "SECN_14" VARCHAR2(88),
 "SEC_REF_15" NUMBER,
 "SECN_15" VARCHAR2(88),
 "SEC_REF_16" NUMBER,
 "SECN_16" VARCHAR2(88),
 "SEC_REF_17" NUMBER,
 "SECN_17" VARCHAR2(88),
 "SEC_REF_18" NUMBER,
 "SECN_18" VARCHAR2(88),
 "SEC_REF_19" NUMBER,
 "SECN_19" VARCHAR2(88),
 "SEC_REF_20" NUMBER,
 "SECN_20" VARCHAR2(88),
 "SEC_REF_21" NUMBER,
 "SECN_21" VARCHAR2(88),
 "SEC_REF_22" NUMBER,
 "SECN_22" VARCHAR2(88),
 "SEC_REF_23" NUMBER,
 "SECN_23" VARCHAR2(88),
 "SEC_REF_24" NUMBER,
 "SECN_24" VARCHAR2(88),
 "SEC_REF_25" NUMBER,
 "SECN_25" VARCHAR2(88),
 "SEC_REF_26" NUMBER,
 "SECN_26" VARCHAR2(88),
 "SEC_REF_27" NUMBER,
 "SECN_27" VARCHAR2(88),
 "SEC_REF_28" NUMBER,
 "SECN_28" VARCHAR2(88),
 "SEC_REF_29" NUMBER,
 "SECN_29" VARCHAR2(88),
 "SEC_REF_30" NUMBER,
 "SECN_30" VARCHAR2(88),
 "SEC_REF_31" NUMBER,
 "SECN_31" VARCHAR2(88),
 "SEC_REF_32" NUMBER,
 "SECN_32" VARCHAR2(88),
 "SEC_REF_33" NUMBER,
 "SECN_33" VARCHAR2(88),
 "SEC_REF_34" NUMBER,
 "SECN_34" VARCHAR2(88),
 "SEC_REF_35" NUMBER,
 "SECN_35" VARCHAR2(88),
 "SEC_REF_36" NUMBER,
 "SECN_36" VARCHAR2(88),
 "SEC_REF_37" NUMBER,
 "SECN_37" VARCHAR2(88),
 "SEC_REF_38" NUMBER,
 "SECN_38" VARCHAR2(88),
 "SEC_REF_39" NUMBER,
 "SECN_39" VARCHAR2(88),
 "SEC_REF_40" NUMBER,
 "SECN_40" VARCHAR2(88),
 "SEC_REF_41" NUMBER,
 "SECN_41" VARCHAR2(88),
 "SEC_REF_42" NUMBER,
 "SECN_42" VARCHAR2(88),
 "SEC_REF_43" NUMBER,
 "SECN_43" VARCHAR2(88),
 "SEC_REF_44" NUMBER,
 "SECN_44" VARCHAR2(88),
 "SEC_REF_45" NUMBER,
 "SECN_45" VARCHAR2(88),
 "SEC_REF_46" NUMBER,
 "SECN_46" VARCHAR2(88),
 "SEC_REF_47" NUMBER,
 "SECN_47" VARCHAR2(88),
 "SEC_REF_48" NUMBER,
 "SECN_48" VARCHAR2(88),
 "SEC_REF_49" NUMBER,
 "SECN_49" VARCHAR2(88),
 "SEC_REF_50" NUMBER,
 "SECN_50" VARCHAR2(88),
 "SEC_REF_51" NUMBER,
 "SECN_51" VARCHAR2(88),
 "SEC_REF_52" NUMBER,
 "SECN_52" VARCHAR2(88),
 "SEC_REF_53" NUMBER,
 "SECN_53" VARCHAR2(88),
 "SEC_REF_54" NUMBER,
 "SECN_54" VARCHAR2(88),
 "SEC_REF_55" NUMBER,
 "SECN_55" VARCHAR2(88),
 "SEC_REF_56" NUMBER,
 "SECN_56" VARCHAR2(88),
 "SEC_REF_57" NUMBER,
 "SECN_57" VARCHAR2(88),
 "SEC_REF_58" NUMBER,
 "SECN_58" VARCHAR2(88),
 "SEC_REF_59" NUMBER,
 "SECN_59" VARCHAR2(88),
 "SEC_REF_60" NUMBER,
 "SECN_60" VARCHAR2(88),
 "SEC_REF_61" NUMBER,
 "SECN_61" VARCHAR2(88),
 "SEC_REF_62" NUMBER,
 "SECN_62" VARCHAR2(88),
 "SEC_REF_63" NUMBER,
 "SECN_63" VARCHAR2(88),
 "SEC_REF_64" NUMBER,
 "SECN_64" VARCHAR2(88),
 "SEC_REF_65" NUMBER,
 "SECN_65" VARCHAR2(88),
 "SEC_REF_66" NUMBER,
 "SECN_66" VARCHAR2(88),
 "SEC_REF_67" NUMBER,
 "SECN_67" VARCHAR2(88),
 "SEC_REF_68" NUMBER,
 "SECN_68" VARCHAR2(88),
 "SEC_REF_69" NUMBER,
 "SECN_69" VARCHAR2(88),
 "SEC_REF_70" NUMBER,
 "SECN_70" VARCHAR2(88),
 "SEC_REF_71" NUMBER,
 "SECN_71" VARCHAR2(88),
 "SEC_REF_72" NUMBER,
 "SECN_72" VARCHAR2(88),
 "SEC_REF_73" NUMBER,
 "SECN_73" VARCHAR2(88),
 "SEC_REF_74" NUMBER,
 "SECN_74" VARCHAR2(88),
 "SEC_REF_75" NUMBER,
 "SECN_75" VARCHAR2(88),
 "SEC_REF_76" NUMBER,
 "SECN_76" VARCHAR2(88),
 "SEC_REF_77" NUMBER,
 "SECN_77" VARCHAR2(88),
 "SEC_REF_78" NUMBER,
 "SECN_78" VARCHAR2(88),
 "SEC_REF_79" NUMBER,
 "SECN_79" VARCHAR2(88),
 "SEC_REF_80" NUMBER,
 "SECN_80" VARCHAR2(88),
 "SEC_REF_81" NUMBER,
 "SECN_81" VARCHAR2(88),
 "SEC_REF_82" NUMBER,
 "SECN_82" VARCHAR2(88),
 "SEC_REF_83" NUMBER,
 "SECN_83" VARCHAR2(88),
 "SEC_REF_84" NUMBER,
 "SECN_84" VARCHAR2(88),
 "SEC_REF_85" NUMBER,
 "SECN_85" VARCHAR2(88),
 "SEC_REF_86" NUMBER,
 "SECN_86" VARCHAR2(88),
 "SEC_REF_87" NUMBER,
 "SECN_87" VARCHAR2(88),
 "SEC_REF_88" NUMBER,
 "SECN_88" VARCHAR2(88),
 "SEC_REF_89" NUMBER,
 "SECN_89" VARCHAR2(88),
 "SEC_REF_90" NUMBER,
 "SECN_90" VARCHAR2(88),
 "SEC_REF_91" NUMBER,
 "SECN_91" VARCHAR2(88),
 "SEC_REF_92" NUMBER,
 "SECN_92" VARCHAR2(88),
 "SEC_REF_93" NUMBER,
 "SECN_93" VARCHAR2(88),
 "SEC_REF_94" NUMBER,
 "SECN_94" VARCHAR2(88),
 "SEC_REF_95" NUMBER,
 "SECN_95" VARCHAR2(88),
 "SEC_REF_96" NUMBER,
 "SECN_96" VARCHAR2(88),
 "SEC_REF_97" NUMBER,
 "SECN_97" VARCHAR2(88),
 "SEC_REF_98" NUMBER,
 "SECN_98" VARCHAR2(88),
 "SEC_REF_99" NUMBER,
 "SECN_99" VARCHAR2(88),
 "SEC_REF_100" NUMBER,
 "SECN_100" VARCHAR2(88),
 "SEC_REF_101" NUMBER,
 "SECN_101" VARCHAR2(88),
 "SEC_REF_102" NUMBER,
 "SECN_102" VARCHAR2(88),
 "SEC_REF_103" NUMBER,
 "SECN_103" VARCHAR2(88),
 "SEC_REF_104" NUMBER,
 "SECN_104" VARCHAR2(88),
 "SEC_REF_105" NUMBER,
 "SECN_105" VARCHAR2(88),
 "SEC_REF_106" NUMBER,
 "SECN_106" VARCHAR2(88),
 "SEC_REF_107" NUMBER,
 "SECN_107" VARCHAR2(88),
 "SEC_REF_108" NUMBER,
 "SECN_108" VARCHAR2(88),
 "SEC_REF_109" NUMBER,
 "SECN_109" VARCHAR2(88),
 "SEC_REF_110" NUMBER,
 "SECN_110" VARCHAR2(88),
 "SEC_REF_111" NUMBER,
 "SECN_111" VARCHAR2(88),
 "SEC_REF_112" NUMBER,
 "SECN_112" VARCHAR2(88),
 "SEC_REF_113" NUMBER,
 "SECN_113" VARCHAR2(88),
 "SEC_REF_114" NUMBER,
 "SECN_114" VARCHAR2(88),
 "SEC_REF_115" NUMBER,
 "SECN_115" VARCHAR2(88),
 "SEC_REF_116" NUMBER,
 "SECN_116" VARCHAR2(88),
 "SEC_REF_117" NUMBER,
 "SECN_117" VARCHAR2(88),
 "SEC_REF_118" NUMBER,
 "SECN_118" VARCHAR2(88),
 "SEC_REF_119" NUMBER,
 "SECN_119" VARCHAR2(88),
 "SEC_REF_120" NUMBER,
 "SECN_120" VARCHAR2(88),
 "SEC_REF_121" NUMBER,
 "SECN_121" VARCHAR2(88),
 "SEC_REF_122" NUMBER,
 "SECN_122" VARCHAR2(88),
 "SEC_REF_123" NUMBER,
 "SECN_123" VARCHAR2(88),
 "SEC_REF_124" NUMBER,
 "SECN_124" VARCHAR2(88),
 "SEC_REF_125" NUMBER,
 "SECN_125" VARCHAR2(88),
 "SEC_REF_126" NUMBER,
 "SECN_126" VARCHAR2(88),
 "SEC_REF_127" NUMBER,
 "SECN_127" VARCHAR2(88),
 "SEC_REF_128" NUMBER,
 "SECN_128" VARCHAR2(88),
 "SEC_REF_129" NUMBER,
 "SECN_129" VARCHAR2(88),
 "SEC_REF_130" NUMBER,
 "SECN_130" VARCHAR2(88),
 "SEC_REF_131" NUMBER,
 "SECN_131" VARCHAR2(88),
 "SEC_REF_132" NUMBER,
 "SECN_132" VARCHAR2(88),
 "SEC_REF_133" NUMBER,
 "SECN_133" VARCHAR2(88),
 "SEC_REF_134" NUMBER,
 "SECN_134" VARCHAR2(88),
 "SEC_REF_135" NUMBER,
 "SECN_135" VARCHAR2(88),
 "SEC_REF_136" NUMBER,
 "SECN_136" VARCHAR2(88),
 "SEC_REF_137" NUMBER,
 "SECN_137" VARCHAR2(88),
 "SEC_REF_138" NUMBER,
 "SECN_138" VARCHAR2(88),
 "SEC_REF_139" NUMBER,
 "SECN_139" VARCHAR2(88),
 "SEC_REF_140" NUMBER,
 "SECN_140" VARCHAR2(88),
 "SEC_REF_141" NUMBER,
 "SECN_141" VARCHAR2(88),
 "SEC_REF_142" NUMBER,
 "SECN_142" VARCHAR2(88),
 "SEC_REF_143" NUMBER,
 "SECN_143" VARCHAR2(88),
 "SEC_REF_144" NUMBER,
 "SECN_144" VARCHAR2(88),
 "SEC_REF_145" NUMBER,
 "SECN_145" VARCHAR2(88),
 "SEC_REF_146" NUMBER,
 "SECN_146" VARCHAR2(88),
 "SEC_REF_147" NUMBER,
 "SECN_147" VARCHAR2(88),
 "SEC_REF_148" NUMBER,
 "SECN_148" VARCHAR2(88),
 "SEC_REF_149" NUMBER,
 "SECN_149" VARCHAR2(88),
 "SEC_REF_150" NUMBER,
 "SECN_150" VARCHAR2(88),
 "SEC_REF_151" NUMBER,
 "SECN_151" VARCHAR2(88),
 "SEC_REF_152" NUMBER,
 "SECN_152" VARCHAR2(88),
 "SEC_REF_153" NUMBER,
 "SECN_153" VARCHAR2(88),
 "SEC_REF_154" NUMBER,
 "SECN_154" VARCHAR2(88),
 "SEC_REF_155" NUMBER,
 "SECN_155" VARCHAR2(88),
 "SEC_REF_156" NUMBER,
 "SECN_156" VARCHAR2(88),
 "SEC_REF_157" NUMBER,
 "SECN_157" VARCHAR2(88),
 "SEC_REF_158" NUMBER,
 "SECN_158" VARCHAR2(88),
 "SEC_REF_159" NUMBER,
 "SECN_159" VARCHAR2(88),
 "SEC_REF_160" NUMBER,
 "SECN_160" VARCHAR2(88),
 "SEC_REF_161" NUMBER,
 "SECN_161" VARCHAR2(88),
 "SEC_REF_162" NUMBER,
 "SECN_162" VARCHAR2(88),
 "SEC_REF_163" NUMBER,
 "SECN_163" VARCHAR2(88),
 "SEC_REF_164" NUMBER,
 "SECN_164" VARCHAR2(88),
 "SEC_REF_165" NUMBER,
 "SECN_165" VARCHAR2(88),
 "SEC_REF_166" NUMBER,
 "SECN_166" VARCHAR2(88),
 "SEC_REF_167" NUMBER,
 "SECN_167" VARCHAR2(88),
 "SEC_REF_168" NUMBER,
 "SECN_168" VARCHAR2(88),
 "SEC_REF_169" NUMBER,
 "SECN_169" VARCHAR2(88),
 "SEC_REF_170" NUMBER,
 "SECN_170" VARCHAR2(88),
 "SEC_REF_171" NUMBER,
 "SECN_171" VARCHAR2(88),
 "SEC_REF_172" NUMBER,
 "SECN_172" VARCHAR2(88),
 "SEC_REF_173" NUMBER,
 "SECN_173" VARCHAR2(88),
 "SEC_REF_174" NUMBER,
 "SECN_174" VARCHAR2(88),
 "SEC_REF_175" NUMBER,
 "SECN_175" VARCHAR2(88),
 "SEC_REF_176" NUMBER,
 "SECN_176" VARCHAR2(88),
 "SEC_REF_177" NUMBER,
 "SECN_177" VARCHAR2(88),
 "SEC_REF_178" NUMBER,
 "SECN_178" VARCHAR2(88),
 "SEC_REF_179" NUMBER,
 "SECN_179" VARCHAR2(88),
 "SEC_REF_180" NUMBER,
 "SECN_180" VARCHAR2(88),
 "SEC_REF_181" NUMBER,
 "SECN_181" VARCHAR2(88),
 "SEC_REF_182" NUMBER,
 "SECN_182" VARCHAR2(88),
 "SEC_REF_183" NUMBER,
 "SECN_183" VARCHAR2(88),
 "SEC_REF_184" NUMBER,
 "SECN_184" VARCHAR2(88),
 "SEC_REF_185" NUMBER,
 "SECN_185" VARCHAR2(88),
 "SEC_REF_186" NUMBER,
 "SECN_186" VARCHAR2(88),
 "SEC_REF_187" NUMBER,
 "SECN_187" VARCHAR2(88),
 "SEC_REF_188" NUMBER,
 "SECN_188" VARCHAR2(88),
 "SEC_REF_189" NUMBER,
 "SECN_189" VARCHAR2(88),
 "SEC_REF_190" NUMBER,
 "SECN_190" VARCHAR2(88),
 "SEC_REF_191" NUMBER,
 "SECN_191" VARCHAR2(88),
 "SEC_REF_192" NUMBER,
 "SECN_192" VARCHAR2(88),
 "SEC_REF_193" NUMBER,
 "SECN_193" VARCHAR2(88),
 "SEC_REF_194" NUMBER,
 "SECN_194" VARCHAR2(88),
 "SEC_REF_195" NUMBER,
 "SECN_195" VARCHAR2(88),
 "SEC_REF_196" NUMBER,
 "SECN_196" VARCHAR2(88),
 "SEC_REF_197" NUMBER,
 "SECN_197" VARCHAR2(88),
 "SEC_REF_198" NUMBER,
 "SECN_198" VARCHAR2(88),
 "SEC_REF_199" NUMBER,
 "SECN_199" VARCHAR2(88),
 "SEC_REF_200" NUMBER,
 "SECN_200" VARCHAR2(88),
 "SEC_REF_201" NUMBER,
 "SECN_201" VARCHAR2(88),
 "SEC_REF_202" NUMBER,
 "SECN_202" VARCHAR2(88),
 "SEC_REF_203" NUMBER,
 "SECN_203" VARCHAR2(88),
 "SEC_REF_204" NUMBER,
 "SECN_204" VARCHAR2(88),
 "SEC_REF_205" NUMBER,
 "SECN_205" VARCHAR2(88),
 "SEC_REF_206" NUMBER,
 "SECN_206" VARCHAR2(88),
 "SEC_REF_207" NUMBER,
 "SECN_207" VARCHAR2(88),
 "SEC_REF_208" NUMBER,
 "SECN_208" VARCHAR2(88)
 );Thank you for any help/advice.
Elie
Edited by: EEG on Jun 12, 2011 2:09 PM

So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
>
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
>
Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
Workaround:
Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
Getting More Help:
This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
Also:
<li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
<li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
Finally:
Somebody's bound to ask, so we might as well get started:
<li>Why so many columns?
<li>What requirement is this trying to fulfil?

Tax error when posting vendor invoice

Dear Friends ,
I am posting this 3rd time, I am geting this error when poatin vendor invoice , I am geting this error in production system before GOLIVE ,when we are doing live data entry test . All the seting related to taxes has been testing more than 10times , But we are unable to find the problem . We had checked with all past messages and best possible solution in SDN ......but problem is not solved . Said error is as follows ....
Tax code V0 country IN does not exist in procedure TAXINN
Message no. FF713
Diagnosis
You entered a tax code which is not defined for the country of the company code to be posted to in the tax calculation procedure.
System Response
Procedure
Check and, if necessary, correct the entry.
Procedure for System Administration
If it is not an input error, check and possibly change the system settings.
To do this, choose Maintain entries (F5).
Check whether the company code is assigned to the correct country and whether the correct tax calculation procedure has been entered for the company code country.
Create a new tax code if necessary.
Caution:
Since it is possible that the tables in question are being updated at a different time on another computer, it can take a certain amount of time for the tax code to be on all local machines in client server architectures after saving the new code.
Raghu

hi
go to ftxp choose tax code v0
here in first input field give 00
then select that field and click on gl acct tab
here mention a gl or go to ob40 and mention gl for the acct key of that field
try finding
Tax code country IN does not exist in procedure TAXINN
on SDN u will get many threads
Tax code XX country IN does not exist in procedure TAXINN (MIRO Error)
conclusion is u must get acct for at least one condition in the tax code
regrads
kunal
award if helpful

Error while parking MIRO invoice

Hi All,
Could anyone please help with the error while parking the invoice through MIR7 :
"Return code 8 is not permitted with Badi fagl_period_check"
Thanks,
SKE

Hi SKE,
Could you please apply the note 1240979 to solve the error you are receiving? It should resolve it.
Best Regards,
Vanessa.

Error message control for invoice w/o PO in SRM

Hi,
Anyone know how to setup error message if invoice value limit is above e.g. 10000 USD? Invoice will be entered without PO.
There will be no PO but invoice will be created and user should get error message if total invoiced value is above 10000 USD.
We are in SRM_SERVER5.5 with SP 06.
If anyone came across during IMS setup, please help me on it.
Thanks in advance.
Regards,
Rahul Mandale

Hi Atul,
Thanks for your useful answer. I am getting error message while creation of invoice. But problem is that it is throwing message for all invocie, need to consider if condition of 'GROSS_AMOUNT >= 1000 USD. During creation of invoice, it should throw msg 001 (YIMS) which I have configured as my exception in IMS when fulfills the condition.
I am sending code for 'CHANGE' and "CHECK' BADI.
Can you check and suggest the correction? Where I need to put this conditon for pop up of error while gross_amount >= 1000 while creation and change of invoice??
Thanks in advance.
regards,
Rahul
method IF_EX_BBP_DOC_CHANGE_BADI~BBP_IV_CHANGE.
DATA: ls_header TYPE bbp_pds_inv_header_d,
 lt_messages TYPE TABLE OF bbp_smessages_badi,
 ls_message TYPE bbp_smessages_badi,
 lf_dummy TYPE c,
 lf_gross_amount TYPE BBP_IV_AMOUNT,
 i_guid TYPE BBP_GUID .
get data of the invoice from guid
CALL FUNCTION 'BBP_PD_INV_GETDETAIL'
 EXPORTING
 i_guid = i_guid
 IMPORTING
 e_header = ls_header.
IF ls_header-GROSS_AMOUNT >= 1000.
CLEAR ls_message.
 ls_message-msgty = 'E'.
 ls_message-msgid = 'YIMS'.
 ls_message-msgno = '001'.
APPEND ls_message to lt_messages.
 EXIT.
ENDIF.
method IF_EX_BBP_DOC_CHECK_BADI~BBP_DOC_CHECK.
Data ls_message TYPE bbp_smessages_badi.
*To create custom message
 clear ls_message.
 ls_message-msgty = 'E'.
 ls_message-msgid = 'YIMS'.
 ls_message-msgno = '001'.
 append ls_message to et_messages.
endmethod.

Error in reconciliation with invoice subject to wtax on payment

Similar Messages

Maybe you are looking for