Payment Scheme Error--

Hi ALL,
I am doing Payment Scheme configuration, while creation of payment scheme i am getting the following error message:
Tax jurisdiction code is not permitted for payment scheme procedure
Message no. EPS117
Could you please help me....
Thanks,
KK

Hi,
we all ready maintained tax jurisdiction at connection object & BP level.
could you give me is there any other configuration settings involved this area...
Thank,
KK

Similar Messages

Payment scheme in ISU

Hi ,
I am getting a error of "Extrapolation is in-consistence for equipment #### and reg ## ,while creating payment scheme through EA61PS.
Can anyone please suggest me where the issue might be ?
Thanks,
Bighnajit

Hi Bighnajit,
The error that you are getting is triggered from a standard include program and can be because of the following reasons-
(a)Too less Quantity-
-Meter reading had an overflow, but the previous reading had none.
- No overflow in previous reading and current reading is still higher than previous.No over flow gets billed.
(b) Both readings had an overflow and current reading is lower than previous reading. (Normally this doesn't happen).
(c) The current reading has no overflow, the previous reading has an overflow,but after the correction the current reading is lower than the previous. This is inconsistent, because the previous reading can't be estimated the current reading.
Check SAP Note 920277 for more information on the same.
Also check SAP Note 909301 and 1895896 if you are having any of these scenarios...
Hope it helps...
Thanks,
Amlan

Org.xml.sax.SAXException: Error:General Schema Error

I am getting the error below. Any clues/workarounds? I am
using WL 6.1.
Thanks in advance,
Eva
The following files are below:
Validate.java
BMDefaultHandler.java
validate.xml
validate.xsd
org.xml.sax.SAXException: Error:General Schema Error: Grammar with uri:http://schemas.xmlsoap.org/soap/envelope/
, can not be
found; schema namespace maybe wrong:
Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema" namespace
or
the instance document's namespace may not match the targetNamespace of the schema.
at
com.bluemartini.xml.BMDefaultHandler.error(BMDefaultHandler.java:32)
at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1249)
at
org.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1821)
at
org.apache.xerces.validators.common.XMLValidator.validateElementAndAttr
ibutes(XMLValidator.java:3232)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLVa
lidator.java:1229)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentS
canner.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(XMLDocumentScanner.java:949)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:381)
at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
va:195)
at
javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:191)
at com.bluemartini.test.Validate.main(Validate.java:32)
===Validate.java
package com.bluemartini.test;
import java.io.*;
import org.w3c.dom.*;
import com.bluemartini.xml.*;
// JAXP imports
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.ParserConfigurationException;
* Sample test case.
* Eva Flora
public class Validate {
public static void main(String[] argv) {
try {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
factory.setAttribute("http://xml.org/sax/features/validation", Boolean.TRUE);
factory.setAttribute("http://apache.org/xml/features/validation/schema",
Boolean.TRUE);
DocumentBuilder builder = factory.newDocumentBuilder();
BMDefaultHandler bmErrorHandler = new BMDefaultHandler();
builder.setErrorHandler(bmErrorHandler);
File temp = new File("validate.xml");
Document doc = builder.parse(temp);
} catch (Exception e) {
e.printStackTrace();
===BMDefaultHandler.java
package com.bluemartini.xml;
import com.bluemartini.dna.*;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.*;
public class BMDefaultHandler extends
DefaultHandler
public BMDefaultHandler()
public void warning(SAXParseException spe)
throws SAXException
System.out.println("Warning: " + spe.getMessage());
public void error(SAXParseException spe)
throws SAXException
throw new SAXException("Error:" + spe.getMessage());
public void fatalError(SAXParseException spe)
throws SAXException
throw new SAXException("Fatal Error: " + spe.getMessage());
===validate.xml
<?xml version="1.0" encoding="UTF-8"?>
<soapns:Envelope xmlns:soapns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" xmlns:test="http://www.test.com"
xsi:noNamespaceSchemaLocation="validate.xsd">
     <soapns:Header/>
     <soapns:Body>
<test:GWSMapRequestMessage>
          </test:GWSMapRequestMessage>
     </soapns:Body>
</soapns:Envelope>
===validate.xsd
<schema xmlns="http://www.w3.org/2000/10/XMLSchema">
<element name="GWSMapRequestMessage" type="TestType"/>
<complexType name="TestType">
</complexType>
</schema>

I am getting the error below. Any clues/workarounds? I am
using WL 6.1.
Thanks in advance,
Eva
The following files are below:
Validate.java
BMDefaultHandler.java
validate.xml
validate.xsd
org.xml.sax.SAXException: Error:General Schema Error: Grammar with uri:http://schemas.xmlsoap.org/soap/envelope/
, can not be
found; schema namespace maybe wrong:
Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema" namespace
or
the instance document's namespace may not match the targetNamespace of the schema.
at
com.bluemartini.xml.BMDefaultHandler.error(BMDefaultHandler.java:32)
at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1249)
at
org.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1821)
at
org.apache.xerces.validators.common.XMLValidator.validateElementAndAttr
ibutes(XMLValidator.java:3232)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLVa
lidator.java:1229)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentS
canner.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(XMLDocumentScanner.java:949)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:381)
at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
va:195)
at
javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:191)
at com.bluemartini.test.Validate.main(Validate.java:32)
===Validate.java
package com.bluemartini.test;
import java.io.*;
import org.w3c.dom.*;
import com.bluemartini.xml.*;
// JAXP imports
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.ParserConfigurationException;
* Sample test case.
* Eva Flora
public class Validate {
public static void main(String[] argv) {
try {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
factory.setAttribute("http://xml.org/sax/features/validation", Boolean.TRUE);
factory.setAttribute("http://apache.org/xml/features/validation/schema",
Boolean.TRUE);
DocumentBuilder builder = factory.newDocumentBuilder();
BMDefaultHandler bmErrorHandler = new BMDefaultHandler();
builder.setErrorHandler(bmErrorHandler);
File temp = new File("validate.xml");
Document doc = builder.parse(temp);
} catch (Exception e) {
e.printStackTrace();
===BMDefaultHandler.java
package com.bluemartini.xml;
import com.bluemartini.dna.*;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.*;
public class BMDefaultHandler extends
DefaultHandler
public BMDefaultHandler()
public void warning(SAXParseException spe)
throws SAXException
System.out.println("Warning: " + spe.getMessage());
public void error(SAXParseException spe)
throws SAXException
throw new SAXException("Error:" + spe.getMessage());
public void fatalError(SAXParseException spe)
throws SAXException
throw new SAXException("Fatal Error: " + spe.getMessage());
===validate.xml
<?xml version="1.0" encoding="UTF-8"?>
<soapns:Envelope xmlns:soapns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" xmlns:test="http://www.test.com"
xsi:noNamespaceSchemaLocation="validate.xsd">
     <soapns:Header/>
     <soapns:Body>
<test:GWSMapRequestMessage>
          </test:GWSMapRequestMessage>
     </soapns:Body>
</soapns:Envelope>
===validate.xsd
<schema xmlns="http://www.w3.org/2000/10/XMLSchema">
<element name="GWSMapRequestMessage" type="TestType"/>
<complexType name="TestType">
</complexType>
</schema>

Org.xml.sax.SAXException: Error:General Schema Error: Grammar

I am getting the error below. Any clues/workarounds? I am
using WL 6.1.
Thanks in advance,
Eva
The following files are below:
Validate.java
BMDefaultHandler.java
validate.xml
validate.xsd
org.xml.sax.SAXException: Error:General Schema Error: Grammar with uri:http://schemas.xmlsoap.org/soap/envelope/
, can not be
found; schema namespace maybe wrong:
Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema" namespace
or
the instance document's namespace may not match the targetNamespace of the schema.
at
com.bluemartini.xml.BMDefaultHandler.error(BMDefaultHandler.java:32)
at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1249)
at
org.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1821)
at
org.apache.xerces.validators.common.XMLValidator.validateElementAndAttr
ibutes(XMLValidator.java:3232)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLVa
lidator.java:1229)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentS
canner.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(XMLDocumentScanner.java:949)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:381)
at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
va:195)
at
javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:191)
at com.bluemartini.test.Validate.main(Validate.java:32)
===Validate.java
package com.bluemartini.test;
import java.io.*;
import org.w3c.dom.*;
import com.bluemartini.xml.*;
// JAXP imports
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.ParserConfigurationException;
* Sample test case.
* Eva Flora
public class Validate {
public static void main(String[] argv) {
try {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
factory.setAttribute("http://xml.org/sax/features/validation", Boolean.TRUE);
factory.setAttribute("http://apache.org/xml/features/validation/schema",
Boolean.TRUE);
DocumentBuilder builder = factory.newDocumentBuilder();
BMDefaultHandler bmErrorHandler = new BMDefaultHandler();
builder.setErrorHandler(bmErrorHandler);
File temp = new File("validate.xml");
Document doc = builder.parse(temp);
} catch (Exception e) {
e.printStackTrace();
===BMDefaultHandler.java
package com.bluemartini.xml;
import com.bluemartini.dna.*;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.*;
public class BMDefaultHandler extends
DefaultHandler
public BMDefaultHandler()
public void warning(SAXParseException spe)
throws SAXException
System.out.println("Warning: " + spe.getMessage());
public void error(SAXParseException spe)
throws SAXException
throw new SAXException("Error:" + spe.getMessage());
public void fatalError(SAXParseException spe)
throws SAXException
throw new SAXException("Fatal Error: " + spe.getMessage());
===validate.xml
<?xml version="1.0" encoding="UTF-8"?>
<soapns:Envelope xmlns:soapns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" xmlns:test="http://www.test.com"
xsi:noNamespaceSchemaLocation="validate.xsd">
     <soapns:Header/>
     <soapns:Body>
<test:GWSMapRequestMessage>
          </test:GWSMapRequestMessage>
     </soapns:Body>
</soapns:Envelope>
===validate.xsd
<schema xmlns="http://www.w3.org/2000/10/XMLSchema">
<element name="GWSMapRequestMessage" type="TestType"/>
<complexType name="TestType">
</complexType>
</schema>

I guess the problem is due to the schema namespace
you are using.
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"
pls try with :
"http://www.w3.org/2001/XMLSchema"
regards,
-manoj
"Eva Flora" <[email protected]> wrote in message
news:[email protected]...
I am getting the error below. Any clues/workarounds? I am
using WL 6.1.
Thanks in advance,
Eva
The following files are below:
Validate.java
BMDefaultHandler.java
validate.xml
validate.xsd
org.xml.sax.SAXException: Error:General Schema Error: Grammar with
uri:http://schemas.xmlsoap.org/soap/envelope/
, can not be
found; schema namespace maybe wrong:
Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema"
namespace
or
the instance document's namespace may not match the targetNamespace of the
schema.
at
com.bluemartini.xml.BMDefaultHandler.error(BMDefaultHandler.java:32)
at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1249)
at
org.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1821)
at
org.apache.xerces.validators.common.XMLValidator.validateElementAndAttr
ibutes(XMLValidator.java:3232)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLVa
lidator.java:1229)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentS
canner.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(XMLDocumentScanner.java:949)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:381)
at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
va:195)
at
javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:191)
at com.bluemartini.test.Validate.main(Validate.java:32)
===Validate.java
package com.bluemartini.test;
import java.io.*;
import org.w3c.dom.*;
import com.bluemartini.xml.*;
// JAXP imports
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.ParserConfigurationException;
* Sample test case.
* Eva Flora
public class Validate {
public static void main(String[] argv) {
try {
DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
factory.setAttribute("http://xml.org/sax/features/validation",
Boolean.TRUE);
factory.setAttribute("http://apache.org/xml/features/validation/schema",
Boolean.TRUE);
DocumentBuilder builder = factory.newDocumentBuilder();
BMDefaultHandler bmErrorHandler = new BMDefaultHandler();
builder.setErrorHandler(bmErrorHandler);
File temp = new File("validate.xml");
Document doc = builder.parse(temp);
} catch (Exception e) {
e.printStackTrace();
===BMDefaultHandler.java
package com.bluemartini.xml;
import com.bluemartini.dna.*;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.*;
public class BMDefaultHandler extends
DefaultHandler
public BMDefaultHandler()
public void warning(SAXParseException spe)
throws SAXException
System.out.println("Warning: " + spe.getMessage());
public void error(SAXParseException spe)
throws SAXException
throw new SAXException("Error:" + spe.getMessage());
public void fatalError(SAXParseException spe)
throws SAXException
throw new SAXException("Fatal Error: " + spe.getMessage());
===validate.xml
<?xml version="1.0" encoding="UTF-8"?>
<soapns:Envelope xmlns:soapns="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"
xmlns:test="http://www.test.com"
xsi:noNamespaceSchemaLocation="validate.xsd">
<soapns:Header/>
<soapns:Body>
<test:GWSMapRequestMessage>
</test:GWSMapRequestMessage>
</soapns:Body>
</soapns:Envelope>
===validate.xsd
<schema xmlns="http://www.w3.org/2000/10/XMLSchema">
<element name="GWSMapRequestMessage" type="TestType"/>
<complexType name="TestType">
</complexType>
</schema>
[att1.html]

Payment verify error!

I play KABAM / Hobbit app on an I-pad and I-phone daily. Mid game gold purchase on I-pad the app crashed (diff issue) and purchase transaction did not go through. Now, every time I open the game I'm asked for my apple I'd and password... then iget message " Payment verify error!"... close that and then I can play.
It's very irritating... I don't care about the 50 gold I never got... I just want to not have to sigh in in every time I open this app. I have a lot of $$$ invested in it and I would hate to loose it all... so I'm chicken to delete app without first asking the question. Any insite into this would be appriciated! Thx

I have this problem as well. I can make purchases but it is really annoying that I have to enter my account password twice and verify my payment information for every purchase I make.

Payment execution error

HI
         this is maqdoom ali
I getting error while go to the execution of payment terms error no f5413.
Best Regrt
NASERK.

Hi,
Define this message as Warning by OBA5. If it isn't allowed go first into OBMSG.
Regards

Payment scheme termination

Hi Experts,
I have created a function module which will call a standard function module ' ISU_PAYSCHEME_TERMINATE'. Can any tell me how this FM will work and where can I see its effect?
Regards,
Pravesh Gupta.

You use transaction E61PSD or method TERMINATE of BOR object PAYSCHEME to end a payment
scheme.
Select a payment scheme that you want to end and enter the end date. If you have maintained table
Payment Scheme Deactivation Reason (TE561), enter a deactivation reason as well. This has no effect
on the deactivation process and is not analyzed by the system. However, you can use it at a later point intime to analyze the deactivated payment schemes.
Once you have entered the end date, the system checks whether payment scheme requests that have
already been paid exist after the end date. If this is the case, the end date is set to the next due date plus
one day.
Depending on the sequence of the end date and the first payment date of the payment scheme, the
system proceeds as follows:
u2022 If the end date lies before the first payment date of the payment scheme, the payment scheme is
deleted from the database. If you have already created statistical requests for this payment scheme,
they are cleared.
u2022 If the end date lies after the first payment date of the payment scheme, the system executes the
following actions:
a. The payment scheme sample line that is active on the end date is prorated so that its end
date is the same as the end date of the payment scheme. A new sample line is created for
the part of the sample line that comes after the end date.
b. All payment scheme sample lines with a start date that comes after the end date are
deactivated.
c. The end date and, if necessary, the deactivation reason are entered in the payment scheme
header data.
d. All statistical requests with due dates that lie after the end date are cleared.
Payment schemes that are ended this way remain active until the end date. You can either change
the payment scheme manually or during creation of an interim or periodic bill. You can also create
statistical requests for this payment scheme. You can change the end date again as long as the
new date comes before the end date that was entered previously.
In order to ensure that a payment scheme can no longer be changed, you must deactivate it once it
has ended. You do this by creating an interim or periodic bill with a billing period that contains the
end date of the payment scheme. During creation of this bill, all payment scheme requests that
have not yet been paid are cleared. Requests with due dates that come after the most recent
interim or periodic bill and that have already been paid are settled against the current consumption
billing when the bill is created. Any overpayments can be refunded at a later point in time. The
system removes the clearing restriction u201CRu201D from all items that were transferred to the payment
scheme that have not yet been paid.
If the interim/periodic bill is reversed, the entire process is cancelled. This means that the clearing of
the paid requests against the transferred items and the current consumption billing is also reversed.
All items that had the clearing restriction u201CRu201D before the bill was created are assigned it again.
u2022 If you enter the current date as the end date, the system may react differently to the above
description. This happens when event Automatic Account Maintenance When Payment Scheme is
Ended (R531) returns parameter X_NO_ACC_MAIN (No Automatic Account Maintenance When PS
is Ended) with the value " ". When the payment scheme is ended, the system carries out integrated
automatic account maintenance. In account maintenance, all payment scheme requests that were
paid after the last interim/periodic bill are settled against all the open items that were transferred to
the payment scheme. If the payments are not enough to clear the items, the clearing restriction u201CRu201D
is removed from the remaining open items. If the amount paid is too high, the clearing restriction u201CRu201D
is removed from the payment scheme request payments that are not required for account
maintenance. You can either refund the customer directly or settle the excess payment in the next
consumption billing.
Regards,
Shiva Kumar

Payment scheme and its behaviour in FPL9

Hi Experts,
I have a concern,
Anybody can explain Payment schem Request and its behaviour?
As statistical line item impact and real item impact and when it will go to down payments tab?
some times i can see same document in few situtions, i am quite confuse. Can you anybody can hlpe on this please?
Thanks,
Abash

Hi Abash,
Payment scheme is a budget billing plan that is offered in SAP for customers accounts where customers wants to pay a constant amount for yearly consumption, so for this the SAP extrapolates the billing line item and gives a amount based on payment frequency , for .e.g $50 per week
Now as customer is not going to pay the invoice amount as customer is on payment scheme, customer will pay the payment scheme amount will settle his invoice,so to take payment scheme payment a line item is required against which customer will be charged its a statistical line item, now when customer pays this amount statistical item gets cleared and payment will reside as down payment , which in turn will clear invoice in account maintenance
Hope it helps.
Regards,
Lalit

Payment Scheme amount adjustment on periodic review

Hi Experts,
Can you please explain me adjustment of extrapolated amount and bill amount, while periodc review. or any document which explain me that, i have debug the program but found nothing.
Example : In periodic review invoice generated for 300 and extrapolation amount will be 600.
In simple case new line on Payment Scheme, extrapolated amount is 900 and bill amount is 300 and instilment amount is 100 per mount ( 600 /12 )
but in some casa the extrapolated amount is differ from extrapolated amount. i observe this deviation comes from last line item of payment scheme that is adjusted due to new line item creation.
I can able to explain the how new extrapolation amount comes but i can't able to explain why this is happening in some case.
Regards
Naresh

Hi!
The process is as follows:
Invoice Entry                       : F-43
Outgoing payment              : F-53
Downpayment                    :F-48
TRansfer amount from Downpayment(Special GL) to normal GL: F-54
Then Clear Normal item       :F-44
First you transfer the advance amount from special GL to Normal GL through F-54(to clear advance payment). Then it will convert the special GL to normal GL to clear the advance amount. Then you clear advance payment through F-44 which is converted as normal item. If still the invoice amount is more than the advance amount, after clearing the advance amount you can clear balance amount by F-44

Payment Scheme - Extrapolation Amount

Hi All,
This is regarding payment scheme that we create through transaction EA61PS.
The problem is: The extrapolation amount that system calculates is only for one installment (i.e. one month). The requirement was to enhance the extrapolation period from standard 3 months to 12 months. But now when I see, even 3 month extrapolation is not happening.
Pls help.
Regards,
Bhaskar

Hello,
To determine the start and end date of the extrapolation period for creating the payment scheme you can use event R510.
Event R510 used to determine the start and end date of the extrapolation period for creating the payment scheme.
The system uses parameter X_OBJ-EP_PERIOD to determine the process from
which the budget billing extrapolation is called:
M Manual creation of payment scheme(EA61PS)
E Move-in
The standard function module for this event is Determine Extrapolation
Period for Payment Scheme (ISU_GET_EXTRAPOLAT_PERIOD_R510).
In this function module, the start date is always set to the start date
of the billing period for which the payment scheme is created.
Exception: If the move-in date comes after the start date of the billing
period. In this case, the start date of the extrapolation period is set
to the same as the move-in date.
The end date of the extrapolation period is always the same as the end
date of the billing period.
If you define your own extrapolation period in this event, it does not
have any effect on the billing period.
This means that if you change the extrapolation period to a full year,
for example, the resulting amount is still only divided amongst the
payment scheme requests remaining in the current billing period.
I hope this information is useful for you.
Regards
Olivia

Installment plan v/s payment schema

Hello,
Instalment paln and payment schema(Budget Billling) both does the same functions.If i am right what are the differences.
which gives the higher flexibility?where, how , when we use????

The biggest difference in payment schemes such as budget billing and installment plans is not in the term, but in the purpose of use.
Budget billing is created upfront for a certain period, using an estimation of the consumption to come over that period. It's used to spread upcoming bills in time (for example, based on your previous year, you'll have to pay 600u20AC in six months time, therefor we'll make you a budget billing already charging you 100u20AC each month until you receive you invoice).
Budget billing is (always) deducted from your next invoice, after which a new bbp starts.
Installment plans are used to pay off debt, after they are already invoices. Installment plans are made from open items, which are combined and redistributed over a couple of months. So, it's for bills you should already have paid, but for which you didn't have the money at the time. For example: you have two unpaid invoices, one for 100u20AC and one for 250u20AC. You cannot paid them this month and ask you utility company for a plan. They create an installment plan for 350u20AC, spreading this amount over 7 months, so you'll have to pay 50u20AC each month.
Usually, there's no need to which between BBP and installment plans. They can be use indepentently and can co-exist for one customer. You can use invoiced BBP items in an installment plan (because once invoices they are just open items). You can also cancel an installment plan and retrieve the original open items.
Hope this helps!

How to reverse payment scheme request line which has origin as RO

Hi Experts,
I have a requirement to reverse the payment scheme request line.
need help on this how to reverse this line item.
Regards,
Lalit

Hi Praveen,
Thank you very much for your reply. I appreciate your time and efforts.
Ok, these are the steps how I have executed the process.
- I have created a service contract for an equipment. In the service contract, I have maintained the service material in the line item, maintained price and assigned equipment in the technical objects.
- I created service notification, which automatically picked up contract.
- When I create service order, from notification screen, system automatically picked up correct order type SM01 (Service order with contract).
- Then I planned operations and spare parts in the service order.
- Checked settlement rule in the service order is SDI.
- released and saved service order.
- Using IW42, in SAP ECC6, you can perform both time confirmation and material consumption using the same screen and also TECO service order. System issues message to say, goods issue have been posted.
- when you check the document flow of service order, you can see operations posted, and also goods issue posted.
- check cost tab to see actual costs. (if I want to settle costs from service order to service contract, I can do so w/o a problem in KO88)
- Use DP90, enter service order number and create billing request. System takes to billing request screen but it is blank. No line items.
- So, since there is a contract, in this case, am I meant to be creating the billing request from Service contract? instead of from Service order?
I hope I have clarified myself better this time.
Best regards,
Abdul Rafey

Organization Payment method Error

Dear All,
When I trying to attach a bank account in cash management Tab im getting following error.
APP-PAY-34070:the bank account does not uniquely map to cash management account
If anybody faced similar issue please let me know the solution you have implemented.
Regards,
Jithin dev

962274 wrote:
Dear All,
When I trying to attach a bank account in cash management Tab im getting following error.
APP-PAY-34070:the bank account does not uniquely map to cash management account
If anybody faced similar issue please let me know the solution you have implemented.
Regards,
Jithin devPlease see these docs.
Defining Organizational Payment Method, Errors: APP-PAY-34070: The Bank Account Does not Uniquely map to Cash Management Account. [ID 1106723.1]
Costing of Payment : Can We Populate Control Account With Multiple Liability Accounts ? [ID 1266020.1]
Thanks,
Hussein

"Your payment method was declined. Please enter another payment method" Error

Hello,
I've been trying to download an app for about two hours now. I recently got a new Macbook and iPad, my iPhone is a bit older and has been used frequently. I have only bought paid apps with my iPhone (and other iPad -- not usable currently). I have been trying to download a game which is $4.99 on my account, I have tried with my Mac, iPad, and iPhone, no luck. Every time I get a error saying "Your payment method was declined. Please enter another payment method". I know for a fact I have more than enough money to pay for this app. All the details have been checked and checked again. What is the problem?
I also get an error when first buying the game (or attemting to) and it says something along the lines of "You've recently used a new device or computer to access this apple id, please sign in to confirm your purchase". That then leads to my confirmation of my security code on my card, which is triggering the first mentioned error.
Apple Support has not yet given me a response, can any of you help?

I think that for some international copyright issue, Apple is now blocking purchases from your store if they detect that your IP is outside the frontiers. I've been using my Canadian Visa Card for two years to purchase from France on ITune Store Canada and I never had a problem until today. Impossible to buy RunKeeper Pro. I get the same message you get. The only option seems to swithch back to IStore France and modify the account details with a french address and a french credit card.
Are you in a similar situation?

Automatic payment program - error No permitted payment method exists

Hi All,
I am doing the automatic payment run and done all the necessary config in FBZP.
1) Created the payment program at country level and assigned payment program
2) Created the payment method at company code level for check and assign the Check Form
3) Coming to Bank determination:
   a) Ranking order : given the payment method(A -> Check) ,currency(MYR), ranking order (1) and assigned to house bank (CIMB)
   b) Bank accounts : given house bank , payment method ,currency, account ID and clearing account number.
4) assigned the payment method (A) in vendor master.
when i run the payment run for the vendor in F110 for company code system hitting below errors:
> -
Payment method selection additional log----
> Payment method selection for items due now to the amount of MYR      112,909.38-
> Payment via payee/payer 0550000008
> Payment method "A" is being checked
> Payment with 28 print items, only 16 are allowed
> No permitted payment method exists
Information re. vendor 500000598 / paying company code 0546 ...
......payment not possible because of reported error
End of log
Job finished
please can any body help me on this. I done the same config in DEV and QAS. there working fine with out any issue.   but coming to PRD its giving problem. i double confirm the config in DEV to pRD every thing fine and same.
thanks.
Sandhya.

Hi...
I did check the 1) vendor address -> No gaps
2) My one is check printing not bank transfer
3) I did check all the vendor line items no payment blocks. user already unblock the relevent item to make payment.
Here weird thing is system hitting the same above mentioned error even I updated the payment method(C) and house bank (CIMB) in each and every line item of vendor invoice.
Thanks,
Sandhya.

Payment Scheme Error--

Similar Messages

Maybe you are looking for