PCard

We r using Standalore Scenario & trying to implement Pcard. We have made all the settings in SPRO settings and created Pcard service provider in R/3 Backend.
While shopping the Payment option Pcard is not enabling in the Drop down list.
Any other settings , pls let me know .
Thanks in Advance
Rgds
SHIV

Hi
I able to to shop with PCard and it is creating the Commitment in the backend system. The next steps which i would like know the following.
1.Whether system should generate the Invoice.
2.What format the PCard Company should send the statement to EBP System
3. How does the statement get converted to IDoc in EBP.
Thanks in advance
Rgds
SHIVA

Similar Messages

  • Pcard in combination with catalog

    Hi all,
    Is there someone who can explain me the process of Pcard purchases in combination with catalogs? I heard that there will be no request and purchase order in SRM for each purchase. There will be a periodic load from the catalog into SAP that creates a dummy requisition and order for all ordered items in that period. This order will be used to verify the settlement. Is this the correct process?
    If it is the correct process, can this be done with external and internal catalogs?
    Thanks,
    Ed

    Hi
    <b>Please go through the related helpful links -></b>
    <u>P-Card Basics</u> http://help.sap.com/saphelp_srm50/helpdata/en/61/2ff300787411d2b41d006094b92d37/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/97/b71c4145a6f723e10000000a155106/frameset.htm
    <u>Process flow -></u>
    http://help.sap.com/saphelp_srm50/helpdata/en/61/2ff300787411d2b41d006094b92d37/frameset.htm
    Pcard and Catalogs
    Re: Pcard Statement Processing
    Re: P card- Business process.
    Regards
    - Atul

  • PCard Functionality in Financials 8.8 SP1

    We are looking at implementing the Procurement card functionality in PeopleSoft Purchasing. We are in the very preliminary stages of this project and are in need of some further clarifications about how this is supposed to work. If there are any existing companies using this that we could contact that would great. But we would also like some feedback here as well.
    The big question we have is how is it implemented in conjuction with Requisitions and PO's. Where do these flow to and what information is transferred with regard to the Pcard. Is the Pcard transaction initiated with the Req or PO and info is sent to vendor. Or is Req or PO more backfilled after the fact from the bank statement. In other words where do these come into play in the process
    The other area revolves around Comodity Codes and Merchant Category Codes. What are there origins and how are they kept in sync. Are commodity codes internal to the application and only apply to items stored in a catalog? Do we need to load the MCC codes from the Pcard issuing bank?
    We have been able to find some very good information on how the card statements can be loaded into PS.
    Here is some of the PeopleBooks I have used:
    PeopleSoft Purchasing 8.8 PeopleBook > Managing Procurement Cards
    Enterprise PeopleTools 8.48 PeopleBook: Security Administration > Understanding PeopleSoft Security, Setting Up Permission Lists, Setting Up Roles, Administering User Profiles
    PeopleSoft Financials, Enterprise Service Automation and Supply Chain Management Application Fundamentals 8.8 PeopleBook > Defining Financials and Supply Chain Management Common Definitions
    What we are struggling with is the purpose of POs and Reqs in the process.
    Anything that someone could tell us about thier experience with PCard would be appreciated.
    Thanks!!
    Scott

    TomL <[email protected]> wrote:
    Any performance improvements?Yes.
    TomL <[email protected]> wrote:
    Is JDK 1.4.2 supported?No, BEA has not published 1.4.2 support for any platform -- some
    platforms do support 1.4.1_03, though.
    TomL <[email protected]> wrote:
    Any changes in supported JDBC drivers?Yes, see e-docs.
    Brian J. Mitchell
    Systems Administrator, MIS
    TRX
    6 West Druid Hills Drive
    Atlanta, GA 30329 USA
    http://www.trx.com
    email: [email protected]
    office: +1 404 327 7238
    mobile: +1 678 283 6530

  • Using PCard, Procurement Card, Purchasing Card

    Client wants to use pcards as part of the procurement process. They are planning on implementing ECC. If we use standard Preq and PO functionality, can we use Pcards? If so, what is the process flow?
    Are Pcards only an SRM functionality?

    Hi
       PCard is a visa or master card credit card that offers alternative procurement, issued to an individual and the individual is responsible for its use and may be personally liable if the card is misused.
    Functional Flow
        1. Create Purchase requisition ( can go for a custom doc type if required)
        2. Create Purchase Order ( Here the vendor is the Bank)
        3. Purchase with Credit Card.
        4. After goods are received Post the GR against PO.
        5. Card holder receives the bank statement
        6. Statement is sent to accounting office where it is reconciled.
        7. Post the invoice.
        8. Pcard issuer (Bank) is Paid.
    Hope it is clear.....
    Syed

  • Tracking Purchase Card (Pcard) vendor activity

    Is there a method of tracking vendor activity in Pcard purchases?
    We currently down load Pcard purchase activity weekly from the bank as a text file, convert to an Excel file and upload using a variant of transaction GLupload.  This works well enough for placing each transaction in the proper GL account/cost center but the entire balance is listed under the bank as the vendor.
    Is there a better way to manage Pcard payment so we can track the charges to individual merchants (vendors) so we can see how much we are paying each vendor without looking through each weekly upload?  Can we match pcard vendors to the SAP vendor master or a separate list of vendor such as business partner?
    Thanks for any ideas!
    Jeff

    Thanks VL, that's a good idea. 
    When I look at the Pcard transaction history there is a wide variety of Merchants, each with a unique identification such as CHEVRON 886, CHEVRON 554 etc.  This will work well for large merchants such as Dell but is there a way to deal with these numberuos individual merchants without having to set up a new vendor for each?  It will be very dificult to set up a new vendor for each new gas station or restaurant that is visited.
    Thanks to anyone that can provide input.
    Jeff

  • SRM PCard functionality in ECC MM

    Hi Friends,
    The standard PCard functionality is available in SRM.
    We are not going for SRM at the moment, but would like to incorporate the PCard functionality in the ECC environment.
    Is it possible to have PCard functionality in ECC? Where the statement can be uploaded via IDOC, vendor entry is posted at this time, further it goes to custom build workflow, and after approval the expense account is hit.
    Can we achieve this in ECC?
    Any idea
    Regards,
    Sandeep

    have you already checked the SAPHelp?
    http://help.sap.com/erp2005_ehp_04/helpdata/en/f0/ca4666260211d28a430000e829fbbd/frameset.htm
    br,G

  • Invoice for PCard Purchasing

    Hi,
    We have done the configuration steps for PCard and are able to create the SC as well as the PO.
    we have also configured the distribution model with the message types relavant to pcard.
    We need help in Invoice postings for the statement that will come from bank.
    1. In what format the Pcard statement from bank will come and where they will be saved
    2. How to Create the IDoc PCSTAT01.
    3. What settings are to be done for workflow approval of the invoices related to these.
    Please help us in building this scenario.
    Thanks & Regards,
    Priya

    Hi,
    You can setup Procurement Card WF as follows:
    Path:  Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Business Workflow
    There are two types available:
    1. WS10000093 u2013 First approval
    2. WS10000100 u2013 Second approval
    After the approval process has been completed, the system makes a posting to a G/L account in the back-end system for each purchasing transaction.
    (Check it; if it's working fine)
    When one approve's PCard ammount; the settlement data is available in the format IDoc BBP_PCSTAT01 & it creates invoice in backend.
    With BBP_PCSTAT01 you should setup ACLPAY, ACC_GOODS_MOVEMENT, ACPJMM (system debits & cost object) messages in distribution model.
    One gets bank statements in approver1's/approver2's inbox. Those are in CSV format.
    In the back-end system, Accounting must be set up and the card company must be created as a vendor.(Check it, I had missed it)
    Regards,
    yaniVy
    reward if helps

  • Pcard Statement Processing

    We currently have PCard processing implemented on BBPCRM 4.0. 
    We are moving to SRM on 5.5 Server. 
    The present processing of PCard statement is quite cumbersome and we would like to evaluate different options.  Current process…
    - Manually access PCard provider's web-site
    - Extract current month's procurement card transactions. 
    - The data is massaged and put into a .txt format file.
    - File is placed on to an ftp server.
    - A batch program is setup in B2B to pick up the file on the ftp server
    - File is converted into the PCard IDOC BBP_PCSTAT01 structure
       (using IDOC_INPUT_BBP_PCSTAT function module
       (as well as generates the invoice IDOC with associated FI invoice in R/3)
    Processing monthly statements and testing is an administrative nightmare trying to line up appropriate data in the text file.
    Also, we currently only create one document for the entire month's file.
    So the 1 document consists of multiple lines for the multiple PCard #'s and multiple transactions.
    I would be interested in how others process the PCard Statements from their PCard Providers.
    - How they receive data from the Pcard provider.
    - How they bring it into their system
    - If they process one document for a statement, 1/PCard# or 1/Pcard transaction.
    - And any additional information that may assist us in this process.
    Thank you!
    Heather Keating / Capgemini / Toronto
    SAP Module Expert / New Horizon System Solutions
    Office: +1 416 207 6446 / www.ca.capgemini.com
    800 Kipling Ave, Etobicoke, ON, M8Z 5S4
    Email: [email protected]

    Hi
    <u>We have done similar work long time back. In that case, we have created a custom program as per our business requirements.</u>
    <b>Here are some related links on P-Card Process Flow -></b>
    <u>P-Card Process Flow</u>
    http://help.sap.com/saphelp_srm50/helpdata/en/61/2ff300787411d2b41d006094b92d37/frameset.htm
    P-Card Settlement
    Re: Implementing PCARDS
    Procurement card Settlement
    Help needed: Cannot use zero rate tax code (V0) with p-card IDOC
    Note 781149 XML Procedure for IDOC BBP_PCSTAT01
    Note 610088 - Report BBPPCRECN without local purchase orders
    Note 594228 - PCard: Admission of the address
    Note 214429 Tax postings in procurement cards
    Note 414087 Pcard. Credit memo in bank file with settlement data
    Note 176025 Procurement card:Field f.Transaction ID too short
    Help needed: Cannot use zero rate tax code (V0) with p-card IDOC
    http://www.dataxstream.com/doclib/ALESuccessfullyLeverageIDocs.pdf
    Do let me know, incase you need more details.
    Regards
    - Atul

  • PCARDS in extended classic scenario

    Is it possible to use PCARDS in extended classic scenario?

    Madidipa-
    True this is only available as a standard option with stand alone scenario.  However it can be enabled with a a customized process, using customer fields.  In fact this process was highlighted in a SAP Teched presentation a couple of years back.
    In short we created customer defined fields to hold the pcard, linked to the pcard master data tables in EBP, and then when it goes to the R/3 we created an additional account assingment category to make R/3 happy and set it for no invoice.(the pcard data was transferred to R/3 as additional customer fields)  As usual, with enough time and money most things are possible.
    Regards-
    b

  • PCard Configuration In ECS Scenario

    Dear Gurus,
    Greetings for the day,
    We are currently in between Development of Procurement Card (PCARD) Deployment in our customer landscape. They have SRM 5.0 version with  Extended Classic Scenario (ECS)
    We have performed below Configurations from SRM point of View:
    - Configuration of Number Range for Procurement Card
    - Define Card Company
    - Allocate Company Code (Mapping of Back end Vendor, Clearing Account & Account Type)
    - Define Blocking Reasons
    - Manage Procurement Card Commitments
    - Process Procurement Card
    Also User Authorization Prospective we have completed below activities:
    - Provide Procurement Card role (SAP_CRM_PAYMENT_CARD)
    - Add Profile (M_BBP_PC) to respective user
    - Maintain Parameter ID's (PCC & PCI)
    - Maintain Authorization value as "4" while creating Procurement Card Master
    Issue: When we tried to raise an "Describe Request" shopping cart with this user we are unable to see "Procurement Card" field in Shopping Cart "Basis Data" tab.
    Also i am unable to find any option to maintain "Product Categories" option under "Procurement Card" node. So in case of SRM 5.0 scenario this option is not available? please advice
    If any one has suggestions please advise.
    Thanks & Regards,
    Manish

    Dear Experts,
    Kindly help me to resolve above issue on SRM PCard Deplyoment
    Thanks & Regards,
    Manish

  • Does SRM 7 Extended Classic Scenario support PCards?

    Does SRM 7 Extended Classic Scenario support PCards as standard?  I know SRM 4 does not but wanted to know if that has changed.

    Paul,
    URL https://websmp208.sap-ag.de/support  ( service.sap.com) ...on header
    Go to 'Release& Upgrade Info' ..then sub item  'Release notes'....look for SAP Solutions on left scroll...then select SRM...
    Open pdf file ' Release Notes SAP SRM 2007, SP00 - SP04 '...and look for pg # 40...
    Let me know if you did not get it..
    Thanks,
    Rahul Mandale

  • Pcard integration in Classic Scenario

    Hi All
    I learnt that it is possible to use pCard in Classic Scenario if a few customizations are made.
    These customizations include adding a few custom fields in the shopping cart & ECC PO for Pcard Company, Pcard Number
    and Validity date.
    However once these customizations are done, would the reconciliation in SRM work as in ECS, or further code changes will be required?
    Thanks
    Kedar

    KedarG wrote:
    > Is it possible in Classic Scenario, to send the SUS confirmation to SRM instead and from there to ECC
    NO. dont think of a situation like that. if it is classic scenario except SC every thing will in ECC. how do you think confirmation creation can be possible in SRM when PO is not present in SRM!!
    > Can you provide some details on ECC workflows. I didn't find any thing on this. Does ECC even support workflows as SRM?
    >
    SRM is a kiddo infront of ECC, so workflows definitely are present in ECC(not BRFs but event driven wfs).
    any ways, your solution would be a custom solution, implement MB_DOCUMENT_BADI, to trigger a custom WF from custom event. this can be used for notification and stuff. but it wont stop the execution, so, dig on it how to stop the GR post till the workflow is not over.
    and invoice anyways has workflows which you can use

  • PCard Authorisation Step

    Just a question re Pcards and the reconciliation process.
    After loading the statement, the workflow agent for the reconciliation workflow is identified by the entry in the card master.
    The second approver agent in the pcard master is required for the authorisation step.
    Is it possible to omit the second approval and take the reconciliation step as the final one required?

    Sorted it myself.
    In the PCard master, the entry for Approval2 (BBP_PCMAS-PCAP2LIM) needs to be maintained with a high value.
    Any value below this will get automatically posted to financials. Anything above it will go on for approval.

  • Generating 1099 for Vendors (PCard Vendors)

    Hi,
    We are in the process of generating 1099 for PCard Vendor from Oracle Applications 11.5.10, which will be filed with the IRS. The following are the fields which needs to be populated.
    1. TIN No
    2. Merchant Name
    3. Address
    4. City
    5. State
    6. Zip
    7. Amount Paid
    I have information for all of the above, but not the Address of the Merchant Name. I was wondering if anybody out there faced the same issue and how did you guys go about getting a solution for this. I plan to generate the file manually and not use the Oracle seeded process.
    The Address is a Required field for the IRS.
    Did anybody of you use a 3rd party Web Service to get Address? If so which one ? btw the TIN is not a required field for the IRS (and we dont have TIN numbers for our PCard Vendors). I would really appreciate if you could let me know.
    thanks
    Kiran Ramachandra __._

    Kiran,
    We have the same question. I pressed the bank for the data in the download but they said they did not have it in the transaction file.
    No other ideas - we are doing it manually since we limit pCard use to a select group of Suppliers.
    Jean

  • Error while running a eBS webservice from the SoapUI Tool

    Hello All,
    I am trying to run PurchaseOrder Service webservice from the soap ui tool, In this service there are 6 methods are available and i am currently running the QueryPurchaseOrder method:
    Following is the soap message I am running:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pox="http://xmlns.oracle.com/java/oracle/apps/po/services/poxpoepo/POXPOEPOServices_DocStyle/" xmlns:orac="http://oracle.apps.fnd.soa.forms.services.rt.formsSchema/">
    <soapenv:Header>
    <pox:SOAHeader>
    <!--Optional:-->
    <pox:Responsibility></pox:Responsibility>
    <!--Optional:-->
    <pox:RespApplication></pox:RespApplication>
    <!--Optional:-->
    <pox:SecurityGroup></pox:SecurityGroup>
    <!--Optional:-->
    <pox:NLSLanguage></pox:NLSLanguage>
    <!--Optional:-->
    <pox:Org_Id>204</pox:Org_Id>
    </pox:SOAHeader>
    </soapenv:Header>
    <soapenv:Body>
    <pox:queryPurchaseOrder_Request>
    <orac:OutsideProcessing>
    <!--Optional:-->
    <orac:Job></orac:Job>
    <!--Optional:-->
    <orac:Line></orac:Line>
    <!--Optional:-->
    <orac:OSPUnitType></orac:OSPUnitType>
    <!--Optional:-->
    <orac:OperationSequence></orac:OperationSequence>
    <!--Optional:-->
    <orac:ResourceSequence></orac:ResourceSequence>
    <!--Optional:-->
    <orac:ResourceCode></orac:ResourceCode>
    </orac:OutsideProcessing>
    <orac:PoHeaders>
    <!--Zero or more repetitions:-->
    <orac:PoLines>
    <orac:LineNum>1</orac:LineNum>
    <orac:LineType>Goods</orac:LineType>
    <!--Optional:-->
    <orac:Item></orac:Item>
    <!--Optional:-->
    <orac:ItemRevision></orac:ItemRevision>
    <!--Optional:-->
    <orac:Job></orac:Job>
    <orac:ItemCategory>MISC.MISC</orac:ItemCategory>
    <orac:ItemDescription>test</orac:ItemDescription>
    <orac:UnitOfMeasure>EA</orac:UnitOfMeasure>
    <!--Optional:-->
    <orac:LineOrderQuantity></orac:LineOrderQuantity>
    <!--Optional:-->
    <orac:Quantity></orac:Quantity>
    <!--Optional:-->
    <orac:LineUnitPrice></orac:LineUnitPrice>
    <!--Optional:-->
    <orac:PromisedDate></orac:PromisedDate>
    <!--Optional:-->
    <orac:NeedByDate></orac:NeedByDate>
    <!--Optional:-->
    <orac:VendorProductNum></orac:VendorProductNum>
    <!--Optional:-->
    <orac:Amount></orac:Amount>
    <!--Optional:-->
    <orac:ChargeAccount></orac:ChargeAccount>
    <!--Optional:-->
    <orac:Reserved></orac:Reserved>
    <!--Optional:-->
    <orac:OPMLineSecondaryUOM></orac:OPMLineSecondaryUOM>
    <!--Optional:-->
    <orac:OPMLineSecondaryQuantity></orac:OPMLineSecondaryQuantity>
    <!--Optional:-->
    <orac:SecondaryQuantity></orac:SecondaryQuantity>
    <!--Optional:-->
    <orac:PreferredLineGrade></orac:PreferredLineGrade>
    <!--Optional:-->
    <orac:ItemListPrice></orac:ItemListPrice>
    <!--Optional:-->
    <orac:ItemMarketPrice></orac:ItemMarketPrice>
    <!--Optional:-->
    <orac:PriceType></orac:PriceType>
    <!--Optional:-->
    <orac:AllowPriceOverride></orac:AllowPriceOverride>
    <!--Optional:-->
    <orac:PriceLimit></orac:PriceLimit>
    <!--Optional:-->
    <orac:Negotiated></orac:Negotiated>
    <!--Optional:-->
    <orac:ContractNum></orac:ContractNum>
    <!--Optional:-->
    <orac:GlobalContract></orac:GlobalContract>
    <!--Optional:-->
    <orac:ContractOwningOrg></orac:ContractOwningOrg>
    <!--Optional:-->
    <orac:SourceDocumentType></orac:SourceDocumentType>
    <!--Optional:-->
    <orac:FromDocumentNum></orac:FromDocumentNum>
    <!--Optional:-->
    <orac:FromDocumentLineNum></orac:FromDocumentLineNum>
    <!--Optional:-->
    <orac:GlobalBlanket></orac:GlobalBlanket>
    <!--Optional:-->
    <orac:SourceDocumentOwningOrg></orac:SourceDocumentOwningOrg>
    <!--Optional:-->
    <orac:SupplierQuotation></orac:SupplierQuotation>
    <!--Optional:-->
    <orac:ProjectsContractNum></orac:ProjectsContractNum>
    <!--Optional:-->
    <orac:ProjectsContractRevNum></orac:ProjectsContractRevNum>
    <!--Optional:-->
    <orac:NoteToSupplier></orac:NoteToSupplier>
    <!--Optional:-->
    <orac:UNNum></orac:UNNum>
    <!--Optional:-->
    <orac:UNNumDescription></orac:UNNumDescription>
    <!--Optional:-->
    <orac:HazardClass></orac:HazardClass>
    <!--Optional:-->
    <orac:CapitalExpense></orac:CapitalExpense>
    <!--Optional:-->
    <orac:TransactionNature></orac:TransactionNature>
    <!--Optional:-->
    <orac:ContractorFirstName></orac:ContractorFirstName>
    <!--Optional:-->
    <orac:ContractorLastName></orac:ContractorLastName>
    <!--Optional:-->
    <orac:ContractorStartDate></orac:ContractorStartDate>
    <!--Optional:-->
    <orac:ContractorEndDate></orac:ContractorEndDate>
    <!--Optional:-->
    <orac:MinimumLineReleaseAmount></orac:MinimumLineReleaseAmount>
    <!--Optional:-->
    <orac:LineQuantityAgreed></orac:LineQuantityAgreed>
    <!--Optional:-->
    <orac:LineAmountAgreed></orac:LineAmountAgreed>
    <!--Optional:-->
    <orac:LlineQuantityReleased></orac:LlineQuantityReleased>
    <!--Optional:-->
    <orac:LineAmountReleased></orac:LineAmountReleased>
    <!--Optional:-->
    <orac:LineExpirationDate></orac:LineExpirationDate>
    <!--Optional:-->
    <orac:CumulativePricing></orac:CumulativePricing>
    <!--Zero or more repetitions:-->
    <orac:PoShipments>
    <orac:ShipmentNum>1</orac:ShipmentNum>
    <orac:ShiptoOrganization>M1</orac:ShiptoOrganization>
    <orac:ShipToLocation>M1- Seattle Mfg</orac:ShipToLocation>
    <!--Optional:-->
    <orac:UnitOfMeasure></orac:UnitOfMeasure>
    <orac:ShipmentQuantity>1</orac:ShipmentQuantity>
    <!--Optional:-->
    <orac:PromisedDate></orac:PromisedDate>
    <!--Optional:-->
    <orac:NeedByDate></orac:NeedByDate>
    <!--Optional:-->
    <orac:OriginalPromisedDate></orac:OriginalPromisedDate>
    <!--Optional:-->
    <orac:CountryofOrigin></orac:CountryofOrigin>
    <!--Optional:-->
    <orac:ChargeAccount></orac:ChargeAccount>
    <!--Optional:-->
    <orac:ShipmentAmount></orac:ShipmentAmount>
    <!--Optional:-->
    <orac:EncumberedFlag></orac:EncumberedFlag>
    <!--Optional:-->
    <orac:OPMShipmentSecondaryUOM></orac:OPMShipmentSecondaryUOM>
    <!--Optional:-->
    <orac:OPMShipmentSecondaryQuantity></orac:OPMShipmentSecondaryQuantity>
    <!--Optional:-->
    <orac:PreferredShipmentGrade></orac:PreferredShipmentGrade>
    <!--Optional:-->
    <orac:ReceiptCloseTolerance></orac:ReceiptCloseTolerance>
    <!--Optional:-->
    <orac:InvoiceCloseTolerance></orac:InvoiceCloseTolerance>
    <orac:MatchApprovalLevel>3WAY</orac:MatchApprovalLevel>
    <orac:InvoiceMatchOption>P</orac:InvoiceMatchOption>
    <!--Optional:-->
    <orac:AccrueatReceipt></orac:AccrueatReceipt>
    <!--Optional:-->
    <orac:Firm></orac:Firm>
    <!--Optional:-->
    <orac:Item></orac:Item>
    <!--Optional:-->
    <orac:Category></orac:Category>
    <!--Optional:-->
    <orac:Description></orac:Description>
    <!--Optional:-->
    <orac:VendorProductNum></orac:VendorProductNum>
    <!--Optional:-->
    <orac:ShipmentStatus></orac:ShipmentStatus>
    <!--Optional:-->
    <orac:QuantityReceived></orac:QuantityReceived>
    <!--Optional:-->
    <orac:QuantityCancelled></orac:QuantityCancelled>
    <!--Optional:-->
    <orac:QuanittyBilled></orac:QuanittyBilled>
    <!--Optional:-->
    <orac:AmountReceived></orac:AmountReceived>
    <!--Optional:-->
    <orac:AmountCancelled></orac:AmountCancelled>
    <!--Optional:-->
    <orac:AmountBilled></orac:AmountBilled>
    <!--Optional:-->
    <orac:OPMSecondaryQuantityReceived></orac:OPMSecondaryQuantityReceived>
    <!--Optional:-->
    <orac:OPMSecondaryCancelled></orac:OPMSecondaryCancelled>
    <orac:BreakPrice></orac:BreakPrice>
    <!--Optional:-->
    <orac:PriceDiscount></orac:PriceDiscount>
    <!--Optional:-->
    <orac:PriceBreakStartDate></orac:PriceBreakStartDate>
    <!--Optional:-->
    <orac:PriceBreakEndDate></orac:PriceBreakEndDate>
    <!--Optional:-->
    <orac:EarlyReceiptDays></orac:EarlyReceiptDays>
    <!--Optional:-->
    <orac:LateReceiptDays></orac:LateReceiptDays>
    <!--Optional:-->
    <orac:ReceiptDaysAction></orac:ReceiptDaysAction>
    <!--Optional:-->
    <orac:LastAcceptDate></orac:LastAcceptDate>
    <!--Optional:-->
    <orac:ReceiptTolerance></orac:ReceiptTolerance>
    <!--Optional:-->
    <orac:ReceiptToleranceAction></orac:ReceiptToleranceAction>
    <!--Optional:-->
    <orac:AllowSubstituteReceipts></orac:AllowSubstituteReceipts>
    <!--Optional:-->
    <orac:ReceiptRouting></orac:ReceiptRouting>
    <!--Optional:-->
    <orac:EnforceShipTo></orac:EnforceShipTo>
    <!--Optional:-->
    <orac:NoteforReceiver></orac:NoteforReceiver>
    <!--Optional:-->
    <orac:VMIEnabled></orac:VMIEnabled>
    <!--Optional:-->
    <orac:ConsignedShipment></orac:ConsignedShipment>
    <!--Zero or more repetitions:-->
    <orac:PoDistributions>
    <orac:DistributionNum>1</orac:DistributionNum>
    <orac:DestinationType>Expense</orac:DestinationType>
    <!--Optional:-->
    <orac:Requester></orac:Requester>
    <!--Optional:-->
    <orac:DeliverToLocation></orac:DeliverToLocation>
    <!--Optional:-->
    <orac:DestinationSubinventory></orac:DestinationSubinventory>
    <orac:DistributionQuantity>?</orac:DistributionQuantity>
    <!--Optional:-->
    <orac:DistributionAmount></orac:DistributionAmount>
    <!--Optional:-->
    <orac:POChargeAccount></orac:POChargeAccount>
    <!--Optional:-->
    <orac:DestinationChargeAccount></orac:DestinationChargeAccount>
    <!--Optional:-->
    <orac:RecoveryRate></orac:RecoveryRate>
    <!--Optional:-->
    <orac:GLDate></orac:GLDate>
    <!--Optional:-->
    <orac:EncumberedFlag></orac:EncumberedFlag>
    <!--Optional:-->
    <orac:RequestingOrganization></orac:RequestingOrganization>
    <!--Optional:-->
    <orac:RequisitionNum></orac:RequisitionNum>
    <!--Optional:-->
    <orac:RequisitionLineNum></orac:RequisitionLineNum>
    <!--Optional:-->
    <orac:OnlineRequisition></orac:OnlineRequisition>
    <!--Optional:-->
    <orac:RateDate></orac:RateDate>
    <!--Optional:-->
    <orac:Rate></orac:Rate>
    <!--Optional:-->
    <orac:POAccrualAccount></orac:POAccrualAccount>
    <!--Optional:-->
    <orac:POBudgetAccount></orac:POBudgetAccount>
    <!--Optional:-->
    <orac:POVarianceAccount></orac:POVarianceAccount>
    <!--Optional:-->
    <orac:ChargeAccountDescription></orac:ChargeAccountDescription>
    <!--Optional:-->
    <orac:BudgetAccountDescription></orac:BudgetAccountDescription>
    <!--Optional:-->
    <orac:AccrualAccountDescription></orac:AccrualAccountDescription>
    <!--Optional:-->
    <orac:VarianceAccountDescription></orac:VarianceAccountDescription>
    <!--Optional:-->
    <orac:Project></orac:Project>
    <!--Optional:-->
    <orac:Task></orac:Task>
    <!--Optional:-->
    <orac:Award></orac:Award>
    <!--Optional:-->
    <orac:ExpenditureType></orac:ExpenditureType>
    <!--Optional:-->
    <orac:ExpenditureOrganization></orac:ExpenditureOrganization>
    <!--Optional:-->
    <orac:ExpenditureDate></orac:ExpenditureDate>
    <!--Optional:-->
    <orac:ProjectsContractLineNum></orac:ProjectsContractLineNum>
    <!--Optional:-->
    <orac:ProjectsDeliverableNum></orac:ProjectsDeliverableNum>
    <!--Optional:-->
    <orac:EndItemUnitNum></orac:EndItemUnitNum>
    <!--Optional:-->
    <orac:DestinationChargeAccountDescription></orac:DestinationChargeAccountDescription>
    <!--Optional:-->
    <orac:DestinationVarianceAccountDescription></orac:DestinationVarianceAccountDescription>
    <!--Optional:-->
    <orac:DestinationVarianceAccount></orac:DestinationVarianceAccount>
    </orac:PoDistributions>
    </orac:PoShipments>
    </orac:PoLines>
    <!--Zero or more repetitions:-->
    <orac:PoBpaDistributions>
    <!--Optional:-->
    <orac:Encumber></orac:Encumber>
    <!--Optional:-->
    <orac:BudgetAccount></orac:BudgetAccount>
    <!--Optional:-->
    <orac:GLDate></orac:GLDate>
    <!--Optional:-->
    <orac:AmountToEncumber></orac:AmountToEncumber>
    </orac:PoBpaDistributions>
    <orac:OperatingUnit>Vision Operations</orac:OperatingUnit>
    <orac:PONum>6194</orac:PONum>
    <!--Optional:-->
    <orac:RevisionNum></orac:RevisionNum>
    <orac:DocumentType>Standard Purchase Order</orac:DocumentType>
    <!--Optional:-->
    <orac:CreationDate></orac:CreationDate>
    <!--Optional:-->
    <orac:Supplier></orac:Supplier>
    <!--Optional:-->
    <orac:SupplierSite></orac:SupplierSite>
    <!--Optional:-->
    <orac:SupplierContact></orac:SupplierContact>
    <!--Optional:-->
    <orac:ShipToLocation></orac:ShipToLocation>
    <!--Optional:-->
    <orac:BillToLocation></orac:BillToLocation>
    <!--Optional:-->
    <orac:Currency></orac:Currency>
    <orac:Buyer>31994</orac:Buyer>
    <!--Optional:-->
    <orac:Status></orac:Status>
    <!--Optional:-->
    <orac:POTotal></orac:POTotal>
    <!--Optional:-->
    <orac:AmounttAgreed></orac:AmounttAgreed>
    <!--Optional:-->
    <orac:HeaderDescription></orac:HeaderDescription>
    <!--Optional:-->
    <orac:PCard></orac:PCard>
    <!--Optional:-->
    <orac:AmountReleased></orac:AmountReleased>
    <!--Optional:-->
    <orac:GlobalAgreementFlag></orac:GlobalAgreementFlag>
    <!--Optional:-->
    <orac:PaymentTerms></orac:PaymentTerms>
    <!--Optional:-->
    <orac:FreightTerms></orac:FreightTerms>
    <!--Optional:-->
    <orac:Carrier></orac:Carrier>
    <!--Optional:-->
    <orac:FreeOnBoard></orac:FreeOnBoard>
    <!--Optional:-->
    <orac:PayOn></orac:PayOn>
    <!--Optional:-->
    <orac:TransportationArranged></orac:TransportationArranged>
    <!--Optional:-->
    <orac:ConfirmingOrder></orac:ConfirmingOrder>
    <!--Optional:-->
    <orac:Firm></orac:Firm>
    <!--Optional:-->
    <orac:AcceptanceRequired></orac:AcceptanceRequired>
    <!--Optional:-->
    <orac:AcceptanceDueDate></orac:AcceptanceDueDate>
    <!--Optional:-->
    <orac:SupplyAgreement></orac:SupplyAgreement>
    <!--Optional:-->
    <orac:SupplierNote></orac:SupplierNote>
    <!--Optional:-->
    <orac:ReceiverNote></orac:ReceiverNote>
    <!--Optional:-->
    <orac:EffectiveStartDate></orac:EffectiveStartDate>
    <!--Optional:-->
    <orac:EffectiveEndDate></orac:EffectiveEndDate>
    <!--Optional:-->
    <orac:AmountLimit></orac:AmountLimit>
    <!--Optional:-->
    <orac:MinimumHeaderReleaseAmount></orac:MinimumHeaderReleaseAmount>
    <!--Optional:-->
    <orac:PriceUpdateTolerance></orac:PriceUpdateTolerance>
    <orac:PoHeaderId>91781</orac:PoHeaderId>
    </orac:PoHeaders>
    </pox:queryPurchaseOrder_Request>
    </soapenv:Body>
    </soapenv:Envelope>
    Now when i run this, I get the below error in the SOAP UI Tool:
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header/>
    <env:Body>
    <Error>[Ljava.lang.StackTraceElement;@118da51</Error>
    </env:Body>
    </env:Envelope>
    Can u please suggest any solution to resolve this error.
    Thanks & Regards,
    Aboothahir M

    Hello All,
    I checked in the log.xml file in the apps server and got the below error:
    <MESSAGE>
    <HEADER>
    <TSTZ_ORIGINATING>2012-01-18T16:50:24.110+05:30</TSTZ_ORIGINATING>
    <COMPONENT_ID>j2ee</COMPONENT_ID>
    <MSG_TYPE TYPE="ERROR"></MSG_TYPE>
    <MSG_LEVEL>1</MSG_LEVEL>
    <HOST_ID>amsgurbluapp009.in.ibm.com</HOST_ID>
    <HOST_NWADDR>9.126.177.20</HOST_NWADDR>
    <MODULE_ID>security</MODULE_ID>
    <THREAD_ID>12</THREAD_ID>
    <USER_ID>orar12</USER_ID>
    </HEADER>
    <CORRELATION_DATA>
    <EXEC_CONTEXT_ID><UNIQUE_ID>1326885623:9.126.177.20:24571:0:38</UNIQUE_ID><SEQ>5</SEQ></EXEC_CONTEXT_ID>
    </CORRELATION_DATA>
    <PAYLOAD>
    <MSG_TEXT>Error when intializing assertion issuer context </MSG_TEXT>
    <SUPPL_DETAIL><![CDATA[java.lang.IllegalArgumentException: Invalid assertion
         at oracle.security.jazn.callback.SAMLTokenCallbackInternal.setAssertion(SAMLTokenCallbackInternal.java:70)
         at oracle.security.jazn.callback.WSSCallbackHandler.handle(WSSCallbackHandler.java:107)
         at javax.security.auth.login.LoginContext$SecureCallbackHandler$1.run(LoginContext.java:955)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.login.LoginContext$SecureCallbackHandler.handle(LoginContext.java:951)
         at oracle.security.jazn.login.module.saml.SAMLLoginModule.initializeAssertionIssuerContext(SAMLLoginModule.java:278)
         at oracle.security.jazn.login.module.saml.SAMLLoginModule.initializeProperties(SAMLLoginModule.java:233)
         at oracle.security.jazn.login.module.saml.SAMLLoginModule.initialize(SAMLLoginModule.java:91)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at javax.security.auth.login.LoginContext.invoke(LoginContext.java:756)
         at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
         at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
         at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
         at oracle.security.wss.jaas.JAASAuthManager.invokeLogin(JAASAuthManager.java:109)
         at oracle.security.wss.jaas.JAASAuthManager.authenticate(JAASAuthManager.java:174)
         at oracle.security.wss.UsernameTokenProcessor.getSubject(UsernameTokenProcessor.java:143)
         at oracle.security.wss.WSSecurity.process(WSSecurity.java:1107)
         at oracle.security.wss.interceptors.AbstractSecurityInterceptor.handleInbound(AbstractSecurityInterceptor.java:131)
         at oracle.security.wss.interceptors.ServiceInterceptor.handleRequest(ServiceInterceptor.java:60)
         at oracle.j2ee.ws.common.mgmt.runtime.InterceptorChainImpl.handleRequest(InterceptorChainImpl.java:124)
         at oracle.j2ee.ws.common.mgmt.runtime.AbstractInterceptorPipeline.handleRequest(AbstractInterceptorPipeline.java:87)
         at oracle.j2ee.ws.server.provider.management.AbstractProviderInterceptorPipeline.executeRequestInterceptorChain(AbstractProviderInterceptorPipeline.java:452)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.executeInterceptorRequestChain(ProviderProcessor.java:750)
         at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:112)
         at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
         at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:194)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
         at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
         at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:619)
    ]]></SUPPL_DETAIL>
    </PAYLOAD>
    </MESSAGE>
    <MESSAGE>
    <HEADER>
    <TSTZ_ORIGINATING>2012-01-18T16:50:25.524+05:30</TSTZ_ORIGINATING>
    <COMPONENT_ID>webservices</COMPONENT_ID>
    <MSG_ID>OWS-04005</MSG_ID>
    <MSG_TYPE TYPE="ERROR"></MSG_TYPE>
    <MSG_LEVEL>1</MSG_LEVEL>
    <HOST_ID>amsgurbluapp009.in.ibm.com</HOST_ID>
    <HOST_NWADDR>9.126.177.20</HOST_NWADDR>
    <MODULE_ID>service</MODULE_ID>
    <THREAD_ID>14</THREAD_ID>
    <USER_ID>orar12</USER_ID>
    </HEADER>
    <CORRELATION_DATA>
    <EXEC_CONTEXT_ID><UNIQUE_ID>1326885621:9.126.177.20:24505:0:46</UNIQUE_ID><SEQ>6</SEQ></EXEC_CONTEXT_ID>
    </CORRELATION_DATA>
    <PAYLOAD>
    <MSG_TEXT>An error occurred for port: SOAProvider: oracle.j2ee.ws.common.soap.fault.SOAP11FaultException: The security token could not be authenticated or authorized.</MSG_TEXT>
    </PAYLOAD>
    </MESSAGE>
    <MESSAGE>
    <HEADER>
    <TSTZ_ORIGINATING>2012-01-18T16:50:25.527+05:30</TSTZ_ORIGINATING>
    <COMPONENT_ID>webservices</COMPONENT_ID>
    <MSG_ID>OWS-04005</MSG_ID>
    <MSG_TYPE TYPE="ERROR"></MSG_TYPE>
    <MSG_LEVEL>1</MSG_LEVEL>
    <HOST_ID>amsgurbluapp009.in.ibm.com</HOST_ID>
    <HOST_NWADDR>9.126.177.20</HOST_NWADDR>
    <MODULE_ID>service</MODULE_ID>
    <THREAD_ID>12</THREAD_ID>
    <USER_ID>orar12</USER_ID>
    </HEADER>
    <CORRELATION_DATA>
    <EXEC_CONTEXT_ID><UNIQUE_ID>1326885623:9.126.177.20:24571:0:38</UNIQUE_ID><SEQ>6</SEQ></EXEC_CONTEXT_ID>
    </CORRELATION_DATA>
    <PAYLOAD>
    <MSG_TEXT>An error occurred for port: SOAProvider: oracle.j2ee.ws.common.soap.fault.SOAP11FaultException: The security token could not be authenticated or authorized.</MSG_TEXT>
    </PAYLOAD>
    </MESSAGE>
    <MESSAGE>
    <HEADER>
    <TSTZ_ORIGINATING>2012-01-18T16:56:08.311+05:30</TSTZ_ORIGINATING>
    <COMPONENT_ID>webservices</COMPONENT_ID>
    <MSG_ID>OWS-04052</MSG_ID>
    <MSG_TYPE TYPE="NOTIFICATION"></MSG_TYPE>
    <MSG_LEVEL>1</MSG_LEVEL>
    <HOST_ID>amsgurbluapp009.in.ibm.com</HOST_ID>
    <HOST_NWADDR>9.126.177.20</HOST_NWADDR>
    <MODULE_ID>service</MODULE_ID>
    <THREAD_ID>13</THREAD_ID>
    <USER_ID>orar12</USER_ID>
    </HEADER>
    <CORRELATION_DATA>
    <EXEC_CONTEXT_ID><UNIQUE_ID>1326885960:9.126.177.20:23538:0:57</UNIQUE_ID><SEQ>242</SEQ></EXEC_CONTEXT_ID>
    </CORRELATION_DATA>
    <PAYLOAD>
    <MSG_TEXT>Unable to determine operation id from SOAP Message.</MSG_TEXT>
    </PAYLOAD>
    </MESSAGE>
    By
    Aboo

Maybe you are looking for

  • CD Burn Error"4280" -- My Story and Happy Ending

    First--a little background: Today I realized that it was two weeks since I backed up my iTunes folder. I'm planning to install a new (larger) secondary hard disk because I need more storage space. Since I need to get all files off my current backup d

  • Premiere only recognizes 15 seconds of my 15 minute shot!! =[

    Okay, so I'm editng on a PC, Windows 7 64 Bit, Adobe Premiere Pro CS5. I love everything about windows 7 and CS5. I have a project in premiere that I was working with in CS4, i opened it in cs5 and everything is working just as it was in cs4. I rende

  • Can i use itunes radio without wifi like while driving in my car?

    can i use itunes radio without sifi like while driving in my car?

  • Why does DVD Studio Pro compress my 3GB video?

    I thought since the original Quicktime movie I made with FCP was under the 4.7(?) capacity of a DVD, that Studio Pro wouldn't compress my 3GB movie. But after import to DVD Studio Pro the whole project only shows up as using 350MB of space. And when

  • What does a globe at the folder icon mean?

    When I installed RH9 or at least after I imported my first project into RH9 I got a folder under \Users\me\Documente\Eigene Robohelp Projekte This folder appears with a globe symbol attached to the folder icon? What is the special meaning of that fol