Character-currency.

I am using FM changedocument_read and passing the f_old and f_new which 254 character in length to a currency data type with 14 character in length....When i do that I am getting short dump.....how to fix the problem

Hi,
Look at the code it may help u.
REPORT ZMMCHGHISTORY NO STANDARD PAGE HEADING
                LINE-SIZE 195 LINE-COUNT 60.
Change doc listing
Grouped into 3 chg types: 1. Part revision  2. Price change  3. Others
TABLES:
        CDHDR, CDPOS, MARA, MAKT, MARD.
FIELD-GROUPS: HEADER.
DATA: BEGIN OF CHGDOC OCCURS 50.
        INCLUDE STRUCTURE CDRED.
DATA: END OF CHGDOC.
DATA:
      CHGTYPE(1),
      PLANT(4),
      MATNR1 LIKE CHGDOC-OBJECTID.
SELECT-OPTIONS:
    XMATNR  FOR CDHDR-OBJECTID,    "Material
    XUDATE  FOR CDHDR-UDATE,       "Change Date
    XUNAME  FOR CDHDR-USERNAME,    "User Name
    XTCODE  FOR CDHDR-TCODE,       "Transaction Code
    XWERKS  FOR MARD-WERKS.        "Plants
SELECTION-SCREEN SKIP.
*Filter change type
SELECTION-SCREEN BEGIN OF BLOCK CHG0 WITH FRAME TITLE TEXT-001.
   PARAMETERS : XCHG1 AS CHECKBOX DEFAULT 'X',
                XCHG2 AS CHECKBOX DEFAULT 'X',
                XCHG3 AS CHECKBOX DEFAULT 'X'.
SELECTION-SCREEN END OF BLOCK CHG0.
START-OF-SELECTION.
INSERT:
        CHGDOC-OBJECTID        "Material
        CHGTYPE                "Change type
        PLANT
        CHGDOC-CHANGENR
        CHGDOC-USERNAME
        CHGDOC-UDATE
        CHGDOC-TCODE
        CHGDOC-TABNAME
        CHGDOC-TABKEY
        CHGDOC-CHNGIND
        CHGDOC-FNAME
        CHGDOC-FTEXT
        CHGDOC-TEXTART
        CHGDOC-OUTLEN
        CHGDOC-F_OLD
        CHGDOC-F_NEW
INTO HEADER.
SELECT * FROM MARA WHERE MATNR IN XMATNR.
   MATNR1 = MARA-MATNR.
   <b>CALL FUNCTION 'CHANGEDOCUMENT_READ'
     EXPORTING
        ARCHIVE_HANDLE             = 0
        CHANGENUMBER               = ' '
        DATE_OF_CHANGE             = '00000000'
          OBJECTCLASS                = 'MATERIAL'
          OBJECTID                   = MATNR1
        TABLEKEY                   = ' '
        TABLENAME                  = ' '
        TIME_OF_CHANGE             = '000000'
        USERNAME                   = ' '
        LOCAL_TIME                 = ' '
     TABLES
          EDITPOS                    = CHGDOC
     EXCEPTIONS
          NO_POSITION_FOUND          = 1
          WRONG_ACCESS_TO_ARCHIVE    = 2
          TIME_ZONE_CONVERSION_ERROR = 3
          OTHERS                     = 4.</b>
   LOOP AT CHGDOC.
      CHECK:  CHGDOC-UDATE    IN XUDATE,
              CHGDOC-USERNAME IN XUNAME,
              CHGDOC-TCODE    IN XTCODE.
    Chg type: 1. Part revision, 2. Price change, 3. Others
      CASE CHGDOC-TCODE.
         WHEN 'MM01' OR 'MM02' OR 'MM03'.  CHGTYPE = '1'.
         WHEN 'MR21'.  CHGTYPE = '2'.
         WHEN OTHERS.  CHGTYPE = '3'.
      ENDCASE.
    Filter chg type
      IF ( CHGTYPE = '1' AND XCHG1 <> 'X' ) OR
         ( CHGTYPE = '2' AND XCHG2 <> 'X' ) OR
         ( CHGTYPE = '3' AND XCHG3 <> 'X' ).
         CONTINUE.
      ENDIF.
    Plant is a substring of tabkey
      PLANT = CHGDOC-TABKEY+21(4).
      IF NOT ( XWERKS IS INITIAL ) AND NOT ( PLANT IS INITIAL ).
         CHECK PLANT IN XWERKS.
      ENDIF.
      EXTRACT HEADER.
   ENDLOOP.
ENDSELECT.
END-OF-SELECTION.
SORT.
LOOP.
Material
   AT NEW CHGDOC-OBJECTID.
      SELECT SINGLE * FROM MAKT  WHERE MATNR = CHGDOC-OBJECTID.
      FORMAT INTENSIFIED ON.
      SKIP.  SKIP.
      WRITE:/' *** Material:', (18) CHGDOC-OBJECTID, MAKT-MAKTX.
   ENDAT.
Change type
   AT NEW CHGTYPE.
      FORMAT INTENSIFIED ON.
      SKIP.
      CASE CHGTYPE.
         WHEN '1'.   WRITE:/ '  **  Change type:  PARTS REVISION'.
         WHEN '2'.   WRITE:/ '  **  Change type:  PRICE CHANGE'.
         WHEN '3'.   WRITE:/ '  **  Change type:  OTHERS'.
      ENDCASE.
      SKIP.
   ENDAT.
   SHIFT CHGDOC-F_OLD LEFT DELETING LEADING SPACE.
   SHIFT CHGDOC-F_NEW LEFT DELETING LEADING SPACE.
   FORMAT INTENSIFIED OFF.
   WRITE:
     /     PLANT          UNDER 'Plant',
      (50) CHGDOC-FTEXT   UNDER 'Field',
      (45) CHGDOC-F_OLD   UNDER 'Old value',
      (45) CHGDOC-F_NEW   UNDER 'New value'.
   AT NEW CHGDOC-CHANGENR.
      FORMAT INTENSIFIED OFF.
      WRITE:
           CHGDOC-CHANGENR   UNDER 'Change doc',
           CHGDOC-TCODE      UNDER 'Tcod',
           CHGDOC-USERNAME   UNDER 'User name   ',
           CHGDOC-UDATE      UNDER 'Date    ' DD/MM/YY.
   ENDAT.
   AT END OF CHGDOC-OBJECTID.
      SKIP.
      ULINE.
      SKIP.
   ENDAT.
ENDLOOP.
TOP-OF-PAGE.
WRITE: / SY-DATUM, SY-UZEIT,
    50 'ABC PTE LTD',
   100 'page', SY-PAGNO,
       / SY-REPID,
    48 'Change Documents Report',
   100 SY-UNAME.
SKIP.
ULINE.
WRITE:/3
        'Change doc',
        'Tcod',
        'User name   ',
        'Date    ',
        'Plant',
   (50) 'Field',
   (45) 'Old value',
   (45) 'New value'.
ULINE.
End of Program
Since i couln't get ur point i am giving u this program.
Pls reward points if u get some help out of it.
Regards,
Ameet

Similar Messages

  • For currency at the time of report generation it is considering decimal

    Dear Team,
    I struck  with this issue from the long time and I really appreciate if any body help me on this,
    Des: Delivery and Billing happened, the amount is 1234/-, the dispalying the same in the documents but while generating the report from VBRK and VBRP for one country it is showing as 12.34/-
    The report is ZVF05N,
    We checked for reference WAERK is also assigned for NETWR
    Best part is in the same report for country currecy it is giving the correct info but only for 1 country it is considering it is taking decimal point,
    Please provide the some input for this

    The output should be done with a WRITE statement with CURRENCY addition specifying the currency, to avoid this issue. Ask your developer to qualify all places where the amount is output with either
    WRITE <amount> CURRENCY <3 character currency key>.
    OR
    WRITE <amount> TO <output variable> CURRENCY <3 character currency key>.

  • TWO CURRENCIES IN ONE Purchase Orders Release Procedure.

    TWO CURRENCIES IN ONE Purchase Orders Release Procedure.
    Please provide a solution if a release strategy is maintained for two currencies like USD and SGD for more clarification please Read the below Requirement.
    Requirement for Singapore:
    u2022          COMPANY Asia (Singapore) wants its own Purchase order release strategy is based on their local currency (SGD)
    u2022          Whereas COMPANY is using only USD as currency in Purchase order release strategy.
    u2022          Standard SAP works based on Character currency which is defining in Class of Purchase release strategy and converts with Local currency to compare with Character Currency.
    Required analysis:
    u2022          The value assigned in classification is based on Conversion from SGD to USD, Due to Exchange rate fluctuations the assigned value is differ by large amounts and hence system is either determining the higher release strategy or Lower release strategy
    u2022          But during Release Strategy Configuration the Net order Value is assigned as 3600 USD considering the Exchange as 1.388889.
    u2022          As per the exchange rate in the purchase order 1.3799 the system is calculation the PO Net order Value but the Strategy is Determined based on the value maintained according to exchange Rate 1.388889
    In the Purchase Order the system is 
    Ex:  Total Purchase Order Value is 4765.21 SGD and 3453.30 in USD
          For Level 1 the value limit is 5000 SGD if it exceeds 5000 SGD it has to go to his manager (Level 2) Exchange rate on 01.04.2008 is 1.3799.
    System Considerations:
    Possible Solution:
    1.        Create a new Class with Characteristic with Currency Value SGD System should determine the class based on the combination of Plant 6000 and Document Category F Purchase Order.
    2.        By using Enhancement spot with Function Module ME_RELEASE_STRATEGIE/ ME_RELEASE_STRATEGIE_EKKO
    Logic:
    1.        System will determine the class PUR_RELEASE from table T16FG if the system finds Plant as 6000 and Document Category as F Then replace PUR_RELEASE with New class as ZPUR _6000.
    2.        Maintain Z table for the combination of Plant and Class for future requirement
    Edited by: Mohammad Irfan on Jun 8, 2009 10:41 AM

    Hi Mohamed,
      You can create separate characteristics far all check points and assign those to class.
    Regards,
    Prasath

  • Issues in WSDL Import

    Hi all,
    I'm trying to import a WSDL file into XI and I get this error
    Unable to convert imported document to WSDL
    Reason: Tag definitions cannot have an attribute version from namespace urn:ebay:api:PayPalAPI
    Check the selected category
    Kindly provide inputs
    Thanks
    Geetha
    My WSDL strcuture looks like this.
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions ns:version="2.4" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns="urn:ebay:api:PayPalAPI" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:cc="urn:ebay:apis:CoreComponentTypes" targetNamespace="urn:ebay:api:PayPalAPI">
    <wsdl:types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ebay:api:PayPalAPI" elementFormDefault="qualified" attributeFormDefault="unqualified">
      <import namespace="urn:ebay:apis:CoreComponentTypes" schemaLocation="CoreComponentTypes.xsd" />
      <import namespace="urn:ebay:apis:eBLBaseComponents" schemaLocation="eBLBaseComponents.xsd" />
    <!--  Custom Security header element
      -->
      <xs:element name="RequesterCredentials" type="ebl:CustomSecurityHeaderType" />
    <!--  API Request/Responses
      -->
      <xs:element name="RefundTransactionRequest" type="ns:RefundTransactionRequestType" />
      <xs:element name="RefundTransactionResponse" type="ns:RefundTransactionResponseType" />
    <xs:element name="RefundTransactionReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:RefundTransactionRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="RefundTransactionRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="TransactionID" type="ebl:TransactionId">
    <annotation>
    <documentation>
      Unique identifier of the transaction you are refunding.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Character length and limitations: 17 single-byte alphanumeric characters
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="RefundType" type="ebl:RefundType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Type of refund you are making
      <br />
      <br />
      <b>Required</b>
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Amount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Refund amount.
      <br />
      <br />
      Amount is
      <b>required</b>
      if RefundType is Partial.
      <br />
      <br />
      NOTE: If RefundType is Full, do not set Amount.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Memo" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Custom memo about the refund.
      <br />
      <br />
      Optional
      <br />
      <br />
      Character length and limitations: 255 single-byte alphanumeric characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="RefundTransactionResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <sequence>
    <element name="RefundTransactionID" type="ebl:TransactionId" minOccurs="0" maxOccurs="1" nillable="true">
    <annotation>
    <documentation>
      Unique transaction ID of the refund.
      <br />
      <br />
      Character length and limitations:17 single-byte characters
      </documentation>
      </annotation>
      </element>
    <element name="NetRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
    <annotation>
      <documentation>Amount subtracted from PayPal balance of original recipient of payment to make this refund</documentation>
      </annotation>
      </element>
    <element name="FeeRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
    <annotation>
      <documentation>Transaction fee refunded to original recipient of payment</documentation>
      </annotation>
      </element>
    <element name="GrossRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
    <annotation>
      <documentation>Amount of money refunded to original payer</documentation>
      </annotation>
      </element>
      </sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="GetTransactionDetailsRequest" type="ns:GetTransactionDetailsRequestType" />
      <xs:element name="GetTransactionDetailsResponse" type="ns:GetTransactionDetailsResponseType" />
    <xs:element name="GetTransactionDetailsReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:GetTransactionDetailsRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="GetTransactionDetailsRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="TransactionID" type="ebl:TransactionId">
    <annotation>
    <documentation>
      Unique identifier of a transaction.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      The details for some kinds of transactions cannot be retrieved with GetTransactionDetailsRequest. You cannot obtain details of bank transfer withdrawals, for example.
      <br />
      <br />
      Character length and limitations: 17 single-byte alphanumeric characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="GetTransactionDetailsResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
      <xs:element ref="ebl:PaymentTransactionDetails" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="BillUserRequest" type="ns:BillUserRequestType" />
      <xs:element name="BillUserResponse" type="ns:BillUserResponseType" />
    <xs:element name="BillUserReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:BillUserRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="BillUserRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
      <xs:element ref="ebl:MerchantPullPaymentDetails" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="BillUserResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
      <xs:element ref="ebl:BillUserResponseDetails" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="TransactionSearchRequest" type="ns:TransactionSearchRequestType" />
      <xs:element name="TransactionSearchResponse" type="ns:TransactionSearchResponseType" />
    <xs:element name="TransactionSearchReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:TransactionSearchRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="TransactionSearchRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="StartDate" type="xs:dateTime" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      The earliest transaction date at which to start the search. No wildcards are allowed.
      <br />
      <br />
      <b>Required</b>
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="EndDate" type="xs:dateTime" minOccurs="0">
    <annotation>
    <documentation>
      The latest transaction date to be included in the search
      <br />
      <br />
      Optional
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Payer" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by the buyers email address
      <br />
      <br />
      Optional
      <br />
      <br />
      Character length and limitations: 127 single-byte alphanumeric characters
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Receiver" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by the receivers email address. If the merchant account has only one email, this is the primary email. Can also be a non-primary email.
      <br />
      <br />
      Optional
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="ReceiptID" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by the PayPal Account Optional receipt ID
      <br />
      <br />
      Optional
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="TransactionID" type="ebl:TransactionId" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by the transaction ID.
      <br />
      <br />
      Optional
      <br />
      <br />
      The returned results are from the merchants transaction records.
      <br />
      <br />
      Character length and limitations: 19 single-byte characters maximum
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="PayerName" type="ebl:PersonNameType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by the buyers name
      <br />
      <br />
      Optional
      <br />
      <br />
      Salutation: 20 single-byte character limit.
      <br />
      <br />
      FirstName: 25 single-byte character limit.
      <br />
      <br />
      MiddleName: 25 single-byte character limit.
      <br />
      <br />
      LastName: 25 single-byte character limit.
      <br />
      <br />
      Suffix: 12 single-byte character limit.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="AuctionItemNumber" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by item number of the purchased goods.
      <br />
      <br />
      Optional
      <br />
      <br />
      To search for purchased items not related to auctions, set the AuctionItemNumber element to the value of the HTML item_number variable set in the shopping cart for the original transaction.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="InvoiceID" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by invoice identification key, as set by you for the original transaction. InvoiceID searches the invoice records for items sold by the merchant, not the items purchased.
      <br />
      <br />
      Optional
      <br />
      <br />
      The value for InvoiceID must exactly match an invoice identification number. No wildcards are allowed.
      <br />
      <br />
      Character length and limitations: 127 single-byte characters maximum
      </documentation>
      </annotation>
      </xs:element>
      <xs:element name="CardNumber" type="xs:string" minOccurs="0" maxOccurs="1" />
    <xs:element name="TransactionClass" type="ebl:PaymentTransactionClassCodeType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by classification of transaction. Some kinds of possible classes of transactions are not searchable with TransactionSearchRequest. You cannot search for bank transfer withdrawals, for example.
      <br />
      <br />
      Optional
      <br />
      <br />
      All: all transaction classifications.
      <br />
      <br />
      Sent: only payments sent.
      <br />
      <br />
      Received: only payments received.
      <br />
      <br />
      MassPay: only mass payments.
      <br />
      <br />
      MoneyRequest: only money requests.
      <br />
      <br />
      FundsAdded: only funds added to balance.
      <br />
      <br />
      FundsWithdrawn: only funds withdrawn from balance.
      <br />
      <br />
      Referral: only transactions involving referrals.
      <br />
      <br />
      Fee: only transactions involving fees.
      <br />
      <br />
      Subscription: only transactions involving subscriptions.
      <br />
      <br />
      Dividend: only transactions involving dividends.
      <br />
      <br />
      Billpay: only transactions involving BillPay Transactions.
      <br />
      <br />
      Refund: only transactions involving funds.
      <br />
      <br />
      CurrencyConversions: only transactions involving currency conversions.
      <br />
      <br />
      BalanceTransfer: only transactions involving balance transfers.
      <br />
      <br />
      Reversal: only transactions involving BillPay reversals.
      <br />
      <br />
      Shipping: only transactions involving UPS shipping fees.
      <br />
      <br />
      BalanceAffecting: only transactions that affect the account balance.
      <br />
      <br />
      ECheck: only transactions involving eCheck
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Amount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by transaction amount
      <br />
      <br />
      Optional
      <br />
      <br />
      You must set the currencyID attribute to one of the three-character currency codes for any of the supported PayPal currencies.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="CurrencyCode" type="ebl:CurrencyCodeType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by currency code
      <br />
      <br />
      Optional
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Status" type="ebl:PaymentTransactionStatusCodeType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Search by transaction status
      <br />
      <br />
      Optional
      <br />
      <br />
      Pending: The payment is pending. The specific reason the payment is pending is returned by the GetTransactionDetails APIPendingReason element. For more information, see PendingReason.
      <br />
      <br />
      Processing: The payment is being processed.
      <br />
      <br />
      Success: The payment has been completed and the funds have been added successfully to your account balance.
      <br />
      <br />
      Denied: You denied the payment. This happens only if the payment was previously pending.
      <br />
      <br />
      Reversed: A payment was reversed due to a chargeback or other type of reversal. The funds have been removed from your account balance and returned to the buyer.
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="TransactionSearchResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
    <xs:element ref="ebl:PaymentTransactions" minOccurs="0" maxOccurs="unbounded">
    <annotation>
      <documentation>Results of a Transaction Search.</documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="MassPayRequest" type="ns:MassPayRequestType" />
      <xs:element name="MassPayResponse" type="ns:MassPayResponseType" />
    <xs:element name="MassPayReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:MassPayRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="MassPayRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="EmailSubject" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Subject line of the email sent to all recipients. This subject is not contained in the input file; you must create it with your application.
      <br />
      <br />
      Optional
      <br />
      <br />
      Character length and limitations: 255 single-byte alphanumeric characters
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="ReceiverType" type="ebl:ReceiverInfoCodeType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Indicates how you identify the recipients of payments in all MassPayItems: either by EmailAddress (ReceiverEmail in MassPayItem), PhoneNumber (ReceiverPhone in MassPayItem), or by UserID (ReceiverID in MassPayItem).
      <br />
      <br />
      <b>Required.</b>
      You must specify one or the other of EmailAddress or UserID.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="MassPayItem" type="ns:MassPayRequestItemType" minOccurs="1" maxOccurs="250">
    <annotation>
    <documentation>
      Details of each payment. A single MassPayRequest can include up to 250 MassPayItems.
      <br />
      <br />
      <b>Required</b>
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="MassPayResponseType">
    <xs:complexContent>
      <xs:extension base="ebl:AbstractResponseType" />
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="MassPayRequestItemType">
    <xs:annotation>
      <xs:documentation>MassPayRequestItemType</xs:documentation>
      </xs:annotation>
    <xs:sequence>
    <xs:element name="ReceiverEmail" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Email address of recipient.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
      <br />
      <br />
      Character length and limitations: 127 single-byte characters maximum.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="ReceiverPhone" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Phone number of recipient.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
      <br />
      <br />
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="ReceiverID" type="ebl:UserIDType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Unique PayPal customer account number. This value corresponds to the value of PayerID returned by GetTransactionDetails.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
      <br />
      <br />
      Character length and limitations: 17 single-byte characters maximum.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Payment amount. You must set the currencyID attribute to one of the three-character currency codes for any of the supported PayPal currencies.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      You cannot mix currencies in a single MassPayRequest. A single request must include items that are of the same currency.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="UniqueId" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Transaction-specific identification number for tracking in an accounting system.
      <br />
      <br />
      Optional
      <br />
      <br />
      Character length and limitations: 30 single-byte characters. No whitespace allowed.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Custom note for each recipient.
      <br />
      <br />
      Optional
      <br />
      <br />
      Character length and limitations: 4,000 single-byte alphanumeric characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:complexType>
      <xs:element name="BAUpdateRequest" type="ns:BAUpdateRequestType" />
      <xs:element name="BAUpdateResponse" type="ns:BAUpdateResponseType" />
    <xs:element name="BillAgreementUpdateReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:BAUpdateRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="BAUpdateRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="MpID" type="ebl:MerchantPullIDType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Preapproved Payments billing agreement identification number. Corresponds to the FORM variable mp_id.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Character limit: 19 single-byte alphanumeric characters. The format of a billing agreement identification number is the single-character prefix B, followed by a hyphen and an alphanumeric character string:
      <br />
      <br />
      B-unique_alphanumeric_string
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Custom" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Custom annotation field for your exclusive use
      <br />
      <br />
      Optional
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Desc" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Description of goods or services associated with the billing agreement
      <br />
      <br />
      Optional
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="MpStatus" type="ebl:MerchantPullStatusCodeType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      The current status of the billing agreement
      <br />
      <br />
      Optional
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="BAUpdateResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
      <xs:element ref="ebl:BAUpdateResponseDetails" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="AddressVerifyRequest" type="ns:AddressVerifyRequestType" />
      <xs:element name="AddressVerifyResponse" type="ns:AddressVerifyResponseType" />
    <xs:element name="AddressVerifyReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:AddressVerifyRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="AddressVerifyRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="Email" type="ebl:EmailAddressType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Email address of buyer to be verified.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Maximum string length: 255 single-byte characters Input mask: ?@?.??
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Street" type="xs:string" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      First line of buyers billing or shipping street address to be verified.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      For verification, input value of street address must match the first three single-byte characters of the street address on file for the PayPal account.
      <br />
      <br />
      Maximum string length: 35 single-byte characters Alphanumeric plus Whitespace and case of input value are ignored.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Zip" type="xs:string" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Postal code to be verified.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      For verification input value of postal code must match the first five single-byte characters of the postal code on file for the PayPal account.
      <br />
      <br />
      Maximum string length: 16 single-byte characters Whitespace and case of input value are ignored.
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="AddressVerifyResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
    <xs:element name="ConfirmationCode" type="ebl:AddressStatusCodeType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Confirmation of a match with one of the following tokens:
      <br />
      <br />
      None: The input value of the Email object does not match any email address on file at PayPal.
      <br />
      <br />
      Confirmed: If the value of the StreetMatch object is Matched PayPal responds that the entire postal address is confirmed.
      <br />
      <br />
      Unconfirmed: PayPal responds that the postal address is unconfirmed
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="StreetMatch" type="ebl:MatchStatusCodeType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      PayPal has compared the postal address you want to verify with the postal address on file at PayPal.
      <br />
      <br />
      None: The input value of the Email object does not match any email address on file at PayPal. In addition an error response is returned. No further comparison of other input values has been made.
      <br />
      <br />
      Matched: The street address matches the street address on file at PayPal.
      <br />
      <br />
      Unmatched: The street address does not match the street address on file at PayPal.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="ZipMatch" type="ebl:MatchStatusCodeType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      PayPal has compared the zip code you want to verify with the zip code on file for the email address.
      <br />
      <br />
      None: The street address was unmatched. No further comparison of other input values has been made.
      <br />
      <br />
      Matched: The zip code matches the zip code on file at PayPal.
      <br />
      <br />
      Unmatched: The zip code does not match the zip code on file at PayPal.
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="CountryCode" type="ebl:CountryCodeType" minOccurs="0" maxOccurs="1">
    <annotation>
      <documentation>Two-character country code (ISO 3166) on file for the PayPal email address.</documentation>
      </annotation>
      </xs:element>
    <xs:element name="PayPalToken" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      The token prevents a buyer from using any street address other than the address on file at PayPal during additional purchases he might make from the merchant. It contains encrypted information about the users street address and email address. You can pass the value of the token with the Buy Now button HTML address_api_token variable so that PayPal prevents the buyer from using any street address or email address other than those verified by PayPal. The token is valid for 24 hours.
      <br />
      Character length and limitations: 94 single-byte characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="EnterBoardingRequest" type="ns:EnterBoardingRequestType" />
      <xs:element name="EnterBoardingResponse" type="ns:EnterBoardingResponseType" />
    <xs:element name="EnterBoardingReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:EnterBoardingRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="EnterBoardingRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
      <xs:element ref="ebl:EnterBoardingRequestDetails" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="EnterBoardingResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
    <xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      A unique token that identifies this boarding session. Use this token with the GetBoarding Details API call.
      <br />
      <br />
      Character length and limitations: 64 alphanumeric characters. The token has the following format:
      <br />
      <br />
      OB-61characterString
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="GetBoardingDetailsRequest" type="ns:GetBoardingDetailsRequestType" />
      <xs:element name="GetBoardingDetailsResponse" type="ns:GetBoardingDetailsResponseType" />
    <xs:element name="GetBoardingDetailsReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:GetBoardingDetailsRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="GetBoardingDetailsRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      A unique token returned by the EnterBoarding API call that identifies this boarding session.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Character length and limitations: 64 alphanumeric characters. The token has the following format:
      <br />
      <br />
      OB-61characterString
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="GetBoardingDetailsResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
      <xs:element ref="ebl:GetBoardingDetailsResponseDetails" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="SetExpressCheckoutRequest" type="ns:SetExpressCheckoutRequestType" />
      <xs:element name="SetExpressCheckoutResponse" type="ns:SetExpressCheckoutResponseType" />
    <xs:element name="SetExpressCheckoutReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:SetExpressCheckoutRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="SetExpressCheckoutRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
      <xs:element ref="ebl:SetExpressCheckoutRequestDetails" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="SetExpressCheckoutResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
    <xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      A timestamped token by which you identify to PayPal that you are processing this payment with Express Checkout. The token expires after three hours. If you set Token in the SetExpressCheckoutRequest, the value of Token in the response is identical to the value in the request.
      <br />
      <br />
      Character length and limitations: 20 single-byte characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="GetExpressCheckoutDetailsRequest" type="ns:GetExpressCheckoutDetailsRequestType" />
      <xs:element name="GetExpressCheckoutDetailsResponse" type="ns:GetExpressCheckoutDetailsResponseType" />
    <xs:element name="GetExpressCheckoutDetailsReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:GetExpressCheckoutDetailsRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="GetExpressCheckoutDetailsRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      A timestamped token, the value of which was returned by SetExpressCheckoutResponse.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Character length and limitations: 20 single-byte characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="GetExpressCheckoutDetailsResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
      <xs:element ref="ebl:GetExpressCheckoutDetailsResponseDetails" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="DoExpressCheckoutPaymentRequest" type="ns:DoExpressCheckoutPaymentRequestType" />
      <xs:element name="DoExpressCheckoutPaymentResponse" type="ns:DoExpressCheckoutPaymentResponseType" />
    <xs:element name="DoExpressCheckoutPaymentReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:DoExpressCheckoutPaymentRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="DoExpressCheckoutPaymentRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
      <xs:element ref="ebl:DoExpressCheckoutPaymentRequestDetails" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="DoExpressCheckoutPaymentResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
      <xs:element ref="ebl:DoExpressCheckoutPaymentResponseDetails" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="DoDirectPaymentRequest" type="ns:DoDirectPaymentRequestType" />
      <xs:element name="DoDirectPaymentResponse" type="ns:DoDirectPaymentResponseType" />
    <xs:element name="DoDirectPaymentReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:DoDirectPaymentRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="DoDirectPaymentRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
      <xs:element ref="ebl:DoDirectPaymentRequestDetails" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="DoDirectPaymentResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
    <xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
    <annotation>
      <documentation>The amount of the payment as specified by you on DoDirectPaymentRequest.</documentation>
      </annotation>
      </xs:element>
    <xs:element name="AVSCode" type="xs:string" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Address Verification System response code. Character limit: One single-byte alphanumeric character
    <table>
    <tr>
      <th>AVS Code</th>
      <th>Meaning</th>
      <th>Matched Details</th>
      </tr>
    <tr>
      <td>A</td>
      <td>Address</td>
      <td>Address only (no ZIP)</td>
      </tr>
    <tr>
      <td>B</td>
      <td>International A</td>
      <td>Address only (no ZIP)</td>
      </tr>
    <tr>
      <td>C</td>
      <td>International N</td>
      <td>None</td>
      </tr>
    <tr>
      <td>D</td>
      <td>International X</td>
      <td>Address and Postal Code</td>
      </tr>
    <tr>
      <td>E</td>
      <td>Not allowed for MOTO (Internet/Phone) transactions</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>F</td>
      <td>UK-specific X</td>
      <td>Address and Postal Code</td>
      </tr>
    <tr>
      <td>G</td>
      <td>Global Unavailable</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>I</td>
      <td>International Unavailable</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>N</td>
      <td>No</td>
      <td>None</td>
      </tr>
    <tr>
      <td>P</td>
      <td>Postal (International Z)</td>
      <td>Postal Code only (no Address)</td>
      </tr>
    <tr>
      <td>R</td>
      <td>Retry</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>S</td>
      <td>Service not Supported</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>U</td>
      <td>Unavailable</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>W</td>
      <td>Whole ZIP</td>
      <td>Nine-digit ZIP code (no Address)</td>
      </tr>
    <tr>
      <td>X</td>
      <td>Exact match</td>
      <td>Address and nine-digit ZIP code</td>
      </tr>
    <tr>
      <td>Y</td>
      <td>Yes</td>
      <td>Address and five-digit ZIP</td>
      </tr>
    <tr>
      <td>Z</td>
      <td>ZIP</td>
      <td>Five-digit ZIP code (no Address)</td>
      </tr>
    <tr>
      <td>All others</td>
      <td>Error Not applicable</td>
      <td />
      </tr>
      </table>
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="CVV2Code" type="xs:string" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Result of the CVV2 check by PayPal.
    <table>
    <tr>
      <th>CVV2 Code</th>
      <th>Meaning</th>
      <th>Matched Details</th>
      </tr>
    <tr>
      <td>M</td>
      <td>Match</td>
      <td>CVV2</td>
      </tr>
    <tr>
      <td>N</td>
      <td>No match</td>
      <td>None</td>
      </tr>
    <tr>
      <td>P</td>
      <td>Not Processed</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>S</td>
      <td>Service not Supported</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>U</td>
      <td>Unavailable</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>X</td>
      <td>No response</td>
      <td>Not applicable</td>
      </tr>
    <tr>
      <td>All others</td>
      <td>Error</td>
      <td>Not applicable</td>
      </tr>
      </table>
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="TransactionID" type="ebl:TransactionId" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Transaction identification number.
      <br />
      <br />
      Character length and limitations: 19 characters maximum.
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="DoCaptureRequest" type="ns:DoCaptureRequestType" />
      <xs:element name="DoCaptureResponse" type="ns:DoCaptureResponseType" />
    <xs:element name="DoCaptureReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:DoCaptureRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="DoCaptureRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="AuthorizationID" type="ebl:AuthorizationId" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      The authorization identification number of the payment you want to capture.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Character length and limits: 19 single-byte characters maximum
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Amount to authorize. You must set the currencyID attribute to USD.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Limitations: Must not exceed $10,000 USD in any currency. No currency symbol. Decimal separator must be a period (.), and the thousands separator must be a comma (,)
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="CompleteType" type="ebl:CompleteCodeType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Indicates if this capture is the last capture you intend to make. The default is Complete. If CompleteType is Complete, any remaining amount of the original reauthorized transaction is automatically voided.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Character length and limits: 12 single-byte alphanumeric characters
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      An informational note about this settlement that is displayed to the payer in email and in transaction history.
      <br />
      <br />
      Optional
      <br />
      <br />
      Character length and limits: 255 single-byte characters
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="InvoiceID" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Your invoice number or other identification number.
      <br />
      <br />
      The InvoiceID value is recorded only if the authorization you are capturing is an order authorization, not a basic authorization.
      <br />
      <br />
      Optional
      <br />
      <br />
      Character length and limits: 127 single-byte alphanumeric characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="DoCaptureResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
      <xs:element ref="ebl:DoCaptureResponseDetails" minOccurs="1" maxOccurs="1" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="DoReauthorizationRequest" type="ns:DoReauthorizationRequestType" />
      <xs:element name="DoReauthorizationResponse" type="ns:DoReauthorizationResponseType" />
    <xs:element name="DoReauthorizationReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:DoReauthorizationRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="DoReauthorizationRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      The value of a previously authorized transaction identification number returned by a PayPal product. You can obtain a buyers transaction number from the TransactionID element of the PayerInfo structure returned by GetTransactionDetailsResponse.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Character length and limits: 19 single-byte characters maximum
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Amount to reauthorize.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Limitations: Must not exceed $10,000 USD in any currency. No currency symbol. Decimal separator must be a period (.), and the thousands separator must be a comma (,).
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="DoReauthorizationResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
    <xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      A new authorization identification number.
      <br />
      <br />
      Character length and limits: 19 single-byte characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="DoVoidRequest" type="ns:DoVoidRequestType" />
      <xs:element name="DoVoidResponse" type="ns:DoVoidResponseType" />
    <xs:element name="DoVoidReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:DoVoidRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="DoVoidRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      The value of the original authorization identification number returned by a PayPal product.
      <br />
      <br />
      If you are voiding a transaction that has been reauthorized, use the ID from the original authorization, and not the reauthorization.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Character length and limits: 19 single-byte characters
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      An informational note about this settlement that is displayed to the payer in email and in transaction history.
      <br />
      <br />
      Optional
      <br />
      <br />
      Character length and limits: 255 single-byte characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    <xs:complexType name="DoVoidResponseType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractResponseType">
    <xs:sequence>
    <xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      The authorization identification number you specified in the request.
      <br />
      <br />
      Character length and limits: 19 single-byte characters
      </documentation>
      </annotation>
      </xs:element>
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
      <xs:element name="DoAuthorizationRequest" type="ns:DoAuthorizationRequestType" />
      <xs:element name="DoAuthorizationResponse" type="ns:DoAuthorizationResponseType" />
    <xs:element name="DoAuthorizationReq">
    <xs:complexType>
    <xs:sequence>
      <xs:element ref="ns:DoAuthorizationRequest" />
      </xs:sequence>
      </xs:complexType>
      </xs:element>
    <xs:complexType name="DoAuthorizationRequestType">
    <xs:complexContent>
    <xs:extension base="ebl:AbstractRequestType">
    <xs:sequence>
    <xs:element name="TransactionID" type="xs:string" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      The value of the orders transaction identification number returned by a PayPal product.
      <br />
      <br />
      <b>Required</b>
      <br />
      <br />
      Character length and limits: 19 single-byte characters maximum
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="TransactionEntity" type="ebl:TransactionEntityType" minOccurs="0" maxOccurs="1">
    <annotation>
    <documentation>
      Type of transaction to authorize. The only allowable value is
      <b>Order</b>
       which means that the transaction represents a customer order that can be fulfilled over 29 days.
      <br />
      <br />
      Optional
      </documentation>
      </annotation>
      </xs:element>
    <xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
    <annotation>
    <documentation>
      Amount to authorize.
      &l

    can you remove this from WSDL  <wsdl:definitions> tag.
    xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:cc="urn:ebay:apis:CoreComponentTypes"
    and add name="yourmessage interface" in <wsdl:definitions> tag.

  • How to convert the character value to currency/numeric

    Hi,
    See the sample code here
    data: v_qtr_field(7).
    data: w_low_limit like glt0-kslvt,
          w_amount like glt0-hslvt.
    w_low_limit = 02.
    w_max_period = 3.
    concatenate 'HSL' w_low_limit into v_qtr_field.
    *comment
    *I am looking for a field formation thru above code like in GLT0 table like HSL02,HSL03 *etc based on the value user entered in the selection *screen
    DO w_max_period TIMES
      VARYING w_amount FROM v_qtr_field NEXT v_qtr_field + 1.
       t_trans_values-dmbe2 = t_trans_values-dmbe2 + w_amount.
      ENDDO.
    I am facing problem in the Do loop as it wont allows multiple data types. can you suggest me how to convert the v_qtr_field whose data type is character to currency?

    Hi,
    Please check this code .
    PERFORM write_currency
                  USING buf_anla-urwrt t_dates-waers t_txw_anla-urwrt.
    *       FORM WRITE_CURRENCY                                           *
    *       convert currency amount to string                             *
    *       - use decimal point                                           *
    *       - remove separator characters                                 *
    *  -->  P_AMOUNT                                                      *
    *  -->  P_CURRENCY_UNIT                                               *
    *  -->  P_STRING                                                      *
    FORM WRITE_CURRENCY
         USING P_AMOUNT        TYPE P
               P_CURRENCY_UNIT LIKE TCURC-WAERS
               P_STRING        TYPE C.
      DATA: DEC2POINT(2) TYPE C VALUE ',.'.
    * convert separator to decimal point
      WRITE P_AMOUNT TO P_STRING CURRENCY P_CURRENCY_UNIT
            NO-GROUPING
            NO-SIGN
            LEFT-JUSTIFIED.
      TRANSLATE P_STRING USING DEC2POINT.
    * put minus sign before number
      IF p_amount < 0.
        SHIFT P_STRING RIGHT.
        P_STRING(1) = '-'.
      ENDIF.
    ENDFORM.
    <i>Hope This Info Helps YOU.</i>
    Regards,
    Lakshmi

  • Need suggestion on Multi currency and Unicode character set use in ABAP

    Hi All,
    Need suggestion. In one of the requirement I saw 'multi-currency and Unicode character set experience in FICO'.
    Can you please elaborate me how ABAPers are invlolved in multi currency as I think this is FICO fuctional area.
    And also what is Unicode character set exp.? Please give me some document of you have any.
    Thanks
    Sreedevi
    Moderator message - This isn't the place to prepare for interviews - thread locked
    Edited by: Rob Burbank on Sep 17, 2009 4:45 PM

    Use the default parser.
    By default, WebLogic Server is configured to use the default parser and transformer to parse and transform XML documents. The default parser and transformer are those included in the JDK 5.0.
    The built-in WebLogic Server DOM factory implementation class is com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl.
    The DocumentBuilderFactory.newInstance method returns the built-in parser.
    DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();

  • Help needed to display character vaiable in currency format

    Hi Friends
    In a SAP Script I am passing a currency field to the subroutine as an i/p parameter and since it gets converted to character format in subroutine because of 'itcsy' , ihave deleted the trailing zeroes and decimal points from the field and performed calculations on the field, now i need to pass this char field back to SAP script but i need to display that field in currency format with commas and decimal points in the script...how do i do that???
    Thanks
    Vishal.

    Hi Vishal,
    When you pass the currency amount into the perform, no need to remove the trailing zeros and the decimal point.
    Only thing you need to remove is the comma seperator as it gives a runtime error during calculation.
    To convert it back to the format with comma, write the below command:
    WRITE v_Item_total currency '2' to v_item_char.
    CONDENSE v_item_char.
    Here v_item_total is a number which is converted to comma seperated number and passed to char variable.
    This char variable is then passed to the SCRIPT.
    regards,
    Gaurav.

  • Problems with EURO currency character

    Hi,
    I'm trying to insert the EURO currency character (€) in a CHAR field from a Java client but after the insert in the field I find a ? turned upside down.
    I'm using
    - Oracle DB server 11.2.0.1.0 running with character set US7ASCII (same problem with a different Oracle server with WE8ISO8859P1 encoding) on a Linux Red Hat server
    - Java client with JDBC driver 11.2.0.1.0 (ojdbc5.jar) with JDK 5 running on Windows XP: the encoding of the JVM is CP1252.
    I've googled a lot but found only solutions like "... change the encoding of the DB ...": I can't change the DB encoding.
    Any idea?
    Thanks.
    Here's is a test case:
    ************ begin test case ************
    Statement stmt = null;
    PreparedStatement pst = null;
    Connection conn = null;
    ResultSet rs = null;
    try {
         Class.forName("oracle.jdbc.driver.OracleDriver");
         conn = DriverManager.getConnection("jdbc:oracle:thin:@SERVER:1521:SID", "USER", "PASSWORD");
         stmt = conn.createStatement();
         stmt.execute("CREATE TABLE JJOVA(A CHAR(5) NOT NULL)");
         stmt.close();
         pst = conn.prepareStatement("INSERT INTO JJOVA(A) VALUES(?)");
         pst.setString(1, "€");
         pst.execute();
         stmt = conn.createStatement();
         rs = stmt.executeQuery("select A from JJOVA");
         while (rs.next()) {
              String tmp = rs.getString(1);
              System.out.println(tmp);
         rs.close();
         pst.close();
         stmt = conn.createStatement();
         stmt.execute("DROP TABLE JJOVA");
    } catch(Exception e) {
         e.printStackTrace();
    } finally {
         try {
              if (rs != null) {
                   rs.close();
              if (pst != null) {
                   pst.close();
              if (stmt != null) {
                   stmt.close();
              if (conn != null) {
                   conn.close();
         } catch(Exception dontcare) {}
    ************ end test case ************
    Regards,
    Andrea

    Thank you Oradba for the explanation of the COBOL program behavior: we're going to change the DB character set (export/import seems not required, we've found an Oracle Note 257722.1 "Changing WE8ISO8859P1 to WE8ISO8859P15"). I'll mark your answer as the (most) correct.
    Oviwan, NLS_NCHAR_CHARACTERSET is AL16UTF16: I tried with an NCHAR field but I can't even store correctly accented vowels.
    Thank you very much everyone,
    Andrea

  • Convert currency to character in smartforms.

    Hi Friends,
    I need one solution.
    I have 5 currency fields and i wanna print these currencies fields into character format in SMARTFORMS.
    How can we do it.
    Plz reply me as soon as possible.
    Thanks & Regards,
    Swapnika

    hi swapnika,
    u need to print amount in words. is this ur requiremnet?
    if s then TAKE A LOOK OF  following code.
    DATA : W_AMOUNT TYPE PC207-BETRG ,
           W_DUTY TYPE IN_WORDS.
    MOVE reguh-rwbtr TO W_AMOUNT.
    CALL FUNCTION 'HR_IN_CHG_INR_WRDS'
    EXPORTING
    amt_in_num   = W_AMOUNT
    IMPORTING
    amt_in_words = W_DUTY.
      REPLACE 'RUPEES' WITH '' INTO W_DUTY.
      REPLACE 'ONLY' WITH '' INTO W_DUTY.
    IF WANTMORE HELP LET M KNW..

  • Currency format - $ replaced by strange character

    Sorry for the duplicate post. I had posted this earlier on the Java Programming forum, but I then I thought this would probably a more appropriate forum for this message.
    I have a web application in which I have HTML tables that show some amount values that have been formatted using the following code:
    NumberFormat.getCurrencyInstance().format(dataElement);
    My development environment is WindowsNT and things work perfectly on it. The problem is that when I move the war file onto the production system (on Sun solaris), the $ sign before the currency amount is replaced by a star shaped character. I am not sure if this is due to the operating system or the font/display settings on the server machine.
    Any ideas on resolvinbg this issue would be appreciated.

    NumberFormat.getCurrencyInstance() returns different formats depending on your default locale. If they are different between the two systems, that suggests that your default locales are different.Locale.getDefault().toString()will tell you what they are.

  • Character  type to currency type conversion

    hi all,
    i need to transfer the character type data to the currency type data.
    my requirement is when i am trying to transfer the data from excel i need to store it as a character. again i need to change the same as currency. any pointers will be highly appriciated.
    thanks.

    Hi use the belwo function module and first move the currecy field to character..and inthe out put table decclare field as character 20 ..and download the field..
    hope will works..
    Amount to string:
    CALL FUNCTION 'HRCM_AMOUNT_TO_STRING_CONVERT'
      EXPORTING
        betrg                         = w_curerency          "currency field
        WAERS                         = 'DKK'
    IMPORTING
       STRING                        =  slam          .    "Output table field type char20
    String to amount:
    CALL FUNCTION 'HRCM_STRING_TO_AMOUNT_CONVERT'
      EXPORTING
        string                    = slam2             "character field
        DECIMAL_SEPARATOR         = '.'
      THOUSANDS_SEPARATOR       =
        WAERS                     = 'HUF'
    IMPORTING
       BETRG                     = b2 .        "converting into currency field
    Prabhudas

  • Moving of character to currency fields

    Dear all,
    i want to populate the numerical value of a character type field to
    currency type field. Pls help me to handle the decimals.
    For eg:
    data : v1(15)  type c value '123456',
              v2       type netwr_ak.
          move v1 to v2.
    How to handle if the value of V1 is 12344546.56 (with decimals)
    I have to get the output as 12.344.546,56.
    Thanks in advance...
    Regards,
    Shalem

    Dear shalem,
    You can pass character field value '12345678.99' to numerical value field.
    And that numberical field will display value 12.345.678,99
    <b>Ex:
    data: f1(15) type c value '12345678.99',
            f2 type netwr_ak.
    move v1 to v2.
    write v2.</b>
    <u>output shows:</u>
    v2 = '12345678.99'
    Reward points if helpful.
    cheer !
    Moqeeth.

  • Character viewer & Currency Symbols

    Yosemite 10.10.3
    I have been trying to access the shortcuts or whatever for various currencies other than $.  I found this on the internet (I know it is not Apple but it is easier to read than anything I have found in these support circles) http://www.maketecheasier.com/type-euro-sign-mac/.   I was able to navigate to enter a € symbol but am using many different currencies and need to have access to all. 
    I have gone to System Preferences > Keyboard and have checked the box for 'Show Keyboard & Characters in Menu Bar'.  I navigated to 'Input Sources' but do not see the option to include the Keyboard & Character Viewer in the list area as it shows on this link.  I do not see mention of it in any other of the support posts so perhaps this is an old feature. 
    The following Apple support post How to type accents, emoji, and symbols on your Mac - Apple Support  indicates that I should be able to find currencies as a special character.  But when I follow those instructions I don't see that I have options for currencies:
    Can someone point me in the right direction?
    Message was edited by: agremminger
    I meant to add a screen shot of the 'missing' character viewer on the input sources tab.

    I see the character viewer now on the menu bar with the flag.  From here it appears that I can view the currencies too.

  • GBP currency symbol showing an extra character.

    Hi
    We're using Oracle Apps 11.5.10 running under Linux with XML Publisher 5.6.
    We are developing an invoice template (RTF) that is muti currency. Our instance is defaulted to NLS_TERRITORY=AMERICA but when we are running a concurrent program to generate the XML file and base on the billing currency, we set the session to its corresponding language (ex: NLS_TERRITORY=UNITED KINGDOM'). In the case of GBP, the XML file does show the "£" in the invoice amount field. But when you look at the PDF file that it generates, the invoice amount has an extra character before the sterling pound symbol:
    £1,000.00
    I tried the <?format-currency:INVOICE_AMOUNT;'GBP'?> but to no avail.
    Any help would greatly appreciated.

    Hi,
    Please check the thread Re: £ is being reported in Oracle reports instead of £
    Cheers!
    Gautam

  • How to get a currency format for a character field

    for some specifix reason, we have a requirement to show character field (which results in value 633948) in the format $633,948
    how do i do this?
    if i do SELECT to_char(:c_1,'$999,999')) from dual;
    it gives me ora: 01722: invalid number error
    c_1 is a user parameter of data type character

    Try using TO_NUMBER first, as in something like:
    SQL> VARIABLE c_1 VARCHAR2(6)
    SQL> EXECUTE :c_1 := '633948';
    PL/SQL procedure successfully completed.
    SQL> SELECT TO_CHAR(TO_NUMBER(:c_1), '$999,999') FROM DUAL;
    TO_CHAR(T
    $633,948Hope this helps.

Maybe you are looking for