Payment scheme

Hi ,
Does we able to create ps for the QROB customer.

Please provide MUCH more information. Your post cannot be answered otherwise.

Similar Messages

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

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 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

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

ISU Payment Plan

Hello,
Please share the link with exhaustive documenatioon on SAP standard ISU Payment Plan material . Also would like to know the difference between Payment Scheme and Payment plan for Australian Market.
Thanks in advance.
Regards,
Sunil S

Hi Sunil,
The major difference between payment plan and a payment scheme is that a payment plan is related to a finite number of open items to be payed on a e.g. monthly basis until the debt is payed finally. On the other hand, the validity period of a payment scheme is unrestricted.
Payment plan:
An agreement between the customer and the utility company, which determines the amount to be paid for each bill on agreed dates. The payment plan amount is not necessarily the bill amount. The difference amount between the bill amount and the payment plan amount is fixed and posted. The payment plan is not to be compared with the budget billing plan that is charged between two periodic bills.
Payment Scheme:
The payment scheme is a statistical budget billing procedure. Consumption billing amounts from previous and current billing periods are copied to the payment scheme and distributed evenly over the next billing period. The budget billing amount is determined partially from an extrapolation portion that reflects the expected consumption for the current billing period and partially from the copied consumption billings. It is not necessary to copy consumption billings to the payment scheme in order to use this procedure. If you do copy them, the bills are not paid directly by the customer but during the next billing period when the
payment scheme requests are paid. The payment scheme allows payments to be made in weekly, fortnightly, monthly, quarterly, and yearly cycles. The validity period of a payment scheme is unrestricted. This means that a payment scheme is not ended and another created when you create a periodic bill. Instead, the existing payment scheme is adjusted.
There is a cookbook payment scheme available in [http://service.sap.com/utilities] -> SAP for Utilities (product information) -> IS-U/CCS -> Billing&Invoicing -> Cookbooks&Guidelines.
Kind regards,
Fritz

Direct debit payment

Hi,
First payment for each customer via credit card and futher payment by direct debit.
How to set the direct debit (other than BP- SP - Bank details and payment scheme) setting in CRM billing and finance posting into R/3.
We are not using Business agreement, only BP. CRM flow includes (sales order-> service order-> Billing) link to install base -> R/3 (finance posting)
All monthly invoice of amount equal to direct debit fix amount, however customer can change the direct debit amount after every 1 month number of times?
Can some one suggest the solution? (With enhancement)
Thanks in advance.

Hi Sanju,
When we are receving an Amount in Advance thorugh credit card or Net Banking (direct debit), we can do one enhancement where we will maintain Customer Account (credit card as customer needs to be create) , the GL Account, Card Type, and here we will have option Net banking or not, if it is credit card dont select net banking option other wise select net banking option. It is Ztable where we will maintain the inputs but for this we required Zprogram to post the entries.
So in this passion we can do enhancement, any further help requires just get back me.
Thanks & Regards
T N R

Creation of Budget Billing Plan for Countries with Tax Jurisdiction

Hello Experts,
When I create a budget billing plan for a company code with country Canada/USA and jursidiction TAXCAJ/TAXUSJ using transaction EA61, I get the message "Taxes with jurisdiction code not permitted with down payments"(Message no. >0194). The long text for this message says "Delete your entry in the field for jurisdiction code" Is any one aware where from this jurisdiction code should be deleted.
Is it possible to create budget billing plan for countries with jurisdiction code at all ?
Thanks in advance
Venkat

Hello Roopali,
What I learnt in the process of exploring the functionality is that Payment PLan (BBP or AMB) is the budget billing method for countries with Tax Jurisdiction. Statistical, Partial & Payment Scheme only works when jurisdiction is not defined for tax procedure. Payment scheme is the recommend procedure for Eurpopean market
Thanks for your clarification
Best Regards
Venkat

Installation failed due to Download Error

I have just purchased Photoshop and Light room CC on a monthly payment scheme. I have downloaded Creative Cloud, but when I click 'Install' and attempt to download either of these programs (and trials of any other program) I get the message 'Installation Failed'. The only other information given is that it is because of a download error, and that I should contact customer support. How do I resolve this error?

Link for Download & Install & Setup & Activation problems may help
-Chat http://www.adobe.com/support/download-install/supportinfo/
OR
Some download & install troubleshooting links
-Comodo Security kills download http://forums.adobe.com/thread/1460361?tstart=0
-http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
-http://helpx.adobe.com/creative-cloud/kb/error-downloading-cc-apps.html
-http://forums.adobe.com/community/download_install_setup
-http://helpx.adobe.com/creative-cloud/kb/troubleshoot-cc-installation-download.html
-http://helpx.adobe.com/x-productkb/global/errors-or-unexpected-behavior-websites.html
-http://helpx.adobe.com/creative-cloud/kb/unknown-server-error-launching-cc.html
-Server won't connect https://forums.adobe.com/thread/1233088
-Enable Mac Root User https://forums.adobe.com/thread/1156604

Installment plan clearing

Hello All,
I have a query regarding clearing of installment plan.
For example:
Posting Date    Due Date           Description    Amt
01.02.2011     20.02.2011         Fees             5000
01.02.2011     20.02.2011         Interest         200
01.02.2011     20.03.2011         Interest         100
01.02.2011     20.04.2011         Interest         50
These are the items posted in a customers account
Based on these items an installment plan is created for 3 months.
My installment plan would be
Posting Date    Due Date           Description    Amt
1.02.2011     20.02.2011         Instalment       1783
1.02.2011     20.03.2011         Instalment       1783
1.02.2011     20.04.2011         Instalment       1785
How will the source item be cleared. In what hierarchy will it clear.
I need to know, that can we clear partially clear the fees amount and interest based on the due date. If so, how can we achieve it.
Regards,
Charvi

Hi,
Payment Scheme requests are just statistical items. So when a payment clears a Payment Scheme request, in background SAP creates a down payment request (can be seen in FPL9 under tab down payment requests). This down payment request in turn clears the original debt. The priority is due date of the debt items which can be overwritten by config to give priority based on document types or main/sub trans.
This answers your second question as well that while original priority is given to due date which in case will clear fees first due on 20.02.2011 but if you want interest to get cleared first, you need to do some enhancements and config to change priorities based on document types or main/sub trans.
Regards,
Ravi

Workshop 9.2 - Web Service Test Client - java.util.NoSuchElementException

I've found an issue with the Web Services Test Client while developing a web service application in the Weblogic Workshop 9.2 tool. The same schema / code in Workshop 8.1 SP4 works okay in its version of the test client.
The error seems to manifest itself, when I add the "addresses" element to the "locations" element.
The error displayed in the weblogic service console is
<BLOCKQUOTE>
java.lang.RuntimeException: java.util.NoSuchElementException
at weblogic.testclient.ConnectionState.createWsdl(ConnectionState.java:63)
at Controller.refreshWsdl(Controller.java:304)
at Controller.begin(Controller.java:173)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
        at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
        at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:878)
        at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:808)
        at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:477)
        at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:305)
        at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:335)
        at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:51)
        at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:95)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2042)
        at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:90)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2114)
        at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:554)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851)
        at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630)
        at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157)
        at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3211)
Caused by: java.util.NoSuchElementException
        at java.util.AbstractList$Itr.next(AbstractList.java:427)
        at weblogic.testclient.RequestTemplate.addSoapForParameter(RequestTemplate.java:341)
        at weblogic.testclient.RequestTemplate.addSoapForParameter(RequestTemplate.java:334)
        at weblogic.testclient.RequestTemplate.addSoapForParameter(RequestTemplate.java:334)
        at weblogic.testclient.RequestTemplate.addSoapForParameter(RequestTemplate.java:334)
        at weblogic.testclient.RequestTemplate.addSoapForParameter(RequestTemplate.java:334)
        at weblogic.testclient.RequestTemplate.addSoapForParameter(RequestTemplate.java:334)
        at weblogic.testclient.RequestTemplate.addSoapForParameter(RequestTemplate.java:334)
        at weblogic.testclient.RequestTemplate.addSoapForParameter(RequestTemplate.java:334)
        at weblogic.testclient.RequestTemplate.addSoapForParameter(RequestTemplate.java:334)
        at weblogic.testclient.RequestTemplate.createMessageBody(RequestTemplate.java:220)
        at weblogic.testclient.RequestTemplate.buildRequest(RequestTemplate.java:169)
        at weblogic.testclient.RequestTemplate.createRequestTemplate(RequestTemplate.java:103)
        at weblogic.testclient.RequestTemplate.<init>(RequestTemplate.java:85)
        at weblogic.testclient.WebServiceOperation.<init>(WebServiceOperation.java:120)
        at weblogic.testclient.WsdlOperationParser.createOperation(WsdlOperationParser.java:115)
        at weblogic.testclient.WebService.createOperation(WebService.java:242)
        at weblogic.testclient.WebService.<init>(WebService.java:86)
        at weblogic.testclient.Wsdl.parseWsdl(Wsdl.java:127)
        at weblogic.testclient.Wsdl.<init>(Wsdl.java:59)
        at weblogic.testclient.ConnectionState.createWsdlFromHttpUrl(ConnectionState.java:113)
        at weblogic.testclient.ConnectionState.createWsdl(ConnectionState.java:54)
        at Controller.refreshWsdl(Controller.java:304)
        at Controller.begin(Controller.java:173)
        at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
        at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
        at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:878)
        at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:808)
        at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:477)
</BLOCKQUOTE>
The code in the Web Service control is...
<BLOCKQUOTE>
package services;
import javax.jws.WebMethod;
import javax.jws.WebService;
import weblogic.jws.WLHttpTransport;
import au.com.suncorp.services.payment.schema.x0.RequestIdDocument;
import au.com.suncorp.services.payment.schema.x0.VendorDocument;
@WebService(targetNamespace="http://suncorp.com.au/services/payment/wsdl/0")
@WLHttpTransport(serviceUri="services/PaymentService")
public class Payment {
     @WebMethod
     public RequestIdDocument setupVendor(VendorDocument request) {
          System.out.println(request.xmlText());
          RequestIdDocument result = RequestIdDocument.Factory.newInstance();
          RequestIdDocument.RequestId response = result.addNewRequestId();
          response.setCorrelationId("CorrelationId-" + request.getVendor().getName());
          return result;
</BLOCKQUOTE>
The XSD schema is as follows....
<BLOCKQUOTE>
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://suncorp.com.au/services/payment/schema/0"
xmlns:tns="http://suncorp.com.au/services/payment/schema/0">

<simpleType name="correlationIdType">
<annotation>
<documentation>
The CorrelationId field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="estTimeIntervalType">
<annotation>
<documentation>
The Estimated Time Interval field.
</documentation>
</annotation>
<restriction base="integer"></restriction>
</simpleType>
<simpleType name="vendorIdType">
<annotation>
<documentation>
The Vendor Id field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="nameType">
<annotation>
<documentation>
The Vendor Name field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="persistenceType">
<annotation>
<documentation>
The Persistence field.
</documentation>
</annotation>
<restriction base="boolean"></restriction>
</simpleType>
<simpleType name="ownerType">
<annotation>
<documentation>
The Owner field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="sourceReferenceType">
<annotation>
<documentation>
The vendor Source Reference field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="abnType">
<annotation>
<documentation>
The vendor ABN field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="countryType">
<annotation>
<documentation>
The Country field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="stateType">
<annotation>
<documentation>
The State field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="cityType">
<annotation>
<documentation>
The City field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="postcodeType">
<annotation>
<documentation>
The Postcode field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="gstRegisteredType">
<annotation>
<documentation>
The GST Registered field.
</documentation>
</annotation>
<restriction base="boolean"></restriction>
</simpleType>
<simpleType name="withHoldingType">
<annotation>
<documentation>
The WithHolding field.
</documentation>
</annotation>
<restriction base="boolean"></restriction>
</simpleType>
<simpleType name="vendorClassType">
<annotation>
<documentation>
The Vendor Class field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="statusType">
<annotation>
<documentation>The Status field.</documentation>
</annotation>
<restriction base="string">
<enumeration value="ACTIVE">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="INACTIVE">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
</restriction>
</simpleType>
<simpleType name="locationIdType">
<annotation>
<documentation>
The Location Id field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="effectiveDateType">
<annotation>
<documentation>
The Effective Date field.
</documentation>
</annotation>
<restriction base="dateTime"></restriction>
</simpleType>
<simpleType name="addressIdType">
<annotation>
<documentation>
The AddressId field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="addressType">
<annotation>
<documentation>
The Address field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="contactIdType">
<annotation>
<documentation>
The ContactId field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="contactMethodType">
<annotation>
<documentation>
The Address field.
</documentation>
</annotation>
<restriction base="string">
<enumeration value="FAX">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="PHONE">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="EMAIL">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
</restriction>
</simpleType>
<simpleType name="dispatchMethodType">
<annotation>
<documentation>
The Dispatch Method field.
</documentation>
</annotation>
<restriction base="string">
<enumeration value="EFT">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="FAX">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="EMAIL">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
</restriction>
</simpleType>
<simpleType name="currencyType">
<annotation>
<documentation>
The Currency field.
</documentation>
</annotation>
<restriction base="boolean"></restriction>
</simpleType>
<simpleType name="payGroupType">
<annotation>
<documentation>
The Pay Group field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="payHoldType">
<annotation>
<documentation>
The Pay Hold field.
</documentation>
</annotation>
<restriction base="boolean"></restriction>
</simpleType>
<simpleType name="freightTermsType">
<annotation>
<documentation>
The Freight Terms field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="payHandlingType">
<annotation>
<documentation>
The Pay Handling field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="delayDaysType">
<annotation>
<documentation>
The Delay Days field.
</documentation>
</annotation>
<restriction base="integer"></restriction>
</simpleType>
<simpleType name="payFromBankType">
<annotation>
<documentation>
The Pay From Bank field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="paymentInstructionsType">
<annotation>
<documentation>
The Payment Instructions field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="paymentTermsType">
<annotation>
<documentation>
The Payment Terms field.
</documentation>
</annotation>
<restriction base="string">
<enumeration value="COD">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="SEVEN_DAYS">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="FOURTEEN_DAYS">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="TWENTYONE_DAYS">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="THIRTY_DAYS">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
</restriction>
</simpleType>
<simpleType name="paymentMethodType">
<annotation>
<documentation>
The Payment Method field.
</documentation>
</annotation>
<restriction base="string">
<enumeration value="EFT">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
<enumeration value="CHEQUE">
<annotation>
<documentation>an enumerated value.</documentation>
</annotation>
</enumeration>
</restriction>
</simpleType>
<simpleType name="payBankIdType">
<annotation>
<documentation>
The PayBankId field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="descriptionType">
<annotation>
<documentation>
The Pay Bank Description field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="bankIdType">
<annotation>
<documentation>
The BankId field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="branchIdType">
<annotation>
<documentation>
The BranchId field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>
<simpleType name="bankAccountType">
<annotation>
<documentation>
The BankAccount field.
</documentation>
</annotation>
<restriction base="string"></restriction>
</simpleType>

<complexType name="payBankDetailsType">
<sequence>
<element name="payBankId" type="tns:payBankIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="description" type="tns:descriptionType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="bankId" type="tns:bankIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="branchId" type="tns:branchIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="bankAccount" type="tns:bankAccountType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="effectiveDate" type="tns:effectiveDateType" maxOccurs="1" minOccurs="0" nillable="true"></element>
</sequence>
</complexType>
<complexType name="paymentDetailsType">
<sequence>
<element name="paymentTerms" type="tns:paymentTermsType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="paymentMethod" type="tns:paymentMethodType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="dispatchMethod" type="tns:dispatchMethodType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="payGroup" type="tns:payGroupType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="currency" type="tns:currencyType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="payHold" type="tns:payHoldType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="freightTerms" type="tns:freightTermsType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="payHandling" type="tns:payHandlingType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="delayDays" type="tns:delayDaysType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="payFromBank" type="tns:payFromBankType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="paymentInstructions" type="tns:paymentInstructionsType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="bankDetails" type="tns:payBankDetailsType" maxOccurs="1" minOccurs="1"></element>
</sequence>
</complexType>
<complexType name="contactDetailsType">
<sequence>
<element name="contactId" type="tns:contactIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="effectiveDate" type="tns:effectiveDateType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="name" type="tns:nameType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="contactMethod" type="tns:contactMethodType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="dispatchMethod" type="tns:dispatchMethodType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="status" type="tns:statusType" maxOccurs="1" minOccurs="1"></element>
</sequence>
</complexType>
<complexType name="arrayOfContactDetails">
<sequence>
<element name="contact" type="tns:contactDetailsType" maxOccurs="unbounded" minOccurs="0"></element>
</sequence>
</complexType>
<complexType name="addressDetailsType">
<sequence>
<element name="addressId" type="tns:addressIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="effectiveDate" type="tns:effectiveDateType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="name" type="tns:nameType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="address" type="tns:addressType" maxOccurs="1" minOccurs="1"></element>
<element name="postcode" type="tns:postcodeType" maxOccurs="1" minOccurs="1"></element>
<element name="city" type="tns:cityType" maxOccurs="1" minOccurs="1"></element>
<element name="state" type="tns:stateType" maxOccurs="1" minOccurs="1"></element>
<element name="country" type="tns:countryType" maxOccurs="1" minOccurs="1"></element>
<element name="contacts" type="tns:arrayOfContactDetails" maxOccurs="1" minOccurs="0"></element>
</sequence>
</complexType>
<complexType name="arrayOfAddressDetails">
<sequence>
<element name="address" type="tns:addressDetailsType" maxOccurs="unbounded" minOccurs="0"></element>
</sequence>
</complexType>
<complexType name="locationDetailsType">
<sequence>
<element name="locationId" type="tns:locationIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="effectiveDate" type="tns:effectiveDateType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="orderingVendorId" type="tns:vendorIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="invoicingVendorId" type="tns:vendorIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="remittingVendorId" type="tns:vendorIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="returningVendorId" type="tns:vendorIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="status" type="tns:statusType" maxOccurs="1" minOccurs="1"></element>
<element name="paymentDetails" type="tns:paymentDetailsType" maxOccurs="1" minOccurs="1"></element>
<element name="addresses" type="tns:arrayOfAddressDetails" maxOccurs="1" minOccurs="0"></element>
</sequence>
</complexType>
<complexType name="arrayOfLocationDetails">
<sequence>
<element name="location" type="tns:locationDetailsType" maxOccurs="unbounded" minOccurs="0"></element>
</sequence>
</complexType>

<element name="Vendor">
<complexType mixed="true">
<annotation>
<documentation>
The Vendor request object.
</documentation>
</annotation>
<sequence>
<element name="vendorId" type="tns:vendorIdType" maxOccurs="1" minOccurs="1"></element>
<element name="name" type="tns:nameType" maxOccurs="1" minOccurs="1"></element>
<element name="persistence" type="tns:persistenceType" maxOccurs="1" minOccurs="1" default="true"></element>
<element name="owner" type="tns:ownerType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="sourceReference" type="tns:sourceReferenceType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="corporateVendorId" type="tns:vendorIdType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="abn" type="tns:abnType" maxOccurs="1" minOccurs="0" nillable="true"></element>
<element name="country" type="tns:countryType" maxOccurs="1" minOccurs="1" default="AUS"></element>
<element name="gstRegistered" type="tns:gstRegisteredType" maxOccurs="1" minOccurs="0" nillable="true" default="true"></element>
<element name="withHolding" type="tns:withHoldingType" maxOccurs="1" minOccurs="0" nillable="true" default="false"></element>
<element name="status" type="tns:statusType" maxOccurs="1" minOccurs="1" default="ACTIVE"></element>
<element name="vendorClass" type="tns:vendorClassType" maxOccurs="1" minOccurs="1"></element>
<element name="locations" type="tns:arrayOfLocationDetails" maxOccurs="1" minOccurs="0"></element>
</sequence>
</complexType>
</element>
<element name="RequestId">
<complexType mixed="true">
<annotation>
<documentation>The typical response object for requests.
</documentation>
</annotation>
<sequence>
<element name="correlationId" type="tns:correlationIdType" maxOccurs="1" minOccurs="1"></element>
<element name="estTimeInterval" type="tns:estTimeIntervalType" maxOccurs="1" minOccurs="0" nillable="true" default="24"></element>
</sequence>
</complexType>
</element>
</schema>
</BLOCKQUOTE>

Hi Paul
I believe there is some issue with the TestClient.
Instead to test, can you please try this?
1) Right click on Payment.java and choose Webservices -> generate wsdl
2) Right click on the wsdl and choose Webservices -> Test with WebServices Explorer.
3) Click on setVendor method
4) Enter the request parameters
Sample one:
<ns:Vendor xmlns="http://www.openuri.org/" xmlns:ns="http://suncorp.com.au/services/payment/schema/0">
<vendorId xmlns="">Vendor Id</vendorId>
<name xmlns="">My correlation Id</name>
<persistence xmlns="">false</persistence>
<country xmlns="">USA</country>
<status xmlns="">ACTIVE</status>
<vendorClass xmlns="">VendorClass</vendorClass>
</ns:Vendor>
5) Hit the button 'Go'. The entire soap response will be displayed in the bottom.
I have tested this and it works fine.
Output I got:
<m:setupVendorResponse xmlns:m="http://suncorp.com.au/services/payment/wsdl/0">
<RequestId xmlns="http://suncorp.com.au/services/payment/schema/0">
<correlationId>CorrelationId-My correlation Id</correlationId>
</RequestId>
</m:setupVendorResponse>
Thanks,
Vimala

Payment scheme

Similar Messages

Maybe you are looking for