F110 Run APP Error in creating payment document, read job log

We are having 2 Bank Accounts ie from SBI and ICICI Bank.
While making the Automatic payment run we are getting an error.
where in i have checked all the configuration for it in Vendor Master, FBZP, House Banks,
While maintaining the F110 Variant Checked the same house bank given in Vendor Master is Placed,
But we are able to get the other bank as Source and payment also, but not able to generate a report from other bank
through reallocate we able to give payment method, and house bank.

Dear,
Please let us know what is the error you are getting. For this you need to go to SM37 and check the log of Payment Run.
Please revert.
Br,Vivek

Similar Messages

F110 " Error in creating the payment document; read job log"

Hi all,
when i execute payment in Tcode F110, getting message " Error in creating the payment document; read job log".
Log for payment run for payment on 30.07.2009, identification TEST1
Error in the recovery of constants
Information re. vendor 1000040256 / paying company code BG10 ...
... payment not possible because of reported error
Because of it, the payment file is also not generated.
The status says " Payment run has been carried out".
But when the open items are cleared.
What could be the reason for this error message?
Regards,
Vidya

Hi,
As the document is in the cleared status, you can try finding out with which run date and run id the documents got cleared. Go to Transaction code SE12 and give the following details - Company code, vendor code and the payment documents (clearing document for the invoice) or you can also give the invoice document numbers and fiscal year.
The output will tell you which payment run id and run date was used to process the payment.
Hope this will help you understand what has happened.
Thanks and Regards,
Anit
Edited by: Anit Mangat on Jul 30, 2009 4:38 PM

Error in creating the payment document; read job log

Hi All,
Recently we are upgraded to EHP4 pack. While running the payment proposal for the vendor I am getting the error 007 "Error in creating the payment document;read job log" Details of job log is as follows
>            Due date determination additional log
> Document 1100001518 line item 001 via ILS          694.00-
> Terms of payment: 05/23/2011   60 0.000 %    0 0.000 %    0
> 01 days grace period is being considered
> Maximum cash discount should always be taken
>   Payment must take place before 07/23/2011; next payment on 07/27/2011
> Item is due with 0.000 % cash discount
Internal error: doc.balance not zero / comp.code SNXL vendor 1009530510 customer
Balances:        2,052.00- ILS /        2,052.00- ILS
>
>            Posting documents additional log
> Currencies in line 1: ILS / ILS Currencies in line 2: USD / ___
> Document company code SNXL currency ILS payment method T
> LIt PK Acct         RA            Amount            Tax
>
> 001 38 2001520500               3,420.00              0.00
>                                  1,002.02              0.00
> 002 50 0032118400               1,026.00              0.00
>                                    297.21              0.00
> 003 25 2001520500              72,645.00              0.00
>                                 20,879.23              0.00
> 004 50 0032118400              21,793.50              0.00
>                                  6,312.93              0.00
> 005 50 0010009101              48,457.50              0.00
>                                 14,036.70              0.00
> 006 40 0096100000                   0.00              0.00
>                                    769.63              0.00
>
Information re. vendor 1009530510 / paying company code SNXL ...
I have checked the configuration of FBZP The configuration settings is correct. Can you please help to solve this problem
Regards
Girish

Hi Girish,
You should be having error FZ326.
Please kindly refer to the following link in order to solve the issue:
http://wiki.sdn.sap.com/wiki/display/ERPFI/PaymentProgram-ErrorMessageFZ326
or
http://wiki.sdn.sap.com/wiki/x/jY3YCw
Apply all notes that are relevant to your support packaged.
Kind Regards,
Fernando Evangelista

F110 Error 007 - Error in creating the payment document; read job log

We have created a new SAP instance (vers 4.7) and testing if its working.
The above error occurs at the payment proposal stage for payment methed C (Cheque), but is OK for E (BACS).
I have been back through the config a couple of times checking FBZP and OBA7, and I can see anything obviously wrong.
The job log says........
10.03.2010 16:27:24 Job started -
                                                                   00           516          S
10.03.2010 16:27:24 Step 001 started (program SAPF110S, variant &0000000000007, user ID BPGB) -
     00           550          S
10.03.2010 16:27:24 Log for proposal run for payment on 10.03.2010, identification GB4 -
           FZ           402          S
10.03.2010 16:27:25                                                                              -
ZT           004          S
10.03.2010 16:27:25 Information re. vendor 500007 / paying company code PS10 ... -
                 FZ           305          S
10.03.2010 16:27:25 ... payment not possible because of reported error -
                           FZ           311          S
10.03.2010 16:27:25 End of log -
                                                                   FZ           398          S
10.03.2010 16:27:25 Job finished -
                                                                 00           517          S
What appears to be the offending line in the log (Error ZT004) is blank, so gives me no clues as to the problem. I'm at a loss what to check net, and I'm hoping somebody can help me.
Any advise welcome.
Thanks
Graham

Thanks Ji, that gives me a much better log to look through.
I've been doing a lot more testing as a result, but ultimately still come up blank. Heres why I am....
1. I have 2 payment methods...
C-Cheque
E=BACS
2. I pay 2 types of vendors...
Eternal (i.e. Invoices)
Internal (i.e. Employees expenses)
3. The payment proposal step is working fine for external suppliers on both payment methods, but fails for internal on both methods.
4. I am using the same payment terms on everything (Immediate payment no discount)
5.The only difference in the logs is (i.e. the line below does not appear on the external supplier logs).....
Cash discount base amount not set!                                                              FZ           753
6. The accounting documents look as I expect (External have an amount in the Cash Discount base, internal do not), this is how our current system behaves where we do not have any issues, and I cannot see any differences in the vendor document between the 2 systems
7. Incase I have missed something that is the real cause of the problem, here is the full log.
If you have any ideas what the problem still is, advice would be gratefully received, as I am pulling what little hair I have left out.
Full log......
Job started                                                                                00           516
Step 001 started (program SAPF110S, variant &0000000000018, user ID BPGB)                          00           550
Log for proposal run for payment on 10.03.2010, identification GB6                                 FZ           402
>                                                                                FZ           693
> Additional log for vendor 500008 company code PS10                                               FZ           691
>                                                                                FZ           693
>            Due date determination additional log                                                 FZ           799
> Document 2100000002 line item 001 via GBP           53.04-                                       FZ           700
> Terms of payment: 10.03.2010    0 0.000 %    0 0.000 %    0                                    FZ           701
> 00 days grace period is being considered                                                        FZ           726
> Cash discount base amount not set!                                                              FZ           753
>   Payment must take place before 10.03.2010; next payment on 12.03.2010                          FZ           728
> Item is due with 0.000 % cash discount                                                           FZ           721
>                                                                                FZ           693
>            Payment method selection additional log                                               FZ           699
> Payment method selection for items due now to the amount of GBP           53.04-                 FZ           601
> Payment method "E" is being checked                                                              FZ           603
> Bank details are being checked                                                                   FZ           640
>    Customer/vendor bank details are being read                                                   FZ           644
> Country GB / Bank number 404731 / Account 12457852 ...                                           FZ           645
>     Customer/vendor bank details are being checked                                               FZ           665
>   System reads house banks and checks if they are allowed                                        FZ           668
> Our bank 1000 is being checked                                                                   FZ           648
> For currency GBP and 001 days 9999,999,999.00 are planned                                        FZ           658
> Available amount is enough, 9999,999,999.00 GBP still available,           53.04 necessary      FZ           657
>   House bank is selected ...                                                                     FZ           673
> Our bank details 1000 GBBK1 are being used                                                       FZ           641
> Bank details of the partner with ctry GB bk no. 404731 acct 12457852 are being used              FZ           642
> Payment method "E" is permitted                                                                  FZ           609
                                                                                ZT           004
Information re. vendor 500008 / paying company code PS10 ...                                       FZ           305
... payment not possible because of reported error                                                 FZ           311
End of log                                                                                FZ           398
Job finished                                                                                00           517
Edited by: gbrandreth on Mar 11, 2010 11:35 AM

F110 Error in creating the payment document; read job

Hello
I am running a payment run for few vendors and I am getting this error "Error in creating the payment document; read job" I have checked all the vendor acconts involved, for any blocked data but nothing is blocked. Is there any thing else that I am missing. Pleas let me know.
Thanks

Hi,
To rectify ur problem u need to check follwing points...
1. doucuments types assogned in payment method in FBZP
2. In Ecc 6.0 u need to create document types and number ranges in N1 ledger, because new ledger is activated by system default in this version.
define document types in N1 ledger
path:Spro-FA-****-Documnet-document types-define doc.types in GL view
give ledger as N1 and enter.
define document types whoch u were assigned in payment method in country. for doucument types u can take reference as OBA7 tcode documnet types..
afetr that
define document N.ranges fro GL view
path:Spro-FA-****-Documnet-document N.ranges-doc. in GL view-define document N.ranges fro GL view
enter comany code and define number ranges for doc.types
afetr all above setting try once in F110. u will get result..
regds
Tony

TDS Challan error - while creating payment document

Hi,
I was trying to create With holding tax Challan through J1INCHLN.
Following error occurred after simulating payment document - "Withholding tax lines are being cleared along with other line items"
Please help in above matter.
Thanks
Deepak

Dear,
Please check with business users that are these manual reversal valid? See the username for these documents and also check which transaction was used whether it is FB08 or manual JV. If it was manual then reset these documents through FBRA and reverse it through FB08 because manual is not recommended.
If reversal are not required then after resetting through FBRA run J1INCHLN, which must bring data and you will be able to create challan.
Respective period means the period which you enter into J1INCHLN screen.
Regards,
Chintan Joshi

BUILD PROGRAM ERROR - CANNOT CREATE PAYMENTS

Hi, I'm trying to run a payment batch using payments manager and encountered this error.
In my test data I used two suppliers that belongs to the same operating unit.
Payments: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
IBYBUILD module: Build Payments
Current system time is 09-NOV-2009 11:26:11
**Starts**09-NOV-2009 11:26:11
**Ends**09-NOV-2009 11:26:13
BUILD PROGRAM ERROR - CANNOT CREATE PAYMENTS
Start of log messages from FND_FILE
IBY_PAYGROUP_PUB.performPostHookProcess: Fatal error - Payment count mismatch after hook operation. # payments passed to hook: 1, # payments returning from hook: 2
IBY_PAYGROUP_PUB.performPostHookProcess: Aborting program ..
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
Exceptions posted by this request:
Concurrent Request for "Build Payments" has completed with error.
Concurrent request completed
Current system time is 09-NOV-2009 11:26:13
Please help
thanks,
Renz

Hi
Please review the below note from Metalink,
Bug No. 6771847
Filed 24-JAN-2008 Updated 13-MAR-2008
Product Oracle Payments Product Version 12.0.4
Platform Linux x86 Platform Version ENTERPRISE 4
Database Version 10.2.0.2 Affects Platforms Generic
Severity Severe Loss of Service Status Closed, Verified by Filer
Base Bug N/A Fixed in Product Version 12.0.4
Problem statement:
R12: AFTER APPLYING 12.0.4 BUILD PAYMENT PROGRAM ERRORS
please review the same if it resolvs your error.
Thanks
Manish Jain.

Error while creating delivary document

Hi
i got error while creating delivary document
"Delevivary documents could not be created"
Thanks&regards
kishore kumar

Hi Kishore,
Please check the sales order is this relevent for the delivery or not.
Check the copy control settings between your sales document type and delivery document type in VTLA transaction.
Check the incompletion log for the sales order.
I hope it will help you,
Regards,
Murali.

Heap space error while creating XML document from Resultset

I am getting Heap space error while creating XML document from Resultset.
It was working fine from small result set object but when the size of resultset was more than 25,000, heap space error
I am already using -Xms32m -Xmx1024m
Is there a way to directly write to xml file from resultset instead of creating the whole document first and then writing it to file? Code examples please?
here is my code:
stmt = conn.prepareStatement(sql);
result = stmt.executeQuery();
result.setFetchSize(999);
Document doc = JDBCUtil.toDocument(result, Application.BANK_ID, interfaceType, Application.VERSION);
JDBCUtil.write(doc, fileName);
public static Document toDocument(ResultSet rs, String bankId, String interfaceFileType, String version)
    throws ParserConfigurationException, SQLException {
        DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
        DocumentBuilder builder = factory.newDocumentBuilder();
        Document doc = builder.newDocument();
        Element results = doc.createElement("sims");
        results.setAttribute("bank", bankId);
        results.setAttribute("record_type", "HEADER");
        results.setAttribute("file_type", interfaceFileType);
        results.setAttribute("version", version);
        doc.appendChild(results);
        ResultSetMetaData rsmd = rs.getMetaData();
        int colCount = rsmd.getColumnCount();
        String columnName="";
        Object value;
        while (rs.next()) {
            Element row = doc.createElement("rec");
            results.appendChild(row);
            for (int i = 1; i <= colCount; i++) {
                columnName = rsmd.getColumnLabel(i);
                value = rs.getObject(i);
                Element node = doc.createElement(columnName);
                if(value != null)
                    node.appendChild(doc.createTextNode(value.toString()));
                else
                    node.appendChild(doc.createTextNode(""));
                row.appendChild(node);
        return doc;
public static void write(Document document, String filename) {
        //long start = System.currentTimeMillis();
        // lets write to a file
        OutputFormat format = new OutputFormat(document); // Serialize DOM
        format.setIndent(2);
        format.setLineSeparator(System.getProperty("line.separator"));
        format.setLineWidth(80);
        try {
            FileWriter writer = new FileWriter(filename);
            BufferedWriter buf = new BufferedWriter(writer);
            XMLSerializer FileSerial = new XMLSerializer(writer, format);
            FileSerial.asDOMSerializer(); // As a DOM Serializer
            FileSerial.serialize(document);
            writer.close();
        } catch (IOException ioe) {
            ioe.printStackTrace();
        //long end = System.currentTimeMillis();
        //System.err.println("W3C File write time :" + (end - start) + " " + filename);
    }

you can increase your heap size..... try setting this as your environment variable.....
variable: JAVA_OPTS
value: -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m

Run time error while creating Ecommerce Order

Dear Friends,
we are using ECC 6.0, Ecommerce 5.0 applications run internet sales.
After selecting the requried products from the product catalog while trying to save the order I am getting a Run time error and also my session is getting logged out of the web shop.
I have searched the threads on similar issue, but found no clue yet..
Any help is highly appreciated.
Regards
Sadhu Kishore

#1.5 #005056A31282001C0000000400001AD800047FB93365B5C7#1266333314895#/Applications/BusinessLogic#sap.com/crmentitlementinquiry#com.sap.isa.core.jmx.ext.ExtBootstrapper#Viw~t0yxJv!nzcjy*!6#67##n/a##157475101b0e11dfb011005056a31282#SAPEngine_Application_Thread[impl:3]_17##0#0#Error#1#/Applications/BusinessLogic#Java###Error in CCMS reporting: #1#unable to register MBeans#
24309   #1.5 #005056A3128200280000000000001AD800047FB938DA2ACD#1266333406410#/Applications/BusinessLogic#sap.com/crm~b2c#com.sap.isa.core.init.InitDescription.getInitializable#Guest#0##n/a##4c1152a01b0e11df8c0b005056a31282#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#/Applications/BusinessLogic#Java###Initalization of failed.#1#com.sap.isa.advisor.backend.tst.AdvisorBackendTST#
24310   #1.5 #005056A31282002A0000000000001AD800047FB93AB6F382#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Administrator#129##n/a##5eb1b1c01b0e11df9db4005056a31282#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
24311   #1.5 #005056A31282002B0000000000001AD800047FB93AB6FCE4#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Guest#0##n/a##5eb1b1c11b0e11dfb98f005056a31282#Thread[Thread-129,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
24312   #1.5 #005056A31282002C0000000000001AD800047FB93AB6FF9E#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Guest#0##n/a##5eb1b1c21b0e11dfa58b005056a31282#Thread[Thread-130,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
24313   #1.5 #005056A31282002F0000000000001AD800047FB93BC6D909#1266333455473#/Applications/BusinessLogic#sap.com/crm~cviews#com.sap.isa.core.init.InitDescription.getInitializable#Administrator#133##n/a##694fbe101b0e11dfcc96005056a31282#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/Applications/BusinessLogic#Java###Initalization of failed.#1#com.sap.isa.useradmin.handler.UseradminInitHandler#
24314   #1.5 #005056A3128200330000000000001AD800047FB93DD62A70#1266333490035#/Applications/Common/Infrastructure#sap.com/crmicss_b2c#org.apache.commons.digester.Digester#Guest#0##n/a##7de97c301b0e11df9146005056a31282#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#org.apache.commons.digester.Digester#Java###system.forward.info#1#com.sap.engine.lib.xml.parser.NestedSAXParserException: com.sap.engine.lib.xml.parser.ParserException: Check whether the open and close tags are properly nested. (CharData is not allowed here.)(file://localhost/F:/usr/sap/EPD/JC10/j2ee/cluster/server0/apps/sap.com/crmicss_b2c/servlet_jsp/icss_b2c/root/WEB-INF/conf/struts-config.xml, row:118, col:9)(:main:, row=0, col=0) -> com.sap.engine.lib.xml.parser.ParserException: Check whether the open and close tags are properly nested. (CharData is not allowed here.)(file://localhost/F:/usr/sap/EPD/JC10/j2ee/cluster/server0/apps/sap.com/crm~icss_b2c/servlet_jsp/icss_b2c/root/WEB-INF/conf/struts-config.xml, row:118, col:9)#
24315   #1.5 #005056A3128200220000001000001AD800047FB961D04BAD#1266334093676#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.maintenanceobject.backend.MaintenanceObjectHelper#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#/Applications/Common/Infrastructure#Plain###Cache already initialized#
24316   #1.5 #005056A3128200220000001200001AD800047FB961F0F65E#1266334095816#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df158fb17a0aebf19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24317   #1.5 #005056A3128200220000001300001AD800047FB961F1C37B#1266334095879#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df1657de7c2d2ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24318   #1.5 #005056A3128200220000001400001AD800047FB961F25A6B#1266334095910#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df17d4e1b2d57ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24319   #1.5 #005056A3128200220000001500001AD800047FB961F2E857#1266334095941#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df180971f2ad43f19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24320   #1.5 #005056A3128200220000001600001AD800047FB961F403B4#1266334096019#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df158fb17a0aebf19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24321   #1.5 #005056A3128200220000001700001AD800047FB961F43A81#1266334096035#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df1657de7c2d2ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24322   #1.5 #005056A3128200220000001800001AD800047FB961F46D0E#1266334096051#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df17d4e1b2d57ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24323   #1.5 #005056A3128200220000001900001AD800047FB961F49D86#1266334096066#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df180971f2ad43f19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24324   #1.5 #005056A3128200340000000000001AD800047FB962954A0E#1266334106598#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.DocumentHandler#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_33##0#0#Warning#1#com.sap.isa.isacore.DocumentHandler#Plain###b2b.dochandler.warn.notontop#
24325   #1.5 #005056A3128200290000004400001AD800047FB962D270BC#1266334110598#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_20##0#0#Warning#1#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#Plain###UI parameter initial.newpos not set properly, 5 taken as default#
24326   #1.5 #005056A3128200350000000000001AD800047FB963A12DA7#1266334124145#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_5##0#0#Warning#1#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#Plain###UI parameter initial.newpos not set properly, 5 taken as default#
24327   #1.5 #005056A3128200320000000100001AD800047FB963FE1C13#1266334130239#/Applications/BusinessLogic#sap.com/crm~b2b#com.sap.isa.core.eai.sp.jco.JCoConnectionStateful#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/BusinessLogic#Java###Error occcurred in EAI layer "".#2#com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CPIC-CALL: 'CMRCV'
24328   null
24329   #parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
24330   Properties: {lang=en, passwd=?, sysnr=00, client=020, user=uname, ashost=hostXX, jco.client.type=A, maxcon=100, codepage=1100}
24331   Client not connected#
24332   #1.5 #005056A3128200320000000300001AD800047FB963FE781C#1266334130271#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.action.order.MaintainBasketSimulateAction#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/UserInterface#Plain###A runtime exception occurred on the highest level#
24333   #1.5 #005056A3128200320000000500001AD800047FB963FEEFEB#1266334130302#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.core.util.MessageListDisplayer#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/UserInterface#Plain###An exception has occurred: .#

Run time error while Creating IDN and Inbound Delivery

Hi All,
I am getting Run time error while creating Inbound Delivery Notification from Inbound Queue and Inbound Delivery from IDN
After debugging i come to know that system is looking for Patch Level SAPKNA7026 but in my system Patch is upto SAPKNA7022
Is there any OSS notes available to deactivate/resolve this run time error ? I tried 0001798794 Deactivation of hierarchical access functionality but system is still giving me run time error
Regards,
P@M

Hi Agrawal
As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
Regards
Srinath

Get SOAP Cannot Create XML Document reader error with Outlook integration?

Hi,
We installed Outlook Email Integration on a windows XP / Office 2007 machine and it installed OK. However when we click the "Add to CRM On Demand" button and try to login we get the following error message when we click the 'Sign In" button
"SOAP: Cannot create XML document reader"
Has anyone come across this? Are there any pre-requisites for using this add-in? e.g. Service Packs, .NET framework etc?
Cheers

It may not be the case...but pls. check if MS Word is defined as editing tool for email.. It should not be.
ANotnio
BExpert, Brazil

Error reading job logs of Apps server from Central Instance

Dear Gurus,
We have newly installed system with one CI ( cluster environment) and 2 application Instances.
Systems are recently installed by other team. I am looking into support part after handover.
We have noticed below error while reading failed background job logs from our CI. If suppose any job is failing, we can read respective job log from that application instance but it throws error while reading job log from CI to either of application instance.
I checked /sapmnt/SID/global is shared among all 3 servers and i am successfully able to "Touch a" from applications instances.
Even though i have given "777" permissions to all folders like /sapmnt/SID , /sapmnt/SID/global , /sapmnt/SID/global/400JOB*
I am not able to read job log from CI , for same failed job I can read job log from respective application instance.
Error log :
Error reading job log JOBLGX00080700X39290
Message no. BT167
Diagnosis
The background processing system was unable to read the job log named in the message.
This message suggests that there is a problem with the TEMSE storage system of the SAP system. The TEMSE storage system is a repository for temporary objects, such as job logs and spool requests. Job logs are always stored in the TEMSE as operating system files.
This error occurs if the TEMSE system is not able to find or access the file that contains the text of the job log that you requested. Possible causes for the loss or unavailability of the job log include the following:
Someone deleted the required TEMSE file (from the operating system, not from within the SAP system).
A CRON (or equivalent scheduler) job has deleted the TEMSE file.
The file system in which the TEMSE stores its files is not mounted or is not accessible (NFS problem, disk failure, or similar problem).
The TEMSE reorganize or consistency check functions were used within the SAP system and deleted the job log.
SM21 logs :
Error 2 for write/read access to a file. File = /usr/sap/SID/SYS/global
BP_JOBLOG_SHOW: Failed to display jobs. Reason:
> Error reading job log JOBLGX00080700X39290
Strange this is I can check failed job log on one application instance frfom other application instance but not from CI.
Kindly throw some lights where to check.
Regards,

Hi Shravan,
I guess it is related to permission to /sapmnt/SID/global folder. Please ensure owner is sidadm:sapsys in all the systems viz CI, App servers etc.
Check the mounting options are correctly set with read/write mode.
Hope this helps.
Regards,
Deepak Kori

F110 - Runtime error when creating payment media

Hi experts,
I use t.code F110, payment proposal is OK, payment run is OK, then I click on print job but there is no payment medium created. If I look at the print job log it says ABAP/4 raise exception.
In the testing environment everything is fine (payment media is created) but not in the production (I get the error)
Any idea?
Many thanks
Ben

Hi
Check the settings under
SPRO - Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Outgoing Payments - Automatic Outgoing Payments - Payment Media - Make Settings for Classic Payment Medium Programs
- Assign Payment Forms for Payment Method in Company Code
- Assign Payment Medium Program for Payment Method in Country
On completion of F110 run, you would get a print out option on top. Execute that and if required check in SP02 for any spool requests
Thank You,

F110 - Run date error

Hi I am running the F110 for the F110 for the Denmark company code with the RFFODK_U in the payment medium program.
I am getting the following error message :
Run date 20081014 changed to 20081015
Message no. F0 235
Diagnosis
The data medium created contains payments with different run dates. BACS only supports payments within a time period of 39 days. The selected run date is too many days after the first payment.
System Response
The run date for payment document 1500000111 was changed from 20081014 to 20081015.
I didnt understand the diagnosis part.. Please guide me little more to solve this error message.
Thanks
Meenakshi.N

Hi,
for some reason the system is not running line items payment with on this date. There is a comparison with last F110 Payment Run and that date is 39 days so far. System fix it changing the date.
About your line items, do you have some especial payment or insatllment?

F110 Run APP Error in creating payment document, read job log

Similar Messages

Maybe you are looking for